CN118055446A - Robust header compression and decompression method, system and communication terminal - Google Patents
Robust header compression and decompression method, system and communication terminal Download PDFInfo
- Publication number
- CN118055446A CN118055446A CN202410444531.3A CN202410444531A CN118055446A CN 118055446 A CN118055446 A CN 118055446A CN 202410444531 A CN202410444531 A CN 202410444531A CN 118055446 A CN118055446 A CN 118055446A
- Authority
- CN
- China
- Prior art keywords
- header compression
- robust header
- packet
- communication terminal
- cell
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000006835 compression Effects 0.000 title claims abstract description 227
- 238000007906 compression Methods 0.000 title claims abstract description 227
- 238000004891 communication Methods 0.000 title claims abstract description 143
- 230000006837 decompression Effects 0.000 title claims abstract description 89
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000008569 process Effects 0.000 claims abstract description 21
- 230000003111 delayed effect Effects 0.000 claims description 10
- 230000001934 delay Effects 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 2
- 230000005540 biological transmission Effects 0.000 description 8
- 230000003068 static effect Effects 0.000 description 4
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 3
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/04—Protocols for data compression, e.g. ROHC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a robust header compression and decompression method, a system and a communication terminal, wherein the method comprises the following steps: in the process of executing cell switching or cell reconstruction by the communication terminal, after resetting the packet data convergence protocol layer, delaying reconstruction of the robust header compression context; after the communication terminal performs cell switching or cell reconstruction, judging whether the type of the received first robust header compression packet is an initialized refreshing data packet or not; when the type of the first robust header compression packet is an initialized refreshing data packet, executing the robust header compression context reconstruction and then re-executing the robust header compression decompression flow; and continuing to execute the robust header compression and decompression flow when the type of the first robust header compression packet is the non-initialized refreshing data packet. The invention can avoid the problem of decompression failure of a large number of continuous compression packets for a long time and improve the communication service quality.
Description
Technical Field
The present invention relates to the field of mobile communications technologies, and in particular, to a robust header compression and decompression method, system, and communication terminal.
Background
When the 5G/LTE terminal uses the robust header compression scheme in the data transmission process, if the base station does not configure ROHCContinue to indicate that the transmission of the data packet is not completed yet and needs a subsequent data packet to continue to transmit complete information, the currently-camping original cell copies the data packet received from the core network, one part of the data packet is sent to the terminal after being continuously compressed by ROHC, the other part of the data packet is directly sent to the target cell, and the target cell sends the data packet to the terminal after being compressed by ROHC. After the terminal switches or rebuilds to the target cell, it will send the packet data convergence protocol layer status report to indicate which data packets have been successfully received, and after the target cell receives the packet data convergence protocol layer status report, it will discard the data packets that the terminal has acknowledged to be received, and resend the data packets that have not been received. When retransmitting the data packet, the initialization refreshing data packet may be lost after being acknowledged by the packet data convergence protocol layer, so the first compression packet issued is the non-initialization refreshing data packet, at this time, the communication terminal has already reset the robust header compression and the context, and when the initialization refreshing data packet is not received to reconstruct the robust header compression context, decompression cannot be performed, which may cause a problem of decompression failure of a long-time and large number of continuous compression packets.
Based on the technical problems, the application provides a robust header compression and decompression method, which can increase the fault tolerance rate of the robust header compression and decompression of a communication terminal under the condition of not affecting the existing flow.
Disclosure of Invention
In order to solve the technical problem that the current robust header compression scheme can fail in decompression of a large number of continuous compression packets for a long time, the invention provides a robust header compression and decompression method, a robust header compression and decompression system and a communication terminal, and the specific technical scheme is as follows:
The invention provides a robust header compression and decompression method, which is applied to a communication terminal and comprises the following steps:
in the process that the communication terminal executes cell switching or cell reconstruction, the packet data convergence protocol layer is reset and then the reconstruction of the robust header compression context is delayed;
after the communication terminal performs cell switching or cell reconstruction, judging whether the type of the received first robust header compression packet is an initialized refreshing data packet or not;
When the type of the first robust header compression packet is the initialization refreshing data packet, executing the robust header compression and decompression flow after reconstructing the robust header compression context;
And when the type of the first robust header compression packet is a non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow.
The robust header compression and decompression method provided by the invention can avoid the problem that data buffered in the base station side RLC layer cannot be decompressed by delaying the operation of reconstructing the robust header compression context in the cell switching or reconstruction process, and simultaneously avoid the problem that the uninitialized refreshing data packet initially issued by the base station cannot be decompressed, thereby increasing the fault tolerance rate of the robust header compression and decompression of the communication terminal, avoiding the problem of decompression failure of a large number of continuous compression packets for a long time and improving the communication service quality.
In some embodiments, a robust header compression decompression method, after the delay rebuilding the robust header compression context, further includes the steps of:
Setting a first delay flag characterizing a delayed reconstruction robustness header compression context;
after the communication terminal performs cell switching or cell reconstruction, judging whether the type of the first robust header compression packet is the initialization refreshing data packet or not and whether the first delay mark is received or not;
executing the robust header compression and decompression flow again after executing the reconstructed robust header compression context when the type of the first robust header compression packet is the initialized refreshing data packet and the first delay mark is received;
When the type of the first robust header compression packet is the initialization refreshing data packet and the first delay mark is not received, continuing to execute the robust header compression and decompression flow;
And when the type of the first robust header compression packet is a non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow.
By setting the delay mark, the robust header compression and decompression method provided by the invention avoids the situation that an initialization refreshing data packet is received at the moment in the process of reconstructing the robust header compression context only according to the robust header compression context information in the data transmission process such as static context updating and the like, and the robust header compression and decompression fault tolerance rate can be increased by adding the delay mark without executing the robust header compression context reconstruction at the moment, so that the problem of continuous compression and decompression failure is avoided.
In some embodiments, the determining whether the first robust header compression packet type is the initialization refresh packet and whether the first delay flag is received specifically includes:
When the type of the first robust header compression packet is the initialized refreshing data packet and the first delay flag is received, executing the robust header compression and decompression flow again after the robust header compression context is rebuilt, and updating the first delay flag to be a second delay flag;
and when the type of the first robust header compression packet is a non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow and updating the first delay flag to be the second delay flag.
In some embodiments, the first delay flag is set to resetContextDelay = TRUE;
the second delay flag is set to resetContextDelay =false.
In some embodiments, according to another implementation manner of the present invention, the present invention further provides a robust header compression and decompression system, which is applied to a communication system including a communication terminal, an original cell, and a target cell, and includes:
The communication terminal sends a cell switching instruction or a cell reconstruction instruction to the original cell, and delays reconstruction of the robust header compression context after resetting the packet data convergence protocol layer;
The target cell sends a robustness header compression packet to the communication terminal after the communication terminal performs cell switching or cell reconstruction;
The communication terminal judges whether the type of the received head compressed packet with the robustness is an initialized refreshing data packet;
When the type of the first robust header compression packet is the initialization refreshing data packet, the communication terminal executes the robust header compression and decompression flow again after rebuilding the robust header compression context;
And when the type of the first robust header compression packet is a non-initialized refreshing data packet, the communication terminal continuously executes the robust header compression and decompression flow.
In some embodiments, after the resetting the packet data convergence protocol layer and delaying the reconstructing of the robust header compression context, the target cell further includes, before the communication terminal performs cell switching or after cell reconstructing is completed, transmitting a robust header compression packet to the communication terminal:
the communication terminal accesses the target cell and completes the reconfiguration of the special radio bearer parameters;
And the communication terminal sends a packet data convergence protocol layer state report to the target cell.
In some embodiments, after the communication terminal sends a cell handover instruction or a cell reestablishment instruction to the original cell, before the communication terminal accesses the target cell and completes reconfiguration of the dedicated radio bearer parameters, the method further includes:
The original cell copies and receives a core network data packet, synchronously transmits the core network data packet to the target cell, and transmits the core network data packet to the communication terminal after being compressed by a robustness header;
the target cell compresses the core network data packet through a robustness header and then sends the core network data packet to the communication terminal;
after the communication terminal sends the packet data convergence protocol layer state report to the target cell, the communication terminal further comprises:
Discarding the robust header compressed packet received by the communication terminal according to the packet data convergence protocol layer state report by the target cell;
And the target cell retransmits the robust header compression packet which is not received by the communication terminal to the communication terminal.
In some embodiments, after the communication terminal sends the packet data convergence protocol layer report to the target cell, the method further includes:
The target cell sends a negative response request data packet to the original cell;
The original cell sends the robustness header compressed data packet to the target cell;
and the original cell retransmits the robust header compressed data packet to the communication terminal.
In some embodiments, a first delay flag characterizing a delayed reconstruction robustness header compression context is set in the communication terminal;
After the communication terminal completes the cell switching or cell reconstruction, judging whether the type of the first robust header compression packet is the initialization refreshing data packet or not and whether the first delay mark is received or not;
The communication terminal executes the robust header compression and decompression flow again after executing the reconstructed robust header compression context when the type of the received first robust header compression packet is the initialization refreshing data packet and the first delay mark is received;
When the communication terminal receives the first robust header compression packet of the type of the initial refreshing data packet and does not receive the first delay mark, continuing to execute the robust header compression and decompression flow;
And when the type of the received first robust header compression packet is a non-initialized refreshing data packet, the communication terminal continuously executes the robust header compression and decompression flow.
In some embodiments, according to another implementation manner of the present invention, the present invention further provides a communication terminal, where the communication terminal includes a processor to perform an operation performed by one of the robust header compression and decompression methods described above.
The method, the system and the communication terminal have the technical effects that whether the type of the received first robust header compression packet is an initialized refreshing data packet is further judged by delaying the operation of rebuilding the robust header compression context in the cell switching or rebuilding process, and whether the corresponding robust header compression context rebuilding operation is executed is confirmed according to the judging result, so that the problem that data cached in the RLC layer of the base station side cannot be decompressed is avoided, the problem that the uninitialized refreshing data packet originally issued by the base station cannot be decompressed is also avoided, the fault tolerance of the robust header compression and decompression of the communication terminal is increased, the problem of decompression failure of a large number of continuous compression packets for a long time is avoided, and the communication service quality is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it will be apparent that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart illustrating a robust header compression and decompression method according to the present invention;
FIG. 2 is a diagram illustrating another exemplary flow of a robust header compression and decompression method of the present invention;
FIG. 3 is a diagram illustrating an exemplary communication of a robust header compression and decompression system in accordance with the present invention.
Reference numerals in the drawings: communication terminal-10, original cell-20 and target cell-30.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
For the sake of simplicity of the drawing, the parts relevant to the present invention are shown only schematically in the figures, which do not represent the actual structure thereof as a product. Additionally, in order to facilitate a concise understanding of the drawings, components having the same structure or function in some of the drawings are depicted schematically only one of them, or only one of them is labeled. Herein, "a" means not only "only this one" but also "more than one" case.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
In addition, in the description of the present application, the terms "first," "second," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will explain the specific embodiments of the present invention with reference to the accompanying drawings. It is evident that the drawings in the following description are only examples of the invention, from which other drawings and other embodiments can be obtained by a person skilled in the art without inventive effort.
In the data transmission process of the 5G/LTE terminal, a robust header compression scheme is generally adopted to reduce redundant transmission of data, save resources and increase transmission rate, static part data of TCP/UDP/IP/RTP HEADER is not changed in the communication transmission process, robust header compression uses fixity in the different IP packets, and does not need to transmit the redundant information each time, and stores the redundant information as associated information (context) in the process of compressing to decoding, and the robust header compression protocol defines 3 working modes and 3 compression and decompression states, so that the robust header compression compresses and decompresses IP packet headers in different wireless link states, maintains synchronization of compressed and decompressed data streams, ensures robustness of the robust header compression protocol, and initializes and resets states of R (initialization AND REFRESH STATE): robust header compression includes three compression states: an IR (initialization AND REFRESH STATE) initialization and reset state for initializing, updating the static domain and dynamic domain information in Wen Jing, in which the compressor continuously transmits all IP header information and stream association identifiers (PID and CID); FO (first order) a stage of compression state, wherein the compressor only needs to transmit complete dynamic header domain information; and SO (second order), the second-stage compression state, namely the SO state is the highest-stage compression state, wherein the compression party only transmits the compression value of the dynamic domain according to the change rule of the dynamic domain, and the compression party transmits the robust header compression packet with the highest compression rate. The compression state starts from IR, and the forward transition has two modes FAST and Normal, and the IR state can be directly transferred to the highest compression state SO in the FAST mode; in Normal mode IR needs to be transferred to FO state first and then from FO state to SO state. The forward transfer of U-Mode adopts a forward optimization strategy, and when the compression party considers that the decompression party receives enough information, the compression Mode is transferred from a lower-level compression Mode to a higher-level compression Mode. In this way, the compression party can continuously send n1/n2/n3 compressed packets containing context update information in a lower state, and the decompression party can receive enough decompression information in this way, and then the compression state of the compression party is shifted forward. n1/n2/n3 is suitably selected according to the circumstances. When the dynamic part of the packet information changes, the state of the compressor is transferred from SO to FO; in addition, the U-Mode uses periodic expiration to transition the compression state from a higher level to a lower level, and the value of the time Timeout for this period expiration is not explicitly specified in RFC and needs to be determined according to implementation. Since U-Mode has no feedback, parameter selection of the compression party is particularly important for overall compression efficiency and guaranteed process robust.
In the situation that the mobile or cell signal quality is not ideal, the communication terminal is necessary to switch and rebuild the cell, such as switching and rebuilding from the original cell where the communication terminal resides to the target cell with better signal. In this process, the terminal and the base station have respective practices to avoid or reduce data transmission failures. The communication terminal can execute two communication schemes:
First, the original cell where the cell resides copies the data packet received from the core network, one part is sent to the communication terminal after continuing to use the robust header compression, and the other part is directly sent to the target cell, and the target cell carries out the robust header compression and then sends to the communication terminal. After the communication terminal switches and rebuilds to the target cell, it will send a status report of the packet data convergence protocol layer (PAKCET DATA Convergence Protocol, packet data convergence protocol layer) to indicate which data packets have been successfully received, and after the target cell receives the status report of the packet data convergence protocol layer, it will discard the data packets that the communication terminal has acknowledged to receive, and resend the data packets that have not been received. When retransmitting a data packet, the first compressed packet that is delivered may be an uninitialized refresh data packet because the initial and refresh (INITIAL AND REFRESH, IR) packets are discarded after being acknowledged by the packet data convergence protocol layer.
And secondly, after the communication terminal is switched and rebuilt to the target cell, reporting a packet data convergence protocol layer state report to the target cell, wherein the target cell requests NACK data packets reported by the communication terminal to the original cell, and the original cell sends the data packets with the robustness header compressed to the target cell and then retransmits the data packets to the communication terminal.
For the above 2 cases, if the base station is not configured RohcContinue with the communication terminal, the communication terminal has reset the robust header compression context (context) and cannot decompress when the robust header compression context is reconstructed without receiving the initialized refresh packet. At this time, since the decompression end mode of the communication terminal is U mode (Unidirectional mode), the protocol does not specify that the STATIC-NACK (STATIC NEGATIVE Acknowledgement) must be returned to the target cell. So if the communication terminal is replied with NACK, all the compressed packets between the STATIC-NACK received by the target cell and the retransmission of the initialization refresh data packet fail to decompress; if the implementation does not reply to NACK, the base station itself selects when to retransmit the initialization refresh data packet, resulting in long-term continuous decompression failure. In the process of switching and reestablishing the communication terminal, the 3GPP protocol prescribes that a packet data convergence protocol layer reset flow is executed and a robust header compression context is reset, and at the moment, the packet after being compressed by the robust header compression processing received from the original cell is cached in a radio link layer control protocol (Radio Link Control, RLC) layer. After the communication terminal is successfully accessed to the target cell and the packet data convergence protocol layer is reconfigured, the RLC sends the cached data to the packet data convergence protocol layer for robust header compression and decompression, and then reports the state of the packet data convergence protocol layer to tell the target cell which packets are received and the target cell will resend the data packets which are not received. Since the robust header compression context has been reset, the received RLC buffered compressed packets cannot be decompressed normally and the target cell will not perform packet data convergence protocol layer retransmissions, resulting in decompression failure and loss of these packets.
Based on this, as shown in fig. 1, the present invention provides a robust header compression and decompression method, which is applied to a communication terminal, and includes the steps of:
S100, in the process of executing cell switching or cell reconstruction by the communication terminal, the reconstruction of the robust header compression context is delayed after the packet data convergence protocol layer is reset.
And S200, judging whether the type of the received first robustness header compression packet is an initialization refreshing data packet or not after the communication terminal performs cell switching or cell reestablishment.
S310 re-executes the robust header compression decompression procedure after executing the reconstruction of the robust header compression context when the first robust header compression packet type is the initialized refresh packet.
S320 continues to execute the robust header compression decompression procedure when the first robust header compression packet type is the non-initialized refresh packet.
The robust header compression and decompression method provided by the embodiment can avoid the problem that data buffered in the base station side RLC layer cannot be decompressed by delaying the operation of reconstructing the robust header compression context in the cell switching or reconstruction process, and simultaneously avoid the problem that the uninitialized refreshing data packet initially issued by the base station cannot be decompressed, thereby increasing the fault tolerance of the robust header compression and decompression of the communication terminal, avoiding the problem of decompression failure of a large number of continuous compression packets for a long time and improving the communication service quality.
In one embodiment, as shown in fig. 2, step S100 further includes the steps of, after the packet data convergence protocol layer is reset and the robust header compression context is delayed to be reconstructed in the process of performing cell handover or cell reconstruction by the communication terminal:
s110, in the process of executing cell switching or cell reconstruction by the communication terminal, resetting the packet data convergence protocol layer and then delaying reconstruction of the robust header compression context, and setting a first delay flag representing the delayed reconstruction of the robust header compression context.
Illustratively, the first delay flag is set to resetContextDelay = TRUE.
S210, after the communication terminal performs cell switching or cell reestablishment, judging whether the type of the first robust header compression packet is an initialized refreshing data packet and whether a first delay mark is received.
S311 re-executes the robust header compression decompression procedure after executing the reconstruction of the robust header compression context when the type of the first robust header compression packet is the initial refresh packet and the first delay flag is received.
S312 continues to execute the robust header compression and decompression procedure when the first robust header compression packet type is the initialization refresh packet and the first delay flag is not received.
S321 continues to execute the robust header compression and decompression procedure when the type of the first robust header compression packet is the non-initialized refresh packet.
Specifically, when the type of the first robust header compression packet is an initialized refreshing data packet and a first delay flag is received, the robust header compression and decompression process is re-executed after the robust header compression context is rebuilt, the first delay flag is updated to be a second delay flag, and when the type of the first robust header compression packet is a non-initialized refreshing data packet, the robust header compression and decompression process is continuously executed, and the first delay flag is updated to be the second delay flag.
Illustratively, the second delay flag is set to resetContextDelay = FALSE.
In one embodiment, as shown in fig. 3, the present invention further provides a robust header compression decompression system, which is applied to a communication system including a communication terminal 10, an original cell 20 and a target cell 30, wherein the communication terminal 10 sends a cell switching instruction or a cell reconstruction instruction to the original cell 20, resets a packet data convergence protocol layer and then delays to reconstruct a robust header compression context, the target cell 30 sends a robust header compression packet to the communication terminal 10 after the communication terminal 10 performs cell switching or cell reconstruction, the communication terminal 10 determines whether the received first robust header compression packet is an initialized refresh packet, the communication terminal 10 executes a robust header compression decompression process again after executing the robust header compression context reconstruction when the first robust header compression packet is an initialized refresh packet, and the communication terminal 10 continues to execute the robust header compression decompression process when the first robust header compression packet is a non-initialized refresh packet.
In one embodiment, as shown in fig. 3, after the packet data convergence protocol layer is reset and the robust header compression context is re-established, the target cell 30 further includes, before the communication terminal 10 performs cell switching or after the cell re-establishment is completed, transmitting the robust header compression packet to the communication terminal 10: the communication terminal 10 accesses the target cell 30 and completes the reconfiguration of the dedicated radio bearer parameters; the communication terminal 10 transmits a packet data convergence protocol layer state report to the target cell 30.
In one embodiment, as shown in fig. 3, after the communication terminal 10 sends a cell handover instruction or a cell reestablishment instruction to the original cell 20, before the communication terminal 10 accesses the target cell 30 and completes the dedicated radio bearer parameter reconfiguration, the method further includes: the original cell 20 copies and receives the core network data packet, synchronously transmits the core network data packet to the target cell 30, and transmits the core network data packet to the communication terminal 10 after the robustness header compression; the target cell 30 compresses the core network data packet through the robustness header and sends the core network data packet to the communication terminal 10; after sending the packet data convergence protocol layer status report to the target cell 30, the communication terminal 10 further includes: the target cell 30 discards the robust header compression packet received by the communication terminal 10 according to the packet data convergence protocol layer report; the target cell 30 retransmits the robust header compression packet to the communication terminal 10 that was not received by the communication terminal 10.
In one embodiment, as shown in fig. 3, after the communication terminal 10 sends the packet data convergence protocol layer status report to the target cell 30, the method further includes the target cell 30 sending a negative acknowledgement request packet to the original cell 20; the original cell 20 sends the robust header compressed data packet to the target cell 30; the original cell 20 retransmits the robust header compressed data packet to the communication terminal 10.
In one embodiment, as shown in fig. 3, a first delay flag characterizing a delayed reconstruction of the robust header compression context is set in the communication terminal 10, after performing cell handover or cell reconstruction, the communication terminal 10 determines whether the type of the first robust header compression packet is an initialized refresh packet and whether the first delay flag is received, when the type of the received first robust header compression packet is the initialized refresh packet and the first delay flag is received, the communication terminal 10 performs the robust header compression decompression process again after performing reconstruction of the robust header compression context, when the type of the received first robust header compression packet is the initialized refresh packet and the first delay flag is not received, the communication terminal 10 continues to perform the robust header compression decompression process, and when the type of the received first robust header compression packet is the non-initialized refresh packet, the communication terminal 10 continues to perform the robust header compression decompression process.
In some embodiments, according to another implementation manner of the present invention, the present invention further provides a communication terminal, where the communication terminal includes a processor to perform an operation performed by the robust header compression and decompression method described above.
In the foregoing embodiments, the descriptions of the embodiments are focused on, and the parts of a certain embodiment that are not described or depicted in detail may be referred to in the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the elements and steps of the examples described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or as a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed method, system and communication terminal for compressing and decompressing a robust header may be implemented in other manners. For example, the embodiments of a robust header compression decompression method, system, and communication terminal described above are merely illustrative, for example, the division of the modules or units is merely a logical function division, and there may be other manners of division in actual implementation, for example, multiple units or modules may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the communications links shown or discussed may be through some interface, device or unit communications link or integrated circuit, whether electrical, mechanical or otherwise.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
It should be noted that the foregoing is only a preferred embodiment of the present invention, and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (10)
1. The robust header compression and decompression method is characterized by being applied to a communication terminal and comprising the following steps:
in the process that the communication terminal executes cell switching or cell reconstruction, the packet data convergence protocol layer is reset and then the reconstruction of the robust header compression context is delayed;
after the communication terminal performs cell switching or cell reconstruction, judging whether the type of the received first robust header compression packet is an initialized refreshing data packet or not;
When the type of the first robust header compression packet is the initialization refreshing data packet, executing the robust header compression and decompression flow after reconstructing the robust header compression context;
And when the type of the first robust header compression packet is a non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow.
2. The robust header compression decompression method according to claim 1, wherein said delayed reconstruction of the robust header compression context further comprises the steps of:
Setting a first delay flag characterizing a delayed reconstruction robustness header compression context;
after the communication terminal performs cell switching or cell reconstruction, judging whether the type of the first robust header compression packet is the initialization refreshing data packet or not and whether the first delay mark is received or not;
executing the robust header compression and decompression flow again after executing the reconstructed robust header compression context when the type of the first robust header compression packet is the initialized refreshing data packet and the first delay mark is received;
When the type of the first robust header compression packet is the initialization refreshing data packet and the first delay mark is not received, continuing to execute the robust header compression and decompression flow;
and when the type of the first robust header compression packet is the non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow.
3. The method of claim 2, wherein said determining whether the first robust header compression packet type is the initialization refresh packet and whether the first delay flag is received comprises:
When the type of the first robust header compression packet is the initialized refreshing data packet and the first delay flag is received, executing the robust header compression and decompression flow again after the robust header compression context is rebuilt, and updating the first delay flag to be a second delay flag;
And when the type of the first robust header compression packet is the non-initialized refreshing data packet, continuing to execute the robust header compression and decompression flow and updating the first delay flag to be the second delay flag.
4. A robust header compression decompression method according to claim 3, wherein said first delay flag is set to resetContextDelay = TRUE;
the second delay flag is set to resetContextDelay =false.
5. A robust header compression decompression system, for use in a communication system comprising a communication terminal, an original cell and a target cell, comprising:
The communication terminal sends a cell switching instruction or a cell reconstruction instruction to the original cell, and delays reconstruction of the robust header compression context after resetting the packet data convergence protocol layer;
The target cell sends a robustness header compression packet to the communication terminal after the communication terminal performs cell switching or cell reconstruction;
The communication terminal judges whether the type of the received head compressed packet with the robustness is an initialized refreshing data packet;
When the type of the first robust header compression packet is the initialization refreshing data packet, the communication terminal executes the robust header compression and decompression flow again after rebuilding the robust header compression context;
And when the type of the first robust header compression packet is a non-initialized refreshing data packet, the communication terminal continuously executes the robust header compression and decompression flow.
6. The robust header compression decompression system of claim 5, wherein said target cell, after said resetting the packet data convergence protocol layer and delaying the reconstruction of the robust header compression context, further comprises, before transmitting the robust header compression packet to said communication terminal after said communication terminal performs cell switching or cell reconstruction is completed:
the communication terminal accesses the target cell and completes the reconfiguration of the special radio bearer parameters;
And the communication terminal sends a packet data convergence protocol layer state report to the target cell.
7. The robust header compression and decompression system according to claim 6, wherein after the communication terminal transmits a cell handover command or a cell reestablishment command to the original cell, the communication terminal accesses the target cell and completes the dedicated radio bearer parameter reconfiguration, further comprising:
The original cell copies and receives a core network data packet, synchronously transmits the core network data packet to the target cell, and transmits the core network data packet to the communication terminal after being compressed by a robustness header;
the target cell compresses the core network data packet through a robustness header and then sends the core network data packet to the communication terminal;
after the communication terminal sends the packet data convergence protocol layer state report to the target cell, the communication terminal further comprises:
Discarding the robust header compressed packet received by the communication terminal according to the packet data convergence protocol layer state report by the target cell;
And the target cell retransmits the robust header compression packet which is not received by the communication terminal to the communication terminal.
8. The robust header compression and decompression system according to claim 6, wherein said communication terminal further comprises, after transmitting a packet data convergence protocol layer report to said target cell:
The target cell sends a negative response request data packet to the original cell;
The original cell sends the robustness header compressed data packet to the target cell;
and the original cell retransmits the robust header compressed data packet to the communication terminal.
9. A robust header compression decompression system according to any one of claims 5 to 8,
Setting a first delay mark representing a delay reconstruction robustness header compression context in the communication terminal;
After the communication terminal completes the cell switching or cell reconstruction, judging whether the type of the first robust header compression packet is the initialization refreshing data packet or not and whether the first delay mark is received or not;
The communication terminal executes the robust header compression and decompression flow again after executing the reconstructed robust header compression context when the type of the received first robust header compression packet is the initialization refreshing data packet and the first delay mark is received;
When the communication terminal receives the first robust header compression packet of the type of the initial refreshing data packet and does not receive the first delay mark, continuing to execute the robust header compression and decompression flow;
and when the type of the received first robust header compression packet is the non-initialization refreshing data packet, the communication terminal continuously executes the robust header compression and decompression flow.
10. A communication terminal comprising a processor for performing the operations performed by a robust header compression decompression method according to any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410444531.3A CN118055446B (en) | 2024-04-15 | 2024-04-15 | Robust header compression and decompression method, system and communication terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410444531.3A CN118055446B (en) | 2024-04-15 | 2024-04-15 | Robust header compression and decompression method, system and communication terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN118055446A true CN118055446A (en) | 2024-05-17 |
| CN118055446B CN118055446B (en) | 2024-06-18 |
Family
ID=91046670
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410444531.3A Active CN118055446B (en) | 2024-04-15 | 2024-04-15 | Robust header compression and decompression method, system and communication terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118055446B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006056122A1 (en) * | 2004-11-26 | 2006-06-01 | Huawei Technologies Co., Ltd. | A method for rapidly resuming the context of compression and decompression |
| CN101690072A (en) * | 2007-09-03 | 2010-03-31 | 中兴通讯股份有限公司 | Method for repairing window-based least significant bit decoding in robust header compression |
| CN102036307A (en) * | 2010-12-17 | 2011-04-27 | 中兴通讯股份有限公司 | Method and device for improving robustness of context update message in robustness header compression |
| WO2012051883A1 (en) * | 2010-10-19 | 2012-04-26 | 中兴通讯股份有限公司 | Method and device for reusing context in robust header compression |
| US9210642B2 (en) * | 2009-01-29 | 2015-12-08 | Samsung Electronics Co., Ltd. | Method and system for computing and sending resource requests and avoiding deadlock situations in mobile communication system |
| CN110830170A (en) * | 2019-11-12 | 2020-02-21 | 北京理工大学 | Data transmission method based on ROHC compression in satellite communication |
| CN111800826A (en) * | 2019-08-01 | 2020-10-20 | 维沃移动通信有限公司 | ROHC feedback processing method and user equipment |
| WO2021017812A1 (en) * | 2019-07-30 | 2021-02-04 | 夏普株式会社 | User equipment and method executed thereby, base station and method executed thereby |
| WO2023102938A1 (en) * | 2021-12-10 | 2023-06-15 | Oppo广东移动通信有限公司 | Wireless communication method and communication device |
| CN116456393A (en) * | 2022-01-07 | 2023-07-18 | 华为技术有限公司 | Communication method and device |
| US20230328831A1 (en) * | 2022-04-12 | 2023-10-12 | Samsung Electronics Co., Ltd. | Method and apparatus for pdcp re-establishment procedure of ue supporting ethernet header compression protocol in wireless communication system |
-
2024
- 2024-04-15 CN CN202410444531.3A patent/CN118055446B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006056122A1 (en) * | 2004-11-26 | 2006-06-01 | Huawei Technologies Co., Ltd. | A method for rapidly resuming the context of compression and decompression |
| CN101690072A (en) * | 2007-09-03 | 2010-03-31 | 中兴通讯股份有限公司 | Method for repairing window-based least significant bit decoding in robust header compression |
| US9210642B2 (en) * | 2009-01-29 | 2015-12-08 | Samsung Electronics Co., Ltd. | Method and system for computing and sending resource requests and avoiding deadlock situations in mobile communication system |
| WO2012051883A1 (en) * | 2010-10-19 | 2012-04-26 | 中兴通讯股份有限公司 | Method and device for reusing context in robust header compression |
| CN102036307A (en) * | 2010-12-17 | 2011-04-27 | 中兴通讯股份有限公司 | Method and device for improving robustness of context update message in robustness header compression |
| WO2021017812A1 (en) * | 2019-07-30 | 2021-02-04 | 夏普株式会社 | User equipment and method executed thereby, base station and method executed thereby |
| CN111800826A (en) * | 2019-08-01 | 2020-10-20 | 维沃移动通信有限公司 | ROHC feedback processing method and user equipment |
| CN110830170A (en) * | 2019-11-12 | 2020-02-21 | 北京理工大学 | Data transmission method based on ROHC compression in satellite communication |
| WO2023102938A1 (en) * | 2021-12-10 | 2023-06-15 | Oppo广东移动通信有限公司 | Wireless communication method and communication device |
| CN116456393A (en) * | 2022-01-07 | 2023-07-18 | 华为技术有限公司 | Communication method and device |
| US20230328831A1 (en) * | 2022-04-12 | 2023-10-12 | Samsung Electronics Co., Ltd. | Method and apparatus for pdcp re-establishment procedure of ue supporting ethernet header compression protocol in wireless communication system |
Non-Patent Citations (4)
| Title |
|---|
| ""R2-1908916"", 3GPP TSG_RAN\\WG2_RL2, 15 August 2019 (2019-08-15) * |
| ERICSSON: "R3-185325 "BL CR for TS 38.463 covering agreements from RAN3-AH-1807 and R3-101"", 3GPP TSG_RAN\\WG3_IU, no. 3, 3 September 2018 (2018-09-03) * |
| SHARP CORPORATION: "R2-2003665 "RoHC handling for inter-gNB and intra-gNB DAPS handover"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 10 April 2020 (2020-04-10) * |
| 徐海鑫: "LTE系统中ROHC报头压缩系统的研究与实现", CNKI优秀硕士学位论文全文库, 15 July 2015 (2015-07-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118055446B (en) | 2024-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8155083B2 (en) | Technique for configuring link layer entities for a handover | |
| JP4005508B2 (en) | Relocation of context information in header compression | |
| JP3763741B2 (en) | Packet discard notification for semi-reliable retransmission protocol | |
| JP4633756B2 (en) | Timer processing method after RLC reset or reconfiguration in wireless communication system | |
| US9072006B2 (en) | Mobile communication method and system | |
| US8175075B2 (en) | Adaptive header compression in a wireless communication network | |
| CN108574967B (en) | Data transmission method and device | |
| WO2019095989A1 (en) | Processing method and device for cache synchronous exception | |
| EP3570631B1 (en) | Data packet transmission method and device | |
| KR102335821B1 (en) | Data transmission method and device | |
| CN102026281A (en) | Method and device for realizing TCP (transmission control protocol) proxy based on RNC (radio network controller) | |
| CN111385268B (en) | Data packet header compression confirmation method and communication equipment | |
| CN108282824B (en) | State updating method, node and user terminal | |
| CN113796057A (en) | User data compression method and apparatus for preventing data loss in wireless communication system | |
| CN113543217A (en) | Data transmission method and communication device | |
| WO2020119718A1 (en) | Data packet decompression method and device | |
| WO2006056122A1 (en) | A method for rapidly resuming the context of compression and decompression | |
| US20100232455A1 (en) | Packet communication apparatus and method for packet communication | |
| WO2021023044A1 (en) | Communication method and device | |
| EP4311300A1 (en) | Data transmission method and apparatus | |
| CN118055446B (en) | Robust header compression and decompression method, system and communication terminal | |
| JP2005217626A (en) | Packet data exchange node through wireless access network, terminal and its program | |
| WO2021208863A1 (en) | Data transmission method and communication apparatus | |
| CN112787759B (en) | Method for optimizing cross-base station switching efficiency | |
| JP2004179917A (en) | Method for processing accidental transmission interruption of wireless communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |