Systems and methods for beam representation of L1 / L2 center cell-to-cell mobility

Abstract

Systems and methods for beam indications for Layer 1 / Layer 2 (L1 / L2) centered cell-to-cell mobility are described herein. A base station may provide beam indications to a user equipment (UE) in one or more transmit configuration indication (TCI) states and may provide different beam indications for different search spaces (SS), including a UE-specific search space (USS) and a common search space (CSS), within the same control channel resource set (CORESET). The UE may implicitly select a radio link monitoring (RLM) and beam failure detection (BFD) reference signal (RS) according to one or more methods, and in some cases, may implicitly select an RLM / BFD RS based on one or more received TCI states or beam indications.

Description

Technology Field

[0001] The present application generally relates to wireless communication systems comprising methods and implementations of beam representation for layer 1 / layer 2 (L1 / L2) center cell-to-cell mobility. Background Technology

[0002] Wireless mobile communication technology transmits data between base stations and wireless communication devices using various standards and protocols. Wireless communication system standards and protocols include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs) (generally, Wi-Fi ® It may include (known to industry groups as).

[0003] As considered by 3GPP, different radio communication system standards and protocols may use various RANs to communicate between a base station of a radio access network (RAN) (which may also, sometimes, generally be referred to as a RAN node, network node, or simply node) and a radio communication device known as user equipment (UE). 3GPP RANs may include, for example, GSM (global system for mobile communications), GERAN (enhanced data rates for GSM evolution (EDGE) RAN), UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved Universal Terrestrial Radio Access Network), and / or NG-RAN (Next-Generation Radio Access Network).

[0004] Each RAN can perform communication between a base station and a UE using one or more radio access technologies (RATs). For example, a GERAN implements GSM and / or EDGE RATs, a UTRAN implements UMTS (universal mobile telecommunication system) RATs or other 3GPP RATs, an E-UTRAN implements LTE RATs (sometimes referred to simply as LTE), and an NG-RAN implements NR RATs (sometimes referred to herein as 5G RATs, 5G NR RATs, or simply NR). In certain deployments, an E-UTRAN may also implement NR RATs. In certain deployments, an NG-RAN may also implement LTE RATs.

[0005] Base stations used by a RAN can correspond to that RAN. One example of an E-UTRAN base station is an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as g Node B or gNB).

[0006] A RAN provides its communication services to external entities through its connection to a core network (CN). For example, E-UTRAN can use the Evolved Packet Core (EPC), whereas NG-RAN can use the 5G Core Network (5GC). Brief explanation of the drawing

[0007] To facilitate the identification of discussions regarding any specific element or action, the top digits or numbers within a drawing number refer to the drawing number in which the element was first introduced. FIG. 1 illustrates a scenario (Scenario 1) in which a UE enters the coverage area for cell 1, acquires cell 1 as its own serving cell, and then approaches or enters the coverage area of ​​a neighboring cell (i.e., cell 2). FIG. 2 illustrates a scenario (Scenario 2) in which a UE enters the coverage area for cell 1, acquires cell 1 as its own serving cell, and then approaches or enters the coverage area of ​​a neighboring cell (i.e., cell 2). FIG. 3 illustrates an exemplary method of a UE, which can be used to optionally apply a TCI state to a set of one or more common search spaces (CSS) associated with a set of control channel resources (CORESET) where a transmit configuration indication (TCI) state is provided. FIG. 4 illustrates an exemplary method of a base station, which can be used to optionally indicate at least one CSS and a corresponding physical downlink shared channel (PDSCH) to which a TCI state transmitted by the base station should be applied. FIG. 5 illustrates an exemplary method of UE, which can be used to selectively apply TCI status only to some search spaces (SS) associated with a CORESET where TCI status is provided. FIG. 6 illustrates an exemplary method of a base station, which can be used to optionally indicate a set of one or more partial CSSs to which a TCI state associated with CORESET should be applied. FIG. 7 illustrates an exemplary timeline of beam indications for CORESET 0 and SSs associated with CORESET 0 as transmitted by a base station and received by a UE. FIG. 8 illustrates an exemplary architecture of a wireless communication system according to embodiments disclosed in this specification. FIG. 9 illustrates a system for performing signaling between a wireless device and a network device according to embodiments disclosed in this specification. Specific details for implementing the invention

[0008] Various embodiments are described with respect to the UE. However, references to the UE are provided only for exemplary purposes. The exemplary embodiments may be used with any electronic component capable of establishing a connection to a network and consist of hardware, software, and / or firmware to exchange information and data with the network. Accordingly, the UE as described herein is used to represent any suitable electronic device.

[0009] In 3GPP Release 17 (Rel-17), an integrated TCI framework is being introduced. According to such an integrated TCI framework, a base station (e.g., gNB) can present a TCI status to a UE that provides antenna port quasi-co-location (QCL) indications (e.g., beam indications) for dedicated Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) / Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmissions. To support L1 / L2 center cell-to-cell mobility, the source reference signal for the TCI status may be a reference signal (RS, e.g., Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS)) transmitted by the UE's serving cell or neighboring cell.

[0010] Two different scenarios regarding L1 / L2 central cell-to-cell mobility between a serving cell and a neighboring cell are illustrated in FIGS. 1 and FIGS. 2. FIGS. 1 illustrates a scenario (100) (Scenario 1) in which a UE (102) enters the coverage area (104) for cell 1 (represented by base station (106)), acquires cell 1 as its serving cell, and then approaches or enters the coverage area (108) of a neighboring cell (e.g., cell 2 represented by base station (110)). The coverage area (108) of cell 2 may partially or wholly overlap with the coverage area (104) of cell 1, but is illustrated as completely overlapping with the coverage area (104) of cell 1 as an example. Assuming that the UE (102) still receives acceptable quality of service (QoS) from cell 1 but can also receive acceptable QoS from cell 2, the UE (102) may keep cell 1 as its serving cell, similar to a multiple-transmission point (multi-TRP) operation, but receive some transmissions (e.g., dedicated information transmissions) from cell 2.

