Method and apparatus for dynamic beam indication mechanism

Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system with a higher data rate beyond a 4th-Generation (4G) system and an Internet of Things (IoT) technology. The disclosure can be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, car-to-car, health care, digital education, smart retail, security and safety services, etc. The disclosure provides a method for operating a user equipment (UE), the method comprising: receiving configuration information, the configuration information including a set of transmission configuration indicator (TCI) states; receiving a medium access control-control element (MAC-CE) indicating that M TCI states are activated from the set of TCI states, where M is a positive integer; identifying a medium indicating a TCI state update, where the medium is a MAC-CE or a downlink control information (DCI), and the TCI state update is from the M activated states; determining a beam based on the TCI state update; and applying the beam to reception of both downlink (DL) control and data channels.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication systems, and more specifically to methods for dynamic beam indication. Background Technology

[0002] To meet the increasing demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher (mmWave) frequency 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-size MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed relative to 5G communication systems. Furthermore, improvements to system networks are being developed 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, system networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0003] The Internet is a human-centric, connected network where people generate and consume information. Today, the Internet is evolving into the Internet of Things (IoT), enabling information exchange and processing by distributed entities, such as objects, without human intervention. The Internet of Everything (IoE) has emerged, a combination of IoT technologies and big data processing technologies enabled by connections to cloud servers. Recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC), as technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required for IoT implementation. Such IoT environments can provide intelligent Internet of Things (IoT) services that create new value for human life by collecting and analyzing data generated between interconnected objects. Through the integration and combination of existing information technology (IT) with various industrial technologies, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Accordingly, 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 through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RAN), as a big data processing technology, 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 downlink channel conditions, the gNB can send a reference signal, such as CSI-RS, to the UE for downlink channel measurement, and the UE can report (e.g., provide feedback) information about the channel measurements, such as the CSI, to the gNB. Through this downlink channel measurement, the gNB can select appropriate communication parameters to perform wireless data communication with the UE efficiently and effectively. 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 for communication. In such beamforming systems, a beam indication mechanism is required to align the spatial beam at both the gNB and the UE. Summary of the Invention

[0006] Technical issues

[0007] For more efficient communication systems, enabling dynamic beam pointing is necessary.

[0008] Technical solution

[0009] In one embodiment, a UE in a communication system is provided. The UE includes: a transceiver configured to receive configuration information including a set of Transmit Configuration Indicator (TCI) states, and to receive Media Access Control-Control Elements (MAC-CEs) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer. The UE also includes a processor operatively coupled to the transceiver. The processor is configured to identify media used to indicate TCI state updates, wherein the media is MAC-CE or downlink control information (DCI) received via the transceiver, and the TCI state update is from M activated states; to determine a beam based on the TCI state update; and to apply the beam to the reception of both downlink (DL) control and data channels, wherein: the TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, wherein the QCL type is a type of QCL attribute associated with at least one source RS; and wherein the beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0010] In another embodiment, a BS is provided in a communication system. The BS includes a processor configured to generate configuration information including a set of Transmit Configuration Indicator (TCI) states, and to generate Media Access Control-Control Elements (MAC-CEs) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer. The BS also includes a transceiver operatively coupled to the processor, configured to transmit the configuration information, transmit TCI state updates indicating beams from the M activated TCI states via a medium, wherein the medium is MAC-CE or Downlink Control Information (DCI), and transmit downlink (DL) control and data channels for reception via the indicated beams, wherein: the TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, wherein the QCL type is a type of QCL attribute associated with at least one source RS, and wherein the beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0011] In another embodiment, a method for operating a UE is provided. The method includes: receiving configuration information including a set of Transmit Configuration Indicator (TCI) states; receiving a Media Access Control-Control Element (MAC-CE) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer; identifying media indicating a TCI state update, where the media is a MAC-CE or Downlink Control Information (DCI), and the TCI state update comes from the M activated states; determining a beam based on the TCI state update; and applying the beam to the reception of both downlink (DL) control and data channels, wherein: the TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, where the QCL type is a type of QCL attribute associated with at least one source RS; and wherein the beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0012] Other technical features will be readily apparent to those skilled in the art from the following figures, description and claims.

[0013] Before proceeding with the detailed description below, it may be advantageous to clarify the definitions of certain words and phrases used throughout this disclosure. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “send,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “include” and “contain,” and their derivatives mean, but are not limited to, including. The term “or” is inclusive, meaning “and / or.” The phrase “associated with” and its derivatives mean to include, contain, interconnect, contain, enclose, connected to or linked with, coupled to or coupled with, communicate with, cooperate with, interweave with, juxtapose with, proximate with, bind to or bind with, possess, have its attributes, associate with or be associated with, or similar meanings. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such controllers 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, either locally or remotely. When used with a series of items, the phrase “at least one of…” means that different combinations of one or more of the listed items may be used, and that only one of the listed items 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.

[0014] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by computer-readable program code and implemented in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, programs, functions, objects, classes, instances, associated data, or portions thereof implemented 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 that can be accessed 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 signals or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and later overwrite said data, such as rewritable optical discs or erasable storage devices.

[0015] Definitions of certain other words and phrases are provided throughout this patent document. It will be understood by one of ordinary skill in the art that, in many cases, if not most, these definitions apply to the prior and future use of the defined words and phrases.

[0016] Beneficial effects

[0017] According to this disclosure, a method and apparatus for enabling dynamic beam pointing in a wireless communication system are provided. Attached Figure Description

[0018] To gain a more complete understanding of this disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts:

[0019] Figure 1 An exemplary wireless network according to an embodiment of this disclosure is shown;

[0020] Figure 2 An exemplary gNB according to an embodiment of this disclosure is shown;

[0021] Figure 3 An exemplary UE according to an embodiment of this disclosure is shown;

[0022] Figure 4A A high-level schematic diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure is shown;

[0023] Figure 4B A high-level schematic diagram of an orthogonal frequency division multiple access (OFDM) receiving path according to an embodiment of the present disclosure is shown;

[0024] Figure 5 A block diagram of a PDSCH transmitter in a subframe according to an embodiment of the present disclosure is shown;

[0025] Figure 6 A receiver block diagram of a PDSCH in a subframe according to an embodiment of the present disclosure is shown;

[0026] Figure 7 A block diagram of a PUSCH transmitter in a subframe according to an embodiment of the present disclosure is shown.

[0027] Figure 8 A receiver block diagram of a PUSCH in a subframe according to an embodiment of the present disclosure is shown;

[0028] Figure 9 This illustrates an exemplary reuse of two slices according to embodiments of the present disclosure;

[0029] Figure 10 This illustrates uplink multi-beam operation according to an embodiment of the present disclosure;

[0030] Figure 11 This illustrates uplink multi-beam operation according to an embodiment of the present disclosure;

[0031] Figure 12 This illustrates downlink multi-beam operation according to an embodiment of the present disclosure;

[0032] Figure 13 An example of a dedicated DCI for receiving downlink control and data, according to embodiments of this disclosure, is shown;

[0033] Figure 14 An example of a dedicated DCI for transmitting uplink control and data, according to embodiments of this disclosure, is shown;

[0034] Figure 15 An example of a dedicated DCI for a common beam for all downlink and uplink channels is shown according to an embodiment of this disclosure;

[0035] Figure 16 An example of a DL MAC PDU according to an embodiment of this disclosure is shown;

[0036] Figure 17 An example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0037] Figure 18Another example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0038] Figure 19 Another example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0039] Figure 20 An example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0040] Figure 21 Another example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0041] Figure 22 Another example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which a single TCI state is indicated in the common beam (TCI state) indication;

[0042] Figure 23 An example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which two TCI states are indicated in the common beam (TCI state) indication;

[0043] Figure 24 Another example of a MAC CE for common beam (TCI state) indication according to an embodiment of the present disclosure is shown, in which two TCI states are indicated in the common beam (TCI state) indication;

[0044] Figure 25 A flowchart illustrating a method for operating a UE according to an embodiment of this disclosure is shown;

[0045] Figure 26 A flowchart illustrating a method for operating a BS according to an embodiment of the present disclosure is shown;

[0046] Figure 27 A UE is shown according to an embodiment of this disclosure; and

[0047] Figure 28 A base station according to an embodiment of this disclosure is shown. Detailed Implementation

[0048] The following discussion Figures 1 to 28The 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 apparatus.

[0049] The following documents and standards are hereby incorporated in this disclosure by reference, as if fully set forth herein: 3GPP TS 36.211 v16.4.0, “E-UTRA, Physical Channels and Modulation” (referred to herein as “REF 1”); 3GPP TS 36.212 v16.4.0, “E-UTRA, Multiplexing and Channel Coding” (referred to herein as “REF 2”); 3GPP TS 36.213 v16.4.0, “E-UTRA, Physical Layer Procedures” (referred to herein as “REF 3”); 3GPP TS 36.321 v16.3.0, “E-UTRA, Media Access Control (MAC) Protocol Specification” (referred to herein as “REF 4”); 3GPP TS 36.331 v16.3.0, “E-UTRA, Radio Resource Control (RRC) Protocol Specification” (referred to herein as “REF 5”); 3GPP TS 3GPP TS 38.211 v16.4.0, “NR, Physical Channels and Modulation” (referred to as “REF 6” in this document); 3GPP TS 38.212 v16.1.0, “NR, Multiplexing and Channel Coding” (referred to as “REF 7” in this document); 3GPP TS 38.213 v16.1.0, “NR, Physical Layer Control Procedures” (referred to as “REF 8” in this document); 3GPP TS 38.214 v16.1.0, “NR, Physical Layer Data Procedures” (referred to as “REF 9” in this document); 3GPP TS 38.215 v16.1.0, “NR, Physical Layer Measurements” (referred to as “REF 10” in this document); 3GPP TS 38.321 v16.1.0; 3GPP TS 38.321 “NR, Media Access Control (MAC) Protocol Specification” (referred to as “REF 11” in this document); and 3GPP TS38.331 v16.1.0, “NR, Radio Resource Control (RRC) Protocol Specification” (referred to as “REF 12” in this document).

[0050] The aspects, features, and advantages of this disclosure will become apparent from the following detailed description only by illustrating several specific embodiments and implementations, including the best mode contemplated for carrying out this disclosure. Other different embodiments of this disclosure are also possible, and modifications may be made to several details in various obvious aspects without departing from the spirit and scope of this disclosure. Accordingly, the drawings and description are to be considered illustrative in nature and not restrictive. This disclosure is illustrated in the accompanying figures by way of example rather than limitation.

[0051] In the following text, for the sake of brevity, both FDD and TDD will be regarded as duplex methods for DL ​​and UL signaling.

[0052] Although the following exemplary description and embodiments 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).

[0053] To meet the ever-increasing 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 being deployed. 5G / NR communication systems are considered to be implemented in higher frequency bands (mmWave), such as 28 GHz or 60 GHz, to achieve higher data rates, or in lower frequency bands, such as 6 GHz, to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-size MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed relative to 5G communication systems.

[0054] In addition, in 5G / NR communication systems, improvement schemes for system networks are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, system networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.

[0055] Since some embodiments of this disclosure can be implemented in 5G systems, the discussion of 5G systems and their associated frequency bands is for reference only. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be utilized in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even higher versions that can use terahertz (THz) frequency bands.

[0056] The following text Figure 1-4BVarious 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 to 3 The description herein does not imply any physical or architectural limitation on the implementation of the different embodiments. Different embodiments of this disclosure can be implemented in any suitably arranged communication system. This disclosure covers multiple components that can be combined or used in combination with each other, or can operate as independent solutions.

[0057] Figure 1 An exemplary wireless network according to an embodiment of this disclosure is shown. Figure 1 The illustrated embodiment of the wireless network is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0058] 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.

[0059] 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 within a small business; UE 112, which may be located within an enterprise (E); UE 113, which may be located within a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop computer, 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 of 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.

[0060] 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 transmitting point (TP), a transmitting-receiving 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 that provide 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).

[0061] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are illustrated as nearly 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.

[0062] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for: receiving configuration information, the configuration information including a set of Transmit Configuration Indicator (TCI) states; receiving a Media Access Control-Control Element (MAC-CE) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer; identifying media indicating a TCI state update, where the media is a MAC-CE or Downlink Control Information (DCI), and the TCI state update comes from M activated states; determining a beam based on the TCI state update; and applying the beam to the reception of both downlink (DL) control and data channels, wherein: the TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, where the QCL type is a type of QCL attribute associated with at least one source RS, and where the beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update. One or more of gNB 101-103 include circuitry, procedures, or combinations thereof for: generating configuration information including a set of Transmit Configuration Indicator (TCI) states; generating a Media Access Control-Control Element (MAC-CE) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer; transmitting the configuration information; transmitting TCI state updates indicating beams from the M activated TCI states via a medium, where the medium is a MAC-CE or Downlink Control Information (DCI); and transmitting downlink (DL) control and data channels for reception via the indicated beams, wherein: a TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, where the QCL type is a type of QCL attribute associated with at least one source RS, and where a beam refers to a QCL type set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0063] 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 those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide 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.

[0064] Figure 2An exemplary gNB 102 according to an embodiment of this disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have various configurations, and Figure 2 This disclosure is not intended to limit the scope to any particular implementation of gNB.

[0065] 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.

[0066] RF transceivers 210a-210n receive input RF signals from antennas 205a-205n, such as signals transmitted by a UE in network 100. RF transceivers 210a-210n down-convert the input RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 220, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 220 sends the processed baseband signals to controller / processor 225 for further processing.

[0067] The TX processing circuit 215 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. RF transceivers 210a-210n receive the processed baseband or IF signal from the TX processing circuit 215 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 205a-205n.

[0068] 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, the controller / processor 225 may control the RF transceivers 210a-210n, the RX processing circuit 220, and the TX processing circuit 215 to receive forward channel signals and transmit reverse channel signals, based on known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities.

[0069] For example, the controller / processor 225 can support beamforming or directional routing operations, where the output signals from multiple antennas 205a-205n are weighted differently to effectively steer the output signals in the desired direction. The controller / processor 225 can also support any of a variety of other functions within the gNB 102.

[0070] 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 by the executing process.

[0071] 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(s). 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 infrastructure supporting communication via wired or wireless connections, such as Ethernet or RF transceivers.

[0072] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0073] although Figure 2 An example of gNB 102 is shown, but it is possible to see more. Figure 2 Various modifications can be made. For example, gNB 102 can include any number of... Figure 2 Each component shown. As a specific example, an access point may include multiple interfaces 235, and a controller / processor 225 may support routing functionality to route data between different network addresses. As another specific example, although illustrated as a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, the gNB 102 may include multiple instances of each type of circuitry (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.

[0074] Figure 3An exemplary UE 116 according to an embodiment of this disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have various configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0075] 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 an 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.

[0076] RF transceiver 310 receives an input RF signal transmitted by a gNB of network 100 from antenna 305. RF transceiver 310 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends 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).

[0077] The TX processing circuit 315 receives analog or digital voice data from the microphone 320 or other output baseband data (such as network data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal transmitted via the antenna 305.

[0078] 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, processor 340 may control the RF transceiver 310, RX processing circuit 325, and TX processing circuit 315 to receive forward channel signals and transmit reverse channel signals according to known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0079] The processor 340 is also capable of executing other processes and programs residing in the memory 360, such as processes for performing the following operations: receiving configuration information, including a set of Transmit Configuration Indicator (TCI) states; receiving a Media Access Control-Control Element (MAC-CE) indicating the activation of M TCI states from the set of TCI states, where M is a positive integer; identifying media indicating TCI state updates, where the media is either a MAC-CE or Downlink Control Information (DCI), and the TCI state updates originate from the M activated states; determining a beam based on the TCI state updates; and applying the beam to both downlink (DL) control and data channel reception, wherein: a TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type, where the QCL type is a type of QCL attribute associated with at least one source RS, and the beam refers to the QCL type being set to a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update. The processor 340 may move data into or out of the memory 360 as needed for the executing 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. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0080] 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).

[0081] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), and another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0082] although Figure 3 An example of UE 116 is shown, but it is possible to see more. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, 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 3The 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.

[0083] Figure 4A This is a high-level schematic diagram of the transmit path circuit. For example, the transmit path circuit can be used for Orthogonal Frequency Division Multiple Access (OFDMA) communication. Figure 4B This is a high-level schematic 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 4B In the context of downlink communication, the transmitting path circuitry can be implemented in the base station (gNB) 102 or a relay station, while the receiving path circuitry can be implemented in the user equipment (e.g., Figure 1 User equipment 116). In other examples, for uplink communication, the receive path circuit 450 can be implemented at the base station (e.g., Figure 1 In the gNB 102) or relay station, and the transmission path circuit can be implemented in the user equipment (e.g., Figure 1 In user equipment 116).

[0084] The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a big-N 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 includes a down-converter (DC) 455, a cyclic prefix removal block 460, a serial-to-parallel (S-to-P) block 465, a big-N fast Fourier transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0085] Figure 4A At least some of the components in 400 and 4B 450 can be implemented in software, while others can be implemented via configurable hardware or a combination of software and configurable hardware. Specifically, it should be noted that the FFT and IFFT blocks described in this disclosure can be implemented as configurable software algorithms, wherein the value of size N can be modified according to the appropriate implementation.

[0086] Furthermore, although this disclosure pertains to embodiments implementing the Fast Fourier Transform (FFT) and Inverse Fast Fourier Transform (IFFT), this is merely illustrative and should not be construed as limiting the scope of this disclosure. It should be understood that in alternative embodiments of this disclosure, the FFT and IFFT functions can be readily replaced by 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 a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0087] 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 serial 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 size N 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 size N 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 via the wireless channel. The signal can also be filtered in baseband before being converted to RF frequency.

[0088] 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 and removes the cyclic prefix (CRMF) using block 460 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. Size-N FFT block 470 then 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 the modulated symbols and then decodes them to recover the original input data stream.

[0089] 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 can implement 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 can implement a reception path corresponding to the architecture used for reception from gNBs 101-103 in the downlink.

[0090] Use cases for 5G communication systems have been identified and described. These use cases can be roughly divided into three distinct groups. In one example, enhanced mobile broadband (eMBB) was identified to meet high bit / second requirements with relatively less stringent latency and reliability requirements. In another example, ultra-reliable low latency (URLL) was identified with relatively less stringent bit / second requirements. In yet another example, massive machine-type communication (mMTC) was identified where the number of devices per square kilometer can reach 100,000 to 1 million, but with relatively less stringent reliability / throughput / latency requirements. This situation may also involve power efficiency requirements, as battery consumption can be minimized as much as possible.

[0091] A communication system includes a downlink (DL) that transmits signals from a transmitting 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, often also called a terminal or mobile station, can be fixed or mobile and can be a cellular phone, personal computer device, or automated device. An eNodeB, typically a fixed station, can also be called an access point or other equivalent terms. In LTE systems, a NodeB is typically referred to as an eNodeB.

[0092] In communication systems such as LTE, DL signals can include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS), also known as pilot signals. The eNodeB transmits data information via the Physical DL Shared Channel (PDSCH). The eNodeB transmits DCI via the Physical Downlink Control Channel (PDCCH) or the Enhanced PDCCH (EPDCCH).

[0093] 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 for demodulating data or control information or performing measurements. To reduce CRS overhead, the eNodeB can transmit CSI-RS at a lower density in the time and / or frequency domains than CRS. DMRS can only be transmitted in the BW of the corresponding PDSCH or EPDCCH, and the UE can use DMRS in the corresponding PDSCH or EPDCCH to demodulate data or control information, respectively. The transmission interval of the DL channel is called a subframe and can have a duration of, for example, 1 millisecond.

[0094] The DL signal also includes the transmission of logical channels carrying system control information. The BCCH is mapped to a transport channel called the Broadcast Channel (BCH) when the DL signal transmits the Main Information Block (MIB), or to the Shared Channel (DL-SCH) when the DL signal transmits the System Information Block (SIB). Most system information is included in the different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe can be indicated by the transmission of the corresponding PDCCH, which transmits codewords with Cyclic Redundancy Check (CRC) scrambled with system information RNTI (SI-RNTI). Alternatively, 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.

[0095] DL resource allocation is performed in subframes and within a set of Physical Resource Blocks (PRBs). Transmitting a BW consists of frequency resource elements called resource blocks (RBs). Each RB comprises N... EPDCCH Each subcarrier or resource element (RE) can have a total of 12 REs. The unit of one RB on a subframe is called a PRB. A total of BWs can be transmitted against the PDSCH. One RE, allocate n to the UE s =(n s0 +y·N EPDCCH )mod D of RB.

[0096] UL signals may include data signals for transmitting data information, control signals for transmitting UL control information (UCI), and UL RS. UL RS may include DMRS and SRS. The UE only transmits DMRS in the BW of the corresponding PUSCH or PUCCH. 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 the corresponding 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 these two in the PUSCH. UCI includes: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, indicating the absence of a correct (ACK) or incorrect (NACK) detection of data TB in the PDSCH or a PDCCH detection (DTX); a scheduling request (SR), indicating whether the UE has data in its UE buffer; a rank indicator (RI); and channel state information (CSI), enabling the eNodeB to perform link adaptation for PDSCH transmissions to the UE. HARQ-ACK information is also sent by the UE in response to the detection of a PDCCH / EPDCCH, which indicates the release of a semi-persistently scheduled PDSCH.

[0097] A UL subframe consists of two time slots. Each time slot includes a space for transmitting data information, UCI, DMRS, or SRS. One symbol. The frequency resource unit of the UL system BW is RB. For all transmitting BW... One RE, allocate N to the UE RS RB. For PUCCH, N RB =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 transmission is If the last subframe symbol is used to transmit SRS, then N SRS =1, otherwise N SRS =0.

[0098] Figure 5 A block diagram 500 of a PDSCH transmitter in a subframe according to an embodiment of the present disclosure is shown. Figure 5 The embodiment of the transmitter block diagram 500 shown is for illustrative purposes only. Figure 5 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more 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 embodiment of the transmitter block diagram 500.

[0099] like Figure 5 As 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 transmit BW selection unit 555 for the assigned PDSCH transmit 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 as signal 590. Additional functions, such as data scrambling, cyclic prefix insertion, time windowing, interleaving, etc., are well known in the art and are not shown for simplicity.

[0100] Figure 6 A receiver block diagram 600 of a PDSCH in a subframe according to an embodiment of the present disclosure is shown. Figure 6 The embodiment of diagram 600 shown is for illustrative purposes only. Figure 6 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 6 This disclosure is not limited to any particular implementation of Figure 600.

[0101] like Figure 6 As shown, the received signal 610 is filtered by filter 620, the RE 630 for the assigned receive BW is selected by BW selector 635, unit 640 applies Fast Fourier Transform (FFT), and the output is serialized by parallel 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.

[0102] Figure 7 A block diagram 700 of a PUSCH transmitter in a subframe according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of block diagram 700 shown is for illustrative purposes only. Figure 5 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 7This disclosure is not limited to any particular embodiment of block diagram 700.

[0103] like Figure 7 As shown, information 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, transmit BW selection unit 755 selects RE 750 corresponding to the assigned PUSCH transmit BW, unit 760 applies IFFT, and after cyclic prefix insertion (not shown), filter is applied by filter 770, and transmit signal 780 is transmitted.

[0104] Figure 8 A receiver block diagram 800 of a PUSCH in a subframe according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of block diagram 800 shown is for illustrative purposes only. Figure 8 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 8 This disclosure is not limited to any particular implementation of block diagram 800.

[0105] 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, and the receive BW selector 845 selects the RE 840 corresponding to the assigned PUSCH receive BW. Unit 850 applies inverse DFT (IDFT), demodulator 860 coherently demodulates the data symbols by applying a channel estimate obtained from DMRS (not shown), and decoder 870, such as a turbo decoder, decodes the demodulated data to provide an estimate of the information data bits 880.

[0106] In next-generation cellular systems, many envisioned use cases exceed the capabilities of LTE systems. One requirement is that systems known as 5G, or fifth-generation cellular systems, can operate both below and above 6GHz (e.g., in mmWave 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, called “enhanced mobile broadband (eMBB),” targets high data rate services with less stringent latency and reliability requirements. The second group, called “ultra-reliable and low-latency (URLL),” targets applications with less stringent data rate requirements but lower latency tolerance. The third group, called “massive MTC (mMTC),” targets a large number of low-power device connections, such as 1 million device connections per square kilometer, with less stringent requirements for reliability, data rate, and latency.

[0107] 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.

[0108] 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.

[0109] Figure 9 An exemplary reuse of two slices 900 according to an embodiment of this disclosure is shown. Figure 9 The two slices 900 shown in the examples are for illustrative purposes only. Figure 9 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 9 This disclosure is not limited to any particular implementation of the reuse of the two slices 900.

[0110] The 3GPP NR specification supports up to 32 CSI-RS antenna ports, enabling eNBs 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. For the mmWave band, although the number of antenna elements may be greater for a given form factor, the number of CSI-RS ports (which can correspond to the number of digital precoding ports) is often limited by hardware constraints (such as the feasibility of installing a large number of ADCs / DACs at mmWave frequencies). Figure 9As shown. In this case, a CSI-RS port is mapped to a large number of antenna elements that can be controlled by a set of analog phase shifters 901. A CSI-RS port can then correspond to a subarray that generates a narrow analog beam through analog beamforming 905. This analog beam can be configured to sweep a wider angular range (920) by changing the set of phase shifters across symbols or subframes. The number of subarrays (equal to the number of RF chains) is the same as the number of CSI-RS ports (NCSI-PORTs). Digital beamforming units 910 perform linear combination across the NCSI-PORT analog beams to further increase precoding gain. Although the analog beam is wideband (and therefore not frequency-selective), digital precoding can vary across frequency subbands or resource blocks. Receiver operation can be envisioned similarly.

[0111] Because the aforementioned system utilizes multiple analog beams for transmission and reception (where one or a few analog beams are selected from a large number of analog beams, for example, after the training duration – this is performed from time to time), 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 transmit beam via selecting the corresponding receive (RX) beam.

[0112] 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 m), more and sharper analog beams (and therefore more radiators in the array) are needed to compensate for the additional path loss.

[0113] In 3GPP LTE and NR (New Radio Access or Interface), network access and radio resource management (RRM) are enabled through 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 its synchronization signal and / or measuring the associated cell-specific RS (e.g., by measuring its RSRP). For next-generation cellular systems, an efficient and uniform radio resource acquisition or tracking mechanism is needed that is 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 desired, given the likelihood of different network and radio resource paradigms being designed. Such goals present at least the following challenges when designing the access, radio resource, and mobility management framework.

[0114] First, because NR can support more diverse network topologies, the concept of a cell can be redefined or replaced by another radio resource entity. 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 a desirable characteristic. Second, when using large antenna arrays and beamforming, defining radio resources according to the beam (although the naming may differ) may be a natural approach. Given that many beamforming architectures can be used, it is desirable to have access, radio resource, and mobility management frameworks that can accommodate various beamforming architectures (or conversely, those independent of beamforming architectures). For example, the framework should be applicable to, or not limited to, forming a beam for a single CSI-RS port (e.g., multiple analog ports connected to a single digital port, and using multiple wide-separation digital ports) or a beam 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 impose different coverage constraints. For example, the mmWave band can cause significant propagation loss. Therefore, some form of coverage enhancement scheme is needed. Several candidate schemes include beam scanning (see...). Figure 9 (), repetition, diversity, and / or multiple TRP transmission. For mMTC with limited transmission bandwidth, time-domain repetition is required to ensure sufficient coverage.

[0115] 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 user groups, the additional overhead associated with higher-layer procedures can further burden the system. This can be achieved by relaxing cell boundaries, creating a large “supercell” where a large number of UEs can roam. In this case, 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 streamlined MIMO design. This presents challenges if implemented in current systems.

[0116] Therefore, an access, radio resource, and mobility management framework is needed that facilitates seamless access by reducing the number of higher-layer processes. Furthermore, streamlined MIMO designs that promote high-capacity MIMO transmission are also required.

[0117] In the 3GPP NR specification, multi-beam operation is primarily used for single transmit-receive point (TRP) and single antenna panel. Therefore, the specification supports beam indication for a single TX beam, where one 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, including the primary synchronizing signal, secondary synchronizing signal, and PBCH). Here, DL beam indication is accomplished via the Transmit Configuration Indicator (TCI) field in the DL-related DCI, which includes an index to one (and only one) assigned reference RS. A set of hypothetical or so-called TCI states is configured via higher-layer (RRC) signaling, and, where applicable, a subset of these TCI states is selected / activated for the TCI field codepoint 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 via 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.

[0118] In the 3GPP NR specification, beam management was designed to share the same framework as CSI acquisition. However, this compromises beam management performance, especially for FR2. This is because beam management primarily operates using analog beams (a characteristic of FR2), which differs paradigmatically from CSI acquisition (designed with FR1 in mind). Consequently, 3GPP NR specification beam management becomes cumbersome and unlikely to keep pace with more aggressive use cases requiring large beams and rapid beam switching (e.g., higher frequency bands, high mobility, and / or more narrower analog beams). Furthermore, the 3GPP NR specification was designed to accommodate many unknown or basic functions (e.g., UEs unable to perform beam-corresponding operations). This flexibility resulted in numerous options. This became cumbersome for L1 control signaling, leading to extensive reconfiguration being performed via RRC signaling (higher-level configuration). While this avoids L1 control overhead, it also results in high latency (if reconfiguration is performed sparsely) or high PDSCH utilization (because RRC signaling consumes PDSCH resources).

[0119] In the 3GPP NR specification, similar to LTE, the handover process for handling inter-cell mobility heavily relies on RRC (and even higher layers) reconfiguration to update cell-specific parameters. This reconfiguration is typically slow and introduces significant latency (up to several milliseconds). For highly mobile UEs, this problem is exacerbated by the need for more frequency handovers, resulting in even more frequency RRC reconfigurations.

[0120] For highly mobile UEs in FR2, the two latency issues mentioned above—layered NW architecture (with visible cell boundaries) and 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.

[0121] One such solution / mechanism is based on a unified TCI state (beam indication) framework, where a common beam (or TCI state) is used (associated with) both data (PDSCH / PUSCH) and control (PDCCH / PUCCH) transmission / reception, and also for DL ​​and UL (e.g., when maintaining beam correspondence between DL and UL). In this common beam (or TCI state)-based multi-beam operation, the common beam (TCI state) indication / update must occur (independently with) the control information (e.g., DL / UL related DCI in PDCCH) scheduled for transmission / reception of DL allocation for DL ​​data (PDSCH) or UL authorization for UL data (PUSCH). Note that common beam-based multi-beam operation is supported in 3GPP NR specification beam management, 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, this MAC-CE-based common beam activation is too slow.

[0122] Because the TCI state of the data beam is updated in a time slot (or subframe) preceding the time slot (or subframe) carrying the DCI for scheduling DL allocation or UL authorization, there may be a performance degradation compared to when the TCI state update of the data beam is performed together with DL allocation or UL authorization. This problem can be exacerbated for highly mobile UEs that require frequent / accurate data beam updates for seamless data transmission / reception. Several embodiments and examples are provided in this disclosure to address this issue.

[0123] In this disclosure, the term "activation" describes the following operation: the UE receives and decodes a signal indicating a start time point from the network (or gNB). The start point can be a current or future time slot / subframe or symbol, i.e., an exact location implicitly or explicitly indicated, or otherwise fixed or configured at a higher layer. Once the signal is successfully decoded, the UE responds accordingly. The term "deactivation" describes the following operation: the UE receives and decodes a signal indicating a stop time point from the network (or gNB). The stop point can be a current or future time slot / subframe or symbol, i.e., an exact location implicitly or explicitly indicated, or otherwise fixed or configured at a higher layer. Once the signal is successfully decoded, the UE responds accordingly.

[0124] Terms such as TCI, TCI status, SpatialRelationInfo, target RS, reference RS, and others are for descriptive purposes and are therefore not normative. Other terms referring to the same function may also be used.

[0125] 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 receive reference RS index / ID in TCI state in an assigned DL, the UE applies the known characteristics of the reference RS to the assigned UL transmission. The UE can receive and measure the reference RS (in this case, the reference RS is a downlink signal such as NZP CSI-RS and / or SSB), and the measurement results are used to calculate a beam report (in the 3GPP NR specification, at least one L1-RSRP is accompanied by at least one CRI). As the NW / gNB receives the beam report, the NW can be better equipped with information to assign a specific DL TX beam to the UE. Optionally, 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 necessary information to assign a specific DL TX beam to the UE. This option is applicable when a DL-UL beam pairing is established.

[0126] 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 characteristics (such as periodicity and offset in the case of periodic RS), or a combination of these pre-configurations and activation / deactivation (in the case of semi-persistent RS).

[0127] The following embodiments are examples of DL multi-beam operation, which utilizes DL beam indication after the network (NW) receives some transmissions from the UE. In a first exemplary embodiment, aperiodic CSI-RS is transmitted by the NW and measured by the UE. Although aperiodic RS is used in these two examples, periodic or semi-persistent RS can also be used.

[0128] For mmWave (or FR2) or higher frequency bands (such as >52.6 GHz or FR4) particularly relevant to multi-beam operation, 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). Once the UL RS is received and measured, the gNB selects the UL RX beam. As a result, the TX-RX beam pair is derived. The NW / gNB can do this 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 (involving maintaining DL-UL beam correspondence or reciprocity), the NW / gNB sends the RS to the UE (for UL and through 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 the TX-RX beam pair for each configured (DL) reference RS. Therefore, although this knowledge is not available to the NW / gNB, once the UE receives the reference RS (and thus the UL RX beam) indication from the NW / gNB, it can select the UL TX beam from the knowledge of all TX-RX beam pairs.

[0129] In this disclosure, the term "resource indicator," also abbreviated as REI, 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 ​​may also be used for signal / channel and / or interference measurements, such as DMRS.

[0130] exist Figure 10 One example shown illustrates the UL Multibeam Operation 1000. Figure 10 The embodiment of the UL multi-beam operation 1000 shown 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.

[0131] UL multi-beam operation 1000 begins with the gNB / NW sending an aperiodic CSI-RS (AP-CSI-RS) trigger or indication to the UE signal (step 1001). This trigger or indication may be included in the DCI (UL-related or DL-related, sent alone or in conjunction with an aperiodic CSI request / trigger) and indicates that the AP-CSI-RS be sent in the same (zero time offset) or later time slot / subframe (>0 time offset). Once the AP-CSI-RS sent by the gNB / NW is received (step 1002), the UE measures the AP-CSI-RS, then calculates and reports the "beam metric" (indicating the quality of a specific TX beam assumption) (step 1003). An example of this beam report is a CSI-RS Resource Indicator (CRI) or an SSB Resource Indicator (SSB-RI), which is coupled to its associated L1-RSRP / L1-RSRQ / L1-SINR / CQI. Once the beam report is received from the UE, the NW can use the beam report to select a UL TX beam for the UE and 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 the NR) (step 1004). The SRI corresponds to the “target” SRS resource linked to the reference RS (AP-CSI-RS in this example) via SpatialRelationInfo configuration. Once the UL-related DCI is successfully decoded 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).

[0132] exist Figure 11 Another example shown illustrates the UL Multibeam Operation 1100. Figure 11 The embodiment of the UL multi-beam operation 1100 shown 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.

[0133] UL multi-beam operation 1100 begins with the gNB / NW sending an aperiodic SRS (AP-SRS) trigger or request to the UE signal (step 1101). This trigger can be included in the DCI (UL-related or DL-related). Once the AP-SRS trigger is received and decoded (step 1102), the UE sends the AP-SRS to the gNB / NW (step 1103) so that the NW (or gNB) can measure the UL propagation channel and select the 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 (AP-SRS in this example) via SpatialRelationInfo. Once the UL-related DCI is successfully decoded 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).

[0134] exist Figure 12 Another example shown illustrates the DL multi-beam operation 1200. Figure 12 The embodiment of DL multi-beam operation 1200 shown is for illustrative purposes only. Figure 12 This disclosure is not intended to limit the scope of any particular implementation of the DL multi-beam operation 1200.

[0135] 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 an aperiodic CSI-RS (AP-CSI-RS) trigger or indication to the UE (step 1201). This trigger or indication may be included in the DCI (UL-related or DL-related, signaled individually or in conjunction with an aperiodic CSI request / trigger) and indicate that the AP-CSI-RS should be transmitted in the same (zero time offset) or later time slot / subframe (>0 time offset). Once the AP-CSI-RS transmitted by the gNB / NW is received (step 1202), the UE measures the AP-CSI-RS, 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 this beam report (supported in the 3GPP NR specification) is a CSI-RS resource indicator (CRI) or SSB resource indicator (SSB-RI) coupled to its associated L1-RSRP / L1-RSRQ / L1-SINR. Once the 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 (bearer DL allocation, such as DCI format 1_1 in NR) (step 1204). The TCI state corresponds to a reference RS (in this example, AP-CSI-RS) defined / configured via the TCI state definition (configured by higher layers / RRC, from which a subset is activated via MAC CE for DCI-based selection). Once the DL-related DCI is successfully decoded using the TCI field, the UE performs DL reception (such as data transmission on the PDSCH) using the DL TX beam associated with the TCI field (step 1205). In this exemplary embodiment, only one DL TX beam is indicated to the UE.

[0136] To facilitate rapid beam management, one requirement is to simplify the basic components (building blocks) of beam management. One function of beam management is beam selection, which includes various functions such as beam measurement (including training), reporting (for DL ​​beam management, reported via (multiple) UL control channels), and indication (for DL ​​and UL beam management, indicated via (multiple) DL control channels). Once the building blocks are simplified [Step 1], additional advanced functions can be added to facilitate faster beam management [Step 2].

[0137] U.S. Patent Application No. 16 / 949,246, filed October 21, 2020 (the disclosure of which is incorporated herein by reference), proposes a streamlined “slender pattern” for such a basic component for fast beam management. Due to its compact nature, this streamlined pattern design can facilitate faster updates / reconfigurations via lower-level control signaling. In other words, L1 control signaling will be the primary signaling mechanism, with higher layers (such as MAC CE or RRC) used only when necessary. Here, L1 control signaling includes the use of UE group DCI as well as dedicated (UE-specific) DCI.

