Bandwidth switching for physical downlink shared channel transmission with shared demodulation reference signal

Abstract

Systems and techniques for wireless communication are provided. A method can include determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission. The PDSCH transmission and the PDCCH transmission can be associated with the shared configured DMRS. The method can include receiving a scheduled PDSCH transmission using the updated bandwidth based on the shared configured DMRS.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general. In some specific embodiments, examples are described for bandwidth updates transmitted on a physical downlink shared channel (PDSCH) associated with a shared, configured demodulation reference signal (DMRS). Background Technology

[0002] Wireless communication systems are deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcasting. Wireless communication systems have undergone several generations of development, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including the transitional 2.5G networks), third-generation (3G) high-speed data wireless service with internet capabilities, fourth-generation (4G) services (e.g., LTE, WiMax), and fifth-generation (5G) services (e.g., New Radio (NR)). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc. Summary of the Invention

[0003] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceptual aspects, nor should it be considered to identify key or decisive elements relating to all conceptual aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a concise form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0004] Systems, methods, apparatuses, and computer-readable media for performing wireless communications are disclosed. According to at least one exemplary example, a method for performing wireless communications at a network entity is provided. The method includes: determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and receiving the scheduled PDSCH transmission using the updated bandwidth based on the shared configured DMRS.

[0005] In another exemplary example, an apparatus for a network entity for wireless communication is provided. The apparatus includes at least one memory and at least one processor coupled to the at least one memory and configured to: determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and, based on the shared configured DMRS, use the updated bandwidth to receive the scheduled PDSCH transmission.

[0006] In another exemplary example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and, based on the shared configured DMRS, use the updated bandwidth to receive the scheduled PDSCH transmission.

[0007] In another exemplary example, an apparatus for wireless communication is provided. The apparatus includes: components for determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and components for receiving the scheduled PDSCH transmission using the updated bandwidth based on the shared configured DMRS.

[0008] According to at least one exemplary example, a method for wireless communication performed at a network entity is provided. The method includes: determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); transmitting configuration information indicating the updated bandwidth; and using the updated bandwidth to transmit the scheduled PDSCH transmission.

[0009] In another exemplary example, an apparatus for a network entity for wireless communication is provided. The apparatus includes at least one memory and at least one processor coupled to the at least one memory and configured to: determine an updated bandwidth corresponding to a scheduled Physical Downlink Shared Channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a Physical Downlink Control Channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); transmit configuration information indicating the updated bandwidth; and use the updated bandwidth to transmit the scheduled PDSCH transmission.

[0010] In another exemplary example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); transmit configuration information indicating the updated bandwidth; and use the updated bandwidth to transmit the scheduled PDSCH transmission.

[0011] In another exemplary example, an apparatus for wireless communication is provided. The apparatus includes: components for determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); components for transmitting configuration information indicating the updated bandwidth; and components for using the updated bandwidth to transmit the scheduled PDSCH transmission.

[0012] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems, as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0013] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing provided in the drawings is for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0014] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects may be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations.

[0015] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of the entire specification, any or all of the drawings, and each claim.

[0016] The foregoing and other features and aspects will become more apparent from the following description, claims and accompanying drawings. Attached Figure Description

[0017] The accompanying drawings are provided to aid in describing various aspects of this disclosure, and are provided for illustrative purposes only and not for limiting the scope of the aspects. For a more detailed understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly summarized above, can be obtained by referring to the aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 This is a block diagram illustrating an example of a wireless communication network based on some examples; Figure 2 These are illustrations of base station and user equipment (UE) designs based on some examples, which enable the transmission and processing of signals exchanged between the UE and the base station; Figure 3 This is a diagram illustrating an example of a decomposed base station based on some examples; Figure 4 This is a block diagram illustrating the components of a user equipment (UE) based on some examples; Figure 5 This is a diagram illustrating examples of physical channels and reference signals in some example wireless networks; Figure 6A and Figure 6B This is a diagram illustrating examples of physical channels in time-division multiplexing (TDM) and frequency-division multiplexing (FDM) resources of some example wireless networks; Figure 7A This is a diagram illustrating an example of a shared configured demodulation reference signal (DMRS) associated with a physical downlink communication channel (PDCCH) and a physical downlink shared channel (PDSCH) according to some examples, wherein the shared configured DMRS and PDSCH have the same bandwidth; Figure 7B This is a diagram illustrating an example of a shared configured DMRS associated with PDCCH and PDSCH, where the shared configured DMRS and PDSCH have different corresponding bandwidths. Figure 8 This is a diagram illustrating an example of an updated Frequency Domain Resource Allocation (FDRA) start time based on an acknowledgment (ACK) and a time offset from the ACK; Figure 9 This is a diagram illustrating examples of various FDRA granularities aligned with Physical Resource Block Group (PRG) meshes, based on some examples; Figure 10AThis is a diagram illustrating an example of the location of a common PDCCH between a first FDRA and a second FDRA, based on some examples; Figure 10B This is a diagram illustrating an example of the location of a common PDCCH between the first FDRA, second FDRA, and third FDRA, based on some examples; Figure 11 This is a diagram illustrating the default FDRA applied periodically between PDCCH monitoring times, based on some examples. Figure 12 This is a diagram illustrating an example of timer-based rollback for the default FDRA, based on some examples; Figure 13 This is a flow diagram illustrating an example of a process for wireless communication based on some examples; Figure 14 This is a flow diagram illustrating another example of a process for wireless communication, based on some examples; and Figure 15 This is a block diagram illustrating an example of a computing system based on some examples. Detailed Implementation

[0019] Certain aspects of this disclosure are provided below for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure. Some aspects described herein can be applied independently, and some of them can be combined, as will be apparent to those skilled in the art. Specific details are set forth in the following description for purposes of explanation to provide a thorough understanding of various aspects of this application. However, it will be apparent, however, that various aspects can be implemented without these specific details. The accompanying drawings and descriptions are not intended to be limiting.

[0020] The following description provides only exemplary aspects and is not intended to limit the scope, applicability, or configuration of this disclosure. Rather, the following description of the exemplary aspects will provide those skilled in the art with descriptions that can be used to implement the exemplary aspects. It should be understood that various changes can be made to the function and arrangement of the elements without departing from the scope of this application as set forth in the appended claims.

[0021] Wireless communication networks can be deployed to provide a variety of communication services, such as voice, video, packet data, message sending and receiving, broadcasting, any combination thereof, or other communication services. Wireless communication networks can support both access links and sidelinks for communication between wireless devices. An access link can refer to any communication link between a client device (e.g., a User Equipment (UE), Station (STA), or other client device) and a base station (e.g., a 3GPP gNB for 5G / NR, a 3GPP eNB for 4G / LTE, a Wi-Fi access point (AP), or other base station). For example, an access link can support uplink signaling, downlink signaling, connection procedures, etc. An example of an access link is the Uu link or interface (also known as NR-Uu) between a 3GPP gNB and a UE.

[0022] In various wireless communication networks, a physical channel can correspond to a set of time-frequency resources used to transmit specific transport channel data, control information, or indicator information. For example, each transport channel can be mapped to a corresponding physical channel. The Physical Downlink Shared Channel (PDSCH) can carry user data and paging information and / or be used to convey such user data and paging information to user equipment (UE) or other terminals. The Physical Downlink Control Channel (PDCCH) can carry control information and / or be used to convey such control information, including scheduling decisions such as scheduling permission for PDSCH reception and / or for implementing transmission on the Physical Uplink Shared Channel (PUSCH).

[0023] In 4G / LTE and 5G / NR, PDCCH and PDSCH transmissions can be associated with separate Time Division Multiplexing (TDM) and / or Frequency Division Multiplexing (FDM) resources. For example, a first set of time-frequency resources can be used for PDCCH transmission, while a second set of time-frequency resources can be used for PDSCH transmission, wherein the first and second sets do not overlap (e.g., the corresponding time-frequency resources can be included in the first or second set, rather than in two sets).

[0024] In 4G / LTE, PDCCH transmission can occur at the beginning of a time slot or subframe (e.g., with PDCCH TDM). Figure 6AFigure 600a illustrates the time-frequency resource allocation (e.g., horizontal time axis, vertical frequency axis) corresponding to two example subframes, each example subframe including a PDCCH area followed by a corresponding data area (e.g., a corresponding PDSCH area). The PDCCH area may also be referred to as the "control area," and the PDSCH area may also be referred to as the "data area." In some examples, PDCCH transmission may occupy one to three Orthogonal Frequency Division Multiplexing (OFDM) symbols (e.g., dynamically indicated by transmission via the Physical Control Format Indicator Channel (PCFICH)). In some cases, the base station (e.g., eNB, etc.) may determine or configure the amount of PDCCH resources in the time slot, for example, based on the corresponding control load associated with PDCCH transmission in the time slot.

[0025] In 5G / NR, PDCCH transmission can utilize corresponding resources within a control resource set (e.g., allocated PDCCH resources). The control resource set is also referred to as a "CORESET" and can refer to the set of physical time-frequency resources associated with transmitting PDCCH and / or downlink control information (DCI). In 5G / NR, PDCCH transmission utilizing CORESET resources can be implemented based on TDM and / or FDM, which are used for PDSCH transmission. In some cases, PDSCH resource allocation is performed to avoid overlap with the CORESET (e.g., one or more time-frequency resources allocated for PDSCH transmission are different from and do not overlap with the CORESET time-frequency resources). For example, Figure 6B Diagram 600b illustrates time-frequency resource allocation corresponding to two example time slots, each example time slot including a CORESET and a data area. The data area may also be referred to as a PDSCH area (e.g., PDSCH resource allocation). In some cases, PDSCH resource allocation may, for example, be based on rate matching around the PDCCH carrying the DL permission for scheduling PDSCH (e.g., within the CORESET) overlapping with the CORESET. Where the CORESET includes a single permission (e.g., a DL permission for scheduling PDSCH), rate matching around the corresponding PDCCH for scheduling PDSCH can be optimized for resource allocation.

[0026] The 5G / NR spectrum resources specified in the 3GPP protocol can be divided into two distinct frequency ranges: Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 and FR2 are also referred to as frequency range specifications. FR1 corresponds to the frequency range below 6 GHz and can include frequencies from 450 MHz to 6 GHz. The low- and mid-band frequencies within FR1 can travel relatively long distances with better obstacle penetration (e.g., better indoor coverage) compared to the high-band frequencies. FR2 corresponds to frequencies from 24.25 GHz to 52.60 GHz and is also known as the millimeter-wave band. FR2 can offer greater bandwidth and / or lower latency than FR1, but may also have shorter range and lower penetration of buildings and other solid obstacles.

[0027] The FR1 band can utilize either FDD or TDD duplex mode. The FR2 band uses analog beamforming (e.g., FR2 has analog beam limiting) and utilizes TDD duplex mode. For example, using analog beamforming in FR2 corresponds to a low probability of serving different UEs (e.g., utilizing traffic) in the same analog beam. Based on this low probability, FDM is not used to serve different UEs (e.g., in the case of a single array). Instead, TDM is used to serve different UEs on the FR2 band (and / or spatial division multiplexing (SDM) when multiple panels or arrays are used). The FR2 band is additionally associated with a relatively large subcarrier spacing (SCS) and a relatively short symbol / slot duration.

[0028] A CORESET is a set of resources (e.g., time-frequency resources) that can be shared by multiple PDCCH transmissions targeting multiple UEs. Sharing of CORESET resources for multiple PDCCH transmissions can be based on increased control capacity and flexibility (e.g., to transmit DCIs to multiple UEs with different geometries and using different aggregation levels). Different UEs can be additionally associated with different channel implementation information. In the prior art, the demodulation reference signal (DMRS) is self-contained within each PDCCH transmission, and pre-decoding can be selected individually for each DCI.

[0029] As noted above, CORESET is designed to support multi-UE DCI transmission (e.g., transmitting DCI to multiple UEs). To support multi-UE DCI transmission, the 3GPP specification stipulates that PDCCH transmission carrying DCI can also include self-contained DMRS (e.g., allowing separate pre-decoding for each DCI).

[0030] CORESET's optimization for multi-UE DCI transmission use cases corresponds to a 5G / NR implementation using FR1, because the FR2 analog beamforming limitation results in a very low probability of multiple UEs being in the same analog beam. Systems and technologies are needed to provide PDCCH / PDSCH multiplexing optimized for FR2 and / or frequencies greater than FR2. For example, PDCCH / PDSCH multiplexing is needed to transmit one or more DCIs to the same UE, where shared pre-decoding and / or beamforming can be used for one or more DCIs and / or between PDCCH and PDSCH.

[0031] This document describes systems, apparatus, processes (also referred to as methods), and computer-readable media (collectively, the “System and Technology”) that can be used to update the PDSCH bandwidth for PDSCH transmissions that share a configured DMRS with PDCCH transmissions. In some examples, the bandwidth allocation for scheduled PDSCH transmissions (e.g., also referred to as “PDSCH bandwidth”) can be the same as the bandwidth allocation for PDCCH transmissions that schedule PDSCH (e.g., also referred to as “PDCCH bandwidth”). The PDSCH bandwidth can also be the same as the bandwidth of the shared configured DMRS associated with the PDSCH and PDCCH (e.g., the DMRS bandwidth can be the same as the PDCCH bandwidth, which in turn can be the same as the PDSCH bandwidth).

[0032] In some cases, the PDSCH bandwidth can be modified and / or updated based on the path loss between the network entity and the UE. For example, the updated PDSCH bandwidth can be determined based on the path loss between the network entity and the UE, where the UE receives the PDCCH, configured shared DMRS, and PDSCH from the network entity. For instance, a UE located further away from the network entity (e.g., a base station, gNB, etc.) can be updated to receive the PDSCH corresponding to the configured shared DMRS and / or PDCCH using a narrower bandwidth. In another example, a UE located closer to the network entity (e.g., a base station, gNB, etc.) can be updated to receive the PDSCH corresponding to the configured shared DMRS and / or PDCCH using a wider bandwidth.

[0033] In some aspects, when a relatively small packet size is associated with PDSCH transmissions from a network entity to the UE, the PDSCH bandwidth can remain the same (e.g., no PDSCH update is performed), and a shorter Time Domain Resource Allocation (TDRA) can be used to receive PDSCH transmissions from the network entity. In some examples, the system and techniques can be used to implement updated PDSCH bandwidth for receiving PDSCH transmissions using a configured shared DMRS associated with PDCCH transmissions that schedule PDSCH transmissions. For example, in some aspects, the system and techniques can implement updated PDSCH bandwidth based on configuring updated Frequency Domain Resource Allocation (FDRA) for the UE. In some aspects, the updated PDSCH bandwidth can be updated without the network entity sending an updated FDRA field and / or updated FDRA information to the UE.

