WO2012065499A1

WO2012065499A1 - Method and system for realizing service quality control

Info

Publication number: WO2012065499A1
Application number: PCT/CN2011/081246
Authority: WO
Inventors: 毕以峰; 霍玉臻; 刘国燕
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-17
Filing date: 2011-10-25
Publication date: 2012-05-24
Also published as: CN102469087A

Abstract

A method and a system for realizing service quality control. The method includes that a secure gateway (SeGW) reports the corresponding relation information between internet protocol security (IPSec) tunnel information and IP data stream information in the downlink direction to a fixed network element through a second network element, the SeGW or a first network element reports a corresponding relation information between the IPSec tunnel information and the IP data stream information in the uplink direction to the fixed network element through the second network element, and the fixed network element performs service quality (QoS) control, wherein, the first network element is a Home evolved Node B (HeNB), and the second network element is a Home evolved Node B Policy Function (HeNB PF); or the first network element is a Home Node B (HNB), and the second network element is a Hone Node B Policy Function (HNB PF). The invention meets the QoS demand of the service with high QoS demand prior to others, and improves user experience.

Description

Method and system for realizing service quality control

Technical field

The present invention relates to the field of wireless communications, and in particular, to a method and system for implementing Quality of Service (QoS) control. Background technique

The Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is evolved by Evolved Universal Terrestrial Radio Access Network (E-UTRAN), mobile management. A component (Mobility Management Entity, MME), a Serving Gateway (S-GW), a Packet Data Network Gateway (P-GW), and a Home Subscriber Server (HSS).

FIG. 1 is a schematic diagram of an architecture of a Home evolved NodeB (HeNB) accessing an EPS in a non-roaming scenario according to the related art. As shown in FIG. 1, the MME and the EUTRAN, the S-GW, and the Home Base Station Gateway (HeNB GW) Connected, responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management; S-GW is an access gateway device connected to E-UTRAN, in E-UTRAN and The P-GW forwards data and is responsible for buffering the paging waiting data. The P-GW is the border gateway of the EPS and Packet Data Network (PDN) network, which is responsible for PDN access and EPS and PDN. Transfer data and other functions.

If the EPS system supports Policy and Charging Control (PCC), the Policy and Charging Rules Function (PCRF) performs policy and charging rules. It passes the interface Rx and the carrier network. The application function (AF) of the protocol (Internet Protocol, IP) service network is connected to obtain service information, which is used to generate service information of the PCC policy. When the S5 interface between the S-GW and the P-GW uses the GPRS Tunneling Protocol (GTP) protocol, the Policy and Charging Enforcement Function (PCEF) resides in the P-GW. The PCRF exchanges information with the P-GW through the Gx interface, and is responsible for initiating the establishment, modification, and release of bearers to ensure service data. Quality of Service (QoS), and charge control. When the S5 interface of the S-GW and the P-GW uses the Proxy Mobile IP (PMIP), the S-GW hosts the Bearer Binding and Event Report Function (BBERF), and The S-GW exchanges information with the PCRF through the Gxc interface. The BBERF is responsible for initiating the establishment, modification, and release of the bearer to ensure the service quality of the service data. The PCEF performs charging control.

In the existing EPS system, the P-GW (or other network element, such as the S-GW) has a bearer binding function. When the bearer binding is performed, the quintuple of the data packet (source address, destination address, source) is used. The port number, the destination port number, and the protocol number are matched to the TFT (traffic flow template), and the PF (a packet filter) that forms the TFT is associated with different bearers. When the quintuple of the data packet matches a certain PF, the data packet is transmitted to the corresponding bearer.

The EPS supports the access of the HeNB, which is a small, low-power base station deployed in indoor places such as homes, offices, and corporate buildings. The Closed Subscriber Group (CSG) is a concept introduced after the introduction of a home base station. Usually a household or an enterprise internal user forms a closed user group, which is identified by a CSG ID. The home base station serving the users in this closed subscriber group has the same CSG ID. When a closed subscriber group is served by only one home base station, the closed subscriber group can also directly identify the home base station identity (e.g., BS ID). According to the wishes of the home base station manager, CSG users and/or non-CSG users can distinguish different levels, and the priority of the service is different, and the service quality and service category can be different. By signing with the operator, the user can access the home base station corresponding to multiple closed user groups, for example, the user's office, home, and the like. The concept of allowing a closed user group list to be introduced is therefore introduced. This list is stored in the user's terminal and the user data server on the network side.

There are three usage modes for home base stations: closed mode, mixed mode, and open mode. When the home base station is in the closed mode, only the CSG subscription user to which the home base station belongs can access the base station and enjoy the service provided by the base station; when the home base station is in the open mode, any operator subscription user can access the base station. The home base station at this time is equivalent to the macro base station; when the home base station is in the hybrid mode, it also allows any operator to sign up the user or the roaming user to access the use, but according to whether the user subscribes to the CSG information to distinguish different levels, that is, Said that users who sign up for the CSG have higher business priorities when using hybrid home base stations, and enjoy better service. Quality and business category.

The HeNB usually accesses the core network of the EPS through the leased fixed network line (as shown in FIG. 1). To ensure the security of the access, a security gateway (SeGW) is introduced in the core network for shielding, and between the HeNB and the SeGW. The data will be encapsulated using the Internet Security (IP Security, IPSec) mechanism. The HeNB is connected to the MME and the S-GW of the core network, or is connected to the MME and the S-GW through the HeNB GW (the HeNB GW is an optional network element, whether or not deployed by the operator-based network), and controls signaling or user data. Intermediate through the IPSec tunnel between the HeNB and the SeGW.

Furthermore, the Universal Mobile Telecommunications System (UMTS) supports access to the home base station HNB (Home NodeB). 2 is a schematic diagram of an architecture of an HNB accessing UMTS in a non-roaming scenario according to the related art. The architecture in FIG. 2 is similar to the architecture of FIG. 1, except that a Serving General Packet Radio Service is used. The Support Node (SGSN) replaces the MME and the S-GW, and replaces the P-GW with a Gateway General Packet Radio Service Support Node (GGSN). Similarly, the HNB can access the EPC core network through the enhanced SGSN (S4-SGSN), and the S4-SGSN and the S-GW are connected through the S4 interface, and the HSS is connected through the S6d/Gr interface, and the S4-SGSN is the same. The function of the MME in the HeNB scenario is as shown in Figure 2a.

In the current HeNB/HNB system, a HeNB/HNB PF (Policy Function) network element is introduced, and its function is to transmit control signaling and corresponding policies of policy negotiation in the 3GPP HeNB/HNB system and the fixed network system. And make certain strategic decisions. Currently, there are two parallel architecture schemes for the functions of the HeNB/HNB PF itself and the information interaction mechanism with other network elements. The two schemes are described as follows:

