CN1992671B - Method for transmitting IP header compressed data packets in the third generation evolution system - Google Patents

Abstract

The invention discloses a method for transmitting IP header compressed data packets in a third-generation evolution system. The IP header is compressed on user equipment and core network equipment, and the IP header is compressed on the core network equipment and the evolved wireless access network equipment respectively. A user creates a user context; and a tunnel is established for the user between the two devices; the evolved wireless access network device maps the wireless interface quality of service QoS parameters of the user IP header compressed data packet to bearer according to the user context information Network QoS parameters or vice versa; encapsulate the IP header compressed data packet of the user with the bearer network QoS parameters, and transmit it through the corresponding tunnel; transmit the channel between the evolved radio access network device and the user equipment with the channel corresponding to the wireless interface QoS parameters User's IP header in compressed packets. The invention can simply and effectively implement the IP header compression technology on the user equipment and the core network equipment in the evolved 3GPP system, and improve the wireless transmission efficiency.

Description

Method for transmitting IP header compressed data packets in the third generation evolution system

technical field

The invention relates to the technical field of mobile communication, in particular to a method for transmitting IP header compressed data packets in a third-generation evolution system.

Background technique

Since the FP (Frame Protocol) frame of the voice service is less than 40 bytes, the overhead generated by the traditional UDP/IP (User Datagram Protocol/Internet Protocol) header reaches 50-100%. The generated overhead is reduced from 28 bytes to 2-3 bytes, thereby greatly reducing the overhead of short packet transmission and improving the efficiency of wireless packet service transmission.

In the traditional 3GPP system, IP header compression is implemented in the RNC (Radio Network Controller) of UE (User Terminal) and UTRAN (Universal Terrestrial Radio Access Network), as shown in Figure 1:

In Fig. 1, the function of IP header compression is performed on the UE and the RNC in the radio access network, and the RNC stores the relevant IP header compression context. When the user UE moves from one radio access network (UTRAN A in the figure) to another radio access network (UTRAN B in the figure), the original radio access network (such as the RNC in UTRAN A) ) in the IP header compression context is transmitted to the new radio access network (RNC in UTRAN B). When the user moves from UTRAN B to UTRAN C, the core network device SGSN A serving the UE switches to SGSN B. Because SGSN has nothing to do with IP header compression, SGSN has no context about IP header compression. Therefore there is no IP header compression related context transfer in the SGSN when switching between SGSNs.

Between RNC and UE, there is another network entity, Node B, which transparently transmits compressed IP data packets. Data transmission is carried out between Node B and RNC through ATM (Asynchronous Transfer Mode) or IP (Internet Protocol) bearer network. When data transmission is carried out between Node B and RNC through the ATM bearer network, because the ATM bearer network has a QoS guarantee mechanism, it can guarantee the QoS of different services. When UDP/IP is used for transmission between Node B and RNC, there may also be IP routers and IP switching devices in the middle, because it is not necessary to use the TOS (Type of Service) or Traffic Class identifier in the IP header to set the IP data packet Priority scheduling, which mainly realizes the guarantee of QoS for different services through high-speed IP switching technology.

In order to ensure the correct transmission of the IP stream compressed by the IP header, the tunneling technology needs to be used. In the Release version before Release7, 3GPP used the GTP (GPRS Tunneling Protocol) protocol between the RNC and the SGSN (General Packet Radio Service Support Node) of the core network, and for each user, if its IP address is different or/ Different from the QoS of the Session (session) used, a different GTP tunnel is used; this GTP tunnel determines the QoS of the Session on it. If the QoS is different, different tunnels will be established; and even if the QoS is the same, if the APN (Access Point Name) is different, different tunnels will also be used.

Moreover, in the traditional 3GPP system, there may be an Iur interface between different RNCs, so that when the UE switches between different RNCs, between the DRNC (drift RNC) and the SRNC (serving RNC), the same as the RNC and Same as SGSN, establish multiple GTP-U (GPRS Tunneling Protocol User Plane) tunnels: Sessions with different IPs (actually different APNs) or/and QoS need to establish multiple GTPs between SRNC and DRNC during handover Tunnel; at the same time, multiple GTP tunnels should be established between the RNC after SRNS relocation and the SGSN.