[0034] In some cases, updated PDSCH bandwidth for sharing the configured DMRS with the PDCCH can be implemented based on one or more semi-static bandwidth configurations. In some examples, the downlink (DL) bandwidth portion (BWP) can be directly reused for the updated PDSCH bandwidth. In another example, the UE can receive Radio Resource Control (RRC) messages and / or receive RRC configurations indicating updated PDSCH bandwidth for the UE. In some examples, the UE can receive configuration information indicating multiple candidate PDSCH bandwidths (e.g., from a network entity associated with the UE). The UE can receive (e.g., sent by a network entity) bandwidth switching information indicating a specific candidate PDSCH bandwidth from multiple configured candidate PDSCH bandwidths. Based on the bandwidth switching information, the UE can update the PDSCH bandwidth used to receive scheduled PDSCH transmissions. In some examples, the bandwidth switching information can be a Media Access Control (MAC)-Control Element (MAC-CE) and / or may include downlink control information (DCI).

[0035] In some examples, updated PDSCH bandwidth for sharing the configured DMRS with the PDCCH can be implemented based on dynamic switching of PDSCH bandwidth. For example, the updated PDSCH bandwidth can be based on a DCI that includes and / or indicates FDRA information (e.g., updated FDRA information) for the UE. The UE can receive the DCI from a network entity (e.g., a base station, gNB, etc.). The UE can apply the updated FDRA at a later FDRA start time than when the UE receives the DCI indicating the updated FDRA. For example, the UE can receive a DL grant DCI that includes an FDRA field indicating the updated FDRA for the UE's PDSCH bandwidth. The UE does not apply the updated FDRA to the current DL grant and waits to apply the updated FDRA to PDSCH transmissions received starting at a later time. The later time can be based on a configured time offset from when the UE receives the DL grant DCI that includes the FDRA field indicating the updated FDRA. In some cases, the time offset may originate from the start or end of a DL grant in which the DCI, including updated FDRA field information, is received by the UE.

[0036] In some cases, the time offset can be determined relative to the acknowledgment (ACK) or negative acknowledgment (NACK) corresponding to DL approval. For example, the time offset can be a configured time offset in units of time slots (e.g., three time slots, etc.) or in units of absolute time (e.g., 3 ms, etc.). In some aspects, the UE can utilize a default FDRA corresponding to the default PDSCH bandwidth. If the UE's understanding of the current active FDRA is incorrect or otherwise differs from the current active FDRA transmitted by the network entity for PDCCH monitoring timings, the UE can utilize the default FDRA at least for some PDCCH monitoring timings to allow the network entity to successfully transmit (e.g., and allow the UE to successfully receive). In some examples, the default FDRA and the corresponding periodicity (e.g., the periodicity pattern or interval used to apply the default FDRA at the UE) can be configured at the UE by the network entity. In another example, the UE can (e.g., by the network entity) utilize the default FDRA and the corresponding timer value used for the default FDRA. If the timer value (e.g., the timer interval) expires, the UE can perform a backoff to the default FDRA. The default FDRA timer can be reset at the UE based on receiving valid control using the UE's current active FDRA information (for example, the default FDRA timer can be reset based on the UE successfully receiving PDCCH or PDSCH using the UE's current active FDRA).

[0037] Other aspects of the system and technology will be described in relation to the accompanying drawings.

[0038] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0039] As used herein, the terms “User Equipment” (UE) and “Network Entity” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable device (e.g., smartwatch, smart glasses, wearable ring, and / or extended reality (XR) device (such as virtual reality (VR) headsets, augmented reality (AR) headsets or glasses, or mixed reality (MR) headsets)), vehicle (e.g., car, motorcycle, bicycle, etc.), aircraft (e.g., airplane, jet, unmanned aerial vehicle (UAV) or drone, helicopter, airship, glider, etc.), and / or Internet of Things (IoT) device, etc., for a user to use to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal," or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the IEEE 802.11 communication standard), etc.

[0040] Network entities can be implemented in aggregated or monolithic base station architectures, or alternatively, in decomposed base station architectures, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. A base station (e.g., with an aggregated / monolithic or decomposed base station architecture) may operate according to one of several RATs communicating with the UE (depending on the network in which it is deployed), and may alternatively be referred to as an access point (AP), network node, NodeB (NB), evolved NodeB (eNB), next-generation eNB (ng-eNB), new radio (NR) NodeB (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication links through which a UE can transmit signals to a base station are called uplink (UL) channels (e.g., reverse traffic channels, reverse control channels, access channels, etc.). The communication links through which a base station can transmit signals to a UE are called downlink (DL) or forward link channels (e.g., paging channels, control channels, broadcast channels, or forward traffic channels, etc.). As used herein, the term traffic channel (TCH) can refer to uplink, reverse or downlink, and / or forward traffic channel.

[0041] The terms "network entity" or "base station" (e.g., having a converged / monolithic or decomposed base station architecture) can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may be co-located or non-co-located. For example, when the term "network entity" or "base station" refers to a single physical TRP, that physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. When the term "network entity" or "base station" refers to multiple co-located physical TRPs, these physical TRPs may be antenna arrays of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (e.g., a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (e.g., a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and the neighboring base station where the UE is measuring its reference radio frequency (RF) signal (e.g., or simply "reference signal"). Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to the specific TRP of that base station.

[0042] In some specific implementations supporting UE positioning, network entities or base stations may not support the UE's radio access (e.g., may not support data, voice, and / or signaling connections regarding the UE), but instead may transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0043] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, can be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote unit (RU), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. Alternatively, a network node may be a base station or a network entity. Alternatively, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

[0044] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) can be, resemble, include, or be included in (e.g., a component of) a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a RedCap device, an eRedCap device, an ambient Internet of Things (IoT) device, an energy harvesting (EH) capable device, a network controller, apparatus, device, computing system, an integrated access and backhaul (IAB) node, a DU, CU, RU (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity can be a UE. As another example, a network entity can be a base station. As used herein, “network entity” can mean an entity configured to operate in a network (such as network entity 108). For example, “network entity” is not limited to an entity currently located in and / or currently operating in a network. Rather, a network entity can be any entity capable of communicating and / or operating within a network.

[0045] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in context, and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0046] Similarly, references to UE, base station, network node, device, equipment, computing system, etc., may include disclosures of UE, base station, network node, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0047] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0048] RF signals comprise electromagnetic waves of a given frequency that transmit information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, where the context clearly indicates that the term “signal” refers to a wireless signal or RF signal, an RF signal may also be referred to as a “wireless signal” or simply a “signal.”

[0049] Various aspects of the systems and technologies described herein will be discussed below with reference to the accompanying drawings. According to these aspects, Figure 1An example of a wireless communication system 100 is illustrated. The wireless communication system 100 (e.g., also referred to as a wireless wide area network (WWAN)) may include individual base stations 102 and individual UEs 104. In some aspects, base station 102 may also be referred to as a "network entity" or "network node". One or more of base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of base stations 102 may be implemented in a decomposed base station architecture and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. Base station 102 may include macrocell base stations (e.g., high-power cellular base stations) and / or small cell base stations (e.g., low-power cellular base stations). On the one hand, macro cell base stations may include eNB and / or ng-eNB (where wireless communication system 100 corresponds to a Long Term Evolution (LTE) network), or gNB (where wireless communication system 100 corresponds to an NR network), or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0050] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 via core network 170 (e.g., the one or more location servers may be part of core network 170 or may be outside core network 170). Among other functions, base station 102 can perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC or 5GC) via backhaul link 134 (which may be wired and / or wireless).

[0051] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. In one aspect, base station 102 in each coverage area 110 can support one or more cells. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of the cell, the terms “cell” and “TRP” can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0052] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in a handover area), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0053] The communication link 120 between base station 102 and UE 104 may include uplink (e.g., also referred to as the reverse link) transmission from UE 104 to base station 102 and / or downlink (e.g., also referred to as the forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. One or more carrier frequencies may be used to provide the communication link 120. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0054] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., one or more of base station 102, UE 104, etc.) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be implemented by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0055] Transmitting and / or receiving devices (e.g., one or more such as base station 102 and / or UE 104) may use beam scanning technology as part of beamforming operations. For example, base station 102 (e.g., or other transmitting devices) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 104 (e.g., or other receiving devices). Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 102 (or other transmitting devices) in different directions. For example, base station 102 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission in different beam directions may be used to identify (e.g., by transmitting devices such as base station 102, or by receiving devices such as UE 104) beam directions so that base station 102 may transmit or receive later.

[0056] Some signals (such as data signals associated with a specific receiving device) may be transmitted by base station 102 in a single beam direction (e.g., the direction associated with a receiving device, such as UE 104). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted in one or more beam directions. For example, UE 104 may receive one or more signals transmitted by base station 102 in different directions, and may report to base station 104 an indication of signals received by UE 104 with the highest signal quality or other acceptable signal quality.

[0057] In some examples, transmissions performed by a device (e.g., by base station 102 or UE 104) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or radio frequency beamforming to generate combined beams for transmission (e.g., from base station 102 to UE 104, from transmitting device to receiving device, etc.). UE 104 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured number of beams across system bandwidth or one or more subbands. Base station 102 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), etc.), which may or may not be pre-decoded. UE 104 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by base station 102 in one or more directions, UE 104 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam direction for subsequent transmission or reception by UE 104), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0058] A receiving device (e.g., UE 104) may attempt multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 102. For example, the receiving device may attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these may be referred to as “listening” according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receiving configuration may be aligned on a beam direction determined based on listening according to different receiving configuration directions (e.g., based on a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0059] The wireless communication system 100 may further include a WLAN AP 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a Free Channel Assessment (CCA) or Listen-After-Talk (LBT) process before communication to determine if the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., using ultra-wideband (UWB) spectrum. The UWB spectrum can range from 3.1 GHz to 10.5 GHz.

[0060] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE and / or 5G in unlicensed spectrum can enhance coverage of the access network and / or increase the capacity of the access network. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0061] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. The mmW base station 180 may be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz with wavelengths between 1 mm and 10 mm. Radio waves in this band can be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW and / or near-mmW radio bands has high path loss and relatively short range. mmW base station 180 and UE 182 can utilize beamforming (e.g., transmission and / or reception) on mmW communication link 184 to compensate for extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0062] In some aspects related to 5G, the spectrum in which wireless network nodes or entities (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (e.g., from 450 MHz to 6,000 MHz), FR2 (e.g., from 24,250 MHz to 52,600 MHz), FR3 (e.g., above 52,600 MHz), and FR4 (e.g., between FR1 and FR2). In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCell.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure in that cell. The primary carrier carries all common control channels as well as UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, since the primary uplink and primary downlink carriers are typically UE-specific, those UE-specific signaling information and signals may not be present on the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a “serving cell” (e.g., whether it is a PCell or a SCell) corresponds to a carrier frequency and / or component carrier that some base stations are using for communication, the terms “cell”, “serving cell”, “component carrier”, “carrier frequency”, etc. can be used interchangeably.

[0063] For example, still refer to Figure 1One of the frequencies used by macro cell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 may be secondary carriers ("SCell"). In carrier aggregation, each carrier of base station 102 and / or UE 104 may use up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz) of spectrum, with up to a total of Yx MHz (e.g., x component carriers) for transmission in each direction. Component carriers may or may not be adjacent to each other in the spectrum. Carrier allocation may be asymmetrical with respect to downlink and uplink (e.g., more or fewer carriers may be allocated to downlink compared to uplink). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20 MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (e.g., 40 MHz) compared to the data rate obtained by a single 20 MHz carrier.

[0064] To operate on multiple carrier frequencies, base station 102 and / or UE 104 may be equipped with multiple receivers and / or transmitters. For example, UE 104 may have two receivers, namely "Receiver 1" and "Receiver 2", where "Receiver 1" is a multi-band receiver that can be tuned to band "X" or band "Y", while "Receiver 2" is a single-band receiver that can be tuned to only band "Z". In this example, if UE 104 is being served in band "X", then band "X" will be referred to as PCell or active carrier frequency, and "Receiver 1" will need to tune from band "X" to band "Y" (e.g., SCell) to measure band "Y" (and vice versa). In contrast, regardless of whether UE 104 is being served in band "X" or band "Y", due to the separate "Receiver 2", UE 104 can measure band "Z" without interrupting service on band "X" or band "Y".

[0065] The wireless communication system 100 may further include a UE 164, which can communicate with the macro cell base station 102 on the communication link 120 and / or with the mmW base station 180 on the mmW communication link 184. For example, the macro cell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0066] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., referred to as "side links"). Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (e.g., UE 190 can indirectly obtain WLAN-based Internet connectivity through this link). In one example, D2D P2P links 192 and 194 can use any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth). ® (etc.) to support.

[0067] Figure 2 A block diagram illustrating an example architecture 200 for a base station 102 and a UE 104 according to some aspects of this disclosure is provided, which enables the transmission and processing of signals exchanged between the UE and the base station. Example architecture 200 includes components of base station 102 and UE 104, which may be... Figure 1 The illustrated base station 102 includes one base station and the UE 104 includes one UE. The base station 102 may be equipped with T antennas 234a to 234t, and the UE 104 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

