A method and apparatus for preserving order of multi-source data streams

Abstract

This application provides a method and apparatus for preserving the order of multi-source data streams. The method includes: in response to a reception request for a first data packet, determining a first source data stream of the first data packet; the first source data stream corresponds to one of three order preservation types: an irrelevant data stream without order preservation requirements, a data stream to be ordered with order preservation requirements, and a related data stream affecting the order preservation of the data stream to be ordered; if the order preservation type corresponding to the first source data stream of the first data packet is a data stream to be ordered, then obtaining a common counter value corresponding to the related data stream affecting the order preservation of the first data packet; setting the latch counter value corresponding to the first data packet to the common counter value; and setting the first data packet to be disallowed from transmission when the latch counter value of the first data packet is not 0. The technical solution of this application saves hardware overhead and improves performance.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of chips, and particularly relates to a multi-source data stream order preserving method and device. BACKGROUND

[0002] With the increasing complexity of chip systems, the correlation processing between multi-source data streams is particularly important. Some data stream processing has little effect on the performance of the system, and some must meet the performance requirements while meeting the constraints of correlation processing, which is particularly important in system processing.

[0003] The related art usually adopts an order preserving processing method of constraint software interface or hardware timestamp. The order preserving method of sampling constraint software interface has certain influence on the flexibility and universality of use. The method generally adopts a compiler tool to support analysis, has constraints on application scenarios, and will inevitably increase the delay of data stream processing. The order preserving processing method of hardware timestamp has certain limitations on order preserving performance, timestamp design bit width and corresponding timestamp overflow time. SUMMARY

[0004] The application aims to provide a multi-source data stream order preserving method and device, and aims to solve the technical problems of large hardware resource consumption, influence on data stream bandwidth and delay of the order preserving scheme of data stream in the related art.

[0005] According to a first aspect of the application, a multi-source data stream order preserving method is provided, comprising:

[0006] In response to a receiving request of a first data packet, determining a first source data stream of the first data packet; the first source data stream corresponds to one of the following three order preserving types: irrelevant data stream without order preserving correlation requirement, data stream to be preserved with order preserving requirement, and relevant data stream affecting order preservation of the data stream to be preserved;

[0007] If the first source data stream of the first data packet corresponds to the data stream to be preserved, a public counter value corresponding to the relevant data stream affecting order preservation of the first data packet is obtained;

[0008] The latch counter value corresponding to the first data packet is set as the public counter value;

[0009] When the latch counter value of the first data packet is not 0, the first data packet is set as not allowed to be sent.

[0010] In an optional embodiment, after determining the first source data stream of the first data packet, the method further comprises:

[0011] If the first source data stream of the first data message corresponds to a relevant data stream, a public counter value corresponding to the first source data stream is increased by 1.

[0012] In an optional embodiment, the method further comprises:

[0013] In response to a sending request of a second data message, determining a second source data stream of the second data message;

[0014] If the second source data stream corresponds to a relevant data stream, a public counter value corresponding to the second source data stream is decreased by 1, and a latch counter value corresponding to each to-be-sequenced data message not sent out in a to-be-sequenced data stream affected by the second source data stream is decreased by 1.

[0015] In an optional embodiment, after the latch counter value corresponding to each to-be-sequenced data message not sent out in the to-be-sequenced data stream affected by the second source data stream is decreased by 1, the method further comprises:

[0016] If a to-be-sequenced data message with a latch counter value of 0 appears, the to-be-sequenced data message with the latch counter value of 0 is set as allowed to be sent.

[0017] In an optional embodiment, after the second source data stream of the second data message is determined, the method further comprises:

[0018] If the second source data stream of the second data message corresponds to a to-be-sequenced data stream, it is determined whether the second data message is allowed to be sent;

[0019] If the second data message is allowed to be sent, the second data message is sent.

[0020] According to a second aspect of the present application, a multi-source data stream sequencing device is provided, comprising:

[0021] A first determining module is configured to determine a first source data stream of a first data message in response to a receiving request of the first data message; the first source data stream corresponds to one of the following three sequencing types: an irrelevant data stream without sequencing correlation requirement, a to-be-sequenced data stream with sequencing requirement, and a relevant data stream affecting sequencing of the to-be-sequenced data stream;