However, for the 3GPP evolved system, the network element between the UE and the core network is EUTRAN (Evolved Radio Access Network). If the network element is the access system gateway, the context content of its IP header compression is stored in both the UE and the access system gateway of the core network, as shown in Figure 2:

When the UE performs handover, if the access point of the core network that the UE accesses remains unchanged, as shown in process ① in Figure 2, the UE switches from the wireless access network A of the access system network A to the wireless access network B, then The IP header compression context content of the core network access system remains unchanged; if the access point of the core network accessed by the UE changes, the original core network access point needs to transfer the IP header compression context to the new core network access point . The network node located in the middle of the IP header compression position (UE and core network), such as EUTRAN, does not have the IP header compression context, so there is no process of transferring the IP header compression context during the handover process. As shown in Figure 2, in process ②, the UE moves from radio access network B to radio access network C, and access system gateway A of the core network needs to transfer its IP header compression context to access system gateway B.

When the access system gateway of the core network and the UE implement IP header compression, the access system gateway of the core network and the UE must save the IP header compression context, and transfer it between the access system gateways during the handover process. At this time, the intermediate node between the access system gateway and the UE accesses the system, such as 3GPP E_UTRAN, there is no IP header compression context data, so the acquisition, setting and scheduling of the QoS parameters of the IP data flow corresponding to the IP header compression Difficulties exist, specifically in the following aspects:

1. The QoS parameter cannot be obtained. Because the access system gateway of the core network and the UE use IP header compression, the network node E_UTRAN between the access system gateway and the UE cannot see the content of the IP header, so it cannot know the QoS parameters carried in the IP header of the IP data flow.

2. The QoS parameters of the air interface cannot be matched with the QoS of the IP layer data flow. Due to the use of IP header compression, EUTRAN cannot know the identification parameters in the IP header, and it cannot map the data with QoS parameters obtained from the air interface to the corresponding QoS IP data flow; The IP header compressed data obtained by the system gateway is sent to the UE with the corresponding QoS parameters of the air interface, so that the wireless resources cannot be set and scheduled with the appropriate QoS parameters.

3. Similar to traditional 3GPP systems, one or more GTP tunnels need to be established for each user between RNC and SGSN, and between different RNCs, and also need to be used between EUTRAN and access system gateways, and between different EUTRANs Tunnel technology to deliver IP header compressed data packets. The establishment of multiple GTP tunnels will increase the complexity of system implementation and handover, and will reduce the probability of successful handover performance and reliability.

Contents of the invention

The purpose of the present invention is to provide a method for transmitting IP header compressed data packets in a third-generation evolution system, so as to solve the problem that E_UTRAN cannot know the QoS parameters in the IP header when using the IP header compression technology in the 3GPP evolution system, so that the entire wireless air The interface and the bearer network cannot perform QoS setting and scheduling, and multiple tunnels need to be used between the E_UTRAN and the access system gateway, and between different E_UTRANs, making the system complex and affecting the handover performance. Implement IP header compression technology in the 3GPP system to improve wireless transmission efficiency.

For this reason, the present invention provides following technical scheme:

A method for transmitting IP header compressed data packets in a third-generation evolution system, the third-generation evolution system includes a core network, an evolved wireless access network, and user equipment, and the IP header is performed on the user equipment and the core network equipment compressing, the method comprising:

Create a user context for each user on the core network device and the evolved radio access network device;

When it is necessary to transmit the user's IP header compressed data packet between the evolved wireless access network device and the core network device, a corresponding tunnel is established for the user;

The evolved wireless access network device maps the wireless interface quality of service QoS parameters of the user's uplink IP header compressed data packet to the bearer network QoS parameters or maps the bearer network QoS parameters of the user's downlink IP header compressed data packet to the wireless interface according to the user context information. Interface QoS parameters;

Encapsulate the user's IP header compressed data packet with the bearer network QoS parameters, and transmit it between the evolved wireless access network device and the core network device through the tunnel corresponding to the user;

The IP header compressed data packet of the user is transmitted between the evolved radio access network device and the user equipment through a channel corresponding to the wireless interface QoS parameter.

