WO2014094446A1 - 数据的解压缩、解压缩处理方法及装置 - Google Patents
数据的解压缩、解压缩处理方法及装置 Download PDFInfo
- Publication number
- WO2014094446A1 WO2014094446A1 PCT/CN2013/081989 CN2013081989W WO2014094446A1 WO 2014094446 A1 WO2014094446 A1 WO 2014094446A1 CN 2013081989 W CN2013081989 W CN 2013081989W WO 2014094446 A1 WO2014094446 A1 WO 2014094446A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- decompressor
- decompressed
- synchronization
- context
- packet
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
Definitions
- the present invention relates to the field of communications, and in particular to a method and apparatus for decompressing and decompressing data.
- Background Art Due to limitations of physical conditions, a wireless link in a mobile communication system has a lower transmission rate and a higher bit error rate than a wired link.
- RObust Header Compress (ROHC) technology has been introduced.
- ROHC technology is the use of information redundancy between packets of traffic flows to transparently compress and decompress information in the packet headers between directly connected nodes.
- the Least Significant Bits (LSB) algorithm is an important algorithm in the ROHC technology. It is mainly used to compress the Master Sequence Number (MSN) information.
- ROHCv2 (RFC5225), the second version of ROHC technology, explicitly proposes packet stream decompression to support out-of-order delivery. It introduces the concept of Reorder-ratio, that is, the compressor can adjust the LSB P value in the transmission process to find a reasonable balance between robustness and compression efficiency, so as to achieve optimal transmission. quality.
- the relationship between the P value and the Reorder_ratio in the LSB algorithm can be seen in FIG. 1 , where p and k in FIG. 1 are natural numbers.
- the compressed data cannot be correctly identified by the decompressor.
- the upper layer application protocol carried by the underlying layer is a voice stream similar to the Real-time Transport Protocol (RTP), it will exhibit a certain degree of frame loss and delay, which greatly affects the communication quality.
- RTP Real-time Transport Protocol
- the decompressor detects the context out of synchronization, it can send a negative answer (Negative Acknowledge, NACK for short) or static negative feedback (STATIC_NACK).
- NACK Negative Acknowledge
- STATIC_NACK static negative feedback
- the compressor After receiving the NACK or STATIC_NACK negative feedback packets, the compressor will immediately send the initial refresh-dynamic part (IR_DYN) or initialization refresh (IR) to refresh the decompressor context.
- IR_DYN initial refresh-dynamic part
- IR initialization refresh
- the feedback packet sent by the decompressor is immediately received by the compressor. During the process, the compressor does not send any compressed packet, as shown in FIG. 2 . That is, the decompressor does not discard any compressed packets after sending the negative feedback packet.
- the passive feedback packet sent by the decompressor is delayed by the underlying link, during which the compressor still chooses to send the compressed packet normally. Since the context of the decompressor and the compressor has been out of sync at this time, these compressed packages cannot be properly decompressed, as shown in Figure 3.
- a data decompression method including: a decompressor sending feedback information for notifying a compressor of a synchronization context, wherein the feedback information is sent after the decompressor detects a context out of synchronization; After transmitting the feedback information, the decompressor buffers the subsequently received data packet to be decompressed; the decompressor receives the synchronization information sent by the compressor for synchronizing the context; and the decompressor decompresses the decompressed data packet according to the synchronization information.
- the decompressor decompresses the decompressed data packet according to the synchronization information, including: the decompressor decompresses the decompressed data packet in a sequence from the back to the front by using a sequence of receiving the data packets to be decompressed.
- the method further includes: when the number of buffered data packets to be decompressed reaches a predetermined number, or does not receive the synchronization information within a predetermined time period, clearing all cached data packets to be decompressed and stopping buffering subsequent reception. The packet to be decompressed.
- the decompressor before decompressing the decompressed data packet according to the synchronization information, the decompressor further includes: the decompressor verifies the synchronization information, where the verification synchronization information is used for decompressing the decompressed data packet.
- a data decompression processing method including: a compressor receiving feedback information of a synchronization context sent by a decompressor, wherein the feedback information detects a context loss in a decompressor Sending after the step; after receiving the feedback information, the compressor sends synchronization information for synchronizing the context to the decompressor, wherein the synchronization information is used to decompress the to-be-decompressed data packet buffered by the decompressor after transmitting the feedback information.
- a data decompressing apparatus located in a decompressor, comprising: a detecting module configured to detect whether a context is out of synchronization; and a sending module configured to detect a context out of synchronization in the detecting module Sending feedback information for notifying the compressor of the synchronization context; the cache module is configured to: after the sending module sends the feedback information, buffer the subsequently received data packet to be decompressed; and the receiving module is configured to receive the sent by the compressor for sending Synchronization information of the synchronization context; a decompression module, configured to decompress the data packet to be decompressed according to the synchronization information.
- the decompression module is configured to decompress the decompressed data packets in a sequence from the back to the front by using a sequence of receiving the data packets to be decompressed.
- the foregoing apparatus further includes: stopping the cache module, configured to clear all cached data packets to be decapsulated when the number of buffered data packets to be buffered reaches a predetermined number, or when synchronization information is not received within a predetermined time period And stop buffering the subsequently received data packet to be decompressed.
- the foregoing apparatus further includes: a verification module, configured to perform verification on the synchronization information, wherein the verification synchronization information is used to decompress the data packet to be decompressed.
- a data decompression processing apparatus including: a receiving module, configured to receive feedback information of a synchronization context sent by a decompressor, wherein the feedback information detects a context out of synchronization in a decompressor
- the sending module is configured to: after receiving the feedback information, send synchronization information for synchronizing the context to the decompressor, where the synchronization information is used to solve the to-be-decompressed data packet buffered by the decompressor after sending the feedback information. compression.
- the compressed packet received subsequently is buffered, and the compressed packet is decompressed according to the received synchronization information, and the solution is solved.
- the decompressor detects the context out-of-synchronization and sends the negative feedback information, the decompressor cannot correctly decompress the technical problems such as the subsequently received compressed packet, thereby effectively reducing the packet loss caused by the context out-of-step. Phenomenon, providing communication quality.
- FIG. 1 is a schematic diagram of a relationship between a P value and re0 rd er _ ra ti 0 in an LSB algorithm according to the related art
- FIG. 2 is a flowchart of a normal arrival of a negative feedback packet according to the related art
- FIG. 3 is a flowchart according to the related art.
- FIG. 4 is a flowchart of a method for decompressing data according to Embodiment 1 of the present invention
- FIG. 5 is a block diagram showing a structure of a data decompressing apparatus according to Embodiment 1 of the present invention
- FIG. 7 is a flowchart of a method for decompressing data according to Embodiment 2 of the present invention
- FIG. 8 is a flowchart of a method for decompressing data according to Embodiment 2 of the present invention
- FIG. 9 is a schematic flow chart of the process of delaying arrival of a passive feedback packet and enabling decompressor packet buffering and repairing according to an embodiment of the present invention
- FIG. 9 is a schematic flow chart of the process of delaying arrival of a passive feedback packet and enabling decompressor packet buffering and repairing according to an embodiment of the present invention
- FIG. 10 is a schematic diagram of opening a packet buffer according to Embodiment 3 of the present invention
- FIG. 11 is a flow chart of packet reception of a decompressor after the packet buffering and repair function is enabled according to Embodiment 3 of the present invention
- FIG. 12 is a flowchart of a packet decompressor according to Embodiment 3 of the present invention
- FIG. 13 according to an embodiment of the present invention
- packet cache is a flowchart of a repair process
- FIG. 14 according to an embodiment of the present invention is a process flow diagram buffer 3 is closed and repair packets.
- Example 1 This embodiment will be described from the viewpoint of the decompressor.
- 4 is a flow chart of a method of decompressing data according to Embodiment 1 of the present invention. As shown in FIG.
- Step S402 The decompressor sends feedback information for notifying a compressor of a synchronization context, where the feedback information is sent after the decompressor detects that the context is out of synchronization; and step S404, sending feedback information. Afterwards, the decompressor buffers the subsequently received data packet to be decompressed.
- Step S406 The decompressor receives the synchronization information sent by the compressor for synchronizing the context.
- Step S408 The decompressor decompresses the decompressed data packet according to the synchronization information.
- the feedback device is configured to send the feedback information for notifying the compressor to synchronize the context
- the subsequently received data packet to be decompressed is buffered, and the synchronization information for the synchronization context is fed back according to the compressor.
- the technical means for decompressing the data packet to be decompressed therefore, the occurrence of packet loss phenomenon is reduced to some extent, and the communication quality is further improved.
- step S402 can be expressed as the following implementation process:
- the decompressor When the decompressor supports out-of-order decompression and the current decompressor detects that the context has been out of synchronization, the decompressor initiates feedback information notifying the compressor of the synchronization context, for example for reflecting The decompressor fails to decompress or decompress the negative feedback information that is out of step. At this point, the decompressor can turn on the compressed packet cache and repair function, setting the variable Redecomp_Flag.
- step S404 may be embodied as the following implementation process in the specific implementation:
- the decompressor buffer and repair function is enabled, that is, when the Redecomp_Flag is set
- the decompressor waits for the synchronization context.
- the packet if it is sent negative feedback (NACK), waits for the IR_DYN packet, and if it sends static negative feedback (STATIC_NACK), it waits for the IR packet.
- NACK negative feedback
- STATIC_NACK static negative feedback
- the decompressor can cache other types of packets that cannot be properly decompressed. Once the context synchronization packet is received correctly, an attempt is made to repair the previously cached data.
- the decompressor decompresses the cached data packet to be decompressed.
- the decompressed data packet may be sequentially decompressed according to the sequence of receiving the data packet to be decompressed, or the decompressed data may be randomly solved. compression.
- the decompressor decompresses the decompressed data packets in order from the back to the front by using the order in which the data packets to be decompressed are received.
- the following forms of expression can be used: In the process of repairing the compressed package, reverse repair is performed. Generally, in the process of initiating negative feedback to receive the IR/IR_DYN packet, the domain that changes most in the packet flow is generally SN/TS/. IPID, for other domains, You can use the fields in the compressed package to be repaired or implicitly use the fields in the IR/IR_DYN package. Even if some compressed packages can be successfully repaired, in order to ensure the synchronization of the context, the package that finally updates the context must be just the IMR-DYN package.
- the maximum delay time can be set according to the upper application.
- the cached data is cleared, the cache and repair functions are turned off, and the above-mentioned identifier Redecomp_Flag is cleared to 0.
- the synchronization information may also be verified, where the synchronization information after verification is used to decompress the data packet to be decompressed. If the context synchronizer packet received by the decompressor is incorrect (ie, the check fails), the cache and repair process is discarded.
- a data decompression device is also provided, which is located in the decompressor, and is used to implement the above-mentioned embodiments and preferred embodiments, which have not been described again, and the following is involved in the device.
- the module to be explained. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function.
- FIG. 5 is a block diagram showing the structure of a data decompressing apparatus according to Embodiment 1 of the present invention. As shown in FIG. 5, the apparatus includes a detecting module 50 connected to the transmitting module 52, configured to detect whether the context is out of synchronization, and a sending module 52 connected to the cache module 54 and configured to detect when the detecting module 50 detects the context out of synchronization.
- the cache module 54 is connected to the decompression module 58 and configured to cache the subsequently received data packet to be decompressed after the sending module 52 sends the feedback information;
- the receiving module 56 is connected to the decompression module 58 and configured to receive synchronization information sent by the compressor for synchronizing the context.
- the decompression module 58 is configured to decompress the data packet according to the synchronization information.
- the decompression module 58 is configured to decompress the decompressed data packets in order from the back to the front by using the sequence of receiving the data packets to be decompressed.
- the foregoing apparatus further includes: stopping the cache module 60, setting the number of the data packets to be decompressed in the cache to reach a predetermined number, or When the synchronization information is not received within the time period, all the buffered data packets to be decompressed are cleared and the subsequent received data packets to be decompressed are stopped. In this embodiment, as shown in FIG.
- the foregoing apparatus may further include the following module: a verification module 62, configured to perform verification on synchronization information, where the synchronization information after verification is used to decompress the data packet Decompress.
- a verification module 62 configured to perform verification on synchronization information, where the synchronization information after verification is used to decompress the data packet Decompress.
- Embodiment 2 This embodiment corresponds to Embodiment 1 and will be described from the perspective of a compressor.
- 7 is a flow chart of a method of decompressing data according to Embodiment 2 of the present invention. As shown in FIG. 7, the method includes: Step S702: The compressor receives feedback information of a synchronization context sent by a decompressor, where the feedback information is sent after the decompressor detects that the context is out of synchronization; and step S704, receiving feedback information.
- the compressor sends synchronization information for synchronizing the context to the decompressor, where the synchronization information is used to decompress the to-be-decompressed data packet buffered by the decompressor after the feedback information is sent.
- the function of the compressor is improved to correspond to the function of the decompressor, thereby solving the problem that the decompressor cannot correctly decompress the subsequent receiving after detecting the context out of synchronization and sending the negative feedback information.
- the technical problem of the compressed package is further provided, and the device is located in a compressor, and is used to implement the foregoing method. As shown in FIG.
- the device includes: The receiving module 80 is connected to the sending module 82, and configured to receive feedback information of the synchronization context sent by the decompressor, where the feedback information is sent after the decompressor detects the context out-of-synchronization; the sending module 82 is configured to receive the feedback information. And sending synchronization information for synchronizing the context to the decompressor, where the synchronization information is used to decompress the to-be-decompressed data packet buffered by the decompressor after transmitting the feedback information.
- Embodiment 3 The main design idea of this embodiment is After the decompressor sends the negative feedback packet, the subsequent compressed packet is buffered.
- Step S902 When the negative feedback information (STATIC_NACK/NACK) sent by the decompressor does not reach the compressor, the compressor sends normally.
- Step S904 decompressing the compressed packet 1 and buffering the compressed packet 1 after the decompression fails; Step S906, the compressor sends the compressed packet 2 to the decompressor; Step S908, the decompressor decompresses the compressed packet 2, after the decompression fails Cache packet 2; Step S910, when the negative feedback information (STATIC_NACK/NACK) arrives at the compressor, the compressor sends the synchronization context information (ie, IR/IR_DYN packet 3) to the decompressor; step S912, the decompressor utilizes IR/IR_DYN The packet 3 repairs the cached compressed packet 1 and the compressed packet 2; in step S914, the compressed packet 1, the compressed packet 2, and the IMR_DYN packet 3 are sequentially delivered in order.
- FIG. 10 is a flow chart showing the function of enabling packet buffering and repairing according to Embodiment 3 of the present invention. As shown in FIG. 10, the process includes the following processing steps: Step S1002: Start the packet buffer and repair function flow starts, go to step S1004; Step S1004, if the decompressor detects the context out of synchronization and needs to initiate negative feedback, proceed to step S1006.
- step S1006 if the version of the ROHC supports the out-of-order decompression, the process goes to step S1008; otherwise, the process goes to step S1012; in step S1008, it is determined whether the compressed package buffer and the repair function are currently enabled, and the identifier Redecomp Flag is checked. If the Redecomp_Flag is 0, the process proceeds to step S1010. Otherwise, the process goes to step S1012; in step S1010, the decompressor needs to enable the packet buffer and repair function, set Redecomp_Flag to 1, and proceeds to step S1012; in step S1012, the process of starting the packet buffer and repair function ends.
- FIG. 1 the process of starting the packet buffer and repair function ends.
- Step S1102 After the packet buffering and repair function is enabled, the decompressor packet receiving process is started, and the process proceeds to step S1104.
- step S1104 if the packet buffering and repairing function is enabled, the Redecomp_Flag is set to 1, and the step is entered.
- step S1106 determines whether the currently received packet is the desired IR/IR_DYN, and if yes, proceeding to step S1108; otherwise, determining that the compressor has not received the negative feedback sent by the decompressor temporarily, the cache
- the currently received compressed packet proceeds to step S1114; step S1108, the IR/IR_DYN packet is decoded, and if the Cyclic Redundancy Check (CRC) check passes, the process proceeds to step S1112; otherwise, the context is considered
- the synchronization process fails, the compressed package buffering and repair process is aborted, and the process goes to step S1110; Step S1110, the packet buffering and repair process is closed, and the process goes to step S1116; Step S1112, the IR/IR_DYN packet is successfully received, and the packet repair process is performed, and the process proceeds to step S1116; S1114, the decompressor waits to receive the IR/IR_DYN packet, temporarily caches the compressed packet that cannot
- Step S1116 the decompressor packet receiving process after the packet buffering and repair function is enabled ends.
- the flow of the compressed packet buffering process in this embodiment is further described in detail below with reference to FIG. 12, as shown in FIG. 12, the process includes: Step S1202, the compressed packet buffering process starts, and proceeds to step S1204; Step S1204, determining whether the cache threshold is reached, that is, whether the packet buffering and repairing function can be continued, if the buffering can be continued, the process proceeds to step S1206; otherwise, the process proceeds to step S1208; and in step S1206, the currently received compressed data packet is cached, and the process proceeds to step S1210.
- Step S1208, the packet buffering and repairing function is closed, and the process proceeds to step S1210.
- step S1210 the compressed packet buffering process ends.
- the process includes: Step S1302: The cache packet repair process starts, and proceeds to step S1304; Step S1304, the closer the IR/IR_DYN packet is, the more likely the compressed package is to be repaired, and the compressed packets are decompressed in reverse order, and the steps are entered.
- Step S1306 Step S1306; Step S1306, determining whether the currently repaired cache compression packet can pass the CRC check, if the repair is successful, proceed to step S1308; otherwise, proceed to step S1310; Step S1308, determine whether there is a cache compression package to be repaired, if yes, enter Step S1304; otherwise, proceeding to step S1310; Step S1310, In the order of receiving the compressed packets, all the successfully repaired data packets are sent to the upper layer together with the IR/IR_DYN packet, and the process goes to step S1312; Step S1312, the current packet buffering and repairing operation is ended, and the process proceeds to step S1314; Step S1314, the successful decompression is used.
- Step S1402 The package buffering and repair process is started, and the process proceeds to step S1404; Step S1404, Emptying the cached compressed package, proceeds to step S1404; Step S1406, sets Redecomp_Flag to 0, closes the packet buffer and repair function, and proceeds to step S1408; In step S1408, the closing of the package buffer and the repair function ends.
- a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.
- the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.
- INDUSTRIAL APPLICABILITY The technical solution provided by the present invention can be applied to a process of decompressing data, and solves the related art. After the decompressor detects the context out of synchronization and sends the negative feedback information, the decompressor cannot correctly decompress the subsequent The technical problems such as the received compressed package effectively reduce the packet loss caused by the context out of synchronization and provide the communication quality.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Communication Control (AREA)
Abstract
本发明提供了一种数据的解压缩、解压缩处理方法及装置,其中,上述解压缩方法包括:解压器发送用于通知压缩器同步上下文的反馈信息,其中,该反馈信息在解压器检测到上下文失步后发送;在发送上述反馈信息后,解压器缓存后续接收到的待解压缩数据包;解压器接收压缩器发送的用于同步上下文的同步信息;解压器根据上述同步信息对待解压缩数据包进行解压缩。采用本发明提供的上述方案,有效地减少了因为上下文失步造成的丢包现象,提供了通信质量。
Description
数据的解压縮、 解压縮处理方法及装置
技术领域 本发明涉及通信领域, 具体而言, 涉及一种数据的解压缩、 解压缩处理方法及装 置。 背景技术 由于物理条件的限制,移动通信系统中的无线链路与有线链路相比传输速率较低, 误码率较高。为了能有效利用有限的无线信道带宽资源,引入了鲁棒性头压缩 (RObust Header Compress, 以下简称 ROHC) 技术。 ROHC技术的核心是利用业务流的分组之 间的信息冗余来透明的压缩和解压缩直接相连节点间的分组头中的信息。 最少有效位 (Least Significant Bits,简称为 LSB)算法是 ROHC技术中的重要算法, 它主要用于压缩主序列号 (Master Sequence Number, 简称为 MSN)信息。 LSB压缩算 法通过使用一个参考值 V_ref以及指定值 P, 将一个待压缩的, 占 kl比特位的值 A进 行 LSB压缩, 随后得到一个压缩后的, 占用更少比特位 k2 (k2<kl ) 的, 与 V_ref关 联的值 B。 通过 LSB压缩, 无变化的比特位被删除, B值所表示的即为从值 V_ref变 化到值 A的最低有效位 (即 B = A的低 k2位)。 采用 LSB解压缩将压缩后的值进行还 原的过程与上述过程相反。
ROHCv2 (RFC5225 ), 即 ROHC技术的第二个版本, 明确提出支持乱序投递的包 流解压缩。它引入了重排序比例(Reorder—ratio)的概念, 即压缩器可以在传输过程中, 通过调整 LSB P值大小, 在健壮性和压缩效率之间寻找合理的平衡点, 从而达到最优 的传输质量。 LSB算法中 P值与 Reorder_ratio之间的关系, 具体可以参见图 1所示, 其中, 图 1中的 p, k为自然数。 在数据传输过程中, 特别是在网络状况一般的场景, 底层总会出现一定概率的误 码及丢包, 这将会导致 ROHC层的压缩器和解压器的上下文在一定程度上失步。 如果 这个失步过程不及时修正, 压缩数据是无法被解压器正确识别的。 如果底层承载的上 层应用协议是类似于实时传输协议 (Real-time Transport Protocol, 简称为 RTP) 这样 的语音流, 则会表现出一定程度的丢帧和延时, 大大影响通信质量。 在存在反馈通道的场景, 当解压器检测到上下文失步时, 可以通过发送否定回答 (Negative Acknowledge, 简称为 NACK) 或者静态消极反馈 (STATIC_NACK) 来及
时通知压缩器主动同步上下文。压缩器在接收到 NACK或者 STATIC_NACK这两种消 极反馈包后则会立即发送初始刷新-动态部分 (IR_DYN)或者初始化刷新 (IR)来刷新解 压器的上下文。 存在下面两种场景, 其一, 解压器发送的反馈包被压缩器立即接收, 期间, 压缩器没有发送任何压缩包, 具体如图 2所示。 即解压器在发送消极反馈包后 没有丢弃任何压缩包。 其二, 解压器发送的消极反馈包被底层链路延迟了, 期间, 压 缩器仍然选择正常发送压缩包。 由于此时解压器和压缩器的上下文已经失步, 这些压 缩包是无法被正确解压的, 具体如图 3所示。 这些无法解压的压缩包会在一定程度上 影响整个包流的通信质量。 针对相关技术中的上述问题, 目前尚未提出有效的解决方案。 发明内容 针对相关技术中, 解压器在检测到上下文失步并发送完消极反馈信息后, 解压器 无法正确解压缩后续接收到的压缩包等技术问题, 本发明实施例提供了一种数据的解 压缩、 解压缩处理方法及装置, 以至少解决上述问题。 根据本发明的一个实施例, 提供了一种数据的解压缩方法, 包括: 解压器发送用 于通知压缩器同步上下文的反馈信息, 其中, 该反馈信息在解压器检测到上下文失步 后发送; 在发送上述反馈信息后, 解压器缓存后续接收到的待解压缩数据包; 解压器 接收压缩器发送的用于同步上下文的同步信息; 解压器根据上述同步信息对待解压缩 数据包进行解压缩。 优选地, 解压器根据同步信息对待解压缩数据包进行解压缩, 包括: 解压器利用 接收待解压缩数据包的先后顺序, 按照从后向前的顺序对待解压数据包进行解压缩。 优选地, 上述方法还包括: 在缓存的待解压缩数据包的数量到达预定数量, 或者 在预定时间段内未接收到同步信息时, 清空缓存的所有待解压缩数据包并停止缓存后 续接收的待解压缩数据包。 优选地, 解压器根据同步信息对待解压缩数据包进行解压缩之前, 还包括: 解压 器对同步信息进行校验, 其中, 校验通过后的同步信息用于对待解压缩数据包进行解 压缩。 根据本发明的另一个实施例, 提供了一种数据的解压缩处理方法, 包括: 压缩器 接收解压器发送的同步上下文的反馈信息, 其中, 反馈信息在解压器检测到上下文失
步后发送; 在接收到反馈信息后, 压缩器向解压器发送用于同步上下文的同步信息, 其中, 同步信息用于对解压器在发送反馈信息后缓存的待解压缩数据包进行解压缩。 根据本发明的又一个实施例, 提供了一种数据的解压缩装置, 位于解压器中, 包 括: 检测模块, 设置为检测上下文是否失步; 发送模块, 设置为在检测模块检测到上 下文失步时, 发送用于通知压缩器同步上下文的反馈信息; 缓存模块, 设置为在发送 模块发送反馈信息后, 缓存后续接收到的待解压缩数据包; 接收模块, 设置为接收压 缩器发送的用于同步上下文的同步信息; 解压缩模块, 设置为根据上述同步信息对待 解压缩数据包进行解压缩。 优选地, 上述解压缩模块, 设置为利用接收待解压缩数据包的先后顺序, 按照从 后向前的顺序对待解压数据包进行解压缩。 优选地, 上述装置还包括: 停止缓存模块, 设置为在缓存的待解压缩数据包的数 量到达预定数量, 或者在预定时间段内未接收到同步信息时, 清空缓存的所有待解压 缩数据包并停止缓存后续接收的待解压缩数据包。 优选地, 上述装置, 还包括: 校验模块, 设置为对同步信息进行校验, 其中, 校 验通过后的同步信息用于对待解压缩数据包进行解压缩。 根据本发明的再一个实施例, 提供了一种数据的解压缩处理装置, 包括: 接收模 块, 设置为接收解压器发送的同步上下文的反馈信息, 其中, 反馈信息在解压器检测 到上下文失步后发送; 发送模块, 设置为在接收到反馈信息后, 向解压器发送用于同 步上下文的同步信息, 其中, 同步信息用于对解压器在发送反馈信息后缓存的待解压 缩数据包进行解压缩。 通过本发明实施例,采用对解压器发送用于通知压缩器同步上下文的反馈信息后, 缓存后续接收到的压缩包, 并根据接收的同步信息对缓存的压缩包进行解压缩的技术 手段, 解决了相关技术中, 解压器在检测到上下文失步并发送完消极反馈信息后, 解 压器无法正确解压缩后续接收到的压缩包等技术问题, 从而有效地减少了因为上下文 失步造成的丢包现象, 提供了通信质量。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中-
图 1为根据相关技术的 LSB算法中 P值与 re0rder_rati0之间的关系示意图; 图 2为根据相关技术的消极反馈包正常抵达时的流程图; 图 3为根据相关技术的消极反馈包延迟抵达时的流程图; 图 4为根据本发明实施例 1的数据的解压缩方法的流程图; 图 5为根据本发明实施例 1的数据的解压缩装置的结构框图; 图 6为根据本发明实施例 1的数据的解压缩装置的另一结构框图; 图 7为根据本发明实施例 2的数据的解压缩处理方法的流程图; 图 8为根据本发明实施例 2的数据的解压缩处理装置的结构框图; 图 9为根据本发明实施例的消极反馈包延迟抵达且开启解压器包缓存及修复工作 的原理流程示意图; 图 10为根据本发明实施例 3的开启包缓存及修复功能流程图; 图 11 为根据本发明实施例 3 的开启包缓存及修复功能后的解压器的包接收流程 图; 图 12为根据本发明实施例 3的压缩包缓存处理流程图; 图 13为根据本发明实施例的对缓存包进行修复处理的流程图; 图 14为根据本发明实施例 3的关闭包缓存及修复功能的处理流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 考虑到相关技术中, 解压器在检测到上下文失步并发送完消极反馈信息后, 解压 器无法正确解压缩后续接收到的压缩包等技术问题, 以下结合实施例 1-3提供了相关 的解决方案, 现详细说明。 实施例 1
本实施例从解压器角度进行说明。 图 4为根据本发明实施例 1的数据的解压缩方 法的流程图。 如图 4所示, 该方法包括: 步骤 S402, 解压器发送用于通知压缩器同步上下文的反馈信息, 其中, 该反馈信 息在解压器检测到上下文失步后发送; 步骤 S404, 在发送反馈信息后, 解压器缓存后续接收到的待解压缩数据包; 步骤 S406, 解压器接收压缩器发送的用于同步上下文的同步信息; 步骤 S408, 解压器根据同步信息对待解压缩数据包进行解压缩。 通过上述处理步骤, 由于采用了解压器通过发送用于通知压缩器同步上下文的反 馈信息后, 缓存后续接收到的待解压缩数据包, 并根据压缩器反馈的用于同步上下文 的同步信息对该待解压缩数据包进行解压缩的技术手段, 因此, 在一定程度上减少了 丢包现象的发生, 进一步提高了通信质量。 在本实施例中,步骤 S402可以表现为以下实现过程: 当解压器支持乱序解压且当 前解压器检测到上下文已失步时, 解压器发起通知压缩器同步上下文的反馈信息, 例 如用于反映解压器解压缩失败或解压缩失步情况严重的消极反馈信息。 此时, 解压器 可以开启压缩包缓存及修复功能, 将变量 Redecomp_Flag置位。 与步骤 S402的上述具体实现过程相对应, 步骤 S404在具体实施时可以表现为以 下实现过程: 上述在解压器缓存及修复功能开启, 即 Redecomp—Flag置位的场合, 解 压器会等待同步上下文的包,如果之前发送的消极反馈(NACK),则等待 IR_DYN包, 如果发送的是静态消极反馈 (STATIC_NACK), 则等待 IR包。 在此过程中, 解压器 可以缓存其他类型无法正确解压的数据包。 一旦正确接收到上下文同步包, 则开始尝 试修复之前缓存的数据。 步骤 S408中,解压器对缓存的上述待解压缩数据包进行解压缩的方式有多种,例 如可以按照接收上述待解压缩数据包的先后顺序依次进行解压缩, 或者随机对待解压 缩数据进行解压缩。 考虑到在 LSB算法中, 在时间或位置上距离 IR或 IR_DYN越近 的数据包, 与 IR或 IR_DYN的关联性越强, 修复的成功率越高, 在本实施例的一个 优选实施方式中, 解压器利用接收待解压缩数据包的先后顺序, 按照从后向前的顺序 对待解压数据包进行解压缩。 具体可以采用以下表现形式: 在压缩包修复过程中, 采取倒序修复, 通常情况下, 在发起消极反馈到接收到 IR/IR_DYN包的过程中, 包流中变化最多的域一般是 SN/TS/IPID, 对于其他域而言,
可以显示的使用待修复压缩包中的域或者隐式的使用 IR/IR_DYN包中的域。即使一些 压缩包可以被成功修复, 为了保证上下文的同步性, 最终更新上下文的包一定只是 IMR—DYN包。 为了防止对上述待解压缩数据包的无限制缓存, 占用较多资源, 进而影响通信质 量, 在缓存的待解压缩数据包的数量到达预定数量, 或者在预定时间段内未接收到同 步信息时, 清空缓存的所有待解压缩数据包并停止缓存后续接收的待解压缩数据包。 具体可以表现为以下处理过程: 在解压器缓存及修复功能开启, 即 Redecomp—Flag置位的场合, 解压器会缓存无 法正确解压的数据包。可以通过设置缓存门限来打开或者关闭该算法。 比如, 方法一, 可以通过设置最大缓存包个数来避免无限制的缓存数据, 因为 ROHC—般承载的上层 应用是实时通信, 它不允许底层产生额外的延迟。 超过缓存门限数量还未收到 IR/IR_DYN, 清空已缓存的数据, 关闭该算法; 方法二, 可以根据上层应用, 设置最 大延迟时间。 当达到最大延迟时间还未收到 IR/IR_DYN时, 清空已缓存的数据, 关闭 缓存及修复功能, 同时将上述标识 Redecomp_Flag清 0。 在本实施例中, 解压器根据同步信息对待解压缩数据包进行解压缩之前, 还可以 对同步信息进行校验, 其中, 校验通过后的同步信息用于对待解压缩数据包进行解压 缩。如果解压器接收到的上下文同步包错误(即校验未通过), 则放弃此次缓存及修复 过程。 在本实施例中还提供了一种数据的解压缩装置, 该装置位于解压器中, 用于实现 上述实施例及优选实施方式, 已经进行过说明的不再赘述, 下面对该装置中涉及到的 模块进行说明。 如以下所使用的, 术语"模块"可以实现预定功能的软件和 /或硬件的组 合。 尽管以下实施例所描述的装置较佳地以软件来实现, 但是硬件, 或者软件和硬件 的组合的实现也是可能并被构想的。 图 5为根据本发明实施例 1的数据的解压缩装置 的结构框图。 如图 5所示, 该装置包括- 检测模块 50, 连接至发送模块 52, 设置为检测上下文是否失步; 发送模块 52, 连接至缓存模块 54, 设置为在检测模块 50检测到上下文失步时, 发送用于通知压缩器同步上下文的反馈信息; 缓存模块 54, 连接至解压缩模块 58, 设置为在发送模块 52发送反馈信息后, 缓 存后续接收到的待解压缩数据包;
接收模块 56,连接至解压缩模块 58, 设置为接收压缩器发送的用于同步上下文的 同步信息; 解压缩模块 58, 设置为根据同步信息对待解压缩数据包进行解压缩。 通过上述各个模块实现的功能, 和上述方法实施例类似, 同样可以在一定程度上 减少丢包现象的发生, 进一步提高通信质量。 在本实施例中,上述解压缩模块 58,设置为利用接收待解压缩数据包的先后顺序, 按照从后向前的顺序对待解压数据包进行解压缩。 在本实施例中, 为了防止无限制地缓存压缩包, 如图 6所示, 上述装置还包括: 停止缓存模块 60, 设置为在缓存的待解压缩数据包的数量到达预定数量, 或者在预定 时间段内未接收到同步信息时, 清空缓存的所有待解压缩数据包并停止缓存后续接收 的待解压缩数据包。 在本实施例中, 如图 6所示, 上述装置还可以包括以下模块: 校验模块 62, 设置 为对同步信息进行校验, 其中, 校验通过后的同步信息用于对待解压缩数据包进行解 压缩。 实施例 2 本实施例与实施例 1相对应, 从压缩器角度进行说明。 图 7为根据本发明实施例 2的数据的解压缩处理方法的流程图。 如图 7所示, 该方法包括: 步骤 S702, 压缩器接收解压器发送的同步上下文的反馈信息, 其中, 该反馈信息 在解压器检测到上下文失步后发送; 步骤 S704, 在接收到反馈信息后, 压缩器向解压器发送用于同步上下文的同步信 息, 其中, 该同步信息用于对解压器在发送所述反馈信息后缓存的待解压缩数据包进 行解压缩。 通过上述处理步骤, 对压缩器的功能作了改进, 从而与解压器的功能相对应, 进 而解决了解压器在检测到上下文失步并发送完消极反馈信息后, 解压器无法正确解压 缩后续接收到的压缩包的技术问题。 在本实施例中, 还提供了一种数据的解压缩处理装置, 该装置位于压缩器中, 用 于实现上述方法, 如图 8所示, 该装置包括:
接收模块 80,连接至发送模块 82, 设置为接收解压器发送的同步上下文的反馈信 息, 其中, 反馈信息在解压器检测到上下文失步后发送; 发送模块 82, 设置为在接收到反馈信息后, 向解压器发送用于同步上下文的同步 信息, 其中, 同步信息用于对解压器在发送所述反馈信息后缓存的待解压缩数据包进 行解压缩 实施例 3 本实施例的主要设计思想在于, 在解压器发送完消极反馈包后, 缓存后续收到的 压缩包, 待收到期望的 IR/IR_DYN包时, 重新倒序解压先前由于上下文失步从而导致 无法正确解压的压缩包。 最后, 尽可能多的将缓存中连续的可修复的压缩包投递给上 层处理, 从而将底层丢包对 ROHC层的影响降到最低, 提高上层应用的通信质量。 具 体可以参见图 9, 如图 9所示, 本实施例的主要设计思路包括以下处理步骤: 步骤 S902, 在解压器发送的消极反馈信息 (STATIC_NACK/NACK) 未抵达压缩 器时, 压缩器正常发送压缩包 1 ; 步骤 S904, 对压缩包 1进行解压, 解压失败后缓存压缩包 1 ; 步骤 S906, 压缩器向解压器发送压缩包 2; 步骤 S908, 解压器对压缩包 2进行解压, 解压失败后缓存包 2; 步骤 S910, 在上述消极反馈信息 (STATIC_NACK/NACK) 抵达压缩器时, 压缩 器向解压器发送同步上下文的信息 (即 IR/IR_DYN包 3 ); 步骤 S912, 解压器利用 IR/IR_DYN包 3修复缓存的压缩包 1和压缩包 2; 步骤 S914, 按顺序依次投递压缩包 1、 压缩包 2以及 IMR_DYN包 3。 图 10为根据本发明实施例 3的开启包缓存及修复功能流程图。 如图 10所示, 该 流程包括以下处理步骤: 步骤 S1002, 开启包缓存及修复功能流程启动, 进入步骤 S1004; 步骤 S1004, 如果解压器由于检测到上下文失步并且需要发起消极反馈, 进入步 骤 S1006; 否则, 解压器上下文和压缩器同步, 进入步骤 S1012;
步骤 S1006, 如果 ROHC的版本支持乱序解压, 进入步骤 S1008; 否则, 进入步 骤 S1012; 步骤 S1008 , 判断当前是否已经开启压缩包缓存及修复功能, 检查标识 Redecomp Flag, 如果 Redecomp_Flag为 0, 进入步骤 S1010; 否则, 进入步骤 S1012; 步骤 S1010, 解压器需要开启包缓存及修复功能, 将 Redecomp_Flag置为 1, 进 入步骤 S1012; 步骤 S1012, 开启包缓存及修复功能流程结束。 图 11 为根据本发明实施例 3 的开启包缓存及修复功能后的解压器的包接收流程 图。 如图 11所示, 该流程包括: 步骤 S1102,开启包缓存及修复功能后的解压器包接收流程启动,进入步骤 S1104; 步骤 S1104,如果开启包缓存及修复功能,即 Redecomp_Flag置 1,进入步骤 S1106; 否则, 进入步骤 S1116; 步骤 S1106, 判断当前接收到的包是否是期望的 IR/IR_DYN, 如果是, 进入步骤 S1108; 否则, 认为压缩器暂时还未收到解压器发送的消极反馈, 缓存当前接收到的压 缩包, 进入步骤 S1114; 步骤 S1108,解码 IR/IR_DYN包,如果循环冗余校验码(Cyclic Redundancy Check, 简称为 CRC) 校验通过, 进入步骤 S1112; 否则, 认为此次上下文同步过程失败, 放 弃压缩包缓存及修复过程, 进入步骤 S1110; 步骤 S1110, 关闭包缓存及修复过程, 进入步骤 S1116; 步骤 S1112, 成功接收 IR/IR_DYN包, 进行包修复过程, 进入步骤 S1116; 步骤 S1114, 解压器等待接收 IR/IR_DYN包, 暂时缓存无法解压的压缩包, 进入 步骤 S1116; 步骤 S1116, 开启包缓存及修复功能后的解压器包接收流程结束。 下面结合图 12对本实施例所涉及的压缩包缓存处理流程做进一步的详细描述,如 图 12所示, 该流程包括: 步骤 S1202, 压缩包缓存处理流程启动, 进入步骤 S1204;
步骤 S1204, 判断是否达到缓存门限, 即能否继续进行包缓存及修复功能, 如果 可以继续缓存, 进入步骤 S1206; 否则, 进入步骤 S1208; 步骤 S1206, 缓存当前收到的压缩数据包, 进入步骤 S1210; 步骤 S1208, 关闭包缓存及修复功能, 进入步骤 S1210; 步骤 S1210, 压缩包缓存处理流程结束; 下面结合图 13对本实施例涉及的缓存包修复处理流程做进一步的详细描述,如图 13所示, 该流程包括: 步骤 S1302, 缓存包修复处理流程启动, 进入步骤 S1304; 步骤 S1304, 由于越靠近 IR/IR_DYN包, 压缩包越可能被修复, 按照倒序的方式 解压所有缓存的压缩包, 进入步骤 S1306; 步骤 S1306, 判断当前修复的缓存压缩包能否通过 CRC校验, 如果修复成功, 进 入步骤 S1308; 否则, 进入步骤 S1310; 步骤 S1308, 判断是否存在待修复的缓存压缩包, 如果存在, 进入步骤 S1304; 否则, 进入步骤 S1310; 步骤 S1310, 按照压缩包的接收顺序, 将所有成功修复的数据包和 IR/IR_DYN包 一起投递给上层, 进入步骤 S1312; 步骤 S1312, 结束本次包缓存及修复操作, 进入步骤 S1314; 步骤 S1314, 使用成功解压的 IR/IR_DYN包更新解压上下文, 完成上下文同步过 程, 进入步骤 S1316; 步骤 S1316, 缓存包修复处理过程结束。 下面结合图 14 对本发明所涉及的关闭包缓存及修复处理流程做进一步的详细描 述, 如图 14所示, 该流程包括: 步骤 S1402, 关闭包缓存及修复流程启动, 进入步骤 S1404; 步骤 S1404, 清空已经缓存的压缩包, 进入步骤 S1404; 步骤 S1406,将 Redecomp_Flag置为 0,关闭包缓存及修复功能,进入步骤 S1408;
步骤 S1408, 关闭包缓存及修复功能结束。 通过上述实施例可以看出, 本发明实施例实现了以下有益效果: 在解压器发现上 下文失步时, 缓存一定数量的无法正确解压的压缩包, 待压缩解压上下文同步后, 再 次尝试解压缓存数据包, 从而最大程度上减少上下文同步过程中可能丢弃的压缩包, 以及将底层丢包对 ROHC层的影响降到最低, 在一定程度上改善上层应用程序的通信 质量。 在另外一个实施例中, 还提供了一种软件, 该软件用于执行上述实施例及优选实 施方式中描述的技术方案。 在另外一个实施例中, 还提供了一种存储介质, 该存储介 质中存储有上述软件, 该存储介质包括但不限于: 光盘、 软盘、 硬盘、 可擦写存储器 等。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技术人 员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的任何 修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。 工业实用性 本发明提供的技术方案, 可以应用于数据的解压缩处理过程中, 解决了相关技术 中, 解压器在检测到上下文失步并发送完消极反馈信息后, 解压器无法正确解压缩后 续接收到的压缩包等技术问题, 从而有效地减少了因为上下文失步造成的丢包现象, 提供了通信质量。
Claims
权 利 要 求 书 、 一种数据的解压缩方法, 包括:
解压器发送用于通知压缩器同步上下文的反馈信息, 其中, 所述反馈信息 在所述解压器检测到上下文失步后发送;
在发送所述反馈信息后, 所述解压器缓存后续接收到的待解压缩数据包; 所述解压器接收所述压缩器发送的用于同步上下文的同步信息; 所述解压器根据所述同步信息对所述待解压缩数据包进行解压缩。 、 根据权利要求 1所述的方法, 其中, 所述解压器根据所述同步信息对所述待解 压缩数据包进行解压缩, 包括:
所述解压器利用接收所述待解压缩数据包的先后顺序, 按照从后向前的顺 序对所述待解压数据包进行解压缩。 、 根据权利要求 1所述的方法, 其中, 还包括:
在缓存的所述待解压缩数据包的数量到达预定数量, 或者在预定时间段内 未接收到所述同步信息时, 清空缓存的所有待解压缩数据包并停止缓存后续接 收的待解压缩数据包。 、 根据权利要求 1至 3中任一项所述的方法, 其中, 所述解压器根据所述同步信 息对所述待解压缩数据包进行解压缩之前, 还包括:
所述解压器对所述同步信息进行校验, 其中, 校验通过后的所述同步信息 用于对所述待解压缩数据包进行解压缩。 、 一种数据的解压缩处理方法, 包括:
压缩器接收解压器发送的同步上下文的反馈信息, 其中, 所述反馈信息在 所述解压器检测到上下文失步后发送;
在接收到所述反馈信息后, 所述压缩器向所述解压器发送用于同步上下文 的同步信息, 其中, 所述同步信息用于对所述解压器在发送所述反馈信息后缓 存的待解压缩数据包进行解压缩。 、 一种数据的解压缩装置, 位于解压器中, 包括:
检测模块, 设置为检测上下文是否失步;
发送模块, 设置为在所述检测模块检测到所述上下文失步时, 发送用于通 知压缩器同步上下文的反馈信息;
缓存模块, 设置为在所述发送模块发送所述反馈信息后, 缓存后续接收到 的待解压缩数据包;
接收模块, 设置为接收所述压缩器发送的用于同步上下文的同步信息; 解压缩模块,设置为根据所述同步信息对所述待解压缩数据包进行解压缩。 、 根据权利要求 6所述的装置, 其中, 所述解压缩模块, 设置为利用接收所述待 解压缩数据包的先后顺序, 按照从后向前的顺序对所述待解压数据包进行解压 缩。 、 根据权利要求 6所述的装置, 其中, 还包括: 停止缓存模块, 设置为在缓存的 所述待解压缩数据包的数量到达预定数量, 或者在预定时间段内未接收到所述 同步信息时, 清空缓存的所有待解压缩数据包并停止缓存后续接收的待解压缩 数据包。 、 根据权利要求 6至 8中任一项所述的装置, 其中, 还包括:
校验模块, 设置为对所述同步信息进行校验, 其中, 校验通过后的所述同 步信息用于对所述待解压缩数据包进行解压缩。 0、 一种数据的解压缩处理装置, 包括:
接收模块, 设置为接收解压器发送的同步上下文的反馈信息, 其中, 所述 反馈信息在所述解压器检测到上下文失步后发送;
发送模块, 设置为在接收到所述反馈信息后, 向所述解压器发送用于同步 上下文的同步信息, 其中, 所述同步信息用于对所述解压器在发送所述反馈信 息后缓存的待解压缩数据包进行解压缩。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210557068.0 | 2012-12-20 | ||
CN2012105570680A CN103051434A (zh) | 2012-12-20 | 2012-12-20 | 数据的解压缩、解压缩处理方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014094446A1 true WO2014094446A1 (zh) | 2014-06-26 |
Family
ID=48063944
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/081989 WO2014094446A1 (zh) | 2012-12-20 | 2013-08-21 | 数据的解压缩、解压缩处理方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103051434A (zh) |
WO (1) | WO2014094446A1 (zh) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103051434A (zh) * | 2012-12-20 | 2013-04-17 | 中兴通讯股份有限公司 | 数据的解压缩、解压缩处理方法及装置 |
US9674803B2 (en) * | 2013-09-23 | 2017-06-06 | Qualcomm Incorporated | Out-of synchronization detection and correction during compression |
CN107645746B (zh) * | 2016-07-20 | 2021-03-16 | 深圳市中兴微电子技术有限公司 | 一种上下文更新方法、系统及设备 |
CN109217975A (zh) * | 2017-06-29 | 2019-01-15 | 大唐移动通信设备有限公司 | 一种数据处理方法和装置 |
CN109842905B (zh) * | 2017-11-28 | 2021-08-06 | 中国移动通信有限公司研究院 | 字典配置方法、网络侧设备及用户终端 |
CN111385263B (zh) * | 2018-12-29 | 2022-05-24 | 大唐移动通信设备有限公司 | 一种数据包头压缩信息的维护方法及通信设备 |
CN112333047B (zh) * | 2020-11-16 | 2022-04-26 | 展讯通信(上海)有限公司 | 数据传输方法、装置及设备 |
CN112469084B (zh) * | 2020-11-26 | 2023-03-07 | 展讯通信(上海)有限公司 | 数据传输方法、装置、设备、存储介质及程序产品 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1780296A (zh) * | 2004-11-26 | 2006-05-31 | 华为技术有限公司 | 一种快速恢复压缩解压缩上下文的方法 |
CN1816150A (zh) * | 2004-12-30 | 2006-08-09 | 微软公司 | 使用帧高速缓存来改善分组丢失恢复 |
CN102484643A (zh) * | 2009-07-08 | 2012-05-30 | 汤姆森特许公司 | 后向鲁棒性首标压缩接收器 |
CN103051434A (zh) * | 2012-12-20 | 2013-04-17 | 中兴通讯股份有限公司 | 数据的解压缩、解压缩处理方法及装置 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7924731B2 (en) * | 2004-11-15 | 2011-04-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for handling out-of-sequence packets in header decompression |
-
2012
- 2012-12-20 CN CN2012105570680A patent/CN103051434A/zh active Pending
-
2013
- 2013-08-21 WO PCT/CN2013/081989 patent/WO2014094446A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1780296A (zh) * | 2004-11-26 | 2006-05-31 | 华为技术有限公司 | 一种快速恢复压缩解压缩上下文的方法 |
CN1816150A (zh) * | 2004-12-30 | 2006-08-09 | 微软公司 | 使用帧高速缓存来改善分组丢失恢复 |
CN102484643A (zh) * | 2009-07-08 | 2012-05-30 | 汤姆森特许公司 | 后向鲁棒性首标压缩接收器 |
CN103051434A (zh) * | 2012-12-20 | 2013-04-17 | 中兴通讯股份有限公司 | 数据的解压缩、解压缩处理方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN103051434A (zh) | 2013-04-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014094446A1 (zh) | 数据的解压缩、解压缩处理方法及装置 | |
US20210144605A1 (en) | Method and apparatus for handling out-of-order packets during handover in a wireless communication system | |
US8572382B2 (en) | Out-of band authentication method and system for communication over a data network | |
Bormann et al. | RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed | |
US6985459B2 (en) | Early transmission and playout of packets in wireless communication systems | |
KR100800878B1 (ko) | 이동통신 시스템에서 사용자 데이터 프로토콜 체크섬을포함하는 음성패킷의 송수신 방법 및 장치 | |
US11159981B2 (en) | Congestion processing method and apparatus | |
JP2002541727A (ja) | 半確認付き再送信プロトコルに対するパケット破棄通知 | |
JP4936079B2 (ja) | セルラー通信ネットワークにおけるハンドオーバ中およびハンドオーバ後のヘッダ圧縮最適化方法 | |
KR20090031239A (ko) | 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법 | |
US20170222943A1 (en) | Method and apparatus for reordering | |
JP2003526970A (ja) | 可変容量無線データチャンネルのための無線リンクプロトコルフレーム整列機構 | |
TW201112688A (en) | Methods and systems for dynamic fragmentation of packets by communication network nodes | |
WO2009038312A2 (en) | A method for handling correctly received but header compression failed packets | |
KR20060107350A (ko) | 통신시스템에서 수신용 윈도우의 크기를 재구성하는 방법및 관련 장치 | |
KR20100106890A (ko) | 이동통신 시스템에서 데이터 중복 재전송에 따른 동작 방법 및 장치 | |
JP2002158712A (ja) | パケット・データ・システムでパケットをトンネルする方法と装置 | |
JP2006094518A (ja) | 無線通信システムにおけるsdu廃棄方法 | |
JP5069399B2 (ja) | 入力データパケットを転送および回復する方法および装置 | |
KR101578047B1 (ko) | 통신 시스템에서 데이터 패킷 재정렬 장치 및 방법 | |
WO2004110013A1 (ja) | パケット通信装置 | |
US20200344174A1 (en) | Radio link control (rlc) acknowledged mode (am) data reception | |
WO2012083762A1 (zh) | 数据传输方法、设备及系统 | |
WO2016106780A1 (zh) | 一种用户数据的传输方法、装置及终端 | |
US20080144490A1 (en) | Method and apparatus for providing voice communication service in a wireless communications system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13864937 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13864937 Country of ref document: EP Kind code of ref document: A1 |