Method and equipment for processing data flow

[0054] The embodiment of the present invention provides a data stream processing method, which can increase the speed of data stream processing. The embodiment of the present invention also provides corresponding equipment. Detailed descriptions are given below.

[0055] Refer to figure 1 , An embodiment of the data stream processing method provided by the embodiment of the present invention includes:

[0056] 101. The first processing module receives a service data stream, and assigns a data stream identifier to the service data stream.

[0057] 102. The first processing module sends the service data stream with the data stream identifier to the second processing module;

[0058] 103. After the second processing module receives the service data stream with the data stream identifier, it determines the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and combines The service data stream with the data stream identifier is pushed to the ROHC entity for ROHC compression.

[0059] In the embodiment of the present invention, a first processing module is used to receive a service data stream, and a data stream identifier is assigned to the service data stream; the first processing module sends a service data stream with the data stream identifier to the second processing module; After the second processing module receives the service data stream with the data stream identifier, it determines the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and combines the data stream identifier with The service data stream with the data stream identifier is pushed to the ROHC entity for ROHC compression. Compared with the comparison of multiple bytes in each processing flow in the prior art, the embodiment of the present invention uses the data flow identification directly in other modules to distinguish different services after performing a service data flow identification identification. Data flow, thereby improving the efficiency of data flow processing.

[0060] Optionally, in the above figure 1 Based on the corresponding embodiment, another embodiment of the data stream processing method provided in the embodiment of the present invention includes:

[0061] The first processing module assigning a data flow identifier to the service data flow specifically includes: the first processing module compares the header information in the service data flow with the parameters of the packet filter PF; the first When the processing module compares the PF that matches the header information in the service data flow, it assigns the data flow identifier corresponding to the PF to the service data flow; the first processing module does not compare with the service data flow. When the header information in the data stream matches the PF, the parameters in the header information of the service data stream are recorded as new PF parameters, and corresponding to the new PF parameters, a new PF is created, and a new PF is created for the The service data stream is assigned an unused service data stream identifier.

[0062] Optionally, in the above figure 1 and figure 1 On the basis of the corresponding optional embodiment, the second processing module determines the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and combines the data stream identifier with the robust header compression ROHC entity Pushing the service data stream to the ROHC entity for ROHC compression specifically includes: the second processing module searches for the corresponding CID from the pre-stored data stream identifier and the channel identifier CID according to the data stream identifier. ROHC entity; when the second processing module finds the ROHC entity corresponding to the data stream identifier, push the service data stream with the data stream identifier to the ROHC entity for ROHC compression.

[0063] Optionally, in the above figure 1 and figure 1 On the basis of the corresponding optional embodiment, the second processing module determines the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and combines the data stream identifier with the robust header compression ROHC entity Pushing the service data stream to the ROHC entity for ROHC compression specifically includes: the second processing module searches for the ROHC entity corresponding to the CID from the pre-stored correspondence between the data stream identifier and the CID according to the data stream identifier When the second processing module does not find the ROHC entity corresponding to the data stream identifier, it creates a new ROHC entity, and pushes the service data stream with the data stream identifier to the newly created ROHC compression is performed in the ROHC entity.

[0064] The second processing module allocates a channel identifier CID to the newly created ROHC entity, and stores the data stream identifier and the CID correspondingly.

[0065] To facilitate understanding, the following takes a specific application scenario as an example to describe in detail the process of data stream processing in the embodiment of the present invention:

[0066] In the embodiment of the present invention, the processing of the data stream by the first processing module can be understood as the processing process of the service stream template TFT, see below figure 2 Detailed description:

[0067] 201. The first processing module receives a service data stream.

[0068] The service data flow may be an IP data flow, and the header information of the service data flow may include the destination address and subnet mask, protocol number (IPv4)/next header (IPv6), source port, destination port, and IPSec security parameter index (SPI), service type (IPv4)/service type (IPv6) and mask, some or all of flow label (IPv6).

[0069] 202. Perform matching according to a packet filter (PF, packet filter) parameter of the network configuration.

[0070] PF parameters include destination address and subnet mask, protocol number (IPv4)/next header (IPv6), source port, destination port, IPSec security parameter index (SPI), service type (IPv4)/service type (IPv6) and mask Code, flow label (IPv6).

