Wireless communication technology for high-speed vehicles

Abstract

The present application relates to devices and components, including apparatus, systems, and methods, for dealing with Doppler shift in wireless communication systems.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 291,277, entitled "TECHNOLOGIES IN WIRELESS COMMUNICATIONS IN CONSIDERATION OF HIGH-SPEED VEHICLE," filed on December 17, 2021, and U.S. Nonprovisional Patent Application No. 18 / 072,415, entitled "TECHNOLOGIES IN WIRELESS COMMUNICATIONS IN CONSIDERATION OF HIGH-SPEED VEHICLE," filed on November 30, 2022, the disclosures of which are incorporated by reference herein in their entireties for all purposes.

[0002] User equipment (UE) and transmission / reception points (TRP) in a 3rd Generation Partnership Project (3GPP) network rely on communication scheduling for proper interpretation of data being exchanged between the UE and the TRP. Generally, communication scheduling results in communications or communication opportunities being scheduled at uniform time intervals, such as being scheduled at a particular frequency.

[0003] However, as either the UE and / or TRP are moved, the time at which the communication is received at the receiving UE or TRP may differ from the uniform time interval and / or frequency at which the receiving UE or TRP expects to receive the communication. For example, when the UE and / or TRP are moved, the Doppler effect caused by the movement can cause a frequency difference between the frequency at which the transmitting device transmits the communication and the frequency at which the receiving device receives the communication. [Brief description of the drawings]

[0004] [Figure 1] 1 illustrates an example of a network configuration having a high speed vehicle (HSV) scenario, according to some embodiments.

[0005] [Diagram 2] 1 illustrates an example signal flow that can support technique 1.1, technique 1.2, and / or technique 1.3, according to some embodiments.

[0006] [Diagram 3] 1 illustrates an example network configuration illustrating the synchronization signal / physical broadcast channel block (SSB) association technique of technique 1.4, according to some embodiments.

[0007] [Figure 4] 13 illustrates an example signal flow for technique 1.4, according to some embodiments.

[0008] [Diagram 5] 1 illustrates an example signal flow that can support technique 2.1, technique 2.2, technique 2.3, and / or technique 2.4, according to some embodiments.

[0009] [Figure 6] 13 illustrates an example signal flow for Technique 2.5, according to some embodiments.

[0010] [Figure 7] 3 illustrates an example network configuration illustrating the configuration of technique 3.1, according to some embodiments.

[0011] [Figure 8] 1 illustrates an example network configuration illustrating the configuration of technique 3.2, according to some embodiments.

[0012] [Figure 9] 1 illustrates an exemplary procedure according to some embodiments.

[0013] [Figure 10] 1 illustrates an exemplary procedure according to some embodiments.

[0014] [Figure 11] 1 illustrates an exemplary procedure according to some embodiments.

[0015] [Figure 12] 1 illustrates an exemplary procedure according to some embodiments.

[0016] [Figure 13] 1 illustrates an example beamforming circuit in accordance with some embodiments.

[0017] [Figure 14] 1 illustrates an exemplary user equipment (UE) in accordance with some embodiments.

[0018] [Figure 15] 1 illustrates an exemplary next generation Node B (gNB) in accordance with some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be implemented in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this disclosure, "A or B" means (A), (B), or (A and B).

[0020] Below is a glossary of terms that may be used in this disclosure.

[0021] As used herein, the term "circuitry" refers to, is a part of, or includes hardware components configured to provide a described functionality, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, programmable systems on chips (SoCs)), digital signal processors (DSPs), and the like. In some embodiments, a circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" may also refer to the combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit configuration.

[0022] As used herein, the term "processor circuitry" refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or the recording, storage, or transfer of digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device that can execute or otherwise operate computer-executable instructions, such as program code, software modules, or functional processes.

[0023] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as, for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0024] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may represent a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless equipment, reconfigurable wireless equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0025] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or components thereof. In addition, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to each other and configured to share computing or networking resources.

[0026] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component in a computing environment, or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and application, workload units, etc. A "hardware resource" may refer to a computational, storage, or network resource provided by a physical hardware element(s). A "virtualized resource" may refer to a computational, storage, or network resource provided by a virtualization infrastructure to an application, device, system, etc. The term "network resource" or "communication resource" may refer to a resource accessible by a computer device / system via a communication network. The term "system resource" may refer to any kind of shared entity for providing services and may include a computing resource or a network resource. A system resource may be thought of as a set of coherent functions, network data objects or services that reside on a single host or on multiple hosts and are accessible through a clearly identifiable server.

[0027] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0028] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, such as may occur during the execution of program code.

[0029] The term "connected" may mean that two or more elements at a common communications protocol layer have an established signaling relationship with each other via a communications channel, link, interface, or reference point.

[0030] As used herein, the term "network element" refers to a physical or virtualized device or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered or referred to as synonymous with networked computer, networking hardware, network equipment, network node, virtualized network function, and the like.

[0031] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an information element or an individual content of a data element that contains the content. An information element may contain one or more further information elements.

[0032] Issuance Statement

[0033] High Speed ​​Vehicles (HSVs) are a deployment scenario of great interest to a few operators, especially Chinese operators such as China Mobile Communications Corporation (CMCC). HSVs may be defined as any user equipment moving at high speed. For example, HSVs may include user equipment moving at or above 350 kilometers per hour (km / h). In some embodiments, HSVs may include high speed trains (HSTs). HSV extensions are being considered for Further Enhanced Multiple Input Multiple Output (FeMIMO) in Release 17 (Rel-17).

[0034] In an HSV scenario, a UE (such as a train with wireless communication capabilities or another UE capable of transportation at high speed) moves between two transmit / receive points (TRPs). The UE may observe a very high positive Doppler shift from one TRP and a very high negative Doppler shift from the other TRP. As a result, the composite channel may change at a very fast rate approaching or even exceeding 2 kilohertz (kHz). This could potentially reduce the channel capability or make it very difficult for the UE to perform an accurate channel estimation.

[0035] 1 illustrates an example network configuration 100 having an HSV condition, according to some embodiments. The illustrated network configuration 100 provides an exemplary illustration of a Doppler shift that may occur when an HSV condition is presented. In particular, an HSV condition may be presented when an element of the network is moving at a high speed compared to other elements of the network with which it is to communicate. In some embodiments, the rate of speed difference between the element and other elements of the network may be 350 km / h or more.

[0036] The network configuration 100 may include one or more TRPs. For example, the network configuration 100 shows a first TRP 102 and a second TRP 104 in the illustrated embodiment. The first TRP 102 and / or the second TRP 104 may include a portion of a network that may be utilized to wirelessly communicate with a UE. For example, the first TRP 102 and / or the second TRP 104 may include a Node B (such as a Node B, an evolved Node B (eNB), a next generation Node B (gNB), or some combination thereof). In some instances, the first TRP 102 and / or the second TRP 104 may include a wireless-enabled device that may route signals between the Node B and the UE. Each of the first TRP 102 and / or the second TRP 104 may include one or more of the features of a gNB 1500 (FIG. 15) in some embodiments.

[0037] The network configuration 100 may further include one or more UEs. For example, the network configuration 100 shows a UE 106 in the illustrated embodiment. The UE 106 may wirelessly communicate with the first TRP 102 and / or the second TRP 104. In particular, the UE 106 may utilize the first TRP 102 and / or the second TRP 104 to communicate with the network. The UE 106 may include one or more of the features of the UE 1400 (FIG. 14) in some embodiments.

[0038] In the illustrated embodiment, the UE 106 may be moving at a high speed, as indicated by the arrow 108. In particular, the UE 106 is shown in the illustrated embodiment as traveling at a high speed relative to the first TRP 102 and the second TRP 104, with the UE traveling toward the first TRP 102 and away from the second TRP 104. The speed at which the UE 106 is traveling may be 350 km / h or more relative to the first TRP 102 and the second TRP 104 in some embodiments. For example, the first TRP 102 and the second TRP 104 may be stationary, but the UE 106 is traveling toward the first TRP 102 and away from the second TRP 104 at a speed of 350 km / h or more.

[0039] Due to the speed at which the UE 106 is moving relative to the first TRP 102 and the second TRP 104, a Doppler shift may affect signals transmitted between the first TRP 102, the second TRP 104, and the UE 106. To illustrate the Doppler shift that may affect signals, the network configuration 100 shows a set of signals emitted from the UE 106 represented by a first set of lines 110 directed to the first TRP 102 and a second set of lines 112 directed to the second TRP 104. The set of signals may be omitted from the UE 106 with a uniform frequency. However, due to the movement of the UE 106, a Doppler shift may spatially condense the signals in the direction in which the UE 106 is moving and spatially expand the signals in the direction in which the UE 106 is traveling. In particular, a first set of lines 110 representing the set of signals are shown closer together to show the effect of a positive Doppler shift for the set of signals in the direction that the UE 106 is moving towards, and a second set of lines 110 representing the set of signals are shown farther apart to show a negative Doppler shift for the set of signals in the direction that the UE 106 is moving away from.

[0040] Without compensation, an element receiving a signal can expect to receive the signal at the same frequency at which the element transmitted the signal. For example, the first TRP 102 and the second TRP 104 can expect to receive the signal transmitted by the UE 106 at the frequency at which the UE 106 transmitted the signal. However, due to Doppler shift, the frequency of the signal received by the first TRP 102 and the second TRP 104 may be different from the frequency at which the UE 106 emitted the signal. The first TRP 102 and the second TRP 104 may have problems processing the signal due to uncompensated Doppler shift.

[0041] To prevent and / or reduce the possibility of errors occurring in transmitting and / or processing signals, techniques for compensating for Doppler shifts may be utilized by elements. Generally, there are two techniques. The first technique, sometimes referred to as High Speed ​​Vehicle (HSV)-Single Frequency Network (SFN) Scheme 1, may allow the UE to estimate two separate Doppler shifts, one from each TRP. This may be used to assist UE channel estimation. For example, the HSV-SFN Scheme 1 may allow the UE 106 to estimate a first Doppler shift between the first TRP 102 and the UE 106, and a second Doppler shift between the second TRP 104 and the UE 106. The UE 106 may utilize the estimated Doppler shifts when transmitting signals to and / or processing signals from the first TRP 102 and / or the second TRP 104. In other embodiments, the UE 106 may provide the estimated Doppler shift to the first TRP 102 and / or the second TRP 104 to compensate for the Doppler shift. HSV, as used herein, may refer to a high-speed train (HST) or other vehicle or mechanism for transporting the UE. Thus, in some embodiments, the HSV-SFN method 1 may include the HST-SFN method 1.

[0042] A second approach to address the Doppler shift includes HSV-SFN with pre-compensation. This approach may allow the network (NW) to pre-compensate for the Doppler shift. The NW may need to know the Doppler shift. For example, the first TRP 102 and / or the second TRP 104 (and / or the network of which the first TRP 102 and / or the second TRP 104 are a part) may estimate the Doppler shift between the first TRP 102 and the UE 106 and between the second TRP 104 and the UE 106. The first TRP 102 and / or the second TRP 104 (and / or the network of which the first TRP 102 and / or the second TRP 104 are a part) may utilize the Doppler shift when transmitting signals to the UE 106 and / or when processing signals from the UE 106.

[0043] Two modes of HSV extensions may be supported in 3rd Generation Partnership Project (3GPP) Rel-17 New Radio (NR). The first mode may be HSV-SFN mode 1. In HSV-SFN mode 1, the NW does not perform Doppler shift pre-compensation. Furthermore, in HSV-SFN mode 1, the Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) / Demodulation Reference Signal (DMRS) may be transmitted based on SFN operation. The second mode may be HSV-SFN with NW pre-compensation. In HSV-SFN with NW pre-compensation mode, the NW performs Doppler shift pre-compensation. Furthermore, in HSV-SFN using NW pre-compensation mode, the PDSCH / DMRS may be transmitted based on Single Frequency Network (SFN) operation.

[0044] The approaches disclosed herein can provide design details for HSV-SFN scheme 1 and pre-compensation. In a first approach, a design for HSV-SFN scheme 1 is disclosed. In a second approach, a design for HSV-SFN with pre-compensation is disclosed. In a third approach, a group-based transmission configuration indicator (TCI) update is disclosed. Method 1: Design for HSV-SFN Method 1

[0045] A first group of approaches presented herein may relate to HSV-SFN scheme 1 design. For example, the approaches may be utilized to configure a UE (such as the UE 106) to execute HSV-SFN scheme 1 to compensate for Doppler shifts. The UE may be configured to estimate one or more Doppler shifts associated with a TRP and utilize the estimated Doppler shifts to compensate for the Doppler shifts.

[0046] As described further throughout this disclosure, the single TRP approach may be configured by the UE and / or the network. In the single TRP approach, the UE may communicate with a single TRP rather than with two TRPs as implemented by HSV-SFN scheme 1. Additionally, the UE may or may not support dynamic switching. Dynamic switching may include switching from a first state in one slot to another state in the next slot. For example, dynamic switching may include switching from HSV-SFN scheme 1 in one slot to a single TRP in the next slot, or vice versa.

[0047] Approach 1.0: For PDSCH, radio resource control (RRC) parameters are used to configure the UE to operate in HSV-SFN scheme 1. For example, the network and / or a TRP (such as the first TRP 102 (FIG. 1) and / or the second TRP 104 (FIG. 1)) of the network may provide RRC communication to the UE to configure the UE to operate in HSV-SFN scheme 1, and the RRC communication may include RRC parameters. Option 1: RRC parameters are configured per component carrier (CC) for PDSCH. For example, the RRC parameters provided to the UE may define parameters for HSV-SFN scheme 1 per CC, and the UE may configure each CC according to the corresponding RRC parameters. Different CCs may correspond to different RRC parameters. In option 1, dynamic bandwidth portion (BWP) switching may not be used to change the PDSCH operation mode, and only RRC reconfiguration may be used to change the PDSCH operation mode. Option 2: RRC parameters are configured per BWP per CC of the PDSCH. For example, the RRC parameters provided to the UE may define parameters for HSV-SFN scheme 1 for each BWP, and the UE may configure each BWP according to the corresponding RRC parameters. Different BWPs may correspond to different RRC parameters. In option 2, dynamic BWP switching may be used to change the PDSCH operation mode.

[0048] Technique 1.1: PDSCH TCI codepoint activation. In particular, technique 1.1 may be utilized for TCI codepoint activation for PDSCH. If RRC parameters are used to configure a UE to operate in HSV-SFN scheme 1 per CC, for example, the RRC parameters may cause the UE to configure all BWPs in the same CC corresponding to the RRC parameters with HSV-SFN scheme 1 or a single TRP in all BWPs configured in the corresponding CC. Different CCs may be configured in different ways, such that all CCs may be configured in HSV-SFN scheme 1, all CCs may be configured in a single TRP, or a portion of a CC may be configured in HSV-SFN scheme 1 and another portion of a CC may be configured in a single TRP. If RRC parameters are used to configure a UE to operate in HSV-SFN scheme 1 per BWP per CC, for example, the RRC parameters may cause the UE to configure a BWP corresponding to the RRC parameters with HSV-SFN scheme 1 or a single TRP in all BWPs configured in the corresponding CC. Different BWPs may be configured in different ways, such that all BWPs may be configured in HSV-SFN scheme 1, all BWPs may be configured in a single TRP, or a portion of the BWPs may be configured in HSV-SFN scheme 1 and another portion of the BWPs may be configured in a single TRP. In one embodiment, the base station may configure up to four BWPs in a CC. Each BWP in a CC may be configured in the same way or in different ways.