The user context created for each user on the core network device at least includes: user identity, tunnel context;

The user context created for each user on the evolved wireless access network device at least includes: a wireless interface user identifier, a wireless interface uplink and downlink QoS parameter set, a tunnel context, and a QoS mapping table;

The tunnel context at least includes: local tunnel node identifier, remote tunnel node identifier, bearer network type, and downlink QoS on the bearer network.

Each user has a unique radio interface user identifier on the radio interface, and corresponds to the local tunnel node identifier TEID used by it in the evolved radio access network device.

Each user has an International Mobile Subscriber Identity (IMSI) and multiple other non-access stratum identities, which correspond to the local tunnel node identities used in the core network equipment.

The step of mapping the wireless interface QoS parameters of the user's uplink IP header compressed data packet to the bearer network QoS parameters by the evolved wireless access network device according to its user context information includes:

The evolved radio access network device obtains the radio interface QoS parameters of the data packet according to the channel and radio interface parameters of the IP header compressed data packet sent by the receiving user equipment;

Map the wireless interface QoS parameters to bearer network QoS parameters according to the QoS mapping table in the user context information corresponding to the user.

The step of mapping the bearer network QoS parameters of the user downlink IP header compressed data packet to the wireless interface QoS parameters by the evolved radio access network device according to the user context information includes:

The evolved wireless access network device obtains the bearer network QoS parameter in the IP header of the IP header compressed data packet transmitted by the core network device through the tunnel;

Map the bearer network QoS parameters to wireless interface QoS parameters according to the QoS mapping table in the user context information corresponding to the user.

The method further comprises:

The tunnel established for the user is carried on the bearer network based on the Internet Protocol version 4 IPv4 protocol or the Internet Protocol version 6 IPv6 protocol or based on Multi-Protocol Label Switching MPLS.

If the tunnel established for the user is carried on the bearer network based on the IPv4 protocol, the downlink QoS on the bearer network in the context of the tunnel corresponds to the service type TOS parameter in the IPv4 header;

If the tunnel established for the user is carried on the bearer network based on the IPv6 protocol, the downlink QoS on the bearer network in the context of the tunnel corresponds to the traffic type Traffic Class parameter in the IPv6 header;

If the tunnel established for the user is carried on the MPLS-based bearer network, the downlink QoS on the bearer network in the context of the tunnel corresponds to the DSCP in the MPLS header.

Preferably, the evolved radio access network device and the core network device tear down the tunnel corresponding to the user according to the active state and/or available resource state of the user equipment, and delete or prohibit the user on the evolved radio access network device and the core network device tunnel context information.

Preferably, when the user equipment is turned off or the user equipment moves to a new wireless access system, the tunnel corresponding to the user is removed, and the tunnel context information corresponding to the user on the evolved radio access network device and the core network device is deleted or prohibited.

Preferably, when the user equipment switches between different evolved radio access networks, one and only one corresponding handover tunnel is established for the user between the source radio access network device and the destination radio access network device to transmit the source Data that has not been sent by the radio access network device to the user equipment.

Preferably, a switching timer is set; when the switching tunnel is established, the switching timer is started; when the switching timer expires, the switching tunnel corresponding to the user is deleted.

The core network device is specifically: an access system gateway or a mobility management entity/user plane entity.

The evolved radio access network device is specifically: a radio network controller and/or a base station.

As can be seen from the technical solution provided by the present invention above, in the evolution system of 3GPP, when the core network and the UE perform IP header compression, the present invention will compress the IP header between the core network equipment (such as the access system gateway ASGW) and the EUTRAN for each user. During switching, only one tunnel corresponding to the user is established between the source EUTRAN and the destination EUTRAN, which makes the transmission of IP header compressed data packets more concise, and improves the reliability and real-time performance of data transmission.

By establishing user context on EUTRAN equipment and core Ethernet equipment, the problem of invisible QoS parameters of IP data packets due to IP header compression is solved.

Compress the QoS of the data packet through the IP header and the QoS parameters of the bearer network and the downlink in the tunnel context, the QoS parameters of the bearer network and the user wireless interface in the tunnel context, the QoS parameters of the bearer network and the QoS of the bearer network in the tunnel context The mutual mapping of parameters solves the problems of QoS setting and scheduling caused by the invisible QoS parameters after IP header compression.