[0022] A first setting module is configured to set a latch counter value corresponding to the first data message as a public counter value corresponding to the relevant data stream affecting sequencing of the first data message.

[0023] A first setting module is configured to set a latch counter value corresponding to the first data message as a public counter value corresponding to the relevant data stream affecting sequencing of the first data message.

[0024] The second setting module is configured to set the first data packet as not allowed to be sent when the latch counter value of the first data packet is not 0.

[0025] In an optional implementation, after the first determining module, the apparatus further includes:

[0026] The first counting module is configured to increase the public counter value corresponding to the first source data flow by 1 if the order-preserving type corresponding to the first source data flow is a relevant data flow.

[0027] In an optional implementation, the apparatus further includes:

[0028] The second determining module is configured to determine a second source data flow of a second data packet in response to a sending request of the second data packet.

[0029] The second counting module is configured to decrease the public counter value corresponding to the second source data flow by 1 if the order-preserving type corresponding to the second source data flow is a relevant data flow, and decrease the latch counter value corresponding to each to-be-order-preserved data packet that has not been sent out in a to-be-order-preserved data flow affected by the second source data flow by 1.

[0030] In an optional implementation, after the second counting module, the apparatus further includes:

[0031] The third setting module is configured to set the to-be-order-preserved data packet with the latch counter value becoming 0 as allowed to be sent if the to-be-order-preserved data packet with the latch counter value becoming 0 exists.

[0032] In an optional implementation, after the second determining module, the apparatus further includes:

[0033] The judging module is configured to judge whether the second data packet is allowed to be sent if the order-preserving type corresponding to the second source data flow of the second data packet is a to-be-order-preserved data flow.

[0034] The sending module is configured to send the second data packet if the second data packet is allowed to be sent.

[0035] Compared with the related art, the technical solution of the present application has at least the following advantages:

[0036] 1. For the hardware resource overhead of the data flow source to the order-preserving processing module in the related art, the above-mentioned solution of the present application can reduce the hardware resource overhead related to the time stamp in the upstream data flow transmission since the time stamp order-preserving solution is not adopted. Especially for a system with a long data transmission path, a larger hardware resource overhead can be reduced, and the design is more friendly to low power consumption.

[0037] 2、For the order related to the OD data flow can reduce the delay, using the above scheme of the application, because the control of the data flow OD to be ordered is at the outlet, relative to the source of the order scheme does not need to wait for OA data flow transmission is completed, so the delay of OD data flow can be effectively reduced, for the performance of OD data flow related to more friendly.

[0038] Other features and advantages of the present application will be set forth in the following description, and in part will become apparent to those skilled in the art from the description, or can be learned by practice of the present application. The objects and other advantages of the present application can be realized and obtained by the structure and process indicated in the specification and drawings. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the embodiments or the related art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0040] Figure 1 is a flow diagram of a multi-source data flow ordering method according to an exemplary embodiment of the present application.

[0041] Figure 2 is a schematic diagram of the ordering method of three types of data flow according to an exemplary embodiment of the present application.

[0042] Figure 3 is an event control execution flow diagram of OA data flow according to an exemplary embodiment of the present application.

[0043] Figure 4 is an event control execution flow diagram of OD data flow according to an exemplary embodiment of the present application.

[0044] Figure 5 is a structural block diagram of a multi-source data flow ordering device according to an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical scheme and advantages of the embodiments of the present application more clear, the technical scheme in the embodiments of the present application will be clearly and completely described below in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0046] The related art also adopts a data stream request source order preservation scheme, which supports order preservation requirements through software or hardware communication for two-way data stream requests requiring order preservation.

[0047] In the timestamp order preservation scheme, the multiple-source data stream sources with order preservation correlation carry timestamps in data stream transmission. For multiple-source data streams, data streams requiring maintenance of order preservation all need to carry order preservation timestamp information. If the out-of-order capability of the data stream requiring order preservation is large, a hardware overhead of a large bit width order preservation timestamp is required. In this order preservation scheme, if the order preservation data stream is large, the hardware processing of data path correlation may have congestion and timing convergence. At the same time, there is a large hardware overhead from the data stream source node to the destination node requiring order preservation processing. Therefore, this scheme requires the data stream source to carry a timestamp to the order preservation control target node, which has a certain impact on hardware overhead and power consumption.

