Communication terminal and method with prioritized control information

COMMUNICATION TERMINAL AND METHOD WITH PRIORITIZED CONTROL INFORMATION

The present invention relates to a communication terminal and a base station that communicate according to a predetermined procedure.

The present invention is an invention filed as PCT International Application No. PCT/JP2009/000370 on January 30, 2009, claiming priority to the invention filed in Japan as Patent Application No. 2008-023171 on February 1, 2008 Based on the invention filed in the United States on July 30, 2010 as 12/865,674 and patented as 8,396,081, all of which are incorporated by reference.

In E-UTRA/E-UTRAN, which is currently standardized, time multiplexing is employed with both an uplink (UL:Up Link) from a terminal to a base station and a downlink (DL:downlink) from a base station to a terminal. In the uplink, when the base station receives data from a plurality of terminals, time multiplexing is not performed efficiently if the reception timing of data transmitted by the plurality of terminals is shifted. Therefore, in the time multiplexing system, it is necessary to adjust the transmission timing of the terminals so that the base station can receive data transmitted from a plurality of terminals within a certain delay.

This is called uplink synchronization (uplink synchronization, timing adjustment, timing alignment, etc. are also used). An operation necessary for the terminal to acquire uplink synchronization is an RACH procedure (Random Access CHannel procedure). First, the outline of this RACH procedure will be described, and then, Message3 transmission based on the present invention will be described.

[Overview of RACH procedure]

In E-UTRA/E-UTRAN, this RACH procedure is used in various cases. The reason for using the RACH procedure is specifically call access (Initial access), handover complete message transmission, UL/DL data resuming (UL/DL data resuming), and reconnection (Radio link failure recovery).

Initial access is a case in which the terminal performs a call connection in an idle (RRC_IDLE) state. Since the terminal is in the IDLE state, uplink synchronization with the base station is not taken.

Handover complete transmission is a case in which the terminal performs handover and notifies that the terminal has moved to the base station of the repair (target). Since the target's base station has not been connected so far, synchronization is obtained here.

UL/DL data resuming is a case in which a terminal that has performed intermittent reception (DRX) starts transmitting and receiving UL or DL data. Since the uplink synchronization of the terminal is lost after a while, synchronization needs to be renewed.

Radio link failure recovery is a case in which a terminal reconnects to a newly found (or connected) cell after it cannot detect a connected cell. The situation is similar to initial access.

Also, there are two main types of RACH procedures. One is when the terminal selects the RACH preamble that is transmitted to the base station by itself (in the case of a non-dedicated RACH preamble), and the other is when the terminal uses the RACH preamble given by the base station (in the case of a dedicated RACH preamble) )am.

Each operation is shown in Figs. 1(a) and (b). As a big difference, in the case of a non-dedicated RACH preamble, since there is a possibility that a plurality of terminals simultaneously use the same RACH preamble, a message (Message4: Contention resolution) for checking the presence or absence of a collision is used, whereas a dedicated RACH preamble is used. In the case of the preamble, the RACH preamble to be used is allocated according to an assignment message (Message0: RA preamble assignment).

Also, Message1 and Message2 are the same for all cases, but Message3 and Message4 are transmitted differently depending on each case. In addition, only handover complete transmission and DL data resuming are possible to use the dedicated RACH preamble. This is because the operation of the base station to allocate the RACH preamble is limited to these two cases.

These two procedures are respectively shown in FIG. 2 . Also, for handover complete transmission and DL data resuming, there may be cases where a non-dedicated RACH preamble is used instead of a dedicated RACH preamble.

Another big difference between the non-dedicated RACH preamble and the dedicated RACH preamble is that in the case of the dedicated RACH preamble, the base station can identify the terminal at the time of receiving it. Thereby, it becomes unnecessary to check which terminal has transmitted the RACH preamble in subsequent messages.

In other words, in the case of the non-dedicated RACH preamble, in Message 3, in order to indicate which terminal has accessed, it is necessary to insert the terminal ID. For the ID of this terminal, when the terminal is active (RRC_CONNECTED), a C-RNTI (Controlling Radio Network Temporary Id) used in units of cells is used, and when the terminal performs initial access, the tracking area (of the terminal of IDLE) is used. S-TMSI (S-Temporary Mobile Subscriber Id entity) used in the mobile management unit) or IMSI (International Mobile Subscriber Identity), which is a terminal-specific ID (corresponding to a phone number), is used. In addition, in radio link failure recovery, the cell identifier (Cell ID) of the cell that was connected before the radio link failure occurred, the C-RNTI in the cell, etc. are used.

[Send Message3]

It is Message3 that the terminal can transmit data to the base station first, and information for it is allocated to Message2. However, it is known that the size of Message3 becomes about 72 bits when the terminal is at the edge of a cell.

Therefore, a case in which it is difficult to transmit all information at once is considered. In order to show how Message3 is configured, the header configurations of MAC (Medium Access Control), RLC (Radio Link Control), and PDCP (Packet Data Convergence Protocol) are shown in FIGS. 3, 4, and 5, respectively. Also, the configuration of the protocol is shown in FIG. 14 . Below is a brief description thereof.

(MAC)

3 Types of MAC subheaders are prepared, and the minimum subheader is 8 bits. Indicates which data is included using LCID (Logical Channel ID), indicates whether there is a MAC subheader after the MAC subheader in the extension area (E(Extension) field), ) represents the size of the data.