Architecture 1 (in Figure 1 and Figure 2, when there are only Tl and T2 interfaces): T1-T2 scheme

In this solution, an interface T1 is set between the SeGW and the HeNB/HNB PF, and an interface T2 is set between the HeNB/HNB and the HeNB/HNB PF.

The T1 interface is used to transmit related HeNB/HNB system messages, such as HeNB/HNB address, HeNB/HNB identifier, etc., to the HeNB/HNB PF and the fixed network when the HeNB/HNB is powered on, for association policy session and positioning. The location of the HeNB/HNB in the fixed network, etc. T2 interface for The HeNB/HNB transmits relevant policy negotiation control signaling and corresponding policies to the HeNB/HNB PF and the fixed network, and implements QoS control on the user data on the HeNB/HNB.

Architecture 2 (Figure 1, Figure 2, when there are only Tl, T3 interfaces): T1-T3 solution

In this solution, an interface T1 is set between the SeGW and the HeNB/HNB PF, and an interface T3 is set between the HeNB/HNB GW/MME and the HeNB/HNB PF.

The T1 interface is used to transmit related HeNB/HNB system messages, such as HeNB/HNB address, HeNB/HNB identifier, etc., to the HeNB/HNB PF and the fixed network when the HeNB/HNB is powered on, for association policy session and positioning. The location of the HeNB/HNB in the fixed network, etc. The T3 interface is used by the HeNB/HNB GW/MME to transmit related policy negotiation control signaling and corresponding policies to the HeNB/HNB PF and the fixed network, and implement QoS control on the user data on the HeNB/HNB.

When the current network HeNB/HNB is connected, the following problems exist in QoS control. In the scenario where the user accesses the core network through the HeNB/HNB, the QoS of the fixed line of the HeNB/HNB is usually restricted by the signing of the owner of the HeNB/HNB and the fixed network operator, and the user service data is passed. When an IPsec tunnel is encapsulated and transmitted by a fixed network link, whether the fixed network can guarantee the QoS of the service data depends entirely on the condition of the fixed network resource. All data services (such as voice, video, and other data services) that are connected to all PDNs of all the terminals of the same HeNB/HNB are transmitted through the same IPSec tunnel, so that different services are used. It is impossible to guarantee the QoS it needs for its characteristics. Especially in the case where the fixed network resources are insufficient, if there is no QoS distinction for different types of services, the services with high QoS requirements cannot be performed or even failed. For example, a type of BE (Best Effort) service such as data downloading is not very demanding on QoS, and a type of service such as voice has very high QoS requirements, but because there is no QoS differentiation mechanism, when resources are insufficient. The above two types of services have obtained the same bandwidth (statistically speaking). Such bandwidth is sufficient for data downloading such BE services, but such bandwidth may not meet the requirements of voice and other services, resulting in voice. The transmission quality of the service is extremely poor or even the business fails. Summary of the invention

The technical problem to be solved by the present invention proposes a method and system for implementing Q 0 S control to realize Guarantee the corresponding QoS for different services.

In order to solve the above problem, the present invention provides a method for implementing quality of service control, comprising: a security gateway (SeGW) passing a downlink network protocol security (IPsec) tunnel information and IP data stream information through a second network element The corresponding relationship information is reported to the fixed network element, and the SeGW or the first network element reports the correspondence between the IPsec tunnel information and the IP data flow information in the uplink direction to the fixed network element through the second network element, and the fixed network element is used by the fixed network. Meta-execution quality of service (QoS) control;

The first network element is an evolved home base station (HeNB), and the second network element is an evolved home base station policy function (HeNB PF); or the first network element is a home base station (HNB), and the second network element For the Home Base Station Policy Function (HNB PF).

Preferably, the above method has the following characteristics:

The information about the correspondence between the IPsec tunnel information and the IP data flow information in the downlink direction is reported to the fixed network element by the second network element, and the SeGW or the first network element sends the IPsec tunnel information in the uplink direction by using the second network element. Before the mapping relationship between the information and the IP data stream information is reported to the fixed network element, the method further includes:

More than one IPsec tunnel is established between the first network element and the SeGW.

Preferably, the above method has the following characteristics:

An IPsec tunnel is established between the first network element and the SeGW in a static or dynamic manner. Preferably, the above method has the following characteristics:

Before reporting the correspondence information in the downlink direction and the uplink direction to the fixed network element, the method further includes:

The first network element and/or the SeGW receive the IP data flow information sent from the core network, and establish a correspondence between the IPsec tunnel information and the IP data flow information.

Preferably, the above method has the following characteristics:

The IPsec tunnel information is a Security Parameter Index (SPI) or a Differentiated Service Code Point (DSCP) information;

The IP data stream information is one or more of the following information: quintuple information, tunnel endpoint identifier (TEID), radio bearer identifier (RB-ID), QoS rule, service flow template (TFT) Or a packet filter (PF), wherein the quintuple information includes information of a source address, a destination address, a source port number, a destination port number, and a protocol number.

Preferably, the above method has the following characteristics:

The corresponding relationship information received by the fixed network element is the correspondence information between the SPI and the QoS rule.

Preferably, the above method has the following characteristics:

The QoS control performed by the fixed network element refers to: The fixed network element provides a hierarchical QoS guarantee for transmitting data packets according to different SPIs and their corresponding QoS rules.

Preferably, the method further includes:

The first network element creates an uplink mapping table or a filter according to the RB-ID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SPI, and maps or filters the uplink data.

The SeGW creates a mapping table or a filter in the downlink direction according to the TEID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SPI, and maps or filters the downlink data.

Preferably, the above method has the following characteristics:

The fixed network element that receives the correspondence information between the IPsec tunnel information and the IP data flow information is a Broadband Forum Policy Control Function (BPCF), and the BPCF provides a hierarchical QoS guarantee for the transmission data, or the BPCF A fixed-line QoS guarantee is provided for transmission data with a fixed network element broadband network gateway (BNG) or a broadband remote access server (BRAS).

Preferably, the above method has the following characteristics:

In the step that the SeGW reports the correspondence information between the IPsec tunnel information and the IP data flow information in the downlink direction to the fixed network element by using the second network element, the SeGW sends the corresponding relationship information to the request information through the notification request message. a second network element; the second network element sends the corresponding relationship information to the fixed network element by using an S9* interface session message;

In the step of reporting, by the second network element, the correspondence information between the IPsec tunnel information and the IP data flow information in the uplink direction to the fixed network element by the second network element, the SeGW, by using the notification request message, Corresponding relationship information is sent to the second network element, or the first network element sends the corresponding relationship information to the second network element by using a resource request message or a resource modification request message; The second network element sends the corresponding relationship information to the fixed network element by using an S9* interface session message.

