Method and apparatus for performing beam management based on uplink reference signal
The method and apparatus for UL reference signal-based beam management in wireless communication systems improve signal transmission distance and coverage by optimizing beam configurations, addressing path loss and atmospheric absorption in 6G terahertz band operations.
Patent Information
- Application Number
- KR1020227039033
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-03-26
- Filing Date
- 2021-04-06
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2041-04-06
AI Technical Summary
There is a need for effective beam management using uplink reference signals in wireless communication systems, particularly in the context of 6G communication systems operating in the terahertz band, to address challenges such as path loss and atmospheric absorption, which affect signal transmission distance and coverage.
A method and apparatus for UL reference signal-based beam management, involving UE and BS operations, including receiving and transmitting UL reference signals, measuring signal quality metrics, and updating beam configurations based on these metrics to optimize beam management.
Enhances signal transmission distance and coverage in wireless communication systems by optimizing beam management, thereby supporting high data rates and low latency required for 6G applications.
Smart Images

Figure R1020227039033_ABST
Abstract
Description
Technology Field
[0001] The present disclosure generally relates to wireless communication systems, and more specifically, the present disclosure relates to uplink (UL) reference signal-based beam management. Background Technology
[0002] Considering the evolution of wireless communication from generation to generation, technologies have primarily advanced for services targeting humans, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th-generation) communication systems, the number of connected devices is expected to increase exponentially. Increasingly, these will be connected to communication networks. Examples of connected objects may include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. Efforts are underway to develop improved 6G communication systems to provide diverse services by connecting hundreds of billions of devices and objects in the 6G (6th-generation) era. For these reasons, 6G communication systems are referred to as beyond-5G systems.
[0003] 6G communication systems, which are expected to be commercialized around 2030, will have a peak data rate of tera (1,000 gigabit) level bps and radio latency of less than 100 μsec, and thus will be 50 times faster and have 1 / 10 radio latency than 5G communication systems.
[0004] To achieve such high data rates and ultra-low latency, the implementation of 6G communication systems in the terahertz band (e.g., 95 GHz to 3 THz bands) is being considered. Due to path loss and atmospheric absorption in terahertz bands being more severe than those in the mmWave bands introduced in 5G, technologies capable of securing signal transmission distance (in other words, coverage) are expected to become more critical. As key technologies for securing coverage, it is necessary to develop radio frequency (RF) elements, antennas, novel waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming, and multi-antenna transmission technologies such as multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas. Additionally, discussions are underway regarding new technologies to improve the coverage of terahertz band signals, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS).
[0005] Furthermore, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology to enable uplink and downlink transmissions to simultaneously use the same frequency resources at the same time; network technology for integrated use of satellites, high-altitude platform stations (HAPS), etc.; improved network architecture to support mobile base stations, etc., and enable network operation optimization and automation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by utilizing AI from the design phase to develop 6G and internalize end-to-end AI support functions; and next-generation distributed computing technology to overcome limitations in user equipment (UE) computing capabilities through reachable ultra-high-performance communication and computing resources across the network (e.g., mobile edge computing (MEC), clouds, etc.). Additionally, attempts are being made to strengthen connections between devices, optimize networks, promote the softwareization of network entities, and increase the openness of wireless communications by designing new protocols to be used in 6G communication systems, developing mechanisms to implement hardware-based security environments and secure use of data, and developing technologies to maintain privacy.
[0006] Research and development of 6G communication systems in hyper-connectivity, including not only P2M (person to machine) but also M2M (machine to machine), is expected to enable the next hyper-connected experience. In particular, services such as truly immersive XR (extended reality), high-fidelity mobile holograms, and digital cloning are expected to be provided through 6G communication systems. Additionally, services such as remote surgery for enhanced security and reliability, industrial automation, and emergency response will be provided through 6G communication systems, enabling technologies to be applied in various fields such as industry, healthcare, automotive, and home appliances. The problem to be solved
[0007] A method and device for beam management using uplink (UL) reference signals are required. means of solving the problem
[0008] The methods and apparatus are for UL reference signal-based beam management. A method for operating a UE comprises the steps of: receiving UL reference signals for beam management, source reference signals for spatial relationships, and configuration information regarding beam reporting; receiving source reference signals; and measuring a signal quality metric for source reference signals regarding spatial relationships. The method further comprises the steps of: transmitting a beam report based on the measured signal quality metric; and receiving updated configuration information for UL reference signals for beam management in response to the beam report. The method further comprises the steps of: determining a time for updating UL reference signals for beam management; and transmitting UL reference signals for beam management based on the updated configuration information at the determined time. Brief explanation of the drawing
[0009] For a more complete understanding of the present disclosure and its merits, the following description, taken in conjunction with the accompanying drawings in which similar reference numbers denote similar parts, will now be mentioned, among which: FIG. 1 illustrates an exemplary wireless network according to embodiments of the present disclosure; FIG. 2 illustrates an exemplary gNB according to embodiments of the present disclosure; FIG. 3 illustrates an exemplary UE according to embodiments of the present disclosure; FIGS. 4 and 5 illustrate exemplary wireless transmission and reception paths according to the present disclosure; FIG. 6a illustrates an example of a beam in a wireless system according to embodiments of the present disclosure; FIG. 6b illustrates an exemplary multi-beam operation according to embodiments of the present disclosure; FIG. 7 illustrates an exemplary antenna structure according to embodiments of the present disclosure; FIG. 8 illustrates an exemplary DL multibeam operation according to embodiments of the present disclosure; FIG. 9 illustrates another exemplary DL multibeam operation according to embodiments of the present disclosure; FIG. 10 illustrates an exemplary UL multibeam operation according to embodiments of the present disclosure; FIG. 11 illustrates another exemplary UL multibeam operation according to embodiments of the present disclosure; FIG. 12 illustrates an exemplary multipath environment according to embodiments of the present disclosure; FIGS. 13a, 13b, 13c, 13d, and 13e illustrate exemplary beam measurement reports according to embodiments of the present disclosure; FIG. 14a illustrates the configuration of a sounding reference signal (SRS) resource set according to embodiments of the present disclosure; FIG. 14b illustrates an example of the configuration of a demodulation reference signal (DMRS) port supergroup according to embodiments of the present disclosure; FIG. 15a illustrates a semi-permanent SRS resource set according to embodiments of the present disclosure; FIG. 15b illustrates a periodic SRS resource set according to embodiments of the present disclosure; FIG. 16 illustrates a set of SRS resources transmitted after a PUSCH (physical uplink shared channel) and / or PUCCH transmission according to embodiments of the present disclosure; FIG. 17 illustrates an exemplary procedure according to embodiments of the present disclosure; FIG. 18 illustrates an exemplary embodiment of downlink transmission from a BS to a UE according to embodiments of the present disclosure; FIG. 19 illustrates an exemplary multipath environment according to embodiments of the present disclosure; FIGS. 20a and FIGS. 20b illustrate exemplary SRS ports according to embodiments of the present disclosure; FIGS. 21a, 21b, 21c, and 21d illustrate exemplary embodiments of UEs determining specific relationships according to embodiments of the present disclosure; FIG. 22 illustrates an exemplary embodiment of an offset according to embodiments of the present disclosure; and FIG. 23 illustrates an exemplary method for transmitting UL reference signals according to embodiments of the present disclosure. Specific details for implementing the invention
[0010] Fifth-generation (5G) or NR (new radio) mobile communications are recently gaining momentum due to global technological activities regarding various candidate technologies from industry and academia. Candidate enablers for 5G / NR mobile communications include large-scale antenna technologies ranging from legacy cellular frequency bands to high frequencies, new waveforms (e.g., RAT (new radio access technology)) that provide beamforming gain and increased capacity, flexibly accommodate various services / applications with different requirements, and new multiple access schemes that support large-scale connections.
[0011] The present disclosure relates to uplink (UL) reference signal-based beam management.
[0012] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive configuration information for uplink (UL) reference signals for beam management, source reference signals for spatial relationships, and a beam report, and to receive source reference signals. The UE further includes a processor operatively connected to the transceiver. The processor is configured to measure a signal quality metric for source reference signals for spatial relationships. The transceiver is further configured to transmit a beam report based on the measured signal quality metric and, in response to the beam report, receive updated configuration information for UL reference signals for beam management. The processor is further configured to determine a time for updating the UL reference signals for beam management. The transceiver is further configured to transmit UL reference signals for beam management based on the updated configuration information at the determined time.
[0013] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to transmit and transmit configuration information for UL reference signals for beam management, source reference signals for spatial relationships, and a beam report. The BS further includes a processor operatively connected to the transceiver. The processor is configured to determine, in response to the beam report, updated configuration information for UL reference signals for beam management; and to determine the time for updating the UL reference signals for beam management. The transceiver is further configured to transmit updated configuration information for UL reference signals for beam management; and to receive UL reference signals for beam management based on the updated configuration information at the determined time.
[0014] In another embodiment, a method for operating a UE is provided. The method includes the steps of: receiving UL reference signals for beam management, source reference signals for spatial relationships, and configuration information regarding beam reporting; receiving source reference signals; and measuring a signal quality metric for source reference signals regarding spatial relationships. The method further includes the steps of: transmitting a beam report based on the measured signal quality metric; and receiving updated configuration information for UL reference signals for beam management in response to the beam report. The method further includes the steps of: determining a time for updating the UL reference signals for beam management; and transmitting the UL reference signals for beam management based on the updated configuration information at the determined time.
[0015] Other technical features can be easily made clear to a person skilled in the art from the following drawings, descriptions, and claims.
[0016] Before proceeding to the “Description of Specific Details for Carrying Out the Invention” below, it may be advantageous to mention the definitions of specific words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms “transmit,” “receive,” and “communicate,” as well as their derivatives, include both direct and indirect communication. The terms “comprising” and “comprising,” as well as their derivatives, mean inclusion without limitation. The term “or” is inclusive and means “and / or.” The phrase “associated with” as well as its derivatives mean “include,” “contain within,” “interconnect with,” “contain within,” “connect to or with,” “couple to or with,” “communicable with,” “cooperate with,” “interleave,” “juxtapose,” “be close to,” “be associated with,” “have,” “possess the characteristics of,” “have a relationship with,” etc. The term “control unit” means any device, system, or part thereof that controls at least one operation. Such control unit may be implemented in hardware or a combination of hardware, software, and / or firmware. Functions associated with any particular control unit may be local or remote, centralized or distributed. The phrase “at least one of” means that, when used with a list of items, different combinations of one or more of the listed items may be used, and that any single item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
[0017] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and stored on a computer-readable medium. The terms “application” and “program” refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or parts thereof suitable for implementation in suitable computer-readable program code. The phrase “computer-readable program code” includes any type of computer code including source code, object code, and executable code. The phrase “computer-readable medium” includes any type of medium accessible by a computer, such as ROM (read-only memory), RAM (random access memory), hard disk drives, CD (compact disc), DVD (digital video disc), or any other type of memory. “Non-transient” computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transient computer-readable media include media in which data can be permanently stored and media in which data can be stored and later overwritten, such as rewritable optical discs or erasable memory devices.
[0018] Definitions for other specific words and phrases are provided throughout this patent document. Those skilled in the art should understand that, in many but not most cases, these definitions apply to the prior and future uses of the words and phrases defined in this manner.
[0019] An embodiment for the present invention
[0020] FIGS. 1 through 23 discussed below and the various embodiments used in this patent document to illustrate the principles of the present disclosure are merely illustrative and should not be construed as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.
[0021] The following documents are incorporated into this disclosure by reference as fully indicated herein: 3GPP TS 38.211 v16.4.0, "NR; Physical channels and modulation," 3GPP TS 38.212 v16.4.0, "NR; Multiplexing and Channel coding," 3GPP TS 38.213 v16.4.0, "NR; Physical Layer Procedures for Control," 3GPP TS 38.214 v16.0.0, "NR; Physical Layer Procedures for Data," 3GPP TS 38.321 v16.3.0, "NR; Medium Access Control (MAC) protocol specification," and 3GPP TS 38.331 v16.3.1, "NR; Radio Resource Control (RRC) Protocol Specification."
[0022] Efforts have been made to develop and deploy improved 5th generation (5G) or pre-5G / NR communication systems to meet the demand for increased wireless data traffic following the deployment of 4th generation (4G) communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE (long term evolution) systems."
[0023] 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as 28 GHz or 60 GHz bands, to achieve higher data rates, or in lower frequency bands such as 6 GHz to enable robust coverage and mobility support. To reduce signal loss and increase transmission distance, beamforming, massive MIMO (multiple-input multiple-output), FD-MIMO (Full Dimensional MIMO), array antennas, analog beamforming, and massive antenna techniques are discussed in 5G communication systems.
[0024] Additionally, in 5G communication systems, development is underway to improve system networks based on next-generation small cells, cloud RANs (Radio Access Networks), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving networks, cooperative communication, coordinated multi-points (CoMP), receiver interference cancellation, etc.
[0025] The discussion of 5G systems and the frequency bands associated with them is for reference only, as specific embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or the frequency bands associated with them, and embodiments of the present disclosure may be used in relation to any frequency band. For example, aspects of the present disclosure may also be applicable to the development of later releases that may use 5G communication systems, 6G, or terahertz (THz) bands.
[0026] FIGS. 1 through 3 below illustrate various embodiments implemented in wireless communication systems and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions in FIGS. 1 through 3 are not intended to imply physical or configurational limitations in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably aligned communication system.
[0027] FIG. 1 illustrates an exemplary wireless network (100) according to embodiments of the present disclosure. The embodiment of the wireless network (100) illustrated in FIG. 1 is for illustrative purposes only. Other embodiments of the wireless network (100) may be used without departing from the scope of the present disclosure.
[0028] As illustrated in FIG. 1, a wireless network may include a gNB (101) (e.g., a base station (BS)), a gNB (102), and a gNB (103). The gNB (101) communicates with the gNB (102) and the gNB (103). The gNB (101) also communicates with at least one network (130), such as the Internet, a proprietary Internet Protocol (IP) network, or another data network.
[0029] The gNB (102) provides wireless broadband access to the network (130) to a plurality of first user devices (UEs) within the coverage area (120) of the gNB (102). The plurality of first UEs include a UE (111) that may be located in a small business location; a UE (112) that may be located in a large business location (E); a UE (113) that may be located in a WiFi hotspot (HS); a UE (114) that may be located in a first residence (R); a UE (115) that may be located in a second residence (R); and a UE (116) that may be a mobile device (M), such as a cell phone, a wireless laptop, a wireless PDA, etc. The gNB (103) provides wireless broadband access to the network (130) to a plurality of second UEs within the coverage area (125) of the gNB (103). The plurality of second UEs include UE (115) and UE (116). In some embodiments, one or more of the gNBs (101–103) can communicate with each other and with the UEs (111–116) using 5G / NR, LTE (long term evolution), LTE-A (long term evolution-advanced), WiMAX, WiFi, or other wireless communication techniques.
[0030] Depending on the network type, the terms “base station” or “BS” may refer to any component (or a collection of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), enhanced base station (eNodeB or eNB), 5G / NR base station (gNB), macrocell, femtocell, WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access according to one or more wireless communication protocols, e.g., 5G / NR 3GPP NR, LTE, LTE-A, HSPA (high speed packet access), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Additionally, depending on the network type, the terms "user equipment" or "UE" may refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is generally considered to be a mobile device (e.g., a mobile phone or a smartphone) or a base station device (e.g., a desktop computer or a vending machine). For example, the UE may be a mobile phone, a smartphone, a monitoring device, an alarm device, a fleet management device, an asset tracking device, a vehicle, a desktop computer, an entertainment device, an infotainment device, a vending machine, an electric meter, a water meter, a gas meter, a security device, a sensor device, a home appliance, etc.
[0031] The dashed lines indicate the approximate range of the coverage areas (120 and 125), and the coverage areas are drawn as approximate circles for illustrative and illustrative purposes only. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas (120 and 125), may have different shapes, including irregular shapes, depending on the configuration of the gNBs and variations in the wireless environment associated with natural and artificial obstacles.
[0032] As described in more detail below, one or more of the UEs (111–116) include circuitry, programming, or a combination thereof for UL reference signal-based beam management. In certain embodiments, and one or more of the gNBs (101–103) include circuitry, programming, or a combination thereof for UL reference signal-based beam management.
[0033] Although FIG. 1 illustrates one example of a wireless network, various modifications may be made to FIG. 1. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. Additionally, a gNB (101) may communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network (130). Likewise, each gNB (102–103) may communicate directly with the network (130) and provide UEs with direct wireless broadband access to the network (130). Furthermore, the gNBs (101, 102, and / or 103) may provide access to other or additional external networks, such as external telephone networks or other types of data networks.
[0034] FIG. 2 illustrates an exemplary gNB (102) according to embodiments of the present disclosure. The embodiment of the gNB (102) shown in FIG. 2 is for illustrative purposes only, and the gNBs (101 and 103) of FIG. 1 may have the same or similar configurations. However, gNBs are provided in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any specific embodiment of the gNB.
[0035] As illustrated in FIG. 2, the gNB (102) includes a plurality of antennas (205a to 205n), a plurality of RF transceivers (210a to 210n), a transmit (TX) processing circuit (215), and a receive (RX) processing circuit (220). The gNB (102) also includes a control unit / processor (225), a memory (230), and a backhaul or network interface (235).
[0036] RF transceivers (210a–210n) receive incoming RF signals, such as signals transmitted by UEs in the network (100), from antennas (205a–205n). The RF transceivers (210a–210n) down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are transmitted to an RX processing circuit (220), which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuit (220) transmits the processed baseband signals to a control unit / processor (225) for further processing.
[0037] The TX processing circuit (215) receives analog or digital data (e.g., voice data, web data, email, or interactive video game data) from the control unit / processor (225). The TX processing circuit (215) encodes, multiplexes, and / or digitizes the transmitted baseband data to generate processed baseband or IF signals. RF transceivers (210a–210n) receive the transmitted processed baseband or IF signals from the TX processing circuit (215) and up-convert the baseband or IF signals into RF signals transmitted through antennas (205a–205n).
[0038] The control unit / processor (225) may include one or more processors or other processing devices that control the overall operation of the gNB (102). For example, the control unit / processor (225) may control the reception of forward channel signals and the transmission of reverse channel signals by RF transceivers (210a–210n), an RX processing circuit (220), and a TX processing circuit (215) according to widely known principles. The control unit / processor (225) may also support additional functions, such as more advanced wireless communication functions. For example, the control unit / processor (225) may support a BIS (blind interference sensing) process, such as one performed by a BIS algorithm, and decode a received signal that has been subtracted by interference signals. Any of a wide variety of other functions may be supported by the control unit / processor (225) in the gNB (102). In some embodiments, the control unit / processor (225) includes at least one microprocessor or microcontroller.
[0039] The control unit / processor (225) can also execute programs and other processes residing in memory (230), such as an operating system (OS). The control unit / processor (225) can move data into or out of memory (230) as required by the execution process. In certain embodiments, the control unit / processor (225) supports communication between entities such as Web RTC. The control unit / processor (225) can move data into or out of memory (230) depending on the process being executed.
[0040] The control unit / processor (225) is also coupled to a backhaul or network interface (235). The backhaul or network interface (235) allows the gNB (102) to communicate with other devices or systems through a backhaul connection or through a network. The interface (235) may support communications through any suitable wired or wireless connection(s). For example, when the gNB (102) is implemented as part of a cellular communication system (e.g., supporting 5G / NR, LTE, or LTE-A), the interface (235) may allow the gNB (102) to communicate with other gNBs through a wired or wireless backhaul connection. When the gNB (102) is implemented as an access point, the interface (235) may allow the gNB (102) to communicate through a wired or wireless local area network or through a wired or wireless connection to a larger network (e.g., the Internet). The interface (235) includes any suitable structure that supports communications via wired or wireless connections, such as an Ethernet or RF transceiver.
[0041] Although FIG. 2 illustrates one example of a gNB (102), various modifications may be made to FIG. 2. For example, the gNB (102) may include any number of individual components as illustrated in FIG. 2. As a specific example, the access point may include multiple interfaces (235), and the control unit / processor (225) may support routing functions for routing data between different network addresses. As another specific example, although it is illustrated as including a single instance of a TX processing circuit (215) and a single instance of an RX processing circuit (220), the gNB (102) may include multiple instances of each (e.g., one per RF transceiver). Additionally, the various components of FIG. 2 may be combined, further subdivided, or omitted, and additional components may be added as needed.
[0042] FIG. 3 illustrates an exemplary UE (116) according to embodiments of the present disclosure. The embodiment of the UE (116) shown in FIG. 3 is for illustrative purposes only, and the UEs (111–115) of FIG. 1 may have the same or similar configurations. However, UEs are provided in a wide variety of configurations, and FIG. 3 does not limit the scope of the present disclosure to any specific embodiment of the UE.
[0043] As illustrated in FIG. 3, the UE (116) may include an antenna (305), a radio frequency (RF) transceiver (310), a TX processing circuit (315), a microphone (320), and a receive (RX) processing circuit (325). The UE (116) also includes a speaker (330), a processor (340), an input / output (I / O) interface (IF) (345), an input device (350), a display (355), and a memory (360). The memory (360) includes an operating system (OS) (361) and one or more applications (362).
[0044] The RF transceiver (310) receives an incoming RF signal transmitted by the gNB of the network (100) from the antenna (305). The RF transceiver (310) down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to an RX processing circuit (325), which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit (325) transmits the processed baseband signal to a speaker (330) (e.g., for voice data) or a processor (340) (e.g., for web browsing data) for further processing.
[0045] The TX processing circuit (315) receives analog or digital voice data from the microphone (320) or other outgoing baseband data from the processor (340) (e.g., web data, email, or interactive video game data). The TX processing circuit (315) encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver (310) receives the processed baseband or IF signal sent from the TX processing circuit (315) and up-converts the baseband or IF signal into an RF signal transmitted through the antenna (305).
[0046] The processor (340) may include one or more processors or other processing devices and may execute an OS (361) stored in memory (360) to control the overall operation of the UE (116). For example, the processor (340) may control the reception of forward channel signals and the transmission of reverse channel signals by means of an RF transceiver (310), an RX processing circuit (325), and a TX processing circuit (315) according to widely known principles. In some embodiments, the processor (340) includes at least one processor or microcontroller.
[0047] The processor (340) may also execute other processes and programs residing in memory (360), such as processes for beam management. The processor (340) may move data into or out of memory (360) as required by the execution process. In some embodiments, the processor (340) is configured to execute applications (362) based on the OS (361) or in response to signals received from gNBs or operators. The processor (340) is also coupled to an I / O interface (345), which provides the UE (116) with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface (345) is a communication path between these accessories and the processor (340).
[0048] The processor (340) is also coupled to the input device (350) and the display (355). An operator of the UE (116) can input data into the UE (116) using the input device (350). The input device (350) may be a keyboard, touchscreen, mouse, trackball, voice input, or other device that can serve as a user interface to allow a user to interact with the UE (116). For example, the input device (350) may include voice recognition processing to allow a user to input voice commands. In other examples, the input device (350) may include a touch panel, a (digital) pen sensor, a key, or an ultrasonic input device. The touch panel may recognize touch input in at least one scheme, such as, for example, a capacitive scheme, a pressure-sensitive scheme, an infrared scheme, or an ultrasonic scheme.
[0049] The processor (340) is also coupled to the display (355). The display (355) may be a liquid crystal display, a light-emitting diode display, or another display capable of rendering text and / or at least limited graphics from a website, such as.
[0050] The memory (360) is coupled to the processor (340). Part of the memory (360) may include random access memory (RAM), and another part of the memory (360) may include flash memory or other read-only memory (ROM).
[0051] Although FIG. 3 illustrates one example of a UE (116), various modifications may be made to FIG. 3. For example, various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to specific requirements. As a specific example, the processor (340) may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, although FIG. 3 illustrates a UE (116) configured as a mobile phone or smartphone, UEs may be configured to operate as other types of mobile or stationary devices.
[0052] The communication system includes a downlink (DL) referring to transmissions from a base station or one or more transmitting points to UEs, and an uplink (UL) referring to transmissions from UEs to a base station or one or more receiving points.
[0053] A time unit for DL signaling or UL signaling on a cell is referred to as a slot and may contain one or more symbols. A symbol may also serve as an additional time unit. A frequency (or bandwidth (BW)) unit is referred to as a resource block (RB). A single RB contains multiple sub-carriers (SCs). For example, a slot may have a duration of 0.5 milliseconds or 1 millisecond and contain 14 symbols, and an RB may have 12 SCs with an interval between SCs of 15 KHz or 30 KHz, and so on.
[0054] DL signals include data signals carrying information content, control signals carrying DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI through each physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). A PDSCH or PDCCH may be transmitted through a variable number of slot symbols, each containing a single slot symbol. For brevity, the DCI format for scheduling PDSCH reception by the UE is referred to as the DL DCI format, and the DCI format for scheduling physical uplink shared channel (PUSCH) transmission from the UE is referred to as the UL DCI format.
[0055] The gNB transmits one or more types of RS, including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily intended for UEs to perform measurements and provide CSI to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reports (IMRs), CSI Interference Measurement (CSI-IM) resources associated with zero-power CSI-RS (ZP CSI-RS) settings are used. The CSI process involves NZP CSI-RS and CSI-IM resources.
[0056] The UE can determine CSI-RS transmit parameters from the gNB through DL control signaling or higher-layer signaling, such as Radio Resource Control (RRC) signaling. Transmit instances of CSI-RS can be directed by DL control signaling or set by higher-layer signaling. DMRS can be transmitted on the BW of each PDCCH or PDSCH, and the UE can use the DMRS to demodulate data or control information.
[0057] FIG. 4 illustrates an exemplary wireless transmission path according to the present disclosure, and FIG. 5 illustrates an exemplary wireless reception path according to the present disclosure. In the following description, the transmission path (400) of FIG. 4 may be described as being implemented in a gNB (e.g., gNB (102)), whereas the reception path (500) of FIG. 5 may be described as being implemented in a UE (e.g., UE (116)). However, it may be understood that the reception path (500) may be implemented in a gNB and the transmission path (400) may be implemented in a UE. In some embodiments, the reception path (500) is configured to support UL reference signal-based beam management as described in the embodiments of the present disclosure.
[0058] A transmission path (400) as exemplified in FIG. 4 includes a channel coding and modulation block (405), a serial-to-parallel (S-to-P) block (410), an inverse fast Fourier transform (IFFT) block of size N (415), a parallel-to-serial (P-to-S) block (420), a cyclic prefix (CP) addition block (425), and an up-converter (UC) (430). A receiving path (500) as illustrated in FIG. 5 includes a down-converter (DC) (555), a CP removal block (560), a serial-to-parallel (S-to-P) block (565), a size N Fast Fourier Transform (FFT) block (570), a parallel-to-serial (P-to-S) block (575), and a channel decoding and demodulation block (580).
[0059] As illustrated in FIG. 4, the channel coding and modulation block (405) receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding), and modulates the input bits (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a frequency domain modulated symbol sequence. The serial-parallel block (410) converts the serially modulated symbols into parallel data (e.g., demultiplexing) to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB (102) and UE (116). The size N IFFT block (415) then performs an IFFT operation on the N parallel symbol streams to generate time domain output signals. The parallel-to-serial block (420) converts (e.g., multiplexes) parallel time domain output symbols from the size N IFFT block (415) to generate a serial time domain signal. The CP addition block (425) inserts a CP into the time domain signal. The up-converter (430) modulates (e.g. up-converts) the output of the CP addition block (425) to an RF frequency for transmission over a wireless channel. The signal may also be filtered in the baseband before conversion to the RF frequency.
[0060] RF signals transmitted from gNB (102) pass through a wireless channel and arrive at UE (116), and inverse operations for them from gNB (102) are performed at UE (116).
[0061] As illustrated in FIG. 5, a down converter (555) down-converts the received signal to a baseband frequency, and a CP removal block (560) removes the CP to generate a serial time domain baseband signal. A serial-to-parallel block (565) converts the time domain baseband signal into parallel time domain signals. A size N FFT block (570) performs an FFT algorithm to generate N parallel frequency domain signals. A parallel-to-serial block (575) converts the parallel frequency domain signals into a sequence of modulated data symbols. A channel decoding and demodulation block (580) demodulates the modulated symbols and then decodes them to restore the original input data stream.
[0062] Each of the gNBs (101–103) can implement a transmission path (400) as exemplified in FIG. 4, similar to transmissions in the downlink to the UEs (111–116), and a reception path (500) as exemplified in FIG. 5, similar to receptions in the uplink from the UEs (111–116). Likewise, each of the UEs (111–116) can implement a transmission path (400) for transmitting uplink to the gNBs (101–103) and a reception path (500) for receiving downlink from the gNBs (101–103).
[0063] Each of the components in FIGS. 4 and 5 may be implemented using hardware or a combination of hardware and software / firmware. As a specific example, at least some of the components of FIGS. 4 and 5 may be implemented in software, while other components may be implemented by configurable hardware or a combination of software and configurable hardware. For example, the FFT block (570) and the IFFT block (515) may be implemented as configurable software algorithms, wherein the value of size N may be modified according to the implementation example.
[0064] Furthermore, although described as using FFT and IFFT, this is merely an example and should not be construed as limiting the scope of the disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, may be used. It will be understood that the value of the variable N may be any integer (e.g., 1, 2, 3, 4, etc.) for the DFT and IDFT functions, but the value of the variable N may be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.) for the FFT and IFFT functions.
[0065] Although FIGS. 4 and 5 illustrate examples of wireless transmission and reception paths, various modifications may be made to FIGS. 4 and 5. For example, various components in FIGS. 4 and 5 may be combined, further subdivided, or omitted, and additional components may be added according to specific requirements. Additionally, FIGS. 4 and 5 are intended to illustrate examples of types of transmission and reception paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.
[0066] FIG. 6a illustrates an example of a beam in a wireless system (600) according to embodiments of the present disclosure. The example of the beam shown in FIG. 6a is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0067] The wireless system (600) of FIG. 6a includes a beam (601) and a device (604). The device (604) may be similar to a UE (116). The beam (601) from the device (604) may be characterized by a beam direction (602) and a beam width (603). For example, a device (604) having a transmitter transmits RF energy in the beam direction and within the beam width. A device (604) having a receiver receives RF energy coming toward the device in the beam direction and within the beam width. As illustrated in FIG. 6a, since point A (605) is within the beam width of the beam coming from the device (604) and moving in the beam direction, the device at point A can receive from the device (604) and transmit to that device. Since point B (606) is outside the beam width and the direction of the beam (601) from the device (604), the device at point B cannot receive from the device (604) and cannot transmit to that device. Although FIG. 6a illustrates a beam in two dimensions (2D) for illustrative purposes, it will be obvious to those skilled in the art that a beam may exist in three dimensions (3D) where the beam direction and beam width are defined in space.
[0068] FIG. 6b illustrates an exemplary multi-beam operation (650) according to embodiments of the present disclosure. One embodiment of the multi-beam operation (650) illustrated in FIG. 6b is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure. The multi-beam operation (650) of FIG. 6b includes a device similar to the device (604) of FIG. 6a and a plurality of beams similar to the beam (601) of FIG. 6a.
[0069] In a wireless system, a device may transmit and / or receive on multiple beams. This is known as "multibeam operation" and is illustrated in FIG. 6b. Although FIG. 6b is in 2D for illustrative purposes, it may be obvious to those skilled in the art that the beams may be 3D, in which the beams can be transmitted or received in any direction in space.
[0070] Rel.14 LTE and Rel.15 NR support up to 32 CSI-RS antenna ports, which allow an eNB or gNB to be equipped with multiple antenna elements (e.g., 64 or 128). In this case, multiple antenna elements are mapped onto a single CSI-RS port. For mmWave bands, although the number of antenna elements may be greater for a given form factor, the number of CSI-RS ports—which may correspond to the number of digitally precoded ports—tends to be limited due to hardware constraints (such as the feasibility of installing a large number of ADCs / DACs at mmWave frequencies) as exemplified in Fig. 7, which is described in more detail below.
[0071] Although FIGS. 6a and 6b illustrate exemplary beam movements, various modifications may be made to FIGS. 6a and 6b. For example, the width and orientation of the beams may differ.
[0072] FIG. 7 illustrates an exemplary antenna structure (700) according to embodiments of the present disclosure. One embodiment of the antenna structure (700) illustrated in FIG. 7 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure. For example, the antenna structure (700) may exist in a wireless communication device such as, for example, the UE (116) or gNB (102) of FIG. 1.
[0073] In this case, a single CSI-RS port is mapped onto a large number of antenna elements that can be controlled by a bank of analog phase shifters (701). A single CSI-RS port can then correspond to a single sub-array (705) that generates a narrow analog beam through analog beamforming. This analog beam can be configured to sweep over a wider angular range (720) by varying the bank of phase shifters over symbols or subframes. The number of sub-arrays (equal to the number of RF chains) is equal to the number of CSI-RS ports (NCSI-PORT). A digital beamforming unit (710) performs linear coupling over the NNCSI-PORT analog beams to further increase the precoding gain. Although the analog beams are broadband (and thus not frequency-selective), digital precoding can be varied over frequency subbands or resource blocks. Receiver operation can be conceived similarly.
[0074] Because the described system utilizes multiple analog beams for transmission and reception (e.g., after a training duration performed occasionally, one or a few analog beams are selected from a large number), the term “multibeam operation” is used to refer to the entire system aspect. This includes, for illustrative purposes, indicating an assigned DL or UL transmit (TX) beam (also referred to as “beam indication”), measuring at least one reference signal to calculate and perform beam reporting (also referred to as “beam measurement”) and “beam reporting”), and receiving a DL or UL transmit through the selection of the corresponding receive (RX) beam.
[0075] The described system is also applicable to higher frequency bands such as >52.6 GHz. In this case, the system employs analog beams. Due to O2 absorption losses around the 60 GHz frequency (~10 dB additional loss @ 100 m distance), a larger number of narrower analog beams (and thus a larger number of radiators in the array) may be required to compensate for additional path losses.
[0076] In Rel-15 NR, multi-beam operation is primarily designed for a single TRP and a single antenna panel. Therefore, the specification supports beam direction for a single TX beam where the TX beam is associated with the reference RS.
[0077] The DL beam indication and measurement, reference RS may be an NZP (non-zero power) CSI-RS and / or SS / PBCH block (synchronization signal / primary broadcast channel block) or SSB for short, which includes a primary synchronization signal, a secondary synchronization signal, and a PBCH.
[0078] DL beam indication is performed via a transmission configuration indicator (TCI) field in DCI format, which includes an index for one (and only one) assigned reference RS. A set of hypotheses or so-called TCI states is established via upper layer (e.g., RRC) signaling, and when applicable, a subset of those TCI states is selected / activated via MAC control elements (CE) for TCI field code points. For UL beam indication and measurement, the reference RS may be an NZP CSI-RS, SSB, and / or SRS.
[0079] UL beam indication is performed via the SRS resource indicator (SRI) field in DCI format, where the indication is linked to one (and only one) reference RS. The link is established via upper-layer signaling using SpatialRelationInfo upper-layer (e.g., RRC) parameters. Essentially, only one TX beam is indicated to the UE.
[0080] Furthermore, a DL channel designed for beam indication may be used by the NW / gNB to indicate to the UE a TCI state for receivers coupling DL and UL beam indications and / or a TCI state for receivers and transmitters and / or a joint TCI state, and / or an SRI for upcoming DL channel(s) and / or UL channel(s) transmitters.
[0081] Furthermore, the beams of the beam-directing channel can be designed to provide beam coverage wider than the beam coverage for data or control channels, and adjacent beams of the beam-directing channel can be additionally designed to partially overlap to provide more robust coverage in a dynamic multipath environment.
[0082] Furthermore, to change the multipath environment in a distributed and rapid manner, the TCI state of the beam direction channel may consist of multiple beams. The gNB may transmit the TCI direction channel and the UE may receive it over one or more of these beams. Furthermore, when the beam direction channel is intended to be received by a group of UEs, the TCI state of the beam direction channel consists of beams that cover the group of UEs.
[0083] Furthermore, as described in this disclosure, a UE may initiate a beam report or request resources for a beam report. In response to a beam report, the network / gNB may update a set of SRS resources for beam management or update DMRS resources configured for beam management. The update may include a spatial relationship reference RS, or the number of SRS / DMRS ports or SRS / DMRS resources having the same spatial relationship reference RS for beam management.
[0084] Embodiments of the present disclosure describe additional design aspects related to uplink beam management. For example, a UE, such as the UE (116) of FIG. 1, may initiate a beam report and / or request resources for the beam report. To support uplink beam management, the UE may be configured with a set(s) of sounding reference signal (SRS) resources and / or additional demodulation reference signal (DMRS) ports / resources for beam management. In the case of the set(s) of SRS resources, the association between the SRS resources and the reference RS, established, for example, through spatial relationships, as well as the number of SRS resources in the set and the number of SRS ports associated with the SRS resources, may be dynamically updated as channel conditions change, for example, based on the beam report. In the case of DMRS resources for beam management, the DMRS resources may be associated with a PUSCH transmission or a PUCCH transmission, wherein DMRS ports are organized into DMRS port groups and DMRS port groups are organized into DMRS port supergroups. For example, the association between DMRS port groups and reference RS established through spatial relationships, as well as the number of DMRS port groups in a DMRS port supergroup and the number of DMRS ports associated with the DMRS port groups, can be dynamically updated as channel conditions change, for example, based on beam reporting.
[0085] In the following, both frequency division duplexing (FDD) and time division duplexing (TDD) are considered as duplex methods for signaling DL and UL. Although the following exemplary descriptions and embodiments assume orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), the present disclosure may be extended to other OFDM-based transmit waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).
[0086] The present disclosure may consider various components that can be used in conjunction with or combined with each other, or may operate as standalone schemes.
[0087] In the present disclosure, the term “activate” describes the action of a UE receiving and decoding a signal from a network (or gNB) indicating a start time. The start time may be a current or future slot / subframe or symbol, and the exact location is indicated either implicitly or explicitly, or is specified in system operations, or is set by higher layers. Upon successful decoding of the signal, the UE responds according to the instructions provided by the signal. The term “deactivate” describes the action of a UE receiving and decoding a signal from a network (or gNB) indicating a stop time. The stop time may be a current or future slot / subframe or symbol, and the exact location is indicated either implicitly or explicitly, or is specified in system operations, or is set by higher layers. Upon successful decoding of the signal, the UE responds according to the instructions provided by the signal.
[0088] Technical terms such as TCI, TCI states, SpatialRelationInfo, Target RS, Reference RS, and other terms are used for illustrative purposes only and are therefore not prescriptive. Other terms referring to the same functions may also be used.
[0089] "Reference RS" corresponds to a set of characteristics of the DL beam or UL TX beam, such as direction, precoding / beamforming, and the number of ports. For example, in the case of DL, since the UE receives the Reference RS index / ID via a field in the DCI format, for example represented by the TCI status, the UE applies the known characteristics of the Reference RS to the associated DL reception. The Reference RS can be received and measured by the UE (for example, the Reference RS is a downlink signal such as NZP CSI-RS and / or SSB), and the UE can use the result of the measurement to calculate the beam report (in Rel-15 NR, the beam report includes at least one L1-RSRP accompanied by at least one CRI (CSI-RS resource indicator)). Using the received beam report, the NW / gNB can assign a specific DL TX beam to the UE. The Reference RS can also be transmitted by the UE (for example, the Reference RS is an uplink signal such as SRS). Since the NW / gNB receives the reference RS from the UE, the NW / gNB can measure and calculate the information used to assign a specific DL TX beam to the UE. This option is applicable when there is at least a DL-UL beam pair correspondence.
[0090] In other cases, for UL transmissions, the UE may receive a reference RS index / ID in a DCI format that schedules UL transmissions, such as PUSCH transmissions, and then the UE applies the known characteristics of the reference RS to the UL transmissions. The reference RS can be received and measured by the UE (e.g., the reference RS is a downlink signal such as NZP CSI-RS and / or SSB), and the UE can use the result of the measurement to calculate the beam report. The NW / gNB can use the beam report to assign a specific UL TX beam to the UE. This option is applicable when at least a DL-UL beam pair correspondence is maintained. The reference RS can also be transmitted by the UE (e.g., the reference RS is an uplink signal such as SRS or DMRS). The NW / gNB can use the received reference RS to measure and calculate information that the NW / gNB can use to assign a specific UL TX beam to the UE.
[0091] The reference RS can be triggered by the NW / gNB, for example, via the DCI in the case of a non-periodic (AP) RS, or set to a specific time domain behavior such as period and offset in the case of a periodic RS, or a combination of these settings and enable / disable in the case of a semi-permanent RS.
[0092] For mmWave bands (or frequency range 2 (FR2)) or for higher frequency bands (e.g., >52.6 GHz) where multibeam operation is particularly relevant, the transmit / receive process includes a receiver that selects an RX beam for a given TX beam. In the case of DL multibeam operation, the UE selects a DL RX beam for every DL TX beam (corresponding to a reference RS). Therefore, when a DL RS, such as a CSI-RS and / or SSB, is used as a reference RS, the NW / gNB transmits a DL RS to the UE so that the UE can select a DL RX beam.
[0093] In response, the UE measures the DL RS, selects the DL RX beam in the process, and reports beam metrics associated with the quality of the DL RS. In this case, the UE determines TX-RX beam pairs for all configured (DL) reference RSs. Therefore, even if this knowledge is not available to the NW / gNB, the UE can select the DL RX beam from the information obtained from all TX-RX beam pairs when receiving the DL RS associated with the DL TX beam indication from the NW / gNB. Conversely, when a UL RS, such as an SRS and / or DMRS, is used as a reference RS, the NW / gNB triggers or sets the UE to transmit the UL RS (in the case of DL and by reciprocity, this corresponds to the DL RX beam). When the gNB receives and measures the UL RS, it can select the DL TX beam. As a result, TX-RX beam pairs are derived. The NW / gNB can perform this operation for all configured UL RSs either per reference RS or by "beam sweeping" and determine all TX-RX beam pairs associated with all configured UL RSs for the UE for transmission.
[0094] The following two embodiments (A-1 and A-2) are examples of DL multibeam operations utilizing DL-TCI state-based DL beam indication. In the exemplary first embodiment (A-1), a non-periodic CSI-RS is transmitted by the NW / gNB and received / measured by the UE. This embodiment can be used regardless of whether or not there is a UL-DL beam correspondence.
[0095] In an exemplary second embodiment (A-2), a non-periodic SRS is triggered by the NW (or gNB) and transmitted by the UE so that the NW can measure the UL channel quality for the purpose of assigning a DL RX beam. This embodiment may be used when there is at least a UL-DL beam correspondence. Although a non-periodic RS is considered in two examples, a periodic or semi-permanent RS may also be used.
[0096] FIG. 8 illustrates an exemplary DL multi-beam operation (800) according to embodiments of the present disclosure. The embodiment of the UL multi-beam operation (800) illustrated in FIG. 8 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0097] In one example illustrated in FIG. 8 (Example A-1), the DL multibeam operation (800) begins with the gNB / NW signaling a non-periodic CSI-RS (AP-CSI-RS) trigger or instruction to the UE (step 801). This trigger or instruction may be included in the DCI and may instruct the transmission of AP-CSI-RS in the same slot / subframe (time offset of zero) or in a later slot / subframe (time offset of >0). For example, the DCI may be involved in the scheduling of DL reception or UL transmission, and the CSI-RS trigger may be coded either jointly with or separately from the CSI reporting trigger. Upon receiving the AP-CSI-RS transmitted by the gNB / NW (step 802), the UE measures the AP-CSI-RS, calculates and reports a "beam metric" indicating the quality of a specific TX beam hypothesis (step 803). Examples of such beam reports are the CSI-RS resource indicator (CRI), or the SSB resource indicator (SSB-RI) coupled with the associated layer 1-received signal received power (L1-RSRP) / L1-received signal received quality (L1-RSRQ) / L1-signal to interference ratio (L1-SINR) / channel quality indicator (CQI).
[0098] When receiving a beam report from the UE, the gNB / NW may use the beam report to select a DL RX beam for the UE and direct the selection of the DL RX beam using a TCI status field in a DCI format such as the DCI format that schedules PDSCH reception by the UE (step 804). In this case, the value of the TCI status field indicates a reference RS, such as AP-CSI-RS, which represents the DL TX beam selected (by the gNB / NW). Additionally, the TCI status may also indicate a "target" RS, such as a CSI-RS linked to the reference RS, such as AP-CSI-RS. Upon successful decoding of the DCI format providing the TCI status, the UE selects the DL RX beam and performs DL reception, such as PDSCH reception, using the DL RX beam associated with the reference CSI-RS (step 805).
[0099] Alternatively, the gNB / NW may use beam reporting to select a DL RX beam for the UE and direct the selected DL RX beam to the UE using the value of the TCI status field in a DL channel designed for beam directing (step 804). The DL channel designed for beam directing may be UE-specific or for a group of UEs. For example, a UE-specific DL channel may be a PDCCH received by the UE according to the UE-specific search space (USS), while a UE group common DL channel may be a PDCCH received by the UE according to the common search space (CSS). In this case, the TCI status indicates a reference RS, such as AP-CSI-RS, which indicates the DL TX beam selected (by the gNB / NW). Additionally, the TCI status may also indicate a "target" RS, such as a CSI-RS, which is linked to the reference RS, such as AP-CSI-RS. When the purpose-designed DL channel for beam indication with DL-TCI is successfully decoded, the UE selects the DL RX beam and performs DL reception, such as PDSCH reception, using the DL RX beam associated with the reference CSI-RS (step 805).
[0100] In this embodiment (A-1), as described above, the UE selects a DL RX beam using an index of a reference RS, such as AP-CSI-RS, provided through the TCI status field, for example in the DCI format. In this case, the CSI-RS resources set as reference RS resources for the UE, or the DL RS resources, which generally include CSI-RS, SSB, or a combination of both, may be linked (associated) to a "beam metric" report such as CRI / L1-RSRP or L1-SINR.
[0101] FIG. 9 illustrates another exemplary DL multi-beam operation (900) according to embodiments of the present disclosure. The embodiment of the UL multi-beam operation (900) illustrated in FIG. 9 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0102] In another example illustrated in FIG. 9 (Example A-2), the DL multibeam operation (900) begins with the gNB / NW signaling a non-periodic SRS (AP-SRS) trigger or request to the UE (step 901). This trigger may be contained in a DCI format, such as a DCI format that schedules, for example, PDSCH reception or PUSCH transmission. Upon receiving and decoding a DCI format containing an AP-SRS trigger (step 902), the UE transmits an SRS (AP-SRS) to the gNB / NW (at least when beam correspondence exists) so that the NW (or gNB) can measure the UL propagation channel and select a DL RX beam for the UE for DL (step 903).
[0103] The gNB / NW may then indicate the selection of a DL RX beam through the value of the TCI status field in a DCI format, such as the DCI format that schedules the PDSCH reception (step 904). In this case, the TCI status indicates a reference RS, such as an AP-SRS, that indicates the selected DL RX beam. Additionally, the TCI status may also indicate a "target" RS, such as a CSI-RS, that is linked to the reference RS, such as an AP-SRS. When the DCI format providing the TCI status is successfully decoded, the UE performs DL receptions, such as PDSCH reception, using the DL RX beam indicated by the TCI status (step 905).
[0104] Alternatively, the gNB / NW may use the TCI status field in a DL channel designed for beam indication to instruct the UE to select a DL RX beam (step 904). The DL channel designed for beam indication may be UE-specific or for a group of UEs. For example, a UE-specific DL channel may be a PDCCH received by the UE according to USS, while a UE group common DL channel may be a PDCCH received by the UE according to CSS. In this case, the TCI status indicates a reference RS, such as an AP-SRS, indicating the selected DL RX beam. Additionally, the TCI status may also indicate a "target" RS, such as a CSI-RS, linked to the reference RS, such as an AP-SRS. When the DL channel designed for beam indication is successfully decoded with the TCI status, the UE performs a DL reception, such as receiving a PDSCH, with the DL RX beam indicated by the TCI status (step 905).
[0105] In this embodiment (A-2), as described above, the UE selects a DL RX beam based on a UL TX beam associated with a reference RS (AP-SRS) index signaled through the TCI state field.
[0106] Similarly, for UL multi-beam operation, the gNB selects a UL RX beam for every UL TX beam corresponding to a reference RS. Therefore, when a UL RS such as an SRS and / or DMRS is used as a reference RS, the NW / gNB triggers or sets the UE to transmit the UL RS associated with the selection of the UL TX beam. When the gNB receives and measures that UL RS, it selects a UL RX beam. As a result, TX-RX beam pairs are derived. The NW / gNB can perform this operation for all set reference RSs either per reference RS or by "beam sweeping" and determine all TX-RX beam pairs associated with all reference RSs set for the UE.
[0107] Conversely, when a DL RS such as a CSI-RS and / or SSB is used as a reference RS (at least when there is DL-UL beam correspondence or mutuality), the NW / gNB transmits the RS to the UE (for UL and by mutuality, this RS also corresponds to the UL RX beam). In response, the UE measures the reference RS (selecting the UL TX beam in this process) and reports beam metrics associated with the quality of the reference RS. In this case, the UE determines the TX-RX beam pair for all set (DL) reference RSs. Therefore, even if this information is not available to the NW / gNB, upon receiving the reference RS (and thus UL RX beam) instruction from the NW / gNB, the UE can select the UL TX beam from the information regarding all TX-RX beam pairs.
[0108] The following two embodiments (B-1 and B-2) are examples of UL multibeam operations that utilize TCI-based UL beam indications after a network (NW) receives a transmission from a UE. In the exemplary first embodiment (B-1), the NW transmits a non-periodic CSI-RS, and the UE receives and measures the CSI-RS. This embodiment may be used, for example, when there is mutuality between at least the UL and the DL beam pair link (BPL). This condition is referred to as "UL-DL beam correspondence." In the exemplary second embodiment (B-2), the NW triggers a non-periodic SRS transmission from the UE, and the UE transmits an SRS so that the NW (or gNB) can measure the UL channel quality for the purpose of assigning a UL TX beam. This embodiment may be used regardless of whether UL-DL beam correspondence exists. Although non-periodic RS is considered in these two examples, periodic or semi-periodic RS may also be used.
[0109] FIG. 10 illustrates an exemplary UL multi-beam operation (1000) according to embodiments of the present disclosure. The embodiment of the UL multi-beam operation (1000) illustrated in FIG. 10 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0110] In one example illustrated in FIG. 10 (Example B-1), the UL multibeam operation (1000) begins with the gNB / NW signaling an aperiodic CSI-RS (AP-CSI-RS) trigger or instruction to the UE (step 1001). This trigger or instruction may be included in a DCI format, such as a DCI format that schedules PDSCH reception to the UE or PUSCH transmission from the UE, and may be signaled either separately from or in conjunction with the aperiodic CSI request / trigger, and may instruct the transmission of AP-CSI-RS in the same slot (time offset of 0) or in a later slot / subframe (time offset of >0). Upon receiving the AP-CSI-RS transmitted by the gNB / NW (step 1002), the UE measures the AP-CSI-RS and, consequently, calculates and reports a beam metric (indicating the quality of a specific TX beam hypothesis) (step 1003). Examples of such beam reports are CRI or SSB-RI with associated L1-RSRP / L1-RSRQ / L1-SINR / CQI.
[0111] When receiving a beam report from the UE, the gNB / NW may use the beam report to select a UL TX beam for the UE and direct the selection of the UL TX beam using a TCI status field in a DCI format, such as the DCI format that schedules a PUSCH transmission from the UE (step 1004). The TCI status indicates a reference RS, such as AP-CSI-RS, that indicates the UL RX beam selected (by the gNB / NW). Additionally, the TCI status may also indicate a "target" RS, such as an SRS linked to the reference RS, such as AP-CSI-RS. Upon successful decoding of the DCI format indicating the TCI status, the UE selects a UL TX beam and performs a UL transmission, such as a PUSCH transmission, using the UL TX beam associated with the reference CSI-RS (step 1005).
[0112] Alternatively, the gNB / NW may use beam reporting to select a UL TX beam for the UE and direct the UE to select the UL TX beam using the value of the TCI status field in a DL channel designed for beam directing (step 1004). The DL channel designed for beam directing may be UE-specific or for a group of UEs. For example, a UE-specific DL channel may be a PDCCH received by the UE according to USS, while a UE group common DL channel may be a PDCCH received by the UE according to CSS. In this case, the TCI status indicates a reference RS, such as AP-CSI-RS, indicating the UL RX beam selected (by the gNB / NW). Additionally, the TCI status may also indicate a "target" RS, such as an SRS linked to the reference RS, such as AP-CSI-RS. When the purpose-designed DL channel providing beam guidance by the TCI status is successfully decoded, the UE selects the UL TX beam and performs a UL transmission, such as a PUSCH transmission, using the UL TX beam associated with the reference CSI-RS (step 1005).
[0113] In this embodiment (B-1), as described above, the UE selects a UL TX beam based on a derived DL RX beam associated with a reference RS index signaled through the value of the TCI state field. In this case, CSI-RS resources set as reference RS resources for the UE, or DL RS resources including, generally, CSI-RS, SSB, or a combination of both, may be linked (associated) to a "beam metric" report such as CRI / L1-RSRP or L1-SINR.
[0114] FIG. 11 illustrates another exemplary UL multibeam operation (1100) according to embodiments of the present disclosure. The embodiment of the UL multibeam operation (1100) illustrated in FIG. 11 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0115] In another example illustrated in FIG. 11 (Example B-2), the UL multibeam operation (1100) begins with the gNB / NW signaling a non-periodic SRS (AP-SRS) trigger or request to the UE (step 1101). This trigger may be contained in a DCI format, such as a DCI format that schedules PDSCH reception or PUSCH transmission. Upon receiving and decoding a DCI format containing an AP-SRS trigger (step 1102), the UE transmits the AP-SRS to the gNB / NW so that the NW (or gNB) can measure the UL propagation channel and select a DL TX beam for the UE (step 1103).
[0116] The gNB / NW can then use the value of the TCI status field in the DCI format to indicate the selection of the UL TX beam (step 1104). In this case, UL-TCI indicates a reference RS, such as AP-SRS, which indicates the selected UL TX beam. Additionally, the TCI status can also indicate a "target" RS, such as an SRS linked to the reference RS, such as AP-SRS. When the DCI format providing the value for the TCI status is successfully decoded, the UE transmits, for example, PUSCH or PUCCH, using the UL TX beam indicated by the TCI status (step 1105).
[0117] Alternatively, the gNB / NW may instruct the UE to select an UL TX beam using the value of the TCI status field in a DL channel designed for beam indication (step 1104). The DL channel designed for beam indication may be UE-specific or for a group of UEs. For example, a UE-specific DL channel may be a PDCCH received by the UE according to USS, while a UE group common DL channel may be a PDCCH received by the UE according to CSS. In this case, UL-TCI indicates a reference RS, such as AP-SRS, indicating the selected UL TX beam. Additionally, the TCI status may also indicate a "target" RS, such as an SRS linked to the reference RS, such as AP-SRS. When the DL channel designed for beam indication is successfully decoded through the value of the TCI status field, the UE transmits, for example, a PUSCH or PUCCH, using the UL TX beam indicated by the value of the TCI status (step 1105).
[0118] In this embodiment (B-2), as described above, the UE selects a UL TX beam from a reference RS (in this case, SRS) index that is signaled through the value of the TCI status field.
[0119] FIG. 12 illustrates an exemplary multipath environment (1200) according to embodiments of the present disclosure. The multipath environment (1200) includes a UE (1202) that may be similar to any of the UEs of FIG. 1, such as UE (116). The multipath environment (1200) also includes a BS (1204) that may be similar to any of the BSs of FIG. 1, such as BS (102). The multipath environment (1200) illustrated in FIG. 12 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0120] In certain embodiments, the beam is determined by either (i) a TCI state that establishes a quasi-colocation (QCL) relationship between a source reference signal (e.g., SSB and / or CSI-RS) and a target reference signal, or (ii) spatial relationship information that establishes an association with a source reference signal such as an SSB, CSI-RS, or SRS. In either case, the ID of the source reference signal identifies the beam.
[0121] For example, the gNB may transmit reference signals such as synchronization signals / PBCH blocks (SSBs) and / or channel state information reference signals (CSI-RS). Due to the distributed multipath nature of the channel, the UE may receive one or more TX beams from the gNB. Multiple paths between the gNB and the UE may also occur in the case of networks with multiple transmit / receive points (multi-TRP) and / or multiple transmit / receive antenna panels.
[0122] A multipath environment (1200) as illustrated in FIG. 12 includes a first path (1210) having a first downlink reference RS and a second path (1212) having a second downlink reference RS. The reference RS may be an SSB and / or a CSI-RS. The UE may be configured to perform beam measurements and provide a corresponding report by measuring the layer 1 (L1)-RSRP and / or L1-SINR of the reference RS and reporting these measurement results to the gNB. Based on the beam measurement report, the gNB may set the SRS to a spatial relationship mapped to the reference RS, which may be an SSB, a CSI-RS, or an SRS.
[0123] In a variation of FIG. 12, the multipath environment includes a first path from the first TRP and a second multipath from the second TRP, and the first TRP and the second TRP belong to the same cell, that is, have the same physical cell ID (PCI).
[0124] If the UE (1202) report indicates two TX beams (associated with two resource indicators) that exceed a threshold in the beam measurement report, the network / gNB (e.g., BS (1204)) can set up multiple SRS ports in spatial relationship to one or more reference RSs of the reported beams. For example, if the network sets two SRS ports in spatial relationship to the reference RS of beam (1210) and two other SRS ports in spatial relationship to the reference RS of beam (1212), the UE can transmit an SRS beam in spatial relationship to each reference RS on the orthogonal beams for additional channel sounding in UL and / or additional UL beam refinement as illustrated for UL beams (1220 and 1222) in spatial relationship to the reference RS of DL beam (1210), and UL beams (1224 and 1226) in spatial relationship to the reference RS of DL beam (1212).
[0125] Although FIG. 12 illustrates one example of a multipath environment (1200), various modifications may be made to FIG. 12. For example, the multipath environment (1200) may include any number and / or type of gNBs and any number of UEs in any suitable arrangement.
[0126] The following embodiments and examples describe beam measurement reports (Component 1) from the UE to the gNB:
[0127] A beam measurement report from the UE may include the L1-RSRP and / or L1-SINR of the DL reference signals associated with the beam, for example, when the L1-RSRP and / or L1-SINR exceed a threshold, or when the UE is configured to report a specific number of L1-RSRP / L1-SINR measurement results in the beam measurement report. The threshold may be specified in the system operation or, for example, set for the UE by upper layers. The DL reference signals may be SSB and / or CSI-RS.
[0128] In specific embodiments, beam measurement reports are included in a physical uplink shared channel (PUSCH) that is scheduled by the downlink control information (DCI) format in PDCCH transmission.
[0129] For example, a field in the DCI format scheduling the PUSCH triggers a beam measurement report. In another example, the UE autonomously provides a beam measurement report when, for example, measurement results change by a set and / or predetermined threshold, such as 6 dB or 10 dB. In other examples, the PUSCH transmitter includes only a beam indication report and nothing else. In yet another example, the beam indication report is multiplexed in the PUSCH transmitter along with UL-SCH data, and / or UL MAC CEs, and / or other L1 control information.
[0130] In certain embodiments, the beam measurement report is included in a Type 1 configured Grant PUSCH (CG-PUSCH) transmitter.
[0131] For example, beam measurement reports may be configured by higher-level signaling, such as RRC signaling. As another example, the UE autonomously provides beam measurement reports, for example, when measurement results change by a configured and / or predetermined threshold. As another example, the PUSCH transmitter includes only beam indication reports and nothing else. As yet another example, the beam indication reports are multiplexed in the PUSCH transmitter along with UL-SCH data, and / or UL MAC CEs, and / or other L1 control information.
[0132] In certain embodiments, the beam measurement report is included in a Type 2 configured Grant PUSCH transmitter.
[0133] For example, a field in the DCI format that enables Type 2 CG-PUSCH transmission triggers a beam measurement report. As another example, the beam measurement report may be set by higher-level signaling, such as RRC signaling. As yet another example, the UE autonomously provides a beam measurement report, for example, when measurement results change by a set and / or predetermined threshold. As yet another example, the PUSCH transmitter includes only a beam indication report and nothing else. As yet another example, the beam indication report is multiplexed on the PUSCH transmitter with UL-SCH data, and / or UL MAC CEs, and / or other L1 control information.
[0134] In specific embodiments, the UE includes a beam measurement report in the Msg3 PUSCH transmitter of a Type 1 random access procedure.
[0135] For example, the UE may include a beam measurement report in the corresponding field in the UL grant of the random access response (RAR) scheduling the Msg3 PUSCH transmission in response to a corresponding instruction in the system information block. For example, for operation in a given frequency range, such as corresponding to at least mmWave bands, the UE may always include a beam measurement report in the Msg3 PUSCH transmission. For example, the beam measurement report may correspond to the SS / PBCH block that the UE used to receive system information associated with the random access procedure, and may also include beam measurement results for additional SS / PBCH blocks (SSBs) that the UE may have received, such as for one additional SS / PBCH block. The UE may provide L1-RSRP and / or L1-SINR measurements of SSBs that exceed a threshold, wherein each SSB measurement result is identified by a corresponding SSB index.
[0136] In certain embodiments, the UE includes a beam measurement report in the PUSCH transmitter of the MsgA of a Type 2 random access procedure.
[0137] For example, a preamble index may indicate the inclusion of a beam measurement report in the PUSCH transmitter of MsgA. As another example, a field in the PUSCH transmitter of MsgA may indicate the inclusion of a beam measurement report in the PUSCH transmitter of MsgA. As another example, the PUSCH transmitter of MsgA includes only a beam indication report and does not include anything else. As another example, the beam indication report is multiplexed with UL-SCH data and / or UL MAC CEs on the PUSCH transmitter of MsgA. As yet another example, the UE may include a beam measurement report in the PUSCH transmitter of MsgA in response to a corresponding indication in a system information block, and the beam measurement report may be for SSBs as described in the embodiment in which the UE includes a beam measurement report in the Msg3 PUSCH transmitter of a type 1 random access procedure.
[0138] In specific embodiments, the UE includes a beam measurement report in the PUCCH transmitter.
[0139] For example, PUCCH transmission is set up by upper layers, such as by RRC signaling. As another example, PUCCH transmission is set up by upper layers, such as by RRC signaling, and is activated as a semi-permanent transmission by L1 or L2 signaling. As yet another example, PUCCH transmission is set up by upper layers, such as by RRC signaling, and is triggered by Layer 1.
[0140] In specific embodiments, resources for a Beam Measurement Report Request (BMRR) are configured on the UE. When the UE determines that a new beam measurement should be provided to the gNB, for example, when beam measurement results change by a configured and / or predetermined threshold, the UE transmits the BMRR to the gNB. The BMRR may be a PUCCH resource that provides one bit of information from the UE to the gNB, and the UE transmits on the PUCCH resource when requesting resources for the beam measurement report; otherwise, there is no transmission on the PUCCH resource configured for the BMRR. The gNB may schedule a PUCCH transmission to the UE to provide the beam measurement report. Similarly, resources for the BMRR are configured on different beams, i.e., different TCI states or different spatial relationship reference RSs. The UE may select a preferred beam to provide the BMRR to the gNB.
[0141] FIGS. 13a, 13b, 13c, 13d, and 13e illustrate exemplary beam measurement reports according to embodiments of the present disclosure. The beam management reports of FIGS. 13a through 13e are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0142] In certain embodiments, the beam measurement report includes the effect of maximum permissible emission (MPE) in one direction. MPE may reduce transmit power in a specific direction for health and safety reasons. In the following examples, the MPE effect may include any reason why the UE may reduce its transmit power when transmitting on the measured and reported beam.
[0143] For example, MPE can be reported separately for each reported beam direction. As another example, the effect of MPE can be included in the measurement report.
[0144] For example, L1-RSRP or L1-SINR measurement results may be reduced by the same amount as MPE in a specific direction.
[0145] For another example, referring to FIG. 13a, a beam measurement report (1300a) includes up to K beam quantities, wherein each beam quantity includes three elements (a measurement RS indicator (e.g., SSBRI or CRI), a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR), and a beam measurement result or metric that includes MPE effects (e.g., L1-RSRP or L1-SINR)). The maximum number K of beam quantities in the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k of beam quantities included in the beam measurement report is equal to the maximum number K specified by system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k of beam quantities included in the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0146] As another example, a beam measurement report (1300b) as exemplified in FIG. 13b includes two parts. The first part of the beam measurement report (1300b) may include up to K1 beam quantities, each beam quantity including two elements (a measurement RS indicator (e.g., SSBRI or CRI) and a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR). The second part of the beam measurement report (1300b) may include up to K2 (or K - K1) beam quantities, each beam quantity including three elements (a measurement RS indicator (e.g., SSBRI or CRI), a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR), and a beam measurement result or metric that includes MPE effects (e.g., L1-RSRP or L1-SINR)). The maximum number K1 of beam quantities in the first part of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. Note that there is. For example, the number k1 of beam quantities included in the first part of the beam measurement report is equal to the maximum number K1 specified in the system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k1 of beam quantities included in the first part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0147] In one instance, the maximum number K2 of beam quantities in the second part of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k2 of beam quantities included in the second part of the beam measurement report is the same as the maximum number K2 specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k2 of beam quantities included in the second part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0148] Alternatively, in other cases, the maximum number K of beam quantities in the first and second parts of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k of beam quantities included in the first and second parts of the beam measurement report is equal to the maximum number K specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k of beam quantities included in the second part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0149] As another example, a beam measurement report (1300c) as illustrated in FIG. 13c comprises two parts. The first part may comprise up to K1 beam quantities, each beam quantity comprising two elements (a measurement RS indicator (e.g., SSBRI or CRI), a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR). The second part may comprise up to K2 (or K - K1) beam quantities, each beam quantity comprising two elements (a measurement RS indicator (e.g., SSBRI or CRI), a beam measurement result or metric that includes MPE effects (e.g., L1-RSRP or L1-SINR)).
[0150] The maximum number of beam quantities K1 in the first part of the beam measurement report can be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling.
[0151] The number k1 of beam quantities included in the first part of the beam measurement report is equal to the maximum number K1 specified in the system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k1 of beam quantities included in the first part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0152] In one instance, the maximum number K2 of beam quantities in the second part of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k2 of beam quantities included in the second part of the beam measurement report is the same as the maximum number K2 specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k2 of beam quantities included in the second part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0153] Alternatively, in other cases, the maximum number K of beam quantities in the first and second parts of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k of beam quantities included in the first and second parts of the beam measurement report is equal to the maximum number K specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k of beam quantities included in the second part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0154] For other examples, beam measurement reports (1300d) as exemplified in FIG. 13d can be transmitted by a UE, such as the UE (116) of FIG. 1. The first report may include up to K1 beam quantities, each beam quantity comprising two elements (a measured RS indicator (e.g., SSBRI or CRI) and a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR). The second report may include up to K2 (or K - K1) beam quantities, each beam quantity comprising two elements (a measured RS indicator (e.g., SSBRI or CRI) and a beam measurement result or metric that includes MPE effects (e.g., L1-RSRP or L1-SINR)). The maximum number of beam quantities K1 in the first report of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number of beam quantities k1 included in the first report of the beam measurement report is the maximum number specified by system specifications and / or set by RRC signaling and / or MAC CE signaling. Identical to K1, that is, It may be. Alternatively, the number k1 of beam quantities included in the first part of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0155] In one instance, the maximum number K2 of beam quantities in the second report of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k2 of beam quantities included in the second report of the beam measurement report is the same as the maximum number K2 specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k2 of beam quantities included in the second report of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0156] Alternatively, in other cases, the maximum number K of beam quantities in the first and second reports of the beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number k of beam quantities included in the first and second reports of the beam measurement report is equal to the maximum number K specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., It may be. Alternatively, the number k of beam quantities included in the first and second reports of the beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where am.
[0157] For other examples, beam measurement reports (1300e) as exemplified in FIG. 13e can be transmitted by a UE, such as the UE (116) of FIG. 1. A first beam report may include up to K1 beams, each beam quantity comprising two elements (a measured RS indicator (e.g., SSBRI or CRI) and a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR). The first beam report may include a flag indicating that the beam report includes beam quantities that do not include MPE effects. A second beam report may include up to K2 beam quantities, each beam quantity comprising three elements (a measured RS indicator (e.g., SSBRI or CRI), a beam measurement result or metric that does not include MPE effects (e.g., L1-RSRP or L1-SINR), and a beam measurement result or metric that includes MPE effects (e.g., L1-RSRP or L1-SINR)). The second beam report may include a flag indicating that the beam report includes beam quantities with MPE effects and beam quantities without MPE effects. In one example is, and in other examples am.
[0158] The maximum number of beam quantities K and / or K1 and / or K2 in the corresponding beam measurement report may be specified by system specifications and / or set or updated by RRC signaling and / or MAC CE signaling. The number of beam quantities k and / or k1 and / or k2 included in the corresponding beam measurement report is the same as the maximum number K and / or K1 and / or K2 specified in system specifications and / or set by RRC signaling and / or MAC CE signaling, i.e., and / or and / or It may be. Alternatively, the number of beam quantities k and / or k1 and / or k2 included in the corresponding beam measurement report may be indicated to the UE in the beam measurement report or in separate L1 control and / or MAC CE signaling, where and / or and / or am.
[0159] The following embodiments and examples describe the configuration of UL RS resources for beam management (Component 2):
[0160] Refer to FIG. 14a and FIG. 14b for the following embodiments and examples describing the configuration of UL RS resources for beam management. FIG. 14a. FIG. 14a illustrates the configuration of an SRS resource set (1400a) according to embodiments of the present disclosure. FIG. 14b illustrates an example of the configuration of a DMRS port supergroup (1400b) according to embodiments of the present disclosure. The configurations (1400a and 1400b) of FIG. 14a and FIG. 14b are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0161] The network / gNB can configure the UE's SRS resource sets, SRS resources, and SRS ports. An SRS resource set may include one or more SRS resources. An SRS resource may include one or more SRS ports. When the applicability of an SRS resource set, configured by the upper layer parameter "usage," is set to "beam management," one SRS resource from each of the multiple SRS resource sets may be transmitted at a time.
[0162] In specific embodiments, the SRS configuration for SRS-based beam management is extended to support SRS transmission using multiple SRS resources within an SRS resource set. An SRS resource may include multiple SRS ports. Additionally, a spatial relationship reference RS, the number of SRS ports included in the SRS resource, and the number of SRS resources in the SRS resource set may be configured for the UE and updated via MAC-CE signaling and / or L1 control signaling.
[0163] This example may include a network / gNB that sets up an SRS resource set containing multiple SRS resources to a UE via RRC signaling, wherein the SRS resources are set up spatially in relation to a reference RS associated with a DL beam and include multiple SRS ports. FIG. 14a illustrates an example of the setup of an SRS resource set (1407). The SRS resource set includes M SRS resources, e.g., 1404, 1405, and 1406. Each SRS resource includes N SRS ports, e.g., SRS resource 1 (1404) includes SRS ports (1401, 1402, and 1403).
[0164] In a variation, the network / gNB may set multiple SRS resource sets for the UE, the SRS resource sets may include a reference RS associated with a DL beam and a spatial relationship, and may include multiple SRS resources, the SRS resources may include one or multiple SRS ports. In another variation, the spatial relationship may include a reference RS associated with an SRS resource and / or a set of SRS resources.
[0165] The above example may also include the configuration of SRS resources through RRC signaling and may include one or more of the following parameters: time and frequency resource allocation including period, offset, and repetition in the time domain and frequency hopping in the frequency domain, sequence index (e.g., PN sequence or ZC sequence), orthogonal cover in time and / or frequency domains, subcarrier comb, and cyclic shift. The network / gNB configures and updates the spatial relationship reference RS for the UE through (i) RRC signaling, (ii) MAC CE signaling, and / or (iii) L1 control signaling.
[0166] The network / gNB can set and update the number of SRS resources transmitted from the SRS resource set and the number of SRS ports transmitted from the SRS resources for the UE through (i) MAC CE signaling and / or (ii) L1 control signaling.
[0167] As illustrated in FIG. 14a, based on channel conditions, the network / gNB determines to allow the UE to transmit the gray-shaded SRS resources and ports (1401, 1402, 1403, 1408). In this example, the network / gNB may update the number of SRS resources to 2, i.e., SRS resource 1 (1404) and SRS resource 2 (1405), via MAC CE signaling and / or L1 control signaling, and furthermore, the network / gNB directs the UE to N ports for SRS resource 1, e.g., 1401, 1402, and 1403, and 1 port for SRS resource 2, e.g., 1408. This indicates the resources that the UE will transmit from the set of SRS resources. In a variation, the number of SRS ports in the transmitted SRS resources is the same. Here, the network / gNB can set and update the number of SRS resource sets to be transmitted to the UE via (i) MAC CE signaling and / or (ii) L1 control signaling.
[0168] For example, the number of ports in each SRS resource is 1 (i.e., N = 1). The NW / gNB can update / set the number (M1) and / or index of SRS resources for SRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where M1 < M and M1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIG. 1) transmits SRS on all SRS ports of the updated / set SRS resources.
[0169] In another example, the number of ports in each SRS resource is fixed (e.g., N>=1). The NW / gNB can update / set the number (M1) and / or indices of SRS resources for SRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where M1 < M and M1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIG. 1) transmits SRS on all SRS ports of the updated / set SRS resources.
[0170] In another example, the number of SRS resources is 1 (i.e., M = 1). The NW / gNB can update / set the number (N1) and / or index of SRS ports for SRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where N1 < N and N1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIG. 1) transmits SRS on the updated / set SRS ports of the SRS resources.
[0171] In another example, the number of SRS resources is fixed (i.e., M >= 1). The NW / gNB can update / set the number (N1) and / or indices of SRS ports for SRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where N1 < N and N1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIG. 1) transmits SRS on the updated / set SRS ports of the M SRS resources.
[0172] As another example, the number of SRS ports in two SRS resources (from M SRS resources) may be the same or different. Generally, person Let be the number of SRS ports in the i-th SRS resource. Then, Is It may be the same or different from, where am. The set of candidate values for is or or It may be. For example, the NW / gNB may update / set the number (M1) and / or indices of SRS resources for SRS transmission to the UE via MAC CE signaling and / or L1 control signaling.). In response, the UE (e.g., UE (116) in FIG. 1) transmits SRS on all ports of the updated / set SRS resources. As another example, the NW / gNB may update / set the number (M1) and / or indices of SRS resources for SRS transmission via MAC CE signaling and / or L1 control signaling. For the updated / set SRS resource having index i If so, NW / gNB is the number of SRS ports in the i-th SRS resource for SRS transmission ( ) and / or indices may be additionally configured. In response, the UE (e.g., UE (116) of FIG. 1) transmits an SRS on any one of the SRS ports of all updated / configured SRS resources or the configured SRS ports.
[0173] As another example, the gNB may update one or more parameters through a UE-specific DCI format. The parameters may include (i) the number of SRS resources (M1) and / or indices of SRS resources and (ii) the corresponding spatial relationship-based RS or TCI status for each SRS resource. In addition to (i) and (ii), the parameters may include (A) the number of ports of the corresponding SRS ports of the i-th SRS resource for each SRS resource i, if the SRS ports may differ for each SRS resource. ) and / or indices, or (B) the number N of SRS ports and / or any one of the SRS ports may also be included. A UE-specific DCI format may be, for example, a DCI format for beam indication and / or a DCI format for scheduling UL and / or DL transmissions.
[0174] As another example, the gNB may update one or more parameters via a group common DCI format. The parameters may include (i) the number of SRS resources (M1) and / or indices of SRS resources and (ii) the corresponding spatial relationship-based RS or TCI status for each SRS resource. In addition to (i) and (ii), the parameters may include (A) the number of ports of the corresponding SRS ports of the i-th SRS resource for each SRS resource i, if the SRS ports may differ for each SRS resource. ) and / or indices, or (B) the number N of SRS ports and / or any one of the SRS ports. A group common DCI format may include, for example, a DCI format for group common beam indication and / or a DCI format for group common SRS updates.
[0175] For other examples, the gNB may update one or more of the following parameters through the MAC control element. The parameters include (i) the number of SRS resources (M1) and / or the indices of the SRS resources, and (ii) the corresponding spatial relationship-based RS or TCI status for each SRS resource. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding SRS ports of the i-th SRS resource for each SRS resource i, if the SRS ports may differ for each SRS resource. ) and / or indices or (B) the number of SRS ports N and / or any one of the SRS ports also includes.
[0176] As another example, a gNB may update one or more of the following parameters via RRC signaling. The parameters include (i) the number of SRS resources (M1) and / or the indices of the SRS resources, and (ii) the corresponding spatial relationship reference RS or TCI state for each SRS resource. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding SRS ports of the i-th SRS resource for each SRS resource i, if the SRS ports may differ for each SRS resource. ) and / or indices or (B) the number of SRS ports N and / or any one of the SRS ports also includes.
[0177] In certain embodiments, the network / gNB (e.g., the BS (102) of FIGS. 1 and 2) configures DMRS ports for uplink DMRS-based beam management for the UE. The DMRS ports may be associated with PUSCH transmission and / or PUCCH transmission. The uplink DMRS for beam management may be configured instead of or in addition to the SRS. Likewise, the uplink DMRS ports for beam management may be configured instead of or in addition to the DMRS ports for channel estimation. The DMRS ports for beam management may be time-division multiplexed with PUSCH and / or PUCCH transmission.
[0178] This example includes a second DMRS port for beam management and a first DMRS port for beam management that can be time-division multiplexed and / or frequency-division multiplexed and / or code / sequence-division multiplexed. The example also includes a set of N DMRS ports that can form a DMRS port group, wherein the DMRS port group includes a spatial relationship with a reference RS, and N is an integer greater than or equal to 1. The example further includes a set of M DMRS port groups that can form a DMRS port supergroup, where M is an integer greater than or equal to 1. Additionally, the example includes a network / gNB that forms a DMRS supergroup to a UE via RRC signaling, the formation may include the formation of M and N.
[0179] FIG. 14b illustrates a configuration (1400b) of a DMRS port supergroup (1417). The DMRS port supergroup comprises M DMRS port groups, e.g., 1414, 1415, and 1416. Each DMRS port group comprises N DMRS ports, e.g., DMRS port group 1 (1414) comprises DMRS ports (1411, 1412, and 1413). The configuration may also include one or more of the following parameters: time and frequency resource allocation including period, offset, and repetition in the time domain and frequency hopping in the frequency domain; sequence index (e.g., PN sequence or ZC sequence); orthogonal cover in the time and / or frequency domains; subcarrier comb and cyclic shift.
[0180] A network / gNB (e.g., BS (102) of FIGS. 1 and 2) can set and update the spatial relationship reference RS of a DMRS port group to a UE (e.g., UE of FIGS. 1 and 3) through at least one of (i) RRC signaling, (ii) MAC CE signaling, and / or (iii) L1 control signaling.
[0181] A network / gNB (e.g., BS (102) of FIGS. 1 and 2) can set and update the number of DMRS ports transmitted from a DMRS port group and the number of DMRS port groups transmitted from a DMRS port super group to a UE (e.g., UE of FIGS. 1 and 3) through MAC CE signaling and / or L1 control signaling.
[0182] In the example illustrated in FIG. 14b, based on channel conditions, the network / gNB (e.g., BS (102) of FIG. 1 and 2) determines to allow the UE (e.g., UE of FIG. 1 and 3) to transmit the gray-shaded DMRS port groups and DMRS ports (1201, 1202, 1203, 1208). In this example, the network / gNB can set and update the number of DMRS port groups to 2, i.e., DMRS port group 1 (1414) and DMRS port group 2 (1415), to the UE via MAC CE signaling and / or L1 control signaling. Furthermore, the network / gNB directs the UE to N DMRS ports for DMRS port group 1, e.g., 1411, 1412, and 1413, and 1 DMRS port for DMRS port group 2, e.g., 1418. This indicates the resources that the UE will transmit from the DMRS port supergroup. In the variation, the number of DMRS ports in the transmitted DMRS port groups is the same.
[0183] For example, the number of ports in each DMRS port group is 1 (i.e., N = 1). The NW / gNB can update / set the number (M1) and / or index of DMRS port groups for DMRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where M1 < M and M1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on all DMRS ports of the updated / set DMRS port groups.
[0184] For example, the number of ports in each DMRS port group is fixed (i.e., N = 1). The NW / gNB can update / set the number (M1) and / or index of DMRS port groups for DMRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where M1 < M and M1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on all DMRS ports of the updated / set DMRS port groups.
[0185] In another example, the number of DMRS resources is 1 (i.e., M = 1). The NW / gNB can update / set the number (N1) and / or index of DMRS ports for DMRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where N1 < N and N1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on the updated / set DMRS ports of the DMRS port group.
[0186] In another example, the number of DMRS port groups is fixed (i.e., M >= 1). The NW / gNB can update / set the number (N1) and / or index of DMRS ports for DMRS transmission to the UE via MAC CE signaling and / or L1 control signaling, where N1 < N and N1 is either fixed or set (via RRC, MAC CE, or DCI format). In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on the updated / set DMRS ports of the DMRS port groups.
[0187] As another example, the number of DMRS ports in two DMRS port groups (from M DMRS port groups) may be the same or different. Generally, person Let be the number of DMRS ports in the i-th DMRS port group. Then, Is It may be the same or different from, where am. The set of candidate values for is or or It may be. For example, the NW / gNB may update / set the number (M1) and / or indices of DMRS port groups for DMRS transmission to the UE via MAC CE signaling and / or L1 control signaling. In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on all ports of the updated / set DMRS port groups. As another example, the NW / gNB may update / set the number (M1) and / or indices of DMRS port groups for DMRS transmission via MAC CE signaling and / or L1 control signaling. For an updated / set DMRS port group having index i If so, NW / gNB is the number of DMRS ports in the i-th DMRS port group for DMRS transmission ( ) and / or indices may be additionally configured. In response, the UE (e.g., UE (116) of FIGS. 1 and 3) transmits DMRS on all DMRS ports of the updated / configured DMRS port groups or on any one of the configured DMRS ports.
[0188] As another example, the gNB may update one or more of the following parameters via a UE-specific DCI format. The parameters include (i) the number of DMRS port groups (M1) and / or indices of the DMRS port groups and (ii) the spatial relationship-based RS or TCI status corresponding to each DMRS port group. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding DMRS ports in the i-th DMRS port group for each DMRS port group i, if the DMRS ports may differ for each DMRS port group ( ) and / or indices or (B) the number of DMRS ports N and / or any one of the DMRS ports may also be included. A UE-specific DCI format may include, for example, a DCI format for beam indication and / or a DCI format for scheduling UL and / or DL transmissions.
[0189] As another example, the gNB may update one or more of the following parameters via the group common DCI format. The parameters include (i) the number of DMRS port groups (M1) and / or the indices of the DMRS port groups, and (ii) the spatial relationship reference RS or TCI status corresponding to each DMRS port group. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding DMRS ports in the i-th DMRS port group for each DMRS port group i, if the DMRS ports may differ for each DMRS port group ( ) and / or indices or (B) the number of DMRS ports N and / or any one of the DMRS ports may also be included. The group common DCI format may include, for example, a DCI format for group common beam indication and / or a DCI format for group common DMRS updates.
[0190] For other examples, the gNB may update one or more of the following parameters through the MAC control element. The parameters include (i) the number of DMRS port groups (M1) and / or the indices of the DMRS port groups and (ii) the RS or TCI status based on the spatial relationship corresponding to each DMRS port group. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding DMRS ports in the i-th DMRS port group for each DMRS port group i, if the DMRS ports may differ for each DMRS port group ( ) and / or indices or (B) also include the number of DMRS ports N and / or any one of the DMRS ports.
[0191] As another example, the gNB may update one or more of the following parameters via RRC signaling. The parameters include (i) the number of DMRS port groups (M1) and / or the indices of the DMRS port groups, and (ii) the spatial relationship reference RS or TCI status corresponding to each DMRS port group. In addition to (i) and (ii), the parameters include (A) the number of ports of the corresponding DMRS ports in the i-th DMRS port group for each DMRS port group i, if the DMRS ports may differ for each DMRS port group ( ) and / or indices or (B) also include the number of DMRS ports N and / or any one of the DMRS ports.
[0192] The following embodiments and examples describe the transmission of SRS ports (Component 3):
[0193] Refer to FIGS. 15a, FIG. 15b, and FIG. 16 for the following embodiments and examples describing the transmission of SRS ports. FIG. 15a illustrates a semi-permanent SRS resource set (1500a) according to embodiments of the present disclosure. FIG. 15b illustrates a periodic SRS resource set (1500b) according to embodiments of the present disclosure. FIG. 16 illustrates an SRS resource set (1600) transmitted after PUSCH and / or PUCCH transmission according to embodiments of the present disclosure. The examples of FIG. 15a, FIG. 15b, and FIG. 16 are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0194] In certain embodiments, a UE (e.g., the UE of FIG. 1 and FIG. 3) may transmit SRS resources and SRS ports of an SRS resource set(s) according to a configuration similar to that of FIG. 14a and its associated examples described above. A first SRS resource includes a spatial relationship to a first reference RS, and a second SRS resource includes a spatial relationship to a second reference RS. Alternatively, a first SRS resource set includes a spatial relationship to a first reference RS, and a second SRS resource set includes a spatial relationship to a second reference RS.
[0195] For example, the SRS resource set has a resourceType aperiodic. The transmission of the SRS resource set can be triggered by L1 control signaling.
[0196] As another example, the SRS resource set is of resourceType semi-permanent (SP). As described in FIG. 15a, SP-SRS resource set transmission can be activated by MAC CE signaling and / or L1 control signaling, for example, at time (1501) in FIG. 15a. A possible scenario as illustrated in FIG. 15a is that (i) spatial relationship reference RS resources, (ii) the number of transmitted SRS ports of the SRS resources, (iii) the number of transmitted SRS resources of the SRS resource set, and / or (iv) the number of transmitted SRS resource sets are updated after semi-permanent SRS activation at time 1502. After an SRS update latency (1503) corresponding to the time required for the UE to process the SRS update signaling and activate the updated parameters, the updated parameters are applied at time 1504. SRS transmissions (1505) occur before the update, and SRS transmissions (1506) occur after the update. In another example, SP-SRS activation and SRS updates occur at the same time, or substantially at the same time, or are included in the same signaling message.
[0197] As another example, the SRS resource set is resourceType periodic (P). As described in FIG. 15b, the P-SRS resource set can be set by RRC signaling, e.g., 1511 in FIG. 15b. A possible scenario as illustrated in FIG. 15b is that the number of transmitted SRS ports of the spatial relationship reference RS resources and / or SRS resources, and / or the number of transmitted SRS resources of the SRS resource set, and / or the number of transmitted SRS resource sets are updated at time 1512. After an SRS update latency (1513) corresponding to the time required for the UE to process the SRS update signaling and activate the updated parameters, the updated parameters are applied at time 1514. SRS transmissions (1515) occur before the update, and SRS transmissions (1516) occur after the update.
[0198] In another example, SRS resource set(s) are transmitted in association with PUSCH and / or PUCCH transmissions. For example, SRS resource set(s) are transmitted in the same slot as the PUSCH transmission and / or in the same slot as the PUCCH transmission. In one case, the SRS resource set is transmitted after the PUSCH and / or PUCCH transmissions as exemplified in FIG. 16. In another case, the SRS resource set is transmitted before the PUSCH and / or PUCCH transmissions.
[0199] Transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH is enabled or disabled by RRC signaling and / or MAC CE signaling and / or DCI format, and when enabled, continues until disabled. In one variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs when enabled and none of the SRS symbols overlap with a PUSCH symbol or a PUCCH symbol. In a second variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs when enabled and follows the last PUSCH symbol or PUCCH symbol in the slot, as long as there are sufficient sill balls to transmit the SRS resource set. In a third variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs for SRS symbols that do not overlap with a PUSCH symbol or a PUCCH symbol when enabled. In the fourth variation, the transmission of an SRS resource set in the same slot as the PUSCH and / or PUCCH occurs following the last PUSCH symbol or PUCCH symbol, when enabled, such that the number of SRS symbols does not exceed the number of symbols in the SRS resource set and does not exceed the remaining symbols in the slot after the last PUSCH symbol or PUCCH symbol.
[0200] Transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH is triggered by a DCI format, for example, a DCI format that schedules PUSCH for transmission in the same slot as PUSCH, or a DCI format that schedules PDSCH or SPS PDSCH release for transmission in the same slot as PUCCH. In one variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs when enabled and none of the SRS symbols overlap with a PUSCH symbol or a PUCCH symbol. In a second variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs when enabled and follows the last PUSCH symbol or PUCCH symbol in the slot, as long as there are sufficient silballs to transmit the SRS resource set. In a third variation, transmission of an SRS resource set in the same slot as PUSCH and / or PUCCH occurs for SRS symbols that do not overlap with a PUSCH symbol or a PUCCH symbol when enabled. In the fourth variation, the transmission of an SRS resource set in the same slot as the PUSCH and / or PUCCH occurs following the last PUSCH symbol or PUCCH symbol, when enabled, such that the number of SRS symbols does not exceed the number of symbols in the SRS resource set and does not exceed the remaining symbols in the slot after the last PUSCH symbol or PUCCH symbol.
[0201] In certain embodiments, a UE (e.g., the UE of FIG. 1 and FIG. 3) may transmit DMRS ports for beam management and DMRS port groups of DMRS port supergroups by following a configuration similar to that of FIG. 14B and its associated examples described above. A first DMRS port group includes a spatial relationship to a first reference RS, and a second DMRS port group includes a spatial relationship to a second reference RS. A DMRS port supergroup for beam management is transmitted in association with a PUSCH and / or PUCCH transmission. In one example, a DMRS port supergroup for beam management is transmitted after a PUSCH and / or PUCCH transmission. In another example, a DMRS port supergroup for beam management is transmitted before a PUSCH and / or PUCCH transmission.
[0202] The following embodiments and examples describe the configuration of UL transmissions (Component 4) based on SRS measurements:
[0203] The gNB can receive and measure SRS and / or DMRS transmissions from the UE, and the SRS and / or DMRS are transmitted from ports set by the UE. Based on the measured SRS and / or DMRS, and possibly the MPE associated with each SRS or reference RS with which the SRS has a spatial relationship, the gNB can determine the UL SRS port(s) / DMRS port(s), and the UE can use the DL reference RS for the quasi-juxtaposition (QCL) for the UL transmission and for the DL transmission.
[0204] For example, the gNB can signal the SRS port(s) / DMRS port(s) in the DCI format where it schedules a PUSCH transmit. As another example, the gNB can signal or enable the UL SRS port(s) / DMRS port(s) in the MAC CE. As yet another example, the gNB can signal the UL SRS port(s) / DMRS port(s) in the beam direction channel / message.
[0205] In specific embodiments, the gNB may signal SRS port(s) / DMRS port(s) in a DCI format that triggers a PUCCH transmission. For example, if a PUCCH transmission is on one port and multiple SRS ports / DMRS ports are signaled, the PUCCH transmission is on a first SRS port / DMRS port, where the first may refer to the port having the lowest index or the port at the first position within the corresponding configuration message.
[0206] For example, the gNB can signal the reference RS as a QCL source for DL transmission in the DCI format scheduling of PDSCH transmission. As another example, the gNB can signal or enable the reference RS as a QCL source for DL transmission in the MAC CE. As another example, the gNB can signal the reference RS as a QCL source for DL transmission in the beam-indicating channel / message. As another example, the gNB can signal or enable UL SRS port(s) / DMRS port(s) in the MAC CE that can be used by the UE for UL transmissions and DL receptions. As yet another example, the gNB can signal UL SRS port(s) / DMRS port(s) that can be used by the UE for UL transmissions and DL receptions in the beam-indicating channel / message.
[0207] FIG. 17 illustrates an exemplary method (1700) according to embodiments of the present disclosure. The steps of the method (1700) may be performed by any of the UEs (111–116) of FIG. 1, such as the UE (116) of FIG. 3. The steps of the method (1700) may also be performed by any of the BSs (101–103) of FIG. 1, such as the BS of FIG. 2. The embodiments of FIG. 17 are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0208] FIG. 17 illustrates a method (1700) according to examples of the components described above. For convenience of reference, steps (1701–1707) may be performed by any of the BSs (101–103) of FIG. 1 and the BS (102) of FIG. 2. Likewise, steps (1711–1717) may be performed by any of the UEs (111–116) of FIG. 1 and the UE (116) of FIG. 3.
[0209] In step 1701, the upper layers may configure downlink reference signals, such as SSB and / or CSI-RS, to the UE, where an association may be established between the beam (e.g., spatial domain filter) and the ID of the reference RS. Network configuration of the reference signals is provided to the UE in step 1711. The downlink reference signals may provide a Type-D QCL source for downlink channels and signals and a spatial relationship source for uplink channels and signals (e.g., the SRS resource set(s) of step 1702 and / or DMRS port supergroups).
[0210] In step 1702, the upper layers configure the SRS resource set(s) and / or DMRS port supergroups by following the examples of Component 2 above. The network configuration of the SRS resource set(s) and / or DMRS port supergroups is provided to the UE in step 1712.
[0211] In step 1703, the gNB transmits the DL reference RS (e.g., SSB and / or CSI-RS). In step 1713, the UE can measure the DL reference RS, the measurement result of which may include signal strength and / or signal quality as described in Component 1 above.
[0212] In step 1714, the UE provides a measurement report of the DL RS to the gNB in accordance with the example of Component 1 above. The measurement report may also include MPE effects. In step 1704, the gNB receives this report. The UE may measure the DL reference RS at any time based on network configuration or according to UE implementation examples and provide the measurement results to the network / gNB. The measured results may be provided to the network / gNB at a set time and / or when the UE detects a change in channel conditions according to set conditions. In another example, the UE may send a beam measurement report request (BMRR) to the gNB so that UL resources for reporting beam measurements are configured.
[0213] In step 1705, the gNB determines the SRS / DMRS ports / resources to be transmitted by the UE for beam management, and the corresponding reference RS for spatial relationships. This is instructed to the UE according to the examples of Component 2 above. In step 1715, the UE receives these instructions and updates the SRS / DMRS ports / resources accordingly.
[0214] In step 1716, the UE transmits SRS / DMRS ports / resources in accordance with the instructions of step 1715 and following the examples of Component 3 above. In step 1706, the gNB receives and measures the transmitted SRS / DMRS ports / resources. Based on the measured SRS / DMRS ports / resources, the gNB determines the SRS / DMRS ports and the corresponding reference RS as determined by the spatial relationship to be used for the transmission and reception of data and control channels, and signals them to the UE in step 1707 following the examples of Component 4 above. The gNB can monitor the SRS / DMRS ports / resources as transmitted by the UE and, accordingly, update the set of SRS / DMRS ports / resources used for the transmission / reception of data / control channels in the gNB and UE in steps 1707 and 1717. Furthermore, the gNB can update the SRS / DMRS ports / resources in accordance with step 1705.
[0215] In steps 1707 and 1717, the gNB and the UE transmit and receive data and / or control channels according to the indicated SRS / DMRS ports / resources.
[0216] Although FIG. 17 illustrates the method (1700), various modifications may be made to FIG. 17. For example, while the method (1700) of FIG. 17 is illustrated as a series of steps, various steps may overlap, occur in parallel, occur in different order, or occur multiple times. In other examples, steps may be omitted or replaced by other steps. For example, the steps of the method (1700) may be executed in different order. For example, it is possible for the gNB (e.g., BS (102)) to transmit the DL RS (i.e., step 1703) before the gNB provides the upper layer configuration of the SRS resource set to the UE (step 1702). Furthermore, some steps may be executed simultaneously, for example, the UE (e.g., UE (116)) may receive and measure the DL RS in the same slot where the UE transmits the SRS / DMRS ports / resources (i.e., step 1713).
[0217] Embodiments of the present disclosure also describe additional design aspects related to uplink beam management. To support uplink beam management for PUCCH transmissions in response to downlink control information (DCI) formats (e.g., PUCCH transmissions in response to PDSCHs scheduled by DCI formats, or PUCCH transmissions triggered by DCI formats), the UE may assume, for the PUCCH transmission, that the spatial relation reference RS is a source RS having a QCL type-D of the TCI state indicated in the DCI format or a separate DCI format dedicated to TCI state updates, and alternatively, the UE may assume that the uplink Tx spatial filter for the PUCCH transmission is an SRS port (or SRS resource) of an SRS resource (or set of SRS resources) having a spatial relation RS that follows the source RS having a QCL type-D of the TCI state indicated in the DCI format or a separate DCI format dedicated to TCI state updates, wherein the SRS port (or SRS resource) is indicated to the UE.
[0218] To support uplink beam management for PUSCH transmission or PUCCH transmission (e.g., PUSCH transmission scheduled by DCI format) in response to DCI format, the UE may assume that for PUSCH transmission or PUCCH transmission, the spatial relationship reference RS is a source RS having a QCL type D of the TCI state indicated in a separate DCI format dedicated to DCI format or TCI state updates, and alternatively, the UE may assume that the uplink Tx spatial filter for PUCCH transmission is an SRS port (or SRS resource) of an SRS resource (or set of SRS resources) having a spatial relationship RS that follows the source RS having a QCL type D of the TCI state indicated in a separate DCI format dedicated to DCI format or TCI state updates, wherein the SRS port (or SRS resource) is indicated to the UE.
[0219] Additionally, to support uplink beam management for uplink configured transmits or UE initiated transmits (e.g., PUSCH configured grant, periodic PUCCH, semi-permanent PUCCH, or RACH), the UE may assume, for an uplink transmit, that the spatial relationship reference RS is a source RS having a QCL type D of the TCI state indicated in a DCI format or a separate DCI format dedicated to TCI state updates received by the UE prior to the uplink transmit, subject to the UE's processing time limits; alternatively, the UE may assume that the uplink Tx spatial filter for the uplink transmit is an SRS port (or SRS resource) of an SRS resource (or set of SRS resources) having a spatial relationship RS that follows the source RS having a QCL type D of the TCI state indicated in a DCI format or a separate DCI format dedicated to TCI state updates received by the UE prior to the uplink transmit, wherein the SRS port (or SRS resource) is indicated to the UE prior to the uplink transmit and subject to the UE's processing time limits.
[0220] In addition, to support beam management and reduce latency, the UE may indicate a beam indicating a preferred beam in an uplink transmission (e.g., PUSCH or PUCCH). This indication may be made through explicit or implicit signaling. The presence of a beam indication in an uplink transmission may be enabled or disabled through gNB signaling. If the beam is multiplexed with other UL control traffic, a field may indicate the presence or absence of a beam indication; furthermore, if the UL control channel payload exceeds the maximum payload, a field in the uplink transmission may indicate the type of payload included in the uplink transmission.
[0221] The embodiments of the present disclosure take into account that beam management frameworks may differ for different channels. Different beam management frameworks for different channels may increase beam management overhead and lead to less robust beam-based operations. For example, in the case of PUCCH, the spatial relationships of PUCCH resources are updated by MAC CE signaling, which is separate from the framework for updating beam indications of downlink channels. This results in unnecessary overhead and longer latency, which reduces the robustness of beam management. As PUCCH HARQ-ACK (hybrid automatic repeat request-acknowledgement) feedback is associated with downlink PDSCH transmission, a common beam management framework may be used for PDSCH and PUCCH HARQ-ACK with common signaling.
[0222] Additionally, embodiments of the present disclosure consider that new beam information may be known to a network through CSI reporting that includes a CSI-RS resource index (CRI) along with RSRP and / or SINR information or an SSB index along with RSRP information. Such reporting may increase reporting overhead on the uplink and cause some latency. Therefore, to help reduce the overhead and latency of reporting new beams, embodiments of the present disclosure provide a mechanism that includes beam information along with HARQ-ACK information.
[0223] Accordingly, the present disclosure considers design aspects related to uplink beam management in which a source RS having QCL type D of the TCI status in a downlink control information (DCI) format or a separate DCI format dedicated to TCI status updates is a spatial relationship reference RS for an uplink transmission. In one example, the uplink transmission is a PUSCH transmission, a PUCCH transmission, or a PRACH transmission. In another example, the uplink transmission is an SRS transmission in which the PUSCH transmission, PUCCH transmission, or PRACH transmission has the same uplink Tx spatial filter as the SRS port / resource of the SRS transmission, and the SRS port / resource of the SRS transmission is indicated to the UE. Furthermore, the present disclosure considers a beam indication in an uplink PUCCH transmission or PUSCH transmission, the beam indication may be multiplexed with other uplink control information, and the presence of the beam indication field or other uplink control information fields may be indicated by a field in the payload.
[0224] FIG. 18 illustrates an exemplary embodiment (1800) of downlink transmission from a BS to a UE according to embodiments of the present disclosure. The exemplary embodiment (1800) of FIG. 18 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0225] Downlink transmissions on the PDSCH (1801) from the gNB to the UE can be scheduled by downlink assignments transmitted on the PDCCH channel (1802), as illustrated in FIG. 18. Uplink transmissions on the PUCCH channel (1803) from the UE to the gNB carry a HARQ-ACK response for the downlink transmission. Here, the HARQ-ACK response indicates an ACK if the downlink PDSCH channel is successfully received, and a NACK otherwise. Note that the UE of the embodiment (1800) may be any of the UEs (111–116) of FIG. 1, such as the UE (116) of FIG. 1 and FIG. 3. The gNB of the embodiment (1800) may be any of the BSs (101–103) of FIG. 1, such as the BS of FIG. 1 and FIG. 2.
[0226] Downlink assignments on the PDCCH channel may include Transmission Establishment Instruction (TCI) status and PUCCH Resource Indicator (PCI). Note that the Transmission Establishment Instruction (TCI) is a status that determines Type D, where the DMRS and Source Reference Signal (RS) of the PDSCH transmission are quasi-juxtaposed (QCL). Additionally, the PUCCH Resource Indicator (PCI) determines the PUCCH resource for the HARQ-ACK.
[0227] The spatial filter for PUCCH transmission is determined by the spatial relationship with respect to the reference RS. The spatial relationship information is enabled / disabled by the MAC control element (MAC-CE). If a UE (e.g., UE (116)) has a beam correspondence, the UE can determine the spatial filter for transmission to the gNB or the transmission / reception point (TRP) based on the spatial filter used for reception from the gNB / TRP. The UE can determine the spatial filter for the PUCCH TX beam based on the spatial filter used for reception of the PDCCH channel and / or PDSCH channel.
[0228] Uplink transmissions on PUSCH from the UE to the gNB can be scheduled by uplink grants transmitted on the PDCCH channel. The uplink grant includes an SRS resource indicator that establishes a spatial relationship to the reference RS for the PUSCH transmission. By utilizing the UE's beam correspondence, the UE can determine the spatial filter of the PUSCH TX beam based on the spatial filter used for the downlink TCI state used for the downlink channels.
[0229] A UE may be configured with one or more sets of SRS resources. A set of SRS resources includes one or more SRS resources. An SRS resource may have a spatial relationship to a reference RS, such as a Synchronization Signal / PBCH Block (SSB), Channel State Information (CSI)-RS, or other SRS. An SRS resource may include one or more SRS ports. A network may configure a set of SRS resources for beam management. By utilizing beam mapping in the UE, the reference RS of the spatial relationship of an SRS resource or set of SRS resources may follow a source RS having a QCL Type-D of the TCI state, where the SRS ports or SRS resources may provide additional spatial filter refinement on the uplink.
[0230] FIG. 19 illustrates an exemplary multipath environment (1900) according to embodiments of the present disclosure. The embodiment of FIG. 1900 is similar to the embodiment (1200) of FIG. 12. The exemplary multipath embodiment (1900) of FIG. 19 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0231] The multipath environment (1900) includes a UE (1902) that may be similar to any of the UEs of FIG. 1, such as UE (116). The multipath environment (1900) also includes a BS (1904) that may be similar to any of the BSs of FIG. 1, such as BS (102).
[0232] In a variation of FIG. 19, the multipath environment includes a first path from the first TRP and a second multipath from the second TRP, where the first TRP and the second TRP belong to the same cell, that is, have the same physical cell ID (PCI).
[0233] As shown in FIG. 19, is a source RS having QCL type D for TCI state M, and is a source RS with QCL type D for TCI state N. The spatial filter for is 1910, and The spatial filter for is 1912. In UE (1902), the spatial relationship criterion RS SRS resource 0 (1914) having and spatial relationship criterion RS A set of SRS resources is established, including SRS resource 1 (1916) having. SRS resource 0 includes two SRS ports, SRS port 0 (1920) and SRS port 1 (1922), and these ports can provide additional UL beam refinement corresponding to downlink transmissions using TCI state M. Likewise, SRS resource 1 includes two SRS ports, SRS port 0 (1924) and SRS port 1 (1926), and these ports can provide additional UL beam refinement corresponding to downlink transmissions using TCI state M.
[0234] Note that in the following embodiments and examples, two or more overlaps will mean that the transmissions overlap in time (partial overlap or full overlap). In the frequency domain, the transmissions may have separate frequency resources, partially overlapping frequency resources, or fully overlapping frequency resources.
[0235] The following embodiments and examples describe the indication of a TCI state or spatial relationship for UL transmission (Component 5):
[0236] In some of the embodiments and examples described below regarding Component 5, the network / gNB may set SRS resources or sets of SRS resources to the UE that have an association with the TCI state. The spatial relationship reference RS for the SRS resource or set of SRS resources is a source RS having QCL type D of the TCI state. Alternatively, the spatial Tx filter for the SRS resource or set of SRS resources is based on the spatial Rx filter of the TCI state.
[0237] In a variant example, the network / gNB may configure DMRS port groups or DMRS port supergroups in the UE that have an association with the TCI state. The spatial relationship reference RS for the DMRS port group or DMRS port supergroup is a source RS having a TCI state of QCL type D. Alternatively, the spatial Tx filter for the DMRS port group or DMRS port supergroup is based on the spatial Rx filter of the TCI state.
[0238] In certain embodiments (referred to as Example 1.1), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is a spatial relationship reference RS for the corresponding PUCCH transmission.
[0239] In certain embodiments (referred to as Example 1.2), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is the spatial relationship reference RS for an SRS resource (referred to as SRS resource A). The spatial relationship for a corresponding PUCCH transmission may be indicated according to one or more of the following examples.
[0240] For example (shown as Example 1.2.1), the spatial relationship of the PUCCH resource is the spatial relationship of the SRS port included in SRS resource A, where the SRS port index is included in the downlink DCI format or a separate DCI format dedicated to TCI state updates.
[0241] For another example (shown as Example 1.2.2), the spatial relationship of the PUCCH resource is the spatial relationship of the SRS port included in the SRS resource A, and the SRS port index is included in the TCI state signaled in the TCI state update (whether through the DL-related DCI format or through a separate DCI format dedicated to the TCI state update).
[0242] For another example (indicated as Example 1.2.3), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in an SRS resource A, where the SRS port index is included in the PUCCH resource index. Each resource in the PUCCH resource set includes an SRS port index. Table 1 illustrates an example in which a PUCCH resource includes an SRS port index, in which the SRS resource has two SRS port indices. This is illustrated by the example in Table 1.
[0243] Table 1. Set of PUCCH resources having an SRS port index containing PUCCH resources
[0244]
[0245] Note that the size of the PUCCH resource set can be increased to include more resources. For example, the size can be increased to 16 elements, and the PCI index field in the DCI format is increased from 3 bits to 4 bits. In the case of PUCCH format 0, where the size of the PUCCH resource set is 32 and 2 bits are implicitly indicated, or PUCCH format 1, the size of the PUCCH resource set can be increased to 64, meaning that a 4-bit PCI has 2 implicitly indicated bits.
[0246] For another example (indicated as Example 1.2.4), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A, where the SRS port index is implicitly indicated (i.e., the SRS port index can be derived from other signals and / or other system parameter values). For example, the SRS port index can be implicitly indicated based on the start control channel element (CCE) of the corresponding PDDCH. For example, as illustrated in the embodiment (2000a) of FIG. 20a, where there are two SRS ports, a PDCCH with an odd floor (start CCE / aggregation level) uses one SRS port index, while a PDCCH with an even floor (start CCE / aggregation level) uses a different SRS port index. In another example having two SRS ports, as illustrated in the embodiment (2000b) of FIG. 20b, a PDCCH in which the starting CCE is in the first half of the CORESET uses one SRS port index, while a PDCCH in which the starting CCE is in the second half of the CORESET uses another SRS port index. Note that FIG. 20a and FIG. 20b illustrate exemplary SRS ports according to embodiments of the present disclosure. The exemplary embodiments of FIG. 20a and FIG. 20b are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0247] For another example (shown as Example 1.2.5), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A, where the SRS port index is indicated / updated by MAC CE.
[0248] For another example (indicated as Example 1.2.6), the number of SRS ports and / or SRS port indices included in an SRS resource (e.g., SRS resource A) may be updated by upper-level RRC signaling and / or MAC CE signaling and / or L1 control signaling. The size of the corresponding field in the DCI format for indicating the SRS ports may be updated accordingly, or an implicit mapping rule may consider the number of updated SRS ports to include in the implicit mapping for the number of updated SRS ports.
[0249] For another example (indicated as Example 1.2.7), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is the spatial relationship reference RS for the DMRS port group. The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the previous examples, such as Examples 1.2.1 through 1.2.6, where the SRS port is replaced by the DMRS port.
[0250] For another example (indicated as Example 1.2.8), a PUCCH transmission for HARQ-ACK may overlap with another PUCCH transmission in which UL control information other than HARQ-ACK information is included in the PUCCH resource, and the spatial relationship of the PUCCH resource may be determined according to Examples 1.2.1 through 1.2.7.
[0251] For another example (indicated as Example 1.2.9), a PUCCH transmission for HARQ-ACK may overlap with a PUSCH transmission in which HARQ-ACK information is multiplexed on the PUSCH, and the spatial relationship of the PUSCH transmissions may be determined according to Examples 1.2.1 through 1.2.7.
[0252] In certain embodiments (referred to as Example 1.3), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is a spatial relationship reference RS for an SRS resource set (referred to as SRS resource set A). The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the following examples.
[0253] For example (shown as Example 1.3.1), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS resource included in SRS resource set A, where the SRS resource index is included in a downlink DCI format, or in a separate DCI format dedicated to TCI state updates.
[0254] For another example (shown as Example 1.3.2), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in an SRS resource set A, and the SRS resource index is included in the TCI state signaled in the TCI state update (whether through a DL-related DCI format or a separate DCI format dedicated to the TCI state update).
[0255] For another example (indicated as Example 1.3.3), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS resource included in an SRS resource set A, wherein the SRS resource index is included in the PUCCH resource index, and each resource included in the PUCCH resource set includes an SRS resource index. Table 2 below illustrates an example in which an SRS resource index is included in a PUCCH resource, in which the SRS resource set has two SRS resources. This is illustrated by the example in Table 2.
[0256] Table 2: PUCCH resource set with SRS resource index containing PUCCH resources
[0257]
[0258] The size of the PUCCH resource set can be increased to include more resources; for example, the size can be increased to 16 elements, and the PCI index field in the DCI format is increased from 3 bits to 4 bits. In the case of PUCCH format 0, where the size of the PUCCH resource set is 32 and 2 bits are implicitly indicated, or PUCCH format 1, the size of the PUCCH resource set can be increased to 64, that is, the 4-bit PCI has 2 implicitly indicated bits.
[0259] For another example (indicated as Example 1.3.4), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS resource included in SRS resource set A, where the SRS resource index is implicitly indicated (i.e., the SRS resource index can be derived from other signals and / or other system parameter values).
[0260] For another example (shown as Example 1.3.5), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS resource included in SRS resource set A, where the SRS resource index is indicated / updated by MAC CE.
[0261] For another example (indicated as Example 1.3.6), the number of SRS resources and / or SRS resource indices included in an SRS resource set (e.g., SRS resource set A) may be updated by upper-level RRC signaling and / or MAC CE signaling and / or L1 control signaling. The size of the corresponding field in the DCI format for indicating SRS resources may be updated accordingly, or an implicit mapping rule may consider the number of updated SRS resources to include for an implicit mapping to the number of updated SRS resources.
[0262] For another example (indicated as Example 1.3.7), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is the spatial relationship reference RS for the DMRS port supergroup. The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the previous examples, such as Examples 1.3.1 through 1.3.6, where the SRS resource is replaced by the DMRS port group.
[0263] For another example (indicated as Example 1.3.8), a PUCCH transmission for HARQ-ACK overlaps with another PUCCH transmission. HARQ-ACK information and other UL control information may be included in the PUCCH resource. The spatial relationships of the PUCCH resource may be determined according to Examples 1.3.1 through 1.3.7.
[0264] For another example (indicated as Example 1.3.9), a PUCCH transmission for HARQ-ACK may overlap with a PUSCH transmission, and the HARQ-ACK information may be multiplexed on the PUSCH. The spatial relationship of the PUSCH transmissions may be determined according to Examples 1.3.1 through 1.3.7.
[0265] In certain embodiments (referred to as Example 1.4), a DCI format having a CSI request includes a TCI state. A source RS having a type D QCL as indicated by the TCI state in the DCI format, or in a separate DCI format dedicated to updating the TCI state, is a spatial relationship reference RS for the corresponding PUCCH transmission.
[0266] For example (indicated as Example 1.4.1), a PUCCH transmission for a CSI overlaps with another PUCCH transmission, and the CSI information and other UL control information are included in the PUCCH resource, and the spatial relationship of the PUCCH resource can be determined according to a source RS having a type D QCL as indicated by the DCI format, or the TCI state in a separate DCI format dedicated to TCI state updates.
[0267] For another example (shown as Example 1.4.2), a PUCCH transmission for a CSI overlaps with a PUSCH transmission. The CSI can be multiplexed over the PUSCH. The spatial relationship of the PUSCH transmission can be determined by a source RS having a type D QCL as indicated by the TCI state in a DCI format, or in a separate DCI format dedicated to TCI state updates.
[0268] In certain embodiments (referred to as Example 1.5), a DCI format having a CSI request includes a TCI state. A source RS having a type D QCL as indicated by the TCI state in the DCI format, or in a separate DCI format dedicated to updating the TCI state, is a spatial relationship reference RS for an SRS resource (referred to as SRS resource A). The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the following examples.
[0269] For example (indicated as Example 1.5.1), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A. The SRS port index is contained in a DCI format, or in a separate DCI format dedicated to TCI status updates.
[0270] For another example (shown as Example 1.5.2), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A. The SRS port index may be included in the TCI state signaled in the TCI state update (whether through a DL-related DCI format or a separate DCI format dedicated to the TCI state update).
[0271] For another example (indicated as Example 1.5.3), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A. The SRS port index may be implicitly indicated. For example, the SRS port index may be derived from other signaling and / or other system parameter values.
[0272] For another example (shown as Example 1.5.4), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS port included in SRS resource A. The SRS port index is indicated / updated by MAC CE.
[0273] For another example (indicated as Example 1.5.5), the number of SRS ports and / or SRS port indices included in an SRS resource (e.g., SRS resource A) may be updated by upper-level RRC signaling and / or MAC CE signaling and / or L1 control signaling. The size of the corresponding field in the DCI format for indicating the SRS ports may be updated accordingly, or an implicit mapping rule may consider the number of updated SRS ports to include in the implicit mapping for the number of updated SRS ports.
[0274] For another example (indicated as Example 1.5.6), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is the spatial relationship reference RS for the DMRS port group. The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the previous examples, such as Examples 1.5.1 through 1.5.5, where the SRS port is replaced by the DMRS port.
[0275] For another example (indicated as Example 1.5.7), a PUCCH transmission for a CSI overlaps with another PUCCH transmission. The CSI and other UL control information may be included in a PUCCH resource, and the spatial relationships of the PUCCH resources may be determined according to Examples 1.5.1 through 1.5.6.
[0276] For another example (indicated as Example 1.5.8), a PUCCH transmission for CSI overlaps with a PUSCH transmission. The CSI is multiplexed over PUSCH, and the spatial relationship of the PUSCH transmissions can be determined according to Examples 1.5.1 through 1.5.6.
[0277] In certain embodiments (referred to as Example 1.6), a DCI format having a CSI request includes a TCI state. A source RS having a type D QCL as indicated by the TCI state in the DCI format, or in a separate DCI format dedicated to updating the TCI state, is a spatial relationship reference RS for an SRS resource set (referred to as SRS resource set A). The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of the following examples.
[0278] For example (indicated as Example 1.6.1), the spatial relationship of a PUCCH resource may be the spatial relationship of an SRS resource included in SRS resource set A, where the SRS resource index is included in a DCI format, or in a separate DCI format dedicated to TCI state updates.
[0279] For another example (indicated as Example 1.6.2), the spatial relationship of a PUCCH resource may be the spatial relationship of an SRS resource included in SRS resource set A. The SRS resource index may be included in the TCI state signaled in the TCI state update (whether through a DL-related DCI format or a separate DCI format dedicated to the TCI state update).
[0280] For another example (indicated as Example 1.6.3), the spatial relationship of a PUCCH resource may be the spatial relationship of an SRS resource included in SRS resource set A. The SRS resource index may be implicitly indicated (i.e., the SRS resource index may be derived from other signaling and / or other system parameter values).
[0281] For another example (shown as Example 1.6.4), the spatial relationship of a PUCCH resource is the spatial relationship of an SRS resource included in SRS resource set A, where the SRS resource index is indicated / updated by MAC CE.
[0282] For another example (indicated as Example 1.6.5), the number of SRS resources and / or SRS resource indices included in an SRS resource set (e.g., SRS resource set A) may be updated by upper-level RRC signaling and / or MAC CE signaling and / or L1 control signaling. The size of the corresponding field in the DCI format for indicating SRS resources may be updated accordingly, or an implicit mapping rule may consider the number of updated SRS resources to include for an implicit mapping to the number of updated SRS resources.
[0283] For another example (indicated as Example 1.6.6), a source RS having a type D QCL as indicated by the TCI status in a DL DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format 1_2), or in a separate DCI format dedicated to TCI status updates, is the spatial relationship reference RS for the DMRS port supergroup. The spatial relationship for the corresponding PUCCH transmission may be indicated according to one or more of Examples 1.6.1 through 1.6.5, where the SRS resource is replaced by the DMRS port group.
[0284] For another example (indicated as Example 1.6.7), a PUCCH transmission for a CSI may overlap with another PUCCH transmission. The CSI and other UL control information may be included in a PUCCH resource, and the spatial relationships of the PUCCH resource may be determined according to Examples 1.6.1 through 1.6.6 described above.
[0285] For another example (indicated as Example 1.6.8), a PUCCH transmission for a CSI overlaps with a PUSCH transmission. The CSI can be multiplexed over the PUSCH, and the spatial relationship of the PUSCH transmissions can be determined according to Examples 1.6.1 through 1.6.6 described above.
[0286] In certain embodiments (referred to as Example 1.7), the DCI format for scheduling PUSCH transmissions includes TCI states, and the spatial relationships for the corresponding PUSCH transmissions can be indicated and determined similarly to Examples 1.4, 1.5, and 1.6 described above, where the PUSCH transmission replaces the PUCCH transmission.
[0287] FIGS. 21a, 21b, 21c, and 21d illustrate exemplary embodiments of UEs determining specific relationships according to embodiments of the present disclosure. The exemplary embodiments of FIGS. 21a, 21b, 21c, and 21d are for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0288] In certain embodiments (referred to as Example 1.8), the DCI format for scheduling a PUCCH transmission or a PUSCH transmission does not include a TCI state, but rather includes or indicates an SRS port index or an SRS resource index. According to Example 1.5 or Example 1.6 described above, a UE (e.g., UE (116) of FIGS. 1 and 3) may determine the spatial relationship to the corresponding PUCCH transmission or PUSCH transmission based on the TCI state included in the most recent PDCCH reception containing the TCI state and the indicated SRS port index or SRS resource index with respect to the time of reception of the DCI format for scheduling a PUCCH transmission or a PUSCH transmission. This is illustrated in the embodiment (2100a) of FIG. 21a.
[0289] In a variant example, the DCI format for scheduling PUCCH transmission or PUSCH transmission does not include a TCI state, but includes or indicates a DMRS port index or a DMRS port group index.
[0290] In certain embodiments (referred to as Example 1.9), the DCI format for scheduling a PUCCH transmission or a PUSCH transmission does not include a TCI state or include or indicate an SRS port index or an SRS resource index. With respect to the time of reception of the DCI format for scheduling a PUCCH transmission or a PUSCH transmission, a UE (e.g., UE (116) of FIG. 1 and FIG. 3) may determine the spatial relationship for the corresponding PUCCH transmission or PUSCH transmission based on the spatial relationship determined by the most recent PDCCH reception that determines the spatial relationship for the uplink transmission. This is illustrated in the embodiment (2100b) of FIG. 21b.
[0291] In a variation, the DCI format for scheduling a PUCCH transmission or a PUSCH transmission does not include a TCI state, but does not include or indicate a DMRS port index or a DMRS port group index. With respect to the reception time of the DCI format for which the UE schedules a PUCCH transmission or a PUSCH transmission, the spatial relationship for the corresponding PUCCH transmission or PUSCH transmission can be determined based on the spatial relationship determined by the most recent PDCCH reception, which determines the spatial relationship for the uplink transmission.
[0292] In certain embodiments (referred to as Example 1.10), the uplink transmission is a grant-free uplink transmission, such as a periodic PUCCH transmission, a semi-permanent PUCCH transmission, a PUCCH-set grant transmission, or a RACH transmission. Based on the preceding examples in which the UE determines a spatial relationship for an uplink transmission earlier than the UL transmission time by at least the UE processing latency time, the UE may determine a spatial relationship for the corresponding UL transmission based on the spatial relationship determined by the most recent PDCCH reception. This is illustrated in the embodiment (2100c) of FIG. 21c.
[0293] In certain embodiments (referred to as Example 1.11), the uplink transmission is a non-grant uplink transmission, such as a periodic PUCCH transmission, a semi-permanent PUCCH transmission, a PUSCH-set grant transmission, or a RACH transmission. Based on the preceding examples corresponding to uplink transmissions that are subject to the UE's processing time limits and start earlier than or from the non-grant uplink transmission, the spatial relationship for the corresponding UL transmission can be determined based on the spatial relationship determined by the most recent PDCCH reception. This is illustrated in the embodiment (2100d) of FIG. 21d.
[0294] The following embodiments and examples describe spatial relationships in PUCCH or updating of TCI states (Component 6):
[0295] The embodiments of the present disclosure explain that, in order to reduce the latency associated with beam switching, the TCI state or spatial relationship in the PUCCH transmission can be updated with HARQ-ACK information corresponding to the downlink transmission.
[0296] In certain embodiments (referred to as Example 2.1), the PUCCH transmitter includes a HARQ-ACK. Additionally, the PUCCH transmitter includes a field containing a TCI status and / or spatial relationship reference RS for a downlink transmitter and / or an uplink transmitter.
[0297] For example (indicated as Example 2.1.1), a set of TCI states may be set in a UE (e.g., UE (116) of FIGS. 1 and 3). For example, the set of TCI states has M TCI state elements, where PUCCH transmission includes an N-bit field containing the preferred TCI state. A set of M TCI states can be updated by upper-layer RRC signaling and / or MAC-CE signaling and / or L1 control signaling. The N-bit field corresponds to code points in the updated set of TCI states. For example, the set of M TCI states to be set If so, an N-bit field may correspond to TCI states according to Table 3 below. The set of TCI states that can be indicated in PUCCH may be a subset of the set of TCI states used for beam indication in PDCCH.
[0298] Table 3: Mapping of an N-bit field to a set of M TCI states
[0299]
[0300] For example, referring to Table 3, "10" is the TCI status It will represent.
[0301] M TCI states When updated, the mapping to an N-bit field follows Table 4 shown below.
[0302] Table 4: Updated mapping of an N-bit field to a set of M TCI states
[0303]
[0304] For example, referring to Table 4, "10" is the TCI status It will represent.
[0305] For another example (indicated as Example 2.1.2), a set of spatial relationship-based RS resources may be configured in the UE. For example, the set of spatial relationship-based RS resources has M spatial relationship-based RS resources, where PUCCH transmission includes an N-bit field representing the preferred spatial relationship reference RS. A set of M spatial relationship reference RS resources can be updated by upper-layer RRC signaling and / or MAC-CE signaling and / or L1 control signaling. The N-bit field corresponds to a code point in the updated TCI state set.
[0306] For another example (indicated as Example 2.1.3), the UE may include a field for beam indications (i.e., spatial filter indications) in the PUCCH transmission for HARQ-ACK, the field being composed of multiple subfields, each subfield following one of the examples discussed above, such as the examples in 2.1.1 and 2.1.2. For example, the field for beam indications may include two subfields, the first subfield being an indication of a preferred TCI status following Example 2.1.1 for downlink transmission, and the second subfield being an indication of a preferred spatial relationship reference RS following Example 2.1.2 for uplink transmission.
[0307] For another example (indicated as Example 2.1.4), the presence of a field for beam indication in a PUCCH containing HARQ-ACK may be enabled and / or disabled by upper-level RRC signaling and / or MAC-CE signaling and / or L1 signaling.
[0308] For another example (indicated as Example 2.1.5), a field for beam indication may be transmitted once every K slots / subframes / frames in a PUCCH transmission with a HARQ-ACK. Note that K may be set and / or updated to the UE by upper-layer RRC signaling and / or MAC-CE signaling and / or L1 signaling. For example, if i is the first index of a PUCCH transmission with a HARQ-ACK in a slot / subframe / frame with index j or thereafter, the UE may determine index i for such slot / subframe / frame, is. Here, O is an offset that can be set and / or updated to the UE by upper-layer RRC signaling and / or MAC-CE signaling and / or L1 signaling. An example is shown in FIG. 22.
[0309] FIG. 22 illustrates an exemplary embodiment (2200) of an offset according to embodiments of the present disclosure. The exemplary embodiment (2200) of FIG. 22 is for illustrative purposes only, and other embodiments may be used without departing from the scope of the present disclosure.
[0310] In this example, as illustrated in FIG. 22, the slots corresponding to index j, K=4, O=1, are {3, 7, 11, ...}. The slots corresponding to index i in which a beam indication can be transmitted are the first slot starting in or after the slot with index j containing HARQ-ACK information. In a variation, the slot / subframe / frame with index j can be determined such that (j)mod K = O.
[0311] In specific embodiments (referred to as Example 2.2), the PUCCH transmission includes a HARQ-ACK and a beam indication field having N bits following the examples of Example 2.1. The UE includes for the HARQ-ACK PUCCH resources are configured. UE Within a set of PUCCH resources, N bits of beam indication are indicated by the selection of the PUCCH resource. For example, if N=2, the UE is configured with a set of 4 PUCCH resources, namely Resource0, Resource1, Resource2, and Resource3. The UE can signal the beam indication field by selecting the corresponding PUCCH resource, for example, according to Table 5 below.
[0312] Table 5: Beam directing through selection of PUCCH resources
[0313]
[0314] Note that the gNB can perform multiple decoding hypotheses to determine the resources transmitted by the UE.
[0315] In a variation example, M PUSCH resources are set for HARQ-ACK, Only M beam instructions can be signaled by the N-bit beam instruction field.
[0316] In certain embodiments (referred to as Example 2.3), the PUCCH transmits include a HARQ-ACK. The UE determines whether there is a change in the preferred beam to be signaled to the gNB. If there is a change in the preferred beam, the UE signals the preferred beam according to the examples of Example 2.1. Otherwise, if there is no change in the preferred beam, the beam indication is not included in the PUCCH transmits. In this example, the UE can determine which of the two PUCCH resources it can transmit: a first PUCCH resource containing a HARQ-ACK and a beam indication, and a second PUCCH resource containing a HARQ-ACK. The gNB may perform a number of decoding hypotheses to determine the resource transmitted by the UE.
[0317] In specific embodiments (referred to as Example 2.4), the PUCCH transmission includes a HARQ-ACK and a beam indication field having N bits following the examples of Example 2.1. The size of the bit-unit PUCCH transmission is is. Here, is the size of the HARQ-ACK report. It determines whether there is a change in the preferred beam to be signaled to the gNB by the UE.
[0318] If there are changes in the preferred beam, the contents of the PUCCH payload are described in Table 6 below. The payload is for presence indication, beam indication reporting. It includes bits, and N bits for beam indication. Note that the presence indication uses one bit to indicate that a beam indication is included, and that, for example, this bit can have a value of "1".
[0319] If there are no changes in the preferred beam, the contents of the PUCCH payload are described in row 4 of Table 6 below. The payload is then for presence indication, beam indication reporting. It will include bits for the beam indicator and N bits for the beam indicator. These are set to predetermined values, for example, they can be set to "0". Note that the presence indicator is a single bit indicating that the beam indicator is not included, and for example, this bit can have a value of "0".
[0320] Table 6: PUCCH payload with presence indicator, HARQ-ACK information, and beam indication
[0321]
[0322] The gNB can decode the PUCCH resource and determine whether the beam indicator field exists or is set to a predetermined value (e.g., all zeros) based on the value of the existence indicator. If it is set to a predetermined value, the predetermined value can be used to improve the decoding performance of the HARQ-ACK report.
[0323] For example (indicated as Example 2.4.1), the PUCCH payload may include other fields such as CSI reports, scheduling requests, and other L1 control fields in addition to presence instructions, HARQ-ACK reports, and beam instructions.
[0324] For example (indicated as Example 2.4.2), if the UE determines a maximum size for a PUCCH transmission and the PUCCH payload exceeds the maximum size, the UE may discard the PUCCH fields according to specific rules, starting with the lowest priority fields, e.g., the lowest priority CSI. The UE may discard (or remove) the HARQ-ACK report, or discard the N-bit TCI field as indicated by the presence indicator.
[0325] For example, if the size of the PUCCH payload is 5 bits, =3 and N=4. The existence indicator can determine the contents of the PUCCH payload according to Table 7 below.
[0326] Table 7: PUCCH payload according to one example.
[0327]
[0328] As another example, if the size of the PUCCH payload is 6 bits, =5 and N=4. The existence indicator can determine the contents of the PUCCH payload according to Table 8 below.
[0329] Table 8: PUCCH payload according to one example.
[0330]
[0331] In another example 2.5, a PUCCH transmission that may include HARQ-ACK information and beam indications overlaps temporally with a PUSCH transmission. According to the previous examples of Component 2, uplink control information that may include HARQ-ACK information and / or beam indications may be multiplexed over a PUSCH transmission without a PUCCH transmission. In a variation, the PUCCH and PUSCH transmissions may be transmitted simultaneously on different frequency resources.
[0332] FIG. 23 illustrates a method (2300) for transmitting UL reference signals according to embodiments of the present disclosure. One embodiment of the method (2300) illustrated in FIG. 23 is for illustrative purposes only. For example, the method (2300) may be performed by a UE such as the UE (116) of FIG. 1 and a complementary method may be performed by a BS such as the BS (102) of FIG. 1. One or more of the components illustrated in FIG. 23 may be implemented in a specialized circuit configured to perform the mentioned functions, or one or more of the components may be implemented by one or more processors that execute instructions for performing the mentioned functions.
[0333] The method (2300) begins with the UE receiving configuration information (step 2302). For example, in step 2302, the configuration information may include one or more of configuration information for UL reference signals for beam management, configuration information for source reference signals for spatial relationships, and configuration information for beam reporting. In various embodiments, the UL reference signals for beam management are UL DMRS for beam management or one or more sets of SRS resources. The UL DMRS for beam management may be time-division multiplexed with PUSCH or PUCCH. In various embodiments, the source reference may be a Type D quasi-juxtaposition (QCL) source reference signal for TCI status, a source reference signal for UL transmission spatial reference, or a measurement reference signal.
[0334] Then, the UE receives source reference signals (step 2304). For example, at step 2304, the UE may receive source reference signals according to configuration information for the source reference signals. Then, the UE measures a signal quality metric for the source reference signals regarding spatial relationships (step 2306) and transmits a beam report (step 2308). For example, at step 2308, the UE generates and transmits a beam report based on the measured signal quality metric. In some embodiments, the beam report includes a preferred spatial domain identifier and is included in a UL transmission for HARQ-ACK feedback of downlink transmissions. In some embodiments, the UE is configured to receive a beam measurement report request for a plurality of beams, determines which of the plurality of beams will signal the beam measurement report request, transmits the beam measurement report request for the determined beam, receives a UL grant for beam measurement reporting, and transmits a beam measurement report for the resources granted by the UL grant. In various embodiments, the beam report is one or more beam reports comprising one or more beam quantities including any combination of a measurement resource ID, a beam metric without MPE effects, and a beam metric with MPE effects. In some embodiments, the UE may initiate the transmission of a beam report or beam measurement report request when it detects a change in the spatial environment.
[0335] Then the UE receives updated configuration information for the UL reference signals for beam management (step 2310). For example, in step 2310, the updated configuration information is in response to the transmitted beam report. In various embodiments, the updated configuration information for the UL reference signals for beam management includes instructions for a set of UL reference signals for beam management to be transmitted by the UE, and instructions for source reference signals regarding spatial relationships for each of one or more groups of UL reference signals for beam management. Here, the set of UL reference signals for beam management may be organized into one or more groups of UL reference signals for beam management, wherein one or more UL reference signals in a set having the same source reference signal regarding spatial relationships constitute a group of UL reference signals in one or more groups.
[0336] Subsequently, the UE determines a time for updating the UL reference signals for beam management (step 2312). For example, in step 2312, the UE may determine the time based on configuration information. Then, the UE transmits the UL reference signals for beam management (step 2314). For example, in step 2314, the transmission is transmitted at the determined time based on the updated configuration information. In some embodiments, the UE may determine a UL spatial domain filter for uplink transmission based on the Transmit Configuration Instruction (TCI) status directed to the UE and the UL reference signal resource indicator for the UL reference signal within the UL reference signal group for beam management. Here, the TCI status represents the source reference signal for the spatial relationship, and the source reference signal for the spatial relationship represents the UL reference signal group for beam management having the same source reference signal for the spatial relationship.
[0337] Although FIG. 23 illustrates exemplary methods, various modifications may be made to FIG. 23. For example, although the method (2300) is illustrated as a series of steps, various steps may overlap, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced by other steps.
[0338] The above flowcharts illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced by other steps.
[0339] Although the drawings illustrate different examples of user equipment, various modifications may be made to the drawings. For example, user equipment may include any number of individual components in any suitable arrangement. In general, the drawings do not limit the scope of the disclosure to any specific configuration(s). Furthermore, while the drawings illustrate operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.
[0340] Although the present disclosure has been described by exemplary embodiments, various changes and modifications may be proposed to those skilled in the art. The present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Nothing in the description of this application should be construed as implying that any specific element, step, or function is an essential element that must be included in the claims. The scope of the subject matter to be patented is defined solely by the claims.
Claims
Claim 1 A user device (UE) in a wireless communication system comprises: a transceiver; and a processor; wherein the processor receives configuration information for a physical uplink control channel (PUCCH) resource for a UE-initiation report instruction through the transceiver, receives the reference signal through the transceiver based on configuration information for a reference signal, determines whether to transmit a UE-initiation report based on the layer 1 reference signal reception power (L1-RSRP) of the reference signal, transmits the UE-initiation report instruction from the PUCCH resource through the transceiver, and, after transmitting the UE-initiation report instruction, transmits the UE-initiation report including the L1-RSRP of the reference signal through the transceiver on a physical uplink shared channel (PUSCH) indicated in a downlink control information (DCI) format or a configured grant PUSCH (CG-PUSCH). Claim 2 In paragraph 1, the reference signal is a UE, which is a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB). Claim 3 In paragraph 1, the above DCI format is a UE that includes a Channel State Information (CSI) request. Claim 4 In paragraph 1, the above CG-PUSCH comprises only the above UE-initiation report, UE. Claim 5 delete Claim 6 In claim 1, determining whether to transmit the UE-initiation report based on the L1-RSRP of the reference signal includes determining to transmit the UE-initiation report when the L1-RSRP of the reference signal changes by a threshold value set by an upper layer. Claim 7 A base station (BS) in a wireless communication system comprises: a transceiver; and a processor; wherein the processor transmits configuration information for a physical uplink control channel (PUCCH) resource for a user equipment (UE)-initiation report instruction through the transceiver; transmits the reference signal through the transceiver based on configuration information for a reference signal; when the UE decides to transmit a UE-initiation report based on the layer 1 reference signal reception power (L1-RSRP) of the reference signal, receives the UE-initiation report instruction from the PUCCH resource through the transceiver; and after receiving the UE-initiation report instruction, receives the UE-initiation report including the L1-RSRP of the reference signal from a physical uplink shared channel (PUSCH) or a configured grant PUSCH (CG-PUSCH) indicated in a downlink control information (DCI) format through the transceiver. Claim 8 In paragraph 7, the reference signal is a BS, which is a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB). Claim 9 In paragraph 7, the DCI format is a BS that includes a Channel State Information (CSI) request. Claim 10 In paragraph 7, the above CG-PUSCH includes only the above UE-initiation report, BS. Claim 11 delete Claim 12 In claim 7, when the UE decides to transmit the UE-initiation report based on the L1-RSRP of the reference signal, receiving the UE-initiation report instruction at the PUCCH resource includes receiving the UE-initiation report instruction at the PUCCH resource when the L1-RSRP of the reference signal changes by a threshold value set by the upper layer through the transceiver. Claim 13 A method performed by a user equipment (UE) in a wireless communication system, comprising: receiving configuration information for a physical uplink control channel (PUCCH) resource for a UE-initiation report instruction; receiving the reference signal based on configuration information for a reference signal; determining whether to transmit a UE-initiation report based on the layer 1 reference signal reception power (L1-RSRP) of the reference signal; transmitting the UE-initiation report instruction from the PUCCH resource; and, after transmitting the UE-initiation report instruction, transmitting the UE-initiation report including the L1-RSRP of the reference signal from a physical uplink shared channel (PUSCH) or a configured grant PUSCH (CG-PUSCH) indicated in a downlink control information (DCI) format. Claim 14 In paragraph 13, the method wherein the reference signal is a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB). Claim 15 In paragraph 13, the method wherein the DCI format includes a channel state information (CSI) request. Claim 16 In paragraph 13, the above CG-PUSCH is a method comprising only the above UE-initiation report. Claim 17 delete Claim 18 In claim 13, the step of determining whether to transmit the UE-initiation report based on the L1-RSRP of the reference signal comprises the step of determining to transmit the UE-initiation report when the L1-RSRP of the reference signal changes by a threshold value set by an upper layer. Claim 19 A method performed by a base station (BS) in a wireless communication system, comprising: transmitting configuration information for a physical uplink control channel (PUCCH) resource for a user equipment (UE)-initiation report instruction; transmitting the reference signal based on configuration information for a reference signal; receiving the UE-initiation report instruction from the PUCCH resource when the UE decides to transmit the UE-initiation report based on the layer 1 reference signal reception power (L1-RSRP) of the reference signal; and receiving the UE-initiation report including the L1-RSRP of the reference signal in a physical uplink shared channel (PUSCH) or a configured grant PUSCH (CG-PUSCH) indicated in a downlink control information (DCI) format after receiving the UE-initiation report instruction. Claim 20 In paragraph 19, the method wherein the reference signal is a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB). Claim 21 In paragraph 19, the above DCI format includes a channel state information (CSI) request, a method. Claim 22 In paragraph 19, the above CG-PUSCH is a method comprising only the above UE-initiation report. Claim 23 delete Claim 24 In claim 19, when the UE decides to transmit the UE-initiation report based on the L1-RSRP of the reference signal, the step of receiving the UE-initiation report instruction from the PUCCH resource comprises receiving the UE-initiation report instruction from the PUCCH resource when the L1-RSRP of the reference signal changes by a threshold value set by an upper layer.
Citation Information
Patent Citations
Method and apparatus for beam management
WO2019140639A1
