WO2013037208A1

WO2013037208A1 - Transport stream template matching method and device in lte system

Info

Publication number: WO2013037208A1
Application number: PCT/CN2012/074457
Authority: WO
Inventors: 郭锋
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-09-14
Filing date: 2012-04-20
Publication date: 2013-03-21
Also published as: CN102325347A

Abstract

Disclosed is a transport stream template matching method in a long term evolution (LTE) system, including: after receiving an Internet Protocol (IP) message, extracting the fields to be matched; determining a packet domain network (PDN) connection having the same source IP address as the IP data message; matching the fields in a filter-linked list of the PDN connection one by one, and removing the mismatched filter after each field match; if all filters are not matched successfully, checking whether a default bearer has a filter or not, and if it does, then indicating that the IP data message cannot be transported, otherwise the packet is transported on the default bearer; and if a filter is matched, then the packet is transported on a corresponding bearer of the filter. Also disclosed is a transport stream template matching device in an LTE system. The present invention can be used to significantly improve the transport stream template matching rate in an LTE system.

Description

Transmission 3⁄4 board matching method and device in LTE system

The present invention relates to the field of mobile communications, and in particular, to a transport stream template matching method and apparatus in an LTE (Long Term Evolution) system. Background technique

Compared with 3G technology, LTE adopts a new network architecture, which reduces the number of network elements and reduces the complexity of the signaling process. The network is designed with IP (Internet Protocol) and PS (Packet Switch). The domain greatly improves the response speed of the control plane, and the speed of the data plane also has a significant improvement. The uplink data plane reaches 50M/S, and the downlink data plane reaches 100M/S.

For a service, the LTE control plane is responsible for allocating channels and establishing bearers, and establishing a link from the UE (User Equipment) through the eNB (evolved NodeB, evolved base station) to the core network; the data plane is responsible for the link. Transfer IP data packets on the road. A plurality of bearers are usually set up between the UE and the core network, and each data packet of the uplink and the downlink is matched to a corresponding bearer, and then transmitted on the link corresponding to the bearer. In order to describe the correspondence between the data packet and the bearer, the concept of the TFT (Traffic Flow Template) is used in the LTE. The TFT is the data filtering rule. The mapping relationship between the data packet and its corresponding bearer passes through the TFT. Match to complete. The uplink data packet is matched in the UE, and the downlink data packet is matched in the P-GW (Packet Gate Way). The entire frame diagram is as shown in FIG. 1 . The upper line in Figure 1 indicates the control flow, and the flow control and parameter configuration are performed between the UE-eNB-MME (Mobility Manage Entity), the communication link is established, and the uplink is allocated and generated in the UE and the P-GW. And the downstream TFT. The lower line in Figure 1 represents the data stream, and data is transferred between the UE-eNB-S-GW-P-GW. If the UE has uplink data to send, The packet is matched in the TFT and matched to a corresponding bearer. The bearer is transmitted from the data plane to the eNB through the air interface, and then sent by the eNB to the S-GW (Service GateWay, service gateway) under the control of the MME. ) /P-GW, which is finally sent to the external network. Similarly, the downlink data is also sent as such. If the core network has downlink data to be sent, the downlink data packet completes the TFT matching in the P-GW, finds the corresponding bearer, and then reaches the UE through the S-GW and the eNB in turn, and the data plane of the UE is submitted upwards layer by layer, and finally submitted. Give the upper application. As can be seen from Figure 1, in the entire data plane from the UE to the core network, except for the bearer matching of the TFT, the other layers are data transmission, with a fixed processing method and a relatively stable transmission speed, and the matching speed of the TFT will be To a large extent affect the speed of the entire data surface. The meanings of the English characters in Figure 1 are as follows: APP: application; NAS: non-access stratum; RRC: radio resource control layer; PDCP: packet data convergence protocol layer; RLC: radio link control layer; MAC: media access control Layer; PHY: physical layer; S1AP: S1 air interface; X2AP: X2 air interface; SCTP: sequence control transmission protocol; GTP: GPRS plane tunneling protocol.

The TFT is associated with a bearer, one dedicated bearer corresponds to one TFT, and the TFT is composed of one or more filters (filters). The Filter stores a set of filtering conditions. If the attributes of an IP data packet satisfy all the filtering conditions of the Filter, the 4 艮 text can be transmitted on the TFT corresponding to the Filter. The default load can be TFT or TFT. If there is a TFT, the matching principle and process are the same as the matching process of the above dedicated bearer; if there is no TFT, the default bearer is equivalent to an all-pass bearer, that is, all data packets that cannot be matched to the dedicated bearer can be Transfer on the default bearer.

During the implementation process, there may be multiple PDN (Packet Domain Network) connections between the UE and the P-GW. Each PDN connection has a default bearer and may have one or more dedicated bearers. If there is only a default bearer on the PDN connection, then there may be no TFT. If there is a dedicated bearer in addition to the default bearer, then there is one or more TFTs, and naturally there is at least one Filter. According to the above analysis, the Filter is managed in units of PDN connections. The Filter on a PDN connection is stored in a circular linked list, and whether a Filter exists in the PDN connection is marked according to whether the header and the end of the linked list are the same. To facilitate matching, all Filters on a PDN connection are organized in the same doubly linked list. The doubly linked list structure of Filter is shown in Figure 2. The head pointer of the doubly linked list points to the first Filter on the PDN connection, and the tail pointer points to the last Filter. If the head pointer is equal to the tail pointer, there is no Filter on this PDN connection, ie there is no dedicated bearer only the default bearer. The Filter node in the linked list is mainly composed of the front and rear node pointers, the bearer ID, and the Filter entity. The actual value of each field of the Filter is stored in the Filter entity, and is allocated by the network side according to the needs of the actual service. The bearer ID is the bearer tag to which the Filter belongs, and all data packets matching the Filter are transmitted on this bearer. A new Filter is assigned to the network side. When an existing Filter is deleted or updated, the Filter list on the PDN connection is also updated synchronously.

The data packets transmitted in LTE are all IP data packets, including IPv4 and IPv6 formats. Figure 3 is a schematic diagram of the structure of an IPv4 packet header, and Figure 4 is a schematic diagram of the structure of an IPv6 packet header. Regardless of whether it is an IPv4 or an IPv6 packet, some fields in the two types of packets have corresponding fields and values in the Filter. . The message is transmitted by such a bearer: each field of the message header and a corresponding field of the Filter in the bearer are the same. According to the Vesion (Protocol Version) field, it can be known whether the packet is IPv4 or IPv6. The IPv4 and IPv6 packets are different, and the matching fields are different. The fields to be matched by the IPv4 message include TOS (Type of Service), Protocol (Protocol Number), SPI (Security Payload Index) in the option, Source Address, Destination Address ( Destination address), where the address contains a mask. The fields to be matched by the IPv6 packet include the Traffic Class, the Flow Label, the Next Header, the SPI, the Source Address obtained from the address of the extended header in the Next Header. Destination Address. For the two types of texts, the above fields are the most matching fields. If all the above fields are not extracted in the message, only the actually extracted fields are matched. Filter contains the above fields that need to match, in addition There are also tag information such as FilterID and bearer ID. The meanings of the characters in Figure 3 and Figure 4 are as follows: Identification: Ten points of discussion: Fragment offset: Dividing the time; Time to Live: Time to live; Header Checksum: Head check code; Payload Length : payload length; Hop Limit: transition limit; IHL: Internet Header Length.

Figure 5 is a flow chart for extracting the header field of the IP data packet, as shown in Figure 5, including:

The IP data packet is extracted from the Version field in the IP data packet, and the IP data packet is determined to be IPv4 or IPv6 according to the Version field. If the IPv4 packet is used, the address, TOS, Identification, and SPI fields are obtained from the packet. End the processing flow; if it is an IPv6 packet, obtain the address, transmission level, flow label, next header, and SPI field from the packet. Further, each field of the extracted IP data packet is matched with each field of the Filter in the TFT. If all the header fields in the packet that match the same are the same as the corresponding field of the Filter, the match is considered Successfully, the IP data packet is sent by the bearer of the TFT where the Filter is located.

The manner of matching each field of the extracted IP data packet with each field of the Filter in the TFT is: matching each field extracted in the IP data packet with each Filter in the TFT to completely match all the fields once. Find a Filter that matches the success, and then transmit the IP data packet from the bearer corresponding to the Filter.

However, since a maximum of 16 filters are allowed on a bearer and each packet is matched in a maximum of 16 filters, the existing method is used to match the filters in the TFT, so that the matching speed is limited. Summary of the invention

The present invention provides a transport stream template matching method and apparatus in an LTE system, so as to solve the problem that the transport stream template matching rate is not high in the prior art.

The present invention provides a method for matching a transport stream template in an LTE system, including the following steps: After receiving an IP data packet, extracting a field that needs to be matched from the IP data packet; determining the address and the IP data The same PDN connection with the same source IP address; Each field is matched one by one in the Filter list of the PDN connection, and each time a field is matched, the Filter that does not match the field is eliminated until a matching result is obtained.

Further, for the IPv4 packet, the field to be matched includes: a part of the service type Type of Service, the protocol number Protocol, the security load index SPI, the source address Source Address, and the destination address for the IPv4 packet. Or all; for the Pv6 message, part or all of the destination address Destination Class, the flow label Flow Label, the next header address Next Header, the secure load index SPI, the source address Source Address, and the destination address Destination Address.

Further, the determining the PDN with the same address as the source IP address of the IP data includes: preferentially connecting the source IP address of the IP data to the PDN used by the previous IP data. The addresses are compared and judged whether they are the same. If they are different, they are compared with the addresses of other PDN connections.

Further, the matching the fields in the Filter Link List of the PDN connection one by one includes: first matching the destination IP address.

After the matching result is obtained, the method further includes: if the matching result is that all the Filters are unsuccessful, check whether the default bearer of the PDN connection has a Filter, and if there is a Filter, the IP The data packet does not find the corresponding transport bearer and cannot be transmitted. If there is no Filter, the IP data packet is transmitted on the default bearer of the PDN connection.

Further, after the matching result is obtained, the method further includes: if the matching result is successfully matched to a Filter, transmitting the IP data to the corresponding port of the Filter.

The present invention also provides a transport stream template matching apparatus in an LTE system, including: a field extracting module, a PDN determining module, and a matching module;

The field tear 4 block, used to receive the IP data message, will be extracted from the IP data message The field to be matched is sent to the PDN determination module;

a PDN determining module, configured to send, according to a field that is required to be matched by the field extraction module, a PDN connection of a packet domain network having the same address as the source IP address of the IP data, and send the PDN connection to a field that needs to be matched. Give a matching module;

a matching module, configured to receive a PDN connection sent by the PDN determining module and send a matching field to the matching module, and match each field that needs to be matched one by one in the filter filter list of the PDN connection, each matching one Field, culling the Filter that does not match the field until a match is obtained.

Further, the field extraction module is specifically configured to extract a field corresponding to the IPv4 packet that needs to be matched, including some or all of the following fields: Type of Service, Protocol, SPL Source Address, Destination Address; and extracting the Pv6 report. The fields corresponding to the text that need to be matched include some or all of the following fields: Traffic Class, Flow Label, Next Header, SPL Source Address, Destination Address.

Further, the device further includes: a matching result analyzing module, configured to receive a matching result sent by the matching module, and if the matching result is that all the filters are unsuccessful, check whether the default bearer of the PDN connection exists. Filter, if there is a Filter, indicating that the IP data packet does not find a corresponding transport bearer, and cannot be transmitted; if there is no Filter, indicating that the IP data packet is transmitted on the default bearer of the PDN connection;

Correspondingly, the matching module is further configured to send a matching result to the matching result analysis module. Further, the matching result analysis module is further configured to: if the matching result is successfully matched to a Filter, instructing to transmit the IP data to the corresponding port of the Filter.

The beneficial effects of the present invention are as follows:

The transport stream template matching method and device in the LTE system proposed by the present invention solves the problem that the transport stream template matching rate is slow in the prior art, and can significantly improve the transport stream template matching rate in the LTE system. Using the technical solution of the present invention, establishing three on a PDN connection In a bearer test environment, the average matching time of a data message was reduced from an average of 22 microseconds to 13 microseconds. DRAWINGS

1 is a schematic diagram of a data plane and a control plane of an LTE network in the prior art;

2 is a schematic diagram of a doubly linked list organization structure of a filter in the prior art;

3 is a schematic structural diagram of an IPv4 packet header in the prior art;

4 is a schematic structural diagram of an IPv6 packet header in the prior art;

FIG. 5 is a flowchart of extracting an IP data packet header field in the prior art;

6 is a schematic flowchart of a transport stream template matching method in an LTE system according to an embodiment of the present invention;

7 is a schematic flowchart of searching for a PDN connection according to an embodiment of the present invention;

8 is a flowchart of a specific implementation of Filter Link Table matching on a PDN according to an embodiment of the present invention; and FIG. 9 is a schematic diagram of a structure of a transport stream template matching apparatus in an LTE system according to an embodiment of the present invention. detailed description

The present invention will be further described in detail below in conjunction with the drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Method embodiment

According to an embodiment of the present invention, a transport stream template matching method in an LTE system is provided. The basic idea is: extracting a required field from an IP data packet header, matching each field in a Filter list, and failing to match the current field. The matched Filter is temporarily culled; the next field is matched in the remaining Filter, and the Filter that cannot match is temporarily removed until the last Filter is left. Normally, all the fields can be matched in the Filter. The bearer of the Filter is the bearer of the IP data packet. With this matching method, each field will be ticked In addition to a number of Filters, the matching range of the Filter is continuously reduced, which can effectively improve the matching speed.

FIG. 6 is a flowchart of a method for matching a transport stream template in an LTE system according to an embodiment of the present invention. As shown in FIG. 6, a transport stream template matching method in an LTE system according to an embodiment of the present invention includes the following processing:

Step 601: After receiving the IP data packet, extract the corresponding field from the IP data packet header according to the type of the IP data packet.

Here, the extracting the corresponding field from the packet header according to the type of the IP data packet is: determining whether the type of the IP data packet is IPv4 or IPv6 according to the Version in the IP data packet header, and then according to the IPv4 or IPv6 format. The corresponding field is extracted from the packet header. The corresponding field is extracted from the packet header according to the IPv4 or IPv6 format. The prior art is not mentioned here.

The corresponding fields may be: a source IP address, a destination IP address (including a mask), a TOS, a protocol number, a next header address, a transmission level, a flow label, and the like.

Step 602: In each PDN connection, find a PDN connection with the same source IP address as the received IP data packet.

After completing step 602, the subsequent matching range is only in the Filter list under this PDN. The PDN connection that is the same as the source IP address of the received IP data packet is: The continuity of the message presentation area sent by the application, for example, the continuous N messages are telephone data, and the subsequent N consecutive messages are SMS data, that is, there may be several data messages adjacent to each other transmitted on the same PDN connection. Based on the continuity of the area, when the next message is searched for the PDN connection, it is prioritized whether the PDN connection used by the previous message is the PDN that can be used in this message. That is, the source IP address of the IP data packet is compared with the address of the PDN used by the previous IP data packet to determine whether it is the same. If not, the address of the other PDN is compared to find the current address. The PDN connection corresponding to the received IP data packet.

In the specific implementation, after the step 602 is completed, after the PDN connection corresponding to the current IP data is found, the PDN connection is recorded in the priority PDN connection, and the subsequent IP data packet takes precedence. It is judged whether the PDN connection recorded in the priority PDN connection is available. If not, the PDN connection with the same source IP address as the received IP data packet is searched, and the new PDN connection is recorded in the priority PDN connection.

Step 603: The corresponding fields extracted from the IP data packet header are matched one by one with each Filter in the PDN filter list, and each time a field is matched, the Filter that does not match the field is removed.

In the embodiment of the present invention, the destination IP address is matched first, the unmatched Filter is removed, and the remaining fields that need to be matched are matched one by one, for example, the TOS, the protocol number, the SPI, the next header, the transmission level, the flow label, and the like. Matching one by one, that is, each time a field is matched, one or more Filters may be excluded, narrowing the matching range. After each part of the field is matched, the filter is checked to check whether the last Filter remains. If yes, stop the culling and go to step 604; No, 'J, continue matching.

Further, if all the filters are eliminated after matching a certain field, the process proceeds to step 605.

Step 604: Whether the remaining fields match successfully on the remaining Filters. If the matching is successful, then go to step 606; otherwise, go to step 605.

Step 605: Check whether the default bearer has a filter. If the default bearer has a Filter, the application is notified that the data packet cannot be transmitted, and the processing flow is ended. If the default bearer does not have a Filter, the process proceeds to step 606.

Step 606: Obtain a bearer ID corresponding to the Filter according to the matching result, and transmit an IP data packet from the bearer.

After the step 606 is completed, all the Filter tags on the PDN connection are reset to be valid, and the next data packet is matched.

Step 602 of the embodiment of the present invention, as shown in FIG. 7, specifically:

Step 6021: Check whether there is a priority PDN connection, if yes, proceed to step 6022; If not, step 6023 is performed.

Step 6022: Confirm that the address of the priority PDN connection is the same as the source IP address in the IP data packet header that needs to be transmitted. If yes, go to step 603. If they are not the same, go to step 6023.

Step 6023: Find the PDN connection with the same source IP address as the IP data packet header that needs to be transmitted.

Specifically, the PDN connection is the same as the source IP address in the IP data packet header that needs to be transmitted one by one. If the PDN connection is found, the IP data packet is transmitted on a certain bearer of the PDN connection, and then the Matching in the Filter list of the PDN connection;

If the match in the PDN connection is successful, go to step 6024. If all the PDN connection addresses are different from the source IP address in the packet header or in the Filter list in all PDN connections, the data packet header. The fields are not matched successfully. If the data packet is abnormal, the exception processing flow is entered.

Step 6024: Transmit data on the bearer corresponding to the Filter in the PDN connection, and set the current PDN connection as the priority PDN connection.

FIG. 8 is a flowchart of a specific implementation of matching each filter in a Filter list in a PDN connection in step 603 of the embodiment of the present invention, including:

After determining the PDN connection, obtain the Filter list corresponding to the PDN connection;

Match the destination IP address, and temporarily remove the Filter whose destination IP address corresponding to the Filter in the Filter list is different from the destination IP address of the extracted IP data. If the other fields are matched in the Filter list, they will no longer match. Eliminated Filter; This way, through a round of matching in a linked list, you can eliminate several Filters and narrow the matching range.

Next, the other fields that are extracted are matched one by one in the remaining Filters. Other fields of the IPv4 data packet include TOS, Protocol, SPI, etc. Other fields of the IPv6 data packet include Traffic Class, Flow Label, Next Header, SPI, etc. A round of matching will eliminate a number of Filters. After each round of matching is completed, the number of remaining Filters and the number of remaining fields are checked.

After each part of the field is matched, the filter is checked, and the last filter is checked. If there is more than one filter, the matching continues.

Otherwise, stop removed, the remaining field matches again on the remaining Filter, determines whether the match is successful, if the match is successful, the obtained Filter corresponding to the bearer ID of the matching result notification data plane to from the ₇ data | carrier corresponding Data Wireless ₇ | (DSB, Data Radio Bearer) is sent out; if the match fails, it checks whether the default bearer has a Filter. A special case is that, during or after the matching process, all Filters in the Filter list are culled, and it is considered to be non-conforming. Then check whether the default bearer has a Filter.

Device embodiment

According to an embodiment of the present invention, a transport stream template matching apparatus in an LTE system is provided. FIG. 9 is a schematic structural diagram of a transport stream template matching apparatus in an LTE system according to an embodiment of the present invention, as shown in FIG. The transport stream template matching apparatus in the LTE system of the embodiment of the present invention includes a field extracting module 901, a PDN determining module 902, a matching module 903, and a matching result analyzing module 904.

The respective modules of the embodiments of the present invention are described in detail below.

Specifically, the field extraction module 901 is configured to send, after receiving the IP data packet, a field that needs to be matched, which is extracted from the IP data packet, to the PDN determining module.

For the IPv4 packet, the fields that need to be matched include: Type of Service, Protocol, SPI, Source Address, Destination Address; for IPv6, the fields that need to be matched include: Traffic Class, Flow Label, Next Header, SPL Source Address, Destination Address. For the two types of texts, the above fields are the most matching fields. If all the above fields are not extracted in the message, only the actually extracted fields are matched.