[0049] The following are restrictions on PDSCH TCI codepoint activation. For example, the PDSCH TCI codepoint activation of method 1.1 may have the following characteristics: If the UE does not support dynamic switching between HSV-SFN scheme 1 and a single TRP, the NW may only use a medium access control-control element (MAC-CE) to activate a TCI codepoint with two TCI states. For example, the UE may indicate to the network or the network's TRP that the UE does not support dynamic switching. Based on the indication that the UE does not support dynamic switching, the network may limit the activation of the TCI codepoint to two TCI states. The network may provide the UE with a MAC-CE to activate a TCI codepoint with two TCI states. Otherwise, if the UE supports dynamic switching between HSV-SFN scheme 1 and a single TRP, the NW may use a MAC-CE to activate a TCI codepoint with either one TCI state or two TCI states. For example, the UE may indicate to the network or the network's TRP that the UE supports dynamic switching. Based on the indication that the UE supports the switching, the network may activate a TCI codepoint with one TCI state or two TCI states.

[0050] Approach 1.2: Regarding the UE capability of supporting HSV-SFN scheme 1 for PDCCH, whether the UE supports it. For example, approach 1.2 may be applied when HSV-SFN scheme 1 is supported by the UE for PDCCH. In some embodiments, approach 1.2 may be further based on whether the UE supports mixed operation of control resource set (CORESET) for application of approach 1.2. In approach 1.2, a CORESET in an active BWP may be configured with different numbers of TCI states. In some CORESETs in an active BWP, only a single TCI state is activated by the MAC-CE. In some CORESETs in an active BWP, two TCI states are activated by the MAC-CE. For example, the network and / or the TRP (such as the first TRP 102 (FIG. 1) and / or the second TRP 104 (FIG. 1)) may provide the UE with a MAC-CE that causes the UE to configure a corresponding CORESET with a single TCI state or two TCI states. The MAC-CE may configure the UE all CORESETS in active BWPs with a single TCI state, all CORESETS in active BWPs with two TCI states, or a first portion of CORESETS in active BWPs with a single TCI and a second portion of CORESETS in active BWPs with two TCI states. The MAC-CE may configure up to three CORESETS in each BWP in some embodiments, and the CORESETs may be configured with different numbers of TCI states.

[0051] The following are options for method 1.2. Option 1: When the UE supports HSV-SFN scheme 1 for PDCCH, the UE may report whether the UE supports it. For example, whether the terminal supports HSV-SFN scheme 1 may be selective. Thus, some UEs may not support HSV-SFN scheme 1 in some cases. The UE may send a signal to the network and / or the network's TRP to indicate whether the UE supports HSV-SFN. In some embodiments, the signal sent by the UE may indicate whether the UE supports CORESET mixed operation in addition to or instead of indicating whether the UE supports HSV-SFN scheme 1. The CORESET mixed operation may include configuring a part of the CORESET of the active BWP in one state (e.g., HSV-SFN scheme 1) and configuring another part of the CORESET of the active BWP in another state (e.g., single TRP). Option 2: If the UE supports HSV-SFN scheme 1, the UE must support CORESET mixed operation. For example, in option 2, all UEs may support mixed operation of the CORESET. In the case where the UE supports mixed operation of the CORESET, the network and / or the TRP of the network may allow the UE to configure a first part of the CORESET using HSV-SFN scheme 1 and configure a second part of the CORESET using a single TRP.

[0052] Approach 1.3: If the UE indicates that the UE does not support mixed operation of CORESET, for all CORESETs configured in the active BWP in the CC NW, activate all CORESETs with two TCI states via MAC-CE or activate all CORESETs with a single TCI state via MAC-CE. For example, the UE can provide an indication that the UE does not support mixed operation of CORESET. The indication can be in addition to the indication that the UE supports HSV-SFN. The network and / or TRP of the network can determine that the UE does not support mixed operation of CORESET based on the indication from the UE. Based on the network and / or TRP determining that the UE does not support mixed operation, the network and / or TRP can either activate all CORESETs in the active BWP with two TCI states or activate all CORESETs in the active BWP with a single TCI state. The network and / or TRP may provide the MAC-CE to the UE and cause the UE to activate all CORESETs in an active BWP with two TCI states or to activate all CORESETs in an active BWP with a single TCI state.

[0053] FIG. 2 illustrates an example signal flow 200 that can support technique 1.1, technique 1.2, and / or technique 1.3, according to some embodiments. In particular, signal flow 200 illustrates signals that can be exchanged between UE 202 and TRP 204. It should be understood that the signals in signal flow 200 can be transmitted in a different order and / or simultaneously than shown. In addition, signal flow 200 may omit some signals (such as acknowledgement signals and / or failure signals) that can be transmitted in configuring technique 1.1, technique 1.2, and / or technique 1.3. Furthermore, one or more of the signals illustrated in signal flow 200 may be omitted in some embodiments. UE 202 may include one or more of the features of UE 106 (FIG. 1). TRP 204 may include one or more of the features of first TRP 102 (FIG. 1) and / or second TRP 104 (FIG. 1).

[0054] The signal flow 200 may begin with the UE 202 sending a support indication 206 to the TRP 204 indicating features that are supported and / or not supported by the UE 202. In some embodiments, the support indication 206 may include one or more UE capability reports indicating the capabilities of the UE 202. The support indication 206 may indicate whether the UE 202 supports HSV-SFN, mixed CORESET operation, or some combination thereof. For example, the support indication 206 may include a UE capability report indicating whether the UE 202 supports HSV-SFN and / or a UE capability report indicating whether the UE 202 supports mixed CORESET operation. Additionally, the support indication 206 may include an indication of whether the UE 202 supports HSV-SFN scheme 1 in some embodiments. The support indication 206 may further include an indication of which channels and / or elements each of the features is supported. For example, the support indication 206 may indicate that HSV-SFN, mixed CORESET operation, and / or HSV-SFN scheme 1 are supported for the PDSCH, PDCCH, and / or CORESET in some embodiments. In some embodiments, the UE 202 may provide the support indication 206 in response to a capability request provided to the UE 202 by the TRP 204. In other embodiments, the UE 202 may provide the support indication 206 upon joining a network (e.g., the UE 202 registers with the network and / or the UE 202 is powered on), and the network may store the information included in the support indication 206.

[0055] Based on the support indication 206, the network and / or TRP 204 can determine which configurations the UE 202 is capable of supporting. For example, the network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN based on an indication of whether the UE 202 supports HSV-SFN included in the support indication 206 in some embodiments. In an embodiment in which the support indication 206 includes a UE capability report indicating whether the UE 202 supports HSV-SFN, the network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN based on the UE capability report. Thus, the network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN for technique 1.1, technique 1.2, and / or technique 1.3. In some embodiments, the network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN technique 1 based on an indication included in the support indication 206.

[0056] The network and / or TRP 204 can further determine the channels (e.g., PDSCH and / or PDCCH) and / or elements (e.g., CORESET) for which the UE 202 supports HSV-SFN and / or HSV-SFN scheme 1 based on the indication included in the support indication 206. For example, the network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN and / or HSV-SFN scheme 1 for PDSCH for scheme 1.1. The network and / or TRP 204 can determine whether the UE 202 supports HSV-SFN and / or HSV-SFN scheme 1 for PDDCH and / or CORESET for scheme 1.2 and / or scheme 1.3.

[0057] For approach 1.2 and / or approach 1.3, the network and / or TRP 204 may further determine whether the UE 202 supports mixed CORESET operation based on the indication included in the support indication 206. In an embodiment where the support indication 206 includes a UE capability report indicating whether the UE 202 supports mixed CORESET operation, the network and / or TRP 204 may determine whether the UE 202 supports mixed CORESET operation based on the UE capability report.

[0058] The network and / or TRP 204 may determine the HSV-SFN state configuration for the UE 202. In an embodiment where a support indication 206 is included, the network and / or TRP 204 may determine the HSV-SFN state configuration based on information in the support indication 206. The TRP 204 may provide the UE 202 with an HSV-SFN state configuration communication 208 indicating the configuration for the UE 202. The HSV-SFN state configuration communication 208 may indicate that the UE 202 should operate with HSV-SFN scheme 1 and / or a single TRP. For scheme 1.1, the HSV-SFN state configuration communication 208 may indicate per CC or per BWP per CC that HSV-SFN scheme 1 or a single TRP is configured. For example, the HSV-SFN state configuration communication 208 may indicate in which state each of the CCs is configured or in which state each of the BWPs is configured for scheme 1.1. For approach 1.2 and / or approach 1.3, the HSV-SFN state configuration communication 208 may indicate whether the CORESET in the active BWP is configured with HFT-SFN approach 1 or a single TRP. In some embodiments, the HSV-SFN state configuration communication 208 may include an RRC communication.

[0059] The UE 202 may receive the HSV-SFN state configuration communication 208 and determine the state configuration to be configured by the UE 202. For example, the UE 202 may determine which of the HSV-SFN scheme 1 and / or the single TRP are configured by the UE 202. The UE 202 may further determine which of the CC and / or the BWP are configured with the HSV-SFN scheme 1 and / or the single TRP for the technique 1.1. The UE 202 may determine which CORESET is configured with the HSV-SFN scheme 1 and / or the single TRP for the technique 1.2 and / or the technique 1.3. At 210, the UE 202 may configure itself according to the state determined from the HSV-SFN state configuration communication 208. For example, the UE 202 may configure the CC and / or the BWP according to the determined HSV-SFN scheme 1 and / or the single TRP from the HSV-SFN state configuration communication 208 for the technique 1.1. For approach 1.2 and / or approach 1.3, the UE 202 may configure a CORESET according to the determined HSV-SFN approach 1 and / or single TRP from the HSV-SFN state configuration communication 208.

[0060] The network and / or TRP 204 may further determine a TCI configuration for the UE 202. In an embodiment in which the support indication 206 is included, the network and / or TRP 204 may determine a TCI configuration for the UE 202 based on information in the support indication 206. For example, the network and / or TRP 204 may determine that the UE 202 should have a TCI codepoint activated in two TCI states based on an indication that the UE 202 does not support dynamic switching from the support indication 206 for technique 1.1. Furthermore, the network and / or TRP 204 may determine that the UE 202 should have a TCI codepoint activated in one TCI state or two TCI states based on an indication that the UE 202 supports dynamic switching from the support indication 206 for technique 1.1. In approach 1.2 and / or approach 1.3, the network and / or TRP 204 may determine that the UE 202 may have a CORESET activated in a mix of a single TCI state and two TCI states based on an indication that the UE 202 supports mixed operation of CORESET in the support indication 206. Further, with respect to approach 1.2 and / or approach 1.3, the network and / or TRP 204 may determine that the UE 202 may have all CORESETs activated in two TCI states or all CORESETs activated in a single TCI state based on an indication that the UE 202 does not support mixed operation of CORESET in the support indication 206. The network and / or TRP 204 may generate a TCI configuration communication 212 indicating a TCI configuration for the UE 202 and may provide the TCI configuration communication 212 to the UE 202. In some embodiments, the TCI configuration communication 212 may include a MAC-CE.

[0061] The UE 202 may determine a TCI configuration for the UE 202 based on the TCI configuration communication 212. For example, the UE 202 may determine which CC or BWP is activated with one TCI state and which CC or BWP is activated with two TCI states based on the TCI configuration communication 212 for technique 1.1. For techniques 1.2 and 1.3, the UE 202 may determine which CORESET is activated with one TCI state and which CORESET is activated with two TCI states based on the TCI configuration communication 212. At 214, the UE 202 may activate the CC, BWP, or CORESET according to the determined state. For example, the UE 202 may activate each of the CCs or BWPs with one TCI state or two TCI states according to the determination from the TCI configuration communication 212 for technique 1.1. In particular, the TCI codepoints for CC or BWP may be activated in one TCI state or two TCI states. For approach 1.2 and / or approach 1.3, UE 202 may activate a CORESET having one TCI state or two TCI states according to a determination from TCI configuration communication 212. In particular, the TCI codepoints for CORESET may be activated in one TCI state or two TCI states.

[0062] At 216, the UE 202 may perform channel estimation. For example, the UE 202 may perform channel estimation to determine a Doppler shift based on the TCI code point. The UE 202 may estimate a Doppler shift that may be caused by movement of the UE 202 and / or the TRP 204. The UE 202 may utilize the estimated Doppler shift to compensate for the Doppler shift in the communication. For example, the TRP 204 may transmit a signal 218 to the UE 202, and the UE 202 may utilize the determined Doppler shift estimate in decoding the signal 218. By compensating for the Doppler shift, the UE 202 may properly interpret the signal. The UE 202 may also utilize the estimated Doppler shift for compensation of the signal transmitted by the UE 202 to the TRP 204.

[0063] In some cases, the TRP 204 may further provide a switching TCI communication 220 to the UE 202. The switching TCI communication 220 may indicate the TCI code points to be switched and / or the updated TCI configuration for the UE 202. For example, the switching TCI communication 220 may indicate that one or more TCI code points are switched from activation with one TCI state to activation with two TCI states and / or from activation with two TCI states to activation with one TCI state. The switching TCI communication 220 may indicate the CC, BWP, and / or CORESET corresponding to the switched TCI code points. For technique 1.1, the switching TCI communication 220 may indicate which CC or BWP may be switched activation on a per-CC or per-BWP basis. For techniques 1.2 and 1.3, the switching TCI communication 220 may indicate which CORESET may be switched activation. At 222, the UE 202 may switch activation of the TCI codepoint according to the indication in the TCI switch communication 220.

[0064] Approach 1.4: For time and frequency tracking, the NW explicitly or implicitly configures the association of a synchronization signal / physical broadcast channel block (SSB) with a TRP. For example, the network and / or the TRP of the network can configure or provide configuration information to the UE so that the UE can associate the SSB with the TRP that provides the SSB. Implicit configuration: The NW configures the SSB to be a quasi-co-located (QCL) source of a tracking reference signal (TRS), which implicitly indicates the association between the SSB and the TRP, since the TRS is used for the QCL source of the PDSCH / demodulation reference signal (DMRS). For example, the network and / or the TRP can provide the UE with configuration information that causes the UE to configure the SSB as a QCL source of the TRS, which may be part of the TRS configuration. The UE can know which TRS is associated with which TRP, which may be derived from the QCL TCI state configuration. The UE can determine which SSB is associated with which TRP based on the SSB configured as a QCL source of the TRS and the known association of the TRS with the TRP. Thus, the network and / or the TRP can implicitly configure the association of the SSB with the TRP in the implicit configuration of method 1.4. If the SSB is not configured as a QCL source of the TRS used for PDSCH / DMRS QCL indication, the UE cannot assume the association of the SSB with any TRP. For example, if the SSB is not configured as a QCL source of the TRS, the UE may not be able to determine the source TRP of the SSB.