[0011] FIG. 2 illustrates a scenario (Scenario 2) in which a UE (202) enters the coverage area (204) for cell 1 (represented by base station (206)), acquires cell 1 as its serving cell, and then approaches or enters the coverage area (208) of a neighboring cell (e.g., cell 2 represented by base station (210). The coverage area (208) of cell 2 may partially or wholly overlap with the coverage area (204) of cell 1, but is illustrated as partially overlapping with the coverage area (204) of cell 1 as an example. In Scenario 2, a handover from cell 1 to cell 2 may be initiated, possibly because the UE (202) can receive better QoS from cell 2 than from cell 1.

[0012] In each of Scenario 1 and Scenario 2, the UE can identify the PDCCH based on the configuration of the CORESET and SS. The SSs may include a CSS and a UE-specific search space (USS; i.e., an SS dedicated to a specific UE). Each SS may be linked to a CORESET, and different SSs may be linked to the same CORESET (i.e., a set of one or more SSs may be linked to the same CORESET). The TCI status introduced in 3GPP Rel-17 is provided to the UE at the CORESET level for a dedicated PDCCH / PDSCH / PUCCH / PUSCH. There are no provisions regarding how the TCI status can be applied to the CSS or whether the TCI status can be applied to the CSS, and the CSS may be received from Cell 1 or Cell 2 in Scenarios 1 and 2.

[0013] As defined in s10.1 of 3GPP TS 38.213, various types of SSs exist. The Type0-PDCCH CSS set is configured by pdcch-ConfigSIB1 within the Master Information Block (MIB), or by searchSpaceSIB1 within PDCCH-ConfigCommon, or by searchSpaceZero within PDCCH-ConfigCommon, for the Downlink Control Information (DCI) format for the Cyclic Redundancy Check (CRC) scrambled by the System Information Radio Network Temporary Identifier (SI-RNTI) on the primary cell of the Master Cell Group (MCG). The Type0A-PDCCH CSS set is configured by searchSpaceOtherSystemInformation within PDCCH-ConfigCommon for the DCI format for the CRC scrambled by the SI-RNTI on the primary cell of the MCG. The Type 1-PDCCH CSS set is configured by the ra-SearchSpace within PDCCH-ConfigCommon for the DCI format for CRCs scrambled by Random Access RNTI (RA-RNTI), MsgB-RNTI, or Temporal Cell RNTI (TC-RNTI) on the primary cell of the MCG. The Type 2-PDCCH CSS set is configured by the pagingSearchSpace within PDCCH-ConfigCommon for the DCI format for CRCs scrambled by Paging RNTI (P-RNTI) on the primary cell of the MCG.Type3-PDCCH CSS is configured by SearchSpace within PDCCH-Config having searchSpaceType = common for DCI formats for CRC scrambled by the interruption RNTI (I-RNTI), slot format indication RNTI (SFI-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), TPC-PUCCH-RNTI, TPC sounding reference symbol RNTI (TPC-SRS-RNTI), or cancellation indication RNTI (CI-RNTI), and only for the primary cell of the MCG, cell RNTI (C-RNTI), modulation coding scheme cell RNTI (MCS-C-RNTI), configuration scheduling RNTI(s) (CS-RNTI(s)), or power saving RNTI (PS-RNTI). The USS set is configured by a SearchSpace within a PDCCH-Config having searchSpaceType = ue-Specific for DCI formats for CRCs scrambled by C-RNTI, MCS-C-RNTI, semi-permanent CSI RNTI (SP-CSI-RNTI), CS-RNTI(s), sidelink RNTI (SL-RNTI), sidelink configuration scheduling RNTI (SL-CS-RNTI), or SL semi-permanent scheduling V2X RNTI (SL semi-permanent scheduling V-RNTI).

[0014] FIG. 3 illustrates an exemplary method (300) of a UE, the method (300) may be used to optionally apply a TCI state to a set of one or more CSSs associated with a CORESET where a TCI state is provided.

[0015] In block (302), the method (300) may include the step of identifying, for CORESET, a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station (e.g., gNB or other type of base station) should be applied.

[0016] In block (304), the method (300) may include the step of receiving a TCI state along with a source reference signal (e.g., SSB or CSI-RS) transmitted by a base station. The operation(s) in block (304) may occur before or after the operation(s) in block (302).

[0017] In block (306), the method (300) may include the step of applying a TCI to at least one of a dedicated PDCCH, PDSCH, PUCCH, and / or PUSCH (e.g., a dedicated PDSCH within a USS), and / or at least one CSS and a corresponding PDSCH within an identified set of one or more CSSs and corresponding PDSCHs.

[0018] The remaining blocks of the method (300) are optional and will be described later in this description.

[0019] In some embodiments of the method (300), the step of identifying a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied may include: receiving an indication of at least one CSS within the set of one or more associated CSSs to which a TCI state is to be applied via radio resource control (RRC) signaling; and at least partially identifying, from the received indication, a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied. In some cases, the received indication may be configured per bandwidth portion (BWP), per serving cell, per serving cell group, or per UE. In some cases, the received indication may be configured per TCI state. In some cases, the indication for at least one CSS may be an indication that a TCI state (or TCI states) is to be applied to all CSSs.

[0020] In some embodiments of the method (300), the step of identifying a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied may include: receiving a mark of at least one CSS within a set of one or more associated CSSs to which a TCI is to be applied in a Media Access Control (MAC) control element (MAC CE); and at least partially identifying, from the received mark, a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied. In some cases, the mark may be applied to all TCI states identified in the MAC CE. That is, the mark may indicate at least one CSS to which all TCI states identified in the MAC CE are to be applied. In some cases, the MAC CE must include a mark for each TCI state. For example, a first mark may indicate at least one first CSS to which a first TCI state identified in the MAC CE is to be applied, and a second mark may indicate at least one second CSS to which a second TCI state identified in the MAC CE is to be applied. In some cases, an indication for at least one CSS may be an indication that a TCI state (or TCI states) should be applied to all CSS.

[0021] In some embodiments of the method (300), the step of identifying a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied may include: receiving a representation of at least one CSS within a set of one or more associated CSSs to which a TCI state is to be applied in a DCI used for TCI representation (e.g., DCI format 0_1 ​​or 0_2); and at least partially identifying, from the received representation, a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state received from a base station is to be applied. In some cases, the received representation may be received in a first field or a first bit distinct from a second field or a second bit representing a TCI state.

[0022] In each of the above embodiments, the received indication may be a 1-bit indicator indicating whether the TCI state (or TCI states) should generally be applied to CSS (e.g., all CSS) or to a predefined set of CSS. In these cases, the step of identifying a set of one or more associated CSS and corresponding PDSCHs to which the TCI state received from the base station should be applied may include the step of analyzing the 1-bit indicator. Alternatively, the received indication may be an N-bit indicator (e.g., a bitmap), where N is greater than 1. In these cases, the step of identifying a set of one or more associated CSS and corresponding PDSCHs to which the TCI state received from the base station should be applied may include the step of analyzing the N-bit indicator. Other bits or combinations of bits may provide indications of whether the TCI state (or TCI states) should be applied to different CSSs.

[0023] In some embodiments of the method (300), the step of identifying one or more associated CSS and corresponding PDSCH sets to which a TCI state received from a base station is to be applied may include the step of determining to apply the TCI state to at least one predetermined CSS. In some cases, at least one predetermined CSS may include at least a set of Type 3-PDCCH CSSs, because such CSSs are not broadcast and are therefore similar to a dedicated SS (or USS).

[0024] As described with reference to FIG. 3, the UE can identify one or more CSSs and a set of associated PDSCHs associated with a CORESET. In some cases, the set of one or more CSSs may include all CSSs associated with the CORESET. In some cases, the set of one or more CSSs may include only some of the CSSs associated with the CORESET, and one or more other CSSs associated with the CORESET may exist. The TCI state may not apply to these other CSSs. In these cases, the base station may associate an SSB with each of these CSSs and repeatedly transmit downlink signals at each monitoring opportunity for the CSS. The UE may select one or more monitoring opportunities to receive downlink signals and may receive downlink signals based on the SSB. In Scenario 1, the SSB and downlink signals may be transmitted from the UE's current serving cell (e.g., Cell 1 in FIG. 1). In Scenario 2, the SSB and downlink signals must be transmitted by the serving cell associated with the TCI state received in block (306). The association between SSB and CSS for both cells must be provided by upper-level signaling (e.g., RRC signaling). Alternatively, association rules may be common to both cells (e.g., time and frequency offsets between CSS instances and SSBs may be common to both cells, and the UE can identify the corresponding CSS based on the SSB pattern for each cell).

[0025] In the cases identified in the preceding paragraph, and in block (308), the method (300) of the UE may further and optionally include the step of identifying a CSS to which no received TCI state applies. In block (310), the method (300) may include the step of selecting a monitoring opportunity to receive downlink signals for the CSS. In block (312), the method (300) may include the step of monitoring a monitoring opportunity for downlink signals. In block (314), the method (300) may include the step of receiving at least one SSB while monitoring a monitoring opportunity for downlink signals (and in some cases, block (314) may include receiving downlink signals such as DCI, PDCCH, etc.).

[0026] Whether the UE's serving cell needs to be changed after receiving a TCI status can be configured by upper-layer signaling (e.g., RRC signaling, MAC CE signaling, or DCI). In one example, an indicator may be provided along with the TCI indication signaling to indicate whether the UE's serving cell needs to be changed.

[0027] The TCI state introduced in 3GPP Rel-17 is a single TCI state. Embodiments in which two TCI states can be received by a UE are described herein. In Scenario 1 described with reference to FIG. 1, the UE can receive PDCCH and PDSCH from both the serving cell and the neighboring cell. However, some UEs may be limited to single-beam communication capabilities (i.e., communication by one beam at a time) and may support only a single active TCI state. In these cases, the UE can time-multiplex communications with Cell 1 and Cell 2 (e.g., in different time windows).

[0028] When the UE is limited to single-beam communication capability, and in the first set of embodiments, the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received in block (304) is to be applied includes a Type 1-PDCCH CSS set, a Type 2-PDCCH CSS set, and a Type 3-PDCCH CSS set. The TCI state may also be applied to USS and the corresponding PDSCH. In these embodiments, the method (300) may further include the step of suppressing the decoding of a System Information Block (SIB) after an RRC connection unless indicated by the base station to decode it. When the UE receives an indication from the base station to decode the SIB, the method may further include the step of suppressing the decoding of other signals within a time window. The duration of the time window may be reported by the UE capability or alternatively configured by upper layer signaling (e.g., RRC signaling or MAC CE).

[0029] When the UE is limited to single-beam communication capability, and in the second set of embodiments, the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received in block (304) is to be applied comprises only the Type 2-PDCCH CSS set and the Type 3-PDCCH CSS set. The TCI state may also be applied to the USS and the corresponding PDSCH. In these embodiments, the method (300) may further include the steps of transmitting a physical random access channel (PRACH) for random access (e.g., for contention-based random access (CBRA) and / or contention-free random access (CFRA)), and, after transmitting PRACH, resetting the beams applied to all channels across all component carriers (CC) within a band or band group based on the SSB associated with PRACH.

[0030] When the UE is limited to single-beam communication capability, and in the third set of embodiments, the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received in block (304) must be applied includes only the Type 1-PDCCH CSS set and the Type 3-PDCCH CSS set. The TCI state may also be applied to the USS and the corresponding PDSCH. In these embodiments, the method (300) may further include the steps of selecting a monitoring opportunity to decode paging information for paging reception, and dropping signals transmitted to the PDCCH / PDSCH for paging within a time window.

[0031] When the UE is limited to single-beam communication capability, and in the fourth set of embodiments, the set of one or more associated CSSs and corresponding PDSCHs to which the TCI status received in block (304) must be applied includes only the Type3-PDCCH CSS set. The TCI status may also be applied to the USS and the corresponding PDSCH.

[0032] When the UE is limited to single-beam communication capability, and in the fifth set of embodiments, one or more associated CSSs and corresponding sets of PDSCHs to which the TCI state received in block (304) is to be applied may be associated with a CORSET other than CORESET #0 or commonControlResourceSet. Furthermore, and in some embodiments, CORESET #0 or commonControlResourceSet may be associated only with some SSs, such as the Type0-PDCCH set, Type0A-PDCCH set, Type1-PDCCH set, and Type2-PDCCH set. Alternatively, CORESET #0 or commonControlResourceSet may be associated with all CSSs. CORESET #0 and commonControlResourceSet may be received in some sets of time windows, and SSs associated with other CORESETs may be received in different sets of time windows. In some cases, different sets of time windows may be associated with receiving signals from different cells.

[0033] FIG. 4 illustrates an exemplary method (400) of a base station (e.g., gNB or other type of base station), the method (400) may be used to optionally indicate at least one CSS and a corresponding PDSCH to which a TCI state transmitted by the base station should be applied.

[0034] In block (402), the method (400) may include the step of transmitting to the UE, for a CORESET, a indication of at least one CSS within a set of one or more associated CSSs and corresponding PDSCHs to which a TCI state transmitted by a base station is to be applied. The indication may include any of the indications described with reference to FIG. 2.

[0035] In block (404), the method (400) may include the step of transmitting the TCI status to the UE along with the associated source reference signal. The operation(s) in block (404) may occur before or after the operation(s) in block (402).

[0036] In some embodiments of the method (400), a designation of at least one CSS within a set of one or more associated CSSs and corresponding PDSCHs may be transmitted via RRC signaling. In some cases, the designation may be configured per BWP, per serving cell, per serving cell group, or per UE. In some cases, the designation may be configured per TCI state.

[0037] In some embodiments of the method (400), an indication of at least one CSS within a set of one or more associated CSSs and corresponding PDSCHs may be transmitted in the MAC CE. In some cases, the indication may be applied to all TCI states identified in the MAC CE. In some cases, the indication may be applied only to the TCI state transmitted in the block (404).

[0038] In some embodiments of the method (400), a notation of at least one CSS within a set of one or more associated CSSs and corresponding PDSCHs may be transmitted in the DCI used for TCI notation. In some cases, the notation may be transmitted in a first field or a first bit distinct from a second field or a second bit indicating the TCI status.

[0039] In some embodiments of the method (400), the UE, to which the display and TCI status are transmitted in blocks (402 and 404), respectively, may be limited to single-beam communication capability. In these embodiments, the base station may adjust the display of at least one CSS within a set of one or more associated CSSs and corresponding PDSCHs based on the determination that the UE is limited to single-beam communication capability. In some cases, the display may be adjusted in one of the ways described with reference to FIG. 2.

[0040] As discussed above, CORESET can be associated with both CSS and USS in some cases. The TCI status introduced in 3GPP Rel-17 is provided to the UE at the CORESET level for dedicated PDCCH / PDSCH / PUCCH / PUSCH. There are no regulations on how TCI status can be applied to CSS or whether TCI status can be applied to CSS, nor are there any regulations on how to receive different SSs on different beams (e.g., from different cells).

[0041] FIG. 5 illustrates an exemplary method (500) of a UE, which can be used to selectively apply a TCI state only to some SS associated with a CORESET where a TCI state is provided.

[0042] In block (502), the method (500) may include the step of receiving a TCI state from a base station (e.g., gNB or other type of base station) and, together with a source reference signal, a first set of one or more SSs associated with CORESET and a first set of PDSCHs corresponding to the first set of one or more SSs.

[0043] In block (504), the method (500) may include the step of applying a TCI state to a first set of at least one SS. The TCI state may also be applied to a first set of corresponding PDSCHs.

[0044] In block (506), the method (500) may include the step of suppressing the application of a TCI state to a second set of one or more SSs associated with the CORESET and a second set of PDSCHs corresponding to the second set of one or more SSs. In some cases, the method (500) may include the step of suppressing the application of a TCI state to all other SSs associated with the CORESET (i.e., all SSs not included in the first set of one or more SSs).

[0045] Optionally, and in block (508), the method (500) may include the step of receiving at least one PDCCH from a second set of one or more SSs, and optionally, the step of receiving at least one PDSCH from a second set of corresponding PDSCHs.

[0046] Optionally, and in block (510), the method (500) may include the step of implicitly selecting the RLM and BFD RS when the explicit wireless link monitoring (RLM) / beam failure detection (BFD) reference signal (RS) (i.e., RLM / BFD RS) is not configured.

[0047] In some embodiments, the TCI state received in block (502) may be a first TCI state, and the beam indication provided by the first TCI state may be a first beam indication. In these embodiments, the method (500) may include the step of receiving a second TCI state in block (508). The second TCI state may provide a second beam indication for a second set of one or more SSs and a second set of corresponding PDSCHs. The second TCI state may be applied by the UE to a second set of at least one SS. The second TCI state may also be applied to a second set of corresponding PDSCHs. In some cases, the first set of one or more SSs may include only USS. Alternatively, the first set of one or more SSs may include USS and at least a Type3-PDCCH CSS set. In some cases, the first and second TCI states may be received with the same source reference signal. Alternatively, the source reference signal received in block (502) may be a first source reference signal, and the second TCI state may be received together with the second source reference signal. The second source reference signal may be a first SSB received from a base station, or a second SSB quasi-co-located (QCLed) with the first SSB. The first TCI state and the second TCI state may be received in the same L1 / L2 signaling or in different L1 / L2 signalings.

[0048] As proposed in 3GPP Rel-17, when the RLM / BFD RS is not explicitly configured, the RLM / BFD RS is selected based on the configuration in the TCI state for the CORESET. For example, refer to s5 and s6 of 3GPP TSS 38.213. When two TCI states are provided to the UE and the RLM / BFD RS is not explicitly configured, a framework is required to implicitly select the RLM / BFD RS. Accordingly, a number of methods for selecting the RLM / BFD RS in block (510) of method (500) are described below.

[0049] A first possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, the RLM / BFD RS may be implicitly selected by the UE based on whether a first TCI state applies to at least the USS or a second TCI state applies to at least the USS (i.e., a reference signal associated with a TCI state applied to at least the USS may be selected). RLM / BFD may be performed using the selected RLM / BFD RS.

[0050] A second possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, the RLM / BFD RS may be implicitly selected by the UE based on whether a first TCI state applies only to CSS or whether a second TCI state applies at least only to CSS (i.e., a reference signal associated with a TCI state that applies only to CSS may be selected).

[0051] A third possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, a first RLM / BFD RS may be implicitly selected by the UE based on a first TCI state, and a second RLM / BFD RS may be selected based on a second TCI state (i.e., different reference signals associated with different TCI states may be selected).

[0052] A fourth possible method for selecting an RLM / BFD RS in block (510) may include receiving an indication of whether to select an RLM / BFD RS based on a first TCI state or a second TCI state in the UE and in RRC signaling or in MAC CE.

[0053] A fifth possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, the RLM / BFD RS may be implicitly selected by the UE based on at least one of a first ID of a first TCI state or a second ID of a second TCI state. For example, the UE may determine by comparing TCI identifiers (IDs) associated with each of the first TCI state and the second TCI state, and selecting an RLM / BFD RS based on the comparison (for example, a reference signal associated with a TCI state having a lower TCI ID may be selected).

[0054] A sixth possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, the RLM / BFD RS may be selected by the UE and reported to the base station.

[0055] A seventh possible method for selecting an RLM / BFD RS in block (510) may include the step of determining that an explicit RS is not configured for RLM and BFD RS selection. Subsequently, an RLM / BFD RS associated with a serving cell of the UE may be selected by the UE. According to the seventh possible method for selecting an RLM / BFD RS, if a neighboring cell of the UE is also associated with a serving cell of the UE, one or another of the first through sixth methods may be used to select the RLM / BFD RS.

[0056] After the UE has performed the Beam Failure Recovery (BFR) procedure (e.g., within 28 symbols after the UE receives the BFR response), the UE may update the beams applied to one or more SSs based on the newly identified beams reported in the BFR request. The one or more SSs to which the updated beams apply may correspond to SSs in a first set of one or more SSs to which the first TCI was applied; SSs in a second set of one or more SSs to which the second TCI was applied; or SSs in both the first and second sets of one or more SSs. The one or more SSs to which the updated beams apply may be predefined (e.g., programmed into the UE) or configured by higher-level signaling (e.g., indicated in RRC signaling, MAC CE, or PDCCH (e.g., in the BFR response)).

[0057] In some embodiments, the method (500) may include the step of receiving, in block (508), a first set of one or more SSs and an indication of an SSB associated with a second set of one or more SSs. The indicated SSB must be an SSB associated with a serving cell for the UE. The UE may monitor a monitoring opportunity associated with the indicated SSB and, in response to the monitoring, receive a PDCCH from the second set of one or more SSs. In some cases, the UE may need to monitor only the monitoring opportunity associated with the indicated SSB in order to receive a PDCCH from the second set of one or more SSs. In some cases, the indication of an SSB associated with the second set of one or more SSs may be received in a MAC CE. In some cases, the indication of an SSB associated with the second set of one or more SSs may be received in a DCI. In some of these embodiments, the first set of one or more SSs may include only a USS. Alternatively, the first set of one or more SSs may include a USS and at least a Type 3-PDCCH CSS set. When an indication of an SSB associated with a second set of one or more SSs is received, and when the RLM / BFD RS is not explicitly configured, the RLM / BFD RS may be implicitly selected by the UE using any of the previously described methods (wherein the indicated SSB is used as a reference signal associated with the second TCI state).

[0058] In some embodiments, the method (500) may include the step of selecting any monitoring opportunity to receive a PDCCH from a second set of one or more SSs in block (508). Subsequently, the UE may monitor the selected monitoring opportunity for the PDCCH. The base station may repeatedly transmit the PDCCH from the monitoring opportunity. In these embodiments, and when the RLM / BFD RS is not explicitly configured, the RLM / BFD RS may be implicitly selected by the UE based on the TCI status indicated in block (502). After the UE performs the BFR procedure, the UE may update the beams applied to the first set of one or more SSs based on the newly identified beams reported in the BFR request.

[0059] As an alternative to method (500), CORESET may be associated only with types of SS that share a single TCI state. In some embodiments, the types of SS that share a single TCI state may be USS alone; or USS and at least a Type3-PDCCH CSS set; or CSS alone; or a Type0-PDCCH CSS set, a Type0A-PDCCH set, a Type1-PDCCH CSS set, and a Type2-PDCCH CSS set.

[0060] FIG. 6 illustrates an exemplary method (600) of a base station (e.g., gNB or other type of base station), the method (600) may be used to optionally indicate a set of one or more partial CSSs to which a TCI state associated with CORESET should be applied.

[0061] In block (602), the method (600) may include the step of transmitting to the UE, along with a source reference signal, a TCI state that provides a first beam indication for one or more SSs associated with CORESET and a first set of PDSCHs corresponding to the first set of one or more SSs.

[0062] In block (604), the method (600) may include the step of transmitting to the UE at least one of a second beam indication or an indication of an SSB for a second set of one or more SSs associated with the CORESET, and a second set of PDSCHs corresponding to the second set of one or more SSs. In some embodiments, the second beam indication of the indication of an SSB may be transmitted as described with reference to FIG. 4.

[0063] In some embodiments of the method (600), the TCI state transmitted in block (602) may be a first TCI state, and the step of transmitting a second beam indication in block (604) may include the step of transmitting a second TCI state to the UE.

[0064] FIG. 7 illustrates an exemplary timeline (700) of beam indicators (702, 704) for CORESET 0 and SSs (706, 708, 710, 712) associated with CORESET 0 as transmitted (by a base station) and received (by a UE). For example, the beam indicators (702, 704) (e.g., a first TCI state (TCI 1 (702)) and a second TCI state (TCI 2 (704)), or other indicators) are shown as being transmitted in the same L1 / L2 signaling. However, the beam indicators (702, 704) may also be transmitted in different L1 / L2 signaling and / or at different times. Following the transmission / reception of beam indicators (702, 704), a first SS (706) associated with CORESET 0 (e.g., CSS 1 (706)) may be transmitted by a base station and received by a UE at a first time (and / or on a first set of time and frequency resources). As indicated in the beam indicator signaling, a second beam indicator (704) may be applied to the first SS (706) and used to receive the first SS (706). A second SS (708) associated with CORESET 0 (e.g., USS 2 (708)) may be transmitted by a base station and received by a UE at a second time (and / or on a second set of time and frequency resources). As indicated in the beam indicator signaling, a first beam indicator (702) may be applied to the second SS (708) and used to receive the second SS (708). A third SS (710) associated with CORESET 0 (e.g., USS 3 (710)) can be transmitted by a base station and received by a UE at a third time (and / or on a third set of time and frequency resources). As indicated in the beam indication signaling, a first beam indication (702) is applied to the third SS (710) and can be used to receive the third SS (710).A fourth SS (712) (e.g., CSS 2 (712)) associated with CORESET 0 can be transmitted by a base station and received by a UE at a fourth time (and / or on a fourth set of time and frequency resources). As indicated in the beam indication signaling, a second beam indication (704) is applied to the fourth SS (712) and can be used to receive the fourth SS (712).

[0065] The embodiments considered herein include a device having means for performing one or more elements of the method (300, 400, 500, or 600). In the context of the method (300 or 500), such a device may be, for example, a device of a UE (e.g., a wireless device (902) which is a UE as described herein). In the context of the method (400 or 600), such a device may be, for example, a device of a base station (e.g., a network device (920) which is a base station as described herein).

[0066] The embodiments considered herein include one or more non-transient computer-readable media storing instructions, the instructions causing an electronic device to perform one or more elements of methods (300, 400, 500, or 600) when the instructions are executed by one or more processors of the electronic device. In the context of method (300 or 500), these non-transient computer-readable media may be, for example, memory of a UE (e.g., memory (906) of a wireless device (902) that is a UE, as described herein). In the context of method (400 or 600), these non-transient computer-readable media may be, for example, memory of a base station (e.g., memory (924) of a network device (920) that is a base station, as described herein).

[0067] The embodiments considered herein include a device having logic, modules, or circuits for performing one or more elements of the method (300, 400, 500, or 600). In the context of the method (300 or 500), such a device may be, for example, a device of a UE (e.g., a wireless device (902) which is a UE as described herein). In the context of the method (400 or 600), such a device may be, for example, a device of a base station (e.g., a network device (920) which is a base station as described herein).

[0068] The embodiments considered herein include a device having one or more processors for using or storing instructions and one or more computer-readable media, wherein the instructions, when executed by one or more processors, cause one or more processors to perform one or more elements of the method (300, 400, 500, or 600). In the context of the method (300 or 500), such a device may be, for example, a device of a UE (e.g., a wireless device (902) which is a UE as described herein). In the context of the method (400 or 600), such a device may be, for example, a device of a base station (e.g., a network device (920) which is a base station as described herein).

[0069] The embodiments considered in this specification include signals such as or related to those described in one or more elements of the method (300, 400, 500, or 600).

[0070] The embodiments considered herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method (300, 400, 500, or 600). In the context of the method (300 or 500), the processor may be a processor of the UE (e.g., processor(s) (904) of the wireless device (902) which is the UE as described herein), and the instructions may be located, for example, in the processor of the UE and / or in memory (e.g., memory (906) of the wireless device (902) which is the UE as described herein). In the context of the method (400 or 600), the processor may be the processor of the base station (e.g., the processor(s) (922) of the network device (920) which is the base station as described herein), and the instructions may be located, for example, in the processor of the base station and / or in memory (e.g., the memory (924) of the network device (920) which is the base station as described herein).

[0071] FIG. 8 illustrates an exemplary architecture of a wireless communication system (800) according to embodiments disclosed herein. The following description is provided for an exemplary wireless communication system (800) operating with LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0072] As illustrated by FIG. 8, the wireless communication system (800) includes a UE (802) and a UE (804) (however, any number of UEs may be used). In this example, the UE (802) and the UE (804) are exemplified as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0073] UE (802) and UE (804) may be configured to be coupled to communicate with RAN (806). In embodiments, RAN (806) may be NG-RAN, E-UTRAN, etc. UE (802) and UE (804) utilize connections (or channels) (respectively illustrated as connection (808) and connection (810)) with RAN (806), each of which includes a physical communication interface. RAN (806) may include one or more base stations, such as base station (812) and base station (814), that enable connection (808) and connection (810).

