CN111148153A

CN111148153A - Data packet sending method, receiving method and equipment

Info

Publication number: CN111148153A
Application number: CN201811301462.1A
Authority: CN
Inventors: 刘佳敏
Original assignee: 电信科学技术研究院有限公司
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-11-02
Filing date: 2018-11-02
Publication date: 2020-05-12
Anticipated expiration: 2038-11-02
Also published as: CN111148153B

Abstract

The embodiment of the invention provides a data packet sending method, a data packet receiving method and data packet receiving equipment, wherein the method comprises the following steps: determining a designated portion of the first data packet to be compressed; determining first information corresponding to the designated part according to the designated part; and sending a second data packet to the receiving end, wherein the second data packet comprises: the other part except the specified part in the first data packet and the first information. In the embodiment of the invention, the data packet in the field of industrial Internet of things can be compressed or decompressed, so that the overhead is saved, the transmission efficiency is improved, and the requirements of high reliability and low time delay of transmission are met.

Description

Data packet sending method, receiving method and equipment

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a data packet sending method, a data packet receiving method and data packet receiving equipment applied to the Internet of things.

Background

In the field of industrial internet of things, it is necessary to transmit a data packet of a Time Sensitive Network (TSN) over a common communication network. The data of the TSN network is typically an ethernet data structure or other type of data structure.

However, in the header compression algorithm supported by the current communication network, there is no existing algorithm for performing header compression on the data packets, so when the data packets are transmitted through the communication network, the overhead ratio of the header is too large, which is not favorable for improving the transmission efficiency, and the service requirements of high reliability and low delay are met.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a data packet sending method, a data packet receiving method, and a device, which solve the problem of compression or decompression of a data packet in the field of industrial internet of things.

According to a first aspect of the embodiments of the present invention, a data packet sending method is provided, which is applied to a sending end, and the method includes: determining a designated portion of the first data packet to be compressed; according to the designated part, determining first information corresponding to the designated part; sending a second data packet to a receiving end, wherein the second data packet comprises: the other part except the specified part in the first data packet and the first information.

Optionally, the specified part is a whole header or a part of a header of the first data packet; correspondingly, the determining the first information corresponding to the designated part according to the designated part comprises: and determining a compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

Optionally, before the sending the second data packet to the receiving end, the method further includes: sending compression indication information to the receiving end; and after receiving ACK information for confirming the compression indication information from the receiving end, performing the step of transmitting the second packet to the receiving end.

Optionally, the compression indication information includes one or more of: second information indicating a correspondence relationship between all or a part of the header of the compressed first packet and a compression Index; third information indicating a position of a partial header of the first packet to be compressed in the first packet header; fourth information indicating an identification of a partial header of the first packet being compressed; fifth information indicating a length of a partial header of the first packet that is compressed.

Optionally, the compression indication information is obtained by at least one of: radio resource control, RRC, signaling; a control protocol data unit PDU of a user plane; a user plane mapping notification PDU; user plane data PDU.

Optionally, the user plane mapping notification PDU includes a first sequence number SN, and the first SN and a second SN of the second packet are allocated by the same SN sequence space.

Optionally, the designated portion is a frame check sequence FCS of the first data packet; correspondingly, the determining the first information corresponding to the designated part according to the designated part comprises: and determining the first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

Optionally, before the determining the specific portion to be compressed in the first data packet, the method further includes: determining the on or off of the compression function of the designated part through RRC signaling; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

Optionally, the turning on or off of the compression function includes any one of: the compression function is started or closed based on the granularity of data bearing DRB of a packet data convergence protocol PDCP layer; the compression function is started or closed based on the granularity of a Protocol Data Unit (PDU) session of a service discovery application Specification (SDAP) layer; the compression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer; the compression function is turned on or off based on the data granularity of the new protocol layer.

Optionally, the second data packet further includes: sixth information for explicitly or implicitly indicating that the second data packet is a compressed data packet or for explicitly or implicitly indicating that the second data packet is not a compressed data packet.

Optionally, the first information is used to indicate that FCS compression is performed, and the sixth information is used to explicitly or implicitly indicate that, when the second packet is a compressed packet, the sixth information and the first information occupy 1bit together, or the sixth information and the first information occupy 1bit respectively.

Optionally, the format of the first data packet or the second data packet is at least one of: the format of the PDCP data packet; the format of the SDAP packet; the format of the data packets of the new protocol layer.

Optionally, the sending end is a network device on a wireless access network side, and the receiving end is a terminal; or the sending end is network equipment on the core network side, and the receiving end is a terminal; or the sending end is a terminal, and the receiving end is network equipment on a wireless access network side or network equipment on a core network side.

According to a second aspect of the embodiments of the present invention, there is provided a data packet receiving method, applied to a receiving end, the method including: receiving a second data packet from a sender, the second data packet comprising: the other part except the appointed part in the first data packet and the first information; obtaining a designated part corresponding to the first information according to the first information; and obtaining the first data packet according to the specified part and other parts of the first data packet except the specified part.

Optionally, the first information is a compression Index; correspondingly, the obtaining of the designated part corresponding to the first information according to the first information includes: and obtaining all or part of the header of the first data packet corresponding to the compression Index according to the compression Index.

Optionally, before receiving the second data packet from the transmitting end, the method further includes: and receiving compression indication information from the sending end, and sending ACK (acknowledgement character) information of the compression indication information to the sending end.

Optionally, the compression indication information includes one or more of: second information indicating a correspondence relationship between all or a part of the header of the compressed first packet and a compression Index; third information indicating a position of a partial header of the first packet to be compressed in the first packet header; fourth information indicating an identification of a partial header of the first packet being compressed; fifth information indicating a length of a partial header of the first packet that has been compressed.

Optionally, the first information is used to indicate that FCS compression is performed; correspondingly, the obtaining of the designated part corresponding to the first information according to the first information includes: determining the FCS of the first data packet according to the first information.

Optionally, before receiving the second data packet from the transmitting end, the method further includes: determining the opening or closing of the decompression function of the designated part through RRC signaling; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

Optionally, the turning on or off of the decompression function includes any one of: the decompression function is started or closed based on the granularity of data bearing DRB of a packet data convergence protocol PDCP layer; the decompression function is started or closed based on the granularity of a Protocol Data Unit (PDU) session of a service discovery application Specification (SDAP) layer; the decompression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer; the decompression function is turned on or off based on the data granularity of the new protocol layer.

Optionally, the first information is used to indicate that, when FCS compression is performed, the sixth information and the first information occupy 1bit in total, or the sixth information and the first information occupy 1bit respectively.

