WO2012022157A1

WO2012022157A1 - Transmission control method and device in robust header compression system

Info

Publication number: WO2012022157A1
Application number: PCT/CN2011/072755
Authority: WO
Inventors: 朱永升; 杜高鹏; 张鹏帅
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-08-16
Filing date: 2011-04-13
Publication date: 2012-02-23
Also published as: CN102378258A

Abstract

A transmission control method and device in a Robust Header Compression (ROHC) system are disclosed by the present invention. The method includes that: a sending side sends an indication message of needing to release context to a receiving side; in response to the indication message, the receiving side releases its own context and returns an indication message of successful release to the sending side; in response to the indication message returned from the receiving side, the sending side releases its own context. The present invention enables that two devices using the ROHC service release the same context. With the present invention, the use efficiency and the transmission efficiency of context are improved effectively, the negotiation state in which the ROHC system always processes CONTEXT is avoided, and the utilization ratio of the wireless communication bandwidth is improved.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a transmission control method and apparatus in a robust head compression system. BACKGROUND In a wireless communication system, a large amount of overhead is transmitted in a service data packet header. In particular, for the same service flow, packet header information transmitted between consecutive packets occupies a large amount of bandwidth, resulting in low network bandwidth utilization. For valuable air interface bandwidth resources, it is a great waste. Robust Header Compression (ROHC) technology is used to send static i in the service data packet header or only once at the beginning of service establishment. Other dynamic domain applications are used. The compression encoding method sends partial bytes, and removes redundant information in the packet header, thereby effectively improving system bandwidth utilization. The ROHC technology can be applied to various communication systems. As shown in FIG. 1, the user equipment 10 and the network side device 12 use ROHC technology to implement data transmission, and the network side device includes a base station 120, a base station controller 122, etc., ROHC technology. These devices are integrated separately, such as user equipment, network side equipment, etc., and these devices use ROHC technology to realize data transmission. In the two-way communication system, a compressor (Compressor) and a decompressor (Decompressor) module are integrated in each device of the ROHC system, and the information required for compressing/decompressing the packet header is stored in the context (CONTEXT), and each CONTEXT corresponds to A corresponding CONTEXT ID (CID for short) identifier. The process of data transmission between two devices can be seen in FIG. 2. In FIG. 2, the compressor is integrated in the user equipment 10 as shown in FIG. 1. The decompressor is integrated in the base station 12, and includes the following during data transmission. Step 4:

S20: The compressor sends context information to the decompressor to synchronize the context between the compressor and the decompressor.

S22: The decompressor feeds back information to the compressor; adjusts its working state and working mode through the feedback information compressor and the decompressor.

S24: Both parties transmit the compressed data stream. During the transmission process, if the context loses synchronization, continue synchronization and execute S24. S26: The compressor sends context information to the decompressor to synchronize the context between the compressor and the decompressor.