[0068] At base station 102, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and decoding schemes (MCS) for each UE based on a channel quality indicator (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based on the selected MCS, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Modulators 232a to 232t are shown as combined modulator-demodulators (MOD-DEMODs). In some cases, the modulators and demodulators can be separate components. Each modulator in modulators 232a to 232t can process a corresponding output symbol stream (e.g., for an orthogonal frequency division multiplexing (OFDM) scheme, etc.) to obtain an output sample stream. Each modulator in modulators 232a to 232t can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals can be transmitted from modulators 232a to 232t via T antennas 234a to 234t, respectively. Based on some aspects described in more detail below, position coding can be used to generate synchronization signals to transmit additional information.

[0069] At UE 104, antennas 252a to 252r can receive downlink signals from base station 102 and / or other base stations, and can provide the received signals to one or more demodulators (DEMODs) 254a to 254r respectively. Demodulators 254a to 254r are shown as combined modulator-demodulators (MOD-DEMODs). In some cases, the modulator and demodulator can be separate components. Each demodulator in 254a to 254r can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator in 254a to 254r can further process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 104 to the data sink 260, and provide the decoded control information and system information to the controller / processor 280. The channel processor can determine the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or Channel Quality Indicator (CQI), etc.

[0070] On the uplink, at UE 104, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmitting processor 264 can also generate reference symbols for one or more reference signals (e.g., based on β values ​​or sets of β values ​​associated with the one or more reference signals). The symbols from the transmitting processor 264 can be pre-decoded by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 102. At base station 102, uplink signals from UE 104 and other UEs can be received by antennas 234a to 234t, processed by demodulators 232a to 232t, detected by MIMO detector 236 (e.g., where applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 104. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller (e.g., processor) 240. Base station 102 may include communication unit 244 and communicate with network controller 231 via communication unit 244. Network controller 231 may include communication unit 294, controller / processor 290, and memory 292.

[0071] In some respects, one or more components of UE 104 may be included in the housing. These include the controller 240 of base station 102, the controller / processor 280 of UE 104, and / or Figure 2 Any other component may perform one or more techniques associated with the implicit UCI β value determination for NR.

[0072] Memory 242 and memory 282 can store data and program code for base station 102 and UE 104, respectively. Scheduler 246 can schedule UE for data transmission on downlink, uplink and / or sidelink.

[0073] In some respects, the deployment of communication systems (such as 5G New Radio (NR) systems) can involve a variety of components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, a BS (e.g., such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (e.g., also known as a standalone BS or monolithic BS) or a decomposed base station.

[0074] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units (e.g., one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0075] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in integrated access backhaul (IAB) networks, open radio access networks (O-RAN (e.g., network configurations such as those initiated by the O-RAN Alliance)), or virtualized radio access networks (e.g., vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0076] Figure 3 This is an illustration of an example decomposed base station 300 architecture. The decomposed base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more decomposed base station units (e.g., a near real-time (near RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links (e.g., F1 interfaces). DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. RUs 340 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 340.

[0077] Figure 3Each of the units shown and / or described herein (e.g., CU 310, DU 330, RU340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0078] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0079] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, DU 330 may host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending on a functional partition (e.g., such as that defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0080] Lower-layer functionality can be implemented by one or more RU 340s. In some deployments, an RU340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 340 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration enables the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0081] SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces (e.g., such as the O1 interface). For virtualized network elements, SMO framework 305 can be configured to interact with a cloud computing platform (e.g., such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (e.g., such as instantiating virtualized network elements) via a cloud computing platform interface (e.g., such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RTRIC 325. In some specific implementations, SMO framework 305 can communicate with the hardware aspects of the 4G RAN (e.g., such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0082] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, for example, via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface, for example, via an E2 interface, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0083] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and may be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0084] Figure 4 An example of a computing system 470 for a wireless device 407 is illustrated. The wireless device 407 may include client devices such as UEs (e.g., UE 104, UE 152, UE 190) or other types of devices usable by an end user (e.g., a station (STA) configured to communicate using a Wi-Fi interface). For example, the wireless device 407 may include mobile phones, routers, tablet computers, laptop computers, tracking devices, wearable devices (e.g., smartwatches, glasses, extended reality (XR) devices such as virtual reality (VR), augmented reality (AR), or mixed reality (MR) devices), Internet of Things (IoT) devices, vehicles, aircraft, and / or another device configured to communicate via a wireless communication network. The computing system 470 includes software and hardware components that may be electrically coupled or communicatively coupled (e.g., or may otherwise communicate, as applicable) via a bus 489. For example, the computing system 470 includes one or more processors 484. One or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, special-purpose hardware, any combination thereof, and / or other processing devices or systems. One or more processors 484 may use bus 489 to communicate between cores and / or with one or more memory devices 486.

[0085] The computing system 470 may also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more SIMs 474, one or more modems 476, one or more wireless transceivers 478, antennas 487, one or more input devices 472 (e.g., camera, mouse, keyboard, touchscreen, touchpad, keypad and / or microphone, etc.) and one or more output devices 480 (e.g., display, speaker and / or printer, etc.).

[0086] In some aspects, computing system 470 may include one or more RF interfaces configured to transmit and / or receive radio frequency (RF) signals. In some examples, the RF interface may include components such as modem 476, wireless transceiver 478, and / or antenna 487. One or more wireless transceivers 478 may transmit and receive wireless signals (e.g., signal 488) from one or more other devices via antenna 487, such as other wireless devices, network devices (e.g., base stations such as eNBs and / or gNBs, Wi-Fi access points (APs) such as routers or range extenders, etc.), and / or cloud networks, etc. In some examples, computing system 470 may include multiple antennas or antenna arrays that facilitate simultaneous transmission and reception functionality. Antenna 487 may be an omnidirectional antenna, allowing radio frequency (RF) signals to be received and transmitted in all directions. Wireless signal 488 may be transmitted via a wireless network. The wireless network may be any wireless network, such as cellular or telecommunications networks (e.g., 3G, 4G, 5G, etc.), wireless local area networks (e.g., Wi-Fi networks), Bluetooth, etc. ™ Networks and / or other networks.

[0087] In some examples, wireless signal 488 can be transmitted directly to other wireless devices using sidelink communication (e.g., using a PC5 interface, using a DSRC interface, etc.). Wireless transceiver 478 can be configured to transmit RF signals via antenna 487 for performing sidelink communication according to one or more transmit power parameters that can be associated with one or more regulated modes. Wireless transceiver 478 can also be configured to receive sidelink communication signals with different signal parameters from other wireless devices.

[0088] In some examples, one or more wireless transceivers 478 may include an RF front end, which includes one or more components such as amplifiers, mixers for down-conversion of signals (e.g., also referred to as signal multipliers), frequency synthesizers (e.g., also referred to as oscillators) that supply signals to the mixers, baseband filters, analog-to-digital converters (ADCs), one or more power amplifiers, and other components. The RF front end typically handles the selection of wireless signals 488 and the conversion of wireless signals to baseband frequencies or intermediate frequencies, and can convert RF signals to the digital domain.

[0089] In some cases, computing system 470 may include a decoder-decoder device (or codec) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 478. In some cases, computing system 470 may include an encryption-decryption device or component configured (e.g., according to AES and / or DES standards) to encrypt and / or decrypt data transmitted and / or received by one or more wireless transceivers 478.

[0090] One or more SIMs 474 may each securely store an International Mobile Subscriber Identity (IMSI) number and associated key assigned to a user of a wireless device 407. The IMSI and key can be used to identify and authenticate the subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 474. One or more modems 476 may modulate one or more signals to encode information to be transmitted using one or more wireless transceivers 478. One or more modems 476 may also demodulate signals received by one or more wireless transceivers 478 to decode the transmitted information. In some examples, one or more modems 476 may include a Wi-Fi modem, a 4G (or LTE) modem, a 5G (or NR) modem, and / or other types of modems. One or more modems 476 and one or more wireless transceivers 478 may be used to transmit data from one or more SIMs 474.

[0091] The computing system 470 may also include one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 486) (and / or communicate with them), which may include, but are not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices such as RAM and / or ROM, which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems and / or database structures.

[0092] In various aspects, functionality may be stored in memory device 486 as one or more computer program products (e.g., instructions or code) and executed by one or more processors 484 and / or one or more DSPs 482. Computing system 470 may also include software elements (e.g., residing within one or more memory devices 486) including, for example, operating systems, device drivers, executable libraries, and / or other code, such as one or more application programs that may include computer programs implementing the functionality provided by various aspects, and / or may be designed to implement methods and / or configure the system as described herein.

[0093] Figure 5 This is a diagram illustrating example 500 of physical channels and reference signals in a wireless network. In some examples, one or more downlink channels and one or more downlink reference signals may carry information from base station 102 to UE 104. One or more uplink channels and one or more uplink reference signals may carry information from UE 104 to base station 102.

[0094] In some respects, downlink channels may include one or more of the following: a Physical Downlink Control Channel (PDCCH) carrying downlink control information (DCI), a Physical Downlink Shared Channel (PDSCH) carrying downlink data, and / or a Physical Broadcast Channel (PBCH) carrying system information. In some respects, PDSCH communication may be scheduled by PDCCH communication.

[0095] In some examples, the uplink channel may include one or more of the following: a Physical Uplink Control Channel (PUCCH) carrying uplink control information (UCI), a Physical Uplink Shared Channel (PUSCH) carrying uplink data, and / or a Physical Random Access Channel (PRACH) for initial network access. In some aspects, UE 104 may send acknowledgment (ACK) or negative acknowledgment (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0096] In some cases, the downlink reference signal may include one or more of the following: Synchronization Block (SSB), Channel State Information (CSI) Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), and / or Phase Tracking Reference Signal (PTRS). In some examples, the uplink reference signal may include one or more of the following: Sounding Reference Signal (SRS), DMRS, and / or PTRS.

[0097] The SSB may carry or include information for initial network acquisition and synchronization. For example, the SSB may carry or include one or more of the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH, and / or PBCH DMRS. The SSB may be referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, base station 102 may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0098] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management, etc. For example, base station 102 may configure a CSI-RS set for UE 104, and UE 104 may measure the configured set of CSI-RS. Based on the CSI-RS measurement, UE 104 may perform channel estimation and report the channel estimation parameters to base station 102 (e.g., in a CSI report). For example, the channel estimation parameters may include one or more of the following: Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), Rank Indicator (RI), and / or Reference Signal Received Power (RSRP), etc.

[0099] In some examples, base station 102 may use CSI reports to select transmission parameters for downlink communication to UE 104. For example, base station 102 may use CSI reports to select transmission parameters including one or more of the following: the number of transmission layers (e.g., rank), the pre-decoding matrix (e.g., pre-decoder), the modulation and decoding scheme (MCS), and / or refined downlink beams (e.g., using beam refinement or beam management procedures), etc.

[0100] The DMRS can carry information used to estimate the radio channel for demodulating the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of the DMRS can be specific to the physical channel it is used to estimate. The DMRS is UE-specific, can be beamformed, can be confined to scheduled resources (e.g., not transmitted over broadband), and can be transmitted only when necessary. As shown, the DMRS is used for both downlink and uplink communication.

[0101] PTRS can carry information for compensating oscillator phase noise. In some cases, oscillator phase noise can increase with increasing oscillator carrier frequency. In some examples, PTRS can be used at high carrier frequencies (e.g., millimeter-wave frequencies) to mitigate oscillator phase noise. PTRS can be used to track the phase of a local oscillator and to achieve suppression of phase noise and common phase error (CPE). Figure 5 As shown, in some examples, one or more PTRS can be used for both downlink communication (e.g., on PDSCH) and uplink communication (e.g., on PUSCH).

[0102] The PRS may carry information associated with timing or ranging measurements of UE 104. For example, UE 104 may utilize one or more signals (e.g., PRS) transmitted by base station 102 to improve Observed Time Difference of Arrival (OTDOA) positioning performance. In some examples, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped diagonally with frequency and time offsets to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). The PRS may be designed to improve the detectability of UE 104, which may need to detect downlink signals from multiple neighboring base stations to perform OTDOA-based positioning. Therefore, UE 104 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report Reference Signal Time Difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, base station 102 may calculate the positioning of UE 104 based on the RSTD measurements reported by UE 104.

[0103] In some examples, the SRS may carry information for uplink channel estimation, which can be used for scheduling, link adaptation, pre-decoder selection, and / or beam management, etc. Base station 102 may configure one or more SRS resource sets for UE 104, and UE 104 may transmit SRS on the configured SRS resource sets. The SRS resource sets may have configurable uses, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. Base station 102 may measure the SRS, perform channel estimation based on the measurement, and / or use the SRS measurement to configure communication with UE 104.

[0104] As previously noted above, this document describes systems and techniques that can be used to update the PDSCH bandwidth for PDSCH transmissions that share a configured DMRS (e.g., also referred to as "shared configured DMRS", "configured shared DMRS", and / or "shared DMRS") with PDSCH transmissions. For example, a PDSCH transmission may share a configured shared DMRS with a PDCCH transmission that is scheduled (e.g., scheduled) for PDSCH transmission. The shared configured DMRS may be a fixed DMRS associated with both the PDCCH and PDSCH transmissions. The fixed DMRS may be configured based on a corresponding time-frequency resource set and DMRS sequence (e.g., by a network entity associated with the UE, such as a base station, gNB, etc.). PDSCH transmissions may be scheduled by PDCCH transmissions (e.g., PDCCH transmissions may include a DCI indicating DL permission corresponding to or associated with the PDSCH). In some cases, this system and technology can be used to integrate PDCCH and PDSCH transmissions for higher frequency bands (such as 5G NR FR2 (e.g., millimeter wave)) and / or provide improved resource utilization for PDCCH and PDSCH transmissions on higher frequency bands.

[0105] Figure 7A and Figure 7B This is a diagram illustrating an example of a shared, configured DMRS associated with PDCCH and PDSCH transmissions. For example, Figure 7A An example time-frequency resource 700 is illustrated, which is associated with a shared configured DMRS having the same bandwidth as PDCCH transmission and PDSCH transmission. Figure 7B An example time-frequency resource 750 is illustrated with a shared configured DMRS having a different bandwidth than the shared configured DMRS and PDCCH transmission (e.g., an updated bandwidth relative to the shared configured DMRS and PDCCH transmission).

[0106] As used herein, the phrase “PDCCH” or “the PDCCH” can be used interchangeably with “PDCCH sent” or “the PDCCH sent”, respectively. The phrase “PDSCH” or “the PDSCH” can also be used interchangeably with “PDSCH sent” or “the PDSCH sent”, respectively. PDCCH can also be referred to as “control information,” and PDSCH can also be referred to as “scheduled downlink data transmission.” For example, a PDCCH that schedules a PDSCH can be referred to as control information indicating scheduled downlink data transmission.

[0107] Figure 7A and Figure 7BExamples of corresponding sets of resource elements (REs) along the horizontal time axis and the vertical frequency axis are shown. For example, Figure 7A The first episode of time / frequency RE 700 is illustrated, and Figure 7B A second set of time / frequency RE 750 is illustrated. Each corresponding set of RE 700 and RE 750 includes a control area and a data area. The control area may also be referred to as a "PDCCH area," and the data area may also be referred to as a "PDSCH area." The control area (e.g., the PDCCH area) includes a subset of the time-frequency resources included in the RE set. Shared, configured DMRS can be transmitted using resource allocation within the PDCCH area (e.g., within PDCCH transmission). Bandwidth can be represented by the height of each area and / or the transmission along the vertical frequency axis. For example, a wider bandwidth includes a larger number of individual frequency resources and is higher along the vertical frequency axis than a narrower bandwidth that includes a smaller number of individual frequency resources.

