Wireless device initiated beam management procedure

Abstract

A method in a wireless device (WD) configured to perform a WD-initiated beam management procedure and communicate with a network node is described. The method includes determining, based on one or more parameters, one or more of: (A) a first timing indication indicating a beam switching delay associated with a WD initiated beam report; (B) a second timing indication indicating when to perform a fallback beam handover associated with a WD initiated beam management process; and (C) a third timing indication indicating a minimum time between the two WD initiated beam reports. The method further includes performing one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more particularly to beam management processes initiated by wireless devices. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) wireless communication systems. Among other features, such systems provide broadband communication between network nodes (NNs) (such as base stations) and mobile wireless devices (WDs) (such as user equipment (UEs)), as well as communication between network nodes (NNs) and between WDs. 3GPP is also developing standards for sixth-generation (6G) wireless communication networks.

[0003] QCL and TCI states

[0004] In NR, several signals can be transmitted from different antenna ports of the same base station. These signals can have the same large-scale properties, such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then referred to as quasi-co-located (QCL).

[0005] If the WD knows that both antenna ports have a QCL (Quality of Channel) with respect to a certain parameter (e.g., Doppler spread), the WD can estimate that parameter based on one antenna port and apply that estimate to receive the signal on the other antenna port. For example, a QCL relationship may exist between the Channel State Information Reference Signal (CSI-RS) used for tracking reference signal RS (TRS) and the Physical Downlink Shared Channel (PDSCH) demodulation reference signal (DMRS). When the WD receives the PDSCH DMRS, it can use measurements already taken on the TRS to assist in DMRS reception. Information about what assumptions can be made regarding QCL is signaled from the network to the WD. In NR (Network Reference Module), four types of QCL relationships are defined between the transmitted source RS and the transmitted target reference signal (RS):

[0006] Type A: {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0007] Type B: {Doppler frequency shift, Doppler spread}

[0008] Type C: {Average delay, Doppler shift}

[0009] Type D: {Space Rx parameter}

[0010] QCL Type D was introduced to facilitate beam management using analog beamforming and is referred to as spatial QCL. There is currently no rigorous definition of spatial QCL, but it is understood that if two transmitting antenna ports are spatially QCL, the WD can use the same receive (RX) beam to receive them. This is helpful for WDs using analog beamforming to receive signals, as the WD needs to adjust its RX beam in a certain direction before receiving a specific signal. If the WD knows that the signal is spatially QCL with some other signal it has previously received, then it can safely use the same RX beam to also receive that signal. For beam management, the discussion mainly revolves around QCL Type D, but it is also necessary to communicate the Type A QCL relationship for RS to the WD so that it can estimate all relevant large-scale parameters.

[0011] Typically, this is achieved by configuring a tracking-based CSI-RS (TRS) for time / frequency offset estimation on the WD. In order to use any QCL reference, the WD must receive it with a sufficiently good signal-to-interference-plus-noise ratio (SINR). In many cases, this means the TRS must be transmitted to a particular WD with a suitable beam.

[0012] To introduce dynamism in beam and transport point (TRP) selection, the WD can be configured via Radio Resource Control (RRC) signaling with up to 128 Transport Configuration Indicator (TCI) states. TCI state information elements (e.g., from 3GPP TS 38.331 V16.7.0) are shown below:

[0013]

[0014] Each TCI state contains QCL information associated with one or two RSs. For example, a TCI state could contain CSI-RS1 associated with QCL type A and CSI-RS2 associated with QCL type D. If a third RS, such as the Physical Downlink Control Channel (PDCCH) demodulation reference signal (DMRS), has this TCI state as a QCL source, this means that when performing channel estimation for the PDCCH DMRS, the WD can derive the Doppler shift, Doppler spread, average delay, and delay spread from CSI-RS1, and derive the spatial RX parameters (i.e., the RX beam to be used) from CSI-RS2.

[0015] A first list of available TCI states is configured for PDSCH, and a second list of TCI states is configured for PDCCH. Each TCI state contains a pointer, called the TCI state ID, which points to the TCI state. The network then activates one TCI state for PDCCH (i.e., provides TCI for PDCCH) and up to eight TCI states for PDSCH via the Media Access Control (MAC) control element (CE). The number of active TCI states supported by the WD is limited by the WD capability, but is a maximum of eight.

[0016] A WD can have four active TCI states (from a list of a total of 64 configurable TCI states). Therefore, for a given WD, 60 TCI states are inactive, and the WD does not need to prepare large-scale parameter estimates for those inactive TCI states. However, the WD continuously tracks and updates the large-scale parameters used for RS in the four active TCI states. When a PDSCH is scheduled to the WD, the Download Control Information (DCI) contains a pointer to an active TCI state. The WD then knows which large-scale parameter estimate to use when performing PDSCH DMRS channel estimation and therefore PDSCH demodulation.

[0017] As long as the WD can use any of the currently active TCI states, DCI signaling is sufficient. However, at some point, the WD may become unable to receive any of the source RSs in the currently active TCI states, i.e., when the WD moves out of the beam in which it transmits the source reference signal (RS) of an active TCI state. When this happens (or actually before it happens), the network node (e.g., gNB) will have to activate a new TCI state. Typically, since the number of active TCI states is fixed, the network node must also deactivate one or more of the currently active TCI states.

[0018] Figure 1 The document describes a two-step process related to TCI state updates, in which a TCI state is selected from the set of active TCI states using DCI, and the set of active TCI states is updated using MAC CE.

[0019] TCI state activation / deactivation for WD-specific PDSCH via MAC CE

[0020] Details are provided for MAC CE signaling used to activate / deactivate TCI states for WD-specific PDSCH. The structure of the MAC CE for activating / deactivating TCI states for WD-specific PDSCH is as follows: Figure 2 As shown (e.g., 3GPP Technical Specification (TS) 38.321 16.12.0), Figure 6 (As shown in .1.3.14-1).

[0021] like Figure 2 As shown, MAC CE includes the following fields:

[0022] • Serving Cell ID: This field indicates the identifier of the serving cell to which MAC CE applies. The field is 5 bits long;

[0023] • BWP ID: This field contains the ID corresponding to the downlink bandwidth portion applicable to MAC CE. The BWP ID is given by the higher-layer parameter BWP-Id as specified in 3GPP TS 38.331 V16.7.0. The BWP ID field is 2 bits long because up to 4 BWPs can be configured to the WD for DL;

[0024] • Variable number of fields T i If a TCI state with TCI state ID i is configured to WD, then field T... i Indicates the active / deactivated state of the TCI state with TCI state ID i. If the WD does not have a TCI state with TCI state ID i configured, the MAC entity should ignore T. i Field. T i The field is set to "1" to indicate that the TCI state with TCI state ID i should be activated and mapped to the code point of the DCI Transmission Configuration Indication field, as specified in 3GPP TS 38.214 V16.14.0 / 38.321 V16.12.0. i The field is set to "0" to indicate that the TCI state with TCI state ID i should be deactivated and is not mapped to any code point in the DCI transport configuration indication field. It should be noted that the code points to which the TCI state is mapped are determined by T... i The ordinal position among all TCI states where the field is set to "1" is determined. In other words, T... i The first TCI state with the field set to "1" should be mapped to a code point value of 0 in the DCI Transport Configuration Indication field. i The second TCI state with the field set to "1" should be mapped to a code point value of 1 in the DCI Transport Configuration Indication field, and so on. In NR 3GPP Release 15 (Rel-15), the maximum number of active TCI states is 8;

[0025] • Reserved bit R: In NR 3GPP Rel-15, this bit is set to "0".

[0026] The activation / deactivation of the TCI state for a WD-specific PDSCH MAC CE can be identified by a MAC PDU subheader with a Logical Channel ID (LCID), as specified in Table 6.2.1-1 of 3GPP TS 38.321 V16.12.0 (which is reproduced in Table 1 below). The MAC CE used to activate / deactivate the TCI state for a WD-specific PDSCH has a variable size.

[0027] TCI state indication for WD-specific PDSCH via DCI

[0028] The gNB can indicate to the WD using DCI format 1_1 or 1_2 that it will use one of the active TCI states for subsequent PDSCH reception. The field used in DCI is called the Transport Configuration Indicator or TCI field, which is 3 bits if the higher layer has tci-PresentInDCI "enabled" or tci-PresentForDCI-Format1-2-r16 present for DCI format 1_1 and DCI 1_2 respectively. Figure 3 An example of such a DCI indication of a TCI state is depicted in the diagram. The TCI field provides a pointer to an ordered list of active TCI states.

[0029] Code point 0 in the TCI field indicates the first TCI state index in the TCI state list, code point 1 in the TCI field indicates the second TCI state index in the list, and so on.

[0030] Overview of NR 3GPP Rel-15 / Rel-16 TCI state framework

[0031] The NR 3GPP release (Rel-15 / 16) framework for beam management is based on spatial QCL assumptions and spatial relationships to support analog beamforming implementations, such as at the WD and / or network. This framework allows network nodes (e.g., gNBs) significant flexibility in instructing the WD to receive signals from and transmit signals in several directions. In this framework, uplink and downlink configurations are decoupled; for example, there is no direct relationship between the spatial QCL assumptions and spatial relationships in the configuration.

[0032] In the 3GPP Rel-15 / Rel-16 framework, downlink beam management is performed by communicating spatial QCL (“Type D”) assumptions to the WD, which are communicated in TCI states. A TCI state contains one or two RSs, and each RS is associated with a QCL type.

[0033] • PDCCH beam management:The network configures the set of PDCCH TCI states to the WD via RRC, and then uses the Media Access Control (MAC) Control Element (CE) to activate a TCI state for each Control Resource Set (CORESET).

[0034] • PDSCH beam management: The network configures the set of PDSCH TCI states to the WD via RRC, and then activates up to eight TCI states via MACCE. After activation, the network uses the TCI field in the DCI to dynamically indicate one of these activated TCI states when scheduling the PDSCH.

[0035] Alternatively, the network can simplify beam management by not enabling the RRC parameter tci-PresentInDCI (which is configured per CORESET). In this case, WD uses the same TCI state for PDSCH as for PDCCH.

[0036] In the 3GPP Rel-15 / Rel-16 framework, uplink beam management is performed using spatial relations configuration. Spatial relations are defined between the source RS and the target RS on the WD side. The source RS can be a received DLRS (Synchronization Signal Block (SSB) or CSI-RS) or a Sound Reference Signal (SRS). The target RS can be a transmitted PUCCH DMRS or SRS. Note that there is no direct configuration for spatial relations for PUSCH: PUSCH follows the spatial relations of either PUCCH or SRS.

[0037] • PUCCH beam management: For PUCCH, the network uses RRC to configure a set of eight spatial relations to the WD, and then uses MAC CE to activate one of these spatial relations. Spatial relations are defined for each PUCCH resource. In 3GPPRel-16, enhancements were made to allow updating spatial relations for a set of PUCCH resources using a single MAC-CE. Additionally, Rel-16 introduced default spatial relations for PUCCH, so that when no spatial relations are configured / activated for a PUCCH resource, the WD uses the TCI state / QCL assumption of the lowest ID CORESET to derive the spatial relations and the derived path loss reference signal.

[0038] • PUSCH beam management:PUSCHs scheduled via DCI format 0_1 ​​are transmitted on ports that can also transmit configured SRS resources. Two (codebook-based) or four (non-codebook-based) SRS resources can be defined in the SRS resource set. The network uses the SRS Resource Indicator (SRI) field in the DCI to select which SRS resource in the set should correspond to the PUSCH transmission (i.e., the PUSCH is transmitted on the same port as the selected SRS and using the spatial relation of the selected SRS). The spatial relation for the SRS resources in the set is provided by Radio Resource Control (RRC) (for periodic or aperiodic SRS) or MAC-CE (for aperiodic or semi-persistent SRS). For PUSCHs scheduled via DCI format 0_0, there is no SRI, and the spatial relation instead follows the spatial relation of the PUCCH resource. In Rel-16, a default spatial relation for SRS was introduced, such that when no spatial relation is configured / activated for an SRS resource, the WD uses the TCI state / QCL assumption of the lowest ID CORESET to derive the spatial relation and the derived path loss reference signal.

[0039] • SRS beam management: Spatial relationships for SRS are configured via RRC (for periodic and aperiodic) or MAC CE (for aperiodic or semi-persistent).

[0040] Issues with 3GPP Rel-15 / Rel-16 TCI state framework

[0041] The 3GPP Rel-15 / Rel-16 framework provides significant network flexibility in some areas at the cost of substantial signaling overhead. In others, the specification is overly restrictive and prohibits efficient (low signaling overhead) and fast beam management. These limitations are particularly pronounced and costly when considering WD (Wide-Wide) mobility. One example is that beam updates using DCI can only be performed on PDSCH and require MAC-CE and / or RRC to update beams used for other reference signals / channels, resulting in additional overhead and latency.

[0042] Furthermore, in most cases, specified beam management flexibility is not really needed because the network will use the same beam to send data and receive control signals from the WD. Therefore, using TCI states for downlink (DL) signals / channels and spatial relationships for uplink (UL) signals / channels would complicate implementation.

[0043] Another issue relates to the path loss reference signal used for UL power control. In NR, only up to four path loss reference signals can be configured for the WD, which is typically significantly fewer than the number of beams used by the TRP to cover the cell at FR2. Therefore, as the WD moves around within the cell, the path loss reference signals need to be updated using MAC-CE and / or RRC, which introduces additional delay and overhead.

[0044] 3GPP Rel-17 TCI state framework

[0045] In 3GPP Rel-17, a new unified TCI state framework was defined, which aims to streamline the indication of transmit / receive spatial filters (and other QCL attributes) for WD by allowing a single TCI state to indicate the QCL attributes for multiple different DL and / or UL signals / channels.

[0046] The unified TCI state framework of 3GPP Rel-17 can be configured via RRC in either "Joint DL / UL TCI" or "Separate DL / UL TCI" operating modes. For "Joint DL / UL TCI" operation, a common joint TCI state is used for both DL and UL signals / channels. For "Separate DL / UL TCI" operation, a common DL-only TCI state is used for the DL channel / signal, and a common UL-only TCI state is used for the UL signal / channel.

[0047] "Joint DL / UL TCI" operation is expected to be the most common use case, but "separate DL / UL TCI" operation may be useful in specific scenarios where the optimal DL beam differs from the optimal UL beam (e.g., when the WD panel associated with the optimal DL beam is affected by P-MPR (Power Management - Maximum Power Reduction) and therefore needs to reduce the maximum allowable output power).

[0048] Beam indication using Rel-17 TCI state framework

[0049] The public TCI status ID can be updated in a similar manner to updating the TCI status ID for PDSCH in 3GPP Rel-15 / 16, i.e., using one of the two alternatives:

[0050] • Two-phase: RRC signaling is used to configure multiple TCI states in PDSCH-config, and MAC-CE is used to activate a single TCI state (which will then be applied).

[0051] • Three phases: RRC signaling is used to configure multiple TCI states in PDSCH-configuration, MAC-CE is used to activate up to 8 TCI states, and the 3-bit TCI state bit field in DCI (consisting of up to 8 code points) is used to indicate one of the activated TCI states (which will then be applied).

[0052] For the "Joint DL / UL TCI" operation, a maximum of one joint TCI state can be activated for each TCI field code point. Figure 4 The diagram illustrates a schematic example of what this might look like, showing an example of the active TCI state and its mapping to TCI field code points for "Joint DL / UL TCI". If the indicated TCI field code point is "1", then WD should apply "Joint TCI State 7" as a common QCL source for both DL and UL signals / channels.

[0053] For “Individual DL / UL TCI” operation, up to two TCI states can be activated for each TCI field code point, one for DL ​​signal / channel (DL TCI state only) and the other for UL signal / channel (UL TCI state only). Figure 5 The diagram illustrates a possible example of what this might look like. Figure 5 This is an example of the active TCI state for "Joint DL / UL TCI" and its mapping to TCI field code points. If the TCI field code point is "0", WD should apply "DL TCI State 3 Only" as the common QCL source for DL ​​signals / channels, without updating the QCL source for UL signal channels. If the TCI field code point is "7", WD should apply "UL TCI State 57 Only" as the QCL source for UL signals / channels, without updating the QCL source for DL ​​signals / channels. If the TCI field code point is "2", WD should apply "DL TCI State 9 Only" as the QCL source for DL ​​signals / channels and "UL TCI State 1 Only" as the QCL source for UL signals / channels.

[0054] Existing DCI formats 1_1 and 1_2 in NR are reused (as in the 3GPP Rel-15 / 16 beam management framework) for beam indication, with or without DL assignment. For DCI formats 1_1 and 1_2 with DL assignment, the ACK / NACK of the PDSCH can be used as an indication of successful reception of the beam indication. For DCI formats 1_1 and 1_2 without DL assignment, a new ACK / NACK mechanism is used, similar to the ACK / NACK mechanism for SPS PDSCH release using type 1 and type 2 HARQ-ACK codebooks, where the WD reports an ACK after successful reception of the beam indication DCI.

[0055] For DCI-based beam indication, the first timeslot of the indicated TCI state is at least Y symbols after the last symbol of the confirmed joint or individual DL / UL beam indication. The Y symbols are configured by the network node based on WD capabilities, which are also reported in symbols.

[0056] QCL and UL spatial relation rules

[0057] For both "Joint DL / UL TCI" and "Alone DL / UL TCI" operations, the large-scale QCL attributes are inferred from one source RS (qcl-type 1 only) or two source RSs (qcl-type 1 and qcl-type 2), similar to the Rel-15 / 16 beam management framework. For "Joint DL / UL TCI" operations, the UL space can be derived from the spatial relationships corresponding to the source RSs of DL QCL type D, similar to the default beam operation used for the 3GPP Rel-15 / 16 beam management framework.

[0058] In DL, the combined / DL-only TCI state can provide public QCL information for at least the following objects:

[0059] •WD dedicated PDCCH

[0060] •PDSCH;

[0061] • Non-periodic CSI-RS for CSI;

[0062] • Non-periodic CSI-RS for beam management;

[0063] ○ CSI-RS for other time-domain behaviors has not yet been approved.

[0064] RRC configuration is used to indicate whether non-WD dedicated PDCCH / PDSCH, AP CSI-RS used for CSI and beam management (BM) should follow a common beam. Here, a common beam refers to the same beam used to receive DL signals / channels indicated as following the common beam. For DL ​​signals / channels that do not follow the common beam, the 3GPP Rel-17 TCI state can be indicated as a QCL source in a manner similar to the 3GPP Rel-15 / 16 beam management framework. As an example, for periodic CSI-RS that do not follow the common beam, the 3GPP Rel-17 TCI state can be configured in the parameter "qcl-InfoPeriodicCSI-RS" of the "NZP-CSI-RS-Resourceinformation element" as specified in 3GPP TS 38.331 V16.7.0. Figure 6 The diagram shows the possible target RS, source RS, and corresponding QCL attributes that are supported for joint / DL-only TCI status indication.

[0065] In UL, a combined / UL TCI status can provide public QCL information for at least the following:

[0066] • All or a subset of all PUCCH resources

[0067] • Dynamic licensing / configuration licensing PUSCH

[0068] • SRS for all uses (except for the "positioning" use)

[0069] RRC configuration is used to indicate whether SRS and PUCCH resources should follow a common beam. Here, a common beam refers to the same beam used to receive UL signals / channels indicated as following the common beam. For UL signals / channels that do not follow a common beam, the 3GPP Rel-17 TCI state can be used to indicate spatial relationships instead of the DL / UL-RS used to indicate spatial relationships for the Rel-15 / 16 beam management framework. As an example, for periodic SRS resources that do not follow a common beam, new RRC parameters in the SRS resource can be configured with a 3GPP Rel-17 TCI state, and the WD will use this 3GPP Rel-17 TCI state to determine the spatial relationships for that SRS resource. Any of the following reference signals can be used to indicate spatial relationships for UL signals / channels within the 3GPP Rel-17 TCI state framework:

[0070] •SSB;

[0071] • TRS (Tracking Reference Signal);

[0072] • CSI-RS for beam management;

[0073] • An SRS that can be configured for beam management.

[0074] Inter-cell beam management

[0075] Inter-cell beam management has been included in the 3GPP Rel-17 TCI state framework to facilitate L1 / L2 inter-cell mobility (to be specified for higher layers in NR Rel-18) and inter-cell multi-TRP operations.

[0076] For inter-cell beam management, the WD can be configured to measure and report 3GPP Rel-15 L1-RSRP for one or more SSBs associated with a non-serving cell. Which serving cell an SSB is associated with is indicated via RRC signaling, where each SSB is paired with a PCI. The maximum number of PCIs different from the serving cell that can be used for SSB measurement / reporting depends on the WD capability and can be one of 0, 1, 2, 3, and 7. Beam indication for inter-cell beam management will operate in the same manner as the intra-cell 3GPP Rel-17 Unified TCI State Framework.

[0077] The DL QCL and UL spatial relationship rules used for inter-cell beam management will operate in the same way as the 3GPP Rel-17 Unified TCI state framework within the cell.

[0078] Mobility measurements in LTE and NR

[0079] The WD can be configured by the network to perform measurements of the serving cell and neighboring cells by sending a measurement configuration, which is provided in an RRCReconfiguration message (in the case of NR) or an RRCConnectionReconfiguration message (for LTE) or as part of broadcast system information. Based on this measurement configuration provided by the network, the WD also reports measurement information to the network using a Measurement Report RRC message. The network then typically uses the measurement report to trigger a handover of the WD to a neighboring cell.

[0080] Neighboring cell measurements are categorized as intra-frequency, inter-frequency, or RAT-inter-frequency measurements.

[0081] WD measurement is defined as the object of measurement, which is part of the measurement configuration. The object of measurement is:

[0082] • For LTE: Carrier frequency

[0083] • For NR: the frequency / time position of the reference signal and the subcarrier spacing.

[0084] The measurement targets can be refined by listing cells (such as allowed cells and / or excluded cells) and specific offsets for those cells. Excluded cells (also known as blacklisted cells) are not considered in event assessments or measurement reports. If configured this way, allowed (also known as whitelisted) cells can be those considered only for event assessments and measurement reports. If neither allowed nor excluded cells are configured, WD considers all detected cells in event assessments and measurement reports.

[0085] The measurement configuration also includes a reporting configuration, which consists of a reporting standard (used to trigger a report) and a reporting format (which quantities to include in the report). The reporting standard can be "periodic" or "single-event". The reported quantity can be, for example, the Reference Signal Received Power (RSRP).

[0086] The measurement configuration also includes a list of measurement identifiers, where each identifier links a measurement object to a report configuration. By configuring multiple measurement identifiers, it is possible to link more than one measurement object to the same report configuration, and more than one report configuration to the same measurement object. Measurement identifiers are also included in the measurement report that triggers the report, serving as a reference for the network.

[0087] The measurement configuration also includes quantity configuration, which defines measurement filtering configurations for all event assessments and related reports, as well as for periodic reports of the measurement.

[0088] Finally, the measurement configuration includes the measurement interval, which is the time period during which WD can perform measurements.

[0089] In the case of the single-event reporting standard, there are many event types defined to trigger measurement reporting, see, for example, Section 5.5.4 of 3GPP TS 38.331 V16.7.0. Below are examples of two event types:

[0090] Figure 7 This is an example of triggering event A3. Event A3 (for LTE, it is also referred to as "the neighbor becomes better than the SpCell by an offset"). In the case of NR, it is also referred to as "the neighbor becomes better than the PCell / PSCell by an offset". The offset is the cell-specific offset portion of the measurement object corresponding to a particular neighbor cell.

[0091] Figure 8This is an example of triggering event A5. Event A5: For LTE, it is also referred to as "SpCell becomes worse than threshold 1 and the neighbor becomes better than threshold 2". In the case of NR, it is also referred to as "PCell / PSCell becomes worse than threshold 1 and the neighbor becomes better than threshold 2". The thresholds are part of the reporting configuration.

[0092] As part of the configuration for events A3, A5, and other event types, hysteresis can also be included. Hysteresis is useful in conjunction with the "reportOnLeave" configuration, where WD sends a report when the trigger quantity of the measured object stops meeting the criteria used for reporting (and hysteresis is taken into account). For example, also as... Figure 7 As shown in the diagram, when “reportOnLeave” is applied on event A3 for a neighboring cell, WD sends a measurement report when the neighboring cell is below the serving cell plus offset minus hysteresis.

[0093] WD-initiated beam management procedure

[0094] The beam management process initiated by the WD is one of the popular candidate agenda items for NR version 19 MIMO. Discussions on the WD side regarding the initiation behavior include at least three variations, which we define below:

[0095] 1. Beam Report Initiated by WD

[0096] 2. Beam indication initiated by WD

[0097] 3. Beam switching initiated by WD.

[0098] WD-initiated beam report

[0099] For the procedure “WD-initiated beam report”, it is assumed that WD triggers the beam report based on one or more triggering conditions. The beam report may or may not include information about the new preferred beam. The network can then use other conventional beam management operations to switch beams or perform additional beam scanning procedures. Figure 9 The diagram illustrates an example of this process. Note that in this solution, the network uses, for example... Figure 9 The TCI status indicator shown indicates the preferred beam. Compared to traditional beam reporting solutions (such as configuring periodic beam reporting), this solution can have the benefit of reduced network latency and signaling overhead. This is because WD only reports beams when one or more triggering conditions are met.

[0100] WD-initiated beam indication

[0101] For the procedure “WD-initiated beam indication”, the WD should include the preferred new candidate beam in the WD-initiated beam indication report. In addition, the WD should store the QCL-related information of the indicated preferred candidate beam, so that the WD can perform fast beam switching after the network has sent a response / acknowledgment to the WD-initiated beam indication report. Figure 10 The diagram illustrates an example of this process. However, in cases such as... Figure 10 In the solution shown, there is no TCI status indication from the network to the WD. The network only confirms the preferred candidate beams indicated by the WD in the beam indication report. Figure 9 Compared to the solution in the previous one, the main benefit of this solution is that it reduces beam activation time.

[0102] WD-initiated beam switching

[0103] For the procedure "WD-Initiated Beam Switching," the WD should include the preferred new candidate beam in its WD-Initiated Beam Switching report, and immediately after sending the report, the WD should apply the TCI state associated with the indicated preferred candidate beam. In some cases, the network may require an additional response / acknowledgment to indicate to the WD that it should continue using the newly applied TCI state associated with the preferred candidate beam in the WD-Initiated Beam Switching report. Otherwise, the WD should switch back to the previously used TCI state. Figure 11 The diagram illustrates an example of this process.

[0104] The beam management process initiated by the WD is a candidate agenda item for NR version 19 MIMO. Discussions regarding the WD-side initiating this behavior include at least three variations: WD-initiated beam reporting, WD-initiated beam indication, and WD-initiated beam switching. Regarding WD-initiated beam indication, the questions are how long the WD should retain QCL-related information and how to ensure agreement between the network and the WD on beam switching delays to mitigate the risk of beam misalignment between the network and the WD (which could lead to link disruptions).

[0105] Another issue concerning all these UE-initiated beam management procedures is how to control when and how often a UE should be allowed to send a UE-initiated beam report, beam indication report, or beam switching report. Without proper control over when and how often a UE performs such beam reports, all three UE-initiated beam management procedures described above could result in numerous reports when triggering conditions are met. Therefore, how to control the frequency of such UE-initiated beam reports remains an open question. Summary of the Invention

[0106] Some embodiments advantageously provide methods, systems, and apparatus for beam management processes initiated by a wireless device. One or more embodiments provide a timing indication for determining a beam switching delay for a beam indication initiated by a WD. In some embodiments, timing methods are described. These methods include determining how long the WD stores QCL-related information associated with the indicated beam(s) in one or more previously initiated beam indication reports by the WD. In some other embodiments, beam switching time and beam application time are determined based on when the network signals back a beam report response / acknowledgment.

[0107] One benefit of this implementation is the introduction of a timing line for beam reports initiated by the WD, aligning with expectations at both the network and the WD. Another advantage is the avoidance of outdated signaling (e.g., the WD being pre-synchronized or updated to a new beam before the network confirms the beam indication for a previously reported beam (pre-synchronization)) and maintaining consistency in the understanding of beam switching timing.

[0108] According to one aspect, a method is described in a WD configured to perform a beam management procedure initiated by a wireless device (WD) and communicate with a network node. The method includes determining one or more of the following based on one or more parameters: (A) a first timing indication indicating a beam switching delay associated with a beam report initiated by the WD; (B) a second timing indication indicating when to perform a backoff beam switching associated with the beam management procedure initiated by the WD; and (C) a third timing indication indicating a minimum time between two beam reports initiated by the WD. The method also includes performing one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication.

[0109] In some embodiments, the beam report initiated by WD indicates one or more beams.

[0110] In some other embodiments, the method further includes one or more of the following: (A) sending a fourth indication instructing the WD to signal the WD-initiated beam report; (B) sending the WD-initiated beam report; (C) receiving from the network node a fifth indication instructing one or both of the WD-initiated beam report acknowledgment and the beam (e.g., the serving beam); (D) determining one or both of the beam switching delay and the beam application time based on when the WD-initiated beam report acknowledgment is received; and (E) applying a spatial filter in response to the fifth indication and the determined beam switching delay and the beam application time.

[0111] In some embodiments, the method further includes: when the first timing indication is determined: (A) determining a storage period for which the WD will store quasi-co-location (QCL) related information associated with one or more beams indicated in a beam report initiated by the WD; and (B) storing the QCL related information during the storage period.

[0112] In some other embodiments, the method further includes: using the QCL-related information to switch to a beam among the one or more beams indicated in the beam switching report initiated by the WD within the beam switching delay.

[0113] In some embodiments, performing the backoff beam switching includes: switching from a first beam to a second beam indicated in a beam report initiated by the WD, and switching back to the first beam if the WD does not receive a beam switching response from the network node after a predetermined time has elapsed.

[0114] In some other embodiments, the method further includes receiving from the network node an indication of a backoff timing configuration corresponding to the predetermined time. The sixth instruction of ).

[0115] In some embodiments, the third timing indication is determined based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication indicating to the network node that the WD has at least one WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (E) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0116] In some other embodiments, the method further includes: when the WD is configured with separate downlink and uplink transmission configuration indicator (TCI) states, determining (e.g., obtaining, receiving, etc.) a second configuration, the second configuration configuring the WD with joint or separate timing constraints associated with the third timing indication for the downlink service link and the uplink service link.

[0117] In some embodiments, the method further includes: determining (e.g., obtaining, receiving, etc.) a third configuration, the third configuration being the maximum number of beam reports initiated by the WD to the WD configuration within a time period.