S28: Both parties transmit the compressed data stream. In the above transmission process, the CONTEX of the context needs to be updated in real time. Otherwise, the CONTEX of the compressor and the decompressor will be inconsistent, resulting in failure of decompression of the data packet. After the service flow returns to the efficient compression state, it takes a certain time. Both the compressor and the decompressor negotiate the correct CONTEXT, during which the traffic is in an unstable state or inefficient compression state. Since the CID of the ROHC in the device is limited by the CID space, when the CONTEXT ID is exhausted, if there is a new service that needs to implement ROHC processing, a CID must be assigned to the service flow to identify CONTEXT, because there is a sender and a receiver. The party does not know which CIDs are being applied in the business and which CIDs are not applied in the business. If the reused CID is still performing ROHC services, it will affect the current ROHC processing of the service. For example, when the service has a packet to process, it again needs to reuse the CID. Repeatedly, it will greatly reduce the efficiency of ROHC; make the ROHC system always handle the CONTEX negotiation status, and reduce the bandwidth utilization of the wireless communication. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a transmission control method and apparatus in a robust header compression system to address at least the above-mentioned negotiation state in which the CID application is in the service because the sender and the receiver do not know which CID applications are in the service. , resulting in lower efficiency of the ROHC system. According to an aspect of the present invention, a transmission control method in a robust header compression system is provided, including: a sender sends an indication message that needs to release a context to a receiver; and the receiver responds to the indication message to release its own context, And returning to the sender an indication message that the release is successful; the sender responds to the indication message from the receiver reply, and releases its own context. Preferably, the indication message carries a context identifier corresponding to the context; the process of releasing the context of the sender or the receiver by the sender includes: releasing the corresponding context according to the context identifier. Preferably, before the releasing, the method further includes: the receiving party determining whether the context exists, and if yes, performing the releasing operation, and the indicating message that the sending party is successful in releasing the release If not, the releasing operation is not performed, and the step of reporting the indication message that the release is successful to the sender is performed. Preferably, after the receiving party determines that the context exists, the method further includes: the receiving party determining whether to allow the context to be released, and if yes, performing a subsequent context step of releasing the self; if not, the The receiving direction responds to the sender with an indication message that the release failed. Preferably, the initiator sends the indication message that needs to release the context to the receiver after the service is interrupted or the timer expires; the step of determining whether to allow the context to be released includes: determining the service Whether interrupt or timer expires; if yes, release is allowed, if no, release is not allowed. Preferably, the initiating party responding to the indication message of the release failure further includes: the initiator recording the current release process as abnormal information in a log. According to another aspect of the present invention, a transmission control apparatus in a robust header compression system is provided, including: a transmitting end and a receiving end, the transmitting end comprising: a sending module, configured to send an indication message that needs to release a context to a receiving end, configured to respond to a release success message from the receiving end, and release its own context; the receiving end includes: a second release module, configured to respond to the sending module Instructing the message to release its own context; and replying to the sending end the indication message that the release is successful. Preferably, the sending end further includes: a first identifier module, configured to control the sending module to add a context identifier corresponding to the context in the indication message; and controlling the first release module to release according to the context identifier The receiving end further includes: a second identifying module, configured to control the second releasing module to release the corresponding context according to the context identifier. Preferably, the receiving end further includes: a first determining module, configured to determine whether the receiving end has the context before the second releasing module performs an operation, and if yes, triggering the second releasing module Executing the operation of releasing the corresponding context, performing the step of returning the indication message to the sender to release the release success message; if not, triggering the second release module to perform the step of reporting the release message to the sender end. Preferably, the receiving end further includes: a second determining module, configured to: after the first determining module determines that the receiving end has the context, determine whether to allow the context to be released, and if yes, allow the The first judging module continues to perform the operation; if not, the first judging module is controlled to stop the operation; and the sending end replies with the indication message that the release fails. Preferably, the sending end further includes: a log module, configured to record the release process as abnormal information in the log in response to the release failure indication message from the receiving end. The present invention implements two devices that use ROHC services to release the same context. Through the invention, the context use efficiency and the transmission efficiency are effectively improved, and the ROHC system is prevented from always processing the CONTEX negotiation state, thereby improving the wireless communication bandwidth utilization rate. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a network environment of a ROHC application in the related art; FIG. 2 is a flowchart of implementing ROHC services between a compressor and a decompressor in the prior art; FIG. 3 is a first embodiment of the present invention. Figure 4 is a flow chart showing the success of releasing the context in the second embodiment of the present invention; Figure 5 is a format diagram of the indication message sent in the second embodiment of the present invention; Figure 6 is a release context in the second embodiment of the present invention; FIG. 7 is a flowchart of Embodiment 3 of the present invention; FIG. 8 is a block diagram showing the structure of a device according to Embodiment 4 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The first embodiment of the present invention is described in detail below. Embodiment 1 of the present invention is applied to the user equipment 10 and the base station 120 shown in FIG. 1, and a compressor and a decompressor are respectively integrated in the user equipment 10 and the base station 120. In the first embodiment, the user equipment 10 acts as a sender and the base station 120 acts as a receiver. Referring to the flow chart shown in Figure 3, the following steps are included: S30: The sender sends an indication message that needs to release the context to the receiver. The indication message sent by the sender includes the context that needs to be released together by the receiver, so that the subsequent sender sends the message.

S32: The receiver responds to the indication message, releases its own context, and replies to the sender with an indication message of consent release. The receiving party may follow the indication message, when the context exists, release the context requested to be released in the indication message, and reply the sender with the indication message agreeing to release.

