WO2009026833A1

WO2009026833A1 - Method and apparatus for resource configuration

Info

Publication number: WO2009026833A1
Application number: PCT/CN2008/072079
Authority: WO
Inventors: Dajun Zhang; Ying Zhang; Haijing Hu
Original assignee: Da Tang Mobile Communications Equipment Co., Ltd.
Priority date: 2007-08-24
Filing date: 2008-08-21
Publication date: 2009-03-05
Also published as: CN101374328A; CN101374328B

Abstract

A method for resource configuration includes: receiving a physical shared channel reconfiguration request message; performing multi-carrier resource configuration according to the HSUPA resource condition of high speed uplink packet access service in the cell; returning a message according to the configuration result. By the method of the embodiments in the invention, the process of configuring the multi-carrier resource of HSUPA is made more flexible, and the present protocol definition is simplified; the problems that the resource configuration scheme used when multi-carrier cell performing high speed data service is not flexible enough and comparably complex in the present or enhancing 3G wideband wireless mobile communication system and the like are resolved.

Description

Resource allocation method and device

The present application claims priority to Chinese Patent Application No. 200710120759.3, entitled "A Resource Configuration Method and Apparatus", filed on Aug. 24, 2007, the entire disclosure of which is incorporated herein by reference. .

Technical field

The present invention relates to the field of mobile communications technologies, and in particular, to a resource configuration method and apparatus.

Background technique

Currently, in the 3GPP (3rd Generation Partnership Project) Release 5 and Release 7 specifications, in order to support high-speed data services, High Speed Downlink Packet Access (HSDPA) is proposed. And High Speed Uplink Packet Access (HSUPA), which stipulates that all users share all code channel resources and adopts adaptive code modulation (AMC) and hybrid request retransmission (HARQ) technology for the channel environment. A good user terminal (UE) allocates a higher rate and assigns a lower rate to user terminals with poor channel conditions.

For the HSUPA system, the transport channel for carrying the upper layer data is the uplink enhanced dedicated channel (E-DCH), and the data of the E-DCH is processed by the encoding, interleaving, etc., and then mapped to the uplink enhanced physical channel (E-PUCH) for transmission. And the radio access network and the UE interact through an uplink enhanced absolute grant channel (E-AGCH), an uplink enhanced acknowledgement indicator channel (E-HICH), and an uplink control channel (E-UCCH); the UE according to the scheduling on the E-AGCH The license information is allocated to the E-DCH, and the UE scheduling information is transmitted on the E-UCCH. The E-UCCH is multiplexed with the E-DCH and mapped to the E-PUCH. The radio access network controls the pair according to the information. The subsequent data transmission of the UE.

In terms of system resource configuration, the RNC (Radio Network Controller) configures and tampers the resources of the E-PUCH, E-AGCH, and E-HICH physical channels through the physical shared channel reconfiguration process, in the E-PUCH resources. When the configuration is performed, the full coverage mode is used. That is, if only the local resources, such as a time slot, are modified, other resources that do not change need to be carried, and the base station (Node B ) replaces the old resource configuration with the new resource configuration. In addition, if all resources are configured successfully, Node B responds with a successful response message; otherwise, Node B will respond with a failed response message.

In the prior art, only the HSUPA resource configuration process of the single carrier frequency is supported, and the configuration of the E-PUCH resource is completely covered, and the Node B only needs to be configured successfully. The success response message is fed back, otherwise Node B will feed back the failure response message. When these technologies are applied to multi-carrier resource configuration, the resource configuration process will be inflexible and more redundant.

Summary of the invention

In view of this, the embodiment of the present invention provides a resource configuration method and device, which makes the multi-carrier resource configuration process of HSUPA more flexible and simplifies the original protocol definition.

Correspondingly, the technical solutions provided by the embodiments of the present invention are as follows:

A resource configuration method, the method includes:

Receiving a physical shared channel reconfiguration request message;

Perform multi-carrier resource configuration according to the high-speed uplink packet access service HSUPA resource status in the cell;

The message is returned according to the configuration result.

A resource configuration device, the device includes: a receiving unit, a configuration unit, and a message unit; the receiving unit is configured to receive a physical shared channel reconfiguration request message;

The configuration unit is configured to perform multi-carrier resource configuration according to the presence of HSUPA resources in the cell;

The message unit is configured to return a message according to the configuration result.

Compared with the prior art, the method and apparatus of the embodiments of the present invention define a new processing mechanism for the HSUPA related configuration IE in the physical shared channel reconfiguration request message, and give a partial success to the physical shared channel reconfiguration failure message. The meaning of the newly defined physical shared channel reconfiguration complete message, which makes the multi-carrier resource process of HSUPA more flexible and simplifies the original protocol definition; can support the multi-carrier frequency HSUPA resource configuration process, and configure the E-PUCH resource In addition to the full coverage of all carrier frequencies, it also supports a separate configuration method based on carrier frequency; it solves the problem of insufficient resource allocation scheme for high-speed data services in multi-carrier cells in current or evolved 3G broadband wireless mobile communication systems. Flexible, relatively complex and other issues.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor. 1 is a schematic flow chart of a method according to Embodiment 1 of the present invention;

Figure 2 is a schematic view of the apparatus of Embodiment 4 of the present invention.

detailed description

In the current 3GPP Release 7 specification, HSUPA adopts single-carrier transmission mode, that is, the user transmits traffic channel data on one carrier, but due to the limitation of signal bandwidth, the peak rate of data transmitted by HSUPA technology will be affected to some extent; Combined with multi-carrier technology, the data transmission rate of HSUPA technology can be further improved, and the scheduling mechanism of HSUPA resources can be brought more flexibility.

The embodiment of the invention provides a resource configuration method, which enables a multi-carrier cell to simultaneously provide services for user terminals having different receiving carrier capabilities, and enables the radio access network to more flexibly allocate HSUPA multi-carrier resources;

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without the creative work are all within the scope of the present invention. As shown in FIG. 1 , the RNC (Wireless Network Access Device) triggers the physical shared channel reconfiguration process as an example, and the specific steps of the method in Embodiment 1 of the present invention are as follows:

Step 101: Receive a physical shared channel reconfiguration request message.

The Node B receives the physical shared channel reconfiguration request message sent by the RNC, where the message carries configuration information of the E-PUCH, the E-AGCH, and the E-HICH physical channel resource.

Step 102: Perform multi-carrier resource configuration according to the existence of the high-speed uplink packet access service HSUPA resource in the cell.

After receiving the physical shared channel reconfiguration request message, if there is no HSUPA related resource in the multi-carrier cell, the multi-carrier resource configuration is performed according to the configuration information of the E-PUCH, the E-AGCH, and the E-HICH;

After receiving the physical shared channel reconfiguration request message, if the HSUPA related resource already exists in the multi-carrier cell, the existing multi-carrier resource configuration is updated according to the configuration information of the E-PUCH, the E-AGCH, and the E-HICH; It should be noted that in this embodiment, during the HSUPA multi-carrier resource reconfiguration process, that is, in the process of updating the multi-carrier resource configuration, if the HSUPA-related resources already exist in the multi-carrier cell, according to the E-PUCH and the E-AGCH. And the configuration information of the E-HICH is used to update the existing multi-carrier resources by using various mechanisms including the prior art, and details are not described herein again.

Step 103: Return a message according to the configuration result.

If the corresponding E-PUCH, E-AGCH, or E-HICH physical channel resources are successfully configured or reconfigured on all carriers, the physical shared channel reconfiguration response message is sent to the RNC, and the physical shared channel reconfiguration process is notified to end;

If the corresponding E-PUCH, E-AGCH, or E-HICH physical channel resource is successfully configured or reconfigured on only part of the carrier, the physical shared channel reconfiguration response message or the failure message is sent to the RNC, and the physical shared channel is notified. The configuration process ends and the failed carrier and cause are indicated;

If the E-PUCH, E-AGCH, or E-HICH physical channel resource configuration or reconfiguration fails on all carriers, a physical shared channel reconfiguration failure message is sent to the RNC to notify the physical shared channel that the reconfiguration process fails.

It should be noted that each step of the method of the present invention in this embodiment is implemented according to various information elements (IE, Information Element) carried in the message; the information element has content and format specified by the standard. Used to pass various parameters and other information needed to establish a connection between the sender and receiver of the message.

In addition, for the update of the existing multi-carrier resource configuration in the embodiment 1, the present invention also proposes two update reconfiguration mechanisms, but is not limited thereto, as described in Embodiment 2 of the present invention:

If the carrier frequency information is added to the E-PUCH Information 1.28 Mcps per UARFCN (low-chip E-PUCH information configured by carrier frequency) information element, resource allocation will be performed according to different carrier frequencies. Similarly, the carrier information may be included in other information elements used by the Iub interface message, or the user may define an information element used in the Iub interface message to include carrier frequency information, and may perform HSUPA according to different carrier frequencies. Resource configuration.

The first mechanism is: when the reconfiguration request message includes HSUPA resource configuration information and the HSUPA resource is configured in the cell, the original configuration is replaced with the information in the new information element as the frequency, time slot, and time slot of the E-PUCH channel. Code channel list; Specifically, the carrier frequency information is added to the E-PUCH Information 1.28 Mcps per UARFCN information element as an example: if the physical shared channel reconfiguration request message includes the E-PUCH Information 1.28 Mcps per UARFCN IE, and the HSUPA is configured in the cell. The resource, then replaces the original configuration with the information in the new IE as the frequency, time slot, and code channel list of the E-PUCH channel;

The specific carrier frequency information is shown in Table 1:

Information Element Presence Range IE Type Semantics

/Group name and Description

Referenc

e

E-PUCH Information 0.. < 1.28Mcps TDD only 1.28Mcps per maxFre

UARFCN quencyi

nCell>

>LTGI Presence M 9.2.3.58

>SNPL Reporting M 9.2.3.62

Type

>E-PUCH Timeslot l..<max

Information noofEP

1.28Mcps UCHslo

tsLCR>

»Time Slot LCR M 9.2.3.24A

»Midamble Shift M 9.2.3.7A

LCR

»Codes LCR l..<max

noofEP

UCHco

Des> »> TDD 9.2.3.19

Channelisation Code

>UARFCN O 9.2.1.65 Corresponds to Nt

( 3GPP TS 25.105 ) Mandatory for

1.28Mcps TDD when using multiple

The table 1 is the standard format of the 3GPP specification TS25433. Except for the first and ninth items in the table, the other items are the standard definitions of the information elements in 3GPP, and are not described here; The first and the nine items are added in the embodiment of the present invention, and the name is E-PUCH Information 1.28 Mcps per UARFCN (low-chip E-PUCH information configured by carrier frequency) and UARFCN (carrier frequency information), and the Presence column indicates The item is optional. The Type and Reference column indicates the position of the detailed explanation of this item in the specification. The Semantics Description column indicates that the meaning of this item is only applicable to the LCR TDD, and the carrier frequency information is mandatory in the case of multiple carrier frequencies. The above updates are based on the contents of the table.

In addition, if a carrier frequency HSUPA resource is configured in the cell, but E-PUCH Information

1.28Mcps per UARFCN IE does not contain any configuration information of this carrier frequency, then the update step is to delete the HSUPA resource on the carrier frequency;

The second mechanism is: when the HSUPA resource configuration information is included in the reconfiguration request message and the HSUPA resource of the carrier frequency is configured in the cell, the original configuration is replaced by the information in the information element where the carrier frequency is located. a list of frequencies, time slots, and code channels of the E-PUCH channel;

Specifically, if the physical shared channel reconfiguration request message includes any E-PUCH Information 1.28 Mcps per UARFCN IE, and the HSUPA resource is configured in the carrier frequency in the cell, the new E-PUCH Timeslot Information 1.28 Mcps IE is used. The information in the (low-chip E-PUCH slot information) replaces the original configuration as the frequency, time slot, and code channel list of the E-PUCH channel in the carrier frequency; the HSUPA resource configuration on other carrier frequencies is not affected; The mechanism is implemented by modifying on the basis of Table 1 above: E-PUCH Timeslot Information in Table 1 1.28Mcps IE value range is changed from l..<maxnooffiPUCHslotsLCR> to 0. <maxnoofEPUCHslotsLCR>;

In addition, if any E-PUCH Information 1.28 Mcps per UARFCN IE does not contain any E-PUCH Timeslot Information 1.28 Mcps IE, but contains the UARFCN IE, all existing E-PUCH resources on the frequency indicated by the UARFCN IE are deleted. At the same time, the H SUP A resource configuration at other frequencies is not affected.

In addition, for the case where the corresponding E-PUCH, E-AGCH or E-HICH physical channel resources are successfully configured or reconfigured on only part of the carriers in Embodiments 1 and 2 of the present invention, Embodiment 3 of the present invention further proposes Two mechanisms for improving local successful configuration are as follows:

In the prior art, if all parts of the configuration may not be supported according to the definition of the existing 3GPP specifications, all channels in the physical shared channel reconfiguration request message will be refused to be configured, and then the physical shared channel reconfiguration fails. In response to the message, the configuration is unsuccessful. In the multi-carrier HSUPA system, in order to make the resource configuration more flexible and independent, it is necessary to support the local success of resource configuration according to the carrier frequency. The following two mechanisms can be considered to improve the local success feature: In a multi-carrier HSUPA system, if all parts of the configuration are not supported, only all configurations on one or some carriers can be supported:

The first mechanism: The HSUPA resources on the carrier or the carriers are different for the configuration (there is no HSUPA resource in the cell, or the HSUPA resource exists in the cell, or the carrier message configuration information is not included in the request message, or only the carrier information is included. The frequency information element, etc.) is regarded as successful establishment or reconfiguration success or deletion success, and rejects the HSUPA related configuration on other failure frequency points; then sends a physical shared channel reconfiguration failure message; the physical shared channel reconfiguration failure message includes a failure indicating Cause The information element Cause IE, the reason information element is a value related to each specific frequency point causing the failure; if this configuration is related to resources such as E-PUCH, the Configuration Generation ID IE in the message is saved (configuration effective information) The value of the element) also ensures that these resources are available for the current and subsequent E-DCH transport channels.

The second mechanism is: the HSUPA resources on the carrier or the carriers are different for the configuration (there is no HSUPA resource in the cell, or the HSUPA resource exists in the cell, or the request message does not include the carrier frequency configuration information, or only contains Frequency information element, etc.) is regarded as successful establishment or reconfiguration success or deletion success, while rejecting HSUPA related configuration on other failure frequency points; then sending physical share Channel reconfiguration completion message; the physical shared channel reconfiguration complete message includes a reason information element Cause IE indicating the cause of failure of a part of the frequency point configuration, and the Cause IE is a value related to each specific frequency point causing the failure; The value of the Configuration Generation ID IE also ensures that these resources are available for current and subsequent E-DCH transport channels.

Specifically, the second mechanism is to add a physical shared channel reconfiguration completion response message to the message returned after the configuration operation is completed, and the message is defined as a operation for supporting partial carrier frequency resource configuration success; similarly, other The Iub interface message uses a similar information element, or the user defines another Iub interface message to complete this part of the feature;

For example, taking the newly added physical shared channel reconfiguration completion response message as an example, Table 2 below is a message table in the case of partial successful configuration:

Table 2

IE/Group Name Presenc Range IE Type Semantics

e and Description

Referenc

e

Message Discriminator M 9.2.1.45