[0108] In some cases, a control area (e.g., a PDCCH area) may correspond to a subset of REs used for transmitting and / or receiving control information (such as PDCCH) (e.g., by network entities, base stations, gNBs, etc.) and / or (e.g., by the UE) receiving control information (such as PDCCH). A data area (e.g., a PDSCH area) may correspond to a subset of REs used for transmitting and / or receiving data information (such as PDSCH).

[0109] For example, Figure 7A The RE 700 set includes a control area 702 and a data area 706. Figure 7B The set of REs 700 and 750 includes control area 752 and data area 756. In some aspects, control areas 702 and 752 and data areas 706 and 756 may not overlap, wherein a corresponding RE in the set of REs 700 and 750 may be included in control area 702 and 752 or may be included in data area 706 and 756, but not both. In some aspects, Figure 7A and Figure 7B An example is shown using a configured shared DMRS (e.g., Figure 7A The configured shared DMRS 705 Figure 7B Example RE allocation sent by the multiplexed PDCCH and PDSCH of the configured shared DMRS 755.

[0110] exist Figure 7A In the example, the bandwidth of the configured shared DMRS 705 can be the same as the bandwidth of the potentially allocated PDSCH 706, and can also be the same as the bandwidth of PDCCH 702. For example, the configured shared DMRS 705, PDCCH 702, and PDSCH 706 can have the same bandwidth BW0.

[0111] exist Figure 7B In the example, the configured bandwidth of the shared DMRS 755 can be the same as the bandwidth of the PDCCH 752 (e.g., BW0), and can be greater than (e.g., wider than) the bandwidth of a potentially allocated PDSCH 756 (e.g., BW1). A narrower PDSCH 756 bandwidth BW1 can include fewer frequency resources than a wider DMRS 755 bandwidth BW0. A narrower PDSCH 756 bandwidth BW0 also includes fewer frequency resources than a wider PDSCH 756 bandwidth BW0.

[0112] If the DMRS is not shared between the PDCCH and the corresponding PDSCH (e.g., the PDSCH scheduled by the PDCCH), the UE can first use the CORESET (e.g., such as...). Figure 6B In Example 600b, the UE searches for the PDCCH within each of the two time slots (as shown in the CORESET). In this example, the UE searches for the PDCCH within the CORESET and then decodes the PDCCH before beginning to decode the corresponding PDSCH scheduled by the PDCCH. Based on the fact that the PDCCH is decoded before the corresponding PDSCH, the PDCCH can be used to indicate the FDRA for the corresponding PDSCH. For example, the UE can decode the PDCCH and determine the FDRA (e.g., PDSCH bandwidth) for the PDSCH before the UE is scheduled to receive the PDSCH (e.g., before the UE demodulates and decodes the PDSCH based on the decoded FDRA from the earlier received PDCCH).

[0113] In an example where the PDCCH and the scheduled PDSCH share the configured DMRS (e.g., such as respectively...), Figure 7A , Figure 7B (Examples of shared configured DMRS 705, 755) The UE can perform blind channel estimation using the same assumed DMRS as the configured shared DMRS 705 or 755 (e.g., the assumed DMRS is the shared configured DMRS 705, 755). For example, the UE can blindly search for the configured shared DMRS 705 as the PDCCH DMRS within the control area 702 of resource grid 700, and can attempt to perform channel estimation and PDCCH decoding based on the blind search of the configured shared DMRS 705. In the blind search and / or blind channel estimation, the UE assumes that the PDCCH DMRS exists on the control area 702 RE, and that the PDCCH DMRS will use a specific combination of time-frequency RE and DMRS sequences corresponding to the configured shared DMRS 705.

[0114] Based on blind channel estimation, the UE may or may not detect the configured shared DMRS 705. For example, the UE may detect the configured shared DMRS 705 as a PDCCH DMRS sent by the gNB to the UE. In some examples, if the gNB does not send the configured shared DMRS 705 (e.g., if the gNB decides not to serve the UE, or if the gNB decides to serve another UE instead, etc.), the UE may not detect the configured shared DMRS 705. For example, after determining blind channel estimation information (e.g., blind channel estimation successfully performed using fixed DMRS), the UE may use the determined blind channel estimation information to continue PDCCH demodulation and decoding (e.g., the UE may use the determined blind channel estimation information to receive PDCCH).

[0115] To perform demodulation (e.g., of modulated PDCCH and / or modulated PDSCH), the UE can use blind channel estimation information to determine the specific REs to be demodulated and the demodulation order of those REs. To perform decoding (e.g., of demodulated PDCCH and / or demodulated PDSCH), the UE can use blind channel estimation information to determine the specific RE or log-likelihood ratio (LLR) for each of one or more DCI hypotheses used for decoding. The UE can additionally determine the payload size of the DCI hypothesis based on the use of blind channel estimation information when performing decoding. In some cases, the UE may not know whether the blind channel estimation is valid. For example, the UE may not know whether the blind channel estimation information is valid until the UE is able to successfully decode the PDCCH or PDSCH. If the UE applies blind channel estimation to a specific fixed DMRS hypothesis and PDCCH or PDSCH decoding is unsuccessful, the UE can determine that the specific fixed DMRS hypothesis does not correspond to the current DMRS (or, if all fixed DMRS hypotheses have been tried for the blind channel estimation, the UE can determine that none of the fixed DMRS hypotheses are valid, and therefore the network entity did not send DMRS). Before the decoding step, the UE does not know whether the blind channel estimation information is valid because the DMRS may not have been transmitted or may not have been sent to the UE. The UE may also be unaware of how many DCIs have been transmitted and / or the aggregation level of the transmitted DCIs. In some examples, blind decoding is still required (e.g., the fixed DMRS assumption can be used to receive PDCCH / PDSCH based on performing blind channel estimation for demodulation and subsequently performing blind decoding on the demodulation results).

[0116] The systems and techniques described herein can be used to update PDSCH bandwidth without using the PDCCH that schedules PDSCH transmissions to indicate the FDRA and / or updated PDSCH bandwidth used for the scheduled PDSCH transmissions. For example, the systems and techniques can be used to provide one or more semi-static configurations of PDSCH bandwidth based on DL BWP information and / or RRC configuration information. In another illustrative example, the systems and techniques can be used to provide dynamic switching (e.g., updating) of PDSCH bandwidth and / or corresponding FDRA information. For example, the updated PDSCH bandwidth can be based on a DCI that includes and / or indicates FDRA information for the UE (e.g., updated FDRA information).

[0117] In some examples, systems and techniques can be used to transfer PDSCH bandwidth from Figure 7A BW0 updated to Figure 7B The narrower PDSCH bandwidth BW1. In another example, this system and technology can be used to increase the PDSCH bandwidth from... Figure 7B BW1 updated to Figure 7A The wider PDSCH bandwidth BW0.

[0118] As previously noted, in some cases, the PDSCH bandwidth can be changed and / or updated based on the path loss between the network entity and the UE (e.g., from...). Figure 7A The wider PDSCH bandwidth BW0 is changed and / or updated to Figure 7B The narrower PDSCH bandwidth PW1, and vice versa. For example, the updated PDSCH bandwidth can be determined based on the path loss between the network entity and the UE, where the UE receives PDCCH, configured shared DMRS, and PDSCH from the network entity. For example, UEs further away from the network entity (e.g., base station, gNB, etc.) can be updated to receive narrower PDSCH bandwidth PW1 from the network entity. Figure 7A The wider PDSCH bandwidth BW0 switch utilizes Figure 7B The narrower PDSCH bandwidth BW1 is used to receive PDSCH 756 corresponding to the configured shared DMRS 755 and / or PDCCH 752. In another example, UEs closer to network entities (e.g., base stations, gNBs, etc.) can be updated to receive PDSCH 756 from the network. Figure 7B The narrower PDSCH bandwidth BW1 is switched to utilize Figure 7A The wider PDSCH bandwidth BW0 is used to receive PDSCH 706 corresponding to the configured shared DMRS 705 and / or PDCCH 702.

[0119] In one exemplary example, the system and technology can be used to provide PDSCH bandwidth switching using one or more semi-static configurations that indicate PDSCH bandwidth update information.

[0120] For example, in some aspects, the updated PDSCH bandwidth can be determined based on downlink (DL) bandwidth portion (BWP) handover information. In some examples, the UE can receive DL BWP handover information from a network entity, where the DL BWP handover information indicates the updated PDSCH bandwidth and / or can be used by the UE to determine that updated PDSCH bandwidth. In some examples, where the DL BWP handover information is used to indicate the updated PDSCH bandwidth for the UE, the UE can receive a DL-granted DCI that does not include the Frequency Domain Resource Allocation (FDRA) field. The size of the DL-granted DCI that does not include the FDRA field can be smaller than the DL-granted DCI that does include the FDRA field. In some aspects, signaling the updated PDSCH bandwidth based on DL BWP handover information can reduce the DCI message overhead between the network entity (e.g., base station, gNB, etc.) and the UE.

[0121] In some examples, the system and technology can utilize BWP handover mechanisms to change and / or update PDSCH bandwidth. For example, the UE can receive a Radio Resource Control (RRC) message indicating one or more BWP bandwidth handover candidates. Each BWP bandwidth handover candidate can be an available BWP bandwidth and can be determined and / or configured, for example, by a network entity associated with the UE. In some aspects, the network entity can send an RRC message, and the UE can receive an RRC message that configures (e.g., pre-configures) one or more available BWP bandwidths as available or potential candidates for handover during PDSCH bandwidth updates. In some examples, the UE can select a specific BWP handover candidate from a plurality of configured BWP handover candidates. In another example, the UE can receive or send information and / or additional messages from a network entity indicating a specific BWP handover candidate from a plurality of configured BWP handover candidates.

[0122] In another example, a network entity may send an RRC message indicating an RRC reconfiguration for changing the BWP bandwidth, and the UE may receive the RRC message. For example, the network entity may send an RRC reconfiguration message and / or RRC reconfiguration information corresponding to the DL BWP used to determine the updated PDSCH bandwidth for the UE, and the UE may receive the RRC reconfiguration message and / or RRC reconfiguration information.

[0123] In another exemplary example of semi-static PDSCH bandwidth configuration, the network entity may send a new RRC configuration corresponding to the updated PDSCH bandwidth, and the UE may receive this new RRC configuration. The new RRC configuration may be included in an additional RRC message sent by the network entity and received by the UE. In some cases, the additional RRC message indicates a new RRC configuration for the PDSCH bandwidth. For example, the new RRC configuration may indicate a new or updated PDSCH FDRA. In some examples, the new or updated PDSCH FDRA indicated by the new RRC configuration may be within the DL BWP currently used, configured for, and / or allocated for the UE. In one exemplary example, the updated PDSCH FDRA may be located at the center of the DL BWP (e.g., the updated PDSCH FDRA uses the central portion of the existing DL BWP).

[0124] In some aspects, multiple candidate PDSCH bandwidths can be configured (e.g., pre-configured and / or pre-defined) for the UE. For example, multiple candidate PDSCH bandwidths can be configured for the UE based on one or more RRC configuration and / or RRC messages sent by a network entity and received by the UE. In some cases, the network entity can send a handover indication, and the UE can receive a handover indication configured to cause the UE to switch between corresponding configured candidate PDSCH bandwidths among multiple configured candidate PDSCH bandwidths. In some aspects, the handover indication can be a MAC-CE and / or MAC-CE-based message sent by the network entity and received by the UE. In some examples, the handover indication can be a DCI and / or DCI-based message sent by the network entity and received by the UE. In some aspects, configuring multiple candidate PDSCH bandwidths based on RRC configuration information and / or RRC messages can reduce DCI signaling overhead between the network entity and the UE because the DCI used for DL ​​approval does not need to include the FDRA field.

[0125] In another exemplary example, this system and technology can be used to provide PDSCH bandwidth switching using dynamic switching.

[0126] For example, a UE can receive (and a network entity can send) a DCI that includes and / or indicates FDRA information, which the UE can apply to receive a PDSCH after a configured time has elapsed. In some aspects, the DCI may be a DL-granted DCI and may include an FDRA field and / or may include FDRA information. The FDRA field and / or FDRA information may indicate an updated FDRA to be applied by the UE. The FDRA field and / or FDRA information may additionally indicate a time offset after which the updated FDRA can be applied. In some cases, the time offset may be pre-configured by the network entity for the UE (e.g., pre-configured, pre-defined, etc.). In some cases, the time offset can be measured from the start of the DL-granted DCI. For example, the time offset may be measured from the time the DL-granted DCI is received, from the end or expiration of the DL grant corresponding to the DL-granted DCI, etc. The time offset may be configured based on the number of time slots (e.g., three time slots, four time slots, etc.). The time offset may be configured based on an amount or interval of absolute time (e.g., three milliseconds, four milliseconds, etc.).

[0127] In some examples, when the UE PDSCH bandwidth is being updated, the DL-granted DCI may include an FDRA field (e.g., FDRA information indicating the updated FDRA corresponding to the updated PDSCH bandwidth). For example, if the UE is associated with PDSCH bandwidth that will not be updated (e.g., will remain the same for a certain amount of future time), the network entity may send one or more DL-granted DCI messages in which the DCI does not include the FDRA field, and the UE may receive such one or more DL-granted DCI messages. In some aspects, including the FDRA field in the DL-granted DCI received by the UE from the network entity may indicate the existence of updated PDSCH bandwidth that will be used for the UE and / or for one or more future scheduled PDSCHs that will be received by the UE. In some aspects, the absence of the FDRA field in the DL-granted DCI received by the UE from the network entity may indicate that the current PDSCH bandwidth and the corresponding FDRA have not been updated for the UE. A DL-granted DCI with an FDRA field may be longer (e.g., larger in size) than a DL-granted DCI without an FDRA field. Sending a DL-grant DCI with an FDRA field only when signaling an updated PDSCH bandwidth can reduce the DCI overhead of sending a (relatively short) DL-grant DCI without an FDRA field when the current PDSCH bandwidth does not need to be updated.

[0128] In an exemplary example, the DL grant DCI received by the UE may include an FDRA field and / or FDRA information indicating an updated FDRA. The updated FDRA corresponds to the updated PDSCH bandwidth used to receive scheduled or potentially allocated PDSCHs. In some aspects, the updated FDRA may be received in the first DL grant and not applied until a future time (e.g., after the first DL grant in which the updated FDRA is received). Applying the FDRA may include using the FDRA to decode incoming PDCCH transmissions and / or incoming PDSCH transmissions. For example, before applying the updated FDRA (e.g., before the FDRA start time of the updated FDRA), the UE may use the current FDRA instead of the updated FDRA to decode any incoming PDCCH and / or incoming PDSCH transmissions. After applying the updated FDRA (e.g., at or after the FDRA start time of the updated FDRA), the UE may use the updated FDRA to decode any incoming PDCCH and / or incoming PDSCH transmissions. Using FDRA (e.g., an updated FDRA) to decode incoming PDCCH and / or PDSCH transmissions can determine the specific RE (e.g., time-frequency resource) of the resource grid that will be used based on the use of FDRA.

[0129] In an exemplary example, the DL grant DCI received by the UE includes an FDRA field and / or indicates updated FDRA information. In some cases, the updated FDRA is not applied to the current grant (e.g., DL grant of a DCI with updated FDRA information) and is applied to PDSCH transmissions starting at some future time.

[0130] For example, a network entity can configure an updated FDRA start time to implement a configurable delay interval (e.g., a configurable time offset) between the DL granting the updated FDRA to be received by the UE and the later time when the updated FDRA is applied and used to receive incoming PDCCH and / or PDSCH transmissions. For example, the configurable delay prior to the updated FDRA application time corresponding to the UE implementing the updated PDSCH bandwidth can be based on the UE processing time. In some cases, the time offset between the DL granting the UE to receive the updated FDRA information and the start time of the UE applying the updated FDRA can correspond to a delay interval greater than or equal to the UE processing time interval.

[0131] In some cases, as noted above, updated FDRA information can be indicated or determined based on the FDRA field in the DL-approved DCI. In some examples, the FDRA field may be included in only a portion of several different DCI formats that can be sent by the network entity and / or received by the UE. For example, several DC formats used for DL ​​approval can be monitored by the UE. In an exemplary example, a long DCI format with updated FDRA information (e.g., with an FDRA field) can be transmitted relatively infrequently, such as when it is necessary to switch the PDSCH bandwidth used for the UE. When it is not necessary to change the PDSCH bandwidth used for the UE, a normal (e.g., short or shorter) DCI format can be used, and DCI overhead between the network entity and the UE can be reduced.

[0132] In some examples, the UE may receive (e.g., and the network entity may send to the UE) configuration information indicating a plurality of pre-determined, predefined, and / or pre-configured FDRA candidates for handover. Based on a finite set of FDRA handover candidates pre-configured at the UE, the network entity may subsequently send (e.g., and the UE may receive) a DL-approval DCI including an FDRA handover field. The FDRA handover field may indicate a selection from a plurality of predefined FDRA handover candidates. The FDRA handover field may be smaller than the full FDRA field, which may be used in examples where no FDRA handover candidates are pre-defined or pre-configured for the UE. In some aspects, configuring multiple FDRA handover candidates and utilizing a DL-approval DCI with an FDRA handover field can reduce DCI overhead compared to utilizing a DL-approval DCI with a full FDRA field. For example, a smaller or fewer bit width than the full FDRA field may be used to indicate the FDRA handover field.

[0133] In some examples, the reliability of FDRA updates and PDSCH bandwidth updates for the UE can be improved by determining the FDRA application time (e.g., the FDRA start time or the time when the UE applies the updated FDRA to receive incoming PDCCH or PDSCH transmissions) as a configured amount of time after receiving the ACK / NACK corresponding to the DL approval. For example, the configured amount of time can be indicated to the UE from the network entity, and the configured amount of time can be in time slots or in absolute time units.

[0134] Figure 8This is an illustration of an example of an updated Frequency Domain Resource Allocation (FDRA) start time based on an acknowledgment (ACK) and a time offset from the ACK. For example, the UE may receive a first DCI 812, which is a DL grant DCI indicating the updated FDRA. In the DL grant corresponding to the first DCI 812, the UE may receive a scheduled PDSCH 815 without using (e.g., without applying) the updated FDRA indicated by the first DCI 812.

[0135] The FDRA start time (e.g., FDRA application time) of the updated FDRA indicated by the first DCI 812 can be determined based on the offset relative to the time when the ACK / NACK corresponding to the DL approval is received. For example, the FDRA start time of the updated FDRA indicated by the first DCI 812 can be determined based on the offset 850 of the ACK 830 corresponding to the DL approval of the first DCI 812. In some aspects, the offset 850 is determined from the time when the network entity sending DCI 812 and / or PDSCH 815 receives the ACK 830 (e.g., the ACK 830 may be sent by the UE to the network entity). In some cases, the UE may receive the ACK 830 from the network entity, and the FDRA start time of the updated FDRA indicated by the first DCI 812 is calculated based on the time when the UE receives the ACK 830 from the network entity.

[0136] After time offset 850 has elapsed (e.g., expired, reached, etc.), the updated FDRA indicated by the first DCI 812 can be applied by the UE. For example, the FDRA application time can correspond to... Figure 8 The time offset 850 ends. The second DCI 872 and the second PDSCH 875 can be received after the FDRA application time. For example, after the time offset 850 relative to ACK 830 expires, the updated FDRA indicated by the first DCI 812 can be applied to update the PDSCH bandwidth associated with the UE receiving the second PDSCH 875.

[0137] In another exemplary example, multiple FDRA options (e.g., FDRA candidates or FDRA handover candidates) can be configured for the UE (e.g., based on configuration information received by the UE from a network entity). In some cases, when the FDRA used for the UE changes (e.g., the updated FDRA and / or the updated PDSCH bandwidth is implemented for the UE by a network entity), if the UE is unaware of the updated FDRA and / or the updated PDSCH bandwidth, the PDCCH decoding performed by the UE will fail or otherwise be incorrect.

[0138] In some cases, when the network entity and the UE have different understandings of the current FDRA and / or current PDSCH bandwidth used for transmissions from the network entity to the UE, the DMRS will be incorrect (e.g., incorrect location and incorrect DMRS scrambling), and the PDCCH will be incorrect (e.g., the PDCCH location is incorrect). In some cases, assuming an OFDM waveform, multiple FDRA candidates can be pre-configured and / or predefined for the UE to reduce the probability of mismatch between the UE and the network entity regarding the use of the current FDRA and / or current PDSCH bandwidth.

[0139] In an exemplary example, multiple FDRA candidates may each be associated with a corresponding DMRS tone position. To prevent the UE from using incorrect DMRS (e.g., incorrect DMRS positions and / or incorrect DMRS scrambling), the multiple FDRA candidates may be configured using DMRS tone positions that at least partially overlap with the corresponding DMRS tone positions of the remaining FDRA candidates among the multiple FDRA candidates. For example, at least a subset of the DMRS tone positions may overlap with a corresponding set of DMRS tone positions corresponding to each of the multiple FDRA candidates (e.g., shared and / or common to this corresponding set of DMRS tone positions). For example, the DMRS tone positions of a smaller FDRA candidate (e.g., a narrower bandwidth FDRA candidate) included within a larger FDRA candidate (e.g., within a wider bandwidth FDRA candidate) may be a subset of the DMRS tone positions of the larger FDRA candidate.

[0140] In some examples, multiple FDRA candidates may not be nested with other FDRA candidates among multiple FDRA candidates, but may at least partially overlap. In some cases, DMRS pitch positions may be aligned for at least the overlapping portion between any corresponding first FDRA candidate and second FDRA candidate among multiple FDRA candidates.

[0141] For DMRS scrambling, a fixed reference point can be used as the starting point. For example, DMRS scrambling for each corresponding FDRA candidate can start from the same fixed reference starting point. The fixed reference starting point used for DMRS scrambling can be FDRA-independent (e.g., DMRS scrambling can be performed without relying on a specific FDRA candidate that is utilized or selected from multiple FDRA candidates configured for the UE).

[0142] In some aspects, PDCCH rate matching can be performed based on configuring multiple FDRA candidates (e.g., multiple FDRA assumptions) utilizing one or more overlapping PDCCH locations. For example, a common PDCCH decoding candidate can be configured across different FDRA assumptions (e.g., under these different FDRA assumptions). In some aspects, even if the FDRA assumption used by the UE is incorrect (e.g., even if a particular FDRA candidate selected by the UE from multiple FDRA candidates is different from the FDRA used for transmission by the network entity), the common PDCCH decoding candidate can still be used (e.g., by the network entity) to transmit and (e.g., by the UE) to receive DCI. In some examples, the overlapping portion of multiple FDRA candidates (e.g., the frequency resources included in the corresponding frequency resource allocation for each FDRA candidate) can be used as the starting point for PDCCH rate matching performed by the UE.

[0143] In some cases, multiple FDRA candidates can be configured based on a common region identifying different FDRA candidates (e.g., a common region of different FDRA assumptions) and by configuring the corresponding DMRS for each FDRA candidate to be the same DMRS sequence over the common region under all FDRA assumptions. In some examples, at least a portion of the PDCCH decoding candidates of multiple FDRA candidates can be configured within the common region (e.g., located within the common region) under all FDRA assumptions.

[0144] Figure 9 This is an illustration of example 900, illustrating various FDRA granularities aligned with a Physical Resource Block Group (PRG) grid, according to some examples. In one illustrative example, the system and techniques can utilize channel estimation based on a Physical Resource Block Group (PRG). In examples where the FDRA granularity is aligned with a PRG grid, the system and techniques can utilize per-PRG channel estimation. In some aspects, the system and techniques can be used to configure a UE using one or more FDRA candidates, where each FDRA candidate is aligned with a PRG grid.

[0145] In some respects, aligning the FDRA with the PRG mesh can be associated with the UE only needing to perform channel estimation for the PRG in the current FDRA (e.g., the FDRA currently applied by the UE). In some cases, if the UE's FDRA assumptions are incorrect, channel estimation is not performed for PRGs in the underlying real FDRA (e.g., the FDRA of the network entity) but not in the UE's assumed FDRA. For PRGs in the UE's incorrect FDRA assumptions but not in the underlying real FDRA of the network entity, channel estimation will be incorrect and wasted.

[0146] For example, Figure 9Examples include a first FDRA 910 (“FDRA0”), a second FDRA 920 (“FDRA1”), and a third FDRA 930 (“FDRA2”). Each FDRA 910-930 is PRG grid aligned. By aligning each FDRA candidate (e.g., FDRA910-930) with the same PRG grid, the UE can reuse portions of its channel estimation information determined for incorrect FDRA assumptions, where the reusable portions correspond to the PRG common to the UE’s incorrect FDRA assumptions and the network entity’s true FDRAs.

[0147] For example, if the UE's incorrect FDRA assumption is FDRA0 910 and the network entity's true FDRA is FDRA1 920, the UE can perform channel estimation for each PRG 915 included within its incorrect FDRA assumption FDRA0 910. Based on aligning each FDRA candidate in the FDRA candidates with the same PRG grid, if the UE's FDRA assumption is FDRA0 (910) and the network entity's true FDRA is FDRA1 (920), then the channel estimation information of PRGs 915-1, ..., 915-3 of FDRA0 can be reused for the corresponding and aligned PRGs 925-3, ..., 925-15 of FDRA1.

[0148] If the FDRA assumption of the UE is FDRA0 (910) and the actual FDRA of the network entity is FDRA2 (930), then the channel estimation information of PRG915-4, ..., 915-13 can be reused for the corresponding and aligned PRG 935-1, ..., 935-10 of FDRA2.

[0149] If the FDRA assumption of the UE is FDRA1 (920) and the actual FDRA of the network entity is FDRA2 (930), then the channel estimation information of PRG 925-6, ..., 925-18 can be reused for the corresponding and aligned PRG 935-1, ..., 935-13 of FDRA2.

[0150] In some respects, if wideband channel estimation is used, the UE can implement multiple FDRA assumptions (e.g., multiple FDRA candidates from multiple configured FDRA candidates from network entities) to perform channel estimation. Using multiple FDRA assumptions for channel estimation can be associated with higher complexity when attempting multiple FDRA assumptions over the FDRA, but the UE can only perform multiple FDRA assumption channel estimation in certain cases. In another example, the UE can additionally or alternatively divide the FDRA into multiple segments along the FDRA boundary. Based on the segmentation, multiple smaller wideband channel estimates can be performed and / or utilized by the UE. The complexity of dividing the FDRA into multiple segments along the FDRA boundary can be lower than performing channel estimation using multiple FDRA assumptions, but higher than the complexity of a single FDRA channel estimate.

[0151] In some respects, the UE can utilize a fixed reference point for DMRS scrambling for each of multiple configured FDRA candidates from network entities. For example, instead of using a first RE for each corresponding FDRA 910, 920, 930, the UE can use the same RE aligned across each corresponding FDRA 910, 920, 930 and included in each corresponding FDRA as a fixed reference point for DMRS scrambling. For example, the UE can use RE 935-1 of FDRA2 (930), RE 925-6 of FDRA1 (920), and RE 915-4 of FDRA0 (910) as fixed reference points for DMRS scrambling.

[0152] Figure 10A This is a diagram illustrating example 1000a of the common PDCCH location between the first FDRA0 and the second FDRA1, based on some examples. Figure 10B This is an illustration of example 1000b illustrating the common PDCCH locations between first, second, and third FDRAs (e.g., FDRA0, FDRA1, and FDRA2, respectively) based on some examples. The common PDCCH locations can also be referred to as common PDCCH areas, and in cases where the UE's FDRA assumptions are incorrect, corresponding channel estimates across FDRA candidate common PDCCH areas can be reused. For example, in... Figure 10A In this context, the common PDCCH area is the same as the first FDRA candidate 1010 (e.g., FDRA0). The first FDRA 1010 corresponds to area 1025 of FDRA1, and if FDRA1 is incorrectly used by the UE as an FDRA assumption, only the upper PDCCH area 1023 and the lower PDCCH area 1027 are wasted and discarded, and the overlapping PDCCH area 1025 can be reused based on its overlap with FDRA0 1010.

[0153] In another example, across Figure 10B The common PDCCH areas of the three FDRAs correspond to PDCCH area 1055 of FDRA0 (e.g., where PDCCH area 1053 is wasted or discarded if FDRA0 is used as an incorrect UE FDRA assumption), PDCCH area 1065 of FDRA1 (e.g., where PDCCH areas 1063 and 1067 are wasted or discarded if FDRA1 is used as an incorrect UE FDRA assumption), and PDCCH area 1075 of FDRA2 (e.g., where PDCCH area 1077 is wasted or discarded if FDRA2 is used as an incorrect UE FDRA assumption).

[0154] Figure 11 Figure 1100 illustrates a default FDRA applied periodically between PDCCH monitoring intervals, according to some examples. In some aspects, the system and techniques can utilize a default FDRA configured for the UE, which is applied at some PDCCH monitoring intervals with the configured default FDRA periodically. For example, a default FDRA can be configured for the UE, and this default FDRA can be used to receive a first DCI 1102 and a corresponding first PDSCH 1105 at the default PDSCH bandwidth of the default FDRA. The default FDRA can be configured using a periodic pattern, wherein the default FDRA is used as the current FDRA for the UE, regardless of what the UE's current or active FDRA might otherwise be used for the periodic default FDRA interval.

[0155] For example, the default FDRA can be applied to Figure 11 The “periodic application interval” shown refers to each periodic application interval being time-varying. Figure 11 The "Periodicity of Default FDRA Configuration" shown is separated. Within each periodic application interval of the default FDRA, the UE can use the default FDRA and the default PDSCH bandwidth corresponding to the default FDRA to receive DCI, PDSCH, etc. from network entities.

[0156] For example, DCI 1102 and PDSCH 1105 are received in the first periodic application interval of the default FDRA, and DCI 1132 and PDSCH 1135 are received in the second periodic application interval of the default FDRA (e.g., DCI 1102 and DCI 1132 can be periodically separated by the configuration of the default FDRA). DCI 1102, 1132 and PDSCH 1105, 1135 can each be received using the default FDRA and the corresponding default PDSCH bandwidth, which is applied (e.g., used) by the UE for receiving incoming PDCCH and PDSCH transmissions during each of the first and second periodic application intervals of the default FDRA.

[0157] Between the first and second periodic application intervals of the default FDRA, the UE can use an FDRA assumption determined by the UE as the currently active FDRA assumption or FDRA candidate to receive any incoming PDCCH and / or PDSCH transmissions. For example, DCIs 1112 and 1122 are received outside the periodic application intervals of the default FDRA and can be received using an FDRA and corresponding PDSCH bandwidth different from the default FDRA and corresponding default PDSCH bandwidth. Similarly, PDSCHs 1115 and 1125 are received outside the periodic application intervals of the default FDRA and can be received using an FDRA and corresponding PDSCH bandwidth different from the default FDRA and corresponding default PDSCH bandwidth. In some cases, the UE can utilize multiple different FDRA candidates or assumptions (e.g., multiple different corresponding PDSCH bandwidths) during the time between the periodic application intervals of the default FDRA. For example, DCI 1112 and PDSCH 1115 can be received using FDRA assumptions and PDSCH bandwidths that are different from those used for receiving DCI 1122 and PDSCH 1125.

[0158] Figure 12This is an illustration of an example of timer-based backoff 1200 for a default FDRA, based on some examples. In an illustrative example, the UE can be configured using a default FDRA or default FDRA information (e.g., the same as or similar to the default FDRA described above) (e.g., based on configuration information received from a network entity). The UE can additionally be configured using a corresponding timer value for applying the default FDRA. For example, the UE can implement a timer that counts down from the configured timer value. Based on the timer expiring at the UE, the UE can apply the default FDRA configured by the network entity. For example, the UE can be configured using the default FDRA and a corresponding default FDRA timer value of 10 seconds. The UE can receive a first DCI 1202 associated with PDSCH 1205 at a first time, and can start a timer upon receiving the first DCI 1202 (e.g., receiving the first DCI 1202 using a current FDRA candidate or assumption different from the configured default FDRA). If the UE does not receive any valid control transmissions (e.g., PDCCH, DCI, etc.) from a network entity before the default FDRA timer expires, the UE will fall back to the default FDRA. For example, if no valid control transmission is received within at least 10 seconds after receiving DCI 1202 using the UE's current FDRA assumption, the UE will switch to applying the default FDRA until it successfully receives the next control transmission using the default FDRA. Figure 12 In the example, the configured default FDRA timer expires before the UE receives DCI 1212 and PDSCH 1215. The UE can use the configured default FDRA to receive DCI 1212 and PDSCH 1215, which is... Figure 12 The example shown corresponds to a PDSCH bandwidth narrower than a wider PDSCH bandwidth, which corresponds to the UE's FDRA assumption that was used earlier to receive DCI 1212 and PDSCH 1205. If DCI 1212 and / or PDSCH 1215 are detected by the UE as valid control using the currently active FDRA, the default FDRA timer can be reset. In some respects, using the default FDRA and default FDRA timer can allow the UE and network entity to establish a connection using the default FDRA in the event of an error and loss of synchronization between the network entity and the UE on the active FDRA. In some respects, the default FDRA and / or default FDRA timer information can be configured based on RRC messages sent by the network entity and received by the UE.

[0159] In some examples, a network entity may send (and a UE may receive) an empty DL grant indicating a modified or updated FDRA or FDRA information. For example, an empty DL grant may be implemented as a DCI message without scheduling PDSCH. In some examples, an empty DL grant DCI message includes an FDRA field or FDRA information indicating an updated FDRA and does not include additional information associated with scheduling PDSCH transmission. For example, an empty DL grant DCI message does not include data allocation. In some examples, an empty DL grant DCI message is not entirely empty but may include an FDRA field and / or other fields and / or information indicating an updated FDRA or updated FDRA information. An empty DL grant DCI message may additionally include one or more indications that the empty DL grant DCI does not schedule data or PDSCH transmission. In some aspects, an empty DL grant DCI message may reuse one or more DIC fields that would originally be used for scheduled data or PDSCH transmission to indicate an upcoming FDRA change for the UE (e.g., an updated FDRA indicating the corresponding updated PDSCH bandwidth to be scheduled for future use by the UE).

[0160] Figure 13 This is a flowchart illustrating an example of a process 1300 for wireless communication. Process 1300 may be performed by a network entity or network device (or apparatus) or a component of the network entity or device (e.g., chipset, codec, etc.). The network entity may be a UE (e.g., Figure 1 , Figure 2 and / or Figure 3 UE 104 Figure 4 The wireless device 407 or other UE). The network entity (e.g., UE) may be a mobile device (e.g., a mobile phone), a network-connected wearable device such as a watch, an extended reality (XR) device (e.g., a virtual reality (VR) device or an augmented reality (AR) device), a vehicle or a component or system of a vehicle, or other type of computing device configured to perform wireless communication. The operation of process 1300 may be implemented in one or more processors (e.g., Figure 2 Transmitter processor 264, receiver processor 258, TX MIMO processor 266, MIMO detector 256, Figure 4 processor 484, Figure 15 Software components executed and running on the processor 1510 or other processor. Furthermore, in process 1000, the network entity's transmission and reception of signals can be achieved, for example, through one or more antennas, one or more transceivers (e.g., wireless transceivers), and / or other communication components (e.g., [missing information]). Figure 2Transmit processor 264, receive processor 258, TX MIMO processor 266, MIMO detector 256, modulator / demodulator 254a to 254t and / or antenna 252a to 252t, Figure 4 Antenna 487 Figure 4 Wireless transceiver 478 Figure 15 This is achieved through a communication interface 1540 or other antennas, transceivers and / or components.

[0161] At box 1302, a network entity (or its components) may determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS).

[0162] For example, a scheduled PDSCH transmission can be the same as or similar to one or more of the following: Figure 7A PDSCH 706; Figure 7B PDSCH 756; Figure 8 PDSCH 815; Figure 8 PDSCH 875; Figure 11 PDSCH 1105, 1115, 1125 and / or 1135; Figure 12 PDSCH 1205 and / or PDSCH 1215; etc. In some examples, PDCCH transmissions may be the same as or similar to one or more of the following: Figure 7A PDCCH 702, Figure 7B PDCCH 752, etc. In some cases, the shared, configured DMRS can be the same as or similar to one or more of the following: Figure 7A DMRS705 Figure 7B DMRS 755, etc.

[0163] For example, a network entity (e.g., a UE) can determine the updated bandwidth based on downlink (DL) bandwidth portion (BWP) handover information. In some cases, DL BWP handover information can be received from a second network entity (e.g., a base station, gNB, etc.). In some cases, the DL BWP handover information can indicate a specific BWP bandwidth included in multiple BWP handover candidates. For example, multiple BWP bandwidth handover candidates can be configured based on radio resource control (RRC) messages indicating multiple BWP bandwidth handover candidates.

[0164] In some respects, scheduled PDSCH transmissions are based on the downlink control information (DCI) included in the PDCCH transmission. PDCCH transmissions and DCI can be received from a second network entity (e.g., a base station, gNB, etc.). In some examples, the DCI does not include the frequency domain resource allocation (FDRA) field for scheduled PDSCH transmissions. In some cases, the DCI may be the same as or similar to one or more of the following: Figure 8 DCI 812 or DCI 872; Figure 11 The DCI values ​​are 1102, 1112, 1122, and 1132. Figure 12 DCI 1202, 1212; etc.

[0165] In some cases, network entities are configured to receive RRC reconfiguration information corresponding to the DL BWP, where the updated bandwidth is determined based on the RRC reconfiguration information. For example, the DL BWP may be associated with a configured DMRS that includes PDSCH transmission, PDCCH transmission, and sharing.

[0166] In some examples, network entities can determine the updated bandwidth based on received RRC configuration information indicating the PDSCH bandwidth. For instance, a network entity can determine the updated bandwidth based on RRC configuration information. In some cases, the updated bandwidth is within the DL BWP.

[0167] In some examples, network entities can be configured to receive configuration information indicating multiple candidate PDSCH bandwidths. For example, configuration information can be received from a base station, gNB, etc. In some examples, network entities can receive information indicating a specific candidate PDSCH bandwidth among multiple candidate PDSCH bandwidths via a Media Access Control-Control Element (MAC-CE) or Downlink Control Information (DCI). In some cases, network entities are configured to determine the updated bandwidth based on the information indicating a specific candidate PDSCH bandwidth.

[0168] In some cases, a network entity may be configured to receive a first downlink control information (DCI) indicating frequency domain resource allocation (FDRA) information, where the first DCI corresponds to a first downlink (DL) grant that precedes a second DL grant corresponding to a scheduled PDSCH transmission. In order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the FDRA information. In some cases, the FDRA information may be the same as or similar to the following: Figure 9 One or more of FRDA0 910, FDRA1 920 and / or FDRA2 930; Figure 10AOne or more of FDRA0 and / or FDRA1; and / or Figure 10B One or more of FDRA0, FDRA1 and / or FDRA2.

[0169] In some examples, network entities are configured to apply FDRA information after a configured delay corresponding to the processing time of the network entity. For example, the configured delay could be... Figure 8 The time offset is the same as or similar to 850. In some examples, the network entity may receive a second DCI indicating a second PDSCH transmission scheduled after the scheduled PDSCH transmission, wherein the second PDSCH transmission reuses the updated bandwidth, and wherein the second DCI does not include the FDRA field.

[0170] In some examples, a network entity may send an acknowledgment (ACK) corresponding to one or more of the FDRA information or the first DCI. For example, an ACK may be associated with... Figure 8 The ACK 830 is the same as or similar to it, and the first DCI can be the same as... Figure 8 The second DCI is the same as or similar to DCI812. Figure 8 The DCI 872 is the same as or similar to the second PDSCH transmission, and the second PDSCH transmission can be the same as or similar to the PDSCH 875. The scheduled PDSCH transmission can be the same as... Figure 8 It is the same as or similar to PDSCH 815.

[0171] In some cases, network entities can determine the FDRA start time based on the time offset from the ACK. For example, the time offset from the ACK can be compared with... Figure 8 The time offset of ACK 830 is the same as or similar to 850. Network entities can apply FDRA information after the FDRA start time. In some cases, the time offset from ACK includes the configured number of time slots or the configured time value. In some examples, network entities are configured to use updated bandwidth to receive scheduled PDSCH transmissions after the FDRA start time.

[0172] In some examples, FDRA information indicates a set of allocated resource blocks (RBs) for a network entity, and the updated bandwidth corresponds to the bandwidth of the set of allocated RBs. In some cases, FDRA information includes an index value indicating the allocation of a specific FDRA among multiple FDRAs configured for the network entity. In some cases, the multiple configured FDRAs are associated with a subset of shared resource elements (REs). In some examples, each of the multiple configured FDRAs includes a subset of shared REs and is associated with a corresponding DMRS sequence for that subset of shared REs. In some examples, each of the multiple configured FDRAs is associated with a fixed reference point for DMRS scrambling. In some examples, the network entity is configured to perform PDCCH rate matching based on a starting point corresponding to a subset of the shared REs associated with the multiple configured FDRAs.

[0173] In some cases, a network entity can be configured to determine when a timer associated with the default frequency domain resource allocation (FDRA) used for the network entity's configuration has expired. For example, the timer may be associated with the one shown between DCI 1202 and DCI 1212. Figure 12 The timers configured are the same or similar. In some cases, network entities can determine the updated bandwidth based on the bandwidth of the configured default FDRA. For example, the updated bandwidth can be compared with and Figure 12 The updated bandwidth associated with one or more of DCI 1212 and / or PDSCH 1215 is the same as or similar. In some examples, the configured default FDRA can be with and Figure 12 The FDRA associated with one or more of DCI 1212 and / or PDSCH 1215 is the same or similar. In some examples, the network entity can determine the periodicity of the configuration associated with the configured default FDRA and apply the configured default FDRA based on the periodicity of the configuration.

[0174] At box 1304, a network entity (or its components) may receive scheduled PDSCH transmissions using updated bandwidth based on a shared, configured DMRS.

[0175] Figure 14 This is a flowchart illustrating an example of a process 1400 for wireless communication. Process 1400 may be performed by a network entity or network device (or apparatus) or a component of the network entity or device (e.g., chipset, codec, etc.). The network entity may be a base station (e.g., eNB, gNB, etc.) or a part of a base station (e.g., one or more of CU, DU, RU, near-RT RIC, and / or non-RT RIC, such as...). Figure 3The decomposed base station 300 may include CU 310, DU 330, RU 340, near-RT RIC 325 and / or non-RT RIC 315), server equipment, or other network entities. The operation of process 1100 can be implemented in one or more processors (e.g., Figure 2 The transmit processor 220, receive processor 238, TX MIMO processor 230, MIMO detector 236 and / or Figure 15 Software components that execute and run on the processor 1510 or other processor. Furthermore, in process 1400, the network entity's transmission and reception of signals may be achieved, for example, through one or more antennas, one or more transceivers (e.g., wireless transceivers) and / or other communication components (e.g., [missing information]). Figure 2 Transmit processor 220, receive processor 238, TX MIMO processor 230, MIMO detector 236, modulator / demodulators 232a to 232t and / or antennas 234a to 234t, Figure 15 This is achieved through a communication interface 1540 or other antennas, transceivers and / or components.

[0176] At box 1402, the network device (or its components) may determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS).