S34: The sender responds to the above indication message from the receiver and releases its own context. The sender responds to the indication message replied by the receiver, releasing the context. After step 4 in the foregoing embodiment 1, the sender and the receiver simultaneously release the same context, and use the released context for subsequent ROHC services, thereby improving ROHC working efficiency and wireless communication bandwidth utilization. In various embodiments of the present invention, in the process of implementing the ROHC service by the compressor and the decompressor, the compressor may trigger the indication message of the release context to be triggered by various conditions. For example: due to the current service interruption, the context is out of synchronization, the timer needs to resynchronize the context or the user's command is received after the timer expires. At this time, the decompressor also needs to determine whether it needs to release the context, if necessary, Then release; if the context does not need to be released, an indication message is sent to the compressor indicating that the context cannot be released. The following is a detailed description of the second embodiment. In the second embodiment, the compressor is integrated in the user equipment 10 as shown in FIG. 1. The decompressor is integrated in the base station 120. Referring to the flowchart shown in FIG. 4, the following Steps:

S400: A compressed data stream is transmitted between the compressor and the decompressor.

S402: The compressor is triggered, and the decision needs to release the context. The compressor in the user device 10 may be triggered by various conditions to initiate an instruction to release the context. For example: The situation is lost due to the current service interruption, the situation is resynchronized due to the timer timeout, the CID is not available in the CID space, or the user's command is received.

S404: The compressor sends an indication message of releasing the context to the decompressor. By adding a feedback option type feedback between the compressor and the decompressor of the ROHC system, using the indication message of mutual interaction, the option carried in the feedback information is added, which indicates that the compressor and the decompressor complete the CONTEX synchronization release that is no longer used, thereby The corresponding CID in the CID space can be used to add new services. The specific feedback options are shown in Table 1: Table 1

Table 1 shows the new context release option CONTEXT-RELEASE-NOTIFY, which asks the receiver to release the corresponding context and feed back information about the options. When the message carries this option, the receiver that processes the feedback will release the CONTEX corresponding to the CONTEXT ID carried in the feedback packet. If the operation succeeds, the system sends the context release success option CONTEXT to the sender. -RELEASE-SUCC's feedback · 艮 ,, otherwise return the message 4 with the context release failure CONTEXT-RELEASE-FAIL option. In this step, the compressor sends a release indication message containing CONTEXT-RELEASE-NOTIFY to the decompressor, and carries a corresponding CID in the release indication message to instruct the decompressor to release the corresponding context. The format of the message can be seen in Figure 5, where 11110 in the 4 表示 text is represented as the feedback 4 ; text; if code (code) =0, the size indicates the subsequent length of the message; if the small CID space is used and the CID is not 0 , Add-CID octet (increased context identifier octet) appears; if large CID space is used, large CID (encoding (encoding);); Add-CID or large CID field gives the CONTEXT ID information to be released ; The value of feedback i or is: CONTEXT-RELEASE-NOTIFY

CONTEXT-RELEASE-SUCC

CONTEXT-RELEASE-FAIL

S406: The decompressor judges that the context can be released. The decompressor releases the context according to the release indication message, and judges that the context that needs to be released is established due to a condition such as a service interruption or a timer timeout.

S408: The decompressor sends an indication message that the context release succeeds to the compressor. After the decompressor successfully releases the context, the decompressor sends an indication message that the release is successful to the compressor. The message is in the form of a feedback 4 艮 and carries the context release success option CONTEXT-RELEASE-SUCC.

S410: The compressor releases its own context in response to the instruction that the decompressor is successfully released. After the above steps, the process of synchronizing the same context is implemented between the compressor and the decompressor, and the compressor can use this context to transfer data in subsequent steps. In the above process, if the decompressor judges that the context cannot be released, the compressor is notified, and the compressor does not release the context. The following is explained in conjunction with FIG. 6. Referring to FIG. 6, in the flow shown in FIG. 6, the method includes:

S600: A compressed data stream is transmitted between the compressor and the decompressor.

S602: The compressor is triggered, and the decision needs to release the context.

S604: The compressor sends an indication message of releasing the context to the decompressor. In this step, the compressor sends a release indication message containing CONTEXT-RELEASE-NOTIFY to the decompressor, and carries a corresponding CID in the release indication message to instruct the decompressor to release the corresponding context.

S606: The decompressor determines that the context cannot be released. The decompressor according to the release indication message determines that the context to be released is being applied in the service if the condition of the service terminal or the timer expires is not established, and the context cannot be released.

S608: The decompressor sends an indication message that the context release fails to the compressor. The decompressor sends an indication message that the release failed to the compressor. The message is in the form of a feedback message and carries the context release failure option CONTEXT-RELEASE-FAIL.

