CN101711043A - Method and device for destroying compression context in robustness header compression - Google Patents
Method and device for destroying compression context in robustness header compression Download PDFInfo
- Publication number
- CN101711043A CN101711043A CN200910252723A CN200910252723A CN101711043A CN 101711043 A CN101711043 A CN 101711043A CN 200910252723 A CN200910252723 A CN 200910252723A CN 200910252723 A CN200910252723 A CN 200910252723A CN 101711043 A CN101711043 A CN 101711043A
- Authority
- CN
- China
- Prior art keywords
- context
- compressed
- timestamp
- compression
- deletion
- 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
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for destroying the compression context in robustness header compression. The method comprises the following steps of: adding a time stamp in the compression context; updating the time stamp of the compression contest into the current time when the compression text is used; judging the time stamp of the current compression text; and deleting part of or all the compression contexts which are not used beyond a predetermined time. The method can destroy the contexts which are no longer in use for a long time in time and can ensure that a new context is established successfully.
Description
Technical field
The present invention relates to a kind of robustness header compression algorithm (the Robust HeaderCompression in moving communicating field, be called for short ROHC), relate in particular to a kind of destruction mechanism, comprising: contextual synchronous and implementation between time tag processing, destroying method, compressor reducer and the decompression machine of compressed context at compressed context.
Background technology
Because the restriction of physical condition, it is lower that the Radio Link in the mobile communication system and wire link are compared transmission rate, and the error rate is higher.In order effectively to utilize limited wireless channel width resource, introduced robustness head compression technology (Robust Header Compression is called for short ROHC).The core of ROHC is to utilize information redundancy between the grouping of Business Stream to come information in the packets headers between the direct connected node of compression and decompression pellucidly.
Context (Context) is important concept in the robustness head compression (ROHC), comprises that the compressed context reconciliation presses hereinafter.The current state information set that compressor reducer is used to compress is called compressed context; The current state information set that decompressor is used to decompress is called the decompress(ion) context.Context has comprised the relevant information of the some packets headers in same Bao Liuzhong front, as static fields, the compressed and decompressed incorporated by reference value of using etc.In addition, also comprise other information of describing bag stream in the context, as the variation pattern of IP message identification (IPID) field, change step, current state and pattern, the clock accuracy etc. of timestamp field.
ROHC supports that for the compression and the decompress(ion) that do not compress (UNCOMPRESSED), IP/UDP/RTP, IP/UDP, IP/ESP type packet packet, corresponding respectively framework (Profile) type is framework 0 (Profile0), framework 1 (Profile1), framework 2 (Profile2) and framework 3 (Profile3) at present.Only have a context for Profile0, then have one or more context for other Profile types, each context identifies by a context ID (Context Identifier is hereinafter to be referred as CID).All contexts under each Profile type all organize together with the form of chained list.
Corresponding all packet data package do not compressed of the context of ROHC Profile0 type, each context in other Profile types are then corresponding with a grouping bag stream.A grouping bag stream is determined by all critical fielies of this Bao Liuzhong (STATIC-DEF field).Such as bag stream, be to determine jointly by source address and destination address, the source port number of UDP part and the SSRC field of destination slogan and RTP part of its IPv4 part for IPv4/UDP/RTP.
The ROHC compressor reducer is after receiving an original packet data bag, need at first judge the affiliated Profile type of this grouping bag, then its search context under it in the context chained list of corresponding Profile type, if do not find then create a new context and its interpolation is entered in the chained list.If found corresponding context, field corresponding in each field in the current bag and the context is compared and encode, after the compressed package type that needs to send of making a strategic decision out, send according to the packet format encapsulation compressed package of expectation.
Only stipulated contextual effect, content and using method in the RFC3095 agreement at present, do not set forth for contextual destruction mechanism.And in the applied environment of reality, be limited owing to consult the operable CID of configuration space, and the context that does not re-use is not for a long time also destroyed, thus new context can't be created under the situation that causes using up in the CID space.
Summary of the invention
The technical problem to be solved in the present invention is, proposes to destroy in a kind of robustness head compression the method and apparatus of compressed context, in time long-term no context destroyed, and guarantees that new context can create success.
For solving the problems of the technologies described above, the present invention proposes to destroy in a kind of robustness head compression the method for compressed context, comprises step:
In compressed context, add timestamp, when using described compressed context, upgrade its timestamp and be the current time;
Judge the timestamp of the compressed context of current existence, deletion or all above the untapped compressed context of a Preset Time.
Further, the method for destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
After receiving an original packet bag, if do not find corresponding context, judge whether to also have enough Context identifier (CID) space to be used for creating new context earlier, if the space is enough, then creates new context and add timestamp; If insufficient space, then all or part of untapped compressed context of a Preset Time that surpasses of deletion earlier to be obtaining enough CID spaces, and then creates new context and add timestamp.
Further, the method for destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
During at deletion or all above the untapped compressed context of a Preset Time, be from the context of current existence, to search the oldest one of timestamp, calculate the time interval that this context is not used then, if should the time interval surpass described Preset Time, then, discharge the CID space with its deletion; Otherwise do not delete this context, adopt framework 0 (Profile0) type compression current grouped data bag.
Further, the method for destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
Deletion is all or part of surpass the untapped compressed context of a Preset Time after, the CID that uses according to the compressed context of described deletion creates new context.
Further, the method for destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
Described its timestamp that upgrades when using described compressed context comprised as the current time:
After receiving an original packet bag, if find corresponding context, the timestamp that then upgrades in the described context is the current time.
For solving the problems of the technologies described above, the present invention also proposes to destroy in a kind of robustness head compression the device of compressed context, comprises context management unit and context destruction unit, wherein:
Described context management unit adds timestamp in compressed context, upgrade its timestamp and be the current time when using described compressed context;
The unit destroyed in described context, judges the timestamp of the compressed context of current existence, deletion or all above the untapped compressed context of a Preset Time.
Further, the device of destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
Described context management unit, when knowing that compression set receives an original packet bag and do not find corresponding context, judge whether to also have enough Context identifier (CID) space to be used for creating new context,, then create new context and add timestamp if the space is enough; If insufficient space is notified described context to destroy the unit and is destroyed context;
The unit destroyed in described context, after receiving the contextual notice of destruction of sending described context management unit, deletes all or part of untapped compressed context of a Preset Time that surpasses.
Further, the device of destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
When the unit destroyed at deletion or all above the untapped compressed context of a Preset Time in described context, be from the context of current existence, to search the oldest one of timestamp, calculate the time interval that this context is not used then, if should the time interval surpass described Preset Time, then, discharge the CID space with its deletion; Otherwise do not delete this context, the notice compression set adopts framework 0 (Profile0) type compression current grouped data bag.
Further, the device of destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
Described context management unit, after described context was destroyed that element deletion is all or part of and surpassed the untapped compressed context of a Preset Time, the CID that uses according to the compressed context of described deletion created new context.
Further, the device of destruction compressed context also can have following characteristics in the above-mentioned robustness head compression:
Described context management unit, upgrade its timestamp and comprise as the current time when using described compressed context: after receiving an original packet bag, if find corresponding context, the timestamp that then upgrades in the described context is the current time.
Destroy the method and apparatus of compressed context in a kind of robustness head compression that the present invention proposes, have the following advantages:
But 1,, in time long-term no context is destroyed, guaranteed that new context can create success when there not being the new CID time spent;
2, can monitor contextual recent usage condition timely and effectively.
Description of drawings
Figure 1A, Figure 1B, Fig. 1 C mutual group become the method flow schematic diagram of destroying compressed context in a kind of robustness head compression of the embodiment of the invention;
Fig. 2 is a device block diagram of destroying compressed context in a kind of robustness head compression of the embodiment of the invention.
Embodiment
The basic design of destroying the compressed context scheme in the robustness head of the present invention compression is: all contexts that compressor reducer has been created all increase the mark of a timestamp, and all stab update time at every turn when using this context, uses this contextual time thereby record is the last.After the CID space of finding compressor reducer has exhausted, will not have the context of use to destroy above certain hour, thereby discharge the CID space of compressor reducer.The compressed package that sends the IR type simultaneously upgrades corresponding decompress(ion) context synchronously to decompression machine after decompression machine is received, keep synchronously with the context of guaranteeing both sides.
Be described in detail in the embodiment that adopts the context of the invention destruction scheme in the compression of robustness head below in conjunction with accompanying drawing.
Figure 1A, Figure 1B, Fig. 1 C mutual group become the method flow schematic diagram of destroying compressed context in a kind of robustness head compression of the embodiment of the invention, wherein Figure 1A is step S101～step S112 schematic diagram, Figure 1B is step S113～step S119 schematic diagram, and Fig. 1 C is step S120～step S128 schematic diagram.
Referring to Figure 1A, Figure 1B, Fig. 1 C, destroy the method for compressed context in a kind of robustness head compression of the embodiment of the invention, specifically comprise the steps:
Step S101: compression process begins, and enters step S102;
Step S102: compressor reducer receives original packet data package, enters step S103;
Step S103: compressor reducer is analyzed the Profile type under the current grouped data bag, enters step S104;
Step S104: compressor reducer is handled respectively according to the Profile type that analysis gets access to, if current Profile type is Profile0, enters step S105; If current Profile type is Profle1, enter step S109; If current Profile type is Profile2, enter step S110; If current Profile type is Profile3, enter step S111;
Step S105: directly use the context of Profile0, enter step S106;
Step S106:, enter step S107 according to the decision-making of the state in Profile0 context compressed package type;
Step S107: the corresponding compressed package of form encapsulation according to defining in the agreement enters step S108;
Step S108: send the compressed package that encapsulation is finished, enter step S128;
Step S109: in the context chained list of Profile1, search affiliated context according to the critical field in the current group bag, enter step S112;
Described critical field is static defining (STATIC-DEF) field;
Step S110: in the context chained list of Profile2, search affiliated context according to the critical field in the current group bag (STATIC-DEF field), enter step S112;
Step S111: in the context chained list of Profile3, search affiliated context according to the critical field in the current group bag (STATIC-DEF field), enter step S112;
Step S112: judge whether in corresponding chained list, to find corresponding context,, otherwise enter step S120 if enter step S113;
Step S113: the timestamp field of upgrading in the context is the current time, enters step S114;
Step S114: field contents in the current bag and the field contents in the context are compared, enter step S115;
Can adopt the method for RFC3095 protocol definition to compare, field identical in each field in the current group bag and the context be compared see if there is variation;
Step S115: adopt the coding method of stipulating in the agreement to encode according to comparative result to corresponding field, enter step S116;
Can adopt the method for RFC3095 protocol definition,, adopt the different coding method that defines in the agreement respectively according to the different needs that changes field at vicissitudinous field.Such as need adopt scale coding or time-based coding for the timestamp field, need adopt WLSB coding etc. for sequence-number field.
Step S116: the compressed package type that expectation sends according to information decisions such as coding result and present mode, states enters step S117;
Step S117: the effective compressed package type that judges whether successfully to make a strategic decision out is then to enter step S119, otherwise enters step S118;
Described effective bag type is meant the compressed package type that defines in the RFC3095 agreement.
Step S118: compressor reducer decision package type again after low state transition enters step S117;
Compressor reducer co-exists in three kinds of states, is IR (Initialization andRefresh, initialization is upgraded) state, FO (First Order) state, SO (Second Order) state from low to high successively according to rank.Compressor reducer changes to low state by high state and all is called to low state transition.Comprise from the SO state variation to the FO state, from the SO state variation to the IR state, from the FO state variation to the IR state.
Step S119: the corresponding compressed package of compressed package type package that goes out according to final decision sends, and enters step S128;
Step S120: judge whether the CID space uses up,, otherwise enter step S124 if enter step S121;
Step S121: from the context chained list of corresponding Profile, find the context that does not have use at most, enter step S122 according to the timestamp field;
Step S122: judge whether the time interval that this context is not used surpassed threshold value, be then to enter step S123, otherwise enter step S105;
Step S123: delete this context and discharge the CID space, enter step S124;
Step S124: create new context and add in the context chained list under the corresponding Profile type, enter step S125;
Step S125: the new context of creating of initialization is also stamped time stamp label, promptly notes contextual initialization time, enters step S126;
Step S126: the compressed package of encapsulation IR type sends, and enters step S127;
Step S127: decompression machine receives that IR type compressed package upgrades the decompress(ion) context later on, guarantees that both sides' context keeps entering step S128 synchronously;
Step S128: flow process finishes.
In order to realize said method, the embodiment of the invention also provides the device of destroying compressed context in a kind of robustness head compression, as shown in Figure 2, comprises context management unit 21 and context destruction unit 22, wherein:
Described context management unit 21 adds timestamp in compressed context, upgrade its timestamp and be the current time when using described compressed context;
Unit 22 destroyed in described context, judges the timestamp of the compressed context of current existence, deletion or all above the untapped compressed context of a Preset Time.
Further, described context management unit 21, when knowing that compression set receives an original packet bag and do not find corresponding context, judge whether to also have enough Context identifier (CID) space to be used for creating new context, if the space is enough, then creates new context and add timestamp; If insufficient space is notified described context to destroy unit 22 and is destroyed context; Unit 22 destroyed in described context, after receiving the contextual notice of destruction of sending described context management unit 21, deletes all or part of untapped compressed context of a Preset Time that surpasses.
Further, when unit 22 destroyed at deletion or all above the untapped compressed context of a Preset Time in described context, be from the context of current existence, to search the oldest one of timestamp, calculate the time interval that this context is not used then, if should the time interval surpass described Preset Time, then, discharge the CID space with its deletion; Otherwise do not delete this context, the notice compression set adopts framework 0 (Profile0) type compression current grouped data bag.
Further, described context management unit 21, described context destroy unit 22 deletion be all or part of surpass the untapped compressed context of a Preset Time after, the CID that uses according to the compressed context of described deletion creates new context.
Further, described context management unit 21, upgrading its timestamp when using described compressed context comprised as the current time: after receiving an original packet bag, if find corresponding context, the timestamp that then upgrades in the described context is the current time.
Be the preferred embodiments of the present invention only below, be not limited to the present invention, for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. destroy the method for compressed context during a robustness head compresses, it is characterized in that, comprise step:
In compressed context, add timestamp, when using described compressed context, upgrade its timestamp and be the current time;
Judge the timestamp of the compressed context of current existence, deletion or all above the untapped compressed context of a Preset Time.
2. destroy the method for compressed context in the robustness head compression as claimed in claim 1, it is characterized in that:
After receiving an original packet bag, if do not find corresponding context, judge whether to also have enough Context identifier (CID) space to be used for creating new context earlier, if the space is enough, then creates new context and add timestamp; If insufficient space, then all or part of untapped compressed context of a Preset Time that surpasses of deletion earlier to be obtaining enough CID spaces, and then creates new context and add timestamp.
3. destroy the method for compressed context in the robustness head compression as claimed in claim 1 or 2, it is characterized in that:
During at deletion or all above the untapped compressed context of a Preset Time, be from the context of current existence, to search the oldest one of timestamp, calculate the time interval that this context is not used then, if should the time interval surpass described Preset Time, then, discharge the CID space with its deletion; Otherwise do not delete this context, adopt framework 0 (Profile0) type compression current grouped data bag.
4. destroy the method for compressed context in the robustness head compression as claimed in claim 3, it is characterized in that:
Deletion is all or part of surpass the untapped compressed context of a Preset Time after, the CID that uses according to the compressed context of described deletion creates new context.
5. destroy the method for compressed context in the robustness head compression as claimed in claim 1, it is characterized in that described its timestamp that upgrades comprised as the current time when using described compressed context:
After receiving an original packet bag, if find corresponding context, the timestamp that then upgrades in the described context is the current time.
6. destroy the device of compressed context during a robustness head compresses, it is characterized in that, comprise context management unit and context destruction unit, wherein:
Described context management unit adds timestamp in compressed context, upgrade its timestamp and be the current time when using described compressed context;
The unit destroyed in described context, judges the timestamp of the compressed context of current existence, deletion or all above the untapped compressed context of a Preset Time.
7. destroy the device of compressed context in the robustness head compression as claimed in claim 6, it is characterized in that:
Described context management unit, when knowing that compression set receives an original packet bag and do not find corresponding context, judge whether to also have enough Context identifier (CID) space to be used for creating new context,, then create new context and add timestamp if the space is enough; If insufficient space is notified described context to destroy the unit and is destroyed context;
The unit destroyed in described context, after receiving the contextual notice of destruction of sending described context management unit, deletes all or part of untapped compressed context of a Preset Time that surpasses.
8. as destroying the device of compressed context in claim 6 or the 7 described robustness head compressions, it is characterized in that:
When the unit destroyed at deletion or all above the untapped compressed context of a Preset Time in described context, be from the context of current existence, to search the oldest one of timestamp, calculate the time interval that this context is not used then, if should the time interval surpass described Preset Time, then, discharge the CID space with its deletion; Otherwise do not delete this context, the notice compression set adopts framework 0 (Profile0) type compression current grouped data bag.
9. destroy the device of compressed context in the robustness head compression as claimed in claim 8, it is characterized in that:
Described context management unit, after described context was destroyed that element deletion is all or part of and surpassed the untapped compressed context of a Preset Time, the CID that uses according to the compressed context of described deletion created new context.
10. destroy the device of compressed context in the robustness head compression as claimed in claim 6, it is characterized in that:
Described context management unit, upgrade its timestamp and comprise as the current time when using described compressed context: after receiving an original packet bag, if find corresponding context, the timestamp that then upgrades in the described context is the current time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910252723A CN101711043A (en) | 2009-12-02 | 2009-12-02 | Method and device for destroying compression context in robustness header compression |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910252723A CN101711043A (en) | 2009-12-02 | 2009-12-02 | Method and device for destroying compression context in robustness header compression |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101711043A true CN101711043A (en) | 2010-05-19 |
Family
ID=42403796
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910252723A Pending CN101711043A (en) | 2009-12-02 | 2009-12-02 | Method and device for destroying compression context in robustness header compression |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101711043A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101977402A (en) * | 2010-10-19 | 2011-02-16 | 中兴通讯股份有限公司 | Method and device for reusing context in robustness header compression |
| WO2016101453A1 (en) * | 2014-12-22 | 2016-06-30 | 中兴通讯股份有限公司 | Method and device for compressing time stamp |
| CN106332179A (en) * | 2015-06-30 | 2017-01-11 | 展讯通信（上海）有限公司 | Message compensation method and mobile terminal |
| CN107273761A (en) * | 2017-06-15 | 2017-10-20 | 深圳天珑无线科技有限公司 | data compression method and device, decompression method and device |
| CN111507072A (en) * | 2019-01-31 | 2020-08-07 | 瑞昱半导体股份有限公司 | Compression end and decompression end based on robust header compression and data processing method thereof |
-
2009
- 2009-12-02 CN CN200910252723A patent/CN101711043A/en active Pending
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101977402A (en) * | 2010-10-19 | 2011-02-16 | 中兴通讯股份有限公司 | Method and device for reusing context in robustness header compression |
| WO2016101453A1 (en) * | 2014-12-22 | 2016-06-30 | 中兴通讯股份有限公司 | Method and device for compressing time stamp |
| CN105791228A (en) * | 2014-12-22 | 2016-07-20 | 中兴通讯股份有限公司 | Method and device for compressing timestamp |
| CN105791228B (en) * | 2014-12-22 | 2019-12-03 | 中兴通讯股份有限公司 | A kind of method and apparatus of compression time stamp |
| CN106332179A (en) * | 2015-06-30 | 2017-01-11 | 展讯通信（上海）有限公司 | Message compensation method and mobile terminal |
| CN106332179B (en) * | 2015-06-30 | 2019-10-25 | 展讯通信（上海）有限公司 | A kind of message compression method and mobile terminal |
| CN107273761A (en) * | 2017-06-15 | 2017-10-20 | 深圳天珑无线科技有限公司 | data compression method and device, decompression method and device |
| CN111507072A (en) * | 2019-01-31 | 2020-08-07 | 瑞昱半导体股份有限公司 | Compression end and decompression end based on robust header compression and data processing method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101674315B (en) | Method and device for compressing and decompressing timestamp | |
| FI107000B (en) | Title compression in real-time services | |
| EP2724505B1 (en) | Header compression with a code book | |
| EP2512099B1 (en) | Message compression methods and apparatuses | |
| EP2854359B1 (en) | Compression and decompression methods of ethernet header and corresponding devices | |
| CN101977402B (en) | Method and device for reusing context in robustness header compression | |
| CN103369593B (en) | A kind of method compressing reconciliation compressed ethernet message and network element device | |
| CN102118792B (en) | Method and device for transmitting data packets | |
| US20070242703A1 (en) | Binding/combining of plural telecommunications functions | |
| CN101523733B (en) | Message compression | |
| CN101711043A (en) | Method and device for destroying compression context in robustness header compression | |
| TW201002016A (en) | Methods and systems for dynamically configuring and managing communication network nodes at the MAC sublayer | |
| US20070242683A1 (en) | Plural telecommunications functions having sharing transaction(s) | |
| CN100433841C (en) | Robustness header compression/decompression method for MIPv6 | |
| CN102694730B (en) | Method and device for parallel processing | |
| CN100379297C (en) | Apparatus and associated method for facilitating deletion of dictionary content pursuant to communication of signaling protocal messages | |
| CN104811265B (en) | The packaging method and de-encapsulation method of base band frame | |
| US8160060B2 (en) | System and method for transferring data using variance based messaging | |
| CN110651457B (en) | Method, apparatus, and medium for learning compression/decompression context | |
| CN112165409A (en) | Port management method, system, device and readable storage medium | |
| EP3257235B1 (en) | A method and apparatus for data mediation | |
| CN103746930B (en) | A kind of improved method of arrowband serial link TCP message header suppression | |
| WO2023231428A1 (en) | Ipv4 packet encapsulation method, electronic device, and computer storage medium | |
| WO2011160350A1 (en) | Method and apparatus for key updating in multimedia broadcast system | |
| CN102202347A (en) | Method and device for processing robust header compression (ROHC) service flow |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20100519 |