CN107113655B

CN107113655B - Method for determining compression parameters of data packet and related equipment

Info

Publication number: CN107113655B
Application number: CN201580073201.7A
Authority: CN
Inventors: 黄正磊; 张万强; 邓强
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2015-08-25
Filing date: 2015-08-25
Publication date: 2020-06-26
Anticipated expiration: 2035-08-25
Also published as: CN107113655A; WO2017031700A1

Abstract

The invention discloses a method for determining compression parameters of a data packet and related equipment, which are used for improving the transmission efficiency of the data packet and the utilization rate of network bandwidth. The method comprises the following steps: a core network node acquires header compression capability information of a terminal; the core network node determines a header compression parameter of the terminal according to the header compression capability information of the terminal; and the core network node initializes or updates the header compression context information of the first data service of the terminal through a control signaling according to the header compression parameter.

Description

Method for determining compression parameters of data packet and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method for determining compression parameters of a data packet and a related device.

Background

(I) EPS network architecture

An Evolved Packet System (EPS) network architecture is shown in fig. 1. The Evolved universal roadbed radio access network (EUTRAN) is a network consisting of a plurality of base stations (eNodeBs), the eNodeBs are connected with a serving gateway (S-GW) through a user plane interface S1-U, and are connected with a Mobility Management Entity (MME) through a control plane interface S1-MME. The MME is responsible for all control plane functions of user session management, including Non Access Stratum (NAS) signaling and security, management of tracking area, selection of Packet Data Network Gateway (PDN, Packet Data Network) and S-GW, and the like. The S-GW is mainly responsible for data transmission, forwarding, route switching, etc. of a terminal (UE), and serves as a local mobility anchor point when the terminal is switched between enodebs. The P-GW is responsible for Internet Protocol (IP) address allocation of the UE, data packet filtering, rate control, generation of charging information, and the like of the terminal.

In the EPS-based network architecture, if there is no data transmission for a long time, the UE enters an IDLE (IDLE) state. When the UE is in an idle state, the EPS network triggers a service request procedure when receiving a data message or signaling for user downlink, in which the MME initiates paging in a tracking area where the UE is located, and the UE switches to a Connected state (Connected) to receive the data or signaling in response to the paging of the MME, where the specific process is shown in fig. 2.

Honeycomb Internet of Things (Cellular Internet of Things, CIoT for short)

Currently, 3GPP is developing a research on cellular network-based internet of things, i.e., CIoT, and supports ultra-low complexity, power-limited, and low data rate internet of things devices through architecture enhancement, as shown in fig. 3, a schematic diagram of a CIoT architecture in a non-roaming scenario, and as shown in fig. 4, a schematic diagram of a CIoT architecture in a roaming scenario. The CIoT service Gateway Node (C-SGN) is configured to support a function related to a CIoT application scenario.

(III) Small data packet Transmission

Some Machine-to-Machine (M2M) applications, such as water meters, electricity meters, sensors, etc., primarily receive or transmit data in small packet amounts. In the existing LTE mechanism, when there is data to be transmitted in an IDLE state in a UE, a Service Request (Service Request) process needs to be initiated to establish a bearer between an air interface and an S1 interface, and Radio Resource Control (RRC) security context information needs to be downloaded to an eNB, so that the efficiency of transmitting small data packets is very low, and signaling overhead caused by transmitting a small data packet once far exceeds the data to be transmitted. The current optimization scheme is to encapsulate a small data packet in NAS signaling for transmission, where a terminal-initiated (MO) small data packet transmission flow is shown in fig. 5 and a terminal-terminated (MT) small data packet transmission flow is shown in fig. 6, where the small data packet is an IP data packet.

For the uplink small data packet, the MTC terminal device encapsulates the encrypted small data packet in an NAS message, transmits a Connection Setup Complete (Connection Setup Complete) message to the eNB, and forwards the message to the MME through an S1 access point Initial ue (ap Initial ue) message. The MME decrypts the NAS message and obtains an IP data Packet and an Evolved Packet System Bearer ID (EPS). When the Downlink small Data packet reaches the S-GW, the S-GW encapsulates the Downlink small Data packet in a Downlink Data Notification (Downlink Data Notification) message and sends the Downlink small Data packet to the MME, the MME carries the Downlink small Data packet by using an encrypted cell of a NAS Protocol Data Unit (PDU) in a Downlink NAS Transport (Downlink NAS Transport) message through S1, and the NAS PDU is sent to the UE through the eNB.

How to further improve the transmission efficiency of small data packets and the network bandwidth utilization rate is a problem to be solved.

Disclosure of Invention

The embodiment of the invention provides a method for determining compression parameters of a data packet and related equipment, which are used for improving the transmission efficiency of the data packet and the utilization rate of network bandwidth.

The embodiment of the invention provides the following specific technical scheme:

in a first aspect, a method for determining compression parameters of a data packet is provided, including:

a core network node acquires header compression capability information of a terminal;

the core network node determines a header compression parameter of the terminal according to the header compression capability information of the terminal;

and the core network node initializes or updates the header compression context information of the first data service of the terminal according to the header compression parameter.

With reference to the first aspect, in a first possible implementation manner, the header compression capability information includes a maximum value of the number of header compression contexts supported by the terminal and a header compression protocol supported by the terminal;

the header compression parameters include a maximum value of the number of header compression contexts that are allowed to be used and a header compression protocol that is allowed to be used.

With reference to the first aspect, in a second possible implementation manner, the header compression capability information includes a header compression protocol supported by the terminal;

the header compression parameters include a header compression protocol that is allowed to be used.

With reference to any one of the first aspect to the second possible implementation, in a third possible implementation, initializing or updating, by the core network node, header compression context information of a first data service of the terminal according to the header compression parameter includes:

the core network node acquires transmission parameters of the first data service of the terminal, wherein the transmission parameters comprise transmission addresses and/or port information;

determining header compression context information according to the header compression parameters and the transmission parameters of the first data service;

initializing or updating the header compression context information of the first data service of the terminal, which is stored by the core network node, according to the determined header compression context information;

and sending the determined header compression context information to the terminal so that the terminal initializes or updates the header compression context information of the first data service stored by the terminal.

With reference to any one of the first aspect to the second possible implementation, in a fourth possible implementation, initializing or updating, by the core network node, header compression context information of a first data service of the terminal according to the header compression parameter includes:

the core network node sends the header compression parameters to the terminal;

receiving header compression context information sent by the terminal, wherein the received header compression context information is determined by the terminal according to the header compression parameters and transmission parameters of the first data service, and the transmission parameters comprise transmission addresses and/or port information;

initializing or updating the header compression context information of the first data service of the terminal stored by the core network node according to the received header compression context information.

With reference to any one of the first aspect to the fourth possible implementation manner, in a fifth possible implementation manner, the header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

With reference to any one of the first aspect to the fifth possible implementation manner, in a sixth possible implementation manner, the method further includes:

the core network node receives a data packet of the first data service sent by the terminal, and decompresses the packet header of the data packet according to the header compression context information of the first data service of the terminal;

alternatively, the first and second electrodes may be,

and the core network node compresses the packet header of the data packet of the first data service to be sent to the terminal according to the header compression context information of the first data service of the terminal to obtain a compressed data packet, and sends the compressed data packet to the terminal.

In a second aspect, a method for determining compression parameters of a data packet is provided, including:

a terminal receives header compression parameters of the terminal or header compression context information of a first data service of the terminal, which are sent by a core network node;

and the terminal initializes or updates the header compression context information of the first data service of the terminal according to the header compression parameter or the received header compression context information.

With reference to the second aspect, in a first possible implementation manner, the header compression parameters include a maximum value of the number of header compression contexts that are allowed to be used and a header compression protocol that is allowed to be used; alternatively, the header compression parameters include a header compression protocol that is allowed to be used.

With reference to the second aspect or the first possible implementation, in a second possible implementation, the initializing or updating, by the terminal, header compression context information of the first data service of the terminal according to the header compression parameter includes:

the terminal acquires transmission parameters of the first data service, and determines header compression context information of the first data service according to the transmission parameters and the header compression parameters, wherein the transmission parameters comprise transmission addresses and/or port information;

initializing or updating the header compression context information of the first data service of the terminal according to the determined header compression context information.

With reference to any one of the second aspect to the second possible implementation, in a third possible implementation, after the initializing or updating, by the terminal, header compression context information of the first data service of the terminal according to the header compression parameter, the method further includes:

sending the header compression context information of the first data service of the terminal to the core network node, so that the core network node initializes or updates the header compression context information of the first data service of the terminal stored by the core network node.

With reference to any one of the second aspect to the third possible implementation manner, in a fourth possible implementation manner, the header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

With reference to any one of the second aspect to the fourth possible implementation manner, in a fifth possible implementation manner, the method further includes:

the terminal compresses the packet header of the data packet to be transmitted of the first data service according to the header compression context information of the first data service to obtain a compressed data packet, and sends the compressed data packet to the core network node;

alternatively, the first and second electrodes may be,

and the terminal receives the data packet of the first data service sent by the core network node and decompresses the packet head of the received data packet according to the header compression context information.

In a third aspect, a core network node is provided, including:

the acquisition module is used for acquiring header compression capability information of the terminal;

a determining module, configured to determine a header compression parameter of the terminal according to the header compression capability information of the terminal acquired by the acquiring module;

and the processing module is used for initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameters determined by the determining module.

With reference to the third aspect, in a first possible implementation manner, the header compression capability information includes a maximum value of the number of header compression contexts supported by the terminal and a header compression protocol supported by the terminal;

With reference to the third aspect, in a second possible implementation manner, the header compression capability information includes a header compression protocol supported by the terminal;

With reference to any one of the third aspect to the second possible implementation manner, in a third possible implementation manner, the processing module is specifically configured to:

acquiring transmission parameters of the first data service of the terminal, wherein the transmission parameters comprise transmission addresses and/or port information;

With reference to any one of the third aspect to the second possible implementation manner, in a fourth possible implementation manner, the processing module is specifically configured to:

sending the header compression parameters to the terminal;

With reference to any one of the third aspect to the fourth possible implementation manner, in a fifth possible implementation manner, the header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

With reference to any one of the third aspect to the fifth possible implementation manner, in a sixth possible implementation manner, the apparatus further includes a data transmission module, configured to:

receiving a data packet of the first data service sent by the terminal, and decompressing the packet header of the data packet according to the header compression context information of the first data service of the terminal initialized or updated by the processing module;

alternatively, the first and second electrodes may be,

and compressing the packet header of the data packet of the first data service to be sent to the terminal according to the header compression context information of the first data service of the terminal initialized or updated by the processing module to obtain a compressed data packet, and sending the compressed data packet to the terminal.

In a fourth aspect, a terminal is provided, including:

a receiving module, configured to receive a header compression parameter of the terminal or header compression context information of a first data service of the terminal sent by a core network node;

a processing module, configured to initialize or update the header compression context information of the first data service of the terminal according to the header compression parameter received by the receiving module or the received header compression context information.

With reference to the fourth aspect, in a first possible implementation manner, the header compression parameters include a maximum value of the number of header compression contexts that are allowed to be used and a header compression protocol that is allowed to be used; alternatively, the header compression parameters include a header compression protocol that is allowed to be used.

With reference to the fourth aspect or the first possible implementation manner, in a second possible implementation manner, the processing module is specifically configured to:

acquiring transmission parameters of the first data service, and determining header compression context information of the first data service according to the transmission parameters and the header compression parameters, wherein the transmission parameters comprise transmission addresses and/or port information;

With reference to the fourth aspect to the second possible implementation, in a third possible implementation, the method further includes a sending module, configured to:

sending the header compression context information of the first data service of the terminal initialized or updated by the processing module to the core network node, so that the core network node initializes or updates the header compression context information of the first data service of the terminal stored by the core network node.

With reference to the fourth aspect to the third possible implementation manner, in a fourth possible implementation manner, the header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

With reference to the fourth aspect to the fourth possible implementation manner, in a fifth possible implementation manner, the method further includes a data transmission module, configured to:

compressing the packet header of the data packet to be transmitted of the first data service according to the header compression context information of the first data service initialized or updated by the processing module to obtain a compressed data packet, and sending the compressed data packet to the core network node;

alternatively, the first and second electrodes may be,

and receiving the data packet of the first data service sent by the core network node, and decompressing the packet header of the received data packet according to the header compression context information.