[0074] In this example, the connection (808) and the connection (810) are air interfaces for enabling this communication coupling and may follow the RAT(s) used by the RAN (806), such as LTE and / or NR.

[0075] In some embodiments, the UE (802) and the UE (804) may also directly exchange communication data through the sidelink interface (816). The UE (804) is illustrated as being configured to access an access point (illustrated as AP (818)) through a connection (820). For example, the connection (820) may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where the AP (818) may include a Wi-Fi® router. In this example, the AP (818) may be connected to another network (e.g., the Internet) without going through the CN (824).

[0076] According to some embodiments, UE (802) and UE (804) may be configured to communicate with each other or with base station (812) and / or base station (814) using OFDM (orthogonal frequency division multiplexing) communication signals over a multicarrier communication channel according to various communication techniques, such as OFDMA (orthogonal frequency division multiplexing) communication technique (e.g., for downlink communications) or SC-FDMA (single carrier frequency division multiple access) communication technique (e.g., for uplink and ProSe or sidelink communications), but not limited thereto, but the scope of embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0077] In some embodiments, all or part of the base station (812) or base station (814) may be implemented as one or more software entities running on server computers as part of a virtual network. Additionally, or in other embodiments, the base station (812) or base station (814) may be configured to communicate with each other through an interface (822). (e.g., when CN (824) is an EPC) In embodiments where the wireless communication system (800) is an LTE system, the interface (822) may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. (e.g., when CN (824) is a 5GC) In embodiments where the wireless communication system (800) is an NR system, the interface (822) may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to 5GC, between a base station (812) (e.g., gNB) connected to 5GC and an eNB, and / or between two eNBs connected to 5GC (e.g., CN (824)).

