Method for signaling back-off information in random access

Information

  • Patent Grant
  • RE49739
  • Patent Number
    RE49,739
  • Date Filed
    Friday, March 26, 2021
    3 years ago
  • Date Issued
    Tuesday, November 28, 2023
    6 months ago
Abstract
A method for performing random access in a wireless communication system is provided. The method includes transmitting a preamble for random access in uplink, receiving a random access response message including back-off information as a response to the preamble, and performing back-off using the back-off information when the random access has failed.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates to a wireless communication system, and more particularly, to a method for performing random access in a wireless communication system.


2. Discussion of the Related Art


The E-UMTS system is an evolved version of the conventional WCDMA UMTS system and basic standardization thereof is in progress under the 3rd Generation Partnership Project (3GPP). The E-UMTS is also referred to as a Long Term Evolution (LTE) system. For details of the technical specifications of the UMTS and E-UMTS, refer to Release 7 and Release 8 of “3rd Generation Partnership Project; Technical Specification Group Radio Access Network”.


The E-UMTS mainly includes a User Equipment (UE), a base station (or eNB or eNode B), and an Access Gateway (AG) which is located at an end of a network (E-UTRAN) and which is connected to an external network. Generally, an eNB can simultaneously transmit multiple data streams for a broadcast service, a multicast service and/or a unicast service. The AG can be divided into a part that handles processing of user traffic and a part that handles control traffic. Here, the AG part for processing new user traffic and the AG part for processing control traffic can communicate with each other using a new interface. One or more cells may exist for one eNB. An interface for transmitting user traffic or control traffic can be used between eNBs. A Core Network (CN) may include the AG and a network node or the like for user registration of the UE. An interface for discriminating between the E-UTRAN and the CN can be used. The AG manages mobility of a UE on a Tracking Area (TA) basis. One TA includes a plurality of cells. When the UE has moved from a specific TA to another TA, the UE notifies the AG that the TA where the UE is located has been changed.



FIG. 1 illustrates a network structure of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) system which is a mobile communication system to which the embodiment of the present invention is applied. The E-UTRAN system is an evolved version of the conventional UTRAN system. The E-UTRAN includes a base station that will also be referred to as “eNode B” or “eNB”. The eNBs are connected through an X2 interface. Each eNB is connected to the User Equipment (UE) through a radio interface and is connected to an Evolved Packet Core (EPC) through a S1 interface.



FIGS. 2 and 3 illustrate the configurations of a control plane and a user plane of a radio interface protocol between a UE and a UMTS Terrestrial Radio Access Network (UTRAN) based on the 3GPP radio access network standard. The radio interface protocol is divided horizontally into a physical layer, a data link layer and a network layer, and vertically into a user plane for data transmission and a control plane for signaling. The protocol layers of FIGS. 2 and 3 can be divided into an L1 layer (first layer), an L2 layer (second layer) and an L3 layer (third layer) based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems.


The control plane is a passage through which control messages that a UE and a network use in order to manage calls are transmitted. The user plane is a passage through which data (e.g., voice data or Internet packet data) generated at an application layer is transmitted. The following is a detailed description of the layers of the control and user planes in a radio interface protocol.


The physical layer, which is the first layer, provides an information transfer service to an upper layer using a physical channel. The physical layer is connected to a Media Access Control (MAC) layer, located above the physical layer, through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. Data transfer between different physical layers, specifically between the respective physical layers of transmitting and receiving sides, is performed through the physical channel. The physical channel is modulated according to the Orthogonal Frequency Division Multiplexing (OFDM) method, using time and frequencies as radio resources.


The MAC layer of the second layer provides a service to a Radio Link Control (RLC) layer, located above the MAC layer, through a logical channel. The RLC layer of the second layer supports data transmission with reliability. The functions of the RLC layer may also be implemented through internal functional blocks of the MAC layer. In this case, the RLC layer need not be existed. A PDCP layer of the second layer performs a header compression function to reduce unnecessary control information in order to efficiently transmit IP packets such as IPv4 or IPv6 packets in a radio interface with a relatively narrow bandwidth.


A Radio Resource Control (RRC) layer located at the lowermost of the third layer is defined only in the control plane and is responsible for control of logical, transport, and physical channels in association with configuration, re-configuration and release of Radio Bearers (RBs). The RB is a service that the second layer provides for data communication between the UE and the UTRAN. To accomplish this, the RRC layer of the UE and the RRC layer of the network exchange RRC messages. The UE is in RRC connected mode if RRC connection has been established between the RRC layer of the radio network and the RRC layer of the UE. Otherwise, the UE is in RRC idle mode.


A Non-Access Stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.


One cell of the eNB is set to use a bandwidth such as 1.25, 2.5, 5, 10 or 20 MHz to provide a downlink or uplink transmission service to UEs. Here, different cells may be set to use different bandwidths.


Downlink transport channels for transmission of data from the network to the UE include a Broadcast Channel (BCH) for transmission of system information, a Paging Channel (PCH) for transmission of paging messages and a downlink Shared Channel (SCH) for transmission of user traffic or control messages. User traffic or control messages of a downlink multicast or broadcast service may be transmitted through a downlink SCH and may also be transmitted through a downlink multicast channel (MCH). Uplink transport channels for transmission of data from the UE to the network include a Random Access Channel (RACH) for transmission of initial control messages and an uplink SCH for transmission of user traffic or control messages.


Logical channels, which are located above the transport channels and are mapped to the transport channels, include a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Multicast Control Channel (MCCH) and a Multicast Traffic Channel (MTCH).



FIG. 4 is a view showing an example of a physical channel structure used in an E-UMTS system. A physical channel includes several subframes on a time axis and several subcarriers on a frequency axis. Here, one subframe includes a plurality of symbols on the time axis. One subframe includes a plurality of resource blocks and one resource block includes a plurality of symbols and a plurality of subcarriers. In addition, each subframe may use certain subcarriers of certain symbols (e.g., a first symbol) of a subframe for a physical downlink control channel (PDCCH), that is, an L1/L2 control channel. In FIG. 4, an L1/L2 control information transmission area (PDCCH) and a data area (PDSCH) are shown. In one embodiment, a radio frame of 10 ms is used and one radio frame includes 10 subframes. In addition, one subframe includes two consecutive slots. The length of one slot may be 0.5 ms. In addition, one subframe includes a plurality of OFDM symbols and a portion (e.g., a first symbol) of the plurality of OFDM symbols may be used for transmitting the L1/L2 control information. A transmission time interval (TTI) which is a unit time for transmitting data is 1 ms.


A base station and a UE mostly transmit/receive data via a PDSCH, which is a physical channel, using a DL-SCH which is a transmission channel, except a certain control signal or certain service data. Information indicating to which UE (one or a plurality of UEs) PDSCH data is transmitted and how the UE receive and decode PDSCH data is transmitted in a state of being included in the PDCCH.


For example, in one embodiment, a certain PDCCH is CRC-masked with a radio network temporary identity (RNTI) “A” and information about data is transmitted using a radio resource “B” (e.g., a frequency location) and transmission format information “C” (e.g., a transmission block size, modulation, coding information or the like) via a certain subframe. Then, one or more UEs located in a cell monitor the PDCCH using its RNTI information. And, a specific UE with RNTI “A” reads the PDCCH and then receive the PDSCH indicated by B and C in the PDCCH information.



FIG. 5 is a process flow diagram illustrating a contention-based random access procedure.


The random access procedure is used to transmit short-length data in uplink. For example, the random access procedure is performed upon initial access in an RRC idle mode, upon initial access after radio link failure, upon handover requiring the random access procedure, and upon the occurrence of uplink/downlink data requiring the random access procedure during an RRC connected mode. Some RRC messages such as an RRC connection request message, a cell update message, and an URA update message are transmitted using a random access procedure. Logical channels such as a Common Control Channel (CCCH), a Dedicated Control Channel (DCCH), or a Dedicated Traffic Channel (DTCH) can be mapped to a transport channel (RACH). The transport channel (RACH) can be mapped to a physical channel (e.g., Physical Random Access Channel (PRACH)). When a UE MAC layer instructs a UE physical layer to transmit a PRACH, the UE physical layer first selects an access slot and a signature and transmits a PRACH preamble in uplink. The random access procedure is divided into a contention-based procedure and a non-contention-based procedure.


As shown in FIG. 5, a UE receives and stores information regarding random access from an eNB through system information. Thereafter, when random access is needed, the UE transmits a random access preamble (message 1) to the eNB (S510). After transmitting the random access preamble (message 1), the UE monitors a PDCCH during a predetermined period of time in order to receive a random access response message. After receiving the random access preamble from the UE, the eNB transmits a random access response (message 2) to the UE (S520). Specifically, downlink scheduling information for the random access response message can be CRC-masked with a Random Access-RNTI and can be transmitted through an L1/L2 control channel (PDCCH). Upon receiving the downlink scheduling signal masked with the RA-RNTI, the UE can receive and decode a random access response message from a PDSCH. Thereafter, the UE checks whether or not a random access response corresponding to the UE is present in the received random access response message. Whether or not a random access response corresponding to the UE is present can be determined based on whether or not a RAID for the preamble that the UE has transmitted is present. After receiving response information, the UE transmits an uplink message (Message 3) through an uplink SCH according to information regarding radio resources included in the response information (S530). After receiving the uplink message from the UE, the eNB transmits a contention resolution message (Message 4) (S540).


When random access has failed, the UE performs back-off. Here, the term “back-off” refers to delaying, by a UE, an access attempt by an arbitrary or predetermined time. If the UE makes an access attempt immediately after random access has failed, the access attempt is likely to fail again for the same or similar reason. Accordingly, when random access has failed, the UE delays an access attempt by a predetermined time to prevent waste of radio resources due to failure of the access attempt and to increase the probability that the random access is successful.



FIG. 6 illustrates a method for signaling back-off information according to a conventional technology.


As shown in FIG. 6, an eNB transmits a back-off parameter to all UEs in the cell through system information (S610). Thereafter, the UE performs its own back-off setting using a back-off parameter obtained from the system information. When random access is needed, the UE transmits a preamble for random access to the eNB (S620). The preamble may include a Random Access IDentity (RAID). Thereafter, when a random access procedure has failed for some reason, the UE performs back-off (S630). Thereafter, the UE retransmits a preamble for random access to the eNB (S640).


In the conventional technology, the UE should receive and store a back-off parameter through system information before making random access since the back-off parameter was broadcast through system information. Since a back-off parameter should be periodically broadcast through system information, a downlink overhead is always broadcast even when back-off is not performed since random access is successful. In addition, it may also be necessary to apply a different back-off parameter due to a cause such as load. However, since a back-off parameter is broadcast through system information, each UE in the cell cannot perform different back-off.


SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a method for performing random access in a wireless communication system that substantially obviates one or more problems due to limitations and disadvantages of the related art.


An object of the present invention is to provide a method for reducing overhead and increasing the efficiency of radio resources in association with a random access procedure performed in a wireless communication system.


Another object of the present invention is to provide a method for efficiently signaling back-off information in random access.


Another object of the present invention is to provide a message format used for signaling back-off information in random access.


Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.


To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a method for performing random access in a wireless communication system includes transmitting a preamble for random access in uplink; receiving a random access response message including back-off information as a response to the preamble; and performing back-off using the back-off information when the random access has failed. The method may further include obtaining the back-off information from the random access response message. The method may further include retransmitting a preamble for random access in uplink.


In another aspect of the present invention, a method for performing random access in a wireless communication system includes receiving a preamble for random access; and transmitting a random access response message including back-off information as a response to the preamble in downlink.


The embodiments of the present invention have the following advantages.


First, it is possible to reduce overhead and increase the efficiency of radio resources in association with a random access procedure performed in a wireless communication system.


Second, it is possible to signal back-off information only when random access is needed, thereby reducing overhead.


Third, it is possible to apply different back-off information to each UE in random access.


Fourth, it is possible to provide a message format for signaling back-off information in random access.


It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:



FIG. 1 illustrates a schematic structure of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN);



FIGS. 2 and 3 illustrate the configurations of a radio interface protocol between a UE and a UTRAN;



FIG. 4 illustrates an example physical channel structure used in an E-UMTS system;



FIG. 5 illustrates an example method for performing a contention-based random access procedure;



FIG. 6 illustrates a method for signaling a back-off parameter regarding random access according to a conventional technology;



FIG. 7 illustrates a method for signaling back-off information regarding random access according to an embodiment of the present invention;



FIG. 8 is a flow chart illustrating a random access procedure according to an embodiment of the present invention;



FIG. 9 illustrates a MAC PDU structure of a random access response message applied to an embodiment of the present invention;



FIG. 10 illustrates a structure of an E/R/RAID MAC sub-header;



FIG. 11 illustrates a MAC RAR structure;



FIG. 12 illustrates a MAC sub-header and a MAC RAR structure when a MAC PDU includes an dedicated back-off (BO) parameter for each RAID according to an embodiment of the present invention;



FIG. 13 illustrates a structure of a MAC sub-header including common back-off information according to an embodiment of the present invention;



FIG. 14 illustrates a MAC RAR structure when a MAC sub-header includes common back-off information according to an embodiment of the present invention;



FIG. 15 illustrates a random access response message when back-off information is included in a MAC sub-header according to an embodiment of the present invention; and



FIGS. 16 and 17 illustrate a MAC sub-header and a MAC RAR structure in the case where a special RAID is used according to an embodiment of the present invention.





DETAILED DESCRIPTION OF THE INVENTION

The above and other configurations, operations, and features of the present invention will be easily understood from the embodiments of the invention described below with reference to the accompanying drawings. The embodiments described below are examples wherein technical features of the invention are applied to an Evolved Universal Mobile Telecommunications System (E-UMTS).


Embodiment
Back-Off Information Signaling Using Random Access Response Message


FIG. 7 illustrates a method for performing random access according to an embodiment of the present invention.


As shown in FIG. 7, a UE transmits a random access preamble including a RAID. The random access preamble is transmitted through a Random Access Channel (RACH) (S710).


Thereafter, an eNB receives the random access preamble and transmits a random access response message including back-off information, as a response to the random access preamble, to the UE. The UE obtains the back-off information from the received random access response message (S720). The format of the random access response message may vary according to a protocol layer that makes a response to the random access preamble. For example, the protocol layer may be a MAC layer. In this case, the random access response message may include a MAC header. The random access response message may further include a MAC Random Access Response (RAR) for one or more UEs. In this case, a MAC RAR for a specific UE may be indicated using a RAID included in a random access preamble transmitted by the UE. The back-off information may be included in a MAC header or a MAC RAR.


The back-off information indicates information required to perform back-off. For example, the back-off information may include a back-off parameter. The back-off parameter may include a delay time for retransmission of a random access preamble or an upper delay time limit. The back-off information may further include information regarding a UE to which the back-off parameter is applied. The back-off information may include a back-off parameter or an index, an identity (or identification), an indicator, simplified information, or the like for indicating a specific UE. The size of the back-off information is not limited to a specific size. For example, the size of the back-off information may be 6 bits or less. The following table illustrates an example of the back-off parameter.












TABLE 1








Backoff Parameter value



Index
(ms)



















0
0



1
10



2
20



3
30



4
40



5
60



6
80



7
120



8
160



9
240



10
320



11
480



12
960










When the back-off parameter is indicated by an index, the index can be expressed by 4 bits.


A method for signaling back-off information using the random access response message will be described later in detail with reference to FIGS. 9 to 17. One important feature of this method is that back-off information is included in the random access response message so that back-off information is provided to the UE only when the UE has requested random access, thereby increasing the efficiency of radio resources and reducing a downlink overhead for signaling back-off.


Thereafter, when random access has failed, the UE performs back-off using the obtained back-off information (for example, a back-off parameter) (S730). Here, the term “back-off” refers to delaying, by a UE, an access attempt by an arbitrary or predetermined time. Specifically, the UE delays transmission of a random access preamble according to the back-off parameter. More specifically, the UE may delay an access attempt by a time indicated by the back-off parameter. In addition, the UE may delay an access attempt randomly within the time indicated by the back-off parameter. That is, the UE can delay an access attempt by a time that is selected with equal probability from a range of 0 ms to the back-off parameter.


The following are the cases where random access has failed. The first case is where the UE has failed to receive a random access response message. The second case is where, although the UE has received a random access response message, no random access response corresponding to the UE is present in the random access response message. The third case is that the UE has failed to perform uplink transmission using radio resources allocated through a random access response message. For example, the uplink transmission includes PUSCH transmission. The fourth case is where the UE has failed to pass through a contention resolution procedure for random access. The contention resolution procedure includes a MAC contention resolution procedure or an RLC contention resolution procedure.


Depending on the cause of the failure of random access, the UE may also fail to obtain back-off information from the random access response message. In this case, the UE may use a default back-off parameter or a back-off parameter obtained from a previous random access response message. The default back-off parameter includes 0 ms.


After performing back-off, the UE retransmits a random access preamble including a RAID (S740).



FIG. 8 is a flow chart illustrating a random access procedure according to an embodiment of the present invention.


As shown in FIG. 8, a UE receives RACH information (S802). When no separate uplink transmission channel is present, the UE performs a random access procedure in the following manner (S804).


The UE initializes a random access preamble counter M to “1” (S806). Thereafter, the UE decides whether or not to perform a random access procedure (S808). Thereafter, when the UE has decided to continue the random access procedure, the UE determines whether or not the value of the counter M is equal to or less than a maximum allowable value Mmax (S810). When the value of the counter M exceeds the maximum allowable value Mmax, the UE terminates the random access procedure (S832). Otherwise, the UE continues the random access procedure. As needed, the UE updates RACH information (S812) and selects a preamble signature/resource (S814). Thereafter, the UE determines preamble transmission power (S816) and transmits a PRACH preamble to an eNB (S818).


After transmitting the preamble, the UE determines whether or not an initial access procedure using the preamble is successful while monitoring an L1/L2 control region in order to receive a random access response message during a predetermined time (S820). For example, the UE determines that the initial access procedure has failed when the UE has failed to receive a downlink scheduling signal masked with an RA-RNTI within the predetermined time. The UE also determines that the initial access procedure has failed when information regarding the UE is not included in the random access response message although the UE has received a downlink scheduling signal masked with an RA-RNTI and has decoded the random access response message. The UE increases the counter value “M” by 1 (S828) and performs back-off when needed (□ S830). In this case, the back-off parameter is a default value including 0 ms or a value obtained through a previous random access response message.


When the UE has successfully received the random access response message, the UE adjust transmission timing using information obtained from the random access response and transmits an uplink message through an uplink SCH (S822). When the eNB has not successfully received the uplink message, the UE increases the counter value “M” by 1 (S828) and performs back-off using a back-off parameter obtained from the random access response message when needed (□ S830).


When the uplink message has been successfully transmitted to the eNB, the eNB transmits a contention resolution message to the UE in downlink. Thereafter, when the UE has passed through the contention resolution procedure, the UE terminates the random access procedure. On the other hand, when the UE has passed through the contention resolution procedure, the UE increases M by 1 (S828) and performs back-off using a back-off parameter obtained from the random access response message when needed (□ S830).


After performing back-off, the UE repeats the random access procedure, starting from step S808.



FIG. 9 illustrates a MAC PDU structure of a random access response message applied to an embodiment of the present invention. A MAC PDU is transmitted to a UE through a downlink SCH channel.


As shown in FIG. 9, one MAC PDU includes a MAC header and MAC payload. The MAC header includes one or more MAC sub-headers (for example, E/R/RAID sub-headers) and the MAC payload includes one or more MAC RARs. The MAC sub-headers correspond to the MAC RARs, respectively.



FIG. 10 illustrates a structure of an E/R/RAID MAC sub-header.


As shown in FIG. 10, the E/R/RAID MAC sub-header includes an E field, an R field, and a RAID field. The fields of the MAC sub-header are arranged on an octet (byte) basis. The following is a description of each of the fields.

    • E field: Extension field. This field serves as a flag indicating whether or not an additional field is included in the MAC header. When the E field is set to “1”, this indicates that another E/R/RAID field (sub-header) is present. When the E field is set to “0”, this indicates that a MAC RAR starts from the next byte.
    • R field: Field including a reserved bit. This field currently has no usage and can be defined and used as needed at a later time. The size of the R field is 1 bit.
    • RAID field: Field identifying a random access preamble transmitted from a UE. The size of the RAID field is 6 bits.


Back-off information signaling using a MAC sub-header will be described later in detail.



FIG. 11 illustrates a MAC RAR structure. As shown in FIG. 11, a MAC RAR includes a TA field, a UL grant field, and a T-CRNTI field. The fields of the MAC RAR are arranged on an octet (byte) basis. The following is a description of each of the fields.

    • TA field: Timing Advance field. The TA field indicates uplink transmission timing required for timing synchronization. The size of the TA field is 11 bits.
    • UL Grant field: Uplink grant field. The UL grant field indicates allocation information of radio resources used in uplink. The size of the UL grant field is 21 bits.
    • T-CRNTI field: Temporary CRNTI field. The T-CRNTI field indicates a temporary identification used by the UE before another random access procedure is initiated or before the contention resolution procedure has passed. The size of the T-CRNTI field is 16 bits.


The following is a detailed description of signaling of back-off information using a random access response message (for example, a MAC PDU).


Back-off information included in a random access response message may be dedicated back-off information or common back-off information depending on implementations. In this specification, the term “dedicated back-off information” refers to back-off information that is individually applied to each of a plurality of UEs that use different random access preambles. For example, the dedicated back-off information may be defined for each RAID used to identify a random access preamble transmitted by the UE. In this case, the same back-off information is applied to UEs that use the same RAID while different back-off information is applied to UEs that use different RAIDS. The term “common back-off information” refers to back-off information that is commonly applied to UEs that use different random access preambles. For example, common back-off information may be defined for a specific RAID group or for each random access response message. Thus, the same back-off information is applied to UEs even when the UEs use different RAIDs.


The following are descriptions of three possible options regarding signaling back-off information through a MAC PDU.


Option 1: Inclusion of Dedicated Back-Off Information


Back-off information can be included in a random access response message for each RAID. Specifically, a back-off parameter can be included in a respective MAC RAR corresponding to each RAID. Since a back-off parameter is mapped one-to-one to a RAID, the back-off parameter is RAID-specific. That is, the back-off parameter is commonly applied to one or more UEs that have accessed a random access response message using the same RAID. On the other hand, different back-off parameters are applied to one or more UEs that have accessed a random access response message using different RAIDs. Since a different back-off parameter can be applied to each RAID in this manner, the back-off parameter can be used to control random access load.



FIG. 12 illustrates a MAC sub-header and a MAC RAR structure when a MAC PDU includes a dedicated back-off (BO) parameter for each RAID according to an embodiment of the present invention.


As shown in FIG. 12, the MAC sub-header has the same structure as the general E/R/RAID sub-header. That is, the MAC sub-header includes an E field, an R field, and a RAID field. On the other hand, a MAC RAR corresponding to the RAID includes a back-off parameter, unlike the general MAC RAR. Since the back-off parameter is provided for each RAID, a MAC RAR having a back-off parameter may also include a TA field. When a UE retransmits a random access preamble after performing back-off, the UE can control transmission timing of the random access preamble using a value included in the TA field of the MAC RAR. The MAC RAR may include only the back-off parameter although “TA” is illustrated as being additionally included in a MAC RAR having a back-off parameter in FIG. 12.


Option 2: Common Back-Off Information


A random access response message may include a back-off parameter commonly used by a plurality of UEs. In this case, the common back-off parameter in the random access response message is applied to UEs that have simultaneously accessed the random access response message using different RAIDs. In this regard, the following two sub-options can be considered.


Option 2a: Replacement of RAID with Back-Off Parameter



FIG. 13 illustrates a structure of a MAC sub-header including common back-off information according to an embodiment of the present invention. As shown in FIG. 13, when an R bit in the E/R/RAID sub-header is set to “0”, a normal RAID is included in the E/R/RAID sub-header (see FIG. 13(a)). On the other hand, when the R bit is set to “1”, a back-off parameter is included in the RAID field (see FIG. 13(b)). Accordingly, when a UE confirmes that an R bit in a specific sub-header is set to “0”, the UE assumes that a RAID field in the specific sub-header is a back-off parameter. This analysis of the R bit is illustrative and the R bit can be interpreted in the reverse manner.


For this reason, when a back-off parameter is included in a specific MAC sub-header, a RAID is not included in the specific MAC sub-header. On the other hand, when a RAID is included in a specific MAC sub-header, a back-off parameter is not included in the specific MAC sub-header. In FIG. 13, the R bit is illustrated as indicating whether or not a back-off parameter field is included in the MAC sub-header. However, FIG. 13 is only illustrative and whether or not the back-off parameter field is included in the MAC sub-header can be indicated by any field having a flag indicating the type of the back-off parameter field or indicating presence or absence of the back-off parameter field. For example, whether or not a back-off parameter field is included in a MAC sub-header can be indicated by an E field or an additional field included in the MAC sub-header. In this case, the size of the field indicating the type or presence of the back-off parameter field may be 1 bit.


The specific MAC sub-header including the back-off parameter may or may not correspond to a specific MAC RAR. The case where the specific MAC sub-header corresponds to a specific MAC RAR will be described later with reference to FIG. 14. In the case where the specific MAC sub-header does not correspond to a specific MAC RAR, a MAC PDU for a random access response may be constructed as follows.


(1) Include only a specific sub-header including back-off parameter


The random access response message may include only a specific MAC sub-header including a back-off parameter. In this case, the back-off parameter is applied to all UEs that receive the specific MAC sub-header. Accordingly, when a UE has received a random access response message including only one specific MAC sub-header including a back-off parameter, the UE obtains and stores the back-off parameter without the need to confirm whether or not a RAID of a preamble transmitted by the UE is included in the random access response message. In this case, a corresponding MAC RAR is not included in the random access response message. Accordingly, all UEs that have received the random access response message assume that random access has failed and perform back-off according to the back-off parameter.


(2) Additionally include normal sub-header without back-off parameter


The random access response message may include a sub-header including a back-off parameter and further include one or more normal sub-headers including no back-off parameter. The random access response message also includes normal MAC RARs corresponding respectively to the normal MAC sub-headers. The structures of the normal MAC sub-header and the normal MAC RAR are identical to those described above with reference to FIGS. 10 and 11. In this case, the back-off parameter is commonly applied to a plurality of UEs that receive the MAC sub-header. However, since the random access response message includes a MAC sub-header having a RAID and a corresponding MAC RAR, the scope of UEs to which the back-off parameter is applied is more restricted.


Specifically, when a UE has received a random access response message, the UE determines whether or not a RAID of the UE is included in a MAC header of the message. When the RAID of the UE is included in the MAC header, the UE can obtain information regarding uplink transmission timing, uplink radio resource allocation information for uplink SCH transmission, and temporary UE ID information from a corresponding MAC RAR. On the other hand, when the UE has failed to find a RAID of the UE in the MAC header, the UE obtains and stores a back-off parameter from a specific sub-header including the back-off parameter. In this case, it is assumed that the random access procedure has failed since the UE has failed to find a RAID of the UE in the random access response message. Accordingly, the UE performs back-off using the back-off parameter obtained from the specific sub-header. When the random access response message includes both the normal MAC sub-header and the specific MAC sub-header, the order of the two sub-headers is not limited. However, taking into consideration the fact that it is desirable that back-off be applied when the UE has failed to find a RAID of the UE, it is more preferable that the specific MAC sub-header having a back-off parameter be located at the end of the MAC header.



FIG. 14 illustrates a MAC RAR structure when a MAC sub-header includes common back-off information according to an embodiment of the present invention. As shown in FIG. 14, the structure of the MAC RAR is determined according to the type of the corresponding MAC sub-header. When the corresponding MAC sub-header includes a RAID (i.e., does not include a back-off parameter), the MAC RAR has a normal structure illustrated in FIG. 11 (see FIG. 14(a)). That is, the MAC RAR includes a Timing Advance (TA) field indicating uplink transmission timing, a UL grant field including uplink radio resource allocation information for uplink SCH transmission, and a T-CRNTI field that serves as a temporary UE identification.


As shown in FIG. 13, the random access response message in Option 2a may not include a MAC RAR corresponding to a MAC sub-header having a back-off parameter. However, the random access response message may further include a specific MAC RAR in order to more selectively control the scope of UEs to which the back-off parameter is applied. In this case, the specific MAC RAR may include UE information (e.g., a UE list) regarding one or more UEs to which the back-off parameter is applied. For example, the UE information may be a RAID for a random access preamble transmitted by a UE. Specifically, the specific MAC RAR may include a list of one or more different RAIDs. More specifically, a list of RAIDs in the specific MAC RAR may include an E field, an R field, and a RAID field. Here, the E field and the R field are identical to those described above with reference to the MAC E/R/RAID sub-header. By introducing a specific MAC RAR which corresponds to a MAC sub-header having a back-off parameter and includes a RAID list, the eNB can more selectively transmit a positive ACK to specific UEs and allow some other specific UEs to perform back-off.


Specifically, when a UE has received a random access response message, the UE determines whether or not a RAID of the UE is included in a MAC header of the message. When a RAID of the UE is included in a MAC header of the message, the UE can obtain information regarding uplink transmission timing, uplink radio resource allocation information for uplink SCH transmission, and temporary UE ID information from a corresponding MAC RAR. On the other hand, when the UE has failed to find a RAID of the UE in the MAC header but instead has found only a specific sub-header including a back-off parameter, the UE determines whether or not a specific MAC RAR corresponding to the specific MAC sub-header is present. When no specific MAC RAR is present, the UE performs back-off using the back-off parameter included in the specific MAC sub-header. On the other hand, when a specific MAC RAR is present, the UE determines whether or not a RAID of the UE is included in the specific MAC RAR. When the UE has found a RAID of the UE in the specific MAC RAR, the UE obtains a back-off parameter from the MAC sub-header. It is determined that the random access procedure has failed since the UE has not received a positive ACK although the UE has obtained the back-off parameter. Accordingly, the UE performs back-off using the back-off parameter. On the other hand, a UE, which has not found a RAID of the UE in the specific MAC RAR, performs back-off using a default back-off parameter or a back-off parameter obtained from a previous random access response message. The default back-off parameter includes 0 ms. The random access response message may include two or more MAC sub-headers having different back-off parameters and specific MAC RARs corresponding respectively to the MAC sub-headers. In this case, even when the back-off parameters have common back-off parameter characteristics, UEs that have transmitted different RAIDs can be configured to use different back-off parameters. Accordingly, the eNB can selectively apply different back-off parameters to different UEs.


When the random access response message includes both the normal MAC RAR and the specific MAC RAR, the order of the two MAC RARs is not limited. In this regard, it is more preferable that the specific MAC sub-header having a back-off parameter be located at the end of the MAC header as described above. Thus, it is also preferable that the specific MAC RAR be located last among the MAC RARs.



FIG. 15 illustrates a random access response message when back-off information is included in a MAC sub-header according to an embodiment of the present invention. The random access response message of FIG. 15 is a combination of the MAC sub-header structure of FIG. 13 and the MAC RAR structure of FIG. 14. The random access response message structure shown in FIG. 15 can be represented by the following table.













TABLE 2








MAC Header
MAC Payload









1
One 2nd MAC sub-header




2
One or more 1st MAC
One or more 1st MAC RARsC)




sub-headersA) +





One 2nd MAC sub-headerB)




3
One or more 1st MAC
One or more 1st MAC RARs +




sub-headers +
One 2nd MAC RARD)




One 2nd MAC sub-header




4
One or more 1st MAC
One or more 1st MAC RARs +




sub-headers +
Two or more 2nd MAC RARs




Two or more 2nd MAC





sub-headers








A)Indicates a normal E/R/RAID sub-header (see FIG. 13A)





B)Indicates a MAC sub-header including a back-off parameter (see FIG. 13(b))





C)Indicates a normal MAC RAR corresponding to an E/R/RAID sub-header (see FIG. 14(a))





D)Indicates a MAC RAR which corresponds to a MAC sub-header including a back-off




parameter and includes a RAID list (see FIG. 14(b))






Option 2b: Special RAID for Common Back-Off Parameter


A certain RAID can be used only to indicate common back-off information. In this specification, the certain RAID is referred to as a “special RAID”. The following is a detailed description thereof.



FIGS. 16 and 17 illustrate a MAC sub-header and a MAC RAR structure in the case where a special RAID is used according to an embodiment of the present invention. The MAC sub-header and the MAC RAR structure according to Option 2b are similar to those of Option 2a. The difference is that a special RAID rather than a back-off parameter is included in a MAC sub-header and a back-off parameter is included in a MAC RAR corresponding to the MAC sub-header. Although a list of RAIDs is illustrated as being additionally included in the MAC RAR, the MAC RAR may include only the back-off parameter. Other basic operations or features are similar to those of Option 2a.


Specifically, when a UE has received a random access response message, the UE determines whether or not a RAID of the UE is included in a MAC header of the message. When a RAID of the UE is included in a MAC header of the message, the UE can obtain information regarding uplink transmission timing, uplink radio resource allocation information for uplink SCH transmission, and temporary UE ID information from a corresponding MAC RAR. On the other hand, when the UE has failed to find a RAID of the UE in the MAC header but instead has found only a special RAID, the UE refers to a specific MAC RAR corresponding to a sub-header having the special RAID. When the specific MAC RAR includes a back-off parameter alone, all UEs which have referred to the specific MAC RAR perform back-off after obtaining the back-off parameter. On the other hand, when a list of RAIDs is included in the specific MAC RAR, the UE determines whether or not a RAID of the UE is included in the specific MAC RAR. When the UE has found a RAID of the UE in the specific MAC RAR, the UE obtains a back-off parameter from the MAC RAR and then performs back-off. On the other hand, a UE, which has not found a RAID of the UE in the specific MAC RAR, performs back-off using a default back-off parameter or a back-off parameter obtained from a previous random access response message. The default back-off parameter includes 0 ms. Accordingly, the eNB can selectively apply different back-off parameters to different UEs.


When the random access response message includes both the normal MAC RAR and the specific MAC RAR, the order of the two MAC RARs is not limited. However, taking into consideration the fact that it is desirable that back-off be applied when the UE has failed to find a RAID of the UE in the MAC sub-header, it is preferable that a sub-header having a special RAID and a corresponding specific MAC RAR be located last among the MAC RARs.


The above embodiments are provided by combining components and features of the present invention in specific forms. The components or features of the present invention should be considered optional if not explicitly stated otherwise. The components or features may be implemented without being combined with other components or features. The embodiments of the present invention may also be provided by combining some of the components and/or features. The order of the operations described above in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It will be apparent that claims which are not explicitly dependent on each other can be combined to provide an embodiment or new claims can be added through amendment after this application is filed.


The embodiments of the present invention have been described focusing mainly on the data communication relationship between a terminal and a Base Station (BS). Specific operations which have been described as being performed by the BS may also be performed by an upper node as needed. That is, it will be apparent to those skilled in the art that the BS or any other network node may perform various operations for communication with terminals in a network including a number of network nodes including BSs. The term “base station (BS)” may be replaced with another term such as “fixed station”, “Node B”, “eNode B (eNB)”, or “access point”. The term “terminal” may also be replaced with another term such as “user equipment (UE)”, “mobile station (MS)”, or “mobile subscriber station (MSS)”.


The embodiments of the present invention can be implemented by hardware, firmware, software, or any combination thereof. In the case where the present invention is implemented by hardware, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPS), digital signal processing devices (DSPDS), programmable logic devices (PLDS), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or the like.


In the case where the present invention is implemented by firmware or software, the embodiments of the present invention may be implemented in the form of modules, processes, functions, or the like which perform the features or operations described above. Software code can be stored in a memory unit so as to be executed by a processor. The memory unit may be located inside or outside the processor and can communicate data with the processor through a variety of known means.


As is apparent from the above description, the embodiments of the present invention have the following advantages.


First, it is possible to reduce overhead and increase the efficiency of radio resources in association with a random access procedure performed in a wireless communication system.


Second, it is possible to signal back-off information only when random access is needed, thereby reducing overhead.


Third, it is possible to apply different back-off information to each UE in random access.


Fourth, it is possible to provide a message format for signaling back-off information in random access.


Those skilled in the art will appreciate that the present invention may be embodied in other specific forms than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above description is therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by reasonable interpretation of the appended claims and all changes coming within the equivalency range of the invention are intended to be embraced in the scope of the invention.


The present invention can be applied to a wireless communication system, and more particularly, to a method for performing random access in a wireless communication system.

Claims
  • 1. A method for performing a random access procedure in a wireless communication system, the method comprising: transmitting a first preamble for random access from a mobile station to a network node;receiving, by the mobile station, a random access response message from the network node as a response to the first preamble, the random access response message having a MAC Medium Access Control headeronly one Medium Access Control (MAC) sub-header having a backoff parameter and zero or morenot having any MAC Random Access ResponsesResponse (MAC RARsRAR);determining ifthat a field in athe MAC sub-header of the MAC header indicates athe backoff parameter exists in the MAC sub-header;obtaining the backoff parameter from the MAC sub-header whenbased on determining that the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header; andperforming backoff using the backoff parameter obtained from the MAC sub-header,wherein there is no corresponding MAC RAR corresponding to the MAC sub-header that has the backoff parameter in the random access response messagewhen the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header.
  • 2. The method of claim 1, wherein the field indicates whether or not the MAC sub-header has a random access preamble identifier or the backoff parameter.
  • 3. The method of claim 1, wherein the backoff parameter is a common backoff parameter or an exclusive backoff parameter to be used exclusively by the mobile terminalstation.
  • 4. The method of claim 1, wherein the field is followed by the backoff parameter.
  • 5. The method of claim 4, wherein the field is directly followed by the backoff parameter.
  • 6. The method of claim 1, wherein the backoff parameter is related with a transmission of a second preamble for random access.
  • 7. A method for performing a random access procedure in a wireless communication system, the method comprising: receiving, at a network node, a first preamble for random access from a mobile terminalstation;transmitting, by the network node, a random access response message to the mobile terminalstation as a response to the first preamble, the random access response message having a MAC Medium Access Control headeronly one Medium Access Control (MAC) sub-header having a backoff parameter and zero or morenot having any MAC Random Access ResponsesResponse (MAC RARsRAR), wherein the MAC header comprises athe MAC sub-header includingincludes a field indicating whether or not the MAC sub-header has a backoff parameter configured to enable the mobile terminalstation to perform backoff;determining, by the mobile terminalstation, ifthat the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header;obtaining, by the mobile terminalstation, the backoff parameter from the MAC sub-header whenbased on determining that the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header; andperforming, by the mobile terminalstation, the backoff using the backoff parameter obtained from the MAC sub-header,wherein there is no corresponding MAC RAR corresponding to the MAC sub-header that has the backoff parameter in the random access response messagewhen the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header.
  • 8. The method of claim 7, wherein the field indicates whether or not the MAC sub-header has a random access preamble identifier or the backoff parameter.
  • 9. The method of claim 7, wherein the backoff parameter is common back-offbackoff parameter or an exclusive backoff parameter to be used exclusively by the mobile terminalstation.
  • 10. The method of claim 7, wherein the field is followed by the backoff parameter.
  • 11. The method of claim 10, wherein the field is directly followed by the backoff parameter.
  • 12. The method of claim 7, wherein the backoff parameter is related with a transmission of a second preamble for random access that is to be received by the network node.
  • 13. A mobile terminalstation configured to perform a random access procedure in a wireless communication system, the mobile station comprising: a processor configured to cause the mobile terminalstation to: transmit a first preamble for random access to a network node;process a random access response message received from the network node as a response to the first preamble, the random access response message having a MAC Medium Access Control headeronly one Medium Access Control (MAC) sub-header having a backoff parameter and zero or morenot having any MAC Random Access ResponsesResponse (MAC RARsRAR);determine ifthat a field in athe MAC sub-header of the MAC header indicates athe backoff parameter exists in the MAC sub-header;obtain the backoff parameter from the MAC sub-header whenbased on determining that the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header; andperform backoff using the backoff parameter obtained from the MAC sub-header,wherein there is no corresponding MAC RAR corresponding to the MAC sub-header that has the backoff parameter in the random access response messagewhen the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header.
  • 14. The mobile terminalstation of claim 13, wherein the field indicates whether or not the MAC sub-header has a random access preamble identifier or the backoff parameter.
  • 15. The mobile terminalstation of claim 13, wherein the backoff parameter is a common backoff parameter or an exclusive backoff parameter to be used exclusively by the mobile terminalstation.
  • 16. The mobile terminalstation of claim 13, wherein the field is followed by the backoff parameter.
  • 17. The mobile terminalstation of claim 16, wherein the field is directly followed by the backoff parameter.
  • 18. The mobile terminalstation of claim 13, wherein the backoff parameter is related with a transmission of a second preamble for random access.
  • 19. A network node configured to perform a random access procedure in a wireless communication system, the network node comprising: a processor configured to cause the network node to process a first preamble for random access received from a mobile terminalstation; and to transmit a random access response message to the mobile terminalstation as a response to the first preamble, the random access response message having a MAC Medium Access Control headeronly one Medium Access Control (MAC) sub-header and zero or morenot having any MAC Random Access ResponsesResponse (MAC RARsRAR),wherein the MAC header includes athe MAC sub-header includingincludes a field indicating whether or not the MAC sub-header includes a backoff parameter, andwherein there is no corresponding MAC RAR corresponding to the MAC sub-header that has the backoff parameter in the random access response messagewhen the field in the MAC sub-header indicates the backoff parameter exists in the MAC sub-header.
  • 20. The network node of claim 19, wherein the field indicates whether or not the MAC sub-header has a random access preamble identifier or the backoff parameter.
  • 21. The network node of claim 19, wherein the backoff informationparameter is a common backoff parameter or an exclusive backoff parameter to be used exclusively by the mobile terminalstation.
  • 22. The network node of claim 19, wherein the field is followed by the backoff parameter.
  • 23. The network node of claim 22, wherein the field is directly followed by the back-offbackoff parameter.
  • 24. The method node of claim 19, wherein the backoff parameter is related with a transmission of a second preamble for random access that is to be received by the network node.
Priority Claims (1)
Number Date Country Kind
10-2009-0005439 Jan 2009 KR national
Parent Case Info

This application is a continuation reissue application of U.S. application Ser. No. 15/826,172 filed on Nov. 29, 2017, now U.S. Pat. No. RE48,836, which is a reissue application of U.S. Pat. No. 8,040,913 issued on Oct. 18, 2011, which is a continuation of co-pending U.S. application Ser. No. 12/362,993 filed on Jan. 30, 2009, now U.S. Pat. No. 8,027,356 issued on Sep. 27, 2011, which claims the benefit of U.S. provisional application 61/025,267, filed on Jan. 31, 2008, and Korean Patent Application No. 10-2009-0005439 filed on Jan. 22, 2009, which are hereby incorporated by reference as if fully set forth herein.

US Referenced Citations (123)
Number Name Date Kind
5754754 Dudley et al. May 1998 A
5802064 Lieberman Sep 1998 A
5878041 Yamanaka et al. Mar 1999 A
6557135 Balachandran et al. Apr 2003 B1
6594240 Chuah et al. Jul 2003 B1
6728918 Ikeda et al. Apr 2004 B1
6738624 Aksentijevic et al. May 2004 B1
6862450 Mikola et al. Mar 2005 B2
6874113 Chao et al. Mar 2005 B2
6967936 Laroia et al. Nov 2005 B1
6987985 Purkayastha et al. Jan 2006 B2
7009940 Vialen et al. Mar 2006 B2
7180885 Terry Feb 2007 B2
7227857 Kuo Jun 2007 B2
7227868 Inden Jun 2007 B2
7295573 Yi et al. Nov 2007 B2
7464166 Larsson et al. Dec 2008 B2
7486699 Yi et al. Feb 2009 B2
7796505 Olsson et al. Sep 2010 B2
7894444 Lohr et al. Feb 2011 B2
8027321 Zheng Sep 2011 B2
8027356 Lee Sep 2011 B2
8040913 Lee Oct 2011 B2
8270361 Yi et al. Sep 2012 B2
8335189 Wang et al. Dec 2012 B2
8422510 Lee Apr 2013 B2
8532135 Lee Sep 2013 B2
8699711 Mukherjee et al. Apr 2014 B2
8712055 Yi et al. Apr 2014 B2
8797956 Hapsari et al. Aug 2014 B2
8812009 Chun et al. Aug 2014 B2
8989382 Yi et al. Mar 2015 B2
RE48836 Lee Nov 2021 E
20020001314 Yi et al. Jan 2002 A1
20020009999 Lee et al. Jan 2002 A1
20020122411 Zimmerman et al. Sep 2002 A1
20030007490 Yi et al. Jan 2003 A1
20030099305 Yi et al. May 2003 A1
20030137931 Hans et al. Jul 2003 A1
20030194992 Kim et al. Oct 2003 A1
20030220119 Terry Nov 2003 A1
20040003106 Cunningham et al. Jan 2004 A1
20040022213 Choi et al. Feb 2004 A1
20040076182 Wu Apr 2004 A1
20040085932 Jiang May 2004 A1
20040103435 Yi et al. May 2004 A1
20040146019 Kim et al. Jul 2004 A1
20040147236 Parkvall et al. Jul 2004 A1
20040156330 Yi et al. Aug 2004 A1
20040235447 Gronberg et al. Nov 2004 A1
20050020260 Jeong et al. Jan 2005 A1
20050047416 Heo et al. Mar 2005 A1
20050054365 Ahn et al. Mar 2005 A1
20050063347 Sarkkinen et al. Mar 2005 A1
20050094596 Pietraski et al. May 2005 A1
20050096017 Kim May 2005 A1
20050118992 Jeong et al. Jun 2005 A1
20050169293 Zhang et al. Aug 2005 A1
20050213605 Kim et al. Sep 2005 A1
20050237972 Van Dervelde et al. Oct 2005 A1
20050250526 Lindoff et al. Nov 2005 A1
20050254467 Li et al. Nov 2005 A1
20050259662 Kim et al. Nov 2005 A1
20050287957 Lee et al. Dec 2005 A1
20060067238 Olsson et al. Mar 2006 A1
20060067289 Lee et al. Mar 2006 A1
20060072494 Matusz Apr 2006 A1
20060072503 Kim et al. Apr 2006 A1
20060084389 Beale et al. Apr 2006 A1
20060154680 Kroth et al. Jul 2006 A1
20060164981 Olsson et al. Jul 2006 A1
20060165045 Kim et al. Jul 2006 A1
20060182065 Petrovic et al. Aug 2006 A1
20060203780 Terry Sep 2006 A1
20060233200 Fifield et al. Oct 2006 A1
20060251027 Chun et al. Nov 2006 A1
20060251105 Kim et al. Nov 2006 A1
20060268798 Kim et al. Nov 2006 A1
20060280145 Revel et al. Dec 2006 A1
20070032255 Koo et al. Feb 2007 A1
20070041397 Hwang Feb 2007 A1
20070047493 Park et al. Mar 2007 A1
20070060139 Kim et al. Mar 2007 A1
20070079207 Seidel et al. Apr 2007 A1
20070081468 Timus Apr 2007 A1
20070081513 Torsner Apr 2007 A1
20070091810 Kim et al. Apr 2007 A1
20070133456 Ding Jun 2007 A1
20070201397 Zhang Aug 2007 A1
20070206531 Pajukoski et al. Sep 2007 A1
20070268861 Diachina et al. Nov 2007 A1
20070274278 Choi et al. Nov 2007 A1
20070287440 Benkert et al. Dec 2007 A1
20070297360 Joachim et al. Dec 2007 A1
20080013521 Rangan et al. Jan 2008 A1
20080051098 Rao Feb 2008 A1
20080081598 Chandra et al. Apr 2008 A1
20080084851 Kim et al. Apr 2008 A1
20080146242 Alanara et al. Jun 2008 A1
20080182609 Somasundaram et al. Jul 2008 A1
20080186936 Chun et al. Aug 2008 A1
20080186944 Suzuki et al. Aug 2008 A1
20080198869 Jiang Aug 2008 A1
20080233940 Jen Sep 2008 A1
20090046617 Tenny et al. Feb 2009 A1
20090046695 Jiang Feb 2009 A1
20090104890 Wang et al. Apr 2009 A1
20090156194 Meylan Jun 2009 A1
20090175163 Sammour et al. Jul 2009 A1
20090201798 Lee Aug 2009 A1
20090232058 Lee Sep 2009 A1
20090318177 Wang et al. Dec 2009 A1
20090323574 Koskinen et al. Dec 2009 A1
20100014466 Meyer et al. Jan 2010 A1
20100014901 Kobashi et al. Jan 2010 A1
20100067498 Lee et al. Mar 2010 A1
20100142457 Chun et al. Jun 2010 A1
20100290427 Sebire et al. Nov 2010 A1
20110216705 Lee Sep 2011 A1
20110216706 Lee Sep 2011 A1
20110305182 Suzuki et al. Dec 2011 A1
20130258919 Damnjanovic Oct 2013 A1
20210014901 Höglund Jan 2021 A1
Foreign Referenced Citations (170)
Number Date Country
1349360 May 2002 CN
1437368 Aug 2003 CN
1457202 Nov 2003 CN
1497922 May 2004 CN
1549610 Nov 2004 CN
1643820 Jul 2005 CN
1829187 Sep 2006 CN
1918825 Feb 2007 CN
101809948 Aug 2010 CN
1035745 Sep 2000 EP
1343267 Sep 2003 EP
L343 267 Sep 2003 EP
1458148 Sep 2004 EP
1 508 992 Feb 2005 EP
1508992 Feb 2005 EP
1557967 Jul 2005 EP
1578111 Sep 2005 EP
1655879 May 2006 EP
1689130 Aug 2006 EP
1689130 Aug 2006 EP
1689134 Aug 2006 EP
1 746 855 Jan 2007 EP
1746855 Jan 2007 EP
1 768 297 Mar 2007 EP
1788751 May 2007 EP
1 796 405 Jun 2007 EP
1768297 Jun 2007 EP
1796405 Jun 2007 EP
2026523 Feb 2009 EP
1695462 Aug 2009 EP
1695462 Aug 2009 EP
2086276 Aug 2009 EP
2086276 Aug 2009 EP
2108223 Sep 2015 EP
2002-198895 Jul 2002 JP
2002198895 Jul 2002 JP
2003-516021 May 2003 JP
2003516021 May 2003 JP
2007-312244 Nov 2007 JP
2010519868 Jun 2010 JP
10-2001-0045783 Jun 2001 KR
1020010045783 Jun 2001 KR
10-2001-0062306 Jul 2001 KR
1020010062306 Jul 2001 KR
10-2002-0004645 Jan 2002 KR
1020020004645 Jan 2002 KR
10-2002-0097304 Dec 2002 KR
1020020097304 Dec 2002 KR
10-2003-0012048 Feb 2003 KR
1020030012048 Feb 2003 KR
10-2003-0060055 Jul 2003 KR
1020030060055 Jul 2003 KR
10-2003-0087914 Nov 2003 KR
1020030087914 Nov 2003 KR
1020040016065 Feb 2004 KR
1020040016334 Feb 2004 KR
10-2004-0034398 Apr 2004 KR
1020040034398 Apr 2004 KR
10-2004-0039944 May 2004 KR
1020040039944 May 2004 KR
10-2004-0072961 Aug 2004 KR
1020040072961 Aug 2004 KR
10-2005-0022988 Mar 2005 KR
1020050022988 Mar 2005 KR
1020050029395 Mar 2005 KR
10-2005-0062359 Jun 2005 KR
1020050062359 Jun 2005 KR
10-2005-0081836 Aug 2005 KR
1020050081836 Aug 2005 KR
10-2005-0092874 Sep 2005 KR
1020050092874 Sep 2005 KR
10-2005-0099472 Oct 2005 KR
10-2005-0100882 Oct 2005 KR
10-2005-0103127 Oct 2005 KR
1020050099472 Oct 2005 KR
1020050100882 Oct 2005 KR
1020050103127 Oct 2005 KR
10-2006-0004935 Jan 2006 KR
1020060004935 Jan 2006 KR
10-2006-0014910 Feb 2006 KR
1020060014910 Feb 2006 KR
10-2006-0029452 Apr 2006 KR
1020060029452 Apr 2006 KR
10-2006-0042858 May 2006 KR
1020060042858 May 2006 KR
10-2006-0069378 Jun 2006 KR
1020060069378 Jun 2006 KR
10-2006-0079784 Jul 2006 KR
1020060079784 Jul 2006 KR
10-2003-0068743 Aug 2006 KR
10-2006-0090191 Aug 2006 KR
1020030068743 Aug 2006 KR
1020060090191 Aug 2006 KR
10-2006-0134058 Dec 2006 KR
1020060131671 Dec 2006 KR
1020060134058 Dec 2006 KR
10-2007-0048552 May 2007 KR
1020070048552 May 2007 KR
10-2007-0076374 Jul 2007 KR
1020070073577 Jul 2007 KR
1020070073588 Jul 2007 KR
1020070076374 Jul 2007 KR
10-2008-0039176 May 2008 KR
1020080039176 May 2008 KR
1020080085694 Sep 2008 KR
1020090084320 Aug 2009 KR
2304348 Aug 2007 RU
WO9937114 Jul 1999 WO
WO0122645 Mar 2001 WO
WO0124411 Apr 2001 WO
WO 0139386 May 2001 WO
WO0139386 May 2001 WO
WO0167664 Sep 2001 WO
WO0201742 Jan 2002 WO
WO0245453 Jun 2002 WO
WO 03045103 May 2003 WO
WO03045103 May 2003 WO
WO 2004042953 May 2004 WO
WO-2004042963 May 2004 WO
WO2004042953 May 2004 WO
WO2004042963 May 2004 WO
WO2004042964 May 2004 WO
WO2004100537 Nov 2004 WO
WO-2005039108 Apr 2005 WO
WO2005039108 Apr 2005 WO
WO 2005122441 Dec 2005 WO
WO 2005125226 Dec 2005 WO
WO2005122441 Dec 2005 WO
WO2005125226 Dec 2005 WO
WO 2006046894 May 2006 WO
WO-2006052086 May 2006 WO
WO2006046894 May 2006 WO
WO2006052086 May 2006 WO
WO2006083149 Aug 2006 WO
WO-2006118418 Nov 2006 WO
WO2006118418 Nov 2006 WO
2007020070 Feb 2007 WO
WO2007020070 Feb 2007 WO
WO-2007024065 Mar 2007 WO
WO2007024065 Mar 2007 WO
WO 2007039023 Apr 2007 WO
WO2007039023 Apr 2007 WO
WO-2007052900 May 2007 WO
WO2007052900 May 2007 WO
WO 2007066900 Jun 2007 WO
WO2007066900 Jun 2007 WO
WO 2007078142 Jul 2007 WO
WO-2007078164 Jul 2007 WO
WO-2007078173 Jul 2007 WO
WO 2007078174 Jul 2007 WO
WO2007078142 Jul 2007 WO
WO2007078156 Jul 2007 WO
WO2007078164 Jul 2007 WO
WO2007078173 Jul 2007 WO
WO2007078174 Jul 2007 WO
WO-2007089797 Aug 2007 WO
WO 2007091831 Aug 2007 WO
WO2007089797 Aug 2007 WO
WO2007091831 Aug 2007 WO
WO2007091838 Aug 2007 WO
2007312244 Nov 2007 WO
WO-2007126793 Nov 2007 WO
WO2007126793 Nov 2007 WO
WO-2007147431 Dec 2007 WO
WO2007147431 Dec 2007 WO
WO 2008004725 Jan 2008 WO
WO2008004725 Jan 2008 WO
WO2008060097 May 2008 WO
WO2008094120 Aug 2008 WO
WO2009045945 Apr 2009 WO
Non-Patent Literature Citations (52)
Entry
“3GPP, ““Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC) protocol specification (3GPP TS 25.331 version 6.6.0 Release 6),”” ETSI TS 125 331 V6.6.0, Jun. 2005, pp. 1-1156”.
“LG Electronics Inc., ““Handling of HFN de-synchronization,”” R2-074746, 3GPP TSG-RAN WG2 #60 , Je ju, Korea, Nov. 5-9, 2007, pp. 1-2”.
“LG Electronics, ““Discussion on Message 4 in Random Access,”” R2-073354, 3GPP TSG-RAN WG2 #59 , Athens, Greece , Aug. 20-24, 2007, pp. 1-4”.
“LG Electronics, ““Resource request in Synchronized Case,”” R2-061018 , TSG-RAN Working Group 2 #52 , Athens , Greece, Mar. 27-31, 2005, pp. 1-2”.
“Motorola et al., ““E-UTRA Random Access Channel TP from email discussion,”” R1-060885, 3GPP TSG RAN1#44-bis, Athens, Greece, Mar. 27-30, 2006, 6 pages”.
“Motorola: ““Contention-free Intra-LTE Handover””, 3GPP Draft, R2-070730-Non_Cont_Handoff_vol. 3rd Generation Partnership Project (3GPP), vol. RAN WG2, no. St. Louis, USA: Feb. 9, 2007, (Feb. 9, 2007), XP050133763.”
“Nokia Corporation et al., ““MAC Header Format,”” R2-073891, 3GPP TSG-RAN WG2 Meeting #59bis, Shanghai, China, Oct. 8-12, 2007, 5 pages”.
“Nokia Siemens Netw Orks, ““Security Update , ”” R2-074526 , 3GPP TSG-RAN2 Meeting #59bis, Shanghai, China, Oct. 8-12, 2007, 4 pages”.
“NTT Docomo, Inc., ““Uplink synchronization,”” R2-070781 , 3GPP TSG RAN WG2 #57, St. Louis, USA, Feb. 12-16, 2007, 3 pages”.
“Samsung, ““MAC functions: ARQ,”” R2-060374, 3GPP TSG-RAN2 Meeting #51, Denver, U.S.A, Feb. 13-17, 2006, 5 pages”.
“Samsung, ““Optimization of contention resolution in aRACH,”” R2-072797, 3GPP TSG-RAN WG2#58bis, Orlando, USA, Jun. 25-29, 2007, 3 pages”.
“Texas Instruments: ““UL Synchronization Management in LTE_Active””, 3GPP Draft; R1-071478_ULSYNC, 3rd Generation Partnership Project (3GPP); vol. Ran WG1. no. St. Julian, Mar. 21, 2007, (Mar. 21, 2007), XP050105413.”
Ericcson: “Scheduling Request in E-UTRAN”, 3GPP Draft, R1-070471, 3rd Generation Partnership Project (3GPP), vol. RAN WG1, no. Sorrento, Italy; Jan. 10, 2007, (Jan. 10, 2007), XP050104502.
Ericsson, “Text proposal on scheduling request triggering criterions for LTE,” R2-073210, 3GPP TSG-RAN WG2 #59, Athens , Greece, Aug. 20-24, 2007, pp. 1-2.
Ghosh, A. et al.; “Random Access Design for UMTS Air-Interface Evolution”, Vehicular Technology Conference, 2007. VTC2007-Spring.IEEE 65th Publication, Apr. 22-25, 2007, pp. 1041-1045.
LG Electronics Inc., “Security de-synchronization,” R2-073258, 3GPP TSG-RAN WG2 #59, Athens, Greece, Aug. 20-24, 2007 (retrieved on Aug. 18, 2007), pp. 1-2.
LG Electronics, “Overall control signaling structure for generic LTE TDD,” R1-071848, 3GPP TSG RAN WG1 LTE TDD Ad Hoc, Beijing, China, Apr. 17-20, 2007, pp. 1-4.
Motorola, “RLC Polling Related Issues,” 3GPP TSG-RAN WG2, R2-073538, Athens, Greece, Aug. 20-24, 2007, 2 pages.
Nec et al., “Need for MAC contention-resolution for non-initial access,” R2-073092, 3GPP TSG-RAN WG2 Meeting #59, Athens, Greece, Aug. 20-24, 2007, 3 pages.
Nokia, “System Information Change Indication,” R2-071739, 3GPP TSG-RAN WG2 Meeting #57bis, Kobe, Japan, May 7-11, 2007, pp. 1-3.
NTT Docomo, “Random Access Channel Structure for E-UTRA Uplink,” R2-061064, 3GPP TSG-RAN WG1 and WG2 Joing Meeting, Athens, Greece, Mar. 27-31, 2006, pp. 1-8.
NTT Docomo, Inc., “RA response format,” R2-080451, 3GPP TSG RAN WG2 #60bis, Sevilla, Spain, Jan. 14-18, 2008 (retrieved on Jan. 8, 2008), 2 pages.
Panasonic , “Random access design for E-UTRA uplink,” R1-061114, TSG-RAN WG1 Meeting#45, Shanghai, China, May 8-12, 2006, pp. 1-5.
RU-2291594-C2 not available; Abstract only provided, as well as corresponding W0-2004/042953-A1.
Siemens, “Signaling in DL for uplink resource allocation,” R1-061290,3GPP TSG RAN WG1#45, Shanghai, China, May 8-12, 2006 (retrieved on May 2, 2006), pp. 1-6.
Texas Instruments: “UL synchronization Management and Maintenance in E-UTRA”, 3GPP Draft: R1-072198_ULSYNC, 3rd Generation Partnership Project (3GPP); vol. RAN WG1, no. Kobe, Japan; May 1, 2007, (May 1, 2007), XP050105936.
Wu et al, Enhanced Random Access Response Formats In E-UTRN, U.S. Appl. No. 61/006,348.
3rd Generation Partnership Project; Technical Specification Group Radio Access Network, “Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification (Release 8),” 3GPP TS 36.32, V8.1.0, dated Mar. 2008, 30 pages.
3rd Generation Partnership Project; Technical Specification Group Radio Access Network, “Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control (RLC) protocol specification (Release 8),” 3GPP TS 36.322, V8.0.0, Dec. 2007, 35 pages.
Ericsson, “Format of Random Access Response,” R2-074938, 3GPP TSG-RAN WG2 #60, Jeju, Korea, dated Nov. 5-9, 2007, 4 pages.
Ericsson, “Clarification to the handling of large RLC status reports,” R2-082018, 3GPP TSG-RAN2 Meeting #61bis, Shenzhen, China, dated Mar. 31-Apr. 4, 2008, 4 pages.
Ericsson, “RLC status report format,” R2-074701, TSG-RAN WG2 Meeting #60, Jeju Island, Korea, dated Nov. 5-9, 2007, 3 pages.
LG Electronics Inc., NTT DoCoMo, “ACK_SN setting for short Status PDU,” R2-082133, 3GPP TSG-RAN WG2 #62, Kansas City, USA, dated May 5-9, 2008, 2 pages.
Motorola, “LTE Random Access Procedure,” R2-061463, 3GPP TSG-RAN WG2 #53, Shanghai, China, dated May 8-12, 2006, pp. 1-4.
Nokia Corporation, Nokia Siemens Networks, “Random Access Message Two,” R2-080948, 3GPP TSG-RAN WG2 Meeting #61, Sorrento, Italy, dated Feb. 11-15, 2008, 4 pages.
Nokia Siemens Networks, Nokia Corporation, “Open issues in RACH overload control,” R2-080221, 3GPP TSG-RAN WG2 Meeting #60bis, Sevilla, Spain, dated Jan. 14 -18, 2008, 5 pages.
TS 36.322 Editor (NTT DoCoMo, Inc.), “Miscellaneous corrections to TS 36.322,” R2-081700, 3GPP TSG-RAN2 Meeting #61bis, Shenzhen, China, dated Mar. 31-Apr. 4, 2008, 13 pages.
Kashima, Method and Apparatus for Providing Timing Alignment, U.S. Appl. No. 60/944,662.
Wu et al, Enhanced Random Access Rsponse Formats in E-UTRN, U.S. Appl. No. 61/006,348.
Nec, “Optimized buffer status reporting”, 3GPP TSG-RAN WG2#58bis Meeting, Orlando, FL, USA, Jun. 25-29, 2007, vol. R2-072515, pp. 1-6, XP002503220, www.3gpp.org.
Catt, Ritt, “Consideration on UL buffer reporting”, 3GPP TSG-RAN WG2#55, R2-062934, Oct. 9, 2006, pp. 1-3, XP002513924, http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_55/Documents/.
Wang et al., U.S. Appl. No. 60/976,139.
Sammour et al., U.S. Appl. No. 61/019,058.
Sadayuki Abeta et al., “Super 3G Technology Trends. Part 2: Research on Super 3G Technology”, NTT DoCoMo Technical Journal, vol. 8, No. 3, pp. 55-62, Dec. 2006, See Section 3; Figure 5.
Nokia, “System Information Distribution”, 3GPP TSG-RAN WG2 Ad Hoc Meeting on LTE, R2-061487, Cannes, France, pp. 1-3, Jun. 27-30, 2006, See Section 2.
LG Electronics, “Delivery of LTE System Information”, 3GPP TSG-RAN WG2 Ad Hoc on LTE, R2-061959, Cannes, France, pp. 1-4, Jun. 27-30, 2006, See Section 3.
XP050131180; ZTE; “Redundant Retransmission Restraint in RLC-AM” 3GPP Draft; Rs-061234.
XP014038519; “Digital Cellular Telecommunications System (Phase 2+); Functional Stage 2 Description of Location Services (LSC) in GERAN (3GPP TS 43.059 version 7.3.0 Release 7); ETSI TS 143 059.”
LG Electronics Inc: “UE State Transition in LTE_Active”, 3GPP Draft: R2-061002 UE State Transition in LTE_Active Mode, 3rd Generation Partnership Project (3GPP); vol. RAN WG2, No. Athens, Greece; 20061323 (Mar. 23, 2006), XP050130928.
Texas Instruments: “UL synchronization Management and Maintenance in E-UTRA”, 3GPP Draft; R1-072198_ULSYNC, 3rd Generation Partnership Project (3GPP); vol. RAN WG1, No. Kobe, Japan; May 1, 2007, XP050105936.
3GPP TSG RAN WG2 #59, NTTDoCoMo, Inc., “Buffer Status Report and Scheduling Request Triggers,” Aug. 20-24, 2007, Athens, Greece, R2-073574, four (4) pages.
3GPP TSG-RAN WG1 #48, QUALCOMM Europe, “Further Details on RACH Procedure,” Feb. 12-16, 2007, St. Louis, Missouri, R1-070649, pp. 1-4.
Provisional Applications (1)
Number Date Country
61025267 Jan 2008 US
Continuations (2)
Number Date Country
Parent 15826172 Nov 2017 US
Child 12475107 US
Parent 12362993 Jan 2009 US
Child 12475107 US
Reissues (2)
Number Date Country
Parent 12475107 May 2009 US
Child 17214041 US
Parent 12475107 May 2009 US
Child 15826172 US