[0138] The aforementioned additional advanced features can include beam management (multi-beam operation) extensions from intra-cell to inter-cell mobility. Using this mechanism, seamless access / mobility for RRC_CONNECTED UEs can be achieved as if no cell boundary were observed unless the UE was in initial access or similar conditions. Another advanced feature includes mechanisms to minimize beam faults (BF) or radio link faults (RLF), such as low-overhead, faster beam switching / selection and UE-initiated / event-triggered beam management. Given these preventative mechanisms, beam fault recovery (BFR) is less likely to be used.

[0139] In this disclosure, a signaling mechanism for implementing the aforementioned fast (dynamic) multi-beam operation is considered. Specifically, the 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).

[0140] In the remainder of this disclosure, the term "beam" may be associated with 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 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 spatial reception of resource signals (RS) or channels from a "port," "antenna port," or "virtual antenna / port." Spatial transmission / reception of beams can occur in three-dimensional (3D) space. In beamforming wireless systems, wireless signals can be transmitted and received using multiple TX and multiple RX beams.

[0141] In this disclosure, dynamic, L1-controlled, or DCI-based common beam indication mechanisms are considered. For illustrative purposes, the following symbols / terms are used in this disclosure. Other terms may also be used to denote the same functions and operations:

[0142] The DCI that indicates the common beam used for data (PDSCH / PUSCH) and control (PDCCH / PUCCH) for both DL and UL is called TCI-DCI (for example, used when maintaining beam correspondence between DL and UL).

[0143] The DCI that indicates the common beam used for data (PDSCH) and control (PDCCH) in DL is called DL-TCI-DCI.

[0144] • The DCI that indicates the common beam used for UL's data (PUSCH) and control (PUCCH) is called UL-TCI-DCI.

[0145] The DCI allocated by the scheduling DL is called the DL-DCI, and

[0146] • The dispatching of a UL-authorized DCI is called a UL-DCI.

[0147] In U.S. Patent Application No. 17 / 214,738, filed March 26, 2021 (the disclosure of which is incorporated herein by reference), a common beam indication of DL data (PDSCH) and DL control (PDCCH) via DL-TCI-DCI is proposed. Figure 13 The image shows an example of a dedicated DCI indicating a common beam for receiving DL control and data 1300. Figure 13 The embodiment shown, which is an example of a dedicated DCI for receiving the common beam of DL control and data 1300, is for illustrative purposes only. Figure 13 This disclosure is not intended to limit the scope to any particular implementation of an example of a dedicated DCI for receiving DL control and data 1300.

[0148] like Figure 13As 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 uses the indicated beam (TCI state) to receive DL control (PDCCH) starting in the same time slot (time slot N) or later (multiple) time slots(s). For illustrative purposes, it is assumed that X is the gap (in terms of the number of time slots / subframes) between the time slot carrying the DL-TCI-DCI and the time slot carrying the DL control; the UE receives DL control starting in time slot N+X. The UE decodes the DL-DCI (e.g., in DL-DCI format) contained in the PDCCH to obtain scheduling information for DL ​​allocation. The UE then receives DL data (PDSCH, allocated according to DL) in time slot N+X+K0 using the indicated beam (TCI state). 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 (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 for signal transmission DL-TCI-DCI can be different from the time unit location used for signal transmission DL-DCI.

[0149] In U.S. Patent Application No. 17 / 222,592, filed April 5, 2021 (the disclosure of which is incorporated herein by reference), a common beam indication (via UL-TCI-DCI) for UL data (PUSCH) and UL control (PUCCH) is proposed. Figure 14 The image shows an example of a dedicated DCI that indicates the common beam used to transmit UL control and data 1400. Figure 14 The example shown is for illustration only and is intended to indicate a dedicated DCI for transmitting UL control and data 1400 via a common beam. Figure 14 This disclosure is not intended to limit the scope to any particular implementation of an example of a dedicated DCI used to transmit UL control and data 1400.

[0150] like Figure 14As shown, the UE is configured to receive a dedicated DCI (UL-TCI-DCI), which indicates 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., in UL-TCI-DCI format) and decodes the UL-TCI-DCI in time slot (or subframe) N′, and receives DL control (PDCCH) starting in the same time slot (time slot N′) or later (multiple) time slots using the indicated beam (TCI state) or another TCI state (beam). For illustrative purposes, it is assumed that X′ is the gap between the time slot carrying DL-TCI-DCI and the time slot carrying DL control (in the number of time slots / subframes), then the UE receives DL control starting in time slot N′+X′. The UE decodes the UL-DCI (e.g., UL-DCI format) contained in the PDCCH 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′+K′0 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 for signal transmission of the UL-TCI-DCI can be different from the time unit location used for signal transmission of the UL-DCI.

[0151] In U.S. Patent Application No. 17 / 222,592, filed April 5, 2021, cited above, a common beam indication (via TCI-DCI) is proposed for both DL and UL, as well as for both data and control. Figure 15 An example of a dedicated DCI that indicates the common beam for all DL and UL channels 1500 is shown. Figure 15 The example shown, indicating a dedicated DCI for the common beam of all DL and UL channels 1500, is for illustrative purposes only. Figure 15 This disclosure is not intended to limit the scope to any particular implementation of a dedicated DCI that indicates a common beam for all DL and UL channels 1500.

[0152] like Figure 15As shown, 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 receiving DL control (PDCCH) and DL data (PDSCH) and transmitting UL control (PUCCH) and UL 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 (see Example I.7). The UE receives (e.g., in TCI-DCI format) and decodes the TCI-DCI in time slot (or subframe) N, and uses the indicated beam (TCI state) or another TCI state (beam) to receive scheduled DL allocations (via DL-DCI) and / or UL-authorized DL control (PDCCH) starting in the same time slot (time slot N) or later (multiple) time slots.

[0153] For DL, assuming X is the gap (in terms of the number of time slots / subframes) between the time slot carrying TCI-DCI and the time slot carrying DL control (via DL-DCI) for scheduling allocation, the UE receives DL control starting 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 ​​allocation. The UE then uses the indicated beam (TCI state) in time slot N+X+K. o DL data (PDSCH, allocated according to DL) is received. 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 DL-DCI), 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 for signal transmission TCI-DCI can be different from the time unit position used for signal transmission DL-DCI.

[0154] For UL, assuming X′ is the gap (in terms of the number of time slots / subframes) between the time slot carrying TCI-DCI and the time slot carrying DL control carrying UL authorization (via UL-DCI), the UE receives DL control starting in time slot N′+X′. The UE decodes the UL-DCI (e.g., UL-DCI format) contained in the PDCCH 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′+K′0 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 position (e.g., time slot, subframe) used for signal transmission of TCI-DCI can be different from the time unit position used for signal transmission of UL-DCI.

[0155] Component 1: DL beam indicator DCI content

[0156] In some embodiments of this disclosure, the UE may be configured with a dynamic beam (TCI state) indication / update for DL ​​reception, either separately from or together with the DL allocation, wherein the TCI state indication is via DL-TCI-DCI and / or DL ​​allocation (DL-DCI), and details regarding DL-TCI-DCI are based on U.S. Patent Application No. 17 / 214,738, filed March 26, 2021, cited above. Specifically, DL-TCI-DCI may be used / configured to enable the possibility of updating / indicating the TCI state separately from the DL allocation. When the beam indication is separate from the DL allocation, the indicated beam can be used to receive DL control (e.g., the PDCCH carrying the DL-DCI that schedules the DL allocation) and DL data (PDSCH). This is referred to in this disclosure as a "common beam (TCI state) indication." When the beam indication is together with the DL allocation, the indicated beam can only be used to receive DL data (PDSCH). In this case, the beam used to receive DL control can be another beam (TCI state), as explained in U.S. Patent Application No. 17 / 214,738, filed March 26, 2021, cited above.

[0157] At least one of the following embodiments can be used. In one alternative, only one embodiment of the following embodiments is used for beam (TCI state) indication. In another alternative, multiple embodiments of the following embodiments can be used for beam (TCI state) indication, one of which is configured to the UE via higher-layer (RRC) and / or MAC CE-based and / or DCI-based signaling. In the following embodiments or examples, beam position (TCI state) indication refers to carrier DCI, such as DL-TCI-DCI or DL-DCI.

[0158] In Example I.1, the common beam (TCI state) indication is always via DL-TCI-DCI, not via DL-DCI (scheduling DL allocation). There is only one beam indication, whose position (or carrier DCI) is fixed at DL-TCI-DCI.

[0159] In Example I.1A, the common beam (TCI state) indication is always via the MAC CE (carried via the PDSCH, which is scheduled via the DCI), and not via DL-TCI-DCI or DL-DCI (scheduled DL allocation). There is only one beam indication, the location (or carrier channel) of which is fixed to the PDSCH carrying the MAC CE. In one example, the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In another example, the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS.

[0160] In Example I.2, the common beam (TCI state) indication can be via DL-TCI-DCI or DL-DCI (scheduling DL allocation). Only one beam indication, whose location (or carrier DCI) is configured to the UE, is used. This configuration can be via RRC and / or MACCE. At least one of the following examples can be used.

[0161] In Example I.2.1, the position of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is configured via DL-TCI-DCI, and when parameter P takes another value (e.g., P = 1 or P > 0), the beam indicator is configured via DL-DCI. Parameter P can be configured via fields in DL-TCI-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via DL-TCI-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0162] In Example I.2.2, the location of the common beam indication is configured via field F in the DL-TCI-DCI. When field F takes one value (e.g., F = 0), the beam indication is via the DL-DCI, and when the field value is another value (e.g., F > 0), the beam indication is via the DL-TCI-DCI. In one example, when F > 0, the value of F indicates both: (a) information: the beam indication is via the DL-TCI-DCI, and (b) the update beam (TCI status) used for both data and control.

[0163] In one example, I.2.3, the location of the common beam indication is configured via an RRC parameter such as tci-PresentInDCI (in PDSCH-Config) or a MAC CE parameter. For example, when the parameter is provided, the common beam indication is via DL-TCI-DCI; otherwise, it is via DL-TCI.

[0164] In Example I.2A, the common beam (TCI state) indication can be via X-DCI or MAC CE, where X = DL or DL-TCI, and MAC CE is carried via PDSCH, which is scheduled via DCI. Only one beam indication is provided, and its location (or carrier channel) is configured for the UE. This configuration can be via RRC and / or MAC CE. In one example (E1), the beam indication is a single beam (TCI state) indicating both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When the beam indication is via X-DCI, a subset of up to N (e.g., N = 8) beams can be activated via MAC CE (similar to Rel. 15), which maps to up to N code points in the DCI field of X-DCI. When the beam indication is via MAC CE, a single beam, i.e., N = 1 (or two beams, in the case of Example E2), is indicated. Please note that N here is the number of TCI states in the activated TCI state set. At least one of the following examples can be used.

[0165] In an example I.2A.1, the position of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is via X-DCI, and when parameter P takes another value (e.g., P = 1 or P > 0), the beam indicator is via MACCE. This parameter P can be configured via a field in X-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via X-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0166] In Example I.2A.2, the location of the common beam indicator is configured via field F in the X-DCI. When field F takes one value (e.g., F = 0), the beam indicator is via the MAC CE, and when the field value is another value (e.g., F > 0), the beam indicator is via the X-DCI. In one example, when F > 0, the value of F indicates one of the following: (a) information: the beam indicator is via the X-DCI, and (b) the update beam (TCI state) used for both data and control.

[0167] In an example I.2A.3, the location of the common beam indication is configured via an RRC parameter such as tci-PresentInDCI (in PDSCH-Config). When the RRC parameter is provided, the common beam indication is via X-DCI; otherwise, it is via MAC CE.

[0168] In Embodiment I.2B, a variation of Embodiment I.2A, the common beam (TCI state) indication is conditionally based and can be via X-DCI or MAC CE, where X = DL or DL-TCI. In one example, the condition is based on the value of N (the number of activated TCI states). Use / configure at least one of the following examples.

[0169] In one example I.2B.1, if N=1, the common beam indication is via MAC C, and if N>1, the common beam indication is via X-DCI. In one example, the value of N is explicitly configured, for example, via RRC and / or MAC CE (or the condition N=1 or N>1). In another example, the value of N is implicitly configured, for example, via RRC and / or MAC CE, such as in the example of embodiment I.2A.

[0170] Optionally, if N=1, the common beam indication is via X-DCI, and if N>1, the common beam indication is via MAC CE. In one example, the value of N is explicitly configured, for example, via RRC and / or MAC CE (or the condition N=1 or N>1). In another example, the value of N is implicitly configured, for example, via RRC and / or MAC CE, such as in the example of Embodiment I.2A.

[0171] In an example I.2B.2, if N ≤ t (or N < t), the common beam indication is via MAC CE, and if N > t (or N ≥ t), the common beam indication is via X-DCI. The value of t can be fixed, for example, t = 1, 2, 4, or 8. Alternatively, the value of t can be configured, for example, via RRC and / or MAC CE. After configuration, the set of candidate values ​​for t can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0172] In one example, the values ​​of N and / or t (or the condition N ≤ t (or N < t) or N > t (or N ≥ t)) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values ​​of N and / or t (or the condition N ≤ t (or N < t) or N > t (or N ≥ t)) are implicitly configured, for example, via RRC and / or MAC CE, as in the example in Example I.2A.

[0173] In an example I.2B.3, if N ≤ t (or N < t), the common beam indication is via X-DCI, and if N > t (or N ≥ t), the common beam indication is via MAC CE. The value of t can be fixed, for example, t = 1, 2, 4, or 8. Alternatively, the value of t can be configured, for example, via RRC and / or MACE CE. After configuration, the set of candidate values ​​for t can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0174] In one example, the values ​​of N and / or t (or the condition N ≤ t (or N < t) or N > t (or N ≥ t)) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values ​​of N and / or t (or the condition N ≤ t (or N < t) or N > t (or N ≥ t)) are implicitly configured, for example, via RRC and / or MAC CE, as in the example in Example I.2A.

[0175] In Embodiment I.2C, a variation of Embodiments I.2A and I.2B, the common beam (TCI state) indication is conditionally based and can be via X-DCI or MAC CE, where X = DL or DL-TCI. In one example, this condition is based on the values ​​of N (the number of activated TCI states for DL) and M (the number of activated TCI states for UL), assuming that the set of activated TCI states is different for DL ​​and UL. Use / configure at least one of the following examples.

[0176] In one example I.2C.1, if N = M = 1, the common beam indication is via the MAC CE, and if N > 1 or M > 1, the common beam indication is via the X-DCI. In one example, the values ​​of N and / or M are explicitly configured, for example, via the RRC and / or MAC CE (or the condition N = M = 1 or N > 1 or M > 1). In another example, the values ​​of N and / or M are implicitly configured, for example, via the RRC and / or MAC CE, as in the example in embodiment I.2A.

[0177] Optionally, if N = M = 1, the common beam indication is via X-DCI, and if N > 1 or M > 1, the common beam indication is via MAC CE. In one example, the value of N is explicitly configured, for example, via RRC and / or MAC CE (or the condition N = 1 or N > 1). In another example, the value of N is implicitly configured, for example, via RRC and / or MAC CE, such as the example in Example I.2A.

[0178] In an example I.2C.2, if N ≤ t and M ≤ Y (or N < t and M < Y), the common beam indication is via MAC CE; otherwise, the common beam indication is via X-DCI. The values ​​of t and / or Y can be fixed, for example, t, Y = 1, 2, 4, or 8. Alternatively, the values ​​of t and / or Y can be configured, for example, via RRC and / or MACE CE. After configuration, the set of candidate values ​​for t and / or Y can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0179] In one example, the values ​​of N and / or t and / or M and / or Y (or conditions such as N≤t and M≤Y) are explicitly configured via RRC and / or MAC CE. In another example, the values ​​of N and / or t and / or M and / or Y (or conditions such as N≤t and M≤Y) are implicitly configured via RRC and / or MAC CE, such as the example in Example I.2A.

[0180] In an example I.2C.3, if N ≤ t and M ≤ Y (or N < t and M < Y), the common beam indication is via X-DCI; otherwise, the common beam indication is via MAC CE. The values ​​of t and / or Y can be fixed, for example, t, Y = 1, 2, 4, or 8. Alternatively, the values ​​of t and / or Y can be configured, for example, via RRC and / or MAC CE. After configuration, the set of candidate values ​​for t and / or Y can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0181] In one example, the values ​​of N and / or t and / or M and / or Y (or conditions such as N≤t and M≤Y) are explicitly configured via RRC and / or MAC CE. In another example, the values ​​of N and / or t and / or M and / or Y (or conditions such as N≤t and M≤Y) are implicitly configured via RRC and / or MAC CE, such as the example in Example I.2A.

[0182] In an example I.2C.4, if N+M≤t (or N+M<t), the common beam indication is via MAC CE, and if N+M>t (or N+M≥t), the common beam indication is via X-DCI. The value of t can be fixed, for example, t, Y = 2, 4, or 8. Alternatively, the value of t and / or Y can be configured, for example, via RRC and / or MACE CE. After configuration, the set of candidate values for t and / or Y can be {2, 4} or {2, 8}, {2, 3} or {2, 4, 6} or {2, 4, 6, 8}.

[0183] In one example, the values of N and / or t and / or M (or the condition such as N+M≤t, etc.) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or t and / or M (or the condition such as N+M≤t, etc.) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.2A.

[0184] In an example I.2C.5, if N+M≤t (or N+M<t), the common beam indication is via X-DCI, and if N+M>t (or N+M≥t), the common beam indication is via MAC CE. The value of t can be fixed, for example, t, Y = 2, 4, or 8. Alternatively, the value of t and / or Y can be configured, for example, via RRC and / or MACE CE. After configuration, the set of candidate values for t and / or Y can be {2, 4} or {2, 8}, {2, 3} or {2, 4, 6} or {2, 4, 6, 8}.

[0185] In one example, the values of N and / or t and / or M (or the condition such as N+M≤t, etc.) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or t and / or M (or the condition such as N+M≤t, etc.) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.2A.

[0186] In an example I.2C.6, if max(N, M)≤t (or max(N, M)<t), the common beam indication is via MACCE, and if max(N, M)>t (or max(N, M)≥t), the common beam indication is via X-DCI. The value of t can be fixed, for example, t, Y = 2, 4, or 8. Alternatively, the value of t and / or Y can be configured, for example, via RRC and / or MACE CE. After configuration, the set of candidate values for t and / or Y can be {2, 4} or {2, 8}, {2, 3} or {2, 4, 6} or {2, 4, 6, 8}.

[0187] In one example, the values of N and / or t and / or M (or conditions such as max(N, M) ≤ t, etc.) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or t and / or M (or conditions such as max(N, M) ≤ t, etc.) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.2A.

[0188] In one example I.2C.7, if max(N, M) ≤ t (or max(N, M) < t), the common beam indication is via X-DCI, and if max(N, M) > t (or max(N, M) ≥ t), the common beam indication is via MAC CE. The value of t can be fixed, for example, t, Y = 2, 4, or 8. Alternatively, the values of t and / or Y can be configured, for example, via RRC and / or MAC CE. After configuration, the set of candidate values for t and / or Y can be {2, 4} or {2, 8}, {2, 3} or {2, 4, 6} or {2, 4, 6, 8}.

[0189] In one example, the values of N and / or t and / or M (or conditions such as max(N, M) ≤ t, etc.) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or t and / or M (or conditions such as max(N, M) ≤ t, etc.) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.2A.