According to a third aspect of the embodiments of the present invention, there is provided a transmitting end, including: the first determining module is used for determining a specified part to be compressed in the first data packet; the second determining module is used for determining first information corresponding to the specified part according to the specified part; a first sending module, configured to send a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

Optionally, the specified part is a whole header or a part of a header of the first data packet; accordingly, the second determining module is further configured to: and determining a compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

Optionally, the sending end further includes: the second sending module is used for sending the compression indication information to the receiving end; the first sending module is further configured to execute the step of sending the second data packet to the receiving end after receiving ACK information for acknowledging the compression indication information from the receiving end.

Optionally, the designated portion is a frame check sequence FCS of the first data packet; accordingly, the second determining module is further configured to: and determining the first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

Optionally, the sending end further includes: a third determining module, configured to determine, through RRC signaling, whether to turn on or off a compression function of the designated portion; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

According to a fourth aspect of the embodiments of the present invention, there is provided a receiving end, including: a first receiving module, configured to receive a second data packet from a sending end, where the second data packet includes: the other part except the appointed part in the first data packet and the first information; the first acquisition module is used for acquiring a designated part corresponding to the first information according to the first information; and the second acquisition module is used for acquiring the first data packet according to the specified part and other parts of the first data packet except the specified part.

Optionally, the first information is a compression Index; accordingly, the first obtaining module is further configured to: and obtaining all or part of the header of the first data packet corresponding to the compression Index according to the compression Index.

Optionally, the receiving end further includes: and the second receiving module is used for receiving the compression indication information from the sending end and sending ACK (acknowledgement character) information of the compression indication information to the sending end.

Optionally, the receiving end further includes: a fourth determining module, configured to determine, through RRC signaling, whether to turn on or off a decompression function of the designated portion; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

According to a fifth aspect of the embodiments of the present invention, there is provided a transmitting end, including: the first transceiver and the first processor, wherein the first processor is used for determining a specified part to be compressed in the first data packet; the first processor is further used for determining first information corresponding to the specified part according to the specified part; the first transceiver is configured to transmit a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

Optionally, the first transceiver is further configured to send compression indication information to the receiving end; the first transceiver is further configured to perform the step of sending the second data packet to the receiving end after receiving ACK information for acknowledging the compression indication information from the receiving end.

Optionally, the compression indication information includes one or more of:

second information indicating a correspondence relationship between all or a part of the header of the compressed first packet and a compression Index;

third information indicating a position of a partial header of the first packet to be compressed in the first packet header;

fourth information indicating an identification of a partial header of the first packet being compressed;

fifth information indicating a length of a partial header of the first packet that is compressed.

Optionally, the first processor is further configured to determine, through RRC signaling, whether to turn on or off a compression function of the designated portion; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

According to a sixth aspect of the embodiments of the present invention, there is provided a receiving end, including: a second transceiver and a second processor, wherein the second transceiver is configured to receive a second data packet from a transmitting end, and the second data packet includes: the other part except the appointed part in the first data packet and the first information; the second processor is used for obtaining a designated part corresponding to the first information according to the first information; the second processor is further configured to obtain the first data packet according to the designated portion and other portions of the first data packet except the designated portion.

Optionally, the second transceiver is further configured to receive compression indication information from the sending end, and send ACK information of the compression indication information to the sending end.

Optionally, the compression indication information includes one or more of:

fifth information indicating a length of a partial header of the first packet that has been compressed.

Optionally, the second processor is further configured to determine, through RRC signaling, whether to turn on or off a decompression function of the designated portion; wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

Optionally, the turning on or off of the decompression function includes any one of: the decompression function is turned on or off based on the granularity of the DRBs of the PDCP layer; the decompression function is turned on or off based on the granularity of the PDU session of the SDAP layer; the decompression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer; the decompression function is turned on or off based on the data granularity of the new protocol layer.

Optionally, the first information is used to indicate that FCS compression is performed, and the sixth information and the first information occupy 1bit in total, or the sixth information and the first information occupy 1bit respectively.

According to a seventh aspect of embodiments of the present invention, there is provided a communication apparatus including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, performs the steps of the method for transmitting data packets according to the first aspect or the steps of the method for receiving data packets according to the second aspect.

According to an eighth aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the packet transmission method according to the first aspect or implements the steps of the packet reception method according to the second aspect.

In the embodiment of the invention, the data packet in the field of industrial Internet of things can be compressed or decompressed, so that the overhead is saved, the transmission efficiency is improved, and the requirements of high reliability and low time delay of transmission are met.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a schematic diagram of a conventional ethernet header structure;

fig. 2 is a schematic structural diagram of a wireless communication system according to an embodiment of the present invention;

fig. 3 is a flowchart of a method for sending a data packet according to an embodiment of the present invention;

fig. 4 is a second flowchart of a data packet receiving method according to an embodiment of the present invention;

fig. 5 is a flowchart of a data packet transmission method according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a data packet according to an embodiment of the present invention;

fig. 7 is a second schematic diagram of a data packet structure according to an embodiment of the present invention;

fig. 8 is a third schematic diagram illustrating a structure of a data packet according to an embodiment of the present invention;

FIG. 9 is a fourth exemplary diagram illustrating a structure of a data packet according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a transmitting end according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a receiving end according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present invention;

fig. 13 is a second schematic structural diagram of a transmitting end according to an embodiment of the present invention;

fig. 14 is a second schematic structural diagram of a receiving end according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

To facilitate understanding of the embodiments of the present invention, the following two technical points are first introduced:

firstly, regarding the head compression:

the Robust Header Compression (ROHC) proposed in the RFC3095 protocol can be described as the interaction between two state machines, a Compression state machine and a decompression state machine. The compression gain is obtained by establishing contexts (contexts), i.e. a set of static and dynamic header fields, in the state machines at both ends of the link. The compression end and the decompression end must keep context synchronization during operation, and ROHC adds Cyclic Redundancy Check (CRC) to a compressed packet and can ensure that the context is updated timely and correctly through feedback (Acknowledgement, ACK)/Negative-Acknowledgement (NACK)).

The compression end has three states: IR (initialization refresh), FO (first level), SO (second level) states, the state of the compression side characterizing the degree of header compression that can be performed. The decompression side also has three states: NC (no context), SC (static context), FC (complete context), state characterization decompression end is able to decompress the corresponding data packet header, so that the state corresponds to the header compression performance. States can migrate from one state to another.

ROHC supports three modes of operation: u (unidirectional), O (bidirectional optimized), R (bidirectional reliable) modes. The three modes can be switched with each other. Each mode specifies the manner and frequency of some information interaction (e.g., whether more feedback is used, etc.). If the system can be switched to the reliable mode in time, feedback information of states, special domains and the like can be interacted more, the consistency of the contexts of the receiving party and the transmitting party can be ensured as much as possible, and therefore the correct probability of decompression under the high compression ratio state is improved.