[0177] For example, a scheduled PDSCH transmission can be the same as or similar to one or more of the following: Figure 7A PDSCH 706; Figure 7B PDSCH 756; Figure 8 PDSCH 815; Figure 8 PDSCH 875; Figure 11 PDSCH 1105, 1115, 1125 and / or 1135; Figure 12 PDSCH 1205 and / or PDSCH 1215; etc. In some examples, PDCCH transmissions may be the same as or similar to one or more of the following: Figure 7A PDCCH 702, Figure 7B PDCCH 752, etc. In some cases, the shared, configured DMRS can be the same as or similar to one or more of the following: Figure 7A DMRS705 Figure 7B DMRS 755, etc.

[0178] In some respects, scheduled PDSCH transmissions are based on the downlink control information (DCI) included in the PDCCH transmission. PDCCH transmissions and DCI can be received from a second network entity (e.g., a base station, gNB, etc.). In some examples, the DCI does not include the frequency domain resource allocation (FDRA) field for scheduled PDSCH transmissions. In some cases, the DCI may be the same as or similar to one or more of the following: Figure 8 DCI 812 or DCI 872; Figure 11 The DCI values ​​are 1102, 1112, 1122, and 1132. Figure 12 DCI 1202, 1212; etc.

[0179] In some cases, a network device (or a component thereof) may be configured to transmit PDCCH transmissions. PDCCH transmissions may include a DCI indicating scheduling information for scheduled PDSCH transmissions. In some cases, the DCI may not include an FDRA field for scheduled PDSCH transmissions. In some examples, a network device (or a component thereof) may be configured to modulate scheduled PDSCH transmissions based on a shared, configured DMRS. In some examples, the network device is a base station or gNB, and scheduled PDSCH transmissions can be sent from the network device to a user equipment (UE) or other network entities associated with the network device.

[0180] At box 1404, the network device (or a component thereof) may send configuration information indicating updated bandwidth. For example, the network device (or a component thereof) may send a Radio Resource Control (RRC) message indicating multiple downlink (DL) bandwidth portion (BWP) handover candidates. In some examples, the network device (or a component thereof) may send information indicating a specific DL BWP handover candidate among multiple DL BWP handover candidates.

[0181] At box 1406, a network device (or a component thereof) may use the updated bandwidth to send a scheduled PDSCH.

[0182] In some cases, a computing device or apparatus configured to perform process 1300 and / or process 1400 may include various components such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other components configured to perform the steps of the processes described herein. In some examples, the computing device may include a display, one or more network interfaces configured to communicate and / or receive data, any combination thereof, and / or other components. One or more network interfaces may be configured to communicate and / or receive wired and / or wireless data, including data according to 3G, 4G, 5G, and / or other cellular standards, data according to the WiFi (802.11x) standard, and data according to Bluetooth. ™ Standard data, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0183] Components of a computing device may be implemented in circuitry. For example, components may include electronic circuitry or other electronic hardware, and / or may be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., a microprocessor, graphics processing unit (GPU), digital signal processor (DSP), central processing unit (CPU), and / or other suitable electronic circuitry), and / or may include computer software, firmware, or any combination thereof for performing the various operations described herein, and / or may be implemented using computer software, firmware, or any combination thereof for performing the various operations described herein.