[0065] Explicit Configuration 1: When the NW activates TCI code points for PDSCH using MAC-CE, the NW configures an association between each TCI code point and a different SSB. For example, the network and / or the TRP of the network can provide an association between the TCI code points and the SSB. The network and / or the TRP can provide the association when providing the activation for the TCI code point, such as by including an indication of the association in the TCI configuration communication 212 (FIG. 2). In some embodiments, the indication of the association can include a mapping between the TCI code points and the SSB. In some embodiments, the indication of the association can include a MAC-CE. The TCI code points can include a TRS, and the UE can know which TRS is associated with which TRP. The UE can determine which SSB corresponds to which TRP based on the association between the TCI code points and the SSB and the relationship between each TRS and each TRP. Thus, the network and / or the TRP can explicitly configure the association between the SSB and the TRP in Explicit Configuration 1 of Method 1.4. For an SSB that is not configured with an association, the UE cannot assume an association between the SSB and any TRP. For example, if an SSB is not configured as a QCL source for a TRS, the UE may not be able to determine the source TRP for the SSB.

[0066] Explicit configuration 2: The NW independently configures for each SSB whether it is from a first TRP, a second TRP, or neither. For example, the network and / or the network's TRPs may provide a separate communication to the UE indicating which SSB is associated with which TRP. The separate communication may include a MAC-CE or an RRC. The MAC-CE and RRC for the association indication may be separate from other MAC-CE and / or RRC utilized for HSV-SFN state configuration and / or TCI configuration. In some embodiments, the indication may include a mapping (such as a bitmap) indicating which SSB is associated with which TRP. Based on the separate communication, the UE may determine which SSB is received from which TRP.

[0067] 3 illustrates an example network configuration 300 illustrating an SSB association technique of technique 1.4 according to some embodiments. In particular, the network configuration 300 illustrates an association between an SSB and a TRP that may be configured according to technique 1.4.

[0068] The network configuration 300 may include one or more TRPs. In the illustrated embodiment, the network configuration 300 includes a first TRP 302 and a second TRP 304. The first TRP 302 and the second TRP 304 may include one or more of the features of the first TRP 102 (FIG. 1) and / or the second TRP 104 (FIG. 1). The network configuration 300 may further include a UE 306. The UE 306 may include one or more of the features of the UE 106.

[0069] Each of the TRPs may provide one or more SSBs and / or one or more TRSs to the UE. In the illustrated embodiment, the first TRP 302 may provide the first SSB 308 and the second SSB 310 to the UE 306. Additionally, the first TRP 302 may provide the first TRS 312 and the second TRS 314 to the UE 306. The first TRP 302 may provide the first SSB 308 and the first TRS 312 to the UE 306 via one or more signals, which may be carried in the first beam 316. The first TRP 302 may provide the second SSB 310 and the second TRS 314 to the UE 306 via one or more signals, which may be carried in the second beam 318.

[0070] In the illustrated embodiment, the second TRP 304 may provide the third SSB 320 and the fourth SSB 322 to the UE 306. Additionally, the second TRP 304 may provide the third TRS 324 and the fourth TRS 326 to the UE 306. The second TRP 304 may provide the third SSB 320 and the third TRS 324 to the UE 306 via one or more signals, which may be carried in the third beam 328. The second TRP 304 may provide the fourth SSB 322 and the fourth TRS 326 to the UE 306 via one or more signals, which may be carried in the fourth beam 330.

[0071] The network via the first TRP 302 and / or the second TRP 304 provides the UE 306 with one or more indications that can be utilized to determine which SSBs are provided by which TRP. In the implicit configuration of approach 1.4, the network can configure each of the SSBs as a QCL source for the corresponding TRS. The network can provide one or more TCI configuration communications (such as the TCI configuration communications 212 (FIG. 2)) to the UE 306 via the first TRP 302 and / or the second TRP 304, which can cause the UE 306 to configure the SSBs as QCL sources for the corresponding TRS. In other embodiments, the UE 306 can be configured at production and / or upon joining the network to determine that the SSBs configured as QCL sources for the TRSs are associated with the same TRP as the TRSs for which the SSBs are configured as QCL sources. For example, the network can configure the first SSB 308 as a QCL source for the first TRS 312. Because the UE 306 knows that the first TRS 312 is associated with the first TRP 302, the UE 306 can determine that the first SSB 308 is associated with the first TRP 302 based on the first SSB 308 being configured as a QCL source for the first TRS 312. Additionally, the network can configure the second SSB 310 as a QCL source for the second TRS 314. Because the UE 306 knows that the second TRS 314 is associated with the first TRP 302, the UE 306 can determine that the second SSB 310 is associated with the first TRP 302 based on the second SSB 310 being configured as a QCL source for the second TRS 314. The network can configure the third SSB 320 as a QCL source for the third TRS 324. Because the UE 306 is aware that the third TRS 324 is associated with the second TRP 304, the UE 306 can determine that the third SSB 320 is associated with the second TRP 304 based on the third SSB 320 being configured as a QCL source for the third TRS 324.Additionally, the network may configure the fourth SSB 322 as a QCL source for the fourth TRS 326. Because the UE 306 knows that the fourth TRS 326 is associated with the second TRP 304, the UE 306 may determine that the fourth SSB 322 is associated with the second TRP 304 based on the fourth SSB 322 being configured as a QCL source for the fourth TRS 326.

[0072] In Explicit Configuration 1 of Method 1.4, the network can configure an association of each of the SSBs with a TCI code point. The TCI code point can be a TCI code point for the PDSCH. For example, the network can provide the UE 306 with one or more indications of which SSBs are associated with which TCI code points via the first TRP 302 and / or the second TRP 304. The network can provide the indications within a TCI configuration communication (such as the TCI configuration communication 212 (FIG. 2)). For example, the network can provide one or more indications indicating that the first SSB 308 is associated with a code point of the first TRS 312, the second SSB 310 is associated with a code point of the second TRS 314, the third SSB 320 is associated with a code point of the third TRS 324, and the fourth SSB 322 is associated with a fourth TRS 326. Because the UE 306 is aware that the first TRS 312 is associated with the first TRP 302, the UE 306 can determine that the first SSB 308 is associated with the first TRP 302 based on the indicated association between the first SSB 308 and the TCI codepoint of the first TRS 312. Because the UE 306 is aware that the second TRS 314 is associated with the first TRP 302, the UE 306 can determine that the second SSB 310 is associated with the first TRP 302 based on the indicated association between the second SSB 310 and the TCI codepoint of the second TRS 314. Because the UE 306 knows that the third TRS 324 is associated with the second TRP 304, the UE 306 can determine that the third SSB 320 is associated with the second TRP 304 based on the indicated association between the third SSB 320 and the TCI codepoint of the third TRS 324.Because the UE 306 knows that the fourth TRS 326 is associated with the second TRP 304, the UE 306 can determine that the fourth SSB 322 is associated with the second TRP 304 based on the indicated association between the fourth SSB 322 and the TCI codepoint of the fourth TRS 326.

[0073] In Explicit Configuration 2 of Method 1.4, the network may independently configure an association between each of the SSBs and the corresponding TRP. For example, the network may provide an indication of the association between the SSBs and the TRP to the UE 306 via the first TRP 302 and / or the second TRP 304. The indication of the association may include a mapping (such as a bitmap) between the SSBs and the corresponding TRP. In some embodiments, the network may provide an indication in MAC-CE and / or RRC communications. In the illustrated embodiment, the first TRP 302 and / or the second TRP 304 may provide one or more indications that the first SSB 308 is associated with the first TRP 302, the second SSB 310 is associated with the first TRP 302, the third SSB 320 is associated with the second TRP 304, and the fourth SSB 322 is associated with the second TRP 304. The UE 306 can determine an association between the SSBs and the TRPs based on the indication. In particular, the UE 306 can determine that a first SSB 308 is received from the first TRP 302, a second SSB 310 is received from the first TRP 302, a third SSB 320 is received from the second TRP 304, and a fourth SSB 322 is received from the second TRP 304 based on the indication.

[0074] FIG. 4 illustrates an example signal flow 400 of technique 1.4, according to some embodiments. In particular, signal flow 400 illustrates signals that may be exchanged between UE 402 and TRP 404. It should be understood that the signals in signal flow 400 may be transmitted in a different order and / or simultaneously than shown. In addition, signal flow 400 may omit some signals that may be transmitted in configuration technique 1.4, such as acknowledgement signals and / or failure signals. Furthermore, one or more of the signals illustrated in signal flow 400 may be omitted in some embodiments. UE 402 may include one or more of the features of UE 106 (FIG. 1). TRP 404 may include one or more of the features of first TRP 102 (FIG. 1) and / or second TRP 104 (FIG. 1). In some embodiments, features of signal flow 400 may be combined with features of signal flow 200 (FIG. 2), such as signal flow 400 including features related to configuring HSV-SFN and / or TCI states described with respect to signal flow 200. Thus, technique 1.4 may include one or more of the features of techniques 1.1, 1.2, and / or 1.3, such as configuring HSV-SFN and / or TCI states.

[0075] The signal flow 400 may involve the UE 402 sending a support indication 406 to the TRP 404 indicating features supported and / or not supported by the UE 402. In some embodiments, the support indication 406 may include one or more UE capability reports indicating the capabilities of the UE 402. The support indication 406 may indicate whether the UE supports HSV-SFN. For example, the support indication 406 may include a UE capability report indicating whether the UE 402 supports HSV-SFN. Further, the support indication 406, in some embodiments, may include an indication of whether the UE 402 supports HSV-SFN scheme 1. In some embodiments, the UE 402 may provide the support indication 406 in response to a capability request provided to the UE 402 by the TRP 404. In other embodiments, the UE 402 may provide the support indication 406 when it joins the network (e.g., the UE 402 registers with the network and / or the UE 402 is powered on), and the network may store the information included in the support indication 406.

[0076] Based on the support indication 406, the network and / or TRP 404 may determine whether the UE 402 supports HSV-SFN scheme 1. In some embodiments, the network and / or TRP 404 may determine whether the UE 402 supports SSB association with the TRP, implicit configuration of scheme 1.4, explicit configuration 1 of scheme 1.4, explicit configuration 2 of scheme 1.4, or some combination thereof. The signal flow 400 may proceed to scheme 1.4 in some embodiments based on a determination that the UE supports SSB association with the TRP.

[0077] The network and / or TRP 404 may determine an HSV-SFN state configuration for the UE 402. In an embodiment where a support indication 406 is included, the network and / or TRP 404 may determine an HSV-SFN state configuration based on information in the support indication 406. The TRP 404 may provide an HSV-SFN state configuration communication 408 to the UE 402 indicating a configuration for the UE 402. The HSV-SFN state configuration communication 408 may indicate that the UE 402 should operate in HSV-SFN scheme 1 and / or a single TRP. The UE 402 may determine an HSV-SFN configuration for the UE 402 based on the HSV-SFN state configuration communication 408. At 410, the UE 402 may configure itself according to the state determined from the HSV-SFN state configuration communication 408.

[0078] The network and / or TRP 404 may further determine a TCI configuration for the UE 402. In an embodiment where the support indication 406 is included, the network and / or TRP 404 may determine the TCI configuration for the UE 402 based on the information in the support indication 406. In an implicit configuration of method 1.4, the network and / or TRP 404 may configure an SSB as a QCL source for the corresponding TRS. In an explicit configuration 1 of method 1.4, the network and / or TRP 404 may determine which SSB is associated with which TCI code point. In some embodiments, the network and / or TRP 404 may generate a TCI configuration communication 412 indicating the TCI configuration for the UE 402. In an implicit configuration of method 1.4, the TCI configuration communication 412 may include configuration information for configuring an SSB as a QCL source for the corresponding TRS. In the explicit configuration of approach 1.4, the TCI configuration communication 412 can include an indication of an association between the SSB and a corresponding TCI code point, which in some embodiments can be a TCI code point for a PDSCH. The network and / or the TRP 404 can provide the TCI configuration communication 412 to the UE 402.

[0079] In Explicit Configuration 2 of Approach 1.4, the network and / or the TRP 404 may further generate an SSB association communication 414. The SSB association communication 414 may include an indication of an association between the SSB and the corresponding TRP. In some embodiments, the association indication may include a mapping (e.g., a bitmap) between the SSB and the corresponding TRP. The association indication may indicate which SSB is associated with which TRP. In some embodiments, the SSB association communication 414 may include a MAC-CE or RRC communication. The TRP 404 may provide the SSB association communication 414 to the UE 402. In the Implicit Configuration of Approach 1.4 and the Explicit Configuration 1 of Approach 1.4, the SSB association communication 414 may be omitted.

[0080] The UE 402 may determine a configuration of a TCI state for the TCI codepoint based on the TCI configuration communication 412 and / or the SSB association communication 414. In some embodiments, the UE 402 may determine an association between an SSB and a TRP based on the TCI configuration communication 412 and / or the SSB association communication 414. At 416, the UE 402 may perform TCI activation such that the TCI codepoint may be activated according to the determined configuration of the TCI state for the TCI codepoint.

[0081] At 418, the UE 402 may perform a channel estimation procedure. The channel estimation procedure may include performing a coarse time and frequency tracking estimation based on the SSB. For example, the UE 402 may estimate a coarse time and frequency for each of the TRPs based on the SSBs, and the UE 402 may determine from which TRP each of the SSBs is received. The UE 402 may track the time and frequency for each of the SSBs to generate a coarse time and frequency estimation for the TRP. In some embodiments, the channel estimation procedure may include performing a fine time and frequency tracking estimation based on a TRS associated with the TRP. The fine time and frequency tracking estimation may be more accurate than the coarse time and frequency tracking estimation. In some embodiments, the UE 402 may be capable of performing a coarse time and frequency tracking estimation at a higher frequency than the fine time and frequency tracking estimation and / or may be capable of performing a coarse time and frequency tracking estimation more quickly than the fine time and frequency tracking estimation. The UE 402 may utilize coarse time and frequency tracking estimates and / or fine time and frequency tracking estimates to estimate the Doppler shift of the signal between the UE 402 and the TRP 404.

[0082] The UE 402 may further utilize the coarse and / or fine time and frequency tracking estimates in transmitting and / or processing signals between the UE 402 and the TRP 404. For example, the TRP 404 may provide a signal 420 to the UE 402. The UE 402 may utilize the coarse and / or fine time and frequency tracking estimates to process the signal 420. Furthermore, the UE 402 may utilize the coarse and / or fine time and frequency tracking estimates in providing signals from the UE 402 to the TRP 404. Method 2: Design for HSV-SFN with pre-compensation.

[0083] In approach 2, the network and UEs may be configured with HSV-SFN with pre-compensation. In particular, in approaches described below in connection with approach 2, the network may pre-compensate for Doppler shift. For example, the network may transmit signals with timing compensated for Doppler shift, configure the UE with scheduling timing compensated for Doppler shift, or do some combination thereof. The network may determine the Doppler shift between each TRP and the UE moving at high speed.

[0084] Approach 2.1: HSV-SFN with pre-compensation may be supported for PDCCH. For example, the network and UE may support HSV-SFN with pre-compensation of PDCCH for communication between TRP and UE. For a specific CORESET in a specific CC, two TCI states may be configured using the MAC-CE. One TCI state has QCL Type A characteristics, i.e., {average delay, delay spread, Doppler shift, Doppler spread}, and QCL-TypeD, if applicable. The other TCI state has new QCL characteristics {average delay, delay spread}, and QCL-TypeD, if applicable. The MAC-CE or RRC may indicate that for this TCI state, some QCL characteristics, e.g., {Doppler shift, Doppler spread}, are dropped. For example, the network and / or the TRP of the network may provide configuration information to the UE indicating two TCI states for configuration of a corresponding CORESET for the UE. The configuration information may indicate that the corresponding CORESET is configured with a first TCI state and a second TCI state. The first TCI state may include QCL-Type A characteristics, such as mean delay, delay spread, Doppler shift, and Doppler spread. In some embodiments, the first TCI state may further include QCL-Type D characteristics. The second TCI state may include QCL characteristics of mean delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics. In some embodiments, the network and / or the TRP of the network may indicate that Doppler shift and Doppler spread are dropped for the second TCI state. The configuration may be provided via MAC-CE or RRC in an embodiment.

[0085] Approach 2.2: When HSV-SFN with pre-compensation is supported for PDCCH, new RRC parameters may be introduced to configure HSV-SFN PDCCH operation with pre-compensation. For example, the network and / or the TRP of the network may generate RRC parameters that may be utilized to configure HSV-SFN with pre-compensation for PDCCH operation. When the RRC configures HSV-SFN with pre-compensation PDCCH operation, if the UE does not support mixed PDCCH monitoring mode, within the same BWP or CC, the NW may activate a CORESET with two TCI states using only MAC-CE. If the UE supports mixed PDCCH monitoring mode, within the same BWP or CC, the NW may activate any CORESET with two TCI states or any CORESET with a single TCI state using MAC-CE. For example, the UE may provide an indication to the network and / or the TRP of whether the UE supports mixed PDCCH monitoring mode. The mixed PDCCH monitoring mode may include a CORESET with a TCI codepoint of the CORESET that may be configured with a mix of two TCI states and a single TCI state. In the case where the UE indicates that the mixed PDCCH monitoring mode is not supported by the UE, the network and / or TRP may decide to activate a CORESET with a single TCI state. In the case where the UE indicates that the mixed PDCCH monitoring mode is supported by the UE, the network and / or TRP may decide to activate a CORESET with a single TCI state, two TCI states, or a mix of a single TCI state and two TCI states. The TRP may provide a TCI configuration communication to the UE indicating the configuration of the CORESET for activation. In some embodiments, the TCI configuration communication may include a MAC-CE.

[0086] Approach 2.3: When HSV-SFN with pre-compensation is supported for PDSCH, PDSCH HSV-SFN with compensation is configured in the MAC-CE to activate the PDSCH TCI codepoint with both of the following, i.e., two TCI states. One TCI state has QCL Type A characteristics, i.e., {average delay, delay spread, Doppler shift, Doppler spread}, and QCL-TypeD, if applicable. The other TCI state has new QCL characteristics {average delay, delay spread}, and QCL-TypeD, if applicable. RRC parameters: The RRC parameters can be (1) per BWP or (2) per CC. For example, the UE can provide an indication to the network and / or the network's TRP of whether the UE supports HSV-SFN with pre-compensation for PDSCH. When HSV-SFN with pre-compensation is supported by the UE for the PDSCH, the network and / or TRP may utilize the MAC-CE to activate the TCI codepoint and RRC parameters that may configure the HSV-SFN state per BWP or per CC. The MAC-CE may configure a TCI codepoint for the PDSCH with two states. The first TCI state may include QCL Type A characteristics of mean delay, delay spread, Doppler shift, and Doppler spread. In some embodiments, the first TCI state may further include QCL-Type D characteristics. The second TCI state may include QCL characteristics of mean delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics.

[0087] Method 2.4: When the RRC parameters configure the UE to operate in HSV-SFN with pre-compensation PDSCH operation, the UE is not capable of dynamic switching of HSV-SFN with pre-compensation with other schemes. The UE can only use MAC-CE to activate PDSCH TCI codepoints with two TCI states. For each activated TCI codepoint: one of the TCI states must be configured with QCL-Type A characteristics and, if applicable, with QCL-TypeD. The other TCI state must be configured with new QCL characteristics of {average delay, delay spread} and, if applicable, with QCL-TypeD. For example, the UE can indicate to the network and / or the network's TRP whether the UE supports dynamic switching of HSV-SFN with pre-compensation with other schemes. When the network and / or the TRP configures the UE in HSV-SFN with pre-compensation for PDSCH operation, the network and / or the TRP can determine that the TCI codepoint for PDSCH is activated with two TCI states. The network and / or TRP may utilize RRC parameters to configure the UE with HSV-SFN with pre-compensation for the PDSCH. Additionally, the network and / or TRP may utilize the MAC-CE to activate a TCI codepoint having two TCI states. The first TCI state may include QCL-Type A characteristics of mean delay, delay spread, Doppler shift, and Doppler spread. In some embodiments, the first TCI state may include QCL-Type D characteristics. The second TCI state may include TCI characteristics of mean delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics.

[0088] FIG. 5 illustrates an example signal flow 500 that can support technique 2.1, technique 2.2, technique 2.3, and / or technique 2.4, according to some embodiments. In particular, signal flow 500 illustrates signals that can be exchanged between UE 502 and TRP 504. It should be understood that the signals in signal flow 500 can be transmitted in a different order and / or simultaneously than shown. In addition, signal flow 500 may omit some signals (such as acknowledgement signals and / or failure signals) that can be transmitted in configuring technique 2.1, technique 2.2, technique 2.3, and / or technique 2.4. Furthermore, one or more of the signals illustrated in signal flow 500 may be omitted in some embodiments. UE 502 may include one or more of the features of UE 106 (FIG. 1). TRP 504 may include one or more of the features of first TRP 102 (FIG. 1) and / or second TRP 104 (FIG. 1).

[0089] The signal flow 500 may begin with the UE 502 sending a support indication 506 to the TRP 504 indicating features supported and / or not supported by the UE 502. In some embodiments, the support indication 506 may include one or more UE capability reports indicating the capabilities of the UE 502. The support indication 506 may indicate whether the UE 502 supports HSV-SFN with pre-compensation. In some embodiments, the support indication 506 may further indicate whether the UE supports a mixed PDCCH monitoring mode and / or whether the UE supports dynamic switching of HSV-SFN with pre-compensation with other schemes. In some embodiments, the UE 502 may provide the support indication 506 in response to a capability request provided to the UE 502 by the TRP 504. In other embodiments, the UE 502 may provide the support indication 506 when it joins the network (e.g., the UE 502 registers with the network and / or the UE 502 is powered on), and the network may store the information included in the support indication 506.

[0090] The network and / or TRP 504 may determine a configuration for the UE 502 based on the information from the support indication 506. For example, the network and / or TRP 504 may determine whether the UE 502 supports HSV-SFN with pre-compensation based on the support indication 506. For approach 2.2, the network and / or TRP 504 may further determine whether the UE supports a mixed PDCCH monitoring mode based on the support indication 506. For approach 2.4, the network and / or TRP 504 may further determine whether the UE supports dynamic switching of HSV-SFN with pre-compensation by other schemes.

[0091] In approach 2.1, the network and / or TRP 504 may determine that the CORESET for a particular CC is configured with two TCI states. The first TCI state may include QCL-Type A characteristics of mean delay, delay spread, Doppler shift, and Doppler spread. The first TCI state may further include QCL-Type D characteristics in some embodiments. The second TCI state may include QCL characteristics of mean delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics. In approach 2.1, the network and / or TRP 504 may generate a pre-compensation configuration communication 508 indicating a determined configuration of HSV-SFN with compensation for PDCCH for the UE 502. In some embodiments, the pre-compensation configuration may include a MAC-CE or RRC for the second TCI state indicating that the Doppler shift and Doppler spread are dropped. The TRP 504 may provide the pre-compensation configuration communication 508 to the UE 502.

[0092] In approach 2.2, the network and / or TRP 504 may determine whether the UE supports a mixed PDCCH monitoring mode. If the network and / or TRP 504 determines that the UE does not support the mixed PDCCH monitoring mode, the network and / or TRP may determine that the CORESET corresponding to the BWP or CC may be activated in two TCI states. If the network and / or TRP 504 determines that the UE supports the mixed PDCCH monitoring mode, the network and / or TRP 504 may determine that some CORESETs corresponding to the BWP or CC are activated in two TCI states and some other CORESETs corresponding to the BWP or CC are activated in a single TCI state. In approach 2.2, the network and / or TRP 504 may generate a pre-compensation configuration communication 508 indicating a determined configuration of the HSV-SFN with compensation for the PDCCH for the UE 502. The TRP 504 may provide the pre-compensation configuration communication 508 to the UE 502.

[0093] In approach 2.3, the network and / or TRP 504 may determine to configure the HSV-SFN using MAC-CE and RRC parameters. The RRC parameters may include that the HSV-SFN is configured per BWP or per CC. The MAC-CE may determine to activate a TCI codepoint for the PDSCH with two TCI states. The first TCI state may include QCL Type A characteristics of average delay, delay spread, Doppler shift, and Doppler spread. The first TCI state may further include QCL-Type D characteristics in some embodiments. The second TCI state may include QCL characteristics of average delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics. In approach 2.3, the network and / or TRP 504 may generate a pre-compensation configuration communication 508 indicating a determined configuration of the HSV-SFN with compensation for the PDSCH for the UE 502. The pre-compensation configuration communication 508 may include RRC parameters in some embodiments. The TRP 504 may provide the pre-compensation configuration communication 508 to the UE 502.

[0094] In method 2.4, the network and / or TRP 504 may determine that the UE does not support dynamic switching of HSV-SFN with pre-compensation by other schemes. Based on the determination that the UE does not support dynamic switching of HSV-SFN with pre-compensation by other schemes, the network and / or TRP 504 may determine to activate a TCI code point for the PDSCH having two TCI states. For each activated TCI code point, the network and / or TRP 504 may determine to activate a TCI code point having two TCI states. The first TCI state may include QCL Type A characteristics of mean delay, delay spread, Doppler shift, and Doppler spread. The first TCI state may further include QCL-Type D characteristics in some embodiments. The second TCI state may include QCL characteristics of mean delay and delay spread. In some embodiments, the second TCI state may further include QCL-Type D characteristics. In approach 2.4, the network and / or the TRP 504 can generate a pre-compensation configuration communication 508 indicating a determined configuration of HSV-SFN with compensation for the PDSCH for the UE 502. The pre-compensation configuration communication 508 can include RRC parameters in some embodiments. The TRP 504 can provide the pre-compensation configuration communication 508 to the UE 502.

[0095] The UE 502 may determine an HSV-SFN having a pre-compensation configuration for the UE 502 based on the pre-compensation configuration communication 508 received from the TRP 504. At 510, the UE 502 may configure the UE 502 with an HSV-SFN having a pre-compensation configuration determined based on the pre-compensation configuration communication 508. For example, in approach 2.1 and / or approach 2.2, the UE 502 may configure a CORESET according to the configuration determined based on the pre-compensation configuration communication 508. In approach 2.3 and / or approach 2.4, the UE 502 may configure a BWP or a CC according to the configuration determined based on the pre-compensation configuration communication 508.

[0096] The network and / or TRP 504 may further generate a TCI configuration communication 512 indicating a determined configuration for the TCI codepoint, the configuration being determined by the network and / or TRP 504. In some embodiments, the TCI configuration communication 512 may include a MAC-CE. For approach 2.1, the TCI configuration communication 512 may indicate that the TCI codepoint for the PDCCH is activated with two TCI states, such as the first TCI state and the second TCI state described above. For approach 2.2, the TCI configuration communication 512 may indicate that the CORESET for the PDCCH is activated with two TCI states in the same BWP or CC when it is determined that the UE 502 does not support a mixed PDCCH monitoring mode. When it is determined that the UE supports a mixed PDCCH monitoring mode for approach 2.2, the TCI configuration communication 512 may indicate that some CORESETs in the BWP or CC are activated with two TCI states and some CORESETs in the same BWP or CC are activated with one TCI state. For technique 2.3, the TCI configuration communication 512 may indicate that the TCI codepoint for the PDSCH is activated in two states, such as the first and second TCI states described above. For technique 2.4, the TCI configuration communication 512 may indicate that the TCI codepoint for the PDSCH is activated in two states (such as the first and second TCI states described above) based on the UE not supporting dynamic switching of HSV-SFN with pre-compensation by other schemes.

[0097] The UE 502 may determine an activation configuration for the UE 502 based on the TCI configuration communication 512. At 514, the UE 502 may perform TCI activation to activate TCI codepoints according to the determined activation configuration.

[0098] Method 2.5: For time and frequency tracking, the NW explicitly or implicitly configures the association of the SSB with the TRP. For example, the network and / or the TRP of the network can configure or provide configuration information to the UE so that the UE can associate the SSB with the TRP that provides the SSB. Implicit configuration: The NW configures the SSB to be a QCL source for the TRS, which implicitly indicates the association between the SSB and the TRP since the TRS is used for the QCL source of the PDSCH / DMRS. If the TRS itself is configured with a reduced set of QCL characteristics, the associated SSB is also configured with the same reduced set of QCL characteristics. For example, the network and / or the TRP can provide the UE with configuration information that causes the UE to configure the SSB as a QCL source for the TRS, which may be part of the TRS configuration. The UE can know which TRS is associated with which TRP, which may be derived from the QCL TCI state configuration. The UE can determine which SSB is associated with which TRP based on the SSB configured as a QCL source of the TRS and the known association of the TRS with the TRP. Thus, the network and / or the TRP can implicitly configure the association of the SSB with the TRP in the implicit configuration of method 2.5. If the TRS has a reduced set of QCL characteristics (such as QCL characteristics of average delay and delay spread), the SSB associated with the TRS can be configured with the same reduced set of QCL characteristics. If the SSB is not configured as a QCL source of the TRS used for PDSCH / DMRS QCL indication, the UE cannot assume the association of the SSB with any TRP. For example, if the SSB is not configured as a QCL source of the TRS, the UE may not be able to determine the source TRP of the SSB.

[0099] Explicit Configuration 1: When the NW activates TCI code points for PDSCH using MAC-CE, the NW configures an association between each TCI code point and a different SSB. For example, the network and / or the TRP of the network can provide an association between the TCI code points and the SSB. The network and / or the TRP can provide the association when providing the activation for the TCI code point, such as by including an indication of the association in the TCI configuration communication 212 (FIG. 2). In some embodiments, the indication of the association can include a mapping between the TCI code points and the SSB. In some embodiments, the indication of the association can include a MAC-CE. The TCI code points can include a TRS, and the UE can know which TRS is associated with which TRP. The UE can determine which SSB corresponds to which TRP based on the association between the TCI code points and the SSB and the relationship between each TRS and each TRP. Thus, the network and / or the TRP can explicitly configure the association between the SSB and the TRP in Explicit Configuration 1 of Method 2.5. For an SSB that is not configured with an association, the UE cannot assume an association between the SSB and any TRP. For example, if an SSB is not configured as a QCL source for a TRS, the UE may not be able to determine the source TRP for the SSB.

[0100] Explicit configuration 2: The NW independently configures for each SSB whether it is from the first TRP, the second TRP, or neither; whether it has QCL characteristics of {average delay, delay spread, Doppler shift, Doppler spread}, or {average delay, delay spread}. For example, the network and / or the network's TRPs can provide a separate communication to the UE indicating which SSBs are associated with which TRPs. The separate communication can include MAC-CE or RRC. The MAC-CE and RRC for the association indication can be separate from other MAC-CE and / or RRC utilized for HSV-SFN state configuration and / or TCI configuration. In some embodiments, the indication can include a mapping (such as a bitmap) indicating which SSBs are associated with which TRPs. In some embodiments, the separate communication can further indicate which QCL characteristics each of the SSBs includes. In particular, the separate communication may indicate whether each SSB includes QCL characteristics of average delay, delay spread, Doppler shift, and Doppler spread, or includes QCL characteristics of average delay and delay spread.

[0101] FIG. 6 illustrates an example signal flow 600 of technique 2.5, according to some embodiments. In particular, signal flow 600 illustrates signals that may be exchanged between UE 602 and TRP 604. It should be understood that the signals in signal flow 600 may be transmitted in a different order and / or simultaneously than shown. In addition, signal flow 600 may omit some signals that may be transmitted in configuration technique 2.5, such as acknowledgement signals and / or failure signals. Furthermore, one or more of the signals illustrated in signal flow 600 may be omitted in some embodiments. UE 602 may include one or more of the features of UE 106 (FIG. 1). TRP 604 may include one or more of the features of first TRP 102 (FIG. 1) and / or second TRP 104 (FIG. 1). In some embodiments, features of signal flow 600 may be combined with features of signal flow 600 (FIG. 6), such as signal flow 500 including features related to configuring HSV-SFN and / or TCI states described with respect to signal flow 500. Thus, technique 2.5 may include one or more of the features of techniques 2.1, 2.2, 2.3, and / or 2.4, such as configuring HSV-SFN and / or TCI states.

[0102] The signal flow 600 may involve the UE 602 sending a support indication 606 to the TRP 604 indicating features supported and / or not supported by the UE 602. In some embodiments, the support indication 606 may include one or more UE capability reports indicating the capabilities of the UE 602. The support indication 406 may indicate whether the UE supports HSV-SFN with pre-compensation. For example, the support indication 606 may include a UE capability report indicating whether the UE 602 supports HSV-SFN with pre-compensation. Additionally, the support indication 606 may include, in some embodiments, an indication of whether the UE 602 supports SSB association with the TRP. In some embodiments, the UE 602 may provide the support indication 606 in response to a capability request provided to the UE 602 by the TRP 604. In other embodiments, the UE 602 may provide the support indication 606 upon joining the network (e.g., the UE 602 registers with the network and / or the UE 602 is powered on), and the network may store the information included in the support indication 606.

[0103] Based on the support indication 606, the network and / or TRP 604 can determine whether the UE 602 supports HSV-SFN with pre-compensation. In some embodiments, the network and / or TRP 604 can determine whether the UE 602 supports SSB association with the TRP, implicit configuration of technique 2.5, explicit configuration 1 of technique 2.5, explicit configuration 2 of technique 2.5, or some combination thereof. The signal flow 600 may proceed to technique 2.5 in some embodiments based on a determination that the UE supports SSB association with the TRP.

[0104] The network and / or TRP 604 may determine an HSV-SFN state configuration for the UE 602. In an embodiment where a support indication 606 is included, the network and / or TRP 604 may determine an HSV-SFN state configuration based on information in the support indication 606. The TRP 604 may provide an HSV-SFN state configuration communication 608 to the UE 602 indicating a configuration for the UE 602. The HSV-SFN state configuration communication 608 may indicate that the UE 602 should operate in HSV-SFN with pre-compensation and / or a single TRP. The UE 602 may determine an HSV-SFN configuration for the UE 602 based on the HSV-SFN state configuration communication 608. At 610, the UE 602 may configure itself according to the state determined from the HSV-SFN state configuration communication 408.

[0105] The network and / or TRP 604 may further determine a TCI configuration for the UE 602. In an embodiment where the support indication 606 is included, the network and / or TRP 604 may determine the TCI configuration for the UE 602 based on the information in the support indication 606. In an implicit configuration of method 2.5, the network and / or TRP 404 may configure an SSB as a QCL source for the corresponding TRS. In an explicit configuration 1 of method 2.5, the network and / or TRP 604 may determine which SSB is associated with which TCI code point. In some embodiments, the network and / or TRP 604 may generate a TCI configuration communication 612 indicating the TCI configuration for the UE 602. In an implicit configuration of method 2.5, the TCI configuration communication 612 may include configuration information for configuring an SSB as a QCL source for the corresponding TRS. In the explicit configuration of approach 2.5, the TCI configuration communication 612 can include an indication of an association between the SSB and a corresponding TCI code point, which in some embodiments can be a TCI code point for a PDSCH. The network and / or the TRP 604 can provide the TCI configuration communication 612 to the UE 602.

[0106] In Explicit Configuration 2 of Method 2.5, the network and / or TRP 604 may further generate an SSB association communication 614. The SSB association communication 614 may include an indication of an association between the SSB and the corresponding TRP. In some embodiments, the association indication may include a mapping (e.g., a bitmap) between the SSB and the corresponding TRP. The association indication may indicate which SSB is associated with which TRP. In some embodiments, the SSB association may include an indication of which SSB is configured with QCL characteristics of average delay, delay spread, Doppler shift, and Doppler spread, and which SSB is configured with QCL characteristics of average delay and delay spread. In some embodiments, the SSB association communication 614 may include MAC-CE or RRC communication. The TRP 604 may provide the SSB association communication 614 to the UE 602. In the Implicit Configuration of Method 2.5 and Explicit Configuration 1 of Method 2.5, the SSB association communication 614 may be omitted.

[0107] The UE 602 may determine a configuration of a TCI state for the TCI codepoint based on the TCI configuration communication 612 and / or the SSB association communication 614. In some embodiments, the UE 602 may determine an association between an SSB and a TRP based on the TCI configuration communication 612 and / or the SSB association communication 614. At 616, the UE 602 may perform TCI activation such that the TCI codepoint may be activated according to the determined configuration of the TCI state for the TCI codepoint.

[0108] At 618, the UE 602 may perform a channel estimation procedure. The channel estimation procedure may include performing a coarse time and frequency tracking estimation based on the SSB. For example, the UE 602 may estimate a coarse time and frequency for each of the TRPs based on the SSBs, and the UE 602 may determine from which TRP each of the SSBs is received. The UE 602 may track the time and frequency for each of the SSBs to generate a coarse time and frequency estimation for the TRP. In some embodiments, the channel estimation procedure may include performing a fine time and frequency tracking estimation based on a TRS associated with the TRP. The fine time and frequency tracking estimation may be more accurate than the coarse time and frequency tracking estimation. In some embodiments, the UE 602 may be capable of performing a coarse time and frequency tracking estimation at a higher frequency than the fine time and frequency tracking estimation and / or may be capable of performing a coarse time and frequency tracking estimation more quickly than the fine time and frequency tracking estimation. The UE 602 may utilize coarse time and frequency tracking estimates and / or fine time and frequency tracking estimates to estimate the Doppler shift of the signal between the UE 602 and the TRP 604.

[0109] The UE 602 may further utilize the coarse and / or fine time and frequency tracking estimates in transmitting and / or processing signals between the UE 602 and the TRP 604. For example, the TRP 604 may provide a signal 620 to the UE 402. The UE 602 may utilize the coarse and / or fine time and frequency tracking estimates to process the signal 620. Furthermore, the UE 602 may utilize the coarse and / or fine time and frequency tracking estimates in providing signals from the UE 602 to the TRP 604. Method 3: Group-based TCI updating.

[0110] Method 3.1: Support NW to update TCI of PDSCH for multiple CCs of UE with same MAC-CE. For example, the network can utilize a single MAC-CE to update the TCI status of TCI codepoints of PDSCH for multiple CCs of UE. Up to two CC lists can be configured by RRC. For example, the network can generate up to two CC lists. Each CC list can include one or more CCs. When updating the TCI status of TCI codepoints, the network can indicate a CC list, and the UE can update the TCI codepoints of CCs included in the indicated CC list. The CC lists should be orthogonal. One CC cannot belong to multiple CC MAC-CEs to activate / deactivate TCI codepoints for UE-specific PDSCH. For example, each CC can belong to at most one CC list to use a single MAC-CE to activate / deactivate TCI codepoints.

[0111] When the MAC-CE is used to activate up to a list of TCI codepoints for the PDSCH, the same list of TCI codepoints is also updated for the PDSCH in other CCs in the same CC list as the CC indicated by the MAC-CE. For example, the UE may maintain a CC list. In response to receiving an indication to activate or deactivate one or more TCI codepoints for a first CC of the PDSCH, the UE may update other CCs in the CC list including the first CC with the same update as that made for the first CC. A scenario in which some CCs are configured with the HSV-SFN scheme and some CCs are configured without the HSV-SFN scheme in the same CC list. Option 1: The NW shall configure the same HSV-SFN for all CCs in the same CC list. Option 2: The UE activates only the first TCI state in a TCI codepoint if the corresponding CC does not support the HSV-SFN scheme. For example, in a case where some of the CCs in a CC list are configured with the HSV-SFN scheme and some CCs in the same CC list are configured without the HSV-SFN scheme, the network may configure all CCs in the same CC list with the same HSV-SFN configuration, or if the CCs do not support the HSV-SFN scheme, the network may cause the UE to activate a first TCI state in the TCI codepoint for the corresponding CC.

[0112] 7 illustrates an example network configuration 700 illustrating the configuration of approach 3.1 according to some embodiments. In particular, the network configuration 700 illustrates a conceptual configuration for approach 3.1 according to some embodiments. The network configuration 700 may include a UE 702 and a TRP 704. The UE 702 may include one or more of the features of the UE 106 (FIG. 1). The TRP 704 may include one or more of the features of the first TRP 102 (FIG. 1) and / or the second TRP 104 (FIG. 1).

[0113] The network configuration 700 illustrates a plurality of CCs 706 of a UE 702. The plurality of CCs 706 may be CCs for a PDSCH. The plurality of CCs 706 are illustrated separated into a first group 708 and a second group 710. The first group 708 may include a first portion of the plurality of CCs 706 that corresponds to a first CC list of technique 3.1. The second group 710 may include a second portion of the plurality of CCs 706 that corresponds to a second list of technique 3.1.

[0114] The TRP 704 may provide a TCI update communication (such as a switching TCI communication 220 (FIG. 2)) to the UE 702 indicating that the TCI codepoint points to one or more of the CCs in the plurality of CCs 706. Based on the TCI update communication, the UE 702 may determine whether the updated CC is included in a first group 708 corresponding to a first CC list, a second group 710 corresponding to a second CC list, or some combination thereof. For example, the UE 702 may determine that some of the updated CCs are in the first group 708 and some others of the updated CCs are in the second group 710. The UE 702 may determine that other CCs in the CC list with the updated CC are updated with the same HSV-SFN as the updated CC. For example, the UE 702 may determine that a first CC 712 in a first group 708 is to be updated based on the TCI update communication, and in some cases may update all CCs in the first group 708 with the same HSV-SFN as requested for the first CC 712. In some cases, the UE 702 may determine that a second CC 714 in a second group 710 is to be updated based on the TCI update communication, and may update all CCs in the second group 710 with the same HSV-SFN as requested for the second CC 714. In cases where the CC determined to be updated does not support the HSV-SFN scheme, the UE, in some embodiments, may configure the CC with the first TCI state.

[0115] Approach 3.2: To support the NW to update the TCI of the PDCCH and / or PDSCH for multiple UEs with the same MAC-CE, the UEs in the same group are configured with the same Radio Network Temporary Identifier (RNTI), e.g., High Speed ​​Vehicular Radio Network Temporary Identifier (HSV-RNTI), used to scramble the Cyclic Redundancy Check (CRC) of the Downlink Control Information (DCI). For example, the network may configure multiple UEs with a single HSV-RNTI. Thus, a first group of UEs may be configured with a first HSV-RNTI, a second group of UEs may be configured with a second HSV-RNTI, and so on. To update the TCI configuration of the TCI codepoints of the PDCCH and / or PDSCH, the network may send (via the TRP) a MAC-CE requesting a TCI configuration update including the HSV-RNTI. Each of the UEs configured with the HSV-RNTI may be updated based on the MAC-CE requesting the TCI configuration update. Thus, multiple UEs may be updated based on a single MAC-CE because two or more UEs may be configured with the same HSV-RNTI. Technique 3.2 may be beneficial when multiple UEs are moving at approximately the same speed and in the same direction, such as when multiple UEs are located in a vehicle.

[0116] Based on the common RNTI configuration, there are two approaches in approach 3.2, namely, Approach 1: Relying on normal downlink (DL) DCI, e.g., DCI format 1_1 or DCI format 1_2. All UEs in the same group configured with the same HSV-RNTI can decode the DCI and then decode the scheduled PDSCH. In the PDSCH, all UEs can extract the MAC-CE. For example, the network and UE can utilize DCI format 1_1 or DCI format 1_2 to convert the TCI configuration. All terminals configured with the same HSV-RNTI can decode the scheduled PDSCH and extract the MAC-CE that requests an update of the TCI configuration. Based on the extraction of the MAC-CE, all UEs can update according to the TCI configuration of the MAC-CE. Approach 2: Relying on a special DCI, e.g., DCI format 2_7. All UEs in the same group configured with the same HSV-RNTI can decode the DCI. The DCI is split into different blocks, and each UE is pre-configured with one block. The UE reads the corresponding block that contains the common configuration among all UEs configured with the same block. For example, each UE is configured with a block of special DCI. The special DCI may be split into different blocks, and each special DCI communication may be split into a different block. The UE may use the HSV-RNTI to decode the DCI communication. The UE may then use the corresponding configured block to determine the block of DCI to be utilized. The corresponding block of DCI may indicate the TCI configuration for the UE. Thus, the UE may determine the TCI configuration for the UE based on the corresponding block of DCI.

[0117] FIG. 8 illustrates an example network configuration 800 illustrating a configuration of technique 3.2 according to some embodiments. In particular, the network configuration 800 illustrates a conceptual configuration for technique 3.2 according to some embodiments. The network configuration 800 may include one or more UEs. For example, the illustrated network configuration 800 includes a first UE 802, a second UE 804, a third UE 806, and a fourth UE 808. The first UE 802, the second UE 804, the third UE 806, and the fourth UE 808 may each include one or more of the features of the UE 106 (FIG. 1). The network configuration 800 may include a TRP 810. The TRP 810 may include one or more of the features of the first TRP 102 (FIG. 1) and / or the second TRP 104 (FIG. 1).