Based on the above technical solution, in the embodiment of the present invention, the core network node determines the header compression parameter of the terminal according to the header compression capability information of the terminal, and initializes or updates the header compression context information of the first data service of the terminal according to the determined header compression parameter, so that the packet header of the data packet of the first data service can be compressed and transmitted between the core network node and the terminal according to the header compression context information of the first data service of the terminal, thereby improving the transmission efficiency of the data packet, and further improving the network bandwidth utilization rate.

Drawings

Fig. 1 is a schematic diagram of an EPS network architecture;

fig. 2 is a schematic flow chart of an EPS network triggering service request;

FIG. 3 is a schematic diagram of a CIoT network architecture in a non-roaming scenario;

FIG. 4 is a schematic diagram of a CIoT network architecture in a roaming scenario;

fig. 5 is a schematic diagram of a transmission flow of a small data packet initiated by a terminal;

fig. 6 is a schematic diagram of a terminal-terminated small data packet transmission flow;

FIG. 7 is a diagram of an EPS system control plane protocol stack;

fig. 8 is a flowchart illustrating a method for a core network node to determine compression parameters of a data packet according to an embodiment of the present invention;

fig. 9 is a flowchart illustrating a method for a terminal to determine compression parameters of a data packet according to an embodiment of the present invention;

fig. 10 is a diagram illustrating header compression parameter negotiation and data transmission processes in an EPS system according to an embodiment of the present invention;

FIG. 11 is a diagram illustrating header compression parameter negotiation and data transmission processes in a CIoT system according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a core network node in the embodiment of the present invention;

fig. 13 is a schematic structural diagram of another core network node according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of a terminal in an embodiment of the present invention;

fig. 15 is a schematic structural diagram of another terminal according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In Packet data in a Packet Switch (PS) domain, a network Protocol header has a large weight relative to a payload, such as an IP Protocol header, a Transmission Control Protocol (TCP) Protocol, a User Datagram Protocol (UDP), a Real-time Transport Protocol (RTP) Protocol, or an IP Encapsulated Security Payload (ESP) Protocol, and occupies a considerable bandwidth. Meanwhile, as the network protocol header is not designed for wireless network data transmission, in the data transmission of the wireless network, many fields in the network protocol header are kept unchanged or changed little, and the fields kept unchanged or changed little are redundant, the purpose of header compression is as follows: in the transmission process from the compression end to the decompression end, the redundant domain of the network protocol header is reduced, and the transmission efficiency and the bandwidth utilization efficiency of the PS domain are improved.

The Packet Data Convergence Protocol (PDCP) is an important component of layer 2 Protocol in the radio interface of the LTE system. Header compression and decompression of data packets is done between two peer PDCP entities, namely UE side PDCP and eNB side PDCP.

Currently, a method for implementing data Header Compression by PDCP of Long Term Evolution (LTE) is based on a Robust Header Compression (RoHC) framework defined by IETF RFC 4995. The mechanism by which RoHC implements header compression is: when the connection starts, the compression end firstly sends a full header packet (full header) packet data to the decompression end, CONTEXT information (CONTEXT) of the packet data stream can be established at the compression end and the decompression end through the full header packet, the compression end sends the compressed packet data to the decompression end, and the decompression end decompresses through a decompression algorithm by using the established CONTEXT information and the received compressed packet data to obtain the packet data (packet) before compression.

The 3GPP TS 36.323PDCP protocol specification gives header compression protocols supported by the current LTE system, as shown in table 1.

TABLE 1

Profile identification	Use of	Reference protocol
			0x0000	Without compression	RFC 4995
0x0001	RTP/UDP/IP	RFC 3095,RFC 4815
			0x0002	UDP/IP	RFC 3095,RFC 4815
0x0003	ESP/IP	RFC 3095,RFC 4815
			0x0004	IP	RFC 3843,RFC 4815
0x0006	TCP/IP	RFC 4996
			0x0101	RTP/UDP/IP	RFC 5225
0x0102	UDP/IP	RFC 5225
			0x0103	ESP/IP	RFC 5225
0x0104	IP	RFC 5225

RoHC-related protocol parameters include:

MAX _ CID: the parameter specifies a maximum value of Context Identification (CID) that the UE and the network entity can support. One RoHC context corresponds to one CID.

PROFILES this parameter specifies the header compression Protocols (PROFILES) that the UE can support. A header compression protocol (Profile) is associated with a CID indicating the Profile that the CID corresponds to.

The header compression mechanism can improve the transmission efficiency of the data packet and the utilization efficiency of the bandwidth. Small data packets of Machine Type Communications (MTC) devices are transmitted encapsulated in NAS PDUs. In EPS, the function of header compression is performed between layer 2 protocol PDCP entities between the UE and the eNB. As shown in fig. 7, the eNB can only process PDUs below the NAS layer, and cannot compress and decompress the protocol header of the small packet encapsulated in the NAS PDU.

Meanwhile, in the existing header compression mechanism of the LTE system, when RRC connection is released, the UE and eNB do not save RoHC context information. Therefore, when the UE initiates the transceiving of the data packet from the idle state, the first data packet transmitted or received by the UE cannot be header-compressed because the RoHC context is not established in advance between the UE and the eNB.

Therefore, the prior art does not support header compression for small packet transmission based on NAS messages, and cannot improve the transmission efficiency and bandwidth utilization efficiency of small packets by using a header compression mechanism.

The following embodiments provide a compression parameter determination process for a packet, which is applicable to an EPS system and a CIoT system, and it should be noted that the possibility of applying the compression parameter determination process for a packet provided in the following embodiments to other systems is not excluded, and the scope of the present invention is not limited thereto.

Based on the above analysis, in the first embodiment of the present invention, as shown in fig. 8, a detailed method flow for a core network node to determine a compression parameter of a data packet is as follows:

step 801: the core network node acquires header compression capability information of the terminal.

In an implementation, if the terminal supports multiple header compression protocols, the header compression capability information includes a maximum value of the number of header compression contexts supported by the terminal and the header compression protocol supported by the terminal, and if the terminal supports only one header compression protocol, the header compression capability information includes the header compression protocol supported by the terminal.

In specific implementation, the modes for the core network node to obtain the header compression capability information of the terminal include, but are not limited to, the following:

firstly, the core network node acquires header compression capability information of the terminal, which is provided by the terminal;

