Method for random access in wireless communication system, wireless communication system, wireless terminal, and base station unit

CROSS-REFERENCE TO RELATED APPLICATION

0001The present application is a continuation of U.S. application Ser. No. 12/689,639, filed on Jan. 19, 2010, now pending, which is a continuation of PCT international application No. PCT/JP2007/065745 filed on Aug. 10, 2007 in Japan, the contents of each are herein wholly incorporated by reference.

FIELD

0002The embodiments discussed herein are related to a method for random access in a wireless communication system, a wireless terminal, and a base station unit.

BACKGROUND ART

0003For a mobile communication system such as mobile telephones, the third-generation scheme has started providing service through the use of CDMA scheme. The 3GPP (3rd Generation Partnership Project) (R) has been discussed over the next-generation mobile communication system (LTE: Long Term Evolution) which makes communication at a higher speed possible (see Non-Patent Document 1 below). In the project, reduction of delay in transmission is being discussed in addition to enhancement in transmission rate.

0004In the event of initiation of communication between a base station unit (evolved Node B: eNB) and a mobile station unit (User Equipment: UE) serving as a wireless terminal prepares in a mobile communication system, a channel is prepared through which the UE first transmits data. The 3GPP calls this channel a random access channel (RACH) and calls a communication starting procedure using a RACH random access (see Non-Patent Document 2 below).

0005A RACH includes minimum information that causes the eNB to recognize transmission from the UE. A RACH is used at the initiation of the communication and the subsequent communication uses an individual channel (or common channel). A RACH can be shared by a number of UEs unless two or more UEs concurrently use the RACH. For the above, a RACH uses an identifier called a signature with which the eNB can identify UEs concurrently transmitting data through the RACH.

0006Random access is carried out in the following four cases of: (1) transmission of first data; (2) establishment uplink synchronization when downlink data arrive; (3) request of uplink data transmission when uplink data arrive; and (4) establishment of synchronization with a destination base station when handover occurs. The direction from the eNB to the UE is defined as “downlink (DL)”, and the reverse direction is defined as “uplink (UL)”.

0007Here, when (1) transmission of first data or when (3) transmission of uplink data, the UE randomly selects one signature from available signatures (preambles) and uses the selected signature (Contention Based Random Access Procedure). Accordingly, there is a possibility, however being low, of two or more UEs concurrently transmit data using the same signature.

0008Conversely, the eNB allocates a dedicated signature to the UE in advance when (2) transmission of downlink data. A possible collision of a signature may cause an instantaneous interruption of the connection or communication disconnection of the communication when (4) handover occurs. Therefore, a dedicated signature is allocated to the UE that is the subject of the handover (Non-contention Based Random Access Procedure).

0000(a) Contention Based Random Access Procedure:

0009<figref idref="DRAWINGS">FIG. 20</figref> illustrates an example of a random access procedure used in the above cases (1) and (3) disclosed in the non-Patent Document 2.

0010Upon uplink data arrival, the UE transmits a message (Random Access Preamble) #<b>1</b>-<b>1</b> (uplink transmission request) containing a signature randomly selected to the eNB through the RACH (step S<b>101</b>). At that time, there is a possibility of occurrence of a contention because two or more UEs concurrently start transmission through the use of the same signature. However, even when a contention occurs, the eNB cannot recognize the effective ID of each UE and cannot therefore grasp that the contention occurs between which UEs.

0011Upon receipt of the message #<b>1</b>-<b>1</b> (the signature), the eNB reply with the response message (Random Access Response) #<b>1</b>-<b>2</b> to the received message #<b>1</b>-<b>1</b> (step S<b>102</b>) along with a timing advanced as synchronization signals for uplink communication, an uplink grant for transmission permission, and others. If a number of UEs <b>20</b> concurrently transmit requests through the RACH, the eNB <b>10</b> returns the response message #<b>1</b>-<b>2</b> to the UEs <b>20</b>.

0012Next, the UE, which receives the response message #<b>1</b>-<b>2</b>, transmits the ID of the UE itself via a message (Scheduled Transmission) #<b>1</b>-<b>3</b> to request the eNB <b>10</b> to schedule UL communication to the eNB (step S<b>103</b>).

0013Upon receipt of the message #<b>1</b>-<b>3</b>, the eNB recognizes the effective ID of the UE (hereinafter also called a terminal ID) and thereby can grasp that the contention of the signature occurs between which UEs. If a contention occurs, the eNB transmits a message (Contention Resolution) #<b>1</b>-<b>4</b> to the UEs in question to resolve the contention (step S<b>104</b>).

0000(b) Non-contention Based Random Access Procedure

0014<figref idref="DRAWINGS">FIG. 21</figref> illustrates an example of a random access procedure (Non-contention Based Random Access Procedure) used in the above cases (2) and (4) disclosed in the Non-Patent Document 2.

0015The eNB allocates a dedicated signature to each UE under the control of the eNB via a message (Random Access Preamble assignment) #<b>2</b>-<b>1</b> in advance (step S<b>20</b>).

0016The UE issues UL synchronization request to the eNB using the dedicated signature allocated by the eNB via the message #<b>2</b>-<b>1</b>. In other words, the UE transmits a message #<b>2</b>-<b>2</b> containing a dedicated signature to the eNB through the RACH (step S<b>202</b>).

0017Upon receipt of the message #<b>2</b>-<b>2</b>, the eNB replies with the response message #<b>2</b>-<b>3</b> to the received message (step S<b>203</b>) along with a timing advanced as synchronization signal, an uplink grant for transmission permission, and others.

0018Non-Patent Document 1: 3GPP, “Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)”, TR25.913 V7.3.0, Release 7, March 2006

0019Non-Patent Document 2: 3GPP, “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)”, TS36.300, Release 8, V8.1.0, June 2007

0020As described above, since the non-Patent Document 2 examines two kinds of procedure of random access, different procedures concurrently proceed in, for example, cases of (2) establishment uplink synchronization when downlink data arrive and (3) request of uplink data transmission when uplink data arrive.

0021Since different procedures concurrently proceeding as the above requires respective resources (such as signature), two kinds of signature are allocated while the procedures are proceeding so that the signatures are wasted.

SUMMARY

0022(1) According to an aspect of the embodiments, a method includes a method for random access in a wireless communication system including a base station unit and a wireless terminal, the method including: at the wireless terminal, detecting first information used for first random access and second information used for second random access, the second information being received from the base station unit; and selecting one between the first information and the second information.

0023(2) According to an aspect of the embodiments, a method includes a method for random access in a wireless communication system including a base station unit and a wireless terminal, the method including: at the wireless terminal, receiving second information used for second random access in response to generation of downlink data from the base station unit before creating first information used for first random access in response to generation of uplink data destined for the base station unit, transmitting third information, which is transmitted to the base station unit during the first random access, to the base station unit during or after the completion of the second random access using the second information.

0024(3) According to an aspect of the embodiments, a system includes a wireless communication system including a base station unit and a wireless terminal, wherein the wireless terminal selects one from first information used for first random access and second information used for second random access, the second information being received from the base station unit; and the base station unit releases management of the information that is not selected between the first information and the second information.

0025(4) According to an aspect of the embodiments, an apparatus includes a wireless terminal including: creating means that creates first information used for first random access to a base station unit; receiving means that receives, from the base station unit, second information used for second random access to the base station unit; and selecting means that selects one between the first information and the second information.

0026(5) According to an aspect of the embodiments, an apparatus includes a base station unit including: managing means that manages first information used for first random access received from a wireless terminal and second information used for second random access transmitted to the wireless terminal; determining means that determines, based on third information received from the wireless terminal, one selected by the wireless terminal between the first information and the second information; and controlling means that continuing random access corresponding to the information that the determining means determines that the wireless terminal selects and that carries out control based on the third information.

0027The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.

0028It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

0029<figref idref="DRAWINGS">FIG. 1</figref> is a functional block diagram illustrating a base station (eNB) according to a first embodiment;

0030<figref idref="DRAWINGS">FIG. 2</figref> is a functional block diagram illustrating a mobile station (UE) according to the first embodiment;