MAC control element (MAC control information: C-RNTI as uplink, Buffer status report (buffer status report, indicating the status of the terminal's buffer; hereafter referred to as BSR), CQI (Channel Quality Indicator, Channel Quality Indicator: Channel status of the terminal) )) is also shown in the LCID. In this case, since the size is determined, the L field is not required.

(RLC)

A 16-bit header is defined for RLC AM (acknowledge mode), and 16-bit (10-bit SN for long data) and 8-bit (5-bit SN for short data) are defined for RLC UM (unacknowledge mode).

(PDCP)

Different headers are defined in a signaling radio bearer (SRB) (a bearer for carrying an RRC message that is a control message) and a data radio bearer (a bearer for carrying data; hereinafter referred to as DRB). In the case of SRB, a header of 40 bits is required.

The data radio bearer is also called a user plane radio bearer.

In addition, Handover complete is considered as an RRC message, including message type (message type: indicating the type of message), transaction identifier (transaction id: indicating the response of which message), etc., and 8 bits are assumed. .

Non-Patent Document 1: TS25.321: "Medium Access Control (MAC) protocol specification"

From the above description, considering the transmission of the handover complete, it can be seen that when the terminal is allocated only 72 bits for transmission, it is necessary to divide the transmission into two as shown in Table 1. In addition, it is determined that BSR is transmitted after handover is performed. In UMTS (Universal Mobile Telecommunication System), MAC control information (MAC control element in LTE) always has a higher priority than SRB and DRB (refer to Non-Patent Document 1).

Therefore, it is assumed that this BSR is sent before Handover complete. In this case, transmission is divided into three times as shown in Table 2, and even transmission of the handover complete is delayed.

<tables num="1"><table><title>Table 1: In case of sending only handover complete</title><tgroup cols="3"><colspec colnum="1" align="justify" colname="col1" colwidth="3707" /><colspec colnum="2" align="justify" colname="col2" colwidth="3707" /><colspec colnum="3" align="justify" colname="col3" colwidth="3707" /><tbody><row><entry align="justify" colname="col1"></entry><entry align="justify" colname="col2"> 1st segment</entry><entry align="justify" colname="col3"> 2nd segment</entry></row><row><entry align="justify" colname="col1"> RRC+PDCP</entry><entry align="justify" colname="col2"> 24 bit</entry><entry align="justify" colname="col3"> 24 bit</entry></row><row><entry align="justify" colname="col1"> RLC</entry><entry align="justify" colname="col2"> 16 bit</entry><entry align="justify" colname="col3"> 16 bit</entry></row><row><entry align="justify" colname="col1"> MAC</entry><entry align="justify" colname="col2"> 8 bit (LCID for RRC)</entry><entry align="justify" colname="col3"> 8 bit (LCID for RRC)</entry></row><row><entry align="justify" colname="col1"> PHY(CRC)</entry><entry align="justify" colname="col2"> 24 bit</entry><entry align="justify" colname="col3"> 24 bit</entry></row><row><entry align="justify" colname="col1"> Total</entry><entry align="justify" colname="col2"> 72 bit</entry><entry align="justify" colname="col3"> 72 bit</entry></row></tbody></tgroup></table></tables>

<tables num="2"><table><title>Table 2: When BSR takes precedence over Handover complete</title><tgroup cols="4"><colspec colnum="1" align="justify" colname="col1" colwidth="2782" /><colspec colnum="2" align="justify" colname="col2" colwidth="2782" /><colspec colnum="3" align="justify" colname="col3" colwidth="2782" /><colspec colnum="4" align="justify" colname="col4" colwidth="2782" /><tbody><row><entry align="justify" colname="col1"></entry><entry align="justify" colname="col2"> 1st segment</entry><entry align="justify" colname="col3"> 2nd segment</entry><entry align="justify" colname="col4"> 3rd segment</entry></row><row><entry align="justify" colname="col1"> RRC+PDCP</entry><entry align="justify" colname="col2"> 0 bit</entry><entry align="justify" colname="col3"> 24 bit</entry><entry align="justify" colname="col4"> 24 bit</entry></row><row><entry align="justify" colname="col1"> RLC</entry><entry align="justify" colname="col2"> 0 bit</entry><entry align="justify" colname="col3"> 16 bit</entry><entry align="justify" colname="col4"> 16 bit</entry></row><row><entry align="justify" colname="col1"> MAC </entry><entry align="justify" colname="col2"> 48 bit (LBSR+LCID) + 24bit padding (LCID+ padding bits)</entry><entry align="justify" colname="col3"> 8 bit (LCID for RRC)</entry><entry align="justify" colname="col4"> 8 bit (LCID for RRC)</entry></row><row><entry align="justify" colname="col1"> PHY(CRC)</entry><entry align="justify" colname="col2"> 24 bit</entry><entry align="justify" colname="col3"> 24 bit</entry><entry align="justify" colname="col4"> 24 bit</entry></row><row><entry align="justify" colname="col1"> Total</entry><entry align="justify" colname="col2"> 72 bit</entry><entry align="justify" colname="col3"> 72 bit</entry><entry align="justify" colname="col4"> 72 bit</entry></row></tbody></tgroup></table></tables>

As described above, when the MAC control element (eg, BSR) is prioritized, it is considered that the transmission of the handover complete is delayed. This has the following disadvantages.

(path switching delay in the network)

The base station can reliably determine that the terminal has moved by receiving the handover complete. Therefore, switching in the network (switching a path from the original base station to the new base station) is performed at the timing when the handover complete is received. When path switching is delayed, data not transmitted from the original base station to the new base station is discarded.

15 shows the relationship between the network-side base station and the entity of the core network. The entity of the core network continues to transmit data to the previous base station (source eNB) until the new base station (Target eNB) receives the handover complete and switches the path to the entity of the core network.

This is not a problem when the previous base station transmits data to the new base station, but it is considered that packets cannot be transmitted in real-time services such as VoIP. In order to suppress this to the minimum, it is required to shorten the path switching delay.

(Downlink transmission start delay)

By receiving the handover complete, the base station can reliably determine that the terminal has moved, and can initiate downlink data transmission. Therefore, if the reception of the handover complete is delayed, the start of downlink data transmission is delayed when there is data transmitted from the original base station to the new base station.

Considering the above, it is not preferable to always give priority to the MAC control element. Therefore, it is necessary to control the priority of the MAC control element.

<p>The present invention has been made in view of the above conventional circumstances, and an object of the present invention is to provide a communication terminal and a base station capable of assigning a priority to MAC control information and freely controlling which information is transmitted.</p>

<p>A communication terminal of the present invention is a communication terminal that communicates with a base station according to a predetermined procedure, which determines the relationship between the priority of MAC control information, which is a priority allocated to MAC control information, and the priority allocated to DRB and SRB. and a priority control unit, and a transmission message generation unit that controls to transmit information having a higher priority first according to the relationship between the priorities determined by the priority control unit.</p><p>According to the above configuration, it is possible to freely control which information is transmitted according to the relationship between the priority of the MAC control information and the priority assigned to the DRB and the SRB. Accordingly, appropriate control according to the content or situation of the communication service is possible. For example, when it is necessary to speed up path switching in the case of VoIP, it is considered that the priority of SRB is higher than that of BSR. In addition, it is possible to increase the priority of the BSR over the SRB in order to quickly grasp the buffer state of the terminal without the need for fast pass switching in the reverse direction.</p><p>In addition, the communication terminal of the present invention may be provided with a receiver for receiving the priority of the MAC control information transmitted from the base station.</p><p>In addition, in the communication terminal of the present invention, the MAC control information includes C-RNTI, BSR, and CQI, and the transmission message generator has priority according to the priority of the DRB, SRB, C-RNTI, BSR, and CQI. High-level information is transmitted first.</p><p>According to the above configuration, for example, if the C-RNTI is set to priority 1 and BSR and CQI are set to priority 3, when the priority of the SRB is 2, only the C-RNTI can be given priority over the SRB. You can freely control whether or not to transmit .</p><p>In addition, the communication terminal of the present invention has a priority table unit for maintaining the priority information of the MAC control information, the receiving unit receives the boundary information indicating the priority boundary of the MAC control information, the priority The control unit determines the relationship between the priority of the MAC control information and the priority allocated to the DRB and the SRB by referring to the boundary information.</p><p>According to the above configuration, since boundary information of the priority of MAC control information can be set with a small number of bits, an increase in signaling overhead can be suppressed.</p><p>In addition, in the communication terminal of the present invention, the priority control unit designates the priority of the MAC control information according to the reason for using the RACH procedure.</p><p>According to the above configuration, by designating the priority of the MAC control information according to the reason for using the RACH procedure, it becomes possible to change the transmission operation for each RACH procedure.</p><p>In addition, in the communication terminal of the present invention, the receiving unit receives a threshold value regarding the size of a message from the base station, and the priority control unit refers to the threshold value and is assigned to the priority of the MAC control information and the DRB and SRB. To determine the relationship with priorities.</p><p>According to the above configuration, when the message set to be transmitted first is large, the MAC control information is transmitted first, thereby reducing overhead due to transmission of the large message.</p><p>In addition, in the communication terminal of the present invention, the receiving unit receives the MAC control information and information necessary for determining the priority of the SRB from the base station, and the priority control unit refers to the information and the SRB and the MAC control information to determine the priorities of</p><p>According to the above configuration, the priority can be determined without an instruction from the network. </p><p>In addition, in the communication terminal of the present invention, the MAC control information and the information necessary to determine the priority of the SRB are information indicating whether a service in which packet loss increases due to pass switching delay is being received, and the handover is known It includes information indicating whether the handover is a domestic handover and information indicating whether the handover is a handover between the base stations.</p><p>According to the above configuration, it is possible to determine the priority of the SRB and MAC control information without an instruction from the network based on whether or not VoIP is used and whether the handover is within or between base stations.</p><p>In addition, the terminal of the present invention arranges an extension area indicating whether the MAC subheader follows next at the beginning of the MAC subheader, and whether the MAC header exists when resources of only 72 bits of the MAC subheader are allocated. is expressed as the value of the extended area located at the beginning of the MAC header.</p><p>According to the above configuration, it is possible for the terminal to notify the base station of whether the MAC header exists without using a new bit.</p><p>In addition, the base station of the present invention is a base station communicating with a communication terminal according to a predetermined procedure, and assigns a priority to MAC control information and transmits the priority of the MAC control information to the communication terminal.</p><p>According to the above configuration, since the priority is assigned to the MAC control information, it is possible to freely control which information the communication terminal transmits.</p><p>In addition, the base station of the present invention determines the priority of the MAC control information in advance, and transmits only boundary information of MAC control information having high priority and MAC control information having low priority to the SRB.</p><p>According to the above configuration, the boundary of MAC control information can be set with a small number of bits, so that an increase in signaling overhead can be suppressed.</p><p>In addition, the base station of the present invention transmits the priority of the MAC control information according to the reason for using the RACH procedure to the communication terminal.</p><p>According to the above configuration, by designating the priority of the MAC control information according to the reason for using the RACH procedure, it becomes possible to change the operation of the terminal for each RACH procedure.</p><p>In addition, the base station of the present invention gives priority to the MAC control information when the size of a message to be transmitted is larger than a predetermined size.</p><p>According to the above configuration, when the message set to be transmitted first is large, the MAC control information is transmitted first, thereby reducing the overhead associated with the transmission of the large message.</p><p>In addition, the base station of the present invention arranges an extension area indicating whether or not the MAC subheader is to be followed at the beginning of the MAC subheader, and determines whether the MAC header exists when resources of only 72 bits of the MAC subheader are allocated. It is determined by the value of the extended area located at the beginning of the header.</p><p>According to the above configuration, it is possible for the base station to determine whether the MAC header exists without using a new bit.</p>

<p>According to the communication terminal of the present invention, by comparing the priority of the MAC control information with the priority allocated to the DRB and the SRB, it is possible to freely control which information is transmitted. Further, according to the base station of the present invention, since the priority of the MAC control information is transmitted to the communication terminal by assigning a priority to the MAC control information, the communication terminal can freely control which information to transmit.</p>

1 is a diagram illustrating operations of a non-dedicated RACH preamble and a dedicated RACH preamble. 2 is a diagram illustrating a procedure of handover complete transmission and DL data resuming. 3 is a diagram showing the configuration of a MAC header of Message3. 4 is a diagram illustrating a header configuration of RLC of Message3. 5 is a diagram showing the configuration of a PDCP header of Message3. 6 is a view showing the concept of Embodiment 2 of the present invention. 7 is a block diagram of a terminal according to Embodiment 2 of the present invention. 8 is a view showing a specific example of the procedure according to Example 2 of the present invention. 9 is a view showing the concept of Embodiment 3 of the present invention. 10 is a block diagram of a terminal according to Embodiment 3 of the present invention. 11 is a diagram for explaining changing the priority of the MAC control element itself for each reason of use of the RACH procedure in Embodiment 3 of the present invention. 12 is a view showing the concept of Embodiment 4 of the present invention. 13 is a block diagram of a terminal according to Embodiment 4 of the present invention. 14 is a diagram showing the configuration of a protocol of Message3. 15 is a diagram illustrating a relationship between a network-side base station and an entity of a core network. 16 is a diagram illustrating an outline of setting a priority for each MAC control element in Embodiment 1 of the present invention. 17 is a block diagram of a terminal according to Embodiment 1 of the present invention. 18 is a diagram illustrating an example of a priority table and boundary information of a MAC control element in Embodiment 2 of the present invention. 19 is a diagram illustrating an operation when the base station considers the speed of the terminal in the second embodiment of the present invention. 20 is a diagram illustrating an operation of temporarily changing a priority in Embodiment 2 of the present invention. 21 is a diagram illustrating a method of transmitting boundary information used when transmitting using semi-persistent scheduling to a terminal in the third embodiment of the present invention. 22 is a block diagram of a terminal according to Embodiment 5 of the present invention. 23 is a flowchart illustrating the essence of operation according to Embodiment 5 of the present invention. 24 is a diagram illustrating a flow when a terminal performs initial access (call connection) and radio link failure recovery (reconnection) in Embodiment 2 of the present invention. 25 is a diagram illustrating a configuration of a MAC subheader used in a conventional proposal. 26 is a diagram showing the configuration of a MAC subheader according to the conventional proposal 1. 27 is a diagram illustrating the configuration of a MAC subheader according to Embodiment 6 of the present invention. 28 is a diagram showing the outline of the operation of the terminal according to the sixth embodiment of the present invention. 29 is a diagram showing a configuration example of a MAC header according to Embodiment 6 of the present invention. 30 is a diagram illustrating an example of definition of LCID according to Embodiment 6 of the present invention. 31 is a diagram showing another configuration example of a MAC header according to Embodiment 6 of the present invention.

Hereinafter, an example in which the base station and the terminal determine the priority of data to be transmitted prior to the RACH procedure will be described. In addition, each of the following embodiments is equally applicable to both the case of the non-dedicated RACH preamble and the case of the dedicated RACH preamble shown in FIG. 1 .

(Example 1)

A signaling radio bearer (SRB: a bearer for carrying an RRC message, which is a control message), and a user plane radio bearer/data radio bearer (DRB: a bearer for carrying data) each have a priority. As the current SRB, a high priority SRB (SRB2) for sending a high-priority RRC message and a low priority SRB (SRB1) having a priority as a normal SRB exist for RRC_CONNECTED terminals to communicate. In addition, another SRB (SRB0) is defined to carry the RRC message until the terminal moves to RRC_CONNECTED due to initial access, radio link failure recovery, etc. As the DRB, it is added according to the service used by the terminal, and, for example, a DRB for VoIP, a DRB for web browsing, a DRB for sending and receiving email, and the like are set as the DRB.

Here, the priority is set for each bearer so that the base station can control which bearer the terminal should transmit. Basically, SRB has higher priority than DRB. In addition, among the DRBs, the more the bearer for a service that requires a delay is strict (time critical), the higher the priority. Therefore, in the above example, the following priorities are considered.

High priority SRB &gt; low priority SRB &gt; DRB for VoIP &gt; DRB for web browsing &gt; DRB for email

In this embodiment, priority is set for each MAC control element so as to be the same as SRB and DRB. The outline is shown in FIG. As shown in this figure, for example, when the value of priority ranges from 1 to 8, and 1 is the highest, the C-RNTI, which is considered to have the highest priority in the MAC control element, has priority 1 and the next priority. It is considered that BSR, CQI, etc., which are considered to be high, are set to priority 3 .

Here, when the priority of the high priority SRB is 2, only the C-RNTI has priority over the high priority SRB. By this operation, it is possible to freely control which information is transmitted to the terminal.

Specifically, when it is necessary for the terminal to perform path switching quickly using VoIP, it is considered that the priority of the high priority SRB is higher than that of the BSR. In addition, it is possible to increase the priority of the BSR over the high priority SRB when it is desired to quickly grasp the buffer state of the terminal without the need for fast path switching.

(block diagram)

17 is a block diagram of a terminal according to the present invention. The communication terminal shown in Fig. 17 includes a receiving unit 701, an SRB generating unit 705, a DRB generating unit 706, a priority control unit 1701, a transmission message generating unit 704, and a buffer unit 707. ), a MAC information generation unit 708 , and a transmission unit 709 . The main operations and roles of each part are as follows.

701 is a receiving unit, and receives a message from a base station. The receiving unit 701 receives the priority of each MAC control element and sends it to the priority control unit 1701 . In addition, the receiving unit 701 receives the message size transmitted by the terminal and sends it to the transmission message generating unit 704 . 705, as an SRB generating unit, creates a message to be transmitted using an SRB such as an RRC message or a NAS message. A 706 is a DRB generation unit, which creates user plane data.

Reference numeral 1701 denotes a priority control unit, and receives a priority for each MAC control element from the reception unit 701 . The priority control unit 1701 determines "C-RNTI &gt; SRB &gt; BSR &gt; CQI &gt; DRB" or "C-RNTI &gt; high priority SRB &gt; BSR &gt; low priority SRB &gt; CQI &gt; DRB" and determine the relationship between the priority of the MAC control element and the SRB. Then, the priority control unit 1701 uses the result to control the transmission message generation unit 704 to create a transmission message so that information having a higher priority is transmitted first.

A transmission message generation unit 704 creates a transmission message based on the priority information from the priority control unit 1701 and the transmission message size from the reception unit 701 . The transmission message generation unit 704 receives the MAC control element from the MAC information generation unit 708, which will be described later, and notifies the buffer unit 707 of the transmittable bearer and the amount thereof, and the SRB or DRB in the buffer unit 707. It also receives information to be transmitted.

707 is a buffer unit, which holds information from the SRB generation unit 705 and the DRB generation unit 706 and transmits it to the transmission message generation unit 704 according to the instruction of the transmission message generation unit 704 .

Reference numeral 708 denotes a MAC information generation unit, which generates a MAC control element and notifies the transmission message generation unit 704 . Specifically, the MAC information generation unit 708 gives the C-RNTI to the transmission message generation unit 704 when it is necessary to transmit the C-RNTI. In addition, when it is necessary to transmit the BSR, the MAC information generating unit 708 generates and transmits the BSR from the information in the buffer unit 707, or the like. Reference numeral 709 denotes a transmission unit, and serves to transmit the message created by the transmission message generation unit 704 to the base station.

As described above, according to this embodiment, since the priority can be freely set for each MAC control element, data to be transmitted to the base station with priority in Message3 of the RACH procedure can be appropriately controlled according to the content or situation of the communication service.

(Example 2)

Fig. 6 is a diagram showing the concept of the present embodiment, Fig. 7 is a block diagram of the terminal, and Fig. 8 is a specific example of the procedure of this operation.

In Example 1, priority can be freely set for each MAC control element. However, in the method of Embodiment 1, there is a problem in that the overhead of signaling for the base station to set the priority for the terminal increases. This embodiment solves the above problem by predetermining the priority in the MAC control element and setting only a boundary between a MAC control element having a high priority and a MAC control element having a low priority for the SRB. . The outline is shown in FIG.

As shown in Figure 6 (a), the MAC control element determines the priority in the MAC control element. It is considered that this is defined by a specification such as standardization, etc., and may be transmitted as report information or the like, or may be transmitted as an individual RRC message. In this embodiment, an example defined by a specification such as standardization will be described. And, what is set is a boundary between a MAC control element having a higher priority than an SRB and a MAC control element having a lower priority than the SRB. Specifically, any of boundary 1-4 in the example of Fig. 6(a) is indicated. An example of signaling at this time is FIG. 6(b). Incidentally, the procedure shown in Fig. 6(b) is executed before Message1 shown in Fig. 1(a).

Specifically, when boundary2 is specified, the following priorities are in order.

C-RNTI &gt; SRB &gt; BSR &gt; CQI &gt; DRB

In addition, although it is collectively used as the SRB in the above, it is also considered to set the priority of the MAC control element in comparison with the high priority SRB. In such a case, it becomes as follows.

C-RNTI &gt; high priority SRB &gt; BSR &gt; low priority SRB &gt; CQI &gt; DRB

(block diagram)

Fig. 7 shows a block diagram of a terminal according to the present embodiment. The terminal shown in FIG. 7 includes a priority control unit 703 and a priority table unit 702 in place of the priority control unit 1701 of the terminal shown in FIG. 17 . The main operation and role of each part will be described differently from the first embodiment.

In this embodiment, the receiving unit 701 serves to receive the boundary information described above from the base station and notify the priority control unit 703 in addition to the role described in the first embodiment.

The priority table unit 702 holds the priority information in the MAC control element shown in Fig. 6(a), and serves to notify the priority control unit 703 thereof.

The priority control unit 703 determines "C-RNTI &gt; SRB &gt; BSR &gt; CQI &gt; DRB" or "C- determine the relationship between the priority of the MAC control element and the SRB such as "RNTI &gt; high priority SRB &gt; BSR &gt; low priority SRB &gt; CQI &gt; DRB". Then, the priority control unit 703 uses the result to control the transmission message generation unit 704 to transmit information having a high priority first.

(detailed description)

The operation of the present invention will be described with reference to FIGS. 7 and 8 . 8 is a specific example of the procedure of handover transmission.

As shown in FIG. 8 , boundary information is first notified from the base station (source cell) to the terminal (UE) (ST8-1: RRC CONNECTION RECONFIGURATION message). This boundary information is received by the receiving unit 701 and given to the priority control unit 703 . The priority control unit 703 uses the boundary information received in ST8-1 and the MAC control unit 702 from two pieces of information, the table indicating the priority in the MAC control element described in FIG. 6(a), maintained in the priority table unit 702. Get information on the priority of a control element. The priority control unit 703 transmits this to the transmission message generation unit 704 .

Next, a response message for ST8-1 created by the transmission message generating unit 704 is transmitted from the transmitting unit 709 of the terminal to the base station (ST8-2: RRC CONNECTION RECONFIGURATION COMPLETE message).

Then, the base station notifies the terminal of the execution of the handover (ST8-3: Handover Command message). Accordingly, the terminal performs a handover. In addition, since this process is a general operation and is not directly related to this invention, description is abbreviate|omitted.

In addition, Handover Command and Handover Complete message are a generic name of a message in which the base station instructs the terminal to handover, and a message in which the terminal indicates the completion of the handover to the base station. Each COMPLETE message is used.

ST8-4: Random Access preamble and ST8-5: Random Access response implemented after ST8-3 are normal RACH procedures, and detailed descriptions are omitted here. After ST8-5, the transmission message generation unit 704 determines the message size in Message3 based on the resource allocation information received in ST8-5. This message size is sent from the receiving unit 701 to the sending message generating unit 704 .

Here, in the case of sending both handover complete and BSR, if both sides do not fit in one message, which one is given priority is decided by priority. That is, if BSR &gt; SRB, BSR is given priority, and if BSR &lt; SRB, handover complete is given priority. Therefore, depending on the priority determined by the priority control unit 703, whether the contents sent in ST8-6 and ST8-8 become Handover complete or BSR is changed.

Examples of MAC control element table and boundary information are shown in FIGS. 18(a) and 18(b), respectively. In this way, the priority of the MAC control element is shown in the table, and the priority of the RRC message (only high priority SRB, both low priority SRB, and low priority SRB alone) is notified by boundary information, so transmission is performed. It is possible to control what

Next, how the base station determines this boundary information will be described. As described above, the transmission delay of the Handover Complete message causes a delay in path switching on the network side. As described above, it is a real-time service such as VoIP in which data is not transmitted from the origin base station to the base station on the handover line that is greatly affected by the delay of this path switching.

For this reason, a process in which transmission of Handover Complete is given priority only to terminals performing VoIP is considered. In addition, the validity of terminal information exchanged between base stations as information for switching paths is also considered. During handover, terminal information is exchanged between base stations.

At this time, information such as the reception quality of the terminal and the buffer status of the terminal is also exchanged. When the mobile speed of the terminal increases that much and the reception quality of the terminal is sufficient for information exchanged between base stations, lowering the CQI priority is considered. do.

In addition, a service in which the buffer state of the terminal is liable to fluctuate and a service in which it is difficult to change are considered. For example, in a service such as VoIP, the buffer state does not change that much. On the other hand, when uploading, it is considered that the buffer state fluctuates greatly.

Therefore, it is considered to lower the priority of the BSR when only a service that is difficult to change is being performed and, conversely, to increase the priority of the BSR when a service that is easy to change is being performed. By this operation, the terminal can control the information to be transmitted.

In addition, although the present embodiment shows an example of setting only one boundary for the MAC control element, it is also possible to increase the boundary to be set. Specifically, a boundary for a high priority SRB (for example, boundary2 in FIG. 6(a)) and a boundary for a low priority SRB (for example, boundary3 in FIG. 6(a)) are set, and "C-RNTI &gt; High priority SRB &gt; BSR &gt; CQI &gt; low priority SRB &gt; DRB" is also considered.

In this embodiment, the priority of the MAC control element can be set only for the SRB. However, it is also possible to set the DRB with the highest priority. That is, processing such as "C-RNTI &gt; SRB &gt; BSR &gt; high priority DRB &gt; CQI &gt; other DRB" can be realized by having a plurality of boundary information.

In this embodiment, an example of handover complete transmission is shown, but it is applicable to other cases as well. As a specific example, UL data resuming increases. UL data resuming is an operation when data transmitted by the terminal occurs during DRX.

Specifically, it is considered to transmit a measurement result indicating the reception state of the terminal (a measurement report as an RRC message) or to send a service request for adding a new service (such as a service request as a NAS message). The measurement report indicating the measurement result is a message with high priority because it is necessary for the implementation of the handover.

Therefore, when the moving speed of the terminal is high, there is a problem that this message must be transmitted quickly. As described above, by considering the movement speed of the terminal, the base station can determine in the processing shown in the present embodiment whether to transmit the data generated at this time, or whether to give priority to BSR or CQI. The operation at that time is shown in FIG. 19 .

It is also possible to make the priority of the MAC control element the same as the order of the LCID. As described above, each MAC control element is represented by an LCID. For example, BSR is 11100, CQI is 11101, and so on. Here, by defining so that the order of the LCID is the order of priority, there is an advantage in that it is not necessary to specially prepare a priority table in the terminal.

In the present embodiment, as shown in FIG. 8, notification of the Handover Command and the Boundary information are different messages. However, it is also possible to notify and change the Boundary information using the Handover Command.

In this embodiment, the operation of setting the priority of the RRC message to be higher, such as when the terminal performs VoIP and prioritizes handover complete, has been shown. However, there is a problem that the situation is different during handover between cells in the same base station.

This is because switching of the base station does not occur, so there is no need to transmit the handover complete quickly. In order to realize this, the operation of temporarily changing the priority is considered.

Fig. 20 shows the operation at that time. Here, the major difference from Fig. 8 is that a temporary priority is allocated in ST20-1 corresponding to ST8-3. This temporary priority is applied only to the response to ST20-1: Handover Command transmitted by the base station, and is applied only to Handover Complete.

Although the present invention has been described focusing on Message 3 of the RACH procedure, this embodiment is applicable to all normal uplink transmissions.

As a typical example when used for both normal uplink transmission, a case in which the terminal performs initial access (call connection) and radio link failure recovery (reconnection) is considered. The flow is shown in FIG. 24 . When the terminal performs call connection and reconnection, the network side does not know exactly the reception status of the terminal. Therefore, information such as CQI is required.

However, on the other hand, the signal sent by the terminal from ST2406a contains information sent to the core network, and if it is not sent, the call connection is not finally terminated. On the other hand, ST2406b is mainly used only for acknowledgment.

Therefore, the quasi-boundary information in ST2404a and ST2404b enables an operation to give priority to the SRB (that is, RRC CONNECTION SETUP COMPLETE) at the time of initial access. Accordingly, it is possible to solve the problem that the delay of the call connection is increased by the transmission of the MAC control element.

(Example 3)

Fig. 9 shows a diagram showing the concept of the present embodiment, and Fig. 10 shows a block diagram of the terminal. In Example 2, a case in which the same priority setting is used for all cases using the RACH procedure is shown. However, since necessary information is slightly different depending on the reason for using the RACH procedure, it is considered to determine the priority for each reason for performing the RACH procedure. According to this embodiment, it is possible to more appropriately control transmission data according to the reason for using the RACH procedure. An example of priority determination for each reason for performing the RACH procedure is shown below.

(Transmission of Handover complete)

If the BSR is not changed that much, it is considered that what is notified from the original base station to the base station of the mobile line can be used. Therefore, it is considered to give priority to Handover complete (that is, SRB).

(Uplink transmission start delay)

BSR is needed to know how much information the terminal has. Therefore, it is considered that BSR is given priority over SRB.

(Downlink transmission start delay)

In order to perform downlink transmission, it is considered that CQI is necessary. Therefore, it is considered to give priority to CQI.

Fig. 9(b) shows an instruction operation of information for realizing this. By determining boundary information for each reason for using the RACH procedure in this way, it is possible to change the operation for each RACH procedure.

(block diagram)

Fig. 10 shows a block diagram of a terminal according to the present embodiment. The terminal shown in FIG. 10 includes a priority control unit 1001 and a transmission message generation unit 1002 in place of the priority control unit 703 and transmission message generation unit 704 of the terminal illustrated in FIG. 7 . Hereinafter, only the differences are demonstrated. The priority control unit 1001 may have different priority settings for each reason of the RACH procedure, and notifies the transmission message generation unit 1002 thereof. The transmission message generating unit 1002 generates a transmission message by using different priority settings for each reason of the RACH procedure.

In addition, although the example in which only boundary information is set for each reason of the RACH procedure is shown in this embodiment, it is also possible to change the priority of the MAC control element itself for each reason of use of the RACH procedure. In this case, as shown in FIG. 11, a priority table unit 1101 is provided instead of the priority table unit 702 shown in FIG. It is good to set the priority of

Specifically, the following examples are considered.

Handover complete: C-RNTI &gt; BSR &gt; CQI

UL data resuming: C-RNTI &gt; BSR &gt; CQI

DL data resuming: C-RNTI &gt; CQI &gt; BSR

In addition, the operation using different priorities due to the reason for using the RACH procedure shown in this embodiment can be applied even when dynamic scheduling and semi-persistent scheduling set different priorities even for the same bearer. In E-UTRA/E-UTRAN, there are dynamic scheduling in which data is allocated to a PDCCH (Physical Downlink Control Channel) every time, and semi-persistent scheduling in which the resource is continuously used in a certain period once allocated to the PDCCH. This semi-persistent scheduling is suitable for services in which data is regularly sent in the same size, such as VoIP. However, if information such as BSR and CQI is to be transmitted prior to VoIP data, it cannot enter the resource allocated by semi-persistent scheduling, so there is a problem that VoIP data cannot be transmitted at once. Therefore, by applying the priority for the MAC control element to the DRB, and furthermore, by changing the setting of the priority according to the scheduling method for the DRB, the solution of the above problem can be realized. Specifically, a method of transmitting boundary information used when transmitting using semi-persistent scheduling to a terminal is considered (FIG. 21). That is, when boundary1 is indicated, the terminal gives priority to VoIP data over BSR and CQI only during semi-persistent scheduling, and gives preference to BSR and CQI as usual in case of dynamic scheduling.

(Example 4)

Fig. 12 is a diagram showing the concept of the present embodiment, and Fig. 13 is a block diagram of the terminal. In Example 2, a means for allowing the SRB to take precedence over the MAC control element is provided. However, when the size of a message that is prioritized over the MAC control element is larger, it is considered that the MAC control element is transmitted first.

Therefore, in the present embodiment, only when a message that has priority over the MAC control element is smaller than a predetermined size, it takes precedence over the MAC control element. A threshold for that is sent together with boundary information as shown in Fig. 12(b).

(block diagram)

Fig. 13 shows a block diagram of a terminal according to the present embodiment. The terminal shown in FIG. 13 includes a priority control unit 1301 and a transmission message generation unit 1302 in place of the priority control unit 703 and transmission message generation unit 704 of the terminal illustrated in FIG. 7 . Hereinafter, only the differences are demonstrated. The priority control unit 1301 receives and processes a threshold used to determine whether to transmit the SRB or DRB having priority over MAC control priority, and sends it to the transmission message generation unit 1302 . The transmission message generation unit 1302 determines whether the size of the preferred SRB or DRB is less than a threshold, and creates a transmission message so that the SRB or DRB is transmitted with priority over the MAC control element only when it is less than the threshold.

(Example 5)

Fig. 22 is a block diagram of the terminal of the present embodiment, and Fig. 23 is a flowchart showing an outline of the operation. In Example 2, a method of determining the priorities of the MAC control element and the SRB by an instruction from the network has been shown. In this embodiment, the operation of determining the priority without an instruction from the network is shown.

(block diagram)

22 shows a block diagram of a terminal in this embodiment. The terminal shown in Fig. 22 has a receiving unit 2201, a priority control unit 2202, and a transmission message generating unit in place of the receiving unit 701, the priority control unit 703, and the transmission message generation unit 704 of the terminal shown in Fig. 7 . (2203) is provided. Hereinafter, only the differences are demonstrated.

Unlike the receiving unit 701, the receiving unit 2201 receives boundary information and does not notify the priority control unit 703, but transmits information necessary for determining the priority of the MAC control element and the SRB to the priority control unit 2202. . Here, the information necessary to determine the priority of the MAC control element and the SRB is information such as whether a service that increases packet loss due to path switching delay, such as VoIP, is being received, whether the handover is within the base station, or between the base stations. .

Unlike the priority control unit 703 , the priority control unit 2202 determines the priority of the SRB and the MAC control element by itself based on the information received from the reception unit 2201 . The priority is determined when the transmission message generation unit 2203 creates a transmission message.

The transmission message generation unit 2203 notifies the priority control unit 2202 of the contents of the message scheduled to be transmitted. Further, the transmission message generation unit 2203 checks the priority with the priority control unit 2202 each time a transmission message is created.

(Flowchart)

23 shows an operation of determining the priority of the SRB and the MAC Control element based on whether VoIP is used when transmitting the handover complete and whether the handover is between base stations.

In ST2301, transmission of the handover complete from the transmission message generation unit 2203 of the terminal to the base station is started. Then, the transmission message generation unit 2203 checks the priority with the priority control unit 2202 .

The priority control unit 2202 determines whether or not VoIP is used in ST2302. If not in use, proceed to ST2304, and if in use, proceed to ST2303. In ST2303, the priority control unit 2202 determines whether this handover is inter-base station handover or intra-base station handover. In ST2303, the process proceeds to ST2304 in case of intra-base station handover, and proceeds to ST2305 in case of inter-base station handover.

In ST2304, the priority control unit 2202 determines that the path switching delay caused by the Handover Complete delay is not a problem, and that the MAC Control element has priority. Conversely, in ST2305, since the delay of the handover complete becomes a problem, it is decided to give priority to the handover complete. These results are notified to the transmission message generation unit 2203, and the transmission message generation unit 2203 generates a transmission message based on the results.

In addition, although the present embodiment shows that the terminal determines the priority of the MAC control element of the SRB based on whether VoIP is performed or handover between base stations, other conditions may be used. Specifically, a process such as giving priority to CQI when the mobile terminal's moving speed is fast and not giving priority to it is also considered. In addition, it is considered that the BSR is given priority when the fluctuation of the buffer state in the terminal is severe, and the BSR is not given priority when the fluctuation is not severe.

In the present embodiment, one criterion for judging whether or not VoIP is performed may be simply determined based on whether there is a service that has not been transmitted between the base stations. The DRB using the UM of the RLC is assumed to be not transmitted. Therefore, whether or not there is a DRB using the UM of the RLC can be used as a criterion for determination.

In addition, it can even be used as a criterion for determining whether the priority of the DRB using the RLC UM is higher than that of the DRB. Thereby, it is possible to avoid being forced to the DRB of the RLC UM having a lower priority, and the priority of the SRB being determined.

(Example 6)

Fig. 27 shows the configuration of the MAC subheader in the present embodiment, and Fig. 28 shows a flowchart showing the outline of the operation of the terminal. In this embodiment, when the terminal selects the RACH preamble to be transmitted to the base station by itself (in the case of the non-dedicated RACH preamble), how the base station distinguishes the content is shown.

When the terminal selects the RACH preamble to be transmitted to the base station by itself, the base station receives the RACH preamble (Message 1 shown in Fig. 1(a)) whether the terminal performs initial access, transmits handover complete, or otherwise You can't know just by doing Therefore, the base station knows what the content of Message3 shown in Fig. 1A is at the time when Message3 is received. At this point, there is one challenge. This is because whether or not the MAC header is used for Message3 differs depending on conditions. Specifically, when a resource for only sending 72 bits of information is allocated to the terminal, the MAC header is not included in the case of call connection and reconnection, and the RRC message is included directly, and other handover complete transmission, The MAC header is included in UL/DL data transmission/reception resume. In addition, when a resource for transmitting more than 72 bits of information, for example, 144 bits of information is allocated, the MAC header is included even in the case of call connection and reconnection. Therefore, when only 72 bits are allocated to the terminal, the base station needs to determine whether the MAC header is included.

In order to solve this problem, two proposals are made in the non-patent literature (R2-080162: Message 3 encoding).

(Priority proposal 1)

The first proposal is the current MAC sub-header described in the non-patent literature (TS36.321 V8.0.0: "Evolved Universal Terrestrial Radio Access (E-UTRA): Medium Access Control (MAC) protocol specification"). ) configuration (refer to Fig. 25(a)), and the leading LCID (Logical Channel IDentifier) field (LCID field) is used. The LCID field is a place to enter an LCID corresponding to the data to be carried or an LCID corresponding to a MAC control element, whereby the receiving side can identify what data is received.

