CN1996819A - A mixed processing method for automatic retransfer request - Google Patents
A mixed processing method for automatic retransfer request Download PDFInfo
- Publication number
- CN1996819A CN1996819A CN 200510132786 CN200510132786A CN1996819A CN 1996819 A CN1996819 A CN 1996819A CN 200510132786 CN200510132786 CN 200510132786 CN 200510132786 A CN200510132786 A CN 200510132786A CN 1996819 A CN1996819 A CN 1996819A
- Authority
- CN
- China
- Prior art keywords
- nodeb
- harq
- type
- message
- radio link
- 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.)
- Granted
Links
Abstract
This invention discloses one mixture automatic repeat require process method, which comprises the following steps: servo wireless network controller gets and stores base station Node HARQ merge type information; sending wireless linkage establishment message or reset message to Node; if the type is supportive for chase combining only type or for incremental redundancy combining only tope, then establishing message or wireless linkage reset message without HARQ merge type information element.
Description
Technical field
The present invention relates to wireless communication field, relate in particular to and adopt High Speed Uplink Packet to insert (HSUPA in Wideband Code Division Multiple Access (WCDMA) (the Wide-band CodeDivision Multiple Address) system, HighSpeed Uplink Packet Access) during technology, the automatic repeat requests of a kind of mixing (HARQ, HybridAutomatic Repeat request) processing method.
Background technology
In the WCDMA system, the HSUPA technology is a kind of up enhancement techniques of up-to-date introducing in the WCDMA R6 version, and it mainly comprises following several technology point:
1) dispatching technique of base station (NodeB) control;
2) HARQ is with soft folding;
3) shorter Transmission Time Interval (transmission Time interval, TTI) technology.
Wherein, above-mentioned HARQ folding is mainly used in the quick retransmission process of physical layer of enhancement type special channel (E-DCH, EnhancedDedicated Channel), improves the decoding performance of E-DCH physical layer by the soft merging between first biography and the re-transmission.
Please refer to Fig. 1, this figure carries out the processing procedure schematic diagram that HARQ handles on the E-DCH physical layer of subscriber terminal equipment (UE) side in the prior art, and its main processing procedure is as follows:
Output N after the E-DCH chnnel coding
E, jBe separated into system bits (Systematic bits), check digit 1 (Parity 1 bits) and three sequences of check digit 2 (Parity 2bits) through bit (bit) separating treatment (bit separation);
These three sequences are carried out rate-matched (Rate Matching respectively, RM) handle, three sequences after the rate-matched processing are carried out bit close road processing (bit collection), and bit is closed bit after handle on the road be mapped to the E-DCH Dedicated Physical Data Channel (E-DCH Dedicated Physical DataChannel transmits in E-DPDCH).
Wherein the main effect handled of rate-matched is the variable number of bits before the rate-matched to be matched on the physical channel of fixed rate transmit.According to bit number before the rate-matched and the relation of the bit number after the rate-matched, can be divided into repetition rate matching treatment and punching rate matching and handle dual mode, during bit number after the bit number before the rate-matched is less than rate-matched, adopt the repetition rate matching way to handle, the bit that is about to preceding some position of sequence of rate-matched repeats to send; Otherwise adopt the punching rate matching processing mode to handle, the bit that is about to preceding some position of sequence of rate-matched does not send.
The HARQ function is subjected to the control of redundancy versions (RV) parameter, and the RV parameter-definition is shown in following table one:
Table one: RV parameter-definition
| E-DCH RV Index (E-DCH redundancy versions index) | s | r |
| 0 | 1 | 0 |
| 1 | 0 | 0 |
| 2 | 1 | 1 |
| 3 | 0 | 1 |
In the last table one, the s parameter be used for selecting be system bits preferentially or check digit preferential, can influence system bits and check digit shared bit number in physical channel after the rate-matched, if s is that 1 expression system bits is preferential, rate-matched preferentially satisfies system bits, if s is that 0 expression check digit is preferential, rate-matched preferentially satisfies check digit.The r parameter bit original position that decides repetition rate matching treatment and punching rate matching to handle.
HARQ is divided into Cai Si and merges (Chase Combining is called for short the CC type) and two kinds of merging types of incremental redundancy merging (Incremental Redundant Combining is called for short the IR type), and when adopting CC to merge type, RV Index is fixed as 0; When adopting IR to merge type, RV Index can (Repeat Serial Number RSN) changes with re-transmission sequence number.
Merge type according to different HARQ, NodeB is divided into and only supports incremental redundancy to merge (Incremental Redundant Combining only, abbreviation IR only), only support that Cai Si merges (Chase Combining only is called for short CC only) and incremental redundancy merges and (IR﹠amp is all supported in the Cai Si merging; CC) NodeB.
RV Index in the table one has defined HARQ redundancy versions configuration cell by the control of UE transmit leg in 23.331 agreements, shown in following table two:
Table two:
| Information element/group name | Need | Multi | Type and reference | Describe | Version |
| The configuration of HARQ redundancy versions | Necessary | Enumeration type (RV) | If be designated as " rv0 ", NodeB only uses RV Index0.Under the default situation, NodeB will use the RV Index that obtains based on RSN. | Version 6 |
Agreement is defined in the Radio Link request of setting up (Radio Link Setup Request), asynchronous radio link reconfiguration request (Radio Link Reconfiguration Request), synchronous wireless link reconfigured request Radio LinkReconfiguration Prepare) carry the HARQ relevant information in the message, concrete HARQInfo for E-DCH element definitions is shown in following table three:
Table three
| Information element/group name | Presence (being present condition) | Range (scope) | IE Type and Reference (cell type and parameter) | Describe |
| HARQ Info for E-DCH | ENUMERATED (enumeration type) (rv0, rvtable) | If be designated as " rv0 ", NodeB only uses RV Index 0.If be designated as rvtable, NodeB will use the RV Index that obtains based on RSN. |
Because in existing protocol, the regulation Radio Link is set up in the request message, " Presence " of HARQ Info forE-DCH cell is " M ", be essential state, therefore, in the prior art, the Radio Link that SRNC sends to NodeB is set up and all will be carried HARQ Info for E-DCH cell in the request message at every turn, and the HARQ that SRNC is selected merges type notification and gives NodeB.
In the existing protocol,, stipulate that " Presence " of its HARQ Info for E-DCH cell is " O ", be optional state for radio link reconfiguration signaling (synchronised radio link reconfigure signaling or asynchronous wireless links are reshuffled signaling).
Particularly, in the prior art, in a Radio Link is set up, decide selection IR type or CC type to carry out HARQ by SRNC according to business information such as Qos and merge; After the SRNC decision, can be by NodeB Application Part (Node B Application Part, NBAP) (Radio Network Subsystem Application Part, RNSAP) message informing NodeB uses the HARQ that selects to merge type for message and Radio Network Subsystem Application Part.The HARQ that supports SRNC to select as NodeB merges type, after finishing Radio Link foundation or radio link reconfiguration, SRNC is by Radio Resource control (RadioResource Control, RRC) HARQ of this communication use of message informing UE merges type, UE merges type according to this HARQ and sends data, and NodeB uses this HARQ merging type to carry out the Data Receiving merging.
When NodeB does not support the merging type of SRNC selection, can directly feed back by NodeB, or feed back by control radio network controller (CRNC), the HARQ of its support of notice SRNC merges type.If feed back by CRNC, NodeB can inform that the HARQ of its support of CRNC merges type by Audit Response message or resource status indication (RESOURCE STATUSINDICATION) process etc. of review process (AuditProcedure).CRNC sets up the HARQ that NodeB that response message (RL Setup Response), asynchronous wireless links reconfiguration response message (RLReconfiguration Response) or synchronised radio link reconfigure response message (RLReconfiguration Ready) will know supports by Radio Link and merges type notification SNRC.
Description by above-mentioned prior art as can be known, no matter NodeB is CC only, IR only or (IR+CC) type, the Radio Link that sends to NodeB at SRNC is set up in the message, all will carry notice NodeB and carry out the merging type cell (HARQ Info for E-DCH cell) that HARQ merges; Be that SRNC does not carry out type classification to NodeB in the prior art, always think that NodeB is the IR+CC type.Because it is very high that Radio Link is set up message frequency of utilization in network, like this, each message is all carried HARQ Info for E-DCH cell, will bring bigger signaling consumption.In fact, for the NodeB that uses CC only or IR only, CC or IR that SRNC can only select for use NodeB to support merge type, therefore needn't set up in request or the radio link reconfiguration request message at Radio Link and carry HARQ information, when promptly the HARQ type of supporting as NodeB is CC only or IR only, sets up at the Radio Link that sends to NodeB and can not comprise HARQ Info for E-DCH cell in message or the radio link reconfiguration message.
Summary of the invention
The invention provides the automatic repeat requests processing method of a kind of mixing, set up at each wireless links that sends to NodeB in order to SRNC in the solution prior art and all must carry HARQ merging type information cell, the problem that signaling consumption is big in the message.
The inventive method comprises: service wireless network controller SRNC obtains and stores the HARQ merging type information that base station node B is supported;
At SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, merge type for only supporting Cai Si merging (ChaseCombining only) type or only supporting incremental redundancy to merge (Incremental redundancyCombining only) type if inquire the HARQ of this NodeB support, then set up not comprise in message or the radio link reconfiguration message and carry the cell that HARQ merges type information at described Radio Link.
According to said method of the present invention, the present condition " presence " that is of Radio Link being set up the enhanced dedicated HARQ information HARQ Info for E-DCH cell in the message changes optional " O " into by essential " M ";
At SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, to merge type be Chase Combining only type or Incremental redundancy Combining only type if inquire HARQ that this NodeB supports, then sets up at described Radio Link not comprise HARQ Info for E-DCH cell in message or the radio link reconfiguration message;
After NodeB finished Radio Link foundation, the HARQ that this NodeB that SRNC preserves this locality supports merged the corresponding portable terminal that type notification is set up Radio Link.
Described SRNC obtains the HARQ merging type that NodeB supports, comprising:
The HARQ that A, control radio network controller CRNC obtain the NodeB support of being administered merges type information;
The HARQ that the corresponding NodeB that B, CRNC will obtain supports merges type information and preserves by RNC around the Iur interface notice.
Described steps A comprises:
A1, NodeB merge type information by audit response (AUDIT RESPONSE) signaling with the HARQ that self supports and are notified to CRNC after receiving audit request (AUDIT REQUEST) signaling that CRNC issues; Perhaps
A2, NodeB initiatively merge type information with the HARQ that self supports by resource status indication (RESOURCE STATUS INDICATION) signaling and are notified to CRNC.
Described step B comprises:
B1, after CRNC is restarted, by restarting the Reset process, RNC preserved around the HARQ that the NodeB that is administered is supported merged the type information notice; Perhaps
B2, by the information exchange Information Exchange process between the RNC, RNC preserved around the HARQ that CRNC supports the NodeB that is administered merged the type information notice.
Described step B2 comprises:
RNC begins request message INFORMATIONEXCHANGE INITIATION REQUEST to described CRNC transmission information exchange on every side, adds the HARQ Info cell of request HARQ information in this message;
Described CRNC return information exchange beginning response message INFORMATION EXCHANGEINITIATION RESPONSE adds cell in this message, carry the HARQ merging type information that its NodeB that administers supports; Perhaps
Described CRNC is the information report message of RNC transmission towards periphery INFORMATIONREPORT regularly, adds cell in this message, carries the HARQ merging type information that its NodeB that administers supports; Perhaps
When the quantity of the NodeB that described CRNC administered changes or the NodeB that administered supports HARQ merges type and changes, CRNC RNC towards periphery sends INFORMATIONREPORT, in this message, add cell, carry the HARQ merging type information that its NodeB that administers supports.
According to said method of the present invention, when whole NodeB that described CRNC administered support that identical HARQ merges type, in the cell of described interpolation, only need carry the corresponding sign that HARQ that NodeB supports merges type; Receiving terminal parses the HARQ that NodeB that described CRNC administers supports according to described sign and merges type;
When the HARQ merging type of the NodeB support that CRNC administered is incomplete same, in the cell of described interpolation, need carry the HARQ that each NodeB identifies and this NodeB the supports merging type information that CRNC administers.
Described SRNC obtains the HARQ that NodeB supports and merges type, also comprises: by the operational administrative platform HARQ of the NodeB that obtains and support thereof is merged the type information human configuration and store in described SRNC.
Described SRNC obtains the HARQ merging type that NodeB supports, also comprises: when NodeB is restarted, the HARQ that self supports is merged the type information notice be attached thereto all RNC that connect.
Described SRNC obtains the HARQ merging type that NodeB supports, also comprises: when NodeB is restarted, the HARQ that self supports is merged type information notify a public entities that is arranged in the network to preserve; Described SNC obtains the HARQ merging type information that NodeB supports from described public entities.
According to said method of the present invention, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, if do not merge type to the HARQ that this NodeB supports at local search, be that Chase Combining and Incremental redundancy Combining support type then according to Node B, set up at described Radio Link and to carry HARQ information in message or the radio link reconfiguration message, the HARQ that indicates this NodeB to use SRNC to select merges type;
When NodeB did not support that the HARQ of SRNC selection merges type, the HARQ that returns its support to SRNC merged type information; SRNC merges type information at the HARQ of its support that this locality preservation NodeB returns.
According to said method of the present invention, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, if inquiring the HARQ merging type of this NodeB support is that ChaseCombining and Incremental redundancy Combining support type, then handle by existing procedure.
According to said method of the present invention, only storing HARQ merging type in SRNC is the NodeB record of ChaseCombining only type and Incremental redundancy Combining only type; , when setting up message or radio link reconfiguration message,, then handles NodeB transmission Radio Link at SRNC by existing procedure if do not inquire the corresponding record of this NodeB.
Beneficial effect of the present invention is as follows:
(1), adopts the inventive method, after the HARQ type of SRNC understanding NodeB support is IR only or CC only, three message in link establishment: Radio Link is set up and all be need not to carry HARQ in request message (Radio LinkSetup Request), asynchronous radio link reconfiguration message (Radio Link ReconfigurationRequest) or the synchronous radio link reconfiguration message (Radio Link Reconfiguration Prepare) and merge type information, saves a large amount of signaling consumptions.
When (2), adopting the inventive method, the presence of the HARQ Info for E-DCH cell in the Radio Link foundation request (Radio Link Setup Request) that only needs to stipulate in the existing protocol changes " O " into by " M ", when the type of NodeB is IR only or CC only, set up at the Radio Link that sends to NodeB and not comprise this HARQ Info for E-DCH cell in message or the radio link reconfiguration message, realize simple.
(3), the present invention also provides the HARQ of the multiple NodeB of obtaining support to merge the concrete grammar of type, make SRNC when indication NodeB sets up Radio Link or reconfiguring radio link, can accurately learn the particular type information of this NodeB, guarantee the enforcement of the inventive method.
Description of drawings
Fig. 1 is for carrying out the processing procedure schematic diagram that HARQ handles on the prior art E-DCH physical layer;
Fig. 2 is the inventive method flow chart.
Embodiment
The basic principle of the inventive method is: when SRNC knows that the HARQ type of NodeB support is CConly or IR only type, do not carry HARQ and merge type information in sending to the RL Setup Request message of NodeB.
Because in 25.423 and 25.433 agreements, the Presence with the HARQ Info forE-DCH cell among the RL Setup Request is defined as essential state " M ", therefore, the present invention changes the selection mode of this Presence into " O " from " M ".
In order to implement method of the present invention, SRNC need know that the HARQ merging type that NodeB supports is CC only, IR only or CC+IR type.
Below how SRNC being obtained HARQ that NodeB supports merges type and provides detailed description.
One, SRNC is the CRNC of NodeB;
CRNC can know that the HARQ of the NodeB support of being administered merges type, and concrete grammar is:
(1), CRNC issues audit request (AUDIT REQUEST) signaling to NodeB, NodeB returns audit response (AUDIT RESPONSE) signaling, the HARQ that self supports is merged type information be notified to CRNC;
(2) NodeB initiatively is notified to CRNC with the HARQ merging type information of self supporting by resource status indication (RESOURCE STATUS INDICATION) signaling.
When SRNC is the CRNC of NodeB (SRNC-＞Node B), SRNC must understand the HARQ merging type that NodeB supports by top two methods, when the HARQ merging type of determining this Node B support is CC only or IR only, SRNC sets up request (Radio Link Setup Request) at the Radio Link that sends, needn't comprise in asynchronous wireless link reconfigured (Radio Link ReconfigurationRequest) and synchronous wireless link reconfigured (Radio Link Reconfiguration Prepare) message and carry HARQ and merge the type cell, promptly in above-mentioned message, not carry HARQ Info forE-DCH cell.SRNC is receiving respective response message, and promptly RL setup Response tells the HARQ merging type that UE should adopt by RRC message after RLReconfiguration Response and the RL Reconfiguration Ready message.
Two, SRNC is not the CRNC of NodeB;
SRNC might not be the CRNC of NodeB, and SRNC understands the HARQ that the NodeB under the RNC on every side supports by the following method and merges type like this:
Method one, understand the HARQ that its NodeB that administers supports at CRNC and merge under the type cases, by RNC around the Iur interface notice.
The mode of notice can be by the Reset process, restarts the back notice at CRNC.Concrete advice method is a prior art, and description is omitted.
Can also give RNC on every side with the HARQ merging type notification that NodeB supports by information exchange (INFORMATION EXCHANGE) process between the RNC.
For example: RNC1 can begin request (INFORMATION EXCHANGEINITIATION REQUEST) message request RNC2 by information exchange and report that the HARQ of the support of the NodeB that it is administered merges type information;
RNC2 begins response (INFORMATION EXCHANGE INITIATIONRESPONSE) message is reported HARQ ability information from the NodeB that is administered to RNC1 by information exchange.
Perhaps after the merging type that RNC2 is regular or complete all NodeB that it is administered of collection support, give RNC1 by report information (INFORMATION REPORT) message report.
The present invention can use above-mentioned information exchanging process, realizes that CRNC is notified to RNC on every side with the HARQ merging type information that the own NodeB that is administered supports.Concrete grammar is:
RNC begins request message INFORMATIONEXCHANGE INITIATION REQUEST to CRNC transmission information exchange on every side, adds the HARQ Info cell of request HARQ information in this message;
CRNC return information exchange beginning response message INFORMATION EXCHANGEINITIATION RESPONSE adds cell in this message, carry the HARQ merging type information that its NodeB that administers supports.
Perhaps CRNC regularly towards periphery RNC send information report message INFORMATIONREPORT, in this message, add cell, carry the HARQ that its NodeB that administers supports and merge type information;
Perhaps when the quantity of the NodeB that CRNC administered changes or the NodeB that administered supports HARQ merges type and changes, CRNC RNC towards periphery sends INFORMATIONREPORT, in this message, add cell, carry the HARQ merging type information that its NodeB that administers supports.
In the real network, the NodeB that the RNC of certain manufacturer is administered down also is certain manufacturer, like this, if a NodeB under certain CRNC is one type among IR only, CC only or the IR+CC, so in general other NodeB under this CRNC also are this type (exception are also arranged certainly).If the whole NodeB under the CRNC belong to same type, promptly be all IR only type, CC only type or IR+CC type, as long as CRNC is himself merging type of RNC around the notice so, represent its whole NodeB that administer all to support this kind merging type with the merging type of self, do not need the sign of its each NodeB that administers and the merging type of support thereof are all notified one by one.That is: when whole NodeB that CRNC administered support that identical HARQ merges type, in the cell of above-mentioned interpolation, only need carry the corresponding sign that HARQ that NodeB supports merges type; Receiving terminal parses the HARQ that NodeB that described CRNC administers supports according to described sign and merges type.
When the HARQ merging type of the NodeB support that CRNC administered is incomplete same, in the cell of above-mentioned interpolation, need carry the HARQ that each NodeB identifies and this NodeB the supports merging type information that CRNC administers.
For this reason, can set up be defined as follows (only being one gives an example) shown in the table four of above-mentioned interpolation cell:
Table four:
| IE/Group Name (cell/group name claims) | Presence (being present condition) | Range (scope) | IE Type and Reference (cell type and parameter) | Semantics Description (description) | Criticality (degree of danger) | Assign ed Critical ity (degree of danger of appointment) |
| RNC-HARQ-info | ||||||
| RNC combining type (RNC merges type) | M (essential) | 1:all cells are IR only (all base stations all be IR only type) 2:all cells are CC only (all base stations all are CC only types) 3:all cells are CC﹠IR (all base stations all are the CC+IR types) 4:not all cells are the same type (be not whole base stations all be the same type) | ||||
| ＞IR only | O (optional) | If RNC type=4 (if the RNC type is 4) | ||||
| ＞＞Cell (sub-district or base station) | O (optional) | 1..＜maxnoofcell〉(sub-district of 1..＜maximum quantity 〉) | ||||
| The C-ID of＞＞＞(Base Station Identification) | O (optional) | Cell which is IR only (base station is an IR only type) | ||||
| ＞CC only | O (optional) | If RNC type=4 (if the RNC type is 4) | ||||
| ＞＞Cell (base station) | O (optional) | 1..<maxnoofcell> | ||||
| The C-ID of＞＞＞(Base Station Identification) | O (optional) | Cell which is CC only (base station is a CC only type) | ||||
| ＞IR&&CC | O (optional) | If RNC type=4 (if the RNC type is 4) | ||||
| ＞＞Cell (base station) | O (optional) | 1..<maxnoofcell> | ||||
| The C-ID of＞＞＞(Base Station Identification) | O (optional) | Cell which is IR ﹠﹠CC (base station is the CC+IR type) |
In the last table four, if the whole NodeB under the CRNC support with a kind of HARQ type the merging type identification " 1 ", " 2 " or " 3 " that only need to carry RNC in the cell that increases; After RNC receives on every side, resolve according to the correspondence sign that receives:
As if be designated " 1 " that receives, the HARQ that then writes down whole NodeB supports of this CRNC administration merges type and merges type (IR only) for only supporting IR;
As if be designated " 2 " that receive, the HARQ that then writes down whole NodeB supports of this CRNC administration merges type and merges type (CC only) for only supporting CC;
As if be designated " 3 " that receive, the HARQ that then writes down whole NodeB supports of this CRNC administration merges type for not only supporting IR to merge type but also support CC merging type (IR+CC).
If RNC merging type identification is " 4 ", represent that the NodeB that this CRNC administers not is to be to support to merge type with a kind of HARQ, at this moment, need be distinguished into three types, the HARQ merging type information with NodeB sign and support thereof is notified to RNC on every side respectively.
Certainly, top form can change, and only notifies the base station of only supporting CC to merge type and only supporting IR merging type as CRNC.Like this, for the uncomprehending base station of SRNC, SRNC takes it as IR+CC type.
Method two: the type of understanding NodeB by the learning process of RNC.
Serve as in the SRNC process at RNC,, in this time communication process, assign this NodeB to use a kind of merging type,, will return the merging type information of the support of NodeB if this NodeB does not support the merging type of this appointment if the type of certain NodeB is not understood.The SRNC record also is stored in this locality, thereby obtains the merging type of this NodeB.Be that SRNC has ability of self-teaching, the merging type of the NodeB that obtains can be write down storage, in the time need obtaining the merging type of this NodeB next time, the local recorded information of inquiry can be learnt.For preventing that NodeB from changing type, SRNC can regularly delete or ignore the merging type information of NodeB, when redesignating this NodeB to use its unsupported merging type, according to the merging type that writes down its support behind the return information of NodeB once more.
Method three: by operational administrative platform (O﹠amp; M) manual configuration.
By the operational administrative platform HARQ of the NodeB that obtains and support thereof being merged the type information human configuration stores in described SRNC.Manual configuration requires than higher.
Method four: process such as restart by NodeB and notify the HARQ of its support to merge type.
When NodeB was restarted, the HARQ that self is supported merged the type information notice and is attached thereto all RNC that connect, and comprised CRNC and other RNC on every side.
Method five: when NodeB is restarted, the HARQ that self supports is merged type information notify a public entities storage.
When NodeB is restarted, the HARQ that self supports is merged type information notify a public entities that is arranged in the network to preserve; SNC regularly obtains the HARQ merging type information that NodeB supports from described public entities.
The above is for SRNC provided by the invention obtains several concrete grammars that HARQ that NodeB supports merges type information.In the real network, can also obtain the HARQ merging type information that NodeB supports by other method.Below only be that the present invention does not limit concrete acquisition methods for example.
The HARQ that the present invention supports the NodeB that gets access to merges type information and stores SRNC this locality into, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, merge type when only supporting that CC merges type (CC only) or only supporting that IR merges type (IR only) if inquire HARQ that this NodeB supports, then set up and do not comprise the cell that carries HARQ merging type information in message or the radio link reconfiguration message at Radio Link; Merge type for not only supporting CC to merge type but also supporting IR to merge type (IR+CC) if inquire the HARQ of NodeB support, then handle by existing procedure, promptly set up at Radio Link and carry HARQ merging type information in message or the radio link reconfiguration message, NodeB merges processing according to the merging type of appointment to the data that receive.
In sum, the idiographic flow of the inventive method comprises the steps: as shown in Figure 2
Step S11, change the present condition " presence " that is of HARQ Info for E-DCH cell into optional " O " by essential " M ";
Step S12, SRNC obtain and store the HARQ merging type information that base station node B is supported;
Step S13, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, inquire the HARQ that this NodeB supports and merge type;
Step S14, judging that the HARQ that NodeB supports merges whether type is CC only or IR only, is not CC only or IR only, then execution in step S15 if the HARQ that NodeB supports merges type; Otherwise, execution in step S16;
Step S15, send Radio Link according to prior art to NodeB and set up message or radio link reconfiguration message;
Step S16, SRNC send Radio Link to NodeB and set up message or radio link reconfiguration message, set up not comprise in message or the radio link reconfiguration message at described Radio Link and carry the cell (promptly not comprising HARQ Info for E-DCH cell) that HARQ merges type information.
In the said method flow process, the NodeB record of might SRNC preserving is not very comprehensive, when SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, if not in the recorded information of local search to this NodeB, then adopt existing procedure to handle, promptly set up at Radio Link and carry HARQ merging type information in message or the radio link reconfiguration message, the HARQ that indicates this NodeB to use SRNC to select merges type; When NodeB did not support that the HARQ of SRNC selection merges type, the HARQ that returns its support to SRNC merged type information; SRNC merges type information at the HARQ of its support that this locality preservation NodeB returns.
In order further to reduce signaling consumption, can only store HARQ merging type in SRNC is the NodeB record of CConly and IR only; , when setting up message or radio link reconfiguration message,, then handles NodeB transmission Radio Link at SRNC by existing procedure if do not inquire the corresponding record of this NodeB.
In sum, adopt the inventive method, after the HARQ merging type of SRNC understanding Node B support is IR only or CC only, three message in link establishment: all need not to carry HARQ among Radio Link Setup Request, Radio Link Reconfiguration Request or the Radio Link Reconfiguration Prepare and merge type information, save a large amount of signaling consumptions.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (13)
1, the automatic repeat requests HARQ processing method of a kind of mixing is characterized in that, comprising:
Service wireless network controller SRNC obtains and stores the HARQ merging type information that base station node B is supported;
At SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, merge type for only supporting Cai Si merging (ChaseCombining only) type or only supporting incremental redundancy to merge (Incremental redundancyCombining only) type if inquire the HARQ of this NodeB support, then set up not comprise in message or the radio link reconfiguration message and carry the cell that HARQ merges type information at described Radio Link.
2, the method for claim 1 is characterized in that, the present condition " presence " that is of Radio Link being set up the enhanced dedicated HARQ information HARQ Info for E-DCH cell in the message changes optional " O " into by essential " M ";
At SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, to merge type be Chase Combining only type or Incremental redundancy Combining only type if inquire HARQ that this NodeB supports, then sets up at described Radio Link not comprise HARQ Info for E-DCH cell in message or the radio link reconfiguration message;
After NodeB finished Radio Link foundation, the HARQ that this NodeB that SRNC preserves this locality supports merged the corresponding portable terminal that type notification is set up Radio Link.
3, the method for claim 1 is characterized in that, described SRNC obtains the HARQ merging type that NodeB supports, comprising:
The HARQ that A, control radio network controller CRNC obtain the NodeB support of being administered merges type information;
The HARQ that the corresponding NodeB that B, CRNC will obtain supports merges type information and preserves by RNC around the Iur interface notice.
4, method as claimed in claim 3 is characterized in that, described steps A comprises:
A1, NodeB merge type information by audit response (AUDIT RESPONSE) signaling with the HARQ that self supports and are notified to CRNC after receiving audit request (AUDIT REQUEST) signaling that CRNC issues; Perhaps
A2, NodeB initiatively merge type information with the HARQ that self supports by resource status indication (RESOURCE STATUS INDICATION) signaling and are notified to CRNC.
5, method as claimed in claim 3 is characterized in that, described step B comprises:
B1, after CRNC is restarted, by restarting the Reset process, RNC preserved around the HARQ that the NodeB that is administered is supported merged the type information notice; Perhaps
B2, by the information exchange Information Exchange process between the RNC, RNC preserved around the HARQ that CRNC supports the NodeB that is administered merged the type information notice.
6, method as claimed in claim 5 is characterized in that, described step B2 comprises:
RNC begins request message INFORMATIONEXCHANGE INITIATION REQUEST to described CRNC transmission information exchange on every side, adds the HARQ Info cell of request HARQ information in this message;
Described CRNC return information exchange beginning response message INFORMATION EXCHANGEINITIATION RESPONSE adds cell in this message, carry the HARQ merging type information that its NodeB that administers supports; Perhaps
Described CRNC is the information report message of RNC transmission towards periphery INFORMATIONREPORT regularly, adds cell in this message, carries the HARQ merging type information that its NodeB that administers supports; Perhaps
When the quantity of the NodeB that described CRNC administered changes or the NodeB that administered supports HARQ merges type and changes, CRNC RNC towards periphery sends INFORMATIONREPORT, in this message, add cell, carry the HARQ merging type information that its NodeB that administers supports.
7, method as claimed in claim 6 is characterized in that, when whole NodeB that described CRNC administered support that identical HARQ merges type, in the cell of described interpolation, only need carry the corresponding sign that HARQ that NodeB supports merges type; Receiving terminal parses the HARQ that NodeB that described CRNC administers supports according to described sign and merges type;
When the HARQ merging type of the NodeB support that CRNC administered is incomplete same, in the cell of described interpolation, need carry the HARQ that each NodeB identifies and this NodeB the supports merging type information that CRNC administers.
8, the method for claim 1 is characterized in that, described SRNC obtains the HARQ that NodeB supports and merges type, comprising: by the operational administrative platform HARQ of the NodeB that obtains and support thereof is merged the type information human configuration and store in described SRNC.
9, the method for claim 1 is characterized in that, described SRNC obtains the HARQ merging type that NodeB supports, comprising: when NodeB is restarted, the HARQ that self supports is merged the type information notice be attached thereto all RNC that connect.
10, the method for claim 1 is characterized in that, described SRNC obtains the HARQ merging type that NodeB supports, comprising: when NodeB is restarted, the HARQ that self supports is merged type information notify a public entities that is arranged in the network to preserve; Described SNC obtains the HARQ merging type information that NodeB supports from described public entities.
11, the method for claim 1, it is characterized in that, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, if do not merge type to the HARQ that this NodeB supports at local search, be that Chase Combining and Incrementalredundancy Combining support type then according to Node B, set up at described Radio Link and to carry HARQ information in message or the radio link reconfiguration message, the HARQ that indicates this NodeB to use SRNC to select merges type;
When NodeB did not support that the HARQ of SRNC selection merges type, the HARQ that returns its support to SRNC merged type information; SRNC merges type information at the HARQ of its support that this locality preservation NodeB returns.
12, the method for claim 1, it is characterized in that, at SRNC when NodeB sends Radio Link and sets up message or radio link reconfiguration message, if inquiring the HARQ merging type of this NodeB support is that Chase Combining and Incremental redundancy Combining support type, then handle by existing procedure.
13, the method for claim 1 is characterized in that, only storing HARQ merging type in SRNC is the NodeB record of Chase Combining only type and Incremental redundancy Combiningonly type; , when setting up message or radio link reconfiguration message,, then handles NodeB transmission Radio Link at SRNC by existing procedure if do not inquire the corresponding record of this NodeB.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005101327863A CN1996819B (en) | 2005-12-26 | 2005-12-26 | A mixed processing method for automatic retransfer request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005101327863A CN1996819B (en) | 2005-12-26 | 2005-12-26 | A mixed processing method for automatic retransfer request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1996819A true CN1996819A (en) | 2007-07-11 |
| CN1996819B CN1996819B (en) | 2010-04-21 |
Family
ID=38251780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2005101327863A Expired - Fee Related CN1996819B (en) | 2005-12-26 | 2005-12-26 | A mixed processing method for automatic retransfer request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1996819B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010015199A1 (en) * | 2008-08-05 | 2010-02-11 | 华为技术有限公司 | Method, device and system for network resource configuration |
| CN101588652B (en) * | 2008-05-23 | 2011-06-01 | 上海贝尔阿尔卡特股份有限公司 | Base station for network or cooperation MIMO system and HARQ method thereof |
| CN102761952A (en) * | 2011-04-28 | 2012-10-31 | 华为技术有限公司 | Method, equipment and system for synchronizing states of physical layers |
| CN102821426A (en) * | 2008-08-05 | 2012-12-12 | 华为技术有限公司 | Network resource configuration method, equipment and system |
| CN101409610B (en) * | 2007-10-02 | 2013-10-30 | 领特德国有限公司 | Retransmission and retransmission request in data communication systems |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1186899C (en) * | 2002-01-17 | 2005-01-26 | 北京邮电大学 | Hybrid automatic request retransmission technology |
| AU2002315928A1 (en) * | 2002-04-09 | 2003-10-23 | Nec Australia Pty Ltd | Improved signalling scheme for high speed downlink packet access |
-
2005
- 2005-12-26 CN CN2005101327863A patent/CN1996819B/en not_active Expired - Fee Related
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409610B (en) * | 2007-10-02 | 2013-10-30 | 领特德国有限公司 | Retransmission and retransmission request in data communication systems |
| CN101588652B (en) * | 2008-05-23 | 2011-06-01 | 上海贝尔阿尔卡特股份有限公司 | Base station for network or cooperation MIMO system and HARQ method thereof |
| WO2010015199A1 (en) * | 2008-08-05 | 2010-02-11 | 华为技术有限公司 | Method, device and system for network resource configuration |
| CN101646238B (en) * | 2008-08-05 | 2012-08-15 | 华为技术有限公司 | Method, device and system for configuring network resources |
| CN102821426A (en) * | 2008-08-05 | 2012-12-12 | 华为技术有限公司 | Network resource configuration method, equipment and system |
| CN102821426B (en) * | 2008-08-05 | 2017-04-12 | 华为技术有限公司 | Network resource configuration method, equipment and system |
| CN102761952A (en) * | 2011-04-28 | 2012-10-31 | 华为技术有限公司 | Method, equipment and system for synchronizing states of physical layers |
| WO2012146082A1 (en) * | 2011-04-28 | 2012-11-01 | 华为技术有限公司 | Method, device and system for physical layer status synchronization |
| CN102761952B (en) * | 2011-04-28 | 2014-12-24 | 华为技术有限公司 | Method, equipment and system for synchronizing states of physical layers |
| US9313755B2 (en) | 2011-04-28 | 2016-04-12 | Huawei Technologies Co., Ltd. | Method, device, and system for synchronizing physical layer state |
| US9998992B2 (en) | 2011-04-28 | 2018-06-12 | Huawei Technologies Co., Ltd. | Method, device, and system for synchronizing physical layer state |
| US10313972B2 (en) | 2011-04-28 | 2019-06-04 | Huawei Technologies Co., Ltd. | Method, device, and system for synchronizing physical layer state |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1996819B (en) | 2010-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2456273B1 (en) | Method, system and device for distributing resources of base station node | |
| CN102395168B (en) | Mobile communications cell changing procedure | |
| CN100384271C (en) | Method and apparatus for handling roaming lists in a wireless communication system | |
| US8982787B2 (en) | Method and apparatus for connecting to network from mobile terminal | |
| CN100488286C (en) | HSDPA resource management method for multi-carrier TD-SCDMA system | |
| CN101283613A (en) | Fast cell selection method and apparatus for high speed downlink packet access system | |
| CN1996819B (en) | A mixed processing method for automatic retransfer request | |
| US20140348037A1 (en) | Method for updating system information, access network equipment and user equipment | |
| CN102143498A (en) | Method and system for multi-standard joint communication and wireless network control equipment | |
| CN102014365A (en) | Method and system for selecting core network operator from radio network sharing | |
| CN101426254A (en) | Method, apparatus and system for information transmission implementation | |
| CN101198092B (en) | Method, system and device for transmitting data to user's set | |
| CN101179858B (en) | Method for obtaining capability information of user facility | |
| CN102547668B (en) | Dual-mode terminal ability information processing method, dual-mode terminal and network side device | |
| CN1913698A (en) | Terminal carrier frequency information interactive method between radio network controller of multiple carrier frequency system | |
| CN101588571B (en) | Method, device and system for managing position based on S1 uniform interface | |
| CN101651897A (en) | Method, device and system for scheduling radio resources | |
| CN101801029A (en) | Method, device and system for managing cell | |
| CN101242218A (en) | Method and system for sending data to user device | |
| CN103037356A (en) | Communication method and communication device | |
| CN103053185B (en) | Network name processing method and mobility management network element device | |
| CN102625361B (en) | data distribution method and base station, data distribution access device | |
| JP5080486B2 (en) | Cell merge capability notification | |
| CN104303473A (en) | Flow control method and apparatus of operator sharing network | |
| CN100502559C (en) | Method for quick switching of service link |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100421 Termination date: 20141226 |
|
| EXPY | Termination of patent right or utility model |