[0078] The RAN (806) is illustrated as being communicably coupled to the CN (824). The CN (824) may include one or more network elements (826), which are configured to provide various data and telecommunication services to customers / subscribers (e.g., users of the UE (802) and UE (804)) connected to the CN (824) through the RAN (806). The components of the CN (824) may be implemented in one physical device or separate physical devices, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transient machine-readable storage medium).

[0079] In embodiments, CN (824) may be an EPC, and RAN (806) may be connected to CN (824) through S1 interface (828). In embodiments, S1 interface (828) may be divided into two parts: an S1 user plane (S1-U) interface that carries traffic data between base station (812) or base station (814) and a serving gateway (S-GW), and an S1-MME interface which is a signaling interface between base station (812) or base station (814) and mobility management entities (MMEs).

[0080] In embodiments, CN (824) may be 5GC, and RAN (806) may be connected to CN (824) through NG interface (828). In embodiments, NG interface (828) may be divided into two parts: an NG user plane (NG-U) interface that carries traffic data between base station (812) or base station (814) and user plane functions (UPF), and an S1 control plane (NG-C) interface that is a signaling interface between base station (812) or base station (814) and access and mobility management functions (AMF).

[0081] Generally, the application server (830) may be an element that provides applications using Internet Protocol (IP) bearer resources together with the CN (824) (e.g., packet-switched data services). The application server (830) may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE (802) and UE (804) through the CN (824). The application server (830) may communicate with the CN (824) through the IP communication interface (832).

