Systems and methods for handling physical random access channel collisions with carrier aggregation switching configurations
By validating PRACH occasions based on semi-static switching patterns and enabling additional switching under certain conditions, the system resolves collisions in carrier aggregation, ensuring efficient and reliable UL synchronization in wireless communication systems.
Patent Information
- Application Number
- PCT/CN2025/093781
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Wireless communication systems face collisions between semi-statically configured switching patterns for carrier aggregation and physical random access channel occasions, leading to conflicts in UL signaling and timing alignment, particularly in low band CA switching mechanisms.
Implementing a validity determination for PRACH occasions based on semi-static switching patterns, allowing PRACH occasions to be used only if they do not overlap with switching gaps or SCell slots, and enabling additional switching to resolve collisions when triggered by specific conditions or network behaviors.
Enhances the efficiency of PRACH operations by minimizing collisions and ensuring timely UL synchronization, thereby improving communication reliability and performance in carrier aggregation scenarios.
Smart Images

Figure CN2025093781_12112026_PF_FP_ABST
Abstract
Description
SYSTEMS AND METHODS FOR HANDLING PHYSICAL RANDOM ACCESS CHANNEL COLLISIONS WITH CARRIER AGGREGATION SWITCHING CONFIGURATIONSTECHNICAL FIELD
[0001] This application relates generally to wireless communication systems, including wireless communication systems implementing carrier aggregation (CA) switching.BACKGROUND
[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) , 3GPP New Radio (NR) (e.g., 5G) , and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as ) .
[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE) . 3GPP RANs can include, for example, Global System for Mobile communications (GSM) , Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and / or Next-Generation Radio Access Network (NG-RAN) .
[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE) , and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR) . In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.
[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) . One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
[0006] A RAN provides its communication services with external entities through its connection to a core network (CN) . For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC) .
[0007] Frequency bands for 5G NR may be separated into two or more different frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating in sub-6 gigahertz (GHz) frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 megahertz (MHz) to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or beyond) . Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0009] FIG. 1 illustrates a semi-static switching pattern and a RACH configuration.
[0010] FIG. 2 illustrates a method of a UE, according to embodiments discussed herein.
[0011] FIG. 3 illustrates a method of a UE, according to embodiments discussed herein.
[0012] FIG. 4 illustrates a method of a base station, according to embodiments discussed herein.
[0013] FIG. 5 illustrates a method of a base station, according to embodiments discussed herein.
[0014] FIG. 6 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
[0015] FIG. 7 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION
[0016] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
[0017] Various embodiments discussed herein relate to low band (LB) -LB switching. In some cases, a device may be configured to support switching between a primary cell (PCell) and a secondary cell (SCell) of a carrier aggregation (CA) configuration. When SCell operation is triggered, a UE switches to the SCell. During such operation, there is no simultaneous transmit (Tx) / receive (Rx) as between the PCell and the SCell. The device switches back to the PCell after the SCell operation is finished.
[0018] Corresponding to these cases, various aspects may be considered. A switching gap may be used, if needed. For example, a switching gap may be used in cases of UEs that need time to tune their hardware from away from first carrier and to a second carrier attendant to a carrier switch.
[0019] Further, physical layer procedures for switching between a first case in which there is both Tx and Rx on a frequency division duplex (FDD) carrier and no Rx on a supplementary downlink (SDL) carrier and a second case in which there is no Tx / Rx on the FDD carrier and Rx (only) on the SDL carrier may be used. In some such cases, semi-static switching pattern may be configured using radio resource control (RRC) configuration signaling.
[0020] Definitions for UE capabilities for these cases may be used.
[0021] Some wireless communication systems (e.g., Rel-19 NR systems) using a LB CA switching mechanism support the use of a semi-static configuration of a switching pattern at a UE (e.g., a UE-specific RRC configuration) . The configuration may indicate a switching pattern for the UE to use to switch between a first case in which there is both Tx and Rx on an FDD carrier of an active PCell and no Rx on an SDL carrier of an inactive SCell and a second case in which there is no Tx / Rx on the FDD carrier / the PCell (the PCell is inactive) and where there is Rx on the SDL carrier / the SCell (the SCell is active) . Some such cases correspond to the use of a 15 kHz subcarrier spacing (SCS) on both these carriers.
[0022] When considering aspects of RRC configuration of the semi-static switching pattern in LB CA switching mechanisms, it may not be permitted that a same slot (e.g., 1 millisecond (ms) slot) contains both symbol (s) configured for use by the FDD carrier and symbol (s) configured for use by the SDL carrier.
[0023] In some cases of LB CA switching using a semi-static switching pattern, the semi-static switching pattern (and any corresponding switching gap (s) ) are based on a downlink (DL) timing (aDL reception time at UE side) on the PCell.
[0024] In some cases for an RRC configuration of LB CA switching using a semi-static switching pattern, a time unit (resolution) of the semi-static switching pattern configuration is a slot (e.g., 1 ms for a 15 kHz SCS case) .
[0025] In some cases for an RRC configuration of LB CA switching using a semi-static switching pattern, a bitmap design may be used. The network configures a periodicity (denoted in / as slots) and a bitmap of P bits. Then, each bit in the bitmap indicates which carrier is configured for a corresponding slot. For example, a ‘0’ bit indicates that the FDD carrier is used on that slot and a ‘1’ bit indicates that the SDL carrier is used on that slot. In some such cases the pattern starts from the beginning of system frame number (SFN) 0 on the PCell. There may be a restriction for a maximum number of switch (es) X that is allowed within a number of slot (s) Y. Relational definitions for X and Y may be considered. Other restriction (s) may also be applied.
[0026] Aspects for switching gap locations in cases of LB CA switching using a semi-static switching pattern are now discussed. In some embodiments, it may be that when switching from the SDL carrier to the FDD carrier, the switching gap is assumed to be applied at the “switched-from” carrier (the SDL carrier) .
[0027] In some embodiments, it may be that when switching from the FDD carrier to the SDL carrier, one of the following alternatives may be applied. In a first alternative, the switching gap is assumed to be applied at the “switched-from” carrier (the FDD carrier) . In a second alternative, the network configures whether the switching gap is applied at the FDD carrier or at SDL carrier. In a third alternative, the switching gap may be assumed to be at the SDL carrier.
[0028] In some cases for an RRC configuration of LB CA switching using a semi-static switching pattern, the semi-static switching pattern may be periodic, with a periodicity of P slots. Some such cases support (up to) P = 40 ms (e.g., 40 slots) .
[0029] In some cases for an RRC configuration of LB CA switching using a semi-static switching pattern, one or more switching gap aspects may be considered. In some such cases, the duration of the switching gap is RRC configured by the network. In some cases, the switching gap duration may be different for an FDD carrier to SDL carrier switch versus an SDL carrier to FDD carrier switch. The network may ensure that the switching gap is enough to cover at least a switching period as may be defined (e.g., as 35 microseconds (μs) , 140 μs, etc. ) and / or any period to facilitate an uplink (UL) timing advance (TA) (if needed) . With respect to needs for an UL TA, it may be that a switching gap for an SDL carrier to FDD carrier switch ends at the end of the slot on the SDL carrier. (It may be assumed in a definition for the wireless communication system that a switching gap for an SDL carrier to FDD carrier switch includes a sufficient duration for UL TA) .
[0030] Embodiments discussed herein relate to collision handling between a semi-statically configured switching pattern for LB CA switching as configured at a UE and physical random access channel (PRACH) occasions (also) configured for use at the UE.
[0031] One example of such a collision is when a PRACH occasion is in a slot that the semi-static switching pattern indicates for use by an SDL carrier / the SCell. In such cases, there is a conflict between the notion that a random access channel (RACH) attempt on the PRACH occasion uses UL signaling, while the SDL carrier / the SCell operates only in the DL direction.
[0032] Another example of such a collision is when a PRACH occasion overlaps (in whole or in part) with a switching gap of the semi-static switching pattern. In such cases, there is a conflict between the notion that a random access channel (RACH) attempt on the PRACH occasion uses UL signaling to the network, while the switching gap represents a period in which the UE is not in active communication with the network.
[0033] Solutions with respect to how to handle such collisions are discussed herein. Such solutions are developed in view of the fact that the transmission of a RACH occasion according to a PRACH operation is only possible on the PCell / FDD band (and not on the SCell / SDL band) , and the fact that successful PRACH operation can correspond to various important use cases (e.g., cases of timing alignment between the UE and the network, cases of initial beam acquisition etc. ) .
[0034] Various embodiments discussed herein relate new UE and / or network behaviors for the handling of such collisions.
[0035] A first proposal for the resolution of collisions between a semi-statically configured switching pattern for LB CA switching configured at a UE and one or more PRACH occasions configured for use at the UE is now discussed. According to the first proposal, a validity of symbols for PRACH on a PCell / FDD carrier may be determined based on the semi-static switching pattern. A PRACH occasion is determined to be valid if the semi-static switching pattern indicates that the slot of the PRACH occasion is for operation in the PCell / FDD carrier and there is no overlap of the PRACH occasion with any switching gap that may be present in the slot of the PRACH occasion.
[0036] Otherwise, a PRACH occasion is determined to be invalid if the semi-static switching pattern indicates that the slot with the PRACH occasion is for operation in the SCell / SDL carrier, or if there is an overlap (in whole or in part) of the PRACH occasion with a switching gap used in the slot containing the PRACH occasion.
[0037] FIG. 1 illustrates a semi-static switching pattern 102 and a RACH configuration 104. The semi-static switching pattern 102 and the RACH configuration 104 may each be configured to the UE by the network.
[0038] As discussed herein, a “PCell” slot is a slot where a switching configuration indicates that a UE is to operate on a PCell, and an “SCell slot” is a slot where a switching configuration indicates that a UE is to operate on an SCell. As illustrated, the semi-static switching pattern 102 calls for the use of a first PCell slot 106, then a first SCell slot 108, then a second PCell slot 110, and then a second SCell slot 112. Note that the PCell uses an FDD carrier and supports both Tx and Rx, while the SCell uses an SDL carrier that supports only Rx.
[0039] The semi-static switching pattern 102 illustrates a case where switching gaps are used at “switched-from” slots. Accordingly, as illustrated, there is a first switching gap 114 at the end of the first PCell slot 106 corresponding to the switch from the first PCell slot 106 to the first SCell slot 108, a second switching gap 116 at the end of the first SCell slot 108 corresponding to the switch from the first SCell slot 108 to the second PCell slot 110, a third switching gap 118 at the end of the second PCell slot 110 corresponding to the switch from the second PCell slot 110 to the second SCell slot 112, and a fourth switching gap 120 at the end of the second SCell slot 112 corresponding to a switch from the second SCell slot 112 to another PCell slot (not illustrated) .
[0040] The RACH configuration 104 configures the UE with each of a first PRACH occasion 122, a second PRACH occasion 124, and a third PRACH occasion 126. The relative timing of these PRACH occasions with respect to the semi-static switching pattern 102 is illustrated.
[0041] As shown, the first PRACH occasion 122 overlaps with the portion of the first PCell slot 106 that includes the first switching gap 114. Because a performance of a RACH attempt in UL at the time of the second SCell slot 112 is not compatible with the use of the first switching gap 114, the first PRACH occasion 122 is understood to collide with (be in collision with) the semi-static switching pattern 102.
[0042] Further, as shown, the second PRACH occasion 124 is within the second PCell slot 110 and does not overlap with any part of the second PCell slot 110 that is used for a switching gap (e.g., does not overlap with the third switching gap 118) . The second PRACH occasion 124 does not collide with the semi-static switching pattern 102, because the second PCell slot 110 is capable of UL transmission to facilitate a RACH attempt on the second PRACH occasion 124, and because the second PRACH occasion 124 does not overlap with any switching gap of the semi-static switching pattern 102.
[0043] Further, as shown, the third PRACH occasion 126 is within the second SCell slot 112. Because a performance of a RACH attempt in UL is not compatible with UE operation on the second SCell slot 112 at the time of the third PRACH occasion 126 (because the SDL carrier of the second SCell slot 112 is DL only) , the third PRACH occasion 126 is understood to collide (be in collision with) with the semi-static switching pattern 102.
[0044] In some embodiments, the UE and the network understand that PRACH occasions that collide with a semi-static switching configuration will not be used by the UE to perform a RACH attempt (even though such PRACH occasions are otherwise configured-for per a RACH configuration) . Herein, PRACH occasions that collide with a semi-static switching pattern and that are therefore determined to be not eligible for use in performing a RACH attempt are considered invalid. Any RACH attempt that would otherwise be performed on such PRACH occasions is correspondingly dropped. The UE does not perform such RACH attempts, and the network does not expect the UE to perform such RACH attempts.
[0045] FIG. 1 corresponds to such a case. FIG. 1 illustrates that the first PRACH occasion 122 is invalid 128 due to its collision with the semi-static switching pattern 102, and further that the third PRACH occasion 126 is invalid 130 due to its collision with the semi-static switching pattern 102. Accordingly, any RACH attempt (s) that the UE would have otherwise performed using either the first PRACH occasion 122 or the third PRACH occasion 126 are dropped.
[0046] Various embodiments discussed herein relate to cases where a RACH attempt may nevertheless be performed on a PRACH occasion that is in a collision with a semi-static switching pattern as just discussed.
[0047] For example, in a second proposal, if a PRACH occasion that collides with a semi-static switching pattern is based on a physical downlink control channel (PDCCH) order received on the SCell / the SDL carrier, then the PRACH occasion is considered invalid (is not used for any RACH attempt) , in the manner just discussed.
[0048] However, if a PRACH occasion that collides with a semi-static switching pattern is based instead on any trigger on the PCell / the FDD carrier, then an additional switching (in addition to switching already called for by the semi-static switching pattern) can be triggered such that there is (due to the additional switching) a PCell slot having no overlapping switching gap at the time of the that PRACH occasion.
[0049] In some such cases, this additional switching may be performed (and thus the PRACH occasion may be used for a RACH attempt) provided that one or more conditions are met. A first of these condition (s) may be that a minimum duration (e.g., of N_gap slots) has passed since the last switch from the PCell to the SCell.
[0050] Another of these condition (s) may be that a maximum number of switching instances has not been exhausted in the last number Y of most recent slots.
[0051] Another of these condition (s) may be that the last number of PRACH occasion (s) N were invalidated because of collision with the switching pattern.
[0052] Another of these condition (s) may be that all prior PRACH occasion (s) within a number M of most recent slots were invalidated because of collision with the switching pattern.
[0053] As will be understood, a RACH attempt may be triggered for purposes of UL timing synchronization. Further, UL timing synchronization may be understood as a relatively important functionality in the wireless communication system. Accordingly, in some embodiments, one or more options that account of this context may be applied in for purposes of determining whether an additional switching (in addition to switching already called for by the semi-static switching pattern) can be triggered such that a PRACH occasion that otherwise collides with a semi-static switching pattern can nevertheless be used.
[0054] In a first such option, if a PRACH occasion that collides with the semi-static switching pattern would be used by RACH attempt that is triggered by a base station communication to the UE to perform contention free random access (CFRA) , then the additional switching may occur in order to enable the use of the PRACH occasion for the RACH attempt. This may be done out of recognition that base-station-triggered CFRA is often performed for UL timing synchronization purposes.
[0055] In a second such option, if a PRACH occasion that collides with the semi-static switching pattern is triggered as a result of a scheduling request (SR) from the UE, then the additional switching may occur in order to enable the use of the PRACH occasion for a RACH attempt. This may be done out of recognition that SR-triggered PRACH is often performed for UL timing synchronization purposes.
[0056] A fourth proposal relates to embodiments where one or more constraints are introduced on the configuration of a semi-static pattern. In some embodiments, such constraints manifest in the form of limitation (s) on the generation, at a base station, of switching pattern configuration information for the semi-static switching pattern.
[0057] One purpose of some such constraint-based cases is to prevent or minimize PRACH occasion collision with the semi-static switching pattern. Corresponding to such cases, it may be that switching pattern configuration information for the semi-static switching pattern is generated in view of / based on / taking into account a RACH configuration that is used at a UE.
[0058] For example, in some cases, a base station generates the switching pattern configuration information such that no SCell slot of the switching pattern overlaps any PRACH occasion of the RACH configuration.
[0059] Additionally or alternatively, a base station generates the switching pattern configuration information such that no slot range of a slot range length M within the switching pattern includes a number N of PRACH occasions of the RACH configuration that overlap any PCell slot of the switching pattern that exceeds a threshold value.
[0060] Additionally or alternatively, the base station generates the switching pattern configuration information such that no switching gap of the switching pattern overlaps any PRACH occasion of the RACH configuration.
[0061] Additionally or alternatively, the base station generates the switching pattern configuration information such that no slot range of a slot range length M within the switching pattern includes a number N of PRACH occasions of the RACH configuration that overlap any switching gap of the switching pattern that exceeds a threshold value.
[0062] A fifth proposal relates to cases where additional switching (in addition to switching already called for by the semi-static switching pattern) is triggered such that a PRACH occasion that otherwise collides with a semi-static switching pattern can nevertheless be used. In such cases, it may be that the use of the additional switching behavior does not change other aspects of the semi-static switching pattern / the switching pattern configuration (such aspects rather remain as before) . These aspects may include, but are not limited to, switching gap locations, switching gap durations, switching instance restrictions, and / or the fact that no Tx or Rx is performed during a switching gap.
[0063] A sixth proposal relates to UE capability signaling. A UE may report its capability / support of an additional switching functionality where a PRACH occasion that otherwise collides with a semi-static switching pattern can nevertheless be used (e.g., as is discussed herein) .
[0064] Various options are contemplated for the case that the UE does not provide such a capability report (and thus the network cannot be sure that the UE is using the additional switching functionality) . In a first option for such cases, it may be that the UE is not expected to be configured with a semi-static switching pattern that collides with configured PRACH occasions at the UE. In other words, the base station generates switching pattern configuration information for the semi-static switching pattern such that no SCell slot and / or switching gap of the switching pattern overlaps any PRACH occasion of the RACH configuration used by the UE.
[0065] In a second option, if a collision occurs between a PRACH occasion and the semi-static switching pattern, then it is assumed that the UE determines that PRACH occasion to be invalid and that it will not be used by the UE to perform a RACH attempt. Accordingly, the base station correspondingly determines that there is no RACH attempt forthcoming on any such PRACH occasions.
[0066] In alternative cases where a capability indication that the UE uses the additional switching behavior is provided, the base station instead understands that the UE may use a PRACH occasion that otherwise collides with the semi-static switching pattern. The determination by the base station may be based on understanding of the UE's manner of performing the additional switching functionality (e.g., according to one or more of the mechanisms for performing additional switching as discussed herein) .
[0067] FIG. 2 illustrates a method 200 of a UE, according to embodiments discussed herein. The method 200 includes receiving 202, from a base station, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier. The method 200 further includes identifying 204 that a first PRACH occasion is in a collision with the switching pattern. The method 200 further includes identifying 206 that the first PRACH occasion is invalid based on the collision. The method 200 further includes dropping 208 a first RACH attempt on the first PRACH occasion in response to the identifying that the first PRACH occasion is invalid.
[0068] In some embodiments of the method 200, the collision between the first PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the first PRACH occasion is an SCell slot.
[0069] In some embodiments of the method 200, the collision between the first PRACH occasion and the switching pattern comprises that the first PRACH occasion overlaps a switching gap of the switching pattern.
[0070] In some embodiments, the method 200 further includes identifying that a second PRACH occasion does not collide with the switching pattern; and performing a second RACH attempt during the second PRACH occasion in response to the identifying that the second PRACH occasion does not collide with the switching pattern.
[0071] In some embodiments of the method 200, the first PRACH occasion is based on a PDCCH order received on the SCell.
[0072] FIG. 3 illustrates a method 300 of a UE, according to embodiments discussed herein. The method 300 includes receiving 302, from a base station, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier. The method 300 further includes identifying 304 that a PRACH occasion is in a collision with the switching pattern. The method 300 further includes determining 306 that a condition for performing a RACH attempt on the PCell during the PRACH occasion despite the collision is met. The method 300 further includes performing 308 the RACH attempt during the PRACH occasion in response to the determining that the condition is met.
[0073] In some embodiments of the method 300, the collision between the PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the PRACH occasion is an SCell slot.
[0074] In some embodiments of the method 300, the collision between the PRACH occasion and the switching pattern comprises that the PRACH occasion overlaps a switching gap of the switching pattern.
[0075] In some embodiments of the method 300, the PRACH occasion is on the PCell, and the condition comprises that a minimum duration has passed since a last switch from the PCell to the SCell.
[0076] In some embodiments of the method 300, the PRACH occasion is on the PCell, and the condition comprises that a maximum number of switching instances for a number of most recent slots has not been reached.
[0077] In some embodiments of the method 300, the PRACH occasion is on the PCell, and the condition comprises that a number of most recent prior PRACH occasions were determined to be invalid.
[0078] In some embodiments of the method 300, the PRACH occasion is on the PCell, and the condition comprises that all prior PRACH occasions that are within a number of most recent prior slots were determined to be invalid.
[0079] In some embodiments of the method 300, the condition comprises that the RACH attempt is for a CFRA procedure triggered by the base station.
[0080] In some embodiments of the method 300, the condition comprises that the RACH attempt is triggered as a result of an SR sent from the UE to the base station.
[0081] In some embodiments, the method 300 further includes sending, to the base station, a capability indication indicating that the UE is capable of performing the RACH attempt on the PCell during the PRACH occasion despite the collision.
[0082] FIG. 4 illustrates a method 400 of a base station, according to embodiments discussed herein. The method 400 includes sending 402, to a UE, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier. The method 400 further includes identifying 404 that a PRACH occasion is in a collision with the switching pattern. The method 400 further includes determining 406 that a condition for performing a RACH attempt on the PCell during the PRACH occasion despite the collision is met. The method 400 further includes monitoring 408 for the RACH attempt during the PRACH occasion in response to the determining that the condition is met.
[0083] In some embodiments of the method 400, the collision between the PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the PRACH occasion is an SCell slot.
[0084] In some embodiments of the method 400, the collision between the PRACH occasion and the switching pattern comprises that the PRACH occasion overlaps a switching gap of the switching pattern.
[0085] In some embodiments of the method 400, the PRACH occasion is on the PCell, and the condition comprises that a minimum duration has passed since a last switch from the PCell to the SCell.
[0086] In some embodiments of the method 400, the PRACH occasion is on the PCell, and the condition comprises that a maximum number of switching instances for a number of most recent slots has not been reached.
[0087] In some embodiments of the method 400, the PRACH occasion is on the PCell, and the condition comprises that a number of most recent prior PRACH occasions were determined to be invalid.
[0088] In some embodiments of the method 400, the PRACH occasion is on the PCell, and the condition comprises that all prior PRACH occasions that are within a number of most recent prior slots were determined to be invalid.
[0089] In some embodiments of the method 400, the condition comprises that the RACH attempt is for a CFRA procedure triggered by the base station.
[0090] In some embodiments of the method 400, the condition comprises that the RACH attempt is triggered as a result of an SR sent from the UE to the base station.
[0091] In some embodiments, the method 400 further includes receiving, from the UE, a capability indication indicating that the UE is capable of performing the RACH attempt on the PCell during the PRACH occasion despite the collision, and wherein the monitoring for the RACH attempt during the PRACH occasion is further in response to receiving the capability indication.
[0092] FIG. 5 illustrates a method 500 of a base station, according to embodiments discussed herein. The method 500 includes generating 502, based on a RACH configuration used at a UE, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier. The method 500 further includes sending 504 the switching pattern configuration information for the switching pattern to the UE.
[0093] In some embodiments of the method 500, the base station generates the switching pattern configuration information such that no SCell slot of the switching pattern overlaps any PRACH occasion of the RACH configuration.
[0094] In some embodiments of the method 500, the base station generates the switching pattern configuration information such that no slot range of a slot range length within the switching pattern includes a number of PRACH occasions of the RACH configuration that overlap any PCell slot of the switching pattern that exceeds a threshold value.
[0095] In some embodiments of the method 500, the base station generates the switching pattern configuration information such that no switching gap of the switching pattern overlaps any PRACH occasion of the RACH configuration.
[0096] In some embodiments of the method 500, the base station generates the switching pattern configuration information such that no slot range of a slot range length within the switching pattern includes a number of PRACH occasions of the RACH configuration that overlap any switching gap of the switching pattern that exceeds a threshold value.
[0097] FIG. 6 illustrates an example architecture of a wireless communication system 600, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 600 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.
[0098] As shown by FIG. 6, the wireless communication system 600 includes UE 602 and UE 604 (although any number of UEs may be used) . In this example, the UE 602 and the UE 604 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device configured for wireless communication.
[0099] The UE 602 and UE 604 may be configured to communicatively couple with a RAN 606. In embodiments, the RAN 606 may be NG-RAN, E-UTRAN, etc. The UE 602 and UE 604 utilize connections (or channels) (shown as connection 608 and connection 610, respectively) with the RAN 606, each of which comprises a physical communications interface. The RAN 606 can include one or more base stations (such as base station 612 and base station 614) that enable the connection 608 and connection 610.
[0100] In this example, the connection 608 and connection 610 are air interfaces to enable such communicative coupling, and may be consistent with RAT (s) used by the RAN 606, such as, for example, an LTE and / or NR.
[0101] In some embodiments, the UE 602 and UE 604 may also directly exchange communication data via a sidelink interface 616. The UE 604 is shown to be configured to access an access point (shown as AP 618) via connection 620. By way of example, the connection 620 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 618 may comprise a router. In this example, the AP 618 may be connected to another network (for example, the Internet) without going through a CN 624.
[0102] In embodiments, the UE 602 and UE 604 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 612 and / or the base station 614 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0103] In some embodiments, all or parts of the base station 612 or base station 614 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 612 or base station 614 may be configured to communicate with one another via interface 622. In embodiments where the wireless communication system 600 is an LTE system (e.g., when the CN 624 is an EPC) , the interface 622 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 600 is an NR system (e.g., when CN 624 is a 5GC) , the interface 622 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 612 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 624) .
[0104] The RAN 606 is shown to be communicatively coupled to the CN 624. The CN 624 may comprise one or more network elements 626, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 602 and UE 604) who are connected to the CN 624 via the RAN 606. The components of the CN 624 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0105] In embodiments, the CN 624 may be an EPC, and the RAN 606 may be connected with the CN 624 via an S1 interface 628. In embodiments, the S1 interface 628 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 612 or base station 614 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 612 or base station 614 and mobility management entities (MMEs) .
[0106] In embodiments, the CN 624 may be a 5GC, and the RAN 606 may be connected with the CN 624 via an NG interface 628. In embodiments, the NG interface 628 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 612 or base station 614 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 612 or base station 614 and access and mobility management functions (AMFs) .
[0107] Generally, an application server 630 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 624 (e.g., packet switched data services) . The application server 630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 602 and UE 604 via the CN 624. The application server 630 may communicate with the CN 624 through an IP communications interface 632.
[0108] FIG. 7 illustrates a system 700 for performing signaling 734 between a wireless device 702 and a network device 718, according to embodiments disclosed herein. The system 700 may be a portion of a wireless communications system as herein described. The wireless device 702 may be, for example, a UE of a wireless communication system. The network device 718 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.
[0109] The wireless device 702 may include one or more processor (s) 704. The processor (s) 704 may execute instructions such that various operations of the wireless device 702 are performed, as described herein. The processor (s) 704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0110] The wireless device 702 may include a memory 706. The memory 706 may be a non-transitory computer-readable storage medium that stores instructions 708 (which may include, for example, the instructions being executed by the processor (s) 704) . The instructions 708 may also be referred to as program code or a computer program. The memory 706 may also store data used by, and results computed by, the processor (s) 704.
[0111] The wireless device 702 may include one or more transceiver (s) 710 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna (s) 712 of the wireless device 702 to facilitate signaling (e.g., the signaling 734) to and / or from the wireless device 702 with other devices (e.g., the network device 718) according to corresponding RATs.
[0112] The wireless device 702 may include one or more antenna (s) 712 (e.g., one, two, four, or more) . For embodiments with multiple antenna (s) 712, the wireless device 702 may leverage the spatial diversity of such multiple antenna (s) 712 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) . MIMO transmissions by the wireless device 702 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 702 that multiplexes the data streams across the antenna (s) 712 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) . Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
[0113] In certain embodiments having multiple antennas, the wireless device 702 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 712 are relatively adjusted such that the (joint) transmission of the antenna (s) 712 can be directed (this is sometimes referred to as beam steering) .
[0114] The wireless device 702 may include one or more interface (s) 714. The interface (s) 714 may be used to provide input to or output from the wireless device 702. For example, a wireless device 702 that is a UE may include interface (s) 714 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 710 / antenna (s) 712 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
[0115] The wireless device 702 may include a switching pattern module 716. The switching pattern module 716 may be implemented via hardware, software, or combinations thereof. For example, the switching pattern module 716 may be implemented as a processor, circuit, and / or instructions 708 stored in the memory 706 and executed by the processor (s) 704. In some examples, the switching pattern module 716 may be integrated within the processor (s) 704 and / or the transceiver (s) 710. For example, the switching pattern module 716 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 704 or the transceiver (s) 710.
[0116] The switching pattern module 716 may be used for various aspects of the present disclosure, for example, aspects of FIG. 2 and / or FIG. 3. For example, the switching pattern module 716 may configure the wireless device 702 to receive, from a base station, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier; identify that a first PRACH occasion is in a collision with the switching pattern; identify that the first PRACH occasion is invalid based on the collision; and drop a first RACH attempt on the first PRACH occasion in response to the identifying that the first PRACH occasion is invalid.
[0117] As another example, the switching pattern module 716 may configure the wireless device 702 to receive, from a base station, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier; identify that a PRACH occasion is in a collision with the switching pattern; determine that a condition for performing a RACH attempt on the PCell during the PRACH occasion despite the collision is met; and perform the RACH attempt during the PRACH occasion in response to the determining that the condition is met.
[0118] The network device 718 may include one or more processor (s) 720. The processor (s) 720 may execute instructions such that various operations of the network device 718 are performed, as described herein. The processor (s) 720 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0119] The network device 718 may include a memory 722. The memory 722 may be a non-transitory computer-readable storage medium that stores instructions 724 (which may include, for example, the instructions being executed by the processor (s) 720) . The instructions 724 may also be referred to as program code or a computer program. The memory 722 may also store data used by, and results computed by, the processor (s) 720.
[0120] The network device 718 may include one or more transceiver (s) 726 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna (s) 728 of the network device 718 to facilitate signaling (e.g., the signaling 734) to and / or from the network device 718 with other devices (e.g., the wireless device 702) according to corresponding RATs.
[0121] The network device 718 may include one or more antenna (s) 728 (e.g., one, two, four, or more) . In embodiments having multiple antenna (s) 728, the network device 718 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
[0122] The network device 718 may include one or more interface (s) 730. The interface (s) 730 may be used to provide input to or output from the network device 718. For example, a network device 718 that is a base station may include interface (s) 730 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 726 / antenna (s) 728 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
[0123] The network device 718 may include a switching pattern module 732. The switching pattern module 732 may be implemented via hardware, software, or combinations thereof. For example, the switching pattern module 732 may be implemented as a processor, circuit, and / or instructions 724 stored in the memory 722 and executed by the processor (s) 720. In some examples, the switching pattern module 732 may be integrated within the processor (s) 720 and / or the transceiver (s) 726. For example, the switching pattern module 732 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 720 or the transceiver (s) 726.
[0124] The switching pattern module 732 may be used for various aspects of the present disclosure, for example, aspects of FIG. 3 and / or FIG. 4. For example, the switching pattern module 732 may configure the network device 718 to send, to a UE, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier; identify that a PRACH occasion is in a collision with the switching pattern; determine that a condition for performing a RACH attempt on the PCell during the PRACH occasion despite the collision is met; and monitor for the RACH attempt during the PRACH occasion in response to the determining that the condition is met.
[0125] As another example, the switching pattern module 732 may configure the network device 718 to generate, based on a RACH configuration used at a UE, switching pattern configuration information for a switching pattern between a PCell on an FDD carrier and an SCell on an SDL carrier; and send the switching pattern configuration information for the switching pattern to the UE.
[0126] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 200 and / or the method 300. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE, as described herein) .
[0127] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the method 200 and / or the method 300. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) .
[0128] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 200 and / or the method 300. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE, as described herein) .
[0129] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 200 and / or the method 300 This apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE, as described herein) .
[0130] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 200 and / or the method 300.
[0131] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of any of the method 200 and / or the method 300. The processor may be a processor of a UE (such as a processor (s) 704 of a wireless device 702 that is a UE, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) .
[0132] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the method 400 and / or the method 500. This apparatus may be, for example, an apparatus of a base station (such as a network device 718 that is a base station, as described herein) .
[0133] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the method 400 and / or the method 500. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory 722 of a network device 718 that is a base station, as described herein) .
[0134] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the method 400 and / or the method 500. This apparatus may be, for example, an apparatus of a base station (such as a network device 718 that is a base station, as described herein) .
[0135] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the method 400 and / or the method 500. This apparatus may be, for example, an apparatus of a base station (such as a network device 718 that is a base station, as described herein) .
[0136] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the method 400 and / or the method 500.
[0137] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the method 400 and / or the method 500. The processor may be a processor of a base station (such as a processor (s) 720 of a network device 718 that is a base station, as described herein) . These instructions may be, for example, located in the processor and / or on a memory of the base station (such as a memory 722 of a network device 718 that is a base station, as described herein) .
[0138] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
[0139] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0140] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) . The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.
[0141] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.
[0142] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0143] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1.A method of a user equipment (UE) , comprising:receiving, from a base station, switching pattern configuration information for a switching pattern between a primary cell (PCell) on a frequency division duplex (FDD) carrier and a secondary cell (SCell) on a supplementary downlink (SDL) carrier;identifying that a first physical random access channel (PRACH) occasion is in a collision with the switching pattern;identifying that the first PRACH occasion is invalid based on the collision; anddropping a first random access channel (RACH) attempt on the first PRACH occasion in response to the identifying that the first PRACH occasion is invalid.2.The method of claim 1, wherein the collision between the first PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the first PRACH occasion is an SCell slot.3.The method of claim 1, wherein the collision between the first PRACH occasion and the switching pattern comprises that the first PRACH occasion overlaps a switching gap of the switching pattern.4.The method of claim 1, further comprising:identifying that a second PRACH occasion does not collide with the switching pattern; andperforming a second RACH attempt during the second PRACH occasion in response to the identifying that the second PRACH occasion does not collide with the switching pattern.5.The method of claim 1, wherein the first PRACH occasion is based on a physical downlink control channel (PDCCH) order received on the SCell.6.A method of a user equipment (UE) , comprising:receiving, from a base station, switching pattern configuration information for a switching pattern between a primary cell (PCell) on a frequency division duplex (FDD) carrier and a secondary cell (SCell) on a supplementary downlink (SDL) carrier;identifying that a physical random access channel (PRACH) occasion is in a collision with the switching pattern;determining that a condition for performing a random access channel (RACH) attempt on the PCell during the PRACH occasion despite the collision is met; andperforming the RACH attempt during the PRACH occasion in response to the determining that the condition is met.7.The method of claim 6, wherein the collision between the PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the PRACH occasion is an SCell slot.8.The method of claim 6, wherein the collision between the PRACH occasion and the switching pattern comprises that the PRACH occasion overlaps a switching gap of the switching pattern.9.The method of claim 6, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a minimum duration has passed since a last switch from the PCell to the SCell.10.The method of claim 6, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a maximum number of switching instances for a number of most recent slots has not been reached.11.The method of claim 6, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a number of most recent prior PRACH occasions were determined to be invalid.12.The method of claim 6, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that all prior PRACH occasions that are within a number of most recent prior slots were determined to be invalid.13.The method of claim 6, wherein the condition comprises that the RACH attempt is for a contention free random access (CFRA) procedure triggered by the base station.14.The method of claim 6, wherein the condition comprises that the RACH attempt is triggered as a result of a scheduling request (SR) sent from the UE to the base station.15.The method of claim 6, further comprising sending, to the base station, a capability indication indicating that the UE is capable of performing the RACH attempt on the PCell during the PRACH occasion despite the collision.16.A method of a base station, comprising:sending, to a user equipment (UE) , switching pattern configuration information for a switching pattern between a primary cell (PCell) on a frequency division duplex (FDD) carrier and a secondary cell (SCell) on a supplementary downlink (SDL) carrier;identifying that a physical random access channel (PRACH) occasion is in a collision with the switching pattern;determining that a condition for performing a random access channel (RACH) attempt on the PCell during the PRACH occasion despite the collision is met; andmonitoring for the RACH attempt during the PRACH occasion in response to the determining that the condition is met.17.The method of claim 16, wherein the collision between the PRACH occasion and the switching pattern comprises that the switching pattern indicates that a slot of the PRACH occasion is an SCell slot.18.The method of claim 16, wherein the collision between the PRACH occasion and the switching pattern comprises that the PRACH occasion overlaps a switching gap of the switching pattern.19.The method of claim 16, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a minimum duration has passed since a last switch from the PCell to the SCell.20.The method of claim 16, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a maximum number of switching instances for a number of most recent slots has not been reached.21.The method of claim 16, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that a number of most recent prior PRACH occasions were determined to be invalid.22.The method of claim 16, wherein the PRACH occasion is on the PCell, and wherein the condition comprises that all prior PRACH occasions that are within a number of most recent prior slots were determined to be invalid.23.The method of claim 16, wherein the condition comprises that the RACH attempt is for a contention free random access (CFRA) procedure triggered by the base station.24.The method of claim 16, wherein the condition comprises that the RACH attempt is triggered as a result of a scheduling request (SR) sent from the UE to the base station.25.The method of claim 16, further comprising receiving, from the UE, a capability indication indicating that the UE is capable of performing the RACH attempt on the PCell during the PRACH occasion despite the collision, and wherein the monitoring for the RACH attempt during the PRACH occasion is further in response to receiving the capability indication.26.A method of a base station, comprising:generating, based on a random access channel (RACH) configuration used at a user equipment (UE) , switching pattern configuration information for a switching pattern between a primary cell (PCell) on a frequency division duplex (FDD) carrier and a secondary cell (SCell) on a supplementary downlink (SDL) carrier; andsending the switching pattern configuration information for the switching pattern to the UE.27.The method of claim 26, wherein the base station generates the switching pattern configuration information such that no SCell slot of the switching pattern overlaps any physical random access channel (PRACH) occasion of the RACH configuration.28.The method of claim 26, wherein the base station generates the switching pattern configuration information such that no slot range of a slot range length within the switching pattern includes a number of physical random access channel (PRACH) occasions of the RACH configuration that overlap any PCell slot of the switching pattern that exceeds a threshold value.29.The method of claim 26, wherein the base station generates the switching pattern configuration information such that no switching gap of the switching pattern overlaps any physical random access channel (PRACH) occasion of the RACH configuration.30.The method of claim 26, wherein the base station generates the switching pattern configuration information such that no slot range of a slot range length within the switching pattern includes a number of physical random access channel (PRACH) occasions of the RACH configuration that overlap any switching gap of the switching pattern that exceeds a threshold value.31.An apparatus comprising means to perform the method of any of claim 1 to claim 30.32.A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 30.33.An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 30.34.A baseband processor for a user equipment (UE) that is configured to cause the UE to perform one or more elements of any one of claim 1 to claim 15.35.A baseband processor for a base station that is configured to cause the base station to perform one or more elements of any one of claim 16 to claim 30.