0031<figref idref="DRAWINGS">FIG. 3</figref> is a sequence diagram explaining a procedure (method) of random access according to the first embodiment;

0032<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram explaining the operation of the eNB when carrying out the random access procedure of FIG. <b>3</b>;

0033<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram explaining the operation of the UE when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 3</figref>;

0034<figref idref="DRAWINGS">FIG. 6</figref> is a sequence diagram explaining a case in which different random access procedures are concurrently proceeding;

0035<figref idref="DRAWINGS">FIG. 7</figref> is a sequence diagram explaining a procedure (method) of random access according to a second embodiment;

0036<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram explaining the operation of the eNB when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 7</figref>;

0037<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram explaining the operation of the UE when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 7</figref>;

0038<figref idref="DRAWINGS">FIG. 10</figref> is a sequence diagram explaining a first modification to the second embodiment;

0039<figref idref="DRAWINGS">FIG. 11</figref> is a sequence diagram explaining a second modification to the second embodiment;

0040<figref idref="DRAWINGS">FIG. 12</figref> is a sequence diagram explaining a procedure (method) of random access according to a third embodiment;

0041<figref idref="DRAWINGS">FIG. 13</figref> is a flow diagram explaining the operation of the eNB when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 10</figref>;

0042<figref idref="DRAWINGS">FIG. 14</figref> is a flow diagram explaining the operation of the UE when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 10</figref>;

0043<figref idref="DRAWINGS">FIG. 15</figref> is a sequence explaining a procedure (method) of random access according to a fourth embodiment;

0044<figref idref="DRAWINGS">FIG. 16</figref> is a flow diagram explaining the operation of the eNB when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 13</figref>;

0045<figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram explaining the operation of the UE when carrying out the random access procedure of <figref idref="DRAWINGS">FIG. 13</figref>;

0046<figref idref="DRAWINGS">FIG. 18</figref> is a sequence diagram explaining a procedure (method) of random access according to a fifth embodiment;

0047<figref idref="DRAWINGS">FIG. 19</figref> is a sequence explaining a procedure (method) of random access according to a sixth embodiment;

0048<figref idref="DRAWINGS">FIG. 20</figref> is a sequence diagram explaining a conventional procedure of random access (contention based random access); and

0049<figref idref="DRAWINGS">FIG. 21</figref> is a sequence diagram explaining a conventional procedure of random access (non-contention based random access).

DESCRIPTION OF EMBODIMENTS

0050Hereinafter, embodiments will be described with reference to the drawings. Note that the embodiments are not limited to the embodiments to be described below, but may be modified in various ways without departing from sprits and scope of the embodiments, as a matter of course.

(1) First Embodiment

0051<figref idref="DRAWINGS">FIG. 1</figref> is a functional block diagram of a base station unit (eNB) according to the first embodiment; and <figref idref="DRAWINGS">FIG. 2</figref> is a functional block diagram of a mobile station unit (UE) according to the first embodiment. The eNB <b>10</b> and the UE <b>20</b> form a wireless communication system. The wireless communication system can include a number of eNBs <b>10</b> and a number of UEs <b>20</b>. The configurations illustrated in <figref idref="DRAWINGS">FIGS. 1 and 2</figref> are also common to second through fourth embodiments detailed below unless otherwise specified. In addition, the base station unit <b>10</b> of the first embodiment assumes to be an LTE eNB which possesses a part of or the entire function of a radio network controller (RNC), but may be a base station of a former generation of the LET (i.e., without the function of RNC). In addition, the base station may comply with any system as long as adopting both the contention based random access procedure and the non-contention based random access procedure.

0000(Description of eNB)

0052Focusing on the major functions, the eNB <b>10</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes, for example, an antenna <b>11</b>, a transmitting/receiving unit, a buffering unit <b>13</b>, a judging unit <b>14</b>, a signature managing unit <b>15</b>, and a wireless resource managing unit <b>16</b>.

0053Here, the antenna <b>11</b> receives an uplink wireless signal from the UE <b>20</b> while transmits downlink wireless signal to the UE <b>20</b>. The antenna <b>11</b> is commonly used for transmitting and receiving, but alternatively an antenna for transmitting may be separated from an antenna for receiving.

0054The transmitting/receiving unit (transmitting means, receiving means) <b>12</b> performs predetermined receiving processing on an uplink wireless signal received by the antenna <b>11</b> while performs predetermined transmitting processing on data (downlink data) from the buffering unit <b>13</b>.

0055The receiving processing includes, for example, low-noise amplification, frequency conversion (down-conversion) to the baseband frequency, gain adjustment, demodulation by a predetermined demodulating scheme, and decoding by a predetermined decoding scheme. The transmitting processing includes encoding of the uplink transmission data by a predetermined encoding scheme, modulating of the encoded data by a predetermined modulating scheme (such as QPSK or 16QAM), creating of a predetermined wireless frame, frequency conversion (up-conversion) to the radio frequency, and electric power amplification. The above wireless frame is exemplified by one conforming to OFDMA, OFDMA, or others.

0056The buffering unit <b>13</b> temporarily stores downlink data destined for the UE <b>20</b> under the control of the signature managing unit <b>15</b>. The judging unit (determining means) <b>14</b> has a function of determining which signature was selected between a random signature and a dedicated signature through judging, on the basis of uplink data (message) subjected to receiving processing in the transmitting/receiving unit <b>12</b>, whether or not an UL synchronization request or an UL scheduling request is issued from the UE <b>20</b>.

0057In the first embodiment, a random signature represents a signature (first information) that the UE <b>20</b> randomly creates and a dedicated signature represents a signature (second information) that the eNB <b>10</b> allocates (sends) to the UE <b>20</b>. The detailed method for the judgment will be described below.

0058The signature managing unit (managing means) <b>15</b> manages a signature (Random Access Preamble, hereinafter also called a preamble) used for random access (procedure), creates a downlink message destined for the UE <b>20</b> and used for random access, and has a function of allocating and releasing a signature for the UE <b>20</b>. The release is based on the result of the judgment by the judging unit <b>14</b>.

0059The wireless resource managing unit <b>16</b> manages UL and DL wireless resources (e.g. channel frequency and time (transmitting/receiving timings)) to be used for communication (including communication when random accessing) with the UE <b>20</b> and allocation of the resources. For example, when OFDMA is adopted, the wireless resource managing unit <b>16</b> has a function to manage the mapping of a two-dimensional transmitting/receiving region (called a burst) defined in terms of the sub-channel frequency and the symbol time.

0060In addition, the wireless resource managing unit <b>16</b> has a function as controlling means that carries out control based on an uplink message (third information) which is received from the UE <b>20</b> during random access corresponding to the signature that is not selected by the UE <b>20</b>.

0000(Description of UE)

0061Focusing on the major functions, the UE <b>20</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref> includes, for example, an antenna <b>21</b>, a transmitting/receiving unit <b>22</b>, a buffering unit <b>23</b>, a signature managing unit <b>24</b>, an access judging unit <b>25</b>, and an identifier providing unit <b>26</b>.

0062Here, the antenna <b>21</b> receives a downlink wireless signal from the eNB <b>10</b> while transmits an uplink wireless signal to the eNB <b>10</b>. Also the antenna <b>21</b> is commonly used for transmitting and receiving, but alternatively, an antenna for transmitting may be separated from an antenna for receiving.

0063The transmitting/receiving unit (transmitting means, receiving means) <b>22</b> performs predetermined receiving processing on a downlink wireless signal received by the antenna <b>21</b> while performs predetermined transmitting processing on data (uplink data) from the buffering unit <b>23</b> and on an uplink message (e.g., a Random. Access Preamble and a Scheduled Transmission message) destined for an eNB via the identifier providing unit <b>26</b>.

0064The receiving processing by the UE <b>20</b> also includes, for example, low-noise amplification, frequency conversion (down-conversion) to the baseband frequency, gain adjustment, demodulation by a predetermined demodulating scheme, and decoding by a predetermined decoding scheme. The transmitting processing includes encoding of the uplink transmission data by a predetermined encoding scheme, modulating of the encoded data by a predetermined modulating scheme (such as QPSK or 16QAM), multiplexing (mapping) of uplink data to a predetermined wireless frame, frequency conversion (up-conversion) to the radio frequency, and electric power amplification.