[0082] FIG. 9 illustrates a system (900) for performing signaling (938) between a wireless device (902) and a network device (920) according to embodiments disclosed herein. The system (900) may be part of a wireless communication system as described herein. The wireless device (902) may be, for example, a UE of a wireless communication system. The network device (920) may be, for example, a base station of a wireless communication system (e.g., an eNB or a gNB).

[0083] The wireless device (902) may include one or more processor(s) (904). The processor(s) (904) may execute instructions to perform various operations of the wireless device (902) as described herein. The processor(s) (904) 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, other hardware devices, firmware devices, or any combination thereof, configured to perform the operations described herein.

[0084] The wireless device (902) may include memory (906). Memory (906) may be a non-transient computer-readable storage medium that stores instructions (908) (e.g., instructions executed by the processor(s) (904)). Instructions (908) may also be referred to as program code or computer programs. Memory (906) may also store data used by the processor(s) (904) and results computed by the processor(s) (904).

[0085] The wireless device (902) may include one or more transceivers (910) that may include radio frequency (RF) transmitter and / or receiver circuits that use antenna(s) (912) of the wireless device (902) to facilitate signaling (e.g., signaling (938)) from and to other devices (e.g., network device (920)) according to corresponding RATs.

[0086] The wireless device (902) may include one or more antenna(s) (912) (e.g., one, two, four or more). In the case of embodiments having multiple antenna(s) (912), the wireless device (902) may leverage the spatial diversity of such multiple antenna(s) (912) to transmit and / or receive multiple different data streams over the same time and frequency resources. This behavior may be referred to, for example, as multiple input multiple output (MIMO) behavior (referring to multiple antennas used in each of the transmitting device and the receiving device that enable this aspect). MIMO transmissions by a wireless device (902) can be achieved by precoding (or digital beamforming) applied in the wireless device (902) which multiplexes data streams across antenna(s) (912) according to known or assumed channel characteristics so that each data stream is received at an appropriate signal strength relative to other streams and at a desired location within the spatial domain (e.g., the location of the receiver associated with the data stream). Specific embodiments may use single user MIMO (SU-MIMO) methods (where all data streams are directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers at different locations within the spatial domain).