The specific method described in this document uses the first 2 bits of the 5-bit LCID to indicate whether or not there is a MAC header. For example, when the value of the first 2 bits is "11", the MAC header is In the case of "00", "01", and "10", the operation is treated as having no MAC header. In the case of RRC messages in the case of call connection and reconnection, that is, RRC CONNECTION REQUEST and RRC CONNECTION RE-ESTABLISHMENT REQUEST, the first 2 bits are considered to be used for the message type indicating the RRC message. Therefore, in the case of "00", "01", and "10", it is identified whether the message received through RRC is RRC CONNECTION REQUEST or RRC CONNECTION RE-ESTABLISHMENT REQUEST. For example, "00" is an RRC CONNECTION REQUEST, "01" is an RRC CONNECTION RE-ESTABLISHMENT REQUEST, and the like.

The drawback in this case is that there is a limit to the area that can be represented by an LCID. When the terminal selects the RACH preamble to be transmitted to the base station by itself, it is necessary to notify the base station of the C-RNTI, and the information must be included. Therefore, it is necessary to reserve 8 LCIDs out of 32 for the MAC control element including the C-RNTI. However, in reality, since even eight MAC control elements including C-RNTI are considered undefined, the LCID is reserved unnecessarily.

Here, other areas in the MAC subheader will also be described. An extension field (E (Extension) field) indicates whether or not the MAC subheader is further followed. If "0", data or a MAC control element is inserted next, and if "1", it indicates that the MAC subheader is continued. Fig. 26 shows a configuration example of a case where a plurality of MAC subheads are connected. Here, FIG. 26(a) is an example of configuring the MAC header only with the MAC subheader without the length field (L(Length) field) shown in FIG. 25 . The length field indicates the size of data to be sent, so that the receiving end can know where the next data or MAC control element starts. In addition, since the length of the MAC control element is fixed, there is no need for a length field, and the last data does not need to be entered because there is no next data. In addition, there are two types of length regions, those of 7 bits (Fig. 26(b)) and those of 15 bits (Fig. 26(c)). Here, which one is used is indicated by the format field F (Format) field. In addition, the reserved bit (R (Reserved) bit) is defined as reserved for later expansion.

(Priority proposal 2)

The second proposal is to use a different MAC header configuration (see Fig. 25(b)). In this operation, 1 bit of the first reserved bit is used to indicate whether or not there is a MAC header. That is, if the value is "0", the MAC header is present, and if the value is "1", the processing is performed as no MAC header. In RRC, since the first bit is always set to "1", only "10" and "11" can be used to identify the message type, "10" is RRC CONNECTION REQUEST, "11" is RRC CONNECTION RE-ESTABLISHMENT REQUEST will have the same form as

The problem in this case is that since all message types are used, a new RRC message cannot be defined. Therefore, it is desirable to secure an area usable for the message type so that the range that can be defined as the LCID is not used unnecessarily and the RRC message can be newly defined.

(this example)

As shown in Fig. 27, a feature of the MAC header configuration in this embodiment is that the extended area is at the beginning, and it is possible to determine whether or not there is a MAC header based on the value. This takes advantage of the feature that it is less necessary to use a plurality of MAC subheaders when only 72 bits are allocated for transmission, and when there is a MAC header, the extension area is always set to "0" and only one MAC subheader is used. is realized by Therefore, when the extension area becomes "0", the receiving side processes it as having a MAC header, and when it becomes "1", the receiving side processes it as an RRC message as an RRC message as there is no MAC header. In RRC, the message is identified using the first 2 bits. As a specific example, "10" has the same form as RRC CONNECTION REQUEST, and "11" has the same form as RRC CONNECTION RE-ESTABLISHMENT REQUEST.

In this method, the second bit of the MAC header is not used as a MAC, but is a reserved bit. Therefore, it is possible to use the reserved bit when performing extension in the MAC afterwards. Also, conversely, it is possible to use the bit even when it is necessary to add an RRC message. Specifically, it is determined that there is no MAC header when the value is "00" by looking at the extended area corresponding to the first 2 bits of the MAC header and the reserved bits, rather than looking at whether there is a MAC header only in the extended area. Thereby, it is possible to use three of "01", "10" and "11" to represent the RRC message. In this way, by using the extension area for identification of the presence or absence of a MAC header, this method responds to MAC extension or addition of an RRC message.

Hereinafter, the operation of the terminal according to the present embodiment will be described with reference to FIG. 28 .

In ST2801, the terminal checks the allocated size with a Random Access Response. Here, if more than 72 bits is allocated, the process proceeds to ST2803. If 72 bits are allocated, proceed to ST2804. In ST2804, the terminal determines whether a call connection or reconnection is performed or not. That is, the terminal determines whether or not to use the MAC header. Here, when the MAC header is used, the process proceeds to ST2805, and when not used, the process proceeds to ST2806. In case of proceeding to ST2805, if the terminal selects the RACH preamble by itself (ie, non-dedicated RACH preamble), proceeds to ST2806, and if the RACH preamble is used by the base station, proceeds to ST2803.