0065The buffering unit <b>23</b> temporarily stores uplink data destined for the eNB <b>10</b> under the control of the signature managing unit <b>24</b>, which manages a signature (Random Access Preamble) used for random access processing (procedure).

0066The access judging unit <b>25</b> generates a predetermined message to be used for the random access procedure in cooperation with the signature managing unit <b>24</b>. In this example, the access judging unit <b>25</b> has a function of monitoring (confirming) whether or not multiple allocation of signatures occurs, that is, whether or not a dedicated signature allocated by the eNB <b>10</b> and a random signature randomly created by the UE <b>20</b> itself (by the signature managing unit <b>24</b>) exist and in the event of occurrence multiple allocation, determining which signature is made to be effective.

0067The identifier providing unit <b>26</b> has a function of providing an uplink message (e.g., a message informing of the terminal ID) which is destined for the eNB <b>10</b> and which is generated by the access judging unit <b>25</b> with information (an identifier, a flag, or the like) indicating that the uplink message also serves as a message that requests to transmit an uplink data (UL scheduling) because also uplink data is being generated at the UE <b>20</b> or that the uplink message serves as UL synchronization confirmation responsive an UL synchronization requests required for receiving downlink data because downlink data arrives at the eNB <b>10</b>. The UL synchronization confirmation is a notification (confirmation response) to the eNB <b>10</b> that the UE <b>20</b> secures UL synchronization due to correct receiving UL timing information from the eNB <b>10</b>.

0000(Description of a Random Access Procedure)

0068Hereinafter, detailed description will now be made in relation to an operation (a random access procedure) in a wireless communication system of the first embodiment having the above configuration with reference to <figref idref="DRAWINGS">FIGS. 3 through 5</figref>. <figref idref="DRAWINGS">FIG. 3</figref> is a sequence diagram explaining the random access procedure (method) of the first embodiment; <figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram explaining the operation of the eNB <b>10</b> when the random access procedure of the first embodiment is being carried out; and <figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram explaining the operation of the UE <b>20</b> when the random access procedure of the first embodiment is being carried out.

0069Hereinafter, similarly to the description of <figref idref="DRAWINGS">FIGS. 20 and 21</figref>, the messages with the reference numbers #<b>1</b>-<b>1</b> through #<b>1</b>-<b>4</b> represents messages originally used for the contention based random access procedure (first random access) and messages with the reference numbers #<b>2</b>-<b>1</b> through #<b>2</b>-<b>3</b> originally used for the non-contention based random access procedure (second random access).

0070First of all, when the UE <b>20</b> generates uplink data and the buffering unit <b>23</b> stores the uplink data (step B<b>1</b> in <figref idref="DRAWINGS">FIG. 5</figref>), the UE <b>20</b> generates and stores a random signature (Random Access Preamble) at the signature managing unit <b>24</b> (step B<b>2</b> in <figref idref="DRAWINGS">FIG. 5</figref>). Namely, the signature managing unit <b>24</b> has a function as creating means that creates a signature to be used for the contention based random access, which is executed when uplink data destined for the eNB <b>10</b> is generated.

0071After that, the UE <b>20</b> creates a random access preamble message (uplink transmission request) #<b>1</b>-<b>1</b> containing the created signature at the access judging unit <b>25</b> and transmits the created message to the eNB <b>10</b> from the antenna <b>21</b> via the transmitting/receiving unit <b>22</b> (step Sla of <figref idref="DRAWINGS">FIG. 3</figref> and step B<b>3</b> in <figref idref="DRAWINGS">FIG. 5</figref>).

0072Upon receipt of the uplink transmission request message #<b>1</b>-<b>1</b>, the eNB <b>10</b> replies with a response message (Random Access Response) #<b>1</b>-<b>2</b> responsive to the received uplink transmission request message #<b>1</b>-<b>1</b> (step S<b>2</b> in <figref idref="DRAWINGS">FIG. 3</figref>) along with a timing advanced as synchronization message for uplink communication, an uplink grant for transmission permission, and others. If a number of UEs <b>20</b> concurrently transmit requests through the RACH, the eNB <b>10</b> returns the response message #<b>1</b>-<b>2</b> to the UEs <b>20</b>.

0073Here, presuming that the eNB <b>10</b> could not recognize the uplink transmission request message #<b>1</b>-<b>1</b> that the UE <b>20</b> transmits because downlink data destined for the UE <b>20</b> arrived at the eNB <b>10</b> from the upper apparatus (i.e., the buffering unit <b>13</b> stores downlink data) before the transmission of the response message #<b>1</b>-<b>2</b> (step A<b>1</b> in <figref idref="DRAWINGS">FIG. 4</figref>) and the eNB <b>10</b> does not complete the receiving process on the downlink data.

0074In this case, the signature managing unit <b>15</b> of the eNB <b>10</b> creates and stores a signature (dedicated signature, the second information) that the UE <b>20</b> that is the destination of the downlink data uses for random access (UL synchronization request) (step A<b>2</b> in <figref idref="DRAWINGS">FIG. 4</figref>), and transmits the dedicated signature to the UE <b>20</b> through the use of a signature allocation message (RA Preamble Assignment) #<b>2</b>-<b>1</b> (step S<b>1</b><i>b </i>in <figref idref="DRAWINGS">FIG. 3</figref> and step A<b>3</b> in <figref idref="DRAWINGS">FIG. 4</figref>).

0075When transmission of the uplink transmission request message #<b>1</b>-<b>1</b> (step S<b>1</b><i>a </i>in <figref idref="DRAWINGS">FIG. 3</figref>) and the signature allocation message #<b>2</b>-<b>1</b> (step S<b>1</b><i>b </i>in <figref idref="DRAWINGS">FIG. 3</figref>) is completed, the eNB <b>10</b> cannot recognize “which UE <b>20</b> uses which signature”. In other words, the eNB <b>10</b> cannot recognize that the two signatures (Random Preamble and Dedicated Preamble) are issued for which UE <b>20</b> because according to Non-Patent Document 2, either message does not contain information (terminal ID) to identify the UE <b>20</b>.

0076According to Non-Patent Document 2, since the terminal ID can be contained in a message (Scheduled Transmission) #<b>1</b>-<b>3</b>, the eNB <b>10</b> grasps which UE <b>20</b> uses which signature after the receipt of the message #<b>1</b>-<b>3</b> from the UE (step S<b>3</b> in <figref idref="DRAWINGS">FIG. 3</figref>).

0077Conversely, regardless of whether or not the UE <b>20</b> notifies the terminal ID of the UE <b>20</b> itself to the eNB <b>10</b>, when transmission of the uplink transmission request message #<b>1</b>-<b>2</b> (step S<b>1</b><i>a </i>in <figref idref="DRAWINGS">FIG. 3</figref>) and the signature allocation message #<b>2</b>-<b>1</b> (step S<b>1</b><i>b </i>in <figref idref="DRAWINGS">FIG. 3</figref>) is completed, both the random signature created by the UE <b>20</b> itself and the dedicated signature (Dedicated Preamble) allocated by the eNB <b>10</b> exist in the UE <b>20</b>, in other words, the UE <b>20</b> can recognize (detect) occurrence of the two kinds of random access.

0078If a number of signatures are issued for a single UE <b>20</b> as the above case, the UE <b>20</b> determines which signature is to be used. Specifically, when the UE <b>20</b> receives (allocation of) a dedicated signature from the eNB <b>10</b> from the step S<b>2</b> (step B<b>4</b> in <figref idref="DRAWINGS">FIG. 5</figref>), the access judging unit <b>25</b> confirms, in cooperation with the signature managing unit <b>24</b>, whether or not multiple allocation of two signatures (preambles) occurs (step B<b>5</b> in <figref idref="DRAWINGS">FIG. 5</figref>).