[0118] In some other embodiments, the one or more parameters include one or more of the following: (A) timing information associated with signaling between the WD and the network node; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0119] In some embodiments, the one or more actions include one or more of the following: (A) if the network node indicates to the WD the beam indicated in the beam report initiated by the WD, then switch to the beam within the beam switching delay; (B) switch to the beam indicated in response to sending the beam report initiated by the WD, and if no switching response is received from the network node, perform the backoff handover associated with the beam management procedure initiated by the WD; and (C) send at least one beam report initiated by the WD based on the third timing indication.

[0120] In one or more embodiments, the WD may remain in the switched beam or continue using the switched beam after receiving an acknowledgment (ACK), perform a switch to the beam included in the non-ACK (NACK) message by the network node, and / or perform a fallback to the previous serving beam if there is only a NACK without a new beam or no feedback from the network node.

[0121] According to another aspect, a WD is configured to perform a beam management procedure initiated by a wireless device (WD) and communicate with a network node. The WD is configured to determine one or more of the following based on one or more parameters: (A) a first timing indication indicating a beam switching delay associated with a beam report initiated by the WD; (B) a second timing indication indicating when to perform a backoff beam switching associated with the beam management procedure initiated by the WD; and (C) a third timing indication indicating the minimum time between two beam reports initiated by the WD. The WD is also configured to perform one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication.

[0122] In some embodiments, the beam report initiated by WD indicates one or more beams.

[0123] In some other embodiments, the WD is also configured to perform one or more of the following: (A) sending a fourth indication instructing the WD to signal the WD-initiated beam report; (B) sending the WD-initiated beam report; (C) receiving from the network node a fifth indication instructing the WD-initiated beam report acknowledgment and one or both of the beams; (D) determining one or both of the beam switching delay and beam application time based on when the WD-initiated beam report acknowledgment is received; and (E) applying a spatial filter in response to the fifth indication and the determined beam switching delay and beam application time.

[0124] In some embodiments, the WD is further configured to, when the first timing indication is determined: (A) determine a storage period for which the WD will store quasi-co-location (QCL) related information associated with one or more beams indicated in a beam report initiated by the WD; and (B) store the QCL related information during the storage period.

[0125] In some other embodiments, the WD is also configured to use the QCL-related information to switch to one or more beams indicated in the beam report initiated by the WD during the beam switching delay.

[0126] In some embodiments, performing the backoff beam switching includes: switching from a first beam to a second beam indicated in a beam report initiated by the WD, and switching back to the first beam if the WD does not receive a beam switching response from the network node after a predetermined time has elapsed.

[0127] In some other embodiments, the WD is also configured to receive from the network node an indication of a backoff timing configuration corresponding to the predetermined time. The sixth instruction of ).

[0128] In some embodiments, the third timing indication is determined based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication indicating to the network node that the WD has at least one WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (D) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0129] In some other embodiments, the WD is also configured to determine a second configuration when the WD is configured with separate downlink and uplink transmission configuration indicator (TCI) states, the second configuration configuring the WD with joint or separate timing limits associated with the third timing indication for the downlink service link and the uplink service link.

[0130] In some embodiments, the WD is further configured to determine a third configuration that configures the WD to send a maximum number of beam reports initiated by the WD within a time period.

[0131] In some other embodiments, the one or more parameters include one or more of the following: (A) timing information associated with signaling between the WD and the network node; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0132] In some embodiments, the one or more actions include one or more of the following: (A) if the network node indicates to the WD the beam indicated in the beam report initiated by the WD, then switch to the beam within the beam switching delay; (B) switch to the beam indicated in response to sending the beam report initiated by the WD, and if no switching response is received from the network node, perform the backoff handover associated with the beam management procedure initiated by the WD; and (C) send at least one beam report initiated by the WD based on the third timing indication.

[0133] In one or more embodiments, the WD may remain in the switched beam or continue using the switched beam after receiving an acknowledgment (ACK), perform a switch to the beam included in the non-ACK (NACK) message by the network node, and / or perform a fallback to the previous serving beam if there is only a NACK without a new beam or no feedback from the network node.

[0134] According to one aspect, a method is described in a network node configured to perform a beam management procedure initiated by a WD and to communicate with the WD. The method includes receiving a WD-initiated beam report from the WD, wherein the WD-initiated beam report is associated with one or more of the following: a first timing indication indicating a beam switching delay; a second timing indication indicating when to perform a backoff beam switching associated with the WD-initiated beam management procedure; and a third timing indication indicating a minimum time between two WD-initiated beam reports. The method further includes determining a beam based on the WD-initiated beam report, and one or both of the following: sending a beam indication to the WD indicating the beam, and sending a WD switching response indicating a switch to the beam.

[0135] In some embodiments, the beam report initiated by the WD indicates one or more beams.

[0136] In some other embodiments, the method further includes one or more of the following: (A) receiving a fourth indication that the WD will signal a beam report initiated by the WD; (B) receiving a beam report initiated by the WD; (C) sending a fifth indication to the WD indicating a beam report acknowledgment initiated by the WD and one or both of the beams; and (D) causing the WD to determine one or both of the beam switching delay and beam application time based on when the beam report acknowledgment initiated by the WD is received, and applying a spatial filter in response to the fifth indication and the determined beam switching delay and beam application time.

[0137] In some embodiments, the transmitted beam indication triggers the WD to perform one or more of the following: (A) determining a storage period for which the WD will store quasi-co-location (QCL) related information associated with one or more beams indicated in the beam report initiated by the WD; (B) storing the QCL related information during the storage period; and (C) using the QCL related information to switch to a beam among the one or more beams indicated in the beam report initiated by the WD during the beam switching delay.

[0138] In some other embodiments, performing the backoff beam switching includes: switching from a first beam to a second beam indicated in the beam report initiated by the WD, and switching back to the first beam if the WD does not receive a beam switching response from the network node after a predetermined time has elapsed.

[0139] In some embodiments, the method further includes sending a backoff timing configuration corresponding to the predetermined time to the WD. The sixth instruction of ).

[0140] In some other embodiments, the third timing indication is based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication instructing the network node that the WD has a WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (D) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0141] In some embodiments, when the WD is configured with separate downlink and uplink transmission configuration indicator (TCI) states, the WD is configured with a second configuration, the second configuration including joint or separate timing limits for the downlink service link and the uplink service link associated with the third timing indication.

[0142] In some other embodiments, the WD is configured with a third configuration that includes a maximum number of beam reports initiated by the WD within a time period.

[0143] In some embodiments, one or more of the first timing indication, the second timing indication, and the third timing indication are based on one or more parameters, the one or more parameters including one or more of the following: (A) timing information associated with signaling between the WD and the network node; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0144] In some other embodiments, the method further includes performing one or more actions, including one or more of the following: (A) causing the WD to switch to the beam within the beam switching delay if the network node indicates to the WD the beam indicated in the beam report initiated by the WD; (B) causing the WD to switch to the beam indicated in response to sending the beam report initiated by the WD, and performing the backoff handover associated with the beam management procedure initiated by the WD if no handover response is received from the network node; and (C) receiving at least one beam report initiated by the WD based on the third timing indication.

[0145] According to another aspect, a network node configured to perform a beam management procedure initiated by a wireless device (WD) and communicate with the WD is described. The network node is configured to receive beam reports initiated by the WD from the WD, wherein the WD-initiated beam reports are associated with one or more of the following: a first timing indication indicating a beam switching delay; a second timing indication indicating when to perform a backoff beam switching associated with the WD-initiated beam management procedure; and a third timing indication indicating the minimum time between two WD-initiated beam reports. The network node is also configured to determine a beam based on the WD-initiated beam reports, and one or both of the following: sending a beam indication to the WD indicating the beam, and sending a WD switching response indicating a switch to the beam.

[0146] In some embodiments, the beam report initiated by the WD indicates one or more beams.

[0147] In some other embodiments, the network node is further configured to perform one or more of the following: (A) receiving a fourth indication that the WD will signal a beam report initiated by the WD; (B) receiving a beam report initiated by the WD; (C) sending a fifth indication to the WD indicating a beam report acknowledgment initiated by the WD and one or both of the beams; and (D) causing the WD to determine one or both of the beam switching delay and beam application time based on when the beam report acknowledgment initiated by the WD is received, and applying a spatial filter in response to the fifth indication and the determined beam switching delay and beam application time.

[0148] In some embodiments, the transmitted beam indication triggers the WD to perform one or more of the following: (A) determining a storage period for which the WD will store quasi-co-location (QCL) related information associated with one or more beams indicated in the beam report initiated by the WD; (B) storing the QCL related information during the storage period; and (C) using the QCL related information to switch to a beam among the one or more beams indicated in the beam report initiated by the WD during the beam switching delay.

[0149] In some other embodiments, performing the backoff beam switching includes: switching from a first beam to a second beam indicated in the beam report initiated by the WD, and switching back to the first beam if the WD does not receive a beam switching response from the network node after a predetermined time has elapsed.

[0150] In some embodiments, the network node is further configured to send a backoff timing configuration corresponding to the predetermined time to the WD. The sixth instruction of ).

[0151] In some other embodiments, the third timing indication is based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication instructing the network node that the WD has a WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (D) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0152] In some embodiments, when the WD is configured with separate downlink and uplink transmission configuration indicator (TCI) states, the WD is configured with a second configuration, the second configuration including joint or separate timing limits for the downlink service link and the uplink service link associated with the third timing indication.

[0153] In some other embodiments, the WD is configured with a third configuration that includes a maximum number of beam reports initiated by the WD within a time period.

[0154] In some embodiments, one or more of the first timing indication, the second timing indication, and the third timing indication are based on one or more parameters, the one or more parameters including one or more of the following: (A) timing information associated with signaling between the WD and the network node; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0155] In some other embodiments, the network node is further configured to perform one or more actions, including one or more of the following: (A) causing the WD to switch to the beam within the beam switching delay if the network node indicates to the WD the beam indicated in the beam report initiated by the WD; (B) causing the WD to switch to the beam indicated in response to sending the beam report initiated by the WD, and performing the backoff handover associated with the beam management procedure initiated by the WD if no handover response is received from the network node; and (C) receiving at least one beam report initiated by the WD based on the third timing indication. Attached Figure Description

[0156] A more complete understanding of this embodiment and its accompanying advantages and features will be more readily obtained by referring to the following detailed description when considered in conjunction with the accompanying drawings:

[0157] Figure 1 This example illustrates a two-stage TCI state update.

[0158] Figure 2 This shows an example TCI state activation / deactivation for a WD-specific PDSCH MAC CE;

[0159] Figure 3 Example DCI indication showing TCI status;

[0160] Figure 4 The example active TCI state and its mapping to TCI field code points are shown for “Joint DL / UL TCI”.

[0161] Figure 5 For “Joint DL / UL TCI”, other example active TCI states and their mappings to TCI field code points are shown;

[0162] Figure 6 The possible target RS, source RS, and corresponding QCL attributes supported for joint / DL-only TCI status indication are shown.

[0163] Figure 7 Example event A3 is shown;

[0164] Figure 8 Example event A5 is shown;

[0165] Figure 9 This shows an example of a beam report initiated by WD;

[0166] Figure 10 This shows a beam indication initiated by an example WD;

[0167] Figure 11 This illustrates a beam switching initiated by an example WD;

[0168] Figure 12 This is a schematic diagram of an example network architecture of a communication system connected to a host via an intermediate network according to the principles of this disclosure;

[0169] Figure 13 This is a block diagram of a network node communicating with a wireless device according to some embodiments of the present disclosure;

[0170] Figure 14 This is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0171] Figure 15This is a flowchart of an example process in a network node according to some embodiments of this disclosure;

[0172] Figure 16 This is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure.

[0173] Figure 17 This is a flowchart of an example process in a network node according to some embodiments of this disclosure;

[0174] Figure 18 This is a flowchart of an example process for a time limit of beam reporting initiated by a wireless device in a network node according to some embodiments of the present disclosure;

[0175] Figure 19 This is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0176] Figure 20 A flowchart illustrating an example process in a wireless device according to some embodiments of the present disclosure;

[0177] Figure 21 This is a flowchart of an example process in a network node according to some embodiments of this disclosure;

[0178] Figure 22 The steps of an example WD-initiated beam management process according to some embodiments of this disclosure are shown;

[0179] Figure 23 Example TCI states are shown according to some embodiments of this disclosure;

[0180] Figure 24 Other example TCI states according to some embodiments of this disclosure are shown;

[0181] Figure 25 An example WD-initiated beam reporting process is shown according to some embodiments of the present disclosure, wherein the beam is switched in response to network node confirmation;

[0182] Figure 26 The steps of an example method for a beam switching process initiated by the WD are shown;

[0183] Figure 27 The illustration shows confirmation messages received during the rollback period according to some embodiments of this disclosure;

[0184] Figure 28 This illustrates another example of the application of rollback periods according to some embodiments of this disclosure;

[0185] Figure 29Example WDs and example beam reports are shown, configured according to some embodiments of the present disclosure, with WD-initiated beam reports.

[0186] Figure 30 Another example of a WD and another example of a beam reporting configuration according to some embodiments of the present disclosure are shown;

[0187] Figure 31 This illustration shows an example report of a WD and a beam, configured with WD-initiated beam reporting according to some embodiments of this disclosure; and

[0188] Figure 32 Another example report of a WD and a beam is shown, configured according to some embodiments of the present disclosure, with WD-initiated beam reporting. Detailed Implementation

[0189] Before describing the exemplary embodiments in detail, it should be noted that the embodiments primarily exist in combinations of apparatus components and processing steps associated with a beam management process initiated by a wireless device. Therefore, components have been indicated by conventional symbols in the accompanying drawings where appropriate, with only those specific details relevant to understanding the embodiments shown so as not to obscure this disclosure with details that would be readily apparent to those skilled in the art who benefit from the description herein. Throughout the description, the same numbers denote the same elements.

[0190] As used herein, relational terms such as “first” and “second,” “top” and “bottom,” etc., may be used only to distinguish one entity or element from another, and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the concepts described herein. As used herein, the singular forms “a” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “comprising” and / or “including” as used herein specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0191] In the embodiments described herein, connection terms such as "communicating with" can be used to indicate electrical or data communication, which can be achieved, for example, through physical contact, induction, electromagnetic radiation, radio signal transmission, infrared signal transmission, or optical signal transmission. Those skilled in the art will understand that multiple components can interoperate, and modifications and variations in achieving electrical and data communication are possible.

[0192] In some embodiments described herein, the terms “coupled,” “connected,” etc., may be used herein to indicate a connection, although not necessarily a direct one, and may include wired and / or wireless connections.

[0193] As used herein, the term "network node" can refer to any type of network node included in a radio network, and may further include any of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g node B (gNB), evolved node B (eNB or eNodeB), node B, multi-standard radio (MSR) radio node (such as MSR BS), multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node control relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH). Core network nodes (e.g., mobility management entity (MME), ad hoc network (SON) node, coordination node, location node, MDT node, etc.), external nodes (e.g., third-party nodes, nodes outside the current network), nodes in distributed antenna systems (DAS), spectrum access systems (SAS) nodes, element management systems (EMS), etc. Network nodes may also include test equipment. The term “radio node” as used in this article may also be used to refer to a wireless device (WD) (such as a wireless device (WD)) or a radio network node.

[0194] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) may be used interchangeably. A WD as used herein can be any type of wireless device capable of communicating with a network node or another WD via radio signals, such as a wireless device (WD). A WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0195] Furthermore, in some embodiments, the generic term "radio network node" is used. It can be any kind of radio network node, which may include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), and remote radio head (RRH).