[0048] The data source order preservation scheme is generally applied in scenarios with low performance and delay requirements. This scheme adopts block processing of order preservation data streams with correlation, and waits for the completion of previous data stream transmission before issuing order preservation correlation data streams. Therefore, this scheme is not friendly to data stream processing requiring order preservation, and has a great impact on data stream bandwidth and the delay of order preservation correlation data stream issuance.

[0049] Therefore, the present application proposes a data stream order preservation method to solve the above problems in the related art. In this method, the data source does not need to carry a timestamp, and only needs to be processed at the control node requiring order preservation. According to the data source type, the data source is divided into three categories: a data stream to be preserved (a data stream that needs to be sent out after the current received data stream OA is sent out, described as OD hereinafter), a data stream to be preserved related data stream (described as OA hereinafter), and a data stream to be preserved unrelated data stream (described as NO hereinafter).

[0050] According to the three types of attributes of data stream order preservation correlation, different order preservation methods are used to control the flow, so as to meet the order preservation requirements. For the OD data stream, a public count of the number of completed data stream packets received is set; for the OA data stream, the number of OD data streams corresponding to the OA data stream is recorded to ensure the correlation between the OA data stream and the OD data stream; and the NO data stream does not need special processing because it has no order preservation correlation. This order preservation method does not need to count the OD data stream separately, and the use of the common counting method can effectively reduce the hardware overhead.

[0051] Referring to Figure 1 The present application exemplarily provides a multiple-source data stream order preservation method, which includes:

[0052] In step S101, in response to a receiving request of the first data message, a first source data flow of the first data message is determined; the first source data flow corresponds to one of the following three ordered types: an irrelevant data flow without ordered correlation requirement, a data flow to be ordered with ordered requirement, and a related data flow affecting ordered of the data flow to be ordered;

[0053] In step S102, if the first source data flow of the first data message corresponds to the data flow to be ordered with ordered requirement, a public counter value corresponding to the related data flow affecting ordered of the first data message is obtained;

[0054] In step S103, a latch counter value corresponding to the first data message is set as the public counter value;

[0055] In step S104, when the latch counter value of the first data message is not 0, the first data message is set as not allowed to be sent.

[0056] Exemplarily, the application divides data flows into three ordered types according to ordered requirements: an irrelevant data flow without ordered correlation requirement, a data flow to be ordered with ordered requirement, and a related data flow affecting ordered of the data flow to be ordered. The irrelevant data flow without ordered correlation requirement is a data flow without ordered requirement and without affecting other data flows to be ordered, which is referred to as an ON data flow hereinafter. The data flow to be ordered with ordered requirement is a data flow with ordered requirement, which is referred to as an OD data flow hereinafter. The related data flow is a data flow without ordered requirement but affecting ordered of the data flow to be ordered, which is referred to as an OA data flow hereinafter. The OA data flow affects ordered of the OD data flow, so that an OD data message from the OD data flow needs to be sent after all OA data messages in the OA data flow received before the OD data message are sent, so as to ensure correct forwarding order of the OD data message in the OD data flow.

[0057] Exemplarily, in order to realize ordered of data flows, the OA data flow sets a public counter storing a public counter value cntr_com, which is used to record number of OA data messages in the OA data flow received currently and not sent out. When an OA data message from the OA data flow is received, the public counter value cntr_com is increased by 1, and when an OA data message from the OA data flow is sent out, the public counter value cntr_com is decreased by 1.

[0058] Exemplarily, referring to Figure 2As shown, upon receiving a request for a first data packet, the system determines the type of data stream from which the first data packet originates, i.e., the first source data stream of the first data packet. If the first source data stream is an OD data stream, the counter value in the common counter value cntr_com corresponding to the OA data stream affecting the first source data stream is latched into the latch counter value cntr_latch[i] corresponding to the first data packet (where i represents the i-th packet in the first source data stream currently received that needs to be kept in order). cntr_latch[i] is used to latch the number of OA data packets in the OA data stream affecting the order of the currently received first data packet. The maximum number of cntr_latch[i] depends on the maximum out-of-order capability of the OD data stream. After an OA data packet in the OA data stream is sent out, if cntr_latch[i] is greater than 0, it is decremented by 1 until it reaches 0. If cntr_latch[i] is 0, then the OD data packet corresponding to cntr_latch[i] is set to allow transmission; otherwise, transmission is not allowed.