The PDN determining module 902 is configured to perform matching words according to the field extraction module. ■n

Send the PDN connection to the matching module with the field that needs to be matched;

The matching module 903 is configured to receive a PDN connection sent by the PDN determining module and send a matching field to the matching module, and match each field that needs to be matched one by one in the filter filter list of the PDN connection, each matching A field that excludes Filters that do not match the field until a match is obtained.

The device further includes: a matching result analysis module 904, configured to receive a matching result sent by the matching module, and if the matching result is that all the Filters are unsuccessful, check whether the default bearer of the PDN connection has a Filter. If there is a Filter, it indicates that the IP data packet does not find the corresponding transport bearer, and cannot be transmitted; if there is no Filter, it indicates that the IP data packet is transmitted on the default bearer of the PDN connection; The matching module is further configured to send a matching result to the matching result analysis module. .

For a specific implementation of the transport stream template matching apparatus in the LTE system of the present invention, reference may be made to the description of the transport stream template matching method in the LTE system of the present invention, and details are not described herein again.

Although the preferred embodiments of the present invention have been disclosed for purposes of illustration, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, therefore, the scope of the present invention should not be limited to the embodiments described above. The scope of protection shall be subject to the provisions of the claims.

Claims

Claim

A transport stream template matching method in a long term evolution LTE system, the method comprising:

After receiving the Internet Protocol IP data packet, extract the field that needs to be matched from the IP data packet;

Determining a packet domain network PDN connection having the same address as the source IP address of the IP data; matching each field one by one in the filter filter list of the PDN connection, each field is matched, and the field is excluded Match the Filter until you get a match.

The method of claim 1, wherein the matching field is: the IPv4 packet is a service type Type of Service, a protocol number Protocol, a security load index SPI, and a source address Source Address. Part or all of the Destination Address; for the Pv64 text, the traffic class Traffic Class, the flow label Flow Label, the next header address Next Header, the security payload index SPI, the source address Source Address, the destination address Destination Address Part or all of it.

The method of claim 1, wherein the determining the PDN connection with the same source IP address as the IP data packet comprises: prioritizing the source IP address of the IP data packet with The addresses of the PDN connections used in the previous IP data packet are compared to determine whether they are the same. If they are different, they are compared with the addresses of other PDN connections.

The method according to claim 1, wherein the matching each field in the Filter Link List of the PDN connection includes: first matching a destination IP address.

The method according to claim 1, wherein after the obtaining the matching result, the method further comprises: if the matching result is that all the Filters are unsuccessful, the default bearer of the PDN connection is checked. If there is a Filter, the IP data packet does not find the corresponding transport bearer and cannot be transmitted. If there is no Filter, the IP data packet is transmitted on the default bearer of the PDN connection.

The method according to claim 1, wherein after the obtaining the matching result, the method further comprises: if the matching result is successfully matched to a Filter, the IP data packet is in the Filter The corresponding bearer is transmitted.

A transport stream template matching apparatus in an LTE system, comprising: a field extracting module, a PDN determining module, and a matching module; wherein

a field extracting module, configured to send, after receiving the IP data packet, a field that needs to be matched from the IP data packet to the PDN determining module;

8. Apparatus according to claim 7 wherein:

The field extraction module is specifically configured to extract a field corresponding to the IPv4 packet that needs to be matched, including some or all of the following fields: Type of Service, Protocol, SPL Source Address, Destination Address; and corresponding to the Pv6 message. Fields that need to be matched, including some or all of the following fields: Traffic Class, Flow Label, Next Header, SPL Source Address, Destination Address.

The device according to claim 7 or 8, wherein the device further comprises: a matching result analysis module, configured to receive a matching result sent by the matching module, if the matching result matches all the Filters If the filter is unsuccessful, check whether the default bearer of the PDN connection exists. If there is a Filter, it indicates that the IP data packet does not find the corresponding transport bearer and cannot be transmitted. If there is no Filter, the IP data is indicated. The message is connected to the PDN. Correspondingly, the matching module is further configured to send a matching result to the matching result analysis module.

10. Apparatus according to claim 9 wherein:

The matching result analysis module is further configured to: if the matching result is successfully matched to a Filter, indicating that the IP data packet is in the