secondly, the core network node acquires header compression capability information of the terminal from a prokaryotic core network node which provides service for the terminal previously;

thirdly, the core network node obtains header compression capability information of the terminal from the subscription data of the terminal, and the subscription data of the terminal may be obtained from a Home Subscriber Server (HSS).

Step 802: and the core network node determines the header compression parameters of the terminal according to the header compression capability information of the terminal.

In implementation, the header compression parameter of the terminal determined by the core network node is adapted to the header compression capability of the terminal, and specifically, if the header compression capability information of the terminal includes the maximum value of the number of header compression contexts supported by the terminal and the header compression protocol supported by the terminal, the header compression parameter includes the maximum value of the number of header compression contexts allowed to be used by the terminal and the header compression protocol allowed to be used by the terminal;

if the header compression capability information of the terminal includes a header compression protocol supported by the terminal, the header compression parameter includes a header compression protocol allowed to be used by the terminal.

In implementation, according to a specific application scenario, after determining a header compression parameter of the terminal according to the header compression capability information of the terminal, the core network node sends the determined header compression parameter to the terminal.

In one specific implementation, the core network node determines a header compression parameter of the terminal according to header compression capability information of the terminal, header compression capability information of the core network node, and subscription information of the terminal.

The header compression capability information of the core network node includes a maximum value of the number of header compression contexts supported by the core network node and a supported header compression protocol.

For example, the core network node first determines that the terminal supports header compression according to the subscription information of the terminal, and then determines a header compression parameter according to the header compression capability information of the terminal and the header compression capability information of the core network node.

In another specific implementation, the core network node determines the header compression parameter of the terminal according to the header compression capability information of the terminal and the header compression capability information of the core network node.

For example, if the header compression capability information of the core network node is: the maximum value of the number of supported header compression contexts is 3, and the types of supported header compression protocols are 3; if the header compression capability information of the terminal is: the maximum value of the number of supported header compression contexts is 2, and the types of supported header compression protocols are 2; and, if the core network node also supports the header compression protocol type supported by the terminal, determining that the header compression parameters are: the maximum number of header compression contexts allowed to be used is 2, and the kinds of header compression protocols allowed to be used are 2.

Step 803: and the core network node initializes or updates the header compression context information of the first data service of the terminal according to the header compression parameters.

In a first specific implementation, the core network node obtains a transmission parameter of the first data service of the terminal, where the transmission parameter includes a transmission address and/or port information; determining header compression context information according to the header compression parameters and the transmission parameters of the first data service; initializing or updating the header compression context information of the first data service of the terminal, which is stored by the core network node, according to the determined header compression context information; and sending the determined header compression context information to the terminal so that the terminal initializes or updates the header compression context information of the first data service stored by the terminal.

The modes for the core network node to acquire the transmission parameters of the first data service of the terminal include, but are not limited to, the following modes, and the modes may be used alone or in combination:

firstly, the core network node acquires the transmission parameter of the first data service from the subscription data of the terminal;

secondly, the core network node acquires the transmission parameter of the first data service of the terminal from an application server;

thirdly, the core network node acquires the transmission parameter of the first data service of the terminal from the received data packet of the first data service sent by the terminal;

fourthly, the core network node acquires the transmission parameters of the first data service of the terminal according to static configuration.

Specifically, the core network node sends the determined header compression context information to the terminal through a control signaling or a user plane data packet.

In a second specific implementation, the core network node sends the header compression parameter to the terminal; receiving header compression context information sent by the terminal, wherein the received header compression context information is determined by the terminal according to the header compression parameters and transmission parameters of the first data service, and the transmission parameters comprise transmission addresses and/or port information; initializing or updating the header compression context information of the first data service of the terminal stored by the core network node according to the received header compression context information.

Specifically, the core network node receives header compression context information sent by the terminal through a control signaling or a user plane data packet.

In the first and second implementations, the transmission address in the transmission parameter is specifically a source address and/or a destination address, and the port information in the transmission parameter is specifically a source port and/or a destination port.

In the first and second embodiments, the transmission parameters may include other parameters related to transmission, such as transmission protocol, protocol version number, etc., besides the transmission address and/or port information.

The header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

Specifically, in the case that the terminal supports multiple types of header compression context information, each header compression context information further includes a context identifier for distinguishing different header compression context information.

In an implementation, if the header compression parameters include only one header compression protocol, only the transmission parameters of the first data service may be included in header compression context information transferred between the core network node and the terminal.

In implementation, the core network node may transmit the data packet of the first data service after initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameter, specifically, there are the following two transmission processes:

firstly, the core network node receives a data packet of the first data service sent by the terminal, and decompresses the packet header of the data packet according to the header compression context information of the first data service of the terminal;

secondly, the core network node compresses the packet header of the data packet of the first data service to be sent to the terminal according to the header compression context information of the first data service of the terminal to obtain a compressed data packet, and sends the compressed data packet to the terminal.

In a specific implementation, in a case that the terminal only supports one type of header compression context information, the transmission process specifically includes the following steps:

in the uplink data transmission process, the core network node receives a data packet of the first data service sent by the terminal, and decompresses the packet header of the data packet according to the header compression context information of the first data service of the terminal;

in the downlink data transmission process, the core network node compresses the packet header of the data packet of the first data service of the terminal to be sent according to the header compression context information of the first data service of the terminal to obtain a compressed data packet, and sends the compressed data packet to the terminal.

In a specific implementation, in the case that the terminal supports multiple types of header compression context information, the transmission process specifically is as follows:

in the uplink data transmission process, the core network node receives the data packet of the first data service and the context identifier of the first data service, which are sent by the terminal, determines header compression context information corresponding to the context identifier of the first data service, and decompresses the packet header of the data packet according to the determined header compression context information;

in the downlink data transmission process, the core network node determines header compression context information corresponding to the context identifier of the first data service, compresses a packet header of a data packet of the first data service of the terminal to be sent according to the determined header compression context information to obtain a compressed data packet, and sends the context identifier of the first data service and the compressed data packet to the terminal.

In the embodiment of the present invention, the data packet of the first data service may be carried and transmitted in transmission modes such as NAS signaling and user plane bearer.

If the core network node is applied to the EPS system, the core network node in this embodiment may be an MME or a P-GW.

