Abstract:
A method for transmitting information includes: by a NodeB, receiving a message for setting up/reconfiguring a shared Enhanced Dedicated Channel (E-DCH) transmission channel from a Radio Network Controller (RNC); and setting up the shared E-DCH transmission channel according to parameters in the message, and exchanging information with the RNC through an established shared E-DCH transmission bearer. A system and NodeB for transmitting information are also provided. With the present invention, the NodeB and the RNC can share the E-DCH transmission bearer, thus saving the channel resources between the NodeB and the RNC while speeding up the information transmission between the RNC and the NodeB.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation of International Application No PCT/CN2008/072841, filed on Oct. 27, 2008, which claims priority to Chinese Patent Application No. 200710124236.6, filed on Oct. 31, 2007, both of which are hereby incorporated by reference in their entireties. 
     
    
     FIELD OF THE INVENTION 
       [0002]    The present invention relates to mobile communication technologies, and in particular, to a method, apparatus, and system for transmitting information. 
       BACKGROUND OF THE INVENTION 
       [0003]    A mobile communication system includes a User Equipment (UE), a base station, and a radio network control device. For ease of description, it is assumed that the base station is a NodeB of Universal Mobile Telecommunications System, and that the radio network control device is a Radio Network Controller (RNC) hereunder. The channel between the UE and the NodeB and the channel between the NodeB and the RNC are Random Access Channels (RACHs). 
         [0004]    To enhance the data transmission rate between the UE and the NodeB, a solution is put forward in the industry: using High Speed Downlink Packet Access (HSDPA) in the downlink common channel, thus making the theoretical downlink transmission rate as high as 100 Kbps. However, the downlink transmission rate is affected by the uplink transmission rate. For example, uplink transmission is currently performed on a shared RACH, which leads to slow uplink response and affects the downlink transmission rate. 
         [0005]    To solve the problem, another solution is put forward in the industry: using High Speed Uplink Packet Access (HSUPA) to implement random access. This solution requires the UE to use an Enhanced Dedicated Channel (E-DCH) transmission channel to transmit the specific messages in the uplink transmission at random access. That is, an E-DCH should be used between the UE and the NodeB. This solution increases the speed of exchanging information between the UE and the NodeB massively. 
         [0006]    During implementing of the present invention, the inventor finds at least the following problems in the prior art: 
         [0007]    To increase the speed of transmitting the data sent by the UE in the uplink direction between the RNC and the NodeB, an E-DCH transmission channel may also be used between the RNC and the NodeB. Because the UE data quantity is small and intermittent, if a dedicated E-DCH channel is used between the RNC and the NodeB, resources are wasted drastically. 
         [0008]    The channel between the RNC and the NodeB is port-based. This channel is different from the air interface based channel between the UE and the NodeB, and the method for allocating an E-DCH transmission channel between the UE and the NodeB at random access is not applicable to allocation of the channel between the RNC and the NodeB. 
       SUMMARY OF THE INVENTION 
       [0009]    The embodiments of the present invention provide a method for transmitting information to save the channel resources between the RNC and the NodeB while speeding up the information transmission between the RNC and the NodeB. In addition, the embodiments of the present invention provide an apparatus and system for transmitting information. 
         [0010]    The objectives of the present invention are fulfilled through the following technical solution. 
         [0011]    A method for transmitting information is provided in an embodiment of the present invention. The method includes: 
         [0012]    receiving, by a NodeB, a message for setting up/reconfiguring a shared Enhanced Dedicated Channel (E-DCH) transmission channel from a Radio Network Controller (RNC); and 
         [0013]    setting up, by the NodeB, the shared E-DCH transmission channel according to parameters in the message, and exchanging information with the RNC through an established shared E-DCH transmission bearer. 
         [0014]    A system for transmitting information is provided in an embodiment of the present invention. 
         [0015]    An RNC in the system is configured to send a message for setting up/reconfiguring a shared E-DCH transmission channel to a NodeB. 
         [0016]    The NodeB in the system is configured to set up the shared E-DCH transmission channel according to the setup/reconfiguration message sent by the RNC, and exchange information with the RNC through an established shared E-DCH transmission bearer. 
         [0017]    A NodeB for transmitting information is provided in an embodiment of the present invention. 
         [0018]    The NodeB is configured to: receive a message for setting up/reconfiguring a shared E-DCH transmission channel from an RNC, set up the shared E-DCH transmission channel according to the parameters in the message, and exchange information with the RNC through the an established E-DCH transmission bearer. 
         [0019]    Compared with the prior art, the embodiments of the present invention use the NodeB to receive the message for setting up/reconfiguring a shared E-DCH transmission channel from the RNC, and set up the shared E-DCH transmission channel based on the message. Afterward, through the shared E-DCH transmission channel, the NodeB exchanges information with the RNC. Therefore, the NodeB and the RNC can share the E-DCH transmission bearer, thus saving the channel resources between the NodeB and the RNC while speeding up the information transmission between the RNC and the NodeB. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0020]      FIG. 1  is a sequence diagram of configuring a shared E-DCH transmission channel between an RNC and a NodeB according to an embodiment of the present invention; 
           [0021]      FIG. 2  shows a structure of a system according to an embodiment of the present invention; and 
           [0022]      FIG. 3  shows a structure of a NodeB according to an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION OF THE EMBODIMENTS 
       [0023]    To make the technical solution, objectives and merits of the present invention clearer, the following describes the embodiments of the present invention in detail with reference to some accompanying drawings. 
         [0024]    As shown in  FIG. 1 , the process of configuring a shared E-DCH transmission channel between an RNC and a NodeB according to an embodiment of the present invention includes the following content. 
         [0025]    Step  101 : The RNC sends a message for setting up/reconfiguring a shared E-DCH transmission channel to the NodeB, requesting the NodeB to set up an E-DCH transmission channel. 
         [0026]    It is assumed herein that the setup/reconfiguration message sent by the RNC to the NodeB is a setup/reconfiguration request. 
         [0027]    The RNC needs to send a request to the NodeB, notifying the parameters required for channel setup/reconfiguration. For example, the parameters may include: the signature list and/or the relevant physical layer channel parameters used when the UE performs random access through the E-DCH, and/or the relevant physical layer channel parameters; and the parameters may further include one or more of these parameters: the physical layer parameters required when the UE performs random access through the E-DCH, transmission channel parameters required when the UE performs random access through the E-DCH, or transmission bearer parameters required when the UE performs random access through the E-DCH, or may further include one or all of the above two types of parameters. The parameters may be sent through a new message; or the parameters are added into a message of the existing process, which means the parameters are sent through the existing process. 
         [0028]    If the RNC sends the signature list used when the UE performs random access through the E-DCH to the NodeB, the RNC may send the signature list in many modes. This embodiment provides several modes: (1) A table is stipulated in the protocol, and a serial number of the table is assigned and sent; or (2) a signature sequence is configured and sent; or (3) the signature list is sent in the mode like Preamble Signatures in the traditional Physical Random Access Channel (PRACH). These sending modes may be performed in the process of setting up the common transmission channel. 
         [0029]    If the RNC sends the physical layer channel parameters required when the UE performs random access through the E-DCH to the NodeB, the RNC may send the parameters in many modes. This embodiment provides the specific processing modes for the RNC to notify the NodeB to assign the relevant resources through configuration of the channel such as the Arrest Indication Channel (AICH), High Speed-DSCH-related Shared Control Channel (HS-SCCH), and High Speed Physical Downlink Shared Channel (HS-PDSCH). The detailed modes are as follows: 
         [0030]    (1) An Arrest Indication (AI) is added into an AICH sent to the NodeB, indicating that the AICH may be used at the time of performing random access through the E-DCH. In this case, the AICH may be modified in the common transmission setup process. 
         [0031]    (2) The second mode is specific to the HS-SCCH. In this mode, the HS-SCCH sent to the NodeB may carry at least one of these items: physical-layer parameters, HS-SCCH format number, and HS-SCCH time sequence relation. In this case, the HS-SCCH may be modified in the process of reconfiguring the physical shared channel. The physical-layer parameters may be channelized codes and power. The power may be the maximum transmit power and/or initial transmit power; for the HS-SCCH format number, the current HS-SCCH comes in three formats, and the specific format needs to be indicated; the HS-SCCH time sequence relation may be a contrast between the HS-SCCH and an absolute time sequence, for example, an offset from the AICH or Primary Common Control Physical Channel (P-CCPCH), measured in timeslots or 256 chips. 
         [0032]    (3) The third mode is specific to the HS-PDSCH. In this mode, the HS-PDSCH sent to the NodeB may be added at least one of these items: physical-layer parameters, HS-PDSCH time sequence relation, and transmission channel parameters. In this mode, the HS-PDSCH may be modified in the process of setting up the common transmission channel. Besides, the physical-layer parameters may include at least one of these items: channelized code, modulation mode, power, and TB size; the HS-PDSCH time sequence relation may be a contrast between an HS-PDSCH and an absolute time sequence, for example, an offset from an AICH or P-CCPCH, measured in timeslots or 256 chips; the transmission channel parameters include an indication of the MAC format, specifically including MAC-hs, MAC-ehs in DPA enhancement, or a newly defined format. 
         [0033]    If the RNC sends the relevant E-DCH physical-layer parameters required when the UE performs random access through the E-DCH, transmission channel parameters required when the UE performs random access through the E-DCH, and the transmission bearer parameters required when the UE performs random access through the E-DCH, etc, to the NodeB, the RNC may send the parameters in many modes as the same. 
         [0034]    The E-DCH physical-layer parameters may include the parameters in the following Table 1, and such parameters may be added in the process of setting up the common transmission channel. 
         [0000]    
       
         
               
               
             
           
               
                   
                 TABLE 1 
               
               
                   
                   
               
             
             
               
                   
                 E-DPCH Information 
               
               
                   
                 &gt;Maximum Set of E-DPDCHs 
               
               
                   
                 &gt;Puncture Limit 
               
               
                   
                 &gt;E-TFCS Information 
               
               
                   
                 &gt;E-TTI 
               
               
                   
                 &gt;E-DPCCH Power Offset 
               
               
                   
                 &gt;HARQ Info for E-DCH 
               
               
                   
                 E-DCH FDD Information 
               
               
                   
                 F-DPCH Information 
               
               
                   
                 &gt;Power Offset Information 
               
               
                   
                 &gt;&gt;PO2 
               
               
                   
                 &gt;FDD TPC DL Step Size 
               
               
                   
                 &gt;Limited Power Increase 
               
               
                   
                 &gt;Inner Loop DL PC Status 
               
               
                   
                   
               
             
          
         
       
     
         [0035]    The transmission channel parameters may include the parameters in the following Table 2. Specifically, an indication may be added into the shared physical channel reconfiguration to indicate that the parameters can be used at the time of performing random access through the E-DCH. Alternatively, the parameters are directly added into the process of setting up the common transmission channel. 
         [0000]    
       
         
               
               
             
           
               
                   
                 TABLE 2 
               
               
                   
                   
               
             
             
               
                   
                 E-AGCH And E-RGCH/E-HICH FDD Scrambling Code 
               
               
                   
                 E-AGCH Code FDD Information 
               
               
                   
                 E-RGCH/E-HICH Code FDD Information 
               
               
                   
                   
               
             
          
         
       
     
         [0036]    The transmission bearer may include the optional parameters in the following Table 3. These optional parameters may be added in the process of setting up the common transmission channel. 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 3 
               
               
                   
               
               
                   
                   
                   
                 IE Type and 
                 Semantics 
               
               
                 IE/Group Name 
                 Presence 
                 Range 
                 Reference 
                 Description 
               
               
                   
               
             
             
               
                 RL Specific E-DCH 
                   
                 1 . . . 
                   
                   
               
               
                 Information 
                   
                 &lt;maxnoofEDCHMACdFlows&gt; 
               
               
                 &gt;Binding ID 
                 ◯ 
                   
                 9.2.1.4 
                 Shall be ignored if 
               
               
                   
                   
                   
                   
                 bearer establishment 
               
               
                   
                   
                   
                   
                 with ALCAP. 
               
               
                 &gt;Transport Layer 
                 ◯ 
                   
                 9.2.1.63 
                 Shall be ignored if 
               
               
                 Address 
                   
                   
                   
                 bearer establishment 
               
               
                   
                   
                   
                   
                 with ALCAP. 
               
               
                 &gt;&gt;&gt;&gt;Common 
                 ◯ 
                   
                 9.2.1.14 
               
               
                 Transport Channel ID 
               
               
                 &gt;&gt;&gt;&gt;Transport Format 
                 ◯ 
                   
                 9.2.1.59 
                 For the UL. 
               
               
                 Set 
               
               
                 &gt;&gt;&gt;&gt;TNL QoS 
                 ◯ 
                   
                 9.2.1.58A 
                 Shall be ignored if 
               
               
                   
                   
                   
                   
                 bearer establishment 
               
               
                   
                   
                   
                   
                 with ALCAP. 
               
               
                 E-AGCH Power Offset 
                 ◯ 
                   
                 9.2.2.13Id 
               
               
                 E-RGCH Power Offset 
                 ◯ 
                   
                 9.2.2.13Ie 
               
               
                 E-HICH Power Offset 
                 ◯ 
                   
                 9.2.2.13If 
               
               
                   
               
             
          
         
       
     
         [0037]    Step  102 : The NodeB sets up the shared E-DCH transmission channel according to parameters in the received message, and exchanges information with the RNC through an established shared E-DCH transmission bearer. 
         [0038]    The NodeB may return a channel setup/reconfiguration response to the RNC, notifying the information about the established E-DCH transmission channel. 
         [0039]    The NodeB sets up the corresponding shared E-DCH transmission channel according to the parameters sent by the RNC, and returns the information about the established channel to the RNC. Specifically, the transmission-layer address and/or Binding ID is notified to the RNC. Alternatively, other relevant parameters of the E-DCH transmission channel may be notified to the RNC. 
         [0040]    Moreover, after the shared E-DCH transmission channel is set up, if the NodeB needs to send UE information to the RNC, the UE ID needs to be notified to the RNC. Specifically, after receiving the information sent by the UE, the NodeB also needs to add the UE ID into the received information, with a view to modifying the data to new E-DCH data, or with a view to modifying the E-DCH FP frame corresponding to the data to the FP frame that carries the UE ID. 
         [0041]    The modified FP frame is shown in the following Table 4. 
         [0000]    
       
         
               
               
             
               
               
               
             
               
             
               
               
               
             
               
               
               
             
               
               
               
             
               
               
             
               
               
               
             
               
               
               
             
               
               
               
             
               
               
               
             
               
               
             
               
               
               
             
               
               
               
             
               
               
               
             
               
               
               
             
               
               
             
               
               
               
             
               
             
           
               
                 TABLE 4 
               
               
                   
               
             
             
               
                 Header crc 
                 FT 
               
             
          
           
               
                 Header CRC cont 
                 FSN 
                   
               
               
                 Spare 
                 Numbers of subframe 
               
             
          
           
               
                 CFN 
               
               
                 UEid1 
               
               
                 UEid1 
               
               
                 Ueid 2 
               
               
                 Ueid 2 
               
               
                 Ueid n 
               
               
                 Ueid n 
               
             
          
           
               
                 Ue 1 
                 Nof HARQ Retransm 
                 1st subframe No. 
               
             
          
           
               
                 N of MAC-es PDUs 
                 First DDI 
                   
               
             
          
           
               
                 First DDI 
                 First N 
                   
               
             
          
           
               
                 Last DDI 
                 Last N 
               
             
          
           
               
                 Last N cont 
                 PAd 
                   
               
             
          
           
               
                 Ue 1 
                 Nof HARQ Retransm 
                 Last subframe No. 
               
             
          
           
               
                 N of MAC-es PDUs 
                 First DDI 
                   
               
             
          
           
               
                 First DDI 
                 First N 
                   
               
             
          
           
               
                 Last DDI 
                 Last N 
               
             
          
           
               
                 Last N cont 
                 PAd 
                   
               
             
          
           
               
                 Ue 1 
                 Nof HARQ Retransm 
                 Last subframe No. 
               
             
          
           
               
                 N of MAC-es PDUs 
                 First DDI 
                   
               
             
          
           
               
                 First DDI 
                 First N 
                   
               
             
          
           
               
                 Last DDI 
                 Last N 
               
             
          
           
               
                 Last N cont 
                 PAd 
                   
               
             
          
           
               
                 New IE flag 
               
               
                 First MAC-es PDU of 1st subframe of UE1 
               
               
                 Last MAC-es PDU of Last subframe of UE1 
               
               
                 Last MAC-es PDU of Last subframe of UEn 
               
               
                 Payload CRC 
               
               
                 Payload CRC cont 
               
               
                   
               
             
          
         
       
     
         [0042]    In the foregoing solution which uses a shared E-DCH transmission channel to transmit data to the RNC, it is necessary to modify the processing logic of the RNC so that the RNC can resolve the UE ID. Specifically, the MAC-es entity may be modified accordingly. Nevertheless, the modification is based on the precondition that the entity corresponding to the resolved UE ID in the RNC is a MAC-es entity. If the entity corresponding to the UE ID is another entity, the entity needs to be modified accordingly. 
         [0043]    The foregoing embodiment reveals that: Random access can also be performed between the RNC and the NodeB through an E-DCH, thus saving the channel resources between the RNC and the NodeB. 
         [0044]    As shown in  FIG. 2 , the system provided in an embodiment of the present invention includes an RNC  210  and a NodeB  220 . 
         [0045]    The RNC  210  needs to send a message for setting up/reconfiguring a shared E-DCH transmission channel to the NodeB  220 . 
         [0046]    The NodeB  220  needs to set up the shared E-DCH transmission channel according to parameters in the message, and exchange information with the RNC through an established shared E-DCH transmission bearer. 
         [0047]    The NodeB  220  is further configured to return the information about the established shared E-DCH transmission channel to the RNC  210 . 
         [0048]    Afterward, information may be transmitted between the NodeB  220  and the RNC  210  through the established shared E-DCH transmission bearer. 
         [0049]    When the RNC  210  sends the setup/reconfiguration request, the setup/reconfiguration request sent by the RNC  210  may carry a signature list used when the UE performs random access through the E-DCH, relevant physical-layer channel parameters required when the UE performs random access through the E-DCH, relevant physical-layer parameters required when the UE performs random access through the E-DCH, transmission channel parameters, or transmission bearer parameters, or any combination thereof. 
         [0050]    The RNC  210  sends a setup/reconfiguration request and returns the information about the established shared E-DCH transmission channel to the NodeB  220 , which is detailed above and not described further. 
         [0051]    After the shared E-DCH transmission bearer channel is set up, if the NodeB  220  needs to send UE information to the RNC  210 , the UE ID needs to be notified to the RNC  210 . Specifically, after receiving the information sent by the UE, the NodeB  220  also needs to add the UE ID into the received information, with a view to modifying the data to new E-DCH data, or with a view to modifying the E-DCH FP frame corresponding to the data to the FP frame that carries the UE ID. 
         [0052]    Accordingly, the RNC  210  needs to resolve the received information to obtain the UE ID. For example, for the new E-DCH data and E-DCH FP frame, the MAC-es entity in the RNC  210  needs to be modified. The implementation is detailed above, and is not described further. 
         [0053]    The foregoing method and system embodiments reveal that: In the apparatus embodiment herein, the NodeB  220  needs to set up a shared E-DCH transmission channel according to the parameters in the message sent by the RNC  220 , and may be further configured to return a channel setup/reconfiguration response to the RNC  210  to indicate the information about the established shared E-DCH transmission channel. 
         [0054]    Accordingly, the RNC  210  needs to send a request for setting up/reconfiguring a shared E-DCH transmission channel to the NodeB  220 . 
         [0055]    After the shared E-DCH transmission channel is set up between the NodeB  220  and the RNC  210 , the NodeB  220  may be further configured to: add an UE ID into the information transmitted by the UE through the shared E-DCH transmission channel and convert the data in the information into the E-DCH data that carries the UE ID, or convert the information into an FP frame that carries the UE ID, and send the modified information to the RNC  210  through the shared E-DCH transmission bearer. 
         [0056]    Specifically, the NodeB  220  for transmitting information may include: 
         [0057]    a transceiver module  221 , configured to receive a message for setting up/reconfiguring a shared E-DCH transmission channel from the RNC  210 ; and 
         [0058]    a channel setup module  222 , configured to: set up the shared E-DCH transmission channel according to parameters in the message, and control the transceiver module  221  to exchange information with the RNC  210  through an established shared E-DCH transmission bearer. 
         [0059]    The NodeB may further include: 
         [0060]    an identification module  223 , configured to: add a UE ID into the information received from the UE, modify the data in the information to new E-DCH data, or modify the E-DCH FP frame corresponding to the data to the FP frame that carries the UE ID, and control the transceiver module  221  to send the modified information to the RNC  210  through the shared E-DCH transmission channel. 
         [0061]    The foregoing embodiment reveals that: Random access may also be performed between the RNC and the NodeB through an E-DCH, thus saving the channel resources between the RNC and the NodeB. 
         [0062]    The NodeB and RNC in the embodiments of the present invention may be replaced with other devices of equivalent functions, which also falls within the scope of protection of the present invention 
         [0063]    Based on the descriptions of the preceding embodiments, those skilled in the art may understand that the present invention may be implemented by hardware only or by software and a necessary universal hardware platform. The technical solution of the present invention may be embodied by a software product which may be stored in a nonvolatile storage medium. The storage medium can be a Compact Disk Read-Only Memory (CD-ROM), a USB disk, or a mobile hard disk. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to execute the methods provided in the embodiments of the present invention. 
         [0064]    The above descriptions are merely some exemplary embodiments of the present invention, but not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made without departing from the spirit and principle of the present invention should fall within the scope of the present invention.