CN113678501B

CN113678501B - Ethernet data packet header compression method, processing method and device thereof

Info

Publication number: CN113678501B
Application number: CN201980094757.2A
Authority: CN
Inventors: 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-26
Filing date: 2019-09-26
Publication date: 2023-07-25
Anticipated expiration: 2039-09-26
Also published as: WO2021056317A1; CN113678501A

Abstract

The application discloses a method for compressing an Ethernet data packet header, a processing method and a device thereof. The method comprises the following steps: the compression device acquires Ethernet header compression parameters configured by the network equipment for the data bearing DRB; according to the Ethernet header compression parameters, the compression device determines a plurality of compression modes; and the compression device performs header compression processing on the Ethernet data packet and generates a compressed packet through the plurality of compression modes. The method perfects the compression mechanism of the Ethernet data packet, and further meets the requirement of header compression of the Ethernet data packet in 5G IIoT.

Description

Ethernet data packet header compression method, processing method and device thereof

Technical Field

The invention relates to the technical field of communication, in particular to the technical field of a processing method of an Ethernet data packet.

Background

In 5G IIoT (Industrial internet of Things, industrial internet), industrial automation (Factory automation), transmission automation (Transport Industry), intelligent power (Electrical Power Distribution) and other services need to be supported for transmission in the 5G system. IIoT introduces the concept of TSN (Time Sensitive Networking, time sensitive network) or TSC (Time Stamp Counter, timestamp register) based on its latency and reliability transmission requirements, and requires header compression of TSN traffic.

In an NR (New Radio) system, a type of a PDU (Protocol Data Unit ) session (session) may be not only an IP packet type but also an Ethernet frame type. For the PDU layer, when the PDU session type is IPv4, IPv6 or IPv4v6, the PDU session is corresponding to an IPv4 data packet and/or an IPv6 data packet; when the PDU Session type is Ethernet, the PDU Session corresponds to an Ethernet frame. Thus, the TSC traffic may be carried by both ethernet frames and IP (Internet Protocol ) packets.

However, in the existing communication system, header compression is only supported for a packet in which a PDU session is an IP packet. The PDCP protocol incorporates header compression and decompression functions to header compress IP packets. The current RoHC (Robust Header Compression ) is configured for DRBs (Data Resource Bearer, data bearers), and the compression device and the decompression device use different header compression and header compression parameters according to the configured profile, and employ the RoHC protocol to perform compression and decompression processing. The current RoHC parameter configuration is concentrated on two parameters, namely maxCID and profiles, and a context ID range (maximum value is maxCID) can be configured in each DRB, and at least one profile can be configured.

However, there are no complete compression mechanism for ethernet packets in the prior art, and there are still many problems that need to be further studied, such as: the information of the context which needs to be included in the compressed packet and the complete packet, the function and the format of the feedback packet and the like. Therefore, the requirement of 5G IIoT cannot be satisfied.

Disclosure of Invention

The invention aims to provide a compression method and a device for an Ethernet packet header, which can perfect an Ethernet packet compression mechanism.

The invention provides the following technical scheme:

in one aspect, a method for compressing an ethernet packet header is provided, which includes: the compression device acquires Ethernet header compression parameters configured by the network equipment for the data bearing DRB; according to the Ethernet header compression parameters, the compression device determines a plurality of compression modes; and the compression device performs header compression processing on the Ethernet data packet and generates a compressed packet through the plurality of compression modes.

In another aspect, a method for processing an ethernet packet header is provided, which includes: the compression device receives a feedback packet determined by the decompression device according to the Ethernet data packet sent by the compression device; according to the feedback packet, the compression device determines the type of the Ethernet data packet which is sent again to the decompression device; the compression device sends the Ethernet data packet with the determined type to the decompression device.

On the other hand, there is also provided a method for compressing the ethernet packet header, after the decompression device receives at least one ethernet packet sent by the compression device, the decompression device establishes and/or stores the context information according to the packet header and the context information of the at least one ethernet packet; and/or decompressing the received at least one ethernet packet according to the established and/or stored context information; and according to the result of the establishment and/or the preservation of the context information and/or the result of the decompression, sending a feedback packet to the compression device.

In another aspect, there is also provided a compression apparatus for ethernet packet header compression, including: an obtaining unit (310) configured to obtain ethernet header compression parameters configured by the network device for the data bearer DRB; and the compression unit (320) is used for determining a plurality of compression modes according to the Ethernet header compression parameters, and performing header compression processing on the Ethernet data packet by the compression device according to the plurality of compression modes to generate a compression packet.

In another aspect, there is also provided a compression apparatus for an ethernet packet header, including: a data packet receiving unit (710) configured to receive a feedback packet determined by the decompressing device according to the ethernet data packet sent by the compressing device; a determining unit (720) configured to determine, according to the feedback packet, a type of the ethernet packet that is retransmitted to the decompression device; and the data packet transmission unit (730) is used for transmitting the Ethernet data packet with the determined type to the decompression device.

In another aspect, there is also provided a compression apparatus for an ethernet packet header, including: a processor, a memory, and a network interface; the processor calls the program in the memory, executes any one of the Ethernet data packet header compression methods for the compression device, and sends out the execution result through the network interface.

In another aspect, there is provided a computer readable storage medium, where the computer readable storage medium stores a program for ethernet packet header compression, where the program for ethernet packet header compression, when executed by a processor, implements any one of the above methods for ethernet packet header compression of a compression device.