The RFC3095 protocol provides for feeding back an ACK if the current packet is an update packet, i.e., an IR/DYN packet, when the CRC at the decompression end succeeds. The compression end and the decompression end initially work in a U mode, the decompression end is switched to an O mode or an R mode after successfully decompressing an update packet, ACK is fed back to the compression end, and the compression end is triggered to be switched to the O mode or the R mode. Later both ends will operate in O or R mode. And if the decompression end continuously monitors that the CRC is successfully checked in the R mode, carrying out state transition of NC- (SC) -FC, feeding back ACK (O), and carrying out conversion of the R-O mode. If the decompression end continuously monitors that the CRC fails in the O mode, the state is degraded, the O- (R) -mode conversion is carried out, and NACK (R) is fed back. And according to the feedback information, the compression end performs corresponding action operation so as to cooperate with the synchronization of the context state.

Second, regarding the ethernet header structure:

the header structure types of the data packets in the field of the industrial physical network are more diversified, taking an IEEE 802.3MAC frame structure as an example, see fig. 1, which illustrates the header structure and the composition of the frame, wherein, Preamble: a preamble; SFD (Start of FrameDelimiter): a frame start symbol; DESTINATION Address: a target address; source Address: a source address; Length/Type: a length type field; TAG Control Information: tag control information; MAC ClientLength/Type: MAC client length/type; MAC Client Data: a MAC client data field; fcs (framecheck sequence): and checking a sequence by using the frame.

It will be appreciated that fig. 1 is merely exemplary of one type of ethernet header, and that different header formats are possible depending on the ethernet protocol used. However, different header formats do not affect the implementation of the embodiments of the present invention, and the compression and decompression principles of other header formats are similar and will not be described herein.

Referring to fig. 2, an embodiment of the present invention provides a wireless communication system. As shown in fig. 2, the wireless communication system may include: a transmitting end 20 and a receiving end 21, the transmitting end 20 can communicate (transmit signaling or transmit data) with the receiving end 21. In practical applications, the connections between the above devices may be wireless connections, and fig. 2 is illustrated with solid lines for convenience and intuition of the connection relationships between the devices.

At least one of the sending end 20 and the receiving end 21 provided in the embodiment of the present invention may be a base station, which may be a commonly used base station, an evolved node base (eNB), or a network device (e.g., a next generation base station (gNB) or a Transmission and Reception Point (TRP)) in a Fifth generation mobile communication technology (5G) system.

At least one of the sending end 20 and the receiving end 21 provided in the embodiment of the present invention may also be a Mobile phone, a tablet Computer, a notebook Computer, an Ultra-Mobile Personal Computer (UMPC), a netbook, a vehicle-mounted device, an internet of things device, or a Personal Digital Assistant (PDA).

Referring to fig. 3, an embodiment of the present invention provides a data packet sending method, where an execution main body of the method is a sending end, and the method includes the following specific steps:

step 301: determining a designated portion of the first data packet to be compressed;

in the embodiment of the present invention, optionally, the designated portion is a full header or a partial header of the first packet; alternatively, the designated portion is the FCS of the first packet.

Step 302: determining first information corresponding to the designated part according to the designated part;

in the embodiment of the present invention, when the specified portion is the full header or the partial header of the first packet, the compression Index (Index) corresponding to the full header or the partial header of the first packet is determined according to the full header or the partial header of the first packet. Or when the specified part is the FCS of the first data packet, determining first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

Further, when the sending end is a network device on the core network side, after compressing all or part of the header of the first data packet, the compressed header is transmitted to the terminal through the RAN device. Wherein the compact Index may multiplex the existing Quality of Service Flow ID (QFI).

Step 303: sending a second data packet to a receiving end;

in an embodiment of the present invention, the second packet includes: the other part except the specified part in the first data packet and the first information. For example: the first data packet comprises a part A and a part B, the part A is determined as a designated part and compressed to obtain a second data packet, and the second data packet comprises: uncompressed part B, and first information indicating compressed part a.

Referring to fig. 4, an embodiment of the present invention provides a data packet sending method, where an execution subject of the method is a receiving end, and the method includes the following specific steps:

step 401: receiving a second data packet from the transmitting end;

in an embodiment of the present invention, the second packet includes: the other part except the appointed part in the first data packet and the first information; for example: the first data packet comprises a part A and a part B, the part A is determined as a designated part and compressed to obtain a second data packet, and the second data packet comprises: uncompressed part B, and first information indicating compressed part a.

Step 402: obtaining a designated part corresponding to the first information according to the first information;

in this embodiment of the present invention, when the first information is a compression Index, obtaining all headers or a part of headers of the first packet corresponding to the compression Index according to the compression Index;

when the first information indicates that the FCS compression is performed, the FCS of the first packet is obtained based on the first information.

Step 403: obtaining a first data packet according to the designated part and other parts of the first data packet except the designated part;

Referring to fig. 5, an embodiment of the present invention provides a method for transmitting a data packet, which includes the following specific steps:

step 501: the sending end and the receiving end determine the opening or closing of the compression function of the designated part through RRC signaling;

in the embodiment of the present invention, before determining the specified portion to be compressed in the first data packet, the sending end determines, through Radio Resource Control (RRC) signaling, whether to turn on or off the compression function of the specified portion. Accordingly, the receiving end determines the turning on or off of the compression function of the designated portion through RRC signaling before receiving the second packet from the transmitting end.

Wherein the designation section includes: a full header or a partial header of the first packet; and/or, the FCS of the first packet.

In the embodiment of the present invention, the RRC signaling starts the compression function based on the bearer granularity or the flow granularity, and when the RRC configures the compression function, it indicates that the compression function can be used.

There are two options at this time:

the first condition is as follows: after the RRC configuration is started, all data packets of the bearer or flow use a compression function;

case two: after the RRC configuration is started, part of the data packets of the bearer or the flow use the compression function, and other data packets continue uncompressed transmission, at this time, a header indication field is needed to distinguish between the two data packets, so that the receiving end can perform parsing according to a correct header structure.

Further, the header (e.g., ethernet header) compression and FCS compression functions may be located in a PDCP layer, an SDAP layer, or a new protocol layer at a Radio Access Network (RAN) side.

The turning on or off of the compression function includes any one of:

(1) the compression function is started or closed based on the granularity of a Data Resource Block (DRB) of a PDCP layer;

the starting or closing of the compression function is realized in the PDCP layer, and the compression function can be started based on the granularity of the DRB, that is, when the RRC configures the PDCP entity, the indication field displayed indicates whether the compression function of the DRB corresponding to the PDCP entity is started or closed.