[0118] According to technique 3.2, the network can configure one or more UEs with the same HSV-RNTI via the TRP 810. For example, a first UE 802 and a second UE 804 can be configured by the network with a first HSV-RNTI in the illustrated embodiment, which can cause the first UE 802 and the second UE 804 to be included in a first group 812 having the first HSV-RNTI. Additionally, a third UE 806 can be configured by the network with a second HSV-RNTI in the illustrated embodiment, which can cause the third UE 806 and the fourth UE 808 to be included in a second group 814 having the second HSV-RNTI.

[0119] When the TRP 810 transmits a TCI configuration update communication (such as the switch TCI communication 220 (FIG. 2)) with the HSV-RNTI, the UEs in the one corresponding to the HSV-RNTI may determine that the TCI configuration for the UE is updated. For example, if the TRP 810 transmits a TCI configuration update communication with a first HSV-RNTI corresponding to the first group 812, the first UE 802 and the second UE 804 in the first group 812 may determine that their TCI configuration is updated based on the TCI configuration update communication. The TCI configuration update communication may include a DCI indicating the TCI configuration that the UE corresponding to the HSV-RNTI should update.

[0120] In an embodiment where a special DCI is utilized and the UE is configured with a corresponding block of the special DCI, the UE may look to the configured block of the special DCI for TCI configuration. For example, the first UE 802 may be configured with a first block of the special DCI and the second UE 804 may be configured with a second block of the special DCI. When the TRP 810 transmits a TCI configuration update communication with a first HSV-RNTI corresponding to the first group 812, the first UE 802 may decode the special DCI and utilize the first block of the special DCI to determine the TCI configuration that the first UE 802 should update to. Additionally, the second UE 804 may decode the special DCI and utilize the second block of the special DCI to determine the TCI configuration that the second UE 804 should update to. The UE may then update with the TCI configuration determined from the TCI configuration update communication.

[0121] 9 illustrates an example procedure 900 according to some embodiments. The procedure 900 may include a procedure for determining a Doppler shift using any of the techniques described herein. The procedure 900 may be performed by a UE, which may include one or more of the features of the UE 1400 (FIG. 14). It should be understood that elements of the procedure 900 may be performed in a different order than shown and / or one or more of the elements may be performed simultaneously. Additionally, one or more of the elements may be omitted in an embodiment.

[0122] The procedure 900 may include determining a configuration at 902. In particular, the UE may determine a configuration per BWP or per CC, and the configuration may be determined based on an RRC communication (such as HSV-SFN state configuration communication 208 (FIG. 2), HSV-SFN state configuration communication 408 (FIG. 4), and / or pre-compensation configuration communication 508 (FIG. 5)) received from the TRP. The configuration may be to configure the UE to operate according to HSV-SFN scheme 1 (such as HSV-SFN scheme 1 described throughout this disclosure) within the BWP or CC.

[0123] In some embodiments, the configuration may be determined per CC, the configuration being for configuring the UE to operate according to HSV-SFN scheme 1 in all BWPs of the CC. In some other embodiments, the configuration may be determined per BWP, the configuration being for configuring the UE to operate according to HSV-SFN scheme 1 in a first BWP of the CC and for configuring the UE to operate according to the single-TRP scheme in a second BWP of the CC.

[0124] The procedure 900 may further include determining whether to activate a TCI codepoint with a single TCI state or two TCI states, at 904. The decision of whether to activate a TCI codepoint with a single TCI state or two TCI states (such as the single TCI state or two TCI states described throughout this disclosure) may be determined based on the MAC-CE received from the TRP.

[0125] The procedure 900 may further include performing a channel estimation procedure, at 906. In particular, the UE may perform a channel estimation procedure (such as a channel estimation procedure described throughout this disclosure) to determine a Doppler shift based on the TCI codepoint.

[0126] The procedure 900 may further include utilizing the determined Doppler shift in decoding at 908. In particular, the UE may utilize the determined Doppler shift determined at 906 in decoding at least one signal received by the UE. The at least one signal may be received via a PDSCH of the BWP or CC.

[0127] The procedure 900 may further include identifying an indication to switch activation, at 910. In particular, the UE may identify an indication in the second MAC-CE or DCI to switch activation of the TCI codepoint to a single TCI state or to two TCI states.

[0128] The procedure 900 may further include switching activation of the TCI codepoint at 912. In particular, the UE may switch activation of the TCI codepoint based on the indication. In some embodiments, switching activation may include switching from a first BWP to a second BWP.

[0129] FIG. 10 illustrates an example procedure 1000 according to some embodiments. The procedure 1000 may include a procedure for configuring with HSV-SFN according to any of the approaches described herein. The procedure 1000 may be performed by a base station, which may include one or more of the features of gNB 1500 (FIG. 15). It should be understood that elements of the procedure 1000 may be performed in a different order than shown and / or one or more of the elements may be performed simultaneously. Additionally, one or more of the elements may be omitted in an embodiment.

[0130] The procedure 1000 may involve, at 1002, determining that the UE supports HSV-SFN scheme 1. The UE may determine whether the UE supports HSV-SFN scheme 1 based on an indication received from the UE.

[0131] The methodology 1000 may further include generating an RRC communication to configure the UE, at 1004. In particular, the base station may generate an RRC communication to configure the UE to operate in accordance with HSV-SFN scheme 1 within the BWP or CC. In some embodiments, the base station may generate the RRC communication based on the indication received at 1002.

[0132] The procedure 1000 may further include determining whether the UE supports dynamic switching, at 1006. Specifically, the base station may determine whether the UE supports dynamic switching between the HSV-SFN scheme 1 and the single TRP scheme.

[0133] The procedure 1000 may further include activating a TCI codepoint at 1008. Specifically, the base station may activate a TCI codepoint having a single TCI state or two TCI states based on a determination of whether the UE supports dynamic switching between the HSV-SFN scheme 1 and the single TRP scheme.

[0134] In some cases, the base station may determine that the UE does not support dynamic switching. In these cases, the base station may activate a TCI codepoint having two TCI states.

[0135] The methodology 1000 may further include generating a MAC-CE at 1010. In particular, the base station may generate a MAC-CE that indicates whether the TCI codepoint is activated in a single TCI state or in two TCI states. In some embodiments, the MAC-CE may indicate a particular CC for which the TCI codepoint is activated. In other embodiments, the MAC-CE may indicate a particular BWP of the CC for which the TCI codepoint is activated.

[0136] The methodology 1000 may further include providing the MAC-CE to the UE. In particular, the base station may provide the MAC-CE to the UE to configure the UE with the TCI codepoint.

[0137] FIG. 11 illustrates an example procedure 1100 according to some embodiments. The procedure 1100 may include a procedure for configuring with HSV-SFN according to any of the approaches described herein. The procedure 1100 may be performed by a base station, which may include one or more of the features of gNB 1500 (FIG. 15). It should be understood that elements of the procedure 1100 may be performed in a different order than shown and / or one or more of the elements may be performed simultaneously. Additionally, one or more of the elements may be omitted in an embodiment.

[0138] The procedure 1100 may include, at 1102, determining whether the UE supports mixed CORESET operation. In particular, the base station may determine whether the UE supports mixed CORESET operation for HSV-SFN. Determining whether the UE supports mixed CORESET operation may include receiving a UE capabilities report indicating that the UE supports HSV-SFN or receiving a UE capabilities report indicating that the UE supports mixed CORESET operation. In some embodiments, the UE capabilities report may indicate that the UE supports HSV-SFN for the PDCCH.

[0139] The methodology 1100 may include configuring multiple CORESETs, at 1104. In particular, the base station may configure multiple CORESETs for the active BWP based on whether the UE supports mixed CORESET operation for HSV-SFN.

[0140] The procedure 1100 may further include, at 1106, transmitting a MAC-CE to activate one or more CORESETs. In particular, the base station may transmit a MAC-CE to activate one or more CORESETs of an active BWP having several TCI states, where the number of TCI states is one or two.

[0141] FIG. 12 illustrates an example procedure 1200 according to some embodiments. The procedure 1200 may include procedures for performing time and frequency tracking estimation according to any of the techniques described herein. The procedure 1200 may be performed by a base station, which may include one or more of the features of the UE 1400 (FIG. 14). It should be understood that elements of the procedure 1200 may be performed in a different order than shown and / or one or more of the elements may be performed simultaneously. Additionally, one or more of the elements may be omitted in an embodiment.

[0142] The procedure 1200 may include, at 1202, determining that the UE should operate in HSV-SFN scheme 1. For example, the UE may determine that the UE should operate in HSV-SFN scheme 1, as described throughout this disclosure.

[0143] The procedure 1200 may include, at 1204, determining that the SSB is associated with the TRP. In some embodiments, determining that the SSB is associated with the TRP includes determining that the SSB is configured as a QCL source for the TRS. In some other embodiments, determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a MAC-CE received by the UE. Furthermore, determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a bitmap indicating that the SSB is associated with the TRP.

[0144] The procedure 1200 may include, at 1206, performing a coarse time and frequency tracking estimation. In particular, the UE may perform the coarse time and frequency tracking estimation based on the SSB. In some embodiments, the UE may perform the coarse time and frequency estimation based on a determination that the UE should operate in HSV-SFN scheme 1.

[0145] The procedure 1200 may involve performing a fine time and frequency tracking estimation, at 1208. In particular, the UE may perform a fine time and frequency tracking estimation based on a TRS associated with the TRP.

[0146] 13 illustrates an example beamforming circuit 1300 according to some embodiments. The beamforming circuit 1300 may include a first antenna panel, panel 1 1304, and a second antenna panel, panel 2 1308. Each antenna panel may include several antenna elements. Other embodiments may include other numbers of antenna panels.

[0147] The digital beamforming (BF) component 1328 may receive an input baseband (BB) signal from a baseband processor, such as, for example, the baseband processor 1404A of FIG. 14. The digital BF component 1328 may rely on complex weights to precode the BB signal and provide a beamformed BB signal to the parallel radio frequency (RF) chains 1320 / 1324.

[0148] Each RF chain 1320 / 1324 may include a digital-to-analog converter for converting the baseband signal to the analog domain, a mixer for mixing the baseband signal into an RF signal, and a power amplifier for amplifying the RF signal for transmission.

[0149] The RF signals may be provided to an analog BF component 1312 / 1316, which may additionally apply beamforming by providing a phase shift in the analog domain. The RF signals may then be fed to the antenna panels 1304 / 1308 for transmission.

[0150] In some embodiments, instead of the hybrid beamforming shown herein, beamforming may be performed solely in the digital domain or solely in the analog domain.

[0151] In various embodiments, control circuitry, which may be present in a baseband processor, may provide BF weights to the analog / digital BF components to provide transmit beams at the respective antenna panels. These BF weights may be determined by the control circuitry to provide directional provisioning of the serving cell as described herein. In some embodiments, the BF components and antenna panels may operate together to provide a dynamic phased array capable of steering beams in desired directions.

[0152] 14 illustrates an exemplary UE 1400 according to some embodiments. The UE 1400 may be any mobile or non-IoT device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a moisture sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device (e.g., a smart watch), a relaxed mobile computing device, etc. In some embodiments, the UE 1400 may be a RedCap UE or an NR-Light UE.

[0153] The UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, an antenna structure 1426, and a battery 1428. The components of the UE 1400 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other module, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 14 is intended to illustrate a high-level view of some of the components of the UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0154] The components of the UE 1400 may be coupled with various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connection, etc. that allows various circuit components (on a common or different chips or chipsets) to interact with one another.

[0155] The processor 1404 may include processor circuitry such as, for example, baseband processor circuitry (BaseBand, BB) 1404A, central processing unit circuitry (CPU) 1404B, and graphics processing unit circuitry (Graphics Processor Unit, GPU) 1404C. The processor 1404 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1412 to cause the UE 1400 to perform the operations described herein.

[0156] In some embodiments, the baseband processor circuitry 1404A may access a communications protocol stack 1436 in the memory / storage 1412 to communicate over a 3GPP compliant network. Generally, the baseband processor circuitry 1404A may access the communications protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers, and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some embodiments, PHY layer operations may additionally / alternatively be performed by components of the RF interface circuitry 1408.

[0157] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, waveforms for NR may be based on Cyclic Prefix OFDM (CP-OFDM) in the uplink or downlink and Discrete Fourier Transform Spread OFDM (DFT-S-OFDM) in the uplink.

[0158] The memory / storage 1412 may include one or more non-transitory computer-readable media (e.g., communication protocol stack 1436) that include instructions that may be executed by one or more of the processors 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 and L2 caches), while other memory / storage 1412 may be external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include, but is not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or other types of memory device technologies.

[0159] The RF interface circuitry 1408 may include transceiver circuitry and a radio frequency front end module (RFEM) that enable the UE 1400 to communicate with other devices over a radio access network. The RF interface circuitry 1408 may include various elements disposed in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, combiner circuits, control circuits, etc.

[0160] In the receive path, the RFEM may receive a radiated signal from the air interface via the antenna structure 1426 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver receiver that downconverts the RF signal to a baseband signal that is provided to a baseband processor of the processor 1404.

[0161] In the transmit path, the transmitter of the transceiver upconverts the baseband signal received from the baseband processor and provides an RF signal to the RFEM, which may amplify the RF signal through a power amplifier before the signal is radiated over the air interface via the antenna 1426.

[0162] In various embodiments, the RF interface circuitry 1408 may be configured to transmit and receive signals in a manner that complies with NR access technologies.

[0163] The antenna 1426 may include antenna elements that convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. The antenna elements may be arranged in one or more antenna panels. The antenna 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output communication. The antenna 1426 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 1426 may have one or more panels designed for a particular frequency band, including bands in FR1 or FR2.

[0164] In some embodiments, the UE 1400 may include the beamforming circuitry 1300 (FIG. 13), which may be utilized for communication with the UE 1400. In some embodiments, components of the UE 1400 and the beamforming circuitry may be shared. For example, the antenna 1426 of the UE may include panel 1 1304 and panel 2 1308 of the beamforming circuitry 1300.

[0165] The user interface circuitry 1416 includes various input / output (I / O) devices designed to enable user interaction with the UE 1400. The user interface 1416 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for accepting input, including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as a sensor reading, an actuator position(s), or other similar information. The output device circuitry may include any number or combination of audio or visual displays, including, among others, one or more simple visual outputs / indicators (e.g., binary status indicators such as light emitting diodes "LEDs" and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where output of characters, graphics, multimedia objects, etc. are generated or produced from operation of the UE 1400.

[0166] The sensors 1420 may include devices, modules, or subsystems that are intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers, microelectromechanical or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors), pressure sensors; barometric pressure sensors; gravitational meters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0167] The driver circuitry 1422 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuitry 1422 may include individual drivers that enable other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1400. For example, the driver circuitry 1422 may include a display driver that controls and enables access to a display device, a touchscreen driver that controls and enables access to a touchscreen interface, a sensor driver that obtains sensor readings of the sensor circuitry 1420 and controls and enables access to the sensor circuitry 1420, a driver that obtains actuator positions of electromechanical components or controls and enables access to electromechanical components, a camera driver that controls and enables access to an embedded image capture device, an audio driver that controls and enables access to one or more audio devices.