[0059] For example, a NO data stream is an irrelevant data stream without order-preserving requirements, and its corresponding data stream does not require special processing. That is, when the first source data stream of the first data packet in the receiving request is a NO data stream, the first data packet can be stored directly.

[0060] It should be noted that different data streams originate from different data receiving channels. Data packets received from the same data receiving channel belong to the same source data stream, and data packets from the same source data stream will be sent out from the corresponding same data sending channel. Therefore, the different data streams in this application refer to data streams from different sources.

[0061] This application can effectively reduce the hardware resource overhead of upstream data streams and reduce the latency of OD data streams by using a sequence-preserving scheme with the common counter value cntr_com, thereby improving performance.

[0062] In some alternative implementations, after determining the first source data stream of the first data packet, the method further includes:

[0063] If the order-preserving type corresponding to the first source data stream of the first data packet is related data stream, then the common counter value corresponding to the first source data stream is incremented by 1.

[0064] For example, see Figure 3 As shown, the OA data stream receiving process is as follows:

[0065] Event T1: A message is received from the OA data stream, then the corresponding cntr The com counter increases by 1.

[0066] Event T2: Sending a data packet from the OA data stream, then the corresponding cntr The com counter decreases by 1.

[0067] Event T3: If a data packet from the OA data stream is received and a data packet from the OA data stream is sent simultaneously, the value of the cntr com counter remains unchanged.

[0068] It should be noted that cntr The design of the COM counter's bit width relies on the maximum number of data packets it can support, ensuring that the counter's count value will never overflow.

[0069] In some alternative implementations, the method also includes:

[0070] In response to the request to send a second data packet, determine the second source data stream of the second data packet;

[0071] If the order preservation type corresponding to the second source data stream is a related data stream, then the common counter value corresponding to the second source data stream is decremented by 1, and the latch counter value corresponding to each unsent data packet in the order preservation data stream affected by the second source data stream is decremented by 1.

[0072] For example, as described above, sending an OA data message in an OA data stream decrements the value of the common counter corresponding to that OA data stream by 1. Furthermore, changes in this common counter value also affect the latch counter values ​​of individual data messages in an OD data stream. See [link to relevant documentation] Figure 4 As shown, for example, the specific events of OD data flow control are described as follows:

[0073] Event T4: An OD data packet is received from the OD data stream. The corresponding common counter value (cntr_com) is latched into the latch counter value (cntr_latch[i]) corresponding to the OD data packet of the OD data stream. Here, cntr_latch[i] represents the number of OA packets with order-preserving dependency for the OD of the current data stream in the current buffer; cntr_com represents the number of packets of all current OAs; therefore, cntr_latch[i] is less than or equal to cntr_com.

[0074] Event T5: When an OA data message is sent out in the OA data stream, the cntr_latch[i] corresponding to all OD data messages in the OD data stream affected by the OA data stream is decremented by 1.

[0075] Event T6: After decrementing cntr_latch[i] by 1, it is necessary to determine whether cntr_latch[i] is 0. If it is 0, then the OD data packet corresponding to cntr_latch[i] set to 0 is allowed to be sent.

[0076] It should be noted that the bit width of cntr_latch[i] is the same as that of cntr_com, and the number of cntr_latch depends on the maximum out-of-order capability of the OD data stream channel.

[0077] For example, as described above, a NO data stream is an irrelevant data stream without order-keeping requirements. Therefore, if the second source data stream of the second data packet in the sending request is a NO data stream, the second data packet can be sent directly.

[0078] In some optional implementations, after decrementing the latch counter value of each unsent data packet in the pending order data stream affected by the second source data stream by 1, the method further includes:

[0079] If a pending data packet with a latch counter value of 0 is encountered, then the pending data packet with a latch counter value of 0 is set to be allowed to be sent.