[0087] In certain embodiments having multiple antennas, the wireless device (902) can implement analog beamforming techniques, thereby adjusting the phases of signals transmitted by the antenna(s) (912) relative to each other so that the (joint) transmission of the antenna(s) (912) can be directed (this is sometimes referred to as beam steering).

[0088] A wireless device (902) may include one or more interface(s) (914). The interface(s) (914) may be used to provide input to the wireless device (902) or to provide output from it. For example, a wireless device (902) which is a UE may include interface(s) (914), such as microphones, speakers, touchscreens, buttons, etc., to allow input and / or output to the UE by a user of the UE. Other interfaces of such a UE may consist of transmitters, receivers, and other circuitry (other than, for example, the transceiver(s) (910) / antenna(s) (912) already described) that allow communication between the UE and other devices, and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, etc.).

[0089] The wireless device (902) may include a beam identification module (916) and / or a BFR module (918). The beam identification module (916) and the BFR module (918) may be implemented through hardware, software, or a combination thereof. For example, the beam identification module (916) and the BFR module (918) may be implemented as instructions (908) stored in a processor, circuit, and / or memory (906) and executed by the processor(s) (904). In some examples, the beam identification module (916) and the BFR module (918) may be integrated within the processor(s) (904) and / or transceiver(s) (910). For example, the beam identification module (916) and the BFR module (918) may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor(s) (904) or transceiver(s) (910).