(2) The compression function is started or closed based on the granularity of a Protocol Data Unit (PDU) session (session) of the SDAP layer;

the compression function is started or closed on an SDAP layer, the compression function can be started based on the PDScess corresponding to the SDAP, and when the RRC configures the SDAP entity, the RRC indicates whether the compression function of the special head of all data streams corresponding to the SDAP is started or closed by a displayed indication field;

(3) the compression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer;

the compression function is turned on or off based on some specific Quality of service (QoS) flows (flows) in the SDAP, and the RRC, when configuring the SDAP entity, indicates with the displayed indication fields that those QoS Flow identifiers (QoS Flow IDs, QFIs) of the SDAP correspond to data flows whose special header compression function is turned on and the rest are turned off by default.

(4) The compression function is turned on or off based on the data granularity of the new protocol layer;

the compression function is enabled or disabled at a new protocol layer depending on the granularity of data that the protocol layer can distinguish, and may be configured to be enabled or disabled by the RRC based on the granularity of PDU session, DRB, QFI, or even a particular special header format.

It should be noted that, the RRC configuration compression function is relatively semi-static to be turned on and off, and once turned on, it is proved that all data packets in the RRC configuration granularity must execute a header format to explicitly indicate information of header compression, and it is also possible to further indicate whether the data packet is header-compressed by a display bit of the data packet header, that is, the compressed data packet may be a header reading format, and the uncompressed data packet may be another header reading format. When the compression function is closed by RRC configuration, it is proved that no reading of header compression information is needed at this time, and the reading and processing are directly performed according to the existing uncompressed data packet format.

As described above, the header compression and the FCS compression may be configured simultaneously or separately.

Step 502: a sending end determines a specified part to be compressed in a first data packet;

When considering whether to perform header compression, it may also be considered to compress the FCS of the suffix of the first packet, including two embodiments:

the first implementation mode comprises the following steps: FCS compression is carried out while the header is compressed;

the second embodiment: the header compression and FCS may be performed independently.

The specific method of header compression is as follows:

only the static part of the header is compressed, the fixed static part of the header of the data packet of the same stream, namely the data packet with the same header, is removed at a compression end, and the compression Index of the stream or the header is indicated at the same time, the compression end informs the decompression end of the corresponding relation between the compression Index and the content of the specific compressed header, and the decompression end stores the corresponding relation. When the subsequent compression end sends the data packet, the static part of the header of the data packet with the established corresponding relation is removed, carries Index, and sends the data packet to the decompression end. After receiving the data packet, the decompressor finds the static part of the corresponding header by using Index, and restores the original header by supplementing the static part, thereby completing decompression.

For FCS compression, the FCS is the last 4 bytes formed by a certain calculation method on the original data frame to prevent transmission errors. However, in the transmission of the communication network, either the whole data packet is completely decoded incorrectly, or the whole data packet is transmitted correctly, and there is no case that the part of the correct data packet is incorrect, so the FCS has no great meaning in the transmission of the communication network, and can be removed in order to save resources.

The specific method of FCS compression is as follows:

when the sending end receives the first data packet, optionally, the FCS of the first data packet is verified according to a predetermined algorithm, and if the FCS verification error indicates that an error has occurred before the first data packet arrives at the RAN side, the first data packet may be deleted; if the FCS verifies correctly, processing may continue;

if the transmitting end is configured to compress the FCS, the last 4 bytes of FCS can be directly removed, and the rest part and first information are packaged into a second data packet and transmitted to the receiving end, wherein the first information indicates that the FCS compression is performed;

after the receiving end correctly receives the second data packet, the receiving end determines that the second data packet is a data packet with compressed FCS according to the first information, calculates the FCS according to a preset algorithm, adds the FCS to the end of the second data packet, obtains the first data packet and delivers the first data packet to a high layer.

Step 503: the sending end determines first information corresponding to the designated part according to the designated part;

Step 504: the sending end sends compression indication information to the receiving end;

the compression indication information refers to a corresponding relationship between the static header compression field and the compression indication Index. Very important context information for header compression and decompression operations that requires absolute synchronization between the compression side and the decompression side for proper compression and decompression operations.

Further, the compression indication information includes one or more of:

second information indicating a correspondence relationship between all or a part of the header of the compressed first packet and the compression Index;

third information indicating a position of a partial header of the compressed first packet in the first packet header;

fourth information indicating an identification of a partial header of the compressed first packet;

fifth information indicating a length of a partial header of the compressed first packet.

Optionally, the format of the first data packet or the second data packet is at least one of: a Packet Data Convergence Protocol (PDCP) Data Packet format; a format of a Service Discovery Application Profile (SDAP) packet; the format of the data packets of the new protocol layer.

Further, the compression indication information is obtained by at least one of:

(1) RRC signaling;

in the embodiment of the invention, the compression indication information is configured through RRC signaling;

when the data stream to be compressed and the header of the data packet are determined by comparison, the mapping relationship between the header field to be compressed and the compression indication Index can be configured through RRC signaling.

Illustratively, when an ethernet header needs to be fully compressed, the binding relationship between the entire content of the ethernet header and a specific compression indication Index is configured by RRC in advance, and the same configuration is performed at the compression end and the decompression end. Thus, when the subsequent compression end receives the data packet of the corresponding header, the ethernet header of the data packet is directly removed, and the Index is carried in the data packet. The uncompressing end receives the compressed data packet, finds the corresponding Ethernet head according to the carried Index, restores the Ethernet head to the fixed position of the corresponding data packet, namely completes the uncompressing operation, and submits the data packet to a high layer for normal processing.

It should be noted that if the PDCP layer carries the compression indication Index, the Index is carried in the PDCP data PDUheader, and after removing the PDCP header, according to whether there is an SDAP header inside, if there is an SDAP header, the SDAPheader is skipped, and then the ethernet header is placed where the ethernet header should be placed inside, and if there is no SDAP header, the ethernet header should be located at the outermost part of the PDCP SDU. Or in a complicated case, the ethernet header and the headers of other PDCP SDUs may have a further inclusion or included relationship, and the same processing may be performed at the compression end and the decompression end through a configuration or a predetermined form, where the compression end removes which header, and the decompression end needs to install the header corresponding to the Index at the same location.