In addition, through the one-to-one mapping of the user identity such as IMSI (International Mobile Subscriber Identity) and the tunnel node identifier TEID (local tunnel node identifier, remote tunnel node identifier) and the user's identifier on the wireless interface, it is solved that a user only uses An identification problem when tunneling.

Description of drawings

Fig. 1 is the functional block diagram that realizes IP header compressed data packet transmission in the traditional 3G system;

Fig. 2 is a functional block diagram of realizing IP header compressed data packet transmission in the 3GPP evolution system;

Fig. 3 is the realization flowchart of the inventive method;

Fig. 4 is a schematic diagram of the encapsulation process when the IP data packet of the user equipment is transmitted to the core network;

Fig. 5 is a schematic diagram of the encapsulation process when the IP data packet of the core network is transmitted to the user equipment;

Fig. 6 is a schematic diagram of the bidirectional transmission process of the IP header compressed data packet;

FIG. 7 is a schematic diagram of QoS mapping during bidirectional transmission of IP data packets.

Detailed ways

The core of the present invention is that when the IP header is compressed on the core network and user equipment of the 3GPP evolved wireless communication system, a user context is created for each user on the core network equipment and the evolved wireless access network equipment respectively, in which User context includes information such as user ID and tunnel context. When it is necessary to transmit the user's IP header compressed data packet between the evolved radio access network device and the core network device, a corresponding tunnel is established for the user; the evolved radio access network device transmits the user's uplink IP header according to its user context information The wireless interface QoS parameters of the compressed data packet are mapped to the bearer network QoS parameters or the bearer network QoS parameters of the user downlink IP header compressed data packet are mapped to the wireless interface QoS parameters. In this way, the IP header compressed data packet of the user is encapsulated with the QoS parameters of the bearer network, so that the bearer network can transmit the IP address in the tunnel corresponding to the user between the evolved wireless access network device and the core network device with a certain priority according to the QoS. The header compressed data packet; and the IP header compressed data packet of the user is transmitted between the evolved radio access network equipment and the user equipment through a channel corresponding to the wireless interface QoS parameter.

For an evolved radio access network device, the context that needs to be created for each user includes at least a radio interface user ID, a radio interface uplink and downlink QoS parameter set, a tunnel context, and a QoS mapping table.

For example, the user context created on the ERAN device includes the following:

■Wireless interface user identification USID

■ Wireless interface uplink and downlink QoS parameter set

■Tunnel context

{

● Local tunnel node ID TEID_A, remote tunnel node ID TEID_B;

● bearer network type;

● Bearer network address, transport layer protocol, port number, etc.;

● bearer network and downlink QoS;

●N_PDU(UL/DL);

●......

}

■QoS mapping table

{

● bearer network QoS_1, {wireless interface QoS parameter set 1};

● Bearer network QoS_2, {radio interface QoS parameter set 2};

● Bearer network QoS_3, {wireless interface QoS parameter set 3};

●......

}

For core network devices, the context that needs to be created for each user includes at least the user identity and tunnel context.

For example, the user context created on the core network device includes the following:

■User ID

{

●International Mobile Subscriber Identity IMSI

●E.164

●SIP URL (Session Initiation Protocol Uniform Resource Identifier)

●Temporary identity (similar to grouped temporary mobile subscriber identity P-TMSI)

●......

}

■Tunnel context

{

● Local tunnel node ID TEID_B, remote tunnel node ID TEID_A;

● bearer network type;

● Bearer network address, transport layer protocol, port number, etc.;

● bearer network and downlink QoS;

●N_PDU(UL/DL)

●......

}

Wherein, N_PDU(UL/DL) represents the uplink and downlink sequence number of the PDU. PDU is a data packet compressed by IP header, UL means uplink, and DL means downlink. N_PDU (UL/DL) is the sequence number of the uplink and downlink IP header compressed data packets.

Each user has a unique radio interface user identifier USID on the radio interface, and corresponds to the local tunnel node identifier used by it in the evolved radio access network device.