The technical problem to be solved by the present invention is to provide a system for implementing quality of service control, including: a first network element, a second network element, a SeGW, and a fixed network element, where

The SeGW is configured to: report, by the second network element, the correspondence information between the IPsec tunnel information and the IP data flow information in the downlink direction to the fixed network element;

The SeGW or the first network element is configured to: report the correspondence information between the IPsec tunnel information and the IP data flow information in the uplink direction to the fixed network element by using the second network element;

The fixed network element is configured to: ensure the QoS of the data transmitted in the phase IPsec tunnel according to the correspondence information in the downlink direction and the uplink direction;

The first network element is an HeNB, and the second network element is an HeNB PF; or the first network element is an HNB, and the second network element is an HNB PF.

Preferably, the above system has the following characteristics:

The first network element is further configured to: establish more than one IPsec tunnel with the SeGW. Preferably, the above system has the following characteristics:

The IPsec tunnel information is a Security Parameter Index (SPI) or a Differential Service Code Point (DSCP) information;

The IP data stream information is one or more of the following information: quintuple information, tunnel endpoint identifier (TEID), radio bearer identifier (RB-ID), QoS rule, service flow template (TFT), or data packet. a filter (PF), wherein the quintuple information includes information of a source address, a destination address, a source port number, a destination port number, and a protocol number.

Preferably, the above system has the following characteristics:

The first network element is further configured to: create an uplink mapping table or a filter according to the RB-ID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SPI, and map or filter the uplink data;

The SeGW is further configured to: create a mapping table or filter in the downlink direction according to TEID or quintuple information and QoS information, and a correspondence between the QoS information and the SPI, and map or filter the downlink data. The embodiments of the present invention can ensure that the QoS is differentiated for different services when the terminal accesses from the HeNB/HNB, and the QoS requirements are preferentially met to improve the user experience. BRIEF abstract

1 is a schematic structural diagram of an HeNB accessing an EPS according to the related art;

2 is a schematic structural diagram of an HNB accessing UMTS according to the related art;

2a is a schematic structural diagram of an HNB accessing an EPS according to the related art;

3 is a schematic flowchart of statically establishing multiple SAs and implementing QoS control according to the present invention; FIG. 4 is a schematic flowchart of dynamically establishing multiple SAs and implementing QoS control according to the present invention; FIG.

6 is a schematic structural diagram of a downlink mapping relationship according to the present invention;

Figure 7 is a schematic structural view of the upper and lower filters of the present invention;

8 is a flowchart of Embodiment 1 of the present invention (SeGW parses Sl/Iuh messages, based on T1-T2 architecture);

9 is a flow chart of the second embodiment of the present invention (SeGW parses Sl/Iuh messages, based on the T1-T3 architecture);

10 is a flowchart of Embodiment 3 of the present invention (SeGW does not parse Sl/Iuh messages, based on T1-T2 architecture);

FIG. 11 is a flowchart of Embodiment 4 of the present invention (the SeGW does not parse the Sl/Iuh message, and is based on the T1-T2 architecture). Preferred embodiment of the invention

In the prior art, different services cannot guarantee the QoS required for their characteristics. The most direct solution is to establish multiple IPsec tunnels between the HeNB/HNB and the SeGW, and different IPsec tunnels transmit different. Business, to achieve the purpose of distinguishing treatment.

In the prior art, an IPSec tunnel/SA (Security Association) has been established. Cheng Wei: IKEv2 (Internet Key exchange) initialization negotiation between two network elements, establish an IKE-SA, and then establish multiple sub-SAs (Child-SA). Each SA (including sub-SAs) is unidirectional, and each SA has a specific SPI (Security Parameter Index) identifier. Because the SA is unidirectional, its identity SPI is also divided into uplink and downlink SPI. In the current HeNB/HNB system, only a single IPSec tunnel (a pair of SAs) is supported, and multiple IPsec tunnels (multiple pairs of SAs) are not supported.

The basic idea of the present invention is: HeNB/HNB and SeGW establish multiple IPSec tunnel/SA pairs, different IPsec tunnel/SA pairs are identified by different SPIs (pairs), and fixed network provides different QoS guarantees according to SPI (pair) .

Specifically, the method includes: establishing one or more IPsec tunnels between the first network element and the SeGW;

The SeGW reports the correspondence between the IPsec tunnel information and the IP data flow information in the downlink direction to the fixed network element by using the second network element, and the SeGW or the first network element sends the IPsec tunnel information in the uplink direction by using the second network element. The correspondence information between the IP data stream information is reported to the fixed network element; the QoS control is performed by the fixed network element.

An IPsec tunnel can be established between the first network element and the SeGW in a static or dynamic manner. The core network sends the IP data stream information to the first network element and/or the SeGW, and establishes a correspondence between the IPsec tunnel information and the IP data stream information.

The IPsec tunnel information can be SPI or DSCP information;

The IP data stream information is one or more of the following information: quintuple information, TEID (Tunnel End Point Identifier), RB-ID (radio-mounted identifier), QoS rule, TFT or PF The quintuple information includes information of a source address, a destination address, a source port number, a destination port number, and a protocol number.

In a specific embodiment, the correspondence information sent to the fixed network element is correspondence information between the SPI and the QoS rule. After the IPsec tunnel/SA is established, the HeNB/HNB subsystem sends the SPI and QoS relationship to the fixed network element. The fixed network element provides a distinction between the transport packets based on different SPIs and their corresponding QoS rules. Level QoS guarantee. The first network element creates an uplink mapping table or a filter according to the RB-ID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SPI, and maps or filters the uplink data.

The SeGW creates a mapping table or a filter in the downlink direction according to the TEID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SP1, and maps or filters the downlink data.

And the solid control function for receiving the correspondence information between the Psec tunnel information and the IP data stream information, the BPCF provides a hierarchical QoS guarantee for the transmission data, or the BPCF and other fixed network elements, for example BNG/BRAS (Broadband Network Gateway/Broadband Remote Access Server) provides a differentiated QoS guarantee for transmitting data.

In addition, in the step that the SeGW reports the correspondence information between the IPsec tunnel information and the IP data flow information in the downlink direction to the fixed network element by using the second network element, the SeGW sends the corresponding relationship information by using a notification request message. Sending to the second network element; the second network element sends the corresponding relationship information to the fixed network element by using the S9* interface session message;

In the step of reporting, by the second network element, the correspondence information between the IPsec tunnel information and the IP data flow information in the uplink direction to the fixed network element by the second network element, the SeGW, by using the notification request message, Corresponding relationship information is sent to the second network element, or the first network element sends the corresponding relationship information to the second network element by using a resource request message or a resource modification request message; the second network element passes the S9* interface. The session message sends the corresponding relationship information to the fixed network element.