Further, the ethernet header is not compressed entirely, only a portion of the static portion is compressed, and the remaining portion remains transmitted. Then, when configuring the corresponding relationship between the compressed part header and the Index, it is also necessary to configure the relative position of the compressed part in the original ethernet header, for example, the original ethernet header is 40 bytes long, where 0-7 (first 8) bytes need to be reserved, 8-19 (total 12) bytes of static unchanged parts can be compressed, 20-25 (total 6) bytes need to be reserved, and 26-39 (total 14) bytes of static unchanged parts can be compressed, and these related contents can be configured in advance and correspond to the Index. The compression end retains 0-7 bytes, removes 8-19 bytes, retains 20-25 bytes, removes 26-39 bytes, and carries Index when processing. And the decompression end receives the data packet, acquires the index, searches the header compression information corresponding to the index, inserts the preconfigured 8-19 bytes after 0-7 bytes, connects 20-25 bytes in the packet, and then inserts the preconfigured 26-39 bytes to form a complete 40-byte header, thereby completing the decompression operation.

(2) PDU of the user plane;

in the embodiment of the invention, the control PDU through a User Plane (UP) carries compression indication information;

the indication information is compressed through RRC configuration, the content of the header of the data packet needs to be known in advance, and subsequently, if a data packet with a new header arrives, an RRC reconfiguration process needs to be performed, which is too large in delay and overhead, and low in flexibility. Therefore, the configuration and synchronization process of the compression indication information can be carried out by adopting the process of the user plane, and the efficiency is improved.

It should be noted that, the following description is made in terms of the format of PDCP data packet, but when other SDAP data packets or the format of data packet of new protocol layer is used, the principle and the content of the carried information are similar, and the arrangement of the header structure is slightly different, which does not affect the core content of the present invention.

Referring to fig. 6, a special type of PDCP control PDU is designed to inform exclusively of the mapping relationship between Ethernet (Ethernet) static header and Index.

Wherein the D/C field is used to indicate whether this is data or control PDU; the PDU type is a control PDU type, and the PDU type needs to be indicated as compression indication information; the Header index is a compression indication and the Header is the compressed Ethernet Header.

The Header Index in fig. 6 is only an example, and the Header Index may be a value specified by a standard or an RRC signaling configuration according to a maximum number of different Ethernet headers that may be included in one bearer. However, the whole byte arrangement of the PDCP header structure should be considered, for example, a 4-bit header index may occupy the existing 4R bits, or 8 bits, 12 bits, 16 bits, etc. If the Ethernet header is compressed entirely or only one large area is compressed, then there is only one header field and this field is located at the end of the Control PDU, no length indication is needed, and after reading the previous field, the following part is all header fields. If the compressed header field is more than one and variable in length, a header length indication is also required.

Further, if the Ethernet header still has a residual uncompressed part, if the resolution cannot be clearly understood, or how the uncompressed part and the compressed part are combined to form an ambiguity, the Ethernet header may further carry related indication information. For example, in the above example, the Header index is followed by a combination of Header offset + Header + Header length, where the offset field indicates the location of the compressed Header in the original ethernet Header, the Header is the particular ethernet Header portion that is compressed away, and the length is the length of the compressed Header.

A sending step:

step 1: before sending the second data packet, the sending end needs to send a control PDU to inform the Ethernet header how to compress and the mapping relation between the Ethernet header and the index;

step 2: after the Control PDU is successfully sent, a data PDU data packet after the Ethernet header is compressed can be sent, wherein the data PDU data packet carries the index established before, and the corresponding static part of the Ethernet header is removed;

and step 3: if a new Ethernet header data stream arrives, repeating the

steps

1 and 2 to establish mapping and compressing;

and 4, step 4: if the data stream of the Index is finished and the Index does not exist any more in the following, the Index can be continuously distributed to the newly arrived data stream, and the compression mapping relationship is reestablished.

A receiving step:

step 1: firstly, receiving a control PDU and storing a mapping relation between an Ethernet header and an index;

step 2: for the Data PDU received subsequently, the mapping relation table is searched by reading the Index, and the recovery of the Ethernet header head is carried out;

and step 3: and if the mapping relation between the Index and the Ethernet header is updated by the transmitting end, decompressing by using the latest mapping relation.

It can be seen from the above steps that the sending end needs to ensure that the receiving end correctly receives the control pdu establishing the mapping relationship first, otherwise, the subsequent data packet cannot be correctly decompressed. Optionally, after the control PDU is successfully transmitted and an explicit ACK is received from the opposite end, the transmission of the compressed data packet is started, and during the waiting process, the data may be suspended, or an uncompressed data packet may be transmitted.

Referring to fig. 7, compressed packets and uncompressed packets, an indication is required to be displayed.

The C/N field is used for displaying whether the packet is a compressed packet or a non-compressed packet, so as to determine whether a Header Index field exists.

In the embodiment of the present invention, FCS compression may also be performed, and since the FCS does not need to establish a mapping relationship in advance, the Control PDU does not need to include FCS compression information, but the C/N field of the data packet may indicate whether FCS compression is performed or not at the same time, or a separate F/N field may indicate whether FCS compression is performed or not.

(3) A user plane mapping notification PDU;

in the embodiment of the invention, the UP header only PDU carries the compression indication information;

optionally, the user plane mapping notification PDU includes a first Sequence Number (SN), and the first SN and a second SN of the second packet are spatially allocated by the same SN Sequence.

The advantage of this method is that the PDU of the notification map also has SN, and can be ordered, so that waiting is not needed, and the mapping relationship notification and the used precedence relationship can be strictly controlled.

Referring to FIG. 8, where M/N indicates whether this is a special format for mapping notification, C/N is used to indicate whether the packet is compressed.

If the M/N shows that this is a mapping notification format, then the Header index field and the subsequent Ethernet Header field will be followed, even Header offset + Header + Header length as shown in the above example. If the format is not mapping notification format, the data field is carried normally, the C/N field shows whether the data field is compressed or not, if the data field is not compressed, no Index exists, and if the data field is compressed, the Index is carried.

A sending step:

step 1: before sending the second data packet, the sending end needs to send mapping notification PDU first, to notify the Ethernet header how to compress and the mapping relation between the Ethernet header and the index;

step 2: after the mapping notification PDU is sent, a data PDU data packet after the Ethernet header compression can be sent, wherein the data PDU data packet carries the previously established index, and the corresponding static part of the Ethernet header is removed;

and step 3: if a new Ethernet header data stream arrives, repeating the

steps

1 and 2 to establish mapping and compressing;

and 4, step 4: if the data stream of the Index is finished and there is no more Index, the Index can be continuously distributed to the newly arrived data stream, and the compression mapping relationship is reestablished.

A receiving step:

step 1: receiving a mapping notification PDU (protocol data Unit) first, storing a mapping relation between an Ethernet header and an index, and carrying SN (sequence number) because the mapping notification PDU also carries the SN, so that reordering is required according to the SN even if a subsequent data packet is received first, processing the mapping notification PDU with a small SN sequence number first, and then processing the subsequent data PDU;

(4) User plane data PDU