If the method is applied to a CIoT scenario, in a non-roaming scenario, the core network node in this embodiment may be a C-SGN, and in a roaming scenario, the core network node in this embodiment may be either a C-SGN or a P-GW.

Based on the same inventive concept, in the second embodiment of the present invention, as shown in fig. 9, a detailed method flow for a terminal to determine compression parameters of a data packet is as follows:

step 901: and the terminal receives the header compression parameters of the terminal or the header compression context information of the first data service of the terminal, which are sent by a core network node.

Wherein the header compression parameters include a maximum value of the number of header compression contexts permitted to be used and a header compression protocol permitted to be used; alternatively, the header compression parameters include a header compression protocol that is allowed to be used.

Step 902: and the terminal initializes or updates the header compression context information of the first data service of the terminal according to the header compression parameter or the received header compression context information.

In a specific implementation, the terminal initializes or updates the header compression context information of the first data service of the terminal according to the header compression parameter, and the specific process is as follows:

the terminal acquires transmission parameters of the first data service, and determines header compression context information of the first data service according to the transmission parameters and the header compression parameters, wherein the transmission parameters comprise transmission addresses and/or port information; initializing or updating the header compression context information of the first data service of the terminal according to the determined header compression context information.

Specifically, the manner in which the terminal acquires the transmission parameter of the first data service includes, but is not limited to, the following two manners:

firstly, the terminal obtains the transmission parameter of the first service data from the packet header information of the first service data generated by the service application;

secondly, the terminal obtains the transmission parameter of the first service data through the application server.

After initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameter, the terminal sends the header compression context information of the first data service of the terminal to the core network node, so that the core network node initializes or updates the header compression context information of the first data service of the terminal, which is stored by the core network node.

Specifically, the terminal sends the header compression context information of the first data service of the terminal to the core network node through a control signaling or a user plane data packet.

Specifically, a terminal receives header compression context information of a first data service of the terminal, which is sent by a core network node through a control signaling or a user plane data packet, and initializes or updates the header compression context information of the first data service of the terminal by using the received header compression context information of the first data service.

The transmission address is specifically a source address and/or a destination address, and the port information is specifically a source port and/or a destination port.

In practice, the transmission parameters may include other parameters related to transmission, such as protocol version number, besides the transmission address and/or port information.

In an implementation, in a case that the terminal supports multiple types of header compression context information, each header compression context information further includes a context identifier for distinguishing different header compression context information. In an implementation, if the header compression parameters include only one header compression protocol, only the transmission parameters of the first data service may be included in the header compression context information transferred between the terminal and the core network node.

In implementation, after initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameter or the received header compression context information, the terminal may transmit a data packet of the first data service, and in a case that the terminal only supports one type of header compression context information, the following two transmission processes are specifically provided:

firstly, the terminal compresses a packet header of a data packet to be transmitted of the first data service according to header compression context information of the first data service to obtain a compressed data packet, and sends the compressed data packet to the core network node;

secondly, the terminal receives the data packet of the first data service sent by the core network node, and decompresses the packet header of the received data packet according to the header compression context information.

in the uplink data transmission process, the terminal compresses the packet header of the data packet of the first data service to be sent according to the header compression context information of the first data service to obtain a compressed data packet, and sends the compressed data packet to the core network node;

in the downlink data transmission process, the terminal receives the data packet of the first data service sent by the core network node, and decompresses the packet header of the data packet according to the header compression context information of the first data service.

in the uplink data transmission process, the terminal determines header compression context information corresponding to the context identifier of the first data service, compresses a packet header of a data packet of the first data service to be sent according to the determined header compression context information to obtain a compressed data packet, and sends the context identifier of the first data service and the compressed data packet to the core network node;

in the downlink data transmission process, a terminal receives a data packet of the first data service and the context identifier of the first data service, which are sent by the core network node, determines header compression context information corresponding to the context identifier of the first data service, and decompresses the packet header of the data packet according to the determined header compression context information.

In a specific embodiment, taking uplink data transmission as an example, a specific process of sending a small data packet by a terminal is as follows:

acquiring packet header information of a first small data packet to be sent under the condition that a terminal needs to send the first small data packet, wherein the packet header information comprises transmission parameters such as a source address, a destination address, a port number and the like;

the terminal judges whether header compression context information corresponding to the header information exists locally;

if the NASDU does not exist, the terminal allocates a Context Identifier (CID) for the first small data packet, determines a header compression protocol corresponding to the first small data packet, wherein the header compression protocol belongs to a header compression protocol contained in header compression parameters, and encapsulates the uncompressed first small data packet, the context identifier of the first small data packet and the identifier of the header compression protocol in an NASDU (self-organizing data protocol data unit) and sends the NASDU to the network side;

if the packet header exists, the terminal compresses the packet header of the first small data packet by using header compression context information corresponding to the packet header information to obtain a compressed first small data packet, encapsulates the compressed first small data packet and the context identifier of the first small data packet in an NAS PDU, and sends the NAS PDU to a network side.

Accordingly, the specific process of receiving the small data packet by the network side is as follows:

the core network node acquires first small data from the NAS PDU, if the header of the acquired first small data packet is not compressed, the header information of the first small data packet, a corresponding CID and a header compression protocol are extracted, header compression context information of the first small data packet is generated, and the corresponding relation between the CID and the header compression context information is stored for subsequent decompression of the first small data packet;

if the obtained packet header of the first small data packet is compressed, determining header compression context information corresponding to the CID of the first small data packet according to the corresponding relation between the CID of the data packet and the header compression context information stored by the core network node, and decompressing the packet header of the first small data packet according to the header compression context information.

The downlink data transmission process is basically the same as the uplink data transmission process, and the difference is that the core network node compresses the first small data packet, and the terminal decompresses the first small data packet.

The following describes in detail a compression parameter determination process and a data transmission process of a data packet according to embodiments of the present invention with several specific embodiments.

In the first specific embodiment, in the EPS system, the process of negotiating the header compression parameters of the UE and performing data transmission between the UE and the core network is as shown in fig. 10, and specifically as follows:

step 1001: the UE initiates an attach or Tracking Area Update (TAU) procedure to the eNB, negotiating header compression parameters with the core network node.

If the attach process is the initial attach process, carrying header compression capability information of the UE in the attach request; or, if the header compression capability information of the UE changes, the TAU request message carries the latest header compression capability information of the UE.