The S9* interface refers to the modified or enhanced S9 interface.

Correspondingly, the system for implementing the quality of service control in the embodiment of the present invention includes: a first network element, a second network element, an SeGW, and a fixed network element, which are implemented as described above.

The key technologies of the present invention are discussed below.

(a) IPSec tunnel / SA creation (static)

In this scenario, after the He B/HNB is powered on, multiple (such as m) IPsec tunnels are established with the SeGW. Each tunnel corresponds to a different QoS rule range, and each tunnel corresponds to the uplink and downlink SA. Each SA corresponds to its respective SPI, corresponding to Figure 3.

m different IPsec channels are arranged according to a certain priority. When user data arrives, the data packets are mapped/matched to the IPsec tunnel/SA according to the priority order, and which tunnel is mapped/matched, which one is used. Tunnel transmission.

As a specific implementation, you can set a lower priority IPsec tunnel to serve the BE.

( Best Effort, best-effort) business or business that cannot be mapped/matched. That is to say: M-1 tunnels correspond to specific QoS or QoS ranges. These M-1 tunnels are called "private tunnels". An IPsec tunnel has no specific QoS requirements, which is called "default/default tunnel". After the user data arrives, map/match to the M tunnels one by one, and which tunnel is mapped/matched to which tunnel, if the former M-1 IPsec tunnels are not suitable for transmitting a certain service or the service is fundamental. Without specific QoS requirements, the service can be mapped/matched to the "default/default tunnel" by default.

As a specific implementation, a specific tunnel is selected from M tunnels (in general, the tunnel has the highest priority and QoS requirements) as a "signaling tunnel", and all 3GPP control planes transmitted through the IPsec tunnel. Signaling is transmitted through this particular "signaling tunnel".

If there is a "signaling tunnel", the signaling tunnel is prioritized over other tunnels, that is, a signaling tunnel is established after the HeNB/HNB access authentication, and the registration signaling or other information sent to other networks by the subsequent HeNB is transmitted. Control plane signaling service.

The establishment of the tunnel can be initiated by the HeNB/HNB or the SeGW. Different IPsec tunnels can be independent IPsec tunnels or multiple IPSec tunnels/sub-SAs (CMd-SAs) belonging to the same family.

(ii) Creation of IPSec tunnel/SA (dynamic)

In this scenario, when a certain user has a S1/Iuh interface message (for example, an attach/PDN connection setup/bearer setup/bearer modification request) and a specific QoS rule is required, the HeNB/HNB/SeGW determines according to the relevant rules. This QoS requires the establishment/modification/deletion of a proprietary SA/IPsec tunnel to guarantee QoS. That is, the solution differs from (1) in that it is not the HeNB that establishes multiple IPsec tunnels with different QoS when powering up, but decides to create a new IPSec tunnel when there is a specific QoS requirement for the service. See Figure 4.

Similar to (1), each IPsec tunnel corresponds to a different QoS range, for each IPsec tunnel. SAs correspond to their respective SPIs.

As a specific implementation, a "default/default tunnel" can be established when the HeNB/HNB is powered on. The tunnel serves the BE service or when all proprietary IPsec tunnels cannot be mapped/matched.

As a specific implementation, a specific tunnel can be established when the HeNB/HNB is powered on (generally, the tunnel has the highest priority and QoS requirements) as a "signaling tunnel", all transmitted through the IPsec channel. 3GPP control plane signaling is transmitted over this particular "signaling tunnel".

If there is a "signaling tunnel", the signaling tunnel is prioritized over other tunnels, that is, a signaling tunnel is established after the HeNB/HNB access authentication, and the registration signaling for the subsequent HeNB/HNB to other networks is transmitted. Or other control plane signaling services.

The establishment of the tunnel can be initiated by the HeNB/HNB or SeGW. Different IPsec tunnels can be independent IPsec tunnels or multiple IPSec tunnels/child SAs belonging to the same family.

(iii) Mapping table / filter structure

The HeNB/HNB acts as an endpoint of the IPsec tunnel and stores an upstream data mapping table/filter. The mapping table/filter is used to map/match the data packet (uplink) to the appropriate IPsec tunnel. The structure of the filter is shown in Figure 5. In the figure, there is a one-to-one or many-to-one relationship between the radio bearer and the QoS range, and the QoS range has a one-to-one relationship with the uplink SA (SPI) of the IPsec tunnel. In this way, the correspondence between the identity of the radio bearer (here identified by RB-ID, Radio Bearer Identity) and SPI is established.

The radio bearer and QoS range, as well as the radio bearer and uplink SA/SPI are not necessarily the corresponding relationship. It is possible that multiple RB-IDs correspond to the same SPI (as shown in Figure 5), or vice versa. This depends on the granularity of the QoS of the radio bearer and the QoS of the IPsec tunnel. But the QoS scope and SPI are - the corresponding relationship. The following SeGW is the same.

As another endpoint of the IPsec tunnel, the SeGW stores a downlink data mapping table/filter, which is used to map/match the data packet (downlink) to the appropriate IPsec tunnel. The structure of the mapping table/filter is as shown in FIG. 6. In the figure, there is a one-to-one or many-to-one relationship between the Sl/Iuh bearer (belonging to the GTP bearer) and the QoS range, and the QoS range and IPsec tunnel/SPI storage. In a one-to-one relationship. Thus, a one-to-one or many-to-one relationship between the identifier TEID and the SPI carried by the Sl/Iuh is established.

The mapping table/filter may have another structure (referred to herein as structure 2), which is different from the RB-ID or TEID described above and establishes a one-to-one or one-to-one correspondence relationship with the SPI (the above structure is called structure one). ), but the quintuple of the data packet (source address, destination address, source port number, destination port number, protocol number of the data packet) establishes a one-to-one or many-to-one correspondence with the SPI. As shown in Figure 7. The mapping table/filter of the structure 2 can be used on the SeGW or the HeNB/HNB, but the corresponding QoS range, SPI, and quintuple are downlink and uplink respectively.

(4) Mapping table / filter generation

In the EPS/UMTS system, the terminal accesses the EPS/UMTS, or establishes a PDN connection, or initiates a dedicated bearer setup, or initiates a dedicated bearer setup on the network side. The final operation is attributed to the network element MME of the EPS/UMTS network. The SGSN sends a message on the S1/Iuh interface to the HeNB/HNB (for example: initial context setup request/attach accept/bearer setup request/PDN connection accept), and the message carries the bearer QoS (except the default bearer) rule (also May include quintuple information). According to the prior art, after receiving the message, the HeNB/HNB determines to modify/create/delete a radio bearer (RB) according to the carried QoS, that is, there is a correspondence between the QoS and the radio bearer. In this invention, the HeNB/HNB finds the "QoS range" corresponding to the corresponding IPSec tunnel according to the QoS, so that the correspondence between the QoS and the SA identifier SPI of the IPSec tunnel is established. In this way, the identity of the radio bearer, the QoS of the bearer, and the SPI establish a correspondence. This corresponding relationship is the mapping table/filter of the bearer. Of course, different bearers have different bearer mapping tables/filters, and different mapping tables/filters on different terminals are also different.