In the embodiment of the invention, the UP data PDU carries the compression indication information;

the advantage of this approach is also that the order is controllable and does not require a separate notification format, which can be merged with the data PDUs.

Referring to fig. 9, a Header Length field is added, mainly to deal with the fact that there may be multiple possible lengths of the compressed Header, and to correctly decode, the indication Length needs to be displayed. Further, a combination of header offset + header + header length may be carried to indicate a complicated compression method.

The specific sending and receiving steps can refer to the above description of sending and receiving steps carrying the compression indication information through the UP header only PDU.

Step 505: the sending end receives ACK information of the compression indication information from the receiving end;

in the embodiment of the invention, after receiving the compression indication information, the receiving end sends ACK information to the sending end.

Step 506: the sending end sends a second data packet to the receiving end;

Optionally, the second data packet further includes: sixth information for explicitly or implicitly indicating that the second packet is a compressed packet or for explicitly or implicitly indicating that the second packet is not a compressed packet.

Further, the first information is used to indicate that FCS compression is performed, and the sixth information is used to explicitly or implicitly indicate that the second packet is a compressed packet, the sixth information and the first information occupy 1bit together, or the sixth information and the first information occupy 1bit respectively.

Illustratively, if RRC configures the compression function to be turned on, there are two ways to implement:

the first method is as follows: after the start, all the packets are subjected to special header compression, which is equivalent to defining a type of packet format for performing special header compression in addition to the original packet format before the special header compression is not introduced, for example, the header needs to carry a compression Index and the like. Once the configuration is opened, the sending end and the receiving end process all data packets by using a special format.

The second method comprises the following steps: after the start, part of the data packets are compressed, and the rest of the data packets are not compressed. The method is equivalent to firstly introducing a 1-bit indicating bit in a header structure to indicate whether the packet is a compressed packet or an uncompressed packet, and processing the compressed packet according to a compressed packet format if the packet is the compressed packet, or processing the uncompressed packet according to an uncompressed packet format if the packet is the uncompressed packet. If header compression and FCS compression are indicated separately, at least 2 bits are required for the indication, respectively.

If the RRC configures the compression function to be turned off, it is sufficient that the header and packet are completely processed according to a format before the special header compression is introduced.

Step 507: the receiving end obtains a designated part corresponding to the first information according to the first information;

Step 508: the receiving end obtains a first data packet according to the designated part and other parts of the first data packet except the designated part;

referring to fig. 10, an embodiment of the present invention provides a transmitting end 1000, including:

a first determining module 1001, configured to determine a specific portion to be compressed in a first data packet;

a second determining module 1002, configured to determine, according to the specified portion, first information corresponding to the specified portion;

a first sending module 1003, configured to send a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

Optionally, the specified part is a whole header or a part of a header of the first data packet;

accordingly, the second determining module 1002 is further configured to: and determining a compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

Optionally, the sending end 1000 further includes:

a second sending module 1004, configured to send compression indication information to the receiving end;

the first sending module is further configured to execute the step of sending the second data packet to the receiving end after receiving ACK information for acknowledging the compression indication information from the receiving end.

Optionally, the compression indication information includes one or more of:

Optionally, the compression indication information is obtained by at least one of:

radio resource control, RRC, signaling;

a control protocol data unit PDU of a user plane;

a user plane mapping notification PDU;

user plane data PDU.

Optionally, the designated portion is a frame check sequence FCS of the first data packet;

accordingly, the second determining module 1002 is further configured to: and determining the first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

Optionally, the sending end 1000 further includes:

a third determining module 905, configured to determine, through RRC signaling, whether to turn on or off a compression function of the designated portion;

wherein the designation section includes: a full header or a partial header of the first packet; and/or, an FCS of the first packet.

Optionally, the turning on or off of the compression function includes any one of:

the compression function is started or closed based on the granularity of data bearing DRB of a packet data convergence protocol PDCP layer;

the compression function is started or closed based on the granularity of a Protocol Data Unit (PDU) session of a service discovery application Specification (SDAP) layer;

the compression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer;

the compression function is turned on or off based on the data granularity of the new protocol layer.

Optionally, the format of the first data packet or the second data packet is at least one of:

the format of the PDCP data packet;

the format of the SDAP packet;

the format of the data packets of the new protocol layer.

Referring to fig. 11, an embodiment of the present invention provides a receiving end 1100, including:

a first receiving module 1001, configured to receive a second data packet from a transmitting end, where the second data packet includes: the other part except the appointed part in the first data packet and the first information;

a first obtaining module 1102, configured to obtain, according to the first information, a specified portion corresponding to the first information;

a second obtaining module 1103, configured to obtain the first data packet according to the specified portion and other portions of the first data packet except for the specified portion.

Optionally, the first information is a compression Index;

accordingly, the first obtaining module 1102 is further configured to: and obtaining all or part of the header of the first data packet corresponding to the compression Index according to the compression Index.

Optionally, the receiving end 1100 further includes:

a second receiving module 1001, configured to receive compression indication information from the sending end, and send ACK information of the compression indication information to the sending end.

Optionally, the compression indication information includes one or more of:

radio resource control, RRC, signaling;

a control protocol data unit PDU of a user plane;

a user plane mapping notification PDU;

user plane data PDU.

Optionally, the first information is used to indicate that FCS compression is performed;

correspondingly, the obtaining of the designated part corresponding to the first information according to the first information includes:

determining the FCS of the first data packet according to the first information.

Optionally, the receiving end 1100 further includes:

a fourth determining module 1104, configured to determine, through RRC signaling, whether to turn on or off a decompression function of the designated portion;

Optionally, the turning on or off of the decompression function includes any one of:

the decompression function is started or closed based on the granularity of data bearing DRB of a packet data convergence protocol PDCP layer;

the decompression function is started or closed based on the granularity of a Protocol Data Unit (PDU) session of a service discovery application Specification (SDAP) layer;

the decompression function is turned on or off based on the granularity of the QoS Flow of the SDAP layer;

the decompression function is turned on or off based on the data granularity of the new protocol layer.

Referring to fig. 12, an embodiment of the present invention provides a communication apparatus 1200, including: a processor 1201, a transceiver 1202, a memory 1203 and a bus interface.

Among other things, the processor 121201 may be responsible for managing the bus architecture and general processing. The memory 1203 may store data used by the processor 1201 in performing operations.

In this embodiment of the present invention, the communication device 1200 may further include: a program stored in the memory 1203 and executable on the processor 1201, when executed by the processor 1201, performs the steps of the methods provided by embodiments of the present invention.

In fig. 12, the bus architecture may include any number of interconnected buses and bridges, with various circuits linking one or more processors, represented by the processor 1201, and memory, represented by the memory 1203. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further in connection with embodiments of the present invention. The bus interface provides an interface. The transceiver 1202 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