[0071] In the same packet filter, some of the above 7 parameters can coexist, and some parameters cannot coexist. Table 1 shows the effective combinations of packet filter parameters. Parameters marked with "X" in the same column can coexist in the same packet filter.

[0072] Table 1: Valid combination table of group filter parameters

[0073]

[0074] 203. Whether there is a matching packet filter.

[0075] You can compare the parameters in the service data flow with the PF parameters in Table 1. For example, first compare the destination address and subnet mask, then compare the protocol number (IPv4)/next header (IPv6), if the header information is Without this item, it is the data packet type III format. According to the data packet type III, compare the remaining TOS (IPv4)/service type (IPv6) and mask and flow label (IPv6); if there is a protocol number (IPv4)/under A header (IPv6), compare the content of the source port number range, if there is no such content, it is the data packet type II format, the data packet type II format, continue to compare IPSec SPI and TOS (IPv4)/service type (IPv6) And mask; if the content of the source port number range, it can only be packet type I, continue to compare the destination port number range and TOS (IPv4)/service type (IPv6) and mask. Compare in turn to confirm whether the header information of the service data stream has a corresponding PF.

[0076] 204. When a corresponding PF exists, record the identifier of the data flow corresponding to the PF in the service data flow.

[0077] In the TFT processing process, first define a data flow identification dataflowId variable, and assign each independent PF a service data flow identification dataflowId value. According to the TFT matching principle, if the service data flow finds the corresponding PF in the TFT, then this The service data stream is sent on the corresponding dedicated radio bearer, otherwise it is sent on the default radio bearer. The business data stream structure (servicePacketDataStruct) is defined in the form of Table 2.

[0078] Table 2: Structure table of business data flow

[0079] Content

[0080] The business data flow can be represented by an array or by a pointer.

[0081] 205. Send the service data flow to the radio bearer corresponding to the PF.

[0082] 206. When no corresponding PF exists, record the parameter in the header information of the data flow as a PF parameter to form a PF created by the first processing module itself, and allocate an unused data flow for the service data flow Logo.

[0083] 207. Because there is no corresponding PF, the service data stream is sent to a default bearer for transmission.

[0084] In the embodiment of the present invention, the processing of the data stream by the second processing module can be understood as a process of robust header compression (ROHC, Robust Header Compression), see below image 3 Detailed description:

[0085] 301. The second processing module receives a service data stream with a data stream identifier.

[0086] 302. Determine whether there is a mapping relationship between the data stream identification and the channel identification (CID, Channel identification).

[0087] Each CID corresponds to a ROHC entity.

[0088] 303. When there is a mapping relationship between the data stream identifier and the channel identifier, push the service data stream with the data stream identifier to the ROHC entity corresponding to the CID for compression.

[0089] 304. When there is no mapping relationship between the data stream identifier and the channel identifier, create a new ROHC entity, and assign a new CID to the newly created ROHC entity.

[0090] 305. Associatively store the data stream identifier and the newly allocated CID.

[0091] 306. Push the service data stream with the data stream identifier to the newly created ROHC entity for compression.

[0092] From the above application scenario embodiments, it can be clearly derived that after performing a service data flow identification, the data flow identification is directly used in other modules to distinguish different service data flows, thereby improving the efficiency of data flow processing.

[0093] In order to clearly illustrate the application of the invention in the actual communication field, the following will illustrate the application of the invention in mobile devices.

[0094] The embodiment of the present invention takes the use in the mobile equipment of the Long Term Evolution (LTE) system as an example for description. In fact, the technical solution of the present invention is also applicable to Wideband Code Division Multiple Access (WCDMA). ) System, Global System of Mobile communication (GSM) and Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) system.

[0095] Refer to Figure 4 , The hardware between the mobile device 20 and the application device 10 adopts a universal serial bus (USB, Universal Serial BUS) interface,

[0096] The TFT matching function is implemented in the data flow control module 210. The data flow control module 210 is responsible for the interface communication between the data path, the protocol stack and the protocol application, and realizes the matching of the TFT to the service data and the corresponding EBI value search. The specific functions are as follows: The data flow control module 210 receives the uplink service data message sent by the USB interface, finds the corresponding external bus interface (EBI, External Bus Interface) through the matching of the TFT module 2101, and transmits the uplink service data message to the wireless access bearer management ( RABM, Radio Acess Bearer Mangement) module 220; The RABM module 220 receives the service data message from the data flow control module 210 after the successful matching of the TFT module 2101, and finds the corresponding data radio according to the EBI value assigned by the service data message Bearer (DRB, Data Radio Bearer).

[0097] For the processing of the service data flow with the TFT module 2101, the network is configured with a PF list, and each PF parameter is recorded as an s_PF_param structure. At the same time, define the TFT parameter list a_TFT_list in the TFT module of the mobile device, a_TFT_list is an array composed of s_PF_param and a dataflowId parameter.

[0098] The example implementation process of this invention in LTE mobile equipment is as follows:

[0099] The first step: the service data flow from the application device 10 is sent to the data flow control module 210 through the USB interface, and the data flow from the application device 10 is identified as the structure pointer of p_servicePacketData in the data flow control module 210. This pointer Is a pointer of type servicePacketDataStruct.

[0100] Step 2: In the data flow control module 210, first call the TFT module function. In the TFT module, compare the data flow header in the servicePacketData service data pointed to by p_servicePacketData with the s_PF_param in the a_TFT_list array. If it is found during the comparison process, The servicePacketData data flow header has a corresponding s_PF_param in a_TFT_list, then the TFT module directly assigns the dataflowId in a_TFT_list to the dataflowId in p_servicePacketData.

[0101] Further, in the process of comparing the data flow header information of the servicePacketData service data with the s_PF_param in the a_TFT_list array, the destination address and the subnet mask are first compared, and then the protocol number (IPv4)/next header (IPv6) is compared. If there is no packet header This item is the data packet type III format. According to the data packet type III, compare the remaining TOS (IPv4)/service type (IPv6) and mask and flow label (IPv6); if there is a protocol number (IPv4)/next Header (IPv6), compare the contents of the source port number range. If there is no such content, it is the data packet type II format, the data packet type II format, continue to compare IPSec SPI and TOS (IPv4)/service type (IPv6) and Mask; if the content of the source port number range, it can only be packet type I, continue to compare the destination port number range and TOS (IPv4)/service type (IPv6) and mask. Compare and confirm whether the servicePacketData in p_servicePacketData has corresponding records in a_TFT_list.

[0102] In the comparison process of this step, the servicePacketData in p_servicePacketData has no corresponding record in a_TFT_list. According to the data stream header information in servicePacketData, a record in a_TFT_list is added, the data stream information is recorded in s_PF_param, and an unused one is allocated. dataflowId value.

[0103] In this step, the data flow control module 210 sends a complete p_servicePacketData data flow to the RABM module 220, and the RABM module 220 forwards it to the corresponding Packet Data Convergence Protocol (PDCP, Packet Data Convergence Protocol) module 230 again.

[0104] The third step: In the PDCP module 230, the ROHC module 2301 stores a structure that records the dataflowId and the ROHC CID, and the structure is defined as: a_TFTandRohcStreamId. Each ROHC CID corresponds to a ROHC entity.

[0105] After the PDCP module 230 receives the data stream from the RABM module 220, it first searches in the a_TFTandRohcStreamId array according to the dataflowId in p_servicePacketData to check whether there is a corresponding ROHC entity that has been created for the service data stream.

[0106] If during the search process, the ROHC module 2301 finds the ROHC entity corresponding to p_servicePacketData, the ROHC module 2301 directly sends p_servicePacketData to the corresponding ROHC entity.

[0107] If during the search process, the ROHC module 2301 does not find the ROHC entity corresponding to p_servicePacketData, then add a new record in a_TFTandRohcStreamId. The dataflowId in this record comes from the dataflowId of p_servicePacketData. In addition, the ROHC module 2301 will assign an unused CID according to the ROHC protocol Value, and create a ROHC entity of a new data stream, and finally send p_servicePacketData data to the newly created ROHC entity.

[0108] In the ROHC entity, the ROHC module does not need to perform a data stream identification process, and other processing is the same as the ROHC protocol processing.

[0109] The technical solution provided by the present invention can be used in any communication entity that needs to support TFT and ROHC functions. The communication entity can be a network device, a mobile communication terminal, or a device in the device.

[0110] Refer to Figure 5 , An embodiment of the data stream processing device provided by the embodiment of the present invention includes: a first processing module 400 and a second processing module 410;

[0111] The first processing module 400 is configured to receive a service data stream, assign a data stream identifier to the service data stream, and send the service data stream with the data stream identifier to the second processing module;

[0112] The second processing module 410 is configured to, after receiving the service data stream with the data stream identifier, determine the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and Push the service data stream with the data stream identifier to the ROHC entity for ROHC compression.

[0113] In the embodiment of the present invention, the first processing module 400 receives a service data stream, assigns a data stream identifier to the service data stream, and sends the service data stream with the data stream identifier to the second processing module;

[0114] After the second processing module 410 receives the service data stream with the data stream identifier, it determines the robust header compression ROHC entity corresponding to the data stream identifier according to the data stream identifier, and combines the The service data stream with the data stream identifier is pushed to the ROHC entity for ROHC compression. Compared with the comparison of multiple bytes in each processing flow in the prior art, the device provided by the embodiment of the present invention directly uses the data stream identifier in other modules to distinguish after performing the service data flow identification identification once. Different business data streams, thereby improving the efficiency of data stream processing.

[0115] In the above Figure 5 Based on the corresponding embodiment, refer to Image 6 In another embodiment of the device provided in the embodiment of the present invention, the first processing module 400 includes:

[0116] The comparing unit 4001 is configured to compare the header information in the service data stream with the parameters of the packet filter PF;

[0117] The first allocation unit 4002 is configured to allocate the data flow identifier corresponding to the PF to the service data flow when the comparison unit 4001 compares the PF that matches the header information in the service data flow;

[0118] The first creating unit 4003 is configured to record the parameter in the header information of the service data stream as a new PF parameter when the comparison unit does not compare the PF that matches the header information in the service data stream , And create a new PF corresponding to the new PF parameter;

[0119] The first allocation unit 4002 is further configured to allocate an unused service data flow identifier to the service data flow after the first creation unit 4003 creates the new PF.

[0120] In the above Figure 5 or Image 6 Based on the corresponding embodiment, refer to Figure 7 In another embodiment of the device provided in the embodiment of the present invention, the second processing module 410 includes:

[0121] The first searching unit 4101 is configured to search for the ROHC entity corresponding to the CID from the pre-stored correspondence between the data flow ID and the channel ID CID according to the data flow ID;

[0122] The first push compression unit 4102 is configured to push the service data stream with the data stream identifier to the ROHC entity when the first search unit 4101 finds the ROHC entity corresponding to the data stream identifier Perform ROHC compression.

[0123] In the above Figure 5 or Image 6 Based on the corresponding embodiment, refer to Figure 8 In another embodiment of the device provided in the embodiment of the present invention, the second processing module 410 includes:

[0124] The second searching unit 4103 is configured to search for the ROHC entity corresponding to the CID from the pre-stored correspondence between the data flow ID and the channel ID CID according to the data flow ID;

[0125] The second creating unit 4104 is configured to create a new ROHC entity when the second searching unit 4103 does not find the ROHC entity corresponding to the data stream identifier;

[0126] The second push compression unit 4105 is configured to push the service data stream with the data stream identifier to the ROHC entity newly created by the second creation unit 4104 for ROHC compression.

[0127] In the above Figure 8 Based on the corresponding embodiment, refer to Picture 9 In another embodiment of the device provided in the embodiment of the present invention, the second processing module 410 further includes:

[0128] The second allocation unit 4106 is configured to allocate a channel identifier CID to the ROHC entity newly created by the second creation unit 4104;

[0129] The associated storage unit 4107 is configured to correspondingly store the data stream identifier and the CID allocated by the second allocation unit 4106.

[0130] The data stream processing equipment provided in multiple embodiments of the present invention can all perform service data stream identification once, and then directly use the data stream identifier in other modules to distinguish different service data streams, thereby improving the efficiency of data stream processing.

[0131] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium, and the storage medium can include: ROM, RAM, magnetic disk or CD, etc.

[0132] The data stream processing methods and devices provided by the embodiments of the present invention are described in detail above. Specific examples are used in this article to illustrate the principles and implementations of the present invention. The descriptions of the above embodiments are only used to help understand the present invention. At the same time, for those skilled in the art, according to the ideas of the present invention, there will be changes in the specific implementation and the scope of application. In summary, the content of this specification should not be understood as Restrictions on the invention.