EP2407002B1 - Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall - Google Patents

Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall Download PDF

Info

Publication number
EP2407002B1
EP2407002B1 EP10710714.6A EP10710714A EP2407002B1 EP 2407002 B1 EP2407002 B1 EP 2407002B1 EP 10710714 A EP10710714 A EP 10710714A EP 2407002 B1 EP2407002 B1 EP 2407002B1
Authority
EP
European Patent Office
Prior art keywords
carrier
wtru
radio link
carriers
link failure
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
EP10710714.6A
Other languages
English (en)
French (fr)
Other versions
EP2407002A1 (de
Inventor
Paul Marinier
Stephen E. Terry
Jean-Louis Gauvreau
Shankar Somasundaram
Peter S. Wang
Ghyslain Pelletier
Marian Rudolf
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings 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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Priority to EP20185131.8A priority Critical patent/EP3761750A1/de
Publication of EP2407002A1 publication Critical patent/EP2407002A1/de
Application granted granted Critical
Publication of EP2407002B1 publication Critical patent/EP2407002B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • This application is related to wireless communications.
  • Wireless communication systems keep evolving to meet the needs for providing continuous and faster access to a data network.
  • wireless communication systems may use multiple carriers for the transmission of data.
  • a wireless communication system that uses multiple carriers for the transmission of data may be referred to as a multi-carrier system.
  • the use of multiple carriers is expanding in both cellular and non-cellular wireless systems.
  • a multi-carrier system may increase the bandwidth available in a wireless communication system according to a multiple of how many carriers are made available. For instance, a dual-carrier system may double the bandwidth when compared to a single carrier system and a tri-carrier system will triple the bandwidth when compared to a single carrier system. In addition to this throughput gain, diversity and joint scheduling gains may also be expected. This may result in improving the quality of service (QoS) for end users. Further, multiple carriers may be used in combination with multiple-input multiple-output (MIMO).
  • MIMO multiple-input multiple-output
  • the wireless transmit/receive unit ensures that its radio connection to the system (i.e., the radio resource control (RRC) connection), once established, is maintained.
  • the WTRU performs radio link monitoring and, upon detection of physical layer problems, increases its monitoring activity until it recovers from the physical layer problems. If the problems persist and conditions to recover from the physical layer problems cannot be met, the WTRU assumes a radio link failure (RLF). Upon RLF, the WTRU performs a recovery procedure, (e.g., an RRC connection re-establishment).
  • a WTRU monitors the downlink (DL) radio quality against thresholds (Q out and Q in ) every frame or every discontinuous reception (DRX) period, depending on whether or not DRX is activated.
  • the physical layer indicates in-synch or out-of-synch to higher layers, (e.g., an RRC layer), when the radio link quality is better than Qin or worse than Q out (respectively).
  • the time periods for this evaluation depend on whether DRX is utilized or not.
  • the radio link quality is measured in terms of the block error rate of a hypothetical physical downlink control channel (PDCCH) transmission, taking into account the physical control format indicator channel (PCFICH) errors with a certain assumed transmission configuration.
  • PDCCH physical downlink control channel
  • PCFICH physical control format indicator channel
  • the RRC Upon the reception of a predefined number (e.g., N310) of consecutive out-of-synch indications, the RRC detects that a physical layer problem has occurred and starts a recovery timer (e.g., T310). If the recovery timer expires before a predefined number (e.g., N311) of consecutive in-synch indications are received, (i.e., the "recovery of a physical layer problem"), the RRC determines that RLF has occurred and either initiates a connection reestablishment procedure or the release of the RRC connection, depending on whether access stratum (AS) security has been activated or not.
  • a predefined number e.g., N310
  • the evaluation period radio link quality evaluation is as if DRX is not used, regardless of whether it is being configured or not. This implies that the WTRU turns on its receiver for the purpose of evaluating radio link quality, even if no reception of data is expected as per DRX rules.
  • the RRC may also determine that RLF has occurred upon an indication from the medium access control (MAC) of a random access problem, or an indication from the radio link control (RLC) that the maximum number of retransmissions has been reached.
  • MAC medium access control
  • RLC radio link control
  • LTE-advanced LTE-A
  • R8 release 8
  • the criteria for radio link monitoring and the actions to take upon detection of a radio link problem need to be redefined, as compared to a single-carrier case. This is because of the possibility of different radio conditions over different component carriers and the modifications that need to be made to the control channel structure and related procedures compared to the single-carrier case.
  • HUAWEI "ALF consideration in DC-HSDPA", 3GPP DRAFT; R2-086693 relates to radio link failure in DC-HSDPA.
  • WO 2006/086359 (INTERDIGITAL TECH CORP) relates to a method and system for recognizing radio link (RL) failures associated with high speed uplink packet access (HSUPA) and high speed downlink packet access (HSDPA) channels established between a WTRU and a Node-B.
  • RL radio link
  • HUAWEI "Discussion on RLF in DC-HSDPA", 3GPP DRAFT; R2-084402 relates to solutions in regard to radio link failure in DC-HSDPA.
  • US 2006/280142 (DAMNJANOVIC ALEKSANDAR ET AL ) relates to a Global System for Mobile Communications (GSM) network supporting multi-carrier operation on the downlink and/or uplink for a mobile station.
  • GSM Global System for Mobile Communications
  • US 2005/281222 (RANTA-AHO KARRI ET AL ) relates to a method and apparatus for defining terminal behavior in a case where the terminal detects that it cannot receive the HS-DSCH from a serving cell reliably when the DCCH is mapped to HS-DSCH.
  • Method and apparatus for providing improved handling and detection of radio link failure conditions is defined by the independent claims. Embodiments are given by the dependent claims. Methods and apparatus are described for monitoring for a radio link failure in a LTE-A system operated with carrier aggregation. The methods include criteria for determining radio link failure, recovery events, and the actions that a WTRU may take upon the occurrence of such events.
  • wireless transmit/receive unit includes, but is not limited to, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of device capable of operating in a wireless environment.
  • UE user equipment
  • PDA personal digital assistant
  • base station includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
  • AP access point
  • the term “primary component carrier (PCC)” includes, without loss of generality, a carrier of a WTRU configured to operate with multiple component carriers for which some functionality, (e.g., derivation of security parameters and non-access stratum (NAS) information), may be applicable only to that component carrier.
  • the WTRU may be configured with at least one PCC for the downlink (DL PCC) and one for the uplink (UL PCC). Consequently, a carrier which is not a PCC of the WTRU is hereafter referred to as a secondary component carrier (SCC).
  • DL PCC downlink
  • UL PCC uplink
  • PDCCH monitoring and/or physical downlink shared channel (PDSCH) reception for a PCC is typically activated and may be governed by DRX (if configured).
  • PDCCH monitoring (if configured) and/or PDSCH reception for a configured SCC may be either activated or deactivated, and may additionally be governed by DRX (if configured) when activated.
  • cross-carrier scheduling i.e., scheduling across carriers using PDCCH
  • monitoring of PDCCH may not be necessary in all configured and/or active carriers.
  • the term "PDCCH carrier” includes a carrier for which the WTRU is configured to monitor PDCCH.
  • the WTRU may be configured with one or more PDCCH carrier(s).
  • anchor carrier includes a PDCCH carrier for which the WTRU additionally monitors for downlink assignments and/or uplink grants which may be applicable to a different carrier of the WTRU's configuration.
  • anchor carrier When the WTRU is operating with multiple component carriers, the WTRU may be configured with one or more anchor carriers.
  • the term "scheduled set" includes at least one anchor carrier and at least one non-anchor carrier (possibly itself a PDCCH carrier) where the anchor carrier can provide control signaling also for the non-anchor carrier(s) in the set.
  • the WTRU may be configured with one or more scheduled set(s). For example, when a WTRU is configured to operate with two or more carriers, (i.e., frequencies or cells), each of these carriers may have distinct characteristics and logical association with the network and the WTRU, and the operating frequencies may be grouped to form more than one scheduled set where each set includes at least a primary or anchor carrier as well as a secondary carrier.
  • the WTRU may be configured with a single scheduled set, (i.e., with a single primary or anchor carrier and one or more secondary carriers).
  • FIG 1 shows an LTE wireless communication system/access network 10 that includes an evolved-universal terrestrial radio access network (E-UTRAN) 20.
  • the E-UTRAN 20 includes a WTRU 100 and several evolved Node-Bs, (eNBs) 150.
  • the WTRU 100 is in communication with an eNB 150.
  • the eNBs 150 may implement an interface with each other using an X2 interface.
  • Each of the eNBs 150 interface with a mobility management entity (MME)/serving gateway (S-GW) 180 through an S1 interface.
  • MME mobility management entity
  • S-GW serving gateway
  • FIG. 2 is a block diagram of an LTE wireless communication system 200 including the WTRU 100, the eNB 150, and the MME/S-GW 180. As shown in Figure 2 , the WTRU 100, the eNB 150 and the MME/S-GW 180 are configured to perform a method of monitoring a radio link with aggregated carriers.
  • the WTRU 100 includes a processor 255 with an optional linked memory 260, at least one transceiver 265, an optional battery 270, and an antenna 275.
  • the processor 255 is configured to perform a method of maintaining validity of system information with aggregated carriers.
  • the transceiver 265 is in communication with the processor 255 and the antenna 275 to facilitate the transmission and reception of wireless communications.
  • the transceiver 265 includes a transmitter and a receiver (not shown individually). In case a battery 270 is used in the WTRU 210, it powers the transceiver 265 and the processor 255.
  • the eNB 150 includes a processor 280 with an optional linked memory 282, transceivers 284, and antennas 286.
  • the processor 280 is configured to perform a method of monitoring a radio link with aggregated carriers.
  • the transceivers 284 are in communication with the processor 280 and antennas 286 to facilitate the transmission and reception of wireless communications.
  • the eNB 150 is connected to the MME/S-GW 180 which includes a processor 288 with an optional linked memory 290.
  • the WTRU 100 is in communication with the Node-B 150, and both are configured to perform a method wherein UL transmissions from the WTRU 100 are transmitted to the Node-B 150 using multiple UL carriers 65, and downlink transmissions are handled using multiple carriers 70.
  • Figure 3 shows additional details of the processor 255 in the WTRU 100.
  • the processor 255 may include a plurality of recovery timers 325 1 , 325 2 , ..., 325N and a plurality of counters 330 1 , 330 2 , 330 3 330 4 , ..., 330 N .
  • HSPA evolved high speed packet access
  • a single set of timers 325 and counters 330 in the processor 255 of the WTRU 100 may be used to perform radio link monitoring for the purpose of determining that radio link failure has occurred.
  • the WTRU 100 performs the detection and recovery of physical layer problems using a single set of counters (e.g., N310, N311) and a single recovery timer (e.g., T310) to detect a radio link failure.
  • a single set of counters e.g., N310, N311
  • a single recovery timer e.g., T310
  • the WTRU 100 Upon detection of a radio link failure, the WTRU 100 performs either an RRC connection re-establishment procedure or an RRC connection release procedure, (depending on whether AS security is activated or not).
  • Radio link monitoring for the purpose of radio link failure detection may be based on in-synch and out-of-synch indications derived from a primary DL carrier.
  • a primary DL carrier amongst the set of different component carriers activated for a WTRU is used for radio link monitoring purposes.
  • the physical layer reports in-synch indications and out-of-synch indications to the RRC layer at least from the DL carrier monitored for the purpose of radio link failure, (i.e., a primary DL carrier); indications may be reported for other DL carriers as well for purposes other than radio link failure detection, (e.g., for management of the set of configured component carriers (e.g., the secondary carriers)).
  • a procedure (400) for monitoring a radio link includes determining (i.e., identifying) a primary DL carrier (405) among a set of component carriers configured for the WTRU 100. At least one primary DL carrier(s) may be identified according to one or a combination of the following methods:
  • the procedure 400 further includes counting the number of out-of-synch indications from the primary DL carrier (410) using a first counter 330 1 (e.g., N310), and initiating a recovery timer 325 1 (e.g., T310) on a condition that a predefined number of out-of-synch indications from the primary carrier was counted (415), as determined by the first counter 330 1 .
  • a first counter 330 1 e.g., N310
  • T310 recovery timer
  • the procedure (400) further includes counting the number of in-synch indications from the primary DL carrier (420) using a second counter 330 2 , and determining whether a predefined number of in-synch indications from the primary DL carrier was counted by the second counter 330 2 before the recovery timer 325 1 expired (425). If the number of in-synch indications from the primary DL carrier reaches the predefined number of in-synch indications, the recovery timer 325 1 is stopped and reset, along with the first and second counters 330 1 and 330 2 (430).
  • a radio link failure is declared (435) and either a connection re-establishment procedure or an RRC connection release procedure is performed (440).
  • Radio link monitoring may also be based on a function to derive in-synch indications and out-of-synch indications across multiple DL carriers within a given period of time, which time period would typically be equivalent to the in-synch/out-synch measurement frequency, e.g., one subframe.
  • the physical layer measures in-synch and out-of-synch indications from multiple DL carriers, (hereinafter referred to as a "set of monitored DL carriers”), and applies a function to combine these indications into a single in-synch indication or a single out-of-synch indication that may be reported to the RRC layer.
  • Such a combination may, for example, may be performed using one or more of the following methods:
  • a procedure 500 for monitoring radio links includes determining a set of monitored DL carriers (505).
  • This set of monitored DL carriers may be determined according to one or a combination of the following methods:
  • the procedure 500 further includes combining out-of-synch indications from each of the carriers in the set of monitored DL carriers into combined out-of-synch indications (510), and combining in-synch indications from each of the carriers in the set of monitored DL carriers into combined in-synch indications (515).
  • the procedure 500 further includes counting the number of combined out-of-synch indications (520) using a first counter 330 1 (e.g., N310), and initiating a recovery timer 325 1 (e.g., T310) on a condition that a predefined number of combined out-of-synch indications was counted (525), as determined by the first counter 330 1 .
  • the procedure (500) further includes counting the number of combined in-synch indications (530) using a second counter 330 2 , and determining whether a predefined number of combined in-synch indications was counted before the recovery timer 325 1 expired (535). If the number of combined in-synch indications reaches the predefined number of combined in-synch indications, the recovery timer 325 1 is stopped and reset, along with the first and second counters 330 1 and 330 2 (540). If the number of combined in-synch indications does not reach the predefined number of combined in-synch indications, a radio link failure is declared (545) and either a connection re-establishment procedure or an RRC connection release procedure is performed (550).
  • Radio link monitoring may be performed within a "scheduled set", as described above, of component carriers.
  • the anchor carrier may correspond to a "primary carrier". This may be realized by having all carriers of the scheduled set controlled from the same PDCCH or from separate PDCCHs.
  • acknowledgement (ACK)/negative acknowledgement (NACK) feedback and channel quality indicator (CQI)/precoding matrix indicator (PMI)/routing indicator (RI) reports pertaining to DL transmissions from the scheduled set of carriers are sent from a single "primary" UL carrier.
  • a recovery timer 325 1 in the WTRU 100 (e.g., T310) is initiated (i.e., started) and radio link quality monitoring is immediately started on all DL carriers of the scheduled set, (i.e., on the SCCs), possibly only for the SCCs that are also PDCCH carriers.
  • the physical layer now provides in-synch indications and out-of-synch indications for each of the DL carriers, (i.e., for the PCC and all of the SCC(s)).
  • a non-DRX evaluation period may be used on all of the DL carriers regardless of whether DRX was used or not on the DL carriers.
  • the WTRU 100 may receive continuously on the DL carriers.
  • the recovery timer 325 1 (e.g., T310) may be stopped upon reception of a predefined number (e.g., N311) of consecutive in-synch indications from the same carrier (the value of the recovery timer 325 1 may be carrier-dependent). If this carrier is different from the primary carrier, the WTRU 100 may initiate transmission of a report from which the network could initiate a procedure to reestablish the PCC or may perform a "primary re-establishment", as described further below.
  • a predefined number e.g., N311
  • the WTRU 100 may initiate transmission of a report from which the network could initiate a procedure to reestablish the PCC or may perform a "primary re-establishment", as described further below.
  • the WTRU 100 may first start the evaluation period on the subset of DL carriers (within the scheduled set) it has been configured to actively receive, (i.e., PDCCH and/or PDSCH reception), and then in a second phase if consecutive in-synch indications have not been detected from any one carrier in this subset.
  • the requirement to start with a carrier subset and alternate detection to other carriers may be based on WTRU capability.
  • the WTRU may initiate a recovery procedure such as a connection re-establishment procedure or an RRC connection release procedure (depending on whether security is activated or not) is performed as in the single carrier case.
  • a recovery procedure such as a connection re-establishment procedure or an RRC connection release procedure (depending on whether security is activated or not) is performed as in the single carrier case.
  • the occurrence of a partial radio link failure for this primary carrier (or for a "scheduled set" of carriers) may be considered, and appropriate actions may be taken as described below.
  • a procedure 600 for monitoring radio links includes initiating a recovery timer (605), counting the number of in-synch indications for each of a plurality of DL carriers of a scheduled set of component carriers (610), and determining whether a predefined number of in-synch indications was received from a particular one of the carriers before the recovery timer expires (615). If a predefined number of in-synch indications was not received from a particular one of the carriers before the recovery timer expires, a radio link failure is declared (620), and either a connection re-establishment procedure or an RRC connection release procedure is performed (625).
  • the recovery timer is stopped and reset (630), and a determination is made as to whether the particular one of the carriers is the primary carrier (635). If the particular one of the carriers is determined not to be the primary carrier, a primary re-establishment procedure is performed (640).
  • a first recovery timer 325 1 (e.g., T310) is initiated (i.e., started) upon reception of a predefined number (e.g., N310) of consecutive out-of-synch indications for one or more carriers of a first subset of DL carriers such as at least one of a PCC, an anchor carrier or a PDCCH carrier of a "scheduled set", and the first recovery timer 325 1 is stopped upon reception of a first predefined number (e.g., N311) of consecutive in-synch indications for the carriers for which the first timer is applicable.
  • a predefined number e.g., N310
  • N311 consecutive out-of-synch indications for the carriers for which the first timer is applicable.
  • a second recovery timer 325 2 (e.g., T310bis) is initiated, and radio link quality monitoring is started on a different subset of the DL carriers such as all SCCs or all PDCCH carriers or all DL carriers of a "scheduled set".
  • the value (e.g., T310bis) of the second recovery timer 325 2 may or may not be the same as the value (e.g., T310) of the first recovery timer 325 1 .
  • a non-DRX evaluation period may be used on all carriers regardless of whether DRX was used or not on these carriers.
  • the WTRU 100 may receive continuously on these carriers.
  • the second recovery timer 325 2 may be stopped upon reception of a second predefined number (e.g., N311bis) of consecutive in-synch indications from the same carrier (the second predefined number may be carrier-dependent). If this carrier is different from the primary carrier, the WTRU 100 may perform a "primary re-establishment" procedure as described below.
  • a second predefined number e.g., N311bis
  • the WTRU 100 may perform a "primary re-establishment" procedure as described below.
  • the WTRU 100 may first start the evaluation period on the subset of DL carriers (within the scheduled set) it has been configured to actively receive, and then in a second phase if consecutive in-synch indications have not been detected from any one carrier in this subset, alternate detection to other DL carriers in this cell.
  • the requirement to start with a carrier subset and alternate detection to other carriers may be based on WTRU capability.
  • the second recovery timer 325 2 expires, either a connection reestablishment procedure or an RRC connection release procedure is performed (depending on whether security is activated or not) as in the single carrier case.
  • a connection reestablishment procedure or an RRC connection release procedure is performed (depending on whether security is activated or not) as in the single carrier case.
  • the occurrence of a partial radio link failure for this primary carrier may be considered, and appropriate actions may be taken as described below.
  • a procedure 700 for monitoring radio links includes initiating a first recovery timer (705), counting the number of in-synch indications for each of a plurality of DL carriers of a scheduled set of component carriers (710), and determining whether a first predefined number of in-synch indications was received from a particular one of the carriers before the first recovery timer expires (715). If a first predefined number of in-synch indications was not received from a particular one of the carriers before the first recovery timer expires, a radio link failure is declared (720), and either a connection re-establishment procedure or an RRC connection release procedure is performed (725).
  • the first recovery timer is stopped and reset (730), a second recovery timer is initiated (735), the number of in-synch indications for each of a plurality of DL carriers of the scheduled set of component carriers is counted (740), and a determination is made as to whether a second predefined number of in-synch indications was received from the same particular one of the carriers before the second recovery timer expires (745).
  • a radio link failure is declared (720), and either a connection re-establishment procedure or an RRC connection release procedure is performed (725). If a second predefined number of in-synch indications was received from a particular one of the carriers before the second recovery timer expires, the second recovery timer is stopped and reset (750), and a determination is made as to whether the particular one of the carriers is the primary carrier (755). If the particular one of the carriers is determined not to be the primary carrier, a primary re-establishment procedure is performed (760).
  • a first recovery timer 325 1 (e.g., T310) is initiated (i.e., started), and a second recovery timer 325 2 (e.g., T310bis) is also initiated.
  • Radio link quality monitoring is immediately started on all DL carriers of the scheduled set.
  • the physical layer now provides in-synch and out-of-synch indications for each carrier of the scheduled set.
  • a non-DRX evaluation period may be used on all carriers regardless of whether DRX was used or not on these carriers.
  • the WTRU 100 may receive continuously on these carriers.
  • the WTRU 100 may start an evaluation period on a subset of DL carriers (within the scheduled set) that the WTRU 100 has been configured to actively receive. If consecutive in-synch indications have not been detected from any one carrier in this subset, alternate detection to other DL carriers in this cell may be implemented, based on WTRU capability.
  • the first recovery timer 325 1 is stopped upon reception of a predefined number (e.g., N311) of consecutive in-synch indications from the primary carrier.
  • the second recovery timer 325 2 is stopped upon reception of a predefined number (e.g., N311) consecutive in-synch indications from the same primary or secondary carrier (the value of the predefined number may be carrier-dependent).
  • a predefined number e.g., N311
  • consecutive in-synch indications from the same primary or secondary carrier the value of the predefined number may be carrier-dependent.
  • the WTRU 100 may perform a "primary re-establishment" procedure as described below.
  • first recovery timer 325 1 expires and the second recovery timer 325 2 had previously expired, (i.e., had not been stopped due to the reception of N311 consecutive in-synch indications)
  • either a connection re-establishment procedure or an RRC connection release procedure is performed (depending on whether security is activated or not) as in the single carrier case.
  • the occurrence of a partial radio link failure for this primary carrier may be considered, and appropriate actions may be taken as described below.
  • a procedure 800 for monitoring radio links includes initiating a first recovery timer and a second recovery timer (805), counting the number of in-synch indications for each of a plurality of DL carriers of a scheduled set of component carriers (810), and determining whether a predefined number of in-synch indications was received from a primary carrier before both of the recovery timers expire (815). If a predefined number of in-synch indications was not received from a primary carrier before both of the recovery timers expire, a radio link failure is declared (820), and either a connection re-establishment procedure or an RRC connection release procedure is performed (825).
  • any of the recovery timers that did not expire is stopped and reset (830), and a primary re-establishment procedure is performed (835).
  • all carriers of the scheduled set are monitored.
  • a radio link monitoring procedure is executed separately and concurrently on each carrier of the scheduled set.
  • the physical layer indicates in-synch and out-of-synch to higher layers.
  • the number of consecutive out-of-synch and in-synch indications is tracked separately.
  • the WTRU 100 detects a "radio link problem" for a specific carrier when a predefined number (N310) of consecutive out-of-synch indications are received for this carrier.
  • the WTRU 100 starts a recovery timer 325 1 (e.g., T310) specific for this carrier.
  • This recovery timer 325 1 is stopped if the predefined number (N311) of consecutive in-synch indications is received for the carrier.
  • the values of the timers 325 and the predefined number of in-synch indications may be carrier-dependent. Once the recovery timer 325 1 expires for a carrier, the behavior may be as follows depending on the type of carrier, (e.g., whether the DL CC is a PCC or a SCC).
  • the WTRU may perform actions upon detection of "partial radio link failure" for this carrier without affecting operations on other carriers (PCC or not).
  • the WTRU 100 may perform one or a combination of:
  • the evaluation period for in-synch and out-of-synch indications on a given carrier depends on the DRX activity of this carrier, if DRX is on a per-carrier basis.
  • the evaluation periods for in-synch/out-of-synch indications are specific to each carrier (depending on the DRX) as long as no recovery timer 325 is running for any carrier.
  • the evaluation period (for all carriers or for a certain subset of carriers signaled by higher layers) for in-synch/out-of-synch indications correspond to that of continuous reception (non-DRX) or reception with a higher duty rate.
  • the values of the recovery timers 325 and the predefined umber of in-synch indications for a given carrier may be modified when the recovery timer 325 is running for any carrier (or any carrier from a certain subset of carriers signaled by higher layers).
  • Another possible scenario is that UL/DL scheduling for a carrier is signaled over the same carrier. This may, for instance, be realized by having the WTRU 100 monitor a PDCCH for each carrier it is assigned to. It is also possible to have a more general scenario where multiple anchor carriers exist with their corresponding scheduled sets of carriers. The former scenario may be considered as a particular case of the latter where the scheduled set of an anchor carrier consists of this anchor carrier. Thus, the solutions described in this section will be described in terms of the more general scenario with multiple PDCCH carriers.
  • One of the PDCCH carriers may correspond to a "primary" carrier which is monitored for the purpose of radio link failure detection as previously described.
  • DRX reception on active carriers may be applied on a per-carrier basis.
  • the WTRU 100 is monitoring the PDCCH on (or for) a given carrier at a given sub-frame, this does not imply that it is monitoring the PDCCH on other carrier(s).
  • DRX reception may be applied jointly on all active carriers.
  • the radio link monitoring procedure is executed separately and concurrently on each PDCCH carrier.
  • the physical layer indicates in-synch and out-of-synch to higher layers.
  • the number of consecutive out-of-synch and in-synch indications is tracked separately.
  • the WTRU 100 detects a "radio link problem" for a specific carrier when a first predefined number (e.g., N310) of consecutive out-of-synch indications are received for this carrier.
  • the WTRU 100 starts a recovery timer 325 (e.g., T310) specific for this PDCCH carrier.
  • This recovery timer 325 is stopped if a second predefined number (e.g., N311) of consecutive in-synch indications are received for the carrier.
  • the values of the recovery timer 325 and the predefined number of consecutive in-synch indications may be carrier-dependent. If the recovery timer 325 expires, a radio link failure is declared for the concerned PDCCH carrier. Such an event may be referred to as a "partial radio link failure.”
  • the WTRU 100 may take actions as described below to notify the network and potentially remove or recover the carrier.
  • the WTRU 100 may take actions as for the currently defined radio link failure procedure for single carrier, i.e., initiate the re-establishment procedure or release the RRC connection.
  • the evaluation period for in-synch and out-of-synch indications on a given PDCCH carrier depends on the DRX activity of this carrier, if DRX is on a per-carrier basis.
  • the evaluation periods for in-synch/out-of-synch indications are specific to each PDCCH carrier (depending on the DRX) as long as no recovery timer 325 is running for any PDCCH carrier (possibly only for a PDCCH that is also a PCC and/or an anchor carrier).
  • the recovery timer 325 (e.g., T310) is running for any PDCCH carrier (possibly only for a PDCCH that is also a PCC and/or an anchor carrier)
  • the evaluation period (for all PDCCH carriers or for a certain subset of primary carriers signaled by higher layers) for in-synch/out-of-synch indications correspond to that of continuous reception (non-DRX) or reception with a higher duty rate.
  • Such monitoring increases the chances of detecting a radio link problem rapidly on other primary carriers, and thus may potentially minimize the loss of data or connection, considering that radio link problems are susceptible to be correlated between carriers.
  • the values of the recovery timer 325 and the predefined number of consecutive in-synch indications (e.g., N310, T310, and N311) for a given carrier may be modified when the recovery timer 325 (e.g., T310) is running for any carrier (or any carrier from a certain subset of carriers signaled by higher layers).
  • a radio link monitoring procedure is executed separately and concurrently on each scheduled set of component carriers as per one of the methods described above.
  • the detection of a radio link problem on any of the PDCCH carriers may result in either in a primary re-establishment or in a partial radio link failure.
  • the values of recovery timers 325 and the predefined number of consecutive in-synch indications, may be dependent on the scheduled set.
  • the WTRU 100 may take actions to notify the network and potentially remove or recover the PDCCH carrier and/or the entire scheduled set of carriers for this anchor PDCCH, if applicable. If all of the PDCCH carriers (possibly only for a PDCCH that is also a PCC and/or an anchor carrier) the WTRU 100 was configured to receive in the cell have detected a radio link failure condition, the WTRU 100 may take actions as for the currently defined radio link failure procedure for a single carrier, (i.e., initiate the re-establishment procedure or release the RRC connection).
  • the evaluation period for in-synch and out-of-synch indications on a given PDCCH carrier depends on the DRX activity of this carrier, if DRX is on a per-carrier basis.
  • the evaluation periods for in-synch/out-of-synch indications are specific to each PDCCH carrier (depending on the DRX) as long as no recovery timer 325 is running for any PDCCH carrier (possibly only for a PDCCH that is also a PCC and/or an anchor carrier).
  • the evaluation period for all PDCCH carriers or for a certain subset of PDCCH carriers signaled by higher layers
  • the evaluation period for in-synch/out-of-synch indications correspond to that of continuous reception (non-DRX) or reception with a higher duty rate.
  • the values of the recovery timers 325 and the predefined number of consecutive in-synch indications, (e.g., N310, N311, T310, and (if applicable) T310bis), for a given carrier may be modified when the recovery timer 325 is running for any PDCCH carrier (or any carrier from a certain subset of carriers signaled by higher layers).
  • the procedures described below may apply to detection of "partial radio link failure" of a downlink carrier configured with PDCCH. They may also apply to the detection of failure of a downlink carrier configured with PDSCH, but not PDCCH.
  • one of the carriers WTRU is configured to operate with has a specific role (e.g., a PPC, anchor carrier or the DL carrier corresponding to the "special cell” or the "serving cell")
  • a specific role e.g., a PPC, anchor carrier or the DL carrier corresponding to the "special cell” or the "serving cell”
  • the procedures below may apply in case this carrier fails.
  • an explicit notification may be signaled to the eNB or it may be left for the eNB to implicitly detect the partial radio link failure.
  • the explicit indication may be signaled by a physical uplink control channel (PUCCH), MAC control element (CE), or RRC measurement report.
  • PUCCH physical uplink control channel
  • CE MAC control element
  • RRC measurement report may indicate a very low CQI report or a unique CQI code point.
  • the MAC CE and RRC measurement report may require a DL carrier identifier is indicated.
  • a new measurement event may be defined to trigger transmission of an RRC measurement report upon occurrence of partial radio link failure for a carrier.
  • the WTRU 100 may stop UL transmissions, disabling the UL carrier that is paired with the failed DL carrier.
  • the pairing with a DL carrier is either pairing for hybrid automatic repeat request (HARQ) feedback or pairing for PDCCH scheduling.
  • the UL carrier may be disabled for scheduling if all DL carriers that may provide scheduling for this UL carrier have failed.
  • HARQ hybrid automatic repeat request
  • the WTRU 100 may stop UL transmissions and release resources on any UL carrier whose timing advance is adjusted with respect to the DL carrier having experienced partial radio link failure. Optionally, this may occur when there is no other DL carrier without a radio link problem to which the same timing advance may be applied. If there is at least one such DL carrier, the WTRU 100 may continue UL transmissions and adjust the timing advance with respect to this DL carrier.
  • the WTRU 100 may take the same actions as if a timing advance timer expired for any UL carrier whose timing advance is adjusted with respect to the DL carrier having experienced partial radio link failure.
  • the implicit eNB detection may be based on UL discontinuous transmission (DTX) detection for PUCCH or HARQ feedback corresponding to the DL carrier.
  • DTX discontinuous transmission
  • a partial MAC reset may be applied for the concerned DL carrier and the HARQ processes associated with this DL carrier are flushed.
  • the WTRU 100 When the WTRU 100 detects a partial radio link failure, it may indicate the cell identity (ID) or carrier ID, (corresponding to the carrier on which the radio link failure occurred), to the network along with the list of other cells it is camped on, (if the different carriers come from different cells in the network). Alternatively, in case of a partial radio link failure, the WTRU 100 may indicate the cell ID or carrier ID of the last PCC along with the cell ID or carrier ID of the new PCC.
  • ID cell identity
  • carrier ID corresponding to the carrier on which the radio link failure occurred
  • one of the carriers (or one of the PDCCH carriers) has a special role (e.g., a PPC, anchor carrier or the DL carrier corresponding to the "special cell” or the "serving cell") with respect to the assignment of certain security parameters.
  • the WTRU 100 autonomously selects a new "serving cell” among one of the remaining carriers and notifies this choice to the network.
  • the WTRU may report that partial radio link failure has occurred for the serving cell, and may perform the re-assignment based on an indication from the network.
  • the WTRU 100 may act as if a change of security parameters has occurred, which may involve re-establishment of packet data convergence protocol (PDCP) entities.
  • PDCP packet data convergence protocol
  • a primary re-establishment procedure may be triggered once the WTRU has detected a radio link failure on the DL primary carrier and monitoring of the other non-primary carriers indicates that one or more carriers are acceptable, whereby in-synch indications for one or more non-primary carriers were sent to higher layers.
  • the procedure may be applied only to the a PCC as previously defined. Alternatively, the procedure may be applied to any "PDCCH carrier".
  • the primary re-establishment procedure may be limited to the subset of DL carriers within the cell that the WTRU 100 has been configured to actively receive.
  • an RRC primary carrier re-establishment procedure may be implemented to request a network 900, including a WTRU 905 and an eNB 910, to change the DL primary carrier.
  • a DL primary carrier 955 is in a radio link failure condition
  • DL non-primary carriers 960 and 965 have in-synch indications
  • UL carrier 970 is paired with the DL primary carrier 955
  • UL carrier 975 is paired with the DL non-primary carrier 960.
  • the WTRU 905 may implicitly designate one of the carriers as the new primary carrier, (e.g., based on signal strength or signal quality).
  • the same set of system parameters e.g., random access channel (RACH), access class barring, or any other suitable parameter
  • RACH random access channel
  • the WTRU 905 may implicitly use the information acquired from the old primary carrier.
  • the WTRU 905 may read selected system information blocks (SIBs) when it accesses the new primary carrier and then proceed to read the RACH.
  • SIBs system information blocks
  • the network 900 may signal whether the network 900 should continue to use the parameters from the current primary carrier when it switches its primary carrier through a one bit field.
  • the WTRU 905 may send a scheduling request (SR) on the PUCCH of the UL carrier 975 paired with a DL non-primary carrier 960 having an in-synch indication.
  • SR scheduling request
  • a RACH procedure may be applied to generate the SR.
  • the RACH procedure may not be required if another primary carrier exists in the cell for which there is no radio link problem and for which the same timing advance is applicable.
  • the WTRU 905 then starts searching through WTRU-specific search space of the DL non-primary carrier 960 for PDCCH candidates based on similar rules as LTE release 8 (R8).
  • a PDCCH candidate matches the cell radio network temporary identifier (C-RNTI) of the WTRU 905 for a downlink control information (DCI) format 0 containing an UL grant for UL-shared channel (SCH) in UL carrier 975.
  • C-RNTI cell radio network temporary identifier
  • DCI downlink control information
  • SCH UL-shared channel
  • the WTRU 905 sends an RRC message requesting the network to change the DL primary carrier 955 to DL carrier 960 on the UL-SCH in UL carrier 975.
  • the hybrid automatic repeat request (HARQ) buffers are left intact during the entire procedure.
  • the WTRU 905 may continue to monitor the previous primary carrier on which the radio link failure occurred and report it to the network if a predefined number of in-synch indications occurred or if the signal strength on the previous primary carrier was above a particular threshold. This may be useful if the network had designated the primary carrier on which the WTRU was camped as the "preferred" component carrier for the WTRU.
  • the SR may be sent over another UL carrier paired with a DL non-primary carrier with the in-synch indicator (in this case, the SR may be sent on UL carrier 970. If no PDCCH with DCI format 0 may be received from any DL non-primary carrier, the procedure fails and the WTRU 905 may perform the existing RRC re-establishment procedure.
  • the network 1000 may change the UL primary carrier or this may be performed implicitly based on which UL carrier is paired with the new DL primary carrier.
  • specific PUCCH resources may be identified by higher layers to indicate that assignment of a certain scheduling request should be received on different DL carriers. For example, UL assignments for a scheduling request sent using PUCCHx and PUCCHy are received on the DL primary carrier, but assignments in response to SRs sent over PUCCHz and PUCCHz+1 are received over DL carrier n and DL carrier n+1, respectively.
  • an RRC primary carrier reestablishment procedure may be implemented to request a network 1000, including a WTRU 1005 and an eNB 1010, to change the DL primary carrier.
  • a DL primary carrier 1055 is in a radio link failure condition
  • DL non-primary carriers 1060 and 1065 have in-synch indications
  • an UL carrier 1070 is established.
  • the WTRU 1005 may implicitly designate one of the carriers as the new primary carrier, (e.g., based on signal strength).
  • the same set of system parameters (e.g., RACH, access class barring, or any other suitable parameter), may be applied to the new primary carrier that the WTRU 1005 used on the previous primary carrier, since the network 1000 may preserve the WTRU context for a limited duration after a radio link failure procedure occurs.
  • the WTRU 1005 may implicitly use the information acquired from the old primary carrier.
  • the WTRU 1005 may read selected system information blocks (SIBs) when it accesses the new primary carrier, and then proceed to read the RACH.
  • SIBs system information blocks
  • the network 1000 may signal whether the network 1000 should continue to use the parameters from the current primary carrier when it switches its primary carrier through a one bit field.
  • the WTRU 1005 sends a new type of SR on the PUCCH of the UL carrier 1070 which contains another bit to indicate that the assignment should not be received on the DL primary carrier 1055.
  • a physical random access channel (PRACH) procedure may be applied to generate the SR.
  • PRACH physical random access channel
  • the WTRU 1005 starts searching through WTRU-specific search space of all DL non-primary carriers 1060 and 1065 with an in-synch indication for PDCCH candidates based on similar rules as LTE R8.
  • a PDCCH candidate matches the C-RNTI of the WTRU 1005 for a DCI format 0 containing a UL grant for UL-SCH in the UL carrier 1070.
  • the WTRU 1005 sends an RRC message requesting the network to change the DL primary carrier 1055 to the DL carrier 1060 over the UL-SCH of the UL carrier 1070.
  • the HARQ buffers are left intact during the entire procedure.
  • Another method may be based on a new MAC CE command signifying a DL primary carrier change.
  • the MAC CE command may explicitly identify the new DL primary carrier.
  • the WTRU 1005 may select DL non-primary carrier 1060 or DL non-primary carrier 1065 based on the best signal strength, or identify the DL carrier for which the consecutive in-synch indications were first detected.
  • a MAC CE command may be sent instead of sending an RCC message.
  • confirmation may be signaled by a MAC CE rather than implicit confirmation based on PDCCH reception.
  • the RRC primary re-establishment procedure may be part of a larger intra-cell handover procedure.
  • Configurations applying to the source DL and possibly UL primary carriers, such as DRX cycles, semi-persistent scheduling (SPS), PUCCH/PDCCH and HARQ entity/processes may be transferred to the new target primary carrier upon establishment.
  • SPS semi-persistent scheduling
  • PUCCH/PDCCH and HARQ entity/processes
  • HARQ entity/processes may be transferred to the new target primary carrier upon establishment.
  • the WTRU 1005 may continue to monitor the previous primary carrier on which the radio link failure occurred and report it to the network if a predefined number of in-synch indications occurred or if the signal strength on the previous primary carrier was above a particular threshold. This may be useful if the network 1000 had designated the primary carrier on which the WTRU 1005 was camped as the "preferred" component carrier for the WTRU 1005.
  • the WTRU 1005 may autonomously consider the carrier for which partial radio link failure has occurred as "de-activated,” and may remove it from its connection configuration state in RRC. Alternatively, the WTRU 1005 may perform these actions upon explicit notification from the network 1000. In the latter case, the WTRU 1005 may consider the carrier as in a "dormant" state and perform special monitoring and recovery actions such as described below.
  • the WTRU may either signal the cell IDs or carrier IDs corresponding to all the component carriers or the cell ID or carrier ID corresponding to the primary component carrier to the network.
  • the carrier identifier (numbered within the cell) or the radio frequency channel number (e.g., E-UTRA absolute radio frequency channel number (EARFCN)), broadcast in the LTE-A cell's system information or indicated in the dedicated carrier assignment message, is signaled to the LTE-A eNB or the network in a RRC message such as the RRC connection re-establishment message or other RRC level messages to facilitate the LTE-A eNB for starting recovery actions such as reassigning the data path or control path to one or more other downlink carriers, new or existing to the concerned WTRU within the LTE-A cell.
  • a RRC message such as the RRC connection re-establishment message or other RRC level messages
  • a radio link failure cause may also need to be indicated to the eNB or the network just to distinguish whether the root of the problem is from a detected out-of-synch, an RLC unrecoverable error, PDCP integrity problem or other related problems.
  • the WTRU also may indicate the signal strength and/or the signal quality of the already actively receiving DL carriers, and optionally of some other DL carriers that have been monitored for the event, to facilitate the eNB carrier reassignment decision or a handover decision. If the detected radio link failure carriers include a PDCCH carrier, the WTRU may need to include the measurement results of another PDCCH carrier if the LTE-A cell is configured with more than one PDCCH carrier in the cell.
  • the affected data plane protocol data unit (PDU) sequence number in the PDCP and/or RLC level, send and receive also may be included with their respective HARQ-process identities, transport block sizes and their transport channel or logical channel numbers, and other relevant channel configuration parameters.
  • the status PDUs in either the PDCP or RLC level may also be generated and transmitted to the eNB if still possible for preparing data recovery actions. If the detected radio link failure carrier carries control plane bearers, the related RRC, PDCP, or RLC sequence number may need to be signaled.
  • the WTRU may continue to send and receive over other unaffected carriers, UL and DL, while holding off the transmission or reception of the affected radio link failure carrier UL and DL or DL until a new assignment of the affected data path channel(s) is received from the eNB.
  • the WTRU starts a timer 325 once it has sent out the RRC message about the full or partial radio link failure detection/re-establishment request. If at the expiration of the timer 325, the WTRU has not received an eNB or network message responding to the radio link failure detection/reestablishment request message, the WTRU may resend the same message again. This resending may be repeated a predefined number of times, and after that the WTRU will release all its radio resources and goes to Idle mode.
  • the WTRU may perform one or a combination of the following actions to ensure that it may receive subsequent signaling from the network from other non-failed carriers.
  • the WTRU may activate or reactivate one or a plurality of carriers that had been configured but de-activated or, were in a dormant state, if such state is defined.
  • the WTRU may continuously listen to the PDCCH of other carriers configured with PDCCH reception. Every sub-frame is part of the active time for these carriers, until a stopping condition occurs.
  • the WTRU may suspend its normal DRX behavior on these carriers.
  • this applies to certain carriers configured for this behavior by the network, or carriers that have periodic on durations with a period above a threshold, in case DRX is configured on a per-carrier basis, or, that do not have any periodic on duration.
  • the stopping condition(s) may correspond to one or a subset of the following events: reception of a reconfiguration message from the network, reception of MAC PDU from the network from any control channel (CC), recovery of the carrier for which partial radio link failure had occurred, and detection of full radio link failure.
  • the network knowing that the WTRU applies the following behavior, knows, upon detection of partial radio link failure, that it may transmit subsequent signaling on these carriers regardless of activation status or DRX state on these carriers.
  • the activation and/or DRX suspension described above is applied when there is no other carrier configured with PDCCH that has not failed and that does not satisfy one or a combination of the following criteria: the carrier is activated or is in an active state, in case an "active/non-active" state exists, or the carrier is configured with periodic on durations, with the possible additional condition that the period is below a threshold.
  • the network may provide a UL grant on one of the DL active carriers for which there is no radio problem or partial radio link failure condition and the WTRU may initiate a RACH procedure utilizing the RACH configuration broadcast from one of the DL carriers for which there is no radio problem. This may allow the network to identify that the DL carrier (or one of the DL carriers) that has advertised the RACH resource which the WTRU used for its random access procedure is still in good radio condition, and thus that any UL grant should be transmitted from this (or one of these) DL carriers.
  • this RACH procedure may be initiated when a specific DL carrier (e.g., "special cell”) has failed.
  • the WTRU may require that the RACH procedure is initiated using the RACH configuration broadcast from this specific carrier (or "special cell"), unless a radio problem is detected on this carrier.
  • the network understands that a radio problem has occurred on the "special cell” based on the WTRU initiating a RACH procedure using resources (UL carrier and preamble) not broadcast from the special cell. Based on this information, the network may take action to replace the special cell, such as initiating an RRC reconfiguration with or without mobility.
  • the WTRU is configured to operate with a specific role (e.g., a PPC, anchor carrier or the DL carrier corresponding to the "special cell” or the "serving cell"), it is possible that specific actions need to be taken in case this carrier fails.
  • the procedures described below apply for instance if either (a) the radio link monitoring is performed on a per-carrier basis (as described above) and the carrier or one of the carriers that failed corresponds to the special cell (while there is still at least one carrier that has not failed), or (b) radio link monitoring is performed for this special cell or PCC, and radio link failure is declared, but the signal quality from other carriers the WTRU is configured with is still acceptable.
  • the WTRU initiates the RRC connection reestablishment procedure (assuming security was activated) upon failure of the special cell or PCC.
  • the procedure is modified. For instance, the following modifications may occur:
  • the WTRU does not initiate the RRC connection re-establishment procedure upon detection of failure of the "special cell.”
  • the WTRU instead performs one or a combination of the following actions:
  • the WTRU may use one or a combination of the following methods to facilitate eventual recovery of this carrier in case radio conditions improve.
  • the WTRU keeps evaluating quality against the Q in and Q out thresholds and the physical layer correspondingly keeps sending in-synch and out-of-synch indications to higher layers, but the periodicity of these indications may be increased (as well as the measurement duration) compared to the periodicity prior to partial radio link failure to avoid unnecessarily consuming battery power.
  • the parameters for in-synch and out-of-synch indication measurement and reporting may revert to that corresponding to the DRX configuration for this carrier.
  • the periodicity of in-synch or out-of-synch may revert to pre-defined values or values previously signaled by higher layers (broadcast or dedicated) which are possibly carrier-specific.
  • the WTRU may determine that recovery may be attempted for a failed carrier if the fraction of the most recent indications that are in-synch is above a threshold, or alternatively if some minimum number of consecutive in-synch indications is attained. These thresholds may also be pre-defined values or values previously signaled by higher layers. When this occurs, the WTRU may perform one or a combination of the following actions to request the network to re-initiate transmission on the failed carrier.
  • the WTRU may ensure that it has valid system information pertaining to the failed carrier. This may be achieved by comparing the current value tag of this system information to the value tag of the previously stored system information for this carrier. Alternatively, the WTRU may re-acquire the whole system information broadcast from this carrier.
  • the WTRU may transmit an RRC message to identify recovery of the carrier.
  • a RRC message may be transmitted on any carrier or any carrier that has not failed. It may consist of a measurement report (in which case a new event could be defined to trigger this report).
  • the WTRU may wait for the reception of a confirmation message from the network before considering that recovery has succeeded.
  • the confirmation may be either an explicit RRC message or implicitly detected by a PDCCH command on the DL carrier with the identity of the WTRU.
  • the confirmation message may contain a value tag of system information (pertaining to the failed carrier) to facilitate verification that the WTRU still has valid system information, or the WTRU may reacquire current value tags to ensure it has valid system information.
  • the WTRU may initiate a RACH procedure based on RACH parameters specific to the failed carrier.
  • a successful RACH procedure (where the RACH response originates from the failed carrier) may then effectively translate in a successful recovery.
  • the WTRU may resume activity on the previously failed carrier and in particular evaluates in-synch/out-of-synch as per parameters previously used before the failure. If a UL carrier was paired with the recovered DL carrier for either HARQ feedback or scheduling on PDCCH, the associated UL carrier is also recovered.
  • the WTRU may evaluate in-synch and out-of-synch indications for a limited duration, after which the in-synch and out-of-synch indications are no longer measured. This may be implemented by starting a new timer upon expiry of T310 and stopping in-synch/out-of-synch evaluation upon expiry of this timer.
  • the value of the timer may be pre-defined or signaled by higher layers.
  • the WTRU may evaluates in-synch and out-of-synch indications if, or as long as, the reference signal received power (RSRP) or reference signal received quality (RSRQ) measurement of the carrier is above a threshold, which may be pre-defined or signaled by higher layers.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • the WTRU may notify the network. Alternatively or in addition, the WTRU may act as if the carrier is "de-activated" and remove it from its connection configuration state in RRC.
  • the WTRU may permanently stop measuring in-synch and out-of-synch.
  • the WTRU may continue the recovery until the network explicitly signals the WTRU to disable the recovery procedure. In this case, whenever the WTRU detects recovery of the DL carrier, it indicates to the revival by MAC or RRC signaling.
  • the network may attempt recovery of the failed carrier by sending DL assignments to the WTRU from time to time.
  • DL assignments could, for example, consist of requests to initiate a RACH procedure where dedicated RACH parameters are provided and possibly system information related signaling (e.g., value tag or the information elements (IEs) from system information pertaining to the failed carrier).
  • system information related signaling e.g., value tag or the information elements (IEs) from system information pertaining to the failed carrier.
  • the WTRU may monitor DL assignments from the network with certain restrictions to prevent excessive battery consumption.
  • the following restrictions may be used individually or in combination.
  • the WTRU may monitor DL assignments in certain sub-frames according to a known pattern pre-defined or pre-signaled by higher layers.
  • the pattern may be periodic and may or may not correspond to the DRX configuration of the WTRU pertaining to the failed carrier prior to the occurrence of partial radio link failure.
  • the WTRU may monitor DL assignments if the signal strength and/or quality of the signal on the carrier are above a threshold, which may be pre-defined or pre-signaled by higher layers.
  • the WTRU may monitor DL assignments for a certain period of time after occurrence of partial radio link failure.
  • the WTRU may consider that the carrier is "de-activated” and update its RRC connection configuration context accordingly after this period of time.
  • the WTRU may monitor DL assignments for a certain period of time after requesting recovery of the failed carrier by sending a message to the network (in case this scheme is used in conjunction with the previous one).
  • the WTRU When the WTRU decodes an assignment from the network on the failed carrier, it may immediately consider that recovery is successful. Alternatively, the WTRU may consider that recovery is successful after completion of the RACH procedure subsequent to the reception of the DL assignment.
  • the WTRU When successful recovery has occurred, the WTRU removes the monitoring restrictions and resumes monitoring PDCCH as per the configuration used before the failure.
  • the WTRU starts performing RSRP and/or RSRQ measurements on the frequency of the failed carrier according to some pre-determined measurement configuration.
  • the WTRU may also interrupt measurements performed according to the measurement configuration defined for this frequency prior to the occurrence of partial radio link failure, if such configuration exists.
  • the pre-determined measurement configuration (applicable to the partial radio link failure state of the carrier) may have been provided upon configuration and/or activation of this carrier. Alternatively, it may be a common measurement configuration applicable to any carrier for which partial radio link failure has occurred, and which is pre-defined or provided by dedicated or broadcast signaling. Alternatively, the measurement configuration is provided by the network upon detection (or notification by the WTRU) that partial radio link failure has occurred.
  • the measurement reports from the measurement configuration may be transmitted to one of the other carriers for which failure has not occurred. Based on the measurement reports, the network may initiate recovery of the failed carrier using RRC signaling and/or as per the previous embodiment.
  • the WTRU initiates a RACH procedure in connected mode from an UL carrier to regain synchronization for its transmissions from the UL carrier. It is possible this occurs while the WTRU is still synchronized to the network for its transmissions from UL carriers.
  • the radio link failure condition for carrier aggregation may be modified based on one of the following methods when a random access problem occurs for a RACH procedure initiated from one of the configured UL carriers.
  • the WTRU considers radio link failure to be detected upon a random access problem, while none of the recovery timers 325 (e.g., T300, T301, T304 nor T311) is running, and if the WTRU is not synchronized for its transmissions from any UL carrier. Thus, the timing advance timer is not running for any UL carrier.
  • the recovery timers 325 e.g., T300, T301, T304 nor T311
  • the WTRU considers radio link failure to be detected upon a random access problem, while none of the recovery timers 325 (e.g., T300, T301, T304 nor T311) is running, and if, for all or a subset of other UL carriers from which it is possible to initiate a RACH procedure (or as configured by the network), a random access problem has occurred after last expiry of the timing advance timer applicable to this carrier, (i.e., since the WTRU last lost synchronization for transmissions from this UL carrier).
  • the recovery timers 325 e.g., T300, T301, T304 nor T311
  • the WTRU 100 monitors for a radio link failure.
  • the WTRU 100 comprises a processor 255 that may be configured to determine a primary DL carrier among a set of component carriers configured or activated for the WTRU 100.
  • a first counter 330 1 in the WTRU 100 may be configured to count out-of-synch indications from the primary DL carrier.
  • a recovery timer 325 1 in the WTRU 100 may be configured to be initiated on a condition that a predefined number of out-of-synch indications from the primary DL carrier was counted, as determined by the first counter 330 1 .
  • a second counter 330 2 in the WTRU 100 may be configured to count in-synch indications from the primary DL carrier.
  • a radio link failure may be declared on a condition that a predefined number of in-synch indications from the primary DL carrier is not counted by the second counter before the recovery timer expires.
  • An RRC connection re-establishment procedure may be initialized, whereby the WTRU 100 selects a cell corresponding to one of the component carriers for which a radio problem does not exist.
  • An RRC connection re-establishment message may be transmitted by initating a random access channel (RACH) procedure using resources broadcast by a cell selected by the WTRU 100 that corresponds to one of the component carriers for which a radio problem does not exist.
  • RACH random access channel
  • An SR may be transmitted on a PUCCH, and an RRC connection reestablishment message may be transmitted.
  • the PUCCH may be allocated on a UL carrier paired to a DL carrier that does not have a radio problem.
  • the primary DL carrier may be selected from a plurality of DL carriers, wherein the selected primary DL carrier has the highest coverage among the plurality of DL carriers.
  • the primary DL carrier may be selected from a plurality of DL carriers, wherein the selected primary DL carrier provides PDCCH signaling.
  • the primary DL carrier may be selected from a plurality of DL carriers that are in DRX active time based on a predefined or signaled priority.
  • the primary DL carrier may be obtained from a network through RRC signaling.
  • a radio link failure may be declared on a condition that a predefined number of in-synch indications from the primary DL carrier is not counted by the second counter before the recovery timer expires, and either a connection reestablishment procedure or an RRC connection release procedure may be performed on a condition that a radio link failure is declared.
  • the recovery timer 325 1 in the WTRU 100 may be stopped on a condition that a predefined number of in-synch indications was received from the primary carrier before the recovery timer 325 1 expires.
  • a primary re-establishment procedure may be performed on a condition that a predefined number of in-synch indications was not received from the primary carrier before the recovery timer expires.
  • the WTRU 100 comprises a plurality of out-of-synch indication counters (e.g., 330 1 , 330 2 , 330 3 ), configured to count out-of-synch indications from each of a plurality of PDCCH carriers activated for the WTRU.
  • a recovery timer 325 1 in the WTRU 100 may be configured to be initiated on a condition that a predefined number of out-of-synch indications from a particular one of the PDCCH carriers was counted.
  • An in-synch indication counter (e.g., 330 4 ) may be configured to count in-synch indications from the particular PDCCH carrier.
  • a partial radio link failure associated with the particular PDCCH may be declared on a condition that the recovery timer 325 1 expires before a predefined number of in-synch indications is counted.
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs); Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • FPGAs Field Programmable Gate Arrays
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, Mobility Management Entity (MME) or Evolved Packet Core (EPC), or any host computer.
  • WTRU wireless transmit receive unit
  • UE user equipment
  • MME Mobility Management Entity
  • EPC Evolved Packet Core
  • the WTRU may be used in conjunction with modules, implemented in hardware and/or software including a Software Defined Radio (SDR), and other components such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a Near Field Communication (NFC) Module, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any Wireless Local Area Network (WLAN) or Ultra Wide Band (UWB) module.
  • SDR Software Defined Radio
  • other components such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard

Claims (8)

  1. Verfahren, das durch eine Drahtlos-Sende- und -Empfangseinheit (Wireless Transmit/Receive Unit, WTRU) implementiert wird, zum Überwachen einer Funkverbindung, wobei das Verfahren Folgendes umfasst:
    Arbeiten mit einem Satz von Downlink (DL)-Komponententrägern, die Folgendes enthalten:
    (1) mehrere Komponententräger, die einen primären Komponententräger (Primary Component Carrier, PCC) enthalten, der mit einem ersten Uplink-Träger gepaart ist und einen Physical Downlink Control Channel (PDCCH) enthält, der durch die WTRU überwacht wird, und
    (2) mindestens einen sekundären Komponententräger, wobei einer des mindestens einen sekundären Komponententrägers mit einem zweiten Uplink-Träger gepaart ist und einen PDCCH enthält, der durch die WTRU überwacht wird;
    Zählen von Asynchronitätsanzeichen für den PCC durch Überwachen von Asynchronitätsanzeichen des PCC und Zählen von Asynchronitätsanzeichen für den einen des mindestens einen sekundären Komponententrägers durch Überwachen von Asynchronitätsanzeichen des einen des mindestens einen sekundären Komponententrägers; und
    unter der Bedingung, dass ein Funkverbindungsausfall des einen des mindestens einen sekundären Komponententrägers detektiert wird:
    (1) Senden einer Benachrichtigung über den Funkverbindungsausfall an einen evolved Node B (eNB), der mit dem ersten Uplink-Träger verknüpft ist, und
    (2) Aussetzen von Uplink-Übertragungen auf dem zweiten Uplink-Träger, der mit dem einen des mindestens einen sekundären Komponententrägers, und aussetzen dem einen des mindestens einen sekundären Komponententrägers gepaart ist,
    wobei der Funkverbindungsausfall des einen des mindestens einen sekundären Komponententrägers auf der Basis von Folgendem detektiert wird:
    (1) ein Wiederherstellungs-Timer in der WTRU startet basierend auf dass eine detektierte Anzahl von Asynchronitätsanzeichen des einen des mindestens einen sekundären Komponententrägers gezählt wird, und
    (2) der Wiederherstellungs-Timer abläuft bevor eine vorgegebene Anzahl von Synchronitätsanzeichen für den einen des mindestens einen sekundären Komponententrägers gezählt wird.
  2. Drahtlos-Sende- und -Empfangseinheit (Wireless Transmit/Receive Unit, WTRU) zum Überwachen auf einen Funkverbindungsausfall, wobei die WTRU Folgendes umfasst:
    einen Empfänger, der dafür konfiguriert ist, mit Folgendem zu arbeiten:
    (1) mehreren Komponententrägern, die einen primären Komponententräger (Primary Component Carrier, PCC) enthalten, der mit einem ersten Uplink-Träger gepaart ist und einen Physical Downlink Control Channel (PDCCH) enthält, der durch die WTRU überwacht wird, und
    (2) mindestens einem sekundären Komponententräger, wobei einer des mindestens einen sekundären Komponententrägers mit einem zweiten Uplink-Träger gepaart ist und einen PDCCH enthält, der durch die WTRU überwacht wird;
    wobei der Empfänger, in Kommunikation mit einem Prozessor, für Folgendes konfiguriert ist:
    Zählen von Asynchronitätsanzeichen für den PCC durch Überwachen von Asynchronitätsanzeichen des PCC und Zählen von Asynchronitätsanzeichen für den einen des mindestens einen sekundären Komponententrägers durch Überwachen von Asynchronitätsanzeichen des einen des mindestens einen sekundären Komponententrägers; und
    wobei unter der Bedingung, dass ein Funkverbindungsausfall des einen des mindestens einen sekundären Komponententrägers detektiert wird, ein Sender für Folgendes konfiguriert ist:
    (1) Senden einer Benachrichtigung über den Funkverbindungsausfall an einen evolved Node B (eNB), der mit dem ersten Uplink-Träger verknüpft ist, und
    (2) Aussetzen von Uplink-Übertragungen auf dem zweiten Uplink-Träger, der mit dem einen des mindestens einen sekundären Komponententrägers, und aussetzen dem einen des mindestens einen sekundären Komponententrägers gepaart ist,
    wobei der Funkverbindungsausfall des einen des mindestens einen sekundären Komponententrägers auf der Basis von Folgendem detektiert wird:
    (1) ein Wiederherstellungs-Timer in der WTRU startet basierend auf dass eine detektierte Anzahl von Asynchronitätsanzeichen des einen des mindestens einen sekundären Komponententrägers gezählt wird, und
    (2) der Wiederherstellungs-Timer abläuft bevor eine vorgegebene Anzahl von Synchronitätsanzeichen für den einen des mindestens einen sekundären Komponententrägers gezählt wird.
  3. Verfahren nach Anspruch 1, wobei die Benachrichtigung eine Zellenidentität, ID, oder eine Träger-ID enthält.
  4. Verfahren nach Anspruch 1, wobei die Benachrichtigung eine Ursache für den Funkverbindungsausfall angibt.
  5. Verfahren nach Anspruch 4, wobei die Ursache des Funkverbindungsausfalls eines von Folgendem ist: Detektieren von Asynchronitätsanzeichen, ein Funkverbindungssteuerungs, Radio Link Control, RLC, -Fehler, oder ein Direktzugriffsfehler.
  6. WTRU nach Anspruch 2, wobei die Benachrichtigung eine Zellenidentität, ID, oder eine Träger-ID enthält.
  7. WTRU nach Anspruch 2, wobei die Benachrichtigung eine Ursache für den Funkverbindungsausfall angibt.
  8. WTRU nach Anspruch 7, wobei die Ursache des Funkverbindungsausfalls eines von Folgendem ist: Detektieren von Asynchronitätsanzeichen, ein Funkverbindungssteuerungs, Radio Link Control, RLC,-Fehler, oder ein Direktzugriffsfehler.
EP10710714.6A 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall Active EP2407002B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20185131.8A EP3761750A1 (de) 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US15964909P 2009-03-12 2009-03-12
US21817109P 2009-06-18 2009-06-18
US24826409P 2009-10-02 2009-10-02
US25077309P 2009-10-12 2009-10-12
US25668709P 2009-10-30 2009-10-30
PCT/US2010/027126 WO2010105148A1 (en) 2009-03-12 2010-03-12 Method and apparatus for monitoring for a radio link failure

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP20185131.8A Division EP3761750A1 (de) 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall

Publications (2)

Publication Number Publication Date
EP2407002A1 EP2407002A1 (de) 2012-01-18
EP2407002B1 true EP2407002B1 (de) 2020-08-12

Family

ID=42184104

Family Applications (2)

Application Number Title Priority Date Filing Date
EP20185131.8A Pending EP3761750A1 (de) 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall
EP10710714.6A Active EP2407002B1 (de) 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP20185131.8A Pending EP3761750A1 (de) 2009-03-12 2010-03-12 Verfahren und vorrichtung zum überwachen auf einen funkstreckenausfall

Country Status (8)

Country Link
US (3) US8711709B2 (de)
EP (2) EP3761750A1 (de)
KR (3) KR101457754B1 (de)
CN (2) CN102396288B (de)
AR (1) AR076115A1 (de)
HK (1) HK1168234A1 (de)
TW (2) TWI502907B (de)
WO (1) WO2010105148A1 (de)

Families Citing this family (170)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2070271A1 (de) * 2006-09-28 2009-06-17 Nxp B.V. Verbessertes verfahren zur datenübertragung in einem zweifachen übertragungsmodus zwischen einem mobilen netzwerk und mobilen stationen sowie entsprechende schaltungsmobilitätsverwaltungseinheit
JP5330531B2 (ja) * 2008-11-10 2013-10-30 インターデイジタル パテント ホールディングス インコーポレイテッド タイマを動作させるための方法および装置
KR101532222B1 (ko) * 2008-12-16 2015-06-29 삼성전자주식회사 통신 시스템 및 그의 ｒｒｃ 접속 방법
AR076115A1 (es) 2009-03-12 2011-05-18 Interdigital Patent Holdings Metodo y aparato para monitorear una falla de enlace radial
CN102187727B (zh) * 2009-03-12 2015-03-25 Lg电子株式会社 无线通信系统中在用户设备处切换操作载波的方法
WO2010103895A1 (ja) 2009-03-13 2010-09-16 シャープ株式会社 移動局装置、基地局装置、集積回路、およびランダムアクセス問題の検出方法
US20100240359A1 (en) * 2009-03-22 2010-09-23 Chih-Hsiang Wu Method of Handling Radio link Failure in a Wireless Communication System and Related Communication Device
US8700029B2 (en) * 2009-03-22 2014-04-15 Htc Corporation Method of handling radio link failure detection in a wireless communication system and related communication device
DK2425661T3 (da) * 2009-04-27 2014-04-22 Ericsson Telefon Ab L M Fremgangsmåder og indretninger til ressourcefordeling for direkte tilgang i trådløse telekommunikationssystemer med bærer-aggregation
CN101873577B (zh) * 2009-04-27 2017-03-22 电信科学技术研究院 通知ue变更成员载波监听的方法、系统及装置
US8971257B2 (en) * 2009-04-30 2015-03-03 Qualcomm Incorporated PCFICH design for multicarrier operation
US20100302951A1 (en) * 2009-05-26 2010-12-02 Ou Meng-Hui Method and Apparatus for Handling Radio Link Failure
KR101617048B1 (ko) * 2009-06-01 2016-05-02 엘지전자 주식회사 다중 반송파 시스템에서 요소 반송파의 실패를 처리하는 방법 및 장치
US9596631B2 (en) 2009-06-22 2017-03-14 Sun Patent Trust Communication terminal
JP5059062B2 (ja) * 2009-07-08 2012-10-24 シャープ株式会社 通信システム、移動局装置および基地局装置
CN101998474B (zh) * 2009-08-13 2012-07-18 电信科学技术研究院 一种载波聚合技术中的无线链路失败判决方法及装置
US9351293B2 (en) * 2009-09-11 2016-05-24 Qualcomm Incorporated Multiple carrier indication and downlink control information interaction
WO2011035420A1 (en) 2009-09-25 2011-03-31 Research In Motion Limited System and method for multi-carrier network operation
WO2011038272A1 (en) 2009-09-25 2011-03-31 Mo-Han Fong System and method for multi-carrier network operation
CN105721132B (zh) 2009-09-25 2019-03-26 黑莓有限公司 用于多载波网络操作的系统和方法
HUE051735T2 (hu) 2009-09-25 2021-03-29 Blackberry Ltd Többvivõs hálózati üzem
US9763197B2 (en) * 2009-10-05 2017-09-12 Qualcomm Incorporated Component carrier power control in multi-carrier wireless network
WO2011043394A1 (ja) * 2009-10-06 2011-04-14 株式会社エヌ・ティ・ティ・ドコモ ユーザ装置、基地局装置及び移動通信方法
TW201129197A (en) * 2009-10-07 2011-08-16 Innovative Sonic Corp Method and apparatus for handling radio link failure in wireless communication system
US9148809B2 (en) * 2009-10-13 2015-09-29 At&T Intellectual Property I, L.P. Employing handover failures for network fault prediction or remedy
JP5445186B2 (ja) 2009-10-30 2014-03-19 ソニー株式会社 基地局、端末装置、通信制御方法及び無線通信システム
US8488443B2 (en) * 2009-11-04 2013-07-16 Lg Electronics Inc. Method for handling radio line failure in multiple carrier system
US8792328B2 (en) * 2009-11-06 2014-07-29 Intel Corporation Radio-link reliability using multi-carrier capability in wireless broadband systems
US8767641B2 (en) * 2009-11-16 2014-07-01 Texas Instruments Incorporated Carrier indication in a bandwidth aggregated wireless communications systems
US9124406B2 (en) * 2009-12-29 2015-09-01 Qualcomm Incorporated Fallback operation for cross-carrier signaling in multi-carrier operation
US20120281527A1 (en) * 2010-01-05 2012-11-08 Benoist Pierre Sebire Re-Establishment of Component Carriers in a Wireless Communication System
CN102123479B (zh) * 2010-01-08 2015-09-16 索尼公司 支持载波汇聚的通信系统及其系统信息更新方法和设备
CN102131243A (zh) * 2010-01-15 2011-07-20 中兴通讯股份有限公司 一种传输ue支持多载波能力的方法和系统
CN106160992B (zh) 2010-02-12 2020-07-03 交互数字专利控股公司 增强无线发射/接收单元的小区边缘性能的方法及网络
JP5654054B2 (ja) * 2010-02-24 2015-01-14 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 無線通信ネットワークにおける搬送波の発見
CN102201888B (zh) * 2010-03-25 2015-04-01 中兴通讯股份有限公司 多载波同步检测的方法及装置
JP4823371B2 (ja) * 2010-03-30 2011-11-24 シャープ株式会社 無線通信システム、移動局装置、基地局装置、無線通信方法および集積回路
US9084195B2 (en) 2010-04-01 2015-07-14 Nokia Technologies Oy Multiple timing advance and carrier aggregation
CN102823170B (zh) * 2010-04-03 2015-07-08 Lg电子株式会社 终端在无线通信系统中建立分量载波的方法及其装置
EP2375850B1 (de) * 2010-04-06 2016-09-07 Alcatel Lucent Steuerung von Kommunikationen in einem drahtlosen Mehrträger-Kommunikationssystem
CN102238750A (zh) * 2010-04-23 2011-11-09 中兴通讯股份有限公司 无线资源控制连接重建触发方法及装置
US9088902B2 (en) * 2010-04-30 2015-07-21 Nokia Technologies Oy User equipment carrier activation
US8780729B2 (en) * 2010-05-03 2014-07-15 Nokia Corporation Monitoring pattern separation between component carriers based on user equipment RF layout
US8649363B2 (en) * 2010-06-01 2014-02-11 Htc Corporation Method of hybrid automatic repeat request entity handling and communication device thereof
EP2398285B1 (de) * 2010-06-18 2016-11-16 Alcatel Lucent Stromsparen
US9119146B2 (en) * 2010-06-30 2015-08-25 Nokia Solutions And Networks Oy Scheduling of user terminals in communication network
US20140050197A1 (en) * 2010-08-11 2014-02-20 Huawei Technologies Co., Ltd. Method for Providing Information in a Cellular Wireless Communication System
US8644832B2 (en) 2010-08-12 2014-02-04 At&T Intellectual Property I, L.P. Redirecting handovers in LTE networks
US8755753B2 (en) * 2010-10-29 2014-06-17 Samsung Electronics Co., Ltd. Apparatus and method for channel measurement in radio link monitoring in a wireless network
CN103238368B (zh) * 2010-12-03 2017-02-15 交互数字专利控股公司 用于执行多无线电接入技术载波聚合的方法、装置和系统
WO2012094573A2 (en) 2011-01-07 2012-07-12 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for handling additional power backoff
KR20120081736A (ko) * 2011-01-12 2012-07-20 삼성전자주식회사 이동 통신시스템에서 알엘씨 엔터티의 재설립 동안의 회복 불능 오류 처리를 위한 방법 및 장치
US20120214540A1 (en) 2011-02-21 2012-08-23 Motorola Mobility, Inc. Signal Measurement on Component Carriers in Wireless Communication Systems
US8503322B2 (en) 2011-02-21 2013-08-06 Motorola Mobility Llc IQ imbalance image compensation in multi-carrier wireless communication systems
US8619716B2 (en) 2011-02-21 2013-12-31 Motorola Mobility Llc IQ imbalance image compensation in multi-carrier wireless communication systems
US8666321B2 (en) 2011-02-21 2014-03-04 Motorola Mobility Llc Signal measurement on component carriers in wireless communication systems
CN102143522B (zh) * 2011-04-13 2015-02-18 电信科学技术研究院 一种无线链路失败的处理方法和设备
EP2698024A1 (de) * 2011-04-15 2014-02-19 Telefonaktiebolaget LM Ericsson (PUBL) Verfahren und vorrichtungen zur funkverbindungsüberwachung
US9380484B2 (en) * 2011-04-18 2016-06-28 Innovative Sonic Corporation Method and apparatus to prevent radio access network (RAN) overload in a wireless communication system
US20120275366A1 (en) * 2011-04-29 2012-11-01 Nicholas William Anderson Switching activation of ue receviers
US9042315B2 (en) 2011-05-03 2015-05-26 Mediatek Inc. SCELL radio link monitoring and radio link failure handling
US8908504B2 (en) * 2011-07-01 2014-12-09 Qualcomm Incorporated Pre-agreed radio link failure recovery channel sequence
KR101542413B1 (ko) * 2011-07-25 2015-08-07 엘지전자 주식회사 무선 통신 시스템에서 무선 링크 모니터링 방법 및 장치
US8995370B2 (en) 2011-07-29 2015-03-31 Interdigital Patent Holdings, Inc. Method and apparatus for radio resources management in multi-radio access technology wireless systems
JP5825616B2 (ja) * 2011-08-12 2015-12-02 ノキア ソリューションズ アンド ネットワークス オサケユキチュア キャリアアグリゲーションのための不連続受信
KR20140075770A (ko) * 2011-09-29 2014-06-19 노키아 솔루션스 앤드 네트웍스 오와이 방법 및 장치
CN106385714B (zh) 2011-09-30 2020-09-08 华为技术有限公司 无线连接重建方法、用户设备和基站
KR101850549B1 (ko) * 2011-10-04 2018-04-20 삼성전자주식회사 무선 통신 시스템에서 무선 링크 모니터링 장치 및 방법
WO2013050646A2 (en) * 2011-10-04 2013-04-11 Nokia Corporation Method and apparatus for handovers
US9094988B2 (en) 2012-01-17 2015-07-28 Qualcomm Incorporated Method and apparatus for performing random access on a secondary carrier
CA2861883A1 (en) * 2012-01-20 2013-07-25 Fujitsu Limited Method for analyzing a cause of link failure, method of network optimization and apparatus
ES2637386T3 (es) * 2012-01-30 2017-10-13 Nokia Solutions And Networks Oy Mejora de la movilidad usando un número más elevado de mediciones de la movilidad durante un período de tiempo
US9019836B2 (en) 2012-02-03 2015-04-28 Qualcomm Incorporated Downlink data transfer flow control during carrier aggregation
US9629028B2 (en) * 2012-03-16 2017-04-18 Qualcomm Incorporated System and method for heterogeneous carrier aggregation
US8780782B2 (en) * 2012-03-16 2014-07-15 Qualcomm Incorporated Method and apparatus for handling radio link failure in LTE eMBMS
US8995366B2 (en) * 2012-03-23 2015-03-31 Google Technology Holdings LLC Radio link monitoring in a wireless communication device for a enhanced control channel
US8982693B2 (en) 2012-05-14 2015-03-17 Google Technology Holdings LLC Radio link monitoring in a wireless communication device
US9198070B2 (en) 2012-05-14 2015-11-24 Google Technology Holdings LLC Radio link monitoring in a wireless communication device
CN103428876B (zh) * 2012-05-16 2016-08-10 华为技术有限公司 物理信道资源调度方法、用户设备及基站
WO2014007595A1 (en) * 2012-07-06 2014-01-09 Samsung Electronics Co., Ltd. Method and apparatus for determining tdd ul-dl configuration applicable for radio frames
US9686800B2 (en) * 2012-08-03 2017-06-20 Qualcomm Incorporated Methods and apparatus for reporting channel quality indicator (CQI)
WO2014031989A1 (en) * 2012-08-23 2014-02-27 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
CN110087266B (zh) 2012-08-23 2021-09-28 交互数字专利控股公司 向不同服务站点提供物理层资源
US9210673B2 (en) 2012-09-06 2015-12-08 Apple Inc. Recovery from uplink timing alignment failures in cellular communications
US9253667B2 (en) * 2012-09-10 2016-02-02 Blackberry Limited Methods and apparatus for mobile device recovery following radio link failure
CN109769278A (zh) * 2012-09-28 2019-05-17 三菱电机株式会社 移动通信系统
EP2904871A1 (de) * 2012-10-05 2015-08-12 Nokia Technologies Oy Begrenzung der wiederherstellung von funkressourcensteuerungsverbindungen
US9042256B2 (en) * 2012-10-15 2015-05-26 Broadcom Corporation Network isolation system
US9131434B2 (en) 2012-10-19 2015-09-08 Blackberry Limited Using a cell as a pathloss or timing reference
GB2507299B (en) * 2012-10-25 2015-04-01 Samsung Electronics Co Ltd Mobile terminal preparation
EP3846576B1 (de) * 2012-11-13 2023-03-08 Telefonaktiebolaget LM Ericsson (publ) Verfahren zum betrieb eines drahtlosen gerätes in einem zellularen kommunikationsnetz sowie entsprechendes drahtloses gerät
RU2606398C1 (ru) 2012-11-13 2017-01-10 Телефонактиеболагет Л М Эрикссон (Пабл) Способ и устройство запуска особого режима работы для терминалов, работающих на увеличенной большой дальности
CN104798321B (zh) 2012-11-25 2018-01-30 Lg 电子株式会社 用于在无线通信系统中发送和接收数据的方法和装置
CN103906097B (zh) * 2012-12-25 2017-12-15 华为技术有限公司 一种同失步处理方法及装置
WO2014132560A1 (ja) * 2013-02-28 2014-09-04 日本電気株式会社 無線通信システム、無線局、無線端末、通信制御方法、及び非一時的なコンピュータ可読媒体
BR112015020215A2 (pt) * 2013-02-28 2017-07-18 Sony Corp dispositivo de terminal, programa, e, método de controle de comunicação
CN104080137B (zh) * 2013-03-29 2018-05-18 华为技术有限公司 小区切换的方法和用户设备
KR20140120806A (ko) * 2013-04-04 2014-10-14 주식회사 케이티 Small cell에서 RLF(Radio Link Failure)를 detection 하는 방법 및 장치
US9160515B2 (en) 2013-04-04 2015-10-13 Intel IP Corporation User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay
CN104685930B (zh) * 2013-04-09 2019-02-19 华为技术有限公司 一种通讯方法和终端
WO2015002466A2 (ko) 2013-07-04 2015-01-08 한국전자통신연구원 이동 통신 시스템에서 복수 연결을 지원하기 위한 제어 방법 및 복수 연결 지원 장치
CN105612804A (zh) * 2013-08-09 2016-05-25 诺基亚通信公司 在无线网络中对从辅基站到主基站的分组状态报告的使用
US9654952B2 (en) * 2013-08-12 2017-05-16 Verizon Patent And Licensing Inc. Personal emergency message framework
KR102126802B1 (ko) * 2013-08-27 2020-06-25 에스케이텔레콤 주식회사 기지국장치 및 기지국장치의 동작 방법
WO2015060543A1 (en) 2013-10-23 2015-04-30 Lg Electronics Inc. Method for reporting a radio link problem and a device therefor
US9450809B2 (en) * 2013-10-28 2016-09-20 Industrial Technology Research Institute Method of handling uplink transmission and related communication device
US9173241B2 (en) * 2013-11-07 2015-10-27 Google Technology Holdings LLC Radio-link establishment for multi-state cells
US9888376B2 (en) * 2014-01-06 2018-02-06 Intel IP Corporation Autonomous enhanced node B
CN109246735B (zh) * 2014-01-24 2021-12-14 索尼公司 无线通信系统、无线通信系统中的装置和方法
EP3823350A1 (de) * 2014-03-21 2021-05-19 Samsung Electronics Co., Ltd. Verfahren und vorrichtung zur steuerung der wartezeit zur bestimmung von funkverbindungsfehlern in einem drahtlosen kommunikationssystem
US9955445B2 (en) * 2014-04-01 2018-04-24 Samsung Electronics Co., Ltd System and method for enhancing reporting information for radio link failure (RLF) in LTE networks
JP6031555B2 (ja) * 2014-05-13 2016-11-24 宏達國際電子股▲ふん▼有限公司 測定構成を処理する装置
US10009925B2 (en) 2014-10-03 2018-06-26 Qualcomm Incorporated Physical layer procedures for LTE in unlicensed spectrum
US9591648B1 (en) * 2014-11-03 2017-03-07 Sprint Spectrum L.P. Semi-persistent secondary signaling channels
WO2016148477A1 (ko) * 2015-03-18 2016-09-22 엘지전자 주식회사 무선 통신 시스템에서 접속 손실 발생시 데이터를 처리하는 방법 및 이를 위한 장치
US10411847B2 (en) * 2015-04-10 2019-09-10 Futurewei Technologies, Inc. Communications with carrier selection, switching and measurements
US10123356B2 (en) 2015-04-27 2018-11-06 Telefonaktiebolaget Lm Ericsson (Publ) Robust selection of PRACH repetition level for MTC enhanced coverage
US10524303B2 (en) * 2015-04-29 2019-12-31 Nokia Solutions And Networks Oy Radio link problem handling in mobile communication systems
US10735982B2 (en) * 2015-05-15 2020-08-04 Kyocera Corporation Radio terminal and base station for monitoring a physical downlink control channel during a discontinuous reception operation
US10154523B2 (en) * 2015-06-10 2018-12-11 Htc Corporation Device and method of aggregating LTE System and WLAN
EP3387769B1 (de) 2015-12-11 2019-04-03 Telefonaktiebolaget LM Ericsson (PUBL) Funknetzknoten und drahtlose vorrichtung sowie verfahren darin
CN106937338B (zh) * 2015-12-31 2020-01-10 中国电信股份有限公司 链路重建方法和系统
WO2017173612A1 (zh) * 2016-04-07 2017-10-12 华为技术有限公司 数据传输方法、用户设备及接入网设备
WO2017176376A1 (en) * 2016-04-08 2017-10-12 Intel IP Corporation 60ghz-lwa support: discovery and keep alive
JP2019110355A (ja) * 2016-04-26 2019-07-04 シャープ株式会社 端末装置、通信方法、および、集積回路
US10314099B2 (en) * 2016-07-02 2019-06-04 Intel IP Corporation Communication protocol recovery system and method
US20180027430A1 (en) * 2016-07-20 2018-01-25 Zinwave Limited Techniques for locating distributed antenna locations
CN107659956B (zh) * 2016-07-26 2021-03-30 财团法人工业技术研究院 以用户设备反馈控制可配置承载的基站、用户设备及方法
CN108781373B (zh) * 2016-08-12 2022-04-08 联发科技（新加坡）私人有限公司 无线链路失败检测的处理方法以及用户设备
EP3497967B1 (de) 2016-08-12 2024-02-14 Sony Group Corporation Kommunikationsvorrichtungen, infrastrukturausrüstung und verfahren
CN107889133B (zh) * 2016-09-30 2021-06-08 华为技术有限公司 无线链路检测和处理方法及装置
EP3566487A4 (de) * 2017-01-06 2020-08-19 LG Electronics Inc. -1- Verfahren zur funkverbindungsüberwachung und ausfallverfahren eines mehrstrahlenbetriebs in einem drahtloskommunikationssystem und vorrichtung dafür
EP4236605A3 (de) * 2017-03-13 2024-01-03 Nokia Technologies Oy Duplizierung und rlc-betrieb in new-radio-zugriffstechnologie
US10219311B2 (en) * 2017-03-15 2019-02-26 Motorola Mobility Llc Monitoring and handling a radio link failure in an inactive state
US20180287869A1 (en) * 2017-03-29 2018-10-04 Intel Corporation Technologies for altering modem configurations
US10644974B2 (en) 2017-05-04 2020-05-05 At&T Intellectual Property I, L.P. Measurements and radio link monitoring in a wireless communications system
US11032744B2 (en) 2017-05-04 2021-06-08 At&T Intellectual Property I, L.P. Inter-distributed unit beam switch procedure triggered by radio link interruption
US11184080B2 (en) 2017-09-11 2021-11-23 Qualcomm Incorporated Radio link monitoring and beam failure recovery resource configuration and operation
EP3461026B1 (de) * 2017-09-22 2020-07-15 ASUSTek Computer Inc. Verfahren und vorrichtung zur verhinderung der bandbreiteteilfehlausrichtung in einem drahtloskommunikationssystem
AU2018342175A1 (en) * 2017-09-27 2020-04-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data generation method, logical channel configuration method, terminal device and chip
US10499398B2 (en) 2017-09-29 2019-12-03 At&T Intellectual Property I, L.P. Facilitating mobile device-assisted mobility enhancement to improve user plane interruption time
US11172392B2 (en) 2017-10-06 2021-11-09 Lg Electronics Inc. Method and apparatus for declaring RLF
CN109699034B (zh) 2017-10-20 2022-03-29 维沃移动通信有限公司 一种波束失败恢复的处理方法及终端
CN111886891B (zh) * 2018-01-11 2024-02-06 株式会社Ntt都科摩 用户终端以及无线通信方法
US20200337102A1 (en) * 2018-01-11 2020-10-22 Telefonaktiebolaget Lm Ericsson (Publ) Radio Link Maintenance Involving Multiple Uplink Carriers
EP3742783A4 (de) * 2018-01-19 2021-09-08 Fujitsu Limited Verfahren und vorrichtung zum empfangen und senden von konfigurationsinformationen und kommunikationssystem
US10873985B2 (en) 2018-02-14 2020-12-22 Htc Corporation Device and method of handling a dual connectivity with base stations
KR102528856B1 (ko) 2018-03-07 2023-05-04 삼성전자주식회사 무선 통신 시스템에서 동기 회복을 위한 장치 및 방법
EP3780838A4 (de) * 2018-04-25 2021-12-15 Beijing Xiaomi Mobile Software Co., Ltd. Verfahren und vorrichtung zur anzeige der belegung einer semi-persistenten planungseinheit und basisstation
JP7128897B6 (ja) 2018-05-07 2022-10-04 オッポ広東移動通信有限公司 Ｒｒｃ接続の回復方法、装置及びコンピュータ記憶媒体
US10880762B2 (en) * 2018-05-21 2020-12-29 Qualcomm Incorporated Link quality monitoring, signaling and procedures for specific service type
CN110611920B (zh) 2018-06-15 2021-06-01 维沃移动通信有限公司 一种无线链路监测方法及终端
US10904939B2 (en) * 2018-08-31 2021-01-26 Samsung Electronics Co., Ltd. User equipment (UE) and method thereof for efficient communication with wireless network
US20220039188A1 (en) * 2018-09-20 2022-02-03 Sharp Kabushiki Kaisha Systems, devices, and methods for handling radio link failures in wireless relay networks
WO2020087214A1 (zh) * 2018-10-29 2020-05-07 北京小米移动软件有限公司 控制波束失败恢复流程的方法及装置
CN113316172B (zh) 2018-10-31 2023-01-06 Oppo广东移动通信有限公司 一种计数方法、终端设备及装置
EP3892047A4 (de) * 2018-12-03 2022-08-03 Telefonaktiebolaget LM Ericsson (publ.) Uplink-übertragung unter verwendung eines unlizenzierten frequenzspektrums
KR20210109534A (ko) * 2018-12-28 2021-09-06 지티이 코포레이션 무선 통신에서 전송 실패를 표시하는 방법, 장치 및 시스템
WO2020149980A1 (en) * 2019-01-15 2020-07-23 Mediatek Singapore Pte. Ltd. Method and apparatus for communication
US11483768B2 (en) * 2019-03-28 2022-10-25 Qualcomm Incorporated Methods and apparatus to facilitate PDCCH monitoring in carrier aggregation for lower power consumption
US11057817B2 (en) * 2019-04-29 2021-07-06 Telefonaktiebolaget Lm Ericsson (Publ) User equipment, network node and method in a wireless communications network
CN111918316B (zh) * 2019-05-10 2022-05-03 大唐移动通信设备有限公司 基站维护方法和基站维护装置
EP3958617A4 (de) * 2019-05-14 2022-07-20 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Verfahren zum umschalten zwischen zugangsnetzwerkvorrichtungen, endgerätevorrichtung und netzwerkvorrichtung
CN114080830B (zh) * 2019-07-04 2023-11-10 Lg电子株式会社 无线通信系统中的信号发送/接收方法
CN112217716A (zh) * 2019-07-10 2021-01-12 北京三星通信技术研究有限公司 数据包路由的方法及设备、数据包传输的控制方法及设备
US20210045177A1 (en) * 2019-08-06 2021-02-11 Qualcomm Incorporated Handling repeated network configuration failure
CN112584443A (zh) 2019-09-27 2021-03-30 苹果公司 辅助小区链路恢复请求传输
CN112954713A (zh) * 2019-12-11 2021-06-11 维沃移动通信有限公司 测量方法和终端
CN112203361B (zh) * 2020-10-12 2023-02-28 Oppo（重庆）智能科技有限公司 无线链路失败的处理方法及装置、终端、存储介质
US11595957B2 (en) * 2021-04-29 2023-02-28 Qualcomm Incorporated Techniques for parallel search and measurement in wireless communications

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60314331T2 (de) * 2002-05-03 2008-02-14 Innovative Sonic Ltd., Road Town Verfahren von Zellenaktualisierung via Leerlauf zwecks Stromsparung in einem UMTS Mobil nach gescheiterter Funkverbindung.
US7551597B2 (en) 2004-05-06 2009-06-23 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for fast downlink information of uplink out-of-synchronization
CN101091332B (zh) * 2004-05-06 2014-11-26 艾利森电话股份有限公司 上行链路不同步的快速下行链路通知的方法和设备
BRPI0512333B1 (pt) * 2004-06-21 2018-08-28 2011 Intellectual Property Asset Trust método de recuperação para conexão de sinalização perdida em uma rede e equipamento de usuário para recuperação de conexão
US7701844B2 (en) 2005-02-09 2010-04-20 Interdigital Technology Corporation Method and apparatus for recognizing radio link failures associated with HSUPA and HSDPA channels
US8169953B2 (en) * 2005-05-17 2012-05-01 Qualcomm Incorporated Method and apparatus for wireless multi-carrier communications
CN102882589A (zh) * 2006-05-05 2013-01-16 北京新岸线移动通信技术有限公司 长期演进上行链路和下行链路中的无线电链路故障检测方法及其装置
US7864724B2 (en) * 2006-05-05 2011-01-04 Nokia Corporation Enhanced UE out-of-sync behavior with gated uplink DPCCH or gated downlink F-DPCH or DPCCH transmission
KR20080008801A (ko) * 2006-07-21 2008-01-24 삼성전자주식회사 패킷 전송 기반 통신 시스템에서 라디오 링크 상태를판단하는 방법 및 장치
TW201507390A (zh) * 2007-10-29 2015-02-16 Interdigital Patent Holdings Ｃｅｌｌ-ｆａｃｈ撞態中偵測增強專用頻道傳輸無線連結失敗方法
US20090116378A1 (en) * 2007-11-07 2009-05-07 Innovative Sonic Limited Method for handling radio link failure in wireless communications system and related apparatus
US8165026B2 (en) * 2008-03-25 2012-04-24 Qualcomm Incorporated Method and apparatus to report and manage cells in a multi carrier system
US8184599B2 (en) * 2008-06-23 2012-05-22 Qualcomm Incorporated Management of UE operation in a multi-carrier communication system
US8670376B2 (en) * 2008-08-12 2014-03-11 Qualcomm Incorporated Multi-carrier grant design
US20100074201A1 (en) * 2008-09-22 2010-03-25 Chih-Hsiang Wu Method for improving uplink signaling transmission for a wireless communications system and related communication device
AR073390A1 (es) * 2008-09-22 2010-11-03 Interdigital Patent Holdings Metodo y aparato para determinar falla en enlace radial lte en modo drx
US8948704B2 (en) * 2008-10-22 2015-02-03 Qualcomm Incorporated Scope of channel quality reporting region in a multi-carrier system
US20110217973A1 (en) * 2008-11-10 2011-09-08 Telefonaktiebolaget Lm Ericsson (Publ) Radio Link Monitoring in DRX
US9019902B2 (en) * 2008-11-11 2015-04-28 Qualcomm Incorporated Channel quality feedback in multicarrier systems
US9019903B2 (en) * 2008-12-08 2015-04-28 Qualcomm Incorporated Optimization to support uplink coordinated multi-point
SG173176A1 (en) * 2009-01-30 2011-08-29 Interdigital Patent Holdings Method and apparatus for performing physical dedicated channel establishment and monitoring procedures
AR076115A1 (es) * 2009-03-12 2011-05-18 Interdigital Patent Holdings Metodo y aparato para monitorear una falla de enlace radial
US8700029B2 (en) * 2009-03-22 2014-04-15 Htc Corporation Method of handling radio link failure detection in a wireless communication system and related communication device
US8599771B2 (en) * 2009-04-15 2013-12-03 Qualcomm Incorporated Control of radio links in a multiple carrier system
CN103687064B (zh) * 2009-04-22 2017-07-14 华为技术有限公司 无线链路失步的处理方法、装置和系统
KR101617048B1 (ko) * 2009-06-01 2016-05-02 엘지전자 주식회사 다중 반송파 시스템에서 요소 반송파의 실패를 처리하는 방법 및 장치
CN101998474B (zh) * 2009-08-13 2012-07-18 电信科学技术研究院 一种载波聚合技术中的无线链路失败判决方法及装置
US8488443B2 (en) * 2009-11-04 2013-07-16 Lg Electronics Inc. Method for handling radio line failure in multiple carrier system
SG183125A1 (en) * 2010-02-22 2012-09-27 Ericsson Telefon Ab L M Detection of radio link failure (rlf) for recovery

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3761750A1 (de) 2021-01-06
US8711709B2 (en) 2014-04-29
US10271232B2 (en) 2019-04-23
EP2407002A1 (de) 2012-01-18
CN104902569A (zh) 2015-09-09
US20140233396A1 (en) 2014-08-21
WO2010105148A1 (en) 2010-09-16
TWI502907B (zh) 2015-10-01
US20170048736A1 (en) 2017-02-16
TW201126932A (en) 2011-08-01
KR101605998B1 (ko) 2016-03-23
CN102396288B (zh) 2015-05-13
TWI497932B (zh) 2015-08-21
US9510386B2 (en) 2016-11-29
AR076115A1 (es) 2011-05-18
KR20150036818A (ko) 2015-04-07
KR101457754B1 (ko) 2014-11-03
TW201404057A (zh) 2014-01-16
HK1168234A1 (en) 2012-12-21
KR20110134475A (ko) 2011-12-14
US20110021154A1 (en) 2011-01-27
CN104902569B (zh) 2018-08-17
KR20130088174A (ko) 2013-08-07
CN102396288A (zh) 2012-03-28

Similar Documents

Publication Publication Date Title
US10271232B2 (en) Method and apparatus for monitoring for radio link failure
US11696198B2 (en) Method and device for performing handover in mobile communication system
JP6134750B2 (ja) マルチキャリアシステムにおけるコンポーネントキャリアのアクティブ化／非アクティブ化
JP6006384B2 (ja) アップリンク一次キャリアを選択し再選択する方法および機器
CA2751725C (en) Method and apparatus for performing physical dedicated channel establishment and monitoring procedures
CN114258161B (zh) 无线通信中用于小数据传送的新数据到达的方法和设备

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

17P Request for examination filed

Effective date: 20111011

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): 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 SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: INTERDIGITAL PATENT HOLDINGS, INC.

RIN1 Information on inventor provided before grant (corrected)

Inventor name: PELLETIER, GHYSLAIN

Inventor name: SOMASUNDARAM, SHANKAR

Inventor name: MARINIER, PAUL

Inventor name: WANG, PETER, S.

Inventor name: GAUVREAU, JEAN-LOUIS

Inventor name: RUDOLF, MARIAN

Inventor name: TERRY, STEPHEN, E.

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170504

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 5/06 20060101ALN20190328BHEP

Ipc: H04W 76/19 20180101ALI20190328BHEP

Ipc: H04W 24/08 20090101AFI20190328BHEP

INTG Intention to grant announced

Effective date: 20190412

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 24/08 20090101AFI20190404BHEP

Ipc: H04W 76/19 20180101ALI20190404BHEP

Ipc: H04L 5/06 20060101ALN20190404BHEP

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTC Intention to grant announced (deleted)
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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/19 20180101ALI20190902BHEP

Ipc: H04W 24/08 20090101AFI20190902BHEP

Ipc: H04L 5/06 20060101ALN20190902BHEP

INTG Intention to grant announced

Effective date: 20191007

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602010065153

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0076040000

Ipc: H04W0024080000

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

INTC Intention to grant announced (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 5/06 20060101ALN20200217BHEP

Ipc: H04W 76/19 20180101ALI20200217BHEP

Ipc: H04W 24/08 20090101AFI20200217BHEP

INTG Intention to grant announced

Effective date: 20200311

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

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): 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 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: DE

Ref legal event code: R096

Ref document number: 602010065153

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: AT

Ref legal event code: REF

Ref document number: 1302794

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200915

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: MG4D

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

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: 20200812

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: 20200812

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: 20200812

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: 20200812

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: 20200812

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: 20201112

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: 20201112

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: 20201113

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1302794

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200812

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

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: 20200812

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: 20200812

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: 20201212

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: 20200812

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: 20200812

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: 20200812

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: 20200812

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: 20200812

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010065153

Country of ref document: DE

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

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: 20200812

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

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

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: 20200812

26N No opposition filed

Effective date: 20210514

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: 20200812

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: 20200812

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: 20200812

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: 20210331

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

Ref country code: CH

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

Effective date: 20210331

Ref country code: LU

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

Effective date: 20210312

Ref country code: LI

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

Effective date: 20210331

Ref country code: IE

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

Effective date: 20210312

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: 20210331

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

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: 20201214

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

Ref country code: FR

Payment date: 20230323

Year of fee payment: 14

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

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: 20100312

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: 20200812

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

Ref country code: GB

Payment date: 20230321

Year of fee payment: 14

Ref country code: DE

Payment date: 20230328

Year of fee payment: 14

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230512

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

Ref country code: NL

Payment date: 20230323

Year of fee payment: 14

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

Ref country code: NL

Payment date: 20240326

Year of fee payment: 15