Method of performing uplink synchronization in wireless communication system
Abstract
A method of performing uplink synchronization in a wireless communication system includes transmitting a random access preamble which is randomly selected from a set of random access preambles, receiving a random access response, the random access response comprising a random access preamble identifier corresponding to the random access preamble and a time alignment value for uplink synchronization, starting a time alignment timer after applying the time alignment value, starting a contention resolution timer after receiving the random access response, wherein contention resolution is not successful when the contention resolution timer is expired, and stopping the time alignment timer when the contention resolution timer is expired.

Term
1.7 yearsto projected expiry
Projected expiry 17 June 2028, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
12 claims: 3 independent, 9 dependent
- 1A method of performing uplink synchronization in a wireless communication system, the method comprising:transmitting a random access preamble which is randomly selected from a set of random access preambles;receiving a random access response, the random access response comprising a random access preamble identifier corresponding to the random access preamble and a time alignment value for uplink synchronization;starting a time alignment timer after applying the time alignment value;starting a contention resolution timer after receiving the random access response, wherein contention resolution is not successful when the contention resolution timer is expired;and stopping the time alignment timer when the contention resolution timer is expired.
- 5A method of performing uplink synchronization in a wireless communication system, the method comprising:transmitting a random access preamble which is randomly selected from a set of random access preambles;receiving a random access response, the random access response comprising a random access preamble identifier corresponding to the random access preamble;starting a time alignment timer after receiving a random access response;and stopping the time alignment timer when contention resolution is not successful.
- 9The method of clam 5, further comprising:transmitting a scheduled message after receiving the random access response, the scheduled message comprising a unique identifier.
Independent claims3
64 paragraphs, as filed
Technical Field
0001The present invention relates to wireless communications, and more particularly, to a method of performing uplink synchronization in a wireless communication system.
Background Art
0002Third generation partnership project (3GPP) mobile communication systems based on a wideband code division multiple access (WCDMA) radio access technology are widely spread all over the world. High-speed downlink packet access (HSDPA) that can be defined as a first evolutionary stage of WCDMA provides 3GPP with a radio access technique that is highly competitive in the mid-term future. However, since requirements and expectations of users and service providers are continuously increased and developments of competing radio access techniques are continuously in progress, new technical evolutions in 3GPP are required to secure competitiveness in the future. Reduction of cost per bit, increase of service availability, flexible use of frequency bands, simple structure and open interface, proper power consumption of a user equipment (UE), and the like are defined as requirements.
0003In general, there are one or more cells within the coverage of a base station (BS). One cell may include a plurality of UEs. A UE is generally subjected to a random access procedure to access a network. The random access procedure is performed by the UE for the following purposes: (1) initial access; (2) handover; (3) scheduling request; and (4) timing synchronization. However, this is for exemplary purposes only, and thus the content or number of purposes for performing the random access procedure may vary depending on systems.
0004The random access procedure can be classified into a contention based random access procedure and a non-contention based random access procedure. Major difference between the two random access procedures lies in whether a random access preamble is dedicatedly assigned to one UE. In the non-contention based access procedure, since a UE uses only the random access preamble dedicatedly assigned to the UE, contention (or collision) with another UE does not occur. The contention occurs when two or more UEs attempt the random access procedure by using the same random access preamble through the same resource. In the contention based random access procedure, there is a possibility of contention since a random access preamble used by the UEs is randomly selected.
0005In an orthogonal frequency division multiplexing (OFDM)-based wireless communication system, timing synchronization between a UE and a BS is important so as to minimize interference between users. The random access procedure is performed for uplink synchronization. While the random access procedure is performed, the UE is time-synchronized according to a time alignment value transmitted from the BS. When uplink synchronization is achieved, the UE runs a time alignment timer. If the time alignment timer is running, it is regarded that the UE and the BS are uplink-synchronized with each other. If the time alignment timer is expired or is not running, it is regarded that the UE and the BS are not synchronized with each other. In this case, uplink transmission cannot be achieved except for transmission of the random access preamble.
0006A random access failure may occur in the contention based random access procedure since there is always a possibility of contention. Therefore, a method is needed for performing uplink synchronization caused by the random access failure.
[Disclosure]
[Technical Problem]
0007The present invention provides a method of performing uplink synchronization while a contention based random access procedure is performed in a wireless communication system.
0008The present invention also provides a method of avoiding interference to other user equipments due to incorrect uplink synchronization in a wireless communication system.
Technical Solution
0009In an aspect, a method of performing uplink synchronization in a wireless communication system is provided. The method includes transmitting a random access preamble which is randomly selected from a set of random access preambles, receiving a random access response, the random access response comprising a random access preamble identifier corresponding to the random access preamble and a time alignment value for uplink synchronization, starting a time alignment timer after applying the time alignment value, starting a contention resolution timer after receiving the random access response, wherein contention resolution is not successful when the contention resolution timer is expired, and stopping the time alignment timer when the contention resolution timer is expired.
0010The method can further include transmitting a scheduled message, the scheduled message comprising a unique identifier and stopping the contention resolution timer when receiving a contention resolution message, the contention resolution message comprising an identifier corresponding to the unique identifier. The contention resolution timer may be started when transmitting the scheduled message.
0011In another aspect, a method of performing uplink synchronization in a wireless communication system is provided. The method includes transmitting a random access preamble which is randomly selected from a set of random access preambles, receiving a random access response, the random access response comprising a random access preamble identifier corresponding to the random access preamble, starting a time alignment timer after receiving a random access response and stopping the time alignment timer when contention resolution is not successful.
Advantageous Effects
0012Incorrect uplink synchronization can be avoided even if contention resolution is unsuccessful. Therefore, interference to other user equipments can be mitigated and service delay due to incorrect uplink synchronization can be prevented.
Description of Drawings
0013<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> shows a structure of a wireless communication system.</li><li><figref idref="f0002">FIG. 2</figref> is a diagram showing functional split between an evolved universal terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC).</li><li><figref idref="f0003">FIG. 3</figref> is a block diagram showing constitutional elements of a user equipment (UE).</li><li><figref idref="f0004">FIG. 4</figref> is a diagram showing a radio protocol architecture for a user plane.</li><li><figref idref="f0005">FIG. 5</figref> is a diagram showing a radio protocol architecture for a control plane.</li><li><figref idref="f0006">FIG. 6</figref> is a flow diagram showing a random access procedure.</li><li><figref idref="f0007">FIG. 7</figref> is a flow diagram showing a method of performing uplink synchronization according to an embodiment of the present invention.</li><li><figref idref="f0008">FIG. 8</figref> is a flow diagram showing a method of performing uplink synchronization according to another embodiment of the present invention.</li></ul>
[Mode for Invention]
0014<figref idref="f0001">FIG. 1</figref> shows a structure of a wireless communication system. The wireless communication system may have a network structure of an evolved-universal mobile telecommunications system (E-UMTS). The E-UMTS may be referred to as a long-term evolution (LTE) system. The wireless communication system can be widely deployed to provide a variety of communication services, such as voices, packet data, etc.
0015Referring to <figref idref="f0001">FIG. 1</figref>, an evolved-UMTS terrestrial radio access network (E-UTRAN) includes at least one base station (BS) 20 which provides a control plane and a user plane.
0016A user equipment (UE) 10 may be fixed or mobile, and may be referred to as another terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc. The BS 20 is generally a fixed station that communicates with the UE 10 and may be referred to as another terminology, such as an evolved node-B (eNB), a base transceiver system (BTS), an access point, etc. There are one or more cells within the coverage of the BS 20. Interfaces for transmitting user traffic or control traffic may be used between the BSs 20. Hereinafter, downlink is defined as a communication link from the BS 20 to the UE 10, and uplink is defined as a communication link from the UE 10 to the BS 20.
0017The BSs 20 are interconnected by means of an X2 interface. The BSs 20 are also connected by means of an S1 interface to an evolved packet core (EPC), more specifically, to a mobility management entity (MME)/serving gateway (S-GW) 30. The S1 interface supports a many-to-may relation between the BS 20 and the MME/S-GW 30.
0018<figref idref="f0002">FIG. 2</figref> is a diagram showing functional split between the E-UTRAN and the EPC.
0019Referring to <figref idref="f0002">FIG. 2</figref>, slashed boxes indicate radio protocol layers and white boxes indicate functional entities of the control plane.
0020The BS performs the following functions: (1) functions for radio resource management (RRM) such as radio bearer control, radio admission control, connection mobility control, and dynamic allocation of resources to the UE; (2) Internet protocol (IP) header compression and encryption of user data streams; (3) routing of user plane data to the S-GW; (4) scheduling and transmission of paging messages; (5) scheduling and transmission of broadcast information; and (6) measurement and measurement reporting configuration for mobility and scheduling.
0021The MME performs the following functions: (1) distribution of paging messages to the BSs; (2) security control; (3) idle state mobility control; (4) system architecture evolution (SAE) bearer control; and (5) ciphering and integrity protection of non-access stratum (NAS) signaling.
0022The S-GW performs the following functions: (1) termination of a user plane packet for paging; and (2) user plane switching for the support of UE mobility.
0023<figref idref="f0003">FIG. 3</figref> is a block diagram showing constitutional elements of the UE. A UE 50 includes a processor 51, a memory 52, a radio frequency (RF) unit 53, a display unit 54, and a user interface unit 55. Layers of a radio interface protocol are implemented in the processor 51. The processor 51 provides the control plane and the user plane. The function of each layer can be implemented in the processor 51. The memory 52 is coupled to the processor 51 and stores an operating system, applications, and general files. The display unit 54 displays a variety of information of the UE 50 and may use a well-known element such as a liquid crystal display (LCD), an organic light emitting diode (OLED), etc. The user interface unit 55 can be configured with a combination of well-known user interfaces such as a keypad, a touch screen, etc. The RF unit 53 is coupled to the processor 51 and transmits and/or receives radio signals.
0024Layers of a radio interface protocol between the UE and the network can be classified into L1 layer (a first layer), L2 layer (a second layer), and L3 layer (a third layer) based on the lower three layers of the open system interconnection (OSI) model that is well-known in a communication system. A physical layer, or simply a PHY layer, belongs to the first layer and provides an information transfer service through a physical channel. A radio resource control (RRC) layer belongs to the third layer and serves to control radio resources between the UE and the network. The UE and the network exchange RRC messages via the RRC layer.
0025<figref idref="f0004">FIG. 4</figref> is a diagram showing a radio protocol architecture for the user plane. <figref idref="f0005">FIG. 5</figref> is a diagram showing a radio protocol architecture for the control plane. They illustrate an architecture of a radio interface protocol between the UE and the E-UTRAN. The user plane is a protocol stack for user data transmission. The control plane is a protocol stack for control signal transmission.
0026Referring to <figref idref="f0004">FIGs. 4</figref> and <figref idref="f0005">5</figref>, a PHY layer belongs to the first layer and provides an upper layer with an information transfer service through a physical channel. The PHY layer is coupled with a medium access control (MAC) layer, i.e., an upper layer of the PHY layer, through a transport channel. Data is transferred between the MAC layer and the PHY layer through the transport channel. Between different PHY layers (i.e., a PHY layer of a transmitter and a PHY layer of a receiver), data are transferred through the physical channel. The PHY layer can be modulated by orthogonal frequency division multiplexing (OFDM). Time and/or frequency can be utilized as radio resources.
0027The MAC layer belongs to the second layer and provides services to a radio link control (RLC) layer, i.e., an upper layer of the MAC layer, through a logical channel. The RLC layer in the second layer supports reliable data transfer. There are three operating modes in the RLC layer, that is, a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM) according to a data transfer method. An AM RLC provides bidirectional data transmission services and supports retransmission when the transfer of a RLC protocol data unit (PDU) fails.
0028A packet data convergence protocol (PDCP) layer belongs to the second layer and performs a header compression function. When transmitting an IP packet such as an IPv4 packet or an IPv6 packet, a header of the IP packet may contain relatively large and unnecessary control information. The PDCP layer reduces a header size of the IP packet so as to efficiently transmit the IP packet.
0029A radio resource control (RRC) layer belongs to the third layer and is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of radio bearers (RBs). A RB is a service provided by the second layer for data transmission between the UE and the E-UTRAN. When an RRC connection is established between an RRC layer of the UE and an RRC layer of the network, it is called that the UE is in an RRC connected mode. When the RRC connection is not established yet, it is called that the UE is in an RRC idle mode.
0030A non-access stratum (NAS) layer belongs to an upper layer of the RRC layer and serves to perform session management and mobility management.
0031A downlink transport channel is a channel through which data is transmitted from the network to the UE. Examples of the downlink transport channel include a broadcast channel (BCH) for transmitting system information and a downlink-shared channel (DL-SCH) for transmitting user traffic or control messages. User traffic of downlink multicast (or broadcast) services or control messages can be transmitted on the DL-SCH or a downlink multicast channel (MCH). An uplink transport channel is a channel through which data is transmitted from the UE to the network. Examples of the uplink transport channel include a random access channel (RACH) for transmitting initial control messages and an uplink-shared channel (UL-SCH) for transmitting user traffic or control messages.
0032A downlink physical channel is mapped to the downlink transport channel. Examples of the downlink physical channel include a physical broadcast channel (PBCH) for transmitting information of the BCH, a physical multicast channel (PMCH) for transmitting information of the MCH, a physical downlink shared channel (PDSCH) for transmitting information of the PCH and the DL-SCH, and a physical downlink control channel (PDCCH) for transmitting control information such as downlink or uplink scheduling grant, which are provided from the first layer and the second layer. The PDCCH is also referred to as a downlink L1/L2 control channel. An uplink physical channel is mapped to the uplink transport channel. Examples of the uplink physical channel include a physical uplink shared channel (PUSCH) for transmitting information of the UL-SCH, a physical random access channel (PRACH) for transmitting information of the RACH, and a physical uplink control channel (PUCCH) for transmitting control information such as hybrid automatic repeat request (HARQ) acknowledgement (ACK)/nonacknowledgement (NACK) signals, a scheduling request signal, and a channel quality indicator (CQI), which are provided from the first layer and the second layer.
0033Now, the random access procedure will be described. A UE performs the random access procedure in the process of performing the following operations, such as, (1) initial access, (2) handover, (3) transmission of downlink data to a non-synchronized UE, (4) transmission of uplink data by the non-synchronized UE, and (5) restoration of radio link failure.
0034<figref idref="f0006">FIG. 6</figref> is a flow diagram showing the random access procedure.
0035Referring to <figref idref="f0006">FIG. 6</figref>, in step S110, a UE transmits a random access preamble to a BS through a selected random access resource by using system information received from the BS. The system information includes information on a set of available random access preambles. The random access preamble transmitted by the UE is selected from the set of random access preambles.
0036In step S120, the BS transmits a random access response through a DL-SCH. The random access response includes a time alignment value for uplink synchronization of the UE, uplink radio resource allocation information, an index of the random access preamble received to identify the UE performing the random access procedure, and a temporary identifier (e.g., temporary cell-radio network temporary identity (C-RNTI)) of the UE.
0037In step S130, the UE applies the time alignment value, and transmits a scheduled message including a unique identifier of the UE to the BS by using the uplink radio resource allocation information. The unique identifier of the UE may be the C-RNTI, a SAE temporary mobile station identifier (S-TMSI), or an upper-layer identifier. The unique identifier is also referred to as a contention resolution identifier since it is used for contention resolution.
0038In step S140, after receiving the scheduled message, the BS transmits to the UE a contention resolution message including the unique identifier of the UE.
0039Due to the limited number of available random access preambles, contention occurs in the random access procedure. Since it is not possible to assign unique random access preambles to all UEs located in a cell, the UEs select one random access preamble from the set of the available random access preambles and then transmit the selected random access preamble. Accordingly, two or more UEs can select and transmit the same random access preamble through the same random access resource. This is a case where contention occurs. Upon receiving the random access preamble, the BS transmits the random access response for the random access preamble in a state where the BS does not know the occurrence of contention. However, since contention has occurred, two or more UEs receive the same random access response and thus transmit scheduled messages according to information included in the random access response. That is, the two or more UEs transmit different scheduled messages according to the uplink radio resource allocation information included in the random access response. In this case, the BS may fail to receive all of the scheduled messages, or may successfully receive only a scheduled message of a specific UE according to the location or transmit (Tx) power of the UEs. If the BS successfully receives the scheduled message, the BS transmits the contention resolution message by using the unique identifier of the UE, wherein the unique identifier is included in the scheduled message. The UE can know that the contention resolution is successful when the unique identifier of the UE is received. The contention resolution allows the UE to know whether the contention is successful or not in the contention based random access procedure.
0040A contention resolution timer is used for the contention resolution. The contention resolution timer starts after the random access response is received. The contention resolution timer may start when the UE transmits the scheduled message. When the contention resolution timer is expired, it is determined that the contention resolution is unsuccessful, and thus a new random access procedure is performed. When the UE receives the contention resolution message including the unique identifier of the UE, the contention resolution timer stops, and the UE determines that the contention resolution is successful. If the UE already has a unique cell identifier (e.g., C-RNTI) before the random access procedure is performed, the UE transmits the scheduled message including the cell identifier of the UE and then starts the contention resolution timer. If the UE receives a PDCCH, which is addressed by the cell identifier of the UE, before the contention resolution timer is expired, the UE determines that the contention is successful and then finishes the random access procedure without errors. If the UE does not have the C-RNTI, the upper-layer identifier may be used as the unique identifier. After transmitting the scheduled message including the upper-layer identifier, the UE starts the contention resolution timer. If the contention resolution message including the upper-layer identifier of the UE is received on the DL-SCH before the contention resolution timer is expired, the UE determines that the random access procedure is successful. The contention resolution message is received by using the PDCCH addressed by the temporary C-RNTI. Otherwise, if the aforementioned contention resolution is not received on the DL-SCH until the contention resolution timer is expired, the UE determines that the contention is unsuccessful.
0041Now, time alignment for uplink synchronization will be described. In an OFDM-based system, timing synchronization between a UE and a BS is important so as to minimize interference between users.
0042The random access procedure is one of uplink time synchronization methods. That is, the BS measures the time alignment value through the random access preamble transmitted by the UE, and provides the time alignment value to the UE through the random access response. Upon receiving the random access response, the UE applies the time alignment value and starts the time alignment timer. Time synchronization between the UE and the BS is maintained while the time alignment timer is running. If the time alignment timer is expired or is not running, it is regarded that the time synchronization between the UE and the BS is not maintained. If the time alignment timer is expired and is not running, the UE can transmit only the random access preamble, and any other uplink transmission cannot be achieved.
0043When contention occurs in the process of performing the random access procedure, the UE may apply an incorrect time alignment value. If the UE is not time-synchronized with the BS before the UE transmits the random access preamble, the random access preamble may be mistakenly transmitted in uplink because of the time alignment timer currently running.
0044First, in a state whether uplink synchronization is not achieved between the UE and the BS, the UE transmits to the BS the random access preamble which is randomly selected, and receives the random access response for the random access preamble. Even if contention occurs, the UE can receive the random access response. In this case, since the UE cannot know the occurrence of contention, the UE applies to the UE itself the time alignment value included in the received random access response, and starts the time alignment timer. Subsequently, the UE transmits to the BS the scheduled message including the unique identifier of the UE and starts the contention resolution timer. If the UE does not receive the contention resolution message addressed by the unique identifier of the UE until the contention resolution timer is expired, the UE retries the random access procedure. However, since the time alignment timer is continuously running, the UE may transmit uplink data when the BS transmits downlink data. This is because the UE determines that uplink synchronization is achieved by the time alignment timer currently running, even in a case where uplink synchronization is not achieved. The incorrect uplink synchronization may result in interference to other users during transmission.
0045<figref idref="f0007">FIG. 7</figref> is a flow diagram showing a method of performing uplink synchronization according to an embodiment of the present invention. At first, a UE is in a state where a time alignment timer is expired or is not running. This is a case where a contention based random access procedure starts when the UE attempts initial network entry or when a cell is searched for again due to a radio link failure.
0046Referring to <figref idref="f0007">FIG. 7</figref>, in step S210, the UE transmits to a BS a random access preamble which is randomly selected. In step S220, in response to the random access preamble, the BS transmits a random access response to the UE. The random access response includes uplink radio resource allocation information, a random access preamble identifier, a time alignment value, and a temporary C-RNTI. In step S230, the UE applies the time alignment value included in the random access response, and starts the time alignment timer.
0047In step S240, through the uplink radio resource allocation information included in the random access response, the UE transmits to the BS a scheduled message including a unique identifier of the UE. In step S250. the UE transmits the scheduled message and then starts a contention resolution timer.
0048In step S260, if the UE does not receive a contention resolution message including the unique identifier of the UE until the contention resolution timer is expired, the UE stops the time alignment timer. In this case, the UE may determine that the contention is unsuccessful, and thus retry the random access procedure.
0049If the random access failure occurs, the UE stops the time alignment timer which has been previously running. This is because the previously received time alignment value can be for another UE. Therefore, since the time alignment timer is stopped, uplink transmission is prevented from using the incorrect time alignment value.
0050<figref idref="f0008">FIG. 8</figref> is a flow diagram showing a method of performing uplink synchronization according to another embodiment of the present invention.
0051Referring to <figref idref="f0008">FIG. 8</figref>, in step S310, a UE transmits to a BS a random access preamble which is randomly selected. In step S320, in response to the random access preamble, the BS transmits a random access response to the UE. The random access response includes a time alignment value and temporary C-RNTI. In step S330, the UE applies the time alignment value and starts a time alignment timer. In step S340, the UE transmits to the BS a scheduled message including a unique identifier of the UE through uplink radio resource allocation information included in the random access response. In step S350, after transmitting the scheduled message, the UE starts a contention resolution timer.
0052In step S360, before the contention resolution timer is expired, the UE receives a contention resolution message indicated by PDCCH addressed by the temporary C-RNTI. The contention resolution message includes a contention resolution identifier. In step S370, the UE determines whether the contention is successful through the contention resolution identifier. For example, the contention resolution identifier can be compared with the identifier included in the scheduled message. If the two identifiers are not identical, it is determined that the contention is unsuccessful.
0053In step S380, if it is determined that the contention is unsuccessful, the UE stops the time alignment timer. In this case, the UE may retry the random access procedure or may report to an upper layer that the contention is unsuccessful.
0054If the contention is unsuccessful in the random access procedure, the UE stops the time alignment timer currently running. Accordingly, a problem can be solved in which the time alignment timer continuously runs even when uplink synchronization is not achieved.
0055The steps of a method described in connection with the embodiments disclosed herein may be implemented by hardware, software or a combination thereof. The hardware may be implemented by an application specific integrated circuit (ASIC) that is designed to perform the above function, a digital signal processing (DSP), a programmable logic device (PLD), a field programmable gate array (FPGA), a processor, a controller, a microprocessor, the other electronic unit, or a combination thereof. A module for performing the above function may implement the software. The software may be stored in a memory unit and executed by a processor. The memory unit or the processor may employ a variety of means that is well known to those skilled in the art.
0056As the present invention may be embodied in several forms without departing from the spirit or essential characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be construed broadly within its spirit and scope as defined in the appended claims. Therefore, all changes and modifications that fall within the metes and bounds of the claims, or equivalence of such metes and bounds are intended to be embraced by the appended claims.
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| GB2462011B | Cited by | United Kingdom | Search report |
| EP2512198A1 | Cited by | European Patent Office (EPO) | Search report |
| US8958755B2 | Cited by | United States of America | Applicant |
| US12452804B2 | Cited by | United States of America | Applicant |
| US9144068B2 | Cited by | United States of America | Applicant |
| GB2462011A | Cited by | United Kingdom | Search report |
| US10966242B2 | Cited by | United States of America | Applicant |
| US10499421B2 | Cited by | United States of America | Applicant |
| US8243672B2 | Cited by | United States of America | Applicant |
| US9357561B2 | Cited by | United States of America | Applicant |
| US9930724B2 | Cited by | United States of America | Applicant |
| US9125157B2 | Cited by | United States of America | Applicant |
| EP2512198A4 | Cited by | European Patent Office (EPO) | Search report |
| US11337246B2 | Cited by | United States of America | Applicant |
| US10420047B2 | Cited by | United States of America | Applicant |
| EP3923667A1 | Cited by | European Patent Office (EPO) | Search report |
| US8432865B2 | Cited by | United States of America | Applicant |
| WO2015142555A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US10362627B2 | Cited by | United States of America | Applicant |
| EP2648471A4 | Cited by | European Patent Office (EPO) | Search report |
| US10966185B2 | Cited by | United States of America | Applicant |
2,153 members in 28 offices; this record represents the family
Members2,153
| Document | Office | Kind | |
|---|---|---|---|
| US5366355A | United States of America | A | |
| EP0652369A1 | European Patent Office (EPO) | A1 | |
| KR950014588A | Republic of Korea | A | |
| BR9404396A | Brazil | A | |
| BR9404396A | Brazil | A | |
| JPH07180656A | Japan | A | |
| JP2675268B2 | Japan | B2 | |
| EP0652369B1 | European Patent Office (EPO) | B1 | |
| DE69408632D1 | Germany | D1 | |
| KR0131960B1 | Republic of Korea | B1 | |
| DE69408632T2 | Germany | T2 | |
| KR20070023203A | Republic of Korea | A | |
| AU2006282195A1 | Australia | A1 | |
| US2007047486A1 | United States of America | A1 | |
| WO2007024098A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200718230A | Taiwan Province of China | A | |
| WO2007052971A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007052972A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20070073571A | Republic of Korea | A | |
| KR20070073577A | Republic of Korea | A | |
| KR20070073578A | Republic of Korea | A | |
| KR20070073588A | Republic of Korea | A | |
| KR20070073608A | Republic of Korea | A | |
| KR20070073627A | Republic of Korea | A | |
| KR20070073635A | Republic of Korea | A | |
| AU2007203852A1 | Australia | A1 | |
| AU2007203861A1 | Australia | A1 | |
| WO2007078051A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007078142A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007078155A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007078156A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007078164A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007078165A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007078171A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007078172A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007078173A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007078174A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200727614A | Taiwan Province of China | A | |
| KR20070076374A | Republic of Korea | A | |
| KR20070076375A | Republic of Korea | A | |
| TW200729785A | Taiwan Province of China | A | |
| TW200729987A | Taiwan Province of China | A | |
| KR20070080541A | Republic of Korea | A | |
| KR20070080544A | Republic of Korea | A | |
| KR20070080545A | Republic of Korea | A | |
| KR20070080552A | Republic of Korea | A | |
| KR20070080553A | Republic of Korea | A | |
| KR20070080556A | Republic of Korea | A | |
| KR20070080557A | Republic of Korea | A | |
| AU2007212916A1 | Australia | A1 | |
| AU2007212923A1 | Australia | A1 | |
| TW200731705A | Taiwan Province of China | A | |
| US2007191019A1 | United States of America | A1 | |
| US2007191020A1 | United States of America | A1 | |
| WO2007091795A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091810A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091811A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091823A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091824A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091831A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007091838A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091839A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091840A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007091841A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200735590A | Taiwan Province of China | A | |
| TW200735680A | Taiwan Province of China | A | |
| WO2007108630A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007108651A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007108655A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007108660A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20070095755A | Republic of Korea | A | |
| TW200737812A | Taiwan Province of China | A | |
| TW200737824A | Taiwan Province of China | A | |
| TW200737825A | Taiwan Province of China | A | |
| TW200737847A | Taiwan Province of China | A | |
| TW200737871A | Taiwan Province of China | A | |
| TW200737872A | Taiwan Province of China | A | |
| TW200737886A | Taiwan Province of China | A | |
| TW200737887A | Taiwan Province of China | A | |
| TW200738005A | Taiwan Province of China | A | |
| TW200738017A | Taiwan Province of China | A | |
| TW200742382A | Taiwan Province of China | A | |
| TW200742468A | Taiwan Province of China | A | |
| KR20070107560A | Republic of Korea | A | |
| WO2007126192A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200743396A | Taiwan Province of China | A | |
| TW200746674A | Taiwan Province of China | A | |
| TW200746699A | Taiwan Province of China | A | |
| TW200746754A | Taiwan Province of China | A | |
| TW200746773A | Taiwan Province of China | A | |
| KR20070121505A | Republic of Korea | A | |
| KR20070121513A | Republic of Korea | A | |
| KR20070121515A | Republic of Korea | A | |
| KR20070121567A | Republic of Korea | A | |
| WO2007148881A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007148895A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007148933A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007148934A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2007148935A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200803304A | Taiwan Province of China | A |
71 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Invalidated european patentMG4D | MG4D | LT | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Definitive protectionFG2A | FG2A | ES | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| Translation filed for an european patent granted for nl, confirming art. 52 par. 1 or 6 of the patents act 1995GrantedT3 | T3 | NL | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04B0007260000R079 | R079 | DE | |
| Designated contracting states (corrected)RBV | RBV | EP | |
| Designation fees paidAKX | AKX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2015478
- Application
- 80109952
Titles3
- German
- Verfahren zur Durchführung von Aufwärtsstreckensynchronisation in einem drahtlosen Kommunikationssystem
- English
- Method of performing uplink synchronization in wireless communication system
- French
- Procédé pour effectuer une synchronisation de liaison montante dans un système de communication sans fil
Classification
- CPC, 9
- H04W56/0005
- H04W56/0015
- H04B7/2662
- H04W56/0045
- H04W74/0833
- H04W74/002
- H04B7/2668
- H04W56/00
- H04W74/08
- IPC, 4
- H04B7 26
- H04W56 00
- H04W74 00
- H04W74 0833
Designated states38
- Contracting states, 34
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
and 10 moreShow fewer
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye
- Extension states, 4
- Albania
- Bosnia and Herzegovina
- North Macedonia
- Serbia