S610: The compressor responds to the instruction that the decompressor fails to release, and does not release its own context. Through the flow in Figure 6, the decompressor sends a message to the compressor that the release failed when the context cannot be released, so that the compressor can reselect the context to be released or perform other steps. In the second embodiment, the decompressor performs the step of releasing the context after the judgment is made, and promptly notifies the compressor after deciding whether to release, so that the compressor can perform the subsequent steps. To further illustrate the present invention, the flow of the present invention will be described below through the third embodiment. In the third embodiment, the ROHC A terminal in FIG. 7 is integrated in the user equipment 10 as shown in FIG. 1, and the ROHC B terminal is integrated in the base station 120. And a compressor and a decompressor are respectively integrated in the ROHC A end and the ROHC B end, and the flow chart shown in FIG. 7 includes the following steps:

S700: After the ROHC A end is triggered, the context needs to be released. Such as business interruption, or timer timeout and other reasons. S702: The ROHC A end constructs a feedback message containing the CONTEXT-RELEASE-NOTIFY option. The message is a release context indication message.

S704: The ROHC A end sends the feedback message to the ROHC B end through the feedback channel.

S706: The ROHC B end receives the release indication message containing the feedback message.

S708: The ROHC B end parses the feedback message and parses the CONTEXT-RELEASE-NOTIFY option, indicating that the ROHC B side needs to release the corresponding context.

S710: The ROHC B determines whether there is a corresponding context according to the CID in the release indication message. If yes, step S712 is performed, otherwise step S711 is performed.

S711: The ROHC B-end constructs an instruction message indicating that the release of the CONTEXT-RELEASE-SUCC option is successful, and executes S720.

S712: The ROHC B terminal determines whether the corresponding context is allowed to be released; if yes, performs step M1 S714; if not, performs step 4 S718. S714: The ROHC B-end constructs an indication message indicating that the CONTEXT-RELEASE-SUCC option is successfully released, and executes S 716.

S716: The ROHC B end releases the corresponding context and executes S720.

S718: The ROHC B end constructs an indication message indicating that the CONTEXT-RELEASE-FAIL option is successfully released, and executes S720.

S720: The ROHC B end sends an indication message to the ROHC A terminal in the form of a feedback message.

S722: The ROHC A end receives the indication message from the ROHC B end feedback, and performs one of the following steps S724 or S728.

S724: ROHC A terminal solution The option in the feedback 4艮 text is CONTEXT-RELEASE-SUCC.

S726: The ROHC A end releases the corresponding context according to the CID.

S728: ROHC A terminal solution The option in the feedback 4艮 text is CONTEXT-RELEASE-FAIL.

S730: The ROHC A end does not operate the context corresponding to the CID, and the release process is recorded as an abnormal information in the log. In the third embodiment, the process of releasing the context between two devices implementing the ROHC service is explained in detail. The transmission of the message and indication message between the ROHC A end and the ROHC B end is also implemented by its internal integrated compressor or decompressor. After receiving the indication message, by determining whether there is a context corresponding to the CID, it is avoided that the system is faulty because the abnormality of the context corresponding to the CID is not found. Maximize the reuse of CONTEXT ID information by both ROHCs, and affect the business flow, improve the stability of the system, and enable the ROHC compressor and decompressor to work in an efficient state and optimal mode to effectively increase system bandwidth. Utilization rate. The various embodiments of the method of the present invention have been described in detail above. The method of the present invention may be separately integrated into a user equipment or network device by various structural forms, or may be integrated with a compressor or a decompressor. The structure of the preferred embodiment 4 is described in detail below. Referring to FIG. 8, the apparatus includes: a transmitting end 80 and a receiving end 82; the transmitting end 80 includes: The sending module 800 is configured to send an indication message that needs to release the context to the receiving end. The first releasing module 802 is configured to respond to the release success indication message replied from the receiving end 82, and release its own context. The receiving end 82 includes: The second release module 804 is configured to release its own context in response to the indication message from the sending module 800; and reply the sending terminal 80 with an indication message that the release is successful. Preferably, the sending end 80 further includes: a first identifying module 806, configured to control the sending module 800 to add a context identifier of the corresponding context in the indication message; and controlling the first releasing module 802 to release the corresponding context according to the context identifier; The method includes: a second identity module 808, configured to control the second release module 804 to release the corresponding context according to the context identifier. Preferably, the method further includes: the sending end 80 further comprising: a first identifying module 806, configured to control the sending module 800 to add a context identifier of the corresponding context in the indication message; and controlling the first releasing module 802 to release the corresponding context according to the context identifier; The terminal 82 further includes: a second identity module 808, configured to control the second release module 804 to release the corresponding context according to the context identifier. Preferably, the receiving end 82 further includes: a first determining module 810, configured to determine whether the receiving end has a context before the second releasing module 804 performs an operation, and if yes, triggering the second releasing module 804 to perform an operation of releasing the corresponding context. The step of performing an indication message that the response to the release is successful is sent to the sender; if not, the step of triggering the second release module 804 to perform an indication of the successful release of the release to the sender is performed. Preferably, the receiving end 82 further includes: a second determining module 812, configured to: after the first determining module determines that the receiving end has a context, determine whether the context is allowed to be released, and if yes, allow the first determining module to continue performing the operation; No, the first judgment module is controlled to stop the operation; and the indication message of the release failure is returned to the sender. Preferably, the sending end 80 further includes: a log module 814, configured to: after the sending module 800 sends the indication message of releasing the context, respond to the indication message of the release failure from the receiving end, and record the release process as the abnormal information in the ambition . In the foregoing apparatus, the sending module 800 may perform the step of sending an indication message that needs to release the context to the receiver after the service interruption or the timer expires. In the step of determining whether the context is allowed to be released, the second judging module 812 may also determine whether the context is allowed to be released by determining whether the service is interrupted or whether the timer expires. The transmitting end in the above device may be a mobile phone, and the receiving end may be a base station; or the transmitting end is a base station, and the receiving end is a base station controller and the like. The apparatus of the present invention has been described in detail above, and the processing flow in the above method embodiments can be implemented in the apparatus of the present invention, and is not described here. Obviously, those skilled in the art should understand that 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. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is 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 scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claims A transmission control method in a robust head compression system, including:

The sender sends an indication message that needs to release the context to the receiver;

Responding to the indication message, the receiver releases its own context, and replies to the sender with an indication message that the release is successful;

The sender responds to the indication message from the recipient reply and releases its own context. The method according to claim 1, wherein the indication message carries a context indicator corresponding to the context only;

The process in which the sender or receiver releases its own context includes: releasing the corresponding context according to the context identifier. The method according to claim 1, wherein before the releasing, the method further comprises:

Determining, by the receiving party, whether the context exists, and if yes, performing the releasing operation, and the step of replying to the sending party with an indication message that the release is successful; if not, performing the releasing operation, performing the Step 4 of the indication message that the sender is replied to the successful release. The method according to claim 3, wherein, after the receiving party determines that the context exists, the method further includes:

The receiving party determines whether the context is allowed to be released, and if so, performs a subsequent context step of releasing the self; if not, the receiving direction returns the indication message that the release fails. The method according to claim 4, wherein the initiator sends the indication message that needs to release the context to the receiver after the service interruption or the timer expires; the determining whether to allow the context to be released The steps include: determining whether the service is interrupted or whether the timer expires; if yes, allowing release, if not, releasing is not allowed.

The method according to claim 5, wherein the initiating party responds to the indication message that the release fails, further comprising:

The initiator records the release process as abnormal information in the log.

A transmission control device in a robust header compression system, comprising: a transmitting end and a receiving end, the transmitting end comprising:

a sending module, configured to send an indication message that needs to release the context to the receiving end; the first releasing module is configured to respond to the release message successfully returned from the receiving end, and release its own context;

The receiving end includes:

And a second release module configured to: release the context of the self in response to the indication message from the sending module; and reply the sending end with the indication message that the release is successful.

8. The apparatus according to claim 7, wherein

The sending end further includes:

a first identifier module, configured to control the sending module to add a context identifier corresponding to the context in the indication message; and controlling the first release module to release a corresponding context according to the context identifier;

The receiving end further includes:

And a second identifier module, configured to control the second release module to release the corresponding context according to the context identifier.

The device according to claim 7, wherein the receiving end further comprises: a first determining module, configured to determine whether the receiving end has the context, if the second releasing module performs an operation, if If yes, the second release module is triggered to perform the operation of releasing the corresponding context, and the step of reporting the release of the success message to the sending end is performed; if not, the second release module is triggered to execute the sending to the sending end Respond to the instructions for releasing the successful message.

The device according to claim 9, wherein the receiving end further comprises:

a second determining module, configured to: after the first determining module determines that the receiving end has the context, determine whether to allow the context to be released, and if yes, allow The first determining module continues to perform an operation; if not, controlling the first determining module to stop the operation; and returning to the sending end an indication message that the release is failed.

The device according to claim 10, wherein the sending end further comprises:

The log module is configured to respond to the indication of the release failure from the receiving end, and record the release process as abnormal information in the log.