[0090] The beam identification module (916) may be used for various embodiments of the present disclosure, e.g., embodiments of FIGS. 1 through 7. The beam identification module (916) may be configured to receive, determine, and / or apply beam indications received from, for example, another device (e.g., network device (920)).

[0091] The BFR module (918) may be used for various embodiments of the present disclosure, e.g., embodiments of FIGS. 1 through 7. The BFR module (918) may be configured to implicitly select an RLM / BFD RS for BFR, e.g., or to perform BFD as described herein.

[0092] The network device (920) may include one or more processor(s) (922). The processor(s) (922) may execute instructions to perform various operations of the network device (920) as described in this specification. The processor(s) (904) may include one or more baseband processors implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, other hardware device, firmware device, or any combination thereof, configured to perform the operations described in this specification.

[0093] The network device (920) may include memory (924). The memory (924) may be a non-transient computer-readable storage medium that stores instructions (926) (e.g., instructions executed by the processor(s) (922)). The instructions (926) may also be referred to as program code or computer programs. The memory (924) may also store data used by the processor(s) (922) and results computed by the processor(s) (922).

[0094] The network device (920) may include one or more transceiver(s) (928) that may include an RF transmitter and / or receiver circuit that uses the antenna(s) (930) of the network device (920) to facilitate signaling (e.g., signaling (938)) to and / or from the network device (920) to other devices (e.g., wireless device (902)) according to the corresponding RATs.

[0095] The network device (920) may include one or more antenna(s) (930) (e.g., one, two, four or more). In embodiments having multiple antenna(s) (930), the network device (920) may perform MIMO, digital beamforming, analog beamforming, beam steering, etc. as described.

[0096] A network device (920) may include one or more interface(s) (932). The interface(s) (932) may be used to provide input to the network device (920) or to provide output from it. For example, a network device (920) that is a base station may include an interface(s) (932) composed of transmitters, receivers, and other circuitry (other than, for example, the transceiver(s) (928) / antenna(s) (930) already described) that enables the base station to communicate with other equipment in a core network and / or enable the base station to communicate with external networks, computers, databases, etc. for the purposes of operation, management, and maintenance of the base station or other equipment operably connected thereto.

[0097] The network device (920) may include a beam display module (934) and / or a BFR module (936). The beam display module (934) and the BFR module (936) may be implemented through hardware, software, or a combination thereof. For example, the beam display module (934) and the BFR module (936) may be implemented as instructions (926) stored in a processor, circuit, and / or memory (924) and executed by the processor(s) (922). In some examples, the beam display module (934) and the BFR module (936) may be integrated within the processor(s) (922) and / or transceiver(s) (928). For example, the beam display module (934) and the BFR module (936) may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor(s) (922) or transceiver(s) (928).

[0098] The beam display module (934) may be used for various embodiments of the present disclosure, for example, embodiments of FIGS. 1 through 7. The beam display module (934) may be configured to transmit beam displays to another device (for example, a wireless device (902)).

[0099] The BFR module (936) may be used for various embodiments of the present disclosure, e.g., embodiments of FIGS. 1 through 7. The BFR module (936) may be configured to use another device (e.g., wireless device (902)) to use BFD as described in the specification, e.g., or to receive BFR on an RLM / BFD RS.

[0100] For one or more embodiments, at least one of the components described in one or more of the prior art drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in relation to one or more of the prior art drawings may be configured to operate according to one or more of the examples described herein. For other examples, circuitry associated with a UE, base station, network element, etc. as described above in relation to one or more of the prior art drawings may be configured to operate according to one or more of the examples described herein.

[0101] Any of the embodiments described above may be combined with any other embodiments (or combinations of embodiments) unless otherwise clearly indicated. The foregoing description of one or more embodiments is for illustrative and descriptive purposes only and is not intended to be comprehensive or to limit the scope of the embodiments to the exact form disclosed. Modifications and variations may be obtained from the practice of possible or various embodiments in consideration of the above teachings.