If the SeGW intercepts the Sl/Iuh message, the SeGW acquires the QoS of the bearer after intercepting the message on the Sl/Iuh interface (for example: initial context setup request/attach accept/bearer setup request/PDN connection acceptance) (except the default bearer) Rules and bearers identify TEID (or quintuple information). Based on the QoS, the SeGW finds the corresponding QoS scope of the IPSec tunnel. This establishes the correspondence between the QoS and the downlink SA identifier SPI of the IPSec tunnel. Thereby, the correspondence between the TEID, the bearer QoS and the SPI is established, and the corresponding relationship is the mapping table/filter of the bearer. Of course, different bearers have different bearer mapping tables/filters, and different mappings/filters on different terminals are also different. If the SeGW does not intercept the Sl/Iuh message, the downlink mapping table/filter may be trusted by other network elements, such as HeNB/HNB PF or HeNB/HNB.

Similarly, the mapping table/filter on the HeNB/HNB can also be commissioned by other network elements, such as SeGW, HeNB/HNB PF, and so on. The specific operation depends on the specific implementation, which will be introduced in the following process examples.

For another form of mapping table/filter, the Sl/Iuh message (eg: initial context setup request/attach accept/bearer setup request/PDN connection accept) message carries the quintuple information and QoS of the service data packet. information. Therefore, both the SeGW and the HeNB can establish a correspondence between quintuple, QoS, and SPI, and the correspondence can be used as a filter for the bearer.

(5) Mapping table / filter application

According to (4), the mapping table/filter on the HeNB/HNB/SeGW is: the identifier/TEID of the radio bearer, the QoS of the bearer, and the correspondence between the SPI. Therefore, after the HeNB/HNB obtains the uplink data from the radio bearer, the IPsec tunnel can be found according to the RB-ID of the radio bearer of the data packet, and the data packet is mapped/matched into the appropriate IPSec tunnel. After obtaining the downlink data from the Sl/Iuh bearer, the SeGW can find the IPsec tunnel according to the TEID carried by the Sl/Iuh of the data packet, and map/match the data packet to the appropriate IPSec tunnel.

Another form of the corresponding filter, when the HeNB/HNB/SeGW receives the uplink/downlink data packet, finds the corresponding SPI according to the quintuple of the data packet, and matches the data packet to the appropriate IPSec tunnel.

(6) Reporting of correspondence

After the mapping/filter is generated, the HeNB/HNB/SeGW is used to locally map/filter the data packets, and the QoS and SPI correspondences need to be reported to the fixed network through the HeNB/HNB PF, so that the fixed network learns the SPI and the SPI. The QoS relationship can guarantee the QoS of data packets transmitted in different IPSec tunnels.

When the HeNB/HNB reports the "Relationship between SPI and QoS" to the fixed network through the HeNB/HNB PF, the HeNB HNB first reports the "correspondence" to the HeNB through the "Resource Request/Modify Request/Release Request" message of the T2 interface. /HNB PF, the HeNB/HNB PF reports the S9* interface session message to the BPCF of the fixed network, and the other network elements of the BPCF and the fixed network are executed according to the corresponding relationship. Lines distinguish between different levels of QoS control.

As a specific implementation manner, the PF is an intermediate network element of the HeNB/HNB and the SeGW interworking mapping relationship/filter and IP data flow information, in addition to the intermediate network element that reports the QoS and SPI correspondence to the fixed network. , embodied in the subsequent process.

In the present invention, the IPsec tunnel information refers to identification information identifying the IPsec tunnel/SA, such as: SPI. It can also be other information that uniquely identifies an IPSec tunnel, such as DSCP (Differential Services Code Point). In the embodiments and key technical descriptions of the present invention, SPI is generally only mentioned as IPsec tunnel information, but the possibility of using other tunnel information such as DSCP is not excluded. That is to say, it can be equivalently replaced with other tunnel information such as DSCP, and the scheme can also be operated, which is also the content of the present invention.

The IP data stream information is identification information, policy information, and the like that can describe an IP data stream, including but not limited to one or more of the following information: a quintuple (source address, destination address, source port number, destination port) No., protocol number), TEID, QoS rules, TFT/PF, etc.

The correspondence between IPsec tunnel information and IP data stream information is any kind of IPsec tunnel information.

Correspondence between (either SPI or DSCP or other) and any one or several kinds of IP data stream information (quintuple, TEID, QoS rule, TFT/PF). In the embodiments of the present invention and the discussion of key technologies, the correspondence between SPI and QoS is a typical implementation. However, it is not excluded that other tunnel information such as DSCP and other QoS rules and other IP data stream information can be used to establish a correspondence. That is to say, the SPI can be equivalently replaced with other IPsec tunnel information such as DSCP, and the QoS rule can be equivalently replaced with other IP data stream information to establish a correspondence, and the scheme can also be operated, which is also the content of the present invention.

Process embodiment

Embodiment 1: The SeGW parses the Sl/Iuh interface message, based on the T1T2 architecture (Fig. 8). Step 801: The UE initiates an attach/PDN connection establishment operation, and the related processing of the wireless side and the core network. This is a prior art.

Step 802: After the terminal accesses the EPS/UMTS through the HeNB/HNB, whether it is attached or not, PDN connection establishment, terminal initiated or private bearer setup initiated by the network side, and finally the corresponding message is sent by the network side to the HeNB/HNB, which is the GTP (GPRS Tunnel Protocol) of the Sl/Iuh interface. Control signaling, as shown in the message: Initial context setup request/attach accept/bearer setup request/PDN connection accept. The message carries the QoS rules corresponding to the bearer to be created/modified/released, and the uplink and downlink TEID, quintuple, and the like, that is, the IP data stream information.

The signaling of the Sl/Iuh interface is intercepted by the SeGW when the SeGW passes through the SeGW, and the IP data stream information in the signaling is obtained, and then the Sl/Iuh message is sent to the HeNB/HNB.

Step 803: The SeGW obtains the IP data flow information from the GTP message, and determines to create a new SA (dynamic scheme) or select the SA (dynamic or static scheme) according to the relevant policy.

If a new SA is created, the SeGW sends a "Create Sub-AS Request" to the HeNB/HNB of the IKEv2 message, and carries the SPI of the downlink SA selected by the SeGW in the message.

The SeGW obtains QoS rules, TEIDs, and/or quintuple information from the GTP messages of the Sl/Iuh interface. The SeGW determines whether the received QoS rules need to be newly created or existing SAs according to the information configured by the SeGW. The requirements of this QoS rule. The SPI of the newly created or selected SA can be associated with the QoS rule. In the GTP message, the QoS rule and the TEID have a corresponding relationship, so the TEID and the SPI establish a correspondence, or a mapping (MAPPING) relationship. , see Figure 6.

If the correspondence between SPI and TEID is not established, but the correspondence between SPI and quintuple is established according to QoS rules, the correspondence is called "filter", see Figure 7.

The mapping table/filter generated on the SeGW is used to filter/map downstream packets, called downlink (DL) mapping/filters.

Step 804: The SeGW sends a "Create Sub-SA Request" to the HeNB/HNB, and carries the SPI of the downlink SA selected by the SeGW in the message; after receiving the request, the HeNB/HNB selects the SPI of the uplink SA, and "creates" The child SA responds with a "message sent to SeGW.

Step 805: The HeNB/HNB receives the Sl/Iuh message and obtains the QoS rule, TEID, and/or quintuple information.

The HeNB/HNB can determine, according to the QoS rule, which radio bearer the GTP bearer corresponds to, That is, the corresponding relationship is established with the radio bearer identifier RB-ID (prior art); the information configured by the HeNB/HNB itself determines whether the received QoS rule needs to create a new SA or an existing SA to satisfy the requirement of the QoS rule. . The SPI of the newly created or selected SA can be associated with the QoS rule; thus, the RB-ID and the SPI establish a correspondence (mapping relationship/mapping table) through the QoS rule, as shown in FIG. 5.

If the correspondence between SPI and RB-ID is not established, but the correspondence between SPI and quintuple is established according to QoS rules, the correspondence is called "filter", see Figure 7.

The mapping table/filter generated on the HeNB/HNB is used to filter/map the upstream packets, called the uplink (UL) mapping/filter.

In the above steps 803-805, there is no specific sequence relationship. The initiation of the establishment of the sub SA may be

The SeGW may also be a HeNB/HNB, and the uplink and downlink SAs established by a pair of IKEv2 messages may not necessarily serve the uplink and downlink data streams on the same bearer. After the SeGW or the HeNB/HNB discovers the newly received QoS rule, it first checks whether there is an SA that is not associated with the QoS in the existing SA. If yes, it establishes an association with the SA; if not, it initiates Newly built and associated with it;

The above mentioned may have "SAs not associated with QoS". This can happen in several scenarios: 1) Because the IKEv2 messages are sent in pairs (request + response), the requester chooses SPI (corresponding A SA can establish the correspondence between SPI and QoS; however, the responder does not know what QoS the SA corresponding to the selected SPI should be associated with, so there is an SA that is not associated with QoS. When the receiver receives the QoS, it can establish the association between the QoS and the "unavailable SA". 2) The EPS/UMTS core network may send a request to release the bearer in addition to the new bearer request. Therefore, after a bearer is released, the SA may be idle (no binding relationship with QoS).

Step 806: The HeNB/HNB forwards the "SPI and QoS correspondence" to the HeNB/HNB PF through the "resource request/modification request" message of the T2 interface. The HeNB/HNB PF replies with a response message to the HeNB/HNB;

In step 807, the SeGW reports the uplink "SPI and QoS correspondence" to the HeNB/HNB PF through the "Notification Request" message of the T1 interface. The HeNB/HNB PF replies with a response message to the SeGW; After receiving the messages of steps 806 and 807, the HeNB/HNB PF associates the corresponding relationship reported by the two sessions. In the prior art, the T1 session and the T2 session can be associated with each other. Therefore, according to the association relationship of the session, the reported upper and lower levels can be reported. The line "SPI and QoS correspondence" is associated with and reported to the fixed network BPCF through the S9* interface. The BPCF or BPCF entrusts other fixed network elements to guarantee QoS for the data packets transmitted in different IPsec tunnels.

Note: If it is a static SA establishment scenario, you can use the "SPI and QoS correspondence" in step S806. You can also use an optimization method, that is, the correspondence between the SPI and QoS rules can be established initially. When all SAs are completed, they are reported to the HeNB/HNB PF.

Step 808: The HeNB/HNB responds to the EPS core network with the GTP message of the Sl/Iuh interface.

Embodiment 2: SeGW parsing Sl/Iuh message, based on T1T3 architecture (Fig. 9)

Step 901: The UE initiates an attach/PDN connection establishment operation, and the related processing of the wireless side and the core network, which is a prior art.

Step 902: After the terminal accesses the EPC/UMTS through the HeNB/HNB, whether it is an attachment, a PDN connection establishment, a terminal initiated, or a dedicated bearer initiated by the network side, the network side sends a corresponding message to the HeNB/ HNB, this message is the GTP control signaling of the Sl/Iuh interface. That is, the message shown in the figure: initial context establishment request/attach acceptance/bearer establishment request/PDN connection acceptance, for example, the message carries the QoS rule corresponding to the bearer to be created/modified/released, and the uplink and downlink TEID, quintuple And other information, that is, IP data stream information.

The GTP signaling of the Sl/Iuh interface is intercepted by the SeGW when the SeGW is passed, and the IP data stream information in the signaling is obtained, and then the Sl/Iuh message is sent to the HeNB/HNB.

Step 903: The SeGW obtains the IP data flow information from the GTP message, and determines to create a new SA (dynamic scheme) or select the SA (dynamic or static scheme) according to the relevant policy.

The SeGW obtains QoS rules, TEIDs, and/or quintuple information from the GTP messages of the Sl/Iuh interface. The SeGW determines whether the received QoS rules need to be newly created or existing SAs according to the information configured by the SeGW. The requirements of this QoS rule. This new or selected SA The SPI can be associated with the QoS rules. In the GTP message, the QoS rule and the TEID have a corresponding relationship. Therefore, the TEID and the SPI establish a correspondence, or a mapping (MAPPING) relationship, as shown in FIG. 6.

The mapping table/filter generated on the SeGW is used to filter/map the downstream packets, which is called the downlink (DL) mapping table/filter.

Step 904: The SeGW sends a "Create Sub-SA Request" to the HeNB/HNB, and carries the SPI of the downlink SA selected by the SeGW in the message; after receiving the request, the HeNB/HNB selects the SPI of the uplink SA, and "creates" The child SA responds with a "message sent to SeGW.

Step 905: The SeGW sends the Sl/Iuh message intercepted in step 902 to the HeNB/HNB in the newly created or selected SA.

Alternatively, the Sl/Iuh message does not necessarily pass through the newly created or selected SA, but carries the newly created or selected SA SPI in the Sl/Iuh message.

Step 906: The HeNB/HNB can determine the SA according to the SA from which the Sl/Iuh message is sent.