[0080] For example, as described above, after decrementing cntr_latch[i] by 1, it is necessary to determine whether cntr_latch[i] is 0. If it is 0, it means that all OA data packets affecting the OD data packet corresponding to cntr_latch[i] have been sent out. Therefore, the OD data packet can also be sent out, and thus the OD data packet is allowed to be sent.

[0081] In some alternative implementations, after determining the second source data stream of the second data packet, the method further includes:

[0082] If the order preservation type corresponding to the second source data stream of the second data packet is a data stream to be ordered, then determine whether the second data packet is allowed to be sent;

[0083] If the second data packet is allowed to be sent, then the second data packet is sent.

[0084] For example, as described above, if the second data packet to be sent is a data packet from the OA data stream, then the common counter value corresponding to the OA data stream is decremented by 1, and the data packet is sent out. However, if the second data packet to be sent is a data packet from the OD data stream, then it is necessary to first determine whether the second data packet is set to be allowed to be sent. If it is set to be allowed to be sent, then the second data packet is sent out; otherwise, the second data packet is not sent.

[0085] The above-mentioned solution in this application can solve the defects and shortcomings of related data flow order preservation solutions, as follows:

[0086] 1. Regarding the hardware resource overhead from the data stream source to the order preservation processing module in related technologies, the above-mentioned solution in this application, by not employing a timestamp-based order preservation scheme, can reduce the hardware resource overhead related to timestamps in the upstream data stream transmission. This is particularly beneficial for systems with long data transmission paths, significantly reducing hardware resource overhead and making it more suitable for low-power designs.

[0087] 2. For OD data streams related to order preservation, latency can be reduced. By adopting the above-mentioned scheme of this application, since the control of the OD of the data stream to be preserved is at the data stream exit, it does not need to wait for the OA data stream to be transmitted to complete, compared with the source preservation scheme. Thus, the latency of the OD data stream can be effectively reduced, which is more friendly to improving the performance of OD data streams.

[0088] Accordingly, see Figure 5 As shown, this application exemplarily proposes a multi-source data stream order preservation device, comprising:

[0089] The first determining module 501 is used to determine the first source data stream of the first data stream in response to the receiving request of the first data stream; the first source data stream corresponds to one of the following three order preservation types: irrelevant data stream without order preservation relevance requirements, data stream to be ordered with order preservation requirements, and relevant data stream that affects the order preservation of the data stream to be ordered.

[0090] The acquisition module 502 is used to acquire the common counter value corresponding to the relevant data stream that affects the ordering of the first data packet if the ordering type corresponding to the first source data stream of the first data packet is a data stream to be ordered.

[0091] The first setting module 503 is used to set the latch counter value corresponding to the first data message to a common counter value;

[0092] The second setting module 504 is used to set the first data packet to be disallowed when the latch counter value of the first data packet is not 0.

[0093] In some alternative implementations, after the first determining module, the device further includes:

[0094] The first counting module is used to increment the common counter value corresponding to the first source data stream by 1 if the order-preserving type corresponding to the first source data stream of the first data packet is a related data stream.

[0095] In some alternative implementations, the apparatus also includes:

[0096] The second determining module is used to determine the second source data stream of the second data packet in response to the sending request of the second data packet;

[0097] The second counting module is used to decrement the common counter value corresponding to the second source data stream by 1 if the order preservation type corresponding to the second source data stream is a related data stream, and to decrement the latch counter value corresponding to each unsent data packet in the order preservation data stream affected by the second source data stream by 1.

[0098] In some alternative implementations, after the second counting module, the device further includes:

[0099] The third setting module is used to set the pending sequence data message whose latch counter value becomes 0 to allow transmission if a pending sequence data message whose latch counter value becomes 0 is found.

[0100] In some alternative implementations, after the second determining module, the apparatus further includes:

[0101] The judgment module is used to determine whether the second data packet is allowed to be sent if the ordering type corresponding to the second source data stream of the second data packet is a data stream to be ordered.

[0102] The sending module is used to send the second data packet if the second data packet is allowed to be sent.

[0103] The above-mentioned device can be implemented by the multi-source data stream order preservation method provided in the above embodiments. For the specific implementation method, please refer to the description of the multi-source data stream order preservation method in the above embodiments, which will not be repeated here.

