CN101252424B - System and method for processing PDU in automatic retransmission request mechanism - Google Patents
System and method for processing PDU in automatic retransmission request mechanism Download PDFInfo
- Publication number
- CN101252424B CN101252424B CN2008101032930A CN200810103293A CN101252424B CN 101252424 B CN101252424 B CN 101252424B CN 2008101032930 A CN2008101032930 A CN 2008101032930A CN 200810103293 A CN200810103293 A CN 200810103293A CN 101252424 B CN101252424 B CN 101252424B
- Authority
- CN
- China
- Prior art keywords
- data
- formation
- node
- timer
- scheduling
- 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.)
- Active
Links
Images
Landscapes
- Communication Control (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Disclosed is a PDU processing method in the ARQ. The method includes that step1, an under transmission block queue is constructed corresponding to the service flow; the send window range is stored; the node of the under transmission block queue is corresponding to a SDU; the node includes a first queue, a feedback waiting queue, a resending queue and a discard queue; step2, the SDU is received and stored in the first queue of the node corresponding to the SDU; step3, within the available bandwidth range of the service flow, the data of the resending queue are scheduled according to the composition mode supported by the service flow; when all data of the resending queue are scheduled, within the residual available bandwidth range, the data of the first queue in the send window range are scheduled according to the composition mode; all the scheduled data are transferred to the feedback waiting queue; a PDU is generated by all the scheduled data according to the composition mode; thereby, the PDU in the ARQ is processed with high efficiency.
Description
Technical field
The invention belongs to communication technical field, relate in particular to the method and system that protocol Data Unit is handled in a kind of automatic repeat requests mechanism.
Background technology
The continuous development of the communications industry has caused the rapid expansion of data volume in the communication network.But no matter be wire message way or wireless channel, all unavoidably exist various transmission to disturb, cause the recipient can not receive data like clockwork.ARQ (Automatic Repeat reQuest, automatically being transmitting terminal repeat requests) retransmits automatically to the loading error occurring or the data of losing, up to a kind of link layer errors control method that data successfully arrive, comprise stopping to wait for that ARQ, the rollback N step retransmits three types of ARQ, selection re-transmission ARQ.For example, IEEE802.16 has proposed a kind of ARQ scheme, but the specific implementation method that does not have specified data to handle, send.Thereby need provide a kind of method and system of realizing that efficiently protocol Data Unit is handled in the automatic repeat requests mechanism.
Summary of the invention
In order to solve above-mentioned technical problem, the invention provides the method and system that protocol Data Unit is handled in a kind of automatic repeat requests mechanism, its purpose is, based on the data organization mode of automatic repeat requests mechanism, realized a kind of method of handling protocol Data Unit in the automatic repeat requests mechanism efficiently.
The invention discloses the method that protocol Data Unit is handled in a kind of automatic repeat requests mechanism, having comprised:
Step 1 is set up the piecemeal formation to be sent corresponding to Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a service data unit, described node comprise first formation, etc. formation to be feedback, retransmission queue and abandon formation;
Step 2 receives service data unit, stores in first formation of described service data unit corresponding node;
Step 3, in described Business Stream available bandwidth scope, composition mode according to described Business Stream support is dispatched data in the described retransmission queue, after the total data scheduling of all retransmission queues is finished, in the residual available bandwidth scope, dispatch data in first formation in the described send window scope according to described composition mode, the data that shift all scheduling to correspondence etc. in the formation to be feedback, and the data of all scheduling are generated protocol Data Unit according to described composition mode.
Described step 1 comprises that also described node is stored the timer of described service data unit correspondence, and described timer comprises timer and retransmission timer life cycle, stops timing after receiving the confirmation message; Described life cycle, corresponding data was transferred to the described formation that abandons during timer expiry; When described retransmission timer was overtime, corresponding data was transferred to described retransmission queue;
Described step 3 also comprises, during data, starts corresponding retransmission timer in the described retransmission queue of scheduling; In the first formation of scheduling during data, start corresponding life cycle of timer and retransmission timer.
The composition mode of Business Stream support in the described step 3 is not packed for not segmentation,
In the described step 3 in the described retransmission queue of scheduling the process of data further comprise, dispatch total data in the retransmission queue of node to be sent;
In the described step 3 in the described first formation of scheduling the process of data further comprise, dispatch total data in first formation of node to be sent;
The process that generates protocol Data Unit in the described step 3 further comprises, the data in the same formation of same node of scheduling are generated a protocol Data Unit.
The composition mode of Business Stream support in the described step 3 can be packed for not segmentation,
In the described step 3 in the described retransmission queue of scheduling the process of data further comprise, dispatch total data in the retransmission queue of node to be sent;
In the described step 3 in the described first formation of scheduling the process of data further comprise, dispatch total data in first formation of node to be sent;
The process that generates protocol Data Unit in the described step 3 further comprises, according to the dispatching sequence, is unit with data in the same formation of same node of scheduling, by the protocol Data Unit maximum length described data dispatching of packing, generates protocol Data Unit.
The composition mode of Business Stream support in the described step 3 is that sectional is not packed,
The process of dispatching data in the described retransmission queue in the described step 3 further comprises, judge that whether the available bandwidth scope is greater than total data size in the retransmission queue of node to be sent, if then dispatch total data in the described retransmission queue, otherwise, dispatch partial data in the described retransmission queue;
The process of dispatching data in described first formation in the described step 3 further comprises, judge that whether the residual available bandwidth scope is greater than total data size in first formation of node to be sent, if, then dispatch total data in described first formation, otherwise, dispatch partial data in described first formation;
The process that generates protocol Data Unit in the described step 3 further comprises, the data in the same formation of same node of scheduling are generated a protocol Data Unit.
The composition mode of Business Stream support in the described step 3 is that sectional can be packed,
In the described step 3 scheduling described retransmission queue in data procedures further comprise, whether judge the available bandwidth scope greater than total data size in the retransmission queue of node to be sent, if greater than, total data in the described retransmission queue then dispatched, otherwise, dispatch partial data in the described retransmission queue;
The process of dispatching data in described first formation in the described step 3 further comprises, judge that whether described residual available bandwidth scope is greater than total data size in first formation of node to be sent, if greater than, then dispatch total data in described first formation, otherwise, dispatch partial data in described first formation;
The process that generates protocol Data Unit in the described step 3 further comprises, according to the dispatching sequence, by the protocol Data Unit maximum length described data dispatching of packing, generates protocol Data Unit.
The invention also discloses the system that protocol Data Unit is handled in a kind of automatic repeat requests mechanism, comprising:
The formation module, be used to set up piecemeal formation to be sent corresponding to Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a service data unit, described node comprise first formation, etc. formation to be feedback, retransmission queue and abandon formation, and the reception service data unit, store in first formation of described service data unit corresponding node;
Processing module, be used in described Business Stream available bandwidth scope, the composition mode of the described Business Stream support of foundation is dispatched the data in the described retransmission queue, the total data of all retransmission queues be scheduled finish after, in the residual available bandwidth scope, dispatch data in first formation in the described send window scope according to described composition mode, the data that shift all scheduling to correspondence etc. in the formation to be feedback, and the data of all scheduling are generated protocol Data Unit according to described composition mode.
Described formation module, also be used to make described node to store the timer of described service data unit correspondence, described timer comprises timer and retransmission timer life cycle, after receiving the confirmation message, stop timing, described life cycle is during timer expiry, corresponding data is transferred to the described formation that abandons, and when described retransmission timer was overtime, corresponding data was transferred to described retransmission queue;
Processing module also is used for starting corresponding retransmission timer when the described retransmission queue data of scheduling, in the described first formation of scheduling during data, starts corresponding life cycle of timer and retransmission timer.
Described processing module comprises:
Not segmentation is the packing data processor not, is used to dispatch support the do not pack data of Business Stream of composition mode of not segmentation;
But not segmentation packing data processor is used to dispatch and supports can the pack data of Business Stream of composition mode of not segmentation;
Sectional is the packing data processor not, is used to dispatch support the do not pack data of Business Stream of composition mode of sectional;
But sectional packing data processor is used to dispatch and supports can the pack data of Business Stream of composition mode of sectional.
Beneficial effect of the present invention is, adopts protocol Data Unit in the automatic repeat requests mechanism that method and system of the present invention can efficiently handle, and can handle the traffic data with different tissues mode.
Description of drawings
Fig. 1 is the inventive method flow chart;
Fig. 2 is a system construction drawing of the present invention;
Fig. 3 is the processing module structure chart;
Fig. 4 is the traffic data scheduling flow figure that not segmentation is not packed;
Fig. 5 is the traffic data scheduling flow figure that not segmentation can be packed;
Fig. 6 is the traffic data scheduling flow figure that sectional is not packed;
Fig. 7 is the traffic data scheduling flow figure that sectional can be packed.
Embodiment
Below in conjunction with accompanying drawing, the present invention is described in further detail.
The flow chart of method of the present invention as shown in Figure 1.
Step S101, foundation is corresponding to the piecemeal formation to be sent of Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a SDU (Service Data Unit, service data unit), the number information of storage SDU, the length of SDU, the timer of SDU correspondence, and comprise the one of four states formation, first formation, etc. formation to be feedback, retransmission queue and abandon formation, described timer comprises timer and retransmission timer life cycle, stop timing after receiving the confirmation message, described life cycle, corresponding data was transferred to the described formation that abandons during timer expiry, when described retransmission timer was overtime, corresponding data was transferred to described retransmission queue;
Step S102 receives the SDU that the upper strata sends, and SDU is carried out logic partitioning, and piecemeal is carried out serial number, stores in first formation of SDU corresponding node;
Step S103, in described Business Stream available bandwidth scope, composition mode according to described Business Stream support, dispatch data in the described retransmission queue, start corresponding retransmission timer, shift described data dispatching to correspondence etc. in the formation to be feedback, after the total data scheduling of all retransmission queues is finished, in the residual available bandwidth scope, according to described composition mode, dispatch data in the first formation in the described send window scope, start corresponding life cycle of timer and retransmission timer, shift described data dispatching to correspondence etc. in the formation to be feedback, and the data of all scheduling are generated PDU (Protocol Data Unit, protocol Data Unit) according to described composition mode.
Among the described step S103, press SDU numbering scheduling node data, the node of the data correspondence of the processing that is scheduled is a node to be sent.
The structure chart of system of the present invention comprises as shown in Figure 2:
Formation module 201, be used to set up piecemeal formation to be sent corresponding to Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a SDU, the number information of described node storage SDU, the length of SDU, the timer of SDU correspondence, and comprise the one of four states formation, first formation, etc. formation to be feedback, retransmission queue and abandon formation, described timer comprise timer and retransmission timer life cycle, stop timing after receiving the confirmation message, described life cycle is during timer expiry, corresponding data is transferred to the described formation that abandons, and when described retransmission timer was overtime, corresponding data was transferred to described retransmission queue, and the SDU of reception upper strata transmission, SDU is carried out logic partitioning, piecemeal is carried out serial number, store in first formation of described SDU corresponding node;
The structure of processing module 202 comprises as shown in Figure 3:
Not segmentation is packing data processor 301 not, is used to dispatch the data of the Business Stream of supporting that not segmentation is not packed, and concrete dispatching method as shown in Figure 4;
But not segmentation packing data processor 302, the data that are used to dispatch the Business Stream of supporting that not segmentation can be packed, concrete dispatching method is as shown in Figure 5;
Sectional is packing data processor 303 not, is used to dispatch the data of the Business Stream of supporting that sectional is not packed, and concrete scheduling mode as shown in Figure 6;
But sectional packing data processor 304, the data that are used to dispatch the Business Stream of supporting that sectional can be packed, concrete scheduling mode is as shown in Figure 7.
Support traffic data scheduling flow that not segmentation do not pack as shown in Figure 4.
Step S401 judges whether Business Stream has available bandwidth, if having, and execution in step S403, otherwise, execution in step S402.
Described available bandwidth is the residual available bandwidth of removing the data of having dispatched.
Step S402 finishes.
Step S403 judges in the retransmission queue of described piecemeal formation node to be sent whether have data, if exist, shows to have data retransmission, and execution in step S404 then, otherwise, show not have data retransmission, execution in step S405.
Step S404, dispatch the total data in the retransmission queue of node to be sent, in formations to be feedback such as the data of described scheduling transferring to from retransmission queue, start corresponding retransmission timer, and generate the PDU that forms by the data in the described retransmission queue, execution in step S401.
Step S405 judges in first formation of described piecemeal formation node to be sent whether have data, if, show that existence does not send data, execution in step S406, otherwise, show not exist not send data, execution in step S402.
Step S406 judges data in first formation whether in described send window scope, if, execution in step S407, otherwise, execution in step S402.
Step S407, dispatch the total data in the first formation of node to be sent, described data dispatching from first formation such as transfers at formation to be feedback, is started corresponding life cycle of timer and retransmission timer, and the head that generates by scheduling passes the PDU that the data in the formation are formed, execution in step S401.
Support traffic data scheduling flow that not segmentation can pack as shown in Figure 5.
Step S501 judges whether Business Stream has available bandwidth, if, execution in step S505, otherwise, execution in step S502.
Described available bandwidth is the residual available bandwidth of removing the data of having dispatched.
Step S502 judges whether to dispatch the not data of packing, if, execution in step S504, otherwise, execution in step S503.
Step S503 finishes.
Step S504 with dispatching the not packing data of packing, generates PDU, and finishes.
Step S505 judges in the retransmission queue of described piecemeal formation node to be sent whether have data, if exist, shows to have data retransmission, and execution in step S506 then, otherwise, show not have data retransmission, execution in step S509.
Step S506 dispatches total data in the retransmission queue of node to be sent, and the data in the described retransmission queue are transferred to etc. in the formation to be feedback, starts corresponding retransmission timer.
Whether step S507 judges the length dispatched after the packing data packing greater than described PDU maximum length, if, execution in step S508, otherwise, execution in step S501.
Step S508 with having dispatched the not packing data of packing before this scheduling, generates PDU, execution in step 501.
Step S509 judges in first formation of piecemeal formation node to be sent whether have data, if, show that existence does not send data, execution in step S510, otherwise, show not exist not send data, execution in step S504.
Step S510 judges data in first formation whether in described send window scope, if, execution in step S511, otherwise, execution in step S504.
Step S511 dispatches total data in first formation of node to be sent, and the data in described first formation are transferred in the formation to be feedback such as described, starts corresponding life cycle of timer and retransmission timer.
Whether step S512 judges the length dispatched after the packing data packing greater than the PDU maximum length, if, execution in step S513 then, otherwise, execution in step S501.
Step S513 with having dispatched the not packing data of packing before this scheduling, generates PDU, execution in step S501.
The traffic data scheduling flow that the support sectional is not packed as shown in Figure 6.
Step S601 judges whether Business Stream has available bandwidth, if, execution in step S603, otherwise, execution in step S602.
Described available bandwidth is the residual available bandwidth of removing the data of having dispatched.
Step S602 finishes.
Step S603 judges in the retransmission queue of described piecemeal formation node to be sent whether have data, if exist, shows to have data retransmission, and execution in step S604 then, otherwise, show not have data retransmission, execution in step S607.
Whether step S604 judges the available bandwidth scope greater than the total data size in the retransmission queue of node to be sent, if, execution in step S605, otherwise, execution in step S606.
Step S605, dispatch the total data in the retransmission queue of node to be sent, the data in the retransmission queue of scheduling are transferred to etc. in the formation to be feedback, start corresponding retransmission timer, and generate the PDU that forms by total data in the retransmission queue of scheduling, execution in step 601.
Step S606, partial data in the retransmission queue of node to be sent in the scheduling available bandwidth scope is transferred to the data of described scheduling etc. in the formation to be feedback, starts corresponding retransmission timer, and generate the PDU that forms by partial data in the retransmission queue of scheduling, and finish.
Step S607 judges in first formation of piecemeal formation node to be sent whether have data, if, show that existence does not send data, execution in step S608, otherwise, show not exist not send data, execution in step S602.
Step S608 judges data in first formation whether in described send window scope, if, execution in step S609, otherwise, execution in step S602.
Whether step S609 judges described available bandwidth scope greater than the total data size in first formation of node to be sent, if, execution in step S610, otherwise, execution in step S611.
Step S610, dispatch the total data in first formation of node to be sent, data in first formation of scheduling are transferred in the formation to be feedback such as described, start corresponding life cycle of timer and retransmission timer, and generate the PDU that forms by total data in first formation of scheduling, execution in step 601.
Step S611, partial data in first formation of node to be sent in the scheduling available bandwidth scope, the data of described scheduling are transferred in the formation to be feedback such as described, start corresponding life cycle of timer and retransmission timer, the PDU that generation is made up of partial data in first formation of scheduling, and finish.
The traffic data scheduling flow that the support sectional can be packed as shown in Figure 7.
Step S701 judges whether Business Stream has available bandwidth, if, execution in step S703, otherwise, execution in step S702.
Described available bandwidth is the residual available bandwidth of removing the data of having dispatched.
Step S702 finishes.
Step S703 judges in the retransmission queue of described piecemeal formation node to be sent whether have data, if exist, shows to have data retransmission, and execution in step S704 then, otherwise, show not have data retransmission, execution in step S711.
Whether step S704 judges the available bandwidth scope greater than the total data size in the retransmission queue of node to be sent, if, execution in step S705, otherwise, execution in step S708.
Step S705 dispatches total data in the retransmission queue of node to be sent, and the data in the described retransmission queue are transferred to etc. in the formation to be feedback, starts corresponding retransmission timer.
Whether step S706 judges the length dispatched after the packing data packing greater than the PDU maximum length, if, execution in step S707, otherwise, execution in step S701.
Step S707 gets the data of dispatching not packing by the PDU maximum length, packs, and generates PDU, execution in step 701.
Step S708, partial data in the retransmission queue of node to be sent in the scheduling available bandwidth scope is transferred to the data in the described retransmission queue etc. in the formation to be feedback, starts corresponding retransmission timer.
Whether step S709 judges the length dispatched after the packing data packing greater than described PDU maximum length, if, execution in step S710, otherwise, execution in step S720.
Step S710 gets the data of dispatching not packing by the PDU maximum length, packs, and generates PDU, execution in step 720.
Step S711 judges in first formation of piecemeal formation node to be sent whether have data, if, show that existence does not send data, execution in step S712, otherwise, show not exist not send data, execution in step S720.
Step S712 judges data in first formation whether in the send window scope, if, execution in step S713, otherwise, execution in step S720.
Whether step S713 judges the available bandwidth scope greater than the total data size in first formation of node to be sent, if, execution in step S717, otherwise, execution in step S714.
Step S714, the partial data in the scheduling available bandwidth scope in first formation of node to be sent is transferred to the data in first formation of scheduling in the formation to be feedback such as described, starts corresponding life cycle of timer and retransmission timer, execution in step 715.
Whether step S715 judges the length dispatched after the packing data packing greater than described PDU maximum length, if, execution in step S716, otherwise, execution in step S720.
Step S716 gets the data of dispatching not packing by the PDU maximum length, packs, and generates PDU, execution in step 720.
Step S717, the total data in the scheduling available bandwidth scope in first formation of node to be sent is transferred to the data in first formation of scheduling in the formation to be feedback such as described, starts corresponding life cycle of timer and retransmission timer, execution in step 718.
Whether step S718 judges the length dispatched after the packing data packing greater than described PDU maximum length, if, execution in step S719, otherwise, execution in step S701.
Step S719 gets the data of dispatching not packing by the PDU maximum length, packs, and generates PDU, execution in step 701.
Step S720 with dispatching the not packing data of packing, generates PDU.
Those skilled in the art can also carry out various modifications to above content under the condition that does not break away from the definite the spirit and scope of the present invention of claims.Therefore scope of the present invention is not limited in above explanation, but determine by the scope of claims.
Claims (7)
1. the method that protocol Data Unit is handled in the automatic repeat requests mechanism is characterized in that, comprising:
Step 1, foundation is corresponding to the piecemeal formation to be sent of Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a service data unit, store the timer of described service data unit correspondence, described timer comprises timer and retransmission timer life cycle, described node comprises first formation, etc. formation to be feedback, retransmission queue and abandon formation, described life cycle, timer and described retransmission timer stopped timing after receiving the confirmation message, described life cycle is during timer expiry, corresponding data is transferred to the described formation that abandons, when described retransmission timer is overtime, corresponding data is transferred to described retransmission queue;
Step 2 receives service data unit, stores in first formation of described service data unit corresponding node;
Step 3, in described Business Stream available bandwidth scope, press service data unit according to the composition mode of described Business Stream support and number data in the retransmission queue of scheduling node, start corresponding retransmission timer, shift described data dispatching to correspondence etc. in the formation to be feedback, after the total data scheduling of all retransmission queues is finished, in the residual available bandwidth scope, press data in the interior first formation of the send window scope of service data unit numbering scheduling node according to described composition mode, start corresponding life cycle of timer and retransmission timer, the data that shift described scheduling to correspondence etc. in the formation to be feedback, and the data of all scheduling are generated protocol Data Unit according to described composition mode; The composition mode of described Business Stream support is for not segmentation can be packed, not segmentation can be packed, sectional is not packed or sectional can be packed.
2. the method that protocol Data Unit is handled in the automatic repeat requests mechanism as claimed in claim 1 is characterized in that the composition mode of Business Stream support in the described step 3 is not packed for not segmentation,
In the described step 3 in the described retransmission queue of scheduling the process of data further comprise, dispatch total data in the retransmission queue of node to be sent;
In the described step 3 in the described first formation of scheduling the process of data further comprise, dispatch total data in first formation of node to be sent;
The process that generates protocol Data Unit in the described step 3 further comprises, the data in the same formation of same node of scheduling are generated a protocol Data Unit.
3. the method that protocol Data Unit is handled in the automatic repeat requests mechanism as claimed in claim 1 is characterized in that the composition mode of Business Stream support in the described step 3 can be packed for not segmentation,
In the described step 3 in the described retransmission queue of scheduling the process of data further comprise, dispatch total data in the retransmission queue of node to be sent;
In the described step 3 in the described first formation of scheduling the process of data further comprise, dispatch total data in first formation of node to be sent;
The process that generates protocol Data Unit in the described step 3 further comprises, according to the dispatching sequence, is unit with data in the same formation of same node of scheduling, by the protocol Data Unit maximum length described data dispatching of packing, generates protocol Data Unit.
4. the method that protocol Data Unit is handled in the automatic repeat requests mechanism as claimed in claim 1 is characterized in that the composition mode of Business Stream support in the described step 3 is that sectional is not packed,
The process of dispatching data in the described retransmission queue in the described step 3 further comprises, judge that whether the available bandwidth scope is greater than total data size in the retransmission queue of node to be sent, if then dispatch total data in the described retransmission queue, otherwise, dispatch partial data in the described retransmission queue;
The process of dispatching data in described first formation in the described step 3 further comprises, judge that whether the residual available bandwidth scope is greater than total data size in first formation of node to be sent, if, then dispatch total data in described first formation, otherwise, dispatch partial data in described first formation;
The process that generates protocol Data Unit in the described step 3 further comprises, the data in the same formation of same node of scheduling are generated a protocol Data Unit.
5. the method that protocol Data Unit is handled in the automatic repeat requests mechanism as claimed in claim 1 is characterized in that the composition mode of Business Stream support in the described step 3 is that sectional can be packed,
In the described step 3 scheduling described retransmission queue in data procedures further comprise, whether judge the available bandwidth scope greater than total data size in the retransmission queue of node to be sent, if greater than, total data in the described retransmission queue then dispatched, otherwise, dispatch partial data in the described retransmission queue;
The process of dispatching data in described first formation in the described step 3 further comprises, judge that whether described residual available bandwidth scope is greater than total data size in first formation of node to be sent, if greater than, then dispatch total data in described first formation, otherwise, dispatch partial data in described first formation;
The process that generates protocol Data Unit in the described step 3 further comprises, according to the dispatching sequence, by the protocol Data Unit maximum length described data dispatching of packing, generates protocol Data Unit.
6. the system that protocol Data Unit is handled in the automatic repeat requests mechanism is characterized in that, comprising:
The formation module, be used to set up piecemeal formation to be sent corresponding to Business Stream, storage send window scope, the node of described piecemeal formation to be sent is corresponding to a service data unit, store the timer of described service data unit correspondence, described timer comprises timer and retransmission timer life cycle, described node comprises first formation, etc. formation to be feedback, retransmission queue and abandon formation, described life cycle, timer and described retransmission timer stopped timing after receiving the confirmation message, described life cycle is during timer expiry, corresponding data is transferred to the described formation that abandons, when described retransmission timer is overtime, corresponding data is transferred to described retransmission queue, and receive service data unit, store in first formation of described service data unit corresponding node;
Processing module, be used in described Business Stream available bandwidth scope, press service data unit according to the composition mode of described Business Stream support and number data in the retransmission queue of scheduling node, start corresponding retransmission timer, shift described data dispatching to correspondence etc. in the formation to be feedback, after the total data scheduling of all retransmission queues is finished, in the residual available bandwidth scope, press data in the interior first formation of the send window scope of service data unit numbering scheduling node according to described composition mode, start corresponding life cycle of timer and retransmission timer, the data that shift described scheduling to correspondence etc. in the formation to be feedback, and the data of all scheduling are generated protocol Data Unit according to described composition mode; The composition mode of described Business Stream support is for not segmentation can be packed, not segmentation can be packed, sectional is not packed or sectional can be packed.
7. the system that protocol Data Unit is handled in the automatic repeat requests mechanism as claimed in claim 6 is characterized in that described processing module comprises:
Not segmentation is the packing data processor not, is used to dispatch support the do not pack data of Business Stream of composition mode of not segmentation;
But not segmentation packing data processor is used to dispatch and supports can the pack data of Business Stream of composition mode of not segmentation;
Sectional is the packing data processor not, is used to dispatch support the do not pack data of Business Stream of composition mode of sectional;
But sectional packing data processor is used to dispatch and supports can the pack data of Business Stream of composition mode of sectional.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101032930A CN101252424B (en) | 2008-04-02 | 2008-04-02 | System and method for processing PDU in automatic retransmission request mechanism |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101032930A CN101252424B (en) | 2008-04-02 | 2008-04-02 | System and method for processing PDU in automatic retransmission request mechanism |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101252424A CN101252424A (en) | 2008-08-27 |
| CN101252424B true CN101252424B (en) | 2011-10-05 |
Family
ID=39955622
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101032930A Active CN101252424B (en) | 2008-04-02 | 2008-04-02 | System and method for processing PDU in automatic retransmission request mechanism |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101252424B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378308B (en) * | 2008-09-24 | 2012-07-04 | 中兴通讯股份有限公司 | Optimizing method for automatic retransmission request in OFDMA system |
| CN101984704A (en) * | 2010-10-19 | 2011-03-09 | 中兴通讯股份有限公司 | Data processing control method and device |
| CN102217256B (en) * | 2011-05-26 | 2015-03-18 | 华为技术有限公司 | Queue scheduling method and apparatus |
| CN102868507B (en) * | 2012-09-19 | 2015-10-28 | 电子科技大学 | Based on the segmentation ARQ method of transmission reliability |
| CN111327404B (en) * | 2018-12-13 | 2022-08-26 | 大唐移动通信设备有限公司 | Service lifetime processing method and device |
| CN112637083B (en) * | 2020-12-14 | 2022-07-01 | 杭州迪普科技股份有限公司 | Packet loss processing method, device, equipment and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1767423A (en) * | 2005-11-25 | 2006-05-03 | 中兴通讯股份有限公司 | Data transmission control method in multi carrier wave high-speed downlink packet access system |
| CN101064663A (en) * | 2006-04-27 | 2007-10-31 | 中兴通讯股份有限公司 | Method for retransmitting data in wireless link control protocol |
-
2008
- 2008-04-02 CN CN2008101032930A patent/CN101252424B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1767423A (en) * | 2005-11-25 | 2006-05-03 | 中兴通讯股份有限公司 | Data transmission control method in multi carrier wave high-speed downlink packet access system |
| CN101064663A (en) * | 2006-04-27 | 2007-10-31 | 中兴通讯股份有限公司 | Method for retransmitting data in wireless link control protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101252424A (en) | 2008-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101252424B (en) | System and method for processing PDU in automatic retransmission request mechanism | |
| JP5521257B2 (en) | Group resource allocation for wireless communication | |
| CN101043301B (en) | Data rearrangement and recombination method in wireless communication system and its base station | |
| CN102143596B (en) | Wireless resource scheduling method and wireless resource scheduling system | |
| CN101682488A (en) | Method and arrangement for retransmission using harq | |
| CN107005560A (en) | A kind of data transmission method for uplink, data receiver method and relevant device | |
| WO2004114610A1 (en) | Radio packet communication method | |
| CN102137504A (en) | Method and device for dispatching transmission of multiple sub-frames | |
| JP2004135301A (en) | Data communication method using control message | |
| MX2011001484A (en) | Communication device, transmission data generation program, and transmission data generation method. | |
| TWI401985B (en) | Method of constructing and transmitting packets with mimo configuration in a wireless communication system | |
| JP2016518749A (en) | Method and apparatus for using more transmission opportunities in a distributed network topology with limited HARQ processes | |
| WO2012163171A1 (en) | Method and device for data transmission | |
| CN103875192A (en) | Method and apparatus for transmitting harq feedback | |
| JP4763343B2 (en) | Method and apparatus for allocating resources in a network | |
| CN101127806A (en) | Scheduling method for downlink voice IP service | |
| CN102948244B (en) | Send method and the wireless device of packet | |
| EP3790213B1 (en) | Mac-based hybrid automatic repeat request (harq) | |
| CN109067497B (en) | Efficient networking method suitable for ultrashort wave TDMA wireless channel | |
| CN104518855B (en) | The method, apparatus of descending HARQ feedback is handled in base station and LTE system | |
| CN102076103B (en) | Data packet processing method for semi-persistent scheduling and base station | |
| CN102638897B (en) | Resource scheduling method and resource scheduling device | |
| CN101989896B (en) | Feedback method and device for ARQ connection | |
| CN101932008A (en) | Automatic repeat method and device | |
| CN113067681B (en) | Hybrid automatic repeat request processing method, communication equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |