Method and apparatus for activating and deactivating component carriers
Abstract
Kind Code: A1 Transmitting and receiving on multiple carriers significantly increases the power consumption of a WTRU. Enabling and disabling additional component carriers on demand and on-the-fly is critical to conserving WTRU resources and providing power consumption savings. Kind Code: A1 Methods and apparatus are described for performing bandwidth aggregation by concurrently monitoring and processing a number of simultaneously non-adjacent or contiguous component carriers in the downlink. A WTRU may be configured by an eNodeB to support additional component carriers. Additional preconfigured component carriers can be used. Various methods for enabling and disabling additional component carriers are also described. [Selection drawing] Fig. 4

Term
15.9 yearsto projected expiry
Projected expiry 29 August 2042, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
16 claims: 5 independent, 11 dependent
- 1発展型ノードB(eノードB)により実装される方法であって、第1のコンポーネントキャリアを通じて、無線リソース制御(RRC)接続再構成メッセージを無線送受信ユニット(WTRU)に送信するステップであって、前記RRC接続再構成メッセージは、前記WTRUが複数の追加のコンポーネントキャリアをサポートするよう事前構成し、前記複数の追加のコンポーネントキャリアの各々は、前記WTRUによる使用に対して最初に無効化され、前記RRC接続再構成メッセージは、後続のコンポーネントキャリア有効化の間の参照のために前記複数の追加のコンポーネントキャリアの各々に割り当てられたそれぞれの識別子を示す、ステップと、前記WTRUによる使用のために前記複数の追加のコンポーネントキャリアのうちの1つまたは複数を有効化する媒体アクセス制御(MAC)制御要素(CE)を前記WTRUに送信するステップであって、前記MAC CEは、前記複数のコンポーネントキャリアのうちの1つまたは複数のどれが前記WTRUによる使用のために有効化されることになるかを示すビットフィールドを含み、前記MAC CEに含まれる前記ビットフィールドおよび前記RRC接続再構成メッセージにおける第2のコンポーネントキャリアに割り当てられた前記それぞれの識別子は、前記第2のコンポーネントキャリアが有効化されることになることを前記WTRUに示す、ステップと、前記第2のコンポーネントキャリアを通じて、物理ダウンリンク制御チャネル(PDCCH)送信を前記WTRUに送信するステップであって、前記PDCCH送信は、前記第2のコンポーネントキャリアを通じた前記WTRUのための物理ダウンリンク共有チャネル(PDSCH)送信をスケジューリングし、前記PDCCH送信は、前記MAC CEの前記ビットフィールドを介する前記第2のコンポーネントキャリアの前記有効化の後に、前記第2のコンポーネントキャリアを通じて前記WTRUへ送信される、ステップと、前記第2のコンポーネントキャリアを通じて送信された前記PDCCH送信に従って、前記第2のコンポーネントキャリアを通じて、前記PDSCH送信を前記WTRUに送信するステップと、を備える、方法。
- 2前記WTRUのための前記第2のコンポーネントキャリアに対する無効化タイマが満了となったと判定するステップと、前記第2のコンポーネントキャリアに対する前記無効化タイマが満了となったと判定したことに基づいて、前記第2のコンポーネントキャリアを通じて前記WTRUのためにPDCCH送信を送信することを停止するステップと、を更に備える、請求項1に記載の方法。
- 3前記MAC CEにおける前記ビットフィールドは、前記WTRUによる使用のために複数の追加のコンポーネントキャリアが有効化されることになることを示す、請求項1に記載の方法。
- 4複数のコンポーネントキャリアを同時にサポートするためのWTRUの能力を示す能力情報を受信するステップを更に備える、請求項1に記載の方法。
- 5前記第1のコンポーネントキャリア上での前記MAC CEの受信の後、前記WTRUが前記第2のコンポーネントキャリア上のPDCCH送信を監視することをセットアップすることの可能にする予め定義された遅延が定義される、請求項1に記載の方法。
- 6第2のMAC CEを前記WTRUに送信するステップであって、前記第2のMAC CEは、前記WTRUによりさらに使用されることから、1つまたは複数の有効なコンポーネントを無効化し、前記第2のMAC CEは、1つまたは複数の有効なコンポーネントキャリアのどれが前記WTRUのよる更なる使用に対して無効化されるかを示すビットフィールドを含む、ステップと、前記第2のMAC CEを前記WTRUに送信することに基づいて、前記第2のコンポーネントキャリアを通じてPDCCH送信を前記WTRUに送信することを停止するステップと、をさらに備える、請求項1に記載の方法。
- 7前記第2のMAC CEは、前記WTRUによりさらに使用されることから、複数の有効なコンポーネントキャリアを無効化する、請求項6に記載の方法。
- 8前記識別子は、割り当てられたビット組み合わせに対応する、請求項1に記載の方法。
- 9プロセッサおよびメモリを備えた発展型ノードB(eノードB)により実装される方法であって、前記プロセッサおよびメモリは、第1のコンポーネントキャリアを通じて、無線リソース制御(RRC)接続再構成メッセージを無線送受信ユニット(WTRU)に送信し、前記RRC接続再構成メッセージは、前記WTRUが複数の追加のコンポーネントキャリアをサポートするよう事前構成し、前記複数の追加のコンポーネントキャリアの各々は、前記WTRUによる使用に対して最初に無効化され、前記RRC接続再構成メッセージは、後続のコンポーネントキャリア有効化の間の参照のために前記複数の追加のコンポーネントキャリアの各々に割り当てられたそれぞれの識別子を示し、前記WTRUによる使用のために前記複数の追加のコンポーネントキャリアのうちの1つまたは複数を有効化する媒体アクセス制御(MAC)制御要素(CE)を前記WTRUに送信し、前記MAC CEは、前記複数のコンポーネントキャリアのうちの1つまたは複数のどれが前記WTRUによる使用のために有効化されることになるかを示すビットフィールドを含み、前記MAC CEに含まれる前記ビットフィールドおよび前記RRC接続再構成メッセージにおける第2のコンポーネントキャリアに割り当てられた前記それぞれの識別子は、前記第2のコンポーネントキャリアが有効化されることになることを前記WTRUに示し、前記第2のコンポーネントキャリアを通じて、物理ダウンリンク制御チャネル(PDCCH)送信を前記WTRUに送信し、前記PDCCH送信は、前記第2のコンポーネントキャリアを通じた前記WTRUのための物理ダウンリンク共有チャネル(PDSCH)送信をスケジューリングし、前記PDCCH送信は、前記MAC CEの前記ビットフィールドを介する前記第2のコンポーネントキャリアの前記有効化の後に、前記第2のコンポーネントキャリアを通じて前記WTRUへ送信され、前記第2のコンポーネントキャリアを通じて送信された前記PDCCH送信に従って、前記第2のコンポーネントキャリアを通じて、前記PDSCH送信を前記WTRUに送信する、ように構成された、eノードB。
- 10前記プロセッサおよびメモリは、前記WTRUのための前記第2のコンポーネントキャリアに対する無効化タイマが満了となったと判定し、前記第2のコンポーネントキャリアに対する前記無効化タイマが満了となったと判定したことに基づいて、前記第2のコンポーネントキャリアを通じて前記WTRUのためにPDCCH送信を送信することを停止する、ように構成された、請求項9に記載のeノードB。
- 11前記MAC CEにおける前記ビットフィールドは、前記WTRUによる使用のために複数の追加のコンポーネントキャリアが有効化されることになることを示す、請求項9に記載のeノードB。
- 12前記プロセッサおよびメモリは、複数のコンポーネントキャリアを同時にサポートするためのWTRUの能力を示す能力情報を受信するように構成された、請求項9に記載のeノードB。
- 13前記第1のコンポーネントキャリア上での前記MAC CEの受信の後、前記WTRUが前記第2のコンポーネントキャリア上のPDCCH送信を監視することをセットアップすることの可能にする予め定義された遅延が定義される、請求項9に記載のeノードB。
- 14前記プロセッサおよびメモリは、第2のMAC CEを前記WTRUに送信し、前記第2のMAC CEは、前記WTRUによりさらに使用されることから、1つまたは複数の有効なコンポーネントを無効化し、前記第2のMAC CEは、1つまたは複数の有効なコンポーネントキャリアのどれが前記WTRUのよる更なる使用に対して無効化されるかを示すビットフィールドを含み、前記第2のMAC CEを前記WTRUに送信することに基づいて、前記第2のコンポーネントキャリアを通じてPDCCH送信を前記WTRUに送信することを停止する、ように構成された、請求項9に記載のeノードB。
- 15前記第2のMAC CEは、前記WTRUによりさらに使用されることから、複数の有効なコンポーネントキャリアを無効化する、請求項14に記載のeノードB。
- 16前記識別子は、割り当てられたビット組み合わせに対応する、請求項9に記載のeノードB。
Independent claims16
88 paragraphs, as filed
This application relates to wireless communications.
An important feature of LTE-A (Long Term Evolution Advanced) is higher data rates. This is supported by allowing the Wireless Transmit/Receive Unit (WTRU) to transmit and receive data on multiple LTE component carriers simultaneously on both the uplink and downlink. This is called carrier aggregation.
Transmitting and receiving on multiple carriers significantly increases the power consumption of the WTRU. The power consumption of the analog front end (which represents a significant percentage of the total power consumption in that WTRU) scales linearly over the bandwidth or multiple aggregated fundamental frequency blocks (i.e. component carriers). known to be proportional. Enabling and disabling additional component carriers on demand and on-the-fly conserves WTRU resources (e.g., Hybrid Automatic Repeat Request (HARQ) processing (Channel Quality Indicator (CQI)). ) and SRS (Sounding Reference Signal) reporting), buffer occupancy and buffer management (e.g. BSR (Buffer Status Report) reporting, and scheduling processes), and providing power consumption savings. is important.
A method and apparatus are described for performing bandwidth aggregation by simultaneously monitoring and processing a number of simultaneously non-adjacent or contiguous component carriers in the downlink. A WTRU may be configured by an eNodeB to support additional component carriers. Additional preconfigured component carriers can be used. Various methods for enabling or disabling additional component carriers are also described.
A more detailed understanding can be obtained from the following description, given by way of example in connection with the accompanying drawings.
<figref num="1">1 illustrates a wireless communication system including an eNodeB and a WTRU; FIG.</figref><figref num="2">2 is a block diagram of the eNodeB of FIG. 1; FIG.</figref><figref num="3">2 is a block diagram of the WTRU of FIG. 1; FIG.</figref><figref num="4">Fig. 3 shows a procedure for monitoring and processing component carriers;</figref><figref num="5">Fig. 3 shows a procedure for monitoring and processing component carriers;</figref>
In future references, the term "WTRU" includes, but is not limited to, User Equipment (UE), Mobile Stations, Fixed or Mobile Subscriber Units, Pagers, Mobile Phones, Personal Digital Assistants (PDAs). information terminal), computer, or any other type of user device capable of operating in a wireless environment.
As used hereinafter, the term "eNodeB" is used without limitation to refer to base stations, site controllers, APs (access points), or any other type of interface device capable of operating in a wireless environment. include.
FIG. 1 shows wireless communication system 100 including eNodeB 105 and WTRU 110 . The eNodeB 105 is configured to send an RRC (Radio Resource Control) connection reconfiguration message 115 to the WTRU 110 .
Various methods and apparatus are described for enabling or disabling transmission and reception on different carriers in an LTE-A system that employs carrier aggregation.
Transition to Connected Mode In standby mode, the WTRU 110 monitors and processes only a single component carrier. Standby mode procedures such as SI (System Information) acquisition and PI (Paging Indication) monitoring are transparent to the WTRU's 110 multi-carrier capabilities. Schemes such as cell selection and cell reselection can be the same with or without carrier aggregation (hereinafter referred to as bandwidth aggregation) capability, or as an input to system selection, The bandwidth aggregation capabilities of the infrastructure (eNodeB 105) can be considered. However, when the WTRU 110 transitions to RRC Connected mode (typically through an RRC connection request), the WTRU 110 informs the network of the WTRU's capabilities for bandwidth aggregation.
The WTRU bandwidth aggregation capability may be defined as the number of simultaneous non-contiguous component carriers that can be monitored and processed simultaneously in the downlink for each band. An alternative metric can be the number of RF (Radio Frequency) receivers (different receivers handle non-adjacent carriers) and the largest bandwidth of each receiver. Consider one example with five component carriers: carriers 1 and 2 are adjacent to each other, carriers 3, 4 and 5 are not, and carriers 3, 4 and 5 are adjacent.
It is also possible to define the WTRU bandwidth aggregation capability as the number of simultaneously contiguous carriers that can be monitored and processed simultaneously in the downlink for each band.
It is also possible to define the WTRU bandwidth aggregation capability as the largest supported bandwidth of aggregated contiguous carriers, not just the number of carriers but also the bandwidth.
It is also possible to define the WTRU bandwidth aggregation capability as the largest total bandwidth of aggregated carriers (neighboring or non-adjacent).
It is also possible to define the WTRU bandwidth aggregation capability as the maximum bandwidth supported per single carrier (according to the current WTRU capabilities of LTE).
Component Carrier RRC Configuration After the WTRU has informed the network about the WTRU's bandwidth capabilities in the RRC connection procedure, an eNodeB that supports bandwidth aggregation may configure additional component carriers (i.e. preconfigured A WTRU can be configured to support additional component carriers). This shall be done by an RRC connection reconfiguration message carrying information enabling the WTRU to set up monitoring (granting and allocation) of one or more additional downlink and/or uplink carriers. can be done. Information contained in the RRC connection reconfiguration message includes cell identification, carrier center frequency, carrier bandwidth, carrier direction (uplink or downlink), and activation and synchronization of additional preconfigured component carriers. may contain other information needed to timely set up the
One RRC connection reconfiguration message is sufficient to set up more than one component carrier by accumulating the previously described information for all preconfigured additional component carriers.
Receipt of the RRC connection reconfiguration message alone may not enable monitoring and processing of additional component carriers immediately or after some delay. In this case, only an explicit or implicit enable command may allow the WTRU to begin monitoring and processing additional carriers, as described below. Alternatively, the RRC connection reconfiguration message may include a field that tells whether monitoring and processing should begin after the reconfiguration procedure has successfully completed. This is useful in setting up to verify that additional pre-configured component carriers are operational. Alternatively, receipt of the RRC connection reconfiguration message enables monitoring and processing of additional component carriers immediately or after some delay.
The RRC connection reconfiguration message allows the WTRU to set up additional component carriers controlled by another eNodeB, such as timing advance and other synchronization related information. May contain additional information.
The RRC connection reconfiguration message can provide one specific C-RNTI (Cell Radio Network Temporary Identifier) for each additional component carrier.
The RRC connection reconfiguration message allocates, for efficiency, a bit combination to each preconfigured additional component carrier up to the maximum number of concurrent additional component carriers supported, and the allocated bit combination so that the enabling or disabling of individual component carriers is mentioned.
[mechanism for enabling or disabling pre-configured additional component carriers]
MAC Control Element Enabling or disabling a pre-configured additional carrier or a predefined subset of pre-configured additional carriers is controlled by the reception of a MAC (Medium Access Control) CE (Control Element). can occur when This enabling or disabling can be performed after a predefined (fixed or configurable through higher layer signaling) delay, or immediately after receipt of the MAC CE. This will be implemented by a new type of MAC CE called MAC_CE_Activation control element.
The MAC_CE_Enable control element may contain a field of bit combinations to indicate which preconfigured carriers are enabled or disabled. Alternatively, the carriers that are enabled or disabled can be indicated by the C-RNTI value used for transmission of MAC PDUs containing MAC Control Elements. A MAC_CE_ENABLE control element can enable or disable multiple carriers at the same time by aggregating bit combinations or sending multiple MAC PDUs using different C-RNTIs. .
Indication of whether the command corresponds to enable or disable can be performed by setting a bit or implied based on the current enable or disable state of the carrier. Alternatively, it can be based on the carrier on which the MAC PDU was received. For example, if a MAC CE is included in a MAC PDU received on a given carrier (e.g., an "anchor carrier" or a "serving cell"), the command is It is understood that it is for activation of the indicated carrier. If a MAC CE is included in a MAC PDU received on a carrier (there may be no explicit indication of the carrier within the MAC CE itself), the command , or alternatively a predefined set of carriers.
In another alternative, all MAC_CE_validations are always received on a specific carrier (eg, the carrier corresponding to the serving cell).
Enable on request Physical Downlink Control Channel (PDCCH) on a specific carrier (e.g. "anchor carrier") with new Downlink Control Information (DCI) format (or modified DCI format for LTE-A) Receiving is performed on preconfigured additional uplink (PUSCH) or downlink (PDSCH) carriers (or a predefined subset of preconfigured additional uplink or downlink carriers). The WTRU may be informed of what is to be done in X subframes. (newnew carrier.) This delay allows the WTRU's analog front end to adapt to the new carrier. PLL (Phase-Locked Loop) and AGC (Automatic Gain Control) settling time and frequency synchronization. The new DCI format includes fields that associate preconfigured carriers with activations, as described above. This allows the WTRU to only monitor the PDCCH from a single carrier (eg, a specific carrier called the 'anchor carrier' or the carrier corresponding to the serving cell), thus saving battery. An indication from the anchor carrier may be for a single grant or allocation on additional component carriers. In this case, HARQ feedback corresponding to grants or allocations may also be delayed (with respect to PDCCH transmission) compared to existing systems. Alternatively, an indication from the anchor carrier that it should begin monitoring PDCCH on additional component carriers or a subset of component carriers until this carrier (or these carriers) is disabled. WTRU can be notified.
A PDCCH received with the new DCI format (or modified DCI format for LTE-A) on a carrier (e.g., an "anchor carrier") is time-delayed on a preconfigured additional component carrier. allocated (PRB (Physical Resource Block), MCS (Modulation and Coding Set), and the like). The delay is based on the WTRU's ability to tune and synchronize to preconfigured component carriers. This delay can be fixed or variable based on WTRU capabilities. Time-delayed assignments are already used for uplink assignments - ie 4 subframe delays. However, this method allows the WTRU to know more in advance about the likelihood of the next uplink transmission compared to existing systems. Such prior knowledge may be beneficial for uplink scheduling decisions. The same approach can be used for additional preconfigured component carriers. This provides the benefit that additional pre-configured component carriers are activated on demand by pre-allocating resources.
[Implicit Enable] The amount of traffic received on the downlink (PHY (Physical), MAC, RLC (Radio Link Control), or PDCP (Packet Data Convergence Protocol)) in a predetermined or configured time. ) exceeds a predetermined or configured threshold, implicit activation of one or some number of carriers may occur. There are several defined thresholds, each corresponding to activation of a particular carrier. For example, if the amount of traffic exceeds Vl, carrier Cl can be activated, and if the amount of traffic exceeds V2, carrier C2 can be activated, and so on.
Also, on certain uplink carriers associated with the enabling downlink carrier, the WTRU may transmit (Random Access Channel (RACH), Physical Uplink Control Channel (PUCCH), or Physical Uplink Shared Channel (PUSCH)). ), implicit activation of one or some number of carriers may occur. This association may be predefined or provided to the WTRU through RRC signaling (system information or dedicated signaling).
When a downlink carrier is enabled, the WTRU will start receiving on the PDCCH configured for this carrier (if PDCCH is defined per carrier) and transmission on PUCCH will be configured to send feedback information for
Implicit Invalidation Implicit invalidation can be performed based on an invalidation timer specific to the validity of the additional component carrier. For example, only the anchor carrier is valid during a web browsing session. When the download begins, it will start allocating PRBs on additional component carriers pre-configured for this WTRU. Once the download is complete, the network stops allocating resources to preconfigured additional component carriers for that WTRU. After some deactivation timer (which is specific to the preconfigured carrier) expires, the WTRU stops monitoring the PDCCH (i.e. dedicated PDCCH per carrier) and uses the front end radio resources allocated to this carrier. Stop. Alternatively, the WTRU may stop monitoring PDCCH for a carrier after expiration of a timing alignment timer (or other timer) specifically defined for this carrier. MAC received on that carrier Such timing alignment timers can be restarted based on the receipt of the timing alignment MAC control element from the PDU.
For activation on demand and control channels shared on the anchor carrier, the WTRU is assigned to a preconfigured additional component carrier as soon as no time-delayed assignment to this carrier is received. It is possible to stop the front end resource. It is more appropriate for the WTRU to wait several consecutive subframes without allocating additional preconfigured component carriers before deactivating front end resources associated with these carriers. can determine if there is
Implicit override may also be based on radio conditions. As an example, front-end radio resources can be de-allocated if the carrier's channel conditions are below some minimum threshold for a period of time.
Explicit Deactivation Order on PDCCH Explicit deactivation by sending a component carrier specific deactivation order so that the WTRU no longer needs to monitor the PDCCH (dedicated PDCCH per carrier). can be executed. The order can be sent using the PDCCH with the new DCI format on the anchor carrier for dedicated channels. Alternatively, the deactivation order using PDCCH can be sent only for preconfigured additional component carriers.
Enabling or Disabling in DRX Connected Mode The MAC DRX configuration remains the same for carrier aggregation. The on-duration and DRX cycle are the same for configured carriers (e.g., "anchor carriers" or serving.Cells).
A DRX Inactivity timer (DRX_Inactivity_timer) running in the WTRU may be started or restarted when a PDCCH is received over a pre-configured additional component carrier enabled for new transmissions. .
A DRX deactivation timer may also be started or restarted when a scheduled grant for an enabled preconfigured additional component carrier is received for a new transmission.
Alternatively, the MAC DRX configuration can have unique DRX deactivation timers for each additional pre-configured component carrier. The DRX deactivation timer associated with the carrier will be started or restarted when a PDCCH allocation is received on this carrier. This would allow the WTRU to effectively disable these preconfigured carriers until the next receive period cycle while the anchor carriers are in a valid time.
The logic previously described for the DRX disable timer can also be applied to other DRX timers, such as ON_Duration_Timer and DRX_Retransmission_Timer.
FIG. 2 is a block diagram of eNodeB 105 of FIG. eNodeB 105 includes antenna 205 , receiver 210 , processor 215 , and transmitter 220 . Receiver 210 is configured to receive a signal indicative of the bandwidth aggregation capabilities of WTRU 110 . Transmitter 220 is configured to transmit RRC connection reconfiguration messages to WTRU 110 .
FIG. 3 is a block diagram of WTRU 110 of FIG. WTRU 110 includes antenna 305 , receiver 310 , processor 315 , transmitter 320 , and DRX (Discontinuous Reception) disable timer 325 .
WTRU 110 monitors and processes component carriers. Receiver 310 of WTRU 110 is configured to monitor and process single component carriers. Transmitter 320 of WTRU 110 is configured to transmit a signal indicative of bandwidth aggregation capabilities of WTRU 110 . Receiver 310 is further configured to receive an RRC connection reconfiguration message. Processing unit 315 of WTRU 110 is configured to set up to monitor and process at least one additional pre-configured component carrier.
Receiver 310 can further be configured to receive MAC CE, and processing unit 315 can be configured to enable or disable pre-configured additional component carriers.
Additional preconfigured component carriers may be enabled or disabled immediately, or may be enabled or disabled after a predefined delay, in response to receipt of MAC CE. The preconfigured additional component carrier can be an uplink carrier or a downlink carrier.
The WTRU 110 may monitor and process single component carriers while in standby mode.
In one example, the bandwidth aggregation capability can represent a certain number of concurrent non-contiguous component carriers that can be monitored and processed concurrently in the downlink for each band.
In another example, bandwidth aggregation capability can represent the largest bandwidth among a certain number of RF receivers and each receiver.
In yet another example, bandwidth aggregation capability can represent a certain number of concurrently contiguous carriers that can be monitored and processed simultaneously in the downlink for each band.
In yet another example, the bandwidth aggregation capability can represent the maximum supported bandwidth among aggregated adjacent carriers.
In yet another example, bandwidth aggregation capability can represent the maximum total bandwidth among aggregated carriers.
In yet another example, the bandwidth aggregation capability can represent the maximum bandwidth supported per single carrier.
A bandwidth aggregation capability can represent more than one of the examples described above.
In another scenario, the receiver 310 specifies a PDCCH in DCI format that indicates that transmission and reception with additional preconfigured uplink or downlink carriers are to occur in a certain number of subframes. can be configured to receive on a carrier of The processor 315 can be configured to set up to monitor and process preconfigured carriers.
FIG. 4 shows a procedure 400 for monitoring and processing component carriers. In step 405, the WTRU monitors and processes single component carriers. At step 410, the WTRU transmits a signal indicative of the WTRU's bandwidth aggregation capabilities. At step 415, the WTRU receives the RRC connection reconfiguration message. At step 420, the WTRU sets up to monitor and process at least one additional pre-configured component carrier. In step 425, the WTRU enables or disables preconfigured additional component carriers in response to receiving the MAC CE.
FIG. 5 shows a procedure 500 for monitoring and processing component carriers. In step 505, the WTRU monitors and processes single component carriers. In step 510, the WTRU transmits a PDCCH on a particular carrier in DCI format, indicating that transmission/reception with additional preconfigured uplink or downlink carriers will occur in a certain number of subframes. to receive. At step 515, the WTRU sets up to monitor and process preconfigured carriers.
Embodiments 1. A method for monitoring and processing component carriers implemented by a WTRU comprising monitoring and processing a single component carrier and generating a signal representing the WTRU's bandwidth aggregation capability. receiving an RRC (Radio Resource Control) connection reconfiguration message; and setting up at least one preconfigured additional component carrier for monitoring and processing. how to.
2. The method of embodiment 1, further comprising: receiving a MAC (Medium Access Control) CE (Control Element); and enabling or disabling the preconfigured additional component carrier. described method.
3. The method of embodiment 2, wherein the preconfigured additional component carrier is immediately enabled or disabled in response to receiving the MAC CE.
4. The method of embodiment 2, wherein the preconfigured additional component carriers are enabled or disabled after a predefined delay.
5. The method of any of embodiments 1-4, wherein the preconfigured additional component carrier is an uplink carrier.
6. The method of any of embodiments 1-4, wherein the preconfigured additional component carrier is a downlink carrier.
7. The method as in any one of embodiments 1-6, wherein the WTRU monitors and processes the single component carrier while in standby mode.
8. The method of embodiments 1-7 wherein the bandwidth aggregation capability represents a number of concurrent non-contiguous component carriers that can be monitored and processed simultaneously in the downlink for each band. Any method described.
9. The method of any of embodiments 1-7, wherein the bandwidth aggregation capability represents a number of RF receivers and the maximum bandwidth of each receiver.
10. Any one of embodiments 1-7 wherein the bandwidth aggregation capability represents a number of simultaneously contiguous carriers that can be monitored and processed simultaneously in the downlink for each band described method.
11. The method of any of embodiments 1-7, wherein the bandwidth aggregation capability represents a maximum supported bandwidth of aggregated adjacent carriers.
12. The method of any of embodiments 1-7, wherein the bandwidth aggregation capability represents a maximum total bandwidth among aggregated carriers.
13. The method as in any one of embodiments 1-7, wherein the bandwidth aggregation capability represents the maximum bandwidth supported per single carrier.
14. A method implemented by a WTRU for monitoring and processing component carriers comprising monitoring and processing a single component carrier and preconfigured additional uplink or downlink carriers. Receiving a PDCCH (Physical Downlink Control Channel) representing that transmission and reception with a carrier will be performed in a certain number of subframes on a specific carrier in a DCI (Downlink Control Information) format; and setting up to monitor and process the detected carrier.
15. A WTRU for monitoring and processing a component carrier, the receiver configured to monitor and process a single component carrier and to transmit a signal indicative of the bandwidth aggregation capability of the WTRU a transmitter configured, said receiver further configured to receive a Radio Resource Control (RRC) connection reconfiguration message, and at least one preconfigured additional component carrier for monitoring and processing. a processing unit configured to set up.
16. The receiver is further configured to receive MAC (Medium Access Control) CE (Control Element), and the processing unit enables or disables the preconfigured additional component carrier. 16. The WTRU of embodiment 15, wherein the WTRU is configured to:
17. The WTRU of embodiment 16, wherein the preconfigured additional component carriers are immediately enabled or disabled in response to receiving the MAC CE.
18. The WTRU of embodiment 16, wherein the preconfigured additional component carriers are enabled or disabled after a predefined delay.
19. The WTRU of any of embodiments 15-18, wherein the preconfigured additional component carrier is an uplink carrier.
20. The WTRU of any of embodiments 15-18, wherein the preconfigured additional component carrier is a downlink carrier.
21. The WTRU of any of embodiments 15-20, wherein the WTRU monitors and processes the single component carrier while in standby mode.
22. The method of embodiments 15-21 wherein the bandwidth aggregation capability represents a certain number of concurrent non-contiguous component carriers that can be monitored and processed simultaneously in the downlink for each band. WTRU as described in any.
23. The WTRU of any of embodiments 15-21, wherein the bandwidth aggregation capability represents a number of RF receivers and the largest bandwidth of each receiver.
24. Any one of embodiments 15-21, wherein the bandwidth aggregation capability represents a number of simultaneously contiguous carriers that can be monitored and processed simultaneously in the downlink for each band WTRU as stated.
25. The WTRU of any of embodiments 15-21, wherein the bandwidth aggregation capability represents a maximum supported bandwidth of aggregated adjacent carriers.
26. The WTRU of any of embodiments 15-21, wherein the bandwidth aggregation capability represents a maximum total bandwidth among aggregated carriers.
27. The WTRU of any of embodiments 15-21, wherein the bandwidth aggregation capability represents the maximum bandwidth supported per single carrier.
28. A WTRU for monitoring and processing a component carrier, the receiver configured to monitor and process a single component carrier and a preconfigured additional uplink carrier or downlink carrier; PDCCH (Physical Downlink Control Channel), which indicates that transmission and reception with a carrier will be performed in a certain number of subframes, is configured to be received on a specific carrier in a DCI (Downlink Control Information) format. A WTRU comprising a receiver and a processing unit configured to set up to monitor and process said preconfigured carrier.
Although features and elements are described above in particular combinations, each feature or element can be used alone without other features and elements, or in various combinations with or without other features and elements. can be used. Any method or flow diagram provided herein may be embodied in a computer program, software, or firmware embodied in a computer-readable storage medium for execution by a general-purpose computer or processing device. can do. Examples of computer-readable storage media include magnets such as ROM (Read Only Memory), RAM (Random Access Memory), registers, cache memory, semiconductor memory devices, internal hard disks and removable disks. It includes media, magneto-optical media, and optical media such as CD-ROM discs and DVDs (Digital Versatile Discs).
Examples of suitable processors include general purpose processors, special purpose processors, conventional processors, DSPs (Digital Signal Processors), multiple microprocessors, one associated with a DSP core. or multiple microprocessors, controllers, microcontrollers, ASICs (Application Specific Integrated Circuits), ASSPs (Application Specific Standard Products), FPGA (Field Programmable Gate Array) circuits, or any other type of IC (Integrated Circuit (integrated circuit), and/or state machines.
Processing associated with software to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, MME (Mobility Management Entity) or EPC (Evolved Packet Core), or any host computer The device can be used. WTRU is a software defined radio (SDR), as well as cameras, video camera modules, videophones, speakerphones, vibration devices, speakers, microphones, TV transceivers, hands-free handsets, keyboards, Bluetooth® module, FM (Frequency Modulated) wireless unit, NFC (Near Field Communication) module, LCD (Liquid Crystal Display) display unit, OLED (Organic Light-Emitting) Diode) display unit, digital music player, media player, video game player module, internet browser, and/or any WLAN (Wireless Local Access Network) module or UWB (Ultra Wide Band) module, etc. It can be used in conjunction with modules implemented in hardware and/or software, including components.
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Category | Cited during | Relevant claims |
|---|---|---|---|---|---|
| JP2021064978A | Cites | Japan | X | Search report | 1,3-4,8-9,11-12,16 |
92 members in 17 offices
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 11020908 | United States of America | P | |
| 11020908 | United States of America | P | |
| 61110209 | United States of America | – | |
| 2021009434 | Japan | A | |
| 61110209 | – | – | – |
| US20080110209P | – | – | – |
Members92
| Document | Office | Kind | |
|---|---|---|---|
| WO2010051209A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2010118720A1 | United States of America | A1 | |
| AR074010A1 | Argentina | A1 | |
| TW201125379A | Taiwan Province of China | A | |
| KR20110084968A | Republic of Korea | A | |
| EP2363008A1 | European Patent Office (EPO) | A1 | |
| CN102204386A | China | A | |
| JP2012507943A | Japan | A | |
| HK1160328A | Hong Kong, China | A | |
| HK1160328A1 | Hong Kong, China | A1 | |
| KR20120099735A | Republic of Korea | A | |
| RU2011121817A | Russian Federation | A | |
| KR101266625B1 | Republic of Korea | B1 | |
| KR20130083483A | Republic of Korea | A | |
| US8514793B2 | United States of America | B2 | |
| JP5330528B2 | Japan | B2 | |
| RU2498537C2 | Russian Federation | C2 | |
| JP2013243757A | Japan | A | |
| US2014016506A1 | United States of America | A1 | |
| JP5647306B2 | Japan | B2 | |
| CN102204386B | China | B | |
| TWI471023B | Taiwan Province of China | B | |
| JP2015027113A | Japan | A | |
| US8953548B2 | United States of America | B2 | |
| CN104394595A | China | A | |
| KR20150038721A | Republic of Korea | A | |
| US2015124755A1 | United States of America | A1 | |
| TW201519670A | Taiwan Province of China | A | |
| KR101560865B1 | Republic of Korea | B1 | |
| BRPI0914513A2 | Brazil | A2 | |
| JP5866427B2 | Japan | B2 | |
| KR101598529B1 | Republic of Korea | B1 | |
| JP2016077003A | Japan | A | |
| US9351290B2 | United States of America | B2 | |
| KR101635333B1 | Republic of Korea | B1 | |
| US2016241376A1 | United States of America | A1 | |
| TWI561094B | Taiwan Province of China | B | |
| US9537643B2 | United States of America | B2 | |
| US2017078075A1 | United States of America | A1 | |
| JP6126253B2 | Japan | B2 | |
| TW201724881A | Taiwan Province of China | A | |
| JP2017121087A | Japan | A | |
| EP3285532A1 | European Patent Office (EPO) | A1 | |
| US9942021B2 | United States of America | B2 | |
| EP2363008B1 | European Patent Office (EPO) | B1 | |
| CN104394595B | China | B | |
| ES2673970T3 | Spain | T3 | |
| US2018198592A1 | United States of America | A1 | |
| DK2363008T3 | Denmark | T3 | |
| JP6368819B2 | Japan | B2 | |
| TWI631860B | Taiwan Province of China | B | |
| NO2363008T3 | Norway | T3 | |
| PL2363008T3 | Poland | T3 | |
| JP2018186548A | Japan | A | |
| HK1251390A | Hong Kong, China | A | |
| HK1251390A1 | Hong Kong, China | A1 | |
| EP3565353A1 | European Patent Office (EPO) | A1 | |
| JP6630785B2 | Japan | B2 | |
| EP3285532B1 | European Patent Office (EPO) | B1 | |
| JP2020036383A | Japan | A | |
| DK3285532T3 | Denmark | T3 | |
| PL3285532T3 | Poland | T3 | |
| ES2787018T3 | Spain | T3 | |
| HUE049992T2 | Hungary | T2 | |
| JP6830147B2 | Japan | B2 | |
| JP2021064978A | Japan | A | |
| US2021160039A1 | United States of America | A1 | |
| EP3565353B1 | European Patent Office (EPO) | B1 | |
| US11095421B2 | United States of America | B2 | |
| DK3565353T3 | Denmark | T3 | |
| EP3917250A1 | European Patent Office (EPO) | A1 | |
| EP3917250A4 | European Patent Office (EPO) | A4 | |
| PL3565353T3 | Poland | T3 | |
| ES2890401T3 | Spain | T3 | |
| HUE056004T2 | Hungary | T2 | |
| JP7133659B2 | Japan | B2 | |
| JP2022166328AThis record | Japan | A | |
| US11671232B2 | United States of America | B2 | |
| US2023308252A1 | United States of America | A1 | |
| BRPI0914513B1 | Brazil | B1 | |
| EP4408059A1 | European Patent Office (EPO) | A1 | |
| EP3917250B1 | European Patent Office (EPO) | B1 | |
| US12107800B2 | United States of America | B2 | |
| DK3917250T3 | Denmark | T3 | |
| FI3917250T3 | Finland | T3 | |
| JP7593970B2 | Japan | B2 | |
| US2024413958A1 | United States of America | A1 | |
| ES2993586T3 | Spain | T3 | |
| JP2025015837A | Japan | A | |
| PL3917250T3 | Poland | T3 | |
| HUE069323T2 | Hungary | T2 | |
| JP7783389B2 | Japan | B2 |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2022166328
- Publication, DOCDB
- 2022166328
- Publication, EPODOC
- JP2022166328
- Application
- 135808
- Application, DOCDB
- 2022135808
- Application, EPODOC
- JP20220135808
Titles2
- Japanese
- コンポーネント・キャリアを監視および処理するための方法および装置
- English
- Method and apparatus for monitoring and processing component carriers
Classification
- CPC, 11
- H04L5/0096
- H04L5/0098
- H04W24/02
- H04W72/51
- H04L5/001
- Y02D30/70
- H04W24/08
- H04W72/0453
- H04W72/23
- H04W72/231
- H04W72/21
- IPC, 5
- H04W76 15
- H04W72 04
- H04W88 08
- H04W76 38
- H04W76 20