Referring to fig. 13, an embodiment of the present invention provides a transmitting end 1300, including: a first transceiver 1301 and a first processor 1302;

the first processor 1302 is configured to determine a specific portion to be compressed in a first data packet;

the first processor 1302 is further configured to determine, according to the specified portion, first information corresponding to the specified portion;

the first transceiver 1301 is configured to transmit a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

correspondingly, the determining the first information corresponding to the designated part according to the designated part comprises:

and determining the compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

Optionally, the first transceiver 1301 is further configured to send compression indication information to the receiving end;

the first transceiver 1301 is further configured to perform the step of sending the second data packet to the receiving end after receiving ACK information of the compression indication information from the receiving end.

Optionally, the compression indication information includes one or more of:

RRC signaling;

PDU of the user plane;

a user plane mapping notification PDU;

user plane data PDU.

Optionally, the user plane mapping notification PDU includes a first SN, and the first SN and a second SN of the second packet are allocated by the same SN sequence space.

and determining the first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

Optionally, the first processor 1302 is further configured to determine, through RRC signaling, whether to turn on or off a compression function of the designated portion;

the compression function is turned on or off based on the granularity of the DRBs of the PDCP layer;

the compression function is turned on or off based on the granularity of the PDU session of the SDAP layer;

the format of the PDCP data packet;

the format of the SDAP packet;

the format of the data packets of the new protocol layer.

Referring to fig. 14, an embodiment of the present invention provides a receiving end 1400, including: a second transceiver 1401 and a second processor 1402;

the second transceiver 1401 is configured to receive a second data packet from a transmitting end, where the second data packet includes: the other part except the appointed part in the first data packet and the first information;

the second processor 1402, configured to obtain, according to the first information, a specified portion corresponding to the first information;

the second processor 1402 is further configured to obtain the first data packet according to the designated portion and other portions of the first data packet except the designated portion.

Optionally, the first information is a compression Index;

and obtaining all or part of the header of the first data packet corresponding to the compression Index according to the compression Index.

Optionally, the second transceiver 1401 is further configured to receive compression indication information from the transmitting end, and send ACK information of the compression indication information to the transmitting end.

Optionally, the compression indication information includes one or more of:

RRC signaling;

PDU of the user plane;

a user plane mapping notification PDU;

user plane data PDU.

Optionally, the second processor 1402 is further configured to determine, through RRC signaling, whether to turn on or off the decompression function of the designated portion;

the decompression function is turned on or off based on the granularity of the DRBs of the PDCP layer;

the decompression function is turned on or off based on the granularity of the PDU session of the SDAP layer;

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the processes of the method embodiments, and can achieve the same technical effects, and in order to avoid repetition, the details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable hard disk, a compact disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

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, embodiments of 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, embodiments of 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, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are 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 embodiments of the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the embodiments 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 encompass such modifications and variations.

Claims

1. A data packet sending method is applied to a sending end, and is characterized by comprising the following steps:

determining a designated portion of the first data packet to be compressed;

according to the designated part, determining first information corresponding to the designated part;

sending a second data packet to a receiving end, wherein the second data packet comprises: the other part except the specified part in the first data packet and the first information.

2. The method of claim 1,

the specified part is the whole head or partial head of the first data packet;

and determining a compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

3. The method of claim 2, wherein before said sending the second packet to the receiving end, the method further comprises:

sending compression indication information to the receiving end;

and after receiving ACK information for confirming the compression indication information from the receiving end, performing the step of transmitting the second packet to the receiving end.

4. The method of claim 3, wherein the compression indication information comprises one or more of:

5. The method of claim 3, wherein the compression indication information is obtained by at least one of:

radio resource control, RRC, signaling;

a control protocol data unit PDU of a user plane;

a user plane mapping notification PDU;

user plane data PDU.

6. The method of claim 5, wherein the user plane map notify PDU includes a first Sequence Number (SN), and wherein the first SN and a second SN of the second packet are spatially allocated by a same SN sequence.

7. The method of claim 1,

the designated part is a frame check sequence FCS of the first data packet;

8. The method of claim 1, wherein prior to said determining the specified portion of the first packet to be compressed, the method further comprises:

determining the on or off of the compression function of the designated part through RRC signaling;

9. The method of claim 8, wherein the turning on or off of the compression function comprises any one of:

10. The method according to any one of claims 2 or 7, wherein the second data packet further comprises: sixth information for explicitly or implicitly indicating that the second data packet is a compressed data packet or for explicitly or implicitly indicating that the second data packet is not a compressed data packet.

11. The method of claim 10, wherein the first information is used to indicate that FCS compression is performed, and wherein the sixth information is used to explicitly or implicitly indicate that the second packet is a compressed packet, the sixth information and the first information occupy 1bit together, or the sixth information and the first information occupy 1bit respectively.

12. The method of claim 1, wherein the format of the first packet or the second packet is at least one of:

the format of the PDCP data packet;

the format of the SDAP packet;

the format of the data packets of the new protocol layer.

13. The method according to claim 1, wherein the transmitting end is a network device on a radio access network side, and the receiving end is a terminal; or the sending end is network equipment on the core network side, and the receiving end is a terminal; or the sending end is a terminal, and the receiving end is network equipment on a wireless access network side or network equipment on a core network side.

14. A data packet receiving method is applied to a receiving end, and is characterized by comprising the following steps:

receiving a second data packet from a sender, the second data packet comprising: the other part except the appointed part in the first data packet and the first information;

obtaining a designated part corresponding to the first information according to the first information;

and obtaining the first data packet according to the specified part and other parts of the first data packet except the specified part.

15. The method of claim 14,

the first information is compression Index;

16. The method of claim 15, wherein before receiving the second packet from the sender, the method further comprises:

and receiving compression indication information from the sending end, and sending ACK (acknowledgement character) information of the compression indication information to the sending end.

17. The method of claim 16, wherein the compression indication information comprises one or more of:

18. The method of claim 16, wherein the compression indication information is obtained by at least one of:

radio resource control, RRC, signaling;

a control protocol data unit PDU of a user plane;

a user plane mapping notification PDU;

user plane data PDU.

19. The method of claim 14,

the first information is used for indicating that FCS compression is performed;

20. The method of claim 14, wherein before receiving the second packet from the sender, the method further comprises:

determining the opening or closing of the decompression function of the designated part through RRC signaling;

21. The method of claim 20, wherein the turning on or off of the decompression function comprises any one of:

22. The method according to claim 15 or 19, wherein the second data packet further comprises: sixth information for explicitly or implicitly indicating that the second data packet is a compressed data packet or for explicitly or implicitly indicating that the second data packet is not a compressed data packet.