[0196] Note that although terms from a particular wireless system (such as 3GPP LTE and / or New Radio (NR)) may be used in this disclosure, this should not be construed as limiting the scope of this disclosure to the systems mentioned above. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Global Microwave Access Interoperability (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas covered in this disclosure.

[0197] It should be noted further that the functions described herein as being performed by wireless devices or network nodes can be distributed across multiple wireless devices and / or network nodes. In other words, it is conceivable that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, and in fact, can be distributed among several physical devices.

[0198] In some embodiments, the term "QCL" refers to quasi-co-location. For example, QCL-related information may refer to location-related information. In other embodiments, QCL may refer to quasi-co-location. For example, an antenna port may be quasi-co-located.

[0199] In some embodiments, the term "between two beam reports initiated by two WDs" is used, and can refer to the time between two beam reports initiated by two WDs when there are more than two WD-initiated reports. For example, the minimum time between two beam reports initiated by two WDs can refer to the minimum time between two beam reports initiated by two WDs or the minimum time between two of more than two WD-initiated beam reports. That is, the embodiments are not limited to the existence of only two WD-initiated beam reports.

[0200] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms used herein shall be interpreted as having the same meaning as they have in the context of this specification and the relevant field, and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0201] Returning to the accompanying drawings, in which the same elements are referred to by the same reference numerals, Figure 12 The diagram illustrates a communication system 10 according to an embodiment. The communication system 10 is, for example, a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), comprising an access network 12 (such as a radio access network) and a core network 14. The access network 12 includes multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16) in each custom corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18), such as NB, eNB, gNB, or other types of wireless access points. Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to or be paged by a corresponding network node 16a. A second WD 22b in coverage area 18b can wirelessly connect to a corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is located in the coverage area or a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0202] Furthermore, it is conceivable that WD 22 can communicate simultaneously with more than one network node 16 and more than one type of network node 16, and / or be configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, WD 22 can have dual connectivity with LTE-enabled network node 16 and the same or different network nodes 16 that support NR. As an example, WD 22 can communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0203] The communication system 10 can connect to the host 24, which can be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host 24 can be under the ownership or control of a service provider, or can be operated by or on behalf of the service provider. Connections 26, 28 between the communication system 10 and the host 24 can extend directly from the core network 14 to the host 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be one or more of public, private, or hosted networks. The intermediate network 30, if present, can be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0204] Network node 16 is configured to include an NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, such as NN functions. Wireless device 22 is configured to include a WD management unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, such as WD functions.

[0205] Now refer to Figure 13 An example implementation of the WD 22, network node 16, and host 24 discussed in the preceding paragraphs is described according to an embodiment.

[0206] The communication system 10 includes a network node 16 disposed within the communication system 10 and includes hardware 58 enabling it to communicate with the host 24 and WD 22. Hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 10, and a radio interface 62 (which includes one or more antennas 76) for establishing and maintaining at least a wireless connection 64 with WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0207] In the illustrated embodiment, the hardware 58 of network node 16 also includes processing circuitry 68. Processing circuitry 68 may include a processor 70 and memory 72. Specifically, in addition to or as an alternative to a processor (such as a central processing unit) and memory, processing circuitry 68 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores adapted to execute instructions and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits). Processor 70 may be configured to access memory 72 (e.g., write to and / or read from memory 72), and memory 72 may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0208] Therefore, network node 16 also has software 74, which is internally stored, for example, in memory 72, or in external memory (e.g., a database, storage array, network storage device, etc.) accessible to network node 16 via an external connection. Software 74 can be executed by processing circuitry 68. Processing circuitry 68 can be configured to control any methods and / or processes described herein, and / or cause such methods and / or processes to be executed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. Memory 72 is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of network node 16 may include NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features, such as NN functions, described in this disclosure.

[0209] The communication system 10 also includes the previously mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with network nodes 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be configured as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0210] The hardware 80 of the WD 22 also includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. Specifically, in addition to or as an alternative to a processor (such as a central processing unit) and memory, processing circuitry 84 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores adapted to execute instructions and / or FPGAs (Field-Programmable Gate Arrays) and / or ASICs (Application-Specific Integrated Circuits). Processor 86 may be configured to access memory 88 (e.g., write to and / or read from memory 88), and memory 88 may include any kind of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0211] Therefore, WD 22 may also include software 90, which is stored, for example, in memory 88 at WD 22, or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by WD 22. Software 90 may be executed by processing circuitry 84. Software 90 may include client application 92. Client application 92 may be operable to provide services to human or non-human users via WD 22.

[0212] Processing circuitry 84 may be configured to control any methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD 22 described herein. WD 22 includes memory 88 configured to store data, programming software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, processing circuitry 84 of wireless device 22 may include WD management unit 34 configured to perform any steps and / or tasks and / or processes and / or methods and / or features, such as WD functions, described in this disclosure.

[0213] In some embodiments, the internal operation of network node 16 and WD 22 can be as follows: Figure 13 As shown, and independently, the surrounding network topology can be Figure 12 The network topology.

[0214] In some embodiments, the cellular network further includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured and / or its processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to the WD 22, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from the WD 22.

[0215] In some embodiments, WD 22 is configured to perform the following operations and / or include a radio interface 82 and / or processing circuitry 84 configured to perform the following operations: perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / terminating reception of transmissions from network node 16.

[0216] although Figure 12 and Figure 13Various "units," such as NN management unit 32 and WD management unit 34, are shown as residing within their respective processors; however, it is conceivable that these units could be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units can be implemented within the processing circuitry in hardware or a combination of hardware and software.

[0217] Figure 14 This is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of processing circuitry 84 (including WD management unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 may be configured, such as via processing circuitry 84 and / or processor 86 and / or radio interface 82, to determine (block S100) a time period in which the WD will store quasi-co-location (QCL) related information associated with one or more beams indicated in a beam indication report initiated by the WD, and to perform (block S102) one or more actions based on the determined time period.

[0218] In some embodiments, the method includes one or more of the following: sending a first indication that WD 22 will signal a WD-initiated beam report; signaling a WD-initiated beam report; receiving from network node 16 a second indication of a WD-initiated beam report acknowledgment and one or both of the beams; applying a spatial filter in response to the second indication; and determining beam switching time and beam application time based on when network node 16 signals a WD-initiated beam report acknowledgment.

[0219] In some other embodiments, the time period for which WD 22 stores QCL-related information is based on the time delay between WD 22 signaling a beam report initiated by WD and receiving a second indication.

[0220] Figure 15This is a flowchart of an example process in network node 16. One or more blocks described herein can be executed by one or more elements of network node 16, such as one or more of processing circuitry 68 (including NN management unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to receive (block S104) a beam report initiated by WD, and cause to send (block S106) a second indication to WD 22 indicating WD-initiated beam report acknowledgment and one or both of the beams. The second indication can be used by WD 22 to determine the time period during which WD 22 will store quasi-co-location (QCL) related information associated with the beams of one or more indications in the WD-initiated beam indication report. Network node 16 is also configured to perform (block S108) one or more actions based on the second indication and the time period.

[0221] In some embodiments, the method further includes receiving a first indication that the WD will signal a beam report initiated by the WD.

[0222] In some other embodiments, the second indication can be used by WD 22 to determine the beam switching time and beam application time based on when the network node signals the WD-initiated beam report confirmation.

[0223] Figure 16 This is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be executed by one or more elements of the wireless device 22, such as one or more of processing circuitry 84 (including WD management unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 is configured, for example via processing circuitry 84 and / or processor 86 and / or radio interface 82, to send (block S110) a beam-switching report associated with a beam-switching from a first beam to a second beam initiated by the WD to network node 16. The first beam and the second beam may be used by the WD 22 to communicate with network node 16. The wireless device 22 is also configured to switch from the first beam (block S112) to the second beam and switch back (block S114) to the first beam if the WD 22 does not receive a beam-switching response from network node 16 after a predetermined time instance has elapsed.

[0224] In some embodiments, the method further includes receiving from network node 16 an indication of a backoff timing configuration corresponding to a predetermined time instance. (instructions).

[0225] In some other embodiments, It is associated with one or more of the following: carrier frequency, parameter set, bandwidth portion, time division duplex (TDD) mode, transmission direction, and reference signal configuration.

[0226] In some embodiments, the method further includes transmitting a WD capability indication indicating one or more of the following: (A) support for WD-initiated beam switching, including (a) the range or parameter set; (b) separate parameters for WD-initiated downlink beam switching and WD-initiated uplink beam switching. Configuration support; and (C) for Support for delayed configuration.

[0227] In some other embodiments, the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0228] Figure 17 This is a flowchart of an example process in network node 16. One or more blocks described herein can be executed by one or more elements of network node 16, such as processing circuitry 68 (including NN management unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, for example via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to send (block S116) information to WD 22 associated with a predetermined time instance corresponding to a beam switching from a first beam to a second beam initiated by WD. The first and second beams can be used by network node 16 to communicate with WD 22, and the predetermined time instance can be used by WD 22 to switch back to the first beam if WD does not receive a beam switching response from the network node after the predetermined time instance has elapsed. The network node is also configured to communicate with WD 22 using one of the first and second beams (block S118).

[0229] In some embodiments, the method further includes sending an indication to WD 22 of a rollback timing configuration corresponding to a predetermined time instance. (instructions).

[0230] In some other embodiments, It is associated with one or more of the following: carrier frequency, parameter set, bandwidth portion, time division duplex (TDD) mode, transmission direction, and reference signal configuration.

[0231] In some embodiments, the method further includes receiving a WD capability indication indicating one or more of the following: (A) support for WD-initiated beam switching, including (a) the range or parameter set; (b) separate parameters for WD-initiated downlink beam switching and WD-initiated uplink beam switching. Configuration support; and (C) for Support for delayed configuration.

[0232] In some other embodiments, the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0233] Figure 18 This is a flowchart of an example process for time constraints of beam reports initiated by a wireless device (WD) in network node 16. One or more blocks described herein can be executed by one or more elements of network node 16, such as processing circuitry 68 (including configuration unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, for example via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to configure (block S120) the beam report configuration initiated by the WD to WD 22. This process includes receiving (block S122) a first WD-initiated beam report configured according to the WD-initiated beam report configuration.

[0234] In some embodiments, the WD-initiated beam report configuration includes a time limit T1, indicating the minimum time WD 22 must wait before triggering a first WD-initiated beam report. In some embodiments, the WD-initiated beam report configuration includes a time limit T1, indicating the minimum time WD 22 must wait before sending an indication to the method that signals the next WD-initiated beam report. In some embodiments, the time limit T1 depends on at least one of a parameter set of at least one downlink reference signal or a subcarrier spacing. In some embodiments, the WD-initiated beam report configuration includes a time limit T2, indicating the minimum time WD 22 must wait before triggering a second WD-initiated beam report. In some embodiments, the first and second WD-initiated beam reports indicate the same preferred beam. In some embodiments, the WD-initiated beam report configuration includes a maximum number of WD-initiated beam reports to be reported within a duration T5.

[0235] Figure 19This is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of processing circuitry 84 (including beam reporting unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 is configured, for example via processing circuitry 84 and / or processor 86 and / or radio interface 82, to receive (block S124) a beam reporting configuration initiated by a WD from network node 16. This process includes transmitting (block S126) a first WD-initiated beam report configured according to the WD-initiated beam reporting configuration.

[0236] In some embodiments, the WD-initiated beam report configuration includes a time limit T1, indicating the minimum time WD 22 must wait before triggering a first WD-initiated beam report. In some embodiments, the WD-initiated beam report configuration includes a time limit T1, indicating the minimum time WD 22 must wait before sending an indication to the method that signals the next WD-initiated beam report. In some embodiments, the time limit T1 depends on at least one of a parameter set of at least one downlink reference signal or a subcarrier spacing. In some embodiments, the WD-initiated beam report configuration includes a time limit T2, indicating the minimum time WD 22 must wait before triggering a second WD-initiated beam report. In some embodiments, the first and second WD-initiated beam reports indicate the same preferred beam. In some embodiments, the WD-initiated beam report configuration includes a maximum number of WD-initiated beam reports to be reported within a duration T5.

[0237] Figure 20 A flowchart illustrating example processes in a wireless device 22 according to some embodiments of the present disclosure is shown. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as one or more of processing circuitry 84 (including beam reporting unit 34), processor 86, radio interface 82, and / or communication interface 60. The wireless device 22 is configured, such as via processing circuitry 84 and / or processor 86 and / or radio interface 82, to determine (block S128) one or more of the following based on one or more parameters: (A) a first timing indication indicating a beam switching delay associated with a beam report initiated by the WD; (B) a second timing indication indicating when to perform a backoff beam switching associated with a beam management procedure initiated by the WD; and (C) a third timing indication indicating the minimum time between two beam reports initiated by the WD. The WD 22 is also configured to perform (block S130) one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication.

[0238] In some embodiments, the beam report initiated by WD indicates one or more beams.

[0239] In some other embodiments, the method further includes one or more of the following: (A) sending a fourth indication that instructs the WD to signal a WD-initiated beam report; (B) sending a WD-initiated beam report; (C) receiving a fifth indication from network node 16 that instructs one or both of a WD-initiated beam report acknowledgment and a beam (e.g., a serving beam); (D) determining one or both of a beam switching delay and a beam application time based on when the WD-initiated beam report acknowledgment is received; and (E) applying a spatial filter in response to the fifth indication and one or both of the determined beam switching delay and beam application time.

[0240] In some embodiments, the method further includes: when a first timing indication is determined: (A) determining a storage period for which WD 22 will store quasi-co-location (QCL) related information associated with one or more beams indicated in a beam report initiated by WD; and (B) storing the QCL related information during the storage period.

[0241] In some other embodiments, the method further includes, within a beam-switching delay, using QCL-related information to switch to one or more beams indicated in a beam report initiated by the WD.

[0242] In some embodiments, performing a backoff beam switch includes switching from a first beam to a second beam indicated in a beam report initiated by the WD, and switching back to the first beam if the WD does not receive a beam switch response from the network node after a predetermined time has elapsed.

[0243] In some other embodiments, the method further includes receiving from a network node an indication of a backoff timing configuration corresponding to a predetermined time. The sixth instruction of ).

[0244] In some embodiments, the third timing indication is determined based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication indicating to network node 16 that WD 22 has at least one WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (E) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0245] In some other embodiments, the method further includes determining (e.g., obtaining, receiving, etc.) a second configuration when the WD 22 is configured with separate downlink and uplink transmission configuration indicator (TCI) states, which configures the WD 22 with joint or separate timing constraints associated with a third timing indication for the downlink service link and the uplink service link.

[0246] In some embodiments, the method further includes determining (e.g., obtaining, receiving, etc.) a third configuration that configures the maximum number of beam reports initiated by the WD within a time period to the WD 22.

[0247] In some other embodiments, one or more parameters include one or more of the following: (A) timing information associated with signaling between WD 22 and network node 16; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0248] In some embodiments, the one or more actions include one or more of the following: (A) if network node 16 indicates to WD 22 the beam indicated in the beam report initiated by WD, then switch to that beam within the beam switching delay; (B) switch to the beam indicated in response to sending the beam report initiated by WD, and if no switching response is received from the network node, perform a backoff handover associated with the beam management procedure initiated by WD; and (C) send at least one beam report initiated by WD based on a third timing indication.

[0249] In one or more embodiments, WD 22 may remain in the switched beam or continue using the switched beam after receiving an acknowledgment (ACK), perform a switch to the beam included in the non-ACK (NACK) message by network node 16, and / or perform a fallback to the previous serving beam if there is only a NACK and no new beam or no feedback from network node.

[0250] Figure 21This is a flowchart of an example process for timing constraints of beam reports initiated by a wireless device (WD) in network node 16. One or more blocks described herein can be executed by one or more elements of network node 16, such as processing circuitry 68 (including configuration unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to receive (block S132) beam reports initiated by WD from WD 22, wherein the beam reports initiated by WD are associated with one or more of the following: a first timing indication indicating a beam switching delay; a second timing indication indicating when to perform a backoff beam switching associated with a WD-initiated beam management process; and a third timing indication indicating the minimum time between two WD-initiated beam reports. Network node 16 is also configured to determine (box S134) a beam based on a beam report initiated by WD, and one or both of the following: sending a beam indication to WD 22 indicating the beam, and sending a WD handover response to WD 22 indicating a switch to the beam (box S136).

[0251] In some embodiments, the beam report initiated by WD indicates one or more beams.

[0252] In some other embodiments, the method further includes one or more of the following: (A) receiving a fourth instruction instructing WD 22 to signal a WD-initiated beam report; (B) receiving a WD-initiated beam report; (C) sending a fifth instruction to WD 22 instructing one or both of a WD-initiated beam report acknowledgment and a beam; and (D) causing WD (22) to determine one or both of a beam switching delay and a beam application time based on when a WD-initiated beam report acknowledgment is received, and applying a spatial filter in response to the fifth instruction and the determined one or both of the beam switching delay and beam application time.

[0253] In some embodiments, the transmitted beam indication triggers WD 22 to perform one or more of the following: (A) determining a storage period during which WD 22 will store quasi-co-location (QCL) related information associated with one or more beams indicated in the WD-initiated beam report; (B) storing the QCL related information during the storage period; and (C) switching to a beam in one or more beams indicated in the WD-initiated beam report using the QCL related information within the beam switching delay.

[0254] In some other embodiments, performing a backoff beam switch includes switching from the first beam to the second beam indicated in the beam report initiated by the WD, and switching back to the first beam if the WD 22 does not receive a beam switch response from the network node 16 after a predetermined time has elapsed.

[0255] In some embodiments, the method further includes sending a backoff timing configuration corresponding to a predetermined time to the WD 22. The sixth instruction of ).

[0256] In some other embodiments, the third timing indication is based on the first configuration, and the third timing indication indicates one or more of the following: (A) the minimum time between two sequential WD-initiated beam reports; (B) the minimum time between two sequential fourth indications, each fourth indication indicating to the network node that WD 22 has a WD-initiated beam report to send; (C) the minimum time between two WD-initiated beam reports indicating the same preferred candidate beam; and (E) the minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

[0257] In some embodiments, when WD 22 is configured with separate downlink and uplink Transport Configuration Indicator (TCI) states, WD is configured with a second configuration that includes joint or separate timing constraints associated with a third timing indication for the downlink service link and the uplink service link.

[0258] In some other embodiments, WD 22 is configured with a third configuration that includes a maximum number of beam reports initiated by WD within a time period.

[0259] In some embodiments, one or more of the first timing indication, the second timing indication, and the third timing indication are based on one or more parameters, including one or more of the following: (A) timing information associated with signaling between WD 22 and network node 16; (B) carrier frequency; (C) parameter set; (D) bandwidth portion; (E) time division duplex (TDD) mode; (F) transmission direction; (G) reference signal configuration; and (H) subcarrier spacing of at least one downlink reference signal.

[0260] In some other embodiments, the method further includes performing one or more actions, including one or more of the following: (A) causing WD 22 to switch to the beam within a beam switching delay if the network node 16 indicates to WD 22 the beam indicated in the beam report initiated by WD; (B) causing WD 22 to switch to the beam indicated in response to sending the beam report initiated by WD, and performing a backoff handover associated with the beam management procedure initiated by WD if no handover response is received from the network node; and (C) receiving at least one beam report initiated by WD based on a third timing indication.

[0261] Having described the general process flow of the arrangements of this disclosure and provided examples of hardware and software arrangements for implementing the processes and functions of this disclosure, the following sections provide details and examples of the arrangements for timing indications for determining the beam switching delay of a beam indication initiated by a WD.

[0262] In some embodiments, capabilities, configurations, events, indications, etc., can be initiated by the WD, and can also refer to capabilities, configurations, events, indications, etc., initiated by the UE. For example, a WD beam reporting capability can refer to a UE-initiated beam reporting capability. Similarly, a WD-initiated beam reporting configuration can refer to a UE-initiated beam reporting configuration, a WD-initiated beam reporting event can refer to a UE-initiated beam reporting event, a WD-initiated beam indication can refer to a UE-initiated beam indication, and so on.

[0263] Figure 22 This is a flowchart illustrating an example of a WD-initiated beam management process according to some embodiments of this disclosure. In step S200, WD 22 signals a “WD-initiated beam reporting capability” (e.g., “UE-initiated beam reporting capability”). In step S202, NN 16 signals a WD-initiated beam reporting configuration (e.g., “UE-initiated beam reporting configuration”). In step S204, NN 16 sends a DL-RS. In step S206, WD 22 performs a measurement of the DL-RS and triggers a WD-initiated beam reporting event (e.g., a UE-initiated beam reporting event). In step S208, WD 22 may instruct itself to signal a WD-initiated beam report, which was signaled in step S210. The WD-initiated beam indication process in step 208 (or any other step) may be skipped, such as when a condition is met.

[0264] The duration of the beam application delay (i.e., the time between S212 and S214) can be determined, for example, in part, based on the delay between steps S210 and S212. During the WD-initiated beam indication process, the beam indication is included in the beam report. A WD-initiated beam indication (or a WD-initiated beam indication report) can be equivalent to a WD-initiated beam report, i.e., a WD-initiated beam report that includes the beam indication. The beam indication or report may include one or more candidate beams to be switched to.

[0265] To facilitate rapid beam switching, the WD can store QCL-related information about one or more candidate beams, enabling it to quickly switch to a new beam when indicated by the network (in step S212). However, if step S212 takes longer than a predetermined time period, the QCL-related information stored by the WD may become outdated, and rapid beam switching may not be possible. To ensure that network node 16 and WD 22 have the same assumptions about whether the QCL-related information is outdated, in one embodiment, a timer (T0) is introduced in the specification, indicating how long the QCL-related information can be assumed to be applicable. The timer starts when a beam indication report is sent by WD 22. The timer always starts with an initial value representing T0. In one embodiment, the timer (T0) is pre-configured according to the specification. In another embodiment, the time value T0 can be configured by network node 16, for example, using MAC-CE or RRC signaling. In step S214, WD 22 applies a new spatial filter, and in step S216, WD 22 and NN 16 communicate using the new beam pair.

[0266] Figure 23 and 24 This illustrates an example beam management process. From network node 16 ( Figure 22 In step S212, the acknowledgment from WD 22 occurs within time T0 from the time the beam report initiated by WD, and therefore the beam switching delay will be short because the QCL-related information associated with the indicated beam has been saved by WD 22 and is assumed to still be valid. At the bottom of the diagram, the acknowledgment from the network to WD 22 is sent after time T0 following the corresponding beam report initiated by WD, and therefore the beam switching delay will be longer (i.e., the delay will be comparable to traditional beam switching delays) because the QCL-related information associated with the indicated beam is assumed to be outdated. In some cases, if T0 expires, the network may assume that the beam report initiated by WD is outdated.

[0267] In one embodiment, time-domain parameters regarding how long the WD should remain in the pre-switched beam (i.e., the beam indicated as the optimal beam in the beam report) are indicated to the WD 22 via at least one of the following methods:

[0268] • Higher-level signaling, such as RRC reconfiguration messages;

[0269] •MACCE;

[0270] •DCI; and

[0271] • It is predefined in the specification.

[0272] In some embodiments, the WD 22 stores QCL-related information for one or more beams included in the beam indication report until timer T0 expires.

[0273] In some other embodiments, the confirmation signal is a beam indication signal carried in the PDCCH (in the Rel-17 Unified TCI framework), which contains the same “best beam” as the best beam reported in WD 22.

[0274] In some embodiments, the confirmation signal is a beam activation signal carried in the MACCE (in the 3GPP Rel-15 / 16TCI framework), which contains the same “best” beam as the best beam reported by WD.

[0275] In some other embodiments, a beam application time (BAT) is introduced, which specifies the application time of the newly determined beam. Depending on whether an acknowledgment message about the new beam is received from the network within T0 after WD 22 sends the WD-initiated beam report (step S210) (step S212), there are different methods to determine the BAT for the WD-initiated beam indication.

[0276] • If an acknowledgment message is received from the network within T0, and the beam indication / beam activation signal contains the same "best beam" as the best beam in the beam report initiated by WD, then WD 22 uses BAT_within_T0 (e.g., from BAT configuration) to switch to the identified "best beam," where BAT may begin after, for example, the following:

[0277] ○1. The last symbol of the PDCCH carrying the beam indication DCI (confirmation message in step S212) that indicates the same "best beam" as the beam report initiated by WD.

[0278] ○2. The last symbol of the PDSCH carrying the beam activation MAC CE (confirmation message in step S212) of the beam that is the same as the "best beam" indicated in the beam report initiated by WD.

[0279] ○3. Transmission of acknowledgment messages for the reception of beam-activated MAC CE

[0280] ○4. ACK sent in PUCCH to confirm messages in PDCCH / PDSCH in sub-items 1 and 2 above.

[0281] • If an acknowledgment signal is received after T0, and the beam switching indication / beam activation signal contains the same beam as the "best beam" indicated in the beam report initiated by WD:

[0282] Apply BAT_after_T0 (e.g., from BAT configuration), and BAT_after_T0 is equal to or greater than BAT_within_T0.

[0283] ○ If BAT is not supported / configured, the WD 22 is expected to receive the DL-RS associated with the indicated "best beam" before it is able to switch to it.

[0284] In another embodiment, if candidate beams in the beam indication report are already activated, i.e., they are associated with an active TCI state at the time of beam indication, the network can indicate beam switching to one of the candidate beams via DCI. Thus, BAT is not needed or BAT=0.

[0285] If candidate beams in the beam indication report are not activated, i.e., they are not associated with any active TCI state at the time of beam reporting, then at least one TCI state of the candidate beams associated with the beam to be switched to needs to be activated first. Activation is typically via a MAC CE carried in the PDSCH. If a MAC CE is received within the T0 time period, the beam or TCI state can be considered activated after sending an acknowledgment to the PDSCH, or within a short period after sending the acknowledgment (e.g., BAT_within_T0), because the QCL information associated with the beam is already available at WD 22. If a MAC CE is received after the T0 timer has expired, WD 22 needs to reacquire the QCL information for the beam, and a longer activation time is required (e.g., BAT_after_T0).

[0286] In one embodiment, the value of T0 is associated with, but is not limited to, the following configuration / parameters:

[0287] • Carrier frequency;

[0288] • Parameter set (subcarrier spacing);

[0289] •Bandwidth portion;

[0290] •TDD mode;

[0291] • Transmission direction (uplink or downlink); and

[0292] • Reference signal configuration.

[0293] The value used for BAT_within_T0 can be determined based on at least one of the following:

[0294] • (As a traditional value);

[0295] • Values ​​configured by the network, where the range should be smaller than the values ​​indicated in the WD capability signaling;

[0296] • The value of the WD capability indication associated with the beam indication initiated by the WD; and

[0297] • Predefined values ​​in the specification.

[0298] For WD 22, which is configured with the same parameter set for active BWPs for UL and DL, and T0 is configured as the number of time slots for that WD 22, if WD 22 sends a beam report with the best beam A1 in time slot n, and if WD 22 receives a DCI in the PDCCH instructing WD 22 to switch to beam A1 within time n+T0, then WD 22 should switch to the new beam after BAT_within_T0 after WD 22 receives the last symbol of the PDCCH carrying the DCI.

[0299] In one embodiment, timer / counter T0 is reset each time a beam report initiated by WD is sent.

[0300] In one embodiment, if the WD 22 is configured with multiple TRPs / panels, such as simultaneous UL or DL ​​transmissions, and M-TRPs with different CORESETPoolIndexes, the WD 22 can apply a separate T0 value for each TRP. That is, if two WD-initiated beam management signaling messages are associated with different TRPs / panels, there are no timing constraints between them. Note that here, different TRPs or panels may be referred to in the specification as different beam or TCI group IDs, different SRS resource set IDs, different CSI-RS resource set IDs, different CORESETPoolIndexes, etc.

[0301] WD capability and RRC signaling

[0302] WD 22 can indicate that it supports the following WD capabilities:

[0303] • Supports WD-initiated beam indication, and supports at least one of the following in its WD capability indication:

[0304] ○The range or parameter set of the signaling interval T0 initiated by WD; and

[0305] ○BeamAppTime-r19.

[0306] An example of RRC signaling for beam activation time (configuration) can be as follows:

[0307]

[0308] Figure 25 This illustrates an example beam reporting process initiated by the WD (where beam switching occurs in response to network node acknowledgment). In step S400, WD 22 performs one or more measurements and / or evaluations that may be associated with the target beam and / or SSB0. In step S402, pre-synchronization may be performed and may be associated with uplink and downlink signaling. In step S404, a report associated with a better beam and / or beam update request is made, sent, received, etc. In step S406, WD 22 performs one or more measurements and / or evaluations that may be associated with the target beam and / or SSB2. In step S408, pre-synchronization may be performed and may be associated with uplink and downlink signaling. In step S410, beam acknowledgment for SSB0 is received (e.g., by WD 22) and may include beam indication DCI. In step S412, WD 22 (and / or network node 16) may switch to SSB0. WD 22 may maintain the target beam SSB0 and be ready for a fast beam switch.

[0309] Figure 26 The steps of an example method for a beam switching procedure initiated by WD 22 are shown. Not all steps may be required, as at least some steps may be optional.

[0310] In step S500, WD 22 indicates its support for WD-initiated beam reporting and WD-initiated beam switching during WD capability signaling. In step S502, network node 16 configures WD-initiated beam reporting and WD-initiated beam switching to WD 22, for example, setting different parameters regarding how to trigger WD-initiated beam management events, how to execute WD-initiated beam reporting (including reports on WD preferred / recommended beams for pre-switching), and how to execute WD-initiated beam switching. In step S504, network node 16 sends a downlink reference signal (DL-RS), such as CSI-RS, SSB, or a new DL-RS in 6G. In step 4, WD 22 performs measurements on the DL-RS and assesses whether a WD-initiated beam reporting trigger event has occurred. In step S506, if such a WD-initiated beam reporting trigger event has occurred, WD 22 optionally instructs network node 16 in S508 that WD 22 will send a WD-initiated beam report to network node 16. In step S510, WD 22 sends a beam report initiated by WD.

[0311] In step S512, WD 22 switches to the newly determined optimal beam. In step S514, network node 16 and WD 22 communicate on the link using the new beam determined during the beam switching process initiated by WD. In step S516, network node 16 receives a beam report initiated by WD and optionally sends a beam report response initiated by WD to WD 22. In step S518, if WD 22 does not receive a "beam switching response" from network node 16, WD 22 falls back to the previous beam.

[0312] That is, in steps S512-S518, WD 22 performs WD-initiated beam switching after sending the WD-initiated beam report.

[0313] In one embodiment, the beam reporting signaling initiated by WD includes, but is not limited to, messages sent from WD 22 to network node 16 to initiate beam management-related operations, including one or more of the following messages.

[0314] •SR in PUCCH;

[0315] • UCI in PUCCH and / or PUSCH;

[0316] • MACCE in PUSCH;

[0317] •PRACH;

[0318] •SRS.

[0319] In one embodiment, the time-domain parameters regarding how long WD 22 should remain in the pre-switched beam (e.g.) It is instructed to WD 22 via at least one of the following methods:

[0320] • Higher-level signaling, such as RRC reconfiguration messages;

[0321] •MACCE;

[0322] •DCI;

[0323] • It is predefined in the specification.

[0324] In one embodiment, It can be associated with a timer / counter. In some scenarios, the timer always starts from its initial value (which is associated with it). The timer is started or restarted with a value of 0. In this case, the timer expires when it reaches a value of 0. In some embodiments, the timer is always started or restarted with a value of 0 and expires when it reaches a value of 0. The timer expires. In some other embodiments, the timer can be stopped. In some embodiments, the timer runs once started and continues until it is stopped or until it expires. The timer can have any of the following states:

[0325] • Started: The timer begins running from the current value toward the end value. The current value can be the initial value or a value different from the initial value.

[0326] • Restarted: The timer is set to its initial value and begins running toward its end value.

[0327] • Expiration: The timer reaches its end value and stops running.

[0328] • Stopped: The timer stopped running before reaching its end value.

[0329] • Reset: The timer is set to its initial value, but it has not started running.

[0330] In one embodiment, when WD 22 applies "WD-initiated beam switching", upon receiving the back-off timing configuration... Afterwards, WD 22 will The information is stored in its processing memory. In some embodiments, when WD 22 has initiated a beam switching process in steps S512-S518, WD 22 stores the QCL and / or spatial information of the serving link / beam in its processing memory and applies a new beam / spatial filter. WD 22 can then wait for a "WD-initiated beam switching response" (step S516) from network node 16 to successfully complete the WD 22-initiated beam switching. Successful completion may mean that WD 22 remains in the same beam as the beam that WD 22 reported and temporarily switched to. If in If no response is received within the specified time, WD 22 can assume that network node 16 disagrees with the timing of the new beam reported in the beam report and can use the stored QCL information to switch back to the previously known service link, such as... Figure 27 As shown. The time can be assumed to start from a time that is assumed to be known to both network node 16 and WD 22 in step S508 or step S510, for example, the time slot in which WD 22 sends a beam report initiated by WD to network node 16.

[0331] More specifically, Figure 27 The confirmation message (i.e., the beam switching response in step S516) is displayed in The contents were received. It is initiated immediately after the beam switching initiated by WD 22 is sent. Since the temporary beam switching initiated by WD 22 is promptly acknowledged by network node 16, WD 22 can continue to communicate with network node 16 using the pre-switched beam (i.e., the beam indicated in the beam switching report initiated by WD).

[0332] Figure 28 Showing about Another example of its application. In step S600, T fallback Configured. In step S602, measurements and / or evaluations associated with the SSB and / or physical channel can be performed. In step S604, a beam switch is reported and / or a temporary beam switch to SSB0 is performed. Step S606 may or may not be performed. For example, beam confirmation (beam indication DCI) associated with SSB0 may not be performed (or is not required). In step S608, if no response is received within T2, a switchback to the beam associated with SSB1 is performed.

[0333] More specifically, WD 22 detects a new "best beam" SSB0 that is different from its serving beam (associated with SSB1). WD 22 can store storage beam information (e.g., QCL information of SSB1) in its processing memory, send a WD-initiated beam report (carried in PUCCH / PUSCH(MACCE) / SRS) to network node 16, and switch to the "best beam" SSB0. Afterward, WD 22 can monitor the PDCCH and PDSCH with the SSB0 QCL. In a non-limiting example, during a timer... Before the expiration date, WD 22 did not receive an acknowledgment response from network node 16. Upon expiration, it corresponds to the failure of the beam switching process initiated by WD, meaning that WD 22 must switch back to the previous beam associated with SSB1 based on the stored QCL information of SSB1. Meanwhile, network node 16... After the expiration date, I learned that WD 22 will switch back to SSB1.

[0334] In some embodiments, time-domain parameters Associated with, but not limited to, the following configurations / parameters:

[0335] • Carrier frequency;

[0336] • Parameter set (subcarrier spacing);

[0337] •Bandwidth portion;

[0338] •TDD mode;

[0339] • Transmission direction (uplink or downlink);

[0340] • Reference signal configuration, such as period, etc.

[0341] In one example, if in With multiple DL-RS measurement opportunities configured internally, the WD 22 can... The system sends a second beam report initiated by the WD and resets or restarts if a better beam is identified during the DL-RS measurement. Timer. In another example, to prevent WD 22 from... Send at least one beam report initiated by a second WD within the internal transmission. The value should be less than the period of the DL reference signal configured for beam management.

[0342] In one embodiment, with The associated timer / counter starts simultaneously with WD 22 switching to the newly identified “best beam” reported to network node 16 in the WD-initiated beam report. In one detailed embodiment, WD 22 switches to the new beam at an offset from the time instance from which the WD-initiated beam report was sent. The delay offset can be configured by network node 16, or follow specifications, etc.

[0343] In one embodiment, the timer / counter operates before the WD 22 switches to the newly identified optimal beam. It is initiated immediately after the beam report initiated by WD is sent.

[0344] In one embodiment, timer / counter The beam switching response is reset after receiving a beam switching response from network node 16. If a NACK message is received, WD 22 can fall back from the pre-switched beam to the previous beam (as associated with the active TCI state). Alternatively, if an ACK message is received, WD 22 can continue communicating with network node 16 using the pre-switched beam. In a detailed embodiment, within the same beam switching response, network node 16 can update the active TCI state to the pre-switched beam.

[0345] In one embodiment, if WD 22 does not receive a "beam switching response" from network node 16, then the timer / counter... It is reset after it expires. In this case, WD 22 can immediately fall back from the pre-switched beam to the previous beam associated with the active TCI state.

[0346] In one embodiment, if WD 22 is in If a new WD-initiated beam report is sent before the expiration date, then the timer / counter... Reset. The beam report initiated by the second WD may carry different or the same information as the beam report initiated by the first WD. Alternatively, in Before the expiration date, WD 22 is not allowed to send a second WD-initiated beam report. In another example, WD 22 is not allowed to... Before the expiration date, send a beam report initiated by a second WD carrying the same information.

[0347] In one embodiment, WD 22 is configured with WD-initiated beam reporting + beam switching for individual DL / UL TCI states, enabling WD 22 to monitor two distinct service links: one associated with the DL signal / channel (i.e., associated with the indicated DL TCI state), and the other associated with the UL signal / channel (i.e., associated with the indicated UL TCI state). In one embodiment, timing parameters... It can be configured publicly or individually for each service link. For example, the WD 22 can be configured with public configurations for both DL and UL service links. Alternatively, each can be configured with a DL beam switching mechanism initiated by the WD. And for UL beam switching initiated by WD .

[0348] In one embodiment, if the WD 22 is configured with multiple TRPs / panels, for example, M-TRPs with different CORESETPoolIndex for simultaneous UL or DL ​​transmission, the WD 22 can apply a separate application for each TRP. The value indicates that if two beam management signaling messages initiated by two WDs are associated with different TRPs / panels, then there are no timing constraints between them. Different TRPs or panels can be referred to as different beams or TCI group IDs, different SRS resource set IDs, different CSI-RS resource set IDs, and different CORESETPoolIndex / Indices, etc.

[0349] WD capabilities

[0350] WD 22 can indicate that it supports the following WD capabilities:

[0351] • Supports beam switching initiated by WD, including time-limited parameters. The range or parameter set;

[0352] • Supports separate DL beam switching and UL beam switching initiated by WD. Configuration;

[0353] •support Delay configuration, i.e., timer / counter Startup time.

[0354] In some embodiments, WD 22 may be configured (e.g., by network node 16) to perform one or more steps of the embodiment via RRC configuration.

[0355] In some embodiments of this disclosure, all three types of WD-initiated reports (i.e., 1. WD-initiated beam reports, 2. WD-initiated beam indications, and 3. WD-initiated beam switching) may generally be referred to as "WD-initiated beam reports".

[0356] Refer again Figure 22 This section describes some embodiments related to step S206. More specifically, WD 22 determines whether a WD-initiated beam report event has occurred (e.g., this may be based in part on comparing measurements of candidate DL-RS and DL-RS associated with the joint TCI state of the current application). If such an event is triggered, WD 22 may proceed to steps S208 and S210 and send a WD-initiated beam report. In some embodiments, such WD-initiated beam report events may occur quite frequently due to, for example, unreliable RSRP measurements or fast fading channels, which may consume too many UL resources. Therefore, in some other embodiments of this disclosure, WD 22 may be configured with one or more timing limits that limit the frequency to which WD 22 may trigger such WD-initiated beam reports.

[0357] In some embodiments, the WD 22 configured to initiate beam reports may be configured with a time limit T1, which indicates the minimum time that the WD 22 must wait before triggering or sending a second beam report after the first beam report. Figure 29 The diagram illustrates an example of this situation.

[0358] In some embodiments, the time limit T1 can be defined as the minimum time that WD 22 must wait before sending an indication to the network that it can signal the next "WD-initiated beam report" (i.e., within...). Figure 22 (in step 5 of the process). In some embodiments, assuming that an indication to the network regarding the next “WD-initiated report” is sent on the PUCCH SR, then T1 is the minimum time between the first WD-initiated beam report and the PUCCH-SR carrying an indication to the network regarding the upcoming second WD-initiated beam report.

[0359] In some embodiments, the time constraint may depend on one or more of the following parameter sets or subcarrier spacing: Figure 22The parameter set of DL-RS, PUCCH, or PUSCH used for measurement in step S206.

[0360] In some embodiments, the WD 22 configured with a WD-initiated beam report may be configured with a time limit T2, which indicates the minimum time that the WD 22 must wait before triggering or sending a second beam report after the first beam report, wherein the first and second beam reports indicate the same preferred beam. Figure 30 The diagram illustrates an example of this situation, where during duration T2, beam report #2 containing "Best Beam SSB1" can be sent instead of beam report containing "Best Beam SSB0" because SSB0 is the same best beam as the best beam reported in beam report #1.

[0361] In some embodiments, the WD 22 configured with a WD-initiated beam report may be configured with a time limit T3, which indicates the minimum time that the WD 22 must wait before triggering or sending a second beam report after the first beam report, wherein the first and second beam reports indicate different preferred beams. Figure 31 The diagram illustrates an example of this situation.

[0362] In some embodiments, WD 22 is configured with WD-initiated beam reports and separate DL / UL TCI states, enabling WD 22 to monitor two distinct service links: one service link associated with the DL signal / channel (i.e., associated with the indicated DL TCI state) and one service link associated with the UL signal / channel (i.e., associated with the indicated UL TCI state). In some embodiments, one or more of T1, T2, and T3 can be configured individually for each service link. For example, WD 22 can be configured with T1 = 200 ms for both the DL and UL service links, and in this case, WD-initiated beam reports for the DL service link and WD-initiated beam reports for the UL service link can be triggered at a maximum frequency of 200 ms (i.e., there are no timing-dependent constraints between the two service links). In other words, timing constraints can be applied independently for the DL and UL service links.

[0363] In some embodiments, the new parameter T4 is used to also indicate the minimum time distance between beam reports initiated by the WD for the first service link and beam reports initiated by the WD for the second service link.

[0364] In some embodiments, the WD 22 configured with WD-initiated beam reports can be configured with a maximum number of reports for WD-initiated beam reports during a duration T5. Figure 32The diagram illustrates an example of this scenario, where the maximum number of reports within duration T5 is 2. In some embodiments, the duration of T5 is configured by higher-layer signaling, and WD 22 determines the start time of T5 via time parameters (e.g., slot offset and system frame number (SFN)) in the RRC configuration. In some embodiments, WD 22 determines the start time of T5 as associated with the transmission time (slot) of each beam report initiated by WD.

[0365] Each of T1 through T5 can be associated with a timer. Each of the timers is started each time a beam indication report is sent or a corresponding acknowledgment is received. A timer is always started or restarted from its initial value, which is the associated T value (e.g., the timer associated with T1 is initialized with T1). In some scenarios, a timer can be stopped. For example, a timer can be stopped when a desired beam switch based on a previous beam indication report has occurred. Once a timer is started, it runs until it is stopped or until it expires. A beam indication report can only be sent when one or more of the timers are stopped or expire (i.e., when the timer value reaches zero).

[0366] Beam reporting signaling initiated by WD includes, but is not limited to, messages sent from WD 22 toward the network to initiate beam management reporting related operations, including one or more of the following messages:

[0367] •SR in PUCCH;

[0368] • Uplink control information (UCI) in PUCCH and / or PUSCH;

[0369] • MAC CE in PUSCH;

[0370] • Physical Random Access Channel (PRACH); and

[0371] •SRS.

[0372] In some embodiments, one or more of the time limits T1, T2, T3, and T4 indicating the minimum time between beam reports initiated by two adjacent WDs are configured / indicated to WD 22 via at least one of the following methods:

[0373] • Higher-level signaling, such as RRC reconfiguration messages;

[0374] •MACCE; and / or

[0375] • It is predefined in the 3GPP specification.

[0376] Upon receiving the configuration / instruction for at least one of time slots T1, T2, T3, T4, and T5, WD 22 may store the parameter(s) in its memory. Each time WD 22 can observe an event that satisfies one or more conditions triggering a WD-initiated beam management signaling, WD 22 may first check the status of T1 / T2 / T3 / T4 / T5, for example, whether it was set or reset from the most recent reception of the T1 / T2 / T3 / T4 / T5 value after, for example, an RRC reconfiguration message. If this is the first time T1 / T2 / T3 / T4 / T5 has been used, WD 22 may initiate its first WD-initiated beam report and store the timestamp of that first WD-initiated beam report in its memory. WD 22 stores the timestamp each time a WD-initiated report is sent. If the current beam report transmission is not the first one—that is, if an earlier beam report transmission was performed after the setting or resetting of timers / counters T1 / T2 / T3 / T4 / T5—WD 22 can compare the time difference between (one or more) latest timestamps to determine when to send a new beam report. If the time difference is greater than (or equal to) the T1 / T2 / T3 / T4 / T5 value, WD 22 can initiate a new beam report transmission. It should be noted that if the time interval between two adjacent signaling messages is less than (or equal to) the T1 / T2 / T3 / T4 value, WD 22 is not expected to send a WD-initiated beam report.

[0377] In some embodiments, if the WD 22 is configured with multiple Transmit Receive Points (TRPs) / panels, such as simultaneous UL or DL ​​transmissions, and M-TRPs with different CORESETPoolIndexes, the WD 22 can apply separate (one or more) T1 / T2 / T3 / T4 / T5 values ​​for each TRP. That is, if two WD-initiated beam management signaling messages are associated with different TRPs / panels, there are no timing constraints between them. Note that here, different TRPs or panels may be referred to in the specification as different beam or TCI group IDs, different SRS resource set IDs, different CSI-RS resource set IDs, and different CORESETPoolIndexes, etc.

[0378] In some embodiments, the timer / counter for T1 / T2 / T3 / T4 is reset each time a beam report initiated by WD is sent.

[0379] WD capabilities

[0380] WD 22 can indicate that it supports the following WD capabilities:

[0381] • Supports beam reporting initiated by WD, including the range or parameter set of at least one of the time-limited parameters T1, T2, T3, T4, and T5; and

[0382] • For WD that supports T5, it can also report the maximum number of WD-initiated reports associated with T5.

[0383] The following is a list of non-limiting example embodiments.

[0384] Example A1. A wireless device (WD) configured to communicate with a network node, the WD being configured to perform the following operations and / or include a radio interface and / or processing circuitry configured to perform the following operations:

[0385] Determine the time period during which WD will store quasi-co-location (QCL) related information associated with one or more beam indications in WD-initiated beam indication reports; and

[0386] Perform one or more actions based on a defined time period.

[0387] Example A2. The WD as described in Example A1, the WD is further configured to perform one or more of the following:

[0388] This results in the transmission of the first indication that the WD will send a signal to transmit the beam report initiated by the WD;

[0389] Transmit a signal to transmit the beam report initiated by WD;

[0390] Receive from the network node a beam report confirmation indicating that the WD has initiated and a second indication of one or both of the beams;

[0391] In response to the second instruction, apply a spatial filter; and

[0392] Based on when network nodes send signals to confirm the beam report initiated by WD, the beam switching time and beam application time are determined.

[0393] Example A3. The WD as described in any of Examples A1 and A2, wherein the time period for which the WD stores QCL-related information is based on the time delay between the WD signaling the beam report initiated by the WD and receiving the second indication.

[0394] Example B1. A method in a wireless device (WD) configured to communicate with a network node, the method comprising:

[0395] Determine the time period during which WD will store quasi-co-location (QCL) related information associated with one or more beam indications in WD-initiated beam indication reports; and

[0396] Perform one or more actions based on a defined time period.

[0397] Example B2. The method as described in Example B1, wherein the method further comprises one or more of the following:

[0398] The WD will send a signal to transmit the first indication of the beam report initiated by the WD;

[0399] Transmit a signal to transmit the beam report initiated by WD;

[0400] Receive from the network node a beam report confirmation indicating that the WD has initiated and a second indication of one or both of the beams;

[0401] In response to the second instruction, apply a spatial filter; and

[0402] Based on when network nodes send signals to confirm the beam report initiated by WD, the beam switching time and beam application time are determined.

[0403] Example B3. The method as described in any of Examples B1 and B2, wherein the time period for which the WD stores QCL-related information is based on the time delay between the WD signaling the beam report initiated by the WD and receiving the second indication.

[0404] Example C1. A network node configured to communicate with a wireless device (WD), the network node being configured to perform the following operations and / or include a radio interface and / or processing circuitry configured to perform the following operations:

[0405] Receive beam reports initiated by WD;

[0406] This results in the WD sending a second indication to the WD initiating a beam report acknowledgment and one or both of the beams. This second indication can be used by the WD to determine the time period during which the WD will store quasi-co-location (QCL) related information associated with the beams of one or more indications in the WD-initiated beam indication report; and

[0407] One or more actions are performed based on the second instruction and the time period.

[0408] Example C2. A network node as described in Example C1, wherein the network node is further configured as follows:

[0409] The receiving instruction WD will send a signal to transmit the first instruction of the beam report initiated by WD.

[0410] Example C3. A network node as described in either Example C1 or C2, wherein the second indication can be used by the WD to determine the beam switching time and beam application time based on when the network node signals a WD-initiated beam report confirmation.

[0411] Example D1. A method in a network node configured to communicate with a wireless device (WD), the method comprising:

[0412] Receive beam reports initiated by WD;

[0413] Send to WD a second indication instructing WD to acknowledge a beam report initiated by WD and one or both of the beams, the second indication being used by WD to determine the time period during which WD will store quasi-co-location (QCL) related information associated with the beams of one or more indications in the WD-initiated beam indication report; and

[0414] One or more actions are performed based on the second instruction and the time period.

[0415] Example D2. The method as described in Example D1, wherein the network node is further configured as follows:

[0416] The receiving instruction WD will send a signal to transmit the first instruction of the beam report initiated by WD.

[0417] Example D3. The method as described in any of Examples C1 and C2, wherein the second indication can be used by the WD to determine the beam switching time and beam application time based on when the network node signals the WD-initiated beam report confirmation.

[0418] Example E1. A wireless device (WD) configured to communicate with a network node, the WD being configured to perform one or more of the following operations and / or including a radio interface and / or processing circuitry configured to perform one or more of the following operations:

[0419] This results in the transmission of a beam switching report associated with the beam switching from the first beam to the second beam initiated by the WD to the network node, i.e., sent to the network node, where the first and second beams can be used by the WD to communicate with the network node.

[0420] Switching from the first beam to the second beam; and

[0421] If WD does not receive a beam switching response from the network node after the scheduled time has elapsed, it switches back to the first beam.

[0422] Example E2. The WD as described in Example E1, wherein the WD is further configured as follows:

[0423] Receive the rollback timing configuration corresponding to the scheduled time instance from the network node. (instructions).

[0424] Example E3. WD as described in Example E2, wherein Associated with one or more of the following:

[0425] Carrier frequency;

[0426] Parameter set;

[0427] Bandwidth portion;

[0428] Time Division Duplex (TDD) mode;

[0429] Transmission direction; and

[0430] Reference signal configuration.

[0431] Example E4. The WD as described in any of Examples E2 and E3, wherein the WD is further configured as follows:

[0432] This results in the transmission of a WD capability indication that includes one or more of the following:

[0433] Support for beam switching initiated by WD, including The range or parameter set;

[0434] Individual for WD-initiated downlink beam handover and WD-initiated uplink beam handover Configuration support; and

[0435] right Support for delayed configuration.

[0436] Example E5. WD as described in any of Examples E1-E4, wherein the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0437] Example F1. A method in a wireless device (WD) configured to communicate with a network node, the WD method comprising one or more of the following:

[0438] Send a beam switching report to the network node associated with the beam switching from the first beam to the second beam initiated by the WD. The first and second beams can be used by the WD to communicate with the network node.

[0439] Switching from the first beam to the second beam; and

[0440] If WD does not receive a beam switching response from the network node after the scheduled time has elapsed, it switches back to the first beam.

[0441] Example F2. The method as described in Example F1, wherein the method further comprises:

[0442] Receive the rollback timing configuration corresponding to the scheduled time instance from the network node. (instructions).

[0443] Example F3. The method as described in Example F2, wherein Associated with one or more of the following:

[0444] Carrier frequency;

[0445] Parameter set;

[0446] Bandwidth portion;

[0447] Time Division Duplex (TDD) mode;

[0448] Transmission direction; and

[0449] Reference signal configuration.

[0450] Example F4. The method as described in any one of Examples F2 and F3, wherein the method further comprises:

[0451] Send WD capability indication, indicating one or more of the following:

[0452] Support for beam switching initiated by WD, including The range or parameter set;

[0453] Individual for WD-initiated downlink beam handover and WD-initiated uplink beam handover Configuration support; and

[0454] right Support for delayed configuration.

[0455] Example F5. The method as described in any of Examples F1-F4, wherein the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0456] Example G1. A network node configured to communicate with a wireless device (WD), the network node being configured to perform one or more of the following operations and / or include a radio interface and / or processing circuitry configured to perform one or more of the following operations:

[0457] The transmission of information to the WD corresponding to a predetermined time instance of beam switching from the first beam to the second beam initiated by the WD, i.e., sending this information to the WD, wherein the first and second beams can be used by the network node to communicate with the WD, and the predetermined time instance can be used by the WD to switch back to the first beam if the WD does not receive a beam switching response from the network node after the predetermined time instance has elapsed; and

[0458] Communicate with WD using one of the first and second beams.

[0459] Example G2. A network node as described in Example G1, wherein the network node is further configured as follows:

[0460] This results in the rollback timing configuration corresponding to the scheduled time instance. The instruction is transmitted to WD.

[0461] Example G3. A network node as described in Example G2, wherein Associated with one or more of the following:

[0462] Carrier frequency;

[0463] Parameter set;

[0464] Bandwidth portion;

[0465] Time Division Duplex (TDD) mode;

[0466] Transmission direction; and

[0467] Reference signal configuration.

[0468] Example G4. A network node as described in any of Examples G2 and G3, wherein the network node is further configured as follows:

[0469] Receive WD capability indication, which indicates one or more of the following:

[0470] Support for beam switching initiated by WD, including The range or parameter set;

[0471] Individual for WD-initiated downlink beam handover and WD-initiated uplink beam handover Configuration support; and

[0472] right Support for delayed configuration.

[0473] Example G5. A network node as described in any of Examples G1-G4, wherein the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0474] Example H1. A method for a network node configured to communicate with a wireless device (WD), the method comprising one or more of the following:

[0475] Send information to the WD associated with a predetermined time instance corresponding to a beam handover initiated by the WD from the first beam to the second beam, wherein the first and second beams can be used by the network node to communicate with the WD, and the predetermined time instance can be used by the WD to switch back to the first beam if the WD does not receive a beam handover response from the network node after the predetermined time instance has elapsed; and

[0476] Communicate with WD using one of the first and second beams.

[0477] Example H2. The method as described in Example H1, wherein the method further comprises:

[0478] Send an instruction to WD to the rollback timing configuration corresponding to the scheduled time instance. (instructions).

[0479] Example H3. The method as described in Example H2, wherein Associated with one or more of the following:

[0480] Carrier frequency;

[0481] Parameter set;

[0482] Bandwidth portion;

[0483] Time Division Duplex (TDD) mode;

[0484] Transmission direction; and

[0485] Reference signal configuration.

[0486] Example H4. The method as described in any one of Examples H2 and H3, wherein the method further comprises:

[0487] Receive WD capability indication, which indicates one or more of the following:

[0488] Support for beam switching initiated by WD, including The range or parameter set;

[0489] Individual for WD-initiated downlink beam handover and WD-initiated uplink beam handover Configuration support; and

[0490] right Support for delayed configuration.

[0491] Example H5. The method as described in any of Examples H1-H4, wherein the first beam is associated with a first synchronization signal block (SSB), the second beam is associated with a second SSB, and switching back to the first beam is based on quasi-co-location information of the first SSB.

[0492] Example I1. A network node configured to communicate with a wireless device (WD), the network node being configured to perform the following operations and / or include a radio interface and / or processing circuitry configured to perform the following operations:

[0493] Configure WD to initiate beam reporting; and

[0494] Receive the first WD-initiated beam report configured according to the WD-initiated beam report configuration.

[0495] Example 12. A network node as described in Example 11, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before triggering a first beam report initiated by the WD.

[0496] Example 13. A network node as described in Example 11, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before sending an indication to the network node, the indication signaling the next beam report initiated by the WD.

[0497] Example I4. A network node as described in any of Examples I2 and I3, wherein the time constraint T1 depends on at least one of the parameter set or subcarrier spacing of at least one downlink reference signal.

[0498] Example I5. A network node as described in any of Examples I1-I4, wherein the beam report configuration initiated by the WD includes a time limit T2, which indicates the minimum time the WD must wait before triggering a second beam report initiated by the WD.

[0499] Example 16. A network node as described in Example 15, wherein the beam reports initiated by the first and second WDs indicate the same preferred beam.

[0500] Example I7. A network node as described in any of Examples I1-I6, wherein the WD-initiated beam report configuration includes the maximum number of WD-initiated beam reports to be reported within a duration T5.

[0501] Example J1. A method implemented in a network node configured to communicate with a wireless device WD, the method comprising:

[0502] Configure WD to initiate beam reporting; and

[0503] Receive the first WD-initiated beam report configured according to the WD-initiated beam report configuration.

[0504] Example J2. The method as described in Example J1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before triggering a beam report initiated by the first WD.

[0505] Example J3. The method as described in Example J1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before sending an indication to a network node, the indication signaling the next beam report initiated by the WD.

[0506] Example J4. The method as described in any of Examples J2 and J3, wherein the time constraint T1 depends on at least one of the parameter set or subcarrier spacing of at least one downlink reference signal.

[0507] Example J5. The method as described in any of Examples J1-J4, wherein the beam report configuration initiated by the WD includes a time limit T2, which indicates the minimum time the WD must wait before triggering a beam report initiated by a second WD.

[0508] Example J6. The method as described in Example J5, wherein the beam reports initiated by the first and second WDs indicate the same preferred beam.

[0509] Example J7. The method as described in any of Examples J1-J6, wherein the WD-initiated beam report configuration includes a maximum number of WD-initiated beam reports to be reported within a duration T5.

[0510] Example K1. A wireless device (WD) configured to communicate with a network node, the WD being configured to perform the following operations and / or include a radio interface and / or processing circuitry configured to perform the following operations:

[0511] Receive beam report configuration initiated by WD from the network node; and

[0512] Send the first WD-initiated beam report configured according to the WD-initiated beam report configuration.

[0513] Example K2. The WD as described in Example K1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before triggering a beam report initiated by the first WD.

[0514] Example K3. The WD as described in Example K1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before sending an instruction to the WD, the instruction signaling the next beam report initiated by the WD.

[0515] Example K4. WD as described in any of Examples K2 and K3, wherein the time constraint T1 depends on at least one of the parameter set or subcarrier spacing of at least one downlink reference signal.

[0516] Example K5. The WD as described in any of Examples K1-K4, wherein the beam report configuration initiated by the WD includes a time limit T2, which indicates the minimum time the WD must wait before triggering a beam report initiated by a second WD.

[0517] Example K6. The WD as described in Example K5, wherein the beam reports initiated by the first and second WDs indicate the same preferred beam.

[0518] Example K7. The WD as described in any of Examples K1-K6, wherein the WD-initiated beam report configuration includes the maximum number of WD-initiated beam reports to be reported within the duration T5.

[0519] Example L1. A method implemented in a wireless device (WD), the method comprising:

[0520] Receive beam report configuration initiated by WD from the network node; and

[0521] Send the first WD-initiated beam report configured according to the WD-initiated beam report configuration.

[0522] Example L2. The method as described in Example L1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before triggering a beam report initiated by the first WD.

[0523] Example L3. The method as described in Example L1, wherein the beam report configuration initiated by the WD includes a time limit T1, which indicates the minimum time the WD must wait before sending an indication to a network node, the indication signaling the next beam report initiated by the WD.

[0524] Example L4. The method as described in any of Examples L2 and L3, wherein the time constraint T1 depends on at least one of the parameter set or subcarrier spacing of at least one downlink reference signal.

[0525] Example L5. The method described in any of Examples L1-L4, wherein the beam report configuration initiated by the WD includes a time limit T2, which indicates the minimum time the WD must wait before triggering a beam report initiated by a second WD.

[0526] Example L6. The method as described in Example L5, wherein the beam reports initiated by the first and second WDs indicate the same preferred beam.

[0527] Example L7. The method as described in any of Examples L1-L6, wherein the WD-initiated beam report configuration includes a maximum number of WD-initiated beam reports to be reported during duration T5.

[0528] As those skilled in the art will understand, the concepts described herein can be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects, collectively referred to herein as “circuit” or “module.” Any process, step, action, and / or function described herein can be performed by and / or associated with a corresponding module, which can be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can take the form of a computer program product on a tangible computer-readable storage medium embodying computer program code executable by a computer. Any suitable tangible computer-readable medium can be utilized, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0529] This document describes several embodiments with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thus creating a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0530] These computer program instructions may also be stored in a computer-readable storage medium or storage medium that can instruct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture comprising instruction means including the implementation of functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0531] Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0532] It will be understood that the functions / actions indicated in the boxes may be performed in a different order than that indicated in the operation diagram. For example, depending on the functions / actions involved, two boxes shown consecutively may actually be performed substantially concurrently, or these boxes may sometimes be performed in reverse order. Although some diagrams include arrows on the communication path to indicate the main direction of communication, it will be understood that communication may occur in the opposite direction to the arrows depicted.

[0533] Computer program code used to perform the operations of the concepts described herein can be written in an object-oriented programming language, such as Python, Java®, or C++. However, computer program code used to perform the operations of this disclosure can also be written in a conventional procedural programming language, such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0534] Numerous different embodiments have been disclosed herein in conjunction with the foregoing description and accompanying drawings. It will be understood that it would be excessive and confusing to describe and illustrate each combination and sub-combination of these embodiments literally. Therefore, all embodiments can be combined in any manner and / or combination, and this specification (including the accompanying drawings) should be construed as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein, as well as the ways and processes of making and using them, and will support the claims to the extent of any such combination or sub-combination.

[0535] Those skilled in the art will understand that the embodiments described herein are not limited to those specifically shown and described above. Furthermore, unless otherwise stated above, it should be noted that all drawings are not to scale. Various modifications and variations are possible based on the foregoing teachings without departing from the scope of the appended claims.

Claims

1. A method in a wireless device, WD (22), configured to perform a WD-initiated beam management procedure and communicate with a network node (16), the method comprising: determining (S128), based on one or more parameters, one or more of: a first timing indication indicating a beam switch delay associated with a WD-initiated beam report; a second timing indication indicating when to perform a fallback beam switch associated with the WD-initiated beam management procedure; and a third timing indication indicating a minimum time between two WD-initiated beam reports; and performing (S130) one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication. The WD-initiated beam report indicates one or more beams.

2. The method of claim 1, wherein, The method further comprises one or more of:

3. The method of any one of claims 1 and 2, wherein, transmitting a fourth indication indicating that the WD (22) is to signal the WD-initiated beam report; transmitting the WD-initiated beam report; receiving, from the network node (16), a fifth indication indicating one or both of a WD-initiated beam report confirmation and a beam; determining one or both of the beam switch delay and a beam application time based on when the WD-initiated beam report confirmation is received; and applying a spatial filter in response to the fifth indication and one or both of the determined beam switch delay and the beam application time. The method further comprises, when the first timing indication is determined:

4. The method of any one of claims 1-3, wherein, determining a storage time period for which the WD (22) is to store quasi co-location, QCL, related information associated with one or more beams indicated in the WD-initiated beam report; and storing the QCL related information for the storage time period. The method further comprises:

5. The method of claim 4, wherein, switching, within the beam switch delay, to a beam of the one or more beams indicated in the WD-initiated beam report using the QCL related information. Performing the fallback beam switch comprises:

6. The method of any one of claims 1-5, wherein, switching from a first beam to a second beam indicated in the WD-initiated beam report; and switching back to the first beam if the WD (22) has not received a beam switch response from the network node (16) after a predetermined time has passed. The method further comprises:

7. The method of claim 6, wherein, The third timing indication is determined based on a first configuration, and the third timing indication indicates one or more of: receiving, from the network node (16), an indication of a back-off timing configuration corresponding to the predetermined time a sixth indication of 8. The method of any one of claims 1-7, wherein, a minimum time between two sequential WD-initiated beam reports; a minimum time between two sequential fourth indications each indicating to the network node (16) that the WD (22) has at least one WD-initiated beam report to transmit; a minimum time between two WD-initiated beam reports indicating a same preferred candidate beam; and a minimum time between two WD-initiated beam reports indicating different preferred candidate beams. The method further comprises: ​ 9. The method of any one of claims 1-8, wherein, ​ determining a second configuration that configures the WD (22) with joint or separate timing restrictions associated with the third timing indication for downlink serving links and uplink serving links when the WD (22) is configured with separate downlink transmission configuration indicator, TCI, states and uplink transmission configuration indicator, TCI, states.

10. The method of any one of claims 1-9, wherein, The method further comprises: determining a third configuration that configures the WD (22) with a maximum number of WD-initiated beam reports within a time period.

11. The method of any one of claims 1-10, wherein, The one or more parameters comprise one or more of: timing information associated with signaling between the WD (22) and the network node (16); a carrier frequency; a numerology; a bandwidth part; a time division duplex, TDD, pattern; a transmission direction; a reference signal configuration; and a subcarrier spacing of at least one downlink reference signal. The one or more actions comprise one or more of:

12. The method of any one of claims 1-11, wherein, switching to a beam indicated in the WD-initiated beam report within the beam switch delay if the network node (16) indicates the beam to the WD (22); switching to the beam indicated in response to sending the WD-initiated beam report and performing the fallback switch associated with the WD-initiated beam management procedure if no switch response is received from the network node (16); and sending at least one WD-initiated beam report based on the third timing indication.

13. A WD (22) configured to perform a WD-initiated beam management procedure and communicate with a network node (16), the WD (22) being configured to: determine, based on one or more parameters, one or more of: a first timing indication indicating a beam switch delay associated with a WD-initiated beam report; and a third timing indication indicating a minimum time between two WD-initiated beam reports; and perform one or more actions based on one or more of the first timing indication, the second timing indication, and the third timing indication. a second timing indication indicating when to perform a fallback beam switch associated with the WD-initiated beam management procedure; The WD-initiated beam report indicates one or more beams. The WD (22) is further configured to perform one or more of: sending a fourth indication indicating that the WD (22) will signal the WD-initiated beam report; sending the WD-initiated beam report; 14. The WD (22) of Claim 13, wherein, receiving, from the network node (16), a fifth indication indicating one or both of a WD-initiated beam report confirmation and a beam; 15. The WD (22) of any one of claims 13 and 14, wherein, determining one or both of the beam switch delay and a beam application time based on when the WD-initiated beam report confirmation is received; and applying a spatial filter in response to the fifth indication and one or both of the determined beam switch delay and the beam application time. The WD (22) is further configured to, when the first timing indication is determined: determine a storage time period for which the WD (22) will store quasi co-location, QCL, related information associated with one or more beams indicated in the WD-initiated beam report; and ​ ​ 16. The WD (22) of any one of claims 13-15, wherein, ​ ​ ​ storing the QCL-related information for the storage time period.

17. The WD (22) of Claim 16, wherein The WD (22) is further configured to: within the beam switch delay, switch to a beam of the one or more beams indicated in the WD-initiated beam report using the QCL-related information.

18. The WD (22) of any one of claims 13-17, wherein, performing the fallback beam switch includes: switching from a first beam to a second beam indicated in the WD-initiated beam report; and switching back to the first beam if the WD (22) has not received a beam switch response from the network node (16) after a predetermined time has passed.

19. The WD (22) of claim 18, wherein the WD (22) is further configured to: receiving, from the network node (16), an indication of a back-off timing configuration corresponding to the predetermined time a sixth indication of 20. The WD (22) of any one of claims 13-19, wherein, The third timing indication is determined based on a first configuration and indicates one or more of: a minimum time between two sequential WD-initiated beam reports; a minimum time between two sequential fourth indications, each fourth indication indicating to the network node (16) that the WD (22) has at least one WD-initiated beam report to send; a minimum time between two WD-initiated beam reports indicating a same preferred candidate beam; and a minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

21. The WD (22) of any of claims 13-20, wherein, The WD (22) is further configured to: determine a second configuration that configures the WD (22) for joint or separate timing restrictions associated with the third timing indication for downlink serving links and uplink serving links when the WD (22) is configured with separate downlink transmission configuration indicator, TCI, states and uplink TCI states.

22. The WD (22) of any of claims 13-21, wherein The WD (22) is further configured to: determine a third configuration that configures the WD (22) for a maximum number of WD-initiated beam reports within a time period.

23. The WD (22) of any of claims 13-22, wherein The one or more parameters include one or more of: timing information associated with signaling between the WD (22) and the network node (16); a carrier frequency; a numerology; a bandwidth part; a time division duplex, TDD, pattern; a transmission direction; a reference signal configuration; and a subcarrier spacing of at least one downlink reference signal.

24. The WD (22) of any one of claims 13-23, wherein, The one or more actions include one or more of: switching to a beam indicated in the WD-initiated beam report within the beam switch delay if the network node (16) indicates the beam to the WD (22); switching to the beam indicated in response to sending the WD-initiated beam report and performing the fallback switch associated with the WD-initiated beam management procedure if no switch response is received from the network node (16); and sending at least one WD-initiated beam report based on the third timing indication.

25. A method in a network node (16) configured to perform a wireless device, WD, initiated beam management procedure and communicate with a WD (22), the method comprising: receiving (S132), from the WD (22), a WD-initiated beam report, the WD-initiated beam report being associated with one or more of: a first timing indication indicating a beam switch delay, a second timing indication indicating when to perform a fallback beam switch associated with the WD-initiated beam management procedure, and a third timing indication indicating a minimum time between two WD-initiated beam reports; determining (S134) a beam based on the WD-initiated beam report; and one or both of: sending (S136), to the WD (22), a beam indication indicating the beam, and sending a WD switch response indicating to the WD (22) to switch to the beam.

26. The method of claim 25, wherein, The WD-initiated beam report indicates one or more beams.

27. The method of any one of claims 25 and 26, wherein, The method further comprises one or more of: receiving a fourth indication indicating that the WD (22) will signal the WD-initiated beam report; receiving the WD-initiated beam report; sending, to the WD (22), a fifth indication of one or both of a WD-initiated beam report confirmation and the beam; and causing the WD (22) to determine one or both of the beam switch delay and a beam application time based on when the WD-initiated beam report confirmation is received, and to apply a spatial filter in response to the fifth indication and the determined one or both of the beam switch delay and the beam application time.

28. The method of any one of claims 25-27, wherein, The sent beam indication triggers the WD (22) to perform one or more of: determining a storage time period for the WD (22) to store quasi co-location, QCL, related information associated with one or more beams indicated in the WD-initiated beam report; storing the QCL related information for the storage time period; and switching to a beam of the one or more beams indicated in the WD-initiated beam report using the QCL related information within the beam switch delay.

29. The method of any one of claims 25-28, wherein, Performing the fallback beam switch comprises: switching from a first beam to a second beam indicated in the WD-initiated beam report; and switching back to the first beam if the WD (22) has not received a beam switch response from the network node (16) after a predetermined time has passed.

30. The method of claim 29, wherein, The method further comprises: sending to the WD (22) an indication of a back-off timing configuration corresponding to the predetermined time a sixth indication of the sixth indication.

31. The method of any one of claims 25-30, wherein, The third timing indication is based on a first configuration, and the third timing indication indicates one or more of: a minimum time between two sequential WD-initiated beam reports; a minimum time between two sequential fourth indications, each fourth indication indicating to the network node (16) that the WD (22) has a WD-initiated beam report to send; a minimum time between two WD-initiated beam reports indicating a same preferred candidate beam; and a minimum time between two WD-initiated beam reports indicating different preferred candidate beams.

32. The method of any one of claims 25-31, wherein, when the WD (22) is configured with separate downlink transmission configuration indicator, TCI, state and uplink transmission configuration indicator, TCI, state, the WD (22) is configured with a second configuration comprising joint or separate timing restrictions associated with the third timing indication for downlink serving links and uplink serving links.

33. The method of any one of claims 25-32, wherein, the WD (22) is configured with a third configuration comprising a maximum number of WD-initiated beam reports within a time period.

34. The method of any one of claims 25-33, wherein, one or more of the first timing indication, the second timing indication, and the third timing indication are based on one or more parameters comprising one or more of: timing information associated with signaling between the WD (22) and the network node (16); a carrier frequency; a numerology; a bandwidth part; a time division duplex, TDD, pattern; a transmission direction; a reference signal configuration; and a subcarrier spacing of at least one downlink reference signal. the method further comprises performing one or more actions comprising one or more of:

35. The method of any one of claims 25-34, wherein, causing the WD (22) to switch to a beam indicated in the WD-initiated beam report within the beam switch delay in case the network node (16) indicates the beam to the WD (22); causing the WD (22) to switch to the beam indicated in response to transmitting the WD-initiated beam report and to perform the fallback switch associated with the WD-initiated beam management procedure in case no switch response is received from the network node (16); and receiving at least one WD-initiated beam report based on the third timing indication.

36. A network node (16) configured to perform a wireless device, WD, initiated beam management procedure and to communicate with a WD (22), the network node (16) being configured to: receive a WD-initiated beam report from the WD (22), the WD-initiated beam report being associated with one or more of: a first timing indication indicating a beam switch delay, a second timing indication indicating when to perform a fallback beam switch associated with the WD-initiated beam management procedure, and a third timing indication indicating a minimum time between two WD-initiated beam reports; determine a beam based on the WD-initiated beam report; and one or both of: transmitting a beam indication to the WD (22) indicating the beam, and transmitting a WD switch response to the WD (22) indicating to switch to the beam. the WD-initiated beam report indicates one or more beams.

37. The network node (16) of Claim 36, wherein, the network node (16) is further configured to perform one or more of:

38. The network node (16) of any of one of Claims 36 and 37, wherein, receiving a fourth indication indicating that the WD (22) is to signal the WD-initiated beam report; receiving the WD-initiated beam report; transmitting a fifth indication to the WD (22) indicating one or both of a WD-initiated beam report confirmation and the beam; and ​ ​ to apply a spatial filter responsive to the fifth indication and one or both of the determined beam switch delay and the beam application time.

39. The network node (16) of any of claims 36-38, wherein, The transmitted beam indication triggers the WD (22) to perform one or more of: determining a storage time period for the WD (22) to store quasi co-location, QCL, related information associated with one or more beams indicated in the WD initiated beam report; storing the QCL related information for the storage time period; and within the beam switch delay, switching to a beam of the one or more beams indicated in the WD initiated beam report using the QCL related information. Performing the fallback beam switch includes:

40. The network node (16) of any of claims 36-39, wherein, switching from a first beam to a second beam indicated in the WD initiated beam report; and switching back to the first beam if the WD (22) does not receive a beam switch response from the network node (16) after a predetermined time has elapsed. The network node (16) is further configured to:

41. The network node (16) of Claim 40, wherein, The third timing indication is based on a first configuration and indicates one or more of: sending to the WD (22) an indication of a back-off timing configuration corresponding to the predetermined time a sixth indication of the sixth indication.

42. The network node (16) of any of claims 36-41, wherein, a minimum time between two sequential WD initiated beam reports; a minimum time between two sequential fourth indications, each fourth indication indicating to the network node (16) that the WD (22) has at least one WD initiated beam report to transmit; a minimum time between two WD initiated beam reports indicating a same preferred candidate beam; and a minimum time between two WD initiated beam reports indicating different preferred candidate beams. The WD (22) is configured with a second configuration comprising joint or separate timing limits associated with the third timing indication for downlink serving links and uplink serving links when the WD (22) is configured with separate downlink transmission configuration indicator, TCI, states and uplink TCI states. The WD (22) is configured with a third configuration comprising a maximum number of WD initiated beam reports within a time period.

43. The network node (16) of any of claims 36-42, wherein, One or more of the first timing indication, the second timing indication, and the third timing indication are based on one or more parameters comprising one or more of:

44. The network node (16) of any of claims 36-43, wherein, timing information associated with signaling between the WD (22) and the network node (16); 45. The network node (16) of any of claims 36-44, wherein, a carrier frequency; a numerology; a bandwidth part; a time division duplex, TDD, pattern; a transmission direction; a reference signal configuration; and a subcarrier spacing of at least one downlink reference signal. The network node (16) is further configured to perform one or more actions comprising one or more of: ​ ​ 46. The network node (16) of any of claims 36-45, wherein, ​ causing the WD (22) to switch to a beam indicated in response to transmitting the WD-initiated beam report, and in the absence of receiving a switch response from the network node (16), to perform the fallback switch associated with the WD-initiated beam management procedure; and receiving at least one WD-initiated beam report based on the third timing indication. ​

Images