Corresponding relationship between the IP flow information and the SA on the bearer to be established by the Sl/Iuh message;

Or the HeNB/HNB can determine the correspondence between the IP flow information and the SA on the bearer to be established by the Sl/Iuh message according to the SPI carried in the Sl/Iuh message.

Based on the above relationship, the HeNB/HNB generates an uplink data MAPPING table using the same mechanism as the S805.

Step 907: Because the SeGW acquires the Sl/Iuh message content in step 902, and establishes the SA in step 904, and obtains the corresponding SPI, the SeGW generates a downlink MAPPING table;

Step 908: According to the foregoing operation, the SeGW may simultaneously generate the correspondence between the uplink and downlink QoS rules and the SPI, and send the HeNB/HNB PF through the notification request message.

The SeGW reports the uplink and downlink "SPI and QoS correspondence" to the HeNB/HNB PF through the "Notification Request" message of the T1 interface. The HeNB/HNB PF replies with a response message to the SeGW;

The HeNB/HNB PF reports to the fixed network BPCF through the S9* interface, and the BPCF or BPCF entrusts other fixed network elements to guarantee QoS for transmitting data packets in different IPsec tunnels. Note: If the scene is statically established, you can use the corresponding relationship in step S908. You can also use an optimization method. That is, the correspondence between the SPI and the QoS rule can be used when all SAs are initially established. Just go to the PF.

Step 909: The HeNB/HNB responds to the EPS core network with the GTP message of the Sl/Iuh interface.

Embodiment 3: The SeGW does not parse the Sl/Iuh message, based on the T1T2 architecture (Fig. 10). Step 1001: The UE initiates an attach/PDN connection establishment operation, and the related processing of the wireless side and the core network. This is a prior art.

Step 1002: After the terminal accesses the EPS/UMTS through the HeNB/HNB, whether it is an attachment, a PDN connection establishment, a terminal initiated, or a dedicated bearer initiated by the network side, the corresponding message is sent by the network side to the HeNB/ HNB, this message is the GTP control signaling of the Sl/Iuh interface. That is, the message shown in the figure: initial context establishment request/attach acceptance/bearer establishment request/PDN connection acceptance, for example, the message carries the QoS rule corresponding to the bearer to be created/modified/released, and the uplink and downlink TEID, quintuple And other information, that is, IP data stream information.

Step 1003: The HeNB/HNB obtains related information according to the GTP message, and determines to create a new SA (dynamic scheme) or select an SA (dynamic or static scheme) according to the related policy.

If a new SA is created, the HeNB/HNB sends a "Create Sub SA Request" of the IKEv2 message to the SeGW, and carries the SPI of the uplink SA selected by the HeNB/HNB in the message.

The HeNB/HNB obtains the QoS rule, the TEID, and/or the quintuple information from the GTP message of the Sl/Iuh interface, and the HeNB HNB can determine, according to the QoS rule, which radio bearer the GTP bearer corresponds to, that is, the radio bearer identifier RB. -ID establishes the correspondence (prior art); the information configured by the HeNB/HNB itself determines whether the received QoS rule needs to create a new SA or an existing SA to satisfy the requirements of the QoS rule. The SPI of the newly created or selected SA can be associated with the QoS rule; thus, the RB-ID and the SPI establish a correspondence (map relationship/mapping table) through the QoS rule, as shown in FIG. 5.

A mapping table/filter generated on the HeNB/HNB is used to filter/map uplink data packets, called Uplink (UL) mapping table/filter.

Step 1004: The HeNB/HNB sends a "Create Sub-SA Request" to the SeGW, and carries the SPI of the uplink SA selected by the HeNB/HNB in the message; after receiving the request, the SeGW selects the SPI of the downlink SA, and "creates" The sub-SA responds with a "message sent to the HeNB/HNB.

Step 1005: The HeNB/HNB reports the uplink SPI and the HeNB/HNB PF through the T1 interface.

Correspondence between QoS and carrying downlink QoS rules;

Step 1006: The HeNB/HNB PF sends a downlink QoS rule to the SeGW.

Step 1007: The SeGW selects an SA according to the downlink QoS rule, and establishes a correspondence between SPI and QoS, that is, a correspondence between the downlink SPI and the QoS.

Step 1008: The SeGW sends a downlink SPI and QoS correspondence to the He B/HNBPF through the T2 interface.

The HeNB/HNB PF associates the correspondence between the uplink and downlink SPI and the QoS obtained in steps 1008 and 1005, and associates the corresponding relationship reported by the two sessions (prior art, the same as FIG. 8), and reports to the fixed network through the S9* interface. BPCF, the BPCF or BPCF entrusts other fixed network elements to guarantee QoS for transmitting data packets in different IPsec tunnels.

Step 1009: The HeNB/HNB responds to the EPS core network with the GTP message of the Sl/Iuh interface.

Embodiment 4: The SeGW does not parse the Sl/Iuh message, and is based on the T1T2 architecture (FIG. 11). Step 1101: The UE initiates an attach/PDN connection establishment operation, and the related processing of the wireless side and the core network. This is a prior art.

Step 1102: After the terminal accesses the EPS/UMTS through the HeNB/HNB, whether it is an attachment, a PDN connection establishment, a terminal initiated, or a dedicated bearer initiated by the network side, the network side sends a corresponding message to the HeNB/ HNB, this message is the GTP control signaling of the Sl/Iuh interface. That is, the message shown in the figure: initial context establishment request/attach acceptance/bearer establishment request/PDN connection acceptance, for example, the message carries the QoS rule corresponding to the bearer to be created/modified/released, and the uplink and downlink TEID, quintuple And other information, that is, IP data stream information.

Step 1103: The HeNB/HNB obtains related information according to the GTP message, and determines to create a new SA (dynamic scheme) or select an SA (dynamic or static scheme) according to the relevant policy. If a new SA is created, the HeNB/HNB sends a "Create Sub-SA Request" of the IKEv2 message to the SeGW, and carries the SPI of the uplink SA selected by the HeNB/HNB in the message.

If the correspondence between SPI and RB-ID is not established, but the correspondence between SPI and quintuple is established according to QoS rules, the correspondence is called "filter", see Figure 7. Uplink (UL) mapping/filter.

Step 1104: The HeNB/HNB sends a "Create Sub-SA Request" to the SeGW, and carries the SPI of the uplink SA selected by the HeNB/HNB in the message; after receiving the request, the SeGW selects the SPI of the downlink SA, and "creates" The sub-SA responds with a "message sent to the HeNB/HNB.

Step 1105: After step 1104, the HeNB/HNB can acquire the SPI of the downlink SA, and the HeNB/HNB acquires the downlink QoS rule, and the HeNB/HNB can generate the correspondence between the downlink QoS and the SPI.