23. The method of claim 22, wherein the first information is used to indicate that FCS compression is performed, and wherein the sixth information and the first information occupy 1bit, or wherein the sixth information and the first information occupy 1bit, respectively.

24. The method of claim 14, wherein the sending end is a network device on a radio access network side, and the receiving end is a terminal; or the sending end is network equipment on the core network side, and the receiving end is a terminal; or the sending end is a terminal, and the receiving end is network equipment on a wireless access network side or network equipment on a core network side.

25. A transmitting end, comprising:

the first determining module is used for determining a specified part to be compressed in the first data packet;

the second determining module is used for determining first information corresponding to the specified part according to the specified part;

a first sending module, configured to send a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

26. The transmitting end according to claim 25,

the specified part is the whole head or partial head of the first data packet;

accordingly, the second determining module is further configured to: and determining a compression Index corresponding to all or part of the header of the first data packet according to all or part of the header of the first data packet.

27. The transmitting end according to claim 25,

the designated part is a frame check sequence FCS of the first data packet;

accordingly, the second determining module is further configured to: and determining the first information according to the FCS of the first data packet, wherein the first information is used for indicating that FCS compression is performed.

28. A receiving end, comprising:

a first receiving module, configured to receive a second data packet from a sending end, where the second data packet includes: the other part except the appointed part in the first data packet and the first information;

the first acquisition module is used for acquiring a designated part corresponding to the first information according to the first information;

and the second acquisition module is used for acquiring the first data packet according to the specified part and other parts of the first data packet except the specified part.

29. The receiving end according to claim 28,

the first information is compression Index;

accordingly, the first obtaining module is further configured to: and obtaining all or part of the header of the first data packet corresponding to the compression Index according to the compression Index.

30. The receiving end according to claim 28,

the first information is used for indicating that FCS compression is performed;

accordingly, the first obtaining module is further configured to: determining the FCS of the first data packet according to the first information.

31. A transmitting end, comprising: a first transceiver and a first processor, wherein,

the first processor is used for determining a specified part to be compressed in the first data packet;

the first processor is further used for determining first information corresponding to the specified part according to the specified part;

the first transceiver is configured to transmit a second data packet to a receiving end, where the second data packet includes: the other part except the specified part in the first data packet and the first information.

32. The transmitting end according to claim 31,

the specified part is the whole head or partial head of the first data packet;

33. The transmitting end according to claim 34,

the first transceiver is further configured to send compression indication information to the receiving end;

the first transceiver is further configured to perform the step of sending the second packet to the receiving end after receiving ACK information of the compression indication information from the receiving end.

34. The transmitting end according to claim 33, wherein the compression indication information includes one or more of the following:

35. The transmitting end according to claim 33, wherein the compression indication information is obtained by at least one of:

RRC signaling;

PDU of the user plane;

a user plane mapping notification PDU;

user plane data PDU.

36. The transmitting end of claim 35, wherein the user plane map notification PDU comprises a first SN, and wherein the first SN and a second SN of the second packet are spatially allocated by a same SN sequence.

37. The transmitting end according to claim 31,

the designated part is a frame check sequence FCS of the first data packet;

38. The transmitting end according to claim 31,

the first processor is further configured to determine, through RRC signaling, whether to turn on or off a compression function of the designated portion;

39. The sender according to claim 38, wherein the turning on or off of the compression function comprises any one of:

40. The transmitting end according to any one of claims 32 or 37, wherein the second data packet further comprises: sixth information for explicitly or implicitly indicating that the second data packet is a compressed data packet or for explicitly or implicitly indicating that the second data packet is not a compressed data packet.

41. The transmitting end of claim 40, wherein the first information is used to indicate that FCS compression is performed, and wherein the sixth information is used to explicitly or implicitly indicate that the second packet is a compressed packet, and the sixth information and the first information occupy 1bit in total, or the sixth information and the first information occupy 1bit respectively.

42. The sender of claim 31, wherein the format of the first data packet or the second data packet is at least one of:

the format of the PDCP data packet;

the format of the SDAP packet;

the format of the data packets of the new protocol layer.

43. The transmitting end according to claim 31, wherein the transmitting end is a network device on a radio access network side, and the receiving end is a terminal; or the sending end is network equipment on the core network side, and the receiving end is a terminal; or the sending end is a terminal, and the receiving end is network equipment on a wireless access network side or network equipment on a core network side.

44. A receiving end, comprising: a second transceiver and a second processor, wherein,

the second transceiver is configured to receive a second data packet from a transmitting end, where the second data packet includes: the other part except the appointed part in the first data packet and the first information;

the second processor is used for obtaining a designated part corresponding to the first information according to the first information;

the second processor is further configured to obtain the first data packet according to the designated portion and other portions of the first data packet except the designated portion.

45. The receiving end according to claim 44,

the first information is compression Index;

46. The receiving end according to claim 45,

the second transceiver is further configured to receive compression indication information from the sending end, and send ACK information of the compression indication information to the sending end.

47. The receiving end according to claim 46, wherein the compression indication information comprises one or more of the following:

48. The receiving end according to claim 46, wherein the compression indication information is obtained by at least one of:

RRC signaling;

PDU of the user plane;

a user plane mapping notification PDU;

user plane data PDU.

49. The receiving end according to claim 44,

the first information is used for indicating that FCS compression is performed;

50. The receiving end according to claim 44,

the second processor is further configured to determine, through RRC signaling, whether to turn on or off a decompression function of the designated portion;

51. The receiving end of claim 50, wherein the turning on or off of the decompression function comprises any one of:

52. The receiver according to claim 45 or 49, wherein the second data packet further comprises: sixth information for explicitly or implicitly indicating that the second data packet is a compressed data packet or for explicitly or implicitly indicating that the second data packet is not a compressed data packet.

53. The receiving end of claim 52, wherein the first information is used to indicate that FCS compression is performed, and the sixth information and the first information occupy 1bit, or the sixth information and the first information occupy 1bit, respectively.

54. The receiving end according to claim 44, wherein the transmitting end is a network device on a radio access network side, and the receiving end is a terminal; or the sending end is network equipment on the core network side, and the receiving end is a terminal; or the sending end is a terminal, and the receiving end is network equipment on a wireless access network side or network equipment on a core network side.

55. A communication device, comprising: processor, memory and a program stored on the memory and executable on the processor, which program when executed by the processor performs the steps of the method for transmitting data packets according to any of claims 1 to 13 or performs the steps of the method for receiving data packets according to any of claims 14 to 24.

56. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the data packet transmission method according to one of claims 1 to 13 or the steps of the data packet reception method according to one of claims 14 to 24.