CN101626600A - HSDPA resource management method in multi-carrier TD-SCDMA system - Google Patents
HSDPA resource management method in multi-carrier TD-SCDMA system Download PDFInfo
- Publication number
- CN101626600A CN101626600A CN200910203717A CN200910203717A CN101626600A CN 101626600 A CN101626600 A CN 101626600A CN 200910203717 A CN200910203717 A CN 200910203717A CN 200910203717 A CN200910203717 A CN 200910203717A CN 101626600 A CN101626600 A CN 101626600A
- Authority
- CN
- China
- Prior art keywords
- hsdpa
- resource
- node
- carrier
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses an HSDPA resource management method in a multi-carrier TD-SCDMA system. When a node B reports the change of the capacity and/or resource operation status of a cell to an RNC, the method comprises the following step: reporting resource status indication information or audit response information to the RNC by the node B, wherein HS-DSCH resource information IE in the information contains carrier information. By adopting the method and the device, HSDPA resources on the multi-carrier can be managed reasonably, thereby the management efficiency of the HSDPA resources on the multi-carrier is improved, the foundation can be provided for multi-carrier HSDPA transmission, the higher peak value data speed can be further provided for a multi-carrier HSDPA user terminal, and the data throughput and the spectrum efficiency of the cell are improved.
Description
The application is to be that February 23, application number in 2006 are 200610055132.X the applying date, the invention name
The dividing an application of application that is called " the HSDPA method for managing resource in the multi-carrier TD-SCDMA system ".
Technical field
The present invention relates to the broadband wireless data communication technology field, relate in particular to the management method that a kind of multi-carrier time-division synchronous code division multiple access accesses high speed downlink packet access (HSDPA) resource in (TD-SCDMA) system.
Background technology
High speed downlink packet access (HSDPA) is a kind of technology of raising Time Division-Synchronous Code Division Multiple Access access (TD-SCDMA) system descending message transmission rate, that 3GPP standardization body proposes in order to satisfy in the system standard of the asymmetric demand of up-downgoing data service by R5 (Release 5) version, can under existing TD-SCDMA system network architecture, user's downlink service data speed be brought up to more than the 2.8Mbps.
Fig. 1 is the residential quarter part configuration diagram of WCDMA or TD-SCDMA system. As shown in Figure 1, the TD-SCDMA system comprises radio network controller (RNC), Node B (Node B) and subscriber equipment (UE). The resource relevant with HSDPA comprises high-speed physical downlink shared channel (HS-PDSCH) (HS-PDSCH, High Speed-Physical Downlink Shared Channel) in the residential quarter of TD-SCDMA system, is used for transmit traffic data; High-Speed Shared Control Channel (HS-SCCH, High Speed-Shared Control Channel), be used for transmitting signaling information and high-speed shared information channel (HS-SICH, High Speed-Shared Information Channel), be used for the control information of transmission user equipment feedback.
Relevant HSDPA resource comes to be this cell configuration/reshuffle by RNC by Physical Shared Channel (the Physical shared channel reconfiguration) process of reshuffling in residential quarter. RNC judges whether that according to Zone model etc. needs reserve the HSDPA resource in the residential quarter. If need to reserve the HSDPA resource, then RNC sends Physical Shared Channel reprovision request (PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST) message and sets up HSDPA resource in the residential quarter to Node B, can also be by the HSDPA resource in this message reprovision/deletion residential quarter.
The relevant HSDPA resource of UE determines whether that according to factors such as the data throughout of this UE, QoS needs are that it distributes by RNC. If necessary, RNC sends wireless link request (Radio Link Setup Request) and/or radio link reconfiguration request (Radio Link Reconfiguration Prepare or Radio Link Reconfiguration Request) message to Node B, requires Node B to distribute the HSDPA resource. Node B responds this request, carries out the HSDPA resource and distributes, and then informs RNC by response message. This response message comprises high speed descending sharing channel TDD mode response cell (HS-DSCH TDD Information Response IE). HS-DSCH TDD Information Response IE comprises the information such as HS-SCCH, HS-SICH and mixed automatic repeat request (HARQ) partition holding. RNC and then with this information notification UE, thus realize the distribution of HSDPA resource.
When the ability (Capability) of a residential quarter and/or its resource operation state (Resource operational state) when changing, Node B will use resource status indication (Resource status indication) message to report to RNC, in addition, Node B can also use audit response (AUDIT RESPONSE) message to RNC report resource operation state.
The specific descriptions of relevant above-mentioned message see also the standard document " 3GPP TS 25.433 v5.13.0 " of 3GPP standardization body.
In order further to improve the downlink service data transfer rate in the TD-SCDMA system, the technology trends of current TD-SCDMA system is that the multicarrier concept is introduced in wave point (Air Interface) technology, makes the residential quarter of a TD-SCDMA system can support wireless transmission on a plurality of carrier waves. HSDPA residential quarter in this multi-carrier TD-SCDMA system can provide about N doubly to single carrier HSDPA terminal use's peak data rate, and wherein N is the number of the supported carrier wave in residential quarter, thereby can significantly improve cell throughout and spectrum efficiency.
In this multi-carrier HSDPA TD-SCDAM system, the HSDPA resource management action of distributing relevant HSDPA resource etc. to be correlated with for the relevant HSDPA resource of cell configuration/reshuffle with for UE all need to be carried out for multicarrier.
In the multi-carrier TD-SCDMA system scheme of current suggestion, Node B applying portion (NBAP, Node B Application Part) agreement does not have the ability of the part success of report Physical Shared Channel reconfiguration request, namely, according to resource allocation information relevant with HSDPA in the Physical Shared Channel reconfiguration request, Node B finishes resource distribution on the some of them carrier wave/reprovision Value Operations only, but during the resource distribution on the whole carrier waves that can not support to ask/reconfiguration operation, Node B can not report this situation to RNC, and Node B can only refuse this Physical Shared Channel reconfiguration request in this case. RNC will resend the Physical Shared Channel reconfiguration request again to dispose the HSDPA resource.
In the multi-carrier TD-SCDMA system scheme of current suggestion, the ability of in resource situation indication and checking response message, also not reporting for the HSDPA resource operation state of each carrier wave. And in Radio Link increase request (Radio link addition request) message, there is not relevant HSDPA information. This means in Node B and in the handoff procedure of minizone, when the HSDPA in the UE use cell-of-origin, can not in Target cell, set up simultaneously DCH and HSDPA related resource.
In addition, because the public-measurement relevant with HSDPA (Common Measurement) in the existing TD-SCDMA system schema is based on a residential quarter, in the residential quarter of a support multicarrier, RNC will be difficult to judge which carrier wave has good HSDPA performance, and this will reduce the performance of RRM. Described relevant amending advice about multi-carrier HSDPA TD-SCDAMA system is please specifically referring to " revision of the TC5-WG9-2005-065Q-of CCSA multi-carrier HSDPA Iub interface ".
In sum, in the multi-carrier TD-SCDMA system scheme of current suggestion, still can not effectively manage the HSDPA resource for multicarrier.
Summary of the invention
In view of this, the main purpose of the embodiment of the invention is to provide the method for managing resource of the HSDPA in a kind of multi-carrier TD-SCDMA system, thereby reasonably the HSDPA resource on the multicarrier is managed, improve the efficiency of management of the HSDPA resource on the multicarrier, provide the basis for carrying out multi-carrier HSDPA transmission, and then higher peak data rates is provided, improves cell data handling capacity and spectrum efficiency for the multi-carrier HSDPA user terminal.
For achieving the above object, the technical scheme in the embodiment of the invention is achieved in that
HSDPA method for managing resource in a kind of multi-carrier TD-SCDMA system as Node B during to the change of the ability of a residential quarter of RNC report and/or resource operation state, comprises step:
Node B sends Resource status indication message or AUDIT RESPONSE message to RNC, has carrier information among the HS-DSCH Resources Information IE in the described message.
HSDPA method for managing resource in a kind of multi-carrier TD-SCDMA system also is provided in the embodiments of the invention, when switch the minizone in carrying out Node B, has comprised step:
RNC sends RADIO LINK ADDITION REQUEST message to Node B, has HS-DSCH TDD Information IE in this message;
Node B receives described message, sends RADIO LINK ADDITION RESPONSE message to RNC, has HS-DSCH TDD Information Response IE in this message.
Also there are HS-DSCH-RNTI IE, HS-PDSCH RL ID IE in the described RADIO LINK ADDITION REQUEST message.
HSDPA method for managing resource in a kind of multi-carrier TD-SCDMA system also is provided in the embodiments of the invention, when carrying out the relevant public-measurement of HSDPA, in the Common measurement initiation request message that RNC sends to Node B, Common Measurement Type IE and frequency point information UARFCN IE are associated.
The public-measurement that described HSDPA is relevant comprises: the bit rate that all are not provided by transmission carrier power, HS-DSCH power demand, the HS-DSCH of the code word of HS-PDSCH or HS-SCCH use.
The method according to this invention can realize effective management to the HSDPA resource to the support of the part success of Physical Shared Channel reconfiguration request, to improve running efficiency of system.
After adding HS-DSCH TDD Information IE to wireless link increasing request message, when UE has the HSDPA resource in the cell-of-origin, can on the lub interface, use Radio Link to increase request when switch the minizone in it carries out Node B and in Target cell, set up corresponding HSDPA resource, make the minizone in the Node B switch more efficient.
As Node B during to the change of the ability of a residential quarter of RNC report and/or resource operation state, Node B is by described amended NBAP protocol message, be Resource status indication message or AUDIT RESPONSE message, can report to RNC for the HSDPA related resource mode of operation on each carrier wave, thereby improve the efficient that Node B reports.
Description of drawings
Fig. 1 is the residential quarter part configuration diagram of WCDMA or TD-SCDMA system.
Fig. 2 is the schematic flow sheet according to the management method of HSDPA resource of the present invention.
The specific embodiment
For making the purpose, technical solutions and advantages of the present invention express clearlyer, the present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
The relevant information of hereinafter mentioning and the associated description of form see also the standard document " 3 GPP TS, 25.433 v5.13.0 " of 3GPP standardization body and the standard document " revision of TC5-WG9-2005-065Q-multi-carrier HSDPA Iub interface " of CCSA.
The present invention realizes the effective management to the HSDPA resource by supporting the part success of Physical Shared Channel reconfiguration request.
According to the management method of HSDPA resource provided by the invention, as shown in Figure 2, the Physical Shared Channel reconfiguration request that RNC sends to Node B, Node B responds this request, and disposes the HSDPA resource according to the configuring condition that Node B supports.
If Node B supports the partial configuration in the described channel reconfiguration request, then be the partial configuration of supporting set up/reshuffle/delete the HSDPA resource, and Node B refuses other partial configurations that it is not supported, and to RNC report failure cause.
If Node B supports the partial configuration in the described channel reconfiguration request, such as the configuration of HS-PDSCH and/or HS-SCCH, Node B reports the situation of this partial configuration success to RNC by NBAP. Successful configuration can move at Node B first, can not dispose the reason of HSDPA resource and can report to RNC by PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE and/or PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. Can avoid like this causing the HSDPA of whole residential quarter unavailable because of the failure of partial configuration.
The management that further specifies according to HSDPA resource of the present invention below by the description to specific implementation process is how to dispose the HSDPA resource and report the failure cause of not supporting the HSDPA relevant configuration.
In the specific embodiment 1 of Physical Shared Channel reconfiguration course, according to the management method of HSDPA resource provided by the invention, to providing as follows of Physical Shared Channel reprovision process:
If Node B can support the configuration all about HS-PDSCH and HS-SCCH in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, Node B should store Configuration Generation ID IE, these resources can be used the present and the future's HS-DSCH transmission channel, and send PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE.
For example, when being configured for the HS-PDSCH channel, PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message comprises HS-PDSCH TDD Information IE, and then Node B will judge:
If HS-PDSCH TDD Information IE does not comprise any DL Timeslot and Code Information LCR per UARFCN IE, then delete all existing HS-PDSCH resources in the residential quarter.
If DL Timeslot and Code Information LCR per UARFCN IE exists, but wherein do not comprise any DL Timeslot and Code Information LCR IE, but comprise UARFCN IE, then delete all the existing HS-PDSCH resources on the indicated carrier wave of this UARFCN IE. HSDPA resource distribution on other carrier waves is unaffected.
If DL Timeslot and Code Information LCR per UARFCN IE had both comprised DL Timeslot and Code Information LCR IE and had also comprised UARFCN IE, and all do not dispose the HS-PDSCH resource on the indicated carrier wave of this UARFCN IE, then dispose HS-PDSCH resource on the corresponding carriers according to the DL Timeslot and Code Information LCR IE on each carrier wave.
If DL Timeslot and Code Information LCR per UARFCN IE had both comprised DL Timeslot and Code Information LCR IE and had also comprised UARFCN IE, but disposed the HS-PDSCH resource on the indicated carrier wave of this UARFCN IE, then disposed to replace original HS-PDSCH resource distribution of corresponding carriers with the DL Timeslot and Code Information LCR IE on each carrier wave.
If Node B can support all configurations on certain carrier wave, then according to request, the HSDPA resource success on this carrier wave of foundation/reprovision/deletion. Specifically, if Node B can support the configuration all about HS-PDSCH and HS-SCCH of this carrier wave in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, Node B makes these resources can use the present and the future's HS-DSCH transmission channel
If Node B can not support all configurations on certain carrier wave, the HSDPA resource on this carrier wave can not successfully be established/reprovision/deletion. Node B reports the unsuccessful reason of HSDPA resource of this carrier wave to RNC by PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
And in this FAILURE message, comprise Cause IE.
If the HSDPA resource distribution on all carrier waves can not support that all Cause IE can be single general cause value, or the value relevant with the carrier wave that causes failure.
If only have the HSDPA resource distribution on the partial carrier wave not support, Cause IE is the value relevant with the carrier wave that causes failure. To refuse the HSDPA relevant configuration on the failed carrier wave among the Node B, the resource that disposes on the carrier wave can be used the present and the future's HS-DSCH transmission channel.
The Physical Shared Channel reconfiguration request message sees also " revision of the TC5-WG9-2005-OB5Q-of CCSA multi-carrier HSDPA Iub interface ", just wherein the scope (Range) of DL Timeslot and Code Information LCR IE from 1..＜maxnoofDLtsLCR change 0..＜maxnoofDLtsLCR into.
Table 1 is the particular content of PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message.
Table 1PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| PUSCH Sets To Delete | 0..<maxnoof PUSCHSets> | GLOBAL | reject | |||
| >PUSCH Sets ID | M | 9.2.3.13 | - | |||
| HS-PDSCH TDD Information | 0..1 | GLOBAL | reject | |||
| Omit ... |
| DL Timeslot and Code Information LCR per UARFCN | 0..<max Frequency inCell> | 1.28Mcps the TDD system is essential, is not suitable for 3.84Mcps TDD system | - | |||
| >>DL Timeslot and Code Information LCR | 0..<maxnoof DLLsLCR> | - | ||||
| >>>Time Slot LCR | M | 9.2.3.24a | - | |||
| Omit ... |
Modification to Physical Shared Channel reconfiguration failure (PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE) message content is as shown in table 2, the content of the zone of grey for revising in the table:
Table 2PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| CHOICE Cause Level | M | YES | ignore | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >Set Specific | TDD Only | - | ||||
| >>Unsuccessful DL Shared Channel Set | 0..<maxnoof PDSCHSets> | EACH | ignore | |||
| >>>PDSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| >>Unsu ccessful UL Shared Channel Set | 0..<maxnoof PUSCHSets> | EACH | ignore | |||
| >>>PUSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | YES | ignore | ||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HSDPA UARFCN | 0..<max Frequency inCell> | EACH | ignore | |||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| Criticality Diagnostics | O | 9.2.1.17 | YES | ignore |
| Range Bound | Explanation |
| maxnoofPDSCHSets | Maximum number of PDSCH Sets in a cell |
| maxnoofPUSCHSets | Maximum number of PUSCH Sets in a cell |
| maxFrequencyinCell | Maximum number of Frequency that can be defined in a Cell |
In the specific embodiment 2 of Physical Shared Channel reconfiguration course, difference from Example 1 is: whether separate the HS-SCCH on certain carrier wave and the configuration successful of HS-PDSCH be.
Concrete regulation to Physical Shared Channel reprovision process is as follows:
If Node B can support the configuration all about HS-PDSCH and HS-SCCH in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, Node B should store Configuration Generation ID IE, these resources can be used the present and the future's HS-DSCH transmission channel, and send PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE.
If Node B can support all the HS-SCCH relevant configuration on certain carrier wave, the HS-SCCH resource on this carrier wave should be regarded as foundation/reprovision/delete successfully, and Node B makes these resources can use the present and the future's HS-DSCH transmission channel. Node B reports that by PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE HS-SCCH disposes the failure cause of unsuccessful carrier wave.
If Node B can support all the HS-PDSCH relevant configuration on certain carrier wave, the HS-PDSCH resource on this carrier wave is regarded as foundation/reprovision/delete successfully, and Node B makes these resources can use the present and the future's HS-DSCH transmission channel. Node B reports that by PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE HS-PDSCH disposes the failure cause of unsuccessful carrier wave.
Comprise Cause IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message. Cause IE can be single general cause value, or causes the value that the specific carriers of failure is relevant with each.
The mode such as following table 3 or table 4 is adopted in the modification of PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message, is the content through revising in the table in the zone of grey.
Table 3PHTSICAL SHARED CHANNEL RECONFIGURATION FAILURE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| CHOICE Cause Level | M | YES | ignore | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >Set Specific | TDD Only | - | ||||
| >>Unsuccessful DL Shared Channel Set | 0..<maxnoof PDSCHSets> | EACH | ignore | |||
| >>>PDSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| >>Unsuccessful UL Shared Channel Set | 0..<maxnoof PUSCHSets> | EACH | ignore | |||
| >>>PUSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | YES | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HS-PDSCH UARFCN | 0..<max Frequency inCell> | EACH | ||||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | YES | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HS-SCCH UARFCN | 0..<max Frequency inCell> | EACH | ||||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| Criticality Diagnostics | O | 9.2.1.17 | YES | ignore |
| Range Bound | Explanation |
| maxnoofPDSCHSets | Maximum number of PDSCH Sets in a cell |
| maxnoofPUSCHSets | Maximum number of PUSCH Sets in a cell |
| maxFrequencyinCell | Maximum number of Frequency that can be defined in a cell |
Table 4PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
| IE/Group Name | Pre- Sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| CHOICE Cause Level | M | YES | ignore | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >Set Specific | TDD Only | - | ||||
| >>Unsuccessful DL Shared Channel Set | 0..<maxnoof PDSCHSets> | EACH | ignore | |||
| >>>PDSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| >>Unsuccessful UL Shared Channel Set | 0..<maxnoof PUSCHSets> | EACH | ignore | |||
| >>>PUSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | YES | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | For HS-PDSCH | - | ||
| >>Cause | O | 9.2.1.6 | For HS-SCCH | - | ||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HS-PDSCH UARFCN | 0..<max Frequency inCell> | EACH | ||||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| >>Unsuccessful HS-SCCH UARFCN | 0..<max Frequency inCell> | EACH | ||||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| Criticality Diagnostics | O | 9.2.1.17 | YES | ignore |
| Range Bound | Explanation |
| maxnoofPDSCHSets | Maximum number of PDSCH Sets in a cell |
| maxnoofPUSCHSets | Maximum number of PUSCH Sets in a cell |
| maxFrequencyinCell | Maximum number of Frequency that can be defined in a Cell |
In the specific embodiment 3 of Physical Shared Channel reconfiguration course, in order to support the part success of Physical Shared Channel reprovision request, Node B PHYSICAL SHARED CHANNEL RECONFIGURATION ESPONSE message and PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message made amendment, so that can report the failure cause of unsuccessful carrier wave.
At this, to providing as follows of Physical Shared Channel reprovision process:
If Node B can support the configuration all about HS-SCCH in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, Node B namely sends PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message.
If Node B can not support the configuration all about HS-SCCH in the PHYSICAL SHARED CHANNEL RECONFIGURATON REQUEST message, Node B should send PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
If Node B can support the configuration all about HS-PDSCH in the PHYSICAL SHARED CHANNEL RECONFIGURATON REQUEST message, and Node B does not need to carry out the configuration of HS-SCCH, and Node B should send PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message. If Node B can not support the configuration all about HS-PDSCH in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then should send PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message or PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
Can comprise Cause IE in PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message or the PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message.
If the HS-PDSCH on all carrier waves configuration can not support that all Cause IE can be single general cause value, or cause the value that the specific carriers of failure is relevant with each. If only have the HS-PDSCH resource distribution on the partial carrier wave not support, Cause IE causes the value that the specific carriers of failure is relevant with each. To refuse the configuration on the failed carrier wave among the Node B, the resource that disposes on the carrier wave can be used the present and the future's HS-DSCH transmission channel.
Correspondingly lower shown in table 5, table 6 to the modification of PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE and PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message, be the content through revising in the table in the zone of grey:
Table 5PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| Criticality Diagnostics | O | 9.2.1.17 | YES | ignore | ||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | YES | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HS-PDSCH UARFCN | 0..<max Frequency inCell> | EACH | ||||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - |
Table 6PHYSICA SHARED CHANNEL RECONFIGURATION FAILURE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| CHOICE Cause Level | M | YES | ignore | |||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >Set Specific | TDD Only | - | ||||
| >>Unsuccessful DL Shared Channel Set | 0..<maxnoof PDSCHSets> | EACH | ignore | |||
| >>>PDSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| >>Unsuccessful UL Shared Channel Set | 0..<maxnoof PUSCHSets> | EACH | ignore | |||
| >>>PUSCH Set ID | M | 9.2.3.13 | - | |||
| >>>Cause | M | 9.2.1.6 | - | |||
| CHOICE Cause Level | O | Be only applicable to use the 1.28Mcps of multi-carrier frequency | YES | ignore |
| The TDD system | ||||||
| >General | - | |||||
| >>Cause | M | 9.2.1.6 | - | |||
| >UARFCN Specific | - | |||||
| >>Unsuccessful HS-PDSCH UARFCN | 0..<max Frequency inCell> | EACH | ignore | |||
| >>>UARFCN | M | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Cause | M | 9.2.1.6 | - | |||
| Criticality Diagnostics | O | 9.2.1.17 | YES | ignore |
| Range Bound | Explanation |
| maxnoofPDSCHSets | Maximum number of PDSCH Sets in a cell |
| maxnoofPUSCHSets | Maximum number of PUSCH Sets in a cell |
| maxFrequencyinCell | Maximum number of Frequency that can be defined in a Cell |
In the specific embodiment 4 of Physical Shared Channel reconfiguration course, PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message can only dispose a HSDPA related resource on the carrier frequency at every turn, if Node B can support the configuration all about HS-PDSCH and HS-SCCH in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, Node B should send PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE.
For example, when being configured for the HS-PDSCH channel, comprise HS-PDSCH TDD Information IE in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, then Node B will judge:
If HS-PDSCH TDD Informat ion IE does not comprise any DL Timeslot and Code Information LCR IE and UARFCN IE, then Node B deletes all existing HS-PDSCH resources in the residential quarter.
If HS-PDSCH TDD Information IE does not comprise any DL Timeslot and Code Information LCR IE, but comprise UARFCN IE, then Node B deletes all the existing HS-PDSCH resources on the indicated carrier wave of this UARFCN IE.
If HS-PDSCH TDD Information IE comprises DL Timeslot and Code Information LCR IE and UARFCN IE, and do not dispose the HS-PDSCH resource on the indicated carrier wave of UARFCN IE, then dispose HS-PDSCH resource on this carrier wave according to DL Timeslot and Code Information LCR IE.
If HS-PDSCH TDD Information IE comprises DL Timeslot and Code Information LCR IE and UARFCN IE, and disposed the HS-PDSCH resource on the indicated carrier wave of UARFCN IE, then replace original HS-PDSCH resource distribution of this carrier wave with the configuration of this DL Timeslot and Code Information LCR IE.
If Node B can not support all configurations, then should refuse all configurations in the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, and send PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message, and in this message, comprise Cause IE.
PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message can with reference to 3GPP TS25.433v5.13.0, also can adopt the mode of table 2.
Correspondingly to modification such as the table 7 of PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message, the clipped in the table 7 is the content through revising referring to 3GPP TS25.433v5.13.0 in the zone of grey in the table:
Table 7PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticality | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| HS-PDSCH TDD Information | 0..1 | GLOBAL | reject | |||
| >DL Timeslot and Code Information | 0..<maxnoof DLts> | 3.84Mcps the TDD system is essential, is not suitable for 1.28Mcps TDD system | - | |||
| Omit ... | ||||||
| >>HS-PDSCH and HS-SCCH Total Power | O | Maximum Transmissi on Power 9.2.1.40 | HS-PDSCH knows the maximum transmission power that the HS-SCCH code word allows in the time slot | YES | reject | |
| >DL Timeslot and Code Information | 0..<maxnoof DLtsLCR> | 1.28Mcps the TDD system is essential, discomfort | - |
| LCR | Be used for 3.84Mcps TDD system | |||||
| >>Time Slot LCR | M | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>Codes LCR | 0..<maxnoof HSPDSCHs > | - | ||||
| >>>TDD Channelisation Code | M | 9.2.3.19 | - | |||
| >>HS-PDSCH and HS-SCCH Total Power | O | Maximum Transmissi on Power 9.2.1.40 | The maximum transmission power that HS-PDSCH and HS-SCCH code word allow in the time slot | YES | reject | |
| >UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| Add to HS-SCCH Resou rce Pool | 0..1 | GLOBAL | reject | |||
| >HS-SCCH Information | 0..<maxnoof HSSCCHs> | Be only applicable to 3.84Mcps TDD system | - | |||
| Omit ... | ||||||
| >>>TDD Channelisaation Code | M | 9.2.3.19 | - | |||
| >HS-SCCH Information LCR | 0..<maxnoof HSSCCHs> | Be only applicable to 1.28Mcps TDD system | GLOBAL | reject | ||
| >>HS-SCCH ID | M | 9.2.3.5Ga | - | |||
| >>Time Slot LCR | M | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>First TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Second TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Maximum HS-SCCH Power | M | DL Power 9.2.1.21 | - | |||
| >HS-SICH Information LCR | 1 | - | ||||
| >HS-SICH ID | M | 9.2.3.5Gb | - | |||
| >Time Slot LCR | M | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>TDD Channelisation Code | M | 9.2.3.19 | - | |||
| >>>UARFCN | O | 9.2.1.65 | Nt is referring to 3GPP TS 25.105 | - |
| Be only applicable to use the 1.28Mcps TDD system of multi-carrier frequency | ||||||
| Modify HS-SCCH Resource Pool | 0..1 | GLOBAL | reject | |||
| >HS-SCCH Information | 0..<maxnoof HSSCCHs> | Be only applicable to 3.84Mcps TDD system | - | |||
| Omit ... | ||||||
| >>>TDD Channelisaation Code | O | 9.2.3.19 | - | |||
| >HS-SCCH Information LCR | 0..<maxnoof HSSCCHs> | Be only applicable to 1.28Mcps TDD system | GLOBAL | reject | ||
| >>HS-SCCH ID | M | 9.2.3.5Ga | - | |||
| >>Time Slot LCR | O | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | O | 9.2.3.7A | - | |||
| >>First TDD Channelisation Code | O | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Second TDD Channelisation Code | O | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Maximum HS-SCCH Power | O | DL Power 9.2.1.21 | - | |||
| >>HS-SICH Information LCR | 0..1 | - | ||||
| >>>HS-SICH ID | M | 9.2.3.5Gb | - | |||
| >>>Time Slot LCR | O | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | O | 9.2.3.7A | - | |||
| >>TDD Channelisation Code | O | 9.2.3.19 | - | |||
| >>>UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| Delete from HS-SCCH Resouce Pool | 0..<maxnoof HSSCCHs> | GLOBAL | reject | |||
| >HS-SCCH ID | M | 9.2.3.5Ga | - | |||
| Configuration Generation ID | O | 9.2.1.16 | YES | reject |
In specific embodiments of the invention 5, management method according to HSDPA resource provided by the invention, when RNC determines that according to factors such as the data throughout of this UE, QoS needs distribute the HSDPA resource of being correlated with for it, RNC sends Radio Link Setup Request/Radio Link Reconfiguration Request/Radio Link Reconfiguration Prepare message to Node B, requires Node B to distribute the HSDPA resource. Node B responds this request, carries out the HSDPA resource and distributes, and then informs RNC by response message. HS-DSCH TDD Information Response IE in this response message only has a carrier wave cell for HS-PDSCH.
Among the HS-DSCH TDD Information Response IE that proposes in " revision of the TC5-WG9-2005-065Q-of CCSA multi-carrier HSDPA Iub interface " literary composition two carrier wave cells are arranged, Controlled Frequency IE as shown in following table 8 and UARFCN IE, what these two carrier wave cells referred to all is the frequency point information of distributing to the HS-PDSCH carrier wave of living in of UE. When two carrier frequency point information inconsistencies of indication in the HS-DSCH TDD Information Response IE that RNC receives, will bring the cost of unnecessary mistake processing to RNC, also might cause the failure of the response message at HS-DSCH TDD Information Response IE place.
Table 8HS-DSCH TDD Information Response IE
| IE/Group Name | Pre- sence | Range | IEType& Reference | Semantics Description | Criticallty | Assigned Criticallly |
| HS-DSCH MAC-d Flow Specific Information Response | 0..<maxnoof MACFlows> | - | ||||
| >HS-DSCH MAC-d Flow ID | M | 9.2.1.31 | - | |||
| >Binding ID | O | 9.2.1.4 | - | |||
| >Transport Layer Address | O | 9.2.1.63 | - | |||
| >HS-DSCH Initial Capacity Allocation | O | 9.2.1.31Ha | - | |||
| >HS-SCCH Specific Information Response | 0..<maxNoOf HSSCCHcod es> | Be not suitable for 1.28Mcps TDD system | GLOBAL | reject | ||
| >Time Slot | M | 9.2.3.23 | - | |||
| >Midamble Shift And Burst Type | M | 9.2.3.7 | - | |||
| >TDD Channelisation Code | M | 9.2.3.19 | - | |||
| >HS-SICH Information | 1 | - | ||||
| >>HS SICH ID | M | 9.2.3.5Gb | - | |||
| >>Time Slot | M | 9.2.3.23 | - | |||
| >>Midamble Shift And Burst Type | M | 9.2.3.7 | - | |||
| >>TDD Channelisation Code | M | 9.2.3.19 | - | |||
| HS-SCCH Specific Information Response LCR per UARFCN | 0..<maxHSD PAFrequenc y> | Be not suitable for 3.84Mcps TDD system | ||||
| >HS-SCCH Specific Information Response LCR | 1..<maxNoOf HSSCCHcod es> | GLOBAL | reject |
| >>Time Slot LCR | M | 9.2.3.24a | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>First TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Second TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>HS-SICH Information LCR | 1 | - | ||||
| >>>HS-SICH ID | M | 9.2.3.5Gb | - | |||
| >>>Time Slot LCR | M | 9.2.3.24A | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>>TDD Channelisation Code | M | 9.2.3.19 | - | |||
| >>ControlledFrequency | O | UARFCN 9.2.1.65 | Be applicable to this IE of 1.28Mcps TDD system when adopting multi-frequency and represent frequency by HS-SCCH control | - | ||
| >UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| HARQ Memory Partitioning per UARFCN | 0..<maxHSD PAFrequenc y> | - | ||||
| >CHOICE HARQ Memony partitioning | O | - | ||||
| >>implicit | - | |||||
| >>>Number of Processes | M | INTEGER( 1..8，...) | For the HARQ process ID, numbering subtracts 1 from 0 to the process number, and the channel bit sum is on average divided between all HARQ processes according to the rule of definition in [18]. | - | ||
| >>Explicit | - | |||||
| >>>HARQ Memory Partitioning Information | 1..<maxnoof HARQproces ses> | First HARQ process examples of parameters is designated 0, the second and is designated 1, by that analogy. | - | |||
| >>>>Process Memory Size | M | 9.2.1.49D | See[18] | - | ||
| >UARFCN | O | 9.2.1.65 | Nt is only applicable to use many referring to 3GPP TS 25.105 | - |
| The 1.28Mcps TDD system of carrier frequency |
Thereby, according to HSDPA method for managing resource of the present invention, two above-mentioned carrier wave cells are combined into one, so just avoided the generation of the problems referred to above. Modification to HS-DSCH TDD Information Response IE is as shown in table 9, is the content through revising in the table in the zone of grey:
Table 9HS-DSCH TDD InformatIon Response IE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| HS-DSCH MAC-d Flow Specific Information Response | 0..<maxnoof MACFlows> | - | ||||
| Omit ... | ||||||
| HS-SCCH Specific Information Response | 0..<maxNoOf HSSCCHcod es> | Be not suitable for 1.28Mcps TDD system | GLOBAL | reject | ||
| Omit ... | ||||||
| >TDD Channelisation Code | M | 9.2.3.19 | - | |||
| HS-SCCH Specific Information Response LCR per UARFCN | 0..<maxHSD PAFrequenc y> | Be not suitable for 3.84Mcps TDD system | ||||
| >HS-SCCH Specific Information Response LCR | 1..<maxNoOf HSSCCHcod es> | GLOBAL | reject | |||
| >>Time Slot LCR | M | 9.2.3.24A | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>First TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>Second TDD Channelisation Code | M | TDD Channelisa tion Code 9.2.3.19 | - | |||
| >>HS-SICH Information LCR | 1 | - | ||||
| >>>HS-SICH ID | M | 9.2.3.5Gb | - | |||
| >>>Time Slot LCR | M | 9.2.3.24A | - | |||
| >>Midamble Shift LCR | M | 9.2.3.7A | - | |||
| >>>TDD Channelisation Code | M | 9.2.3.19 | - | |||
| >UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>ControlledFrequency | O | UARFCN 9.2.1.65 | Be applicable to 1.28Mcps when adopting multi-frequency | - |
| This IE of TDD system represents the frequency by HS-SCCH control | ||||||
| >CHOICE HARQ Memony partitioning | O | - | ||||
| >>implicit | - | |||||
| >>>Number of Processes | M | INTEGER( 1..8，...) | For the HARQ process ID, numbering subtracts 1 from 0 to the process number, and the channel bit sum is on average divided between all HARQ processes according to the rule of definition in [18]. | - | ||
| >>Explicit | - | |||||
| >>>HARQ Memory Partitioning Information | 1..<maxnoof HARQproces ses> | First HARQ process examples of parameters is designated 0, the second and is designated 1, by that analogy. | - | |||
| >>>>Process Memory Size | M | 9.2.1.49D | See[18] | - |
In specific embodiments of the invention 6, management method according to HSDPA resource provided by the invention, when the ability of a residential quarter and/or its resource operation state change, Node B will use Resource status indication message or AUDIT RESPONSE message to report to RNC, have carrier information among the HS-DSCH Resources Information IE in the described message, thereby so that Node B can be by the resource operation state of carrier wave to RNC report HS-DSCH.
Modification for AUDIT RESPONSE and RESOURCE STATUS INDICATION message namely increases carrier information, shown in table 10, table 11, is the content through revising in the table in the zone of grey.
Table 10AUDIT RESPONSE
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| Cell Information | 0..<maxCellin NodeB> | EACH | ignore | |||
| >C-ID | M | 9.2.1.9 | - | |||
| ......Omitted...... | ||||||
| >DwPCH Information | O | Common Physical Channel Status | Be only applicable to 1.28Mcps TDD system | YES | ignore |
| Information 9.2.1.13A | ||||||
| >HS-DSCH Resouroes Information | 0..<maxFrequ encyinCell> | YES | ignore | |||
| >>Resource Operational State | M | 9.2.1.52 | - | |||
| >>Availablity Status | M | 9.2.1.2 | - | |||
| >UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| Communication Control Port Information | 0..<maxCCPi nNodeB> | EACH | ignore | |||
| Omit ... |
| Range Bound | Explanation |
| Omit ... | |
| maxFPACHCell | Maximum number of FPACH that can be defined in a Cell |
| maxFrequencyinCell | Maximum number of Frequency that can be defined in a Cell |
Table 11RESOURCE STATUS INDICATION
| IE/Grouq Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Message Type | M | 9.2.1.46 | YES | reject | ||
| Transaction ID | M | 9.2.1.62 | - | |||
| CHOICE Indication Type | M | YES | ignore | |||
| >No Failure | - | |||||
| >>Local Cell Information | 1..<maxLocal CellinNodeB> | EACH | ignore | |||
| Omit ... | ||||||
| >>>HSDPA Capability | O | 9.2.1.31Ga | YES | ignore | ||
| >>Local Cell Group Information | 0..<maxLocal CellinNodeB> | EACH | ignore | |||
| Omit ... | ||||||
| >Service Impacting | - | |||||
| >>Local Cell Information | 0..<maxLocal CellinNodeB> | EACH | ignore | |||
| >>>Local Cell ID | M | 9.2.1.38 | - | |||
| Omit ... | ||||||
| >>>Reference Clock Availability | O | 9.2.3.14A | TDD only | YES | ignore | |
| >>>HSDPA Capability | O | 9.2.1.31Ga | YES | ignore | ||
| >>Loeal Cell Group Information | 0..<maxLocal CellinNodeB> | EACH | ignore | |||
| Omit ... | ||||||
| >>Cell Information | 0..<maxCellin NodeB> | EACH | ignore | |||
| >>>C-ID | M | 9.2.1.9 | - | |||
| >>>Resource | O | 9.2.1.52 | - |
| Operational State | ||||||
| >>>Availability Status | O | 9.2.1.2 | - | |||
| >DwPCH Information | O | Common Physical Channel Status Information 9.2.1.13A | Be only applicable to 1.28Mcps TDD system | YES | ignore | |
| >HS-DSCH Resources Information | 0..<maxFrequ encyinCell> | YES | ignore | |||
| >>>>Resource Operational State | M | 9.2.1.52 | - | |||
| >>>>Availablity Status | M | 9.2.1.2 | - | |||
| >>>>UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >>Power Local Cell Group Information | 0..<maLocalC ellinNodeB> | EACH | ignore | |||
| Omit ... |
In specific embodiments of the invention 7, method according to HSDPA resource management of the present invention, in RADIO LINK ADDITION RESPONSE message, increase HS-DSCH TDD Information Response IE, increase HS-DSCH TDD information IE in the RADIO LINK ADDITION REQUEST message, set up simultaneously dedicated channel and HSDPA related resource when switching with the minizone in Node B. Described HS-DSCH TDD Information Response IE can come according to prior art, better the practice is that described HS-DSCH TDD Information Response IE the method according to this invention is made amendment, and makes only to have a carrier wave cell in its amended content. In addition, also can in RADIO LINK ADDITION REQUEST message, increase HS-DSCH-RNTI IE, HS-PDSCH RL ID IE, can efficient when switch the minizone in Node B so higher.
The modification of RADIO LINK ADDITION REQUEST message and RADIO LINK ADDITION RESPONSE message is the content through revising in the zone of grey in the table shown in table 12, table 13.
Table 12RADIO LINK ADDITION REQUEST
| IE/Group Name | Presence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| RL Information | 1 | YES | reject | |||
| Omit ... | ||||||
| >>Uplink Synchronisation Frequency | M | 9.2.3.26G | - | |||
| HS-DSCH Information | O | HS-DSCH TDD Information 9.2.3.5F | YES | reject | ||
| HS-DSCH-RNTI | C-InfoHSDSCH | 9.2.1.31J | YES | reject | ||
| HS-PDSCH RL ID | C-InfoHSDSCH | RL ID 9.2.1.53 | YES | reject |
| Range Bound | Explanation |
| maxnoCCTrCH | Number of CCTrCH for one UE |
| Condition | Explanation |
| InfoHSDSCH | The IE shall be present if HS-DSCH Information IE is present |
Table 13RADIO LINK ADDITION RESPONSE MESSAGE
| IE/Group Name | Pre- sence | Range | IE Type&Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| RL Information Response LCR | 0..1 | 1.28Mcps the TDD system is essential, is not suitable for 3.84 Mcps TDD systems | YES | ignore | ||
| Omit ... | ||||||
| >USCH Informatio Response | O | 9.2.3.29 | YES | ignore | ||
| HS-DSCH Information Response | O | HS-DSCH TDD Information 9.2.3.5G | YES | ignore |
In specific embodiments of the invention 8, according to HSDPA method for managing resource of the present invention, in order to make the relevant measurement of HSDPA based on each carrier wave in the residential quarter, Common Measurement Type IE and frequency point information UARFCN IE are cooperated.
As shown in table 14, Common Measurement Type IE in the table 14 comprises the public-measurement that HSDPA is relevant: all are not by the transmission carrier power of HS-PDSCH and the employed code word of HS-SCCH (Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission), HS-DSCH power demand (HS-DSCH Required Power), the bit rate that HS-DSCH provides (HS-DSCH Provided Bit Rate). Common Measurement Type IE and frequency point information UARFCN IE cooperate, the public-measurement that expression HSDPA is relevant is for carrying out on the indicated carrier wave of UARFCN IE, this is so that can be based on each carrier wave in the residential quarter about the measurement of HSDPA, RNC is easy to judge which carrier wave has good HSDPA performance, is conducive to RRM. Load balance between for example access control, the carrier wave etc. can benefit from the public-measurement relevant with HSDPA based on carrier wave.
Table 14COMMON MEASUREMENT INlTlATION REQUEST
| IE/Group Name | Pre- sence | Range | IE Type& Reference | Semantics Description | Criticallty | Assigned Criticallty |
| Message Discriminator | M | 9.2.1.45 | - | |||
| Omit ... | ||||||
| CHOICE Commnon Measurement Object Type | M | YES | reject | |||
| >Cell | - | |||||
| >>C-ID | M | 9.2.1.9 | - | |||
| Omit ... | ||||||
| >>>>>>Neighbouring TDD Cell Measurement Information LCR | M | 9.2.1.47E | YES | reject | ||
| >>UARFCN | O | 9.2.1.65 | Nt is only applicable to use the 1.28Mcps TDD system of multi-carrier frequency referring to 3GPP TS 25.105 | - | ||
| >RACH | FDD only | - | ||||
| Omit ... | ||||||
| Common Measurement Type | M | 9.2.1.11 | YES | reject | ||
| Omit ... |
The above is preferred embodiment of the present invention only, is not for limiting protection scope of the present invention. Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (5)
1, the HSDPA method for managing resource in the multi-carrier TD-SCDMA system is characterized in that, as Node B during to the change of the ability of a residential quarter of RNC report and/or resource operation state, comprises step:
Node B sends Resource status indication message or AUDIT RESPONSE message to RNC, has carrier information among the HS-DSCH Resources Information IE in the described message.
2, the HSDPA method for managing resource in the multi-carrier TD-SCDMA system is characterized in that, when switch the minizone in carrying out Node B, comprises step:
RNC sends RADIO LINK ADDITION REQUEST message to Node B, has HS-DSCH TDD Information IE in this message;
Node B receives described message, sends RADIO LINK ADDITION RESPONSE message to RNC, has HS-DSCH TDD Information Response IE in this message.
3, the management method of HSDPA resource as claimed in claim 2 is characterized in that,
Also there are HS-DSCH-RNTI IE, HS-PDSCH RL ID IE in the RADIO LINK ADDITION REQUEST message.
4, the HSDPA method for managing resource in the multi-carrier TD-SCDMA system is characterized in that,
When carrying out the relevant public-measurement of HSDPA, in the Common measurement initiation request message that RNC sends to Node B, Common Measurement Type IE and frequency point information UARFCN IE are associated.
5, the management method of HSDPA resource as claimed in claim 4 is characterized in that, the public-measurement that described HSDPA is relevant comprises:
The bit rate that all are not provided by transmission carrier power, HS-DSCH power demand, the HS-DSCH of the code word of HS-PDSCH or HS-SCCH use.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910203717A CN101626600A (en) | 2006-02-23 | 2006-02-23 | HSDPA resource management method in multi-carrier TD-SCDMA system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910203717A CN101626600A (en) | 2006-02-23 | 2006-02-23 | HSDPA resource management method in multi-carrier TD-SCDMA system |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200610055132XA Division CN100488286C (en) | 2006-02-23 | 2006-02-23 | HSDPA resource management method for multi-carrier TD-SCDMA system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101626600A true CN101626600A (en) | 2010-01-13 |
Family
ID=41522218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910203717A Pending CN101626600A (en) | 2006-02-23 | 2006-02-23 | HSDPA resource management method in multi-carrier TD-SCDMA system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101626600A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011103787A1 (en) * | 2010-02-25 | 2011-09-01 | 中兴通讯股份有限公司 | Method and system for managing carrier information in multi-carrier system |
| WO2012167420A1 (en) * | 2011-06-07 | 2012-12-13 | 中兴通讯股份有限公司 | Method and system for updating carriers in radio network controller |
-
2006
- 2006-02-23 CN CN200910203717A patent/CN101626600A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011103787A1 (en) * | 2010-02-25 | 2011-09-01 | 中兴通讯股份有限公司 | Method and system for managing carrier information in multi-carrier system |
| US8787288B2 (en) | 2010-02-25 | 2014-07-22 | Zte Corporation | Method and system for managing carrier information in multi-carrier system |
| WO2012167420A1 (en) * | 2011-06-07 | 2012-12-13 | 中兴通讯股份有限公司 | Method and system for updating carriers in radio network controller |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100488286C (en) | HSDPA resource management method for multi-carrier TD-SCDMA system | |
| KR101256155B1 (en) | Method for implement hsdpa for td-scdma | |
| CN101127556B (en) | A dynamic scheduling method for carrier resource | |
| US8027292B2 (en) | Method for reporting the frequency resource arrangement and frequency information of the multi-frequency cell | |
| CN102067697B (en) | Method and apparatus for reducing interference in a mobile communications network | |
| CN101345988A (en) | Resource allocation method and device of multi-carrier system | |
| CN100512565C (en) | Method for enhancing wireless communication up-grouping dispatch | |
| CN100518042C (en) | Carrier resource process method based on multi-carrier high speed downlink block access system | |
| CN104270764A (en) | Base station node resource allocating method, system and device | |
| CN101547515A (en) | Method, device and communication system for resource allocation | |
| CN101646198A (en) | Implementation method for downlink of LTE-Advanced system, base station and user equipment | |
| KR20050046307A (en) | Method for managementing resource in a mobile communication system using high-speed packet data service | |
| CN101345976A (en) | Resource allocation method and system for multi-carrier system cross-wireless network controller service | |
| CN100547951C (en) | Physical channel configuration and signal transmission method in the TD-SCDMA system | |
| CN101094166B (en) | Method of assigning wireless resources for multicarrier, high speed down going packet access | |
| CN100359982C (en) | Shared channel allocation and using method in multi-carrier frequency cell system | |
| CN101742658B (en) | Method for allocating resource of enhanced district forward access channel in multi-carrier system | |
| CN101175301A (en) | Sharing method for unscheduled and scheduled resource in ascending reinforcement system | |
| CN101854720B (en) | Data transmission method, system and device | |
| CN101626600A (en) | HSDPA resource management method in multi-carrier TD-SCDMA system | |
| CN101521940B (en) | Method for reporting ability grades and allocating channel resources for user equipment | |
| CN101188486B (en) | Sharing method for non scheduled resources and scheduled resources in uplink enhanced system | |
| CN102196541B (en) | Method and system for realizing multi-carrier enhanced uplink access power sharing management | |
| CN101340260A (en) | High-order modulation realizing method in high-speed downlink packet access | |
| CN101193431A (en) | A management method for high-speed share of control channel resource pool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20100113 |