Similarly, each user has an International Mobile Subscriber Identity (IMSI) and multiple other non-access stratum identifiers, which correspond to the local tunnel node identifiers used in the core network equipment. Because an IMSI user can have multiple NAS user IDs at the same time, each NAS ID can only correspond to one IMSI, and thus can only correspond to one TEID ID, but a TEID ID corresponds to one or more A non-access stratum user ID.

In addition, since the IP header is compressed on the user equipment and the core network equipment, the IP header compression context is also saved on the core network equipment.

In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

With reference to Fig. 3, Fig. 3 has shown the implementation process of the method of the present invention, comprises the following steps:

Step 301: Create a user context for each user on the core network device and the E_UTRAN (Evolved Radio Access Network) device.

The content of the user context can refer to the previous description.

Step 302: When the user's IP header compressed data packet needs to be transmitted between the evolved radio access network device and the core network device, a corresponding tunnel is established for the user.

For example, when the IP header of the IP flow data between the UE and the access system gateway of the core network is compressed, the access system gateway and the access system must use tunnel technology. There are many ways to use the tunneling technology, for example, the GTP (GPRS Tunneling Protocol) protocol can be used.

The tunnel header structure of the tunnel protocol used can adopt the header structure of the existing tunnel protocol, or can be customized. For example, the definition of the tunnel header structure includes the following content:

■Version

■Message Type

■QoS (optional)

■Length

■TEID

■UL N_PDU

■DL N_PDU

■Next Extension Header TYpe

■Data

Among them, the data item before Data is the Tunnel header, and Data is the data encapsulated by the Tunnel.

Version is the version number;

Message Type is the message name of the Tunnel. When the Tunnel transmits data, it is not a control message. The Message Type is a dedicated reserved value, such as -1.

QoS The QoS used by this tunnel data, this parameter is optional.

Length is the length of the entire tunnel data packet. The specific length can be obtained by subtracting the tunnel header from the length of the tunnel data.

TEID is the tunnel node identifier TEID value of the receiver.

UL N_PDU: the sequence number of the uplink PDU (protocol data unit). Similar to the sequence number in the TCP (Transmission Control Protocol) header: for ASGW (access system gateway), it is the sequence number of the next received PDU, and ASGW notifies E_UTRAN (evolved radio access network) through the sequence number of UL N_PDU The location of the data sent to the ASGW next time or the location of the data received by the ASGW next time. The UL N_PDU of ASGW increases according to the length of received Tunnel data. E_UTRAN notifies ASGW of the position of the Tunnel data sent by E_UTRAN next time or the position of ASGW receiving data next time through the sequence number of ULN_PDU. The UL N_PDU of E_UTRAN increases according to the length of the transmitted Tunnel data.

DL N_PDU: The sequence number of the downlink PDU. It is also similar to the sequence number in the TCP header: for ASGW, it is the sequence number of the PDU to be sent next time, and ASGW notifies E_UTRAN of the next data location that ASGW will send or the location of E_UTRAN's next received data through the sequence number of DL N_PDU. The DL N_PDU of ASGW increases according to the length of the sent Tunnel data. E_UTRAN notifies ASGW of the position of the Tunnel data received next time or the position of ASGW sent data next time through the sequence number of DL N_PDU. The UL N_PDU of E_UTRAN increases according to the length of the transmitted Tunnel data.

Next Extension Header TYpe is defined to support the extended Tunnel header.

In the present invention, only one tunnel is established for a user between the radio access network equipment and the core network equipment and between the source radio access network equipment and the destination radio access network equipment during handover, instead of different services Create different tunnels, which can greatly reduce the number of contexts.

Each user's tunnel between the radio access network device and the core network device has one and only one tunnel context corresponding to it on the radio access network device and the core network device. During handover, the user's tunnel between the source radio access network device and the destination radio access network device also has one and only one tunnel context corresponding to the two devices. Each tunnel is uniquely identified by any one of the TEIDs of the nodes at both ends of the tunnel. The devices at both ends of the tunnel guarantee the uniqueness of the TEIDs they allocate.

The tunnel established for the user is carried on a bearer network based on IPv4 (Internet Protocol Version 4) protocol or IPv6 (Internet Protocol Version 6) protocol or based on MPLS (Multiprotocol Label Switching). Therefore, in the tunnel context, it is necessary to define the type of the bearer network of the tunnel, the address of each endpoint of the tunnel, the source port, the destination port in the IP network, and whether the transport layer protocol used is UDP or other protocols.

In this way, the uplink and downlink QoS on the bearer network in the tunnel context is respectively related to the TOS (Type of Service) parameter in the IPv4 header, the Traffic Class (traffic type) parameter in the IPv6 header, and the DSCP (Differential Service Code Dot Field) in the MPLS header. correspond.

Step 303: The evolved wireless access network device maps the wireless interface QoS parameters of the user's uplink IP header compressed data packet to the bearer network QoS parameters or maps the bearer network QoS parameters of the user's downlink IP header compressed data packet to Wireless interface QoS parameters.

Step 304: Encapsulate the IP header compressed data packet of the user with the QoS parameters of the bearer network, and transmit between the evolved radio access network device and the core network device through the tunnel corresponding to the user.

Step 305: Transmit the IP header compressed data packet of the user between the evolved radio access network device and the user equipment through a channel corresponding to the wireless interface QoS parameters.

Taking the ASGW and E_UTRAN in the 3GPP evolution system as an example, the encapsulation and transmission process of the IP header compressed data packet between the UE and the ASGW will be described in detail.

Fig. 4 shows the process that the IP packet of the user equipment is transmitted to the core network:

Among them, UP1 represents the uncompressed IP data packet of the UE, which contains the TOS parameter in the IP header; the UE compresses the IP header of UP1 according to the IP header compression context saved by it, and the compressed IP data packet is UP2, in UP2 due to The IP header is compressed so the QoS in the TOS parameter is not visible. UE sends the compressed UP2 to E_UTRAN.

After E_UTRAN receives the data packet, it will establish a corresponding tunnel for the user to transmit the IP header compressed data packet of the user; the outer layer of the received IP header compressed data packet is encapsulated on the Tunnel header, that is, UP3; then, the The tunnel is carried on the IP network for transmission. To this end, a layer of IP header needs to be encapsulated outside the Tunnel header, and the QoS parameters in the IP header of the UE uncompressed data packet UP1 are mapped to the IP header outside the Tunnel header. The last IP data is UP4.

Fig. 5 shows the process that the IP packet of the core network is transmitted to the user equipment:

Among them, DN1 represents the uncompressed IP data packet of ASGW, which contains TOS parameters in the IP header; ASGW compresses the IP header of UP1 according to the IP header compression context saved by ASGW, and the compressed IP data packet is DN2, in DN2 due to The IP header is compressed so the QoS in the TOS parameter is not visible and needs to be tunneled. The ASGW establishes a corresponding tunnel for the user to transmit the IP header compressed data packet of the user; encapsulates the outer layer of the IP header compressed data packet with the Tunnel header, that is, DN3; then, the tunnel is carried on the IP network for transmission. , it is also necessary to encapsulate a layer of IP header outside the Tunnel header, and map the QoS parameters in the IP header of the uncompressed data packet DN1 to the IP header outside the Tunnel header, and the encapsulated IP data is DN4.

For the same user, only one tunnel is established between the UE and the ASGW, which is determined by the local tunnel node ID and the remote tunnel node ID in the tunnel context. The two-way transmission process of the IP header compressed data packet is shown in Figure 6.

The mapping process of the QoS parameters in the above IP header is shown in Figure 7:

In E_UTRAN, the QoS parameters in the tunnel context and the QoS parameters in the radio interface are mapped to each other. E_UTRAN obtains the QoS parameters of the tunnel from the tunnel data received from the core network or from the source access system during handover, and then maps this QoS to the QoS parameters of the wireless interface, and then maps the IP The header compressed data packet is sent to the UE according to the QoS parameters of the radio interface obtained through mapping. Similarly, E_UTRAN obtains the IP header compressed data packet with a certain QoS parameter of the wireless interface, and then maps the QoS parameter of the wireless interface to the QoS parameter of the tunnel, and encapsulates the IP header compressed data packet with the mapped QoS parameter of the tunnel , sending the encapsulated IP header compressed data packet to the core network.