[0168] The PMIC 1424 may manage the power supplied to various components of the UE 1400. In particular, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0169] In some embodiments, the PMIC 1424 may control or otherwise be part of various power saving mechanisms of the UE 1400. For example, if the platform UE is in an RRC_Connected state where it is still connected to a RAN node because it expects to receive traffic shortly, after some period of inactivity the platform UE may enter a state known as Discontinuous Reception Mode (DRX). During this state, the UE 1400 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1400 may transition to an RRC_Idle state where it disconnects from the network and does not perform operations such as channel quality feedback, handovers, etc. The UE 1400 goes into a very low power state and performs paging, waking up periodically again to listen to the network and powering down again. The UE 1400 may not be able to receive data in this state. To receive data, it must transition back to the original RRC_Connected state. In a further power saving mode, the device may be allowed to be unavailable from the network for periods longer than the paging interval (which can range from a few seconds to a few hours). During this time, the device may be completely unable to reach the network and may be completely powered down. Any data transmitted during this time will be significantly delayed, but the delay is deemed acceptable.

[0170] The battery 1428 may provide power to the UE 1400, although in some examples the UE 1400 may be deployed and mounted at a fixed location or may have a power source coupled to a power grid. The battery 1428 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, etc. In some implementations, such as vehicle-based applications, the battery 1428 may be a typical automotive lead acid battery.

[0171] 15 illustrates an example gNB 1500 according to some embodiments. The gNB 1500 may include a processor 1504, an RF interface circuit 1508, a core network (CN) interface circuit 1512, a memory / storage circuit 1516, and an antenna structure 1526.

[0172] The components of the gNB 1500 may be coupled to various other components via one or more interconnects 1528.

[0173] The processor 1504, RF interface circuitry 1508, memory / storage circuitry 1516 (including communication protocol stack 1510), antenna structure 1526, and interconnect 1528 may be similar to the like-named elements shown and described with respect to FIG.

[0174] The CN interface circuitry 1512 can provide connectivity to a core network, e.g., a fifth generation network interface (5GC), using a 5GC compatible core network protocol, such as the Carrier Ethernet protocol, or some other suitable protocol. Network connectivity can be provided to or from the gNB 1500 via optical fiber or wireless backhaul. The CN interface circuitry 1512 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1512 can include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0175] It is understood that use of personally identifiable information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0176] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, or methods as described in the example section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the example section. Working Example

[0177] Further exemplary embodiments are provided in the following sections.

[0178] Proposal 1.1

[0179] Example 1 may include a method including: determining, by a user equipment (UE), a configuration per bandwidth portion (BWP) or per component carrier (CC) based on a radio resource control (RRC) communication received from a transmission / reception point (TRP), where the configuration configures the UE to operate in accordance with a high speed vehicular-single frequency network (HSV-SFN) scheme 1 within the BWP or CC; determining whether to activate a transmission configuration indicator (TCI) codepoint having a single TCI state or two TCI states based on a medium access control-control element (MAC-CE) received from the TRP; performing a channel estimation procedure to determine a Doppler shift based on the TCI codepoint; and utilizing the determined Doppler shift in decoding at least one signal received by the UE.

[0180] Example 2 may include the method of example 1, wherein the at least one signal is received over a physical downlink shared channel (PDSCH) of the BWP or CC.

[0181] Example 3 may include the method of example 1, wherein the UE determines a configuration for each CC, the configuration configuring the UE to operate according to HSV-SFN scheme 1 within all BWPs of the CC.

[0182] Example 4 may include the method of example 1, wherein the UE determines a configuration for each BWP, the configuration configuring the UE to operate according to the HSV-SFN scheme 1 within a first BWP of the CC, and the UE is further configured to operate according to the single TRP scheme within a second BWP of the CC.

[0183] Example 5 may include the method of example 1, where the MAC-CE is a first MAC-CE, and the method further includes identifying an indication in a second MAC-CE or downlink control information (DCI) to switch activation of the TCI codepoint to a single TCI state or to two TCI states, and switching activation of the TCI codepoint based on the indication.

[0184] Example 6 may include the method of example 5, wherein switching activation of the TCI codepoint includes switching from a first bandwidth part (BWP) to a second BWP.

[0185] Proposal 1.1

[0186] Example 7 may include a method including: generating, by a base station, a radio resource control (RRC) communication to configure a user equipment (UE) to operate in accordance with a high speed vehicular - single frequency network (HSV-SFN) scheme 1 within a bandwidth portion (BWP) or a component carrier (CC); determining whether the UE supports dynamic switching between the HSV-SFN scheme 1 and a single transmission / reception point (TRP) scheme; and activating a transmission configuration indicator (TCI) code point having a single TCI state or two TCI states based on a determination of whether the UE supports dynamic switching between the HSV-SFN scheme 1 and the single TRP scheme.

[0187] Example 8 may include the method of example 7, further including: determining, based on an indication received from the UE, that the UE supports HSV-SFN scheme 1; and the TRP generating an RRC based on the indication.

[0188] Example 9 may include the method of example 7, where determining whether the UE supports dynamic switching includes determining that the UE does not support dynamic switching, and activating the TCI codepoint includes activating a TCI codepoint having two TCI states.

[0189] Example 10 may include the method of Example 7, further including generating a medium access control-control element (MAC-CE) indicating whether the TCI codepoint is activated in a single TCI state or in two TCI states, and providing the MAC-CE to the UE for configuring the UE with the TCI codepoint.

[0190] Example 11 may include the method of example 10, wherein the MAC-CE further indicates a particular component carrier (CC) for which the TCI codepoint is activated.

[0191] Example 12 may include the method of example 10, wherein the MAC-CE further indicates a particular bandwidth portion (BWP) of a component carrier (CC) for which the TCI codepoint is activated.

[0192] Proposal 1.2:

[0193] Example 13 may include a method of operating a base station, the method including determining whether a UE supports mixed CORESET operation for high speed vehicular - single frequency network (HSV-SFN) and configuring multiple CORESETs for an active BWP based on whether the UE supports mixed CORESET operation for HSV-SFN.

[0194] Example 14 may include the method of Example 13, wherein determining whether the UE supports mixed CORESET operation for HSV-SFN includes receiving a UE capabilities report indicating that the UE supports HSV-SFN or receiving a UE capabilities report indicating that the UE supports mixed CORESET operation.

[0195] Example 15 may include the method of example 14, wherein the UE capability report indicates that the UE supports HSV-SFN for a physical downlink control channel (PDCCH).

[0196] Suggestion 1.3

[0197] Example 16 may include the method of Example 13, where determining whether the UE supports mixed CORESET operation includes determining that the UE does not support mixed CORESET operation, and the method further includes transmitting a medium access control-control element (MAC-CE) to activate one or more CORESETs of an active BWP having multiple TCI states, where the number of TCI states is one or two.

[0198] Suggestion 1.4:

[0199] Example 17 may include a method of operating a user equipment (UE), the method including determining that a synchronization signal / physical broadcast channel block (SSB) is associated with a transmission / reception point (TRP), performing a coarse time and frequency tracking estimation based on the SSB, and performing a fine time and frequency tracking estimation based on a tracking reference signal (TRS) associated with the TRP.

[0200] Example 18 may include the method of example 17, wherein determining that the SSB is associated with the TRP includes determining that the SSB is configured as a quasi-co-location (QCL) source of the TRS.

[0201] Example 19 may include the method of Example 17, wherein determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a medium access control-control element (MAC-CE) received by the UE.

[0202] Example 20 may include the method of example 17, wherein determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a bitmap indicating that the SSB is associated with the TRP.

[0203] Example 21 may include the method of Example 17, further including determining that the UE should operate in a high speed vehicular-single frequency network (HSV-SFN) scheme 1, and the UE performing a coarse time and frequency estimation based on a determination that the UE should operate in the HSV-SFN scheme 1.

[0204] Proposal 1.1:

[0205] Example 22 may include a method for determining a Doppler shift, including: determining, by a user equipment (UE), that the UE should operate in a high speed vehicular-single frequency network (HSV-SFN) scheme 1 within a bandwidth portion (BWP) or component carrier (CC) for the UE to determine a Doppler shift based on radio resource control (RRC) communications; determining, by the UE, based on a medium access control-control element (MAC-CE), that a transmission configuration indicator (TCI) code point is activated in a single TCI state or two TCI states; activating, by the UE, the TCI code point for which the single TCI state or two TCI states has been determined; and determining, by the UE, a Doppler shift based on the TCI code point.

[0206] Example 23 may include the method of example 22, further including utilizing the determined Doppler shift to decode at least one signal received by the UE.

[0207] Example 24 may include the method of example 23, wherein the at least one signal is received via a physical downlink shared channel (PDSCH).

[0208] Example 25 may include the method of example 22, wherein activating the TCI codepoint includes activating the TCI codepoint for the CC.

[0209] Example 26 may include the method of example 22, wherein activating the TCI codepoint includes activating the TCI codepoint for the BWP.

[0210] Example 27 may include the method of Example 22, where the MAC-CE is a first MAC-CE, and the method further includes identifying, by the UE, an indication in a second MAC-CE or downlink control information (DCI) for switching activation of the TCI codepoint between the single TCI state and the two TCI states, and switching, by the UE, activation of the TCI codepoint based on the indication.

[0211] Proposal 2.1

[0212] Example 28 may include a method of operating a user equipment (UE), the method including: determining, based on one or more signals from a transmission / reception point (TRP), that the TRP should perform high speed vehicular-single frequency network (HSV-SFN) pre-compensation; determining, based on a medium access control-control element (MAC-CE) from the TRP, one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) in a carrier component (CC), the MAC-CE indicating a quasi-co-location (QCL) characteristic for the one or two TCI states; and configuring a CORESET having the QCL characteristic based on the determination of the one or two TCI states.

[0213] Example 29 may include the method of Example 28, wherein the one or two TCI states include two TCI states, the first QCL characteristic for a first TCI state of the two TCI states includes QCL type A characteristics, and the second QCL characteristic for a second TCI state of the two TCI states includes QCL characteristics of average delay and delay spread.

[0214] Example 30 may include the method of example 29, wherein the QCL Type A characteristics include QCL characteristics of average delay, delay spread, Doppler shift, and Doppler spread.

[0215] Example 31 may include the method of example 29, further including identifying a MAC-CE or radio resource control (RRC) from the TRP indicating that the second QCL characteristic does not include a Doppler shift and a Doppler spread.

[0216] Proposal 2.2

[0217] Example 32 may include the method of example 28, further including providing an indication of whether the UE supports a mixed physical downlink control channel (PDCCH) monitoring mode.

[0218] Example 33 may include the method of Example 32, where providing the indication includes providing an indication that the UE does not support the mixed PDCCH monitoring mode, and determining one or two TCI states for the configuration of the CORESET includes determining to activate a CORESET having two TCI states based on the MAC-CE.

[0219] Example 34 may include the method of Example 32, wherein the CORESET is a first CORESET, determining one or two TCI states for configuration of the first CORESET includes determining two TCI states for configuration of the first CORESET, configuring the first CORESET includes configuring the first CORESET having two TCI states, and the method further includes determining one TCI state for configuration of a second CORESET based on the MAC-CE, and configuring the second CORESET having one TCI state based on the determination of the one TCI state.

[0220] Example 35 may include the method of example 28, where the HSV-SFN pre-compensation includes HSV-SFN pre-compensation for a physical downlink control channel (PDCCH).

[0221] Proposal 2.3

[0222] Example 36 may include a method of operating a user equipment (UE), including determining, based on one or more signals from a transmission / reception point (TRP), that the TRP performs a high speed vehicular-single frequency network (HSV-SFN) with pre-compensation, determining, based on a medium access control-control element (MAC-CE) from the TRP, two transmission configuration indicator (TCI) states for configuration of a TCI code point, the MAC-CE indicating a quasi-co-location (QCL) characteristic for the two TCI states, and configuring the TCI code point having the two TCI states based on the determination of the two TCI states.

[0223] Example 37 may include the method of example 36, where determining the two TCI states includes determining a first TCI state including a QCL type A characteristic of the TCI and a second TCI state including a QCL characteristic of an average delay and a delay spread.

[0224] Example 38 may include the method of example 37, wherein the QCL type A includes the QCL characteristics of the mean delay, the delay spread, the Doppler shift, and the Doppler spread.

[0225] Example 39 may include the method of example 36, wherein the one or more signals include a radio resource control (RRC) signal indicating that the TRP is configured for HSV-SFN with pre-compensation.

[0226] Proposal 2.4

[0227] Example 40 may include the method of example 36, further including indicating that the UE does not support dynamic switching of HSV-SFN with pre-compensation, and the MAC-CE indicates two TCI states for the configuration of the TCI codepoint based on the indication that the UE does not support dynamic switching of HSV-SFN with pre-compensation.

[0228] Proposal 2.5

[0229] Example 41 may include a method of operating a user equipment (UE), including determining, based on radio resource control (RRC) communications, that the UE should operate in a high speed vehicular - single frequency network (HSV-SFN) with pre-compensation, determining that a synchronization signal / physical broadcast channel block (SSB) is associated with a transmission / reception point (TRP), and performing coarse time and frequency estimation based on the SSB using the HSV-SFN with pre-compensation.

[0230] Example 42 may include the method of example 41, further including determining a quasi-co-location (QCL) characteristic corresponding to the SSB based at least in part on the medium access control-control element (MAC-CE).

[0231] Example 43 may include the method of example 42, wherein the QCL characteristics include a first set of QCL characteristics including an average delay, a delay spread, a Doppler shift, and a Doppler spread, or a second set of QCL characteristics including an average delay and a delay spread.

[0232] Example 44 may include the method of Example 41, wherein determining that the SSB is associated with the TRP includes determining that the SSB is configured as a quasi-co-located (QCL) source of a tracking reference signal (TRS) associated with the TRP, and the method further includes performing a precise time and frequency estimation based on the TRS.

[0233] Example 45 may include the method of Example 41, wherein determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a medium access control-control element (MAC-CE) received by the UE.

[0234] Example 46 may include the method of Example 41, wherein determining that the SSB is associated with the TRP includes determining that the SSB is associated with the TRP based on a bitmap indicating that the SSB is associated with the TRP.

[0235] Proposal 3.1

[0236] Example 47 may include a method of operating a user equipment (UE), comprising: determining a high speed vehicular-single frequency network (HSV-SFN) scheme based on a medium access control-control element (MAC-CE) received from a first transmission / reception point (TRP); determining a plurality of component carriers (CCs) configured using the HSV-SFN scheme based on the MAC-CE; and configuring at least a portion of the plurality of CCs using the HSV-SFN scheme, wherein the HSV-SFN scheme is utilized by at least a portion of the plurality of CCs to estimate a Doppler shift.