In another aspect, there is also provided a decompression apparatus for ethernet packet headers, including: a receiving unit (510) for receiving at least one ethernet packet sent by the compression device; a parsing unit (520) for establishing and/or saving context information based on the header and the context information of the at least one ethernet packet; and/or decompressing the received at least one ethernet packet according to the established and/or stored context information; and the feedback unit (530) is used for sending a feedback packet to the compression device according to the establishment and/or storage result and/or the decompression result.

In another aspect, there is also provided a decompression apparatus for ethernet packet header compression, including: a processor, a memory, and a network interface; the processor calls the program in the memory, executes any one of the Ethernet data packet header compression methods for the decompression device, and sends out the execution result through the network interface.

In another aspect, there is provided a computer readable storage medium, where the computer readable storage medium stores a program for ethernet packet header compression, where the program for ethernet packet header compression, when executed by a processor, implements any one of the above methods for ethernet packet header compression of a decompression device.

The invention has the beneficial effects that: the method comprises the steps of determining the information of the context needed to be included in a compressed packet and a complete packet in a data packet sent by a compression device, so that the problem that a decompression end fails due to no context information decompression is solved; the role of the feedback packets sent by the decompression means is also defined. Therefore, the compression mechanism of the Ethernet data packet is perfected, and the requirement of header compression of the Ethernet data packet in 5G IIoT is met.

Drawings

Fig. 1 is a system architecture diagram applied to the embodiment of the present application.

Fig. 2 is a timing diagram of a method for compressing an ethernet packet header according to an embodiment of the present application.

Fig. 3 is a flowchart of the substeps of step S260 in the embodiment of the present application.

Fig. 4 is a schematic block diagram of a compression apparatus for ethernet packet header compression according to a second embodiment of the present application.

Fig. 5 is a block schematic diagram of the compression unit 320 of fig. 4.

Fig. 6 is a block schematic diagram of a compression apparatus for ethernet packet header compression according to a third embodiment of the present application.

Fig. 7 is a schematic structural diagram of a compression device for compressing ethernet packet headers according to a fourth embodiment of the present application.

Fig. 8 is a block schematic diagram of a decompression apparatus for ethernet packet header compression according to a fifth embodiment of the present application.

Fig. 9 is a schematic structural diagram of a decompression device for ethernet packet header compression according to a sixth embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and detailed description. It should be understood that the detailed description is presented by way of example only and is not intended to limit the invention. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The term "and/or" as used herein includes any and all combinations of one or more of the associated listed items.

The following is an abbreviation for the key terms appearing in the present application and the correspondence table of the full names of chinese and english:

the technical scheme provided in the specific embodiment of the application can be applied to various communication systems, for example: global mobile communications (Global System of Mobile communication, abbreviated as "GSM") system, code division multiple access (Code Division Multiple Access, abbreviated as "CDMA") system, wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as "WCDMA") system, general packet radio service (General Packet Radio Service, abbreviated as "GPRS"), long term evolution (Long Term Evolution, abbreviated as "LTE") system, LTE frequency division duplex (Frequency Division Duplex, abbreviated as "FDD") system, LTE time division duplex (Time Division Duplex, abbreviated as "TDD"), universal mobile telecommunications system (Universal Mobile Telecommunication System, abbreviated as "UMTS"), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, abbreviated as "WiMAX") communication system, or 5G system, and the like.

The invention discloses a method, a device and a system for compressing an Ethernet data packet header. Fig. 1 illustrates a wireless communication system 100 in which embodiments of the present invention may be employed. The wireless communication system includes: a network device 110, and at least one terminal device 120 located within the coverage area of the network device 110. In the uplink transmission, the network device 110 is a decompression device, and the terminal device 120 is a compression device; in downlink transmission, the network device 110 is a compression device, and the terminal device 120 is a decompression device.

The network device 110 configures the DRB with ethernet header compression parameters. The compression device (the terminal device 120 in the uplink transmission and the network device 110 in the downlink transmission) performs header compression according to the ethernet header compression parameters, and sends a data packet. After receiving the data packet, the decompression device (network device 110 in uplink transmission and terminal device 120 in downlink transmission) establishes and/or saves context information, or decompresses the context information; and sends a feedback packet to the compression device according to whether the context information is successfully established and/or saved or whether the context information is successfully decompressed. The compression device determines whether to send the complete data packet or the compressed data packet to the decompression device according to the information content contained in the feedback packet.

Alternatively, the wireless communication system 100 may include a plurality of network devices and each network device may include other numbers of terminal devices within a coverage area of the network device, which is not limited in this application.

Wherein the network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area. Alternatively, the network device 100 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The terminal device 120 may be mobile or stationary. Alternatively, the terminal device 120 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

The following detailed description of the present application will describe in detail how the ethernet data compression mechanism of the prior art is perfected.

Detailed description of the preferred embodiments

Referring to fig. 2, a method for compressing an ethernet packet header is provided in an embodiment of the present application. Header compression (header compression) is to compress a packet header of a data packet to improve transmission efficiency of user data. Currently, in LTE and NR, roHC is used in the PDCP layer to header compress IP packets. In Ethernet, ethernet header compression processing can be performed by using an Ethernet header compression mechanism accordingly. Accordingly, the functional entity of the Ethernet header compression process may be in the PDCP layer, and the configuration parameters of the Ethernet header compression may be configured by a dedicated RRC, such as PDCP-config. When configuring the profiles and the CIDs, a corresponding CID parameter (e.g. maxCID) may be configured for each profile, or a set of CID parameters (e.g. maxCID) may be configured for all profiles.