Message Type M 9.2.1.46

Transaction ID M 9.2.1.62

Unsuccessful HSDPA 0.. <

UARFCN maxFre

Quencyi

nCell>

>UARFCN M 9.2.1.65 Corresponds to

Nt ( 3GPP TS

25.105 )

>Cause M 9.2.1.6 Unsuccessful HSUPA 0.. <

UARFCN maxFre

Quencyi

nCell>

>UARFCN M 9.2.1.65 Corresponds to

Nt ( 3GPP TS

25.105 )

>Cause M 9.2.1.6

Criticality Diagnostics O 9.2.1.17 This table is the standard format of the 3GPP specification TS25433. Except for the fourth and seventh items in the table, the other items are the standard definitions of the information elements in 3GPP, and will not be described here. The seventh item is a new addition to the embodiment of the present invention, specifically Unsuccessful HSDPA UARFCN (the carrier frequency information of the HSDPA is not configured successfully), the Presence column indicates that the item is optional, and the Type and Reference column indicates a detailed explanation of the item. In the position in the specification, the Semantics Description column indicates the meaning of this item. It is easy to know that some of the above successful configurations are based on the modifications in the above table.

Those skilled in the art will appreciate that all or part of the steps in implementing the above-described embodiments may be performed by hardware associated with the program instructions, and the programs are stored in a particular storage medium.

It can be seen that the method of the embodiment of the present invention defines a new processing mechanism for the HSUPA related configuration IE in the physical shared channel reconfiguration request message, and assigns a partial success meaning or a newly defined physics to the physical shared channel reconfiguration failure message. The shared channel reconfiguration complete message makes the multi-carrier resource process of configuring HSUPA more flexible and simplifies the original protocol definition.

Based on the above idea, Embodiment 4 of the present invention further provides a resource configuration apparatus. As shown in FIG. 2, the apparatus includes: a receiving unit 201, a configuration unit 202, and a message unit 203;

The receiving unit 201 is configured to receive a physical shared channel reconfiguration request message sent by the RNC, where the message carries configuration information of an E-PUCH, an E-AGCH, and an E-HICH physical channel resource; The configuration unit 202 is configured to perform multi-carrier resource configuration according to the presence of a high-speed uplink packet access service HSUPA resource in the cell;

The message unit 203 is configured to return a message according to the configuration result;

Specifically, the configuration unit 202 may further include a multi-carrier resource configuration unit and an update unit. The multi-carrier resource configuration unit is configured to receive, according to the receiving unit 201, when there is no HSUPA related resource in the multi-carrier cell. The configuration information of the E-PUCH, the E-AGCH, and the E-HICH in the reconfiguration request message is configured for multi-carrier resources;

The update unit is configured to update the configuration information of the E-PUCH, the E-AGCH, and the E-HICH in the reconfiguration request message received by the receiving unit 201 when the HSUPA related resource exists in the multi-carrier cell. Some multi-carrier cells;

In addition, the update unit may further include a first configuration update unit, where the first configuration update unit is configured to: when the reconfiguration request message includes HSUPA resource configuration information and the HSUPA resource is configured in the cell, The information in the information element replaces the original configuration as the frequency, time slot and code channel list of the E-PUCH channel;

Specifically, the carrier frequency information is added to the E-PUCH information element configured by the carrier frequency as an example: if the carrier information element is included in the physical shared channel reconfiguration request message, and the HSUPA resource is configured in the cell, The information in the new information element replaces the original configuration as the frequency, time slot, and code channel list of the E-PUCH channel. If the HSUPA resource of a certain carrier frequency is already configured in the cell, the carrier frequency information element does not include the payload. For any configuration information of the frequency, the update step is to delete the HSUPA resource on the carrier frequency;

In addition, the update unit may further include a second configuration update unit, where the second configuration update unit is configured to: when the reconfiguration request message includes the HSUPA resource configuration information and the HSUPA resource of the carrier frequency is configured in the cell, Replacing the original configuration with the information in the information element in which the carrier frequency is located as the frequency, time slot, and code channel list of the E-PUCH channel in the carrier frequency;

Specifically, if the physical shared channel reconfiguration request message includes any carrier frequency configuration

E-PUCH information element, and the HSUPA resource is configured in the carrier frequency in the cell, and the original configuration is replaced by the information in the new E-PUCH Timeslot Information 1.28 Mcps IE (slot information of the low chip E-PUCH) As the frequency, time slot and code channel list of the E-PUCH channel in the carrier frequency; the HSUPA resource configuration on other carrier frequencies is not affected; if any E-PUCH information element configured by carrier frequency Does not contain any E-PUCH Timeslot Information 1.28 Mcps IE (slot information of low chip E-PUCH), but contains UARFCN IE, delete all existing E-PUCH resources at the frequency indicated by the UARFCN IE, At the same time, the HSUPA resource configuration at other frequencies is not affected.

The message unit 203 may further include a success unit, a partial success unit, and a failure unit. The success unit is configured to return a physical shared channel reconfiguration response message after all carriers successfully configure or reconfigure physical channel resources.

The partial success unit is configured to return a physical shared channel reconfiguration response or a failure message after the partial carrier successfully configures or reconfigures the physical channel resource, and indicates the failed carrier and the reason;

The failure unit is configured to return a physical shared channel reconfiguration failure message after all carrier configuration or reconfiguration fails;

In addition, the partial success unit may further include a first partial configuration unit;

The first part configuration unit is configured to: when the device supports only the configuration of the partial carrier, the HSUPA resource on the part of the carrier is regarded as successfully established or reconfigured successfully or deleted successfully, and the HSUPA configuration on the other failed frequency points is rejected. And returning a physical shared channel reconfiguration failure message including a reason information element corresponding to each frequency point that caused the failure;

Specifically, in the multi-carrier HSUPA system, if all parts of the configuration are not supported, and only all configurations on one or some carriers are supported, the first part configuration unit configures the HSUPA resources on the one or more carriers for the configuration. Different situations (there are no HSUPA resources in the cell, or HSUPA resources exist in the cell, or the carrier message configuration information is not included in the request message, or only the carrier frequency information element is included), and the successful establishment or reconfiguration succeeds or the deletion is successful. And rejecting the HSUPA related configuration on the other failed frequency points; then sending a physical shared channel reconfiguration failure message to the RNC; the physical shared channel reconfiguration failure message includes a reason information element Cause IE indicating the reason for the failure, and the cause information element is The value associated with each particular frequency point that caused the failure.

In addition, the partial success unit may further include a second partial configuration unit;

The second part configuration unit is configured to: when the device supports only a part of the carrier configuration, the HSUPA resource on the part of the carrier is regarded as being successfully established or reconfigured or deleted, and the HSUPA configuration on the other failed frequency points is rejected. At the same time, a newly added physical shared channel reconfiguration complete message containing the cause information element corresponding to each frequency point causing the failure is returned; then the value of the Configuration Generation ID IE in the message is saved. Specifically, in the multi-carrier HSUPA system, if all parts of the configuration are not supported, and only all configurations on one or some carriers are supported, the second part configuration unit targets the HSUPA resources on the one or more carriers. Different conditions in the configuration (there is no HSUPA resource in the cell, or the HSUPA resource exists in the cell, or the carrier message configuration information is not included in the request message, or only the carrier frequency information element is included), and the successful establishment or reconfiguration is successful or deleted. Successfully, rejecting the HSUPA related configuration on the other failed frequency points; then sending the physical shared channel reconfiguration complete message to the RNC; the physical shared channel reconfiguration complete message includes a cause information element Cause IE indicating the cause of the failure of a certain frequency point configuration, Cause IE is the value associated with each specific frequency point that caused the failure; the value of the Configuration Generation ID IE in the message is saved; the second part of the configuration unit is added to the message returned after the configuration operation is completed. A physical shared channel reconfiguration complete response message, the message is defined as a support part Successful operation frequency resource allocation; Similarly, may also be used in other similar information element message Iub interface, the Iub interface, or the definition of another message by the user to complete this portion of properties.