[0237] Example 48 may include the method of Example 47, further including configuring one or more CC lists based on radio resource control (RRC) received from the TRP, each of the one or more CC lists including a corresponding CC, and determining the plurality of CCs configured in the HSV-SFN scheme includes determining the plurality of CCs configured in the HSV-SFN scheme based on the one or more CC lists.

[0238] Example 49 may include the method of example 48, wherein the one or more CC lists are orthogonal.

[0239] Example 50 may include the method of Example 47, further including determining one or more transmission configuration indicator (TCI) codepoints to be activated based on the MAC-CE, and activating the one or more TCI codepoints based on the determination of the one or more TCI codepoints.

[0240] Example 51 may include the method of Example 47, further including determining a first portion of the plurality of CCs that support the HSV-SFN scheme and a second portion of the plurality of CCs that do not support the HSV-SFN scheme, and configuring at least a portion of the plurality of CCs using the HSV-SFN scheme includes configuring the first portion of the plurality of CCs using the HSV-SFN scheme and configuring the second portion of the plurality of CCs without the HSV-SFN scheme.

[0241] Example 52 may include the method of example 51, further including activating a second portion of the plurality of CCs having a single TCI state.

[0242] Example 53 may include the method of example 47, wherein at least a portion of the plurality of CCs are configured for a physical downlink shared channel (PDSCH).

[0243] Proposal 3.2

[0244] Example 54 may include a method of operating a base station, the method including generating a common Radio Network Temporary Identifier (RNTI); providing the common RNTI to a plurality of user equipments (UEs); providing the common RNTI to cause the plurality of UEs to configure the common RNTI; and providing downlink control information (DCI) to at least the plurality of UEs, the DCI indicating a high speed vehicular-single frequency network (HSV-SFN) scheme for configuration by the plurality of UEs.

[0245] Example 55 may include the method of example 54, wherein the DCI includes DCI format 1_1 or DCI format 1_2.

[0246] Example 56 may include the method of example 54, wherein the DCI is divided into different blocks, and further includes providing a mapping of corresponding blocks of DCI to a plurality of UEs, the mapping indicating corresponding blocks of DCI to utilize to determine an HSV-SFN scheme for which each of the plurality of UEs is configured.

[0247] the goal

[0248] Example 57 may include a method of operating a user equipment (UE), the method including: determining a configuration per bandwidth portion (BWP) based on a radio resource control (RRC) communication received from a transmission / reception point (TRP), the configuration configuring the UE to operate in accordance with a high speed vehicular-single frequency network (HSV-SFN) scheme 1 within the BWP; determining one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) based on a medium access control-control element (MAC-CE) received from the TRP; and configuring the CORESET within the BWP based on the determination of the one or two TCI states.

[0249] Example 58 may include the method of example 57, wherein the one or two TCI states include two TCI states.

[0250] Example 59 may include the method of Example 57, further including: determining whether to activate a TCI codepoint having one or two transmit TCI states based on the MAC-CE; performing a channel estimation procedure to determine a Doppler shift based on the TCI codepoint; and utilizing the determined Doppler shift in decoding at least one signal received by the UE.

[0251] Example 60 may include the method of example 59, wherein the at least one signal is received over a physical downlink shared channel (PDSCH) of the BWP.

[0252] Example 61 may include the method of Example 59, where the MAC-CE is a first MAC-CE, and the method further includes identifying an indication in a second MAC-CE or downlink control information (DCI) to switch activation of the TCI codepoint to one or two TCI states, and switching activation of the TCI codepoint based on the indication.

[0253] Example 62 may include the method of Example 61, wherein switching activation of the TCI codepoint includes switching from the first BWP to the second BWP.

[0254] Example 63 may include the method of example 57, wherein the BWP is a first BWP, and configuring the CORESET includes configuring the UE to operate in accordance with the HSV-SFN scheme 1 within the first BWP and in accordance with the single TRP scheme within the second BWP.

[0255] Example 64 may include a method of operating a user equipment (UE), the method including: determining, based on one or more signals from a transmission / reception point (TRP), that pre-compensation is performed for the UE; determining, based on a medium access control-control element (MAC-CE) from the TRP, one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET); and configuring the CORESET based on the determination of the one or two TCI states.

[0256] Example 65 may include the method of example 64, wherein the one or two TCI states include two TCI states.

[0257] Example 66 may include the method of example 64, wherein the MAC-CE exhibits a quasi-collocation (QCL) property for one or two TCI states.

[0258] Example 67 may include the method of example 64, wherein the one or two TCI states include two TCI states, and the MAC-CE drops a first Doppler shift and a first Doppler spread for a first TCI state of the two TCI states, and the MAC-CE drops a second Doppler shift and a second Doppler spread for a second TCI state of the two TCI states.

[0259] Example 68 may include the method of Example 64, wherein the one or two TCI states include two TCI states, and the first quasi-colocation (QCL) characteristic for a first TCI state of the two TCI states includes a QCL type A characteristic, and the second QCL characteristic for a second TCI state of the two TCI states includes a QCL characteristic of average delay and delay spread.

[0260] Example 69 may include the method of example 68, wherein the QCL Type A characteristics include QCL characteristics of average delay, delay spread, Doppler shift, and Doppler spread.

[0261] Example 70 may include the method of example 64, wherein the pre-compensation includes high speed vehicular-single frequency network (HSV-SFN) pre-compensation.

[0262] Example 71 may include a method of operating a user equipment (UE), the method including storing configuration information for configuration; determining a configuration per bandwidth portion (BWP) based on a radio resource control (RRC) communication received from a transmission / reception point (TRP), the configuration configuring the UE to operate with pre-compensation within the BWP; determining one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) based on a medium access control-control element (MAC-CE) received from the TRP; and configuring the CORESET within the BWP based on the determination of the one or two TCI states.

[0263] Example 72 may include the method of example 71, wherein the one or two TCI states include two TCI states.

[0264] Example 73 may include the method of example 71, wherein the MAC-CE exhibits a quasi-collocation (QCL) property for one or two TCI states.

[0265] Example 74 may include the method of example 71, wherein configuring the CORESET includes configuring the CORESET with RRC parameters based on the BWP.

[0266] Example 75 may include the method of example 71, wherein the pre-compensation includes high speed vehicular-single frequency network (HSV-SFN) pre-compensation.

[0267] Example 76 may include the method of example 71, wherein the one or two TCI states include two TCI states, and determining the one or two TCI states includes determining a first TCI state including a QCL type A characteristic of the TCI and a second TCI state including a QCL characteristic of a mean delay and a delay spread.

[0268] Example 77 may include a method of operating a base station, the method including determining a bandwidth portion (BWP) for a component carrier (CC) configured with a high speed vehicular - single frequency network (HSV-SFN) scheme 1, generating a radio resource control (RRC) communication indicating that the BWP for the CC is configured with the HSV-SFN scheme 1, sending the RRC communication to a user equipment (UE) to configure the UE with the HSV-SFN scheme 1, generating a medium access control - control element (MAC-CE) indicating one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET), and sending the MAC-CE to the UE to configure the CORESET within the BWP.

[0269] Example 78 may include the method of Example 77, the method further including receiving an indication from the UE that the UE supports dynamic switching, and the MAC-CE indicates one or two TCI states based on the indication that the UE supports dynamic switching.

[0270] Example 79 may include the method of example 77, wherein the one or two TCI states include two TCI states.

[0271] Example 80 may include the method of Example 77, the method further including receiving an indication from the UE that the UE does not support dynamic switching, and the one or two TCI states include two TCI states based on the indication that the UE does not support dynamic switching.

[0272] Example 81 may include the method of example 77, wherein the BWP is a first BWP and the RRC communication indicates configuration for up to four BWPs for the CC.

[0273] Example 82 may include an apparatus including means for performing one or more elements of the method described or related to any of Examples 1-81, or any other method or process described herein.

[0274] Example 83 may include one or more non-transitory computer-readable media containing instructions that, in response to execution of the instructions by one or more processors of the electronic device, cause an electronic device to perform one or more elements of a method described or related to any of Examples 1-81, or any other method or process described herein.

[0275] Example 84 may include an apparatus including logic, modules, or circuitry for performing one or more elements of the method described or related to any of Examples 1-81, or any other method or process described herein.

[0276] Example 85 may include any method, technique, or process described or related to any of Examples 1-81, or any part or portion thereof.

[0277] Example 86 may include an apparatus having one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in connection with any or a portion of Examples 1-81.

[0278] Example 87 may include a signal described or related to any of Examples 1-81, or a portion or part thereof.

[0279] Example 88 may include a datagram, information element, packet, frame, segment, PDU, or message described or related to any of Examples 1-81, or any portion or part thereof, or others described in this disclosure.

[0280] Example 89 may include a signal encoded with data described or related to any of Examples 1-81, or a portion or part thereof, or other method described in this disclosure.

[0281] Example 90 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message described or related to any of Examples 1-81, or a portion or part thereof, or a signal otherwise described in this disclosure.

[0282] Example 91 may include an electromagnetic signal carrying a plurality of computer-readable instructions, where execution of the plurality of computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1-81 or portions thereof.

[0283] Example 92 may include a computer program including instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples 1-81, or a portion thereof.

[0284] Example 93 may include signals in a wireless network as shown and described herein.

[0285] Example 94 may include a method of communicating in a wireless network as shown and described herein.

[0286] Example 95 may include a system for providing wireless communication as shown and described herein.

[0287] Example 96 may include a device for providing wireless communication as shown and described herein.

[0288] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0289] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. 1. A method of operating a user equipment (UE), comprising: determining a configuration per Bandwidth Part (BWP) based on a Radio Resource Control (RRC) communication received from a Transmission / Reception Point (TRP), the configuration being for configuring the UE to operate in accordance with a High Speed ​​Vehicle - Single Frequency Network (HSV-SFN) scheme 1 within the BWP; determining one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) based on a medium access control-control element (MAC-CE) received from the TRP; configuring the CORESET within the BWP based on the determination of the one or two TCI conditions.

2. The method of claim 1 , wherein the one or two TCI conditions include two TCI conditions.

3. The method further comprising: determining whether to activate a TCI codepoint having the one or two transmit TCI states based on the MAC-CE; performing a channel estimation procedure to determine a Doppler shift based on said TCI code points; The method of claim 1 , further comprising: utilizing the determined Doppler shift in decoding at least one signal received by the UE.

4. The method of claim 3 , wherein the at least one signal is received via a Physical Downlink Shared Channel (PDSCH) of the BWP.

5. the MAC-CE is a first MAC-CE, and the method comprises: identifying an indication in a second MAC-CE or a Downlink Control Information (DCI) for switching activation of the TCI codepoint to the one or two TCI states; The method of claim 3 , further comprising: toggling activation of the TCI codepoint based on the indication.

6. The method of claim 5 , wherein switching activation of the TCI codepoint comprises switching from a first BWP to a second BWP.

7. 2. The method of claim 1, wherein the BWP is a first BWP, and configuring the CORESET includes configuring the UE to operate according to the HSV-SFN scheme 1 in the first BWP and to operate according to a single-TRP scheme in a second BWP.

8. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user equipment (UE) to: determining, based on one or more signals from a transmission / reception point (TRP), that pre-compensation is performed for the UE; determining one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) based on a medium access control-control element (MAC-CE) from the TRP; One or more computer-readable media for configuring the CORESET based on the determination of the one or two TCI states.

9. The one or more computer-readable media of claim 8 , wherein the one or two TCI conditions comprises two TCI conditions.

10. The one or more computer-readable media of claim 8 , wherein the MAC-CE indicates a quasi-collocation (QCL) characteristic for the one or two TCI states.

11. 10. The one or more computer-readable media of claim 8, wherein the one or two TCI states include two TCI states, the MAC-CE includes a first Doppler shift and a first Doppler spread for a first TCI state of the two TCI states, and the MAC-CE drops a second Doppler shift and a second Doppler spread for a second TCI state of the two TCI states.

12. 9. The one or two TCI states of claim 8, wherein the one or two TCI states include two TCI states, a first quasi-collocation (QCL) characteristic for a first TCI state of the two TCI states includes a QCL Type A characteristic, and a second QCL characteristic for a second TCI state of the two TCI states includes a QCL characteristic of average delay and delay spread.

13. The one or more computer-readable media of claim 12 , wherein the QCL Type A characteristics include the following QCL characteristics: mean delay, delay spread, Doppler shift, and Doppler spread.

14. The one or more computer-readable media of claim 8 , wherein the pre-compensation comprises High Speed ​​Vehicle-Single Frequency Network (HSV-SFN) pre-compensation.

15. a memory for storing configuration information for the configuration; a processing circuit coupled to the memory, determining a configuration per Bandwidth Part (BWP) based on a Radio Resource Control (RRC) communication received from a Transmission / Reception Point (TRP), the configuration being for configuring the UE to operate with pre-compensation within the BWP; determining one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET) based on a medium access control-control element (MAC-CE) received from the TRP; and configuring the CORESET in the BWP based on the determination of the one or two TCI states.

16. The UE of claim 15, wherein the one or two TCI states include two TCI states.

17. The UE of claim 15, wherein the MAC-CE indicates a quasi-collocation (QCL) characteristic for the one or two TCI states.

18. The UE of claim 15, wherein configuring the CORESET comprises configuring the CORESET with RRC parameters based on the BWP.

19. The UE of claim 15, wherein the pre-compensation comprises High Speed ​​Vehicular - Single Frequency Network (HSV-SFN) pre-compensation.

20. 16. The UE of claim 15, wherein the one or two TCI states include two TCI states, and determining the one or two TCI states includes determining a first TCI state including QCL type A characteristics for the TCI and a second TCI state including QCL characteristics of average delay and delay spread.

21. 1. A method of operating a base station, comprising the steps of: Determining a bandwidth portion (BWP) for a component carrier (CC) configured in a high speed vehicle-single frequency network (HSV-SFN) system 1; generating a radio resource control (RRC) communication indicating that the BWP for the CC is configured using HSV-SFN scheme 1; Sending the RRC communication to the UE to configure the UE in HSV-SFN mode 1; generating a medium access control-control element (MAC-CE) indicating one or two transmission configuration indicator (TCI) states for configuration of a control resource set (CORESET); and transmitting the MAC-CE to the UE to configure the CORESET within the BWP.

22. The method further comprising:

22. The method of claim 21, further comprising receiving an indication from the UE that the UE supports dynamic switching, the MAC-CE indicating one or two TCI states based on the indication that the UE supports dynamic switching.

23. 22. The method of claim 21, wherein the one or two TCI conditions include two TCI conditions.

24. The method comprises:

22. The method of claim 21, further comprising receiving an indication from the UE that the UE does not support dynamic switching, wherein the one or two TCI states include two TCI states based on the indication that the UE does not support dynamic switching.

25. 22. The method of claim 21, wherein the BWP is a first BWP and the RRC communication indicates configuration for up to four BWPs for the CC.

Images