In ST2803, the terminal creates transmission data using the MAC header as usual. On the other hand, in ST2806, the terminal creates transmission data so that the first extended area of the MAC header becomes "0". 29(c), (d), (e), and (f) show examples of the MAC header configuration at this time. In addition, an example of the definition of LCID is shown in FIG.

29(c) shows a case in which only C-RNTI is transmitted. Here, 16 bits among 40 bits are used as C-RNTI, and the remaining 24 bits are used as padding. Therefore, the LCID (11000 in Fig. 30) indicating that the C-RNTI and padding are included is included here.

In Fig. 29(d), the C-RNTI and the BSR are transmitted, and the LCID (11001 in Fig. 30) indicating that the C-RNTI and the BSR are included is included here. This is used when BSR has priority over handover complete.

In FIG. 29(e), C-RNTI and DCCH (Dedicated Control Channel) are transmitted. Here, the DCCH is a name as a logical channel of the above-described SRB, and is divided into a plurality of DCCHs just as it is divided into a high priority SRB and a low priority SRB. As the definition of the LCID, it is also possible to define only that C-RNTI and high priority SRB are transmitted later, and conversely, it is also possible to define only that C-RNTI and low priority SRB are transmitted later. It is free to define 30 shows an example in which both are defined. Then, the LCID is set according to the actually transmitted DCCH (11010 or 11011 in FIG. 30).