Step 1002: and the eNB obtains the original MME according to the parameter GUMMEI carried in the attachment request or TAU request message of the UE. And if the original MME can not provide service for the UE or the original GUMMEI is invalid, reselecting an MME capable of supporting header compression for the UE, and forwarding an attach request or TAU request message of the UE to the target MME.

Step 1003: optionally, if the eNB selects a new MME, the target MME sends a context request message requesting to acquire context information of the UE to the source MME.

Step 1004: optionally, the source MME returns a context response message to the target MME, where the context response message carries context information of the UE, and the source MME is an MME providing a service for the UE before switching to the target MME.

Step 1005: and the target MME makes a decision according to the header compression capability information of the UE, the subscription information of the UE, the context information of the UE acquired from the source MME, a local policy and the like, and determines the header compression parameters of the UE.

Step 1006: optionally, if the target MME decides to perform header compression processing of an uplink and downlink data packet between the P-GW and the UE, the target MME sends a header compression parameter of the UE to the P-GW through a create session request message, or the target MME sends header compression capability information of the UE to the P-GW through a create session request message;

step 1007: and the P-GW accepts or refuses to perform header compression processing according to the local strategy, and determines the header compression parameters of the UE under the condition of accepting the header compression processing. And the P-GW feeds back the header compression parameters of the UE to the target MME through creating a session response message. The PGW may determine whether to accept the header compression parameter of the UE sent by the target MME, or the PGW determines the header compression parameter of the UE according to header compression capability information of the UE, a local policy, and the like.

Step 1008: and the target MME sends an attach or TAU acceptance message to the UE, wherein the attach or TAU acceptance message carries the header compression parameters of the UE.

Step 1009: the UE sends a header compression context initialization or update message to a target MME, wherein the message comprises a Context Identifier (CID) of a first data service and an identifier of a header compression protocol adopted by the first data service, the header compression protocol belongs to a header compression protocol in header compression parameters of the UE, and the header compression protocol also comprises header information of a data packet of the first data service.

Step 1010: alternatively, if the header compression process is performed by the P-GW, the target MME forwards the header compression context initialization or update message to the P-GW.

Step 1011 to step 1012: the target MME or P-GW saves the header compression context information and optionally replies an acknowledgement message to the UE.

The header compression context initialization or update process in steps 1009 to 1012 may be implemented by control signaling, for example, the UE carries the header compression context information of the first data service in the attach or TAU complete message, or the header compression context initialization or update process may be implemented by a user plane data packet, that is, the UE carries the header compression context information of the first data service in the sent user plane data packet.

If the UE or the target MME does not support header compression, the UE and the source MME or the P-GW delete the stored header compression context information of the first data service of the UE.

In the first embodiment, the UE provides header compression capability information to the core network, a node of the core network makes a decision according to the header compression capability information of the UE, subscription information of the UE, and a local policy, and determines a header compression parameter of the UE, the UE and the node of the core network initialize or update header compression context information of the first data service based on the negotiated header compression parameter, and based on the initialized or updated header compression context information of the first data service, the UE and the MME or the P-GW may compress a packet header of a packet of the first data service and transmit the compressed packet, thereby improving transmission efficiency of the packet.

In a second specific embodiment, in a CIoT system, a process of negotiating header compression parameters of a UE and performing data transmission between the UE and a core network is shown in fig. 11, where a process related to a P-GW is only applicable in a roaming scenario, and the specific details are as follows:

step 1101: the UE initiates an attach or Tracking Area Update (TAU) procedure to the RAN node, negotiating header compression parameters of the UE with a core network node.

Step 1102: and the RAN node selects the C-SGN according to the attachment request or the TAU request message of the UE, reselects the C-SGN capable of supporting header compression for the UE if the original C-SGN cannot provide service for the UE, and forwards the attachment request or the TAU request message of the UE to the target C-SGN.

Step 1103: optionally, if the RAN node selects a new C-SGN for the UE, the target C-SGN requests the source C-SGN for a context request message for acquiring context information of the UE.

Step 1104: optionally, the source C-SGN provides context information of the UE to the target C-SGN, where the source C-SGN refers to a C-SGN that serves the UE before handover to the target C-SGN.

Step 1105: and the target C-SGN makes a decision according to the header compression capability information of the UE, the subscription information of the UE, the context information of the UE acquired from the source C-SGN, a local policy and the like, and determines the header compression parameters of the UE.

Step 1106: optionally, if the target C-SGN decides to perform header compression processing by the P-GW, the target C-SGN sends the header compression parameters of the UE to the P-GW through a create session request message, or the target C-SGN sends the header compression capability information of the UE to the P-GW through a create session request message.

Step 1107: and the P-GW accepts or refuses to perform header compression processing according to the local strategy, and determines the header compression parameters of the UE under the condition of accepting the header compression processing. And the P-GW feeds back the header compression parameters of the UE to the target C-SGN through creating a session response message. Specifically, the P-GW determines whether to accept the header compression parameter of the UE sent by the target C-SGN, or the P-GW determines the header compression parameter of the UE according to header compression capability information of the UE, a local policy, and the like.

Step 1108: and the target C-SGN sends an attach or TAU acceptance message to the UE, wherein the attach or TAU acceptance message carries the header compression parameters of the UE.

Step 1109: the UE sends a header compression context initialization or update message to the target C-SGN, wherein the header compression context initialization or update message comprises a Context Identifier (CID) of the first data service and an identifier of a header compression protocol adopted by the first data service, the header compression protocol belongs to a header compression protocol in header compression parameters, and the header information of a data packet of the first data service is also included.

Step 1110: alternatively, if the header compression process is performed by the P-GW, the target C-SGN forwards a header compression context initialization or update message to the P-GW.

Step 1111 to step 1112: the target C-SGN or P-GW saves the header compression context information of the first data traffic, and optionally replies an acknowledgement message to the UE.

The header compression context initialization or update process of steps 1109 to 1112 may be implemented by a control signaling, for example, the UE carries the header compression context information of the first data service in an attach or TAU complete message, or the header compression context initialization or update process may be implemented by a user plane data packet, that is, the UE carries the header compression context information of the first data service in a sent user plane data packet.

If the UE or the target C-SGN does not support header compression, the UE and the source C-SGN or the P-GW delete the stored header compression context information of the first data service of the UE.

