Uplink parameter prediction and indication in wireless communications
By using downlink control information and machine learning models to predict uplink parameters in 5G wireless communication system, the problem of difficulty in predicting uplink parameters is solved, channel quality and data transmission efficiency are improved, and power consumption of user equipment is reduced .
Patent Information
- Application Number
- CN202280095074.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-03
AI Technical Summary
In 5G wireless communication systems, the prior art is difficult to effectively predict and indicate uplink parameters, resulting in inadequate channel quality and data transmission efficiency.
The uplink pre-coding scheme is dynamically determined between the user equipment and the network entity by receiving and sending downlink control information, and predicting UL parameters using machine learning models and analysis techniques, reducing the power and overhead of beam scanning.
It improves the channel quality and data transmission efficiency of the uplink, reduces the power consumption and processing overhead of the user equipment, and enhances the mobility and flexibility of the communication system.
Smart Images

Figure CN119072882A_ABST
Abstract
Description
Technical Field
[0001] The techniques discussed below relate generally to wireless communication systems, and more particularly, to uplink parameter prediction and indication in wireless communications. Background Art
[0002] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcasting. An example of a telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. In a 5G network, a user equipment may use beam scanning (sounding reference signal (SRS) beam scanning) to send SRS. A network entity may determine channel quality based on the SRS beam scanning and indicate to the user equipment an uplink precoding scheme for future UL transmissions. An exemplary precoding scheme may include one or more of the following: an SRS resource indicator (SRI), a transmit precoder matrix indicator (TPMI), a transmit rank indicator (TRI), and a modulation and coding scheme (MCS). Summary of the invention
[0003] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to define the scope of any or all aspects of the present disclosure. The sole purpose of this overview is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.
[0004] Various aspects of the present disclosure provide various techniques for uplink precoding scheme prediction and indication in wireless communications. In some aspects, a user equipment may dynamically identify a predicted uplink precoding scheme for a future uplink transmission, for example based at least in part on downlink control information received from a network entity and downlink measurements prior to the future uplink transmission.
[0005] One aspect of the present disclosure provides a method for wireless communication at a user equipment (UE). The method includes: receiving first downlink control information (DCI) from a network entity. The method also includes: sending a first uplink (UL) transmission scheduled by the first DCI. The method also includes: sending a second UL transmission after the first UL transmission, the precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
[0006] Another aspect of the present disclosure provides a user equipment (UE) for wireless communication. The UE includes a transceiver for wireless communication, a memory, and a processor, the processor being coupled to the transceiver and the memory. The processor and the memory are configured to receive first downlink control information (DCI) via the transceiver. The processor and the memory are further configured to send a first uplink (UL) transmission scheduled by the first DCI via the transceiver. The processor and the memory are further configured to send a second UL transmission following the first UL transmission via the transceiver, the precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
[0007] One aspect of the present disclosure provides a method for wireless communication at a network entity. The method includes: sending a first downlink control information (DCI). The method also includes: receiving a first uplink (UL) transmission scheduled by the first DCI. The method also includes: receiving a second UL transmission after the first UL transmission, the precoding scheme of the second UL transmission being determined at a user equipment (UE) at least in part based on the first DCI and a downlink measurement before the second UL transmission.
[0008] Another aspect of the present disclosure provides a network entity for a communication network. The network entity includes a memory and a processor coupled to the memory. The processor and the memory are configured to: send a first downlink control information (DCI). The processor and the memory are further configured to: receive a first uplink (UL) transmission scheduled by the first DCI. The processor and the memory are configured to: receive a second UL transmission after the first UL transmission, and the pre-coding scheme of the second UL transmission is determined at a user equipment (UE) at least in part based on the first DCI and a downlink measurement before the second UL transmission.
[0009] After reading the following specific embodiments, these and other aspects of the present invention will be more fully understood. After reading the following description of specific exemplary implementations in conjunction with the accompanying drawings, other aspects, features and specific implementations will become apparent to those of ordinary skill in the art. Although each feature may be discussed with respect to certain examples and drawings below, all specific implementations may include one or more advantageous features in the advantageous features discussed herein. In other words, although one or more specific implementations may be discussed as having certain advantageous features, one or more features in such features may also be used according to the various examples discussed herein. In a similar manner, although each example may be discussed as a device, system or method specific implementation below, it should be understood that such examples can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects.
[0011] Figure 2 is an illustration of an example of a radio access network (RAN) in accordance with some aspects.
[0012] Figure 3 is a diagram illustrating an example of a RAN including distributed entities in accordance with some aspects.
[0013] Figure 4 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.
[0014] Figure 5 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communication.
[0015] Figure 6 is a diagram illustrating communications between a network entity and a user equipment (UE) using beamformed signals in accordance with some aspects.
[0016] Figure 7 is a signaling diagram illustrating exemplary signaling between a network entity and a UE for providing channel state information feedback within a wireless network.
[0017] Figure 8 is a diagram illustrating a process for predicting uplink (UL) parameters according to some aspects.
[0018] Fig. 9 is a flow chart illustrating a process for determining UE predicted UL parameters according to some aspects.
[0019] Fig.10 is a diagram conceptually illustrating example uplink grant downlink control information in accordance with some aspects.
[0020] Fig.11 is a diagram illustrating an example UL transmission using predicted UL parameters in accordance with some aspects.
[0021] Fig.12 is a diagram illustrating a process for predicting UL parameters using a machine learning model according to some aspects.
[0022] Fig.13 is a diagram illustrating a process for predicting UL parameters using analytical techniques in accordance with some aspects.
[0023] Fig.14is a flow chart illustrating a process for scheduling UL transmissions using downlink control information that does not include associated UL parameters in accordance with some aspects.
[0024] Fig.15 is a diagram illustrating an example timeline for UL parameter prediction in accordance with some aspects.
[0025] Fig.16 is a block diagram illustrating an example of a hardware implementation of a network entity according to some aspects.
[0026] Fig.17 is a flow chart illustrating an example process for UL precoding scheme prediction at a network entity in accordance with some aspects.
[0027] Fig.18 is a block diagram illustrating an example of a hardware implementation of a UE according to some aspects.
[0028] Fig.19 is a flow chart illustrating an example process for UL precoding scheme prediction at a UE in accordance with some aspects. DETAILED DESCRIPTION
[0029] The specific embodiments set forth below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.
[0030] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many other arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementations and / or uses may occur via integrated chips and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically relate to use cases or applications, the innovation described may have various types of applicability. Specific implementations may have a range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovation. In some practical settings, the device in combination with the described aspects and features may also necessarily include additional components and features for the specific implementation and practice of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components include antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and UEs), end-user devices, etc.
[0031] Various aspects of the present disclosure provide various techniques for uplink precoding scheme prediction and indication in wireless communications. In some aspects, a user equipment may dynamically identify a predicted uplink precoding scheme for a future uplink transmission, for example based at least in part on downlink control information received from a network entity and downlink measurements prior to the future uplink transmission.
[0032] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100, by way of illustrative example and not limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.
[0033] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR, commonly referred to as Long Term Evolution (LTE), and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards. 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.
[0034] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a next generation node B (gNB), a transmit receive point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands.
[0035] RAN 104 is further illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.
[0036] In this document, a "mobile" device does not necessarily need to have the ability to move, and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components of a size, shape, and arrangement that facilitate communication; such components may include antennas, antenna arrays, radio frequency (RF) chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablets, personal digital assistants (PDAs), and a wide range of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)). A mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc.). The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may additionally be a smart energy device, security device, solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise equipment; logistics controller; agricultural equipment, etc. Further, the mobile device may provide connected medicine or telemedicine support, such as remote health care. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or priority access relative to other types of information, for example, in terms of priority access for transmission of critical service data and / or associated QoS for transmission of critical service data.
[0037] Wireless communication between RAN 104 and UE 106 is described as utilizing an air interface. Transmissions over the air interface from a network entity (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to point-to-multipoint transmissions originating at a network entity (further described below; e.g., base station 108). Another way to describe this scheme may be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" may refer to point-to-point transmissions originating at a scheduled entity (further described below; e.g., UE 106).
[0038] In some examples, access to the air interface may be scheduled, wherein a network entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a network entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106 (which may be a scheduled entity) may utilize resources allocated by the network entity 108.
[0039] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a network entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs).
[0040] like Figure 1 As illustrated, a network entity 108 (e.g., a base station) may broadcast downlink traffic 112 to one or more scheduled entities 106. In a broad sense, a network entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and (in some examples) uplink traffic 116 from one or more scheduled entities 106 to the network entity 108. In another aspect, a scheduled entity 106 is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the network entity 108. The scheduled entity 106 may further send uplink control information 118 to the network entity 108, including, but not limited to, scheduling requests or feedback information or other control information.
[0041] In addition, uplink and / or downlink control information 114 and / or 118 and / or traffic information 112 and / or 116 may be sent on a waveform that may be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.
[0042] In general, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.
[0043] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.
[0044] Figure 2 is a diagram of an example of a RAN 200 according to some aspects. In some examples, the RAN 200 can be used with the RAN 200 described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.
[0045] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), because base station 218 supports a cell with a relatively small size. Cell size setting may be performed according to system design and component constraints.
[0046] It should be understood that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The network entity 108 is the same as that illustrated in FIG.
[0047] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a quadcopter or a drone. UAV 220 may be configured to act as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as a quadcopter 220.
[0048] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the above-described and Figure 1 The UE / scheduled entity 106 illustrated in FIG.
[0049] In some examples, UAV 220 (e.g., a quadcopter) can be configured to act as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210.
[0050] In another aspect of the RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in, for example, a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may each act as a scheduling entity (e.g., network entity 108) or a sending sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without routing the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.
[0051] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of base station 212 may operate as relay UEs to extend the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.
[0052] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are typically managed by an access and mobility management function (AMF, not shown). Figure 1 The function may include a security context management function (SCMF) and a security anchor function (SEAF) for performing authentication. The SCMF may manage the security context for both the control plane functionality and the user plane functionality in whole or in part.
[0053] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a network entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 (illustrated as a vehicle, although any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .
[0054] In a network configured for UL-based mobility, the network may select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of these cells may measure the strength of the pilot signal, and the RAN (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within a core network) may determine a serving cell for UE 224. As UE 224 moves through RAN 200, the network may continue to monitor the uplink pilot signals sent by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 200 may handover UE 224 from the serving cell to a neighboring cell with or without notifying UE 224.
[0055] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.
[0056] The air interface in the RAN 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.
[0057] In addition, the air interface in the RAN 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA) or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.
[0058] Figure 3 is a diagram illustrating an example of a RAN 300 including distributed entities according to some aspects. The RAN 300 may be connected to Figure 2 The illustrated radio access network 200 may be similar in that the RAN 300 may be divided into a number of cells (e.g., cell 322), each of which may be served by a corresponding network entity (e.g., a control unit, a distributed unit, and a radio unit). The network entity may constitute an access point, a TRP, a base station (BS), an eNB, a gNB, or other node that utilizes a wireless spectrum (e.g., a radio frequency (RF) spectrum) and / or other communication links to support access by one or more UEs located within a cell. In some examples, Figure 3 Some or all of the network entities may be implemented within an integrated access backhaul (IAB) network. Figure 3 Some or all of the nodes may be implemented according to an Open Radio Access Network (O-RAN) architecture.
[0059] exist Figure 3In the example of FIG. 1 , a control unit (CU) 302 communicates with a core network 304 via a backhaul link 324, and communicates with a first distributed unit (DU) 306 and a second distributed unit 308 via respective midhaul links 326a and 326b. The first distributed unit 306 communicates with a first radio unit (RU) 310 and a second radio unit 312 via respective fronthaul links 328a and 328b. The second distributed unit 308 communicates with a third radio unit 314 via a fronthaul link 328c. The first radio unit 310 communicates with at least one UE 316 via at least one RF access link 330a. The second radio unit 312 communicates with at least one UE 318 via at least one RF access link 330b. The third radio unit 314 communicates with at least one UE 320 via at least one RF access link 330c.
[0060] In some examples, the control unit (e.g., CU 302) is a logical node that hosts a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, and other control functions. The control unit may also terminate an interface (e.g., an E1 interface, an E2 interface, etc.) of a core network node (e.g., a node of a core network). Figure 3 In addition, the F1 interface ( Figure 3 The F1 interface may provide a mechanism for interconnecting the CU 302 (e.g., the PDCP layer and higher layers) and the DU (e.g., the radio link control (RLC) layer and lower layers). In some aspects, the F1 interface may provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC messaging, etc.). For example, the F1 interface supports F1-C on the control plane and F1-U on the user plane. F1AP is an application protocol for F1, which in some examples defines a signaling procedure for F1.
[0061] In some examples, a DU (e.g., DU 306 or DU 308) is a logical node that hosts an RLC layer, a medium access control (MAC) layer, and a high physical (PHY) layer based on a lower layer functional split (LLS). In some aspects, a DU may control the operation of at least one RU. A DU may also terminate to an interface (e.g., F1, E2, etc.) of a CU and / or other network nodes. In some examples, a high PHY layer includes portions of PHY processing, such as forward error correction 1 (FEC 1) encoding and decoding, scrambling, modulation, and demodulation.
[0062] In some examples, a RU (e.g., RU 310, RU 312, or RU 314) is a logical node that hosts low PHY layers and radio frequency (RF) processing based on a lower layer functional split. In some examples, a RU may be similar to a 3GPP transmit receive point (TRP) or a remote radio head (RRH), while also including a low PHY layer. In some examples, the low PHY layer includes parts of PHY processing, such as fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and physical random access channel (PRACH) extraction and filtering. The RU may also include a radio (e.g., radio frequency (RF)) chain for communicating with one or more UEs.
[0063] In different examples, the functional split between the entities of the RAN 300 may be different. In some examples, layer 1 functions, layer 2 functions, and layer 3 functions may be allocated between the RU, DU, and CU entities. Examples of layer 1 functions include RF functions and low PHY layer functions. Examples of layer 2 functions include high PHY layer functions, low MAC layer functions, high MAC layer functions, low RLC layer functions, and high RLC layer functions. Examples of layer 3 functions include PDCP layer functions and RRC layer functions. In other examples, other functional splits may be used.
[0064] As discussed above, two layer 3 functions may be implemented in the CU. Thus, in this case, other layer 1 functions and layer 2 functions may be split between the RU and the DU. In some examples, layer 1 functions are implemented in the RU and layer 3 functions are implemented in the DU. In some examples, all PHY functionality is implemented in the RU (i.e., high PHY layer functions are implemented in the RU but not the DU). In other examples, other functional splits may be used.
[0065] In different examples, different splits may be used between low-level functionality and high-level functionality. For example, in some cases, a division between low-PHY layer functions and high-PHY layer functions may be defined between RE mapping and precoding. Thus, in this case, RE mapping may be designated as a low-PHY layer function performed by the RU, and precoding may be designated as a high-PHY layer function performed by the DU. In other examples, other functional splits may be used.
[0066] Figure 4 is a diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects. Figure 4Various aspects of the present disclosure are described using OFDM waveforms schematically illustrated in . It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.
[0067] Reference now Figure 4 , illustrates an expanded view of an exemplary subframe 402 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical layer (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers of a carrier.
[0068] Resource grid 404 may be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 404 may be available for communication. Resource grid 404 is divided into a plurality of resource elements (REs) 406. RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which may contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).
[0069] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 404. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a network entity such as a base station, gNB, eNB, etc., or may be self-scheduled by a UE implementing D2D sidelink communication.
[0070] In this illustration, RB 408 is shown as occupying a portion of the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying a portion of the entire duration of subframe 402, although this is only one possible example.
[0071] Each 1 ms subframe 402 may include one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.
[0072] An expanded view of one of the time slots 410 illustrates the time slot 410 including a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 4 The illustrated structure is merely exemplary in nature and different slot structures may be utilized and may include one or more for each of the control region and the data region.
[0073] Although in Figure 4Although not illustrated in the figure, each RE 406 within the RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control channels and / or data channels within the RB 408.
[0074] In some examples, time slot 410 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.
[0075] In an example of cellular communication on a cellular carrier via a Uu interface, for DL transmissions, a network entity (e.g., a base station or a scheduling entity) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI) including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL transmissions and UL transmissions. The PDCCH may also carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique known to those of ordinary skill in the art, where the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any suitable integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may transmit a HARQ retransmission, which may enable append combining, incremental redundancy, and the like.
[0076] A network entity (e.g., a base station) may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.
[0077] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).
[0078] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 406 to carry UL control information (UCI) including one or more UL control channels (such as a physical uplink control channel (PUCCH)) to the scheduling entity. The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for a network entity to schedule an uplink transmission. Here, in response to the SR sent on the UCI, the network entity may send a DCI, which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.
[0079] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL transmissions, or a physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH may carry multiple SIBs, not limited to the SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above).
[0080] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.
[0081] Figure 4 The channels or carriers illustrated are not necessarily all channels or carriers that may be utilized between devices, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.
[0082] In some aspects of the present disclosure, a network entity (eg, a base station) and / or a scheduled entity (eg, a UE) may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 5 An example of a wireless communication system 500 that supports MIMO and beamforming is illustrated. In a MIMO system, a transmitter 502 includes multiple transmit antennas 504 (e.g., N transmit antennas), and a receiver 506 includes multiple receive antennas 508 (e.g., M receive antennas). Therefore, there are N×M signal paths 510 from the transmit antennas 504 to the receive antennas 508. Each of the transmitter 502 and the receiver 506 may be implemented, for example, within a network entity 108, a scheduled entity 106, or any other suitable wireless communication device.
[0083] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously send different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be sent to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial characteristics, and the different spatial characteristics enable each of the UEs to recover one or more data streams destined for the UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.
[0084] The number of data streams or layers corresponds to the rank of transmission. In general, the rank of the MIMO system 500 is limited to the lower of the number of transmit antennas 504 or receive antennas 508. In addition, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and therefore the number of data streams) may be determined based on a rank indicator (RI) sent from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) on each receive antenna in the receive antenna and the measured signal to interference and noise ratio (SINR). The RI may indicate, for example, the number of layers that can be supported under the current channel conditions. The base station may use the RI and resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign the rank of transmission to the UE.
[0085] In a time division duplex (TDD) system, UL and DL are reciprocal because they each use different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station may assign a rank for DL MIMO transmission based on UL SINR measurements (e.g., based on an SRS sent from the UE, or other pilot signals). Based on the assigned rank, the base station may then send a CSI-RS with a separate C-RS sequence for each layer to provide multi-layer channel estimation. The UE may measure the channel quality across layers and resource blocks based on the CSI-RS, and feed back RI and a channel quality indicator (CQI) (which indicates to the base station the modulation and coding scheme (MCS) to be used for transmission to the UE) for updating the rank and assigning REs for future downlink transmissions.
[0086] In the simplest case, Figure 5As shown, rank 2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will send one data stream from each transmit antenna 504. Each data stream follows a different signal path 510 to each receive antenna 508. The receiver 506 can then reconstruct the data streams using the signals received from each receive antenna 508.
[0087] Beamforming is a signal processing technique that can be used at a transmitter 502 or a receiver 506 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 502 and the receiver 506. Beamforming can be achieved by combining signals communicated via antennas 504 or 508 (e.g., antenna elements of an antenna array module) so that some of the signals experience constructive interference and other signals experience destructive interference. In order to produce the desired constructive / destructive interference, the transmitter 502 or the receiver 506 may apply an amplitude and / or phase offset to the signal transmitted or received from each of the antennas 504 or 508 associated with the transmitter 502 or the receiver 506.
[0088] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0089] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designation FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0090] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, the term "below 6 GHz" and the like can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.
[0091] In 5G NR systems, especially for FR2 (e.g., mmWave) systems, beamformed signals can be used for most downlink channels, including PDCCH and PDSCH. In addition, broadcast control information (such as SSB, slot format indicator (SFI), and paging information) can be sent in a beam scanning manner so that all scheduled entities (e.g., UEs) in the coverage area of the network entity (e.g., base station, gNB, TRP) can receive the broadcast control information. In addition, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels (including PUCCH and PUSCH).
[0092] Figure 6 6 is a diagram illustrating communication between a network entity 604 and a UE 602 using beamformed signals according to some aspects. The network entity 604 may be Figure 1 and / or Figure 2 Any of the illustrated base stations (e.g., gNB, CU, DU) or scheduling entities, and UE 602 may be Figure 1 and / or Figure 2 Any of the UEs or scheduled entities illustrated.
[0093] The network entity 604 may generally be capable of communicating with the UE 602 using one or more transmit beams, and the UE 602 may further be capable of communicating with the network entity 604 using one or more receive beams. As used herein, the term transmit beam refers to a beam on the network entity 604 that can be used for downlink or uplink communication with the UE 602. Additionally, the term receive beam refers to a beam on the UE 602 that can be used for downlink or uplink communication with the network entity 604.
[0094] exist Figure 6In the example shown, the network entity 604 is configured to generate a plurality of transmit beams 606a-606h, each of which is associated with a different spatial direction. In addition, the UE 602 is configured to generate a plurality of receive beams 608a-608e, each of which is associated with a different spatial direction. It should be noted that although some beams are illustrated as being adjacent to each other, this arrangement may be different in different aspects. For example, the transmit beams 606a-606h transmitted during the same symbol may not be adjacent to each other. In some examples, the network entity 604 and the UE 602 may each transmit more or less beams distributed in all directions (e.g., 360 degrees) and in three dimensions. In addition, the transmit beams 606a-606h may include beams with varying beam widths. For example, the network entity 604 may transmit certain signals (e.g., SSB) on a wider beam and transmit other signals (e.g., CSI-RS) on a narrower beam.
[0095] The network entity 604 and the UE 602 may use a beam management procedure to select one or more transmit beams 606a-606h on the network entity 604 and one or more receive beams 608a-608e on the UE 602 for communicating uplink and downlink signals therebetween. In one example, during initial cell acquisition, the UE 602 may perform a P1 beam management procedure to scan the multiple transmit beams 606a-606h on the multiple receive beams 608a-608e to select a beam pair link (e.g., one of the transmit beams 606a-606h and one of the receive beams 608a-608e) for a physical random access channel (PRACH) procedure for initial access to a cell. For example, periodic SSB beam scanning may be implemented at a specific interval (e.g., based on an SSB periodicity) on the network entity 604. Thus, the network entity 604 may be configured to scan or transmit an SSB on each of the plurality of wider transmit beams 606a-606h during a beam scanning interval. The UE may measure a reference signal received power (RSRP) of each SSB transmit beam on each receive beam of the UE and select transmit and receive beams based on the measured RSRP. In an example, the selected receive beam may be the receive beam on which the highest RSRP is measured, and the selected transmit beam may have the highest RSRP, as measured on the selected receive beam.
[0096] After completing the PRACH procedure, the network entity 604 and the UE 602 may perform a P2 beam management procedure for beam refinement at the network entity 604. For example, the network entity 604 may be configured to scan or transmit a DL reference signal (e.g., CSI-RS) on each of a plurality of narrower transmit beams (e.g., beams 606a-606h). Each of the narrower CSI-RS beams may be a sub-beam of a selected SSB transmit beam (e.g., within a spatial direction of the SSB transmit beam). Transmission of the CSI-RS transmit beam may occur periodically (e.g., as configured by the network entity via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the network entity via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., as triggered by the network entity via DCI). The UE 602 is configured to scan multiple CSI-RS transmit beams 606a-606h on multiple receive beams 608a-608e. The UE 602 then performs beam measurements (e.g., RSRP, SINR, etc.) on the CSI-RS received on each of the receive beams 608a-608e to determine the corresponding beam quality of each of the CSI-RS transmit beams 606a-606h, as measured on each of the receive beams 608a-608e.
[0097] The UE 602 may then generate and send a layer 1 (L1) measurement report to the network entity 604, which includes a corresponding beam index (e.g., CSI-RS resource indicator (CRI)) and beam measurements (e.g., RSRP or SINR) for one or more of the CSI-RS transmit beams 606a-606h on one or more of the receive beams 608a-608e. The network entity 604 may then select one or more CSI-RS transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 602. In some examples, the selected CSI-RS transmit beam has the highest RSRP from the L1 measurement report. The sending of the L1 measurement report may occur periodically (e.g., as configured by the network entity via RRC signaling), semi-persistently (e.g., as configured by the network entity via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., triggered by the network entity via DCI).
[0098] UE 602 may further select a corresponding receive beam on UE 602 for each selected serving CSI-RS transmit beam to form a corresponding beam pair link (BPL) for each selected serving CSI-RS transmit beam. For example, UE 602 may utilize beam measurements obtained during a P2 procedure or perform a P3 beam management procedure to obtain new beam measurements for the selected CSI-RS transmit beam to select a corresponding receive beam for each selected transmit beam. In some examples, the selected receive beam to be paired with a particular CSI-RS transmit beam may be the receive beam on which the highest RSRP is measured for the particular CSI-RS transmit beam.
[0099] In some examples, in addition to performing CSI-RS beam measurements, the network entity 604 may configure the UE 602 to perform SSB beam measurements and provide an L1 measurement report containing beam measurements of the SSB transmit beams 606a-606h. For example, the network entity 604 may configure the UE 602 to perform SSB beam measurements and / or CSI-RS beam measurements for beam failure detection (BFD), beam failure recovery (BFR), cell reselection, beam tracking (e.g., for mobile UE 602 and / or network entity 604), or other beam optimization purposes.
[0100] In addition, when the channel is reciprocal, an uplink beam management scheme may be used to select transmit beams and receive beams. In an example, the UE 602 may be configured to scan or transmit on each of the multiple receive beams 608a-608e. For example, the UE 602 may send an SRS on each beam in different beam directions (i.e., SRS beam scanning). In addition, the network entity 604 may be configured to receive an uplink beam reference signal (e.g., SRS) on multiple transmit beams 606a-606h. The network entity 604 then performs a beam measurement (e.g., RSRP, SINR, etc.) of the beam reference signal on each of the transmit beams 606a-606h to determine the corresponding beam quality of each of the receive beams 608a-608e, as measured on each of the transmit beams 606a-606h.
[0101] The network entity 604 may then select one or more transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 602. In some examples, the selected transmit beam has the highest RSRP. The UE 602 may then select a corresponding receive beam for each selected serving transmit beam using, for example, the P3 beam management procedure as described above to form a corresponding beam pair link (BPL) for each selected serving transmit beam.
[0102] In one example, a single CSI-RS transmit beam (e.g., beam 606d) on the network entity 604 and a single receive beam (e.g., beam 608c) on the UE may form a single BPL for communication between the network entity 604 and the UE 602. In another example, multiple CSI-RS transmit beams (e.g., beams 606c, 606d, and 606e) on the network entity 604 and a single receive beam (e.g., beam 608c) on the UE 602 may form respective BPLs for communication between the network entity 604 and the UE 602. In another example, multiple CSI-RS transmit beams (e.g., beams 606c, 606d, and 606e) on the network entity 604 and multiple receive beams (e.g., beams 608c and 608d) on the UE 602 may form multiple BPLs for communication between the network entity 604 and the UE 602. In this example, a first BPL may include a transmit beam 606c and a receive beam 608c, a second BPL may include a transmit beam 608d and a receive beam 608c, and a third BPL may include a transmit beam 608e and a receive beam 608d.
[0103] In addition to the L1 measurement report, the UE 602 may further utilize the beam reference signal to estimate the channel quality of the channel between the network entity 604 and the UE 602. For example, the UE 602 may measure the SINR of each received CSI-RS and generate a CSI report based on the measured SINR. The CSI report may include, for example, a channel quality indicator (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), and / or a layer indicator (LI). The network entity (e.g., a gNB) may use the CSI report to select a rank for the UE, along with a precoding matrix and an MCS for future downlink transmissions to the UE. The MCS may be selected from one or more MCS tables, each MCS table being associated with a particular type of coding (e.g., polar coding, LDPC, etc.) or modulation (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM, 256QAM, etc.). The LI may be used to indicate which column of the precoding matrix for the reported PMI corresponds to the strongest layer codeword corresponding to the reported maximum wideband CQI.
[0104] Uplink parameters
[0105] In wireless networks (e.g., 5G NR), precoding may be used for UL communications (e.g., SRS and PUSCH transmissions). Precoding assumes that channel state information is known at the transmitter (e.g., UE for UL transmissions). Precoding may begin with channel sounding, which involves transmitting a decoding message (e.g., SRS) to a network entity (e.g., gNB), which may then determine channel state information based on the sounding message and provide uplink precoding information for subsequent UL transmissions (e.g., PUSCH). For the sounding message, the UE may scan UL beams across multiple SRS resources. Depending on the configuration of the network entity and the UE (e.g., antenna panel, number of beams, polarization), the UE may perform beam scanning across a large number of beam pairs. However, beam scanning across a large number of beams or SRS resources may consume a lot of power and increase processing overhead at the UE.
[0106] In some aspects, the UE may use one or more SRS resources to send SRS, and one SRS resource may have up to four ports. Each SRS resource may include an SRS resource parameter set that configures the SRS resource. For example, the SRS resource parameters may include a port set, the number of consecutive symbols (Nsymb), the time domain allocation (Ioffset), repetition, the transmission comb structure (kTC), the bandwidth (mSRS), and other suitable parameters. The SRS resource set may include one or more SRS resources, and multiple SRS resource sets may be configured for the UE. In addition, each SRS resource set may be configured as periodic, aperiodic, or semi-persistent, so that each SRS resource in the corresponding SRS resource set is periodic, aperiodic, or semi-persistent, respectively.
[0107] A network entity (e.g., a base station) may determine UL parameters based on the received SRS scan and indicate certain UL parameters for uplink transmission (e.g., SRS, PUSCH) to the UE. For example, the UL parameters may include an SRS resource indicator (SRI), a transmit pre-decoder matrix indicator (TPMI), and a transmit rank indicator (TRI). The SRI indicates the selected SRS resource. The TRI indicates the preferred transmit rank. The TPMI indicates the preferred pre-decoder on the port in the selected SRS resource, and the pre-decoder may be selected from the uplink codebook. The UE may then perform uplink transmission based on the SRI, TRI, and TPMI. In some aspects, the UL parameters may also include an MCS and an uplink resource in which the PUSCH is to be transmitted. In the present disclosure, the UL parameters may include one or more of the following: SRI, TPMI, TRI, MCS, and PUSCH resources.
[0108] Figure 7is a signaling diagram illustrating exemplary signaling 700 between a network entity (NE) 702 and a UE 704 for providing channel state information feedback (CSF) within a wireless network. In the illustrated scenario, the UE 704 may provide a CSI report to the network entity 702. The network entity 702 may correspond to, for example Figure 1 , Figure 2 and / or Figure 3 The illustrated base station (e.g., gNB or eNB) or other network entity or node. The network entity 702 may be implemented as a converged base station or a decomposed base station. In a decomposed base station architecture, the network entity 702 may include one or more of a central unit (CU), a distributed unit (DU), or a radio unit (RU). The UE 704 may correspond to, for example, Figure 1 , Figure 2 and / or Figure 3 The UE or other scheduled node is shown.
[0109] At 706, the network entity 702 may send a reference signal, such as a CSI-RS or an SSB, to the UE 704. In some examples, the reference signal may include multiple reference signals. The reference signal may be sent via a corresponding channel measurement resource. The channel measurement resource may include a time-frequency resource and a beam direction within which a specific reference signal may be sent. For example, the channel measurement resource may include a non-zero power (NZP) CSI-RS resource. The NZP resource may be used for channel measurement together with one or more interference measurement resources that can be used for interference measurement. The interference measurement resource may include a zero power (ZP) CSI-RS resource and an NZP CSI-RS resource having properties similar to those of the NZP CSI-RS resource used for channel measurement. In addition, each reference signal may include multiple pilots allocated within the corresponding channel measurement resource.
[0110] At 708, UE 704 may estimate the wireless channel based on the reference signals. For example, UE 704 may measure SINRs of one or more of the reference signals to obtain a channel estimate of the wireless channel.
[0111] At 710, the UE 704 may determine various CSI values from the channel estimate. For example, the UE 704 may determine the RI, PMI, and CQI from the channel estimate. The CQI may include an index (e.g., a CQI index) ranging from, for example, 0 to 15. The CQI index may indicate, for example, the highest MCS at which a block error rate (BLER) of the channel does not exceed 10%. Once the CSI value is determined, the CSI value may be fed back. For example, at 712, the UE 504 may send a CSI report including the determined CSI value to the network entity 702.
[0112] The network entity 702 and the UE 704 may each support different types of CSI reports (including L1 measurement reports) and / or different types of measurements. In order to distinguish between different report / measurement types and measurement configurations, the network entity 702 may configure one or more report settings to the UE 704. Each report setting may be associated with a resource setting indicating a configuration of one or more reference signals (e.g., CSI-RS) for generating a CSI report.
[0113] In some aspects, a network entity (e.g., a gNB, CU, or DU) may determine the UL beam (or beam parameters) of a UE by beam scanning across multiple SRS resources. In one example, the network entity may use one antenna panel / array to communicate with the UE, and the antenna panel may support 32 transmit beams in two polarizations (e.g., beams 605a-606h). The UE may have two antenna panels / arrays, each of which may support four receive beams in two polarizations (e.g., beams 608a-608e). In this case, the network entity needs to process 1024 beam pairs. In another example, the network entity may use SRS resources with TDM regarding eight transmit beams for a particular antenna panel, and when scheduling the UE's PUSCH, the network entity may indicate the SRS resources (e.g., SRI) to the UE. However, SRS-based beam scanning is power and overhead intensive for the UE.
[0114] Various aspects of the present disclosure provide techniques and apparatus that can reduce SRS beam scanning. In some aspects, time domain UL parameter (e.g., SRI, TPMI, etc.) predictions can be used to reduce the power and / or overhead associated with SRS-based beam scanning. In some aspects, a UE can use a machine learning (ML) model to generate UL parameter predictions that can be used to achieve such power / OH reduction. For example, the input to the ML model may include at least one of the following: historically received UL parameters; a (rough) UL parameter prediction for a future time instance indicated by the network, which can guide the UE to extrapolate in a specific direction in the UL parameter prediction; and other channel characteristics based on DL-RS measurements / predictions. The output of the ML model can provide UL parameter predictions (e.g., SRI / TPMI predicted for another future time instance).
[0115] To facilitate the UL parameter prediction techniques described above, the UL grant DCI may signal the predicted UL parameters for future time instances. In some aspects, the ML model may be defined in a communication standard (e.g., a 3GPP NR standard). The definition of the ML model may include inputs, outputs, model training, modem inference, etc. The association between the DL reference signal and the UL parameter prediction may be predefined.
[0116] Various aspects of the present disclosure provide various techniques for determining predicted UL parameters for future UL transmissions so that power consumption and overhead associated with UL transmissions can be reduced at a wireless device. In some aspects, a UE can use the disclosed techniques to predict UL parameters for a precoding scheme to achieve power and overhead savings at the UE.
[0117] Figure 8 800 for predicting UL parameters according to some aspects. In one aspect, a UE 802 may predict UL parameters 804 for potential future instances of UL transmissions based at least in part on historical UL parameters 806 received from a network entity (e.g., a base station, gNB), base station (BS) predicted UL parameters 808 for future instances of uplink transmissions (e.g., SRS / PUSCH), and / or DL measurements 810. An example of a DL measurement may be an L1 measurement (e.g., RSRP or SINR) of a DL reference signal (e.g., SSB, CSI-RS). In one aspect, the historical UL parameters may include SRI, TPMI, and / or MCS information received by the UE for past UL transmissions. Similarly, the base station predicted UL parameters 808 and the UE predicted UL parameters 804 may include SRI, TPMI, and / or MCS information for future UL transmissions (e.g., PUSCH, SRS). The base station predicted UL parameters 808 may assist the UE in determining (e.g., using interpolation / extrapolation) the UE predicted UL parameters 804.
[0118] Fig. 9 9 is a flow chart illustrating a process 900 for determining UE-side predicted UL parameters according to some aspects. For example, the process may be performed by UE 602, 704, or 802 described above. At block 902, the UE may receive downlink control information (e.g., UL grant DCI) from a network entity (e.g., network entity 604). Example UL grant DCI 1000 (see Fig.10) may schedule or trigger a PUSCH and provide UL parameters 1002 for PUSCH transmission. The UL grant DCI 1000 may also provide UL parameters 1004 predicted by the base station for an instance of future PUSCH transmission. In one aspect, the UL grant DCI 1000 may use a new DCI format that is different from an existing DCI format that does not provide predicted UL parameters. In one aspect, the UL grant DCI 1000 may be scrambled using a specific radio network temporary identifier (RNTI) to indicate that the UL grant DCI includes UL parameters predicted by the base station. In one aspect, the UL grant DCI 1000 may use reserved bits in the DCI format to convey UL parameters (e.g., SRI, TPMI, MCS) predicted by the base station. In one aspect, the network entity may (e.g.) configure the UE using an RRC configuration to identify the UL grant DCI format. In one aspect, the UL grant DCI format may be predefined in a standard specification (e.g., a 3GPP specification) that governs communications between the network entity and the UE.
[0119] At block 904, the UE may determine UE-side predicted UL parameters (e.g., UL parameters 804) for one or more future or potential UL transmissions (e.g., PUSCH transmissions) based at least in part on the UL grant DCI and DL measurements (e.g., L1 measurements of SSB and / or CSI-RS) obtained prior to the future UL transmissions. In this case, the UL grant DCI may not directly schedule the future UL transmissions. The UE-predicted UL parameters may be used for future UL transmissions that occur prior to the future UL transmissions indicated by the DCI associated with the base station predicted UL parameters included in the DCI.
[0120] At block 906, the UE may send the UL transmission using a precoding scheme based on the UL parameters predicted by the UE. In one example, the UE may select an SRS resource based on an SRI indicated by the UL parameters predicted by the UE. In one example, the UE may select a precoder based on a TPMI indicated by the UL parameters predicted by the UE. In one example, the UE may select an MCS for the UL transmission based on the UL parameters predicted by the UE.
[0121] In some aspects, the UE may predict UL parameters for future or potential UL transmissions (e.g., PUSCH) based on one or more factors. The first factor may be the UL parameters predicted by the base station indicated by the UL grant DCI as described above. The second factor may be the UL parameters for PUSCH scheduled by the same DCI indicated by the UL grant DCI. The third factor may be historical UL parameters received by the UE. In one example, the UE may consider a time instance associated with the reception of historical UL parameters. In one example, the UE may consider a time instance associated with the reception of historical UL parameters (e.g., SRI and TPMI). In one example, the UE may consider a time instance associated with the last SRS transmission prior to the time instance of the reception of the historical UL parameters.
[0122] The fourth factor may be a time difference associated with UL parameter prediction and channel measurement. In one example, the UE may consider the time difference (e.g., symbol / time slot) between the time of the future PUSCH 1102 and the time (e.g., symbol / time slot) of receiving the UL grant DCI 1104. Fig.11 In one example, the UE may consider the time difference between the time of the future PUSCH 1102 and the time of sending the SRS 1106 associated with the indicated UL parameters (e.g., Fig.11 1104), wherein the indicated UL parameters are for a PUSCH (e.g., PUSCH 1108) scheduled by the UL grant DCI 1104. In one example, the UE may consider the time difference (e.g., symbol / time slot) between the time of the future PUSCH 1102 and the time instance of the future PUSCH 1108 for which the BS predicted UL parameters indicated in the UL grant DCI 1104 are for. Fig.11 In one example, the UE may consider the time difference between the time of receiving the UL grant DCI 1104 and the time instance before the future PUSCH 1102 but after the time instance of receiving the UL grant DCI 1104 (e.g., Fig.11 T4 in ).
[0123] The fifth factor may be DL measurements, if applicable. For example, the UE may consider channel quality or conditions estimated or predicted based on measurements of DL reference signals (e.g., SBS and CSI-RS). For example, a channel profile may be estimated from CSI-RS, SSB, or DMRS, which may be used as input to an ML model for predicting UL parameters. Channel quality may affect the determination of UL parameters or precoding schemes used by the UE.
[0124] In some aspects of the present disclosure, a UE may use machine learning (ML) techniques to predict UL parameters for potential or future UL transmissions (eg, PUSCH). Fig.12 is a diagram illustrating a process for predicting UL parameters for future UL transmissions using an ML model in accordance with some aspects. For example, a UE may use an ML model 1204 to determine UL parameters 1202 (e.g., SRI, TPMI, and / or MCS) for future PUSCH. In some aspects, the ML model 1204 may be provided by the network, pre-configured (e.g., defined in a 3GPP specification), or specific to a particular UE implementation. In one aspect, the ML model 1204 used by the UE may be made known to a network entity (e.g., a base station). In one aspect, the ML model may include considerations as described above with respect to Figures 8 to 11 Various inputs (e.g., ML model inputs 1206) for one or more of the factors described. For example, the ML model inputs 1206 may include at least UL parameters (e.g., SRI and TPMI) for a future scheduled PUSCH (e.g., PUSCH 1108) associated with a future time instance. In some aspects, the ML model inputs and / or outputs may be standard predefined (e.g., defined in 3GPP specifications), or network configured (e.g., the UE may download the ML model from a network entity).
[0125] In some aspects, the ML model 1204 may be trained using suitable methods and data, such as a sequence of UL parameters for associated future UL transmission instances determined via specific SRS measurements. In one example, the ML model 1204 may be trained with an input sequence of SRI and TPMI determined based on periodic SRS measurements (e.g., having a periodicity of 5 milliseconds (ms)) and via DL measurements of periodic CSI-RS (e.g., having a periodicity of 5 ms). The output may be a predicted SRI and TPMI for future (e.g., 5 ms) UL instances. In one example, the periodic SRS may have a periodicity of 20 ms. The UE may receive a UL grant DCI indicating a predicted future SRI / TPMI targeting a future PUSCH scheduled by a current UL grant DCI, which may be determined by a network entity based on a periodic SRS sent prior to the UL grant DCI. The UE may use the indicated SRI / TPMI as part of the ML model input sequence, and the SRI / TPMI predicted by the ML model may also be used as a model input to establish an input sequence of SRI / TPMI with periodicity (e.g., 5ms). For future PUSCHs without SRI / TPMI indicated by the UL grant DCI, the UE may determine the SRI / TPMI for the future PUSCH based on the ML predicted UL parameters associated with the corresponding PUSCH time instance.
[0126] Fig.13 1 is a diagram illustrating a process for predicting UL parameters for future UL transmissions using analysis techniques according to some aspects. The UE may use certain analysis techniques 1302 to determine predicted UL parameters 1300 (e.g., SRI and TPMI) for future UL transmissions (e.g., PUSCH). In one aspect, the UE may consider the above description of Figures 8 to 11 One or more of the options described.
[0127] In one example, the UE may use interpolation to determine the predicted UL parameters based on: 1) the predicted SRI / TPMI for the future PUSCH indicated by the UL grant DCI; 2) the SRI / TPMI for the PUSCH scheduled by the same UL grant DCI indicated by the UL grant DCI; 3) the time difference between the time when the future PUSCH is scheduled and the time when the UL grant DCI is received (or the time when the SRS associated with the indicated SRI / TPMI for the PUSCH scheduled by the UL grant DCI is sent); 4) the time difference between the time when the future PUSCH is scheduled and the future time instance for which the predicted SRI / TPMI indicated in the UL grant DCI is indicated; and 5) DL measurements.
[0128] In another example, the UE may first use extrapolation to determine predicted UL parameters based on: 1) predicted SRI / TPMI for future PUSCH indicated by UL grant DCI; 2) SRI / TPMI for PUSCH scheduled by the same UL grant DCI indicated by UL grant DCI; 3) time difference between a time instance before the scheduled time of future PUSCH but after the time of receiving UL grant DCI and the time of receiving UL grant DCI; and 4) DL measurement. Based on the extrapolation, the UE may determine an intermediate predicted SRI / TPMI. The UE may then use interpolation to determine the predicted SRI / TPMI for the future PUSCH based on: 1) the intermediate predicted SRI / TPMI; 2) the predicted SRI / TPMI for the future PUSCH indicated by the UL authorization DCI; 3) the time difference between the scheduled time of the future PUSCH and the time of receiving the UL authorization DCI (or the time of sending the SRS associated with the indicated SRI / TPMI for the PUSCH scheduled by the UL authorization DCI); 4) the time difference between the scheduled time of the future PUSCH and the future time instance for which the predicted SRI / TPMI is indicated in the UL authorization DCI; 5) the time difference between the time instance before the scheduled time of the future PUSCH but after the time of receiving the UL authorization DCI and the time of receiving the UL authorization DCI; and 6) DL measurement.
[0129] In some aspects, the analysis techniques described above may be defined in a communication standard (e.g., a 3GPP specification), defined in a network entity configuration, or defined based on a UE-specific implementation. In some aspects, the analysis techniques may include interpolation and / or extrapolation. In some aspects, the interpolation and / or extrapolation may be linear, polynomial, or kernel-based. In some aspects, coefficients associated with the interpolation and / or extrapolation may be indicated by a UL grant DCI, or may be preconfigured.
[0130] In some aspects, the network entity may also configure DL reference signals (e.g., SSB and CSI-RS) for measuring DL channel characteristics associated with the determination of predicted UL parameters (e.g., SRI / TPMI). In one example, a network entity (e.g., gNB, CU, etc.) may associate a DL reference signal (e.g., CSI-RS / SSB) resource setting, resource set, or resource ID with an SRS resource set for facilitating UL parameter prediction. In some aspects, the DL reference signal resource setting may be configured by an information element (IE) (e.g., CSI-ResourceConfig). For example, the CSI-ResourceConfig IE may configure one or more CSI resource sets or SSB resource sets. Additional information related to the DL reference signal may also be configured by the CSI-ResourceConfig IE. In some aspects, a reference signal resource set may include a set-specific configuration. Each DL reference signal resource may indicate a specific beam, frequency resource, and OFDM symbol on which a reference signal may be measured. Each reference signal resource may also be indexed by a corresponding reference signal resource ID. The reference signal resource ID may not only identify a specific beam (e.g., a port), but may also identify a resource on which a reference signal may be measured. For example, the reference signal resource ID may include a CSI-RS resource indicator (CRI) or an SRI. In one aspect, a network entity may use an RRC configuration (e.g., SRS-ResourceSet) to set an SRS usage type (e.g., PredictiveSRS type) for an SRS resource used to predict UL parameters. In one example, a network entity may associate a DL reference signal (e.g., CSI-RS / SSB) resource setting, resource set, or resource ID with an ML model for UL parameter prediction.
[0131] Fig.14is a flow chart illustrating a process 1400 for scheduling UL transmissions using DCI without UL parameter indication according to some aspects. At block 1402, a UE may receive an UL grant DCI from a network entity (e.g., a gNB). The UL grant DCI may schedule a PUSCH without providing or indicating corresponding UL parameters (e.g., SRI, TPMI, and / or MCS) for the UL transmission. At block 1404, the UE may autonomously determine UL parameters (e.g., SRI, TPMI, and / or MCS) for an UL transmission (e.g., PUSCH) based on previously received UL parameters. In one example, the UE may apply the UL parameters identified in the previous DCI to future UL transmissions scheduled by a configured grant (e.g., an uplink grant configured by RRC). In some aspects, the network entity may use a specific DCI format for the UL grant DCI without indicating the UL parameters. In one example, the DCI may be scrambled using a specific RNTI indicating the UL grant DCI without UL parameters.
[0132] In one aspect, in response to the network entity transmitting a UL grant DCI without UL parameters, the UE may determine the UL parameters based on a previous UL grant DCI including information for predicting future UL parameters. In one example, based on the previous UL grant DCI, the UE may identify a time window for receiving a UL grant DCI scheduling a PUSCH without UL parameters. In one example, the network entity may use RRC signaling to preconfigure multiple time window selections, and the UL grant DCI may indicate one of the windows.
[0133] In one aspect, the configured grant PUSCH configuration may indicate that the UL parameters may be predicted UL parameters identified in a previous proposal (e.g., a UL grant DCI with UL parameters for future UL transmissions). In this case, the UE does not expect the DCI (for triggering the configured grant PUSCH) to include the UL parameters.
[0134] In some aspects, the UE may determine that UL parameters (e.g., SRI, TPMI, and / or MCS) are not explicitly indicated in the UL grant DCI based on the DCI format used, and may then use UL parameters based on predictions proposed previously. The DCI may have a specific format or be scrambled with a specific RNTI to indicate that the DCI does not explicitly indicate UL parameters.
[0135] In some aspects, a network entity (e.g., a gNB) may explicitly (e.g., using DCI, MAC control element (MAC-CE), and / or RRC signaling) initialize (start) and terminate (stop) use of the UL parameter prediction process described above. In some aspects, the network entity may implicitly indicate to the UE whether to start or stop use of the UL parameter prediction process described above by using a specific DCI format or DCI scrambled with a specific RNTI. In some aspects, the UE may assume that the predicted UL parameters are based on the same transmission rank identified from the UL grant DCI that provides information for identifying the predicted UL parameters.
[0136] In some aspects, the UE may proactively or autonomously transmit a request or report (e.g., a scheduling request (SR), UCI, MACCE, or RRC message) to indicate a request to stop using the UL parameter prediction process described above. In one example, the UE may determine that it will move faster and the UL parameter prediction may be less effective or less accurate. In this case, the UE may request the network entity to stop using the UL parameter prediction process. In one example, the UE may predict based on DL measurements that channel conditions will change more quickly. In this case, the UE may request the network entity to stop using the UL parameter prediction process.
[0137] In some aspects, the UL parameter prediction process described above can be used for time domain MCS prediction. In some aspects, the prediction of MCS and SRI / TPMI can be used jointly for UL transmission. In some aspects, the ML model that predicts the future MCS also uses the future predicted SRI / TPMI as input for MCS prediction.
[0138] In some aspects, the future UL time instance associated with the predictive UL parameters (e.g., SRI and TPMI) indicated by the UL grant DCI for the future PUSCH may be based on at least one of: a standard definition (e.g., a 3GPP specification), an RRC configuration, or indicated in the UL grant DCI. For example, one or more available options (e.g., future time instances of the PUSCH) may be predefined (e.g., in a 3GPP specification or an RRC configuration), and the UL grant DCI may indicate one of the options.
[0139] Fig.151500 is a diagram illustrating an exemplary timeline of UL parameter prediction 1500 at a UE according to some aspects. A UE 1502 may receive historical (past) UL parameters 1504 (e.g., SRI / TPMI#1, SRI / TPMI#2, SRI / TPMI#3, and SRI / TPMI#4) from a network entity (e.g., a base station). The UE may save these historical UL parameters 1504 at the UE. For future UL transmissions, the UE 1502 may predict future UL parameters 1506 (e.g., SRI / TPMI) based on the historical UL parameters 1504, the BS-predicted future UL parameters (e.g., BS-predicted SRI / TPMI 1508), and DL measurements 1510. The BS-predicted future UL parameters may have a coarse time resolution relative to the UE-predicted UL parameters 1506. Therefore, the UE may predict UL parameters for UL transmissions in future time instances that are different from the time instances of the BS-predicted future UL parameters.
[0140] Fig.16 1614 is a block diagram illustrating an example of a hardware implementation of a network entity 1600 that employs a processing system 1614. For example, the network entity 1600 may be Figure 1 , Figure 2 , Figure 3 , Figure 6 and / or Figure 7 The RAN node 1600 may be further implemented in a converged or monolithic base station architecture, or in a disaggregated 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.
[0141] The network entity 1600 may be implemented with a processing system 1614 including one or more processors 1604. Examples of processor 1604 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, the network entity 1600 may be configured to perform any one or more of the functions described herein. That is, the processor 1604 as utilized in the network entity 1600 may be used to implement the various functions described in the present disclosure. Figures 8 to 14 and Fig.17 Any one or more of the processing procedures and procedures described and illustrated in .
[0142] In some examples, processor 1604 may be implemented via a baseband or modem chip, and in other implementations, processor 1604 may include multiple devices distinct and different from a baseband or modem chip (e.g., in scenarios that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.
[0143] In this example, the processing system 1614 may be implemented using a bus architecture (which is generally represented by bus 1602). The bus 1602 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1614. The bus 1602 communicatively couples various circuits including one or more processors (which are generally represented by processor 1604), memory 1605, and computer-readable media (which are generally represented by computer-readable media 1606). The bus 1602 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1608 provides an interface between the bus 1602 and the transceiver 1610. The transceiver 1610 provides a communication interface or component for communicating with various other devices through a transmission medium. Depending on the nature of the device, a user interface 1612 (e.g., a keypad, display, speaker, microphone, joystick, touch screen) may also be provided. Of course, such a user interface 1612 is optional and may be omitted in some examples (such as a base station).
[0144] The processor 1604 is responsible for managing the bus 1602 and general processing, including executing software stored on the computer-readable medium 1606. The software, when executed by the processor 1604, causes the processing system 1614 to perform the various functions described below for any particular device. The computer-readable medium 1606 and the memory 1605 may also be used to store data that is manipulated by the processor 1604 when executing the software.
[0145] One or more processors 1604 in the processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. The software may reside on a computer-readable medium 1606. The computer-readable medium 1606 may be a non-transient computer-readable medium. Non-transient computer-readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1606 may reside in processing system 1614, external to processing system 1614, or distributed across multiple entities including processing system 1614. Computer readable medium 1606 may be embodied in a computer program product. By way of example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.
[0146] In some aspects of the present disclosure, processor 1604 may include circuits configured for various functions including, for example, UL pre-coding prediction and indication. For example, the circuits may be configured to implement Figures 8 to 14 and Fig.17 One or more of the functions described.
[0147] In some aspects of the present disclosure, processor 1604 may include communication and processing circuitry 1640 configured for various functions, including, for example, communicating with a network core (e.g., a 5G core network), a scheduled entity (e.g., a UE), or any other entity, any other entity such as, for example, a local infrastructure or an entity that communicates with network entity 1600 via the Internet (such as a network provider). In some examples, the communication and processing circuitry 1640 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals to be transmitted). For example, the communication and processing circuitry 1640 may include one or more transmit / receive chains. In addition, the communication and processing circuitry 1640 may be configured to receive and process uplink traffic and uplink control messages (e.g., similar to Figure 1 The communication and processing circuit 1640 may be configured to execute communication and processing software 1650 stored on the computer-readable medium 1606 to implement one or more functions described herein.
[0148] In some implementations where communication involves receiving information, the communication and processing circuitry 1640 may obtain information from a component of the network entity 1600 (e.g., from a transceiver 1610 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process the information (e.g., decode), and output the processed information. For example, the communication and processing circuitry 1640 may output the information to another component of the processor 1604, to the memory 1605, or to the bus interface 1608. In some examples, the communication and processing circuitry 1640 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1640 may receive information via one or more channels. In some examples, the communication and processing circuitry 1640 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1640 may include functionality for components for processing, including components for demodulating, components for decoding, and the like.
[0149] In some implementations where the communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1640 may obtain the information (e.g., from another component of the processor 1604, the memory 1605, or the bus interface 1608), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1640 may output the information to the transceiver 1610 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1640 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1640 may transmit the information via one or more channels. In some examples, the communication and processing circuitry 1640 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1640 may include functionality for components for generating, including components for modulating, components for encoding, and the like.
[0150] In some aspects of the present disclosure, the processor 1604 may include a UL pre-coding prediction circuit 1642 configured for various functions, including, for example, predicting UL parameters for future UL transmissions. In one aspect, the UL pre-coding prediction circuit 1642 may be configured to determine the SRI, TPMI, and / or MCS of future UL transmissions. For example, the UL pre-coding prediction circuit 1642 may be configured to predict the SRI, TPMI, and / or MCS of future PUSCH using the processes and procedures described herein. In some examples, the UL pre-coding prediction circuit 1642 may be further configured to execute UL pre-coding prediction software 1652 stored on the computer-readable medium 1606 to implement one or more functions described herein.
[0151] Fig.17 1700 is a flow chart illustrating an exemplary process 1700 for UL precoding scheme prediction according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, process 1700 may be performed by Fig.16 The illustrated network entity 1600 performs the process 1700. In some examples, the process 1700 can be performed by any suitable device or component for performing the functions or algorithms described below.
[0152] At block 1702, a network entity may send a DCI (a first DCI) to a UE. For example, the network entity may be Figure 1 , Figure 2 , Figure 3 , Figure 6 and / or Figure 7In one example, the communication and processing circuit 1640 may provide a component for sending a DCI to a UE using the transceiver 1610. In one example, the DCI may be similar to DCI 1000, which may provide a UL transmission (e.g., Fig.11 The first DCI may also provide UL parameters 1002 for future UL transmissions (e.g., Fig.11 For example, the UL precoding prediction circuit 1642 may provide means for determining predicted UL parameters that may be used in a precoding scheme (e.g., SRI, TPMI, and / or MCS) for future UL transmissions.
[0153] At block 1704, the network entity may receive a first UL transmission scheduled by the first DCI. For example, the communication and processing circuitry 1640 may provide means for receiving the first UL transmission (e.g., a PUSCH scheduled by the DCI) using the transceiver 1610. For example, the first UL transmission may use a precoding scheme (e.g., SRI, TPMI, and / or MCS) indicated in the first DCI.
[0154] At block 1706, the network entity may receive a second UL transmission subsequent to the first UL transmission. The second UL transmission is not scheduled by the first DCI. For example, the communication and processing circuitry 1640 may provide for receiving the second UL transmission (e.g., Fig.11 The second UL transmission may be in a future UL transmission (eg, Fig.11 occurs before an instance of PUSCH 1108).
[0155] The precoding scheme for the second UL transmission may be determined at the UE at least in part based on the first DCI and downlink measurements (e.g., L1 measurements of SSB and / or CSI-RS) before the second UL transmission. In some aspects, the UE may autonomously determine the precoding scheme (e.g., SRI, TPMI, and / or MCS) based on one or more factors. The first factor is the precoding information associated with the first UL transmission scheduled by the first DCI. The second factor is the predicted precoding information associated with the potential UL transmission at the time instance after the second UL transmission (e.g., BS predicted UL parameters 1004). The third factor is the historical uplink precoding information sent by the network entity. The fourth factor is the time difference between the time instance associated with the second UL transmission and the reception time of the first DCI. The fifth factor is the time difference between the time instance associated with the second UL transmission and the time instance associated with the predicted UL transmission.
[0156] In one configuration, the network entity 1600 includes components for performing the UL precoding scheme prediction process described above. In one aspect, the aforementioned components may be Fig.16 The processor 1604 is shown configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.
[0157] Of course, in the above examples, the circuits included in the processor 1604 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to storage in the computer-readable storage medium 1606 or in the computer-readable storage medium 1606. Figure 1 , Figure 2 , Figure 3 , Figure 6 and / or Figure 7 In any other suitable device or component described in any of the foregoing and utilizing, for example, Figures 8 to 14 and / or Fig.17 Instructions of the described processes and / or algorithms.
[0158] Fig.18 1800 is a diagram illustrating an example of a hardware implementation of an exemplary UE 1800 employing a processing system 1814. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1814 including one or more processors 1804. For example, UE 1800 may be such as Figure 1 , Figure 2 , Figure 3 , Figure 5 and / or Figure 6 A UE or scheduled entity illustrated by any one or more of the.
[0159] Processing system 1814 can be used with Fig.16 The illustrated processing system 1614 is substantially the same, including a bus interface 1808, a bus 1802, a memory 1805, a processor 1804, and a computer-readable medium 1806. In addition, the UE 1800 may include substantially the same as described above in Fig.16 That is, the processor 1804 as used in the UE 1800 may be used to implement the user interface 1812 and the transceiver 1810 similar to those described in the Figures 8 to 14 and Fig.19 Any one or more of the processes described and illustrated in .
[0160] In some aspects of the present disclosure, processor 1804 may include circuits configured for various functions including, for example, UL pre-coding scheme prediction. For example, the circuits may be configured to implement Figures 8 to 14 and Fig.19 One or more of the functions described.
[0161] In some aspects of the present disclosure, processor 1804 may include communication and processing circuitry 1840 configured for various functions, including, for example, communicating with a network entity (e.g., a base station, gNB, CU, or DU). In some examples, the communication and processing circuitry 1840 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals to be transmitted). For example, the communication and processing circuitry 1840 may include one or more transmit / receive chains. In addition, the communication and processing circuitry 1840 may be configured to send and process uplink traffic and uplink control messages (e.g., similar to Figure 1 The communication and processing circuit 1840 may be configured to receive and process downlink traffic and downlink control messages (e.g., similar to downlink traffic 112 and downlink control 114). The communication and processing circuit 1840 may be further configured to execute communication and processing software 1750 stored on the computer-readable medium 1806 to implement one or more functions described herein.
[0162] In some implementations where the communication involves receiving information, the communication and processing circuitry 1840 may obtain information from a component of the UE 1800 (e.g., from a transceiver 1810 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1840 may output the information to another component of the processor 1804, to the memory 1805, or to the bus interface 1808. In some examples, the communication and processing circuitry 1840 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1840 may receive information via one or more channels. In some examples, the communication and processing circuitry 1840 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1840 may include functionality for components for processing, including components for demodulation, components for decoding, and the like.
[0163] In some implementations where the communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1840 may obtain information (e.g., from another component of the processor 1804, the memory 1805, or the bus interface 1808), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1840 may output the information to the transceiver 1810 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1840 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1840 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1840 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1840 may include functionality for components for generating, including components for modulating, components for encoding, and the like.
[0164] In some aspects of the present disclosure, the processor 1804 may include a UL precoding prediction circuit 1842 configured for various functions, including, for example, predicting UL parameters for use in a precoding scheme for UL transmissions. For example, the UL precoding prediction circuit 1842 may be configured to determine or predict the SRI, TPMI, and / or MCS of future UL transmissions. For example, the UL precoding prediction circuit 1842 may be configured to predict the SRI, TPMI, and / or MCS of future PUSCH using the processes and procedures described herein.
[0165] In one aspect, the UL precoding prediction circuit 1842 may be configured to determine the precoding scheme based on at least one of: 1) precoding information associated with the UL transmission scheduled by the DCI; 2) historical uplink precoding information received from the network entity; 3) a time difference between a time instance associated with the UL transmission and a reception time of the DCI; 4) a time difference between a time instance associated with the UL transmission and a time instance associated with the predicted UL transmission; and 5) downlink measurements. In one aspect, the UE may store the historical uplink precoding information (e.g., precoding history 1820) in the memory 1805. In some examples, the UL precoding prediction circuit 1842 may be further configured to execute the UL precoding scheme prediction software 1852 stored on the computer-readable medium 1806 to implement one or more functions described herein.
[0166] In some aspects of the invention, processor 1804 may include machine learning circuitry 1844 configured for various functions, such as ML techniques for processing data and information. In some examples, machine learning circuitry 1844 may be configured to execute machine learning software 1854 stored on computer-readable medium 1806 to implement one or more functions described herein. In one aspect, machine learning circuitry 1844 may be configured to implement any of the ML techniques described herein for predicting UL parameters or precoding schemes for UL transmissions.
[0167] Fig.19 1 is a flow chart illustrating an exemplary process 1900 for UL precoding scheme prediction according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, process 1900 may be performed by Fig.18 The illustrated UE 1800 performs. In some examples, the process 1900 can be performed by any suitable device or component for performing the functions or algorithms described below.
[0168] At block 1902, the UE may receive a first DCI from a network entity (e.g., a base station, a gNB). For example, the UE may be Figure 1 , Figure 2 , Figure 3 , Figure 6 and / or Figure 7 In one aspect, the communication and processing circuit 1840 may provide a component for receiving the DCI using the transceiver 1810. In one example, the DCI may be DCI 1000, which provides for UL transmissions scheduled by the first DCI (e.g., Fig.11 The first DCI may also provide UL parameters 1002 for future UL transmissions (e.g., Fig.11 The predicted UL parameters 1004 of the first instance of PUSCH 1108).
[0169] At block 1904, the UE may transmit a first UL transmission scheduled by the first DCI. In one example, the communication and processing circuitry 1840 may provide means for transmitting the first UL transmission (e.g., PUSCH) using the transceiver 1810. For example, the UE may transmit the first UL transmission using a precoding scheme (e.g., SRI, TPMI, and / or MCS) indicated in the first DCI.
[0170] At block 1906, the UE may send a second UL transmission subsequent to the first UL transmission. The second UL transmission is not scheduled by the first DCI. For example, the communication and processing circuitry 1940 may provide for using the transceiver 1810 to send the second UL transmission (e.g., Fig.11 The UL precoding prediction circuit may provide a component for determining a precoding scheme for a second UL transmission based at least in part on a first DCI, a downlink measurement (e.g., L1 measurement of SSB and / or CSI-RS) before the second UL transmission, and historical precoding information. In some aspects, the precoding scheme (e.g., SRI, TPMI, and / or MCS) may be based on one or more factors. The first factor is the precoding information associated with the first UL transmission scheduled by the first DCI. The second factor is the predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission. The third factor is the historical uplink precoding information (e.g., precoding history 1820) sent by the network entity. The fourth factor is the time difference between the time instance associated with the second UL transmission and the reception time of the first DCI. The fifth factor is the time difference between the time instance associated with the second UL transmission and the time instance associated with the predicted UL transmission.
[0171] In one aspect, the UL precoding prediction circuit 1842 may provide means for determining predicted UL parameters for the second UL transmission. In one example, the precoding prediction circuit 1842 may use the machine learning circuit 1844 to determine the predicted UL parameters using the ML techniques described herein. In one example, the precoding prediction circuit 1842 may use the analysis techniques described herein to determine the predicted UL parameters.
[0172] In one configuration, the UE 1800 includes components for performing a UL precoding scheme prediction process. In one aspect, the aforementioned components may be Fig.18 The processor 1804 is shown configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means.
[0173] Of course, in the above examples, the circuits included in the processor 1804 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to storage in the computer-readable storage medium 1806 or in the computer-readable storage medium 1806. Figure 1 , Figure 2 , Figure 3 , Figure 6 and / or Figure 7 In any other suitable device or component described in any of the foregoing and utilizing, for example, Figures 8 to 14 and / or Fig.19 Instructions of the described processes and / or algorithms.
[0174] In a first aspect, a method of wireless communication at a UE is disclosed. The method includes: receiving first downlink control information (DCI) from a network entity; sending a first uplink (UL) transmission scheduled by the first DCI; and sending a second UL transmission subsequent to the first UL transmission, the precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
[0175] In a second aspect, alone or in combination with the first aspect, the method further comprises determining the precoding scheme based at least in part on predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission.
[0176] In a third aspect, alone or in combination with any one of the first to second aspects, the determining of the precoding scheme further comprises determining the precoding scheme based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0177] In a fourth aspect, alone or in combination with the first aspect, the method further comprises: determining the precoding scheme using a machine learning (ML) model, the input of the ML model comprising at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0178] In a fifth aspect, either alone or in combination with the first aspect, the method further comprises determining the precoding scheme using at least one of interpolation or extrapolation based on at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0179] In a sixth aspect, either alone or in combination with the first aspect, the method further comprises determining the precoding scheme based at least in part on predicted precoding information included in the first DCI and downlink measurements obtained prior to the second UL transmission.
[0180] In the seventh aspect, alone or in combination with any one of the first aspect, the second aspect, the fourth aspect, the fifth aspect and the sixth aspect, the method also includes: receiving a second DCI for scheduling the second UL transmission; and determining the precoding scheme for the second UL transmission without relying on information provided by the second DCI.
[0181] In an eighth aspect, alone or in combination with any one of the first, second, fourth, fifth and sixth aspects, the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator or a modulation and coding scheme MCS.
[0182] In the ninth aspect, alone or in combination with any one of the first aspect, the second aspect, the fourth aspect, the fifth aspect and the sixth aspect, the method also includes at least one of the following: sending a request to the network entity to stop the process for predicting the precoding scheme; or receiving a command from the network entity to start or stop the process for predicting the precoding scheme.
[0183] In a tenth aspect, a user equipment (UE) for wireless communication is disclosed. The UE includes: a transceiver for wireless communication; a memory; and a processor, the processor being coupled to the transceiver and the memory. The processor and the memory are configured to: receive first downlink control information (DCI) via the transceiver; send a first uplink (UL) transmission scheduled by the first DCI via the transceiver; and send a second UL transmission subsequent to the first UL transmission via the transceiver, the precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
[0184] In an eleventh aspect, either alone or in combination with the tenth aspect, the processor and the memory are further configured to determine the precoding scheme based at least in part on predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission.
[0185] In the twelfth aspect, alone or in combination with any one of the tenth to eleventh aspects, the processor and the memory are further configured to determine the precoding scheme based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0186] In the thirteenth aspect, alone or in combination with the tenth aspect, the processor and the memory are further configured to determine the precoding scheme using a machine learning (ML) model, the input of the ML model including at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0187] In a fourteenth aspect, alone or in combination with the tenth aspect, wherein the processor and the memory are further configured to determine the precoding scheme using at least one of interpolation or extrapolation based on at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or a downlink measurement.
[0188] In the fifteenth aspect, alone or in combination with the tenth aspect, the processor and the memory are further configured to: determine the precoding scheme based at least in part on predicted precoding information included in the first DCI and downlink measurements obtained before the second UL is sent.
[0189] In the sixteenth aspect, alone or in combination with any one of the tenth aspect, the eleventh aspect, the thirteenth aspect, the fourteenth aspect and the fifteenth aspect, wherein the processor and the memory are further configured to: receive a second DCI configured to schedule the second UL transmission; and determine the precoding scheme of the second UL transmission without relying on information provided by the second DCI.
[0190] In the seventeenth aspect, alone or in combination with any one of the tenth aspect, the eleventh aspect, the thirteenth aspect, the fourteenth aspect and the fifteenth aspect, wherein the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator or a modulation and decoding scheme.
[0191] In the eighteenth aspect, alone or in combination with any one of the tenth aspect, the eleventh aspect, the thirteenth aspect, the fourteenth aspect and the fifteenth aspect, wherein the processor and the memory are further configured to perform at least one of the following: sending a request to stop the process for predicting the pre-decoding scheme; or receiving a command to start or stop the process for predicting the pre-decoding scheme.
[0192] In a nineteenth aspect, a method of wireless communication at a network entity is disclosed. The method includes: transmitting first downlink control information (DCI); receiving a first uplink (UL) transmission scheduled by the first DCI; and receiving a second UL transmission subsequent to the first UL transmission, the precoding scheme of the second UL transmission being determined at a user equipment (UE) at least in part based on the first DCI and a downlink measurement prior to the second UL transmission.
[0193] In the twentieth aspect, alone or in combination with the nineteenth aspect, wherein the precoding scheme is based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; historical uplink precoding information sent by the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; or a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission.
[0194] In aspect 21, alone or in combination with any one of aspect 19 and aspect 20, the method further includes: sending a second DCI scheduling the second UL transmission without providing information in the second DCI for determining the precoding scheme for the second UL transmission.
[0195] In the twenty-second aspect, alone or in combination with any one of the nineteenth and twentieth aspects, the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme.
[0196] In the twenty-third aspect, alone or in combination with any one of the nineteenth and twentieth aspects, the method further includes at least one of: receiving a request to stop the process for predicting the precoding scheme; or sending a command to start or stop the process for predicting the precoding scheme.
[0197] In aspect 24, alone or in combination with any one of aspect 19 and aspect 20, the method further includes at least one of: sending information about the association between downlink reference signal resources and uplink reference signal resources for predicting the precoding scheme; or sending information about the association between downlink reference signal resources and a machine learning model configured for predicting the precoding scheme.
[0198] In a twenty-fifth aspect, a network entity for a communication network is disclosed. The network entity includes a memory and a processor coupled to the memory. The processor and the memory are configured to: send a first downlink control information (DCI); receive a first uplink (UL) transmission scheduled by the first DCI; and receive a second UL transmission after the first UL transmission, wherein a precoding scheme of the second UL transmission is determined at a user equipment (UE) at least in part based on the first DCI and a downlink measurement before the second UL transmission.
[0199] In aspect 26, alone or in combination with aspect 25, wherein the precoding scheme is based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; historical uplink precoding information sent by the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; or a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission.
[0200] In aspect 27, alone or in combination with any one of aspect 25 and aspect 26, the processor and the memory are further configured to: send a second DCI configured to schedule the second UL transmission without providing information in the second DCI for determining the precoding scheme for the second UL transmission.
[0201] In the twenty-eighth aspect, alone or in combination with any one of the twenty-fifth and twenty-sixth aspects, the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme.
[0202] In aspect twenty-ninth, alone or in combination with any one of aspect twenty-fifth and aspect twenty-sixth, wherein the processor and the memory are further configured to perform at least one of: receiving a request to stop the process for predicting the pre-decoding scheme; or sending a command to start or stop the process for predicting the pre-decoding scheme.
[0203] In the thirtieth aspect, alone or in combination with any one of the twenty-fifth and twenty-sixth aspects, the processor and the memory are configured to perform at least one of the following: sending information about the association between downlink reference signal resources and uplink reference signal resources for predicting the precoding scheme; or sending information about the association between downlink reference signal resources and a machine learning model configured to predict the precoding scheme.
[0204] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.
[0205] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
[0206] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly, and are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).
[0207] Figures 1 to 19 One or more of the illustrated components, steps, features, and / or functions may be rearranged and / or combined into a single component, step, feature, or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 19 The illustrated apparatus, devices and / or components may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.
[0208] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of the various steps in an example order, but are not meant to be limited to the specific order or hierarchy given unless explicitly stated herein.
[0209] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. A phrase referring to "at least one" in a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly recited in the claims, anything disclosed herein is not intended to be disclosed to the public.
Claims
1. A method for wireless communication at a user equipment (UE), the method comprising: receiving first downlink control information (DCI) from a network entity; Sending a first uplink (UL) transmission scheduled by the first DCI; as well as A second UL transmission is transmitted subsequent to the first UL transmission, a precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
2. The method according to claim 1, further comprising: The precoding scheme is determined based at least in part on predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission.
3. The method of claim 2, wherein the determining the precoding scheme further comprises determining the precoding scheme based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
4. The method according to claim 1, further comprising: The precoding scheme is determined using a machine learning (ML) model, the input of the ML model comprising at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
5. The method according to claim 1, further comprising: The precoding scheme is determined using at least one of interpolation or extrapolation based on at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
6. The method according to claim 1, further comprising: The precoding scheme is determined based at least in part on predicted precoding information included in the first DCI and downlink measurements obtained prior to the second UL transmission.
7. The method according to claim 1, further comprising: receiving a second DCI for scheduling the second UL to send; as well as The precoding scheme for the second UL transmission is determined independently of information provided by the second DCI.
8. The method of claim 1, wherein the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme (MCS).
9. The method according to claim 1, further comprising at least one of the following: sending a request to the network entity to stop a process for predicting the precoding scheme; or A command is received from the network entity to start or stop the process for predicting the precoding scheme.
10. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: transceivers for wireless communications; Memory; and a processor coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receiving, via the transceiver, first downlink control information (DCI); transmitting, via the transceiver, a first uplink (UL) transmission scheduled by the first DCI; and A second UL transmission subsequent to the first UL transmission is transmitted via the transceiver, a precoding scheme of the second UL transmission being determined at least in part based on the first DCI.
11. The UE according to claim 10, wherein the processor and the memory are further configured to: The precoding scheme is determined based at least in part on predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission.
12. The UE of claim 11, wherein the processor and the memory are further configured to determine the precoding scheme based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
13. The UE according to claim 10, wherein the processor and the memory are further configured to: The precoding scheme is determined using a machine learning (ML) model, the input of the ML model comprising at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
14. The UE according to claim 10, wherein the processor and the memory are further configured to: The precoding scheme is determined using at least one of interpolation or extrapolation based on at least one of: predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; precoding information associated with the first UL transmission scheduled by the first DCI; historical uplink precoding information received from a network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; a time difference between a time instance associated with the second UL transmission and a time instance associated with a predicted UL transmission; or Downlink measurements.
15. The UE according to claim 10, wherein the processor and the memory are further configured to: The precoding scheme is determined based at least in part on predicted precoding information included in the first DCI and downlink measurements obtained prior to the second UL transmission.
16. The UE according to claim 10, wherein the processor and the memory are further configured to: receiving a second DCI configured to schedule the second UL transmission; and The precoding scheme for the second UL transmission is determined independently of information provided by the second DCI.
17. The UE of claim 10, wherein the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme.
18. The UE of claim 10, wherein the processor and the memory are further configured to perform at least one of the following: sending a request to stop a process for predicting the precoding scheme; or A command is received to start or stop the process for predicting the precoding scheme.
19. A method for wireless communication at a network entity, the method comprising: Sending first downlink control information (DCI); receiving a first uplink (UL) transmission scheduled by the first DCI; as well as A second UL transmission is received subsequent to the first UL transmission, the precoding scheme of the second UL transmission being determined at a user equipment (UE) based at least in part on the first DCI and downlink measurements prior to the second UL transmission.
20. The method of claim 19, wherein the precoding scheme is based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; Historical uplink precoding information sent by the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; or A time difference between a time instance associated with the second UL transmission and a time instance associated with the predicted UL transmission.
21. The method according to claim 19, further comprising: A second DCI scheduling the second UL transmission is transmitted without providing information for determining the precoding scheme for the second UL transmission in the second DCI.
22. The method of claim 19, wherein the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme.
23. The method of claim 19, further comprising at least one of the following: receiving a request to stop a process for predicting the precoding scheme; or A command is sent to start or stop the process for predicting the precoding scheme.
24. The method of claim 19, further comprising at least one of the following: transmitting information on association between downlink reference signal resources and uplink reference signal resources for predicting the precoding scheme; or Information about an association between downlink reference signal resources and a machine learning model configured to predict the precoding scheme is sent.
25. A network entity for a communication network, the network entity comprising: Memory; and a processor coupled to the memory, wherein the processor and the memory are configured to: Sending first downlink control information (DCI); receiving a first uplink (UL) transmission scheduled by the first DCI; and A second UL transmission is received subsequent to the first UL transmission, the precoding scheme of the second UL transmission being determined at a user equipment (UE) based at least in part on the first DCI and downlink measurements prior to the second UL transmission.
26. The network entity of claim 25, wherein the precoding scheme is based on at least one of: precoding information associated with the first UL transmission scheduled by the first DCI; predicted precoding information associated with a potential UL transmission at a time instance after the second UL transmission; Historical uplink precoding information sent by the network entity; a time difference between a time instance associated with the second UL transmission and a reception time of the first DCI; or A time difference between a time instance associated with the second UL transmission and a time instance associated with the predicted UL transmission.
27. The network entity of claim 25, wherein the processor and the memory are further configured to: A second DCI configured to schedule the second UL transmission is transmitted without providing information for determining the precoding scheme for the second UL transmission in the second DCI.
28. The network entity of claim 25, wherein the precoding scheme comprises at least one of: an SRS resource indicator, a transmit precoder matrix indicator, or a modulation and coding scheme.
29. The network entity of claim 25, wherein the processor and the memory are further configured to perform at least one of the following: receiving a request to stop a process for predicting the precoding scheme; or A command is sent to start or stop the process for predicting the precoding scheme.
30. The network entity of claim 25, wherein the processor and the memory are further configured to perform at least one of the following: transmitting information on association between downlink reference signal resources and uplink reference signal resources for predicting the precoding scheme; or Information about an association between downlink reference signal resources and a machine learning model configured to predict the precoding scheme is sent.