[0102] The embodiments and implementations of the systems and methods described herein may include various operations that can be implemented as machine-executable instructions to be executed by a computer system. The 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 operations, or may include a combination of hardware, software, and / or firmware.

[0103] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into single systems, partially combined into other systems, divided into multiple systems, or divided or combined in other ways. Additionally, it is considered that parameters, attributes, aspects, etc. of one embodiment may be used in other embodiments. It is recognized that parameters, attributes, aspects, etc. are described in only one or more embodiments for clarity, and that parameters, attributes, aspects, etc. may be combined with or replaced by parameters, attributes, aspects, etc. of other embodiments unless specifically disclaimed herein.

[0104] It is well understood that the use of personally identifiable information must follow privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data must be managed and processed to minimize the risk of unintended or unauthorized access or use, and the nature of authorized use must be clearly indicated to users.

[0105] Although the foregoing has been described in some detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and apparatuses described herein. Accordingly, the embodiments shall be regarded as illustrative rather than restrictive, and the description is not limited to the details given herein but may be modified within the scope and equivalents of the appended claims.

Claims

Claim 1 A method comprising: receiving, through wireless resource control (RRC) signaling, a transmission configuration indication (TCI) received from a network device, a indication of at least one common search space (CSS) within a set of one or more common search spaces (CSS) associated with a control channel resource set (CORESET) to which the TCI received from the network device to be applied; identifying, at least partially from the indication of the at least one CSS and with respect to the control channel resource set (CORESET), a set of one or more associated CSSs and corresponding physical downlink shared channels (PDSCH) to which the TCI received from the network device to be applied; receiving the TCI state; and applying the TCI state to at least one dedicated PDSCH; and at least one CSS and a corresponding PDSCH within the identified set of the one or more CSSs and the corresponding PDSCH. Claim 2 delete Claim 3 The method of claim 1, wherein the step of identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device to be applied comprises: receiving a indication of the at least one CSS within the set of one or more associated CSSs to which the TCI state to be applied in a media access control (MAC) control element (MAC CE); and at least partially identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device to be applied from the received indication. Claim 4 The method of claim 1, wherein the step of identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device to be applied comprises: receiving a representation of at least one CSS within the set of one or more associated CSSs to which the TCI state to be applied in downlink control information (DCI) used for TCI representation; and at least partially identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device to be applied from the received representation. Claim 5 A method according to claim 1, wherein the step of identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device to be applied comprises the step of analyzing a 1-bit indicator received from the network device. Claim 6 The method of claim 1, wherein the step of identifying the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device is to be applied comprises the step of analyzing an N-bit indicator received from the network device, wherein N is greater than 1; and different bits or combinations of bits provide indicators of whether the TCI state is to be applied to different CSSs within the set of one or more associated CSSs. Claim 7 A method according to claim 1, wherein the step of identifying a set of one or more associated CSSs and corresponding PDSCHs to which the TCI state received from the network device is to be applied comprises the step of determining to apply the TCI state to at least one predetermined CSS. Claim 8 The method of claim 1 further comprises the steps of: identifying a CSS to which no received TCI state is applied; selecting a monitoring opportunity to receive downlink signals for said CSS; receiving a synchronization signal block (SSB) associated with said CSS; and monitoring the monitoring opportunity for said downlink signals. Claim 9 In claim 1, the method is applied to a user equipment (UE) limited to a single-beam communication capability; the TCI state is applied to a UE-specific search space (USS) and a corresponding PDSCH; the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state is to be applied comprises only a Type 1-PDCCH CSS set, a Type 2-PDCCH CSS set, and a Type 3-PDCCH CSS set; and the method further comprises the step of suppressing the decoding of a System Information Block (SIB) after a Wireless Resource Control (RRC) connection, unless indicated to be decoded by the network device. Claim 10 The method of claim 1, wherein the method is applied to a user equipment (UE) limited to a single-beam communication capability; wherein the TCI state is applied to a UE-specific search space (USS) and a corresponding PDSCH; wherein the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state is to be applied comprises only a Type 2-PDCCH CSS set and a Type 3-PDCCH CSS set; and wherein the method further comprises the steps of: transmitting a physical random access channel (PRACH) for random access; and resetting the beam applied to all channels across all component carriers (CC) within a band or band group based on a synchronization signal block (SSB) associated with the PRACH. Claim 11 In claim 1, the method is applied to a user equipment (UE) limited to a single-beam communication capability; the TCI state is applied to a UE-specific search space (USS) and a corresponding PDSCH; the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state is to be applied comprises only a Type 1-PDCCH CSS set and a Type 3-PDCCH CSS set; the method further comprises the steps of: selecting a monitoring opportunity to decode paging information for receiving paging; and dropping signals transmitted to the PDCCH / PDSCH for paging within a time window. Claim 12 In claim 1, the method is applied to a user equipment (UE) limited to single-beam communication capability; the TCI state is applied to a UE-specific search space (USS) and a corresponding PDSCH; and the set of one or more associated CSSs and corresponding PDSCHs to which the TCI state is to be applied comprises only a Type 3-PDCCH CSS set. Claim 13 In claim 1, the method is applied to user equipment (UE) limited to single-beam communication capability; and the CORESET to which the TCI status is received is not CORESET #0 or commonControlResourceSet. Claim 14 delete Claim 15 delete Claim 16 delete Claim 17 delete Claim 18 A method of a network device comprising: transmitting to a user device (UE) a representation of at least one CSS within a set of one or more common search spaces (CSS) associated with a control channel resource set (CORESET) to which a transmission configuration indication (TCI) status transmitted by the network device is to be applied, via wireless resource control (RRC) signaling; and transmitting the TCI status to the UE. Claim 19 A method of a network device according to claim 18, wherein the indication of at least one CSS within the set of one or more associated CSSs is transmitted in a first field or first bit distinct from a second field or second bit indicating the TCI status. Claim 20 A method comprising, for a wireless communication network and a user device (UE) limited to single-beam communication capability, identifying, for a control channel resource set (CORESET), a set of one or more associated common search spaces (CSS) and corresponding physical downlink shared channels (PDSCH) to which a transmission configuration indication (TCI) state received from a network device is to be applied, wherein the set of one or more associated CSS and corresponding PDSCH comprises only a Type 3-PDCCH CSS set; receiving the TCI state; and applying the TCI state to a UE-specific search space (USS) and a corresponding PDSCH; and at least one CSS and a corresponding PDSCH within the set of the identified one or more CSS and corresponding PDSCH.

Images