In a second specific embodiment, the UE provides header compression capability information to the core network node, the core network node makes a decision according to the header compression capability information of the UE, subscription information of the UE, and a local policy, and determines a header compression parameter of the UE, the header compression context information of the first data service is initialized or updated between the UE and the core network node based on the negotiated header compression parameter of the UE, and based on the initialized or updated header compression context information of the first data service, a header of a data packet of the first data service may be compressed between the UE and the target C-SGN or P-GW and the compressed data packet may be transmitted, thereby improving transmission efficiency of the data packet.

Based on the same inventive concept, a third embodiment of the present invention provides a core network node, where specific implementation of the core network node may refer to related descriptions in the foregoing method embodiment, and repeated descriptions are omitted, and as shown in fig. 12, the core network node mainly includes:

an obtaining module 1201, configured to obtain header compression capability information of a terminal;

a determining module 1202, configured to determine a header compression parameter of the terminal according to the header compression capability information of the terminal acquired by the acquiring module;

a processing module 1203, configured to initialize or update header compression context information of the first data service of the terminal according to the header compression parameter determined by the determining module.

Specifically, the header compression capability information includes a maximum value of the number of header compression contexts supported by the terminal and a header compression protocol supported by the terminal;

Specifically, the header compression capability information includes a header compression protocol supported by the terminal;

In one implementation, the processing module is specifically configured to:

In another specific implementation, the processing module is specifically configured to:

sending the header compression parameters to the terminal;

In an implementation, the header compression context information of the first data service includes a header compression protocol used for compressing or decompressing a data packet of the first data service, and a transmission parameter of the first data service, where the transmission parameter includes a transmission address and/or port information.

In an implementation, the core network node further includes a data transmission module 1204, configured to:

alternatively, the first and second electrodes may be,

Based on the same concept, in a fourth embodiment of the present invention, another core network node is provided, and specific implementation of the core network node may refer to related descriptions in the foregoing method embodiment portions, and repeated parts are not described again, as shown in fig. 13, the core network node mainly includes a processor 1301 and a memory 1302, where a preset program is stored in the memory 1302, and the processor 1301 reads the program stored in the memory 1302, and executes the following processes according to the program:

acquiring header compression capability information of a terminal;

determining a header compression parameter of the terminal according to the header compression capability information of the terminal;

and initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameters.

In a specific implementation, the processor 1301 acquires a transmission parameter of the first data service of the terminal, where the transmission parameter includes a transmission address and/or port information; determining header compression context information according to the header compression parameters and the transmission parameters of the first data service; initializing or updating the header compression context information of the first data service of the terminal, which is stored by the core network node, according to the determined header compression context information; and sending the determined header compression context information to the terminal so that the terminal initializes or updates the header compression context information of the first data service stored by the terminal.

In another implementation, the processor 1301 transmits the header compression parameter to the terminal; receiving header compression context information sent by the terminal, wherein the received header compression context information is determined by the terminal according to the header compression parameters and transmission parameters of the first data service, and the transmission parameters comprise transmission addresses and/or port information; initializing or updating the header compression context information of the first data service of the terminal stored by the core network node according to the received header compression context information.

In an implementation, the core network node further comprises a transceiver 1303, and the transceiver 1303 is configured to receive or transmit data under the control of the processor 1301. The processor 1301 receives the data packet of the first data service sent by the terminal through the transceiver 1303, and decompresses the packet header of the data packet according to the header compression context information of the first data service of the terminal; alternatively, the first and second electrodes may be,

compressing a packet header of a data packet of the first data service to be sent to the terminal according to the header compression context information of the first data service of the terminal to obtain a compressed data packet, and sending the compressed data packet to the terminal through the transceiver 1303.

Based on the same inventive concept, a fifth embodiment of the present invention provides a terminal, and specific implementation of the terminal may refer to related description of the foregoing method embodiment, and repeated details are not repeated, as shown in fig. 14, where the terminal mainly includes:

a receiving module 1401, configured to receive a header compression parameter of the terminal or header compression context information of a first data service of the terminal, where the header compression parameter is sent by a core network node;

a processing module 1402, configured to initialize or update the header compression context information of the first data service of the terminal according to the header compression parameter received by the receiving module or the received header compression context information.

In one implementation, the processing module 1402 is specifically configured to:

In implementation, the terminal further includes a sending module 1403, configured to:

In practice, the terminal further includes a data transmission module 1404 for:

alternatively, the first and second electrodes may be,

Based on the same inventive concept, in a sixth embodiment of the present invention, a terminal is provided, and specific implementation of the terminal may refer to related descriptions in the above method embodiment sections, and repeated details are omitted, as shown in fig. 15, the terminal mainly includes a processor 1501, a memory 1502, and a transceiver 1503, where the memory 1502 stores a preset program, and the processor 1501 reads the program in the memory 1502, and executes the following processes according to the program:

receiving, by the transceiver 1503, header compression parameters of the terminal or header compression context information of a first data service of the terminal, which are transmitted by a core network node;

initializing or updating the header compression context information of the first data service of the terminal according to the header compression parameter or the received header compression context information.

In a specific implementation, a processor obtains a transmission parameter of the first data service, and determines header compression context information of the first data service according to the transmission parameter and the header compression parameter, wherein the transmission parameter includes a transmission address and/or port information; initializing or updating the header compression context information of the first data service of the terminal according to the determined header compression context information.

In implementation, the processor 1501 sends the header compression context information of the first data service of the terminal to the core network node through the transceiver 1503, so that the core network node initializes or updates the header compression context information of the first data service of the terminal stored by the core network node.

In implementation, the processor 1501 compresses a packet header of a data packet to be transmitted of the first data service according to the header compression context information of the first data service to obtain a compressed data packet, and sends the compressed data packet to the core network node through the transceiver 1503;

alternatively, the first and second electrodes may be,

the data packet of the first data service sent by the core network node is received through the transceiver 1503, and the header of the received data packet is decompressed according to the header compression context information.

Based on the above technical solution, in the embodiment of the present invention, the core network node determines the header compression parameter of the terminal according to the header compression capability information of the terminal, and initializes or updates the header compression context information of the first data service of the terminal according to the determined header compression parameter, so that the packet header of the data packet of the first data service can be compressed and transmitted between the core network node and the terminal according to the header compression context information of the first data service of the terminal, thereby improving the transmission efficiency of the data packet, and further improving the network bandwidth utilization rate. Compared with the mode of performing header compression only in the wireless link transmission between the terminal and the base station, the embodiment of the invention can support the transmission of the data packet subjected to header compression in the wireless link and the wired network by mutually negotiating the compression parameters of the data packet between the terminal and the core network node, and can further improve the transmission efficiency of the data packet in the wireless link and the wired network. In addition, the header compression between the terminal and the core network node can support multiple service data transmission modes such as NAS signaling and user plane bearing, thereby improving the flexibility of transmitting service data and the flexibility of supporting service data transmission by the network.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for determining compression parameters of a data packet, comprising:

the core network node acquires transmission parameters of a first data service of the terminal, wherein the transmission parameters comprise transmission addresses and/or port information;

the core network node determines header compression context information according to the header compression parameters and the transmission parameters of the first data service;

the core network node initializes the header compression context information of the first data service of the terminal according to the determined header compression context information, or updates the header compression context information of the first data service of the terminal stored by the core network node according to the determined header compression context information;

and the core network node sends the determined header compression context information to the terminal through a control signaling.

2. The method of claim 1, wherein the header compression capability information includes a maximum value of the number of header compression contexts supported by the terminal and a header compression protocol supported by the terminal;

3. The method of claim 1, wherein the header compression capability information includes header compression protocols supported by the terminal;

4. The method of claim 1, wherein the core network node obtaining header compression capability information of the terminal comprises:

and the core network node acquires the header compression capability information of the terminal from an attachment request message or a tracking area update TAU request message sent by the terminal.

5. The method according to any of claims 1-4, wherein the header compression context information of the first data traffic comprises a header compression protocol used for compressing or decompressing data packets of the first data traffic, and transmission parameters of the first data traffic, the transmission parameters comprising transmission address and/or port information.

6. The method of any one of claims 1-4, further comprising:

alternatively, the first and second electrodes may be,

7. A method for determining compression parameters of a data packet, comprising:

a terminal receives a header compression parameter of the terminal sent by a core network node through a control signaling;

the terminal acquires transmission parameters of a first data service, and determines header compression context information of the first data service according to the transmission parameters and the header compression parameters, wherein the transmission parameters comprise transmission addresses and/or port information;

and the terminal initializes or updates the header compression context information of the first data service of the terminal according to the determined header compression context information.

8. The method of claim 7, wherein the header compression parameters include a maximum number of header compression contexts allowed to be used and a header compression protocol allowed to be used; alternatively, the header compression parameters include a header compression protocol that is allowed to be used.

9. The method of claim 7, wherein before the terminal receives the header compression parameters of the terminal or the header compression context information of the first data service of the terminal sent by the core network node through the control signaling, the method further comprises:

and the terminal sends the header compression capability information of the terminal to the core network node through an attachment request message or a tracking area update TAU request message.

10. The method according to any of claims 7 to 9, wherein after the terminal initializes or updates header compression context information of the first data service of the terminal according to the header compression parameter, further comprising:

and the terminal sends the header compression context information of the first data service of the terminal to the core network node through a control signaling, so that the core network node initializes or updates the header compression context information of the first data service of the terminal, which is stored by the core network node.

11. The method according to any of claims 7 to 9, wherein the header compression context information of the first data traffic comprises a header compression protocol used for compressing or decompressing data packets of the first data traffic, and transmission parameters of the first data traffic, the transmission parameters comprising transmission address and/or port information.

12. The method of any of claims 7 to 9, further comprising:

alternatively, the first and second electrodes may be,

13. A core network node, comprising:

the processing module is used for acquiring transmission parameters of a first data service of the terminal, wherein the transmission parameters comprise transmission addresses and/or port information; determining header compression context information according to the header compression parameters and the transmission parameters of the first data service; initializing the header compression context information of the first data service of the terminal according to the determined header compression context information, or updating the header compression context information of the first data service of the terminal, which is stored by the core network node, according to the determined header compression context information; and sending the determined header compression context information to the terminal through a control signaling.

14. The core network node of claim 13, wherein the header compression capability information includes a maximum value of a number of header compression contexts supported by the terminal and a header compression protocol supported by the terminal;

15. The core network node of claim 13, wherein the header compression capability information includes header compression protocols supported by the terminal;

16. The core network node of claim 13, wherein the determining module is specifically configured to:

and acquiring the header compression capability information of the terminal from an attach request message or a tracking area update TAU request message sent by the terminal.

17. The core network node according to any of claims 13-16, wherein the header compression context information of the first data traffic comprises a header compression protocol used for compressing or decompressing data packets of the first data traffic, and transmission parameters of the first data traffic, the transmission parameters comprising transmission address and/or port information.

18. The core network node according to any of claims 13-16, further comprising a data transmission module for:

alternatively, the first and second electrodes may be,

19. A terminal, comprising:

a receiving module, configured to receive a header compression parameter of the terminal sent by a core network node through a control signaling;

the processing module is used for acquiring transmission parameters of a first data service, and determining header compression context information of the first data service according to the transmission parameters and the header compression parameters, wherein the transmission parameters comprise transmission addresses and/or port information; initializing or updating the header compression context information of the first data service of the terminal according to the determined header compression context information.

20. The terminal of claim 19, wherein the header compression parameters include a maximum number of header compression contexts allowed to be used and a header compression protocol allowed to be used; alternatively, the header compression parameters include a header compression protocol that is allowed to be used.

21. The terminal of claim 19, further comprising a transmitting module to:

and sending the header compression capability information of the terminal to the core network node through an attachment request message or a tracking area update TAU request message.

22. The terminal according to any of claims 19 to 21, further comprising a sending module for:

sending the header compression context information of the first data service of the terminal initialized or updated by the processing module to the core network node through a control signaling, so that the core network node initializes or updates the header compression context information of the first data service of the terminal stored by the core network node.

23. The terminal according to any of claims 19 to 21, wherein the header compression context information of the first data traffic comprises a header compression protocol used for compressing or decompressing data packets of the first data traffic, and transmission parameters of the first data traffic, the transmission parameters comprising transmission address and/or port information.

24. The terminal according to any of claims 19 to 21, further comprising a data transmission module for:

alternatively, the first and second electrodes may be,