[0190] In Embodiment I.3, the common beam (TCI state) indication can be via both DL-TCI-DCI and DL-DCI (scheduling DL assignment). There are two types of beam indications, one via DL-TCI-DCI and the other via DL-DCI. In one example, the higher layer parameter tci-PresentInDCI (in PDSCH-Config) is set to "enabled", which indicates that the TCI state is indicated via DL-DCI (in addition to the beam indication via DL-TCI-DCI). In another example, the MAC CE signaling enables / disables the TCI state indication via DL-DCI (in addition to the beam indication via DL-TCI-DCI). At least one of the following examples can be used.

[0191] In one example I.3.1, the TCI state for receiving DL control (e.g., PDCCH carrying DL-DCI) can be the TCI state indicated via DL-TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be the TCI state indicated via DL-DCI.

[0192] In an example I.3.2, the TCI state for receiving DL control (e.g., PDCCH carrying DL-DCI) can be the TCI state indicated via DL-TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be the latest TCI state indicated via DL-TCI-DCI or DL-DCI.

[0193] In Example I.3A, the common beam (TCI state) indication can be via both X-DCI and MAC CE, where X = DL or DL-TCI, and MAC CE is carried via PDSCH, which is scheduled via DCI. There are two beam indications, one via X-DCI and the other via MAC CE. In one example, the higher-layer parameter tci-PresentInDCI (in PDSCH-Config) is set to "enabled," indicating that the TCI state is indicated via X-DCI (in addition to the beam indication via MAC CE). In another example, MAC CE signaling enables / disables the TCI state indication via X-DCI (in addition to the beam indication via MAC CE). In one example (E1), the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When beam indication is via X-DCI, a subset of up to N (e.g., N=8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to N code points of the DCI field in X-DCI. When beam indication is via MAC CE, a single beam (or two beams, in the case of example E2) is indicated. At least one of the following examples can be used.

[0194] In an example I.3A.1, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI) can be a TCI state indicated via MAC CE, and the TCI state for receiving DL data (PDSCH) can be a TCI state indicated via X-DCI.

[0195] In an example I.3A.2, the TCI state for receiving DL control (e.g., PDCCH carrying DL-DCI) can be the TCI state indicated via MAC CE, and the TCI state for receiving DL data (PDSCH) can be the latest TCI state indicated via MAC CE or X-DCI.

[0196] In an example I.3A.3, the TCI state used to receive DL control (e.g., PDCCH carrying DL-DCI) and DL data (PDSCH) can be the latest TCI state indicated via MAC CE or X-DCI.

[0197] In Example I.4, the common beam (TCI state) indication can be via one or both of DL-TCI-DCI and DL-DCI. At least one of the following examples can be used.

[0198] In one example, I.4.1, the common beam (TCI state) indication can be via one of two states: (a) only DL-TCI-DCI or (b) both DL-TCI-DCI and DL-DCI. In one option, one of the two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, DL-TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.3. In one example, DL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of the two states is configured by two RRC parameters, for example, setting tci-dci-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (in PDSCH-Config). In another example, one of the two states is configured using a single RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0199] In one example, I.4.2, the common beam (TCI state) indication can be via one of two states: (a) DL-DCI only or (b) both DL-TCI-DCI and DL-DCI. In one option, one of the two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, DL-TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.3. In one example, DL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of the two states is configured by two RRC parameters, for example, setting tci-PresentInDCI (in PDSCH-Config) = 'enabled' and enabling / disabling tci-dci-IsPresent. In another example, one of the two states is configured using a single RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0200] In one example, I.4.3, the common beam (TCI state) indication can be via one of three states: (a) DL-TCI-DCI only, (b) DL-DCI only, or (c) both DL-TCI-DCI and DL-DCI. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, DL-TCI-DCI indicates one of these three states. When the state is configured / indicated as (a) or (b), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication follows embodiment I.3. In one example, DL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of the three states is configured by enabling / disabling two RRC parameters (e.g., tci-dci-IsPresent and tci-PresentInDCI (in PDSCH-Config)). In another example, one of the three states is configured using a single RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0201] In Example I.4A, the common beam (TCI state) indication can be via one or both of X-DCI and MAC CE. In one example (E1), the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When the beam indication is via X-DCI, a subset of up to N (e.g., N=8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to N code points of the DCI field in X-DCI. When the beam indication is via MAC CE, a single beam (or two beams, in the case of Example E2) is indicated. At least one of the following examples can be used.

[0202] In one example I.4A.1, the common beam (TCI state) indication can be via one of two states: (a) X-DCI only or (b) both X-DCI and MAC CE. In one option, one of the two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the two states. When the state is configured / indicated as (a), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (b), the common beam indication follows embodiment I.3A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of the two states is configured by two RRC parameters, for example, setting tci-mac-ce-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (in PDSCH-Config). In another example, one of the two states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0203] In one example, I.4A.2, the common beam (TCI state) indication can be via one of two states: (a) MAC CE only or (b) both X-DCI and MAC CE. In one option, one of these two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.3A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of the two states is configured by two RRC parameters, for example, setting tci-mac-ce-IsPresent (in PDSCH-Config) = 'enabled' and enabling / disabling tci-PresentInDCI. In another example, one of the two states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0204] In one example, I.4A.3, the common beam (TCI state) indication can be via one of three states: (a) X-DCI only, (b) MAC CE only, or (c) both X-DCI and MAC CE. In one option, one of the three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the three states. When the state is configured / indicated as (a) or (b), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication follows embodiment I.3A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of these three states is configured by enabling / disabling two RRC parameters (e.g., tci-mac-ce-IsPresent and tci-PresentInDCI (in PDSCH-Config)). In another example, one of these three states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0205] In Example I.5, the DL-TCI-DCI can be a two-level DCI comprising a first-level DCI and a second-level DCI, wherein the first-level DCI always exists (i.e., is configured and therefore can be received by the UE), has a fixed payload, and indicates the presence (i.e., is configured and therefore can be received by the UE) or absence (i.e., is not configured and / or therefore not received) of the second-level DCI. When the second-level DCI does not exist (is not configured and / or is not received), the UE assumes that the TCI state has not been updated. When the second-level DCI exists (is configured and therefore can be received by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used.

[0206] In an example I.5.1, the position of the second-level DCI is fixed as DL-DCI (scheduled DL allocation).

[0207] In an example I.5.2, the position of the second-level DCI is fixed as dedicated (second-level) DL-TCI-DCI.

[0208] In Example I.5.3, the location of the second-level DCI is fixed as either DL-DCI or dedicated (second-level) DL-TCI-DCI. In this case, when the first-level DCI indicates the presence of the second-level DCI (configured to the UE), it also indicates the location of the second-level DCI (via the first-level DCI). For example, when field Y in the first-level DCI is set to 00, the second-level DCI does not exist; when field Y in the first-level DCI is set to 01, the second-level DCI exists and its location is DL-DCI; when field Y in the first-level DCI is set to 10, the second-level DCI exists and its location is (second-level) DL-TCI-DCI.

[0209] In Embodiment I.5AA, the common beam indication can be a two-level indication including a first-level indication and a second-level indication, wherein the first-level indication always exists (i.e., is configured and therefore can be received by the UE), has a fixed payload, and indicates the presence (i.e., is configured and therefore can be received by the UE) or absence (i.e., is not configured and / or therefore not received) of the second-level indication. When the second-level indication does not exist (is not configured and / or is not received), the UE assumes that the TCI state has not been updated. When the second-level indication exists (is configured and therefore can be received by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used. In one example, the first-level indication is via MAC CE, and the second-level indication is via X-DCI.

[0210] In an example I.5AA.1, the first-level indication is via MAC CE, and the position of the second-level indication is fixed at X-DCI, where X = DL or DL-TCI-DCI.

[0211] In an example I.5AA.2, the first-level indication is via the first-level MAC CE, and the position of the second-level indication is fixed at the second-level MAC CE.

[0212] In an example I.5AA.3, the first-level indication is via X-DCI, where X = DL or DL-TCI-DCI, and the position of the second-level indication is fixed at MAC CE.

[0213] In Example I.5AA.4, the first-level indication is via MAC CE, and the location of the second-level DCI can be either X-DCI or MAC CE. In this case, when the first-level indication indicates the presence of the second-level indication (configured to the UE), it also indicates the location of the second-level indication (via the first-level indication). For example, when field Y in the first-level indication is set to 00, the second-level indication does not exist; when field Y in the first-level indication is set to 01, the second-level indication exists and its location is X-DCI; when field Y in the first-level indication is set to 10, the second-level indication exists and its location is (second-level) MAC CE.

[0214] In one embodiment I.5A, the common beam (TCI state) indication can be via one or both of DL-TCI-DCI and DL-DCI. At least one of the following examples can be used.

[0215] In an example I.5A.1, the common beam (TCI state) indication is based on two RRC parameters, such as tci-dci-IsPresent and tci-PresentInDCI, as shown below. When tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0216] • When the time threshold is met, the TCI status of DL control reception is transmitted via DL-TCI-DCI, and the TCI status of DL data reception is transmitted via DL-DCI.

[0217] • When the time threshold is not met, the TCI status of both DL data and DL control is received via DL-TCI-DCI.

[0218] When tci-dci-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI status of both DL data and DL control is received via DL-TCI-DCI.

[0219] In an example I.5A.2, the common beam (TCI state) indication is via both DL-TCI-DCI and DL-DCI. Specifically, TCI state 1 is indicated via DL-TCI-DCI, and TCI state 2 is indicated via DL-DCI (e.g., by setting tci-PresentInDCI=enabled). The TCI state received by DL control is then the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state received by DL control is either TCI state 1 or TCI state 2, or the latest of the TCI states indicated via MAC CE. The TCI state received by DL data is TCI state 2.

[0220] In an example I.5A.3, the common beam (TCI state) indication is via both DL-TCI-DCI and DL-DCI. Specifically, TCI state 1 is indicated via DL-TCI-DCI, and TCI state 2 is indicated via DL-DCI (e.g., by setting tci-PresentInDCI=enabled). The TCI state of both DL data and DL control reception is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state of both DL data and DL control reception is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE, subject to a fixed timeline constraint.

[0221] In Example I.5AAA, the common beam (TCI state) indication can be via one or both of X-DCI and MAC CE. At least one of the following examples can be used.

[0222] In an example I.5AAA.1, the common beam (TCI state) indication is based on two RRC parameters, such as tci-mac-ce-IsPresent and tci-PresentInDCI, as shown below. When tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0223] • When the time threshold is met, the TCI status received by DL control is transmitted via MAC CE, and the TCI status received by DL data is transmitted via X-DCI.

[0224] • When the time threshold is not met, the TCI status of both DL data and DL control reception is transmitted via MAC CE.

[0225] When tci-mac-ce-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI status of both DL data and DL control reception is transmitted via MAC CE. When tci-PresentInDCI=enabled and tci-mac-ce-IsPresent is not provided, the TCI status of both DL data and DL control reception is transmitted via X-DCI.

[0226] In an example I.5AAA.2, the common beam (TCI state) indication is via both X-DCI and MAC CE. Specifically, TCI state 1 is indicated via MAC CE, and TCI state 2 is indicated via X-DCI (e.g., by setting tci-PresentInDCI=enabled). Subsequently, the TCI state of DL control reception is the latest of TCI state 1 and TCI state 2. The TCI state of DL data reception is TCI state 2. Alternatively, the TCI states of both DL control and data reception are the latest of TCI state 1 and TCI state 2.

[0227] In an example I.5AAA.3, the common beam (TCI state) indication is via both X-DCI and MAC CE. Specifically, TCI state 1 is indicated via MAC CE, and TCI state 2 is indicated via X-DCI (e.g., by setting tci-PresentInDCI=enabled). The TCI state of both DL data and DL control reception is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state of both DL data and DL control reception is the latest of either TCI state 1 or TCI state 2, subject to a fixed timeline constraint.

[0228] In Example I.5B, the common beam (TCI state) indication can be via one or more of DL-TCI-DCI, DL-DCI, or PDSCH. In one example, the PDSCH can carry MAC CE parameters (or activation commands or bitmaps) for the common beam indication, where the MAC CE parameters are included in the MAC control message, the UE is configured to receive the MAC control message via the MAC CE PDSCH, and can receive such configuration via the DCI in the PDCCH. Furthermore, the MAC CE PDSCH can be dedicated to the MAC control message (without any DL data), or it can be a PDSCH multiplexed with both the MAC CE control message and DL data. In one example, the PDSCH can carry the common beam indication multiplexed with DL data (i.e., without any MAC control message). At least one of the following examples can be used.

[0229] In Example I.5B.1, the common beam (TCI state) indication is via both X-DCI and PDSCH, where X = DL or DL-TCI. Specifically, TCI state 1 is indicated via X-DCI, while TCI state 2 is indicated via PDSCH. Subsequently, the TCI state received by DL control is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state received by DL control is the latest of TCI state 1, TCI state 2, or the TCI state indicated via MAC CE. The TCI state received by DL data is TCI state 1. In one example, X is fixed as DL. In one example, X is fixed as DL-TCI. In one example, X is configured via RRC and / or MAC CE. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission.

[0230] In Example I.5B.2, the common beam (TCI state) indication is via all of DL-TCI-DCI, DL-DCI, and PDSCH. Specifically, TCI state 1 is indicated via DL-TCI-DCI, TCI state 2 via DL-TCI, and TCI state 3 via PDSCH. Subsequently, the TCI state received by DL control is the latest state among TCI state 1 and TCI state 2. Alternatively, the TCI state received by DL control is the latest state among TCI state 1, TCI state 3, or the TCI state indicated via MAC CE. The TCI state received by DL data is TCI state 2. Alternatively, the TCI state received by DL data is the latest state among TCI state 1 and TCI state 2. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission.

[0231] In Example I.6, the RRC Information Element (IE) sps-Config can be used to configure a semi-persistent scheduling (SPS) for DL ​​data (PDSCH) for the UE, including a configuration for cs-RNTI (RNTI used to receive the DCI for activating / releasing the SPS). Since the gNB can activate / reactivate / releasing the SPS at any time using a DCI (e.g., DCI format 1_1 or 1_2 in NR), the UE should monitor the PDCCH with a CRC scrambled by the cs-RNTI in each time slot. In the SPS, the UE is configured to receive PDSCH without any DL-TCI (as explained in the dynamic scheduling above). The UE is configured to receive a common beam (TCI state) indication / update, which indicates the common beam used for receiving the PDCCH, and also for receiving the PDSCH if activated by a received PDCCH. This common beam indication can be via a dedicated DCI (DL-TCI-DCI) and / or another DCI for activating / releasing PDSCH reception (depending on the configured SPS). Details regarding the common beam indication are similar to some embodiments of this disclosure (e.g., embodiments I.1 to I.5 / I.5A / I.5B).

[0232] In Example I.6.1, the UE is configured to receive a dedicated DCI (e.g., DL-TCI-DCI) via PDCCH, which includes (a) a field for the common beam (TCI state) and (b) a field for activating / deactivating PDSCH reception (based on the configured SPS). When PDSCH reception is activated by field (b), field (a) can be used to indicate / update a new (TCI state) beam for PDSCH reception (with or without PDCCH reception) for the UE. Once field (b) is deactivated or PDSCH reception is deactivated, field (a) alone can be used to indicate / update a new (TCI state) beam for PDCCH reception for the UE.

[0233] In Example I.6.2, the UE is configured to receive two DCIs: (a) a dedicated DCI (e.g., DL-TCI-DCI) for the common beam (TCI state) and (b) another DCI for activating / deactivating PDSCH reception (based on the configured SPS). These two DCIs can be indicated via two separate PDCCHs or two parts of a PDCCH. In one example, the other DCI may also include beam indication / update (in addition to the beam indication via DL-TCI-DCI).

[0234] Component 2: UL's beam indicator DCI content

[0235] In some embodiments of this disclosure, the UE may be configured with a Dynamic Beaming (TCI) status indication / update for UL transmission, either separately from or together with UL authorization, wherein the TCI status indication is via UL-TCI-DCI and / or UL authorization (UL-DCI), and details regarding UL-TCI-DCI are based on U.S. Patent Application No. 17 / 222,592, filed April 5, 2021, cited above. Specifically, UL-TCI-DCI may be used / configured to enable the possibility of updating / indicating TCI status separately from UL authorization.

[0236] When beam indication is separate from UL authorization (i.e., via UL-TCI-DCI), the UE receives and decodes the UL-TCI-DCI and receives DL control (PDCCH) starting in the same or later timeslot(s) using the indicated beam (TCI state) or another TCI state (beam). The UE decodes the UL-DCI contained in the PDCCH (e.g., UL-DCI format) to obtain scheduling information for UL authorization. The UE then transmits UL control (PUCCH) and / or UL data (PUSCH, according to UL authorization) in the authorized timeslot(s) using the beam (TCI state) indicated in the UL-TCI-DCI. Optionally, a common beam may also be used for PRACH transmission.

[0237] When beam indication is used in conjunction with UL authorization (i.e., via UL-DCI), the indicated beam can only be used to transmit UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH. In this case, the beam used to receive UL-DCI can be another beam (TCI state), as explained in U.S. Patent Application No. 17 / 222,592, filed April 5, 2021, cited above.

[0238] At least one of the following embodiments can be used. In one alternative, only one embodiment of the following embodiments is used for beam (TCI state) indication. In another alternative, multiple embodiments of the following embodiments can be used for beam (TCI state) indication, one of which is configured to the UE via higher layer (RRC) and / or MAC CE-based and / or DCI-based signaling. In the following embodiments or examples, beam position (TCI state) indication refers to carrier DCI, such as UL-TCI-DCI or UL-DCI.

[0239] In Example I.7, the common beam (TCI state) indication is always via UL-TCI-DCI, not via UL-DCI (scheduling UL authorization). There is only one beam indication, whose position (or carrier DCI) is fixed at UL-TCI-DCI.

[0240] In Example I.7A, the common beam (TCI state) indication is always via the MAC CE (beared via the PDSCH, which is scheduled via the DCI), and not via UL-TCI-DCI or UL-DCI (scheduling UL authorization). There is only one beam indication, the location (or carrier channel) of which is fixed to the PDSCH carrying the MAC CE. In one example, the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In another example, the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS.

[0241] In Example I.8, the common beam (TCI state) indication can be via UL-TCI-DCI or UL-DCI (scheduling UL authorization). Only one beam indication is provided to the UE, and its location (or carrier DCI) is configured. At least one of the following examples can be used.

[0242] In Example I.8.1, the location of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is via UL-TCI-DCI, and when parameter P takes another value (e.g., P = 1 or P > 0), the beam indicator is via UL-DCI. Parameter P can be configured via fields in UL-TCI-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via UL-TCI-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0243] In Example I.8.2, the location of the common beam indicator is configured via field F in the UL-TCI-DCI. When field F takes one value (e.g., F = 0), the beam indicator is transmitted via the UL-DCI, and when the field value is another value (e.g., F > 0), the beam indicator is transmitted via the UL-TCI-DCI. In one example, when F > 0, the value of F indicates both: (a) information: the beam indicator is transmitted via the UL-TCI-DCI, and (b) the updated beam (TCI status) used for both data and control.

