Method and apparatus for dynamic downlink multi-beam operation in wireless communication system
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SAMSUNG ELECTRONICS CO LTD
- Filing Date
- 2021-04-13
- Publication Date
- 2026-05-29
Smart Images
Figure CN115462156B_ABST
Abstract
Description
Technical Field
[0001] This disclosure generally relates to wireless communication systems, and more specifically, to methods for implementing dynamic multi-beam operation. Background Technology
[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60GHz band, to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, system network improvements are under development in 5G communication systems based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, Coordinated Multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) as advanced coding modulation (ACM), as well as sliding window superposition coding (SWSC), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies have been developed.
[0003] The internet is a human-centric network where humans generate and consume information. It is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. IoT technology, combined with big data processing technology and connected to cloud servers, has given rise to the Internet of Everything (IoE). Because IoT implementation requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been researched. Such an IoT environment can provide intelligent internet technology services, creating new value for human life by collecting and analyzing data generated from connected things. Through the integration and combination of existing information technology (IT) with various industrial applications, IoT can be applied to multiple fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0004] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence between 5G and IoT technologies.
[0005] Understanding and accurately estimating the channel between a User Equipment (UE) and a Base Station (BS) (e.g., a gNode B (gNB)) is crucial for efficient and effective wireless communication. To accurately estimate DL channel conditions, the gNB can transmit reference signals, such as CSI-RS, to the UE for DL channel measurements, and the UE can report (e.g., provide feedback) information about the channel measurements to the gNB, such as CSI. With such DL channel measurements, the gNB can select appropriate communication parameters to perform wireless data communication with the UE efficiently and effectively. Summary of the Invention
[0006] Technical issues
[0007] For millimeter-wave communication systems, the reference signal can correspond to a spatial beam, and the CSI can correspond to a beam report indicating the preferred spatial beam used for communication. In such beamforming systems, a beam indication mechanism is required to align the spatial beams at both the gNB and the UE.
[0008] Technical solution
[0009] Embodiments of this disclosure provide methods and apparatus for implementing dynamic multi-beam operation in a wireless communication system.
[0010] In one embodiment, a UE (User Equipment) is provided in a wireless communication system. The UE includes a transceiver configured to receive configuration information via downlink control information (DCI) regarding a Transport Configuration Indicator (TCI) state indication. This configuration information includes a set of TCI states and information for configuring a DCI from one of a downlink (DL) DCI (DL-DCI) and a DL-TCI-DCI, wherein the DL-DCI schedules a DL Physical DL Shared Channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for the TCI state indication; and to receive the configured DCI based on the configuration information. The UE also includes a processor operatively coupled to the transceiver. The processor is configured to decode the configured DCI to obtain a TCI state update; determine a receive beam based on the TCI state update; and apply the receive beam to the reception of DL control or DL data.
[0011] In another embodiment, a BS (Base Station) is provided in a wireless communication system. The BS includes a processor configured to generate configuration information via downlink control information (DCI) regarding Transmission Configuration Indicator (TCI) state indications, the configuration information including a set of TCI states and information for configuring the DCI from one of a downlink (DL) DCI (DL-DCI) and a DL-TCI-DCI, wherein the DL-DCI schedules DL physical DL shared channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for TCI state indication; and to generate a configured DCI including TCI state updates. The BS also includes a transceiver operatively coupled to the processor. The transceiver is configured to: transmit the configuration information; transmit the configured DCI including TCI state updates based on the configuration information; and transmit DL control or DL data for reception by a receive beam indicated via the TCI state update.
[0012] In another embodiment, a method for operating a UE is provided. The method includes: receiving configuration information via downlink control information (DCI) regarding a Transport Configuration Indicator (TCI) state indication, the configuration information including a set of TCI states and information for configuring a DCI from one of a downlink (DL) DCI (DL-DCI) and a DL-TCI-DCI, wherein the DL-DCI schedules DL Physical DL Shared Channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for the TCI state indication; receiving the configured DCI based on the configuration information; decoding the configured DCI to obtain a TCI state update; determining a receive beam based on the TCI state update; and applying the receive beam to the reception of DL control or DL data.
[0013] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.
[0014] Beneficial effects
[0015] According to embodiments of this disclosure, effective and efficient dynamic multi-beam operation can be performed. Attached Figure Description
[0016] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:
[0017] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;
[0018] Figure 2 An example gNB according to an embodiment of this disclosure is shown;
[0019] Figure 3 An example UE according to an embodiment of the present disclosure is shown;
[0020] Figure 4A A high-order diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure is shown;
[0021] Figure 4B A high-order diagram of an orthogonal frequency division multiple access (OFDM) receiving path according to an embodiment of the present disclosure is shown;
[0022] Figure 5 A transmitter block diagram for PDSCH in a subframe according to an embodiment of the present disclosure is shown;
[0023] Figure 6 A receiver block diagram for a PDSCH in a subframe is shown according to an embodiment of the present disclosure;
[0024] Figure 7A transmitter block diagram for PUSCH in a subframe is shown according to an embodiment of the present disclosure;
[0025] Figure 8 A receiver block diagram for a PUSCH in a subframe is shown according to an embodiment of the present disclosure;
[0026] Figure 9 An example of two slices being reused according to an embodiment of this disclosure is shown;
[0027] Figure 10 Uplink multi-beam operation according to an embodiment of this disclosure is illustrated;
[0028] Figure 11 Uplink multi-beam operation according to an embodiment of this disclosure is illustrated;
[0029] Figure 12 Downlink multi-beam operation according to an embodiment of this disclosure is illustrated;
[0030] Figure 13 An example of a dedicated DCI for receiving DL control and data, according to embodiments of this disclosure, is shown;
[0031] Figure 14 An example of receiving DL-TCI-DCI and DL-DCI in the same time slot or subframe according to an embodiment of the present disclosure is shown;
[0032] Figure 15 An example of decoding DL-TCI-DCI and DL-DCI according to embodiments of the present disclosure is shown;
[0033] Figure 16 An example of a dedicated DCI for transmitting UL control and data, according to embodiments of this disclosure, is shown;
[0034] Figure 17 An example of receiving UL-TCI-DCI and UL-DCI in the same time slot or subframe according to an embodiment of the present disclosure is shown;
[0035] Figure 18 An example of a dedicated DCI for a common beam used for all DL and UL channels, according to an embodiment of this disclosure, is shown;
[0036] Figure 19 An example of receiving TCI-DCI and DL-DCI in the same time slot or subframe according to an embodiment of the present disclosure is shown;
[0037] Figure 20 An example of receiving TCI-DCI and UL-DCI in the same time slot or subframe according to an embodiment of the present disclosure is shown;
[0038] Figure 21 Examples of receiving TCI-DCI, UL-DCI and DL-DCI in the same time slot or subframe according to embodiments of the present disclosure are shown;
[0039] Figure 22 A flowchart of a method for operating a UE according to an embodiment of the present disclosure is shown;
[0040] Figure 23 A flowchart of a method for operating a BS according to an embodiment of the present disclosure is shown;
[0041] Figure 24 An electronic device according to an embodiment of the present disclosure is shown; and
[0042] Figure 25 A base station according to an embodiment of this disclosure is shown. Detailed Implementation
[0043] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “including” and “comprising,” and their derivatives mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated with” and its derivatives mean including, encompassing, interconnected, containing, contained within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, interleaving, juxtaposing, proximate, bound to or bound with, having, possessing attributes, related to or having a relationship with, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. When used with a list of items, the phrase "at least one" indicates that different combinations of one or more of the listed items may be used, as well as that only one item from 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.
[0044] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate 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 read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that permanently store data and media that store data and can subsequently be rewritten, such as rewritable optical discs or erasable memory devices.
[0045] Definitions of other specific words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many (if not most) cases, these definitions apply to the prior and future use of the words and phrases thus defined.
[0046] The following discussion Figures 1 to 23 The various embodiments used to describe the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.
[0047] The following documents and standards are incorporated herein by reference as if fully set forth herein: 3GPP TS 36.211 v16.4.0, “E-UTRA, Physical Channels and Modulation” (hereinafter referred to as “REF 1”); 3GPP TS 36.212 v16.4.0, “E-UTRA, Multiplexing and Channel Coding” (hereinafter referred to as “REF 2”); 3GPP TS 36.213 v16.4.0, “E-UTRA, Physical Layer Procedures” (hereinafter referred to as “REF 3”); 3GPP TS 36.321 v16.3.0, “E-UTRA, Media Access Control (MAC) Protocol Specification” (hereinafter referred to as “REF 4”); 3GPP TS 36.331 v16.3.0, “E-UTRA, Radio Resource Control (RRC) Protocol Specification” (hereinafter referred to as “REF 5”); 3GPP TS 38.211 3GPP TS 38.212 v16.1.0, “NR, Physical Channels and Modulation” (REF 6 in this document); 3GPP TS 38.212 v16.1.0, “NR, Multiplexing and Channel Coding” (REF 7 in this document); 3GPP TS 38.213 v16.1.0, “NR, Physical Layer Procedures for Data” (REF 8 in this document); 3GPP TS 38.214 v16.1.0, “NR, Physical Layer Procedures for Control” (REF 9 in this document); 3GPP TS 38.215 v16.1.0, “NR, Physical Layer Measurements” (REF 10 in this document); 3GPP TS 38.321 v16.1.0, “NR, Media Access Control (MAC) Protocol Specification” (REF 11 in this document); and 3GPP TS 38.331 v16.1.0, “NR, Radio Resource Control (RRC) Protocol Specification” (referred to as “REF 12” in this document).
[0048] Aspects, features, and advantages of this disclosure will become apparent from the following detailed description merely by illustrating several specific embodiments and implementations, including the best mode contemplated for carrying out this disclosure. This disclosure is also capable of having other different embodiments, and several details thereof may be modified in various obvious ways without departing from the spirit and scope of this disclosure. Therefore, the drawings and description are to be considered illustrative in nature and not restrictive. This disclosure is illustrated by way of example, not limitation, in the accompanying figures.
[0049] For the sake of brevity, FDD and TDD are both considered to be duplexing methods used for both DL and UL signaling.
[0050] Although the exemplary description and embodiments below assume orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).
[0051] To meet the increased demand for wireless data services since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands, such as 28 GHz or 60 GHz, to achieve higher data rates, or in lower frequency bands, such as 6 GHz, to achieve strong coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.
[0052] In addition, in 5G / NR communication systems, system network improvements are under development based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.
[0053] The discussion of 5G systems and their associated frequency bands is for reference only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to 5G communication systems, 6G, or even higher-version deployments that can use terahertz (THz) frequency bands.
[0054] The following Figures 1-4B Various embodiments of communication technologies implemented in wireless communication systems and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) are described. Figures 1-3 The description is not intended to imply any physical or architectural limitations on the ways in which different embodiments may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system. This disclosure covers several components that may be used in combination or in combination with each other or that may operate as independent solutions.
[0055] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.
[0056] like Figure 1 As shown, the wireless network includes gNB 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.
[0057] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes UE 111, which may be located in a small business; UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a primary residence (R); UE 115, which may be located in a secondary residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G, LTE, LTE-A, WiMAX, WiFi or other wireless communication technologies.
[0058] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wireless-enabled equipment. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed Packet Access (HSPA), 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 providing wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user equipment." For convenience, the terms “user equipment” and “UE” used in this patent document refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).
[0059] The dashed lines show the approximate extent of coverage areas 120 and 125, and are shown as roughly circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment related to natural and man-made obstacles.
[0060] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for receiving configuration information via downlink control information (DCI) regarding Transport Configuration Indicator (TCI) state indications, the configuration information including a set of TCI states and information for configuring a DCI from one of a downlink (DL) DCI (DL-DCI) and a DL-TCI-DCI, wherein the DL-DCI schedules a DL Physical DL Shared Channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for the TCI states; receiving the configured DCI based on the configuration information; decoding the configured DCI to obtain a TCI state update; determining a receive beam based on the TCI state update; and applying the receive beam to the reception of DL control or DL data. One or more gNBs 101-103 include circuitry, programming, or a combination thereof for generating configuration information regarding Transmission Configuration Indicator (TCI) status indications via downlink control information (DCI), the configuration information including a set of TCI states and information for configuring the DCI from one of a downlink (DL) DCI (DL-DCI) and a DL-TCI-DCI, wherein the DL-DCI schedules DL physical DL shared channel (PDSCH) assignments, and the DL-TCI-DCI is a dedicated DCI for TCI status indication; generating the configured DCI including TCI status updates; transmitting the configuration information; transmitting the configured DCI including TCI status updates based on the configuration information; and transmitting DL control or DL data for reception by a receive beam indicated via TCI status updates.
[0061] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.
[0062] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only. Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have multiple configurations, and Figure 2This disclosure is not intended to limit the scope of any particular implementation of gNB.
[0063] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.
[0064] RF transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals transmitted by a UE in network 100. RF transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 220 transmits the processed baseband signal to controller / processor 225 for further processing.
[0065] TX processing circuit 215 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 225. TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceivers 210a-210n receive the outgoing processed baseband or IF signals from TX processing circuit 215 and up-convert the baseband or IF signals into RF signals transmitted through antennas 205a-205n.
[0066] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, based on well-known principles, the controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceivers 210a-210n, RX processing circuitry 220, and TX processing circuitry 215. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities.
[0067] For example, the controller / processor 225 can support beamforming or directional routing operations, where outgoing signals from multiple antennas 205a-205n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 225 can also support any of a variety of other functions in the gNB 102.
[0068] The controller / processor 225 is also capable of executing programs and other processes, such as an operating system, residing in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as needed during execution.
[0069] The controller / 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 via a backhaul connection or over a network. Interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a system supporting 5G, LTE, or LTE-A), interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 235 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). Interface 235 includes any suitable architecture that supports communication via a wired or wireless connection, such as an Ethernet or RF transceiver.
[0070] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, while another portion of memory 230 may include flash memory or other ROM.
[0071] although Figure 2 This illustrates an example of gNB 102, but it is possible to... Figure 2 Various changes can be made. For example, gNB 102 can include... Figure 2 Each component can be any number shown. As a specific example, an access point may include multiple interfaces 235, and the controller / processor 225 may support routing functionality to route data between different network addresses. As another specific example, although shown as a single instance including TX processing circuitry 215 and a single instance including RX processing circuitry 220, gNB 102 may include multiple instances of each instance (such as one per RF transceiver). Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.
[0072] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only. Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have multiple configurations, and Figure 3 This disclosure is not intended to limit the scope of any particular implementation of the UE.
[0073] like Figure 3 As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and a receive (RX) processing circuit 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.
[0074] RF transceiver 310 receives incoming RF signals transmitted by the gNB of network 100 from antenna 305. RF transceiver 310 down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which filters, decodes, and / or digitizes the baseband or IF signal to generate a processed baseband signal. RX processing circuitry 325 transmits the processed baseband signal to speaker 330 (e.g., for voice data) or to processor 340 for further processing (e.g., for web browsing data).
[0075] TX processing circuit 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, email, or interactive video game data) from processor 340. TX processing circuit 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives the processed baseband or IF signal from TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal transmitted through antenna 305.
[0076] Processor 340 may include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, based on well-known principles, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.
[0077] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as a process for receiving configuration information regarding Transport Configuration Indicator (TCI) status indications via downlink control information (DCI), the configuration information including a set of TCI states and information for configuring a DCI from one of the downlink (DL) DCI (DL-DCI) and DL-TCI-DCI, wherein the DL-DCI schedules DL Physical DL Shared Channel (PDSCH) assignments, and the DL-TCI-DCI is a dedicated DCI for TCI status indication; receiving the configured DCI based on the configuration information; decoding the configured DCI to obtain a TCI status update; determining a receive beam based on the TCI status update; and applying the receive beam to the reception of DL control or DL data. Processor 340 may move data into or out of memory 360 as needed for the execution of the process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. 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 laptops and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.
[0078] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website).
[0079] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).
[0080] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, you can combine, further subdivide, or omit. Figure 3 The processor 340 can be divided into various components, and additional components can be added as needed. As a specific example, the processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.
[0081] Figure 4AThis is a high-order diagram of the transmit path circuit. For example, the transmit path circuit can be used in Orthogonal Frequency Division Multiple Access (OFDMA) communication. Figure 4B This is a high-order diagram of the receive path circuit. For example, the receive path circuit can be used in Orthogonal Frequency Division Multiple Access (OFDMA) communication. Figure 4A and Figure 4B In the context of downlink communication, the transmitting path circuitry can be implemented in the base station (gNB) 102 or a relay station, and the receiving path circuitry can be implemented in the user equipment (e.g., Figure 1 The user equipment 116) is implemented in this system. In other examples, for uplink communication, the receive path circuit 450 can be implemented in the base station (e.g., [missing information]). Figure 1 This can be implemented in a gNB 102 or a relay station, and the transmit path circuit can be implemented in the user equipment (e.g., gNB 102) or a relay station. Figure 1 Implemented in user equipment 116).
[0082] The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, an N-point inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. The receive path circuitry 450 includes a down-converter (DC) 455, a cyclic prefix removal block 460, a serial-to-parallel (S-to-P) block 465, an N-point fast Fourier transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.
[0083] Figure 4A 400 and Figure 4B At least some of the components in 450 can be implemented in software, while others can be implemented using configurable hardware or a combination of software and configurable hardware. In particular, it should be noted that the FFT and IFFT blocks described in this disclosure can be implemented as configurable software algorithms, where the values of N points can be modified depending on the implementation.
[0084] Furthermore, although this disclosure pertains to embodiments implementing the Fast Fourier Transform (FFT) and Inverse Fast Fourier Transform (IFFT), this is merely exemplary and should not be construed as limiting the scope of this disclosure. It is understood that in alternative embodiments of this disclosure, the FFT and IFFT functions can be readily replaced by the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, respectively. It is understood that for the DFT and IDFT functions, the value of the N variable can be any integer (i.e., 1, 4, 3, 4, etc.), while for the FFT and IFFT functions, the value of the N variable can be any integer power of 2 (i.e., 1, 2, 4, 8, 16, etc.).
[0085] In the transmit path circuit 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., LDPC coding), and modulates (e.g., Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) the input bits to produce a sequence of frequency-domain modulated symbols. The serial-to-parallel block 410 converts (i.e., demultiplexes) the serially modulated symbols into parallel data to produce N parallel symbol streams, where N is the IFFT / FFT size used in BS 102 and UE 116. The N-point IFFT block 415 then performs an IFFT operation on the N parallel symbol streams to produce a time-domain output signal. The parallel-to-serial block 420 converts (i.e., multiplexes) the parallel time-domain output symbols from the N-point IFFT block 415 to produce a serial time-domain signal. The cyclic prefix addition block 425 then inserts a cyclic prefix into the time-domain signal. Finally, the upconverter 430 modulates (i.e., upconverts) the output of the cyclic prefix addition block 425 to an RF frequency for transmission over the wireless channel. The signal can also be filtered in baseband before being converted to RF frequency.
[0086] The transmitted RF signal arrives at UE 116 after passing through the wireless channel and performs the opposite operation to that at gNB 102. Downconverter 455 downconverts the received signal to the baseband frequency, removes the cyclic prefix block 460, and removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. Then, N-point FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and subsequently decodes the modulated symbols to recover the original input data stream.
[0087] Each of gNBs 101-103 can implement a transmission path similar to that used for transmission to user equipments 111-116 in the downlink, and a reception path similar to that used for reception from user equipments 111-116 in the uplink. Similarly, each of user equipments 111-116 can implement a transmission path corresponding to the architecture used for transmission to gNBs 101-103 in the uplink, and a reception path corresponding to the architecture used for reception from gNBs 101-103 in the downlink.
[0088] Use cases for 5G communication systems have been identified and described. These use cases can be broadly categorized into three distinct groups. In one example, enhanced mobile broadband (eMBB) is characterized by high bit / second requirements, while latency and reliability requirements are less stringent. In another example, ultra-reliable and low-latency (URLL) is defined with less stringent bit / second requirements. In yet another example, massive machine-type communication (mMTC) is identified as having up to 100,000 to 1 million devices per square kilometer, but reliability / throughput / latency requirements may be less stringent. This situation may also involve power efficiency requirements, as battery consumption can be minimized as much as possible.
[0089] A communication system comprises a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE) and an uplink (UL) that transmits signals from the UE to a receiving point such as a NodeB. A UE, also commonly referred to as a terminal or mobile station, can be fixed or mobile and can be a cellular phone, personal computer device, or automated device. An eNodeB is typically a fixed station and may also be referred to as an access point or other equivalent terms. For LTE systems, a NodeB is typically referred to as an eNodeB.
[0090] In communication systems such as LTE, DL signals can include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS), also known as pilot signals. The eNodeB transmits data information through the Physical DL Shared Channel (PDSCH). The eNodeB transmits DCI through the Physical DL Control Channel (PDCCH) or the Enhanced PDCCH (EPDCCH).
[0091] In response to a data transmission block (TB) from the UE, the eNodeB transmits acknowledgment information in the Physical Hybrid ARQ Indicator Channel (PHICH). The eNodeB transmits one or more types of RS, including UE Common RS (CRS), Channel State Information RS (CSI-RS), or Demodulated RS (DMRS). CRS is transmitted over the DL system bandwidth (BW) and can be used by the UE to obtain channel estimates to demodulate data or control information or perform measurements. To reduce CRS overhead, the eNodeB can transmit CSI-RS with a lower density than CRS in the time and / or frequency domains. DMRS can be transmitted only in the BW of each PDSCH or EPDCCH, and the UE can use DMRS to demodulate data or control information in the PDSCH or EPDCCH respectively. The transmission time interval of the DL channel is called a subframe and can have a duration of, for example, 1 millisecond.
[0092] The DL signal also includes the transmission of logical channels carrying system control information. When the DL signal transmits a Master Information Block (MIB), the BCCH is mapped to a transport channel called the Broadcast Channel (BCH), or when the DL signal transmits a System Information Block (SIB), it is mapped to the DL Shared Channel (DL-SCH). Most system information is included in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe can be indicated by transmitting a corresponding PDCCH, which transmits a codeword with Cyclic Redundancy Check (CRC) scrambled with system information RNTI (SI-RNTI). Optionally, scheduling information for SIB transmission can be provided in an earlier SIB, and scheduling information for the first SIB (SIB-1) can be provided by the MIB.
[0093] DL resource allocation is performed in subframe units and physical resource block (PRB) groups. A transmission BW comprises frequency resource elements called resource blocks (RBs). Each RB consists of N... EPDCCH Each subcarrier or resource element (RE) can have a total of 12 REs. One RB cell on a subframe is called a PRB. A total of [number] subcarriers or resource elements (REs) can be allocated to the UE for PDSCH transmission BW. n REs s =(n s0 +y·N EPDCCH )mod D of RB.
[0094] UL signals can include data signals for transmitting data information, control signals for transmitting UL control information (UCI), and UL RS. UL RS includes DMRS and SNR (Sounding RS). The UE only transmits DMRS in its respective PUSCH or PUCCH BW. The eNodeB can use DMRS to demodulate data signals or UCI signals. The UE transmits SRS to provide UL CSI to the eNodeB. The UE transmits data information or UCI through its respective Physical UL Shared Channel (PUSCH) or Physical UL Control Channel (PUCCH). If the UE needs to transmit data information and UCI in the same UL subframe, the UE can multiplex both in a single PUSCH. UCI includes: a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) message indicating a correct (ACK) or incorrect (NACK) detection of data TB in the PDSCH or the absence of a PDCCH detection (DTX); a Scheduling Request (SR) indicating whether the UE has data in its buffer; a Rank Indicator (RI); and Channel State Information (CSI) enabling the eNodeB to perform link adaptation for PDSCH transmissions to the UE. In response to the detection of a PDCCH / EPDCCH indicating the release of a semi-permanently scheduled PDSCH, a HARQ-ACK message is also sent by the UE.
[0095] A UL subframe consists of two time slots. Each time slot includes a space for transmitting data information, UCI, DMRS, or SRS. The frequency resource unit (RB) of the UL system BW is a symbol. A total of [number] RBs are allocated to the UE for transmitting the BW. The number of NRBs and RBs for each RE. For PUCCH, NRB = 1. The last subframe symbol can be used to multiplex SRS transmissions from one or more UEs. The number of subframe symbols available for data / UCI / DMRS transmissions is... If the last subframe symbol is used to transmit SRS, then NSRS = 1; otherwise, N... SRS =0.
[0096] Figure 5 A block diagram 500 of a transmitter for PDSCH in a subframe is shown according to an embodiment of the present disclosure. Figure 5 The embodiment of transmitter block diagram 500 shown is for illustrative purposes only. Figure 5 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Figure 5 This disclosure is not intended to limit the scope of any particular implementation of transmitter block diagram 500.
[0097] like Figure 5As shown, information bits 510 are encoded by encoder 520, such as a turbo encoder, and modulated by modulator 530, for example using quadrature phase shift keying (QPSK) modulation. A serial-to-parallel (S / P) converter 540 generates M modulation symbols, which are then provided to mapper 550 to map to REs selected by transmission BW selection unit 555 for a specified PDSCH transmission BW. Unit 560 applies an inverse fast Fourier transform (IFFT), and the output is then serialized by parallel-to-serial (P / S) converter 570 to create a time-domain signal, filtered by filter 580, and transmitted at 590. Additional features such as data scrambling, cyclic prefix insertion, time windowing, interleaving, and others are well known in the art and are not shown for the sake of brevity.
[0098] Figure 6 A receiver block diagram 600 for a PDSCH in a subframe is shown according to an embodiment of the present disclosure. Figure 6 The embodiment shown in Figure 600 is for illustrative purposes only. Figure 6 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Figure 6 The scope of this disclosure is not limited to any particular implementation of Figure 600.
[0099] like Figure 6 As shown, the received signal 610 is filtered by filter 620, the RE 630 for specifying the received BW is selected by BW selector 635, unit 640 applies Fast Fourier Transform (FFT), and the output is serialized by parallel-to-serial converter 650. Subsequently, demodulator 660 coherently demodulates data symbols by applying a channel estimate obtained from DMRS or CRS (not shown), and decoder 670, such as a turbo decoder, decodes the demodulated data to provide an estimate of information data bits 680. For simplicity, additional functions such as time windowing, cyclic prefix removal, descrambling, channel estimation, and deinterleaving are not shown.
[0100] Figure 7 A transmitter block diagram 700 for PUSCH in a subframe is shown according to an embodiment of the present disclosure. Figure 7 The embodiment of block diagram 700 shown is for illustrative purposes only. Figure 7 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Figure 7 This disclosure is not intended to limit the scope of any particular implementation of block diagram 700.
[0101] like Figure 7 As shown, information data bits 710 are encoded by encoder 720, such as a turbo encoder, and modulated by modulator 730. Discrete Fourier Transform (DFT) unit 740 applies DFT to the modulated data bits, RE 750 corresponding to the specified PUSCH transmission BW is selected by transmission BW selection unit 755, unit 760 applies IFFT, and after cyclic prefix insertion (not shown), filtering is applied by filter 770 and the signal is transmitted at 780.
[0102] Figure 8 A receiver block diagram 800 for a PUSCH in a subframe is shown according to an embodiment of the present disclosure. Figure 8 The embodiment of block diagram 800 shown is for illustrative purposes only. Figure 8 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Figure 8 This disclosure is not intended to limit the scope of any particular implementation of block diagram 800.
[0103] like Figure 8 As shown, the received signal 810 is filtered by filter 820. Subsequently, after removing the cyclic prefix (not shown), unit 830 applies FFT, RE 840 corresponding to the specified PUSCH receive BW is selected by receive BW selector 845, unit 850 applies inverse DFT (IDFT), demodulator 860 coherently demodulates data symbols by applying channel estimation obtained from DMRS (not shown), and decoder 870, such as turbo decoder, decodes the demodulated data to provide an estimate of information data bits 880.
[0104] In next-generation cellular systems, the envisioned use cases extend beyond the capabilities of LTE systems. The so-called 5G, or fifth-generation cellular system, requires the ability to operate both below and above 6 GHz (e.g., in millimeter wave mode). In 3GPP TR 22.891, 74 5G use cases have been identified and described; these use cases can be broadly categorized into three groups. The first group, known as “enhanced mobile broadband (eMBB),” targets high data rate services with less stringent latency and reliability requirements. The second group, known as “ultra-reliable and low-latency (URLL),” targets applications with less stringent data rate requirements but lower tolerance for latency. The third group, known as “massive MTC (mMTC),” targets connections of a large number of low-power devices, such as 1 million per square kilometer, with less stringent requirements for reliability, data rate, and latency.
[0105] To enable 5G networks to support diverse services with different qualities of service (QoS), a scheme called network slicing has been defined in the 3GPP specifications.
[0106] To effectively utilize PHY resources and reuse various slices (with different resource allocation schemes, parameter sets, and scheduling strategies) in DL-SCH, a flexible and self-contained frame or subframe design was used.
[0107] Figure 9 An example of reuse of two slices 900 according to an embodiment of the present disclosure is shown. Figure 9 The example shown, which reuses two slices 900, is for illustrative purposes only. Figure 9 One or more of the components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Figure 9 This disclosure is not intended to limit the scope of any particular implementation that reuses two slices 900.
[0108] The 3GPP NR specification supports up to 32 CSI-RS antenna ports, allowing gNBs to be equipped with a large number of antenna elements (such as 64 or 128). In this case, multiple antenna elements are mapped to a single CSI-RS port. Figure 9 As shown, for millimeter-wave bands, although the number of antenna elements can be larger for a given waveform factor, the number of CSI-RS ports (which can correspond to the number of digital precoding ports) tends to be limited by hardware constraints (such as the feasibility of installing a large number of ADCs / DACs at millimeter-wave frequencies). In this case, one CSI-RS port maps to a large number of antenna elements that can be controlled by a group of analog phase shifters 901. One CSI-RS port can correspond to a subarray that generates a narrow analog beam through analog beamforming 905. By changing the group of phase shifters across symbols or subframes, this analog beam can be configured to sweep a wider angle (920). The number of subarrays (equal to the number of RF chains) is related to the number of CSI-RS ports N. CSI-PORT Same. Digital beamforming unit 910 spans N CSI-PORT Linear combination is performed between the analog beams to further increase the precoding gain. While the analog beams are broadband (and therefore not frequency-selective), digital precoding can vary across frequency subbands or resource blocks. Receiver operation can be envisioned similarly.
[0109] Because the aforementioned system utilizes multiple analog beams for transmission and reception (whereby one or a few analog beams are selected from a large number of analog beams, for example, periodically after a training period), the term "multi-beam operation" is used to refer to this aspect of the entire system. For illustrative purposes, this includes indicating the assigned DL or UL transmit (TX) beam (also referred to as "beam indication"), measuring at least one reference signal for calculating and performing beam reporting (also referred to as "beam measurement" and "beam reporting," respectively), and receiving the DL or UL transmission via selecting the appropriate receive (RX) beam.
[0110] The above system is also applicable to higher frequency bands, such as >52.6 GHz (also known as FR4). In this case, the system can only use analog beams. Due to O2 absorption loss near 60 GHz (an additional loss of about 10 dB at a distance of 100 meters), more and sharper analog beams (and therefore a larger number of radiators in the array) will be needed to compensate for the additional path loss.
[0111] In 3GPP LTE and NR (New Radio Access or Interface), network access and radio resource management (RRM) are implemented by physical layer synchronization signals and higher-layer (MAC) procedures. Specifically, the UE attempts to detect the presence of a synchronization signal and at least one cell ID for initial access. Once the UE is in the network and associated with a serving cell, it monitors several neighboring cells by attempting to detect their synchronization signals and / or measuring the associated cell-specific RS (e.g., by measuring their RSRP). For next-generation cellular systems, an efficient and uniform radio resource acquisition or tracking mechanism is desired, applicable to various use cases (such as eMBB, URLLC, mMTC, each corresponding to different coverage requirements) and frequency bands (with different propagation losses). Seamless and low-latency RRM is also expected, most likely designed with different network and radio resource paradigms. These objectives raise at least the following questions when designing access, radio resource, and mobility management frameworks.
[0112] First, because NR can support even more diverse network topologies, the concept of a cell can be redefined or replaced by other radio resource entities. For example, in a synchronous network, a cell can be associated with multiple TRPs (transmit-receive points), similar to the COMP (Coordinated Multipoint Transmission) scenario in LTE. In this case, seamless mobility is the desired feature. Second, when utilizing large antenna arrays and beamforming, defining radio resources according to beams (although there may be different terminology) may be a natural approach. Assuming that many beamforming architectures can be utilized, it is desirable to have access, radio resource, and mobility management frameworks that are adaptable to various beamforming architectures (or, agnostic beamforming architectures). For example, the framework should be adaptable to whether or not a beam is formed for a single CSI-RS port (e.g., where multiple analog ports are connected to a single digital port and multiple widely spaced digital ports are utilized), or a beam is formed by multiple CSI-RS ports. Furthermore, regardless of whether beam scanning (e.g., ...) is used... Figure 9 As shown), this framework should apply to all cases. Third, different frequency bands and use cases will impose different coverage limitations. For example, millimeter-wave frequency bands will result in significant propagation loss. Therefore, some form of coverage enhancement solution is needed. Several alternatives include beam scanning (see...). Figure 9 (), repetition, diversity, and / or multiple TRP transmissions. For mMTC with small transmission bandwidth, time-domain repetition is required to ensure sufficient coverage.
[0113] A prerequisite for seamless access is significantly reducing higher-layer procedures for UEs already connected to the network. For example, when a UE moves from one cell to another (i.e., inter-cell mobility), the presence of cell boundaries (or the typical cell concept) necessitates RRC(L3) reconfiguration. For heterogeneous networks with closed subscriber groups, the additional overhead associated with higher-layer procedures can further burden the system. This can be achieved by relaxing cell boundaries to create large “supercells” where a large number of UEs can roam. In this context, high-capacity MIMO transmissions (especially MU-MIMO) become more prevalent. While this offers the opportunity to increase system capacity (measured by the number of sustainable UEs), it requires a simplified MIMO design. This presents challenges if implemented in current systems.
[0114] Therefore, an access, radio resource, and mobility management framework is needed that facilitates seamless access by reducing the number of higher-layer processes. Furthermore, a simplified MIMO design that is conducive to high-capacity MIMO transmission is also required.
[0115] In the 3GPP NR specification, multi-beam operation is primarily designed for a single transmit-receive point (TRP) and a single antenna panel. Therefore, the specification supports beam indication for a single TX beam, where the TX beam is associated with a reference RS. For DL beam indication and measurement, the reference RS can be an NZP (non-zero power) CSI-RS and / or an SSB (synchronization signal block, which includes the primary synchronizing signal, secondary synchronizing signal, and PBCH). Here, DL beam indication is accomplished via the Transmission Configuration Indicator (TCI) field in the DL-associated DCI, which includes an index to one (and only one) assigned reference RS. This is configured via higher-layer (RRC) signaling assumptions or a set of so-called TCI states, and, where applicable, by selecting / activating a subset of those TCI states for the TCI field code points via MAC CE. For UL beam indication and measurement, the reference RS can be an NZP CSI-RS, an SSB, and / or an SRS. Here, UL beam indication is accomplished through the SRS Resource Indicator (SRI) field in the UL-related DCI, which is linked to one (and only one) reference RS. This link is configured via higher-layer signaling using the SpatialRelationInfo (RRC) parameter. Essentially, only one TX beam is indicated to the UE.
[0116] In the 3GPP NR specification, beam management was designed to share the same framework as CSI acquisition. However, this compromised beam management performance, especially for FR2. This is because beam management primarily operates using analog beams (a characteristic of FR2), which is fundamentally different from CSI acquisition (designed with FR1 in mind). Therefore, beam management in the 3GPP NR specification becomes cumbersome and unlikely to keep up with more aggressive use cases requiring large numbers of beams and rapid beam switching (e.g., higher frequency bands, high mobility, and / or a greater number of narrower analog beams). Furthermore, the 3GPP NR specification was designed to accommodate many unknown or basic capabilities (e.g., the UE cannot perform beam communication). For the sake of flexibility, this leads to numerous options. This becomes burdensome for L1 control signaling, thus requiring many reconfigurations via RRC signaling (higher-layer configuration). While this avoids L1 control overhead, it either results in high latency (if reconfigurations are performed sparsely) or high PDSCH usage (because RRC signaling consumes PDSCH resources).
[0117] In the 3GPP NR specification, similar to LTE, the handover process for inter-cell mobility relies heavily on RRC (and even higher-layer) reconfiguration to update cell-specific parameters. Such reconfiguration is typically slow and introduces long delays (up to several milliseconds). For high-mobility UEs, this problem is exacerbated by the need for even more RRC reconfigurations due to the increased frequency of handovers.
[0118] For highly mobile UEs in FR2, the two latency issues mentioned above—one with a hierarchical NW structure (with visible cell boundaries) and the other with beam management—combine to exacerbate the latency problem and lead to frequent radio link failures (RLFs). Therefore, solutions / mechanisms that can reduce RLFs in highly mobile UEs in FR2 are needed.
[0119] One such solution / mechanism is based on a unified TCI (beam indication) framework, where a common beam (or TCI state) is used for both data (PDSCH / PUSCH) and control (PDCCH / PUCCH) transmission / reception, and also for DL and UL (e.g., when beam correspondence between DL and UL is established). In this multi-beam operation based on the common beam (or TCI state), the common beam (TCI state) indication / update must occur (independently) before the transmission / reception of control information (e.g., DCI associated with DL / UL in the PDCCH), which is scheduled for DL dispatch for DL data (PDSCH) or UL authorization for UL data (PUSCH). Note that 3GPP NR specification beam management supports multi-beam operation based on common beams, where the common beam for DL data (PDSCH) and control (PDCCH) is indicated via MAC-CE based signaling (when the higher-layer parameter tci-PresentInDCI in PDSCH-Config is not "enabled"). However, for the reasons mentioned above, such MAC-CE based common beam activation is too slow.
[0120] Because the TCI state of the data beam is updated in a time slot (or subframe) preceding the DCI carrying the scheduling DL assignment or UL authorization, there may be some performance penalty compared to situations where the TCI state update of the data beam is performed together with the DL assignment or UL authorization. This problem may be more severe for highly mobile UEs that require frequent / precise updates of the data beam for seamless data transmission / reception. Several embodiments and examples are provided in this disclosure to address this issue.
[0121] In this disclosure, the term "activation" describes an operation in which the UE receives and decodes a signal representing a time start point from the network (or gNB). The start point can be a current or future time slot / subframe or symbol—the exact location is implicitly or explicitly indicated, or it can be fixed or configured by a higher layer. Upon successful decoding of the signal, the UE responds accordingly. The term "deactivation" describes an operation in which the UE receives and decodes a signal representing a time stop point from the network (or gNB). The stop point can be a current or future time slot / subframe or symbol—the exact location is implicitly or explicitly indicated, or it can be fixed or configured by a higher layer. Upon successful decoding of the signal, the UE responds accordingly.
[0122] Terms such as TCI, TCI status, SpatialRelationInfo, target RS, reference RS, and others are for illustrative purposes and are therefore not normative. Other terms referring to the same function may also be used.
[0123] A “reference RS” corresponds to a set of characteristics of a DL or UL TX beam (such as orientation, precoding / beamforming, number of ports, etc.). For example, when a UE receives a reference RS index / ID in a DL assignment represented by a TCI state, the UE applies the known characteristics of the reference RS to the assigned DL transmission. The reference RS can be received and measured by the UE (in this case, the reference RS is a downlink signal such as NZP CSI-RS and / or SSB), and the UE can use the measurement results to calculate a beam report (in Rel. 15NR, at least one L1-RSRP is accompanied by at least one CRI). When the NW / gNB receives a beam report, the NW can be better equipped with information to assign a specific DL TX beam to the UE. Alternatively, the reference RS can be transmitted by the UE (in this case, the reference RS is a downlink signal such as SRS). When the NW / gNB receives the reference RS, the NW / gNB can measure and calculate the information needed to assign a specific DL TX beam to the UE. This option applies when a DL-UL beam pairing is established.
[0124] Reference RS can be dynamically triggered by NW / gNB (e.g., via DCI in the case of aperiodic RS), pre-configured with specific time-domain behavior (e.g., period and offset in the case of periodic RS), or a combination of such pre-configuration and activation / deactivation (in the case of semi-persistent RS).
[0125] The following examples illustrate DL multi-beam operation utilizing DL beam indication after the network (NW) receives some transmissions from the UE. In the first example embodiment, aperiodic CSI-RS is transmitted by the NW and measured by the UE. Although aperiodic RS is used in both examples, periodic or semi-persistent RS can also be used.
[0126] For millimeter wave (or FR2) or higher frequency bands where multi-beam operation is particularly relevant (such as >52.6 GHz or FR4), the transmit-receive procedure involves the receiver selecting a receive (RX) beam for a given TX beam. For UL multi-beam operation, the gNB selects a UL RX beam for each 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 configures the UE to transmit the UL RS (which is associated with the selection of the UL TX beam). After receiving and measuring the UL RS, the gNB selects the UL RX beam. As a result, TX-RX beam pairs are derived. The NW / gNB can perform this operation for all configured reference RSs (each reference RS or "beam scan") and determine all TX-RX beam pairs associated with all reference RSs configured for the UE. On the other hand, when a DL RS (such as a CSI-RS and / or SSB) is used as a reference RS (as relevant when DL-UL beam correspondence or reciprocity is established), the NW / gNB sends an RS to the UE (for UL and reciprocity, this corresponds to the UL RX beam). In response, the UE measures the reference RS (and selects the UL TX beam in the process) and reports the beam metric associated with the quality of the reference RS. In this case, the UE determines a TX-RX beam pair for each configured (DL) reference RS. Therefore, although this knowledge is unavailable to the NW / gNB, the UE can select the UL TX beam from the knowledge about all TX-RX beam pairs when it receives the reference RS (and therefore the UL RX beam) indication from the NW / gNB.
[0127] In this disclosure, the term "resource indicator" is also abbreviated as REI and is used to refer to an indicator of RS resources used for signal / channel and / or interference measurements. This term is for illustrative purposes and can therefore be replaced by any other term referring to the same function. Examples of REI include the aforementioned CSI-RS resource indicator (CRI) and SSB resource indicator (SSB-RI). Any other RS can also be used for signal / channel and / or interference measurements, such as DMRS.
[0128] exist Figure 10 One example shown illustrates the UL Multibeam Operation 1000. Figure 10 The illustrated embodiment of the UL multi-beam operation 1000 is for illustrative purposes only. Figure 10 This disclosure is not intended to limit the scope of any particular implementation of the UL Multibeam Operation 1000.
[0129] UL multi-beam operation 1000 begins with the gNB / NW signaling to the UE a non-periodic CSI-RS (AP-CSI-RS) trigger or indication (step 1001). This trigger or indication may be included in the DCI (UL-related or DL-related, signaled separately or jointly with the non-periodic CSI request / trigger) and indicates the transmission of AP-CSI-RS in the same time slot (zero time offset) or in a subsequent time slot / subframe (>0 time offset). Upon receiving the AP-CSI-RS sent by the gNB / NW (step 1002), the UE measures the AP-CSI-RS and then calculates and reports a "beam metric" (indicating the quality of a specific TX beam assumption) (step 1003). Examples of such beam reporting are CSI-RS resource indicators (CRI) or SSB resource indicators (SSB-RI) and their associated L1-RSRP / L1-RSRQ / L1-SINR / CQI. When the NW receives a beam report from the UE, it can use the beam report to select a UL TX beam for the UE and use the SRI field in the UL-related DCI (which carries UL authorization, such as DCI format 0_1 in the NR) to indicate the UL TX beam selection (step 1004). The SRI corresponds to the “target” SRS resource linked to the reference RS (in this case, AP-CSI-RS) via SpatialRelationInfo configuration. Upon successful decoding of the UL-related DCI using the SRI, the UE performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam associated with the SRI (step 1005).
[0130] exist Figure 11 Another example shown illustrates the UL Multibeam Operation 1100. Figure 11 The illustrated embodiment of the UL multi-beam operation 1100 is for illustrative purposes only. Figure 11 This disclosure is not intended to limit the scope of any particular implementation of the UL Multibeam Operation 1100.
[0131] UL multi-beam operation 1100 begins with the gNB / NW signaling to the UE a non-periodic SRS (AP-SRS) trigger or request (step 1101). This trigger can be included in the DCI (UL-related or DL-related). After receiving and decoding the AP-SRS trigger (step 1102), the UE sends the AP-SRS to the gNB / NW (step 1103), allowing the NW (or gNB) to measure the UL propagation channel and select a UL TX beam for the UE. The gNB / NW can then indicate the UL TX beam selection using the SRI field in the UL-related DCI (which carries UL authorization, such as DCI format 0_1 in NR) (step 1104). The SRI corresponds to the “target” SRS resource linked to the reference RS (in this case, the AP-SRS) via SpatialRelationInfo configuration. Upon successful decoding of the UL-related DCI using the SRI, the UE performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam associated with the SRI (step 1105).
[0132] exist Figure 12 Another example shown illustrates the DL multi-beam operation 1200. Figure 12 The illustrated embodiment of the DL multi-beam operation 1200 is for illustrative purposes only. Figure 12 The scope of this disclosure is not limited to any particular implementation of the DL multi-beam operation 1200.
[0133] exist Figure 12In the example shown, where the UE is configured to measure / receive aperiodic CSI-RS (AP-CSI-RS) and report aperiodic CSI (AP CSI), DL multi-beam operation 1200 begins with the gNB / NW signaling to the UE that an aperiodic CSI-RS (AP-CSI-RS) trigger or indication has been made (step 1201). This trigger or indication may be included in the DCI (UL-related or DL-related, signaled separately or jointly with the aperiodic CSI request / trigger) and indicates the transmission of AP-CSI-RS in the same time slot (zero time offset) or in a subsequent time slot / subframe (>0 time offset). Upon receiving the AP-CSI-RS sent by the gNB / NW (step 1202), the UE measures the AP-CSI-RS and then calculates and reports the "beam metric" (included in the CSI, indicating the quality of a specific TX beam assumption) (step 1203). An example of such a beam report (supported in the 3GPP NR specification) is a CSI-RS resource indicator (CRI) or SSB resource indicator (SSB-RI) and its associated L1-RSRP and / or L1-SINR. When a beam report is received from the UE, the NW / gNB can use the beam report to select a DL TX beam for the UE and indicate the DL TX beam selection using the TCI field in the DL-related DCI (which carries the DL assignment, such as DCI format 1_1 in NR) (step 1204). The TCI state corresponds to a reference RS (in this case, AP-CSI-RS) defined / configured via the TCI state definition (configured with higher-layer / RRC, activating a subset of DCI-based selection via MAC CE). Upon successful decoding of the DL-related DCI with the TCI field, the UE performs DL reception (such as data transmission over PDSCH) using the DL TX beam associated with the TCI field (step 1205). In this example embodiment, only one DL TX beam is indicated to the UE.
[0134] To facilitate rapid beam management, one requirement is to simplify the basic components (building blocks) used for beam management. One function of beam management is beam selection, which includes functions such as beam measurement (including training), reporting (via the UL control channel for DL beam management), and indication (via the DL control channel for both DL and UL beam management). Once the building blocks are simplified [Step 1], additional advanced features can be added to facilitate faster beam management [Step 2].
[0135] In U.S. Patent Application Serial No. 16 / 949,246, filed October 21, 2020, the disclosure of which is incorporated herein by reference, proposes a “slim mode” [Step 1] with such basic components for fast beam management. Due to its compact nature, the slim mode design can facilitate faster updates / reconfigurations via lower-level control signaling. In other words, L1 control signaling will be the primary signaling mechanism, and higher layers (such as MAC CE or RRC) will only be used when necessary. Here, L1 control signaling includes the use of UE group DCI as well as dedicated (UE-specific) DCI.
[0136] The aforementioned additional advanced features can include the extension of beam management (multi-beam operation) from intra-cell mobility to inter-cell mobility. Using such a mechanism, seamless access / mobility for RRC_CONNECTED (RRC_connected) UEs can be achieved as if no cell boundary were observed unless the UE was in an initial access or similar state. Another advanced feature includes mechanisms to minimize beam failure (BF) or radio link failure (RLF), such as low-overhead, faster beam handover / selection and UE-initiated / event-triggered beam management. With such preventative mechanisms, beam failure recovery (BFR) is less likely to be used.
[0137] In this disclosure, signaling mechanisms for implementing the aforementioned fast (dynamic) multi-beam operation are considered. In particular, indication of a common beam (TCI state) via a separate DCI is considered, wherein the indicated beam is common to both data and control (as described above).
[0138] In the remainder of this disclosure, the term "beam" may be associated with the spatial transmission / reception of resource signals (RS) from a "port," "antenna port," or "virtual antenna / port." Similarly, the term "transmit (TX) beam" may be associated with the spatial transmission of resource signals (RS) or channels from a "port," "antenna port," or "virtual antenna / port," and the term "receive (RX) beam" may be associated with the spatial reception of resource signals (RS) or channels from a "port," "antenna port," or "virtual antenna / port." The spatial transmission / reception of beams can occur in three-dimensional (3D) space. In beamforming wireless systems, the transmission and reception of wireless signals can be via multiple TX and multiple RX beams.
[0139] This disclosure considers dynamic, L1-controlled or DCI-based common beam indication mechanisms. For illustrative purposes, the following symbols / terms are used in this disclosure. Other terms may also be used to represent the same functions and operations:
[0140] - The DCI that indicates the common beam used for both DL and UL data (PDSCH / PUSCH) and control (PDCCH / PUCCH) is called TCI-DCI (for example, when beam correspondence between DL and UL is established).
[0141] - The DCI that indicates the common beam used for data (PDSCH) and control (PDCCH) in DL is called DL-TCI-DCI.
[0142] - The DCI that indicates the common beam used for UL's data (PUSCH) and control (PUCCH) is called UL-TCI-DCI.
[0143] - The DCI for scheduling DL assignment is called DL-DCI, and
[0144] - A DCI authorized by UL is called a UL-DCI.
[0145] In some embodiments of this disclosure, the beam pointer for DL reception is a reference / source RS with QCL information of QCL type = Type D, and the beam pointer for UL transmission is spatial relationship information (e.g., associated with the reference / source RS).
[0146] In some embodiments of this disclosure, DL-TCI-DCI (which includes a common beam or TCI state) is a new DCI format different from DL-DCI formats (e.g., DCI formats 1_0, 1_1, and 1_2 in the Rel.15NR specification). Optionally, DL-TCI-DCI (which includes a common beam or TCI state) is one of the DL-DCI formats (e.g., DCI formats 1_0, 1_1, and 1_2 in the Rel.15NR specification). Alternatively, DL-TCI-DCI (which includes a common beam or TCI state) can be a new DCI format or one of the DL-DCI formats (e.g., DCI formats 1_1 and 1_2 in the Rel.15NR specification), where information regarding whether it is a new format or an existing format can be configured (e.g., via RRC). In the example, whether DL-TCI-DCI can be a new TCI format depends on the UE's capability (reported by the UE). That is, DL-TCI-DCI can only be a new DCI format if the UE reports that it can receive the new DCI format; otherwise, it is the existing DCI format.
[0147] Similarly, in some embodiments of this disclosure, UL-TCI-DCI (including the common beam or TCI state) is a new DCI format different from UL-DCI formats (e.g., DCI formats 0_0, 0_1, and 0_2 in the Rel.15NR specification). Optionally, UL-TCI-DCI (including the common beam or TCI state) is one of the UL-DCI formats (e.g., DCI formats 0_0, 0_1, and 0_2 in the Rel.15NR specification). Optionally, UL-TCI-DCI (which includes the common beam or TCI state) can be a new DCI format or one of the DL-DCI formats (e.g., DCI formats 0_0, 0_1, and 0_2 in the Rel.15NR specification), where information on whether it is a new format or an existing format can be configured (e.g., via RRC). In the example, whether UL-TCI-DCI can be a new TCI format depends on the UE's capability (reported by the UE). That is, UL-TCI-DCI can only be a new DCI format if the UE reports that it can receive the new DCI format; otherwise, it is the existing DCI format.
[0148] In some embodiments of this disclosure, the TCI-DCI (which includes a common beam or TCI state) is a new DCI format different from DL- or UL-DCI formats (e.g., DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2 in the Rel.15NR specification). Optionally, the TCI-DCI (including a common beam or TCI state) is one of the DL- or UL-DCI formats (e.g., DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2 in the Rel.15NR specification). Optionally, the TCI-DCI (including a common beam or TCI state) can be a new DCI format or one of the DL- or UL-DCI formats (e.g., DCI formats 0_0, 0_1, 0_2, 1_0, 1_1, and 1_2 in the Rel.15NR specification), wherein information regarding whether it is a new format or an existing format can be configured (e.g., via RRC). In one example, whether TCI-DCI can be a new TCI format depends on the UE's capability (reported by the UE). That is, TCI-DCI can only be a new DCI format if the UE reports that it can receive the new DCI format; otherwise, it is the existing DCI format.
[0149] Component 1: DL Beam Indication (DCI)
[0150] Figure 13 Example 1300 of a dedicated DCI is shown, indicating a common beam for receiving DL control and data. Figure 13 The embodiment 1300 shown in the diagram, which indicates a dedicated DCI for receiving DL control and data via a common beam, is for illustrative purposes only. Figure 13This disclosure is not intended to limit the scope to any particular implementation of Example 1300 of a dedicated DCI that indicates a common beam for receiving DL control and data.
[0151] In Example I.1, as Figure 13 As shown, the UE is configured to receive a dedicated DCI (DL-TCI-DCI) indicating a common beam (TCI state) for receiving DL control (PDCCH) and data (PDSCH). The UE receives (e.g., in DL-TCI-DCI format) and decodes the DL-TCI-DCI in time slot (or subframe) N, and begins receiving DL control (PDCCH) in the same (time slot N) or a subsequent time slot using the indicated beam (TCI state). For illustration, assuming X is the gap (number of time slots / subframes) between the time slot carrying the DL-TCI-DCI and the time slot carrying DL control, the UE begins receiving DL control in time slot N+X. The UE decodes the DL-DCI contained in the PDCCH (e.g., in DL-DCI format) to obtain scheduling information for DL dispatch. The UE then receives DL data (PDSCH, according to DL dispatch) in time slot N+X+K0 using the indicated beam (TCI state). Here, the value of X is fixed. Alternatively, the value of X can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (DL-TCI-DCI and / or DL-DCI), the value of X is not configured or set in a specific way. That is, the time unit location (e.g., time slot, subframe) used to signal DL-TCI-DCI can be different from the time unit location used to signal DL-DCI. In some examples, X may also be referred to as the Downlink Beam Application Time (DL-BAT) value B. In some examples, X is a lower bound of B, i.e., X ≥ B.
[0152] In the example, the units of N and / or X and / or K0 are defined based on the number of OFDM symbols. The value X is measured from the end of DL-TCI-DCI decoding (i.e., the last symbol carrying DL-TCI-DCI) and the beginning of DL-DCI reception (i.e., the first symbol carrying DL-DCI), or the value X is determined as the first time slot at least Pms or Q symbols after DL-TCI-DCI with common beam indication, where P or Q can be fixed, configured, or determined / configured based on a UE capability report. Similarly, the value K0 is measured from the end of DL-DCI decoding (i.e., the last symbol carrying DL-DCI) and the beginning of PDSCH reception (i.e., the first symbol carrying PDSCH). In the remainder of this disclosure, the units of N, X, and K0 are assumed to be time slots (i.e., subframes). However, the embodiments of this disclosure are general and applicable to any unit, such as the number of OFDM symbols.
[0153] In the example, the value of X is set / determined based on the UE's processing limitations (i.e., processing latency) or capabilities. When a new beam (TCI state) is indicated via DL-TCI-DCI, it can be used for DL-DCI reception no earlier than X time (slot, subframe, or OFDM symbol), where X depends on (or is based on) the UE's capabilities.
[0154] In one example, the UE is configured / triggered to have a PUCCH transmission (e.g., for HARQ-ACK feedback) that can be associated with DL (e.g., PDSCH) reception, which is triggered (or scheduled) by DL-DCI. In this case, the TCI state (beam) of the PUCCH transmission is indicated / updated via UL-TCI-DCI (see Examples I.4 to I.6 below) or DL-TCI-DCI. The time slot between DL-TCI-DCI / UL-TCI-DCI reception and PUCCH transmission can be N+X+K0+J, where J is the time slot (number of time slots, subframes, or OFDM symbols) between PDSCH reception and PUCCH transmission, and J can be fixed or configured from a set of candidate values.
[0155] When a PDCCH carrying DL-TCI-DCI is associated (configured) with a HARQ-ACK (or ACK / NACK) feedback (e.g., via PUCCH transmission) indicating that the UE receives an updated common beam, the beam application time can include the time between PDCCH reception (from the start or end of PDCCH reception) and the corresponding PUCCH transmission (from the start or end of PUCCH transmission), i.e., X = Y1 + Y2, where Y1 = the time between PDCCH reception and PUCCH transmission, and Y2 = the time between PUCCH transmission and DL-DCI reception. Alternatively, the beam application time is equal to Y2. In this case, the TCI state (beam) used for PUCCH transmission can be the latest (previous) beam indicated via DL-TCI-DCI prior to the new / updated TCI state in the current timeslot.
[0156] The beam (or TCI state) for receiving DL-TCI-DCI in slot N can be the beam (or TCI state) indicated via the latest DL-TCI-DCI in an earlier slot M < N. If the latest DL-TCI-DCI is not received or not configured, a default beam can be used. For example, the default beam for PDCCH reception in Rel.15 / 16 NR can be used. Alternatively, the beam (or TCI state) for receiving DL-TCI-DCI can be the beam for receiving the DL channel and / or DL RS in an earlier slot M < N. Alternatively, the beam (or TCI state) for receiving DL-TCI-DCI can be associated with the beam for transmitting the UL channel and / or UL RS in an earlier slot M < N. Alternatively, the beam (or TCI state) for receiving DL-TCI-DCI can be associated with the beam for receiving the SSB associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Alternatively, the beam (or TCI state) for receiving DL-TCI-DCI can be associated with the beam for receiving the CSI-RS associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Optionally, instead of using the default beam to receive DL-TCI-DCI in slot N, the beam (or TCI state) for receiving DL-TCI-DCI can be signaled via a MAC CE. For example, the mechanism supported in Rel.15 / 16 NR for updating the TCI state of the PDCCH can be reused to update the TCI state (beam) for receiving DL-TCI-DCI).
[0157] At least one of the following examples can be used to determine the values of X and K0.
[0158] In Example I.1.1, X is fixed, for example, fixed as X = 0 (described below) or X = 1. That is, DL-TCI-DCI is received X time slots / subframes before each DL-DCI, or before the first DL-DCI in a plurality of DL-DCIs (when DL-TCI-DCI indicates the TCI state for receiving multiple DL-DCIs). The value of parameter K0 can be configured via DL-DCI. Alternatively, parameter K0 can be configured via MAC CE-based signaling. Alternatively, parameter K0 can be configured via RRC signaling. Alternatively, parameter K0 can be configured via a combination of MAC-CE and RRC signaling. Alternatively, parameter K0 can be configured via a combination of MAC-CE and DL-DCI signaling. Alternatively, parameter K0 can be configured via a combination of DL-DCI and RRC signaling. Alternatively, parameter K0 can be configured via a combination of DL-DCI, MAC-CE, and RRC signaling. This example is particularly relevant when signaling DL-TCI-DCI to each UE (as opposed to a group of UEs).
[0159] In Example I.1.2, X and K0 are configured via two independent parameters. The value of parameter K0 can be configured via DL-DCI. Alternatively, parameter K0 can be configured via MAC CE-based signaling. Alternatively, parameter K0 can be configured via RRC signaling. Alternatively, parameter K0 can be configured via a combination of MAC-CE and RRC signaling. Alternatively, parameter K0 can be configured via a combination of MAC-CE and DL-DCI signaling. Alternatively, parameter K0 can be configured via a combination of DL-DCI and RRC signaling. Alternatively, parameter K0 can be configured via a combination of DL-DCI, MAC-CE, and RRC signaling.
[0160] The value of X can be selected from a set of values (including or excluding X=0). Similarly, the value of parameter X can be configured via DL-TCI-DCI. Alternatively, parameter X can be configured via MAC CE-based signaling. Alternatively, parameter X can be configured via RRC signaling. Alternatively, parameter X can be configured via a combination of MAC-CE and RRC signaling. Alternatively, parameter X can be configured via a combination of MAC-CE and DL-TCI-DCI signaling. Alternatively, parameter X can be configured via a combination of DL-TCI-DCI and RRC signaling. Alternatively, parameter X can be configured via a combination of DL-TCI-DCI, MAC-CE, and RRC signaling.
[0161] In Example I.1.3, X and K0 are configured via joint parameters. The (value) of parameter (X, K0) can be configured via DL-TCI-DCI. Alternatively, parameter (X, K0) can be configured via MAC CE-based signaling. Alternatively, parameter (X, K0) can be configured via RRC signaling. Alternatively, parameter (X, K0) can be configured via a combination of MAC-CE and RRC signaling. Alternatively, parameter (X, K0) can be configured via a combination of MAC-CE and DL-TCI-DCI signaling. Alternatively, parameter (X, K0) can be configured via a combination of TCI-DCI and RRC signaling. Alternatively, parameter (X, K0) can be configured via a combination of DL-TCI-DCI, MAC-CE, and RRC signaling. The value of X can be selected from the set of values for (X, K0) (including or excluding X = 0).
[0162] In Example I.1.4, K0 is configured, and X can be implicitly derived based on the value of K0. The configuration of parameter K0 is based on at least one example in Example I.1.1.
[0163] In Example I.1.5, X is configured, and K0 can be implicitly derived based on the value of X. The configuration of parameter X is based on at least one example in Example I.1.2.
[0164] In Example I.1.6, due to the (aperiodic) nature of DCI signaling (DL-TCI-DCI and / or DL-DCI), the value of X is not configured, used, and / or set in a specific manner. Here, the UE monitors the presence of DL-TCI-DCI and DL-DCI in each slot / subframe by detecting the presence of the associated ID (such as C-RNTI, group-RNTI, or TCI-RNTI). In this case, the location of the associated DL-TCI-DCI can be in any slot relative to the location of the DL-DCI. The applicability of the TCI state signaled in the DL-TCI-DCI can be determined based on its location relative to the DL-DCI, for example, to ensure sufficient time to decode the DL-TCI-DCI so that the TCI state is applicable to some subsequent DL-DCIs. For example, the UE assumes the minimum TCI state (beam) switching time (in terms of the number of slots / subframes or ODFM symbols) between the end of DL-TCI-DCI decoding (i.e., the last symbol carrying DL-TCI-DCI) and the start of DL-TCI reception (i.e., the first symbol carrying DL-DCI). In one example, this switching time is reported by the UE in its capability signaling (either fixed or configured to the UE).
[0165] Figure 14Example 1400 of receiving DL-TCI-DCI and DL-DCI in the same time slot or subframe is shown. Figure 14 The shown example 1400 of receiving DL-TCI-DCI and DL-DCI in the same time slot or subframe is for illustration only. Figure 14 The scope of the present disclosure is not limited to any specific implementation in example 1400 of receiving DL-TCI-DCI and DL-DCI in the same time slot or subframe.
[0166] In at least one of the above embodiments (or examples), as Figure 14 shown, when the value of parameter X = 0, the UE is configured to receive DL-TCI-DCI and DL-DCI in the same time slot (or subframe) N. The UE receives / decodes DL-TCI-DCI and DL-DCI in time slot (or subframe) N, and obtains the indicated beam (TCI state) from DL-TCI-DCI and the scheduling information for DL dispatch from DL-DCI. Then, the UE receives DL data (PDSCH) according to the DL dispatch using the indicated beam in time slot N+K0.
[0167] Since DL-DCI and DL-TCI-DCI are received in the same time slot, the UE cannot use the beam indicated via DL-TCI-DCI to receive DL control (PDCCH carrying DL-DCI) in the current time slot. The beam (or TCI state) for receiving DL-TCI-DCI and DL-DCI in time slot N can be the beam indicated via the latest DL-TCI-DCI in an earlier time slot M < N, or optionally, the latest TCI state applicable to the DL-DCI signaled via other means. If the latest DL-TCI-DCI is not received or not configured, the default beam can be used. For example, the default beam for PDCCH reception in Rel.15 / 16 NR can be used. Alternatively, the beam (or TCI state) for receiving DL-TCI-DCI and DL-DCI can be the beam for receiving DL channels and / or DL RS in an earlier time slot M < N. Or, the beam (or TCI state) for receiving DL-TCI-DCI and DL-DCI can be associated with the beam for transmitting UL channels and / or UL RS in an earlier time slot M < N. Optionally, instead of using the default beam to receive DL-TCI-DCI and DL-DCI in time slot N, the beam (or TCI state) for receiving DL-TCI-DCI can be signaled via MAC CE. For example, the mechanism for updating the TCI state of PDCCH supported in Rel.15 / 16 NR can be reused to update the TCI state (beam) for receiving DL-TCI-DCI.
[0168] When DL-TCI-DCI and DL-DCI are received in the same time slot, at least one of the following examples can be applied.
[0169] In Example I.1.7, DL-TCI-DCI and DL-DCI correspond to (or are functionally combined into) a single (joint) DCI that includes all DCI fields of both DL-TCI-DCI and DL-DCI. In one example, this joint DCI is labeled DL-TCI-DCI. In another example, this joint DCI is labeled DL-DCI (e.g., formats 1_0, 1_1, and 1_2 in the NR specification). In one example, the DL DCI format may include one or both of the common beam (TCI state) and DL assignment. At least one of the following examples can be used / configured.
[0170] In Example I.1.7.1, the UE decodes the DL_DCI and determines whether only one or both of the common beam (TCI state) and DL dispatch are included. For example, when the TCI state field in the DCI takes a value (e.g., 0), it indicates that the TCI state (or common beam) is not indicated (or does not exist). Similarly, when the parameter in the dispatch field of the DCI takes a value (e.g., 0), it indicates that there is no DL dispatch (does not exist).
[0171] - In Example I.1.7.2, information about whether to include only one or both of the common beam (TCI state) and DL assignment can be configured or activated via MAC CE.
[0172] Figure 15 The following is a decoding example 1500 of DL-TCI-DCI and DL-DCI. Figure 15 The DL-TCI-DCI and DL-DCI decoding examples 1500 shown are for illustrative purposes only. Figure 15 This disclosure is not intended to limit the scope to any particular implementation of Example 1500 that decodes DL-TCI-DCI and DL-DCI.
[0173] In Example I.1.8, DL-TCI-DCI can be independent of DL-DCI, but they reside in the same time slot. Several examples are as follows: Figure 15As shown. In one example, the decoding of TCI-DCI and DL-DCI is independent. In another example, the decoding of TCI-DCI and DL-DCI is not independent. For example, the UE needs to decode DL-TCI-DCI first, and then decode DL-DCI. If the decoding of DL-TCI-DCI fails, the decoding of DL-DCI also fails. In the latter example, DL-TCI-DCI and DL-DCI can be the first and second stages of a two-stage DCI, respectively (see Examples 2.5 and 4).
[0174] In any of the previously described and subsequent examples and embodiments associated with X = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X. In other words, any such example or embodiment can be utilized without any parameterization of X or setting an offset parameter (such as X) to 0.
[0175] In one embodiment 1.2, the UE can be configured with higher-layer parameters (and / or MAC CE and / or DL-DCI fields) to implement TCI status (beaming) indication via DL-TCI-DCI. For example, depending on the configuration of DL-DCI and / or DL-TCI-DCI, the UE can be configured to derive its TCI status update from DL-DCI and / or DL-TCI-DCI. Similar to embodiment 1.1, as... Figure 13 As shown, the UE is configured to receive a dedicated DCI (DL-TCI-DCI), which indicates a common beam (TCI state) for receiving DL control (PDCCH) and data (PDSCH). The UE receives (e.g., in DL-TCI-DCI format) and decodes the DL-TCI-DCI in time slot (or subframe) N, and begins receiving DL control (PDCCH) in time slot N+X (assuming X>0) using the indicated beam (TCI state). The UE decodes the DL-DCI (e.g., in DL-DCI format) contained in the PDCCH to obtain scheduling information for DL dispatch. The UE then receives DL data (PDSCH, according to DL dispatch) in time slot N+X+K0 using the indicated beam (TCI state). Here, the value of X is fixed. Alternatively, the value of X can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (DL-TCI-DCI and / or DL-DCI), the value of X is not configured or set in a specific way. In other words, the time unit position (e.g., time slot, subframe) used to signal DL-TCI-DCI can be different from the time unit position used to signal DL-DCI. The method for setting the X and K0 values is similar to the method applicable to Embodiment I.1.
[0176] In any of the previously described and subsequent examples and embodiments associated with X = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X. In other words, any such example or embodiment can be utilized without any parameterization of X or by setting the offset parameter (e.g., X) to 0.
[0177] In Example I.2.1, when using or configuring the offset parameter X, the resulting UE procedure can depend on the value of X. For example, when X = 0, there is no DL-TCI-DCI (not received and / or not configured) (or DL-TCI-DCI and DL-DCI correspond to (or functionally combine into) a single (joint) DCI (see Example I.1.7)), and the TCI status indication / update exists and is signaled / received in the DL-DCI (and for receiving DL data); and when X > 0, the DL-TCI-DCI exists (is configured and therefore can be received), and the TCI status indication / update exists and is signaled / received in the DL-TCI-DCI (and for receiving DL data associated with DL dispatch in the DL-DCI and both DL control including the DL-DCI).
[0178] In Example I.2.2, the resulting UE procedure can be based on higher-layer (RRC) parameters, such as tci-dci-IsPresent (tci-dci-existence), regardless of whether offset parameter X is used / configured. When tci-dci-IsPresent is set to "enabled", DL-TCI-DCI exists (is configured and therefore can be received), and the TCI status indication / update is the TCI status indication / update in DL-TCI-DCI (and is used to receive DL data associated with DL dispatch in DL-DCI and DL control including DL-DCI). Otherwise, DL-TCI-DCI does not exist (is not received and / or is not configured) (or DL-TCI-DCI and DL-DCI correspond to (or functionally combine into) a single (joint) DCI, see Example I.1.7), and the TCI status indication / update exists and is signaled / received in DL-DCI (and is used to receive DL data).
[0179] In Example I.2.3, regardless of whether the offset parameter X is used / configured, and regardless of whether the higher-level parameter controlling the presence of DL-TCI-DCI (e.g., tci-dci-IsPresent) is used / configured, the resulting UE procedure can (also) be based on the higher-level parameter tci-PresentInDCI in the PDSCH-Config (which controls the presence of DL-DCI). For example, when the parameter tci-dci-IsPresent is "enabled" and tci-PresentInDCI in the PDSCH-Config is also "enabled," both DL-TCI-DCI and DL-DCI exist (are configured and therefore can be received). In this case, the TCI status indication / update applicable to decoding DL-DCI (in the relevant PDCCH) is signaled / received in the latest (most recent) DL-TCI-DCI, while the TCI status indication / update applicable to decoding DL data dispatched in the relevant PDSCH (related to DL dispatch in DL-DCI) is signaled / received in the latest (most recent) DL-DCI. When the parameter tci-dci-IsPresent is "Enabled" and tci-PresentInDCI in PDSCH-Config is not "Enabled", DL-TCI-DCI exists (is configured and therefore can be received), and the TCI status indication / update is the TCI status indication / update in DL-TCI-DCI (and is used to receive DL data associated with DL dispatch in DL-DCI and both DL control including DL-DCI).
[0180] In Example I.2.4, the obtained UE procedure can be activated based on higher-layer (RRC) parameters and / or MAC CE, regardless of whether the offset parameter X is used / configured.
[0181] In Example I.2.5, the obtained UE procedure can be based on system information (i.e., for all UEs in the cell) regardless of whether the offset parameter X is used / configured.
[0182] In one embodiment I.3, the UE can use the RRC Information Element (IE) sps-Config to configure semi-persistent scheduling (SPS) for DL data (PDSCH), which includes configuration for cs-RNTI (an RNTI for receiving DCI to activate / release SPS). Since the gNB can activate / reactivate / release SPS at any time using DCI (e.g., DCI format 1_1 or 1_2 in NR), the UE will monitor the PDCCH in each slot using a CRC scrambled by the cs-RNTI. In SPS, the UE is configured to receive PDSCH without any DL-TCI (as explained in the dynamic scheduling above).
[0183] In Example I.3.1, the UE is configured to receive a dedicated DCI (DL-TCI-DCI) that indicates a common beam (TCI state) for receiving DL control (PDCCH) and, if activated by the received PDCCH, also for receiving DL data (PDSCH). The UE receives (e.g., in DL-TCI-DCI format) and decodes the DL-TCI-DCI in time slot (or subframe) N, and begins receiving DL control (PDCCH) in the same (time slot N) or a subsequent time slot using the indicated beam (TCI state). For illustration, assuming X1 is the gap (number of time slots / subframes) between the time slot carrying the DL-TCI-DCI and the time slot carrying DL control, the UE begins receiving DL control in time slot N+X1. The UE decodes the DCI (e.g., in DCI format) contained in the PDCCH to obtain activation information (via SPS) for DL dispatch. If the PDSCH is activated by DCI, the UE receives DL data (PDSCH, according to DL dispatch via SPS) in time slot N+X1+K1 using the indicated beam (TCI state). Here, the value of X1 can be fixed. Alternatively, the value of X1 can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (DL-TCI-DCI and / or DCI), the value of X1 is not configured or set in a particular way. That is, the time unit location (e.g., time slot, subframe) used to signal DL-TCI-DCI can be different from the time unit location used to signal DCI. In one example, X1 = X as defined above in this disclosure. In one example, X1 = X + K0. In one example, K1 = K0.
[0184] In Example I.3.2, the UE is configured to receive a dedicated DCI (DL-TCI-DCI) via PDCCH. This dedicated DCI includes a common beam (TCI state) for receiving PDCCH in subsequent time slots, and if activated by the received PDCCH, the common beam is also used to receive DL data (PDSCH) scheduled by the SPS. The UE receives (e.g., in DL-TCI-DCI format) and decodes the DL-TCI-DCI in time slot (or subframe) N, and begins receiving DL control (PDCCH) in subsequent time slots using the indicated beam (TCI state). If PDSCH reception is activated by the DL-TCI-DCI, the UE receives DL data (PDSCH, according to DL dispatch via SPS) in time slot N+X1 using the indicated beam (TCI state). Here, the value of X1 can be fixed. Alternatively, the value of X1 can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (DL-TCI-DCI), the value of X1 is not configured or set in a specific manner. That is, the time unit location (e.g., time slot, subframe) used to signal DL-TCI-DCI can be different from the time unit location used to signal PDSCH. In one example, X1 = X as defined above in this disclosure. In one example, X1 = X + K0. In one example, K1 = K0.
[0185] In Example I.3.3, the UE is configured to receive a dedicated DCI (e.g., DL-TCI-DCI) via PDCCH, which includes (a) a field (TCI state) for a common beam and / or (b) other fields for activating / releasing PDSCH reception (based on the configured SPS). When PDSCH reception is activated by field (b), the UE can be indicated / updated using field (a) with a new (TCI state) beam for PDSCH reception (with or without PDCCH reception). Once field (b) is no longer activated or released from PDSCH reception, the UE can be indicated / updated using only field (a) with a new (TCI state) beam for PDCCH reception.
[0186] Component 2: UL Common Beam Indicator (DCI)
[0187] Figure 16 Example 1600 of a dedicated DCI indicating a common beam for transmitting UL control and data is shown. Figure 16 The example 1600 shown is for illustration only and indicates a dedicated DCI for transmitting UL control and data via a common beam. Figure 16 This disclosure is not intended to limit the scope to any particular implementation of the example 1600 of a dedicated DCI used to transmit UL control and data via a common beam.
[0188] In one embodiment I.4, as Figure 16 As shown, the UE is configured to receive a dedicated DCI (UL-TCI-DCI) indicating a common beam (TCI state) for transmitting UL control (PUCCH) and data (PUSCH), where the PUCCH may be associated with (or in response to) DL reception and / or UL transmission. Optionally, the common beam may also be used for PRACH transmission. The UE receives (e.g., UL-TCI-DCI format) and decodes the UL-TCI-DCI in time slot (or subframe) N', and begins receiving DL control (PDCCH) in the same (time slot N') or subsequent time slots using the indicated beam (TCI state) or other TCI states (beams). For illustration, assuming X' is the gap (number of time slots / subframes) between the time slot carrying the DL-TCI-DCI and the time slot carrying the DL control, the UE begins receiving DL control in time slot N'+X'. The UE decodes the UL-DCI contained in the PDCCH (e.g., UL-DCI format) to obtain UL-permitted scheduling information. The UE transmits UL control (PUCCH) and / or UL data (PUSCH, as permitted by UL) in time slot N'+X'+K0' using the beam (TCI state) indicated in the UL-TCI-DCI. Here, the value of X' can be fixed. Alternatively, the value of X' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (UL-TCI-DCI and / or UL-DCI), the value of X' is not configured or set in a specific way. That is, the time unit location (e.g., time slot, subframe) used to signal the UL-TCI-DCI can be different from the time unit location used to signal the UL-DCI. In some examples, X' may also be referred to as the uplink beam application time (UL-BAT) value B'. In some examples, X' is a lower bound of B', i.e., X' ≥ B'.
[0189] In one example, the units of N' and / or X' and / or K0' are defined based on the number of OFDM symbols. The value X' is measured from the end of UL-TCI-DCI decoding (i.e., the last symbol carrying UL-TCI-DCI) and the beginning of UL-DCI reception (i.e., the first symbol carrying UL-DCI), or the value X' is determined as the first time slot at least P'ms or Q' symbols after UL-TCI-DCI with common beam indication, where P' or Q' can be fixed, configured, or determined / configured based on UE capability reports. Similarly, the value K0' is measured from the end of UL-DCI decoding (i.e., the last symbol carrying UL-DCI) and the beginning of PUCCH / PUSCH transmission (i.e., the first symbol carrying PUCCH / PUSCH). In the remainder of this disclosure, the units of N', X', and K0' are assumed to be time slots (or subframes). However, embodiments of this disclosure are general and applicable to any unit, such as the number of OFDM symbols.
[0190] In the example, the value of X' is set / determined based on the UE's processing limitations (i.e., processing delay) or capabilities. When a new beam (TCI state) is indicated via UL-TCI-DCI, it can be used for UL-DCI reception no earlier than X' time (slot or subframe or OFDM symbol), where X' depends on (or is based on) the UE's capabilities (determined / configured).
[0191] In one example, the UE is configured / triggered to have a PUCCH transmission (e.g., for HARQ-ACK feedback) that can be associated with DL (e.g., PDSCH) reception, which is triggered (or scheduled) by DL-DCI. In this case, the TCI status (beam) of the PUCCH transmission is indicated / updated via UL-TCI-DCI (see Examples I.4 to I.6 below) or DL-TCI-DCI.
[0192] When the PDCCH carrying UL-TCI-DCI is associated (configured) with the HARQ-ACK (or ACK / NACK) feedback indicating that the UE receives an updated common beam (e.g., transmitted via PUCCH), the beam application time may include the time between PDCCH reception (starting or ending from PDCCH reception) and the corresponding PUCCH transmission (starting or ending from PUCCH transmission), that is, X’ = Y1 + Y2, where Y1 is the time between PDCCH reception and PUCCH transmission, and Y2 is the time between PUCCH transmission and UL-DCI reception. Alternatively, the beam application time is equal to Y2. In this case, the TCI state (beam) for PUCCH transmission may be the latest (previous) beam indicated via UL-TCI-DCI before the new / updated TCI state in the current time slot.
[0193] The beam (or TCI state) receiving UL-TCI-DCI in time slot N’ may be the beam (or TCI state) indicated via the latest UL-TCI-DCI in an earlier time slot M’ < N’. If the latest UL-TCI-DCI is not received or not configured, a default beam may be used. For example, the default beam for PDCCH reception in the 3GPP NR specification may be used. Alternatively, the beam (or TCI state) receiving UL-TCI-DCI may be the beam receiving the DL channel and / or DL RS in an earlier time slot M’ < N’. Alternatively, the beam (or TCI state) receiving UL-TCI-DCI may be associated with the beam transmitting the UL channel and / or UL RS in an earlier time slot M’ < N’. Alternatively, the beam (or TCI) receiving UL-TCI-DCI may be associated with the beam for receiving the SSB associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Alternatively, the beam (or TCI) for receiving UL-TCI-DCI may be associated with the beam for receiving the CSI-RS associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Optionally, instead of using the default beam to receive UL-TCI-DCI in time slot N’, the beam (or TCI state) for receiving UL-TCI-DCI may be signaled via MAC CE. For example, the mechanism for updating the TCI state of PDCCH supported in the 3GPP NR specification may be reused to update the TCI state (beam) for receiving UL-TCI-DCI.
[0194] At least one of the following examples may be used to determine the values of X’ and K0’.
[0195] Examples I.4.1 to I.4.5, in which the values of X' and K0' are set, are similar to Examples I.1.1 to I.1.5 (X and K0) in Example I.1.
[0196] In Example I.4.6, due to the (aperiodic) nature of DCI signaling (UL-TCI-DCI and / or UL-DCI), the value of X' is not configured, used, and / or set in a specific manner. Here, the UE monitors the presence of UL-TCI-DCI and UL-DCI in each slot / subframe by detecting the presence of the associated ID (such as C-RNTI, group-RNTI, or TCI-RNTI). In this case, the location of the associated UL-TCI-DCI can be in any slot relative to the location of the UL-DCI. The applicability of the TCI state signaled in the UL-TCI-DCI can be determined based on its location relative to the UL-DCI, for example, to ensure sufficient time to decode the UL-TCI-DCI so that the TCI state is applicable to some subsequent UL-DCIs. For example, the UE assumes a minimum TCI state (beam) switching time (in terms of the number of slots / subframes or ODFM symbols) from the end of UL-TCI-DCI decoding (i.e., the last symbol carrying UL-TCI-DCI) and the start of UL-TCI reception (i.e., the first symbol carrying UL-DCI). In one example, this switching time is reported by the UE in its capability signaling (either fixed or configured to the UE).
[0197] In any of the previously described and subsequent examples and embodiments associated with X' = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X'. In other words, any such example or embodiment can be utilized without any parameterization of X', or by setting the offset parameter (e.g., X') to 0.
[0198] Figure 17 Example 1700 shows the reception of UL-TCI-DCI and UL-DCI in the same time slot or subframe. Figure 17 The example 1700 shown, which receives UL-TCI-DCI and UL-DCI in the same time slot or subframe, is for illustrative purposes only. Figure 17 This disclosure is not intended to limit the scope of any particular implementation of Example 1700 that receives UL-TCI-DCI and UL-DCI in the same time slot or subframe.
[0199] In at least one of the above embodiments (or examples), such as Figure 17As shown, when the value of parameter X’ = 0, that is, the UE is configured to receive UL-TCI-DCI and UL-DCI in the same time slot (or subframe) N’. The UE receives / decodes UL-TCI-DCI and UL-DCI in time slot (or subframe) N’, obtains the indicated beam (TCI state) from UL-TCI-DCI and the scheduling information for UL grant from UL-DCI. Then, the UE uses the beam indicated in time slot N’+K0’ to transmit UL control (PUCCH) and / or UL data (PUSCH, according to the UL grant).
[0200] [[ID=~3]]Since UL-DCI and UL-TCI-DCI are received in the same time slot, the UE cannot use the beam indicated via UL-TCI-DCI to receive DL control (the PDCCH carrying UL-DCI) in the current time slot. The beam (or TCI state) for receiving UL-TCI-DCI and UL-DCI in time slot N’ can be the beam indicated via the latest UL-TCI-DCI in an earlier time slot M’ < N’, or optionally, the latest TCI state applicable to the UL-DCI signaled in other ways. If the latest UL-TCI-DCI is not received or not configured, the default beam can be used. For example, the default beam for PDCCH reception in the 3GPP NR specification can be used. Alternatively, the beam (or TCI state) for receiving UL-TCI-DCI and UL-DCI can be the beam for receiving the DL channel and / or DL RS in an earlier time slot M’ < N’. Or, the beam (or TCI state) for receiving UL-TCI-DCI and UL-DCI can be associated with the beam for transmitting the UL channel and / or UL RS in an earlier time slot M’ < N’. Optionally, instead of using the default beam to receive UL-TCI-DCI and UL-DCI in time slot N’, the beam (or TCI state) for receiving UL-TCI-DCI can be signaled via MAC CE. For example, the mechanism supported in the 3GPP NR specification for updating the TCI state of PDCCH can be reused to update the TCI state (beam) for receiving UL-TCI-DCI.
[0201] When UL-TCI-DCI and UL-DCI are received in the same time slot, at least one of the following examples can apply.
[0202] In Example I.4.7, UL-TCI-DCI and UL-DCI correspond to (or are functionally combined into) a single (joint) DCI that includes all DCI fields of both UL-TCI-DCI and UL-DCI. In one example, this joint DCI is labeled UL-TCI-DCI. In another example, this joint DCI is labeled UL-DCI (e.g., format 0_0, 0_1, or 0_2 in the NR specification). In one example, the UL-DCI format may include one or both of the common beam (TCI status) for UL transmission and UL licensing. At least one of the following examples can be used / configured.
[0203] - In Example I.4.7.1, the UE decodes the UL-DCI and determines whether only one or both of the common beam (TCI status) and UL clearance are included. For example, when the TCI status field in the DCI takes a value (e.g., 0), it indicates that the TCI status (or common beam) is not indicated (or does not exist). Similarly, when the parameter in the dispatch assignment field in the DCI takes a value (e.g., 0), it indicates that there is no UL clearance (it does not exist).
[0204] - In Example I.4.7.2, whether information including only one or both of the common beam (TCI status) and UL license can be configured via RRC or activated via MAC CE.
[0205] In Example I.4.8, UL-TCI-DCI can be independent of UL-DCI, but they are in the same time slot. The remaining details are similar to Example I.1.8.
[0206] In Example I.4.9, UL-TCI-DCI and DL-DCI (scheduling DL dispatch) correspond to (or functionally combine into) a single (joint) DCI that includes all DCI fields of both UL-TCI-DCI and DL-DCI. In one example, this joint DCI is labeled UL-TCI-DCI. In another example, this joint DCI is labeled DL-DCI (e.g., format 1_0, 1_1, or 1_2 in the NR specification). In one example, the DL-DCI format may include one or both of the common beam (TCI state) and DL dispatch for UL transmission. At least one of the following examples can be used / configured.
[0207] - In Example I.4.9.1, the UE decodes the DL-DCI and determines whether only one or both of the common beam (TCI state) and DL dispatch are included. For example, when the TCI state field in the DCI takes a value (e.g., 0), it indicates that the TCI state (or common beam) is not indicated (or does not exist). Similarly, when the parameter in the dispatch field of the DCI takes a value (e.g., 0), it indicates that there is no DL dispatch (does not exist).
[0208] - In Example I.4.9.2, information on whether to include only one or both of the common beam (TCI state) and DL assignment can be configured via RRC or activated via MAC CE.
[0209] In one embodiment 1.5, the UE can be configured with higher-layer parameters (and / or MAC CE and / or DL-DCI fields) to implement TCI status (beaming) indication via UL-TCI-DCI. For example, depending on the configuration of UL-DCI and / or UL-TCI-DCI, the UE can be configured to derive its TCI status update from UL-DCI and / or UL-TCI-DCI. The remaining details are similar to the corresponding embodiment 1.2 of DL.
[0210] In Example I.5.1, the resulting UE procedure when using or configuring the offset parameter X' can depend on the value of X'. For example, when X' = 0, UL-TCI-DCI is absent (not received and / or not configured) (or UL-TCI-DCI and UL-DCI correspond to (or functionally combine into) a single (joint) DCI, see Example I.4.7), and TCI status indication / update is present and signaled / received in UL-DCI (and for UL data transmission); and when X > 0, UL-TCI-DCI is present (configured and therefore can be received), and TCI status indication / update is present and signaled / received in UL-TCI-DCI (and for UL data and / or UL control transmission).
[0211] In Example I.5.2, regardless of whether the offset parameter X' is used / configured, the resulting UE procedure can be based on higher-layer (RRC) parameters, such as ul-tci-dci-IsPresent (ul-tci-dci-existence). When ul-tci-dci-IsPresent is set to "enabled", UL-TCI-DCI exists (is configured and therefore can be received), and the TCI status indication / update is the TCI status indication / update in UL-TCI-DCI (and used for the transmission of UL data and / or UL control). Otherwise, UL-TCI-DCI does not exist (is not received and / or is not configured) (or UL-TCI-DCI and UL-DCI correspond to (or functionally combine into) a single (joint) DCI, see Example I.4.7), and the TCI status indication / update exists and is signaled / received in UL-DCI (and used for the transmission of UL data).
[0212] In Example I.5.3, regardless of whether the offset parameter X' is used / configured, and regardless of whether the higher-level parameter controlling the presence of UL-TCI-DCI (e.g., ul-tci-dci-IsPresent) is used / configured, the resulting UE procedure can (also) be based on the PUSCH-Config (which controls the presence of UL-DCI) or the higher-level parameter tci-PresentInDCI in the PDSCH-Config. For example, when the parameter ul-tci-dci-IsPresent is "enabled" and tci-PresentInDCI is also "enabled," both UL-TCI-DCI and UL-DCI exist (are configured and therefore can be received). In this case, the TCI status indication / update applicable to decoding UL-DCI (in the relevant PDCCH) is signaled / received in the latest (most recent) UL-TCI-DCI, while the TCI status indication / update applicable to UL data transmission in the relevant PUSCH (associated with UL authorization in UL-DCI) is signaled / received in the latest (most recent) UL-DCI. When the parameter ul-tci-dci-IsPresent is “enabled” and tci-PresentInDCI is not “enabled”, UL-TCI-DCI exists (is configured and therefore can be received), and TCI status indication / update is TCI status indication / update in UL-TCI-DCI (and is used for the transmission of both UL data and UL control associated with UL authorization in UL-DCI).
[0213] In Example I.5.4, the resulting UE procedure can be activated based on higher-layer (RRC) parameters and / or MAC CE, regardless of whether the offset parameter X' is used / configured.
[0214] In Example I.5.5, the resulting UE procedure can be based on system information (i.e., for all UEs in the cell) regardless of whether the offset parameter X' is used / configured.
[0215] In any of the previously described and subsequent examples and embodiments associated with X' = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X'. In other words, any such example or embodiment can be utilized without any parameterization of X', or by setting the offset parameter (e.g., X') to 0.
[0216] In one embodiment I.6, the UE can be configured with PUSCH transmissions corresponding to configured grant type 1 or type 2. The configured grant type 1 PUSCH transmission is semi-statically configured to operate upon receiving a higher-layer parameter, `configuredGrantConfig`, which includes `rrc-ConfiguredUplinkGrant`, without detecting UL grants in the DCI. Upon receiving a higher-layer parameter `configuredGrantConfig` excluding `rrc-ConfiguredUplinkGrant`, the configured grant type 2 PUSCH transmission is semi-persistently scheduled (SPS) by effectively activating UL grants in the DCI. If `Configuredgrantconfig-ToAddModList-r16` is configured, more than one configured grant type 1 and / or configured grant type 2 can be active simultaneously on the active BWP of the serving cell. For the configured license type 2PUSCH transmission, the UE is configured with cs-RNTI (an RNTI for receiving DCI activation / release of SPS). Since the gNB can activate / reactivate / release SPS at any time using DCI (e.g., DCI format 0_1 or 0_2 in NR), the UE will use a CRC scrambled by cs-RNTI to monitor the PDCCH in each time slot.
[0217] The UE can be configured to have PUCCH transmissions corresponding to periodic or semi-persistent CSI reports sent on the PUCCH. Such PUCCH transmissions are configured by CSI-ReportConfig without requiring UL clearance in the UL-DCI. The MAC CE can activate / deactivate semi-persistent CSI reports on the PUCCH.
[0218] In Example I.6.1, the UE is configured to receive a dedicated DCI (UL-TCI-DCI) that indicates a common beam (TCI state) for UL control (PUCCH) and / or data (PUSCH) transmissions (if activated by a received PDCCH). The UE receives (e.g., in UL-TCI-DCI format) and decodes the UL-TCI-DCI in time slot (or subframe) N', and begins receiving DL control (PDCCH) in the same (time slot N') or a subsequent time slot using the indicated beam (TCI state). For illustration, assuming X1' is the gap (number of time slots / subframes) between the time slot carrying the UL-TCI-DCI and the time slot carrying DL control, the UE begins receiving DL control in time slot N'+X1'. The UE decodes the DCI (e.g., in DCI format) contained in the PDCCH to obtain activation information for UL dispatch (for configured license type 2 PUSCH transmission). If PUSCH is activated by DCI, the UE transmits UL data (PUSCH, according to UL assignment) in time slot N'+X1'+K1' using the indicated beam (TCI state). Here, the value of X1' can be fixed. Alternatively, the value of X1' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (UL-TCI-DCI and / or DCI), the value of X1' is not configured or set in a particular way. That is, the time unit location (e.g., time slot, subframe) used to signal UL-TCI-DCI can be different from the time unit location used to signal DCI. In one example, X1' = X' as defined earlier in this disclosure. In one example, X1' = X'+K0'. In one example, K1' = K0'.
[0219] In Example I.6.2, the UE is configured to receive a dedicated DCI (UL-TCI-DCI) via PDCCH. This dedicated DCI includes a common beam (TCI state) for receiving PDCCH in subsequent time slots, and if activated by the received PDCCH, the common beam is also used for the transmission of UL data (PUSCH) (for configured license type 2 PUSCH transmission). The UE receives (e.g., in UL-TCI-DCI format) and decodes the UL-TCI-DCI in time slot (or subframe) N', and begins receiving DL control (PDCCH) in subsequent time slots using the indicated beam (TCI state). If PUSCH transmission is activated by the UL-TCI-DCI, the UE transmits UL data (PUSCH, according to UL assignment) in time slot N'+X1' using the indicated beam (TCI state). Here, the value of X1' can be fixed. Alternatively, the value of X1' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (UL-TCI-DCI), the value of X1' is not configured or set in a specific manner. That is, the time unit location (e.g., time slot, subframe) used to signal UL-TCI-DCI can be different from the time unit location used to signal PUSCH. In one example, X1' = X' as defined earlier in this disclosure. In one example, X1' = X' + K0'. In one example, K1' = K0'.
[0220] In Example I.6.3, the UE is configured to receive a dedicated DCI (UL-TCI-DCI) indicating a common beam (TCI state) for UL control (PUCCH) and / or data (PUSCH) transmission. The UE receives (e.g., in UL-TCI-DCI format) and decodes the UL-TCI-DCI in time slot (or subframe) N', and begins transmitting UL control (PUCCH) (e.g., periodic PUCCH or semi-persistent PUCCH) and / or data (PUSCH) (e.g., configured license type 1) in the same time slot (time slot N') or a subsequent time slot using the indicated beam (TCI state). For illustration, assuming X1' is the gap (number of time slots / subframes) between the time slot carrying the UL-TCI-DCI and the time slot carrying UL transmission, the UE can begin uplink transmission in time slot N'+X1' using the indicated beam (TCI state). Here, the value of X1' can be fixed. Alternatively, the value of X1' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (UL-TCI-DCI and / or DCI), the value of X1' is not configured or set in a particular manner. That is, the time unit location (e.g., time slot, subframe) used to signal UL-TCI-DCI may differ from the time unit location used to signal DCI. In one example, X1' = X' as defined earlier in this disclosure. In one example, X1' = X' + K0'. In one example, K1' = K0'.
[0221] In one embodiment 1.7, the UE can be configured to receive a dedicated DCI (RACH-TCI-DCI) indicating a common beam (TCI state) for transmitting a contention-free random access (CFRA) preamble triggered by a PDCCH. Such a PDCCH is called a PDCCH command, which can be a DCI format 1_0 with the "Domain Resource Allocation" field set to all 1s, as described in TS38.212 [REF7]. In this example and its sub-examples, the PDCCH command is used for contention-free random access preamble transmission. The UE receives (e.g., in RACH-TCI-DCI format) and decodes the RACH-TCI-DCI in time slot (or subframe) N', and begins receiving DL control (PDCCH commands) in the same (time slot N') or subsequent time slots using the indicated beam (TCI state) or other TCI state (beam). For illustration, assuming X' is the gap (number of time slots / subframes) between the time slot carrying RACH-TCI-DCI and the time slot carrying DL control (i.e., PDCCH command), the UE begins receiving DL control in time slot N'+X'. The UE decodes the PDCCH command to obtain the preamble transmission parameters (i.e., the preamble index and PRACH transmission timing). The UE uses the beam (TCI state) indicated in RACH-TCI-DCI to begin transmitting the CFRA preamble in time slot N'+X'+K0' at the indicated PRACH timing. Here, the value of X' can be fixed. Alternatively, the value of X' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (RACH-TCI-DCI and / or PDCCH command), the value of X' is not configured or set in a specific way. That is, the time unit position (e.g., time slot, subframe) used to signal RACH-TCI-DCI can be different from the time unit position used to signal PDCCH command.
[0222] In the example, the units of N' and / or X' and / or K0' are defined based on the number of OFDM symbols. The value X' is measured from the end of RACH-TCI-DCI decoding (i.e., the last symbol carrying RACH-TCI-DCI) and the beginning of PDCCH command reception (i.e., the first symbol carrying PDCCH commands). Similarly, the value K0' is measured from the end of PDCCH command decoding (i.e., the last symbol carrying PDCCH orders) and the earliest possible start of the PRACH preamble. In the remainder of this disclosure, the units of N', X', and K0' are assumed to be time slots (or subframes). However, the embodiments of this disclosure are general and applicable to any unit, such as the number of OFDM symbols.
[0223] The beam (or TCI state) for receiving the RACH-TCI-DCI in slot N' can be the beam (or TCI state) indicated via the latest RACH-TCI-DCI in an earlier slot M' < N'. If the latest RACH-TCI-DCI is not received or not configured, a default beam can be used. For example, the default beam used for PDCCH reception in the 3GPP NR specification can be used. Alternatively, the beam (or TCI state) for receiving the RACH-TCI-DCI can be the beam for receiving the DL channel and / or DL RS in an earlier slot M' < N'. Alternatively, the beam (or TCI state) for receiving the RACH-TCI-DCI can be associated with the beam for transmitting the UL channel and / or UL RS in an earlier slot M' < N'. Alternatively, the beam (or TCI) for receiving the RACH-TCI-DCI can be associated with the beam for receiving the SSB associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Alternatively, the beam (or TCI) for receiving the RACH-TCI-DCI can be associated with the beam for receiving the CSI-RS associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Optionally, instead of using the default beam to receive the RACH-TCI-DCI in slot N', the beam (or TCI state) for receiving the RACH-TCI-DCI can be signaled via a MAC CE. For example, the mechanism for updating the TCI state of the PDCCH supported in the 3GPP NR specification can be reused to update the TCI state (beam) for receiving the RACH-TCI-DCI.
[0224] At least one of the following examples can be used to determine the values of X' and K0'.
[0225] The embodiments I.7.1 to I.7.5 in which the values of X' and K0' are set are similar to the embodiments I.1.1 to I.1.5 (X and K0) in embodiment I.1
[0226] In Example I.7.6, due to the (aperiodic) nature of DCI signaling (RACH-TCI-DCI and / or PDCCH commands), the value of X' is not configured, used, and / or set in a specific manner. Here, the UE monitors the presence of RACH-TCI-DCI and PDCCH commands in each slot / subframe by detecting the presence of the associated ID (e.g., C-RNTI, Group-RNTI, or TCI-RNTI). In this case, the location of the associated RACH-TCI-DCI can be anywhere relative to the location of the PDCCH command. The applicability of the TCI state signaled in the RACH-TCI-DCI can be determined based on its location relative to the PDCCH command, for example, to ensure sufficient time to decode the RACH-TCI-DCI so that the TCI state is applicable to some subsequent PDCCH commands. For example, the UE assumes the minimum TCI state (beam) switching time (in terms of the number of slots / subframes or ODFM symbols) from the end of RACH-TCI-DCI decoding (i.e., the last symbol carrying RACH-TCI-DCI) to the start of PDCCH command reception (i.e., the first symbol carrying PDCCH commands). In one example, this switching time is reported by the UE in its capability signaling (either fixed or configured to the UE).
[0227] In any of the previously described and subsequent examples and embodiments associated with X' = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X'. In other words, any such example or embodiment can be utilized without any parameterization of X', or by setting the offset parameter (e.g., X') to 0.
[0228] In at least one of the above embodiments (or examples), when the value of parameter X' = 0, the UE is configured to receive RACH-TCI-DCI and PDCCH commands in the same time slot (or subframe) N'. The UE receives / decodes the RACH-TCI-DCI and PDCCH commands in time slot (or subframe) N', obtains the indicated beam (TCI state) from the RACH-TCI-DCI, and obtains UL-granted scheduling information from the PDCCH command. Then, the UE uses the indicated beam to begin transmitting the PRACH preamble (according to the PDCCH command) in time slot N'+K0' at the indicated PRACH timing.
[0229] Since the PDCCH command and the RACH-TCI-DCI are received in the same time slot, the UE cannot use the beam indicated via the RACH-TCI-DCI to receive DL control (PDCCH command) in the current time slot. The beam (or TCI state) for receiving the RACH-TCI-DCI and the PDCCH command in time slot N' can be the beam indicated via the latest RACH-TCI-DCI in an earlier time slot M' < N', or optionally, the latest TCI state applicable to the PDCCH command signaled via other means. If the latest RACH-TCI-DCI is not received or not configured, the default beam can be used. For example, the default beam for PDCCH reception in the 3GPP NR specification can be used. Alternatively, the beam (or TCI state) for receiving the PDCCH-TCI-DCI and the PDCCH command can be the beam for receiving the DL channel and / or DL RS in an earlier time slot M' < N'. Or, the beam (or TCI state) for receiving the RACH-TCI-DCI and the PDCCH command can be associated with the beam for transmitting the UL channel and / or UL RS in an earlier time slot M' < N'. Optionally, instead of using the default beam to receive the RACH-TCI-DCI and the PDCCH command in time slot N', the beam (or TCI state) for receiving the RACH-TCI-DCI can be signaled via a MAC CE. For example, the mechanism supported in the 3GPP NR specification for updating the TCI state of the PDCCH can be reused to update the TCI state (beam) for receiving the RACH-TCI-DCI.
[0230] When the RACH-TCI-DCI and the PDCCH command are received in the same time slot, at least one of the following examples can be applied.
[0231] In an example I.7.7, the RACH-TCI-DCI and the PDCCH command correspond to (or are functionally combined into) a single (joint) DCI including all DCI fields of both the RACH-TCI-DCI and the PDCCH command. In one example, the joint DCI is labeled as the RACH-TCI-DCI. In one example, the joint DCI is labeled as the PDCCH command.
[0232] In an example I.7.8, the RACH-TCI-DCI can be independent of the PDCCH command, but they are in the same time slot. The remaining details are similar to Example I.1.8.
[0233] In an example I.7.9, the RACH-TCI-DCI can be the UL-TCI-DCI in the above example.
[0234] Component 3: Common Beam Indicator (DCI) for DL and UL
[0235] Figure 18 Example 1800 of a dedicated DCI is shown, indicating the common beam for all DL and UL channels. Figure 18 The example 1800 shown here, which indicates the common beam of all DL and UL channels, is for illustrative purposes only. Figure 18 This disclosure is not intended to limit the scope to any particular implementation of the example 1800 of a dedicated DCI that indicates a common beam for all DL and UL channels.
[0236] like Figure 18 As shown, in Embodiment I.8, the UE is configured to receive a dedicated DCI (TCI-DCI) indicating a common beam (TCI state) for all DL and UL channels. Specifically, the indicated common beam is used for the reception of DL control (PDCCH) and DL data (PDSCH), and for the transmission of UL control (PUCCH) and UL data (PUSCH), wherein the PUCCH may be associated with (or in response to) DL reception and / or UL transmission. Optionally, the common beam may also be used for the transmission of PRACH (see Embodiment I.7). The UE receives (e.g., in TCI-DCI format) and decodes the TCI-DCI in time slot (or subframe) N, and begins receiving DL control (PDCCH) scheduling DL assignment (via DL-DCI) and / or UL authorization (via UL-DCI) in the same (time slot N) or a subsequent time slot using the indicated beam (TCI state) or other TCI state (beam).
[0237] For DL, assuming X is the gap (number of time slots / subframes) between the time slot carrying TCI-DCI and the time slot carrying DL control (via DL-DCI) for scheduling, the UE begins receiving DL control in time slot N+X. The UE decodes the DL-DCI (e.g., DL-DCI format) contained in the PDCCH to obtain scheduling information for DL dispatch. Then, the UE receives DL data (PDSCH, according to DL dispatch) in time slot N+X+K0 using the indicated beam (TCI state). Here, the value of X is fixed. Alternatively, the value of X can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (TCI-DCI and / or DL-DCI), the value of X is not configured or set in a specific way. That is, the time unit location (e.g., time slot, subframe) used to signal TCI-DCI can be different from the time unit location used to signal DL-DCI. The method for setting the values of X and K0, and their units (the number of time slots, subframes, or OFDM symbols), is similar to the method applicable to Embodiment I.1. In some examples, X may also be referred to as the downlink beam application time (DL-BAT) B. In some examples, X is a lower bound of B, i.e., X ≥ B.
[0238] For UL, assuming X' is the gap (number of time slots / subframes) between the time slot carrying TCI-DCI and the time slot carrying DL control scheduling UL authorization (via UL-DCI), the UE begins receiving DL control in time slot N'+X'. The UE decodes the UL-DCI contained in the PDCCH (e.g., UL-DCI format) to obtain scheduling information for UL authorization. The UE transmits UL control (PUCCH) and / or UL data (PUSCH, according to UL authorization) in time slot N'+X'+K0' using the beam (TCI state) indicated in the TCI-DCI. Here, the value of X' can be fixed. Alternatively, the value of X' can be selected from a set of values. Optionally, due to the aperiodic nature of DCI signaling (TCI-DCI and / or UL-DCI), the value of X' is not configured or set in a specific way. That is, the time unit location (e.g., time slot, subframe) used to signal TCI-DCI can be different from the time unit location used to signal UL-DCI. The method for setting the values of X' and K0', and their units (the number of time slots, subframes, or OFDM symbols), is similar to the method applicable to Embodiment I.4. In some examples, X' may also be referred to as the uplink beam application time (UL-BAT) B'. In some examples, X' is a lower bound of B', i.e., X' ≥ B'.
[0239] In the example, value X is measured from the end of TCI-DCI decoding (i.e., the last symbol carrying TCI-DCI) and the beginning of DL-DCI reception (i.e., the first symbol carrying DL-DCI), or value X is determined as the first time slot at least P ms or Q symbols after TCI-DCI with common beam indication, where P or Q can be fixed, configured, or determined / configured based on UE capability reports. Similarly, value K0 is measured from the end of DL-DCI decoding (i.e., the last symbol carrying DL-DCI) and the beginning of PDSCH reception (i.e., the first symbol carrying PDSCH). It is assumed that the units for N, X, and K0 are the number of time slots (i.e., subframes) or OFDM symbols.
[0240] In the example, the value X' is measured from the end of TCI-DCI decoding (i.e., the last symbol carrying the TCI-DCI) and the start of UL-DCI reception (i.e., the first symbol carrying the UL-DCI), or the value X' is determined as the first time slot at least P'ms or Q' symbols after TCI-DCI with common beam indication, where P' or Q' can be fixed or configured, or determined / configured based on the UE capability report. Similarly, the value K0' is measured from the end of UL-DCI decoding (i.e., the last symbol carrying the UL-DCI) and the start of PUSCH transmission (i.e., the first symbol carrying the PUSCH). The unit is assumed to be a time slot (i.e., a subframe) or the number of OFDM symbols.
[0241] In the example, the values of X and / or X' are set / determined based on the UE's processing limitations (i.e., processing delay) or capabilities. When a new beam (TCI state) is indicated via TCI-DCI, it can be used for DL-DCI or UL-DCI reception no earlier than X or X' time (slot or subframe or OFDM symbol), where X and X' depend on (or are based on) the UE's capabilities.
[0242] In one example, the UE is configured / triggered to have a PUCCH transmission (e.g., for HARQ-ACK feedback) that can be associated with DL (e.g., PDSCH) reception, which is triggered (or scheduled) by DL-DCI. In this case, the TCI state (beam) of the PUCCH transmission is indicated / updated via TCI-DCI.
[0243] When the PDCCH carrying TCI-DCI is associated (configured) with the HARQ-ACK (or ACK / NACK) feedback indicating that the UE receives an updated common beam (e.g., via PUCCH transmission), the beam application time may include the time between the PDCCH reception (from the start or end of PDCCH reception) and the corresponding PUCCH transmission (from the start or end of PUCCH transmission), i.e., X (or X’) = Y1 + Y2, where Y1 = the time between PDCCH reception and PUCCH transmission, and Y2 = the time between PUCCH transmissions. Alternatively, the beam application time is equal to Y2. In this case, the TCI state (beam) for PUCCH transmission may be the latest (previous) beam indicated via TCI-DCI before the new / updated TCI state in the current time slot.
[0244] The beam (or TCI state) receiving TCI-DCI in time slot N may be the beam (or TCI state) indicated via the latest TCI-DCI in an earlier time slot M < N. If the latest TCI-DCI is not received or not configured, a default beam may be used. For example, the default beam for PDCCH reception in the 3GPP NR specification may be used. Alternatively, the beam (or TCI state) receiving TCI-DCI may be the beam receiving the DL channel and / or DL RS in an earlier time slot M < N. Alternatively, the beam (or TCI state) receiving TCI-DCI may be associated with the beam transmitting the UL channel and / or UL RS in an earlier time slot M < N. Alternatively, the beam (or TCI) receiving TCI-DCI may be associated with the beam for receiving the SSB associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Alternatively, the beam (or TCI) receiving TCI-DCI may be associated with the beam for receiving the CSI-RS associated with the most recent random access procedure (e.g., a random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure). Optionally, instead of using the default beam to receive TCI-DCI in time slot N, the beam (or TCI state) for receiving TCI-DCI may be signaled via a MAC CE. For example, the mechanism supported in the 3GPP NR specification for updating the TCI state of the PDCCH may be reused to update the TCI state (beam) for receiving TCI-DCI.
[0245] At least one of the following examples may be used to determine the values of X and K0 and X’ and K0’.
[0246] Examples I.8.1 to I.8.5, which set the values of X and K0, are similar to Examples I.1.1 to I.1.5 in Implementation Scheme I.1; and examples I.4.1 to I.4.5, which set the values of X and K0.
[0247] In Example I.8.6, due to the (aperiodic) nature of DCI signaling (TCI-DCI and / or UL-DCI / DL-DCI), the values of X and / or X' are not configured, used, and / or set in a specific manner. Here, the UE monitors the presence of TCI-DCI and UL-DCI / DL-DCI in each slot / subframe by detecting the presence of the associated ID (such as C-RNTI or Group-RNTI or TCI-RNTI). In this case, the location of the associated TCI-DCI can be in any slot relative to the location of the UL-DCI / DL-DCI. The applicability of the TCI state signaled in the TCI-DCI can be determined based on its location relative to the UL-DCI / DL-DCI, for example, to ensure sufficient time to decode the TCI-DCI so that the TCI state is applicable to some subsequent UL-DCI / DL-DCI. For example, the UE assumes the minimum TCI state (beam) switching time (in terms of the number of slots / subframes or ODFM symbols) from the end of TCI-DCI decoding (i.e., the last symbol carrying TCI-DCI) to the start of UL-TCI / DL-DCI reception (i.e., the first symbol carrying UL-DCI / DL-DCI). In one example, this switching time is reported by the UE in its capability signaling (either fixed or configured to the UE).
[0248] In any of the previously described and subsequent examples and embodiments associated with X' = 0 and / or X = 0, these methods may exist independently and therefore may be implemented without using any offset parameters X and / or X'. In other words, any such example or embodiment may be used without any parameterization of X and / or X' or with offset parameters (such as X and / or X') set to 0.
[0249] Figure 19 Example 1900 shows the reception of TCI-DCI and DL-DCI in the same time slot or subframe. Figure 19 The example 1900 showing the reception of TCI-DCI and DL-DCI in the same time slot or subframe is for illustrative purposes only. Figure 19 This disclosure is not intended to limit the scope of any particular implementation of Example 1900 that receives TCI-DCI and DL-DCI in the same time slot or subframe.
[0250] In at least one of the above embodiments (or examples), such as Figure 19 As shown, when parameter X = 0 and X' > 0, the UE is configured to receive TCI-DCI and DL-DCI in the same time slot (or subframe) N. The UE receives / decodes TCI-DCI and DL-DCI in time slot (or subframe) N, obtaining the indicated beam (TCI state) from TCI-DCI and the scheduling information for DL dispatch from DL-DCI. Then, the UE uses the indicated beam to receive DL data (PDSCH) in time slot N+K0 according to DL dispatch.
[0251] Figure 20 Example 2000 shows receiving TCI-DCI and UL-DCI in the same time slot or subframe. Figure 20 The example 2000 showing the reception of TCI-DCI and UL-DCI in the same time slot or subframe is for illustrative purposes only. Figure 20 This disclosure is not intended to limit the scope of any particular implementation of Example 2000 that receives TCI-DCI and UL-DCI in the same time slot or subframe.
[0252] In at least one of the above embodiments (or examples), such as Figure 20 As shown, when parameter X' = 0 and X > 0, the UE is configured to receive TCI-DCI and UL-DCI in the same time slot (or subframe) N. The UE receives / decodes TCI-DCI and UL-DCI in time slot (or subframe) N', obtaining the indication beam (TCI state) from TCI-DCI and the scheduling information for UL licensing from UL-DCI. The UE then uses the indicated beam to transmit UL control (PUCCH) and / or UL data (PUSCH, according to UL licensing) in time slot N'+K0'.
[0253] Figure 21 Example 2100 illustrates receiving TCI-DCI, UL-DCI, and DL-DCI in the same time slot or subframe. Figure 21 Example 2100, showing the reception of TCI-DCI, UL-DCI, and DL-DCI in the same time slot or subframe, is for illustrative purposes only. Figure 21 This disclosure is not intended to limit the scope of any particular implementation of Example 2100 that receives TCI-DCI, UL-DCI and DL-DCI in the same time slot or subframe.
[0254] In at least one of the above embodiments (or examples), such as Figure 21As shown, when the parameters X = X' = 0, that is, the UE is configured to receive TCI-DCI, UL-DCI, and DL-DCI in the same time slot (or subframe) N. The UE receives / decodes TCI-DCI, DL-DCI, and UL-DCI in the time slot (or subframe) N, and obtains the indicated beam (TCI state) from the TCI-DCI, the scheduling information for DL dispatch from the DL-DCI, and the scheduling information for UL grant. Then, the UE receives DL data (PDSCH) according to the DL dispatch in the time slot N+K0 using the indicated beam, and transmits UL control (PUCCH) and / or UL data (PUSCH, according to the UL grant) in the time slot N'+K0' using the indicated beam.
[0255] In the above three examples, since the TCI-DCI and DL-DCI (and / or UL-DCI) are received in the same time slot, the UE cannot use the beam indicated via the TCI-DCI in the current time slot to receive DL control (the PDCCH carrying DL-DCI (and / or UL-DCI)). The beam (or TCI state) for receiving the TCI-DCI and DL-DCI (and / or UL-DCI) in the time slot N can be the beam indicated via the latest TCI-DCI in an earlier time slot M < N, or optionally, the latest TCI state applicable to the DL-DCI (and / or UL-DCI) signaled via other means. If the latest TCI-DCI is not received or not configured, the default beam can be used. For example, the default beam for PDCCH reception in the 3GPP NR specification can be used. Alternatively, the beam (or TCI state) for receiving the TCI-DCI and DL-DCI (and / or UL-DCI) can be the beam for receiving the DL channel and / or DL RS in an earlier time slot M < N. Alternatively, the beam (or TCI state) for receiving the TCI-DCI and DL-DCI (and / or UL-DCI) can be associated with the beam for transmitting the UL channel and / or UL RS in an earlier time slot M < N. Optionally, instead of using the default beam to receive the TCI-DCI and DL-DCI (and / or UL-DCI) in the time slot N. For example, the mechanism for updating the TCI state of the PDCCH supported in the 3GPP NR specification can be reused to update the TCI state (beam) for receiving the TCI-DCI.
[0256] When the TCI-DCI and DL-DCI (and / or UL-DCI) are received in the same time slot, at least one of the following examples can be applied.
[0257] In Example I.8.7, TCI-DCI and DL-DCI (and / or UL-DCI) correspond to (or are functionally combined into) a single (joint) DCI that includes all DCI fields of both TCI-DCI and DL-DCI (and / or UL-DCI). In one example, this joint DCI is labeled TCI-DCI. In another example, this joint DCI is labeled DL-DCI (e.g., format 1_0, 1_1, or 1_2 in the NR specification). In yet another example, this joint DCI is labeled UL-DCI (e.g., format 0_0, 0_1, or 0_2 in the NR specification).
[0258] In one example, when UL-DCI is used for common beam indication of both DL and UL, the UL-DCI format can include one or both of the common beam (TCI status) and UL license. At least one of the following examples can be used / configured.
[0259] - In Example I.8.7.1, the UE decodes the UL-DCI and determines whether only one or both of the common beam (TCI state) and UL clearance are included. For example, when the TCI state field in the DCI takes a value (e.g., 0), it indicates that the TCI state (or common beam) is not indicated (or does not exist). Similarly, when the parameter in the dispatch field of the DCI takes a value (e.g., 0), it indicates that there is no UL clearance (it does not exist).
[0260] - In Example I.8.7.2, whether information including only one or both of the common beam (TCI status) and UL license can be configured via RRC or activated via MAC CE.
[0261] In one example, when UL-DCI is used for common beam indication of both DL and UL, the DL-DCI format can include one or both of the common beam (TCI state) and DL assignment. At least one of the following examples can be used / configured.
[0262] - In Example I.8.7.1A, the UE decodes the DL-DCI and determines whether only one or both of the common beam (TCI state) and DL dispatch are included. For example, when the TCI state field in the DCI takes a value (e.g., 0), it indicates that the TCI state (or common beam) is not indicated (or does not exist). Similarly, when the parameter in the dispatch field of the DCI takes a value (e.g., 0), it indicates that there is no DL dispatch (does not exist).
[0263] - In Example I.8.7.2A, information on whether to include only one or both of the common beam (TCI state) and DL assignment can be configured via RRC or activated via MAC CE.
[0264] In Example I.8.8, TCI-DCI can be independent of DL-DCI (and / or UL-DCI), but they are in the same time slot. The remaining details are similar to Example I.1.8 (and / or I.4.8).
[0265] In any of the previously described and subsequent examples and embodiments associated with X = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X. In other words, any such example or embodiment can be utilized without any parameterization of X or by setting the offset parameter (e.g., X) to 0.
[0266] In any of the previously described and subsequent examples and embodiments associated with X' = 0, these methods can be standalone and therefore can be implemented without using any offset parameter X'. In other words, any such example or embodiment can be utilized without any parameterization of X', or by setting the offset parameter (e.g., X') to 0.
[0267] In one embodiment 1.9, the UE can be configured with higher-layer parameters (and / or MAC CE and / or DL-DCI fields) to implement TCI status (beaming) indication via TCI-DCI. For example, depending on the configuration of TCI-DCI and / or DL-DCI (and / or UL-DCI), the UE can be configured to derive its TCI status update from TCI-DCI and / or DL-DCI (and / or UL-DCI). The remaining details are similar to the corresponding embodiment 1.2 for DL and embodiment 1.5 for UL.
[0268] In Example I.9.1, when offset parameters X and / or X' are used or configured, the resulting UE procedure may depend on the values of X and / or X'. For example, when X = 0, TCI-DCI is absent (not received and / or not configured) (or TCI-DCI and DL-DCI correspond to (or functionally combine into) a single (joint) DCI, see Example I.1.7), and TCI status indication / update is present and signaled / received in DL-DCI (and for receiving DL data); and when X > 0, TCI-DCI is present (configured and therefore can be received), and TCI status indication / update is present and signaled / received in TCI-DCI (and for receiving DL data associated with DL dispatch in DL-DCI and both DL control including DL-DCI). Similarly, for example, when X' = 0, TCI-DCI is absent (not received and / or not configured) (or TCI-DCI and UL-DCI correspond to (or functionally combine into) a single (joint) DCI, see Example I.4.7), and TCI status indication / update is present and signaled / received in UL-DCI (and for the transmission of UL data); and when X > 0, TCI-DCI is present (configured and therefore can be received), and TCI status indication / update is present and signaled / received in TCI-DCI (and for the transmission of UL data and / or UL control).
[0269] In Example I.9.2, regardless of whether offset parameters X and / or X' are used / configured, the resulting UE procedure can be based on higher-layer (RRC) parameters, such as tci-dci-IsPresent. When tci-dci-IsPresent is set to "Enabled", TCI-DCI exists (is configured and therefore can be received), and the TCI status indication / update is the TCI status indication / update in TCI-DCI (and is used for the transmission of UL data and / or UL control, and / or for the reception of DL data and DL control). Otherwise, TCI-DCI does not exist (is not received and / or is not configured) (or TCI-DCI and DL-DCI / UL-DCI correspond to (or are functionally combined into) a single (joint) DCI, see Examples I.1.7 / I.4.7), and the TCI status indication / update exists and is signaled / received in UL-DCI (and for the transmission of UL data) or DL-DCI (and for the reception of DL data).
[0270] In an example I.9.3, regardless of whether offset parameters X and / or X' are used / configured, and regardless of whether higher-level parameters controlling the presence of TCI-DCI (e.g., tci-dci-IsPresent) are used / configured, the resulting UE procedure can (also) be based on the higher-level parameter tci-PresentInDCI in PDSCH-Config or PUSCH-Config (which controls the presence of DL-DCI or UL-DCI). For example, when the parameter tci-dci-IsPresent is "enabled" and tci-PresentInDCI is also "enabled," both TCI-DCI and UL-DCI (and / or DL-DCI) are present (configured and therefore can be received). In this scenario, TCI status indications / updates applicable to decoding DL-DCI and / or UL-DCI (in the relevant PDCCH) are signaled / received in the latest (most recent) TCI-DCI, while TCI status indications / updates applicable to decoding DL data dispatched in the relevant PDSCH (related to DL dispatch in DL-DCI) are signaled / received in the latest (most recent) DL-DCI; and / or, TCI status indications / updates applicable to transmitting UL data in the relevant PUSCH (related to UL authorization in UL-DCI) are signaled / received in the latest (most recent) UL-DCI. When the parameter tci-dci-IsPresent is "Enabled" and tci-PresentInDCI is not "Enabled", TCI-DCI exists (is configured and therefore can be received), and TCI status indication / update is TCI status indication / update in TCI-DCI (and is used to transmit both UL data and UL control associated with UL authorization in UL-DCI, and / or to receive both DL data and DL control associated with DL dispatch in DL-DCI).
[0271] In one example I.9.4, the resulting UE procedure can be activated based on higher-layer (RRC) parameters and / or MAC CE, regardless of whether offset parameters X and / or X' are used / configured.
[0272] In Example I.9.5, the resulting UE procedure can be based on system information (i.e., for all UEs in the cell) regardless of whether the offset parameters X and / or X' are used / configured.
[0273] In one embodiment I.10, the UE may be configured with semi-persistent scheduling (SPS) for DL data (PDSCH) and / or configured with permitted type 1 or type 2 PUSCH transmissions. Details of the SPS for PDSCH reception are according to embodiment I.3, and details of the SPS for the configured permitted type 1 or type 2 PUSCH transmissions are according to embodiment I.6.
[0274] In Example I.10.1, the UE is configured to receive a dedicated DCI (TCI-DCI) that instructs a common beam (TCI state) for (a) reception of DL control (PDCCH) and, if activated by the received PDCCH, also for reception of DL data (PDSCH), and / or (b) for transmission of UL control (PUCCH) and / or data (PUSCH) (configured license type 2 PUSCH) if activated by the received PDCCH. Details of (a) are according to Example I.3.1, and details of (b) are according to I.6.1.
[0275] In Example I.10.2, the UE is configured to receive a dedicated DCI (TCI-DCI) via PDCCH, which includes a common beam (TCI state) for receiving PDCCH in subsequent time slots, and if the received PDCCH is activated, the common beam is also used for (a) receiving DL data (PDSCH) scheduled by SPS and / or (b) transmitting UL data (PUSCH) (for configured license type 2 PUSCH transmission). Details of (a) are according to Example I.3.2, and details of (b) are according to I.6.2.
[0276] In Example I.10.3, the UE is configured to receive a dedicated DCI (e.g., TCI-DCI) via PDCCH, which includes (a) a field for a common beam (TCI state) and / or (b) additional fields for activation / deactivation of PDSCH reception (based on the configured SPS) and / or PUSCH transmission (configured license type 2 PUSCH). When PDSCH reception and / or PUSCH transmission are activated via field (b), the UE can be indicated / updated using field (a) with a new (TCI state) beam for PDSCH reception and / or PUSCH transmission (with or without PDCCH reception). Once field (b) is no longer activated or deactivated for PDSCH reception and / or PUSCH transmission, the UE can be indicated / updated using only field (a) with a new (TCI state) beam for PDCCH reception and / or PUSCH transmission.
[0277] In Example I.10.4, the UE is configured to receive a dedicated DCI (TCI-DCI) that indicates a common beam (TCI state) for (a) receiving DL control (PDCCH) and, if activated by the received PDCCH, also for receiving DL data (PDSCH), and / or (b) transmitting UL control (PUCCH) and / or data (PUSCH). Details of (a) are as per Example I.3.1. For (b), the UE receives (e.g., in TCI-DCI format) and decodes the TCI-DCI in time slot (or subframe) N', and begins transmitting UL control (PUCCH) (e.g., periodic PUCCH or semi-persistent PUCCH) and / or data (PUSCH) (e.g., configured license type 1) in the same (time slot N') or a subsequent time slot using the indicated beam (TCI state). Details in (b) are as per I.6.3.
[0278] In Example I.10.5, the UE can be configured to receive a dedicated DCI (TCI-DCI) indicating a common beam (TCI state) for transmitting a contention-free random access (CFRA) preamble triggered by a PDCCH. Such a PDCCH is called a PDCCH command and can be a DCI format 1_0 with the "Domain Resource Allocation" field set to all 1s, as described in TS 38.212 [REF7]. Except for the functionality of RACH-TCI-DCI being included in the TCI-DCI, the remaining details are as described in Example I.7. Note that in this example, the TCI-DCI indicates a common beam for (a) DL control and DL data and / or (b) UL data and UL control and / or (c) PRACH.
[0279] Additional examples regarding beam application timing
[0280] In Embodiment II, the UE is configured with beam indicators that include a combined DL / UL TCI for both DL reception and UL transmission (for control and / or data channels), or two separate TCIs, UL-TCI and DL-TCI, for UL transmission and DL reception respectively, wherein the beam indicators indicate M beams for DL reception and / or N beams for UL transmission. The definitions of DL-TCI, UL-TCI, and the combined DL / UL TCI are as follows.
[0281] For M=1:
[0282] -DL TCI: The (multiple) source reference signals in the DL TCI (similar to Rel.15, 2, if qcl_Type2 is configured in addition to qcl_Type1) provide QCL information for at least PDSCH in CC and UE-specific reception on all CORESETs.
[0283] For N=1:
[0284] -UL TCI: The source reference signal in the UL TCI provides a reference for determining the UL TX spatial filter, at least for the PUSCH and all dedicated PUCCH resources in the CC based on dynamic licensing / configuration.
[0285] For M = N = 1:
[0286] - Joint DL / UL TCI: TCI refers to the common source reference RS used at least to determine the DL QCL information and UL TX spatial filter.
[0287] - Separate DL / UL TCI: TCI DL and UL TCI are different (therefore, separate).
[0288] For M>1:
[0289] -DL TCI: Each of the M source reference signals (or 2M, if qcl_Type2 is configured in addition to qcl_Type1) in the M DL TCIs provides QCL information for at least one of the M beamp-pair links for UE-specific reception on the PDSCH and / or CORESET subset in the CC.
[0290] For N>1:
[0291] -UL TCI: Each of the N source reference signals in the N UL TCIs provides a reference for determining the UL TX spatial filter in at least one of the N beam pair links associated with a subset of PUSCH and / or dedicated PUCCH resources based on dynamic licensing / configuration licensing in the CC.
[0292] For M>1 and / or N>1:
[0293] - Joint DL / UL TCI: TCI refers to the common source reference RS used at least to determine the DL QCL information and the UL TX spatial filter. In this case, M = N.
[0294] - Individual DL / UL TCIs: M DL TCIs and N UL TCIs are different (therefore, individual).
[0295] In Example II.1, parameters X and X′ are determined / configured according to at least one of the following examples (as described in this disclosure).
[0296] In Example II.1.1, X = X', where X = B or X ≥ B, where B is the beam application time (for DL or UL, or a value for both DL and UL). At least one of the following examples has been used / configured.
[0297] - In one example, X is fixed.
[0298] - In one example, X is configured via higher-level RRC and / or MAC CE and / or DCI-based signaling.
[0299] - In one example, the value of X depends on the beam application time or the minimum BAT value (which can be reported by the UE) to determine (fixed or configured).
[0300] In one example II.1.2, X and X' can be different, where X = B or X ≥ B, where B is the beam application time (for DL or a common value of L for both DL and U), and similarly, X' = B' or X' ≥ B', where B' is the beam application time (for UL, or a common value of both DL and UL). At least one of the following examples has been used / configured.
[0301] - In one example, X and X' are fixed.
[0302] - In one example, X' is determined based on the value of X, where X is fixed or configured via higher-layer RRC and / or MACCE and / or DCI-based signaling, or the value of X is determined (fixed or configured) depending on the beam application time or minimum BAT value (which may be reported by the UE). The value of X' is determined based on the value of X, where the relationship between X and X' can be fixed or implicit (e.g., relationship-based) or explicit (e.g., configuration-based).
[0303] - In one example, X is determined based on the value of X', where X' is fixed, or configured via higher-layer RRC and / or MAC CE and / or DCI-based signaling, or the value of X' is determined (fixed or configured) depending on the beam application time or minimum BAT value (which may be reported by the UE). The value of X is determined based on the value of X', where the relationship between X and X' can be fixed or implicit (e.g., based on a relationship) or explicit (e.g., based on configuration).
[0304] - In one example, X and X' are configured (jointly or separately) via higher-layer RRC and / or MAC CE and / or DCI-based signaling. This configuration may depend on the beam application time or the minimum BAT value (which may be reported by the UE).
[0305] In Example II.2, the beam application time for DL reception and UL transmission (data and control channels) is determined / configured according to at least one of the following examples.
[0306] In Example II.2.1, the individual beam application time B is determined / configured via higher-layer RRC and / or MAC CE and / or DCI-based signaling. This configuration may depend on the beam application time or the minimum BAT value reported by the UE in its capability report; that is, the configured value is equal to or greater than the value reported by the UE.
[0307] The value B is applied to both X and X', i.e., X ≥ B and X' ≥ B. Therefore, no earlier than beam application time B after receiving the beam indication DCI (first or last symbol), the UE uses a new beam indicated via the beam indication DCI (e.g., TCI-DCI, UL-TCI-DCI, or DL-TCI-DCI) to receive the DL channel and / or transmit the UL channel. This is independent of whether the beam indication for DL reception and UL transmission (of data and control channels) is via a joint DL / UL TCI or two separate TCIs, i.e., DL-TCI and UL-TCI.
[0308] In Example II.2.2, two beam application time values, B1 and B2, are determined / configured via higher-layer RRC and / or MAC CE and / or DCI-based signaling. This configuration may depend on the beam application time or the minimum BAT value reported by the UE in its capability report. At least one of the following examples is used / configured.
[0309] - In one example, value B1 is applied to receive DL channels (PDCCH and PDSCH), and value B2 is applied to transmit UL channels (PUCCH and PUSCH).
[0310] - In one example, value B1 is applied to receive DL control (PDCCH) and value B2 is applied to transmit UL control (PUCCH).
[0311] - In one example, value B1 is applied when (A) the beam indication for (data and control channel) DL reception and UL transmission is via the joint DL / UL TCI, or (B) the beam indication for (data and control channel) DL reception is via DL-TCI; and value B2 is applied when the beam indication for (data and control channel) UL transmission is via UL-TCI.
[0312] - In one example, value B1 is applied when the beam indication for (data and control channels) DL reception and UL transmission is via a joint DL / UL TCI, and value B2 is applied when the beam indication for (data and control channels) DL reception and UL transmission is via two separate TCIs, namely DL-TCI and UL-TCI.
[0313] - In one example, value B1 is applied to receive DL channels (PDCCH and PDSCH) from the serving cell and / or send UL channels (PUCCH and PUSCH) to the serving cell, and value B2 is applied to receive DL channels (e.g., PDSCH) from a non-serving cell.
[0314] - In one example, when the UE does not need to change / switch its antenna panel, value B1 is applied to receive DL channels (PDCCH and PDSCH) and / or transmit UL channels (PUCCH and PUSCH), and when the UE needs to change / switch its antenna panel, value B2 is applied to receive DL channels (PDCCH and PDSCH) and / or transmit UL channels (PUCCH and PUSCH).
[0315] In Example II.2.3, the three beam application time values B1, B2, and B3 are determined / configured via higher-layer RRC and / or MAC CE and / or DCI-based signaling. This configuration may depend on the beam application time or the minimum BAT value reported by the UE in its capability report. At least one of the following examples is used / configured.
[0316] - In one example, value B1 is applied when the beam indication for DL reception and UL transmission (for data and control channels) is via the combined DL / UL TCI, value B2 is applied when the beam indication for DL reception (for data and control channels) is via the DL-TCI, and value B3 is applied when the beam indication for UL transmission (for data and control channels) is via the UL-TCI.
[0317] In Example II.3, the UE reports Z minimum BAT values in its capability report. At least one of the following examples is used / configured.
[0318] In Example II.3.1, Z = 1, meaning the UE reports a minimum BAT value that is common (identical) to both DL and UL channels. In one example, such reporting is conditional on the UE only supporting joint DL / UL TCI for beam indication (e.g., the UE may report this in its capability report). In one example, there are no additional conditions or restrictions for a UE that only reports a minimum BAT value.
[0319] In Example II.3.2, Z = 2, meaning the UE reports two distinct minimum BAT values, one for the DL channel and the other for the UL channel. In one example, such reporting is conditional upon the UE supporting two separate TCIs (DL-TCI and ULTCI) for beam indication (e.g., the UE may report this in its capability report). In one example, there are no additional conditions or restrictions for UEs that only report two minimum BAT values.
[0320] In Example II.3.3, Z=2, meaning the UE reports two distinct minimum BAT values: one for beam indication based on the joint DL / UL TCI, and another for beam indication based on two individual TCIs (DL-TCI and UL-TCI). In one example, such reporting is conditional upon (limited to) the UE supporting both the joint DL / UL TCI and the individual TCIs for beam indication (e.g., the UE may report this in its capability report). In one example, there are no additional conditions or restrictions for UEs that report only one minimum BAT value.
[0321] In Example II.3.4, Z = 2, meaning the UE reports two distinct minimum BAT values: one for beam indication based on the combined DL / UL TCI and the DL-TCI-based beam indication (for DL channels), and another for beam indication based on the UL-TCI (for UL channels). In one example, this reporting is conditional upon the UE supporting both the combined DL / UL TCI and the individual TCI for beam indication (e.g., the UE may report this in its capability report). In one example, there are no additional conditions or restrictions for UEs that report only one minimum BAT value.
[0322] In Example II.3.5, Z = 2, meaning the UE reports two distinct minimum BAT values: one for beam indication based on the joint DL / UL TCI and the UL-TCI-based beam indication (for UL channels), and another for beam indication based on the DL-TCI (for DL channels). In one example, this reporting is conditional upon the UE supporting both the joint DL / UL TCI and the individual TCI for beam indication (e.g., the UE may report this in its capability report). In one example, there are no additional conditions or restrictions for UEs that report only one minimum BAT value.
[0323] In Example II.3.6, Z = 3, meaning the UE reports three distinct minimum BAT values: a first value for beam indication based on the joint DL / UL TCI, a second value for beam indication based on the DL-TCI (for DL channels), and a third value for beam indication based on the UL-TCI (for UL channels). In one example, this reporting is conditional upon (limited to) the UE supporting both the joint DL / UL TCI and individual TCI for beam indication (e.g., the UE may report this in its capability report). In one example, for a UE that reports only one minimum BAT value, there are no additional conditions or restrictions.
[0324] In Example II.3.7, the value of Z depends on the number of antenna port groups Ng (or the number of panels) at the UE. In one example, Z = N g That is, the UE reports a minimum BAT value for each antenna port group (or antenna panel). In one example, Z=2, that is, the UE reports two minimum BAT values, one for cases where the UE does not need to change its antenna panel for DL reception and / or UL transmission, and the other for cases where the UE needs to change its antenna panel for DL reception and / or UL transmission.
[0325] In Example II.3.8, for beam indication via the combined DL-UL TCI, Z = 1, meaning the UE reports a different minimum BAT value; while for beam indication via individual TCIs (DL-TCI and UL-TCI), Z = 2, meaning the UE reports two different minimum BAT values. In one example, such reporting depends on whether the UE supports combined DL / UL TCI, two individual TCIs, or both. For example, Z = 1 when the UE only supports combined DL / UL TCI or only individual TCIs, and Z = 2 when the UE supports both.
[0326] In Example II.3.9, Z=2, that is, the UE reports two different minimum BAT values, one for receiving DL channels (PDCCH and PDSCH) from the serving cell and / or sending UL channels (PUCCH and PUSCH) to the serving cell, and the other for receiving DL channels (e.g., PDSCH) from a non-serving cell.
[0327] Any of the above variations can be used independently or in combination with at least one other variation.
[0328] Figure 22 A flowchart of a method 2200 for operating a user equipment (UE) according to an embodiment of the present disclosure is shown, which can be performed by a UE such as UE 116. Figure 22The embodiments of method 2200 shown are for illustrative purposes only. Figure 22 This disclosure is not intended to limit the scope to any particular implementation.
[0329] like Figure 22 As shown, method 2200 begins at step 2202. In step 2202, the UE (e.g., Figure 1 As shown in 111-116), configuration information regarding the Transmission Configuration Indicator (TCI) status indication is received via downlink control information (DCI). This configuration information includes a set of TCI states and information for configuring the DCI from one of the downlink (DL) DCI (DL-DCI) and DL-TCI-DCI, wherein the DL-DCI schedules the DL physical DL shared channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for TCI status indication.
[0330] In step 2204, the UE receives the configured DCI based on the configuration information. In step 2206, the UE decodes the configured DCI to obtain a TCI state update. In step 2208, the UE determines the receive beam based on the TCI state update. In step 2210, the UE applies the receive beam to the reception of DL control or DL data.
[0331] In one embodiment, TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, and the QCL type is the type of QCL attribute associated with at least one source RS; beam refers to the QCL type configured to receive or transmit spatial attributes of at least one source RS included in the TCI state update.
[0332] In one embodiment, when the configured DCI is DL-TCI-DCI, the TCI status update is used to indicate the receive beam used to receive both DL control and DL data.
[0333] In one embodiment, when the configured DCI is DL-DCI, the TCI state update is used to indicate the receive beam for receiving DL data, and the receive beam for receiving DL control is indicated by the previous TCI state, wherein: if an earlier time slot exists, the previous TCI state is indicated via DL-TCI-DCI in the earlier time slot, and if an earlier time slot does not exist, the previous TCI state is the default TCI state.
[0334] In one embodiment, the TCI status update is indicated via both DL-DCI and DL-TCI-DCI, the first TCI status update is via DL-TCI-DCI, and the second TCI status update is via DL-DCI, wherein: the first TCI status update is used to indicate the receive beam for receiving DL control, and the latest of the first and second TCI status updates is used to indicate the receive beam for receiving DL data.
[0335] In one embodiment, the UE determines the transmit beam based on the TCI state update and applies the transmit beam to the transmission of UL control or UL data, wherein: either the transmit beam is the same as the receive beam and the TCI state update indicates the joint TCI state of both DL and UL, or the transmit beam and the receive beam are separate and the TCI state update indicates two separate TCI states, one for DL and the other for UL.
[0336] In one embodiment, the configuration information includes the DCI format for the configured DCI, wherein the DCI format is the same for both DL-DCI and DL-TCI-DCI.
[0337] Figure 23 A flowchart of another method 2300 according to an embodiment of the present disclosure is shown, which can be performed by a base station (BS) such as BS102. Figure 23 The embodiments of method 2300 shown are for illustrative purposes only. Figure 23 This disclosure is not intended to limit the scope to any particular implementation.
[0338] like Figure 23 As shown, method 2300 begins at step 2302. In step 2302, BS (e.g., as...) Figure 1 As shown in 101-103), configuration information regarding the Transmission Configuration Indicator (TCI) status indication is generated via downlink control information (DCI). This configuration information includes a set of TCI states and information for configuring the DCI from one of the downlink (DL) DCI (DL-DCI) and DL-TCI-DCI, wherein the DL-DCI schedules the DL physical DL shared channel (PDSCH) assignment, and the DL-TCI-DCI is a dedicated DCI for TCI status indication.
[0339] In step 2304, the BS generates the configured DCI including the TCI status update. In step 2306, the BS sends configuration information. In step 2308, the BS sends the configured DCI including the TCI status update based on the configuration information. In step 2310, the BS sends DL control or DL data to be received by the receive beam indicated by the TCI status update.
[0340] In one embodiment, TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, and the QCL type is the type of QCL attribute associated with at least one source RS; beam refers to the QCL type configured to receive or transmit the spatial attributes of at least one source RS included in the TCI state update.
[0341] In one embodiment, when the configured DCI is DL-TCI-DCI, the TCI status update is used to indicate the receive beam used to receive both DL control and DL data.
[0342] In one embodiment, when the configured DCI is DL-DCI, the TCI state update is used to indicate the receive beam for receiving DL data, and the receive beam for receiving DL control is indicated by the previous TCI state, wherein: if an earlier time slot exists, the previous TCI state is indicated via DL-TCI-DCI in the earlier time slot, and if an earlier time slot does not exist, the previous TCI state is the default TCI state.
[0343] In one embodiment, the TCI status update is indicated via DL-DCI and DL-TCI-DCI, the first TCI status update is via DL-TCI-DCI, and the second TCI status update is via DL-DCI, wherein: the first TCI status update is used to indicate the receive beam for receiving DL control, and the latest of the first and second TCI status updates is used to indicate the receive beam for receiving DL data.
[0344] In one embodiment, the TCI status update indication will be applied to the transmit beam for the transmission of UL control or UL data, wherein: either the transmit beam is the same as the receive beam, and the TCI status update indicates the joint TCI status of both DL and UL, or the transmit beam and the receive beam are separate, and the TCI status update indicates two separate TCI statuses, one for DL and the other for UL.
[0345] In one embodiment, the configuration information includes the DCI format for the configured DCI, wherein the DCI format is the same for both DL-DCI and DL-TCI-DCI.
[0346] Figure 24 An electronic device according to an embodiment of the present disclosure is shown.
[0347] refer to Figure 24 Electronic device 2400 may include processor (or controller) 2410, transceiver 2420, and memory 2430. However, not all of the components shown are necessary. Electronic device 2400 may be composed of... Figure 24It can be implemented with more or fewer components. Furthermore, according to another embodiment, the processor 2410, transceiver 2420, and memory 2430 can be implemented as a single chip.
[0348] Electronic device 2400 may correspond to the aforementioned electronic device. For example, electronic device 2400 may correspond to... Figure 3 The UE 116 shown.
[0349] The aforementioned components will now be described in detail.
[0350] Processor 2410 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of electronic device 2400 may be implemented by processor 2410.
[0351] Transceiver 2420 may include an RF transmitter for up-converting and amplifying the transmitted signal and an RF receiver for down-converting the received signal. However, according to another embodiment, transceiver 2420 may be implemented with more or fewer components than shown in the components.
[0352] Transceiver 2420 can be connected to processor 2410 and transmit and / or receive signals. These signals may include control information and data. Furthermore, transceiver 2420 can receive signals via a wireless channel and output signals to processor 2410. Transceiver 2420 can also transmit signals output from processor 2410 via a wireless channel.
[0353] Memory 2430 may store control information or data included in signals obtained by electronic device 2400. Memory 2430 may be connected to processor 2410 and store at least one instruction or protocol or parameters for the proposed function, process, and / or method. Memory 2430 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.
[0354] Figure 25 A base station according to an embodiment of this disclosure is shown.
[0355] refer to Figure 25 Base station 2500 may include processor (or controller) 2510, transceiver 2520, and memory 2530. However, not all of the components shown are required. Base station 2500 may be composed of... Figure 25 It can be implemented with more or fewer components as shown. Furthermore, according to another embodiment, the processor 2510, transceiver 2520, and memory 2530 can be implemented as a single chip.
[0356] Base station 2500 can correspond to the aforementioned gNB. For example, base station 2500 can correspond to... Figure 2 The gNB 102 shown.
[0357] The aforementioned components will now be described in detail.
[0358] Processor 2510 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of base station 2500 may be implemented by processor 2510.
[0359] Transceiver 2520 may include an RF transmitter for up-converting and amplifying the transmitted signal and an RF receiver for down-converting the received signal. However, according to another embodiment, transceiver 2520 may be implemented with more or fewer components than shown in the components.
[0360] Transceiver 2520 can be connected to processor 2510 and transmit and / or receive signals. These signals may include control information and data. Furthermore, transceiver 2520 can receive signals via a wireless channel and output signals to processor 2510. Transceiver 2520 can also transmit signals output from processor 2510 via a wireless channel.
[0361] The memory 2530 may store control information or data included in the signals obtained by the base station 2500. The memory 2530 may be connected to the processor 2510 and store at least one instruction or protocol or parameters for the proposed function, process and / or method. The memory 2530 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.
[0362] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.
[0363] The flowchart above illustrates an example method that can be implemented according to the principles of this disclosure, and various modifications can be made to the method shown in the flowchart herein. For example, although shown as a series of steps, the individual steps in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps can be omitted or replaced by other steps.
[0364] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Nothing described herein should be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.
Claims
1. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and The controller is configured as follows: The transceiver receives configuration information from the base station, including a set of one or more Transmission Configuration Indicator (TCI) states and parameters indicating the presence of TCI fields in the Downlink Control Information (DCI) used for downlink reception. Based on configuration information, a DCI (Digital Cipher Interface) including a TCI field indicating one or more TCI states is received from the base station via a transceiver. The DCI is specifically used for TCI states that do not have downlink dispatch, where the scheduling dispatch field in the DCI is set to a predetermined value, and The indicated TCI state is applied to the reception of at least one of the Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH).
2. The UE according to claim 1, wherein, DCI corresponds to DCI format 1_1 or DCI format 1_2.
3. The UE according to claim 1, wherein, The TCI field indicates the combined TCI status used for both downlink and uplink.
4. A base station in a wireless communication system, the base station comprising: transceiver; and The controller is configured as follows: The transceiver sends configuration information to the user equipment (UE) including a set of one or more Transport Configuration Indicators (TCI) states and parameters indicating the presence of TCI fields in the downlink control information (DCI) for downlink reception. The DCI, which includes a TCI field indicating the TCI state in a set of one or more TCI states, is transmitted to the UE via the transceiver. The indicated TCI state is applied to the transmission of at least one of the Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH). DCI is specifically used for TCI states that do not have downlink dispatch, and DCI includes a scheduling and assignment field that is set to a predetermined value.
5. The base station according to claim 4, wherein, DCI corresponds to DCI format 1_1 or DCI format 1_2.
6. The base station according to claim 4, wherein, The TCI field indicates the combined TCI status used for both downlink and uplink.
7. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive configuration information from the base station, including a set of one or more Transmission Configuration Indicator (TCI) states and parameters indicating the presence of TCI fields in the Downlink Control Information (DCI) for downlink reception; Based on configuration information, receive DCI from the base station including a TCI field indicating one or more TCI states from a set of TCI states; DCI is identified specifically for TCI states that do not have downlink dispatch, where the scheduling dispatch field in DCI is set to a predetermined value. as well as The indicated TCI state is applied to the reception of at least one of the Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH).
8. The method according to claim 7, wherein, DCI corresponds to DCI format 1_1 or DCI format 1_2.
9. The method according to claim 7, wherein, The TCI field indicates the combined TCI status used for both downlink and uplink.
10. A method performed by a base station in a wireless communication system, the method comprising: Send to the user equipment (UE) a set including one or more Transport Configuration Indicator (TCI) states and configuration information indicating the presence of TCI fields in the downlink control information (DCI) for downlink reception; Send a DCI to the UE, which includes a TCI field indicating one or more TCI states from a set of TCI states; and The indicated TCI state is applied to the transmission of at least one of the Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH). DCI is specifically used for TCI states that do not have downlink dispatch, and DCI includes a scheduling and assignment field that is set to a predetermined value.
11. The method according to claim 10, wherein, DCI corresponds to DCI format 1_1 or DCI format 1_2.
12. The method according to claim 10, wherein, The TCI field indicates the combined TCI status used for both downlink and uplink.