In the user context, the QoS parameters in the tunnel context and the QoS parameters of the bearer network (such as IP network) are prepared and mapped to each other.

When the ASGW sends IP data to the UE, it sets the QoS parameters of the IP data as the QoS parameters of the tunnel, compresses the IP header of the IP data packet, passes through the unique tunnel established in advance, and transmits the IP header compressed data packet through the bearer The network sends it to E_UTRAN, and the bearer network sends this data packet to E_UTRAN with a certain priority according to the QoS settings.

When E_UTRAN receives a data packet received with a certain wireless QoS parameter from the air, that is, after the IP header compresses the data packet, it maps to a QoS parameter of the tunnel according to its wireless QoS parameter setting, and then compresses the received IP header The data packet is encapsulated through the Tunnel header with the QoS parameters mapped to it, and the bearer network transmits the data packet to the ASGW with a certain priority according to the QoS of the tunnel.

Although above ASGW and E_UTRAN are taken as examples, the IP header compressed data packet transmission process of the present invention is described, but in the present invention, the core network device is not limited to ASGW, for example, it can also be MME/UPE (Mobility Management Entity/ user plane entity); and the evolved radio access network device may be a radio network controller and/or a base station.

Evolved radio access network equipment and core network equipment tear down the tunnel corresponding to the user according to the activity status and/or available resource status of the user equipment, and delete or prohibit the tunnel context corresponding to the user on the evolved radio access network equipment and core network equipment information.

When a user equipment switches between different evolved radio access networks, a corresponding handover tunnel needs to be established for the user between the source radio access network device and the destination radio access network device to transmit the source radio access network Data that the device has not yet sent to the user device. At the same time, part of the content of the user context of the original E_UTRAN, such as the uplink and downlink serial numbers of the tunnel, needs to be copied to the new E_UTRAN, and other content is directly created in the target E_UTRAN.

After the handover is complete, delete the handover tunnel corresponding to the user. A handover timer can be set, and when the handover tunnel is established, the handover timer is started, and when the time of the handover timer expires, the handover tunnel corresponding to the user can be deleted.

When the user equipment is turned off or the user equipment moves to a new wireless access system, the tunnel corresponding to the user is removed, and the tunnel context information corresponding to the user on the evolved radio access network equipment and the core network equipment is deleted or prohibited.

The present invention can support the encryption or integrity protection of the entire tunnel data packet or only the IP header compressed data packet encapsulated in the tunnel. Because the bearer network IP header or MPLS encapsulation header is not encrypted, the QoS of the tunnel context can be mapped with the QoS of the bearer network without affecting it. Moreover, since the sequence number of the uplink and downlink data packets is included in the tunnel context information, the transmission sequence of the IP header compressed data packets can be guaranteed, and the efficiency of the IP header compression can be improved.

While the invention has been described by way of example, those skilled in the art will appreciate that there are many variations and changes to the invention without departing from the spirit of the invention, and it is intended that the appended claims cover such variations and changes without departing from the spirit of the invention.

Claims (14)

1. the method for IP compressed data packets of transmission in the third generation evolution system, described third generation evolution system comprises core net, evolution wireless access network and subscriber equipment, and on subscriber equipment and equipment of the core network, the IP head is compressed, it is characterized in that described method comprises:

On equipment of the core network and evolution wireless access network equipment, be respectively each user and create user's context;

In the time that IP compressed data packets of user need be transmitted, set up the tunnel of a correspondence for this user between evolution wireless access network equipment and equipment of the core network;

The wave point service quality QoS parameter of a user uplink IP compressed data packets is mapped as the bearer network qos parameter or the bearer network qos parameter of user's downstream IP compressed data packets is mapped as the wave point qos parameter according to its user context information by the evolution wireless access network equipment;

Encapsulate this user's IP compressed data packets with described bearer network qos parameter, and between evolution wireless access network equipment and equipment of the core network by transmitting in the tunnel corresponding with this user;

Between evolution wireless access network equipment and subscriber equipment, transmit this user's IP compressed data packets with the channel corresponding with described wave point qos parameter.