[0244] In one example, I.8.3, the location of the common beam indicator is configured via an RRC parameter such as tci-PresentInDCI (in PUSCH-Config) or a MAC CE parameter. For example, when the parameter is provided, the common beam indicator is via UL-TCI-DCI; otherwise, it is via UL-TCI.

[0245] In Example I.8A, the common beam (TCI state) indication can be via X-DCI or MAC CE, where X = UL or UL-TCI, and the MAC CE is carried via PDSCH, which is scheduled via DCI. Only one beam indication is provided, and its location (or carrier channel) is configured for the UE. This configuration can be via RRC and / or MAC CE. In one example (E1), the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When the beam indication is via X-DCI, a subset of up to M (e.g., M = 8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to M code points in the DCI field of X-DCI. When the beam indication is via MAC CE, a single beam, i.e., M = 1 (or two beams, in the case of Example E2), is indicated. Please note that M here is the number of TCI states in the activated TCI state set. At least one of the following examples can be used.

[0246] In an example I.8A.1, the location of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is via X-DCI, and when parameter P takes another value (e.g., P = 0 or P > 0), the beam indicator is via MAC CE. Parameter P can be configured via a field in X-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via X-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0247] In Example I.8A.2, the location of the common beam indicator is configured via field F in the X-DCI. When field F takes one value (e.g., F = 0), the beam indicator is via the MAC CE, and when the field value is another value (e.g., F > 0), the beam indicator is via the X-DCI. In one example, when F > 0, the value of F indicates both: (a) information: the beam indicator is via the X-DCI, and (b) the update beam (TCI status) used for both data and control.

[0248] In an example I.8A.3, the location of the common beam indicator is configured via an RRC parameter such as tci-PresentInDCI (in PUSCH-Config). When the RRC parameter is provided, the common beam indicator is via X-DCI; otherwise, it is via MAC CE.

[0249] In Embodiment I.8B, a variation of Embodiment I.2A, the common beam (TCI state) indication is conditionally based and can be via X-DCI or MAC CE, where X = DL or DL-TCI. In one example, the condition is based on the value of M (the number of activated TCI states of the UL). Use / configure at least one of the following examples.

[0250] In one example I.8B.1, if M=1, the common beam indication is via the MAC CE, and if M>1, the common beam indication is via the X-DCI. In one example, the value of M is explicitly configured, for example, via the RRC and / or the MAC CE (or the condition M=1 or M>1). In another example, the value of M is implicitly configured, for example, via the RRC and / or the MAC CE, as in the example of embodiment I.8A.

[0251] In an example I.8B.2, if M ≤ Y (or M < Y), the common beam indication is via MAC CE, and if M > Y (or M ≥ Y), the common beam indication is via X-DCI. The value of Y can be fixed, e.g., Y = 1, 2, 4, or 8. Alternatively, the value of Y can be configured, for example, via RRC and / or MAC CE. After configuration, the set of candidate values of Y can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0252] In one example, the values of M and / or Y (or the condition of M ≤ Y (or M < Y) or M > Y (or M ≥ Y)) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or Y (or the condition of M ≤ Y (or M < Y) or M > Y (or M ≥ Y)) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.8A.

[0253] In an example I.8B.3, if M ≤ Y (or M < Y), the common beam indication is via X-DCI, and if M > Y (or M ≥ Y), the common beam indication is via MAC CE. The value of Y can be fixed, e.g., Y = 1, 2, 4, or 8. Alternatively, the value of Y can be configured, for example, via RRC and / or MAC CE. After configuration, the set of candidate values of Y can be {1, 2} or {1, 4}, {1, 2, 3} or {1, 2, 4} or {1, 2, 3, 4}.

[0254] In one example, the values of M and / or Y (or the condition of M ≤ Y (or M < Y) or M > Y (or M ≥ Y)) are explicitly configured, for example, via RRC and / or MAC CE. In another example, the values of N and / or Y (or the condition of M ≤ Y (or M < Y) or M > Y (or M ≥ Y)) are implicitly configured, for example, via RRC and / or MAC CE, such as the example in Embodiment I.8A.

[0255] In Embodiment I.8C, which is a variant of Embodiments I.8A and I.8B, the common beam (TCI state) indication can be via X-DCI or MAC CE based on a condition, where X = DL or DL-TCI. In one example, the condition is based on the values of N (the number of activated TCI states for DL) and M (the number of activated TCI states for UL), assuming that the set of activated TCI states is different for DL and UL. At least one of Examples I.2C.1 to I.2C.7 is used / configured.

[0256] In Example I.9, the common beam (TCI status) indication can be via both UL-TCI-DCI and UL-DCI (scheduling UL authorization). There are two beam indications, one via UL-TCI-DCI and the other via UL-DCI. In one example, the higher-layer parameter ul-tci-PresentInDCI (e.g., in PUSCH-Config) is set to "enabled," indicating that the TCI status is indicated via UL-DCI (in addition to the beam indication via UL-TCI-DCI). In another example, MAC CE signaling enables / disables the TCI status indication via UL-DCI (in addition to the beam indication via UL-TCI-DCI). At least one of the following examples can be used.

[0257] In an example I.9.1, the TCI state for receiving DL control (e.g., PDCCH carrying UL-DCI) can be a TCI state indicated via UL-TCI-DCI, and the TCI state for transmitting UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH can be a TCI state indicated via UL-DCI.

[0258] In an example I.9.2, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-UCI) can be the TCI state indicated via UL-TCI-DCI, and the TCI state for transmitting UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH can be the latest TCI state indicated via UL-TCI-DCI or UL-DCI.

[0259] In Example I.9A, the common beam (TCI state) indication can be via both X-DCI and MAC CE, where X = UL or UL-TCI, and MAC CE is carried via PDSCH, which is scheduled via DCI. There are two beam indications, one via X-DCI and the other via MAC CE. In one example, the higher-layer parameter tci-PresentInDCI (in PUSCH-Config) is set to "enabled," indicating that the TCI state is indicated via X-DCI (in addition to the beam indication via MAC CE). In another example, MAC CE signaling enables / disables the TCI state indication via X-DCI (in addition to the beam indication via MAC CE). In one example (E1), the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When beam indication is via X-DCI, a subset of up to N (e.g., N=8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to N code points of the DCI field in X-DCI. When beam indication is via MAC CE, a single beam (or two beams, in the case of example E2) is indicated. At least one of the following examples can be used.

[0260] In an example I.9A.1, the TCI state for receiving DL control (e.g., PDCCH carrying UL-DCI) can be a TCI state indicated via MAC CE, and the TCI state for transmitting UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH can be a TCI state indicated via X-DCI.

[0261] In an example I.9A.2, the TCI state for receiving DL control (e.g., PDCCH carrying UL-DCI) can be the TCI state indicated via MAC CE, and the TCI state for transmitting UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH can be the latest TCI state indicated via MAC CE or X-DCI.

[0262] In an example I.9A.3, the TCI status for receiving DL control (e.g., PDCCH carrying UL-DCI) and transmitting UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH can be the latest TCI status indicated via MAC CE or X-DCI.

[0263] In Example I.10, the common beam (TCI state) indication can be via one or both of UL-TCI-DCI and UL-DCI. At least one of the following examples can be used.

[0264] In one example, I.10.1, the common beam (TCI state) indication can be via one of two states: (a) UL-TCI-DCI only or (b) both UL-TCI-DCI and UL-DCI. In one option, one of the two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, UL-TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.9. In one example, UL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of the two states is configured by two RRC parameters, such as setting ul-tci-dci-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (e.g., in PUSCH-Config). In another example, one of the two states is configured using a single RRC parameter, such as ul-tci-dci-IsPresent or tci-PresentInDCI (e.g., in PUSCH-Config).

[0265] In one example, I.10.2, the common beam (TCI state) indication can be via one of two states: (a) UL-DCI only or (b) both UL-TCI-DCI and UL-DCI. In one option, one of the two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, UL-TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.9. In one example, UL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters, such as setting ul-tci-dci-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (e.g., in PUSCH-Config). In another example, one of these two states is configured using a single RRC parameter, such as ul-tci-dci-IsPresent or tci-PresentInDCI (e.g., in PUSCH-Config).

[0266] In one example, I.10.3, the common beam (TCI state) indication can be via one of three states: (a) UL-TCI-DCI only, (b) UL-DCI only, or (c) both UL-TCI-DCI and UL-DCI. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, UL-TCI-DCI indicates one of these three states. When the state is configured / indicated as (a) or (b), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication follows embodiment I.9. In one example, UL-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of these two states is configured by two RRC parameters, such as setting ul-tci-dci-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (e.g., in PUSCH-Config). In another example, one of these two states is configured using a single RRC parameter, such as ul-tci-dci-IsPresent or tci-PresentInDCI (e.g., in PUSCH-Config).

[0267] In Example I.10A, the common beam (TCI state) indication can be via one or both of X-DCI and MAC CE. In one example (E1), the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When the beam indication is via X-DCI, a subset of up to N (e.g., N=8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to N code points of the DCI field in X-DCI. When the beam indication is via MAC CE, a single beam (or two beams, in the case of Example E2) is indicated. At least one of the following examples can be used.

[0268] In one example, I.10A.1, the common beam (TCI state) indication can be via one of two states: (a) X-DCI only or (b) both X-DCI and MAC CE. In one option, one of these two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the two states. When the state is configured / indicated as (a), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (b), the common beam indication follows embodiment I.9A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters, such as setting tci-mac-ce-IsPresent='enabled' and enabling / disabling tci-PresentInDCI (in PUSCH-Config). In another example, one of these two states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PUSCH-Config).

[0269] In one example, I.10A.2, the common beam (TCI state) indication can be via one of two states: (a) MAC CE only or (b) both X-DCI and MAC CE. In one option, one of these two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the two states. When the state is configured / indicated as (a), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (b), the common beam indication follows embodiment I.9A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters, for example, setting tci-mac-ce-IsPresent (in PD=USCH-Config)='enabled' and enabling / disabling tci-PresentInDCI. In another example, one of these two states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PUSCH-Config).

[0270] In one example, I.10A.3, the common beam (TCI state) indication can be via one of three states: (a) X-DCI only, (b) MAC CE only, or (c) both X-DCI and MAC CE. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, X-DCI (or MAC CE) indicates one of the three states. When the state is configured / indicated as (a) or (b), the common beam indication is according to some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication is according to embodiment I.9A. In one example, X-DCI (or MAC CE) includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of these three states is configured by enabling / disabling two RRC parameters (e.g., tci-mac-ce-IsPresent and tci-PresentInDCI (in PUSCH-Config)). In another example, one of these three states is configured using a single RRC parameter, such as tci-mac-ce-IsPresent or tci-PresentInDCI (in PUSCH-Config).

[0271] In Example I.11, the UL-TCI-DCI can be a two-level DCI comprising a first-level DCI and a second-level DCI, wherein the first-level DCI always exists (i.e., is configured and therefore can be received by the UE), has a fixed payload, and indicates the presence (i.e., is configured and therefore can be received by the UE) or absence (i.e., is not configured and / or therefore not received) of the second-level DCI. When the second-level DCI does not exist (is not configured and / or is not received), the UE assumes that the TCI state has not been updated. When the second-level DCI exists (is configured and therefore can be received by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used.

[0272] In an example I.11.1, the position of the second-level DCI is fixed as UL-DCI (Dispatch UL Authorization).

[0273] In an example I.11.2, the position of the second-level DCI is fixed as a dedicated (second-level) UL-TCI-DCI.

[0274] In Example I.11.3, the location of the Level 2 DCI is fixed as UL-DCI or dedicated (Level 2) UL-TCI-DCI. In this case, when the Level 1 DCI indicates the presence of Level 2 (configured to the UE), it also indicates the location of Level 2 DCI (via Level 1 DCI). For example, when field Y in Level 1 DCI is set to 00, Level 2 DCI does not exist; when field Y in Level 1 DCI is set to 01, Level 2 DCI exists and its location is UL-DCI; when field Y in Level 1 DCI is set to 10, Level 2 DCI exists and its location is (Level 2) UL-TCI-DCI.

[0275] In Embodiment I.11AA, the common beam indication can be a two-level indication including a first-level indication and a second-level indication (see U.S. Provisional Patent Application No. 62 / 987,497, filed March 10, 2020), wherein the first-level indication is always present (i.e., configured and therefore receivable by the UE), has a fixed payload, and indicates the presence (i.e., configured and therefore receivable by the UE) or absence (i.e., not configured and / or therefore not receivable) of the second-level indication. When the second-level indication is absent (not configured and / or not receivable), the UE assumes that the TCI state has not been updated. When the second-level indication is present (configured and therefore receivable by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used. In one example, the first-level indication is via MAC CE, and the second-level indication is via X-DCI.

[0276] In an example I.11AA.1, the first-level indication is via MAC CE, and the position of the second-level indication is fixed at X-DCI, where X = UL or UL-TCI-DCI.

[0277] In an example I.11AA.2, the first-level indication is via the first-level MAC CE, and the position of the second-level indication is fixed at the second-level MAC CE.

[0278] In an example I.11AA.3, the first-level indication is via X-DCI, where X = UL or UL-TCI-DCI, and the location of the second-level indication is fixed at MAC CE.

[0279] In Example I.11AA.4, the first-level indication is via MAC CE, and the location of the second-level DCI can be either X-DCI or MAC CE. In this case, when the first-level indication indicates the presence of the second-level indication (configured to the UE), it also indicates the location of the second-level indication (via the first-level indication). For example, when field Y in the first-level indication is set to 00, the second-level indication does not exist; when field Y in the first-level indication is set to 01, the second-level indication exists and its location is X-DCI; when field Y in the first-level indication is set to 10, the second-level indication exists and its location is (second-level) MAC CE.

[0280] In embodiment I.11A, the common beam (TCI state) indication can be via one or both of UL-TCI-DCI and UL-DCI. At least one of the following examples can be used.

[0281] In an example I.11A.1, the common beam (TCI state) indication is based on two RRC parameters, such as ul-tci-dci-IsPresent and tci-PresentInDCI, as shown below. When ul-tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0282] • When the time threshold is met, the TCI status of UL control transmission is transmitted via UL-TCI-DCI, and the TCI status of UL data transmission is transmitted via UL-DCI.

[0283] • When the time threshold is not met, both UL data and UL control transmit their TCI status via UL-TCI-DCI.

[0284] When ul-tci-dci-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI status for both UL data and UL control transmissions is via UL-TCI-DCI. The TCI status for PRACH transmission can be via UL-TCI-DCI or UL-DCI. Alternatively, the TCI status for PRACH transmission can be indicated separately, for example, via MAC CE and / or a separate DCI.

[0285] In an example I.11A.2, the common beam (TCI state) indication is via both UL-TCI-DCI and UL-DCI. Specifically, TCI state 1 is indicated via UL-TCI-DCI, and TCI state 2 is indicated via UL-DCI (e.g., by setting ul-tci-PresentInDCI=enabled). The TCI state transmitted by UL control thereafter is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state transmitted by UL control is the latest of TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE. The TCI state transmitted by UL data is TCI state 2. The TCI state transmitted by PRACH can be the TCI state via UL-TCI-DCI or UL-DCI. Alternatively, the TCI state transmitted by PRACH can be indicated separately, for example, via MAC CE and / or a separate DCI.

[0286] In an example I.11A.3, the common beam (TCI state) indication is via both UL-TCI-DCI and UL-DCI. Specifically, TCI state 1 is indicated via UL-TCI-DCI, and TCI state 2 is indicated via UL-DCI (e.g., by setting ul-tci-PresentInDCI=enabled). The TCI state transmitted by both UL data and UL control is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state transmitted by both UL data and UL control is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE. Alternatively, the TCI state transmitted by both UL data and UL control is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE, subject to a fixed timeline constraint. The TCI state transmitted by PRACH can be the TCI state via either UL-TCI-DCI or UL-DCI. Alternatively, the TCI status sent by PRACH can be indicated separately, for example, via MAC CE and / or DCI alone.

[0287] In Example I.11AAA, the common beam (TCI state) indication can be via one or both of X-DCI and MAC CE. At least one of the following examples can be used.

[0288] In an example I.11AAA.1, the common beam (TCI state) indication is based on two RRC parameters, such as tci-mac-ce-IsPresent and tci-PresentInDCI, as shown below. When tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0289] • When the time threshold is met, the TCI status transmitted by UL control is sent via MAC CE, and the TCI status transmitted by UL data is sent via X-DCI.

[0290] • When the time threshold is not met, both UL data and UL control transmit their TCI status via MAC CE.

[0291] When tci-mac-ce-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI status of both UL data and UL control transmissions is transmitted via MAC CE. When tci-PresentInDCI=enabled and tci-mac-ce-IsPresent is not provided, the TCI status of both UL data and UL control transmissions is transmitted via X-DCI. The TCI status transmitted by PRACH can be the TCI status transmitted via X-DCI or MAC CE. Alternatively, the TCI status transmitted by PRACH can be indicated separately, for example, via MAC CE and / or DCI alone.

[0292] In an example I.11AAA.2, the common beam (TCI state) indication is via both X-DCI and MAC CE. Specifically, TCI state 1 is indicated via MAC CE, and TCI state 2 is indicated via X-DCI (e.g., by setting tci-PresentInDCI=enabled). Subsequently, the TCI state transmitted by UL control is the latest of TCI state 1 and TCI state 2. The TCI state transmitted by UL data is TCI state 2. Alternatively, the TCI states of both UL control and data transmission are the latest of TCI state 1 and TCI state 2.

[0293] In an example I.11AAA.3, the common beam (TCI state) indication is via both X-DCI and MAC CE. Specifically, TCI state 1 is indicated via MAC CE, and TCI state 2 is indicated via X-DCI (e.g., by setting tci-PresentInDCI=enabled). The TCI state for both UL control and data transmission is the most recent of TCI state 1 and TCI state 2. Alternatively, the TCI state for both UL control and data transmission is the most recent of either TCI state 1 or TCI state 2, subject to a fixed timeline constraint.

[0294] In Example I.11B, the common beam (TCI state) indication can be via one or more of UL-TCI-DCI, UL-DCI, or PDSCH. In one example, the PDSCH can carry MAC CE parameters (or activation commands or bitmaps) for the common beam indication, where the MAC CE parameters are included in the MAC control message. The UE is configured to receive the MAC control message via the MAC CE PDSCH, and this configuration can be received via the DCI in the PDCCH. Furthermore, the MAC CE PDSCH can be dedicated solely to the MAC control message (without any DL data), or it can be a PDSCH multiplexed with both the MAC CE control message and DL data. In one example, the PDSCH can carry the common beam indication multiplexed with DL data (i.e., without any MAC control message). At least one of the following examples can be used.

[0295] In Example I.11B.1, the common beam (TCI state) indication is via both X-DCI and PDSCH, where X = UL or UL-TCI. Specifically, TCI state 1 is indicated via X-DCI, while TCI state 2 is indicated via PDSCH. Subsequently, the TCI state transmitted by UL control is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state transmitted by UL control is the latest of TCI state 1, TCI state 2, or the TCI state indicated via MAC CE. The TCI state for UL data transmission is TCI state 1. In one example, X is fixed as UL. In another example, X is fixed as UL-TCI. In yet another example, X is configured via RRC and / or MAC CE. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission. The TCI status transmitted via PRACH can be the TCI status via X-DCI or PDSCH. Alternatively, the TCI status transmitted via PRACH can be indicated separately, for example, via MAC CE and / or separate DCI.