[0184] Processes 1300 and 1400 are illustrated as logic flow diagrams, whose operations represent sequences of operations that can be implemented by hardware, computer instructions, or combinations thereof. In the context of computer instructions, each operation represents a computer-executable instruction stored on one or more computer-readable storage media that, when executed by one or more processors, performs the described operation. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a specific function or implement a specific data type. The order in which the operations are described is not intended to be construed as limiting, and any number of described operations can be combined in any order and / or in parallel to implement the process.

[0185] Additionally, processes 1300, 1400, and / or other processes described herein may be executed under the control of one or more computer systems configured with executable instructions, and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) that executes jointly on one or more processors, by hardware, or a combination thereof. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising multiple instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

[0186] Figure 15 This is a diagram illustrating an example of a system used to implement certain aspects of this technology. Specifically, Figure 15 An example of a computing system 1500 is illustrated. This computing system can be any computing device, such as constituting an internal computing system, a remote computing system, a camera, or any component thereof, wherein the components of the system communicate with each other using connection 1505. Connection 1505 can be a physical connection using a bus, or a direct connection to processor 1510, such as in a chipset architecture. Connection 1505 can also be a virtual connection, a networking connection, or a logical connection.

[0187] In some aspects, computing system 1500 is a distributed system in which the functions described herein can be distributed across a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more system components described represent a plurality of such components, each performing some or all of the functions described for which the component is used. In some aspects, the components can be physical or virtual devices.

[0188] Example system 1500 includes at least one processing unit (CPU or processor) 1510 and a connection 1505 that communicatively couples various system components, including system memories 1515 such as read-only memory (ROM) 1520 and random access memory (RAM) 1525, to processor 1510. Computing system 1500 may include a cache 1514 of high-speed memory that is directly connected to, closely proximates, or integrated into processor 1510.

[0189] Processor 1510 may include any general-purpose processor and hardware or software services, such as services 1532, 1534, and 1536 stored in storage device 1530, which are configured to control processor 1510 and dedicated processors in which software instructions are incorporated into the actual processor design. Processor 1510 may be a substantially completely independent computing system containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0190] To enable user interaction, the computing system 1500 includes an input device 1545 that can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, voice input, etc. The computing system 1500 may also include an output device 1535 that can be one or more of a plurality of output mechanisms. In some instances, a multi-mode system allows a user to provide multiple types of input / output to communicate with the computing system 1500.

[0191] The computing system 1500 may include a communication interface 1540, which typically controls and manages user input and system output. The communication interface may perform or facilitate the receiving and / or transmitting of wired or wireless communications using wired and / or wireless transceivers, including utilizing audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple... ™ Lightning ™ Ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal transmission, Bluetooth ™ Wireless signal transmission, Bluetooth ™ Low-power (BLE) wireless signal transmission, IBEACON ™Wireless signal transmission, including radio frequency identification (RFID) wireless signal transmission, near field communication (NFC) wireless signal transmission, dedicated short range communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, wireless local area network (WLAN) signal transmission, visible light communication (VLC), microwave access global interoperability (WiMAX), infrared (IR) wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, ad hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or some combination thereof. The communication interface 1540 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers for determining the location of the computing system 1500 based on one or more signals received from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the U.S. Global Positioning System (GPS), Russia's Global Navigation Satellite System (GLONASS), China's BeiDou Navigation Satellite System (BDS), and Europe's Galileo GNSS. There are no limitations on operation on any particular hardware configuration, and therefore the underlying features here can be easily replaced to obtain improved hardware or firmware configurations as they are developed.

[0192] Storage device 1530 may be a non-volatile and / or non-transitory and / or computer-readable storage device, and may be a hard disk or other type of computer-readable medium capable of storing data accessible by a computer, such as magnetic tape, flash memory cards, solid-state storage devices, digital versatile discs, cartridges, floppy disks, hard disks, magnetic tapes, magnetic stripes, any other magnetic storage media, flash memory, memristor memory, any other solid-state storage, CD-ROM, rewritable CD, digital video disc (DVD), Blu-ray Disc (BDD), holographic disc, another optical medium, secure digital storage (SD) cards, micro-secure digital storage (microSD) cards, Memory Stick. ®Cards, smart card chips, EMV chips, Subscriber Identity Module (SIM) cards, mini / micro / nano / micro SIM cards, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM, cache memory (e.g., layer 1 (L1) cache, layer 2 (L2) cache, layer 3 (L3) cache, layer 4 (L4) cache, layer 5 (L5) cache, other (L#) cache), resistive random access memory (RRAM / ReRAM), phase change memory (PCM), spin-transfer torque RAM (STT-RAM), another memory chip or cassette and / or combinations thereof.

[0193] Storage device 1530 may include software services, servers, services, etc., which enable the system to perform functions when the code defining such software is executed by processor 1510. In some aspects, hardware services performing specific functions may include software components stored in a computer-readable medium connected to necessary hardware components, such as processor 1510, connection 1505, output device 1535, etc., to perform functions. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data can be stored and which does not include carrier waves and / or transient electronic signals propagated wirelessly or via a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or magnetic tapes, optical storage media (such as compact discs (CDs) or digital versatile discs (DVDs)), flash memory, memory, or memory devices. Computer-readable media may store code and / or machine-executable instructions thereon, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or any combination of instructions, data structures, or program statements. Code segments may be coupled to other code segments or hardware circuitry by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means, including memory sharing, message passing, token passing, network transmission, etc.

[0194] Specific details have been provided in the foregoing description to offer a thorough understanding of the aspects and examples presented herein, but those skilled in the art will recognize that this application is not limited thereto. Therefore, although illustrative aspects of this application have been described in detail herein, it is to be understood that the various inventive concepts can be implemented and employed in a variety of other ways, and the appended claims are not intended to be construed as including such variations unless limited by prior art. The various features and aspects of the applications described above can be used individually or in combination. Furthermore, without departing from the broader scope of the specification, aspects can be utilized in any number of environments and applications beyond those described herein. Therefore, the specification and drawings should be considered illustrative rather than restrictive. For illustrative purposes, the methods are described in a particular order. It should be understood that, in alternative aspects, the methods may be performed in a different order than described.

[0195] For clarity, in some instances, this technology may be presented as comprising various functional blocks, which include devices, device components, steps, or routines embodied in a method, either in software or a combination of hardware and software. Additional components may be used in addition to those shown in the figures and / or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form to avoid obscuring these aspects in unnecessary detail. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the aspects.

[0196] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

[0197] The various aspects described above can be presented as processes or methods, depicted as flowcharts, diagrams, data flow diagrams, structure diagrams, or block diagrams. Although flowcharts can describe operations as sequential processes, many operations within an operation can be executed in parallel or concurrently. Furthermore, the order of operations can be rearranged. A process terminates when its operations are completed, but a process may have additional steps not included in the accompanying drawings. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, the termination of the process may correspond to the function returning to the calling function or the main function.

[0198] The processes and methods described in the examples above can be implemented using stored computer-executable instructions or computer-executable instructions otherwise available from a computer-readable medium. Such instructions may include, for example, instructions and data that configure, or otherwise configure, a general-purpose computer, special-purpose computer, or processing device to perform a function or group of functions. The portion may be accessible via a network of the computer resources used. The computer-executable instructions may be, for example, binary files, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that can be used to store the instructions, the information used, and / or information created during the methods according to the described examples include disks or optical discs, flash memory, USB devices with non-volatile memory, networked storage devices, etc.

[0199] In some respects, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly exclude media such as energy, carrier signals, electromagnetic waves, and the signals themselves.

[0200] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may, in some cases, be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0201] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and can take any form factor of various form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks can be stored in a computer-readable or machine-readable medium. A processor can perform the necessary tasks. Examples of form factors include: laptop computers, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, self-contained devices, etc. The functionality described herein can also be embodied in peripheral devices or interlocking cards. By further example, such functionality can also be implemented on circuit boards in different chips or different processes running on a single device.

[0202] Instructions, media for delivering such instructions, computing resources for executing them, and other structures for supporting such computing resources are example components for providing the functionality described in this disclosure.

[0203] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as a module or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0204] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein.

[0205] Those skilled in the art will appreciate that the less than ("<") and greater than (">") symbols or terms used herein can be represented by less than or equal to ("<") respectively. ") and greater than or equal to (" The symbol "" is used to replace the actual content without departing from the scope of this description.

[0206] When a component is described as being “configured” to perform certain operations, such configuration can be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., microprocessors or other suitable electronic circuits) to perform the operations, or any combination thereof.

[0207] The phrase “coupled to” or “communicatively coupled to” means that any component is physically connected directly or indirectly to another component, and / or that any component is in communication with another component directly or indirectly (e.g., connected to that other component via a wired or wireless connection and / or other suitable communication interface).

[0208] The claim language of “at least one of” and / or “one or more of” in the set indicates that one or more members of the set (in any combination) satisfy the claim. For example, the claim language of “at least one of A and B” or “at least one of A or B” means A, B, or A and B. In another example, the claim language of “at least one of A, B, and C” or “at least one of A, B, or C” means A, B, C, or A and B or A and C or B and C, A and B and C, or any repeating information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other ordering, repetition, or combination of A, B, and C. The language of “at least one of” and / or “one or more of” in the set does not limit the set to the items listed in the set. For example, the language of a claim that states “at least one of A and B” or “at least one of A or B” may mean A, B or A and B, and may additionally include items not listed in the set of A and B.

[0209] Claims using phrases such as "at least one processor, the at least one processor being configured to," or other languages ​​indicate that one or more processors (in any combination) are capable of performing associated operations. For example, a claim using the phrase "at least one processor, the at least one processor being configured to: X, Y, and Z" means that a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each assigned a specific subset of tasks involving operations X, Y, and Z, such that the multiple processors together perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, a claim using the phrase "at least one processor, the at least one processor being configured to: X, Y, and Z" may mean that any single processor can perform only a subset of operations X, Y, and Z.

[0210] When referring to one or more elements that perform functions (e.g., steps of a method), one element may perform all functions, or more than one element may jointly perform these functions. When more than one element jointly performs these functions, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform functions, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions.

[0211] When referring to an entity that performs or is configured to perform functions (e.g., steps of a method) (e.g., any entity or device described herein), the entity may be configured to cause one or more elements (individually or collectively) to perform those functions. One or more components of the entity may include at least one memory, at least one processor, at least one communication interface, another component configured to perform one or more of those functions, and / or any combination thereof. When referring to an entity that performs functions, the entity may be configured to cause one component to perform all functions, or to cause more than one component to perform those functions collectively. When the entity is configured to cause more than one component to perform those functions collectively, each function does not need to be performed by every single component (e.g., different functions may be performed by different components), and / or each function does not need to be performed by only one component as a whole (e.g., different components may perform different sub-functions of a function).

[0212] The exemplary aspects of this disclosure include: Aspect 1. A network entity for wireless communication, the network entity comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the network entity is configured to: determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and receive the scheduled PDSCH transmission using the updated bandwidth based on the shared configured DMRS.

[0213] Aspect 2. The network entity according to Aspect 1, wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on downlink (DL) bandwidth portion (BWP) switching information.