The HeNB/HNB reports the correspondence between the uplink and downlink SPI and QoS to the HeNB/HNB PF through the T1 interface.

The HeNB/HNB PF reports the correspondence between the uplink and downlink SPI and QoS obtained in step 1105, and reports it to the fixed network BPCF through the S9* interface. The BPCF or BPCF entrusts other fixed network elements to ensure the data packets in different IPsec tunnels. QoS.

Step 1106: The He B/HNBPF sends a corresponding relationship between the downlink QoS rule and the SPI to the SeGW.

Step 1107: The SeGW establishes a downlink MAPPING table or a filter according to the downlink QoS rule. Step 1008: The He B/HNB responds to the EPS core network with the GTP message of the Sl/Iuh interface.

Embodiment 5:

In the above example, the uplink/downlink mapping table/filter, the SPI and QoS correspondence are generated by the HeNB/HNB and the SeGW respectively, or the HeNB/HNB respectively generate the uplink and downlink, and the PF mediation is advertised. Give the peer SeGW. Finally, the corresponding relationship between the SPI and the QoS is reported by the HeNB/HNB and the SeGW to the PF and finally to the fixed network (T1T2 architecture), or reported by the SeGW to the PF and finally to the fixed network (T1T3 architecture). The following scheme can be formed in the flow of the foregoing embodiment, and the processing described below is used to form a new embodiment.

1) As another implementation for the T1T3 architecture, the SeGW and the HeNB/HNB can respectively generate respective mapping tables/filters and "correspondence between SPI and QoS", and the HeNB/HNB will respond to the uplink "SPI and QoS". The relationship is sent to the SeGW through the extended IKEv2 message, and is reported by the SeGW to the PF through the T1 interface to the fixed network.

2) For the case where the SeGW does not parse the Sl/Iuh message, the HeNB/HNB can acquire the content of the Sl/Iuh message and send it to the SeGW through the extended IKEv2 message for the SeGW to generate the downlink mapping/filter and downlink SPI and QoS. Correspondence.

3) As a specific implementation, when the HeNB/HNB generates the uplink "relationship between SPI and QoS" but cannot report directly to the PF (T1T3 architecture, no T2 interface), the SeGW can obtain uplink based on "anti-mapping" uplink data. "Relationship between SPI and QoS". After the SeGW generates/acquires the uplink "Relationship between SPI and QoS", but cannot advertise the HeNB/HNB, the HeNB/HNB can obtain the uplink "Relationship between SPI and QoS" based on the "anti-mapping" downlink data system. That is to say, SeGW and HeNB/HNB can negotiate the correspondence between SPI and QoS through the demapping mechanism.

The demapping refers to: after the SeGW or the HeNB/HNB receives the data packet of the opposite end (HeNB/HNB or SeGW), the SPI of the IPSec header encapsulated by the data packet is used to search for the SPI generated by the pair. As the reverse SPI, the QoS rule, TEID, quintuple and other information corresponding to the data packet are reversed: Up/down QoS/TEID is mapped to lower/uplink QoS/TEID, source in quintuple information/ Destination address/port number exchange. After finding the SPI and the reverse processed QoS Rules, TEID, quintuple and other information are associated. The above is the anti-mapping mechanism. By doing so, it is possible to generate a "mapping table/filter" and "correspond relationship between SPI and QoS" of the peer.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may use software functions. The form of the module is implemented. The invention is not limited to any specific form of combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

The embodiments of the present invention can ensure that the QoS is differentiated for different services when the terminal accesses from the He B/HNB, and the services with high QoS requirements are prioritized to meet the QoS requirements and improve the user experience.

Claims

Claim

1. A method of implementing quality of service control, comprising:

The security gateway (SeGW) reports the correspondence between the Internet Protocol security (IPsec) tunnel information and the IP data flow information in the downlink direction to the fixed network element through the second network element, and the SeGW or the first network element passes the second The network element reports the correspondence between the IPsec tunnel information and the IP data flow information in the uplink direction to the fixed network element, and the quality of service (QoS) is controlled by the fixed network element;

2. The method of claim 1 wherein

The SeGW sends the correspondence information between the IPsec tunnel information and the IP data flow information in the downlink direction to the fixed network element through the second network element, and the SeGW or the first network element passes the IPsec in the uplink direction through the second network element. Before the mapping between the tunnel information and the IP data stream information is reported to the fixed network element, the method further includes:

3. The method of claim 2, wherein

An IPsec tunnel is established between the first network element and the SeGW in a static or dynamic manner.

The method according to any one of claims 1 to 3, wherein before the reporting of the correspondence information in the downlink direction and the uplink direction to the fixed network element, the method further includes:

The first network element and/or the SeGW receive the IP data flow information sent from the core network, and establish

Correspondence between IPsec tunnel information and IP data stream information.

5. The method according to any one of claims 1 to 3, wherein

The IP data stream information is one or more of the following information: quintuple information, tunnel endpoint identifier (TEID), radio bearer identifier (RB-ID), QoS rule, service flow template (TFT), or data packet. a filter (PF), wherein the quintuple information includes a source address, a destination address, and a source port Number, destination port number, and protocol number information.

The method according to claim 5, wherein the correspondence information received by the fixed network element is correspondence information between the SPI and the QoS rule.

7. The method of claim 6, wherein

The QoS control performed by the fixed network element refers to: the fixed network element is based on different SPIs and their corresponding

QoS rules provide differentiated QoS guarantees for transporting packets.

The method according to any one of claims 5, wherein the method further comprises: the first network element according to RB-ID or quintuple information and QoS information, and correspondence between QoS information and SPI The relationship creates an upstream mapping table or filter, and maps or filters the uplink data.

9. The method according to any one of claims 1 to 3, wherein

10. The method according to any one of claims 1 to 3, wherein

In the step that the SeGW sends the correspondence information between the IPsec tunnel information and the IP data stream information in the downlink direction to the fixed network element by using the second network element, the SeGW sends the corresponding relationship information by using a notification request message. Sending to the second network element; the second network element sends the corresponding relationship information to the fixed network element by using the S9* interface session message;

11. A system for implementing quality of service control, comprising: a first network element, a second network element, and a SeGW And fixed network elements, wherein

12. The system of claim 11 wherein:

The first network element is further configured to: establish more than one IPsec tunnel with the SeGW.

13. The system of claim 11 or 12, wherein

14. The system of claim 12, wherein

The first network element is further configured to: according to RB-ID or quintuple information and QoS information, and

The mapping between the QoS information and the SPI creates an upstream mapping table or filter, and maps or filters the uplink data.

The SeGW is further configured to: create a mapping table or a filter in the downlink direction according to the TEID or the quintuple information and the QoS information, and the correspondence between the QoS information and the SPI, and map or filter the downlink data.