[0104] It is understood that the circuit structures, names, and parameters described in the above embodiments are merely examples. Those skilled in the art can also make readily conceived combinations and adjustments to the structural features of the above embodiments according to their needs, and the concept of this application should not be limited to the specific details of the above examples.

[0105] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for preserving the order of multi-source data streams, characterized in that, The method comprises the following steps: determining a first source data stream of the first data message in response to a receiving request of the first data message; the first source data stream corresponds to one of the following three ordered types: irrelevant data stream without ordered correlation requirement, ordered data stream to be ordered, and relevant data stream affecting ordered data stream to be ordered; if the first source data stream of the first data message corresponds to the ordered data stream to be ordered, obtaining a public counter value corresponding to the relevant data stream affecting the ordered data stream of the first data message; setting the latch counter value corresponding to the first data message as the public counter value; setting the first data message as not allowed to send when the latch counter value of the first data message is not 0; determining a second source data stream of the second data message in response to a sending request of the second data message; if the second source data stream corresponds to the relevant data stream, reducing the public counter value corresponding to the second source data stream by 1, and reducing the latch counter value corresponding to each ordered data message to be ordered in the ordered data stream to be ordered affected by the second source data stream by 1; wherein, after determining the first source data stream of the first data message, the method further comprises: if the first source data stream of the first data message corresponds to the relevant data stream, increasing the public counter value corresponding to the first source data stream by 1.

2. The multiple source data flow order preserving method of claim 1, wherein, after reducing the latch counter value corresponding to each ordered data message to be ordered in the ordered data stream to be ordered affected by the second source data stream by 1, the method further comprises: if there is an ordered data message to be ordered with a latch counter value of 0, setting the ordered data message to be ordered with the latch counter value of 0 as allowed to send.

3. The multiple source data flow order preserving method of claim 1, wherein, after determining the second source data stream of the second data message, the method further comprises: if the second source data stream of the second data message corresponds to the ordered data stream to be ordered, judging whether the second data message is allowed to send; if the second data message is allowed to send, sending the second data message.

4. A multi-source data flow order preserving apparatus, characterized by, The method comprises the following steps: a first determination module is configured to determine a first source data stream of the first data message in response to a receiving request of the first data message; the first source data stream corresponds to one of the following three ordered types: irrelevant data stream without ordered correlation requirement, ordered data stream to be ordered, and relevant data stream affecting ordered data stream to be ordered; an acquisition module is configured to obtain a public counter value corresponding to the relevant data stream affecting the ordered data stream of the first data message if the first source data stream of the first data message corresponds to the ordered data stream to be ordered; a first setting module is configured to set the latch counter value corresponding to the first data message as the public counter value; a second setting module is configured to set the first data message as not allowed to send when the latch counter value of the first data message is not 0; a second determination module is configured to determine a second source data stream of the second data message in response to a sending request of the second data message; if the second source data stream corresponds to the relevant data stream, reducing the public counter value corresponding to the second source data stream by 1, and reducing the latch counter value corresponding to each ordered data message to be ordered in the ordered data stream to be ordered affected by the second source data stream by 1; a second counting module, configured to decrease, if the ordered type corresponding to the second source data stream is a dependent data stream, a public counter value corresponding to the second source data stream by 1, and decrease, for each to-be-ordered data packet in a to-be-ordered data stream affected by the second source data stream and not sent out, a latch counter value corresponding to the to-be-ordered data packet by 1; wherein, after the first determining module, the device further comprises: a first counting module, configured to increase, if the ordered type corresponding to the first source data stream of the first data packet is a dependent data stream, a public counter value corresponding to the first source data stream by 1.

5. The multiple source data flow preserving order apparatus of claim 4, wherein, after the second counting module, the device further comprises: a third setting module, configured to set, if there is a to-be-ordered data packet with a latch counter value of 0, the to-be-ordered data packet with the latch counter value of 0 as allowed to be sent.

6. The multiple source data flow preserving device of claim 4, wherein, after the second determining module, the device further comprises: a judging module, configured to judge, if the ordered type corresponding to the second source data stream of the second data packet is a to-be-ordered data stream, whether the second data packet is allowed to be sent; a sending module, configured to send the second data packet, if the second data packet is allowed to be sent.

Images