0079The confirmation concluded occurrence of multiple allocation (yes route in step B<b>5</b>), the UE <b>20</b> (the access judging unit <b>25</b>) ignores the dedicated signature allocated by the eNB <b>10</b> (step S<b>1</b><i>c </i>in <figref idref="DRAWINGS">FIG. 3</figref> and step B<b>6</b> in <figref idref="DRAWINGS">FIG. 5</figref>), and selects the random signature created by the UE <b>20</b> itself as an effective signature. In other words, the access judging unit <b>25</b> has a function of selecting means which selects one between the two signatures. In addition, when no multiple allocation occurs, the UE <b>20</b> determines the random signature created by the UE <b>20</b> itself to be effective (no route in step B<b>5</b>).

0080Thereby, the random access procedure (contention based random access procedure) using the random signature created by the UE <b>20</b> becomes effective, so that the UE <b>20</b> continues the contention based random access procedure.

0081In other words, the UE <b>20</b> creates a message #<b>1</b>-<b>3</b> and transmits the message to the eNB <b>10</b> (step S<b>3</b> in <figref idref="DRAWINGS">FIG. 3</figref> and step B<b>7</b> in <figref idref="DRAWINGS">FIG. 5</figref>). At that time, the UE <b>20</b> grasps, through receiving the signature allocation message #<b>2</b>-<b>1</b>, that the downlink data destined for the UE <b>20</b> itself arrives at the eNB <b>10</b>, and therefore transmits the message #<b>1</b>-<b>3</b> to the eNB <b>10</b> preferably after providing the message with information (such as an identifier or a flag) indicating that “the message #<b>1</b>-<b>3</b> also serves as UL synchronization confirmation required for receiving downlink data”. UL synchronization confirmation is a confirmation response that UL synchronization is secured because the UE <b>20</b> correctly receives UL timing information contained in the message (Random access Response) #<b>1</b>-<b>2</b>.

0082In other words, UL synchronization request (third information), which is transmitted to the eNB <b>10</b> during the non-contention random access which is however not selected, is a message to receive UL timing information from the eNB <b>10</b> for UL synchronization, but the UE <b>20</b> already obtains the timing information during the contention based random access (#<b>1</b>-<b>2</b>). For the above, the UE <b>20</b> provides UL synchronization confirmation informing eNB <b>10</b> of securing of UL synchronization to the message #<b>1</b>-<b>3</b> to be transmitted and then transmits the message #<b>1</b>-<b>3</b>.

0083However, as described above, since the eNB <b>10</b> recognizes the UE <b>20</b> to which two signatures are allocated at the time of receiving the message #<b>1</b>-<b>3</b>, the eNB <b>10</b> can implicitly judge that the message #<b>1</b>-<b>3</b> also serves as a UL synchronization request even when the identifier or a flag is not explicitly provided.

0084Upon recognition of receiving the message (also serving as UL synchronization confirmation) #<b>1</b>-<b>3</b> (yes route of step A<b>4</b> in <figref idref="DRAWINGS">FIG. 4</figref>), the eNB <b>10</b> judges in the judging unit <b>14</b> that the dedicated signature allocated to the UE <b>20</b> is ignored in the same UE <b>20</b> (that is, the random signature created by the UE <b>20</b> is preferentially selected) and consequently releases the dedicated signature allocated to the same UE <b>20</b> in the signature managing unit <b>15</b> (step S<b>3</b>-<b>1</b> in <figref idref="DRAWINGS">FIG. 3</figref> and step A<b>5</b> in <figref idref="DRAWINGS">FIG. 4</figref>).

0085Accordingly, the random access procedure (the non-contention based random access procedure) using the dedicated signature allocated by the eNB <b>10</b> is halted, so that the dedicated signature allocated to the UE <b>20</b> can be released during the random access procedure (at an early stage), which makes it possible to efficiently use signatures. Here, if the message #<b>1</b>-<b>3</b> is determined not to also serve as UL synchronization confirmation (no route in step S<b>4</b>), the downlink data does not arrive and only normal uplink communication occurs, so that the eNB <b>10</b> transmits a message #<b>1</b>-<b>4</b> (step A<b>7</b>).

0086The eNB <b>10</b> starts processing (control), such as scheduling of downlink data, based on the UL synchronization confirmation (third information) in the wireless resource managing unit <b>16</b> (step A<b>6</b> in <figref idref="DRAWINGS">FIG. 4</figref>).

0087By receiving of the message (also serving as UL synchronization confirmation) #<b>1</b>-<b>3</b>, the eNB <b>10</b> can recognize that the response (Random Access Preamble) to the signature allocation message #<b>2</b>-<b>1</b> from the UE <b>20</b> can be omitted, so that unnecessary retransmission of the signature allocation message #<b>2</b>-<b>1</b> can be avoided. Further, reception of the message #<b>1</b>-<b>3</b> used for the contention based random access procedure, despite allocation of the dedicated signature, makes the eNB <b>10</b> possible to recognize generation of uplink data at the UE <b>20</b>.

0088Since the eNB <b>10</b> grasps the effective ID of the UE <b>20</b> through receiving the message (also serving as UL synchronization confirmation) #<b>1</b>-<b>3</b>, so that the eNB <b>10</b> can recognize that the contention occurred between which UEs. The contention can be resolved by transmitting a Contention Resolution message #<b>1</b>-<b>4</b> to the UEs <b>20</b> in question (step S<b>4</b> in <figref idref="DRAWINGS">FIG. 3</figref>).

0089As described above, in the method of random access of the first embodiment, even when uplink data and downlink data arrive in the same UE <b>20</b>, the UE <b>20</b> selects the signature the UE <b>20</b> itself created and thereby the contention based random access is continued. Consequently, the two kinds of random access procedure do not concurrently proceed for a single UE <b>20</b> until the last stage as denoted in <figref idref="DRAWINGS">FIG. 6</figref>. Accordingly, the control plane of the random access can be simplified and signatures used for random access can be efficiently used. In addition, the interference of the random access channel can be inhibited.

0090However, the two kind of random access procedure can be concurrently proceeded. Accordingly, for example, in the event that the message (UL synchronization confirmation) #<b>1</b>-<b>3</b> is contend with another UE, the UE <b>20</b> recognizes occurrence of the contention with reference to the Contention Resolution message #<b>1</b>-<b>4</b> notified from the eNB <b>10</b>. In this case, since continuation of the non-contention based random access may require a time to secure UL synchronization, the contention based random access can be concurrently executed through the use of a dedicated signature allocated in the message #<b>2</b>-<b>1</b> by eNB <b>10</b>. However, the expiration period of a dedicated signature for the UE <b>20</b> needs to be set to be long in that case.

0091Since the information (UL synchronization confirmation) which is transmitted to the eNB <b>10</b> during the non-contention based random access that is not selected is transmitted to eNB <b>10</b> during the contention based random access, the reception processing of downlink data can be surely carried out along with the transmitting processing on uplink data.

0092Further, since the UL synchronization confirmation can be common to the uplink message #<b>1</b>-<b>3</b> that is originally determined to be transmitted to the eNB <b>10</b> during the contention based random access that is selected, there is no need to prepare (define) an unlink message dedicated to UL synchronization confirmation, so that the wireless resource can be efficiently used.

0093Further, since the first embodiment can reduce the number of messages that are communicated between the eNB <b>10</b> and the UE <b>20</b> as compared with a second embodiment to be detailed below, it is possible to efficiently use the wireless resource and to shorten error recovery with the use of retransmission control (HARQ: Hybrid Automatic Repeat reQuest).

(2) Second Embodiment

0094<figref idref="DRAWINGS">FIG. 7</figref> is a sequence diagram illustrating a random access procedure according to the second embodiment; <figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram explaining the operation of eNB <b>10</b> during the random access procedure of the second embodiment; and <figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram explaining the operation of UE <b>20</b> during the random access procedure of the second embodiment.

0095In the second embodiment, in the event of occurrence of multiple allocation of the preambles, the UE <b>20</b> ignores the signature (first information) created by the UE <b>20</b> itself and selects the dedicated signature (second information) allocated by the eNB <b>10</b>. Thereby, the non-contention based random access procedure continues.

0096First of all, when uplink data arrive in the UE <b>20</b> and is stored in the buffering unit <b>23</b> (step B<b>11</b> in <figref idref="DRAWINGS">FIG. 9</figref>), the UE <b>20</b> creates and stores a random signature (Random Access Preamble) at the signature managing unit <b>24</b> (step B<b>12</b> in <figref idref="DRAWINGS">FIG. 9</figref>), creates an uplink transmission request (Random Access Preamble) message #<b>1</b>-<b>1</b> containing the signature at the access judging unit <b>25</b>, and transmits the message #<b>1</b>-<b>1</b> from the antenna <b>21</b> via the transmitting/receiving unit <b>22</b> (step Sla in <figref idref="DRAWINGS">FIG. 7</figref> and step B<b>13</b> in <figref idref="DRAWINGS">FIG. 9</figref>).

0097Upon receipt of the uplink transmission request message #<b>1</b>-<b>1</b>, the eNB <b>10</b> replies with a response message (Random Access Response) #<b>1</b>-<b>2</b> to the received uplink transmission request message (step S<b>2</b> in <figref idref="DRAWINGS">FIG. 7</figref>) along with a timing advanced for synchronization signal for uplink communication, an uplink grant for transmission permission, and others. If a number of UEs <b>20</b> concurrently transmit requests through the RACH, the eNB <b>10</b> returns the response message #<b>1</b>-<b>2</b> to the UEs <b>20</b>.

0098Here, also in the second embodiment presumes that the eNB <b>10</b> could not recognize the uplink transmission request message #<b>1</b>-<b>1</b> transmitted by the UE <b>20</b> because downlink data destined for the UE <b>20</b> arrived at the eNB <b>10</b> from the upper apparatus (i.e., the buffering unit <b>13</b> stores downlink data) before the transmission of the response message #<b>1</b>-<b>2</b> (step A<b>11</b> in <figref idref="DRAWINGS">FIG. 8</figref>) and the eNB <b>10</b> does not complete the receiving process on the downlink data.

0099In this case, the signature managing unit <b>15</b> of the eNB <b>10</b> creates and stores a signature (dedicated signature) that the UE <b>20</b> that is the destination of the downlink data uses for random access (UL synchronization request) (step A<b>12</b> in <figref idref="DRAWINGS">FIG. 8</figref>), and transmits the dedicated signature to the UE <b>20</b> through the use of a signature allocation message (RA Preamble Assignment) #<b>2</b>-<b>1</b> (step S<b>1</b><i>b </i>in <figref idref="DRAWINGS">FIG. 7</figref> and step A<b>13</b> in <figref idref="DRAWINGS">FIG. 8</figref>).

0100The UE <b>20</b>, which receives the signature allocation message #<b>2</b>-<b>1</b>, transmits, to the eNB <b>10</b> through the RACH, a message (Random Access Preamble) #<b>2</b>-<b>2</b> containing the dedicated signature allocated by the eNB <b>10</b>. (step S<b>2</b><i>a </i>in <figref idref="DRAWINGS">FIG. 7</figref>).

0101Here, when transmission of the uplink transmission request message #<b>1</b>-<b>1</b> (step S<b>1</b><i>a </i>in <figref idref="DRAWINGS">FIG. 7</figref>) and signature allocation message #<b>2</b>-<b>1</b> (step S<b>1</b><i>b </i>in <figref idref="DRAWINGS">FIG. 7</figref>) is completed, the UE <b>20</b> can recognizes the presence of both the random signature created by the UE <b>20</b> itself and the dedicated signature allocated by the eNB <b>10</b>.

0102Therefore, the UE <b>20</b> judges which signature is to be used. In other words, when the eNB <b>10</b> allocates a signature from step S<b>2</b> (step B<b>14</b> in <figref idref="DRAWINGS">FIG. 9</figref>), the UE <b>20</b> of the second embodiment confirms, in cooperation with the signature managing unit <b>24</b>, whether or not multiple allocation of two signatures (preambles) is occurring (step B<b>15</b> in <figref idref="DRAWINGS">FIG. 9</figref>).

0103As a result, when multiple allocation is occurring (yes route in step B<b>15</b>), the UE <b>20</b> ignores the random access signature created by the UE <b>20</b> itself (the signature transmitted to the eNB <b>10</b>) (step Sid in <figref idref="DRAWINGS">FIG. 7</figref> and step B<b>16</b> in <figref idref="DRAWINGS">FIG. 9</figref>), and selects the dedicated signature allocated by the eNB <b>10</b> as an effective signature. When multiple allocation is not occurring, the dedicated signature is made effective (no route in step B<b>15</b>).

0104Consequently, the random access procedure (the non-contention based random access procedure) through the use of the dedicated signature allocated by the eNB <b>10</b> continues.

0105After that, the UE <b>20</b> creates the message #<b>1</b>-<b>3</b> and transmits the created message to the eNB <b>10</b> (step S<b>3</b> in <figref idref="DRAWINGS">FIG. 7</figref> and step B<b>17</b> in <figref idref="DRAWINGS">FIG. 9</figref>). Concurrently, since also uplink data arrive, the UE <b>20</b> provides the message #<b>1</b>-<b>3</b> with information (an identifier or a flag) indicating that the message #<b>1</b>-<b>3</b> also “serves as a message (UL scheduling request) to request transmission (scheduling) of unlink data” by the identifier providing unit <b>26</b> and transmits the message #<b>1</b>-<b>3</b> to the eNB <b>10</b>.

0106In other words, UL scheduling request (third information), which is transmitted to the eNB <b>10</b> during the contention random access, which is not selected, is provided to the message #<b>1</b>-<b>3</b> destined for the eNB <b>10</b> and is transmitted to the eNB <b>10</b>.

0107However, as described above, since the eNB <b>10</b> recognizes a UE <b>20</b> to which two signatures are allocated at the time of receiving the message #<b>1</b>-<b>3</b>, the eNB <b>10</b> can implicitly judge that the message #<b>1</b>-<b>3</b> from the UE <b>20</b> also serves as a UL scheduling request even when the identifier or a flag is not explicitly provided.

0108Upon recognition of receiving the message (also serving as UL scheduling request) #<b>1</b>-<b>3</b> (yes route of step A<b>14</b> in <figref idref="DRAWINGS">FIG. 8</figref>), the eNB <b>10</b> judges that the UE <b>20</b> makes the dedicated signature allocated by the eNB <b>10</b> to the UE <b>20</b> effective, and releases the random signature which the eNB <b>10</b> manages and which is received from the UE <b>20</b> in the signature managing unit <b>15</b> (step S<b>3</b>-<b>2</b> in <figref idref="DRAWINGS">FIG. 7</figref> and step A<b>15</b> in <figref idref="DRAWINGS">FIG. 8</figref>).

0109Consequently, the random access procedure (the contention based random access) through the use of the random signature created by the UE <b>20</b> becomes ineffective (halts), so that the dedicated signature can be released during the random access procedure (at an early stage), which makes it possible to efficiently use signatures.

0110In the eNB <b>10</b>, the wireless resource managing unit <b>16</b> carries out processing (control) of allocation of UL wireless resource in response to the UL scheduling request (step A<b>16</b> in <figref idref="DRAWINGS">FIG. 8</figref>). Since the second embodiment makes the dedicated signature effective, there is no need to transmit Contention Resolution message #<b>1</b>-<b>4</b> used for the contention based random access procedure to the UE <b>20</b> in question and therefore the transmission can be halted (step S<b>4</b> in <figref idref="DRAWINGS">FIG. 7</figref> and step A<b>17</b> in <figref idref="DRAWINGS">FIG. 8</figref>). In addition, if the eNB <b>10</b> judges that the message #<b>1</b>-<b>3</b> does not serve as the UL scheduling request, the eNB <b>10</b> terminates the processing (no route in step A<b>14</b> in <figref idref="DRAWINGS">FIG. 8</figref>).

0111As describe above, according to the method of random access of the second embodiment, even when uplink data and downlink data are concurrently arrive in the same UE <b>20</b>, the UE <b>20</b> selects the signature allocated by the eNB <b>10</b> and thereby the non-contention based random access is continued. Consequently, the two kinds of random access procedure do not concurrently proceed until the last. Accordingly, the control plane of the random access can be simplified and signatures used for random access can be efficiently used. In addition, the interference of the RACH can be inhibited.

0112Since the information (UL scheduling request) which is transmitted to the eNB <b>10</b> during the contention based random access that is not selected is transmitted to eNB <b>10</b> during the contention based random access, the reception processing of downlink data can be surely carried out along with the transmitting processing on uplink data.

0113Further, when the UL scheduling request to the eNB <b>10</b> is common to the uplink message #<b>1</b>-<b>3</b>, there is no need to prepare (define) an unlink message dedicated to UL scheduling request, so that the wireless resource can be efficiently used.

0114The first and the second embodiments assumes that the eNB <b>10</b> transmits the signature allocation request message #<b>2</b>-<b>1</b> to the UE <b>20</b> after the UE <b>20</b> transmits the uplink transmission request message #<b>1</b>-<b>1</b>. However, even when these messages #<b>1</b>-<b>1</b> and #<b>2</b>-<b>1</b> are transmitted in the reverse order, multiple allocation also occurs so that it is sufficient that either one of the signatures is made effective.

(2.1) First Modification

0115The above message also serving as UL scheduling request to the eNB <b>10</b> may be a message (Random Access Preamble) #<b>2</b>-<b>2</b> transmitted in step S<b>2</b><i>a </i>in <figref idref="DRAWINGS">FIG. 7</figref> as denoted in the example <figref idref="DRAWINGS">FIG. 10</figref>.

0116In this case, the UE <b>20</b> needs not transmit the message #<b>1</b>-<b>3</b> and can consequently halt the transmission of the message #<b>1</b>-<b>3</b> (step S<b>3</b>). Accordingly, unnecessary transmission of uplink messages can be avoided so that efficiently use of uplink wireless resource (band) can be ensured.

0117Since the eNB <b>10</b> cannot recognize (i.e., cannot manage) that which UE <b>20</b> uses which preamble unless receives the message #<b>1</b>-<b>3</b>, there is no need to release the preamble (no need to carry out step S<b>3</b>-<b>2</b> in <figref idref="DRAWINGS">FIG. 7</figref>). Consequently, it is possible to reduce the processing load of the preamble management on the eNB <b>10</b>.

(2.2) Second Embodiment

0118Further, alternative to transmitting the UL scheduling request to the eNB <b>10</b> during the non-contention based random access procedure, the UL scheduling request may be, as denoted in <figref idref="DRAWINGS">FIG. 11</figref>, transmitted along with the response (ACK/NACK signal) responsive to the message #<b>2</b>-<b>3</b> upon completion of the procedure (step S<b>5</b> in <figref idref="DRAWINGS">FIG. 11</figref>). Further alternatively, the request may be transmitted in the form of an independent uplink message after the transmission of the message #<b>2</b>-<b>3</b>.

(3) Third Embodiment

0119<figref idref="DRAWINGS">FIG. 12</figref> is a sequence diagram illustrating a random access procedure according to the third embodiment; <figref idref="DRAWINGS">FIG. 13</figref> is a flow diagram explaining the operation of eNB <b>10</b> during the random access procedure of the third embodiment; and <figref idref="DRAWINGS">FIG. 14</figref> is a flow diagram explaining the operation of UE <b>20</b> during the random access procedure of the third embodiment.

0120Differently from the first and the second embodiments, description of the third embodiment presumes that uplink data arrive in the UE <b>20</b> under a state where a dedicated signature is allocated to the UE <b>20</b>.

0121In other words, when downlink data which is destined for the UE <b>20</b> and which is transmitted from the upper apparatus arrives at the eNB <b>10</b> (i.e., the buffering unit <b>13</b> stores downlink data) (step A<b>21</b> in <figref idref="DRAWINGS">FIG. 13</figref>), the eNB <b>10</b> creates and stores a signature (dedicated signature) (step A<b>22</b> in <figref idref="DRAWINGS">FIG. 13</figref>) that is to be used for random access (UL synchronization request) by the UE <b>20</b>, the destination of the downlink data (step A<b>2</b> in <figref idref="DRAWINGS">FIG. 13</figref>), and then transmits the created signature by means of a signature allocation message #<b>2</b>-<b>1</b> (RA Preamble Assignment) to the destination UE <b>20</b> through the transmitting/receiving unit <b>12</b> (step A<b>11</b> in <figref idref="DRAWINGS">FIG. 12</figref> and step A<b>23</b> in <figref idref="DRAWINGS">FIG. 13</figref>).

0122Upon receipt of the signature allocation message #<b>2</b>-<b>1</b>, the UE <b>20</b> stores and manages the dedicated signature allocated by the received message in the signature managing unit <b>24</b> (step B<b>21</b> in <figref idref="DRAWINGS">FIG. 14</figref>).

0123After that, when UE <b>20</b> generates uplink data and the buffering unit <b>23</b> stores the uplink data (step B<b>22</b> in <figref idref="DRAWINGS">FIG. 14</figref>), the UE <b>20</b> (the signature managing unit <b>24</b>) does not generates a random signature (step S<b>12</b> in <figref idref="DRAWINGS">FIG. 12</figref> and step B<b>23</b> in <figref idref="DRAWINGS">FIG. 14</figref>) differently from the first and the second embodiments.

0124As the substitute, the UE <b>20</b> creates, in the access judging unit <b>25</b>, an UL synchronization request (Random Access Preamble) message #<b>2</b>-<b>2</b> containing the dedicated signature allocated by eNB <b>10</b> and transmits the created message to the eNB <b>10</b> through the transmitting/receiving unit <b>22</b> from the antenna <b>21</b>.

0125At that time, because of the generation of the uplink message, the UE <b>20</b> provides information (an identifier or a flag) indicating that “the message also serves as an UL scheduling request” to the message #<b>2</b>-<b>2</b> in the identifier providing unit <b>26</b> and transmits the message to the eNB <b>10</b> (step S<b>13</b> in <figref idref="DRAWINGS">FIG. 12</figref> and step B<b>24</b> in <figref idref="DRAWINGS">FIG. 14</figref>).

0126In other words, the UE <b>20</b> additionally transmits the UL scheduling request to the eNB <b>19</b> (sic, correctly 10) in the event of executing random access through the use of a signature for obtaining (establishing) the uplink synchronization when downlink data is generated.

0127Upon confirmation of the reception of the message #<b>2</b>-<b>2</b> (also serving as UL scheduling request) (yes route in step A<b>24</b> in <figref idref="DRAWINGS">FIG. 13</figref>), the eNB <b>10</b> causes the wireless resource managing unit <b>16</b> to control allocation of the UL resource corresponding to the UL scheduling request (step A<b>25</b> in <figref idref="DRAWINGS">FIG. 13</figref>) and creates the signature managing unit <b>15</b> to create a response message #<b>2</b>-<b>3</b> to the message #<b>2</b>-<b>2</b> and transmit the created message to the UE <b>20</b> (step S<b>14</b> in <figref idref="DRAWINGS">FIG. 12</figref>). Conversely, since an UL synchronization request message #<b>2</b>-<b>2</b> not containing the UL scheduling request (no route in step A<b>24</b> in <figref idref="DRAWINGS">FIG. 13</figref>) represents a case in which a normal uplink data communication is arriving, the eNB <b>10</b> transmits the message #<b>2</b>-<b>3</b> without allocation of an UL resource (step A<b>26</b> in <figref idref="DRAWINGS">FIG. 13</figref>).

0128As described above, according to the method of random access of the third embodiment, after downlink data destined for a UE <b>20</b> arrive at eNB <b>10</b> and responsively allocates a signature to the same UE <b>20</b>, the UE <b>20</b> does not generate a signature used for the contention based random access, but does continue the non-contention based random access using the signature allocated by the eNB <b>10</b>. Consequently, the two kinds of random access do not concurrently proceed.

0129Accordingly, the control plane of the random access can be simplified and signatures used for random access can be efficiently used. In addition, both the UE <b>20</b> and the eNB <b>10</b> do not have to always manage the two kinds of signature.

0130Further, since, during the non-contention based random access, information (UL scheduling request), which is transmitted to the eNB <b>10</b> during the contention based random access, is transmitted to the eNB <b>10</b>, the transmitting processing of the uplink data can be surely carried out along with the receiving processing of the downlink data.

0131Still further, the random access preamble message #<b>2</b>-<b>2</b> also serves as an UL scheduling request, delay until the start of transmitting uplink data can be reduced as compared with the following fourth embodiment (in which a confirmation response message to the random access response message #<b>2</b>-<b>3</b> also serves as the UL scheduling request).

(4) Fourth Embodiment

0132<figref idref="DRAWINGS">FIG. 15</figref> is a sequence diagram illustrating a random access procedure according to the fourth embodiment; <figref idref="DRAWINGS">FIG. 16</figref> is a flow diagram explaining the operation of eNB <b>10</b> during the random access procedure of the fourth embodiment; and <figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram explaining the operation of UE <b>20</b> during the random access procedure of the fourth embodiment.

0133Similarly to the third embodiment, the fourth embodiment presumes that the UE <b>20</b> generates uplink data under a state where a dedicated signature is previously allocated to the UE <b>20</b>.

0134In other words, when downlink data which is destined for the UE <b>20</b> and which is transmitted from the upper apparatus arrives at the eNB <b>10</b> (i.e., the buffering unit <b>13</b> stores downlink data) (step A<b>31</b> in <figref idref="DRAWINGS">FIG. 16</figref>), the eNB <b>10</b> creates and stores at the signature managing unit <b>15</b> a signature (dedicated signature) (step A<b>32</b> in <figref idref="DRAWINGS">FIG. 16</figref>) that is to be used for random access (UL synchronization request) by the UE <b>20</b>, the destination of the downlink data, and then transmits the created signature by means of a signature allocation message #<b>2</b>-<b>1</b> (RA Preamble Assignment) to the UE <b>20</b> through the transmitting/receiving unit <b>12</b> (step S<b>11</b> in <figref idref="DRAWINGS">FIG. 15</figref> and step A<b>33</b> in <figref idref="DRAWINGS">FIG. 16</figref>).

0135Upon receipt of the signature allocation message #<b>2</b>-<b>1</b>, the UE <b>20</b> stores and manages the dedicated signature allocated by the received message in the signature managing unit <b>24</b> (step B<b>31</b> in <figref idref="DRAWINGS">FIG. 17</figref>).

0136After that, UE <b>20</b> generates uplink data and the buffering unit <b>23</b> stores the uplink data (step B<b>32</b> in <figref idref="DRAWINGS">FIG. 17</figref>), the UE <b>20</b> (the signature managing unit <b>24</b>) does not generate a random signature (step S<b>12</b> in <figref idref="DRAWINGS">FIG. 15</figref> and step B<b>33</b> in <figref idref="DRAWINGS">FIG. 17</figref>) differently from the first and the second embodiments.

0137As the substitute, the UE <b>20</b> creates a message #<b>2</b>-<b>2</b> (Random Access Preamble) containing the dedicated signature allocated by eNB <b>10</b> in the access judging unit <b>25</b>, and transmits the message to the eNB <b>10</b> through the transmitting/receiving unit <b>22</b> from the antenna <b>21</b> (step S<b>13</b> in <figref idref="DRAWINGS">FIG. 15</figref> and step B<b>34</b> in <figref idref="DRAWINGS">FIG. 17</figref>).

0138Upon recognizing reception of the message #<b>2</b>-<b>2</b> (yes route in step A<b>34</b> in <figref idref="DRAWINGS">FIG. 16</figref>), the eNB <b>10</b> causes the wireless resource managing unit <b>16</b> to allocate the UL wireless resource (step A<b>35</b> in <figref idref="DRAWINGS">FIG. 16</figref>) and causes the signature managing unit <b>15</b> to create a response message #<b>2</b>-<b>3</b> to the message #<b>2</b>-<b>2</b> and transmit the created message to the UE <b>20</b> (step S<b>14</b> in FIG. <b>15</b>). Conversely, if the eNB <b>10</b> cannot recognize the reception of the message #<b>2</b>-<b>2</b> (also serving as the UL scheduling request), the eNB <b>10</b> terminates the process (no route in step A<b>34</b> in <figref idref="DRAWINGS">FIG. 16</figref>).

0139On the other hand, upon receipt of the response message #<b>2</b>-<b>3</b> from the eNB <b>10</b> (step B<b>34</b> in <figref idref="DRAWINGS">FIG. 17</figref>), the UE <b>20</b> creates a confirmation response (ACK/NACK) message #<b>3</b> to the response message #<b>2</b>-<b>3</b> in the access judging unit <b>25</b> and transmits the created message to the eNB <b>10</b>. At that time, the UE <b>20</b> provides information (an identifier or a flag) indicating that “the message #<b>3</b> also serves as an UL scheduling request” to the confirmation response message #<b>3</b> in the identifier providing unit <b>26</b> and transmits the message to the eNB <b>10</b> (step <b>35</b> in <figref idref="DRAWINGS">FIG. 17</figref>). The provided information may be transmitted by a dedicated uplink message alternatively to being transmitted concurrently with the confirmation response message #<b>3</b>.

0140In other words, when executing random access through the use of a signature for obtaining (establishing) the uplink synchronization, the UE <b>20</b> additionally transmits the UL scheduling request to the eNB <b>10</b> when the random access terminates.

0141As described above, according to the method of random access of the fourth embodiment, when uplink data is generated in a UE <b>20</b> after the eNB <b>10</b> generates downlink data destined for the UE <b>20</b> and responsively allocates a signature to the same UE <b>20</b>, the UE <b>20</b> does not create a signature used for the contention based random access but does continue the non-contention based random access using the signature allocated by the eNB <b>10</b>, which thereby brings the same effects and advantages as the third embodiment.

0142In addition, since the confirmation response message #<b>3</b> to the random access response message #<b>2</b>-<b>3</b> also serves as an UL scheduling request, at least transmission of downlink data can be normally started even if the eNB <b>10</b> cannot correctly receive or recognize the confirmation response message #<b>3</b> due to the propagation environment.

0143The uplink message also serving as an UL scheduling request may be, for example, one for reporting the CQI to the eNB <b>10</b>.

(5) Fifth Embodiment

0144<figref idref="DRAWINGS">FIG. 18</figref> is a sequence diagram explaining a random access procedure of the fifth embodiment. This embodiment is an example of transmitting the signature allocation message (RA preamble Assignment) #<b>2</b>-<b>1</b> after the transmission of Response message (Random Access Response) #<b>1</b>-<b>2</b> to the UE <b>20</b> from the eNB <b>10</b>.

0145In other words, the UE <b>20</b> generates uplink data, the UE <b>20</b> creates a random signature at the signature managing unit <b>24</b> and transmits a random access preamble message (uplink transmission request) #<b>1</b>-<b>1</b> containing the created random signature to the eNB <b>10</b> (step S<b>1</b><i>a</i>).

0146Upon receipt of the message #<b>1</b>-<b>1</b>, the eNB <b>10</b> replay with the response message (Random Access Response) #<b>1</b>-<b>2</b> to the received uplink transmission request message #<b>1</b>-<b>1</b> (step S<b>2</b>) along with a timing advanced as synchronization signal for uplink communication, an uplink grant for transmission permission, and others. If a number of UEs <b>20</b> concurrently transmit requests through the RACH, the eNB <b>10</b> returns the response message #<b>1</b>-<b>2</b> to the UEs <b>20</b>.

0147At this stage, when downlink data which is destined for the UE <b>20</b> and which is from the upper apparatus arrives at the eNB <b>10</b>, the eNB <b>10</b> creates a dedicated signature in the signature managing unit <b>15</b>, and transmits the signature to the UE <b>20</b> via the signature allocation message (RA Preamble Assignment) #<b>2</b>-<b>1</b> (step S<b>2</b><i>b</i>).

0148Upon receipt of the signature allocation message (RA Preamble Assignment) #<b>2</b>-<b>1</b>, multiple allocation occurs due to the presence both the random signature and the dedicated signature at the UE <b>20</b>. When detecting the multiple allocation, the UE <b>20</b> selects one signature and continues the execution of the random access corresponding to the selected signature (<figref idref="DRAWINGS">FIG. 18</figref> assumes the contention based random access is selected) in the same manner as the first and the second embodiments.

0149In this case, the uplink message #<b>1</b>-<b>3</b> that is to be transmitted in the later step S<b>3</b> can also serve as UL synchronization confirmation the same as the first embodiment. Alternatively, the uplink message #<b>1</b>-<b>3</b> can also serve as the UL scheduling request the same as the second embodiment. Further, the uplink message (Random Access Preamble) #<b>2</b>-<b>2</b> can also serve as the UL scheduling request, which may be transmitted by means of an ACK/NACK signal responsive to the response message #<b>2</b>-<b>3</b> or may be transmitted by means of a dedicated uplink message.

0150Then, the eNB <b>10</b> confirms the effective ID of the UE <b>20</b> by, for example, receiving the message #<b>1</b>-<b>3</b> and can release one of the signatures in the state of the multiple allocation.

0151Namely, from the first and the fifth embodiment, the signature allocation message (RA Preamble Assignment) #<b>2</b>-<b>1</b> may be transmitted at any timing as long as before the eNB <b>10</b> receives the message #<b>1</b>-<b>3</b>.

(6) Sixth Embodiment

0152<figref idref="DRAWINGS">FIG. 19</figref> is a sequence diagram explaining a random access procedure of the sixth embodiment. This embodiment is an example of transmitting the signature allocation message (RA preamble Assignment) #<b>2</b>-<b>1</b> after the transmission of a message (Scheduled Transmission) #<b>1</b>-<b>3</b> to the eNB <b>10</b> from the UE <b>20</b>.

0153Specifically, when the UE <b>20</b> generates uplink data, the UE <b>20</b> transmits the random access preamble message (uplink transmission request) #<b>1</b>-<b>1</b> containing the random signature to the eNB <b>10</b> (step S<b>1</b><i>a</i>), receives a response message #<b>1</b>-<b>2</b> to this message (step S<b>2</b>), and transmits the message #<b>1</b>-<b>3</b> (step S<b>3</b>).

0154Upon receipt of the message #<b>1</b>-<b>3</b>, the eNB <b>10</b> starts the detection of the effective ID (terminal ID) of the UE <b>20</b>. Successful detection of the effective ID makes it possible to recognize that the contention of signatures occurs between which UEs <b>20</b>. If a contention occurs, the eNB <b>10</b> transmits the contention resolution message (Contention Resolution) #<b>1</b>-<b>4</b> to the UEs <b>20</b> in question to solve the contention (step S<b>4</b>).

0155Here, presuming that the eNB <b>10</b> could not recognize the message #<b>1</b>-<b>3</b> due to the reason that during processing the message #<b>1</b>-<b>3</b>, downlink data destined for the UE <b>20</b> arrives at the eNB <b>10</b> from the upper apparatus (the buffering unit <b>13</b> stores downlink data) and therefore the receiving of the message #<b>1</b>-<b>3</b> could not be completed.

0156In this case, the eNB <b>10</b> causes the signature managing unit <b>15</b> to create and store a signature (dedicated signature: the second information) that is to be used for random access (UL synchronization request) by UE <b>20</b>, and transmits the dedicated signature via the signature allocation message (RA preamble Assignment) #<b>2</b>-<b>1</b> to the UE <b>20</b> through the transmitting/receiving unit <b>12</b> (step S<b>3</b><i>a</i>).

0157Upon completion of transmitting and receiving processing on these messages #<b>1</b>-<b>3</b> and #<b>2</b>-<b>1</b> the eNB <b>10</b> can recognize “which UE <b>20</b> uses which signature”, that is, can recognize “two signatures (i.e., Random Preamble and Dedicated Preamble) are issued to which UE <b>20</b>.

0158Here, when the UE <b>20</b> and another UE (hereinafter called the second UE) do not establish contention, the UE <b>20</b> can be judged to have multiple allocation, so that the eNB <b>10</b> (the signature managing unit <b>15</b>) immediately releases the dedicated signature allocated to the UE <b>20</b>, and normally transmits a Contention Resolution message #<b>1</b>-<b>4</b> (step S<b>4</b>). At this time, the uplink synchronization can correctly secured, so that the transmission of downlink data can be started.

0159Conversely, when the UE <b>20</b> and the second UE establish contention, there is a possibility of collision between messages #<b>1</b>-<b>3</b> that the UE <b>20</b> and the second UE transmit. At this stage, the UE <b>20</b> cannot be judged to have multiple allocation, and the dedicated signature allocated to the UE <b>20</b> cannot be immediately released. In the event of contention, the eNB <b>10</b> notifies the UE <b>20</b> of the contention through the Contention Resolution message #<b>1</b>-<b>4</b>. This case preferably maintains the dedicated signature until an UE <b>20</b> having multiple signatures is detected.

0160In the meantime, regardless of whether or not the UE <b>20</b> notifies the eNB <b>10</b> the terminal ID of the UE <b>20</b> itself to the eNB <b>10</b>, the UE <b>20</b> can recognize (detect) the presence of both the random signature (Random Preamble) created in the UE <b>20</b> itself and the dedicated signature allocated by the eNB <b>10</b>, that is, occurrence of two kinds of random access, when the transmission of the message #<b>1</b>-<b>3</b> and the signature allocation message #<b>2</b>-<b>1</b> is completed.

0161At that time, when the messages #<b>1</b>-<b>3</b> transmitted from the UE <b>20</b> and the second UE do not collide with each other, the UE <b>20</b> grasps that no contention is established with reference to the Contention Resolution message #<b>1</b>-<b>4</b> notified from the eNB <b>10</b>. Consequently, the UE <b>20</b>, for example, releases the dedicated preamble, and maintains UL synchronization in the contention based random access procedure because the UE <b>20</b> correctly receives UL timing information via the message #<b>1</b>-<b>2</b>.

0162Conversely, when the messages #<b>1</b>-<b>3</b> transmitted from the UE <b>20</b> and the second UE collide with each other, the UE <b>20</b> grasps that contention is established with reference to the Contention Resolution message #<b>1</b>-<b>4</b> notified from the eNB <b>10</b>. Consequently, the UE <b>20</b> releases the dedicated preamble and can concurrently perform both the UL synchronization request and the UL scheduling request in the contention based random access the same as the first embodiment. Alternatively, the UE <b>20</b> can perform both the UL synchronization request and the UL scheduling request in the non-contention based random access the same as the second through the fourth embodiments.

0163Further, as described in the first embodiment, both random access procedures can be concurrently proceed. In other words, upon detection that the contention is established, the non-contention based random access can also be carried out at the same time through the use of the dedicated signature notified in the message #<b>2</b>-<b>1</b>.

0164The sixth embodiment describes the case where the message #<b>2</b>-<b>1</b> is transmitted during the message #<b>1</b>-<b>3</b> is being processed. Needless to say, this embodiment results the same if the message #<b>2</b>-<b>1</b> is transmitted between the messages #<b>1</b>-<b>2</b> and #<b>1</b>-<b>3</b>.

0165The embodiments can selectively perform one among a number of kinds of random access.

0166In addition, resources such as signatures to be used for the random access can be efficiently used. In addition, the interference of the random access channel (RACH) can be inhibited.

0167As detailed above, since the embodiments can selectively carry out one among a number of random access procedures and can efficiently use resource such as signatures used for the random access procedures, the embodiments seem to be extremely useful for the technical field of the wireless communication.

0168All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a illustrating of the superiority and inferiority of the invention. Although the embodiments have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.