In the following, the processing of the uplink packet will be described as an example, and the header compression processing of the downlink packet is similar to the above, and will not be repeated.

The Ethernet data packet header compression method comprises the following steps:

step S210, the network equipment configures Ethernet header compression parameters for the DRB; and indicates the ethernet header compression parameter to the terminal device (in uplink transmission, the terminal device is a compression device, and for this specific embodiment, the technical solution of the present application is described by taking uplink transmission as an example, and for convenience of description, the terminal device is referred to as a compression device hereinafter, and explanation will not be repeated. But the network device configures the ethernet header compression parameters for the DRBs, either upstream or downstream.

The ethernet data packet includes an ethernet data packet corresponding to the ethernet stream, or an ethernet frame.

Alternatively, the network device may map or configure different ethernet packets into the same DRB via configuration parameters.

Optionally, the ethernet header compression parameters include at least: maxCID and at least one profile. For example, the network device configures profile 1 and profile2 for the DRB, with a maxCID of 2.

Optionally, the ethernet header compression parameters include at least: at least one maxCID and at least one profile, wherein each profile is configured with a corresponding maxCID. For example, the network device configures profile 1 for the DRB, the corresponding maxCID is 3, and configures profile2, the corresponding maxCID is 2.

Alternatively, the message is indicated to the terminal device by dedicated RRC signaling. Such as: the message is indicated to the terminal device by a PDCP-config IE (Information Element ).

Step S220, the terminal equipment determines a plurality of compression modes according to the Ethernet header compression parameters;

step S225, the terminal equipment performs header compression processing on the Ethernet data packet and generates a compression packet through the plurality of compression modes;

In step S230, the terminal device transmits at least one ethernet packet to the network device (in the uplink transmission, the network device is referred to as a decompression device, and for convenience of description, the network device is referred to as a decompression device, and explanation will not be repeated). Optionally, the at least one ethernet packet includes complete header information and Context ID. Alternatively, the at least one ethernet packet may be a compressed packet.

Optionally, step S230 may also precede step S210 or precede step S220.

Step S240, after the network device receives the at least one Ethernet data packet, the network device establishes and/or stores the context information according to the packet header and the context information of the at least one Ethernet data packet; and/or decompressing the received at least one ethernet packet according to the established and/or stored context information;

step S250, the network device sends a feedback packet (feedback packet) to the terminal device according to the establishment and/or storage result and/or decompression result;

in step S260, the terminal device receives the feedback packet, and determines to send a complete packet or a compressed packet according to the information in the feedback packet.

The full packet (Ethernet packet) refers to an Ethernet packet (Ethernet packet), and the Ethernet packet includes complete Ethernet header information (Ethernet header), context information (e.g., an indication information of whether the Ethernet packet has a context ID or is a compressed packet or a complete packet), and the like. The compressed packet (compressed packet) refers to an ethernet packet that contains compressed header information (or does not contain header information), context information, and the like. The context information is used for header compression and/or decompression. Specifically, when the compression device and the decompression device establish a context relationship, or after the decompression device receives and stores valid context information, the compression device and the decompression device can interactively compress the package.

Optionally, in step S225, "the terminal device performs header compression processing on the ethernet packet and generates a compressed packet by using the multiple compression methods," header compression processing may be performed in one of the following manners:

in the first compression mode, the step S225 includes:

step S2251, selecting a different context ID for each profile of the at least one profile;

step S2252, setting the profile and the corresponding context ID in the context of the complete package;

Step S2253, setting the profile and/or the corresponding context ID in the context of the compression packet. Wherein "containing context ID and/or profile ID as context" means that one of the following three cases is possible: only context ID, or only profile ID, or both context ID and profile ID.

In the second compression mode, the step S220 includes:

step S2254, selecting the same context ID for each profile in the at least one profile;

step S2255, setting the profile and the corresponding context ID in the context of the complete package;

step S2256, setting the profile and the corresponding context ID in the context of the compression packet.

Wherein selecting the same context ID for different profiles comprises: the case of selecting the same context ID for all profiles; alternatively, the same context ID is selected for at least two profiles among the plurality of profiles. For example: there are three profiles, where two profiles select the same context ID, and then the two profiles or all the compression packets corresponding to the profiles contain the profile ID and the context ID. For another example, there are three profiles, where two profiles select the same partial context ID (e.g., profile ID 1 selects the context ID of 1, 2, profile ID 2 selects the context ID of 1, 3), and then the two profiles or all the compression packets corresponding to the profiles include the profile ID and the context ID.

As a specific example, when only one profile is included or configured in one DRB, only context ID may be included in the full packet and/or the compressed packet. Of course, profile ID may be further included.

Optionally, the terminal device performs header compression processing in the first compression mode or the second compression mode, which may be configured by a network, may be predefined, or may be selected by the terminal device itself. The selection is performed by a network configuration mode, and may be an explicit instruction or an implicit instruction. The implicit indication means that the terminal device derives according to the parameter condition of the network configuration, so as to determine whether to perform header compression processing in the first compression mode or the second compression mode. For example: each profile is given a maxCID, and the maxCID ranges are the same, and a compression mode two should be adopted; each profile is given a maxCID, and the maxCID ranges are different, then a compression mode one should be adopted; giving a maxCID with multiple profiles, and adopting a compression mode II; multiple profiles are given to one maxCID, and the maxCID selected by different profiles is specified to be different, then compression mode one should be adopted.

In the application, if the network device (i.e. the decompression device) configures an ethernet packet with multiple profiles mapped in one DRB, and the terminal device (i.e. the compression device) selects different context IDs for different profiles when selecting the context ID, the context ID and the profile ID are included in the complete packet as the context, and at least the context ID and/or the profile ID are in the compressed packet as the context.

If the network device (i.e. the decompression device) configures an ethernet packet with multiple profiles mapped in one DRB, and when the terminal device (i.e. the compression device) selects a context ID for different profiles, the complete packet and the compressed packet both contain the context ID and the profile ID as contexts.

In one embodiment, when the terminal device determines to compress the ethernet packet header, the terminal device performs header compression according to configuration information, ethernet packet information received from a higher layer, and the like. That is, the terminal device determines the path to which the ethernet packet belongs, that is, the profile that can be corresponding, context selected for the terminal device, and/or corresponding context, and the like. The terminal device then transmits a complete packet for each path, and then transmits a compressed packet when a condition is satisfied (e.g., when a feedback packet transmitted by the network device is received and/or N complete packets are transmitted).

For example: assuming that the DRB configures profile1 and profile2 at this time, the terminal device performs the following processing:

when the packets packet1 and packet2 of the higher layer are received and the profile1 corresponding to the packet1 and the profile2 corresponding to the packet2 are determined, the terminal device selects the context ID corresponding to the packet1 to be 1 and the context ID corresponding to the packet2 to be 2, and then the complete packet corresponding to the packet1 contains the context ID1 and the profile ID1, and the compressed packet corresponding to the packet1 contains the context ID1. Correspondingly, the context ID2 and the profile ID2 are contained in the whole corresponding to the packet2, and the context ID2 and/or the profile ID are contained in the compressed packet corresponding to the packet 1.

When the packets packet1 and packet2 of the higher layer are received and the packet1 packet corresponds to the profile1 and the profile2 corresponding to the packet2 is determined, the UE selects the context ID corresponding to the packet1 to be 1 and the context ID corresponding to the packet2 to be 1, and then the complete packet corresponding to the packet1 contains the context ID1 and the profile ID1 and the compressed packet corresponding to the packet1 contains the context ID1 and the profile ID1. Correspondingly, the context ID1 and the profile ID2 are contained in the complete corresponding to the packet2, and the context ID1 and the profile ID2 are contained in the compressed packet corresponding to the packet 1.

In the first embodiment, in the ethernet packet header compression processing, a scheme of determining whether profile information is included in a context is provided, so that the problem that when a network device receives a compressed packet, since there is insufficient context information, how to select a path or a context is not known, and decompression fails is avoided.

Optionally, step S250 "sending a feedback packet to the terminal device according to the result of the establishing and/or storing and/or the result of decompressing" specifically includes:

step S251, when the network device successfully establishes and/or saves the context information, a feedback packet containing a success indication (such as ACK) is sent; if the compression device is a context ID and/or a transmitted data packet determined by adopting the compression mode one, setting the context ID and/or profile ID and ACK in the feedback packet containing the success indication; if the compression device adopts the context ID and/or the transmitted data packet determined by the compression mode II, setting the context ID, profile ID and ACK information in a feedback packet;

Step S252, when the network device fails to establish and/or save the context information, or fails to decompress (or the number of times of decompression fails exceeds a predetermined value), or fails, or deletes the context, or when the context is wrong, a feedback packet containing a failure indication (NACK) is sent; if the compression device is a context ID and/or a transmitted data packet determined by the compression method, setting the context ID and/or profile ID and NACK information in the feedback packet; if the compression device adopts the context ID and/or the transmitted data packet determined by the compression mode II, setting the context ID, profile ID and NACK information in a feedback packet;

step S253, when the network device sends a feedback packet that does not include a specific indication (information indicating whether the context information is established and/or saved successfully or failed, or information indicating whether the decompression is successful or failed, or carries an ACK/NACK indication, or carries a feedback packet length indication), if the compression device is a context ID and/or a data packet that is sent and determined by adopting the compression method, the context ID and/or profile ID is set in the feedback packet; if the compression device adopts the context ID and/or the transmitted data packet determined by the compression mode II, the context ID and the profile ID are set in the feedback packet. That is, if the compression device adopts the context ID and/or the transmitted data packet determined by the compression method two, the feedback packet must carry the context ID and the profile ID.

Optionally, the feedback packet may further carry SN (Sequence Number) of at least one PDCP PDU, and for each PDCP data PDU corresponding to SN, the decompression status of the network device, i.e. failure (such as NACK) or success (such as ACK), may be indicated respectively. Optionally, the PDCP PDU corresponding to each sequence number is a packet that fails decompression. Optionally, the PDCP PDU corresponding to each sequence number is a successfully decompressed packet. Optionally, the PDCP PDU corresponding to the sequence number is the last successfully decompressed packet. Optionally, the PDCP PDU corresponding to the sequence number is the first SN after the last successfully decompressed packet. Optionally, the PDCP PDU corresponding to each sequence number is information indicating whether decompression of all received packets is successful or failed, starting with the first unsuccessfully decompressed packet.

As shown in fig. 3, optionally, step S260 "the terminal device receives the feedback packet and determines to send a complete packet or a compressed packet according to information in the feedback packet" includes:

step S261, the terminal equipment receives a feedback packet determined by the network equipment according to the Ethernet data packet sent by the terminal equipment;

step S262, according to the feedback packet, the terminal device determines the type of the ethernet packet that is resent to the network device;

In step S263, the terminal device sends the ethernet packet of the determined type to the network device.

Optionally, step S262 further includes determining, by the terminal device, that the context state of the network device is successful in establishing the context and/or storing the context according to the feedback packet.

Optionally, step S262 specifically includes: and according to the indication information carried in the feedback packet, the compression device determines the type of the Ethernet data packet which is sent again to the decompression device. The specific steps can be as follows:

when the feedback packet received by the terminal equipment contains an ACK indication, a compressed packet is sent to the network equipment; that is, when the feedback packet received by the terminal device includes an ACK indication, it is considered that the context information of the network device has been successfully established and/or stored, so that a compressed packet can be sent;

when the feedback packet received by the terminal equipment contains a NACK indication, a complete packet is sent to the network equipment; when the feedback packet received by the terminal equipment contains a NACK indication, the context information of the network equipment is considered to be unsuccessfully established and/or stored, or is invalid/wrong/deleted, or is decompressed and fails, so that a complete packet needs to be sent;

optionally, in step S262, the context state of the decompressing device may be determined according to the indication information carried in the feedback packet. The transmitted ethernet data type is then acknowledged according to the context state. The method comprises the following steps:

Under the condition that the indication information is determined to be ACK indication, the compression device determines that the context state of the decompression device is that the context establishment is successful and/or the context is saved; then send the compressed packet;

in the case that the indication information is determined to be a NACK indication, the compression device determines that the context state of the decompression device is one of the following: the context fails, the context is deleted, and the context is wrong; the complete packet is sent.

Optionally, step S262 may further include determining a context state of the decompressing device according to the indication information carried in the feedback packet. The transmitted ethernet data type is then acknowledged according to the context state. Specific:

under the condition that the indication information is determined to be ACK indication, the compression device determines that the context state of the decompression device is that the context establishment is successful and/or the context is saved; the compressed packet may be sent;

in the case that the indication information is determined to be a NACK indication, the compression device determines that the context state of the decompression device is one of the following: the context fails, the context is deleted, and the context is wrong; the complete packet needs to be sent.

And when the feedback packet received by the terminal equipment does not contain a specific indication, transmitting a compressed packet. That is, when the feedback packet received by the terminal device does not contain a specific indication, it is also considered that the context information of the network device has been successfully established and/or saved, or that there is no unsuccessful decompression, so that the compressed packet may be sent out.

Optionally, the terminal device may further execute step S264, where the terminal device may send the complete packet or the compressed packet according to a preset rule after receiving the feedback packet. For example: the terminal device may send the compressed packet after receiving the feedback packet for the first time, send the complete packet after receiving the feedback packet for the second time, send the compressed packet after receiving the feedback packet for the third time, send the complete packet after receiving the fourth time, and so on. In this transmission scheme, the feedback packet does not need to include the specific instruction information.

Optionally, the terminal device may further perform step S265, where the terminal device sends a complete packet when the feedback packet is not received, or sends a compressed packet after sending or continuously sending a predetermined number of complete packets, or sends a compressed packet after sending a predetermined time period of the first complete packet, or sends a complete packet all the time when the feedback packet is not received.

In a first embodiment of the present application, the role and format of a feedback packet sent by a network device are defined, which reveals how the feedback packet is used, and perfects the protocol rule.

Detailed description of the preferred embodiments

Referring to fig. 4, a compression apparatus 300 for ethernet packet header compression is provided in a second embodiment of the present application. The compression device 300 includes:

an obtaining unit 310, configured to obtain an ethernet header compression parameter configured by the network device for the DRB;

Optionally, the ethernet header compression parameters include at least: at least one profile and a maxCID corresponding to each of the at least one profile, respectively.

Optionally, in uplink transmission, the network device indicates the message to the compression device (i.e. the terminal device) through dedicated RRC signaling. Such as: the message is indicated to the compression device by the PDCP-config IE.

And the compression unit 320 is configured to determine a plurality of compression modes according to the ethernet header compression parameters, and through the plurality of compression modes, the compression device performs header compression processing on the ethernet packet and generates a compressed packet.

Optionally, the at least one ethernet packet includes complete header information and Context ID. Alternatively, the at least one ethernet packet may be a compressed packet.

Optionally, the compression device further includes: and a transmitting unit 330 for transmitting the compressed packet to a decompressing device.

Optionally, the compression device further includes: the mapping unit 340 is configured to map the plurality of ethernet packets into one DRB according to the ethernet header compression parameter.

Referring to fig. 5, optionally, the compression unit 320 includes:

a first compression unit 321, configured to select a different context ID for each profile of the at least one profile; setting the profile and the corresponding context ID in the context of the complete package; setting the profile and/or the corresponding context ID in the context of the compression packet;

a second compression unit 322, configured to select the same context ID for each profile of the at least one profile; setting the profile and the corresponding context ID in the context of the complete package; and setting the profile and the corresponding context ID in the context of the compressed package.

Optionally, the compression unit 320 further includes:

a selecting unit 323 for selecting whether to perform the header compression processing by the first compressing unit 321 or the second compressing unit 322. The selection mode can be network configuration, predefined or selected by the compression device.

The selection is performed by a network configuration mode, and may be an explicit instruction or an implicit instruction. The implicit indication means that the terminal device derives according to the parameter conditions of the network configuration, so as to determine whether to use the first compression unit 321 or the second compression unit 322 for header compression. For example: each profile is given a maxCID, and the maxCID ranges are the same, the second compression unit 322 should be used; each profile is given a maxCID, and the maxCID ranges are different, the first compression unit 321 should be used; a plurality of profiles to one maxCID, the second compression unit 322 should be employed; the first compression unit 321 should be used if a plurality of profiles are given to one maxCID and it is specified that the maxCID selected by different profiles is different.

In the second embodiment, when it is determined to compress the ethernet packet header, the compression device performs header compression processing based on the configuration information, ethernet packet information received from a higher layer, and the like. That is, the compression device determines the path to which the ethernet packet belongs, i.e. the profile that can be mapped, context selected for it and/or the corresponding context, etc. The compression device then transmits a complete packet for each path, and then transmits the compressed packet when a condition is satisfied (e.g., when a feedback packet transmitted by the decompression device is received and/or when N complete packets are transmitted).

In the second embodiment, in the ethernet packet header compression processing, a scheme of determining whether profile information is included in a context is provided, so that the problem that when a decompression device receives a compressed packet, since there is insufficient context information, how to select a path or a context is not known, and decompression fails is avoided.

Detailed description of the preferred embodiments

Referring to fig. 6, a compression apparatus 700 for ethernet packet headers is provided in accordance with a third embodiment of the present application. The compression device 700 includes:

a data packet receiving unit 710, configured to receive a feedback packet determined by the decompressing device according to the ethernet data packet sent by the compressing device;

a determining unit 720, configured to determine, according to the feedback packet, a type of the ethernet packet that is sent again to the decompression device;

and a packet transmission unit 730, configured to send the ethernet packet of the determined type to the decompression device.

Optionally, the determining unit 720 is further configured to determine, according to the feedback packet, that the context state of the decompressing device is that the context establishment is successful and/or the context is saved.

Optionally, the determining unit 720 is specifically configured to determine, according to the indication information carried in the feedback packet, a type of the ethernet packet that is sent again to the decompressing device. The method specifically comprises the following steps:

Determining to send the compressed packet to the decompression device under the condition that the indication information is determined to be ACK indication;

and if the indication information is determined to be NACK indication, determining to send the complete packet to the decompression device.

Optionally, the determining unit 720 is specifically configured to:

under the condition that the indication information is ACK indication, determining that the context state of the decompression device is successful in establishing the context and/or saving the context;

and under the condition that the indication information is determined to be NACK indication, determining that the context state of the decompression device is one of the following: the context fails, the context is deleted, and the context is erroneous.

Optionally, the data packet transmission unit 730 is further configured to send a complete packet or a compressed packet according to a preset rule after receiving the feedback packet.

Optionally, the data packet transmission unit 730 is further configured to send a complete packet to the decompression device when the feedback packet is not received; or, after transmitting or continuously transmitting a predetermined number of complete packets, transmitting the compressed packets to the decompression device; alternatively, the compressed packet is transmitted after a predetermined period of time from the transmission of the first complete packet.

The compression device in the third embodiment of the present application determines whether to send the complete packet or the compressed packet according to the feedback packet of the decompression device; or determining whether to transmit the complete packet or the compressed packet according to the feedback condition of the decompression device, if the complete packet is transmitted without the feedback packet; or according to a predetermined rule, for example, transmitting the compressed packet after transmitting N complete packets, or transmitting the compressed packet after transmitting a predetermined time period after transmitting the first complete packet. Thus, the problem of decompression failure of the decompression device can be solved. In the third embodiment, please refer to the corresponding or related portion in the first embodiment, and the detailed description is not repeated here.

Detailed description of the preferred embodiments

Referring to fig. 7, a compression apparatus 400 for compressing ethernet packet headers according to a fourth embodiment of the present invention is shown. The compression apparatus 400 includes: processor 410, memory 420, and network interface 430. The processor 410 invokes a program in the memory 420, performs the steps performed by the terminal device 120 in the ethernet packet header compression method provided in the first embodiment, and sends the execution result through the network interface 430.

The processor 410 may be a single component or may be a combination of processing elements. For example, it may be a CPU, ASIC, or one or more integrated circuits configured to implement the above methods, such as at least one microprocessor DSP, or at least one programmable gate array FPGA, or the like.

Detailed description of the preferred embodiments

Referring to fig. 8, a decompression apparatus 500 for ethernet packet header compression is provided in a fifth embodiment of the present application. The application scenario of the decompression apparatus 500 is: the network equipment configures Ethernet header compression parameters for the DRB; and indicates the ethernet header compression parameter to the compression device. The decompression device 500 processes the packets sent by the compression device.

The decompression apparatus 500 includes:

a receiving unit 510, configured to receive at least one ethernet packet sent by the compression device;

a parsing unit 520, configured to establish and/or store context information according to the header and the context information of the at least one ethernet packet; and/or decompressing the received at least one ethernet packet according to the established and/or stored context information;

and a feedback unit 530, configured to send a feedback packet to the compression device according to the result of the establishing and/or saving and/or the decompression result.

Optionally, the feedback unit 530 is specifically configured to send a feedback packet including indication information, where the indication information is used to indicate whether the decompressing device successfully establishes and/or saves the context information, or whether the decompressing device successfully decompresses.

Optionally, the feedback unit 530 is specifically configured to send a feedback packet including a success indication (such as ACK) when the decompressing device successfully establishes and/or saves the context information; when the decompression device fails to establish and/or save the context information, or fails to decompress (or the number of times of decompression fails exceeds a predetermined value), or the context fails, or the context is deleted, or the context is erroneous, a feedback packet containing a failure indication (NACK) is sent.

Preferably, the feedback unit 530 may be further specifically configured to send a feedback packet that does not include a specific indication (information indicating whether the context information is established and/or saved successfully or failed).

Optionally, the feedback packet may further carry SN of at least one PDCP PDU, and the corresponding PDCP PDU corresponding to each SN may indicate decompression status of the network device, i.e. failure or success, respectively. Optionally, the PDCP PDU corresponding to each sequence number is a packet with decompression failure. Optionally, the PDCP PDU corresponding to each sequence number is a successfully decompressed packet. Optionally, the PDCP PDU corresponding to the sequence number is the last successfully decompressed packet. Optionally, the PDCP PDU corresponding to the sequence number is the first SN number after the last successfully decompressed packet. Optionally, the PDCP PDU corresponding to each sequence number is information indicating whether decompression of all received packets is successful or failed, starting from the first packet that is not successfully decompressed.

Optimally, the decompressing device 500 may further include:

a configuration unit 540, configured to map different ethernet packets into the same DRB through configuration parameters.

In a fourth embodiment of the present application, the role and format of the feedback packet sent by the network device are defined, which reveals how the feedback packet is used, and perfects the protocol rule. In the fifth embodiment, please refer to the corresponding or related portion in the first embodiment, and the detailed description is not repeated here.

Detailed description of the preferred embodiments six

Referring to fig. 8, a decompression apparatus 600 for ethernet packet header compression according to a sixth embodiment of the present application is shown. The decompression apparatus 600 includes: processor 610, memory 620, and network interface 630. The processor 610 invokes a program in the memory 620 to perform the steps of an uplink control channel transmission method according to the first embodiment. The network interface 630 transmits the signal processed by the processor 610.

The processor 331 may be a separate component or may be a generic term for multiple processing elements. For example, it may be a CPU, ASIC, or one or more integrated circuits configured to implement the above methods, such as at least one microprocessor DSP, or at least one programmable gate array FPGA, or the like.

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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. The program may be stored in a computer readable storage medium, which may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.

The above-described embodiments illustrate but do not limit the invention, and a person skilled in the art can devise numerous alternative examples within the scope of the claims. Those skilled in the art will appreciate that appropriate adaptations, modifications, etc. may be made to the specific embodiments without departing from the scope of the invention as defined by the appended claims. Accordingly, any modification or variation of the present invention in light of the spirit and principles of the present invention is intended to be within the scope of the present invention as defined in the appended claims.

Claims

1. A method for compressing an ethernet packet header, the method comprising:

the compression device acquires Ethernet header compression parameters configured by the network equipment for the data bearing DRB;

according to the Ethernet header compression parameters, the compression device determines a plurality of compression modes;

the compression device performs header compression processing on the Ethernet data packet and generates a compression packet through the plurality of compression modes;

wherein after the compressing device generates the compressed ethernet packet, the method further comprises:

the compression device sends the compressed packet to a decompression device;

wherein the method comprises the following steps:

The compression device receives a feedback packet determined by the decompression device according to the compression packet sent by the compression device;

according to the feedback packet, the compression device determines the type of the Ethernet data packet which is sent again to the decompression device;

the compression device sends the Ethernet data packet with the determined type to the decompression device;

wherein the type of the retransmitted ethernet packet includes one of the following: complete packets and compressed packets;

the step of determining, by the compression device, the type of the ethernet packet sent again to the decompression device according to the feedback packet, includes:

and according to the indication information carried in the feedback packet, the compression device determines the type of the Ethernet data packet which is sent again to the decompression device.

The step of determining, by the compression device, the type of the ethernet packet sent again to the decompression device according to the indication information carried in the feedback packet includes:

in the case that the indication information is determined to be an ACK indication, the compression device determines to send the ethernet packet of which the type is the retransmission of the compressed packet to the decompression device;

In the case that the indication information is determined to be a NACK indication, the compression device determines to send the Ethernet data packet with the type of the retransmission of the complete packet to the decompression device.

2. The method of claim 1, wherein the ethernet header compression parameters comprise one of:

at least one profile and a maximum context identification maxCID;

at least one profile and a maxCID corresponding to each of the at least one profile, respectively.

3. The method of claim 1, wherein the step of performing header compression processing on the ethernet packet by the compression device through the plurality of compression modes comprises:

the compression device selects different contextID for each profile in at least one profile;

the compression device sets the profile and the corresponding contextID in the context of the complete packet;

the compression device sets the profile and/or the corresponding contextID in the context of the compression packet.

4. A method according to any one of claims 1 to 3, wherein said step of header compression processing of ethernet packets by said compression means through said plurality of compression means comprises:

The terminal selects the same contextID for each profile in the at least one profile;

the terminal sets the profile and the corresponding contextID in the context of the complete packet;

the terminal sets the profile and the corresponding contextID in the context of the compressed packet.

5. A method as claimed in any one of claims 1 to 3, the method further comprising, prior to the compression means determining one or more compression modes in dependence on the ethernet header compression parameters: the network device maps a plurality of the Ethernet data packets into one DRB according to the Ethernet header compression parameters.

6. The method of claim 1, the method further comprising:

according to the feedback packet, the compression device determines that the context state of the decompression device is that the context establishment is successful and/or the context is saved.

7. The method of claim 1, the method further comprising:

and according to the indication information carried in the feedback packet, the compression device determines the context state of the decompression device.

8. The method of claim 7, the method further comprising: according to the indication information carried in the feedback packet, the step of determining the context state of the decompressing device by the compressing device includes:

Under the condition that the indication information is determined to be ACK indication, the compression device determines that the context state of the decompression device is that the context establishment is successful and/or the context is saved;

in the case that the indication information is determined to be a NACK indication, the compression device determines that the context state of the decompression device is one of the following: the context fails, the context is deleted, and the context is erroneous.

9. The method of claim 1, wherein the method further comprises:

and after receiving the feedback packet, sending the retransmitted Ethernet data packet with the type of a complete packet or the retransmitted Ethernet data packet with the type of a compressed packet according to a preset rule.

10. The method of claim 1, wherein the method further comprises:

when the feedback packet is not received, sending the retransmitted Ethernet data packet with the complete packet type to a decompression device; or,

transmitting the retransmitted ethernet data packet with the compressed packet type to a decompression device after transmitting or continuously transmitting a predetermined number of complete packets; or,

and transmitting the retransmitted Ethernet data packet with the compressed packet type after transmitting the retransmitted Ethernet data packet with the first type being a complete packet for a preset time.

11. A compression apparatus for an ethernet packet header, the compression apparatus comprising:

an obtaining unit (310) configured to obtain ethernet header compression parameters configured by the network device for the data bearer DRB;

the compression unit (320) is used for determining a plurality of compression modes according to the Ethernet header compression parameters, and performing header compression processing on the Ethernet data packet by the compression device according to the plurality of compression modes to generate a compression packet;

wherein the compression device further comprises:

a transmission unit (330) for transmitting the compressed packet to a decompression device;

wherein the compression device further comprises:

a data packet receiving unit (710) configured to receive a feedback packet determined by the decompressing device according to the compressed packet sent by the compressing device;

a determining unit (720) configured to determine, according to the feedback packet, a type of the ethernet packet that is retransmitted to the decompression device;

a packet transmission unit (730) for transmitting the ethernet packet of the determined type to the decompression device;

The determining unit (720) is specifically configured to determine, according to the indication information carried in the feedback packet, a type of the ethernet packet that is sent again to the decompression device;

wherein the determining unit (720) is specifically configured to:

determining to transmit the ethernet packet of which the type is the retransmission of the compressed packet to the decompression device, if the indication information is determined to be an ACK indication;

and if the indication information is determined to be NACK indication, determining to send the Ethernet data packet which is the resending type of the complete packet to the decompression device.

12. The compression device of claim 11, wherein the compression device further comprises: and the mapping unit (340) is used for mapping a plurality of Ethernet data packets into one DRB according to the Ethernet header compression parameters by the network equipment.

13. The compression apparatus of claim 11, wherein the ethernet header compression parameters comprise one of:

at least one profile and a maximum context identification maxCID;

14. The compression apparatus as set forth in claim 11, wherein the compression unit (320) includes:

a first compression unit (321) for selecting a different context ID for each of the at least one profile; setting the profile and the corresponding context ID in the context of the complete package; setting the profile and/or the corresponding contextID in the context of the compression packet;

a second compression unit (322) for selecting the same context ID for each of the at least one profile; setting the profile and the corresponding context ID in the context of the complete package; and setting the profile and the corresponding contextID in the context of the compressed package.

15. The compression apparatus as set forth in claim 14, wherein the compression unit (320) further includes:

and a selection unit (323) for selecting whether to perform header compression processing by using the first compression unit (321) or the second compression unit (322).

16. The compression device according to claim 11, wherein the determining unit (720) is further configured to determine, based on the feedback packet, that the context state of the decompression device is context establishment success and/or context preservation.

17. The compression apparatus of claim 11, wherein the determining unit (720) is further configured to determine the context state of the decompression apparatus according to the indication information carried in the feedback packet.

18. The compression device of claim 17, wherein the determining unit (720) is specifically configured to:

19. The compression apparatus of claim 11, wherein said packet transmission unit (730),

and the method is also used for sending the retransmitted Ethernet data packet with the type of a complete packet or the retransmitted Ethernet data packet with the type of a compressed packet according to a preset rule after receiving the feedback packet.

20. The compression apparatus as set forth in claim 11, wherein said packet transmission unit (730) is further configured to:

transmitting the retransmitted ethernet data packet with the type of a complete packet to a decompression device when the feedback packet is not received; or,

21. A compression apparatus for an ethernet packet header, the compression apparatus comprising: a processor, a memory, and a network interface; the processor invokes the program in the memory, performs the ethernet packet header compression method according to any one of the preceding claims 1 to 10, and sends the execution result out through the network interface.

22. A computer readable storage medium, wherein a program for ethernet packet header compression is stored on the computer readable storage medium, and the program for ethernet packet header compression, when executed by a processor, implements the ethernet packet header compression method of any one of claims 1 to 10.