In addition, a person skilled in the art can easily understand that the apparatus of the foregoing embodiment can be applied to any base station, and the base station including the apparatus can implement the power configuration of the resource configuration implemented by the apparatus in the foregoing embodiment.

It can be seen that when the resource is configured by the device in the embodiment of the present invention, the HSUPA resource configuration of multiple carrier frequencies can be supported, and the configuration of the E-PUCH resource can be completely covered by all carrier frequencies, and the carrier frequency alone can be supported. The configuration also enables the HSUPA multi-carrier resource configuration process to support local successful operations, making the resource configuration process more flexible and reducing redundancy.

Those skilled in the art will appreciate that information, messages, and signals can be represented using any of a number of different processes and techniques. For example, the messages and information mentioned in the above description may be expressed as voltage, current, electromagnetic wave, magnetic field or magnetic particle, light field or any combination of the above.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A skilled person can use different methods to implement the described functions for each particular application, but such implementation should not be considered as an extension of the present invention. Wai.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded to the broadest scope of the principles and novel features disclosed herein.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are included in the spirit and scope of the present invention, should be included in the present invention. Within the scope of protection.

The embodiments of the present invention described above are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the appended claims.

Claims

OP080634 WO 2009/026833 PCT/CN2008/072079 - 14- Claims

A resource configuration method, which is characterized by comprising:

Receiving a physical shared channel reconfiguration request message;

Perform multi-carrier resource configuration according to HSUPA resource status in the cell;

The message is returned according to the configuration result.

2. The method according to claim 1, wherein the performing the multi-carrier resource configuration further comprises:

When there is no HSUPA resource in the cell, the multi-carrier resource configuration is performed according to the reconfiguration request message;

When an existing HSUPA resource exists in the cell, the existing multi-carrier resource is updated according to the reconfiguration request message.

The method according to claim 2, wherein the updating further comprises: when the reconfiguration request message includes HSUPA resource configuration information and the HSUPA resource is configured in the cell, in a new information element The information replaces the original configuration as the frequency, time slot and code channel list of the E-PUCH channel;

The HSUPA resource configuration information includes at least E-PUCH information configured according to a carrier frequency.

4. The method of claim 3, wherein:

When the HSUPA resource of the carrier frequency is configured in the cell, and the configuration information of the carrier frequency is not included in the reconfiguration request message, the HSUPA resource on the carrier frequency is deleted.

The method according to claim 2, wherein the updating further comprises: when the reconfiguration request message includes HSUPA resource configuration information and the HSUPA resource of the carrier frequency is configured in the cell, The information in the information element in which the frequency is located replaces the original configuration as the frequency, time slot and code channel list of the E-PUCH channel in the carrier frequency;

The HSUPA resource configuration information includes at least carrier frequency information.

6. The method of claim 5, wherein:

When any of the HSUPA resource configuration information elements includes a carrier frequency information element and does not include a time slot information element, the existing E-PUCH resource at the frequency indicated by the carrier frequency information element is deleted.

The method according to claim 1, wherein the returning the message according to the configuration result further comprises: OP080634

WO 2009/026833 PCT/CN2008/072079

- 15 - After all carriers successfully configure or reconfigure physical channel resources, return a physical shared channel reconfiguration response message;

After the partial carrier successfully configures or reconfigures the physical channel resource, it returns a physical shared channel reconfiguration response or failure message, and indicates the failed carrier and cause;

After all carrier configuration or reconfiguration fails, the physical shared channel reconfiguration failure message is returned.

The method according to claim 7, wherein the returning the response message after the partial carrier configuration succeeds further comprises:

When only the configuration of the partial carrier is supported, the HSUPA resource on the part of the carrier is regarded as successfully established or reconfigured successfully or deleted successfully, and the HSUPA configuration on the failed frequency point is rejected, and the physical shared channel reconfiguration failure message is returned; The message contains a reason information element that corresponds to each frequency point that caused the failure.

9. The method of claim 8 wherein:

When the part is successfully configured to be related to the E-PUCH resource, the value of the configuration effective information element in the message is saved.

The method according to claim 7, wherein the returning the response message after the partial carrier configuration is successful includes:

When only the configuration of the partial carrier is supported, the HSUPA resource on the part of the carrier is regarded as successful establishment or reconfiguration succeeded or deleted successfully, and the HSUPA configuration on the other failed frequency points is rejected, and the newly added physical shared channel reconfiguration is returned. The completion message; the message contains a reason information element that corresponds to each frequency point that caused the failure; then the value of the configuration validation information element in the message is saved.

11. A method according to any one of claims 1 to 10, characterized in that:

The reconfiguration request message includes configuration information of the E-PUCH, the E-AGCH, and the E-HICH.

12. A method according to any one of claims 1 to 10, characterized in that:

The information element has a standard specified content and format for passing various parameters and information required to establish a connection between the sender and the recipient of the message.

13. A resource configuration apparatus, the apparatus comprising: a receiving unit, a configuration unit, and a message unit;

The receiving unit is configured to receive a physical shared channel reconfiguration request message; OP080634

WO 2009/026833 PCT/CN2008/072079

The configuration unit is configured to perform multi-carrier resource configuration according to the existence of the HSUPA resource in the cell;

The apparatus according to claim 13, wherein the configuration unit further comprises: a multi-carrier resource configuration unit and an update unit;

The multi-carrier resource configuration unit is configured to perform multi-carrier resource configuration according to the reconfiguration request message received by the receiving unit when there is no HSUPA resource in the cell;

The updating unit is configured to update an existing multi-carrier resource according to the reconfiguration request message received by the receiving unit when the HSUPA resource already exists in the cell.

The device according to claim 14, wherein the updating unit further comprises: a first configuration update unit and a second configuration update unit;

The first configuration update unit is configured to: when the received reconfiguration request message includes the HSUPA resource configuration information and the HSUPA resource is configured in the cell, replace the original configuration with the information in the new information element as the E- The frequency, the time slot, and the code channel list of the PUCH channel; when the received reconfiguration request message does not include the configuration information of the carrier frequency, and the HSUPA resource of the carrier frequency is configured in the cell, the carrier frequency is deleted. HSUPA resources;

The second configuration update unit is configured to: when the received HSUPA resource configuration information is included in the received reconfiguration request message, and the HSUPA resource of the carrier frequency is configured in the cell, the information in the information element where the carrier frequency is located Replacing the original configuration as the frequency, time slot, and code channel list of the E-PUCH channel in the carrier frequency; when any of the HSUPA resource configuration information elements in the received reconfiguration request message includes the carrier frequency information element and is not included The slot information element deletes the existing E-PUCH resource at the frequency indicated by the carrier frequency information element.

The apparatus according to claim 13, wherein the message unit further comprises: a success unit, a partial success unit, and a failure unit;

The success unit is configured to return a physical shared channel reconfiguration response message after all carriers successfully configure or reconfigure physical channel resources;

The failure unit is configured to return a physical shared channel when all carrier configurations or reconfiguration fails. OP080634

WO 2009/026833 PCT/CN2008/072079

- 17- Configuration failure message.

The apparatus according to claim 16, wherein the partial success unit further comprises: a first part configuration unit and a second part configuration unit;

The second part configuration unit is configured to: when the device supports only a part of the carrier configuration, the HSUPA resource on the part of the carrier is regarded as being successfully established or reconfigured or deleted, and the HSUPA configuration on the other failed frequency points is rejected. At the same time, a newly added physical shared channel reconfiguration complete message containing the cause information element corresponding to each frequency point causing the failure is returned; then the value of the configuration effective information element in the message is saved.