In Fig. 29(f), C-RNTI and CQI are transmitted. Therefore, the LCID (11100 in Fig. 30) indicating that the C-RNTI and the CQI are included is included here.

In ST2807, the terminal transmits the message without the MAC header. Examples of transmission data at that time are shown in Figs. 29(a) and 29(b) as at the time of call connection and at the time of reconnection, respectively. In addition, with respect to the location of information other than the message type, another arrangement may be used.

By the operation of the present embodiment, it is possible to reserve an area usable for the message type so as not to uselessly use a range that can be defined as an LCID, and to define a new RRC message.

In addition, although the above description shows an example in which the LCID is defined to combine the C-RNTI and other information, other methods are also considered. When the terminal selects the RACH preamble by itself, the base station can predict that the terminal inserts the C-RNTI in Message3. Therefore, when the terminal selects the RACH preamble by itself, it is not necessary to define the LCID so as to combine the C-RNTI with other information if it is determined that the C-RNTI is always inserted after the MAC header. Specifically, the example is shown in FIG. Figure 31 (a) is a case in which only C-RNTI is included and the rest is padding. In this case, the terminal includes the LCID indicating padding as the LCID. Since it is known that the base station always puts the C-RNTI after the MAC header when the terminal selects the RACH preamble by itself, it is possible to interpret the C-RNTI as follows after the MAC header, and then padding. Although other cases are shown in Figs. 31(b), (c) and (d), the operation is the same, and it is possible to interpret that the base station has a C-RNTI, and thereafter, information indicated by LCID is added.

In addition, although the example in which the C-RNTI is inserted immediately after the MAC header is shown in the above, it is also possible to set it in other places.

This application is based on Japanese Patent Application No. 2008-023171 filed on February 1, 2008, the contents of which are incorporated herein by reference.

As mentioned above, various embodiments of the present invention have been described, but the present invention is not limited to the matters shown in the above embodiments, and modifications and applications by those skilled in the art based on the description of the specification and well-known techniques are also intended for the present invention. , are included in the scope for which protection is sought.

The present invention can be used as a communication terminal, a base station, and the like, which can freely control which information is transmitted by assigning a priority to MAC control information.

701,2201 Receiver 702,1101 Priority table part 703,1001,1301,1701,2202 Priority control unit 704,1002,1302,2203 Send message generator 705 SRB generator 706 DRB generator 707 buffer 708 MAC information generator 709 transmitter