EP3684113B1 - Support of multiple timing advance groups for user equipment in carrier aggregation in lte - Google Patents

Support of multiple timing advance groups for user equipment in carrier aggregation in lte Download PDF

Info

Publication number
EP3684113B1
EP3684113B1 EP19214979.7A EP19214979A EP3684113B1 EP 3684113 B1 EP3684113 B1 EP 3684113B1 EP 19214979 A EP19214979 A EP 19214979A EP 3684113 B1 EP3684113 B1 EP 3684113B1
Authority
EP
European Patent Office
Prior art keywords
timing advance
component carrier
advance group
random access
downlink component
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19214979.7A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3684113A1 (en
Inventor
Wanshi Chen
Peter Gaal
Masato Kitazoe
Jelena M. Damnjanovic
Juan Montojo
Hao Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3684113A1 publication Critical patent/EP3684113A1/en
Application granted granted Critical
Publication of EP3684113B1 publication Critical patent/EP3684113B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, 3GPP Long Term Evolution (LTE) systems, and orthogonal frequency-division multiple access (OFDMA) systems.
  • CDMA code-division multiple access
  • TDMA time-division multiple access
  • FDMA frequency-division multiple access
  • LTE 3GPP Long Term Evolution
  • OFDMA orthogonal frequency-division multiple access
  • a wireless multiple-access communications system may include a number of base stations, each simultaneously supporting communication for multiple mobile terminals.
  • Base stations may communicate with user equipment on downstream and upstream links.
  • Each base station has a coverage range, which may be referred to as the coverage area of the cell.
  • Some wireless multiple-access communications systems may utilize carrier aggregation, where multiple component carriers are aggregated and used together for transmission between base stations and user equipment. To achieve proper timing for transmission and reception on these different carriers, timing advance information may be distributed from base station to a user equipment to allow the device to account for propagation delay and/or delay due to other factors (e.g. , repeaters) on different carriers. Timing advance information can help ensure synchronized reception timing of the uplink stream links transmitted from multiple mobile terminals.
  • the multiple component carriers may be aggregated into different timing advance groups. In some cases, the multiple component carriers may be aggregated into different timing advance groups based on having similar delay characteristics. Synchronization issues, however, may arise for timing advance groups depending on the nature of the component carriers within a given timing advance group.
  • Independent claim 1 defines a method performed by a user equipment.
  • Independent claim 8 defines a corresponding apparatus.
  • Independent claim 15 defines a corresponding computer product.
  • the claimed method may be implemented utilizing a variety of wireless communications systems that may include means for performing one or more of the methods, wireless communications devices that may include a processor configured to perform oneor more of the methods, and/or computer program products including a computer readable storage medium may that includes code to perform one or more of the methods.
  • Timing advance group synchronization information across multiple timing advance groups may be provided.
  • Support for performing random access procedures in relation to timing advance groups that may not include a primary component carrier may be provided in some designs.
  • Timing advance group indexes may be utilized to enable cross-carrier random access procedure management.
  • Other aspects may support parallel random access procedures across multiple timing advance groups.
  • a reference downlink component carrier for timing within a timing advance group may be provided in some cases.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Code Division Multiple Access
  • SC-FDMA Code Division Multiple Access
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases 0 and A are commonly referred to as CDMA2000 IX, IX, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the systems and radio technologies mentioned above, as well as other systems and radio technologies.
  • the description above describes an LTE and/or LTE-Advanced system for purposes of examples, and LTE terminology is used in much of the description above, although the techniques are applicable beyond LTE applications.
  • FIG. 1 a block diagram illustrates an example of a wireless communications system 100.
  • the system 100 includes base transceiver stations 105, disposed in cells 110, mobile user equipment 115 (UEs), controller 120, and core network 125.
  • UE mobile user equipment
  • controller 120 controller 120
  • core network 125 core network
  • the system 100 may support operation on multiple carriers (waveform signals of different frequencies) and/or carrier aggregation.
  • a user equipment 115 may be configured by a serving base station 105 to communicate using multiple component carriers (CCs).
  • the CCs configured for the UE 115 may include uplink CCs and downlink CCs, which may be further described as primary component carriers (PCCs) or secondary component carriers (SCCs).
  • PCCs primary component carriers
  • SCCs secondary component carriers
  • the PCC primary component carriers
  • SCCs secondary component carriers
  • these different CCs may be aggregated into different timing advance groups based on different factors, such as their delay characteristics. Different embodiments may address different synchronization issues that may arise for timing advance groups depending on the nature of the component carriers within a given timing advance group.
  • the base stations 105 can wirelessly communicate with the user equipment 115 via a base station antenna.
  • the base stations 105 may be configured to communicate with the user equipment 115 under the control of the controller 120 via multiple carriers.
  • Each of the base stations 105 can provide communication coverage for a respective geographic area, here the cells 110-a, 110-b, or 110-c.
  • the system 100 may include base stations 105 of different types, e.g., macro, pico, and/or femto base stations.
  • the base stations 105 may include Node B, Home Node B, eNode B, and/or Home eNode B base stations.
  • the user equipment 115 can be dispersed throughout the cells 110.
  • the user equipment 115 may be referred to as mobile stations, mobile devices, user equipment (UE), or subscriber units.
  • the user equipment 115 here include cellular phones and a wireless communication device, but can also include personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, etc.
  • PDAs personal digital assistants
  • the user equipment 115 may operate on (are "camped" on) a macro or similar network facilitated by multiple macro base stations 105.
  • Each macro base station 105 may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by terminals with a service subscription.
  • System 100 may be an LTE system that supports multiple timing advance groups for user equipment 115 in carrier aggregation.
  • carrier aggregation multiple component carriers may be aggregated and used together for transmission between base stations 105 and UEs 115.
  • timing advance information may be distributed from base stations 105 to UEs 115 to allow the UEs 115 to account for propagation delay and/or delay due to other factors (e.g. , repeaters) on different carriers.
  • Timing advance information can help ensure synchronized reception timing of the uplink stream links transmitted from multiple UEs 115.
  • the multiple component carriers (CCs) may be aggregated into different timing advance groups.
  • the multiple component carriers may be aggregated into different timing advance groups based on having similar delay characteristics. Synchronization issues, however, may arise for timing advance groups depending on the nature of the component carriers within a given timing advance group.
  • System 100 may provide different solutions to these problems in accordance with various embodiments.
  • different CCs may have different delay characteristics for UEs 115.
  • Multiple CCs may be aggregated into different timing advance groups based on having similar delay characteristics.
  • Uplink transmissions from multiple UEs115 generally need to be properly aligned. This generally involves utilizing one or more references for timing adjustments.
  • One natural approach may involve utilizing SIB2 linkage between uplink CCs and downlink CCs.
  • timing advance groups CCs with similar characteristics can be grouped together. Different timing advance groups may thus involve different considerations with respect to timing references, such as a reference CC. For example, a secondary CC can be activated and deactivated, while a primary CC is generally always activated. In some cases, a system may benefit through not providing UEs 115 autonomy in selecting a reference CC. Instead, a PCC may be utilized as a reference CC in general. While a PCC may be utilized as a reference CC across different timing advance groups, different implementations may utilize different offsets with respect to the PCC for CCs in different timing advance groups. As discussed in more detail below, determining a reference downlink CC, such as a PCC, may be based in part on a Radio Resource Control (RRC) configuration by user equipment 115.
  • RRC Radio Resource Control
  • user equipment 115 may be configured for utilizing timing advance group synchronization information across multiple timing advance groups.
  • User equipment 115 may be configured to identify multiple component carriers as part of a carrier aggregation operation.
  • the multiple component carriers may include one or more downlink component carriers and two or more uplink component carriers.
  • Multiple timing advance groups may be determined by user equipment 115. Each component carrier in the multiple component carriers may be included in one of the timing advance groups.
  • a first timing advance group from the multiple timing advance groups may be identified by user equipment 115.
  • a reference downlink component carrier may be determined for the first timing advance group based at least in part on a RRC configuration by user equipment 115. The determined reference downlink component carrier may be utilized by user equipment 115 for timing adjustment within at least the first timing advance group.
  • user equipment 115 may receive from base station 105 an indication of a primary downlink component carrier through the RRC configuration.
  • the primary downlink component carrier may be the determined reference downlink component carrier.
  • User equipment 115 may utilize the primary downlink component carrier for timing adjustment within a second timing advance group from the multiple timing advance groups.
  • the primary downlink component carrier may be included in the second timing advance group.
  • one or more downlink component carriers of the one or more identified downlink carriers is included in the first timing advance group. Determining the reference downlink component carrier by user equipment 115 may be based on an RRC configuration for the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined by user equipment 115 to be a downlink component carrier with a smallest cell index of multiple cell indices configured for each one of the one or more downlink component carriers in the first timing advance group.
  • User equipment 115 may determine the reference downlink component carrier from a set of activated downlink component carriers.
  • the one or more downlink component carriers and the two or more uplink component carriers may be associated with two or more bands.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers of the same band or similar band.
  • the reference downlink component carrier may be determined to be a downlink component carrier of the same or similar band as an uplink component carrier associated with a random access attempt for the first timing advance group. group.
  • User equipment 115 may perform multiple random access procedures in parallel with respect to two or more of the multiple timing advance groups.
  • Performing the multiple random access procedures may include performing a first random access procedure linked with the first timing advance group; and/or performing a second random access procedure linked with a second timing advance group of the multiple timing advance groups, where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • User equipment 115 may initiate a non-contention based random access procedure on an uplink component carrier within the first timing advance group through utilizing a downlink control channel transmitted on a downlink component carrier that is not linked with the uplink component carrier via a system information block broadcast.
  • a cross-carrier indication field may be included in the downlink control channel to enable cross-carrier scheduling.
  • the reference downlink component carrier for the first timing advance group may be determined by user equipment 115 from a set of downlink component carriers with a similar delay due to downlink repeaters.
  • the reference downlink component carrier for the first timing advance group may be determined by user equipment 115 from a set of downlink component carriers with a same carrier type where the carrier type includes at least a legacy carrier type or a new carrier type.
  • the reference downlink component carrier for the first timing advance group may be determined by user equipment 115 from a set of downlink component carriers with a similar activity factor.
  • System 100 may take into account different characteristics of a component carrier (e.g., whether it is equipped with a repeater, whether it is always on or periodically turned off, whether it is a new or legacy carrier type, etc.) in determining the reference downlink component carrier.
  • a component carrier may be equipped with a repeater while another component carrier is not.
  • the component carriers of the same or similar delay characteristics due to repeaters may be determined to be possible candidates for the reference downlink component carrier for the given timing advance group.
  • Different component carriers may have different activity factors.
  • a component carrier may periodically be turned on and carries much less frequent downlink information compared with a regular carrier. It may then be preferable to avoid using this component carrier as the reference downlink component carrier.
  • a component carrier may be of a legacy carrier type and another can be of a new carrier type. Carriers of the same type may be determined to be possible candidates for the reference downlink component carrier for a given timing advance group.
  • base stations 105 and/or user equipment 115 may be configured to support multiple timing advance (TA) groups in connection with random access procedures. For example, different timing advance information may be transmitted to user equipment 115 for different groups of uplink carriers as part of the random access process. First timing advance information may be applicable to a first subset of uplink carriers, while second timing advance information may be applicable to a second, different subset of uplink carriers (e.g., due to a repeater) configured for a particular user equipment 115.
  • a user equipment 115 may support two or more timing advance groups and, in some aspects, the user equipment 115 may conduct parallel random access procedures to obtain timing adjustment information applicable to the carriers in each group. Some timing advance groups may not include the primary component carrier, and different specifications may be applicable to such groups.
  • system 100 can support random access procedures for timing advance groups without a primary component carrier.
  • random access procedures between base stations 105 and user equipment 115 may utilize messages in different search spaces and/or different component carriers. Some messages may be transmitted in a user equipment-specific search space ("UESS"). Other messages may be transmitted in a common search space ("CSS") on the primary component carrier. Additional embodiments may utilize a common search space on a secondary component carrier. Some embodiments may utilize non-contention based random access procedures, while other embodiments may utilize contention based random access procedures. More details are discussed herein with respect to providing support for random access for timing advance groups without a primary carrier component.
  • timing advance group indexes to enable cross-carrier random access procedure management.
  • a base station 105 may transmit a random access response to a user equipment 115 that includes a timing advance group index.
  • the user equipment 115 may determine a carrier with which to complete the random access procedure.
  • Timing advance group index information may be facilitated using timing advance group index information. More details are discussed herein with respect to utilizing timing advance group indexes to enable cross-carrier random access procedure management.
  • Some embodiments support parallel random access procedures across multiple timing advance groups. For example, multiple parallel random access procedures may occur between base station 105 and user equipment 115. Some embodiments may utilize power prioritization to facilitate these overlapping access procedures. Some embodiments may provide for an Aperiodic Channel Quality Indicator (A-CQI) being triggered within these parallel random access procedures. More details are discussed herein with respect to supporting parallel random access procedures across multiple timing advance groups.
  • A-CQI Aperiodic Channel Quality Indicator
  • Some embodiments provide for a reference downlink component carrier for timing within a timing advance group.
  • user equipment 115 may utilize a reference downlink component carrier from base station 105 for timing within a timing advance group. More details are discussed herein with respect to providing for a reference downlink component carrier for timing within a timing advance group.
  • FIG. 2 is a block diagram of a wireless communication system 200 including a base station 105-a and a user equipment 115-a.
  • This system 200 may be an example of the system 100 of FIG. 1 .
  • the base station 105-a may be equipped with antennas 234-a through 234-x, and the user equipment 115-a may be equipped with antennas 252-a through 252-n.
  • a transmit processor 220 may receive data from a data source.
  • the transmit processor 220 and/or processor 240 may process and/or transmit data.
  • the transmit processor 220 may also generate reference symbols and a cell-specific reference signal.
  • a transmit (TX) MIMO processor 230 may perform spatial processing (e.g. , precoding) on data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to the transmit modulators 232-a through 232-x.
  • Each modulator 232 may process a respective output symbol stream (e.g. , for OFDM, etc.) to obtain an output sample stream.
  • Each modulator 232 may further process (e.g. , convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal.
  • DL signals from modulators 232-a through 232-x may be transmitted via the antennas 234-a through 234-x, respectively.
  • Processor 240, TX MIMO processor 230, and/or transmit processor 220 may be configured in some embodiments to support random access procedures for timing advance groups without a primary component carrier (e.g., a TA group that includes only secondary component carriers).
  • these processors may be configured to conduct a random access procedure by which user equipment 115-a achieves uplink synchronization with base station 105-a. Random access procedures may involve the exchange of a series of messages on different carriers and/or different channels.
  • the base station 115-a may send messages in a common search space (or control region) that is monitored by all UEs 115 in a cell, or it may send messages in a search space that is defined for a particular UE.
  • a UE-specific search space may be defined by with a starting offset for blind decodes in the PDCCH.
  • random access procedures may be classified as contention-free or contention-based.
  • base station 105-a may transmits a physical downlink control channel (PDCCH) order indicating a random access preamble and physical random access channel (PRACH) resource for the UE 115-a to send signaling and data on a physical uplink shared channel (PUSCH).
  • PDCCH physical downlink control channel
  • PRACH physical random access channel
  • the UE may select the random access preamble and PRACH resource.
  • Processor 240, TX MIMO processor 230, and/or transmit processor 220 may be configured enable cross-carrier random access procedure management.
  • processor 240, TX MIMO processor 230, and/or transmit processor 220 may transmit random access responses to user equipment 115-a that include a timing advance group index as part of a random access procedure.
  • base station 105-a transmits a PDCCH message in a UE-specific search space of a secondary component carrier which is included in a particular TA group.
  • base station 105-a transmits a random access response (RAR) PDCCH in a common search space of the PCC.
  • RAR random access response
  • An RAR message associated with the PDCCH may convey an index corresponding to a timing advance group.
  • the timing advance group may include only SCCs (including the SCC utilized to initiate the random access procedure).
  • the timing advance group index may enable cross-carrier RAR to a secondary SCC as part of the random access procedure. Different aspects of cross-carrier management, including random access response management, may be facilitated using timing advance group index information.
  • Processor 240, TX MIMO processor 230, and/or transmit processor 220 may also be configured in some embodiments to transmit reference downlink component carrier information for timing within a timing advance group to user equipment 115-a.
  • the user equipment antennas 252-a through 252-n may receive the DL signals from the base station 105-a and may provide the received signals to the demodulators 254-a through 254-n, respectively.
  • Each demodulator 254 may condition (e.g. , filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples ( e.g. , for OFDM, etc.) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all the demodulators 254-a through 254-n, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g. , demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the user equipment 115-a to a data output, and provide decoded control information to a processor 280, or memory 282.
  • the received signals at the user 115-a from base station 105-a may be utilized for a variety of purposes with respect to different embodiments.
  • the receive processor 258 and/or the processor 280 may process information according to different embodiments. Some embodiments may configure receive processor 258 and/or the processor 280 to support random access for timing advance groups without a primary component carrier. These embodiments may utilize different search spaces that the receive processor 258 and/or the processor 280 may examine to determine information that may be utilized during a random access procedure.
  • the receive processor 258 and/or the processor 280 may be configured to receive and determine information from different random access response (RAR) grants that utilize different search spaces. These search spaces may include, but are not limited to, UE-specific search spaces on the PCC and SCCs, a common search space on PCC, and/or common search spaces on secondary component carriers.
  • RAR random access response
  • Some embodiments may involve configuring the receive processor 258 and/or the processor 280 to utilize timing advance group indexes to enable cross-carrier random access procedure management.
  • the receive processor 258 and/or the processor 280 may receive random access responses from base station 105-a that includes a timing advance group index as part of a random access procedure.
  • the receive processor 258 and/or the processor 280 may then utilize this index information for cross-carrier management, including random access response management.
  • the receive processor 258 and/or the processor 280 may also be configured to receive reference downlink component carrier information from base station 105-a.
  • the receive processor 258 and/or the processor 280 may utilize this reference downlink component carrier information for timing within a timing advance group.
  • a transmit processor 264 may receive and process data from a data source.
  • the transmit processor 264 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 264 may be precoded by a transmit MIMO processor 266 if applicable, further processed by the demodulators 254-a through 254-n (e.g., for SC-FDMA, etc.), and be transmitted to the base station 105-a in accordance with the transmission parameters received from the base station 105-a.
  • the UL signals from the user equipment 115-a may be received by the antennas 234, processed by the demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor.
  • the receive processor 238 may provide decoded data to a data output and to the processor 240.
  • processor 280 and/or other components of user equipment 115-a may be configured for utilizing timing advance group synchronization information across multiple timing advance groups.
  • Processor 280 and/or other components of user equipment 115-a may be configured to identify multiple component carriers as part of a carrier aggregation operation.
  • the multiple component carriers may include one or more downlink component carriers and two or more uplink component carriers.
  • Multiple timing advance groups may be determined by processor 280 and/or other components of user equipment 115-a. Each component carrier in the multiple component carriers may be included in one of the timing advance groups.
  • a first timing advance group from the multiple timing advance groups may be identified by processor 280 and/or other components of user equipment 115-a.
  • a reference downlink component carrier may be determined for the first timing advance group based at least in part on a RRC configuration by user equipment processor 280 and/or other components of user equipment 115-a.
  • the determined reference downlink component carrier may be utilized by user equipment 115 for timing adjustment within at least the first timing advance group.
  • processor 280 and/or other components of user equipment 115-a may receive from base station 105-a an indication of a primary downlink component carrier through the RRC configuration.
  • the primary downlink component carrier may be the determined reference downlink component carrier.
  • Processor 280 and/or other components of user equipment 115-a may utilize the primary downlink component carrier for timing adjustment within a second timing advance group from the multiple timing advance groups.
  • the primary downlink component carrier may be included in the second timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined by processor 280 and/or other components of user equipment 115-a to be a downlink component carrier with a smallest cell index of multiple cell indices configured for each one of the one or more downlink component carriers in the first timing advance group.
  • Processor 280 and/or other components of user equipment 115-a may determine the reference downlink component carrier from a set of activated downlink component carriers.
  • the one or more downlink component carriers and the two or more uplink component carriers may be associated with two or more bands.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers of the same band or similar band.
  • the reference downlink component carrier may be determined to be a downlink component carrier of the same or similar band as an uplink component carrier associated with a random access attempt for the first timing advance group. .
  • Processor 280 and/or other components of user equipment 115-a may perform multiple random access procedures in parallel with respect to two or more of the multiple timing advance groups.
  • Performing the multiple random access procedures may include performing a first random access procedure linked with the first timing advance group; and/or performing a second random access procedure linked with a second timing advance group of the multiple timing advance groups, where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • Processor 280 and/or other components of user equipment 115-a may initiate a non-contention based random access procedure on an uplink component carrier within the first timing advance group through utilizing a downlink control channel transmitted on a downlink component carrier that is not linked with the uplink component carrier via a system information block broadcast.
  • a cross-carrier indication field may be included in the downlink control channel to enable cross-carrier scheduling.
  • the reference downlink component carrier for the first timing advance group may be determined by processor 280 and/or other components of user equipment 115-a from a set of downlink component carriers with a similar delay due to downlink repeaters.
  • the reference downlink component carrier for the first timing advance group may be determined by processor 280 and/or other components of user equipment 115-a from a set of downlink component carriers with a same carrier type where the carrier type includes at least a legacy carrier type or a new carrier type.
  • the reference downlink component carrier for the first timing advance group may be determined by processor 280 and/or other components of user equipment 115-a from a set of downlink component carriers with a similar activity factor.
  • Transmit processor 264 and/or processor 280 may be configured in some embodiments to support parallel random access procedures across multiple timing advance groups. For example, multiple parallel random access procedures may occur between base station 105-a and user equipment 115-a. Transmit processor 264 and/or processor 280 may be configured to utilize power prioritization to facilitate these overlapping access procedures. Transmit processor 264 and/or processor 280 may be configured to provide for an Aperiodic Channel Quality Indicator (A-CQI) being triggered within these parallel random access procedures.
  • A-CQI Aperiodic Channel Quality Indicator
  • FIG. 3A shows an example of a configuration 300-a of timing advance groups in accordance with various embodiments.
  • Two or more timing advance groups may be configured in various embodiments.
  • Configuration 300 shows two timing advance groups 310-a and 310-b.
  • a base station such as a serving eNodeB, may configure the timing advance groups utilizing dedicated signaling.
  • one of the timing advance groups includes a primary cell 320.
  • timing advance group 310-a includes primary cell 320.
  • Primary cell 320 includes uplink and downlink primary component carriers, UL-1 and DL-1 respectively.
  • Timing group 310-a also includes a secondary cell 330-a, which includes an uplink component carrier UL-2 and a downlink component carrier DL-2.
  • the second timing advance group 310-b includes another secondary cell, labeled 330-b, with a downlink component carrier DL-3 and an uplink component carrier UL-3. While this example shows two timing advance groups, other embodiments may include more timing advance groups. In addition, different timing advance groups may include more or fewer secondary cells 330. As will be discussed in more detail below, a timing advance group that does not include a primary cell, such as timing advance group 310-b, may have a random access process triggered for the timing advance group by an order, such as a PDCCH order, addressed to an active secondary cell in the timing advance group.
  • an order such as a PDCCH order
  • FIG. 3B shows an example of a configuration 300-b of timing advance groups in accordance with various embodiments and based on configuration 300-a of FIG. 3A .
  • Configuration 300-b shows an example where an RRC-configured primary downlink component carrier (DL-1) may serve as the reference carrier for component carriers in each of the two timing advance groups 310-a, 310-b.
  • DL-1 RRC-configured primary downlink component carrier
  • This RRC-based approach may be advantageous when the activation status of the secondary downlink component carriers (DL-2, DL-3) changes from time to time.
  • a reference downlink component carrier may be determined based on an RRC configuration of user equipment 115.
  • a base station such as a base station 105 of the other figures, may send RRC configuration message(s) to user equipment 115 identifying one carrier as the primary component carrier (PCC) and additional carriers as secondary component carriers (SCCs).
  • PCC primary component carrier
  • SCCs secondary component carriers
  • the carrier that is identified as PCC may serve as the reference downlink carrier for one or more timing advance groups 310.
  • configuration 300-b may be an example of utilizing timing advance group synchronization information across multiple timing advance groups by a user equipment, such as the user equipment 115 of FIGs. 1 , 2 , 4 , 7B , 8B , and/or 9B.
  • multiple component carriers such as UL-1, UL-2, UL-3, DL-1, DL-2, and/or DL-3, may be identified as part of a carrier aggregation operation.
  • the multiple component carriers may include one or more downlink component carriers (e.g., DL-1, DL-2, and/or DL-3) and two or more uplink component carriers (e.g., UL-1, UL-2, and/or UL-3).
  • Timing advance groups 310-a and 310-b may be determined. Each component carrier in the multiple component carriers may be included in one of the timing advance groups.
  • a first timing advance group, such as timing advance group 310-b, from the multiple timing advance groups may be identified.
  • a reference downlink component carrier, such as DL-1 may be determined for the first timing advance group based at least in part on an RRC. The determined reference downlink component carrier may be utilized for timing adjustment within at least the first timing advance group.
  • the determined reference downlink component carrier may also be utilized for other timing advance groups, such as timing advance group 310-a.
  • timing offset information may be utilized along with timing information from the determined downlink component carrier to determine timing information for the different timing advance groups.
  • an indication of a primary downlink component carrier may be received through the RRC configuration.
  • the primary downlink component carrier may be the determined reference downlink component carrier.
  • the primary downlink component carrier may be utilized for timing adjustment within a second timing advance group (e.g., timing advance group 310-a) from the multiple timing advance groups.
  • the primary downlink component carrier may be included in the second timing advance group.
  • one or more downlink component carriers of the one or more identified downlink carriers is included in the first timing advance group, such as DL-3 of timing advance group 310-b. Determining the reference downlink component carrier may be based on an RRC configuration for the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined to be a downlink component carrier with a smallest cell index in the first timing advance group, which is the primary component carrier.
  • the second timing advance group may have two or more secondary component carriers, and the reference downlink component for the second timing advance group may be determined to be a downlink component carrier with a smallest cell index within the second timing advance group.
  • the reference downlink component carrier may be determined from a set of activated downlink component carriers.
  • the one or more downlink component carriers and the two or more uplink component carriers may be associated with two or more bands.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers of the same band or similar band.
  • the reference downlink component carrier may be determined to be a downlink component carrier of the same or similar band as an uplink component carrier associated with a random access attempt for the first timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a similar delay due to downlink repeaters.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a same carrier type where the carrier type includes at least a legacy carrier type or a new carrier type.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a similar activity factor.
  • a component carrier may be equipped with a repeater while another component carrier is not.
  • the component carriers of the same or similar delay characteristics due to repeaters may be determined to be possible candidates for the reference downlink component carrier for the given timing advance group.
  • Different component carriers may have different activity factors.
  • a component carrier may periodically be turned on and carries much less frequent downlink information compared with a regular carrier.
  • a component carrier may be of a legacy carrier type and another can be of a new carrier type. Carriers of the same type may be determined to be possible candidates for the reference downlink component carrier for a given timing advance group.
  • multiple random access procedures may be performed in parallel with respect to two or more of the multiple timing advance groups, such as timing advance group 310-a and 310-b.
  • Performing the multiple random access procedures may include performing a first random access procedure linked with the first timing advance group, such as timing advance group 310-b; and/or performing a second random access procedure linked with a second timing advance group, such as timing advance group 310-a, of the multiple timing advance groups, where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • Some embodiments include utilizing a non-contention based random access procedure on an uplink component carrier, such as UL-3, within the first timing advance group, such as timing advance group 310-a, through utilizing a downlink control channel transmitted on a downlink component carrier that is not linked with the uplink component carrier via a system information block broadcast (e.g., the primary component carrier (DL-1)).
  • a cross-carrier indication field may be included in the downlink control channel to enable cross-carrier scheduling.
  • Some embodiments may provide advantages, for example, when the activation status of the SCCs changes from time to time.
  • a timing advance group that contains SCCs, but no PCC may face synchronization issues because of deactivation of the corresponding secondary cells.
  • a timing advance group with a primary cell that corresponds to a PCC may not face the same issues because the primary cell cannot be deactivated.
  • Embodiments may also provide advantages over some other techniques that may be provide timing information for a timing advance group that include SCCs but no PCC, such as through SIB2 linkage. For example, when a secondary cell downlink component carrier is activated or deactivated, the SIB2 linked uplink component carrier is also generally activated or deactivated. As another example, the characteristics of a component carrier can be taken into account (activation status, whether it is equipped with a repeater, whether it is always on or periodically turned off, legacy or new carrier type, etc) in determining the reference downlink component carrier.
  • FIG. 4A , FIG. 4B , and/or FIG. 4C show examples of random access procedures 400-a, 400-b, and 400-c in accordance with various embodiments. These embodiments provide examples of search space designs that may be utilized with timing advance groups. In particular, these embodiments provide different ways to support random access for timing advance groups without primary component carriers.
  • Random access procedures 400-a, 400-b, and/or 400-c may include non-contention based random access. Some of these random access procedures may also be configured for contention-based random access, such as random access procedure 400-b and/or 400-c.
  • a non-contention based random access procedure may be initiated for any of the procedures 400-a, 400-b, and/or 400-c utilizing Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • the various fields of DCI format 1A may be configured to initiate the random access procedure.
  • eNB 105-i may transmit a DCI format 1A message to UE 115-j on a Physical Downlink Control Channel (PDCCH).
  • the format 1A Cyclic Redundancy Check (CRC) may be scrambled with a Cell Radio-Network Temporary Identifier (C-RNTI).
  • CRC Cyclic Redundancy Check
  • C-RNTI Cell Radio-Network Temporary Identifier
  • the remaining fields of the format 1A may be configured in the following manner: Localized/Distributed VRB assignment flag (1 bit is set to '0'); resource block assignment (all bits set to '1'); preamble index (6 bits); Physical Random Access Channel (PRACH) Mask Index (4 bits).
  • the remaining bits in format 1A for compact scheduling assignment of the one Physical Downlink Shared Channel (PDSCH) codeword may be set to zero.
  • Other embodiments may utilize other field settings.
  • some embodiments may utilize other DCI formats.
  • the PDCCH may be transmitted in UE-specific search space (UESS).
  • UESS UE-specific search space
  • some embodiments may not allow PDCCH for downlink data arrival using format 1A to be transmitted from a common search space (CSS).
  • the UESS can be on one SCC in a target timing advance group or any other component carrier when a carrier indicator field (CIF) is enabled.
  • CIF carrier indicator field
  • Embodiments as shown in random access procedures 400 may provide different ways to handle a random access response (RAR) grant.
  • the RAR grant may include an uplink grant on PUSCH and timing information such as a timing advance command for controlling the amount of timing adjustment to be applied by the user equipment.
  • Procedures 400 provide several different examples of search spaces for the accessing procedures. In particular, procedures 400 provide examples of how to send PDCCH for RAR grant (shown as message 2 in procedures 400).
  • random access procedure 400-a shows an example where a UE-specific search space may be utilized to send PDCCH for the RAR grant.
  • Procedure 400-a shows PDCCH transmitted from eNB 105-i in UESS 410-a as DCI format 1A (message 0) to user equipment 115-i.
  • User equipment 115-i may make a random access attempt by sending a random access preamble as PRACH (message 1) to eNB 105-i.
  • PRACH messagessage 1
  • PDCCH for RAR grant (message 2) may be sent from eNB 105-i in UESS 420-a.
  • Procedure 400-a also shows Physical Uplink Shared Channel (PUSCH) (message 3) and Physical Downlink Shared Channel (PDSCH) (message 4); these messages may involve transmitting signaling and/or user data between eNB105-i and user equipment 115-i.
  • PUSCH Physical Uplink Shared Channel
  • PDSCH Physical Downlink Shared Channel
  • the PDCCH scheduling the PDSCH may utilize UESS 430-a in some cases.
  • Some embodiments may utilize a Random Access Radio-Network Temporary Identifier (RA-RNTI) in the UESS for the user equipment 115-i.
  • RA-RNTI Random Access Radio-Network Temporary Identifier
  • the number of PDCCH blind decodes may be increased in some cases, depending on whether the CSS DCI format or UESS DCI format is used as they have different sizes, and/or whether DCI format 1C is used. In some embodiments, only DCI format 1A may be utilized. In some cases, the DCI format 1A may confirm to the UESS format. This may result in the number of PDCCH blind decodes not increasing. Embodiments such as procedure 400-a may apply to non-contention based timing advance groups.
  • random access procedure 400-b shows an example where a CSS on a PCC may be utilized to send PDCCH for the RAR grant.
  • procedure 400-b may involve physical layer based handling and/or MAC layer based handling.
  • Procedure 400-b shows PDCCH transmitted from eNB 105-j in UESS 410-b as DCI format 1A (message 0) to user equipment 115-j.
  • User equipment 115-j may make a random access attempt by sending a random access preamble as PRACH (message 1) to eNB 105-j.
  • PDCCH for RAR grant may be sent from eNB 105-j from the common search space on the primary carrier component 420-b.
  • Procedure 400-b also shows Physical Uplink Shared Channel (PUSCH) (message 3) subsequent to the RAR grant and a Physical Downlink Shared Channel (PDSCH) (message 4); these messages may involve transmitting signaling and/or user data between eNodeB 105-j and user equipment 115-j.
  • PUSCH Physical Uplink Shared Channel
  • PDSCH Physical Downlink Shared Channel
  • the PDCCH scheduling the PDSCH may utilize UESS 430-b in some cases.
  • procedure 400-b may utilize a physical layer based approach.
  • a carrier indicator field may be enabled for some DCI in CSS.
  • CIF may be added in DCI format 1A, for example, and may enable cross-carrier scheduling in the RAR grant. Additionally, or separately, CIF may be added in DCI format 1C.
  • a combination these approaches, or splitting PDCCH decoding candidates may increase the number of decoding candidates in CSS. If it may be desirable to avoid increasing the number of PDCCH blind decodes, some embodiments may enable on the CIF for DCI format 1C and/or use it for message 2. In this case, there may be no cross-carrier RAR grant for DCI format 1A, but may be allowed only with DCI format 1C.
  • procedure 400-b may utilize a MAC layer based approach.
  • a component carrier index and/or a timing advance group index may be utilized to enable a cross-carrier random access procedure.
  • the component carrier index and/or timing advance group index may be introduced in message 0 particularly when CIF is configured for the UE.
  • the signaling of the CC index and/or TA group index in this case can be done by re-interpreting some of the reserved bit(s) in DCI format 1A message 0.
  • the CC index and/or the TA group index may also be included with the RAR in the MAC payload.
  • the CC index and/or TA group index may be introduced to enable cross-carrier RAR management from the PCC to SCC.
  • a CC index may be utilized to identify specific component carriers that may be utilized in the cross-carrier RAR.
  • a TA group index may be utilized to identify different groups of component carriers or cells. TA group indexes are discussed in more detail below.
  • a timing advance group index may need the RRC to identify which component carrier to transmit PRACH and/or other messages in the RACH procedure within the timing advance group.
  • a contention-free random access procedure is initiated when eNB 105-j transmits a properly configured PDCCH message (message 0) to UE 115-j.
  • the contention-free random access procedure may be used to establish a timing adjustment applicable to a group of secondary component carriers in a targeted TA group.
  • eNB 105-j may transmit the PDCCH message on an SCC in the targeted group.
  • the PDCCH may include a TA group index corresponding to the group of SCCs.
  • the UE 115-j transmits message 1 on a physical random access channel (PRACH).
  • PRACH physical random access channel
  • the CC on which PRACH is transmitted may be identified by the TA group index included with PDCCH order initiating the random access procedure and/or it may be determined according to the SCC on which the PDCCH was received.
  • the PRACH transmission may occur in a specified subframe and may include a predetermined preamble sequence.
  • eNB 105-j detects the PRACH transmission, it may generate a random access response message which, at the physical layer, may be referred to as an RAR grant (message 2).
  • the PDCCH for the RAR may be transmitted in a common search defined for UE 115-j on its primary component carrier.
  • the RAR grant enables cross-carrier operation from PCC (on which the corresponding PDCCH is received) to an SCC in the target TA group.
  • the PDSCH transmission corresponding to the PDCCH may carry an RAR message that includes a timing adjustment (TA) value and uplink grant.
  • a MAC payload of the RAR message may also include a TA group index.
  • UE 115-j may identify the set of SCCs targeted for timing adjustment and a specific CC to use for completing the random access procedure. Thereafter, the UE 115-j may transmit PUSCH (message 3) on the CC in accordance with the grant included in the RAR message.
  • multiple TA groups may be configured for UE 115-j, including TA groups without PCC.
  • random access procedure 400-c shows an example where a common search space on a SCC may be utilized to send the PDCCH for RAR grant.
  • Procedure 400-c shows PDCCH transmitted from eNodeB 105-k in UESS or CSS on SCC 410-c as DCI 1A message 0 to user equipment 115-k.
  • User equipment 115-k may make a random access attempt by sending a random access preamble as PRACH message 1 to eNodeB 105-k.
  • PDCCH for RAR grant message 2 may be sent from eNodeB 105-k from the common search space on the secondary carrier component 420-c.
  • Procedure 400-c also shows Physical Uplink Shared Channel (PUSCH) message 3 and Physical Downlink Shared Channel (PDSCH) message 4; these messages may involve transmitting signaling and/or user data in general between eNodeB 105-k and user equipment 115-k.
  • the PDCCH scheduling the PDSCH may utilize CSS on SCC and/or UESS 430-c in some cases.
  • Utilizing CSS on SCC for the user equipment 115-k may provide for other useful features so as group power control.
  • Procedure 400-c may also be utilized for contention based SCC timing advance groups.
  • FIG. 5 shows one example of a table 500 that includes timing advance group indexing information in accordance with various embodiments.
  • Different CCs or cells may be grouped into different timing advance groups.
  • a primary cell, Pcell, and two secondary cells, Scell-1 and Scell-2 may be grouped together and identified by a TA group index, "0" in this case.
  • a second group including two secondary cells, Scell-3 and Scell-4 may be grouped together and identified utilizing another TA group index, "1" in this case.
  • a single bit of information may be utilized to identify each timing advance group, although different amounts of information may be used in different embodiments.
  • This information may be configured for a user equipment 115 by a base station 105 and signaled to the UE 115 in one or RRC messages .
  • the TA group index may generally indicate the timing advance group that includes a primary cell or PCC through a "0" index.
  • Some embodiments may include timing advance indexes that may utilize additional bits to convey their information. The number of bits utilized may depend upon the number of timing advance groups. Thus, the use of two timing advance groups is provided merely as an example; other examples may include more than two timing advance groups and each group may include zero or more secondary cells or secondary component carriers. The number of timing advance groups with associated timing advance group indexes may depend upon a variety of factors including, but not limited, propagation delay characteristics, channel characteristics, user equipment device characteristics, and/or bandwidth characteristics of the component carriers.
  • the timing advance group index may be included in a MAC payload in some embodiments.
  • the TA group index such as seen in table 500, may be transmitted as part of a PDCCH payload in some embodiments.
  • Some embodiments may utilize additional information such as a component carrier identifier as part of an RRC configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index. The identified component carrier may be utilized for a random access attempt and/or other messages in the RACH procedure.
  • FIG. 6 shows an exemplary configuration 600 of multiple timing advance groups that may utilize parallel random access procedures in accordance with various embodiments.
  • the exemplary configuration 600 shows two timing advance groups, 610-a and 610-b.
  • Timing advance group 610-a includes primary component carrier 620 and secondary component carrier 630-a.
  • Timing advance group 610-b includes secondary component carrier 630-b and secondary component carrier 630-c.
  • Other embodiments may include timing advance groups that include more or less component carriers.
  • random access procedures 640-a for timing advance group 610-a may occur in parallel or overlap with random access procedures 640-b of timing advance group 610-b.
  • different embodiments may handle these parallel random access procedures in a variety of ways.
  • FIG. 7A a block diagram illustrates a device 700-a that supports multiple timing advance groups for user equipment in carrier aggregation.
  • the device 700-a may be the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , and/or FIG. 9 .
  • the device 700-a may also be a processor.
  • the device 700-a may include a receiver module 705, a random access module 715, a timing advance group index module 720, a reference downlink component carrier module 725, and/or a transmitter module 730. Each of these components may be in communication with each other.
  • ASICs Application Specific Integrated Circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art.
  • the functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • the receiver module 705 may receive information from difference sources over different channels and deliver to other modules of device 700-a.
  • the transmitter module 730 may transmit information it may receive form the other modules of device 700-a.
  • the timing advance group index receive module 720 may provide a variety of cross-carrier management functions for multiple timing advance groups is provided. For example, the timing advance group index receive module 720 may receive a timing advance group index. The timing advance group index may identify a timing advance group from multiple timing advance groups. Each group may include different sets of component carriers. Some embodiments may include enabling cross-carrier random access procedure through the utilization of the timing advance group index.
  • the TA group receive module 720 may receive a TA group index for a first timing advance group from the multiple timing advance groups that includes a PCC and a second timing advance group includes at least one SCC.
  • the first timing advance group may also include one or more secondary component carriers, while the second timing advance group does not include the PCC.
  • the timing advance group index receive module 720 may also work with timing advance groups that also include additional timing advance groups besides the first and second timing advance group.
  • the TA group index module 720 may receive TA group indexes that include a single bit of information.
  • a first configuration of the single bit of information may indicate that the timing advance group includes a primary component carrier; a second configuration of the single bit may indicate that the timing advance group one or more secondary component carriers without the primary component carrier.
  • Some embodiments may include timing advance indexes that may utilize additional bits to convey their information. The number of bits that the timing advance group module 720 may utilize may depend upon the number of timing advance groups.
  • the TA group index may be received by receiver module 705 as part of a MAC payload in some embodiments. Some embodiments may also include receiving through the receiver module 705 a component carrier identifier as part of a Radio Resource Control (RRC) configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index. The identified component carrier may be utilized from a random access procedure.
  • RRC Radio Resource Control
  • the random access module 715 may be utilized to perform multiple parallel random access procedures. For example, the random access module 715 may be utilized to perform a first random access procedure associated with a first timing advance group of component carriers. The random access module 715 may be utilized to perform a second random access procedure associated with a second timing advance group of component carriers where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • the random access module 715 may be utilized to perform power prioritization with respect to the first random access procedure and the second random access procedure.
  • Performing the power prioritization may include performing an equal power scaling with respect to the first random access procedure and the second random access procedure.
  • performing the power prioritization may include transmitting a first random access attempt with respect to the first timing advance group of component carriers prior to transmitting a second random access attempt with respect to the second timing advance group of component carriers, where the first timing advance group of component carriers includes a primary component carrier.
  • the random access module 715 may be utilized to perform the first random access procedure that may include a non-contention based random access procedure and the second random access procedure may include a contention based random access procedure.
  • Performing the power prioritization in this case may include transmitting a first random access attempt with respect to the first timing advance group of component carriers prior to transmitting a second random access attempt with respect to the second timing advance group of component carriers. These transmissions may utilize the transmitter module 730 also.
  • performing the power prioritization may take into account some combination of the type of the group (primary or secondary), the type of the RACH procedure (contention-based or non-contention based), and/or simple equal power scaling.
  • a primary group may be given the highest priority, followed by equal power scaling for all the remaining secondary groups if there are two or more secondary timing advance groups.
  • a primary group may be given the highest priority, followed by equal power scaling for the secondary groups containing non-contention based RACH procedure, and finally, followed by equal power scaling for the secondary groups containing contention-based RACH procedure.
  • Some embodiments may include triggering an aperiodic channel quality indicator (A-CQI) using the random access module 715.
  • A-CQI aperiodic channel quality indicator
  • device 700-a and random access module 715 in particular may not expect to receive more than one aperiodic Channel-State Information (CSI) report request for a given subframe.
  • CSI Channel-State Information
  • parallel message 3 PUSCH may be utilized. For example, a component carrier 1 RAR grant in subframe n, with delay bit set to 1, may utilize a message 3 PUSCH in subframe n+7.
  • a component carrier 2 RAR grant in subframe n+1, delay bit set to 0, may utilize a message 3 PUSCH in subframe n+7.
  • parallel message 3 PUSCH in subframe n+7 may be utilized, but only one of the RAR grants may set A-CQI to 1.
  • the PUSCH corresponding to the RAR grant with A-CQI set to 1 carries the A-CQI feedback.
  • the reference downlink component carrier receiver module 725 may be utilized to receive timing advance group synchronization information.
  • the reference downlink component carrier receiver module 725 may receive a reference downlink component carrier information.
  • the reference downlink component carrier information may be utilized by device 700-a for timing adjustment within a first timing advance group from multiple timing advance groups.
  • Each timing advance group may include at least one downlink component carrier.
  • Device 700-a may be configured for performing random access by a multi-carrier UE in some embodiments.
  • a downlink control message configured to initiate a random access procedure may be received at receiver module 705 and passed to random access module 715.
  • a response to the downlink control message may be generated at the random access module 715 and may be transmitted on a physical random access channel (PRACH) from transmitter module 730.
  • An access grant may be received on a PCC of the user equipment at the receiver module 705.
  • a set SCCs may be determined based on the random access grant.
  • the timing advance group index receive module 720 and/or the random access module 715 may determine the set of secondary components.
  • the random access procedure facilitated by the random access module 715 may be completed using a carrier in the set of SCCs to obtain TA information applicable to the set of SCCs.
  • the receiver module 705 and/or the random access module 715 may be configured to receive the downlink control message through detecting a physical downlink control channel (PDCCH) message in a UE-specific search space.
  • the receiver module 705 and/or the random access module 715 may be configured to receive the random access grant through detecting a PDCCH message in a common search space of the PCC.
  • PDCCH physical downlink control channel
  • device 700-a may be configured to obtain a medium access control (MAC) protocol data unit (PDU) with the random access grant.
  • MAC medium access control
  • PDU protocol data unit
  • a TA group index may be determined corresponding to the set of SCCs based on the MAC PDU.
  • Some embodiments may further include configuring the timing advance group index receive module 720 to receive a configuration of TA groups corresponding to component carriers configured for the UE.
  • the TA group index may be obtained from the MAC PDU.
  • the configuration of TA groups may include at least a first TA group including the PCC, and a second TA group including the set of secondary CCs.
  • the timing advance group index receive module may be configured to determine TA group index corresponding to the set of SCCs as part of a PDCCH payload.
  • Some embodiments may further include utilizing the reference downlink component carrier receive module 725 to determine a reference downlink CC for completing the random access procedure based on the TA group index.
  • the downlink control message may be configured to initiate the random access procedure comprises an identifier corresponding to the set of SCCs.
  • the transmitter module 730 may transmit the response to the downlink control message to further include determining an SCC to transmit the PRACH based on the identifier.
  • a second random access procedure may be initiated concurrently with the first random access procedure using the random access module 715.
  • Some embodiments may further include configuring the random access module 715 to determine a priority for allocating power between the first random access procedure and the second random access procedure.
  • the random access module 715 may allocate power to the first random access procedure at a higher priority than the second random access procedure when the first random access procedure comprises a contention-free random access procedure and the second random access procedure comprises a contention-based random access procedure.
  • the random access module 715 may allocate power to the second random access procedure at a higher priority than the first random access procedure when the second random access procedure when the second random access procedure is performed in relation to a group of carriers comprising a primary component carrier of the UE.
  • the random access module 715 may determine the priority including performing an equal power scaling for each CC.
  • FIG. 7B is a block diagram 700-b of a user equipment 115-b in accordance with various embodiments.
  • the user equipment 115-b may have any of various configurations, such as personal computers (e.g., laptop computers, netbook computers, tablet computers, etc.), cellular telephones, PDAs, digital video recorders (DVRs), internet appliances, gaming consoles, e-readers, etc.
  • the user equipment 115-b may have an internal power supply (not shown), such as a small battery, to facilitate mobile operation. .
  • the user equipment 115-b may be the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9 , and/or device 700-a of FIG. 7A
  • the user equipment 115-b may include antennas 740, a transceiver module 750, memory 780, and a processor module 770, which each may be in communication, directly or indirectly, with each other (e.g., via one or more buses).
  • the transceiver module 750 is configured to communicate bi-directionally, via the antennas 740 and/or one or more wired or wireless links, with one or more networks, as described above.
  • the transceiver module 750 may be configured to communicate bi-directionally with base stations 105 of FIG. 1 or 2 .
  • the transceiver module 750 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 740 for transmission, and to demodulate packets received from the antennas 740. While the user equipment 115-b may include a single antenna, the user equipment 115-b will typically include multiple antennas 740 for multiple links.
  • the memory 780 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 780 may store computer-readable, computer-executable software code 785 containing instructions that are configured to, when executed, cause the processor module 770 to perform various functions described herein (e.g., call processing, database management, message routing, etc.).
  • the software 785 may not be directly executable by the processor module 770 but be configured to cause the computer (e.g., when compiled and executed) to perform functions described herein.
  • the processor module 770 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel ® Corporation or AMD ® , a microcontroller, an application specific integrated circuit (ASIC), etc.
  • the processor module 770 may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 30 ms in length) representative of the received audio, provide the audio packets to the transceiver module 750, and provide indications of whether a user is speaking.
  • an encoder may only provide packets to the transceiver module 750, with the provision or withholding/suppression of the packet itself providing the indication of whether a user is speaking.
  • the user equipment 115-b may further include a communications management module 760.
  • the communications management module 760 may manage communications with other user equipment 115.
  • the communications management module 760 may be a component of the user equipment 115-b in communication with some or all of the other components of the user equipment 115-b via a bus.
  • functionality of the communications management module 760 may be implemented as a component of the transceiver module 750, as a computer program product, and/or as one or more controller elements of the processor module 770.
  • the components for user equipment 115-b may be configured to implement aspects discussed above with respect to device 700-a in FIG. 7A and may not be repeated here for the sake of brevity.
  • the timing advance group index receive module 720-a may be an example of the timing advance group index receive module 720 of FIG. 7A .
  • the reference downlink component carrier receive module 725-a may be an example of the reference downlink component carrier receive module 725 of FIG. 7A .
  • Parallel random access control module 717, power prioritization module 718, and/or A-CQI triggering module 719 may provide specific functionality individually or in combination for a random access module 715-a that may be an example of the random access module 715 of FIG. 7A .
  • FIG. 8A a block diagram illustrates a device 800-a that supports multiple timing advance groups for user equipment in carrier aggregation.
  • the device 800-a may be the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , and/or FIG. 9 ; and/or device 700-a of FIG. 7 .
  • the device 800-a may also be a processor.
  • the device 800-a may include a receiver module 805, a component carrier identification module 815, a timing advance group module 820, a reference downlink component carrier module 825, and/or a transmitter module 830. Each of these components may be in communication with each other.
  • Device 800-a may be configured as one or more processors.
  • ASICs Application Specific Integrated Circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs
  • the functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • the receiver module 805 may receive information from difference sources over different channels and deliver to other modules of device 800-a.
  • the transmitter module 830 may transmit information it may receive form the other modules of device 800-a.
  • the component carrier identification module 815 may identify multiple component carriers as part of a carrier aggregation operation.
  • the multiple component carriers may include one or more downlink component carriers and two or more uplink component carriers.
  • the timing advance group module 820 may determine multiple timing advance groups. Each component carrier in the multiple component carriers may be included in one of the timing advance groups.
  • the timing advance group module 820 may identify a first timing advance group from the multiple timing advance group.
  • the reference downlink component carrier module 825 may determine a reference downlink component carrier for the first timing advance group based at least in part on a Radio Resource Control (RRC) configuration.
  • RRC Radio Resource Control
  • the timing advance group module 820, the reference downlink component carrier module 825, and/or other components of device 800-a may utilize the determined reference downlink component for timing adjustment within at least the first timing advance group.
  • device 800-a may receive indication of a primary downlink component carrier through the RRC configuration, such as through receiver 805.
  • the primary downlink component carrier may be the determined reference downlink component carrier.
  • Some embodiments of device 800-a through the timing advance group module 820, the reference downlink component carrier module 825, and/or other components of device 800-a, include utilizing the primary downlink component carrier for timing adjustment within a second timing advance group from the multiple timing advance groups.
  • the primary downlink component carrier may be included in the second timing advance group.
  • the timing advance group module 820 may include one or more downlink component carriers of the one or more identified downlink carriers in the first timing advance group.
  • the reference downlink component carrier module 825 may determine the reference downlink component carrier based on an RRC configuration for the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier module 825 may determine the reference downlink component carrier for the first timing advance group to be a downlink component carrier with a smallest cell index from multiple cell indices configured for each one of the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier may be determined by the reference downlink component carrier module 825 from a set of activated downlink component carriers. In some cases, the component carrier identification module 815 may determine that the one or more downlink component carriers and the two or more uplink component carriers are associated with two or more bands.
  • the reference downlink component carrier for the first timing advance group may be determined by the reference downlink component carrier module 825 or the timing advance group module 820 from a set of downlink component carriers of the same or similar band. As an example, the reference downlink component carrier may be determined to be a downlink component carrier of the same or similar band as an uplink component carrier associated with a random access attempt for the first timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined by the reference downlink component carrier module 825 from a set of downlink component carriers with a similar delay due to downlink repeaters.
  • the reference downlink component carrier for the first timing advance group may be determined by the reference downlink component carrier module 825 from a set of downlink component carriers with a same carrier type where the carrier type includes at least a legacy carrier type or a new carrier type.
  • the reference downlink component carrier for the first timing advance group may be determined by the reference downlink component carrier module 825 from a set of downlink component carriers with a similar activity factor.
  • Device 800-a through component carrier identification module 815, timing advance group module 820, or reference downlink component carrier module 825, may take into account different characteristics of a component carrier (e.g., whether it is equipped with a repeater, whether it is always on or periodically turned off, whether it is a new or legacy carrier type, etc.) in determining the reference downlink component carrier.
  • a component carrier may be equipped with a repeater while another component carrier is not.
  • the component carriers of the same or similar delay characteristics due to repeaters (either downlink repeaters, or uplink repeaters, or a combination thereof) may be determined to be possible candidates for the reference downlink component carrier for the given timing advance group. Different component carriers may have different activity factors.
  • a component carrier may periodically be turned on and carries much less frequent downlink information compared with a regular carrier. It may then be preferable to avoid using this component carrier as the reference downlink component carrier.
  • a component carrier may be of a legacy carrier type and another can be of a new carrier type. Carriers of the same type may be determined to be possible candidates for the reference downlink component carrier for a given timing advance group.
  • Some embodiments of device 800-a may be configured for performing multiple random access procedures in parallel with respect to two or more of the multiple timing advance groups.
  • Performing the multiple random access procedures may include performing a first random access procedure linked with the first timing advance group; and/or performing a second random access procedure linked with a second timing advance group of the multiple timing advance groups, where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • Some embodiments of device 800-a may be configured for initiating a non-contention based random access procedure on an uplink component carrier within the first timing advance group through utilizing a downlink control channel transmitted on a downlink component carrier that is not linked with the uplink component carrier via a system information block broadcast (e.g., the primary component carrier).
  • a cross-carrier indication field may be included in the downlink control channel to enable cross-carrier scheduling.
  • FIG. 8B is a block diagram 800-b of a user equipment 115-c in accordance with various embodiments.
  • the user equipment 115-c may have any of various configurations, such as personal computers (e.g., laptop computers, netbook computers, tablet computers, etc.), cellular telephones, PDAs, digital video recorders (DVRs), internet appliances, gaming consoles, e-readers, etc.
  • the user equipment 115-c may have an internal power supply (not shown), such as a small battery, to facilitate mobile operation..
  • the user equipment 115-c may be the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 9 , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A
  • the user equipment 115-c may include antennas 840, a transceiver module 850, memory 880, and a processor module 870, which each may be in communication, directly or indirectly, with each other (e.g., via one or more buses).
  • the transceiver module 850 is configured to communicate bi-directionally, via the antennas 840 and/or one or more wired or wireless links, with one or more networks, as described above.
  • the transceiver module 850 may be configured to communicate bi-directionally with base stations 105 of FIG. 1 or 2 .
  • the transceiver module 850 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 840 for transmission, and to demodulate packets received from the antennas 840. While the user equipment 115-c may include a single antenna, the user equipment 115-c will typically include multiple antennas 840 for multiple links.
  • the memory 880 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 880 may store computer-readable, computer-executable software code 885 containing instructions that are configured to, when executed, cause the processor module 870 to perform various functions described herein (e.g., call processing, database management, message routing, etc.).
  • the software 885 may not be directly executable by the processor module 870 but be configured to cause the computer (e.g., when compiled and executed) to perform functions described herein.
  • the processor module 870 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel ® Corporation or AMD ® , a microcontroller, an application specific integrated circuit (ASIC), etc.
  • the processor module 870 may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 30 ms in length) representative of the received audio, provide the audio packets to the transceiver module 850, and provide indications of whether a user is speaking.
  • an encoder may only provide packets to the transceiver module 850, with the provision or withholding/suppression of the packet itself providing the indication of whether a user is speaking.
  • the user equipment 115-c may further include a communications management module 860.
  • the communications management module 860 may manage communications with other user equipment 115.
  • the communications management module 860 may be a component of the user equipment 115-c in communication with some or all of the other components of the user equipment 115-c via a bus.
  • functionality of the communications management module 860 may be implemented as a component of the transceiver module 850, as a computer program product, and/or as one or more controller elements of the processor module 870.
  • the components for user equipment 115-c may be configured to implement aspects discussed above with respect to device 800-a in FIG. 8A and may not be repeated here for the sake of brevity.
  • the timing advance group module 820-a may be an example of the timing advance group index module 820 of FIG. 8A .
  • the reference downlink component carrier module 825-a may be an example of the reference downlink component carrier module 825 of FIG. 8A .
  • the component carrier identification module 815-a may be an example of the component carrier identification module 815 of FIG. 8A .
  • User equipment 115-c may also include a timing adjustment module 835, whose function has been described above with respect to device 800-a.
  • User equipment 115-c may also include a random access module 845, whose functions have been described above with respect to device 800-a.
  • FIG. 9A a block diagram illustrates a device 900-a that supports multiple timing advance groups for user equipment in carrier aggregation.
  • the device 900-a may be the base station 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , and/or FIG. 9B .
  • the device 900-a may also be a processor.
  • the device 900-a may include a receiver module 905, a search space module 910, a parallel random access module 915, a timing advance group index generation module 920, a reference downlink component carrier module 925, and/or a transmitter module 930. Each of these components may be in communication with each other.
  • ASICs Application Specific Integrated Circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs
  • the functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • the receiver module 905 may receive information from difference sources over different channels and deliver to other modules of device 900-a.
  • the transmitter module 930 may transmit information it may receive form the other modules of device 900-a.
  • Search space module 910 may be utilized to support random access procedures for timing advance groups without a primary component carrier. Search space module 910 may be utilized to generate different search spaces. Some embodiments may utilize a UE-specific search space. Other embodiments may utilize a common search space on the primary component carrier. Additional embodiments may utilize a common search space on a secondary component carrier. Some embodiments may utilize non-contention based random access procedures, while other embodiments may utilize contention based random access procedures.
  • the timing advance group index generation module 920 may provide a variety of cross-carrier management functions for multiple timing advance groups is provided. For example, the timing advance group index generation module 920 may generate a timing advance group index. The timing advance group index may identify a timing advance group from multiple timing advance groups. Each group may include different sets of component carriers. The timing advance group index generation module 920 may send the generated timing advance group index to the transmitter module 930, from where the timing advance group index may be transmitted as part of a random access response. Some embodiments may include enabling cross-carrier random access procedure management through the utilization of the timing advance group index.
  • the timing advance index generation group module 920 may generate a timing advance group index for a first timing advance group from the multiple timing advance groups that includes a primary component carrier and a second timing advance group includes at least one secondary component carrier.
  • the first timing advance group may also include one or more secondary component carriers, while the second timing advance group does not include a primary component carrier.
  • the timing advance group index generation module 920 may also work with timing advance groups that also include additional timing advance groups besides the first and second timing advance group.
  • the number of timing advance groups associated with timing advance group indexes generated by the timing advance group index generation module 920 may depend upon a variety of factors including, but not limited to, propagation delay characteristics, channel characteristics, user equipment device characteristics, and/or bandwidth characteristics of the component carriers.
  • the timing advance group index generation module 920 may generate timing advance group indexes that utilizes a single bit of information.
  • the transmitter module 930 may transmit these timing advance group indexes as a single bit of information.
  • a first bit configuration of the single bit of information may indicate that the timing advance group includes a primary component carrier; a second bit configuration of the single bit may indicate that the timing advance group one or more secondary component carriers without the primary component carrier.
  • Some embodiments may include timing advance indexes that may utilize additional bits to convey their information.
  • the number of bits that the timing advance group module 920 may utilize may depend upon the number of timing advance groups.
  • the timing advance group index may be transmitted by the transmitter module 930 as part of a MAC payload in some embodiments. Some embodiments may also include transmitting through the transmitter module 930 a component carrier identifier as part of a Radio Resource Control (RRC) configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index. The identified component carrier may be utilized for a random access response.
  • RRC Radio Resource Control
  • the parallel random access module 915 may be utilized to perform multiple parallel random access procedures. For example, the parallel random access module 915 may be utilized to perform a first random access procedure associated with a first timing advance group of component carriers. The parallel random access module 915 may be utilized to perform a second random access procedure associated with a second timing advance group of component carriers where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • the parallel random access module 915 may configure a first subframe that includes a first random access response as part of the first random access procedure.
  • a second subframe including a second random access response may be configured by the parallel random access module 915 as part of the second random access procedure.
  • the first subframe and the second subframe may be transmitted from the parallel random access module 915 through the transmitter module 930. As a result, the first and second random access responses may not be transmitted in the same subframe.
  • the reference downlink component carrier module 925 may be utilized to provide timing advance group synchronization information. For example, the reference downlink component carrier module 925 may determine a reference downlink component carrier. Reference downlink component carrier information may be transmitted from transmitter 930 to a user equipment 115 where it may be utilized for timing adjustment within a first timing advance group from multiple timing advance groups. Each timing advance group may include at least one downlink component carrier.
  • the reference downlink component carrier module 925 may determine the reference downlink component carrier such that a second timing advance group includes a primary component carrier. In some embodiments, the reference downlink component carrier module 925 may determine the reference downlink component carrier utilizing a downlink component carrier linked with an uplink component carrier associated with a random access attempt to determine the reference downlink component carrier. The downlink component carrier may be linked with the uplink component carrier through a SIB2 linkage.
  • the reference downlink component carrier module 925 may determine the reference downlink component carrier based on a Radio Resource Control
  • RRC configuration of the user equipment.
  • device 900-a may send RRC configuration message(s) to a user equipment 115 identifying one carrier as the PCC and additional carriers as SCCs.
  • the carrier that is identified as PCC may serve as the reference downlink carrier for one or more timing advance groups.
  • FIG. 3B illustrates the RRC-configured PCC (DL-1) for a user equipment 115 serves as the reference carrier for component carriers in each of the two timing advance groups 310-a, 310-b.
  • This RRC-based approach may be advantageous when the activation status of the SCCs (DL-2, DL-3) changes from time to time.
  • Device 900-a may be configured for performing random access by a base station in some embodiments.
  • Transmitter module 930 and/or search space module 910 may generate and/or transmit a downlink control message configured to initiate a random access procedure may be transmitted.
  • Receiver module 905 may receive a response to the downlink control message on a physical random access channel (PRACH).
  • Transmitter module 930 and/or search space module 910 may generate and/or transmit an access grant on a primary component carrier (PCC) of a user equipment, wherein the access grant includes information regarding a set of secondary component carriers (SCCs).
  • PCC primary component carrier
  • SCCs secondary component carriers
  • Transmitter module 930, timing advance group index generation module 920, and/or reference downlink component carrier module 925 may generate and/or transmit timing advance (TA) information applicable to the set of SCCs to complete the random access procedure using a carrier in the set of SCCs.
  • TA timing advance
  • Transmitting the downlink control message may include transmitting a physical downlink control channel (PDCCH) message in a UE-specific search space.
  • Transmitting the random access grant may include transmitting a PDCCH message in a common search space of the PCC.
  • PDCCH physical downlink control channel
  • transmitter module 930 and/or search space module 910 may further generate and/or transmit a medium access control (MAC) protocol data unit (PDU) with the random access grant.
  • Transmitter module 930 and/or timing advance group index generation module 920 may generate and/or transmit a timing advance (TA) group index corresponding to the set of SCCs with the random access grant.
  • a configuration of TA groups corresponding to component carriers configured for the UE may be transmitted in some embodiments.
  • the TA group index may be transmitted as part of the MAC PDU.
  • the configuration of TA groups may include at least a first TA group including the PCC, and a second TA group including the set of secondary CCs.
  • Transmitter module 930 and/or reference downlink component carrier module 925 may generate and/or transmit a reference downlink CC for completing the random access procedure based on the TA group index.
  • the transmitter module 930 and/or the timing advance group index generation module 920 may generate and/or transmit a timing advance (TA) group index corresponding to the set of SCCs as part of a PDCCH payload.
  • the downlink control message configured to initiate the random access procedure may include an identifier corresponding to the set of SCCs that may be generated and/or transmitted by the transmitter module 930 and/or search space module 910.
  • Receiving the response to the downlink control message at the receiver module 905 may further include receiving the PRACH on an SCC based on the identifier.
  • FIG. 9B shows a block diagram of a communications system 900-b that may be configured to support multiple timing advancing groups for user equipment.
  • This system 900-b may be an example of aspects of the system 100 depicted in FIG. 1 and/or system 200 of FIG. 2 and/or device 900-a of FIG. 9A , for example.
  • the base station 105-b may include antennas 945, a transceiver module 950, memory 970, and a processor module 965, which each may be in communication, directly or indirectly, with each other (e.g., over one or more buses).
  • the transceiver module 950 may be configured to communicate bi-directionally, via the antennas 945, with the user equipment 115-d.
  • the transceiver module 950 (and/or other components of the base station 105-b) may also be configured to communicate bi-directionally with one or more networks.
  • the base station 105-b may communicate with the network 125-a and/or controller 120-a through network communications module 975.
  • Base station 105-b may be an example of a eNodeB base station, a Home eNodeB base station, a NodeB base station, and/or a Home NodeB base station.
  • the memory 970 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 970 may also store computer-readable, computer-executable software code 971 containing instructions that are configured to, when executed, cause the processor module 965 to perform various functions described herein (e.g., call processing, database management, message routing, etc.).
  • the software 971 may not be directly executable by the processor module 965 but be configured to cause the computer, e.g., when compiled and executed, to perform functions described herein.
  • the processor module 965 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel ® Corporation or AMD ® , a microcontroller, an application specific integrated circuit (ASIC), etc.
  • the processor module 965 may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 30 ms in length) representative of the received audio, provide the audio packets to the transceiver module 950, and provide indications of whether a user is speaking.
  • an encoder may only provide packets to the transceiver module 950, with the provision or withholding/suppression of the packet itself providing the indication of whether a user is speaking.
  • the transceiver module 950 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 945 for transmission, and to demodulate packets received from the antennas 945. While some examples of the base station 105-b may include a single antenna 945, the base station 105-b preferably includes multiple antennas 945 for multiple links which may support carrier aggregation. For example, one or more links may be used to support macro communications with user equipment 115-d.
  • the base station 105-b may further include a communications management module 930.
  • the communications management module 930 may manage communications with other base station 105.
  • the communications management module 930 may be a component of the base station 105-b in communication with some or all of the other components of the base station 105-b via a bus.
  • functionality of the communications management module 930 may be implemented as a component of the transceiver module 950, as a computer program product, and/or as one or more controller elements of the processor module 965.
  • the components for user equipment base station 105-b may be configured to implement aspects discussed above with respect to device 900-a in FIG. 9A and may not be repeated here for the sake of brevity.
  • the timing advance group index generation module 920-a may be an example of the timing advance group index module 920 of FIG. 9 .
  • the reference downlink component carrier module 925-a may be an example of the reference downlink component carrier module 925 of FIG. 9 .
  • Parallel random access module 915-a may be an example of the parallel random access module 915 of FIG. 9 .
  • UESS search space module 911, CSS on PCC search space module 912, and/or CSS on SCC search space module 913 may provide specific functionality individually or in combination for a search space module 910-a that may be an example of search space module 910 of FIG. 9 .
  • Method 1000-a may be implemented various devices including, but not limited to, the base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9A .
  • a timing advance group index may be generated.
  • the timing advance group index may identify a timing advance group from multiple timing advance groups. Each group may include different sets of component carriers.
  • the timing advance group index may be transmitted as part of a random access procedure.
  • a first timing advance group from the multiple timing advance groups includes a primary component carrier and a second timing advance group includes at least one secondary component carrier.
  • the first timing advance group may also include one or more secondary component carriers, while the second timing advance group does not include a primary component carrier.
  • Some embodiments may also include additional timing advance groups besides the first and second timing advance group.
  • the number of timing advance groups may depend upon a variety of factors including, but not limited, propagation delay characteristics, channel characteristics, user equipment device characteristics, and/or bandwidth characteristics of the component carriers.
  • the timing advance group index is transmitted as a single bit of information.
  • a first bit configuration of the single bit of information may indicate that the timing advance group includes a primary component carrier; a second bit configuration of the single bit may indicate that the timing advance group one or more secondary component carriers without the primary component carrier.
  • Some embodiments may include timing advance indexes that may utilize additional bits to convey their information. The number of bits may depend upon the number of timing advance groups.
  • the timing advance group index may be transmitted as part of a MAC payload in some embodiments.
  • the timing advance group index may be transmitted as part of a PDCCH payload.
  • Some embodiments may also include transmitting a component carrier identifier as part of an RRC configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index. The identified component carrier may be utilized for a random access attempt.
  • Some embodiments may enable cross-carrier random access response procedure management through the utilization of the timing advance group index. Some embodiments may enable cross-carrier PDCCH order through the utilization of the timing advance group index.
  • Method 1000-b may be implemented on various devices including, but not limited to, the base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9A .
  • Method 1000-b may be an example or utilize aspects of method 1000-a of FIG. 10A .
  • a timing advance group index may be generated that includes a single bit.
  • the timing advance group index may identify a timing advance group from multiple timing advance groups. Each group may include different sets of component carriers.
  • the timing advance group index may be transmitted as part of a random access response.
  • a component carrier identifier may be transmitted as part of an RRC.
  • cross-carrier random access procedure management may be enabled through the utilization of the timing advance group index and the component carrier identifier.
  • Method 1100-a may be implemented on various devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • a timing advance group index may be received as part of a random access procedure.
  • the timing advance group index may be utilized to determine a timing advance group for transmitting data.
  • Some embodiments may further include utilizing the timing advance group index to enable cross-carrier random access procedure management.
  • Some embodiments may further include utilizing the timing advance group index to enable cross-carrier PDCCH order management.
  • Some embodiments may further include receiving a component carrier identifier as part of an RRC configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index.
  • the RRC configuration may be used to identify a DL component carrier which will serve as a timing reference for component carriers in multiple timing advance groups.
  • a user equipment may utilize its RRC-configured primary component carrier as the timing reference for the component carriers in multiple timing advance groups as discussed in connection with FIG. 3B , or it may use another component carrier which is determined based on the RRC configuration for this purpose. Determining a DL reference carrier for multiple TA groups based on RRC configuration can improve the base station's flexibility to activate/deactivate secondary component carriers. Alternatively, the timing reference may be determine based on a SIB2 linkage as previously discussed.
  • Method 1100-b may be implemented on various devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 7B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8B .
  • Method 1100-b may be an example of or utilize aspects of method 1100-a of FIG. 11A .
  • a timing advance group index may be received as part of a random access response.
  • the timing advance group index may be utilized to determine a timing advance group for transmitting data.
  • a component carrier identifier may be received as part of an RRC configuration to identify a component carrier within a timing advance group associated with a specific timing advance group index, wherein the identified component carrier is utilized for a random access response.
  • the timing advance group index and the component carrier identifier may be utilized to enable cross-carrier random access procedure management.
  • Method 1200-a may be implemented on systems and/or devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • method 1200-a may be implemented on systems and/or devices including, but not limited to, base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9B .
  • a first random access procedure associated with a first timing advance group of component carriers may be performed.
  • a second random access procedure associated with a second timing advance group of component carriers may be performed where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • Some embodiments of method 1200-a may include performing a power prioritization with respect to the first random access procedure and the second random access procedure.
  • Performing the power prioritization may include performing an equal power scaling with respect to the first random access procedure and the second random access procedure.
  • performing the power prioritization may include transmitting a first random access attempt with respect to the first timing advance group of component carriers prior to transmitting a second random access attempt with respect to the second timing advance group of component carriers, where the first timing advance group of component carriers includes a primary component carrier.
  • the first random access procedure may include a non-contention-based random access procedure and the second random access procedure may include a contention based random access procedure.
  • Performing the power prioritization in this case may include transmitting a first random access attempt with respect to the first timing advance group of component carriers prior to transmitting a second random access attempt with respect to the second timing advance group of component carriers.
  • Method 1200-a may further include configuring a first subframe that includes a first random access response as part of the first random access procedure.
  • a second subframe including a second random access response may be configured as part of the second random access procedure.
  • the first subframe and the second subframe may be transmitted.
  • the first and second random access responses may not be transmitted in the same subframe.
  • Some embodiments may include triggering an aperiodic channel quality indicator (A-CQI).
  • A-CQI aperiodic channel quality indicator
  • Method 1200-b may be implemented on systems and/or devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • method 1200-b may be implemented on systems and/or devices including, but not limited to, base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9B .
  • Method 1200-b may be an example of or utilize aspects of method 1200-a of FIG. 12A .
  • a first random access procedure associated with a first timing advance group of component carriers may be performed.
  • a second random access procedure associated with a second timing advance group of component carriers may be performed where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • an equal power scaling may be performed with respect to the first random access procedure and the second random access procedure.
  • FIG. 13 shows a flowchart of a method 1300 for utilizing timing advance group synchronization information.
  • Method 1300 may be implemented on systems and/or devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • method 1300 may be implemented on systems and/or devices including, but not limited to, base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9A .
  • a reference downlink component carrier may be determined.
  • the reference downlink component carrier may be utilized for timing adjustment within a first timing advance group from multiple timing advance groups.
  • Each timing advance group may include at least one downlink component carrier.
  • a second timing advance group includes a primary component carrier.
  • determining the reference downlink component carrier includes utilizing a downlink component carrier linked with an uplink component carrier associated with a random access attempt to determine the reference downlink component carrier.
  • the downlink component carrier may be linked with the uplink component carrier through a SIB2 linkage.
  • determining the reference downlink component carrier may include determining the reference downlink component carrier from an RRC configuration.
  • multiple timing advance groups may share a common reference downlink component carrier.
  • the common reference may be the UE-specific primary component carrier.
  • more than one downlink carrier is designated as a PCC for a particular UE, there may be a many-to-one relationship between timing advance groups and each RRC-configured PCC.
  • different PCCs may serve as reference carriers for different timing advance groups as determined by base station 105 based on channel and interference conditions experienced by the UE, system loading considerations of the component carriers, scheduling requirements, etc.
  • Method 1400 may be implemented on various devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • a downlink control message configured to initiate a random access procedure is received by the UE.
  • the downlink control message may include a message 0 transmission as previously discussed.
  • the UE transmits a response to the downlink control message on a PRACH.
  • the CC for transmitting the PRACH may be determined based on an indicator carried with the message 0 transmission and/or based on an association with the CC on which the message 0 was received.
  • the UE receives an access grant on PCC.
  • the UE determines a set of SCCs based on the random access grant.
  • the random access grant may enable cross-carrier RAR and the UE may determine the set of SCC based on information in the RAR message or corresponding PDCCH payload.
  • the UE may complete the random access procedure using a carrier in the set of SCCs to obtain TA information applicable to the set of SCCs.
  • Receiving the downlink control message may include detecting a PDCCH message in a UE-specific search space.
  • Receiving the random access grant may include detecting a PDCCH message in a common search space of the PCC.
  • the method 1400 may further include obtaining a MAC protocol data unit with the random access grant.
  • a TA group index may be determined corresponding to the set of SCCs based on the MAC PDU.
  • Some embodiments may further include receiving a configuration of TA groups corresponding to component carriers configured for the UE.
  • the configuration of TA groups may include at least a first TA group including the PCC, and a second TA group including only SCCs in a set of secondary CCs.
  • Some embodiments may further include determining a reference downlink CC for completing the random access procedure based on the TA group index.
  • the method 1400 may further include determining a TA group index corresponding to the set of SCCs as part of a PDCCH payload.
  • the downlink control message may be configured to initiate the random access procedure comprises an identifier corresponding to the set of SCCs. Transmitting the response to the downlink control message further include determining an SCC to transmit the PRACH based on the identifier.
  • method 1400 may further include initiating a second random access procedure concurrently with the first random access procedure. Some embodiments may further include determining a priority for allocating power between the first random access procedure and the second random access procedure. Some embodiments may further include allocating power to the first random access procedure at a higher priority than the second random access procedure when the first random access procedure comprises a contention-free random access procedure and the second random access procedure comprises a contention-based random access procedure. Some embodiments may further include allocating power to the second random access procedure at a higher priority than the first random access procedure when the second random access procedure when the second random access procedure is performed in relation to a group of carriers comprising a primary component carrier of the UE. Determining the priority may include performing an equal power scaling for each CC.
  • Method 1500 may be implemented on various devices including, but not limited to, the base stations 105 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 9B , and/or device 900-a of FIG. 9A .
  • a downlink control message configured to initiate a random access procedure may be transmitted.
  • a response to the downlink control message may be received on a PRACH.
  • an access grant may be transmitted on a PCC of a user equipment, wherein the access grant includes information regarding a set of SCCs.
  • TA information applicable to the set of SCCs may be transmitted to complete the random access procedure using a carrier in the set of SCCs.
  • Transmitting the downlink control message may include transmitting a PDCCH message in a UE-specific search space.
  • Transmitting the random access grant may include transmitting a PDCCH message in a common search space of the PCC.
  • method 1500 may further include transmitting a medium access control (MAC) protocol data unit (PDU) with the random access grant.
  • a TA group index corresponding to the set of SCCs with the random access grant may be transmitted.
  • a configuration of TA groups corresponding to component carriers configured for the UE may be transmitted.
  • the TA group index may be transmitted as part of the MAC PDU.
  • the configuration of TA groups may include at least a first TA group including the PCC, and a second TA group including the set of secondary CCs.
  • a reference downlink CC may be transmitted for completing the random access procedure based on the TA group index.
  • method 1500 may further include transmitting a TA group index corresponding to the set of SCCs as part of a PDCCH payload.
  • the downlink control message configured to initiate the random access procedure may include an identifier corresponding to the set of SCCs.
  • Receiving the response to the downlink control message may further include receiving the PRACH on an SCC based on the identifier.
  • FIG. 16 a flow diagram of a method 1600 for utilizing timing advance group synchronization information in accordance with various embodiments.
  • Method 1600 may be implemented on various devices including, but not limited to, the user equipment 115 described with reference to FIG. 1 , FIG. 2 , FIG. 4A , FIG. 4B , 4C , FIG. 7B , FIG. 8B , FIG. 9B , and/or device 700-a of FIG. 7A and/or device 800-a of FIG. 8A .
  • multiple component carriers as part of a carrier aggregation operation may be identified.
  • the multiple component carriers may include one or more downlink component carriers and two or more uplink component carriers.
  • multiple timing advance groups may be determined. Each component carrier in the multiple component carriers may be included in one of the timing advance groups.
  • a first timing advance group from the multiple timing advance groups may be identified.
  • a reference downlink component carrier may be determined for the first timing advance group based at least in part on an RRC configuration.
  • the determined reference downlink component carrier may be utilized for timing adjustment within at least the first timing advance group.
  • the method further includes receiving an indication of a primary downlink component carrier through the RRC configuration.
  • the primary downlink component carrier may be the determined reference downlink component carrier.
  • Some embodiments include utilizing the primary downlink component carrier for timing adjustment within a second timing advance group from the multiple timing advance groups.
  • the primary downlink component carrier may be included in the second timing advance group.
  • One or more downlink component carriers of the one or more identified downlink carriers may be included in the first timing advance group. Determining the reference downlink component carrier may be based on an RRC configuration for the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier for the first timing advance group may be determined to be a downlink component carrier with a smallest cell index of multiple cell indices configured for each one of the one or more downlink component carriers in the first timing advance group.
  • the reference downlink component carrier may be determined from a set of activated downlink component carriers.
  • the one or more downlink component carriers and the two or more uplink component carriers may be associated with two or more bands.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers of the same band or similar band.
  • the reference downlink component carrier may be determined to be a downlink component carrier of the same or similar band as an uplink component carrier associated with a random access attempt for the first timing advance group..
  • Some embodiments include performing multiple random access procedures in parallel with respect to two or more of the multiple timing advance groups.
  • Performing the multiple random access procedures may include performing a first random access procedure linked with the first timing advance group; and/or performing a second random access procedure linked with a second timing advance group of the multiple timing advance groups, where one or more portions of the second random access procedure overlap with one or more portions of the first random access procedure.
  • Some embodiments include initiating a non-contention based random access procedure on an uplink component carrier within the first timing advance group through utilizing a downlink control channel transmitted on a downlink component carrier that is not linked with the uplink component carrier via a system information block broadcast.
  • a cross-carrier indication field may be included in the downlink control channel to enable cross-carrier scheduling.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a similar delay due to downlink repeaters.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a same carrier type where the carrier type includes at least a legacy carrier type or a new carrier type.
  • the reference downlink component carrier for the first timing advance group may be determined from a set of downlink component carriers with a similar activity factor.
  • Method 1600 may take into account different characteristics of a component carrier (e.g., whether it is equipped with a repeater, whether it is always on or periodically turned off, whether it is a new or legacy carrier type, etc.) in determining the reference downlink component carrier.
  • a component carrier may be equipped with a repeater while another component carrier is not.
  • the component carriers of the same or similar delay characteristics due to repeaters either downlink repeaters, or uplink repeaters, or a combination thereof
  • Different component carriers may have different activity factors.
  • a component carrier may periodically be turned on and carries much less frequent downlink information compared with a regular carrier.
  • a component carrier may be of a legacy carrier type and another can be of a new carrier type. Carriers of the same type may be determined to be possible candidates for the reference downlink component carrier for a given timing advance group.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended embodiments. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes computer storage media.
  • a storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable storage media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP19214979.7A 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte Active EP3684113B1 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US201161533614P 2011-09-12 2011-09-12
US201261610151P 2012-03-13 2012-03-13
US13/610,139 US9204411B2 (en) 2011-09-12 2012-09-11 Support of multiple timing advance groups for user equipment in carrier aggregation in LTE
EP12766258.3A EP2756719B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte
PCT/US2012/054848 WO2013040026A1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP12766258.3A Division EP2756719B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte
EP12766258.3A Division-Into EP2756719B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte

Publications (2)

Publication Number Publication Date
EP3684113A1 EP3684113A1 (en) 2020-07-22
EP3684113B1 true EP3684113B1 (en) 2022-04-06

Family

ID=47829796

Family Applications (2)

Application Number Title Priority Date Filing Date
EP19214979.7A Active EP3684113B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte
EP12766258.3A Active EP2756719B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP12766258.3A Active EP2756719B1 (en) 2011-09-12 2012-09-12 Support of multiple timing advance groups for user equipment in carrier aggregation in lte

Country Status (8)

Country Link
US (1) US9204411B2 (ja)
EP (2) EP3684113B1 (ja)
JP (1) JP5882471B2 (ja)
KR (2) KR101860517B1 (ja)
CN (1) CN103947267B (ja)
ES (1) ES2784513T3 (ja)
HU (1) HUE049049T2 (ja)
WO (1) WO2013040026A1 (ja)

Families Citing this family (72)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201249150A (en) * 2007-09-28 2012-12-01 Interdigital Patent Holdings Method and apparatus for terminating transmission of a message in a enhanced random access channel
KR101681622B1 (ko) 2008-01-02 2016-12-01 시그널 트러스트 포 와이어리스 이노베이션 셀 재선택을 위한 방법 및 장치
JP5565475B2 (ja) * 2011-02-10 2014-08-06 富士通株式会社 無線通信システム、受信装置、送信装置および無線通信方法
US8395985B2 (en) 2011-07-25 2013-03-12 Ofinno Technologies, Llc Time alignment in multicarrier OFDM network
EP2797377B1 (en) * 2011-12-20 2018-12-05 LG Electronics Inc. Method and apparatus for performing random access process in wireless communication system
US9237537B2 (en) 2012-01-25 2016-01-12 Ofinno Technologies, Llc Random access process in a multicarrier base station and wireless device
EP3937551A3 (en) 2012-01-25 2022-02-09 Comcast Cable Communications, LLC Random access channel in multicarrier wireless communications with timing advance groups
US8526389B2 (en) 2012-01-25 2013-09-03 Ofinno Technologies, Llc Power scaling in multicarrier wireless device
EP2621210B1 (en) * 2012-01-27 2014-01-22 Alcatel Lucent Method for determining cell configuration parameters in a wireless telecommunication network
IN2014KN01525A (ja) * 2012-01-29 2015-10-23 Ericsson Telefon Ab L M
KR101885540B1 (ko) 2012-03-23 2018-09-11 주식회사 골드피크이노베이션즈 다중 요소 반송파 시스템에서 상향링크 동기화 장치 및 방법
US20130258862A1 (en) 2012-04-01 2013-10-03 Esmael Hejazi Dinan Radio Access for a Wireless Device and Base Station
US20130259008A1 (en) 2012-04-01 2013-10-03 Esmael Hejazi Dinan Random Access Response Process in a Wireless Communications
US11943813B2 (en) 2012-04-01 2024-03-26 Comcast Cable Communications, Llc Cell grouping for wireless communications
US9215678B2 (en) 2012-04-01 2015-12-15 Ofinno Technologies, Llc Timing advance timer configuration in a wireless device and a base station
US11825419B2 (en) 2012-04-16 2023-11-21 Comcast Cable Communications, Llc Cell timing in a wireless device and base station
US8964593B2 (en) 2012-04-16 2015-02-24 Ofinno Technologies, Llc Wireless device transmission power
US8989128B2 (en) 2012-04-20 2015-03-24 Ofinno Technologies, Llc Cell timing in a wireless device and base station
US11252679B2 (en) 2012-04-16 2022-02-15 Comcast Cable Communications, Llc Signal transmission power adjustment in a wireless device
WO2013158511A1 (en) 2012-04-16 2013-10-24 Dinan Esmael Hejazi Cell group configuration for uplink transmission in a multicarrier wireless device and base station with timing advance groups
US8958342B2 (en) 2012-04-17 2015-02-17 Ofinno Technologies, Llc Uplink transmission power in a multicarrier wireless device
US11582704B2 (en) 2012-04-16 2023-02-14 Comcast Cable Communications, Llc Signal transmission power adjustment in a wireless device
US9179425B2 (en) 2012-04-17 2015-11-03 Ofinno Technologies, Llc Transmit power control in multicarrier communications
US8971298B2 (en) 2012-06-18 2015-03-03 Ofinno Technologies, Llc Wireless device connection to an application server
US9084228B2 (en) 2012-06-20 2015-07-14 Ofinno Technologies, Llc Automobile communication device
US9179457B2 (en) 2012-06-20 2015-11-03 Ofinno Technologies, Llc Carrier configuration in wireless networks
US9107206B2 (en) 2012-06-18 2015-08-11 Ofinne Technologies, LLC Carrier grouping in multicarrier wireless networks
US11882560B2 (en) 2012-06-18 2024-01-23 Comcast Cable Communications, Llc Carrier grouping in multicarrier wireless networks
US9210619B2 (en) 2012-06-20 2015-12-08 Ofinno Technologies, Llc Signalling mechanisms for wireless device handover
US11622372B2 (en) 2012-06-18 2023-04-04 Comcast Cable Communications, Llc Communication device
US9113387B2 (en) 2012-06-20 2015-08-18 Ofinno Technologies, Llc Handover signalling in wireless networks
WO2014015479A1 (zh) * 2012-07-24 2014-01-30 华为技术有限公司 下行控制信息的发送、接收方法、服务节点及用户设备
CN109889248A (zh) * 2012-11-12 2019-06-14 华为技术有限公司 上报信道状态信息的方法、用户设备及基站
EP2941077B1 (en) * 2013-01-18 2019-06-05 Huawei Technologies Co., Ltd. Pdsch transmission method and device
KR20140116705A (ko) * 2013-03-25 2014-10-06 주식회사 팬택 무선 통신 시스템에서 NCT를 고려한 CoMP 지원 방법 및 그 장치
RU2631251C2 (ru) * 2013-05-31 2017-09-20 Хуавэй Текнолоджиз Ко., Лтд. Способ обмена информацией, базовая станция и устройство пользователя
EP3016467B1 (en) 2013-07-26 2019-04-03 Huawei Technologies Co., Ltd. Data transmission method, device and system
US20150036666A1 (en) * 2013-07-30 2015-02-05 Blackberry Limited Timing Advance Group in LTE Small Cell Enhancement
BR112015031463B1 (pt) * 2013-08-09 2023-04-18 Huawei Technologies Co., Ltd Método e aparelho de ajuste de valor de temporização
CN105580457B (zh) * 2013-09-10 2019-09-10 Lg电子株式会社 确定上行链路发送定时的方法及使用该方法的用户设备
JP5913255B2 (ja) * 2013-10-31 2016-04-27 株式会社Ｎｔｔドコモ 移動局及び移動通信方法
KR102156798B1 (ko) * 2014-01-16 2020-09-16 삼성전자주식회사 무선 통신 시스템에서 단말의 타이밍을 제어하기 위한 방법 및 그 전자 장치
US10499421B2 (en) * 2014-03-21 2019-12-03 Qualcomm Incorporated Techniques for configuring preamble and overhead signals for transmissions in an unlicensed radio frequency spectrum band
KR101982306B1 (ko) * 2014-03-21 2019-05-24 후아웨이 테크놀러지 컴퍼니 리미티드 랜덤 액세스 응답 방법, 기지국, 및 단말기
US10609663B2 (en) * 2014-07-11 2020-03-31 Qualcomm Incorporated Techniques for reporting timing differences in multiple connectivity wireless communications
CN104640118B (zh) * 2015-01-30 2019-02-12 中兴通讯股份有限公司 小区分组方法、同步失效处理方法、基站和用户设备
PL3351047T3 (pl) * 2015-09-18 2021-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Procedura dostępu losowego dla ograniczenia opóźnienia
WO2017087705A1 (en) * 2015-11-17 2017-05-26 Wilson Electronics, Llc Cellular signal booster with multiple signal chains
US10986599B2 (en) * 2016-05-13 2021-04-20 Huawei Technologies Co., Ltd. TA obtaining method and apparatus
EP3503660B1 (en) * 2016-08-18 2021-08-11 LG Electronics Inc. Method for transmitting uplink signal through multiple unlicensed component carriers in wireless communication system supporting unlicensed band, and device supporting same
US11160071B2 (en) * 2016-10-18 2021-10-26 Qualcomm Incorporated Carrier aggregation with self-contained subframe for efficient modem processing
US11770855B2 (en) * 2016-10-19 2023-09-26 Qualcomm Incorporated Random access channel (RACH) procedure design
US10433342B2 (en) 2016-10-19 2019-10-01 Qualcomm Incorporated Enhanced random access channel (RACH) procedure
US10257835B2 (en) 2017-03-24 2019-04-09 At&T Intellectual Property I, L.P. Facilitating enhanced beam management in a wireless communication system
US9949298B1 (en) 2017-05-04 2018-04-17 At&T Intellectual Property I, L.P. Facilitating signaling and transmission protocols for enhanced beam management for initial access
EP3639606A4 (en) * 2017-06-16 2020-12-16 Motorola Mobility LLC IMPLEMENTATION OF MULTIPLE RANDOM ACCESS METHODS
US20200169990A1 (en) * 2017-08-10 2020-05-28 Ntt Docomo, Inc. User terminal and radio communication method
JP2018011348A (ja) * 2017-09-20 2018-01-18 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． データ送信方法、デバイスおよびシステム
US11277792B2 (en) * 2017-11-17 2022-03-15 Qualcomm Incorporated Methods and apparatus for reporting aperiodic CQI in a new SCell state of LTE carrier aggregation
US10517045B2 (en) * 2017-11-17 2019-12-24 Qualcomm Incorporated Techniques for power control using carrier aggregation in wireless communications
US10419954B1 (en) * 2018-04-11 2019-09-17 Cisco Technology, Inc. Two stage clustering of wireless access points
CN110831238B (zh) * 2018-08-09 2022-12-30 中兴通讯股份有限公司 数据的发送、资源的获取方法及装置
US10779251B2 (en) * 2018-09-25 2020-09-15 Huawei Technologies Co., Ltd. Timing advance in new radio
US11723067B2 (en) * 2019-07-18 2023-08-08 Qualcomm Incorporated Supporting cross-TAG scheduling and 2-step RACH payload transmission for a PDCCH-ordered contention-free random access procedure
US11671890B2 (en) 2019-12-23 2023-06-06 Qualcomm Incorporated Timing advance group reporting for layer 1/layer 2-centric inter-cell mobility
US11943725B2 (en) 2020-01-24 2024-03-26 Qualcomm Incorporated Techniques for timing advance group per subset of synchronization signal blocks in a wireless communication system
US11412471B2 (en) * 2020-04-20 2022-08-09 AR & NS Investment, LLC Repeater device with slave mode
US11405096B2 (en) * 2020-07-15 2022-08-02 At&T Intellectual Property I, L.P. System and method to improve carrier aggregation efficiency for aerial user equipment over terrestrial 5G networks
WO2022078920A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for propagation delay compensation
US20240188016A1 (en) * 2021-04-02 2024-06-06 Ntt Docomo, Inc. Terminal, radio communication method, and base station
WO2024069583A1 (en) * 2022-09-30 2024-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Handling time overlapped ul transmissions
WO2024103218A1 (en) * 2022-11-14 2024-05-23 Qualcomm Incorporated Cbra enhancement without ssb grouping

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN201409229Y (zh) * 2007-10-25 2010-02-17 交互数字专利控股公司 一种无线发射接收单元
KR101648241B1 (ko) 2009-06-26 2016-08-12 텔레폰악티에볼라겟엘엠에릭슨(펍) 전기통신망에서 방법 및 배열
CN102014477B (zh) * 2009-10-30 2013-11-06 电信科学技术研究院 一种上行同步的方法、装置和系统
JP5702806B2 (ja) 2010-01-08 2015-04-15 インターデイジタル パテント ホールディングス インコーポレイテッド 複数のアップリンクキャリアとのタイムアライメントの維持
KR101753586B1 (ko) 2010-02-03 2017-07-04 엘지전자 주식회사 무선 통신 시스템에서 제어 정보의 전송 방법 및 장치
US20110243111A1 (en) 2010-03-31 2011-10-06 Niklas Andgart Timing of Uplink Transmissions in a Multi-Carrier Communication System
US9084195B2 (en) * 2010-04-01 2015-07-14 Nokia Technologies Oy Multiple timing advance and carrier aggregation
CN102884848B (zh) 2010-04-06 2016-02-17 上海贝尔股份有限公司 载波聚合的无线网络中用于定时提前的方法和装置
WO2012041422A2 (en) 2010-09-30 2012-04-05 Panasonic Corporation Timing advance configuration for multiple uplink component carriers
US9467959B2 (en) * 2011-04-01 2016-10-11 Mediatek, Inc. Method of maintaining multiple timing advance
TW201731266A (zh) * 2011-05-10 2017-09-01 內數位專利控股公司 獲德次胞元上鏈定時校準方法及裝置

Also Published As

Publication number Publication date
KR101860517B1 (ko) 2018-05-23
KR20140068184A (ko) 2014-06-05
JP5882471B2 (ja) 2016-03-09
HUE049049T2 (hu) 2020-09-28
EP2756719A1 (en) 2014-07-23
CN103947267A (zh) 2014-07-23
KR101625568B1 (ko) 2016-05-30
WO2013040026A1 (en) 2013-03-21
US20130064165A1 (en) 2013-03-14
JP2014526834A (ja) 2014-10-06
KR20160062221A (ko) 2016-06-01
CN103947267B (zh) 2017-11-14
EP2756719B1 (en) 2020-01-15
US9204411B2 (en) 2015-12-01
ES2784513T3 (es) 2020-09-28
EP3684113A1 (en) 2020-07-22

Similar Documents

Publication Publication Date Title
EP3684113B1 (en) Support of multiple timing advance groups for user equipment in carrier aggregation in lte
CN110089178B (zh) 具有特定于用户设备的资源的公共控制资源集合
EP3577974B1 (en) Half-duplex operation in new radio systems
KR102537041B1 (ko) 캐리어 집성을 위한 사운딩 기준 신호 송신
CN108370301B (zh) 用于基于竞争的物理上行链路共享信道的方法和装置
CN108886447B (zh) 用于pusch传输的用户设备、基站和方法
KR102150770B1 (ko) 로우 레이턴시 디바이스-투-디바이스 통신
EP3284304B1 (en) Random access for low latency wireless communications
EP3266253B1 (en) Repetition level coverage enhancement techniques for physical random access channel transmissions
EP3243351B1 (en) Evolved multimedia broadcast multicast service on enhanced component carriers
KR102339312B1 (ko) 듀얼 pucch에 대한 시간 정렬 프로시저들
EP3262779B1 (en) Frequency resource allocation for a narrow-band cellular internet of things system
EP3536052B1 (en) Power control, reporting techniques, and control channel configuration in unlicensed spectrum and licensed assisted access
EP3688946B1 (en) Increasing physical random access capacity using orthogonal cover codes
KR20190131534A (ko) 저 레이턴시 무선 통신을 위한 스케줄링 요청들 및 버퍼 상태 보고들
KR102586657B1 (ko) 향상된 캐리어 어그리게이션을 위한 채널 상태 정보
AU2015300974A1 (en) Linked narrowband operation for MTC
WO2011097998A1 (zh) 非竞争随机接入的调度及前导码发送方法、系统和设备
US20140307603A1 (en) Discontinuous reception for multicarrier systems with flexible bandwidth carrier
KR102387908B1 (ko) 커버리지 향상을 위한 물리 브로드캐스트 채널
JP2018534832A (ja) 拡張キャリアアグリゲーションに関するチャネル状態の計算
US10038537B2 (en) Common search space in secondary ENBS

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20191210

AC Divisional application: reference to earlier application

Ref document number: 2756719

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20211109

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 2756719

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1482585

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012078021

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1482585

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220808

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220706

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220707

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220706

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220806

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012078021

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20230110

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220912

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220912

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20120912

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240813

Year of fee payment: 13

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220406

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240808

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240808

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240808

Year of fee payment: 13