2. method according to claim 1 is characterized in that,

The described user's context of creating for each user on equipment of the core network comprises at least: User Identity, tunnel context;

The described user's context of creating for each user on the evolution wireless access network equipment comprises at least: wave point user ID, wave point up-downgoing qos parameter set, tunnel context, QoS mapping table;

Described tunnel context comprises at least: local tunnel node identification, far-end tunnel node identification, bearer network type, bearer network up-downgoing QoS.

3. method according to claim 2 is characterized in that, each user has a unique described wave point user ID on wave point, and corresponding with the described local tunnel node identification TEID of its use in the evolution wireless access network equipment.

4. method according to claim 2 is characterized in that, each user has an international mobile subscriber identity IMSI and a plurality of other Non-Access Stratum signs, and corresponding with the described local tunnel node identification of its use in equipment of the core network.

5. method according to claim 2 is characterized in that, describedly the step that the wave point qos parameter of a user uplink IP compressed data packets is mapped as the bearer network qos parameter is comprised according to its user context information by the evolution wireless access network equipment:

The evolution wireless access network equipment is according to the channel of IP the compressed data packets that receives the subscriber equipment transmission and the wave point qos parameter that radio interface parameter obtains this packet;

According to the QoS mapping table in the user context information corresponding described wave point qos parameter is mapped as the bearer network qos parameter with this user.

6. method according to claim 2 is characterized in that, describedly the step that the bearer network qos parameter of user's downstream IP compressed data packets is mapped as the wave point qos parameter is comprised according to its user context information by the evolution wireless access network equipment:

The evolution wireless access network equipment obtains equipment of the core network by the bearer network qos parameter in the IP head of IP compressed data packets of tunnel transmission;

According to the QoS mapping table in the user context information corresponding described bearer network qos parameter is mapped as the wave point qos parameter with this user.

7. method according to claim 2 is characterized in that, described method further comprises:

To be carried on for the tunnel that the user sets up based on Internet Protocol the 4th version IPv4 agreement or Internet Protocol sixth version this IPv6 agreement or the bearer network based on multiprotocol label switching MPLS.

8. method according to claim 7 is characterized in that,

If the tunnel of setting up for the user is carried on the bearer network based on the IPv4 agreement, the bearer network up-downgoing QoS in the then described tunnel context is corresponding with the COS TOS parameter in the IPv4 head;

If the tunnel of setting up for the user is carried on the bearer network based on the IPv6 agreement, the bearer network up-downgoing QoS in the then described tunnel context is corresponding with the discharge pattern Traffic Class parameter in the IPv6 head;

If the tunnel of setting up for the user is carried on the bearer network based on MPLS, the bearer network up-downgoing QoS in the then described tunnel context is corresponding with differentiated services code-point territory DSCP in the MPLS head.

9. method according to claim 1 is characterized in that, described method further comprises:

Evolution wireless access network equipment and equipment of the core network are removed tunnel that should the user according to the active state of subscriber equipment and/or available resources state, and deletion or forbid on evolution wireless access network equipment and the equipment of the core network tunnel context information that should the user.

10. method according to claim 1 is characterized in that, described method further comprises:

When subscriber equipment shutdown or subscriber equipment move to new wireless access system, remove tunnel that should the user, and deletion or forbid on evolution wireless access network equipment and the equipment of the core network tunnel context information that should the user.

11. method according to claim 1 is characterized in that, described method further comprises:

When subscriber equipment switches between different evolution wireless access networks, between source wireless access network equipment and purpose wireless access network equipment,, also do not send to the data of subscriber equipment with the transmission sources wireless access network equipment for this user sets up one and the handover tunnel of a correspondence only.

12. method according to claim 11 is characterized in that, described method further comprises:

Set switching timer;

After described handover tunnel is set up, start this switching timer;

After the described switching timer time arrived, deletion was to handover tunnel that should the user.

13. method according to claim 1 is characterized in that, described equipment of the core network is specially: connecting system gateway or Mobility Management Entity/user plane entity.

14. method according to claim 1 is characterized in that, described evolution wireless access network equipment is specially: radio network controller and/or base station.

Images