[0296] In an example I.11B.2, the common beam (TCI state) indication is via all of UL-TCI-DCI, UL-DCI, and PDSCH. Specifically, TCI state 1 is indicated via UL-TCI-DCI, TCI state 2 via UL-TCI, and TCI state 3 via PDSCH. Subsequently, the TCI state transmitted by UL control is the latest of either TCI state 1 or TCI state 3. Alternatively, the TCI state transmitted by UL control is the latest of either TCI state 1 or TCI state 3, or the latest of the TCI states indicated via MAC CE. The TCI state transmitted by UL data is TCI state 2. Alternatively, the TCI state transmitted by UL data is the latest of both TCI state 1 and TCI state 2. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission. The TCI status transmitted via PRACH can be the TCI status via UL-TCI-DCI, UL-DCI, or PDSCH. Alternatively, the TCI status transmitted via PRACH can be indicated separately, for example, via MAC CE and / or separate DCI.

[0297] In Example I.12, the UE can be configured with multiple PUSCH transmissions corresponding to a 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` including `rrc-ConfiguredUplinkGrant`, without detecting UL grant in the DCI. Upon receiving a higher-layer parameter `configuredGrantConfig` excluding `rrc-ConfiguredUplinkGrant`, the configured grant type 2 PUSCH transmission is effectively activated by UL grant semi-persistent scheduling (SPS) 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 grant type 2 PUSCH transmission, the UE is configured with `cs-RNTI` (RNTI is used to receive DCI activation / deactivation of SPS). Since the gNB can activate / reactivate / release the SPS at any time using DCI (e.g., DCI format 0_1 ​​or 0_2 in NR), the UE should monitor the PDCCH with a CRC scrambled by cs-RNTI in each time slot.

[0298] The UE can be configured to send (multiple) PUCCH reports corresponding to periodic or semi-persistent CSI reports transmitted on the PUCCH. These PUCCH reports are configured by CSI-ReportConfig without detecting UL authorization in UL-DCI. Semi-persistent CSI reports on the PUCCH can be activated / deactivated by MAC CE.

[0299] The UE can be configured to receive a common beam (TCI status) indication / update, which indicates the common beam for transmitting a configured license type 1 or type 2 PUSCH and / or PUCCH. This common beam indication can be transmitted via a dedicated DCI (UL-TCI-DCI) and / or another DCI (configured license type 2) for activating / deactivating the PUSCH. Details regarding this common beam indication are similar to some embodiments of this disclosure (e.g., embodiments I.7 to I.11 / I.11A / I.11B).

[0300] In Example I.12.1, the UE is configured to receive a dedicated DCI (e.g., UL-TCI-DCI) via the PDCCH, which includes (a) a field for the common beam (TCI state) and (b) another field for activating / releasing PUSCH transmission (for configured license type 2 PUSCH transmission). When PUSCH transmission is activated by field (b), field (a) can be used to indicate / update a new (TCI state) beam for PUSCH transmission (with or without PUSCH transmission) for the UE. Once field (b) is deactivated or PUSCH transmission is released, field (a) alone can be used to indicate / update a new (TCI state) beam for PUSCH transmission for the UE.

[0301] In Example I.12.2, the UE is configured to receive two DCIs: (a) a dedicated DCI for the common beam (TCI state) (e.g., UL-TCI-DCI) and (b) another DCI for activating / deactivating PUSCH transmission (for configured type 2 PUSCH transmission). These two DCIs can be indicated via two separate PDCCHs or two parts of a PDCCH. In one example, the other DCI may also include beam indication / update (in addition to the beam indication via the UL-TCI-DCI).

[0302] In Example I.12.3, the UE is configured to receive a dedicated DCI (UL-TCI-DCI), which indicates a common beam (TCI state) for transmitting UL control (PUCCH) and / or data (PUSCH). The UE receives (e.g., in UL-TCI-DCI format) and decodes the UL-TCI-DCI, and uses the indicated beam (TCI state) to transmit UL control (PUCCH) (e.g., periodic PUCCH or semi-persistent PUCCH) and / or data (PUSCH) (e.g., configured license type 1).

[0303] In Example I.12.4, the UE is configured to receive a DCI and a MAC CE: (a) a MAC CE for common beam (TCI state) indication, and (b) a DCI for activating / releasing PUSCH transmission (for configured license type 2 PUSCH transmission). This DCI, as well as the DCI of the scheduled MAC CE, can be indicated via two separate PDCCHs or two parts of a PDCCH. In one example, the DCI may also include beam indication / update (in addition to the beam indication via the MAC CE).

[0304] When the beam indication is via MAC CE, it is a direct extension of at least one of embodiments I.7A, I.8A, I.9A, I.10A, I.11AA, I.11AAA or I.1A, I.2A, I.3A, I.4A, I.5AA, I.5AAA.

[0305] In Embodiment I.13, the UE may be configured with a dynamic beam (TCI state) indication / update, either separately from or together with the PDCCH command, for transmitting a PDCCH-triggered contention-free random access (CFRA) preamble, wherein the TCI state indication is via RACH-TCI-DCI and / or the PDCCH command, and details regarding RACH-TCI-DCI are based on U.S. Provisional Patent Application No. 63 / 009,234, filed April 13, 2020. Specifically, RACH-TCI-DCI may be used / configured to enable the possibility of updating / indicating the TCI state separately from the PDCCH command. When the beam indication is separate from the PDCCH command, the indicated beam can be used for both DL control (e.g., PDCCH command) reception and PRACH preamble transmission. This is referred to herein as a "common beam (TCI state) indication." When the beam indication is together with the PDCCH command, the indicated beam can only be used for transmitting the PRACH preamble. In this case, the beam used to receive DL control (i.e., PDCCH commands) can be another beam (TCI state), as explained in U.S. Patent Application No. 17 / 222,592, filed April 5, 2021, cited above.

[0306] At least one of the following embodiments can be used. In one alternative, only one embodiment of the following embodiments is used for beam (TCI state) indication. In another alternative, multiple embodiments of the following embodiments can be used for beam (TCI state) indication, one of which is configured to the UE via higher-layer (RRC) and / or MAC CE-based and / or DCI-based signaling. In the following embodiments or examples, the location of beam (TCI state) indication refers to carrier DCI, such as RACH-TCI-DCI or PDCCH commands.

[0307] In Example I.13.1, the common beam (TCI state) indication is always via RACH-TCI-DCI, not via PDCCH command. There is only one beam indication, whose position (or carrier DCI) is fixed at RACH-TCI-DCI.

[0308] In Example I.13.2, the common beam (TCI state) indication can be via RACH-TCI-DCI or PDCCH commands. Only one beam indication, whose position (or carrier DCI) is configured to the UE, can be used. At least one of the following examples can be used.

[0309] In Example I.13.2.1, the position of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is configured via RACH-TCI-DCI, while when parameter P takes another value (e.g., P = 1 or P > 0), the beam indicator is configured via PDCCH commands. Parameter P can be configured via fields in RACH-TCI-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via RACH-TCI-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0310] In Example I.13.2.2, the position of the common beam indicator is configured via field F in the RACH-TCI-DCI. When field F takes one value (e.g., F = 0), the beam indicator is transmitted via the PDCCH command, while when the field value is another value (e.g., F > 0), the beam indicator is transmitted via the RACH-TCI-DCI. In one example, when F > 0, the value of F indicates both (a) information about the beam indicator transmitted via the RACH-TCI-DCI and (b) the updated beam (TCI status) used for both data and control.

[0311] In Example I.13.3, the common beam (TCI state) indication can be via both RACH-TCI-DCI and PDCCH commands. There are two beam indication methods, one via RACH-TCI-DCI and the other via PDCCH commands. In one example, setting a higher-layer parameter to "enabled" indicates that the TCI state is indicated via PDCCH commands. In another example, MACCE signaling enables / disables the TCI state indication (in addition to the beam indication via RACH-TCI-DCI) via PDCCH commands. At least one of the following examples can be used.

[0312] In an example I.13.3.1, the TCI state used to receive the PDCCH command can be the TCI state indicated via RACH-TCI-DCI, and the TCI state used to send the PRACH preamble can be the TCI state indicated via the PDCCH command.

[0313] In an example I.13.3.2, the TCI state used to receive the PDCCH command can be the TCI state indicated via RACH-TCI-DCI, and the TCI state used to send the PRACH preamble can be the latest TCI state indicated via RACH-TCI-DCI or the PDCCH command.

[0314] In Example I.13.3.3, the TCI state / space relationship used to send the PRACH preamble follows the TCI state used for the PDCCH command.

[0315] In Example I.13.4, the common beam (TCI state) indication can be via one or both of the RACH-TCI-DCI and PDCCH commands. At least one of the following examples can be used.

[0316] In one example, I.13.4.1, the common beam (TCI state) indication can be via one of two states: (a) RACH-TCI-DCI only or (b) both RACH-TCI-DCI and PDCCH commands. In one option, one of these states is configured via higher-layer signaling and / or MAC CE signaling. In another option, RACH-TCI-DCI indicates one of these two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.13.3. In one example, RACH-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters. In one example, one of these two states is configured using a single RRC parameter.

[0317] In one example, I.13.4.2, the common beam (TCI state) indication can be via one of two states: (a) PDCCH command only or (b) both RACH-TCI-DCI and PDCCH command. In one option, one of these states is configured via higher-layer signaling and / or MAC CE signaling. In another option, RACH-TCI-DCI indicates one of these two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.13.3. In one example, RACH-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters. In one example, one of these two states is configured using a single RRC parameter.

[0318] In one example, I.13.4.3, the common beam (TCI state) indication can be via one of three states: (a) RACH-TCI-DCI only, (b) PDCCH command only, or (c) both RACH-TCI-DCI and PDCCH command. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, RACH-TCI-DCI indicates one of these three states. When the state is configured / indicated as (a) or (b), the common beam indication is according to some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication is according to embodiment I.13.3. In one example, RACH-TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of these three states is configured by enabling / disabling two RRC parameters. In another example, one of these three states is configured using only one RRC parameter.

[0319] In Example I.13.5, the RACH-TCI-DCI can be a two-level DCI comprising a first-level DCI and a second-level DCI, wherein the first-level DCI always exists (i.e., is configured and therefore can be received by the UE), has a fixed payload, and indicates the presence (i.e., is configured and therefore can be received by the UE) or absence (i.e., is not configured and / or therefore not received) of the second-level DCI. When the second-level DCI does not exist (is not configured and / or is not received), the UE assumes that the TCI state has not been updated. When the second-level DCI exists (is configured and therefore can be received by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used.

[0320] In an example I.13.5.1, the position of the second-level DCI is fixed as the PDDCH command.

[0321] In one example, I.13.5.2, the position of the second-level DCI is fixed as dedicated (second-level) RACH-TCI-DCI.

[0322] In Example I.13.5.3, the location of the Level 2 DCI is fixed as either a PDCCH command or a dedicated (Level 2) RACH-TCI-DCI. In this case, when the Level 1 DCI indicates the presence of Level 2 (configured to the UE), it also indicates the location of the Level 2 DCI (via the Level 1 DCI). For example, when field Y in the Level 1 DCI is set to 00, Level 2 DCI does not exist; when field Y in the Level 1 DCI is set to 01, Level 2 DCI exists and its location is DL-DCI; when field Y in the Level 1 DCI is set to 10, Level 2 DCI exists and its location is (Level 2) DL-TCI-DCI.

[0323] In Example I.13A, the common beam (TCI state) indication can be via one or both of the RACH-TCI-DCI and PDCCH commands. At least one of the following examples can be used.

[0324] In an example I.13A.1, the common beam (TCI state) indication is based on two RRC parameters, e.g., rach-tci-dci-IsPresent and tci-PresentInDCI, as shown below. When rach-tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0325] • When the time threshold is met, the TCI state of PDCCH order reception is transmitted via RACH-TCI-DCI, and the TCI state of RACH preamble transmission is transmitted via PDCCH command.

[0326] • When the time threshold is not met, the TCI states of both PDCCH command reception and RACH preamble transmission are transmitted via RACH-TCI-DCI.

[0327] When rach-tci-dci-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI states for both PDCCH command reception and RACH preamble transmission are via RACH-TCI-DCI.

[0328] In Example I.13A.2, the common beam (TCI state) indication is via both RACH-TCI-DCI and PDCCH commands. Specifically, TCI state 1 is indicated via RACH-TCI-DCI, while TCI state 2 is indicated via PDCCH commands. Subsequently, the TCI state received by the PDCCH command is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state received by the PDCCH command is either TCI state 1 or TCI state 2, or the latest of the TCI states indicated via MAC CE. The TCI state transmitted by the RACH preamble is TCI state 2.

[0329] In an example I.13A.3, the common beam (TCI state) indication is via both RACH-TCI-DCI and PDCCH commands. Specifically, TCI state 1 is indicated via RACH-TCI-DCI, while TCI state 2 is indicated via PDCCH commands. The TCI state for both PDCCH command reception and RACH preamble transmission is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state for both PDCCH command reception and RACH preamble transmission is the latest of either TCI state 1 or TCI state 2, or the latest of the TCI states indicated via MAC CE. Alternatively, the TCI state for both PDCCH command reception and RACH preamble transmission is the latest of either TCI state 1 or TCI state 2, or the latest of the TCI states indicated via MAC CE, subject to a fixed timeline constraint.

[0330] In Example I.13B, the common beam (TCI state) indication can be via one or more of RACH-TCI-DCI, PDCCH command, or PDSCH. At least one of the following examples can be used.

[0331] In Example I.13B.1, the common beam (TCI state) indication is via X and PDSCH, where X = RACH-TCI-DCI or PDCCH command. Specifically, TCI state 1 is indicated via X, and TCI state 2 is indicated via PDSCH. Subsequently, the TCI state received by the PDCCH command is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state received by the PDCCH command is the latest of TCI state 1, TCI state 2, or TCI state indicated via MAC CE. The TCI state transmitted by the RACH preamble is TCI state 1. In one example, X is fixed as RACH-TCI-DCI. In one example, X is fixed as the PDCCH command. In one example, X is configured via RRC and / or MAC CE. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission can be the same as the first PDSCH transmission, or it can change during the retransmission.

[0332] In an example I.13B.2, the common beam (TCI state) indication is via all of the RACH-TCI-DCI, PDCCH command, and PDSCH. Specifically, TCI state 1 is indicated via RACH-TCI-DCI, TCI state 2 via PDCCH command, and TCI state 3 via PDSCH. Subsequently, the TCI state received by the PDCCH command is the latest state among TCI state 1 and TCI state 3. Alternatively, the TCI state received by the PDCCH command is the latest state among TCI state 1, TCI state 3, or TCI state indicated via MAC CE. The TCI state transmitted by the RACH preamble is TCI state 2. Alternatively, the TCI state transmitted by the RACH preamble is the latest state among TCI state 1 and TCI state 2. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in the previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission.

[0333] UL's common beam indication can also be via MAC CE (and / or DCI). When the beam indication is via MAC CE, it is a direct extension of at least one of embodiments I.7A, I.8A, I.9A, I.10A, I.11AA, I.11AAA or I.1A, I.2A, I.3A, I.4A, I.5AA, I.5AAA.

[0334] Component 3: Beam indication of DL and UL content in DCI

[0335] In some embodiments of this disclosure, the UE is configured with dynamic beaming (TCI status) indication / updating for both DL reception and UL transmission, either separately from or together with DL allocation / UL authorization, wherein the TCI status indication is via TCI-DCI and / or DL ​​authorization (DL-DCI) and / or UL authorization (UL-DCI), and details regarding TCI-DCI are based on U.S. Patent Application No. 17 / 222,592, filed April 5, 2021, cited above. Specifically, TCI-DCI can be used / configured to enable the possibility of updating / indicating TCI status separately from DL allocation / UL authorization.

[0336] The indicated beam (TCI state) is common to all DL and UL channels. Specifically, the indicated common beam is used for the reception of DL control (PDCCH) and DL data (PDSCH) and 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 PRACH transmission.

[0337] Optionally, the indicated beam (TCI state) is shared for at least one DL channel and at least one UL channel. Specifically, the indicated common beam is used to receive at least one DL channel (where the at least one DL channel corresponds to PDCCH or PDSCH) and to transmit at least one UL channel (where the at least one UL channel corresponds to PUCCH, PUSCH, or PRACH).

[0338] When the beam indication is separate from DL allocation / UL authorization (i.e., via TCI-DCI), the indicated beam can be used to receive DL control (e.g., PDCCH carrying DL-DCI / UL-DCI) and / or DL ​​data (PDSCH) and to transmit UL control (PUCCH) and / or UL data (PUSCH) and / or PRACH.

[0339] When beam indication is used in conjunction with DL allocation (i.e., via DL-DCI), the indicated beam can only be used to receive DL data (the beam used to receive DL-DCI can be another beam (TCI state) as described in U.S. Patent Application No. 17 / 214,738, filed March 26, 2021, cited above) and / or DL ​​control carrying UL-DCI. Furthermore, the indicated beam can also be used to transmit UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH.

[0340] When beam indication is used in conjunction with UL authorization (i.e., via UL-DCI), the indicated beam can be used to transmit UL data (PUSCH) and / or UL control (PUCCH) and / or PRACH. Additionally, the indicated beam can also be used to receive DL control (e.g., PDCCH carrying DL-DCI) and / or DL ​​data (PDSCH).

[0341] At least one of the following embodiments can be used. In one alternative, only one embodiment of the following embodiments is used for beam (TCI state) indication. In another alternative, multiple embodiments of the following embodiments can be used for beam (TCI state) indication, one of which is configured to the UE via higher-layer (RRC) and / or MAC CE-based and / or DCI-based signaling. In the following embodiments or examples, beam position (TCI state) indication refers to carrier DCI, such as TCI-DCI, DL-DCI, or UL-DCI.

[0342] In Example I.14, the common beam (TCI state) indication is always via TCI-DCI, not via DL-DCI or UL-DCI. There is only one beam indication, the position (or carrier DCI) of which is fixed at TCI-DCI.

[0343] In Example I.14A, the common beam (TCI state) indication is always via the MAC CE (carried via the PDSCH, which is scheduled via the DCI), and not via TCI-DCI, UL-DCI, or DL-DCI. There is only one beam indication, whose location (or carrier channel) is fixed to the PDSCH carrying the MAC CE. In one example, the beam indication indicates a single beam (TCI state) for both the DL and UL channels / RS. In another example, the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS.

[0344] In Example I.15, the common beam (TCI state) indication can be via A-DCI. Only one beam indication, whose position A (or carrier DCI) is configured to the UE from the set {TCI-DCI,DL} or {TCI-DCI,UL} or {TCI-DCI,DL-DCI,UL-DCI}. At least one of the following examples can be used.

[0345] In Example I.15.1, the position A of the common beam indicator is configured via parameter P. For example, for A configured from {TCI-DCI,DL} or {TCI-DCI,UL}, when parameter P takes a value (e.g., P=0), the beam indicator is via TCI-DCI, and when parameter P takes another value (e.g., P=1 or P>0), the beam indicator is via DL-DCI or UL-DCI. Parameter P can be configured via a field in TCI-DCI. Alternatively, parameter P can be configured via a higher-level (RRC) parameter. When configuring parameter P via TCI-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0346] In Example I.15.2, the location A of the common beam indication is configured via field F in the TCI-DCI. For example, for A configured from {TCI-DCI,DL} or {TCI-DCI,UL}, when field F takes one value (e.g., F = 0), the beam indication is via DL-DCI or UL-DCI, and when the field takes another value (e.g., F > 0), the beam indication is via TCI-DCI. In one example, when F > 0, the value of F indicates both (a) information about the beam indication via TCI-DCI and (b) the updated beam (TCI state) used for both data and control.

[0347] In an example I.15.3, the location of the common beam indication is configured via an RRC parameter such as tci-PresentInDCI (in PDSCH-Config) or a MAC CE parameter. For example, when the parameter is provided, the common beam indication is via TCI-DCI; otherwise, it is via A-TCI, where A = DL or UL.

[0348] In Example I.15A, the common beam (TCI state) indication can be via X-DCI or MAC CE, where X = DL or UL or TCI, and the MAC CE is carried via PDSCH, which is scheduled via DCI. Only one beam indication is provided, and its location (or carrier channel) is configured for the UE. This configuration can be via RRC and / or MAC CE. In one example (E1), the beam indication is a single beam (TCI state) indicating both the DL and UL channels / RS. In one example (E2), the beam indication indicates two beams (TCI states), one for the DL channel / RS and one for the UL channel / RS. When the beam indication is via X-DCI, a subset of up to N (e.g., N = 8) beams can be activated via MAC CE (similar to Rel.15), which maps to up to N code points in the DCI field of X-DCI. When beam indication is via MAC CE, a single beam, i.e., N=1 (or two beams, in the case of example E2), is indicated (or both are indicated). Note that N here is the number of TCI states in the activated TCI state set. At least one of the following examples can be used.

[0349] In an example I.15A.1, the location of the common beam indicator is configured via parameter P. When parameter P takes a value (e.g., P = 0), the beam indicator is via X-DCI, while when parameter P takes another value (e.g., P = 1 or P > 0), the beam indicator is via MAC CE. Parameter P can be configured via a field in X-DCI. Alternatively, parameter P can be configured via two states of a higher-level (RRC) parameter. When configuring parameter P via X-DCI, it can be explicitly configured using a separate field or implicitly configured using another field (e.g., a joint DCI field for P and TCI states).

[0350] In Example I.15A.2, the location of the common beam indicator is configured via field F in the X-DCI. When field F takes a value (e.g., F = 0), the beam indicator is via the MAC CE, and when the field value is another value (e.g., F > 0), the beam indicator is via the X-DCI. In one example, when F > 0, the value of F indicates both (a) information about the beam indicator via the X-DCI and (b) the updated beam (TCI state) used for both data and control.

[0351] In an example I.15A.3, the location of the common beam indication is configured via an RRC parameter such as tci-PresentInDCI (in PDSCH-Config). When the RRC parameter is provided, the common beam indication is via X-DCI; otherwise, it is via MAC CE.

[0352] In Embodiment I.15B, a variation of Embodiment I.15A, the common beam (TCI state) indication is conditionally based and can be via X-DCI or MAC CE, where X = DL or UL or TCI. In one example, the condition is based on the value of N (the number of activated TCI states), and at least one of Examples I.2B.1 to I.2B.3 is used / configured. In another example, the condition is based on the value of M (the number of activated TCI states of UL). At least one of Examples I.8B.1 to I.8B.3 is used / configured.

[0353] In embodiment I.15C, a variation of embodiments I.15A and I.15B, the common beam (TCI state) indication is conditionally based and can be via X-DCI or MAC CE, where X = DL or UL or TCI. In one example, the condition is based on the values ​​of N (the number of activated TCI states for DL) and M (the number of activated TCI states for UL), assuming that the set of activated TCI states is different for DL ​​and UL, and at least one of examples I.2C.1 to I.2C.7 is used / configured.

[0354] In Example I.16, the common beam (TCI state) indication can be via both TCI-DCI and A-DCI. There are two beam indications, one via TCI-DCI and the other via A-DCI, with position A (or carrier DCI) fixed to DL or UL, or configured from the set {UL, DL}. In one example, for A=DL, the higher-layer parameter tci-PresentInDCI (in PDSCH-Config) is set to "enabled," indicating that the TCI state is indicated via DL-DCI (in addition to the beam indication via TCI-DCI). In another example, MAC CE signaling enables / disables the TCI state indication via DL-DCI (in addition to the beam indication via TCI-DCI). At least one of the following examples can be used.

[0355] In an example I.16.1, when A = DL, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be a TCI state indicated via TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be a TCI state indicated via DL-DCI.

[0356] The TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via DL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI or DL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be the latest TCI status indicated via TCI-DCI or DL-DCI.

[0357] In an example I.16.2, when A = DL, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be the TCI state indicated via TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be the latest TCI state indicated via TCI-DCI or DL-DCI.

[0358] The TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via DL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI or DL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be the latest TCI status indicated via TCI-DCI or DL-DCI.

[0359] In Example I.16.3, when A = UL, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be a TCI state indicated via TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be a TCI state indicated via TCI-DCI or UL-DCI. Alternatively, the TCI state for receiving DL data (PDSCH) can be configured from a TCI state indicated via TCI-DCI or UL-DCI.

[0360] The TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via UL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI or UL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be the most recent TCI status indicated via TCI-DCI or UL-DCI.

[0361] In an example I.16.4, when A = UL, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be the TCI state indicated via TCI-DCI, and the TCI state for receiving DL data (PDSCH) can be the latest TCI state indicated via TCI-DCI or UL-DCI.

[0362] The TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via UL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be a TCI status indicated via TCI-DCI or UL-DCI. Alternatively, the TCI status used for transmitting PUCCH and / or PUSCH and / or PRACH can be the most recent TCI status indicated via TCI-DCI or UL-DCI.

[0363] In Embodiment I.16A, the common beam (TCI state) indication can be via both X-DCI and MAC CE, where X = UL or DL ​​or TCI, and MAC CE is carried via PDSCH, which is scheduled via DCI. The remaining details (examples) are the same as in Embodiments I.2A and I.9A.

[0364] In embodiment I.17, the common beam (TCI state) indication can be via one or both of TCI-DCI and A-DCI, wherein position A (or carrier DCI) is fixed to DL or UL, or configured from the set {UL,DL}. At least one of the following examples can be used.

[0365] In one example, I.17.1, the common beam (TCI state) indication can be via one of two states: (a) TCI-DCI only or (b) both TCI-DCI and A-DCI. In one option, one of these states is configured via higher-layer signaling and / or MAC CE signaling. In another option, TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.16. In one example, TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters, for example, setting tci-dci-IsPresent = 'enabled' and enabling / disabling tci-PresentInDCI (in PDSCH-Config). In another example, one of these two states is configured using an RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0366] In one example, I.17.2, the common beam (TCI state) indication can be via one of two states: (a) A-DCI only or (b) both TCI-DCI and A-DCI. In one option, one of these two states is configured via higher-layer signaling and / or MAC CE signaling. In another option, TCI-DCI indicates one of the two states. When configured / indicated as state (a), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (b), the common beam indication follows embodiment I.16. In one example, TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 1, the beam indication is via (a), and when Z = 2, the beam indication is via (b). In one example, one of these two states is configured by two RRC parameters, for example, setting tci-PresentInDCI (in PDSCH-Config) = 'enabled' and enabling / disabling tci-dci-IsPresent. In another example, one of the two states is configured using an RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0367] In one example, I.17.3, the common beam (TCI state) indication can be via one of three states: (a) TCI-DCI only, (b) A-DCI only, or (c) both TCI-DCI and A-DCI. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, TCI-DCI indicates one of these three states. When the state is configured / indicated as (a) or (b), the common beam indication follows some embodiments of this disclosure; when the state is configured / indicated as (c), the common beam indication follows embodiment I.16. In one example, TCI-DCI includes a parameter Z indicating multiple TCI states. When Z = 0, the beam indication is via (a); when Z = 1, the beam indication is via (b); and when Z = 2, the beam indication is via (c). In one example, one of these three states is configured by enabling / disabling two RRC parameters (e.g., tci-dci-IsPresent and tci-PresentInDCI (in PDSCH-Config)). In another example, one of the three states is configured using a single RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0368] In one example, I.17.4, the common beam (TCI state) indication can be configured via one of three states: (a) TCI-DCI only, (b) A-DCI only, or (c) both TCI-DCI and B-DCI, where A ≠ B, and (A, B) is fixed as (DL, UL) or (UL, DL), or configured from the set {(DL, UL), (UL, DL)}. In one option, one of these three states is configured via higher-layer signaling and / or MAC CE signaling. In another option, TCI-DCI indicates one of these three states. When configured / indicated as state (a) or (b), the common beam indication follows some embodiments of this disclosure; when configured / indicated as state (c), the common beam indication follows embodiment I.16. In one example, TCI-DCI includes a parameter Z indicating multiple TCI states. When Z=0, the beam indication is via (a); when Z=1, the beam indication is via (b); and when Z=2, the beam indication is via (c). In one example, one of these three states is configured by enabling / disabling two RRC parameters (e.g., tci-dci-IsPresent and tci-PresentInDCI (in PDSCH-Config)). In another example, one of these three states is configured using a single RRC parameter, such as tci-dci-IsPresent or tci-PresentInDCI (in PDSCH-Config).

[0369] In Embodiment I.17A, the common beam (TCI state) indication can be via one or both of X-DCI and MAC CE, where X = UL or DL ​​or TCI, and MAC CE is carried via PDSCH, which is scheduled via DCI. The remaining details (examples) are the same as in Embodiments I.3A and I.10A.

[0370] In Example I.18, the common beam (TCI status) indication can be via all three DCIs, TCI-DCI, DL-DCI, and UL-TCI. In one example, the higher-layer parameter is set to "enabled," indicating that the TCI status is indicated via DL-DCI and / or UL-DCI (in addition to the beam indication via TCI-DCI). In another example, MAC CE signaling enables / disables the TCI status indication via DL-DCI and / or UL-DCI (in addition to the beam indication via TCI-DCI). At least one of the following examples can be used.

[0371] In an example I.18.1, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be a TCI state indicated via TCI-DCI, the TCI state for receiving DL data (PDSCH) can be a TCI state indicated via DL-DCI, and the TCI state for transmitting UL data (PDSCH) and / or PUCCH and / or PRACH can be a TCI state indicated via UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be configured, for example, from a TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be the most recent TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI.

[0372] In Example I.18.2, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be a TCI state indicated via TCI-DCI, the TCI state for receiving PDSCH can be configured, for example, from a TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI, and the TCI state for transmitting UL data (PDSCH) and / or PUCCH and / or PRACH can be a TCI state indicated via UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be configured, for example, from a TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be the most recent TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI.

[0373] In an example I.18.3, the TCI state for receiving DL control (e.g., a PDCCH carrying DL-DCI and / or UL-DCI) can be a TCI state indicated via TCI-DCI, the TCI state for receiving PDSCH can be the latest TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI, and the TCI state for transmitting UL data (PDSCH) and / or PUCCH and / or PRACH can be a TCI state indicated via UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be configured, for example, from a TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI. Alternatively, the TCI state for transmitting PUCCH and / or PUSCH and / or PRACH can be the latest TCI state indicated via TCI-DCI, DL-DCI, or UL-DCI.

[0374] In Example I.18AA, the common beam indication can be a two-level indication including a first-level indication and a second-level indication, wherein the first-level indication always exists (i.e., is configured and therefore can be received by the UE), has a fixed payload, and indicates the presence (i.e., is configured and therefore can be received by the UE) or absence (i.e., is not configured and / or therefore not received) of the second-level indication. When the second-level indication does not exist (is not configured and / or is not received), the UE assumes that the TCI state has not been updated. When the second-level indication exists (is configured and therefore can be received by the UE), the UE uses / updates the TCI state according to the second-level DCI. At least one of the following examples can be used. In one example, the first-level indication is via MAC CE, and the second-level indication is via X-DCI.

[0375] In an example I.18AA.1, the first-level indication is via MAC CE, and the position of the second-level indication is fixed at X-DCI, where X = UL or DL ​​or TCI-DCI.

[0376] In an example I.18AA.2, the first-level indication is via the first-level MAC CE, and the position of the second-level indication is fixed at the second-level MAC CE.

[0377] In an example I.18AA.3, the first-level indication is via X-DCI, where X = UL or DL ​​or TCI-DCI, and the location of the second-level indication is fixed at MAC CE.

[0378] In Example I.18AA.4, the first-level indication is via MAC CE, and the location of the second-level DCI can be either X-DCI or MAC CE. In this case, when the first-level indication indicates the presence of the second level (configured to the UE), it also indicates the location of the second-level indication (via the first-level indication). For example, when field Y in the first-level indication is set to 00, the second-level indication does not exist; when field Y in the first-level indication is set to 01, the second-level indication exists and its location is X-DCI; when field Y in the first-level indication is set to 10, the second-level indication exists and its location is (second-level) MAC CE.

[0379] In embodiment I.18A, the common beam (TCI state) indication can be via one or both of TCI-DCI and A-DCI, wherein position A (or carrier DCI) is fixed at DL or UL, or configured from the set {UL,DL}. At least one of the following examples can be used.

[0380] In an example I.18A.1, the common beam (TCI state) indication is based on two RRC parameters, such as tci-dci-IsPresent and tci-PresentInDCI, as shown below. When tci-dci-IsPresent = enabled, tci-PresentInDCI = enabled, and

[0381] ● When the time threshold is met, the TCI status of UL control transmission (and DL control reception) is transmitted via TCI-DCI, and the TCI status of UL data transmission (and DL data reception) is transmitted via A-DCI.

[0382] ● When the time threshold is not met, the TCI status of both UL data and UL control transmission (as well as DL data and DL control reception) is transmitted via TCI-DCI.

[0383] When tci-dci-IsPresent=enabled and tci-PresentInDCI is not provided, the TCI status of both UL data and UL control transmissions (and both DL data and DL control receptions) is transmitted via TCI-DCI. The TCI status transmitted via PRACH can be a TCI status transmitted via TCI-DCI or A-DCI. Alternatively, the TCI status transmitted via PRACH can be indicated separately, for example, via MAC CE and / or separate DCI.

[0384] In an example I.18A.2, the common beam (TCI state) indication is via both TCI-DCI and A-DCI. Specifically, TCI state 1 is indicated via TCI-DCI, and TCI state 2 is indicated via A-DCI (e.g., by setting tci-PresentInDCI=enabled). Subsequently, the TCI state for UL control transmission (and DL control reception) is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state for UL control transmission (and DL control reception) is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE. The TCI state for UL data transmission (and DL data reception) is TCI state 2. The TCI state for PRACH transmission can be a TCI state via TCI-DCI or A-DCI. Alternatively, the TCI state for PRACH transmission can be indicated separately, for example, via MAC CE and / or a separate DCI.

[0385] In an example I.18A.3, the common beam (TCI state) indication is via both TCI-DCI and A-DCI. Specifically, TCI state 1 is indicated via TCI-DCI, and TCI state 2 is indicated via A-DCI (e.g., by setting tci-PresentInDCI=enabled). The TCI state for both UL data and UL control transmission (and both DL data and DL control reception) is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state for both UL data and UL control transmission (and both DL data and DL control reception) is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE. Alternatively, the TCI state for both UL data and UL control transmission (and both DL data and DL control reception) is the latest of either TCI state 1 or TCI state 2, or the TCI state indicated via MAC CE, subject to a fixed timeline constraint. The TCI state for PRACH transmission can be a TCI state via either TCI-DCI or A-DCI. Alternatively, the TCI status sent by PRACH can be indicated separately, for example, via MAC CE and / or DCI alone.

[0386] In Example I.18B, the common beam (TCI state) indication can be via one or more of TCI-DCI and A-DCI or PDSCH, where position A (or carrier DCI) is fixed to either DL or UL, or configured from the set {UL,DL}. In one example, the PDSCH can carry MAC CE parameters (or activation commands or bitmaps) for the common beam indication, where the MAC CE parameters are included in the MAC control message, the UE is configured to receive the MAC control message via the MAC CE PDSCH, and can receive such configuration via the DCI in the PDCCH. Furthermore, the MAC CE PDSCH can be dedicated to the MAC control message (without any DL data), or it can be a PDSCH multiplexed together with both the MAC CE control message and DL data. In one example, the PDSCH can carry the common beam indication multiplexed with DL data (i.e., without any MAC control message). At least one of the following examples can be used.

[0387] In Example I.18B.1, the common beam (TCI state) indication is via both X-DCI and PDSCH, where X = TCI or A. Specifically, TCI state 1 is indicated via X-DCI, and TCI state 2 is indicated via PDSCH. Subsequently, the TCI state for UL control transmission (and DL control reception) is the latest of TCI state 1 and TCI state 2. Alternatively, the TCI state for UL control transmission (and DL control reception) is the latest of TCI state 1, TCI state 2, or the TCI state indicated via MAC CE. The TCI state for UL data transmission (and DL data reception) is TCI state 1. In one example, X is fixed as TCI. In one example, X is fixed as A. In one example, X is configured via RRC and / or MAC CE. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission may be the same as the first PDSCH transmission, or it may change during the retransmission. The TCI status transmitted via PRACH can be the TCI status via X-DCI or PDSCH. Alternatively, the TCI status transmitted via PRACH can be indicated separately, for example, via MAC CE and / or separate DCI.

[0388] In Example I.18B.2, the common beam (TCI state) indication is via all of TCI-DCI, A-DCI, and PDSCH. Specifically, TCI state 1 is indicated via TCI-DCI, TCI state 2 via A-TCI, and TCI state 3 via PDSCH. Subsequently, the TCI state for UL control transmission (and DL control reception) is the latest state among TCI state 1 and TCI state 3. Alternatively, the TCI state for UL control transmission (and DL control reception) is the latest state among TCI state 1, TCI state 3, or the TCI state indicated via MACCE. The TCI state for UL data transmission (and DL data reception) is TCI state 2. Alternatively, the TCI state for UL data transmission (and DL data reception) is the latest state among TCI state 1 and TCI state 2. When a HARQ retransmission occurs for PDSCH reception (due to PDSCH decoding failure in a previous transmission / retransmission), the TCI state indicated via retransmission can be the same as the first PDSCH transmission, or it can change during the retransmission. The TCI state of the PRACH transmission can be the TCI state via TCI-DCI, A-DCI, or the PDSCH TCI state. Alternatively, the TCI state of the PRACH transmission can be indicated separately, for example, via MAC CE and / or a separate DCI.

[0389] In Embodiment I.19, the common beam indication according to some embodiments of this disclosure is subject to the UE capability report. That is, when the UE capability report includes an indication that the UE is capable of common beam indication, the NW / gNB can configure the common beam indication for the UE as proposed in some embodiments of this disclosure. Otherwise (when the UE does not report common beam indication capability), the NW / gNB can configure the beam indication for the UE according to the Rel.15 / 16 beam indication mechanism (i.e., the TCI state received by DL control is via MAC CE, and the TCI state received by DL data is either the same TCI state as DL control, or indicated via DL-DCI).

[0390] In addition, the UE supports a variety of common beam indication schemes (as proposed in this disclosure), and one of these schemes can then be configured via RRC and / or MAC CE and / or DCI.

[0391] In Example I.20, one of the following configurations can be configured for the UE for Common Beam (TCI State) indication.

[0392] • Config1: TCI status indication is based on the Rel.15 / R16 beam indication mechanism (i.e., the TCI status received by DL control or transmitted by UL control is via MAC CE, and the TCI status received by DL data or transmitted by UL data is either the same as the TCI status of DL / UL control or indicated via DL / UL-DCI).

[0393] • Config2: TCI status indication is updated via UL / DL-DCI (e.g., DCI format 1_x and / or DCI format 0_x, where x = 0, 1).

[0394] •Config3: TCI status indicator is updated via dedicated DL / TC-TCI-DCI or TCI-DCI.

[0395] • Config4: TCI status indicator updated via a combination of Config2 and Config3, for example, the latest TCI status indicated by Config2 and Config3. This may be subject to a fixed timeline limit.

[0396] • Config5: For both data and control, the TCI status indication is updated via MAC-CE command.

[0397] The common beam indication for both DL and UL can also be via MAC CE (and / or DCI). When the beam indication is via MAC CE, it is a direct extension according to the embodiment or at least one of I.1A, I.2A, I.3A, I.4A, I.5AA, I.5AAA.

[0398] Component 4: Beam indication based on MAC CE

[0399] As described in 3GPP specification TS 38.321, a MAC PDU consists of one or more MAC subPDUs. Each MAC subPDU consists of one of the following:

[0400] • MAC subheader only (including padding);

[0401] • MAC subheader and MAC SDU;

[0402] • MAC subheader and MAC CE;

[0403] • MAC subheader and padding.

[0404] MAC SDUs have variable sizes. Each MAC subheader corresponds to a MAC SDU, MAC CE, or padding. Except for fixed-size MAC CEs, padding, and MAC SDUs containing UL CCCHs, MAC subheaders consist of the header fields R / F / LCID / (eLCID) / L. MAC subheaders for fixed-size MAC CEs, padding, and MAC SDUs containing UL CCCHs consist of two header fields, R / LCID.

[0405] Figure 16 An example of the DL MAC PDU 1600 is shown. Figure 16 The example of the DL MAC PDU 1600 shown is for illustrative purposes only. Figure 16 This disclosure is not intended to limit the scope of any particular implementation of the DL MAC PDU 1600 example.

[0406] like Figure 16 As shown, MAC CEs are placed together. Multiple DL MAC sub-PDUs with (multiple) MAC CEs are placed before any MAC sub-PDU with a MAC SDU and the MAC sub-PDU with padding.

[0407] In Example II.1, when the beam (or TCI status) indication is via the MAC CE, the TCI status indication MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1 of TS 38.321, for example, by using an existing code point / index in Table 6.2.1-1 (e.g., 52 or 53) or by using a new code point / index in Table 6.2.1-1 (e.g., 63).

[0408] Table 6.2.1-1 LCID values ​​of DL-SCH

[0409]

[0410]

[0411] MAC CE has a fixed size of 16 bits or 24 bits, and all of them include the following fields:

[0412] • Serving Cell ID: This field indicates the identifier of the serving cell to which MAC CE is applied.

[0413] • CORESET ID: As specified in TS 38.331, this field indicates the control resource set identified by ControlResourceSetId, for which the TCI status is indicated.

[0414] • TCI State ID: As specified in TS 38.331, this field indicates the TCI state identified by TCI-StateId, which applies to both DL data and controls and UL data and controls.

[0415] • BWP ID: As specified in TS 38.212, this field indicates the DL BWP, for which the MAC CE applies the code point of the DCI bandwidth portion indicator field.

[0416] • CORESET Pool ID: As specified in TS 38.331, this field indicates the mapping between the activated TCI state and the code point indicated by the DCI transmission configuration set in field Ti, specific to the ControlResourceSetId configured using the CORESET Pool ID. Setting this field to 1 indicates that the MAC CE should be applied to DL transmissions scheduled by a CORESET with a CORESET Pool ID equal to 1; otherwise, the MAC CE should be applied to DL transmissions scheduled by a CORESET Pool ID equal to 0.

[0417] Figure 17 Example 1700 of a MAC CE for Common Beam (TCI state) indication is shown, where a single TCI state is indicated. Example 1700 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 17 This disclosure is not intended to limit the scope to any particular implementation of Example 1700 of the MAC CE for Common Beam (TCI Status) indication.

[0418] Figure 18 Another example 1800 of a MAC CE for Common Beam (TCI state) indication is shown, where a single TCI state is indicated. Example 1800 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 18 This disclosure is not intended to limit the scope of any particular implementation of the MAC CE for Common Beam (TCI status) indication to any particular embodiment of Example 1800.

[0419] Figure 19 Another example 1900 of a MAC CE for indicating a common beam (TCI state) is shown, wherein a single TCI state is indicated. Example 1900 of a MAC CE for indicating a common beam (TCI state) is for illustrative purposes only. Figure 19 This disclosure is not intended to limit the scope to any particular implementation of Example 1900 of the MAC CE for Common Beam (TCI Status) indication.

[0420] Figure 20Another example 2000 of a MAC CE for Common Beam (TCI state) indication is shown, wherein a single TCI state is indicated. Example 2000 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 20 This disclosure is not intended to limit the scope to any particular implementation of the Example 2000 MAC CE for Common Beam (TCI Status) indication.

[0421] Figure 21 Another example 2100 of a MAC CE for Common Beam (TCI state) indication is shown, wherein a single TCI state is indicated. Example 2100 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 21 This disclosure is not intended to limit the scope of any particular implementation of Example 2100 of the MAC CE for Common Beam (TCI Status) indication.

[0422] Figure 22 Another example 2200 of a MAC CE for Common Beam (TCI state) indication is shown, wherein a single TCI state is indicated. Example 2200 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 22 This disclosure is not intended to limit the scope of any particular implementation of Example 2200 of the MAC CE for Common Beam (TCI Status) indication.

[0423] Figure 23 Example 2300 of a MAC CE for Common Beam (TCI state) indication is shown, wherein two TCI states are indicated. Example 2300 of a MAC CE for Common Beam (TCI state) indication is for illustrative purposes only. Figure 23 This disclosure is not intended to limit the scope of any particular implementation of Example 2300 of the MAC CE for Common Beam (TCI Status) indication.

[0424] Figure 24 Another example 2400 of a MAC CE for common beam (TCI state) indication is shown, wherein two TCI states are indicated. Example 2400 of a MAC CE for common beam (TCI state) indication is for illustrative purposes only. Figure 24 This disclosure is not intended to limit the scope of any particular implementation of the MAC CE example 2400 for Common Beam (TCI status) indication.

[0425] As mentioned above, some examples of MAC CE are in Figures 17 to 22 As shown, a single TCI state is indicated, which can be used, for example, for all DL and UL control and data channels (and RS). Figure 23 and Figure 24The diagram shows some examples of MAC CEs, which indicate two TCI states (1 and 2), one of which is available for all DL control and data channels (and RS), and the other is available for all UL control and data channels (and RS).

[0426] Any of the above-described variant embodiments can be used alone or in combination with at least one other variant embodiment.

[0427] Figure 25 A flowchart illustrating a method 2500 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 25 The embodiments of method 2500 shown are for illustrative purposes only. Figure 25 This disclosure is not intended to limit the scope to any particular implementation.

[0428] like Figure 25 As shown, method 2500 begins with step 2502. In step 2502, the UE (e.g., as...) Figure 1 The reception shown in 111-116 includes a set of configuration information including the status of the Transmit Configuration Indicator (TCI).

[0429] In step 2504, the UE receives an indication to activate M Media Access Control-Control Elements (MAC-CEs) from the group of TCI states, where M is a positive integer.

[0430] In step 2506, the UE identifies the medium indicating the TCI state update, which is either MAC-CE or downlink control information (DCI), and the TCI state update comes from M active states.

[0431] In step 2508, the UE determines the beam based on the TCI state update.

[0432] In step 2510, the UE applies a beam to both downlink (DL) control and data channel reception; wherein, TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type; QCL type is the type of QCL attribute associated with at least one source RS; and beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0433] In one embodiment, the media is determined based on conditions relating to the value of M.

[0434] In one embodiment, the condition corresponds to M≤t or M>t, where t is a threshold.

[0435] In one embodiment, t = 1, and: when M = 1, the medium is a MAC-CE that activates M TCI states, and the M activated TCI states correspond to a single activated TCI state, which also corresponds to a TCI state update; when M > 1, the medium is a DCI.

[0436] In one embodiment, media is identified based on information included in the configuration information.

[0437] In one embodiment, in response to a TCI state update indicating the joint TCI state of both the DL and the uplink (UL), the processor is configured to apply beaming to both the transmission of the UL control and data channels.

[0438] In one embodiment, in response to a TCI state update indicating two separate TCI states (DL TCI state and UL TCI state) respectively, the processor is configured to: determine a beam based on the DL TCI state, determine a UL transmit beam based on the UL TCI state, and apply the UL transmit beam to both the UL control channel and the data channel for transmission, wherein: the UL TCI state is indicated from N UL TCI states activated via MAC-CE, the N UL TCI states are activated from a second set of TCI states, where N≥1, and the medium is determined based on a condition that depends on either or both of the M and N values.

[0439] Figure 26 A flowchart illustrating another method 2600 performed by a base station (BS), such as BS 102, according to an embodiment of this disclosure is shown. Figure 26 The embodiments of method 2600 shown are for illustrative purposes only. Figure 26 This disclosure is not intended to limit the scope to any particular implementation.

[0440] like Figure 26 As shown, method 2600 begins with step 2602. In step 2602, BS (e.g., as...) Figure 1 As shown in 101-103), configuration information is generated including a set of Send Configuration Indicator (TCI) statuses.

[0441] In step 2604, the BS generates a Media Access Control-Control Element (MAC-CE) indicating the activation of M TCI states from the group of TCI states, where M is a positive integer.

[0442] In step 2606, the BS sends configuration information.

[0443] In step 2608, the BS transmits TCI state updates indicating the beam from M activated TCI states via a medium, wherein the medium is MAC-CE or downlink control information (DCI).

[0444] In step 2610, the BS transmits downlink (DL) control and data channels for reception via the indicated beam; wherein, TCI state refers to at least one source reference signal (RS) having a corresponding quasi-co-located (QCL) type; QCL type is the type of QCL attribute associated with at least one source RS; and beam refers to the QCL type being set as a spatial attribute for receiving or transmitting at least one source RS included in the TCI state update.

[0445] In one embodiment, the media is based on a conditional indication of the value of M.

[0446] In one embodiment, the condition corresponds to M≤t or M>t, where t is a threshold.

[0447] In one embodiment, t = 1, and: when M = 1, the medium is a MAC-CE that activates M TCI states, and the M activated TCI states correspond to a single activated TCI state, and the single activated TCI state also corresponds to a TCI state update; when M > 1, the medium is a DCI.

[0448] In one embodiment, the media is indicated based on information included in the configuration information.

[0449] In one embodiment, in response to a TCI status update indicating the joint TCI status of both the DL and the uplink (UL), the transceiver is configured to receive the UL control and data channels transmitted via the indicated beam.

[0450] In one embodiment, in response to a TCI state update indicating two separate TCI states (DL TCI state and UL TCI state) respectively, the transceiver is configured to: transmit a DL control and data channel for reception via a beam indicated by the DL TCI state, and receive a UL control and data channel transmitted via a UL transmit beam indicated by the UL TCI state, wherein: the UL TCI state is indicated from N UL TCI states activated via MAC-CE, the N UL TCI states are activated from a second set of TCI states, where N≥1, and the medium is indicated based on a condition that depends on either or both of the M and N values.

[0451] Figure 27 A UE according to an embodiment of this disclosure is shown.

[0452] refer to Figure 27 UE 2700 may include a processor 2710, a transceiver 2720, and a memory 2730. However, none of the components shown in the figures are required. UE 2700 may be composed of components such as processor 2710, transceiver 2720, and memory 2730. Figure 27The components shown can be implemented with more or fewer components. Furthermore, according to another embodiment, the processor 2710, transceiver 2720, and memory 2730 can be implemented as a single chip.

[0453] UE 2700 can correspond to the UE described above. For example, UE 2700 can correspond to... Figure 3 UE in the middle.

[0454] The above components will now be described in detail.

[0455] Processor 2710 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. Operation of UE 2700 may be implemented by processor 2710.

[0456] Transceiver 2720 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for down-converting the frequency of the received signal. However, according to another embodiment, transceiver 2720 may be implemented with more or fewer components than those shown in the components.

[0457] Transceiver 2720 can be connected to processor 2710 and send and / or receive signals. Signals may include control information and data. Furthermore, transceiver 2720 can receive signals via a wireless channel and output signals to processor 2710. Transceiver 2720 can also transmit signals output from processor 2710 via a wireless channel.

[0458] Memory 2730 may store control information or data included in signals received by electronic device 2700. Memory 2730 may be connected to processor 2710 and store at least one instruction, protocol, or parameter for the proposed function, process, and / or method. Memory 2730 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.

[0459] Figure 28 A base station according to an embodiment of this disclosure is shown.

[0460] Reference Figure 28 The base station 2800 may include a processor 2810, a transceiver 2820, and a memory 2830. However, none of the components shown in the figures are essential. The base station 2800 may be composed of components such as... Figure 28 The components shown may be implemented with more or fewer components. In addition, according to another embodiment, the processor 2810, transceiver 2820, and memory 2830 may be implemented as a single chip.

[0461] Base station 2800 may correspond to the gNB described in this disclosure. For example, base station 2800 may correspond to Figure 2 gNB in ​​the middle.

[0462] The above components will now be described in detail.

[0463] Processor 2810 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of base station 2800 may be implemented by processor 2810.

[0464] Transceiver 2820 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for down-converting the frequency of the received signal. However, according to another embodiment, transceiver 2820 may be implemented with more or fewer components than those shown in the components.

[0465] Transceiver 2820 can be connected to processor 2810 and transmit and / or receive signals. Signals may include control information and data. Furthermore, transceiver 2820 can receive signals via a wireless channel and output signals to processor 2810. Transceiver 2820 can also transmit signals output from processor 2810 via a wireless channel.

[0466] The memory 2830 may store control information or data included in signals acquired by the base station 2800. The memory 2830 may be connected to the processor 2810 and store at least one instruction, protocol, or parameter for the proposed function, process, and / or method. The memory 2830 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.

[0467] The flowcharts above illustrate exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although illustrated as a series of steps, the individual steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0468] Although this disclosure has been described using exemplary embodiments, various changes and modifications can be made by those skilled in the art. This disclosure is intended to include changes and modifications that fall within the scope of the appended claims. Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of this patent subject matter is defined only by the claims.

Claims

1.A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a radio resource control (RRC) message including a plurality of transmission configuration indicator (TCI) states; receiving, from the base station, first information that activates at least one TCI state among the plurality of TCI states via a medium access control-control element (MAC-CE); in case that only one TCI state is activated by the first information, applying the only one TCI state activated by the first information; and in case that tci-PresentInDCI is configured, receiving downlink control information (DCI) including second information on a TCI state and applying the TCI state indicated by the second information in the DCI. 2.The method of claim 1, tci-PresentInDCI indicates that a TCI state is indicated via the DCI and is configured by the RRC message. wherein 3.The method of claim 1, in case that only one TCI state is activated by the first information, the only one TCI state to be applied is determined based on the first information regardless of whether tci-PresentInDCI is configured or not. wherein 4.The method of claim 1, the only one TCI state activated by the first information or the TCI state indicated by the second information is a joint TCI state, and wherein wherein the joint TCI state is applied to a downlink channel and an uplink channel. 5.A method performed by a base station in a wireless communication system, the method comprising: transmitting, to a terminal, a radio resource control (RRC) message including a plurality of transmission configuration indicator (TCI) states; transmitting, to the terminal, first information that activates at least one TCI state among the plurality of TCI states via a medium access control-control element (MAC-CE); in case that tci-PresentInDCI is configured, transmitting, to the terminal, downlink control information (DCI) including second information on a TCI state, and transmitting a downlink channel or receiving an uplink channel based on a TCI state to be applied, in case that only one TCI state is activated by the first information, the TCI state to be applied is determined based on the first information in the MAC-CE, and wherein wherein, in case that tci-PresentInDCI is configured, the TCI state to be applied is determined based on the second information in the DCI. 6.The method of claim 5, tci-PresentInDCI indicates that a TCI state is indicated via the DCI and is configured by the RRC message. wherein, 7.The method of claim 5, in case that only one TCI state is activated by the first information, the only one TCI state to be applied is determined based on the first information regardless of whether tci-PresentInDCI is configured or not. wherein 8.The method of claim 5, the only one TCI state activated by the first information or the TCI state indicated by the second information is a joint TCI state, and wherein, wherein the joint TCI state is applied to a downlink channel and an uplink channel. ​ 9.A terminal in a wireless communication system, the terminal comprising: a transceiver; and a controller configured to: receive, from a base station via the transceiver, a radio resource control (RRC) message including a plurality of transmission configuration indicator (TCI) states, and receive, from the base station via the transceiver, first information activating at least one TCI state among the plurality of TCI states via a medium access control-control element (MAC-CE), in case that only one TCI state is activated by the first information, apply only the one TCI state activated by the first information, and in case that tci-PresentInDCI is configured, receive, from the base station via the transceiver, downlink control information (DCI) including second information on a TCI state, and apply the TCI state indicated by the second information in the DCI. 10.The terminal of claim 9, wherein tci-PresentInDCI indicates that a TCI state is indicated via the DCI and is configured by the RRC message. 11.The terminal of claim 9, wherein in case that only one TCI state is activated by the first information, the only one TCI state to be applied is determined based on the first information regardless of whether tci-PresentInDCI is configured. 12.The terminal of claim 9, wherein the only one TCI state activated by the first information or the TCI state indicated by the second information is a joint TCI state, and wherein the joint TCI state is applied to a downlink channel and an uplink channel. 13.A base station in a wireless communication system, the base station comprising: a transceiver; and a controller configured to: transmit, to a terminal via the transceiver, a radio resource control (RRC) message including a plurality of transmission configuration indicator (TCI) states, transmit, to the terminal via the transceiver, first information activating at least one TCI state among the plurality of TCI states via a medium access control-control element (MAC-CE), in case that tci-PresentInDCI is configured, transmit, to the terminal via the transceiver, downlink control information (DCI) including second information on a TCI state, and based on a TCI state to be applied, transmit a downlink channel or receive an uplink channel, wherein in case that only one TCI state is activated by the first information, the TCI state to be applied is determined based on the first information in the MAC-CE, and wherein, in case that tci-PresentInDCI is configured, the TCI state to be applied is determined based on the second information in the DCI. 14.The base station of claim 13, wherein, tci-PresentInDCI indicates that a TCI state is indicated via the DCI and is configured by the RRC message. 15.The base station of claim 13, wherein, in case that only one TCI state is activated by the first information, the only one TCI state to be applied is determined based on the first information regardless of whether tci-PresentInDCI is configured. 16.The base station of claim 13, wherein only one TCI state activated by the first information or the TCI state indicated by the second information is a joint TCI state, and wherein the joint TCI state is applied to the downlink channel and the uplink channel.

Images