[0214] Aspect 3. The network entity according to Aspect 2, wherein: the scheduled PDSCH transmission is scheduled based on the downlink control information (DCI) included in the PDCCH transmission; and the DCI does not include a frequency domain resource allocation (FDRA) field for the scheduled PDSCH transmission.

[0215] Aspect 4. The network entity according to any one of Aspects 2 to 3, wherein the DL BWP switching information indicates a specific BWP bandwidth included in a plurality of BWP bandwidth switching candidates.

[0216] Aspect 5. The network entity according to Aspect 4, wherein the plurality of BWP bandwidth switching candidates are configured based on Radio Resource Control (RRC) messages indicating the plurality of BWP bandwidth switching candidates.

[0217] Aspect 6. A network entity according to any one of Aspects 1 to 5, wherein the network entity is configured to: receive Radio Resource Control (RRC) reconfiguration information corresponding to a downlink (DL) bandwidth portion (BWP), wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the RRC reconfiguration information.

[0218] Aspect 7. The network entity according to Aspect 6, wherein the DL BWP is associated with the PDSCH transmission, the PDCCH transmission and the shared configured DMRS.

[0219] Aspect 8. A network entity according to any one of Aspects 1 to 7, wherein the network entity is configured to: receive Radio Resource Control (RRC) configuration information indicating PDSCH bandwidth, wherein in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the RRC configuration information.

[0220] Aspect 9. The network entity according to aspect 8, wherein the updated bandwidth is within the downlink (DL) bandwidth portion (BWP).

[0221] Aspect 10. A network entity according to any one of Aspects 1 to 9, wherein the network entity is configured to: receive configuration information indicating a plurality of candidate PDSCH bandwidths; and receive information indicating a specific candidate PDSCH bandwidth among the plurality of candidate PDSCH bandwidths via a Media Access Control-Control Element (MAC-CE) or Downlink Control Information (DCI), wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the information indicating the specific candidate PDSCH bandwidth.

[0222] Aspect 11. A network entity according to any one of Aspects 1 to 10, wherein the network entity is configured to: receive first downlink control information (DCI) indicating frequency domain resource allocation (FDRA) information, wherein the first DCI corresponds to a first downlink (DL) grant, the first downlink (DL) grant being earlier than a second DL grant corresponding to the scheduled PDSCH transmission, wherein in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the FDRA information.

[0223] Aspect 12. The network entity according to aspect 11, wherein the network entity is configured to apply the FDRA information after a configured delay corresponding to the processing time of the network entity.

[0224] Aspect 13. A network entity according to any one of Aspects 11 to 12, wherein the network entity is configured to: receive a second DCI indicating a second PDSCH transmission scheduled after the scheduled PDSCH transmission, wherein the second PDSCH transmission reuses the updated bandwidth, and wherein the second DCI does not include an FDRA field.

[0225] Aspect 14. A network entity according to any one of Aspects 11 to 13, wherein the network entity is configured to: send an acknowledgment (ACK) corresponding to one or more of the FDRA information or the first DCI; determine an FDRA start time based on a time offset from the ACK; and apply the FDRA information after the FDRA start time.

[0226] Aspect 15. The network entity according to aspect 14, wherein the time offset from the ACK includes a configured number of time slots or a configured time value.

[0227] Aspect 16. The network entity according to any one of Aspects 14 to 15, wherein, in order to use the updated bandwidth to receive the scheduled PDSCH transmission, the network entity is configured to use the updated bandwidth to receive the scheduled PDSCH transmission after the FDRA start time.

[0228] Aspect 17. A network entity according to any one of Aspects 11 to 16, wherein the FDRA information indicates a set of allocated resource blocks (RBs) for the network entity, and wherein the updated bandwidth corresponds to the bandwidth of the set of allocated RBs.

[0229] Aspect 18. A network entity according to any one of Aspects 11 to 17, wherein the FDRA information includes an index value indicating the allocation of a particular FDRA among a plurality of FDRAs for the configuration of the network entity.

[0230] Aspect 19. The network entity according to aspect 18, wherein: the configured plurality of FDRAs are associated with a subset of shared resource elements (REs); and each of the configured plurality of FDRAs includes said subset of shared REs and is associated with a corresponding DMRS sequence of said subset of shared REs.

[0231] Aspect 20. The network entity according to any one of Aspects 18 to 19, wherein each of the plurality of FDRAs in the configuration is associated with a fixed reference point for DMRS scrambling.

[0232] Aspect 21. A network entity according to any one of Aspects 18 to 20, wherein the network entity is configured to perform PDCCH rate matching based on a starting point corresponding to a subset of shared REs associated with a plurality of configured FDRAs.

[0233] Aspect 22. A network entity according to any one of Aspects 1 to 21, wherein the network entity is configured to: determine that a timer associated with a default frequency domain resource allocation (FDRA) for the configuration of the network entity has expired; and determine an updated bandwidth based on the bandwidth of the default FDRA of the configuration.

[0234] Aspect 23. The network entity according to aspect 22, wherein the network entity is configured to: determine the periodicity of a configuration associated with a default FDRA of the configuration; and apply the default FDRA of the configuration based on the periodicity of the configuration.

[0235] Aspect 24. The network entity according to any one of Aspects 1 to 23, wherein the network entity is a user equipment (UE).

[0236] Aspect 25. A method for wireless communication by a network entity, the method comprising: determining an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); and receiving the scheduled PDSCH transmission using the updated bandwidth based on the shared configured DMRS.

[0237] Aspect 26. A network entity for wireless communication, the network entity comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the network entity is configured to: determine an updated bandwidth corresponding to a scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with a physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS); transmit configuration information indicating the updated bandwidth; and transmit the scheduled PDSCH transmission using the updated bandwidth.

[0238] Aspect 27. The network entity according to aspect 26, wherein the network entity is configured to: transmit the PDCCH transmission, wherein the PDCCH includes downlink control information (DCI) indicating scheduling information for the scheduled PDSCH transmission, and wherein the DCI does not include a frequency domain resource allocation (FDRA) field for the scheduled PDSCH transmission.

[0239] Aspect 28. A network entity according to any one of Aspects 26 to 27, wherein, in order to send configuration information indicating the updated bandwidth, the network entity is configured to: send a radio resource control (RRC) message indicating a plurality of downlink (DL) bandwidth portion (BWP) handover candidates; and send information indicating a specific DL BWP handover candidate among the plurality of DL BWP handover candidates.

[0240] Aspect 29. The network entity according to any one of Aspects 26 to 28, wherein the network entity is configured to modulate the scheduled PDSCH transmission based on the shared configured DMRS.

[0241] Aspect 30. The network entity according to any one of Aspects 26 to 29, wherein the network entity is a base station or gNB.

[0242] Aspect 31. A method for wireless communication, the method comprising performing operations according to any one of aspects 1 to 24.

[0243] Aspect 32. A method for wireless communication, the method comprising performing the operations described in aspect 25.

[0244] Aspect 33. A method for wireless communication, the method comprising performing operations according to any one of aspects 26 to 30.

[0245] Aspect 34. A non-transitory computer-readable storage medium comprising instructions stored thereon, the instructions causing the at least one processor, when executed by at least one processor, to perform any one of aspects 1 to 24.

[0246] Aspect 35. A non-transitory computer-readable storage medium comprising instructions stored thereon, the instructions causing the at least one processor, when executed by at least one processor, to perform the operations described in aspect 25.

[0247] Aspect 36. A non-transitory computer-readable storage medium comprising instructions stored thereon, the instructions causing the at least one processor, when executed by at least one processor, to perform any one of aspects 26 to 30.

[0248] Aspect 37. An apparatus for wireless communication, the apparatus comprising one or more components for performing operations according to any one of aspects 1 to 24.

[0249] Aspect 38. An apparatus for wireless communication, the apparatus comprising one or more components for performing the operations described in aspect 25.

[0250] Aspect 39. An apparatus for wireless communication, the apparatus comprising one or more components for performing operations according to any one of aspects 26 to 30.

Claims

1. A network entity for wireless communication, the network entity comprising: At least one memory; and At least one processor, said at least one processor being coupled to said at least one memory, wherein said network entity is configured to: Determine the updated bandwidth corresponding to the scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with the physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS). as well as Based on the shared configured DMRS, the updated bandwidth is used to receive the scheduled PDSCH transmissions.

2. The network entity of claim 1, wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on downlink (DL) bandwidth portion (BWP) switching information.

3. The network entity according to claim 2, wherein: The scheduled PDSCH transmission is scheduled based on the downlink control information (DCI) included in the PDCCH transmission; and The DCI does not include the Frequency Domain Resource Allocation (FDRA) field used for the scheduled PDSCH transmission.

4. The network entity according to claim 2, wherein the DL BWP switching information indicates a specific BWP bandwidth included in a plurality of BWP bandwidth switching candidates.

5. The network entity of claim 4, wherein the plurality of BWP bandwidth switching candidates are configured based on radio resource control (RRC) messages indicating the plurality of BWP bandwidth switching candidates.

6. The network entity according to claim 1, wherein the network entity is configured as follows: Receive Radio Resource Control (RRC) reconfiguration information corresponding to the downlink (DL) bandwidth portion (BWP), wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the RRC reconfiguration information.

7. The network entity of claim 6, wherein the DL BWP is associated with the PDSCH transmission, the PDCCH transmission and the shared configured DMRS.

8. The network entity according to claim 1, wherein the network entity is configured as follows: Receive Radio Resource Control (RRC) configuration information indicating PDSCH bandwidth, wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the RRC configuration information.

9. The network entity of claim 8, wherein the updated bandwidth is within the downlink (DL) bandwidth portion (BWP).

10. The network entity according to claim 1, wherein the network entity is configured as follows: Receive configuration information indicating the bandwidth of multiple candidate PDSCHs; and The network entity receives information indicating a specific candidate PDSCH bandwidth among the plurality of candidate PDSCH bandwidths via a Media Access Control-Control Element (MAC-CE) or Downlink Control Information (DCI), wherein, in order to determine the updated bandwidth, the network entity is configured to determine the updated bandwidth based on the information indicating the specific candidate PDSCH bandwidth.

11. The network entity according to claim 1, wherein the network entity is configured as follows: The network entity receives a first downlink control information (DCI) indicating frequency domain resource allocation (FDRA) information, wherein the first DCI corresponds to a first downlink (DL) grant, the first downlink (DL) grant being earlier than a second DL grant corresponding to the scheduled PDSCH transmission, wherein the network entity is configured to determine the updated bandwidth based on the FDRA information in order to determine the updated bandwidth.

12. The network entity of claim 11, wherein the network entity is configured to apply the FDRA information after a configured delay corresponding to the processing time of the network entity.

13. The network entity of claim 11, wherein the network entity is configured as follows: Receive a second DCI indicating a second PDSCH transmission scheduled after the scheduled PDSCH transmission, wherein the second PDSCH transmission reuses the updated bandwidth, and wherein the second DCI does not include the FDRA field.

14. The network entity of claim 11, wherein the network entity is configured to: Send an acknowledgment (ACK) corresponding to one or more of the FDRA information or the first DCI. The FDRA start time is determined based on the time offset from the ACK; and The FDRA information is applied after the FDRA start time.

15. The network entity of claim 14, wherein the time offset from the ACK includes a configured number of time slots or a configured time value.

16. The network entity of claim 14, wherein, in order to use the updated bandwidth to receive the scheduled PDSCH transmission, the network entity is configured to use the updated bandwidth to receive the scheduled PDSCH transmission after the FDRA start time.

17. The network entity of claim 11, wherein the FDRA information indicates a set of allocated resource blocks (RBs) for the network entity, and wherein the updated bandwidth corresponds to the bandwidth of the set of allocated RBs.

18. The network entity of claim 11, wherein the FDRA information includes an index value indicating the allocation of a particular FDRA among a plurality of FDRAs for the configuration of the network entity.

19. The network entity according to claim 18, wherein: The configured multiple FDRAs are associated with a subset of shared resource elements (REs); and Each of the multiple FDRAs in the configuration includes the subset of shared REs and is associated with a corresponding DMRS sequence of the subset of shared REs.

20. The network entity of claim 18, wherein each of the plurality of FDRAs configured is associated with a fixed reference point for DMRS scrambling.

21. The network entity of claim 18, wherein the network entity is configured to: PDCCH rate matching is performed based on the starting point corresponding to the subset of shared REs associated with the multiple FDRAs in the configuration.

22. The network entity according to claim 1, wherein the network entity is configured as follows: Determine that a timer associated with the default frequency domain resource allocation (FDRA) configured for the network entity has expired; and determine the updated bandwidth based on the bandwidth of the default FDRA configured.

23. The network entity of claim 22, wherein the network entity is configured to: Determine the periodicity of the configuration associated with the default FDRA of the configuration; and The default FDRA of the configuration is applied based on the periodicity of the configuration.

24. The network entity of claim 1, wherein the network entity is a user equipment (UE).

25. A method for wireless communication by a network entity, the method comprising: Determine the updated bandwidth corresponding to the scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with the physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS). as well as Based on the shared configured DMRS, the updated bandwidth is used to receive the scheduled PDSCH transmissions.

26. A network entity for wireless communication, the network entity comprising: At least one memory; and At least one processor, said at least one processor being coupled to said at least one memory, wherein said network entity is configured to: Determine the updated bandwidth corresponding to the scheduled physical downlink shared channel (PDSCH) transmission, wherein the scheduled PDSCH transmission is associated with the physical downlink control channel (PDCCH) transmission, and wherein the PDSCH transmission and the PDCCH transmission are associated with a shared configured demodulation reference signal (DMRS). Send configuration information indicating the updated bandwidth; and The updated bandwidth is used to send the scheduled PDSCH transmission.

27. The network entity of claim 26, wherein the network entity is configured to: The PDCCH is transmitted, wherein the PDCCH includes downlink control information (DCI) indicating the scheduling information for the scheduled PDSCH transmission, and wherein the DCI does not include a frequency domain resource allocation (FDRA) field for the scheduled PDSCH transmission.

28. The network entity of claim 26, wherein, in order to send configuration information indicating the updated bandwidth, the network entity is configured to: Sending Radio Resource Control (RRC) messages indicating multiple downlink (DL) bandwidth portion (BWP) handover candidates; and Send information indicating a specific DL BWP handover candidate among the plurality of DL BWP handover candidates.

29. The network entity of claim 26, wherein the network entity is configured to modulate the scheduled PDSCH transmission based on the shared configured DMRS.

30. The network entity according to claim 26, wherein the network entity is a base station or gNB.

Images