CN117715109A - Communication processing method, device, apparatus and storage medium - Google Patents
Communication processing method, device, apparatus and storage medium Download PDFInfo
- Publication number
- CN117715109A CN117715109A CN202311701780.8A CN202311701780A CN117715109A CN 117715109 A CN117715109 A CN 117715109A CN 202311701780 A CN202311701780 A CN 202311701780A CN 117715109 A CN117715109 A CN 117715109A
- Authority
- CN
- China
- Prior art keywords
- decompression
- end device
- data packet
- compressed data
- compression
- 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.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 87
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 230000006837 decompression Effects 0.000 claims abstract description 263
- 238000007906 compression Methods 0.000 claims abstract description 142
- 230000006835 compression Effects 0.000 claims abstract description 141
- 238000012545 processing Methods 0.000 claims abstract description 128
- 238000000034 method Methods 0.000 claims abstract description 77
- 230000008569 process Effects 0.000 claims abstract description 42
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012790 confirmation Methods 0.000 claims description 3
- 230000005856 abnormality Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 21
- 230000015654 memory Effects 0.000 description 17
- 230000006870 function Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 7
- 230000007704 transition Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000013144 data compression Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000005457 optimization 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
- 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
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The embodiment of the application discloses a communication processing method, equipment, a device and a storage medium, wherein the method is applied to decompression terminal equipment and comprises the following steps: when robust header compression ROHC is enabled, responding to decompression failure of the decompression end device on the first compressed data packet, and counting the number of times of decompression failure; and if the number of decompression failures determined by the counting process meets the state reset condition, executing state reset processing on the decompression end device and the compression end device. By adopting the invention, the communication abnormality between the terminal and the network side equipment caused by the decompression failure for a long time can be avoided.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a communication processing method, device, apparatus, and storage medium.
Background
The header compression and header decompression processes are performed on data transmitted between the terminal and the network side device by using ROHC (Robust Header Compression ) technology, so that an IP (Internet Protocol )/UDP (User Datagram Protocol, user datagram Protocol)/RTP (Real-Time Protocol) packet or a header of TCP (Transmission Control Protocol )/IP packet can be compressed to a few bytes under extremely bad channel conditions, so as to improve the performance of carrying IP flows in the wireless network between the terminal and the base station, especially in voice services, for example: in the Voice over Long-Term Evolution (lte) Voice service, the header of the data packet occupies a relatively large area, and the efficiency of transmitting Voice service data can be improved by performing header compression processing using the ROHC technology.
Header decompression is performed on a received compressed data packet that is subjected to header compression by using the ROHC technology at a decompression end device, and header decompression failure may occur due to an abnormal condition of header decompression, for example: since the HFN (Hyper Frame Number, superframe number) of the decompression end device and the compression end device are out of step, decryption of the compressed data packet is wrong, so that subsequent decompression of the compressed data packet fails, for example: decompression failure due to a jump of SN (Sequence Number) in the compressed data packet is also described as follows: decompression fails because the value of the CRC (Cyclic Redundancy Check ) field of the compressed packet is erroneous.
At present, when the average error rate of a communication channel is determined to reach a threshold, the communication channel is generally detected to trigger the recompression and recompression processing of data so as to cope with the abnormal condition of header decompression, but the success rate of decompression still cannot be effectively improved, and the consumption of transmission resources and the time delay of communication between a decompression terminal device and a compression terminal device are increased.
Disclosure of Invention
The embodiment of the application provides a communication processing method, device and apparatus and a storage medium, which can avoid abnormal communication between a terminal and network side equipment caused by long-time decompression failure.
In order to solve the above technical problem, in a first aspect, an embodiment of the present application provides a communication processing method, which is applied to a decompression end device, where the method includes:
when robust header compression ROHC is enabled, responding to decompression failure of the decompression end device on the first compressed data packet, and counting the number of times of decompression failure;
and if the number of decompression failures determined by the counting process meets the state reset condition, executing state reset processing on the decompression end device and the compression end device.
In a second aspect, an embodiment of the present application further provides a communication processing method, applied to a compression end device, where the method includes:
generating a first compressed data packet when the robust header compression ROHC is enabled;
and sending the first compressed data packet.
In a third aspect, an embodiment of the present application provides a communication processing apparatus, including: a memory device and a processor, wherein the memory device is configured to store data,
the storage device is used for storing program codes;
the processor is configured to execute the communication processing method according to the first aspect when the stored code is called.
In a fourth aspect, embodiments of the present application further provide a communication processing apparatus, including: a memory device and a processor, wherein the memory device is configured to store data,
The storage device is used for storing program codes;
the processor, when calling the stored code, is configured to execute the communication processing method according to the second aspect.
In a fifth aspect, an embodiment of the present application provides a communication processing apparatus, including:
the counting module is used for responding to the decompression failure of the decompression end device to the first compressed data packet when the robust header compression ROHC is enabled, and counting the number of times of the decompression failure;
and the resetting module is used for executing the state resetting processing of the decompression end device and the compression end device if the number of times of decompression failure determined by the counting processing meets the state resetting condition.
In a sixth aspect, embodiments of the present application further provide a communication processing apparatus, including:
the generation module is used for generating a first compressed data packet when the robust header compression ROHC is enabled;
and the sending module is used for sending the first compressed data packet.
In a seventh aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program that causes a computer to execute the communication processing method of the first aspect.
In an eighth aspect, embodiments of the present application further provide a computer-readable storage medium for storing a computer program that causes a computer to execute the communication processing method of the second aspect.
In a ninth aspect, embodiments of the present application further provide a communication processing system, where the communication processing system includes a first communication processing device and a second communication processing device, where the first communication processing device is configured to implement the method in the first aspect, and the second communication processing device is configured to implement the method in the second aspect.
The implementation of the embodiment of the application has the following beneficial effects:
when the number of decompression failures of the decompression terminal equipment meets the state reset condition, the state reset processing of the decompression terminal equipment and the compression terminal equipment is automatically triggered and executed, so that the accuracy of the decompression processing of the decompression terminal equipment can be improved, wireless transmission resources are saved, and communication abnormality between the terminal and the network side equipment caused by long-time decompression failures is avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a data plane protocol stack of a terminal and a network side device according to an embodiment of the present application;
fig. 2a is a functional schematic diagram of PDCP layers of a terminal and a network side device in an LTE (Long Term Evolution ) communication system according to an embodiment of the present application;
fig. 2b is a functional schematic diagram of PDCP layers of a terminal and a network side device in an NR (New Radio) communication system according to an embodiment of the present application;
fig. 3 is a schematic diagram of encryption and decryption performed in a PDCP layer according to an embodiment of the present application;
fig. 4 is a schematic diagram of a COUNT value according to an embodiment of the present application;
fig. 5 is a schematic diagram of HFN synchronization and HFN out-of-synchronization between a terminal and a network side device according to an embodiment of the present application;
fig. 6 is a scene diagram of a communication processing method according to an embodiment of the present application;
fig. 7 is a schematic flow chart of a communication processing method according to an embodiment of the present application;
fig. 8 is an interaction flow diagram of a communication processing method according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a communication processing device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a communication processing device according to an embodiment of the present application;
Fig. 11 is a schematic structural diagram of another communication processing apparatus according to an embodiment of the present application.
Detailed Description
The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that, in the description and claims of the present application and in the above figures, the terms "first," "second," and the like are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present application described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
In order to better understand the communication decoding method, device, apparatus and storage medium provided in the embodiments of the present application, technical terms related to the present application are explained as follows:
(1) ROHC (Robust Header Compression robust head compression)
ROCH header compression may be described as the interaction between two state machines, a compression state machine (compression end device) and a decompression state machine (decompression end device). Compression gain is achieved by establishing Context, i.e. a set of static and dynamic header fields, at the state machines at both ends of the communication link. The compression end device and the decompression end device must keep context synchronous when running, the compression end device adds CRC (Cyclic Redundancy Check ) in the compressed packet, and the decompression end device ensures that the context can be updated timely and correctly by feeding back ACK (Acknowledgement) or NACK (Negative Acknowledgement ).
ROHC supports three modes of operation: u (unidirectional) mode, O (bi-directional optimization) mode, and R (bi-directional reliability) mode. Each mode specifies the manner and frequency of some information interactions, such as: whether feedback is used more, etc. If the method can be switched to a reliable mode in time, more feedback information such as states, special domains and the like can be interacted, and the consistency of the contexts of the compression end equipment and the decompression end equipment can be ensured as much as possible, so that the correct probability of decompression processing in a high compression ratio state is improved.
Wherein, the U mode is suitable for unidirectional feedback-free channel environment. Since mobile cellular network bandwidth is at a premium, feedback-free channels will be a significant percentage, and U-mode will operate on such channels. In the U mode, since the compression end device cannot obtain feedback information of the decompression end device, state transition of the compression end device can only depend on its own independent transition mechanism.
There are three compression states of the compression end device: an IR (Initialization and Refresh) state, a FO (First Order) state, a SO (Second Order) state. The compression status of the compression end device may be used to indicate the extent of header compression that may be performed; the state levels of the IR state, the FO state and the SO state are sequentially increased; state transitions may be made between the compression states. The compression end equipment sends different types of compressed data packets in different compression states, specifically, the compression end equipment sends an initialization compressed data packet in an IR state, the compressed data packet contains all context information related to decompression processing, and the decompression end equipment establishes a context through information in the IR compressed data packet; the compression end device sends some dynamic domain change information in FO state, such as: dynamic change information such as the middle change of the priority of the compressed data packet; the compression end device transmits only the minimized compression header in the SO state, which is the fully compressed state.
The compression state starts from the IR state and there are two modes of forward transition: FAST mode and NORMAL mode. In FAST mode, the IR state can jump directly to the SO state. In NORMAL mode, the IR state is first transferred to the FO state and then from the FO state to the SO state. In the U mode, since there is no information fed back by the decompression side device, the compression side device may transition from the lower-level compression state to the higher-level compression state according to the "own" belief that the decompression side device receives sufficient information. In the O mode or the R mode, the compression end device may send information fed back by the decompression end device, for example: and (5) decompressing the successful confirmation message, determining whether the decompression end device obtains enough information when performing decompression processing, and further performing migration of the corresponding compression state.
There are three decompression states of the decompression side device: NC (No Context) state, SC (Static Context) state, FC (Full Context) state; state transitions may be made between the decompressed states. The decompression status of the decompression end device may be used to indicate the capability of the decompression end device to decompress the corresponding compressed data packet header, such that the decompression status corresponds to header compression performance. The state levels of the NC state, the SC state and the FC state are sequentially increased.
The decompression end device is always in the FC state after obtaining enough decompression information, and can be shifted from the FC state to the SC state only when the decompression of k1 compressed data packets in the n1 continuous compressed data packets received recently fails. In the SC state, when one compressed data packet containing enough update information is successfully decompressed, the state is shifted to the FC state, and when k2 compressed data packets in n2 consecutive compressed data packets are recently received and the decompression of the k2 compressed data packets fails, the state is shifted to the NC state. n1, k1, n2, k2 are positive integers, configurable by higher layer signaling, or set by protocol, or set by human.
(2) Function of PDCP (Packet Data Convergence Protocol ) layer of terminal and network side device
Referring to fig. 1, fig. 1 is a schematic diagram of a data plane protocol stack of a terminal and a network side device provided in an embodiment of the present application, and as shown in fig. 1, the network side device is a compression end device, and the terminal is a decompression end device; the network side equipment sequentially performs (header) compression processing on the data at the PDCP layer of the network side equipment, and performs encryption processing on the header-compressed data to generate a compressed data packet; after the compressed data packet sequentially passes through the RLC (Radio Link Control ) layer, MAC (Media Access Control, medium access control) layer and PHY (Physical ) layer of the network side device, the compressed data packet is processed by an interface from the PHY layer of the network side device, for example: the wireless interface transmits the compressed data packet to the PHY layer of the terminal, the compressed data packet is transmitted to the PDCP layer of the terminal after being processed by the PHY layer, the MAC layer and the RLC layer of the terminal in sequence, the PDCP layer of the terminal sequentially decrypts the compressed data packet, and (head) decompresses the decrypted compressed data packet. Wherein the compression process and the decompression process are both performed in terms of ROHC.
Referring to fig. 2a, fig. 2a is a functional schematic diagram of PDCP layers of a terminal and a network side device in an LTE (Long Term Evolution ) communication system according to an embodiment of the present application, and specifically as shown in fig. 2a, the network side device serves as a compression end device, i.e. a PDCP transmitting entity, and the terminal serves as a decompression end device, i.e. a PDCP receiving entity. After receiving the data transferred to the PDCP layer by the upper layer, the PDCP transmitting entity sequentially performs the following steps on the data:
step 10.1: adding SN (Sequence Number );
step 10.2: performing header compression or UDC (Uplink Data Compression, upstream data compression) processing, wherein the header compression or upstream data compression processing is applied only to the user plane;
if the compressed data packet is a data packet associated with PDCP SDU (Service Data Unit ), then step 10.3 is performed; if the data packet after compression processing is a data packet which is not associated with the PDCP SDU, executing step 10.5;
step 10.3: integrity protection is performed, wherein the integrity protection is only applied to the control plane;
step 10.4: performing encryption processing;
step 10.5: adding PDCP Header (Header information);
Step 10.6: if RB (Resource Block) segmentation exists in the data packet processed in steps 10.1 to 10.5, a Routing function is added.
The PDCP transmitting entity transmits the compressed data packet after the compression ciphering process to the PDCP receiving entity through a radio interface, such as Uu interface. After receiving the compressed data packet, the PDCP receiving entity sequentially performs the following steps on the compressed data packet:
step 20.1: removing the PDCP Header;
if the compressed data packet is a data packet associated with PDCP SDUs, step 20.2 is performed; if the compressed data packet is a data packet not associated with PDCP SDUs, then step 20.5 is performed;
step 20.2: performing decryption processing;
step 20.3: carrying out integrity verification;
step 20.4: performing a reordering process, wherein the reordering process is applied only to the user plane;
step 20.5: performing header decompression, wherein header compression processing is only applied to the user plane;
step 20.6: sequentially submitting and detecting repeatability;
the sequential delivery is to sequentially deliver the data obtained by the header decompression processing to an upper layer of the PDCP receiving entity according to the sequence of the SN corresponding to the data.
Fig. 2b is a functional schematic diagram of PDCP layers of a terminal and a network side device in an NR (New Radio) communication system provided in this embodiment, and specifically as shown in fig. 2b, the network side device is used as a compression end device, i.e. a PDCP transmitting entity, and the terminal is used as a decompression end device, i.e. a PDCP receiving entity. After receiving the data transferred to the PDCP layer by the upper layer, the PDCP transmitting entity sequentially performs the following steps on the data:
Step 11.1: adding SN (Sequence Number );
step 11.2: performing head compression processing;
if the data packet after header compression processing is the data packet associated with the PDCP SDU, executing step 11.3; if the data packet after header compression processing is a data packet not associated with the PDCP SDU, executing step 11.5;
step 11.3: performing integrity protection;
step 11.4: performing encryption processing;
step 11.5: adding a PDCP Header;
step 11.6: if RB (Resource Block) segmentation exists in the data packet processed in steps 11.1 to 11.5, a Routing function and a Duplication function are added.
The PDCP transmitting entity transmits the compressed data packet after the compression ciphering process to the PDCP receiving entity through a radio interface, such as Uu interface. After receiving the compressed data packet, the PDCP receiving entity sequentially performs the following steps on the compressed data packet:
step 21.1: removing the PDCP Header;
if the compressed data packet is a data packet associated with PDCP SDUs, step 21.2 is performed; if the compressed data packet is a data packet not associated with PDCP SDUs, then step 21.5 is performed;
step 21.2: performing decryption processing;
step 21.3: carrying out integrity verification;
Step 21.4: performing reordering and repeated discarding processes;
step 21.5: performing header decompression processing;
after performing step 21.5, the header decompression processing result data is delivered to an upper layer of the PDCP receiving entity.
The PDCP layer of the terminal includes an ROHC module, which is configured to perform (header) decompression processing on the decrypted compressed data packet according to an ROHC protocol, that is, perform decompression processing on the decrypted compressed data packet, and send a decompression result to a PDCP layer of the terminal (processing module).
Specifically, if the ROHC module decompresses the compressed data packet successfully, the ROHC module sends information that the compressed data packet is decompressed successfully to a (processing module) of a PDCP layer of the terminal. If the ROHC module fails to decompress the compressed data packet N times, the ROHC module sends information of the decompression failure of the compressed data packet to a (processing module) of a PDCP layer of the terminal.
Where N is a positive integer, such as: n=3, N may be configured by higher layer signaling of the terminal, or N may be specified by a protocol, or N may be set at the terminal by an operator, and N is not limited herein.
In this embodiment of the present application, if the PDCP layer of the terminal receives the decompression result of the compressed data packet, the decompression process is not performed on the compressed data packet again; if the PDCP layer of the terminal receives the decompression result of the compressed data packet and the terminal also receives other compressed data packets, the terminal performs decompression on the other compressed data packets that have not been subjected to the decompression.
(3) Encryption and decryption of data in PDCP layer
Referring to fig. 3, fig. 3 is a schematic diagram of encryption and decryption performed at a PDCP layer according to an embodiment of the present application, and specifically as shown in fig. 3, a network side device is used as a compression end device, and a terminal is used as a decompression end device. At the PDCP layer of the compression end device, inputting a COUNT value, a bearer identification, an uplink and downlink direction, a key stream length, and a ciphering key into a ciphering algorithm model to output a key stream block from the ciphering algorithm model; and encrypting the plaintext block by using the key stream block to obtain a ciphertext block, wherein the plaintext block refers to data to be encrypted.
The uplink and downlink directions are used for indicating whether the data to be encrypted is uplink data or downlink data.
At the PDCP layer of the decompression side device, inputting the COUNT value, the bearer identification, the uplink and downlink directions, the key stream length, and the encryption key into an encryption algorithm model to obtain a key stream block from the output; and decrypting the received ciphertext block by using the key stream block to obtain a plaintext block.
In this embodiment, the COUNT value includes two parts: high HFN (Hyer Frame Number, superframe number) and low SN; wherein the value range of SN is 0 to [2 ] ^ (PDCP SN size)-1]PDCP SN size indicates the data length of SN, such as: bit length.
Referring to fig. 4, fig. 4 is a schematic diagram of a COUNT value provided in the embodiment of the present application, specifically, as shown in fig. 4, the COUNT value occupies 32 bits, then the SN occupies the bit length of PDCP SN size, and the HFN occupies the bit length of 32-PDCP SN size.
(4) HFN synchronization and HFN out-of-synchronization between terminal and network side device
In this embodiment of the present application, the terminal and the network side device may maintain respective HFNs, where SN reaches 2 ^ (PDCP SN size)-When 1, SN will be sequentially valued from 0 again, and HFN will be accumulated 1 time. Under normal communication conditions, the terminal and the network side equipment keep synchronous HFNs of the terminal and the network side equipment.
Referring to fig. 5, fig. 5 is a schematic diagram of HFN synchronization and HFN out-of-step between a terminal and a network side device provided in an embodiment of the present application, and as shown in fig. 5, the network side device is a compression end device, and the terminal is a decompression end device; in the process of hfn=0 to hfn=1, the HFN of the terminal and the network side device are kept synchronous, and under the condition that no jump occurs in SN corresponding to the compressed data packet sent by the network side device, the COUNT value used by the terminal for decryption is correct, so that the compressed data packet can be decrypted correctly, and further the subsequent decompression of the decrypted compressed data packet is facilitated to be successful.
In the hfn=1 to hfn=2, the compressed Data Packet transmitted by the network side device is lost, specifically, PDCP PDUs (Packet Data units) are lost, and the terminal does not receive the lost Data Packet, so that in the hfn=1 to hfn=2, the terminal cannot update the HFN, so that the HFN of the terminal and the HFN of the network side device are out of step; when hfn=2, the COUNT value of the terminal for decryption is not matched with the received compressed data packet, so that the compressed data packet cannot be decrypted correctly, resulting in that the decrypted data is a problematic invalid data packet, and the subsequent decompression processing of the decrypted compressed data packet is also erroneous, i.e. the decompression fails.
It should be noted that, besides the failure of decompression of the terminal caused by the out-of-sync HFN, SN jump, errors in the CRC field value of the compressed data packet, and other network side devices and/or terminal processing anomalies may cause decompression failure of the terminal, and the reasons for the decompression failure are not limited herein.
(5) Three modes of operation of the RLC layer
The RLC layer has three modes of operation: AM (Acknowledged Mode ), TM (Transparent Mode), UM (Unacknowledged Mode ).
When the RLC layer is configured as an AM, the RLC AM transmitting end needs to add additional information to the upper layer, and the RLC AM receiving end needs to send an RLC AM status report to the RLC AM transmitting end according to its receiving condition of the RLC PDU, so that the RLC AM transmitting end confirms that the RLC AM receiving end has correctly received the RLC PDU currently according to the status report, and the RLC AM receiving end has not correctly received the RLC PDU that needs to be retransmitted by the RLC AM transmitting end.
When the RLC layer is configured as UM, the RLC AM sender needs to add additional information to the upper layer, and the RLC AM receiver does not need to feed back an RLC AM status report to the RLC AM sender.
When the RLC layer is configured as TM, the RLC AM transmitting end does not need to add additional information to the upper layer, and directly performs transparent transmission.
Referring to fig. 6, fig. 6 is a schematic diagram of a communication processing method according to an embodiment of the present application, and specifically, as shown in fig. 6, in this scenario, a terminal 601 communicates with a network device 602 by using compressed data packets.
The network side device 602 is a compression end device, the terminal 601 is a decompression end device, or the terminal 601 is a compression end device, and the network side device 602 is a decompression end device. In this embodiment of the present application, the description is mainly directed to a scenario in which the network side device 602 is a compression end device and the terminal 601 is a decompression end device.
In this embodiment, when ROHC is enabled, the network side device 602 performs compression processing on the data packet according to the ROHC manner to obtain a compressed data packet. The network-side device 602 transmits the compressed data packet to the terminal 601.
After receiving the compressed data packet, the terminal 601 performs decompression processing on the compressed data packet in an ROHC manner, and if the number of continuous decompression failures meets a state reset condition, the terminal 601 performs state reset processing on the decompression end device and the compression end device; if decompression is successful, the terminal 601 may feed back a corresponding decompression success acknowledgement message to the network side device 602.
The specific process of the compression and decompression may be described with reference to fig. 1, fig. 2a, fig. 2b, and fig. 3, which are not described herein.
In the present embodiment, the terminal 601 includes, but is not limited to, an access terminal, a subscriber unit, a subscriber Station, a Mobile Station (MS), a remote Station, a remote terminal, a Mobile device, a subscriber terminal, a terminal device (Terminal Equipment), a wireless communication device, a user agent, or a user equipment. The terminal 601 may also be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, abbreviated WLL) station, a personal digital assistant (Personal Digital Assistant, abbreviated PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in other 4G networks, a terminal device in future 5G networks or a terminal device in future evolved public land mobile network (Public Land Mobile Network, abbreviated PLMN), or the like with wireless communication capabilities.
In this embodiment, the network-side device 602 may be a base station, where the base station includes, but is not limited to, a device that provides a base station function in a 2G network, such as: base transceiver stations (english: base Transceiver Station, BTS for short), devices in 3G networks that provide base station functionality, such as: node B (NodeB), a device providing base station functionality in a 4G network, such as: an Evolved NodeB (eNB) is a device that provides a base station function in a wireless local area network (Wireless Local Area Networks, WLAN for short), such as: an Access Point (AP) provides a device Gnb with a base station function in a New air interface (New Radio, NR), and a node B (ng-eNB) that continues to evolve, where the Gnb and the terminal communicate using NR technology, the ng-eNB and the terminal communicate using E-UTRA (Evolved Universal Terrestrial Radio Access ) technology, and both the Gnb and the ng-eNB may be connected to a 5G core network. The base station in the embodiment of the present application also includes a device or the like that provides a base station function in a new communication system in the future.
Referring to fig. 7, fig. 7 is a schematic flow chart of a communication processing method according to an embodiment of the present application, and the present disclosure provides the method operation steps described in the embodiment or the flowchart, but may include more or less operation steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When the terminal or the storage medium product in practice is executed, it may be executed sequentially or in parallel according to the method shown in the embodiment or the drawings. As shown in fig. 7, the communication processing method is applied to a decompression end device, and the method includes:
S701: and when the robust header compression ROHC is enabled, responding to decompression failure of the first compressed data packet by the decompression end device, and counting the number of times of decompression failure.
If the number of decompression failures determined by the counting process satisfies the state reset condition, step S702 is executed.
S702: and (3) resetting the states of the decompression end device and the compression end device.
In the embodiment of the application, when the number of decompression failures of the decompression end device meets the state reset condition, the state reset processing of the decompression end device and the compression end device is automatically triggered and executed, so that the accuracy of the decompression processing of the decompression end device can be improved, wireless transmission resources are saved, and communication abnormality between the terminal and the network side device caused by the long-time decompression failure is avoided.
Referring to fig. 8, fig. 8 is an interactive flow chart of a communication processing method according to an embodiment of the present application, where the method operation steps described in the examples or the flow chart are provided, but more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When the terminal or the storage medium product in practice is executed, it may be executed sequentially or in parallel according to the method shown in the embodiment or the drawings. As shown in fig. 8, the method includes:
S801: and when the robust header compression ROHC is enabled, the compression end equipment performs compression processing on the data to generate a compressed data packet.
In this embodiment of the present application, the decompression end device is a terminal, and the compression end device is a network side device. The data may be delivered to the PDCP layer of the compression end device by an upper layer of the compression end device, and then step S801 is performed at the PDCP layer of the compression end device.
The compression end device performs other processing on the data in addition to the compression processing, and the content of performing other processing is described with reference to fig. 1, fig. 2a, fig. 2b, and fig. 3, which are not described herein.
When the robust header compression ROHC is enabled, the compression end device performs compression processing on the data, and the method comprises the following steps: compression processing is performed on the data in the ROHC manner.
In an embodiment of the present application, the generating a compressed data packet includes: a first compressed data packet is generated.
In an embodiment of the present application, the generating the compressed data packet may further include: a second compressed data packet is generated.
The compression end device may generate more compressed data packets in addition to the first compressed data packet and the second compressed data packet, and the number of the generated compressed data packets is not limited.
S802: the compression end device sends compressed data packets.
The compression end device may occupy certain wireless transmission resources, such as: bandwidth resources, and sends compressed data packets to decompression end devices.
In an embodiment of the present application, the sending a compressed data packet includes: and sending the first compressed data packet.
In this embodiment of the present application, the sending the compressed data packet may further include: and sending the second compressed data packet.
It should be noted that, the compression end device may send more compressed data packets in addition to the first compressed data packet and the second compressed data packet, that is, the compression end device may correspondingly send the generated compressed data packets.
S803: and the decompression end device receives the first compressed data packet.
S804: and the decompression end device executes decompression processing on the first compressed data packet.
The decompression side device performs other processing on the first compressed data packet in addition to the decompression processing on the first compressed data packet, and the content of the other processing is described with reference to fig. 1, 2a, 2b and 3, which are not described herein.
If the decompression end device fails to decompress the first compressed data packet, when the robust header compression ROHC is enabled, step S805 is executed in response to the decompression end device failing to decompress the first compressed data packet.
S805: the decompression terminal equipment counts the number of times of decompression failure;
in this embodiment of the present application, the counting the number of decompression failures includes: the number of decompression failures is accumulated 1 time.
The number of decompression failures is used to represent the accumulated number of decompression failure results of the decompression end device on different compressed data packets, for example: the decompression end device continuously fails to decompress two different compressed data packets, and then accumulates the times of decompression failure for 2 times.
When the number of decompression failures is counted, the decompression failures of the same compressed data packet are accumulated for 1 time only.
In the embodiment of the present application, the decompression side device may set a counter to perform counting processing on the number of times that the decompression fails by the counter execution.
Before the terminal does not start to perform the counting process, the number of decompression failures is initialized to 0, that is, the count value of the counter is initialized to 0, the counter accumulates the number of continuous decompression failures of the decompression terminal device, and if the decompression is successful, the count value of the counter needs to be cleared.
If the number of decompression failures determined by the counting process satisfies the state reset condition, step S806 is performed.
If the number of times of decompression failure determined by the counting process does not satisfy the state resetting condition and the second compressed data packet is received, step S807 is executed.
The operations of the compression end device generating the second compressed data packet, the compression end device transmitting the second compressed data packet, the decompression end device receiving the second compressed data packet, and the like are not limited to being performed before step S805, as long as they are performed before the decompression processing of the second compressed data packet is performed, that is, before step S807 is performed.
In this embodiment of the present application, the satisfaction of the state reset condition refers to that the number of times of decompression failure determined by the counting process reaches a threshold value of state reset.
The number of decompression failures reaching the threshold of state reset refers to the number of continuous decompression failures of different compressed data packets reaching the threshold of state reset.
S806: the decompression side device performs a state reset process for the decompression side device and the compression side device.
In this embodiment of the present application, the performing the state resetting process on the decompression side device and the compression side device has two modes:
The first way is: if data is transmitted between the decompression end device and the compression end device according to the unacknowledged mode UM, the decompression end device triggers the reconstruction of a communication link between the decompression end device and the compression end device, so that the decompression end device enters a non-context NC state of a unidirectional U mode, and the compression end device enters an initialized refresh IR state of the unidirectional U mode.
In this embodiment of the present application, the transmitting data between the decompression side device and the compression side device according to the unacknowledged mode UM means that RLC layers of the decompression side device and the compression side device are both configured as UM.
In this embodiment of the present invention, the PDCP layer of the terminal may send an event for indicating that the number of decompression failures determined by the counting process satisfies a state reset condition to the RRC (Radio Resource Control, radio resource control layer) layer of the terminal, and the RRC layer of the terminal may send RRC reestablishment request information to the network side device according to the event, and the network side may feed back corresponding reestablishment information to the terminal according to the received RRC reestablishment request information, so as to reestablish a communication link between the terminal and the network side device.
After reestablishing a communication link between a terminal and network side equipment, the terminal will first enter an NC state of a U mode, and the network side equipment will first enter an IR state of the U mode; therefore, the HFNs of the terminal and the network side device are initialized, so as to realize the synchronization of the HFNs of the terminal and the network side device, and reduce the decompression failure of the terminal caused by the out-of-sync HFNs.
The second way is: and if data is transmitted between the decompression end device and the compression end device according to the confirmation mode AM, the decompression end device executes Release processing so that the decompression end device enters a non-context NC state of the unidirectional U mode, and the compression end device enters an initialized refresh IR state of the unidirectional U mode.
In this embodiment of the present application, the transmitting data between the decompression side device and the compression side device according to the acknowledged mode AM means that RLC layers of the compression side device and the compression side device are both configured to be AM.
In this embodiment of the present application, because the decompression end device is a terminal, the performing Release processing by the decompression end device means that the terminal performs local Release processing.
The decompressing end device executes Release processing, including:
the terminal releases the current RRC connection locally;
after the terminal releases the current RRC connection locally, the terminal may also initiate an RRC connection establishment procedure through a TAU (Tracking Area Update ) to reestablish a communication link between the terminal and the network side device.
After the terminal executes the local Release processing, the terminal can firstly enter an NC state of a U mode, and the network side equipment can firstly enter an IR state of the U mode; therefore, the HFNs of the terminal and the network side device are initialized, so as to realize the synchronization of the HFNs of the terminal and the network side device, and reduce the decompression failure of the terminal caused by the out-of-sync HFNs.
S807: the decompression side device performs decompression processing on the second compressed data packet.
The decompression end device executes the decompression processing of the second compressed data packet in the same manner as the decompression processing of the first compressed data packet; the decompression end device performs other processing on the second compressed data packet in addition to the decompression processing on the second compressed data packet, and the manner in which the decompression end device performs other processing on the second compressed data packet is the same as that in which the decompression end device performs other processing on the first compressed data packet, which is not described herein.
In this embodiment of the present application, the first compressed data packet corresponds to a current compressed data packet, and the second compressed data packet corresponds to a next compressed data packet to be decompressed after the current compressed data packet is decompressed.
If the decompression of the second compressed data packet is successful, step S808 is performed.
If the decompression of the second compressed data packet fails, the second compressed data packet is taken as a new first compressed data packet, and step S805 is executed.
If the new first compressed data packet fails to be decompressed, after the count processing is performed on the number of times of the decompression failure, the count processing determines that the number of times of the decompression failure does not meet the condition of state reset, and other compressed data packets are received, the other compressed data packets are taken as new second compressed data packets, step S807 is performed, and the cycle is performed until the number of times of the decompression failure determined by the count processing meets the condition of state reset, and step S806 is performed.
S808: the decompression end device clears the number of decompression failures determined by the counting process.
In this embodiment of the present application, the number of decompression failures determined by the counting process is a positive integer, for example: and 3, when the decompression end equipment successfully decompresses any compressed data packet, resetting the number of decompression failures determined by the counting process, namely updating the number of decompression failures to 0.
In this embodiment of the present application, after clearing the number of decompression failures determined by the counting process, if other compressed data packets are received, for example: and step S804, if the third compressed data packet is a new first compressed data packet, the other compressed data packets are used as new first compressed data packets.
If the new first compressed data packet fails to be decompressed, after the count processing is performed on the number of times of the decompression failure, the number of times of the decompression failure determined by the count processing does not satisfy the condition of the state reset, and the new compressed data packet is received, the new compressed data packet is taken as a new second compressed data packet, step S807 is performed, and the cycle is performed until the number of times of the decompression failure determined by the count processing satisfies the condition of the state reset, and step S806 is performed.
In the embodiment of the application, if the decompression end device fails to decompress any compressed data packet, counting the number of times of decompression failure; if the decompression end device successfully decompresses any compressed data packet, resetting the number of decompression failures determined by the counting process. That is, if the number of consecutive decompression failures reaches the threshold value of the state reset, the state reset processing for the decompression side device and the compression side device is triggered to be executed.
In the embodiment of the application, when the number of continuous decompression failures meets the state reset condition, the terminal automatically triggers and executes the state reset processing on the terminal and the network side equipment, so that the accuracy of the terminal decompression processing can be improved, wireless transmission resources are saved, and abnormal communication between the terminal and the network side equipment caused by long-time decompression failures is avoided.
Referring to fig. 9, fig. 9 is a schematic structural diagram of a communication processing device according to an embodiment of the present application, and specifically as shown in fig. 9, the communication processing device includes: a storage 901 and a processor 902; and the communication processing device may further comprise a data interface 903, a user interface 904. Connections between the various hardware may also be made through various types of buses.
Through the data interface 903, the communication processing device may exchange data with other devices such as a terminal and a server; the user interface 904 is configured to enable human-machine interaction between a user and the communication processing device; the user interface 904 may provide a touch display screen, physical keys, or the like to enable human-machine interaction between a user and the communication processing device.
The storage 901 may include a Volatile Memory (RAM), such as a Random-Access Memory (RAM); the storage device 901 may also include a Non-Volatile Memory (Non-Volatile Memory), such as a Flash Memory (Flash Memory), a Solid-State Drive (SSD), etc.; the storage 901 may also include a combination of the above types of memories.
The processor 902 may be a central processing unit (Central Processing Unit, CPU). The processor 902 may further comprise a hardware chip. The hardware chip may be an Application-specific integrated circuit (ASIC), a programmable logic device (Programmable Logic Device, PLD), or the like. The PLD may be a Field programmable gate array (Field-Programmable Gate Array, FPGA), general array logic (Generic Array Logic, GAL), or the like.
Corresponding to the case that the communication processing device is a decompression end device:
the storage 901 is configured to store program codes;
the processor 902 is configured to, when the stored code is called, perform counting processing on the number of times of decompression failure in response to the decompression failure of the decompression end device on the first compressed data packet when robust header compression ROHC is enabled;
and if the number of decompression failures determined by the counting process meets the state reset condition, executing state reset processing on the decompression end device and the compression end device.
In one embodiment, the satisfaction of the state reset condition refers to the count process determining that the number of decompression failures reaches a threshold value of state reset.
In one embodiment, the processor 902 is further configured to perform, after the counting the number of times of decompression failure, if the number of times of decompression failure determined by the counting process does not meet the state reset condition and the second compressed data packet is received, performing decompression processing on the second compressed data packet;
and if the second compressed data packet is successfully decompressed, resetting the number of times of decompression failure determined by the counting process.
In one embodiment, the processor 902 is further configured to receive the first compressed data packet before counting the number of times that decompression fails;
and performing decompression processing on the first compressed data packet.
In one embodiment, the processor 902 is specifically configured to accumulate the number of decompression failures 1.
In one embodiment, the processor 902 is specifically configured to trigger, if data is transmitted between the decompression side device and the compression side device according to the unacknowledged mode UM, to reconstruct a communication link between the decompression side device and the compression side device, so that the decompression side device enters a context-free NC state of the unidirectional U mode, and the compression side device enters an initialized refresh IR state of the unidirectional U mode.
In one embodiment, the processor 902 is specifically configured to perform Release processing if data is transferred between the decompression side device and the compression side device according to the acknowledged mode AM, so that the decompression side device enters a context-free NC state of the unidirectional U mode, and the compression side device enters an initialized refresh IR state of the unidirectional U mode.
In one embodiment, the decompression end device is a terminal, and the compression end device is a network side device.
Corresponding to the case that the communication processing device is a compression end device:
the storage 901 is configured to store program codes;
the processor 902 is configured to generate a first compressed data packet when the robust header compression ROHC is enabled when the stored code is invoked;
and sending the first compressed data packet.
In one embodiment, the processor 902 is further configured to generate a second compressed data packet;
and sending the second compressed data packet.
In one embodiment, the decompression end device is a terminal, and the compression end device is a network side device.
Referring to fig. 10, fig. 10 is a schematic structural diagram of a communication processing apparatus according to an embodiment of the present application; as shown in fig. 10, the communication processing apparatus includes:
A counting module 1001, configured to, when robust header compression ROHC is enabled, respond to a decompression failure of the first compressed data packet by the decompression end device, and count the number of times of decompression failure;
a resetting module 1002, configured to execute a state resetting process for the decompression side device and the compression side device if the number of times of decompression failure determined by the counting process satisfies a state resetting condition.
In one embodiment, the satisfaction of the state reset condition refers to the count process determining that the number of decompression failures reaches a threshold value of state reset.
In one embodiment, the communication processing apparatus further includes:
the decompression module is used for executing the decompression processing of the second compressed data packet if the number of times of decompression failure determined by the counting processing does not meet the state resetting condition and the second compressed data packet is received after the number of times of decompression failure is counted;
the counting module 1001 is further configured to clear the number of decompression failures determined by the counting process if the decompression of the second compressed data packet is successful.
In one embodiment, the communication processing apparatus further includes:
The receiving module is used for receiving the first compressed data packet before the number of times of decompression failure is counted;
the decompression module is used for executing decompression processing on the first compressed data packet.
In one embodiment, the counting module 1001 is specifically configured to accumulate the number of decompression failures for 1 time.
In one embodiment, the resetting module 1002 is specifically configured to trigger, if data is transmitted between the decompressing end device and the compressing end device according to the unacknowledged mode UM, to reconstruct a communication link between the decompressing end device and the compressing end device, so that the decompressing end device enters a context-free NC state of the unidirectional U mode, and the compressing end device enters an initialized refresh IR state of the unidirectional U mode.
In one embodiment, the reset module 1002 is specifically configured to perform Release processing if data is transferred between the decompression side device and the compression side device according to the acknowledged mode AM, so that the decompression side device enters a context-free NC state of the unidirectional U mode, and the compression side device enters an initialized refresh IR state of the unidirectional U mode.
In one embodiment, the decompression end device is a terminal, and the compression end device is a network side device.
Referring to fig. 11, fig. 11 is a schematic structural diagram of another communication processing apparatus according to an embodiment of the present disclosure; as shown in fig. 11, the communication processing apparatus includes:
a generating module 1101, configured to generate a first compressed data packet when robust header compression ROHC is enabled;
a sending module 1102, configured to send the first compressed data packet.
In one embodiment, the generating module 1101 is further configured to generate a second compressed data packet;
the sending module 1102 is further configured to send the second compressed data packet.
In one embodiment, the decompression end device is a terminal, and the compression end device is a network side device.
Accordingly, the embodiment of the present invention also provides a computer-readable storage medium for storing a computer program that causes a computer to execute the method described in any of steps S701 to S702 and steps S803 to S808 of the present application. It should be understood that the computer storage medium herein may include a built-in storage medium in the smart terminal, and may include an extended storage medium supported by the smart terminal. The computer storage medium provides a storage space that stores an operating system of the intelligent terminal. Also stored in the memory space are one or more instructions, which may be one or more computer programs (including program code), adapted to be loaded and executed by the processor. The computer storage medium may be a high-speed RAM Memory or a Non-Volatile Memory (Non-Volatile Memory), such as at least one magnetic disk Memory; optionally, at least one computer storage medium remote from the processor may be present.
Accordingly, the embodiment of the present invention also provides a computer-readable storage medium for storing a computer program that causes a computer to execute the method described in any of the embodiments in steps S801 to S802 of the present application. It should be understood that the computer storage medium herein may include a built-in storage medium in the smart terminal, and may include an extended storage medium supported by the smart terminal. The computer storage medium provides a storage space that stores an operating system of the intelligent terminal. Also stored in the memory space are one or more instructions, which may be one or more computer programs (including program code), adapted to be loaded and executed by the processor. The computer storage medium may be a high-speed RAM Memory or a Non-Volatile Memory (Non-Volatile Memory), such as at least one magnetic disk Memory; optionally, at least one computer storage medium remote from the processor may be present.
Accordingly, the embodiment of the present application further provides a communication processing system, where the communication processing system includes a first communication processing device and a second communication processing device, where the first communication processing device is configured to implement the method described in any embodiment of steps S701 to S702 and steps S803 to S808 of the present application, and the second communication processing device is configured to implement the method described in any embodiment of steps S801 to S802 of the present application.
The above disclosure is only a few examples of the present invention, and it is not intended to limit the scope of the present invention, but it is understood by those skilled in the art that all or a part of the above embodiments may be implemented and equivalents thereof may be modified according to the scope of the present invention.
Claims (12)
1. A communication processing method, applied to a decompression end device, the method comprising:
when robust header compression ROHC is enabled, responding to decompression failure of the decompression end device on the first compressed data packet, and counting the number of times of decompression failure;
and if the number of decompression failures determined by the counting process meets the state reset condition, executing state reset processing on the decompression end device and the compression end device, wherein the processing comprises the following steps: and if the data is transmitted between the decompression end device and the compression end device according to the unacknowledged mode UM, triggering the reconstruction of a communication link between the decompression end device and the compression end device, so that the decompression end device enters a non-context NC state of a unidirectional U mode, and the compression end device enters an initialized refresh IR state of the unidirectional U mode.
2. The method of claim 1, wherein the satisfaction of the state reset condition is that a number of decompression failures determined by the counting process reaches a threshold value of state reset.
3. The method of claim 1, wherein after counting the number of decompression failures, the method further comprises:
if the number of times of decompression failure determined by the counting process does not meet the state resetting condition and the second compressed data packet is received, executing the decompression process of the second compressed data packet;
and if the second compressed data packet is successfully decompressed, resetting the number of times of decompression failure determined by the counting process.
4. The method of claim 1, wherein prior to counting the number of decompression failures, the method further comprises:
receiving the first compressed data packet;
and performing decompression processing on the first compressed data packet.
5. The method of claim 1, wherein counting the number of decompression failures comprises:
the number of decompression failures is accumulated 1 time.
6. The method of claim 1, wherein the performing state reset processing for the decompression side device and compression side device further comprises:
And if data is transmitted between the decompression end device and the compression end device according to the confirmation mode AM, executing Release processing so that the decompression end device enters a non-context NC state of the unidirectional U mode, and the compression end device enters an initialized refresh IR state of the unidirectional U mode.
7. The method of any one of claims 1-6, wherein the decompression end device is a terminal and the compression end device is a network side device.
8. A communication processing method, applied to a compression end device, the method comprising:
generating a first compressed data packet when the robust header compression ROHC is enabled;
and sending the first compressed data packet.
9. A communication processing apparatus, characterized in that the communication processing apparatus comprises: a memory device and a processor, wherein the memory device is configured to store data,
the storage device is used for storing program codes;
the processor, when invoking the stored code, is operable to perform the method of any of claims 1-7, or to perform the method of claim 8.
10. A communication processing apparatus, characterized in that the communication processing apparatus comprises:
the counting module is used for responding to the decompression failure of the decompression end device to the first compressed data packet when the robust header compression ROHC is enabled, and counting the number of times of the decompression failure;
A reset module, configured to execute a state reset process for the decompression side device and the compression side device if the number of decompression failures determined by the counting process satisfies a state reset condition, where the reset module includes: and if the data is transmitted between the decompression end device and the compression end device according to the unacknowledged mode UM, triggering the reconstruction of a communication link between the decompression end device and the compression end device, so that the decompression end device enters a non-context NC state of a unidirectional U mode, and the compression end device enters an initialized refresh IR state of the unidirectional U mode.
11. A communication processing apparatus, characterized in that the communication processing apparatus comprises:
the generation module is used for generating a first compressed data packet when the robust header compression ROHC is enabled;
and the sending module is used for sending the first compressed data packet.
12. A computer readable storage medium for storing a computer program for causing a computer to perform the method of any one of claims 1-7 or to perform the method of claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311701780.8A CN117715109A (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311701780.8A CN117715109A (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
| CN202011331752.8A CN112333773B (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011331752.8A Division CN112333773B (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117715109A true CN117715109A (en) | 2024-03-15 |
Family
ID=74308539
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311701780.8A Pending CN117715109A (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
| CN202011331752.8A Active CN112333773B (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011331752.8A Active CN112333773B (en) | 2020-11-24 | 2020-11-24 | Communication processing method, device, apparatus and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN117715109A (en) |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101594290B (en) * | 2008-05-26 | 2011-11-30 | 中兴通讯股份有限公司 | Processing method and device for compressing context identification by a robust head |
| CN101998438B (en) * | 2009-08-17 | 2013-08-07 | 电信科学技术研究院 | Method and equipment for improving performance of PDCP (Packet Data Convergence Protocol) ROHC (Robust Header Compression) algorithm |
| CN102045132B (en) * | 2009-10-23 | 2014-04-30 | 华为技术有限公司 | Retransmission mechanism-based method and device for transmitting header compression data packet |
| CN102202347B (en) * | 2010-03-27 | 2014-12-10 | 中兴通讯股份有限公司 | Method and device for processing robust header compression (ROHC) service flow |
| US20150280905A1 (en) * | 2014-04-01 | 2015-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for detecting and correcting pdcp hyper frame number (hfn) desynchronization |
| CN106416356A (en) * | 2015-05-20 | 2017-02-15 | 华为技术有限公司 | Method, device and base station for processing uplink data packet |
| WO2017105077A1 (en) * | 2015-12-15 | 2017-06-22 | 엘지전자 주식회사 | User equipment and data reception method, and network node and data transmission method |
| CN108616880B (en) * | 2017-01-17 | 2022-07-29 | 中兴通讯股份有限公司 | Data transmission method, device and system |
| WO2019093828A1 (en) * | 2017-11-10 | 2019-05-16 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting and receiving data in wireless communication system |
| KR102472292B1 (en) * | 2018-01-10 | 2022-11-30 | 삼성전자 주식회사 | Method and apparatus for performing contention-based and non- contention-based beam failure recovery in a wireless communication system |
| CN110636507A (en) * | 2018-06-21 | 2019-12-31 | 华为技术有限公司 | Communication method and device |
| CN110062420B (en) * | 2019-04-26 | 2021-01-08 | 维沃移动通信有限公司 | Control method of ROHC state of ROHC (robust head compression protocol), terminal equipment and network equipment |
| CN111163081B (en) * | 2019-12-26 | 2022-04-22 | 展讯通信（上海）有限公司 | Data transmission method, device, equipment and storage medium |
-
2020
- 2020-11-24 CN CN202311701780.8A patent/CN117715109A/en active Pending
- 2020-11-24 CN CN202011331752.8A patent/CN112333773B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112333773A (en) | 2021-02-05 |
| CN112333773B (en) | 2023-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9544404B2 (en) | RoHC optimizations for burst losses | |
| KR101387537B1 (en) | A method for handling correctly received but header compression failed packets | |
| US11627510B2 (en) | Data processing method and apparatus, and computer storage medium | |
| US20080123655A1 (en) | Apparatus and method for transmitting/receiving ciphered packet in mobile communication system | |
| EP1686718A2 (en) | Method of CRC residue error detection and handling | |
| EP3186912B1 (en) | Method and apparatus for handling packet loss in mobile communication network | |
| CN111385268B (en) | Data packet header compression confirmation method and communication equipment | |
| US20150382395A1 (en) | Method For Recovering From PDCP HFN De-Synchronization For VoLTE Call And Data Failure In RLC Layer | |
| US10681108B2 (en) | Apparatus adapted for maintaining receiving data quality and method for receiving data | |
| CN111556506B (en) | Abnormal link processing method and equipment | |
| US20080101608A1 (en) | Method and apparatus for handling protocol error in a wireless communications system | |
| US20080148111A1 (en) | Method and apparatus for recovering protocol error in a wireless communications system | |
| US20080137574A1 (en) | Method and apparatus for handling data delivery in a wireless communications system | |
| WO2013001838A1 (en) | Reception device, transmission device, and feedback method | |
| KR20160035953A (en) | Method and apparatus of performing of call using long-term evolution system | |
| CN112333773B (en) | Communication processing method, device, apparatus and storage medium | |
| EP4311300A1 (en) | Data transmission method and apparatus | |
| CN111769914B (en) | Data communication method and storage medium | |
| US20080137687A1 (en) | Method and apparatus for handling reordering in a wireless communications system | |
| EP1947871A1 (en) | Method and apparatus for reordering of packets in PDCP layer of a wireless communications system | |
| CN114205262A (en) | Data processing method and related device | |
| Shah | IP header compression in the SGSN |
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 |