Beam indication channel support method and apparatus
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SAMSUNG ELECTRONICS CO LTD
- Filing Date
- 2021-02-26
- Publication Date
- 2026-08-07
Smart Images
Figure CN115211198B_ABST
Abstract
Description
Technical Field
[0001] This disclosure generally relates to wireless communication systems, and more specifically, to beam indication channels in multi-beam systems. Background Technology
[0002] To meet the increased demand for wireless data services since the deployment of fourth-generation (4G) communication systems, efforts have been focused on developing improved fifth-generation (5G) or near-5G communication systems. 5G or near-5G communication systems are also referred to as "super-4G networks" or "post-Long Term Evolution (LTE) systems." 5G communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., the 60 MHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technologies for 5G communication systems are discussed. Furthermore, in 5G communication systems, system network improvements 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, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid frequency shift keying (FSK), Feher orthogonal amplitude modulation (FQAM), and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), while 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, a human-centric network for generating and consuming information, is now evolving into the Internet of Things (IoT), where distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE), a network of interconnected things connected to cloud servers and combined with big data processing technologies, has emerged as a result. As technological elements of the connectivity network for human-generated and consumed information evolve towards the IoT, with cloud servers providing IoT implementations, sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), and other technologies have recently been studied. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination of existing information technology (IT) with various industrial applications, IT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart cars or connected vehicles, smart grids, healthcare, smart devices, and advanced medical services.
[0004] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communication can be implemented through beamforming, MIMO, and array antennas. Cloud RAN, as an application of the aforementioned big data processing technologies, can also be considered an example of the integration of 5G and IoT technologies. Summary of the Invention
[0005] This disclosure relates to wireless communication systems, and more specifically, to beam indication channels in multi-beam systems.
[0006] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to: receive configuration information for one or more Transmission Configuration Indication (TCI) states, associated TCI state identifiers (IDs), and channels transmitting one or more TCI state IDs; and receive channels transmitting one or more TCI state IDs. The UE also includes a processor operatively connected to the transceiver. The processor is configured to: determine one or more spatial domain filters for receiving a downlink channel and transmitting an uplink channel based on one or more TCI state IDs; and determine the time for applying the one or more spatial domain filters. The transceiver is further configured to: receive a downlink channel using the one or more spatial domain filters starting at the determined time; and transmit an uplink channel using the one or more spatial domain filters starting at the determined time.
[0007] Other technical features will be apparent to those skilled in the art from the following figures, description and claims. Attached Figure Description
[0008] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:
[0009] Figure 1 An exemplary wireless network according to an embodiment of this disclosure is shown;
[0010] Figure 2 An exemplary gNB according to an embodiment of this disclosure is shown;
[0011] Figure 3 An exemplary UE according to an embodiment of this disclosure is shown;
[0012] Figure 4 and Figure 5 An exemplary wireless transmission and reception path according to an embodiment of this disclosure is shown;
[0013] Figure 6AAn exemplary wireless system beam according to an embodiment of this disclosure is shown;
[0014] Figure 6B Exemplary multibeam operation according to embodiments of this disclosure is illustrated;
[0015] Figure 7 An exemplary antenna structure according to an embodiment of the present disclosure is shown;
[0016] Figure 8 An exemplary DL multibeam operation according to an embodiment of this disclosure is shown;
[0017] Figure 9 Another exemplary DL multibeam operation according to an embodiment of this disclosure is shown;
[0018] Figure 10 An exemplary UL multibeam operation according to an embodiment of this disclosure is shown;
[0019] Figure 11 Another exemplary UL multibeam operation according to an embodiment of this disclosure is shown;
[0020] Figure 12 An exemplary cell covered by N beams according to an embodiment of this disclosure is shown;
[0021] Figure 13 An exemplary TCI state configuration according to an embodiment of this disclosure is shown;
[0022] Figure 14 An exemplary layered beam structure according to an embodiment of the present disclosure is shown;
[0023] Figure 15 An exemplary relationship between an SSB and a beam indication channel according to an embodiment of the present disclosure is shown;
[0024] Figure 16 An exemplary relationship between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown;
[0025] Figure 17 Another exemplary relationship between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown;
[0026] Figure 18 Another exemplary relationship between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown;
[0027] Figure 19 An exemplary relationship between CSI-RS and beam indication channel according to an embodiment of this disclosure is shown;
[0028] Figure 20 Exemplary components of a DCI format according to embodiments of the present disclosure are shown;
[0029] Figure 21 Another exemplary component of the DCI format according to an embodiment of this disclosure is shown;
[0030] Figure 22 An exemplary two-stage beam indication according to an embodiment of this disclosure is shown;
[0031] Figure 23 Exemplary time and frequency offsets according to embodiments of this disclosure are shown;
[0032] Figure 24 An exemplary beam indication according to an embodiment of this disclosure is shown;
[0033] Figure 25 A flowchart of a method for beam processing of a gNB according to an embodiment of the present disclosure is shown;
[0034] Figure 26 A flowchart of a method for beam processing of a UE according to an embodiment of the present disclosure is shown;
[0035] Figure 27 A base station according to an embodiment of the present disclosure is shown;
[0036] Figure 28 A user equipment (UE) according to an embodiment of the present disclosure is shown. Detailed Implementation
[0037] [Best Mode]
[0038] According to embodiments of this disclosure, a user equipment (UE) is provided. The UE includes a transceiver and a processor operatively connected to the transceiver. The processor is configured to: receive configuration information for one or more Transmission Configuration Indication (TCI) states, associated TCI state identifiers (IDs), and channels transmitting one or more TCI state IDs; and receive channels transmitting one or more TCI state IDs. The processor is configured to: determine one or more spatial domain filters for at least one of downlink channel reception and uplink channel transmission based on one or more TCI state IDs; and determine the time for applying the one or more spatial domain filters. The transceiver is further configured to: receive a downlink channel using one or more spatial domain filters starting from the determined time; and transmit an uplink channel using one or more spatial domain filters starting from the determined time.
[0039] In this embodiment, the determined time is based on at least one of the following: the channel transmitting one or more TCI status IDs, and the acknowledgment of the channel transmitting one or more TCI status IDs.
[0040] In this embodiment, the determined time is based on at least one of the following: UE capability, subcarrier spacing, predetermined time interval, and higher layer configuration.
[0041] In this embodiment, the channel transmitting one or more TCI status IDs is a Physical Downlink Control Channel (PDCCH) with Downlink Control Information (DCI) format. The DCI format is used to schedule the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) in a cell; and the DCI format includes: one or more TCI status IDs and downlink scheduling allocation or uplink scheduling grant, or one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling grant.
[0042] In this embodiment, the DCI format including one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling authorization further includes at least one of the following: a cyclic redundancy check (CRC) of the DCI format scrambled by a beam-indicating radio network temporary identifier (RNTI), a field in the DCI format for indicating that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization, and a bit pattern using one or more fields in the DCI format to indicate that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization; and bits of the DCI format being reused to transmit one or more TCI status IDs.
[0043] In this embodiment, the channel transmitting one or more TCI status IDs is transmitted on one or more beams, and at least one of the one or more beams is associated with one of the one or more TCI status IDs being transmitted.
[0044] In this embodiment, the channel transmitting one or more TCI status IDs is configured or determined as a two-part channel or signal; and the first part of the two-part channel or signal indicates at least one of the following: the existence of a second part in the two-part channel or signal, the payload size and content of the second part, the beam for transmitting the second part, and the resource elements and configuration for the second part.
[0045] According to embodiments of this disclosure, a base station (BS) is provided. The BS includes a transceiver and a processor operatively connected to the transceiver. The transceiver is configured to transmit configuration information for one or more Transmission Configuration Indication (TCI) states, associated TCI state identifiers (IDs), and channels for transmitting one or more TCI state IDs. The processor is configured to: generate one or more TCI state IDs associated with one or more spatial domain filters; and determine the time for applying one or more spatial domain filters. The transceiver is further configured to: transmit channels for transmitting one or more TCI state IDs; and perform at least one of the following operations: starting from the determined time, transmit a downlink channel using one or more spatial domain filters; and starting from the determined time, receive an uplink channel using one or more spatial domain filters.
[0046] In this embodiment, the determined time is based on at least one of the following: the channel transmitting one or more TCI status IDs, and the acknowledgment of the channel transmitting one or more TCI status IDs.
[0047] In this embodiment, the determined time is based on at least one of the following: UE capability, subcarrier spacing, predetermined time interval, and higher layer configuration.
[0048] In this embodiment, the channel transmitting one or more TCI status IDs is a Physical Downlink Control Channel (PDCCH) with Downlink Control Information (DCI) format. The DCI format is used to schedule the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) in a cell; and the DCI format includes: one or more TCI status IDs and downlink scheduling allocation or uplink scheduling grant, or one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling grant.
[0049] In this embodiment, the DCI format including one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling authorization further includes at least one of the following: a cyclic redundancy check (CRC) of the DCI format scrambled by a beam-indicating radio network temporary identifier (RNTI), a field in the DCI format for indicating that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization, and a bit pattern using one or more fields in the DCI format to indicate that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization; and bits of the DCI format being reused to transmit one or more TCI status IDs.
[0050] In this embodiment, the channel transmitting one or more TCI status IDs is transmitted on one or more beams, and at least one of the one or more beams is associated with one of the one or more TCI status IDs being transmitted.
[0051] In this embodiment, the channel transmitting one or more TCI status IDs is configured or determined as a two-part channel or signal; and the first part of the two-part channel or signal indicates at least one of the following: the existence of a second part in the two-part channel or signal, the payload size and content of the second part, the beam for transmitting the second part, and the resource elements and configuration for the second part.
[0052] According to embodiments of this disclosure, a method for operating a user equipment (UE) is provided. The method includes receiving configuration information for one or more Transmission Configuration Indication (TCI) states, associated TCI state identifiers (IDs), and a channel transmitting one or more TCI state IDs; receiving the channel transmitting one or more TCI state IDs; determining one or more spatial domain filters based on the one or more TCI state IDs for at least one of downlink channel reception and uplink channel transmission; determining a time for applying the one or more spatial domain filters; and performing at least one of the following operations: receiving a downlink channel using the one or more spatial domain filters starting from the determined time; and transmitting an uplink channel using the one or more spatial domain filters starting from the determined time.
[0053] In this embodiment, the method further includes determining time based on at least one of the following: a channel that transmits one or more TCI status IDs, acknowledgment of a channel that transmits one or more TCI status IDs, UE capability, subcarrier spacing, a predetermined time interval, and higher layer configuration.
[0054] In this embodiment, the channel transmitting one or more TCI status IDs is a Physical Downlink Control Channel (PDCCH) with Downlink Control Information (DCI) format. The DCI format is used to schedule the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) in a cell; and the DCI format includes: one or more TCI status IDs and downlink scheduling allocation or uplink scheduling grant, or one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling grant.
[0055] In this embodiment, the DCI format including one or more TCI status IDs but excluding downlink scheduling allocation or uplink scheduling authorization further includes at least one of the following: a cyclic redundancy check (CRC) of the DCI format scrambled by a beam-indicating radio network temporary identifier (RNTI), a field in the DCI format for indicating that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization, and a bit pattern using one or more fields in the DCI format to indicate that the DCI format does not include downlink scheduling allocation or uplink scheduling authorization; and bits of the DCI format being reused to transmit one or more TCI status IDs.
[0056] In this embodiment, the channel transmitting one or more TCI status IDs is transmitted on one or more beams, and at least one of the one or more beams is associated with one of the one or more TCI status IDs being transmitted.
[0057] In this embodiment, the channel transmitting one or more TCI status IDs is configured or determined as a two-part channel or signal; and the first part of the two-part channel or signal indicates at least one of the following: the existence of a second part in the two-part channel or signal, the payload size and content of the second part, the beam for transmitting the second part, and the resource elements and configuration for the second part.
[0058] [Invention Model]
[0059] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout the patent document. The term “connection” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “include” and “comprise,” and their derivatives imply non-limiting inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives mean including, being included within, interconnected with, comprising, included in, connected to or connected with, linked to or connected with, capable of communicating with, cooperating with, intertwined, juxtaposed, proximate, bound to or bound with, having, possessing the characteristics of, having a relationship with, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a “controller” may be implemented in hardware or a combination of hardware and software and / or firmware. Whether local or remote, the functionality associated with any particular controller can be centralized or distributed. The phrase "at least one" when used with a list of items means that different combinations of one or more of the listed items are available, and only one item from the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A; B; C; A and B; A and C; B and C; and A and B and C.
[0060] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and included in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, examples, related data, or portions thereof, implemented in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as 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 excludes wired, wireless, optical, or other communication links that transmit transient electrical signals or other transient signals. Non-transitory computer-readable media includes media capable of permanently storing data, as well as media capable of storing data and subsequently rewriting it, such as rewritable optical discs or erasable storage devices.
[0061] Throughout the patent document, definitions are provided for certain other words and phrases. Those skilled in the art will understand that, in many (if not most) instances, such definitions apply to the prior and future use of such defined words and phrases.
[0062] Fifth-generation (5G) or new radio (NR) mobile communications are gaining momentum recently, fueled by global technical activity from industry and academia regarding various candidate technologies. Potential drivers for 5G / NR mobile communications include massive MIMO technology from traditional cellular bands to higher frequencies to provide beamforming gain and support increased capacity; new waveforms for new radio access technologies (RATs) to flexibly adapt to various services / applications with different needs; and new multiple access schemes to support massive connectivity, among others.
[0063] The following discussion in this patent document Figures 1 to 28 The various embodiments used to describe the principles of this disclosure are merely exemplary and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.
[0064] The following documents are incorporated herein by reference, as fully set forth herein: 3GPP TS 38.211 v16.4.0, “NR; Physical channels and modulation”; 3GPP TS 38.212 v16.4.0, “NR; Multiplex and channel coding”; 3GPP TS 38.213 v16.4.0, “NR; Physical Layer Procedures for Control”; 3GPP TS 38.214 v16.4.0, “NR; Physical Layer Procedures for Data”; 3GPP TS 38.321 v16.3.0, “NR; Medium Access Control (MAC) protocol specification”; 3GPP TS 38.331 v16.3.1, “NR; Radio Resource”. Control (RRC) protocol specification)".
[0065] The following Figures 1 to 3Various implementations of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies are described in wireless communication systems. Figures 1 to 3 The description herein does not imply any limitation on the physical or architectural aspects of the different implementation methods. The various implementations of this disclosure can be implemented in any suitably arranged communication system.
[0066] Figure 1 An exemplary wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.
[0067] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station BS), 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).
[0068] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business; UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a 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 implementations, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.
[0069] 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 and receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless-enabled devices. A base station may provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3GPP 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” are used in this patent document to 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 to be a fixed device (such as a desktop computer or vending machine).
[0070] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that the 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 associated with natural and man-made obstacles.
[0071] As described in more detail below, one or more of UEs 111 to UE 116 include circuitry, programming, or a combination thereof for using a beam indication channel in a multi-beam system. In some embodiments, one or more of gNBs 101 to gNBs 103 include circuitry, programming, or a combination thereof for using a beam indication channel in a multi-beam system.
[0072] although Figure 1 An example of a wireless network is shown, but it is not possible to compare it with other wireless networks. Figure 1Various modifications can be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102 and gNB 103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, gNB 101, gNB 102, and / or gNB 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.
[0073] Figure 2 An 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. Figure 1 The gNB 101 and gNB 103 can have the same or similar configurations. However, gNBs have multiple configurations, and Figure 2 This disclosure is not intended to limit the scope of any particular implementation of gNB.
[0074] like Figure 2 As shown, gNB 102 includes multiple antennas 205a to 205n, multiple RF transceivers 210a to 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.
[0075] RF transceivers 210a to 210n receive input RF signals, such as signals transmitted by a UE in network 100, from antennas 205a to 205n. RF transceivers 210a to 210n down-convert the input RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 220 sends the processed baseband signal to controller / processor 225 for further processing.
[0076] TX processing circuit 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 225. TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. RF transceivers 210a to 210n receive the processed baseband or IF signal from TX processing circuit 215 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 205a to 205n.
[0077] 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, according to known principles, control the RF transceivers 210a to 210n, the RX processing circuitry 220, and the TX processing circuitry 215 to receive forward channel signals and transmit reverse channel signals. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations, differently weighting the signals output from the multiple antennas 205a to 205n and the signals input to the multiple antennas 205a to 205n to efficiently manipulate the output signals in the desired direction. Any of a variety of other functions can be supported in the gNB 102 via the controller / processor 225.
[0078] The controller / processor 225 can also execute programs and other processes (such as an OS) stored in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution process.
[0079] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a system supporting 5G / NR, 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 with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 235 includes any suitable architecture that supports communication via wired or wireless connections (such as Ethernet or RF transceivers).
[0080] The memory 230 is coupled to the controller / processor 225. A portion of the memory 230 may include RAM, while another portion of the memory 230 may include flash memory or other ROM.
[0081] although Figure 2 An example of gNB 102 is shown, but it is possible to modify it. Figure 2 Various changes can be made. For example, gNB 102 can include any number of Figure 2Each component shown. As a specific example, an access point may include several interfaces 235, and a controller / processor 225 may support routing capabilities for routing data between different network addresses. As another specific example, although shown as including 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 TX processing circuitry 215 and multiple instances of RX processing circuitry 220 (such as one instance per RF transceiver). Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and other components can be added as needed.
[0082] Figure 3 An exemplary UE 116 according to an embodiment of this disclosure is shown. Figure 3 The implementation of UE 116 shown is for illustrative purposes only. Figure 1 UEs 111 to UE 115 may have the same or similar configurations. However, UEs have multiple configurations, and Figure 3 This disclosure is not intended to limit the scope of any particular implementation of the UE.
[0083] like Figure 3 As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and a receive (RX) processing circuit 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.
[0084] 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 processor 340 for further processing (e.g., for web browsing data).
[0085] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or baseband data (such as web 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.
[0086] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 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.
[0087] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as those for beam management. Processor 340 can move data into or out of memory 360 as needed by the executing processes. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from the gNB or operator. Processor 340 is also coupled to I / O interface 345, which enables UE 116 to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.
[0088] The processor 340 is also connected 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 an LCD, an LED display, or other display capable of displaying text (such as from a website) and / or at least limited graphics.
[0089] 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).
[0090] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3The 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 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.
[0091] To meet the increased demands of wireless data services since the deployment of 4G communication systems and to enable various vertical applications, efforts have been made to develop and deploy 5G / NR communication systems. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz) to achieve higher data rates; or in lower frequency bands (e.g., 6 GHz) to achieve strong coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology in 5G / NR communication systems are discussed.
[0092] In addition, in 5G / NR communication systems, system network improvements 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, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.
[0093] Since one embodiment of this disclosure can be implemented in a 5G system, the discussion of 5G systems and associated frequency bands is for reference only. However, this disclosure is not limited to 5G systems or associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure are also applicable to the deployment of 5G communication systems, 6G, or even subsequent versions that can use terahertz (THz) frequency bands.
[0094] Since one embodiment of this disclosure can be implemented in a 5G system, the discussion of 5G systems and associated frequency bands is for reference only. However, this disclosure is not limited to 5G systems or associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure are also applicable to the deployment of 5G communication systems, 6G, or even subsequent versions that can use terahertz (THz) frequency bands.
[0095] The communication system includes downlink (DL) and uplink (UL). DL refers to the transmission from the base station or one or more transmitting points to the UE, and UL refers to the transmission from the UE to the base station or one or more receiving points.
[0096] On a cell, the time unit used for DL signaling or UL signaling is called a time slot, and it may include one or more symbols. Symbols may also be used as other time units. Frequency (or bandwidth (BW)) units are called resource blocks (RBs). An RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of 0.5 milliseconds or 1 millisecond, include 14 symbols, and an RB may include 12 SCs with an inter-SC spacing of 15 kHz or 30 kHz, etc.
[0097] DL signals include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). PDSCH or PDCCH can be transmitted on a variable number of time slot symbols, each consisting of one time slot symbol. For simplicity, the DCI format of the scheduling PDSCH received by the UE is referred to as the DL DCI format, and the DCI format of the scheduling Physical Uplink Shared Channel (PUSCH) transmitted by the UE is referred to as the UL DCI format.
[0098] The gNB transmits one or more types of RS, including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily used by the UE to perform measurements and provide CSI to the gNB. For channel measurements, Non-Zero Power CSI-RS (NZP CSI-RS) resources are used. For Interference Measurement Reporting (IMR), CSI Interference Measurement (CSI-IM) resources associated with the Zero Power CSI-RS (ZP CSI-RS) configuration are used. CSI processing includes both NZP CSI-RS and CSI-IM resources.
[0099] The UE can determine CSI-RS transmission parameters via DL control signaling from the gNB or higher-layer signaling such as Radio Resource Control (RRC) signaling. CSI-RS transmission examples can be indicated by DL control signaling or configured by higher-layer signaling. DM-RS is transmitted only in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.
[0100] Figure 4 and Figure 5Exemplary wireless transmit and receive paths according to this disclosure are illustrated. In the following description, transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while receive path 500 may be described as being implemented in a UE (such as UE 116). However, it will be understood that receive path 500 may be implemented in a gNB, and transmit path 400 may be implemented in a UE. In some embodiments, as described in embodiments of this disclosure, receive path 500 is configured to support a beam indication channel in a multi-beam system.
[0101] like Figure 4 The transmission path 400 shown includes a channel coding and modulation block 405, a serial-to-parallel (S to P) block 410, an N-size 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. For example... Figure 5 The receiver path 500 shown includes a downconverter (DC) 555, a cyclic prefix removal block 560, a serial-to-parallel (S to P) block 565, a fast Fourier transform (FFT) block of size N, a parallel-to-serial (P to S) block 575, and a channel decoding and demodulation block 580.
[0102] like Figure 4 As shown, the channel coding and modulation block 405 receives a set of information bits and applies coding (such as low-density parity-check (LDPC) coding) and modulation (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to the input bits to generate a frequency domain modulated symbol sequence.
[0103] Serial-to-parallel block 410 converts (e.g., demultiplexes) serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. Then, IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 420 converts (e.g., multiplexes) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (e.g., upconverts) the output of cyclic prefix addition block 425 to an RF frequency for transmission via the wireless channel. The signal may also be filtered at baseband before being converted to this RF frequency.
[0104] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the reverse operation relative to the operation at gNB 102.
[0105] like Figure 5As shown, downconverter 555 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 565 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 570 of size N executes the FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 575 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.
[0106] Each of gNBs 101 to 103 can implement a similar functionality to that sent to UEs 111 to UEs 116 in the downlink. Figure 4 The transmission path 400 shown can achieve a similar effect to that received from UE 111 to UE 116 in the uplink. Figure 5 The receive path 500 is shown. Similarly, each of UEs 111 to UE 116 may implement a transmit path 400 for transmitting to gNBs 101 to gNBs 103 in the uplink and a receive path 500 for receiving from gNBs 101 to gNBs 103 in the downlink.
[0107] Figure 4 and Figure 5 Each component can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components can be implemented in software, while others can be implemented using configurable hardware or a combination of software and configurable hardware. For example, FFT block 570 and IFFT block 415 can be implemented as configurable software algorithms, wherein the value of size N can be modified according to the implementation. Furthermore, although this disclosure is described as using FFT and IFFT, this is illustrative only and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT), can be used. It will be understood that for DFT and IDFT functions, the value of variable N can be any integer (such as 1, 2, 3, 4, etc.); while for FFT and IFFT functions, the value of variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).
[0108] although Figure 4 and Figure 5 An example of a wireless transmit and receive path is shown, but it is possible to modify it. Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5The various components can be combined, further subdivided, or omitted, and other components can be added as needed. Furthermore, Figure 4 and Figure 5 This is intended to illustrate examples of transmit and receive path types that can be used in wireless networks. Any other suitable architecture can be used to support wireless communication in wireless networks.
[0109] Figure 6A An exemplary wireless system beam 600 according to an embodiment of the present disclosure is shown. Figure 6A The implementation of the wireless system beam 600 shown is for illustrative purposes only.
[0110] like Figure 6A As shown, in a wireless system, the beam 601 for device 604 can be characterized by beam direction 602 and beamwidth 603. For example, device 604 with a transmitter transmits radio frequency (RF) energy within the beam direction and beamwidth. Device 604 with a receiver receives RF energy directed toward the device within the beam direction and beamwidth. Figure 6A As shown, the device at point A 605 can receive from and transmit to device 604 because point A is within the beamwidth of the beam traveling in the beam direction and from device 604.
[0111] like Figure 6A As shown, the device at point B (606) cannot receive from or transmit to device (604) because point B is outside the beamwidth of the beam traveling in the beam direction from device (604). Although for illustrative purposes, Figure 6A A two-dimensional (2D) beam is shown, but it will be apparent to those skilled in the art that the beam can be three-dimensional (3D), where the beam direction and beamwidth are defined in space.
[0112] Figure 6B An exemplary multi-beam operation 650 according to an embodiment of this disclosure is shown. Figure 6B The implementation of the multi-beam operation 650 shown is for illustrative purposes only.
[0113] In wireless systems, devices can transmit and / or receive on multiple beams. This is known as "multi-beam operation" and is... Figure 6B As shown in the image. Although for illustrative purposes, Figure 6B It is 2D, but to those skilled in the art, the beam can be 3D, wherein the beam can be sent in any direction in space or received in any direction in space.
[0114] Rel.14 LTE and Rel.15 NR support up to 32 CSI-RS antenna ports, allowing eNBs to be equipped with a large number of antenna elements (e.g., 64 or 128). In this case, multiple antenna elements are mapped to a single CSI-RS port. Figure 7 As shown, for millimeter-wave bands, although the number of antenna elements can be greater for a given shape factor, the number of CSI-RS ports (which can correspond to the number of digital precoding ports) tends to be limited by hardware constraints (e.g., the feasibility of installing a large number of ADCs / DACs in millimeter-wave bands).
[0115] Figure 7 An exemplary antenna structure 700 according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of the antenna structure 700 shown is for illustrative purposes only.
[0116] In this configuration, a CSI-RS port is mapped to a large number of antenna elements that can be controlled by a set of analog phase shifters 701. A CSI-RS port can then correspond to a subarray that generates a narrow analog beam through analog beamforming 705. This analog beam can be configured to scan a wider range of angles 720 by altering the set of phase shifters across symbols or subframes. The number of subarrays (equal to the number of RF chains) is related to the number of CSI-RS ports N. CSI-PORT Same. The digital beamforming unit 710 performs cross-N... CSI-PORT A linear combination of analog beams is used to further increase precoding gain. While the analog beams are broadband (and therefore not frequency-selective), digital precoding can vary across frequency subbands or resource blocks. Receiver operation can be similarly conceived.
[0117] Because the described system uses multiple analog beams for transmitting and receiving (where, for example, after a training duration to be performed from time to time, one or a few analog beams are selected from a large number of beams), 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 to calculate and perform beam reporting (also referred to as "beam measurement" and "beam reporting," respectively), and receiving the DL or UL transmit via the selection of the corresponding receive (RX) beam.
[0118] The described system can also be applied to higher frequency bands, such as above 52.6 GHz. In this case, the system can only use analog beams. Due to O2 absorption loss near 60 GHz (approximately 10 dB of additional loss at a distance of 100 m), more and sharper analog beams (and therefore more radiators in the array) may be needed to compensate for the additional path loss.
[0119] In Rel.15 NR, multi-beam operation is primarily designed for single TRP and single antenna panels. Therefore, this specification supports beam indication for a single TX beam, where the TX beam is associated with a reference RS. For DL beam indication and measurement, the reference RS can be an NZP CSI-RS and / or a synchronization signal block (including the primary synchronization signal, secondary synchronization signal, and PBCH). Here, DL beam indication is accomplished via the Transmission Configuration Indicator (TCI) field in the DL-associated DCI, which includes an index to one (and only one) assigned reference RS. A set of hypothetical or so-called TCI states is configured via higher-layer (RRC) signaling, and, where applicable, subgroups of these TCI states are selected / activated via MAC CE for TCI field code points. For UL beam indication and measurement, the reference RS can be an NZP CSI-RS, SSB, and / or SRS. Here, UL beam indication is accomplished via the SRS Resource Indicator (SRI) field in the UL-associated DCI 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. In various implementations, the DCI associated with the DL or the DCI associated with the UL, which includes beam indication, may be referred to as a beam indication channel. As used herein, a beam indication channel is a channel that transmits information indicating the desired or intended beam to be used, such as indication information like the TCI status ID.
[0120] Furthermore, the NW / gNB may use a DL channel designed for beam indication purposes to indicate to the UE the DL-TCI and / or UL-TCI and / or combined TCI and / or SRI of an upcoming DL channel transmission and / or UL channel transmission. In various embodiments, the DL channel designed for beam indication purposes may be referred to as a beam indication channel. As used herein, a beam indication channel is a channel that transmits information indicating the desired or intended beam, such as indication information including a TCI status ID.
[0121] Furthermore, the beam of the beam indication channel can be designed to provide wider beam coverage than that of the data and control channels, and can be designed such that adjacent beams of the beam indication channel partially overlap to provide more robust coverage in dynamic multipath environments.
[0122] Furthermore, for divergent and rapidly changing multipath environments, the TCI state of the beam indication channel can compromise by considering multiple beams, where the gNB transmits the TCI indication channel on one or more of these beams. Additionally, when the beam indication channel is for a group of UEs, the TCI state of the beam indication channel includes the beams covering that group of UEs.
[0123] In mobile wireless systems, a base station or TRP can serve multiple UEs. As UEs move and / or rotate, beam management processes enable the NW / gNB and / or UE to measure, report, indicate, and use new, suitable beams for communication. For robust operation in multipath environments, the gNB can indicate better new beams to the UE as the multipath environment changes, allowing the UE to reliably receive the new beam indications. As described in patent application No. 17 / 148,517, incorporated herein by reference, beam indication channels can use partially overlapping wide beams, and beam indication channels can be transmitted on multiple beams. This disclosure provides beam indication channels using SSB-based beams or wide-beamwidth CSI-RS beams, which can provide coverage across the cell width or coverage of specific areas within the cell. Furthermore, spatial filters can be used to transmit beam indication channels using SSB-based beams or wide-beamwidth CSI-RS beams, which can be a design aspect of the beam indication channel. Furthermore, in order to improve network operating efficiency, embodiments of this disclosure use a UE group-based beam indication channel, wherein the beam indication channel carries beam indications for multiple UEs, such as DL / UL / or combined TCI status.
[0124] Furthermore, this disclosure provides the design of a beam indication channel, including aspects such as the transmission resources of the beam indication channel, the triggering and transmission conditions of the beam indication channel, the payload of the beam indication, and the channel structure of the beam indication channel. This disclosure provides aspects of enhanced beam indication from NW / gNB to UE. In this disclosure, the use of SSB-based beams or wide-beamwidth CRI-RS beams is provided, which provide cell-wide coverage or coverage of a specific area within the cell for the beam indication channel.
[0125] In the following text, for the sake of brevity, both FDD and TDD are considered duplexing methods for DL and UL signaling. Although the exemplary description and implementation below assumes orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure is extendable to other OFDM-based transmission waveforms or multiple access schemes such as filtered OFDM (F-OFDM).
[0126] This disclosure provides several components that can be used in combination or together, or can operate independently.
[0127] In this disclosure, the term "activation" describes the following operation: the UE receives and decodes a signal from the network (or gNB) indicating a time start point. The start point can be a current or future time slot / subframe or symbol, the exact location of which is implicitly or explicitly indicated, or fixed or configured by a higher layer. Upon successful decoding of the signal, the UE responds accordingly. The term "disable" describes the following operation: the UE receives and decodes a signal from the network (or gNB) indicating a time stop point. The stop point can be a current or future time slot / subframe or symbol, the exact location of which is implicitly or explicitly indicated, or fixed or configured by a higher layer. Upon successful decoding of the signal, the UE responds accordingly.
[0128] In this disclosure, the terms "related" and "corresponding" are used interchangeably. Terms such as TCI, TCI status, SpatialRelationInfo, target RS, reference RS, and other terms are for illustrative purposes and are therefore not normative. Other terms relating to the same function may also be used.
[0129] 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, for DL, when the UE receives a reference RS index / ID in a DL allocation represented by a TCI state, the UE applies the known characteristics of the reference RS to the allocated DL transmission. The reference RS can be received and measured by the UE (in this case, the reference RS is a downlink signal such as an NZP CSI-RS and / or an SSB), and the measurement results are used to calculate a beam report (in Rel.15 NR, at least one L1-RSRP is accompanied by at least one CRI). When the NW / gNB receives the beam report, the NW can better equip the information to allocate 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 an uplink signal such as an SRS). When the NW / gNB receives the reference RS, the NW / gNB can measure and calculate the necessary information to allocate a specific DL TX beam to the UE. This option applies when the correspondence between DL-UL beam pairs is established.
[0130] In another example, for UL, when the UE receives a reference RS index / ID in the UL authorization, the UE applies the known characteristics of the reference RS to the authorized UL transmission. The reference RS can be received and measured by the UE (in this case, the reference RS is a downlink signal such as NZP CSI-RS and / or SSB), and the measurement results are used to calculate the beam report. When the NW / gNB receives the beam report, the NW can better equip the information to allocate a specific UL TX beam to the UE. This option is applicable when the correspondence between DL-UL beam pairs is established. Alternatively, the reference RS can be transmitted by the UE (in this case, the reference RS is an uplink signal such as SRS or DMRS). When the NW / gNB receives the reference RS, the NW / gNB can measure and calculate the necessary information to allocate a specific UL TX beam to the UE.
[0131] Reference RS can be dynamically triggered by NW / gNB (e.g., via DCI in the case of aperiodic RS), (in the case of periodic RS, such as periodicity and offset) pre-configured with specific time-domain behavior, or (in the case of semi-persistent RS) a combination of such pre-configuration and activation / disabling.
[0132] For mmWave (or FR2) or higher frequency bands (e.g., > 52.6 GHz), especially those associated with multi-beam operation, the transmit-receive process involves the receiver selecting a receive (RX) beam for a given TX beam. For DL multi-beam operation, the UE selects a DL RX beam for each DL TX beam (which corresponds to a reference RS). Therefore, when a DL RS (such as a CSI-RS and / or SSB) is used as a reference RS, the NW / gNB transmits the DL RS to the UE (which is associated with the selection of the DL TX beam). In response, the UE measures the DL RS (and selects the DL RX beam in the process) and reports beam metrics associated with the quality of the DL RS.
[0133] In this scenario, the UE determines the TX-RX beam pair for each configured (DL) reference RS. Therefore, although this knowledge is unavailable to the NW / gNB, the UE can select the DL RX beam from the knowledge of all TX-RX beam pairs when it receives a DL RS (and thus a DL TX beam) indication from the NW / gNB. Conversely, when a UL RS (such as an SRS and / or DMRS) is used as a reference RS (which is relevant when the DL-UL beam correspondence or reciprocity holds), the NW / gNB triggers or configures the UE to send a UL RS (which, for DL and reciprocity, corresponds to the DL RX beam). The gNB selects the DL TX beam upon receiving and measuring the UL RS. As a result, a TX-RX beam pair is obtained. The NW / gNB can perform this operation (each reference RS or "beam scan") on all configured UL RSs and determine all TX-RX beam pairs associated with all UL RSs configured for the UE.
[0134] The following two implementations (A-1 and A-2) are examples of DL multi-beam operation using DL beam indication based on DL-TCI. In the first exemplary implementation (A-1), the aperiodic CSI-RS is transmitted by the NW / gNB and measured by the UE. This implementation can be used regardless of whether the UL-DL beam correspondence is established. In the second exemplary implementation (A-2), the aperiodic SRS is triggered by the NW and transmitted by the UE, enabling the NW (or gNB) to measure the UL channel quality to allocate the DL RX beam. This implementation can be used when the UL-DL beam correspondence is established. Although aperiodic RS is used in these two examples, periodic or semi-persistent RS can also be used.
[0135] Figure 8 An exemplary DL multibeam operation 800 according to an embodiment of this disclosure is shown. Figure 8 The implementation of the DL multi-beam operation 800 shown is for illustrative purposes only.
[0136] exist Figure 8 In one example shown (e.g., implementation A-1), DL multi-beam operation 800 begins with the gNB / NW sending an aperiodic CSI-RS (AP-CSI-RS) trigger or indication signaling to the UE (step 801). This trigger or indication may be included in a DCI (either UL-related or DL-related, sent separately or together with an aperiodic CSI request / trigger) and indicates that the AP-CSI-RS will be transmitted in the same (zero time offset) or later (time offset > 0) time slot / subframe.
[0137] Upon receiving the AP-CSI-RS transmitted by the gNB / NW (step 802), the UE measures the AP-CSI-RS and sequentially calculates and reports the "beam metric" (indicating the assumed quality of a specific TX beam) (step 803). An example of such beam reporting is a CSI-RS resource indicator (CRI) or SSB resource indicator (SSB-RI) associated with the associated L1-RSRP / L1-RSRQ / L1-SINR / CQI.
[0138] When a beam report is received from the UE, the gNB / NW can use the beam report to select a DL RX beam for the UE and indicate the DL RX beam selection using the DL-TCI field or the joint DCI field in the DL-related DCI (which carries DL authorization, such as DCI format 1_1 in NR) (step 804). In this case, the DL-TCI or joint DCI indicates the reference RS (in this case, AP-CSI-RS) representing the selected DL TX beam (by the gNB / NW). Furthermore, the DL-TCI or joint DCI may also indicate the “target” RS (e.g., CSI-RS) linked to the reference RS (in this case, AP-CSI-RS). Upon successful decoding of the DL-related DCI with the DL-TCI or joint DCI, the UE selects the DL RX beam and performs DL reception (such as data reception via PDSCH) using the DL RX beam associated with the reference CSI-RS (step 805).
[0139] Alternatively, the gNB / NW can use a beamforming report to select a DL RX beam for the UE and use the DL-TCI field or the combined DCI field in a DL channel designed for beamforming purposes to indicate the DL RX beam selection to the UE (step 804). The DL channel designed for beamforming purposes can be UE-specific or for a group of UEs. In this case, the DL-TCI indicates the reference RS (in this case, AP-CSI-RS) representing the selected DL TX beam (by the gNB / NW). Furthermore, the DL-TCI or combined DCI may also indicate the “target” RS (e.g., CSI-RS) linked to the reference RS (in this case, AP-CSI-RS). Upon successful decoding of a DL channel designed for beamforming purposes with DL-TCI or combined DCI, the UE selects the DL RX beam and performs DL reception (such as data reception via PDSCH) using the DL RX beam associated with the reference CSI-RS (step 805).
[0140] For this implementation (A-1), as described above, the UE selects the DL RX beam based on the reference RS (in this case, AP-CSI-RS) index signaled via the DL-TCI field or the combined DCI field. In this case, the CSI-RS resource configured for the UE as a reference RS resource (or, generally, DL RS resources including CSI-RS, SSB, or a combination of both) can be linked to (associated with) a "beammetric" report, such as CRI / L1-RSRP or L1-SINR.
[0141] Figure 9 Another exemplary DL multi-beam operation 900 according to an embodiment of this disclosure is shown. Figure 9 The implementation of the DL multi-beam operation 900 shown is for illustrative purposes only.
[0142] exist Figure 9 In another example shown (Implementation A-2), DL multi-beam operation 900 begins with the transmission of an aperiodic SRS (AP-SRS) trigger or request signaling from the gNB / NW to the UE (step 901). This trigger may be included in a DCI (related to UL or DL). Upon receiving and decoding the AP-SRS trigger (step 902), the UE transmits the AP-SRS to the gNB / NW (step 903), enabling the NW (or gNB) to measure the UL propagation channel and select a DL RX beam for the UE for DL (assuming beam correspondence).
[0143] Then, the gNB / NW can use the DL-TCI field or the joint TCI field in the DL-related DCI (which carries DL authorization, such as DCI format 1_1 in NR) to indicate DL RX beam selection (step 904). In this case, the DL-TCI or joint TCI indicates the reference RS (in this case, AP-SRS) representing the selected DL RX beam. In addition, the DL-TCI or joint TCI may also indicate the “target” RS (e.g., CSI-RS) linked to the reference RS (in this case, AP-SRS). Upon successful decoding of the DL-related DCI with the DL-TCI or joint TCI, the UE performs DL reception (such as data reception via PDSCH) using the DL RX beam indicated by the DL-TCI or joint TCI (step 905).
[0144] Alternatively, the gNB / NW can use the DL-TCI field or the combined TCI field in a DL channel designed for beam indication purposes to indicate DL RX beam selection for the UE (step 904). The DL channel designed for beam indication purposes can be UE-specific or for a group of UEs. In this case, the DL-TCI or combined TCI indicates the reference RS (in this case, AP-SRS) of the selected DL RX beam. Furthermore, the DL-TCI or combined TCI may also indicate the “target” RS (e.g., CSI-RS) linked to the reference RS (in this case, AP-SRS). Upon successful decoding of a DL channel with DL-TCI or combined TCI designed for beam indication purposes, the UE performs DL reception (such as data reception via PDSCH) using the DL RX beam indicated by the DL-TCI or combined TCI (step 905).
[0145] In this implementation (A-2), the UE selects the DL RX beam based on the UL TX beam associated with the reference RS (AP-SRS) index that is signaled via the DL-TCI field or the combined TCI field.
[0146] Similarly, 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). The gNB selects the UL RX beam upon receiving and measuring the UL RS. As a result, a TX-RX beam pair is obtained. The NW / gNB can perform this operation (each reference RS or "beam scan") for all configured reference RSs and determine all TX-RX beam pairs associated with all reference RSs configured for the UE.
[0147] On the other hand, when a DL RS (such as CSI-RS and / or SSB) is used as a reference RS (which is relevant when DL-UL beam correspondence or reciprocity is established), the NW / gNB sends the RS to the UE (which corresponds to the UL RX beam for UL and reciprocity). 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, the UE can select the UL TX beam from the knowledge of all TX-RX beam pairs when it receives the reference RS (and therefore the UL RX beam) indication from the NW / gNB.
[0148] The following two implementations (B-1 and B-2) are examples of UL multi-beam operation using UL beam indication based on UL-TCI after the network (NW) has received some transmissions from the UE. In the first exemplary implementation (B-1), the aperiodic CSI-RS is transmitted by the NW and measured by the UE. This implementation can be used, for example, when reciprocity between the UL and DL beampair links (BPL) is met. This condition is referred to as the "UL-DL beam correspondence". In the second exemplary implementation (B-2), the aperiodic SRS is triggered by the NW and transmitted by the UE, allowing the NW (or gNB) to measure the UL channel quality to allocate the UL TX beam. This implementation can be used regardless of whether the UL-DL beam correspondence is met. Although aperiodic RS is used in these two examples, periodic or semi-persistent RS can also be used.
[0149] Figure 10 An exemplary UL multibeam operation 1000 according to an embodiment of this disclosure is shown. Figure 10 The embodiment of the UL multi-beam operation 1000 shown is for illustrative purposes only.
[0150] like Figure 10 As shown in Implementation B-1, UL multi-beam operation 1000 begins with the transmission of an aperiodic CSI-RS (AP-CSI-RS) trigger or indication signaling from the gNB / NW to the UE (step 1001). This trigger or indication may be included in a DCI (transmitted separately or together with an aperiodic CSI request / trigger, either UL-related or DL-related) and indicates that the AP-CSI-RS will be transmitted at the same (zero time offset) or later (time offset > 0). Upon receiving the AP-CSI-RS transmitted by the gNB / NW (step 1002), the UE measures the AP-CSI-RS and sequentially calculates and reports a "beam metric" (indicating the assumed quality of a specific TX beam) (step 1003). An example of such beam reporting is a CRI or SSB resource indicator (SSB-RI) associated with the associated L1-RSRP / L1-RSRQ / L1-SINR / CQI.
[0151] When a beam report is received from the UE, the gNB / NW can use the beam report to select a UL TX beam for the UE and indicate the UL TX beam selection using the UL-TCI field or the joint TCI field in the UL-related DCI (which carries UL authorization, such as DCI format 0_1 in NR) (step 1004). In this case, the UL-TCI indicates the reference RS (in this case, AP-CSI-RS) representing the selected UL TX beam (by the gNB / NW). Additionally, the UL-TCI may also indicate the “target” RS (e.g., SRS) linked to the reference RS (in this case, AP-CSI-RS). Upon successful decoding of the UL-related DCI with the UL-TCI or joint TCI, the UE selects the UL TX beam and performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam associated with the reference CSI-RS (step 1005).
[0152] Alternatively, the gNB / NW can use a beamforming report to select a UL TX beam for the UE and use the UL-TCI field or joint TCI field in a DL channel designed for beamforming purposes to indicate the UL TX beam selection to the UE (step 1004). The DL channel designed for beamforming purposes can be UE-specific or for a group of UEs. In this case, the UL-TCI or joint TCI indicates the reference RS (in this case, AP-CSI-RS) representing the UL RX beam selected (by the gNB / NW). Furthermore, the UL-TCI or joint TCI may also indicate the “target” RS (e.g., SRS) linked to the reference RS (in this case, AP-CSI-RS). Upon successful decoding of a DL channel designed for beamforming purposes with UL-TCI or joint TCI, the UE selects a UL TX beam and performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam associated with the reference CSI-RS (step 1005).
[0153] In this implementation (B-1), the UE selects the UL TX beam based on the derived DL RX beam, and the derived DL RX beam is associated with a reference RS index signaled via the UL-TCI field or a combined TCI field. In this case, the CSI-RS resource configured for the UE as a reference RS resource (or, generally, DLRS resources including CSI-RS, SSB, or a combination of both) can be linked to (associated with) a "beammetric" report, such as CRI / L1-RSRP or L1-SINR.
[0154] Figure 11 Another example of UL multi-beam operation 1100 according to an embodiment of this disclosure is shown. Figure 11The embodiment of the UL multi-beam operation 1100 shown is for illustrative purposes only.
[0155] like Figure 11 As shown in Embodiment B-2, the UL multi-beam operation 1100 begins with the transmission of an aperiodic SRS (AP-SRS) trigger or request signaling from the gNB / NW to the UE (step 1101). This trigger may be included in a DCI (UL-related or DL-related). Upon receiving and decoding the AP-SRS trigger (step 1102), the UE transmits the AP-SRS to the gNB / NW (step 1103), enabling the NW (or gNB) to measure the UL propagation channel and select the UL TX beam for the UE.
[0156] The gNB / NW can then use the UL-TCI field or the combined TCI field in the UL-related DCI (which carries UL authorization, such as DCI format 0_1 in NR) to indicate the UL TX beam selection (step 1104). In this case, the UL-TCI indicates the reference RS (in this case, AP-SRS) representing the selected UL TX beam. Additionally, the UL-TCI may also indicate the “target” RS (e.g., SRS) linked to the reference RS (in this case, AP-SRS). Upon successful decoding of the UL-related DCI with the UL-TCI or combined TCI, the UE performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam indicated by the UL-TCI or combined TCI (step 1105).
[0157] Alternatively, the gNB / NW may use the UL-TCI field or the combined TCI field in a DL channel designed for beam indication purposes to indicate UL TX beam selection for the UE (step 1104). The DL channel designed for beam indication purposes may be UE-specific or for a group of UEs. In this case, the UL-TCI or combined TCI indicates the reference RS (in this case, AP-SRS) of the selected UL TX beam. Furthermore, the UL-TCI or combined TCI may also indicate the “target” RS (e.g., SRS) linked to the reference RS (in this case, AP-SRS). Upon successful decoding of a DL channel with UL-TCI or combined TCI designed for beam indication purposes, the UE performs UL transmissions (such as data transmission on the PUSCH) using the UL TX beam indicated by the UL-TCI or combined TCI (step 1105).
[0158] In this implementation (B-2), the UE selects the UL TX beam based on the reference RS (in this case, SRS) index that is signaled via the UL-TCI field or the combined TCI field.
[0159] In the above exemplary embodiments, the DL and UL beam indicators are independent (separate), that is, the DL beam indicator is based on the DL-TCI indicator, while the UL beam indicator is based on the UL-TCI. A joint TCI that connects the DL and UL beam indicators (partially or entirely) is provided. An exemplary use case for the provided joint TCI indicator can be a system in which the UL-DL beam correspondence is established.
[0160] Beam indication can correspond to a TCI state, which indicates the target reference signal and one or more source reference signals, as well as the QCL type relative to each source reference signal. Beam indication can also correspond to an SRS resource index or spatial relation information.
[0161] After the NW / gNB has determined the channel conditions guaranteeing the use of one or more new beams, the beam indication channel is transmitted. Optionally or additionally, the beam indication channel may be transmitted to the UE periodically to indicate one or more beams that the UE can use.
[0162] Figure 12 An exemplary cell 1200 covered by N beams according to an embodiment of the present disclosure is shown. Figure 12 The embodiment shown, which covers 1200 cells with N beams, is for illustrative purposes only.
[0163] Figure 12 This is an example of a cell covered by N beams (1201 to 1208), each beam corresponding to a Synchronization Signal / PBCH Block (SSB) index, where the SSB index is transmitted using the spatial filter and / or TCI state of the corresponding beam. Each beam corresponding to an SSB can also be divided into narrower beams. For example, in Figure 12 In the example, beam 1201 corresponding to SSB0 corresponds to M narrow beams (1209 to 1211), M = 3.
[0164] Each narrow beam corresponds to a CSI-RS resource, which is transmitted using the narrow beam's spatial filter and / or TCI state. An association is established between reference signals (e.g., between the SSB and the CSI-RS resource) via the TCI state framework. This association is established with respect to a quasi-co-address (QCL) type, such as QCL-Type-D with respect to the spatial Rx parameter.
[0165] Figure 13 An exemplary TCI state configuration 1300 according to an embodiment of this disclosure is shown. Figure 13 The implementation of the TCI state configuration 1300 shown is for illustrative purposes only.
[0166] Figure 13This is an example of TCI state configuration according to 3GPP Release 15. The TCI state configuration table includes rows (1301, 1302, 1303) for each TCI state ID. Each row includes the TCI state ID (1304), QCL type 1 (1305), and optional QCL type 2 (1306). Each QCL type includes a source reference signal and a QCL-Type, where the QCL-Type can be Type-A, Type-B, Type-C, or Type-D. Each TCI state can have at most one QCL-Type-D. A reference signal can be associated with another reference signal via the TCI state ID. For example, in Figure 12 In this context, CSI-RS0-0 (1209) may include a TCI state with source resource signal SSB0 and QCL-Type-D.
[0167] exist Figure 12 In this structure, the beam corresponding to the SSB can be considered a Class 0 beam, and a narrower beam corresponding to the CSI-RS with a TCI state using the SSB as the source RS can be considered a Class 1 beam. A Class 1 beam can include multiple narrower beams, each corresponding to the CSI-RS and having a TCI state using a Class 1 CSI-RS as the source RS. These narrower beams can be considered Class 2 beams. This hierarchical beamforming structure can extend to more classes.
[0168] Figure 14 An exemplary layered beam structure 1400 according to an embodiment of the present disclosure is shown. Figure 14 The implementation of the layered beam structure 1400 shown is for illustrative purposes only.
[0169] like Figure 4 As shown, 1401 is the beam corresponding to SSB0, and beam 1401 includes two beams (1402 and 1403) corresponding to CSI-RS0-0 and CSI-RS0-1, respectively. Beams 1402 and 1403, corresponding to CSI-RS0-0 and CSI-RS0-1, are Level 1 CSI-RS beams. Beam 1402 includes two beams (1404 and 1405) corresponding to CSI-RS0-0 and CS-RS0-0-1, respectively. Similarly, beam 1403 includes two beams (1406 and 1407) corresponding to CSI-RS0-1-0 and CS-RS0-1-1, respectively. Beams 1404, 1405, 1406, and 1407, corresponding to CSI-RS0-0-0, CSI-RS0-0-1, CSI-RS0-1-0, and CSI-RS0-1-1, are level 2 CSI-RS beams. This layered beam structure can be extended to more levels.
[0170] The configuration of data or control channels in the downlink or uplink direction may include a TCI state relative to the source reference signal, which is QCL-Type-D. This can be achieved through methods such as... Figure 14 The layered beamforming structure shown can establish associations with SSB or lower-level CSI-RS resources.
[0171] The configuration of the beam indication channel can include the TCI state relative to the source reference signal, which is QCL-Type-D. This can be achieved through methods such as... Figure 14 The layered beamforming structure shown can establish an association with the SSB or a lower-level CSI-RS.
[0172] Figure 15 An exemplary relationship 1500 between the SSB and the beam indication channel according to an embodiment of this disclosure is shown. Figure 15 The exemplary implementation of the relationship 1500 between the SSB and the beam indication channel shown is for illustrative purposes only.
[0173] like Figure 15 As shown, 1501, 1504, and 1507 represent the transmission timings of SSB0. 1502, 1505, and 1508 represent the transmission timings of SSB1. 1503, 1506, and 1509 represent the transmission timings of SSB2. Beam indicator channels 1510 and 1513 associated with SSB0 can be frequency-division multiplexed with SSB0. Beam indicator channels 1511 and 1514 associated with SSB1 can be frequency-division multiplexed with SSB1. Beam indicator channels 1512 and 1515 associated with SSB2 can be frequency-division multiplexed with SSB2.
[0174] Figure 16 An exemplary relationship 1600 between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown. Figure 16 The implementation of the relationship between CORESET0 / search space 0 and beam indication channel 1600 shown is for illustrative purposes only.
[0175] like Figure 16As shown, 1601, 1604, and 1607 represent the monitoring timings of the Type 0-PDCCH CSS associated with SSB0. 1602, 1605, and 1608 represent the monitoring timings of the Type 0-PDCCH CSS associated with SSB1. 1603, 1606, and 1609 represent the monitoring timings of the Type 0-PDCCH CSS associated with SSB2. Beam indication channels 1610 and 1613 associated with SSB0 can be frequency-division multiplexed with the monitoring timings of the CORESET0 / Type 0-PDCCH CSS of SSB0. Beam indication channels 1611 and 1614 associated with SSB1 can be frequency-division multiplexed with the monitoring timings of the CORESET0 / Type 0-PDCCH CSS of SSB1. The beam indication channels 1612 and 1615 associated with SSB2 can be frequency-division multiplexed with the monitoring timing of the CORESET0 / Type0-PDCCH CSS of SSB2.
[0176] In one implementation, Type0-PDCCH CSS (public search space) can be search space 0.
[0177] Figure 17 Another exemplary relationship between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown. Figure 17 The implementation of the relationship between CORESET0 / search space 0 and beam indication channel 1700 shown is for illustrative purposes only.
[0178] like Figure 17 As shown, 1701 and 1704 represent monitoring times of the Type 0-PDCCH CSS associated with SSB0. 1702 and 1705 represent monitoring times of the Type 0-PDCCH CSS associated with SSB1. 1703 and 1706 represent monitoring times of the Type 0-PDCCH CSS associated with SSB2. Beam indication channels 1707 and 1710 associated with SSB0 can be in DCI format during the monitoring times of the CORESET0 / Type 0-PDCCH CSS of SSB0. Beam indication channels 1708 and 1711 associated with SSB1 can be in DCI format during the monitoring times of the CORESET0 / Type 0-PDCCH CSS of SSB1. Beam indication channels 1709 and 1712 associated with SSB2 can be in DCI format during the monitoring times of the CORESET0 / Type 0-PDCCH CSS of SSB2.
[0179] Figure 18Another exemplary relationship 1800 between CORESET0 / search space 0 and beam indication channel according to an embodiment of this disclosure is shown. Figure 18 The implementation of the relationship between CORESET0 / search space 0 and beam indication channel 1800 shown is for illustrative purposes only.
[0180] like Figure 18 As shown, 1801 represents the monitoring timing of the Type 0-PDCCH CSS associated with SSB0. 1802 represents the monitoring timing of the Type 0-PDCCH CSS associated with SSB1. 1803 represents the monitoring timing of the Type 0-PDCCH CSS associated with SSB2. The beam indication channel 1807 associated with SSB0 can be a PDSCH transmission scheduled by DCI format 1804 in the monitoring timing of the CORESET0 / Type 0-PDCCH CSS of SSB0. The beam indication channel 1808 associated with SSB1 can be a PDSCH transmission scheduled by DCI format 1805 in the monitoring timing of the CORESET0 / Type 0-PDCCH CSS of SSB1. The beam indication channel 1809 associated with SSB2 can be a PDSCH transmission scheduled by DCI format 1806 in the monitoring timing of the CORESET0 / Type 0-PDCCH CSS of SSB2.
[0181] Figure 19 An exemplary relationship 1900 between CSI-RS and beam indication channel according to an embodiment of this disclosure is shown. Figure 19 The implementation of the relationship between CSI-RS and beam indication channel 1900 shown is for illustrative purposes only.
[0182] like Figure 19 As shown, 1901, 1904, and 1907 represent the transmission timings of CSI-RS resource 0. 1902, 1905, and 1908 represent the transmission timings of CSI-RS resource 1. 1903, 1906, and 1909 represent the transmission timings of CSI-RS resource 2. Beam indicator channels 1910 and 1913 associated with CSI-RS resource 0 can be frequency-division multiplexed with CSI-RS resource 0. Beam indicator channels 1911 and 1914 associated with CSI-RS resource 1 can be frequency-division multiplexed with CSI-RS resource 1. Beam indicator channels 1912 and 1915 associated with CSI-RS resource 2 can be frequency-division multiplexed with CSI-RS resource 2.
[0183] In one implementation, an SSB-based beam is provided for beam indication.
[0184] The beam indication channel can be transmitted using the corresponding synchronization signal / PBCH block (SSB) spatial filter and / or TCI state.
[0185] In one example, the gNB can use the beam indication channel corresponding to the SSB with beam indication of QCL-Type-D to transmit beam indication.
[0186] In one example, the gNB can use the beam indication channel corresponding to the SSB with beam indication of QCL-Type-D to transmit beam indication. In this example, beam indication can correspond to multiple beams, for example in the case of multiple TRPs / multiple panels, or in the case of using more than one beam for transmission in a divergent multipath environment.
[0187] In one example, the gNB can use a beam indication channel corresponding to a set of SSBs in the overall direction of the UE to transmit beam indication.
[0188] In one example, the gNB can use the beam indication channel corresponding to all SSBs of the cell to send beam indication.
[0189] In one example, the UE monitors beam indicator channels for SSBs whose RSRP exceeds a configured or pre-configured threshold.
[0190] In one example, the UE monitors beam indicator channels for all SSBs whose RSRP exceeds a configured or pre-configured threshold.
[0191] In one implementation, a CSI-RS-based beam is provided for beam indication.
[0192] The gNB is configured with one or more periodic CSI-RS resource sets that can be used for beam management. The spatial filters and / or TCI states of the corresponding CSI-RS resources can be used to transmit beam indication channels.
[0193] In one example, the gNB can use the beam indication channel corresponding to the CSI-RS resource with beam indication of QCL-Type-D to transmit beam indication.
[0194] In one example, the gNB can use the beam indication channel corresponding to a CSI-RS resource with beam indication of QCL-Type-D to transmit beam indication. In this example, beam indication can correspond to multiple beams, for example in the case of multiple TRPs / multiple panels, or in the case of using more than one beam for transmission in a divergent multipath environment.
[0195] In one example, the gNB can use a beam indication channel corresponding to a set of SSBs in the overall direction of the UE to transmit beam indication.
[0196] In one example, the gNB can use the beam indication channel corresponding to all CSI-RS resources in the CSI-RS resource set to transmit beam indication.
[0197] In one example, the gNB may use the beam indication channel corresponding to all (or some) of the CSI-RS resources in the CSI-RS resource set to transmit beam indication, wherein the CSI-RS resource set includes CSI-RS with beam indication of QCL-Type-D.
[0198] In one example, the gNB can use the beam indication channel corresponding to all CSI-RS resources in all CSI-RS resource sets of the cell to transmit beam indication.
[0199] In one example, the UE monitors beam indicator channels of CSI-RS resources where RSRP exceeds a configured or pre-configured threshold.
[0200] In one example, the UE monitors the beam indication channels of all CSI-RS resources in a CSI-RS resource set whose RSRP exceeds a configured or pre-configured threshold.
[0201] In one example, the UE monitors the beam indication channels of all CSI-RS resources in all CSI-RS resource sets whose RSRP exceeds a configured threshold or a pre-configured threshold.
[0202] In one example, the gNB can activate or disable CSI-RS resources and / or CSI-RS resource sets via MAC CE signaling.
[0203] In one example, the gNB can activate or disable CSI-RS resources and / or CSI-RS resource sets via L1 signaling.
[0204] In one example, the gNB configures or reconfigures CSI-RS resources and / or CSI-RS resource sets via higher-level RRC signaling.
[0205] In one example, a CSI-RS resource can be a semi-persistent CSI-RS resource.
[0206] In one implementation, an SSB-based CSI-RS-based beam is provided for beam indication.
[0207] The gNB is configured with one or more periodic CSI-RS resource sets that can be used for beam management. The spatial filter and / or TCI state of the corresponding SSB or CSI-RS resource can be used to transmit the beam indication channel. The embodiments / examples described in this disclosure can be combined with and applied to the other embodiments.
[0208] In one implementation, transmission resources for a beam indication channel are provided.
[0209] In one example, the beam indication channel is frequency-division multiplexed with the SSB corresponding to the indicated beam. This is in Figure 15 The example is shown.
[0210] In one example, the beam indicator channel can occupy some symbols of the SSB.
[0211] In one example, the beam indicator channel can occupy all symbols of the SSB.
[0212] In one example, the beam indicator can occupy other symbols not occupied by the SSB.
[0213] In one example, the beam indication channel is frequency-division multiplexed with the SSB (Service Sub-Side) of QCL-Type-D CSI-RS resource corresponding to the indicated beam. The association between the SSB and the CSI-RS resource can be achieved through, for example... Figure 14 The hierarchical relationship shown is used to establish this.
[0214] In one example, the beam indicator channel can occupy some symbols of the SSB.
[0215] In one example, the beam indicator channel can occupy all symbols of the SSB.
[0216] In one example, the beam indicator can occupy other symbols not occupied by the SSB.
[0217] In one example, the beam indication channel is frequency-division multiplexed with the CSI-RS resource corresponding to the indicated beam. This is in Figure 19 The example is shown.
[0218] In one example, the beam indicator channel may occupy some symbols of CSI-RS resources.
[0219] In one example, the beam indicator channel can occupy all symbols of the CSI-RS resource.
[0220] In one example, the beam indicator can occupy other symbols not occupied by CSI-RS resources.
[0221] In one example, the beam indication channel and the CSI-RS resource corresponding to the indicated beam are frequency-division multiplexed with a QCL-Type-D CSI-RS resource. The association between the two CSI-RS resources can be achieved through methods such as... Figure 12 The hierarchical relationship shown is used to establish this.
[0222] In one example, the beam indicator channel may occupy some symbols of CSI-RS resources.
[0223] In one example, the beam indicator channel can occupy all symbols of the CSI-RS resource.
[0224] In one example, the beam indicator can occupy other symbols not occupied by CSI-RS resources.
[0225] In one example of this disclosure and in the example described herein, the beam indication channel is transmitted every Nth occurrence of a candidate resource. Here, N is an integer equal to or greater than 1. Figure 15 As shown, the beam indicator channel is transmitted at every second timing of the SSB index, in this example N = 2.
[0226] In one example, the beam indication channel is frequency-division multiplexed with CORESET 0 and search space 0 in the SSB corresponding to the indicated beam. This is in Figure 16 As shown in the diagram, the timing overlap between the beam indication channel and the monitoring timing of CORESET 0 can be complete or partial.
[0227] In one example, the beam indication channel is frequency-division multiplexed with CORESET 0 and search space 0 in the SSB of a QCL-Type-D CSI-RS resource corresponding to the indicated beam. The association between the SSB and the CSI-RS resource can be achieved through methods such as... Figure 12 The hierarchical relationship shown is used to establish the beam indication channel. The timing overlap between the beam indication channel and the monitoring timing of CORESET 0 can be complete or partial.
[0228] In one example of this disclosure and in the example described herein, the beam indication channel is transmitted every Nth occurrence of a candidate resource. Here, N is an integer equal to or greater than 1. Figure 16 As shown, the beam indicator channel is transmitted at every second timing in the CORESET 0 monitoring timing associated with the SSB index, in this example N = 2.
[0229] In one example, the beam indication channels are CORESET0 in the corresponding SSB and the PDCCH channel with DCI format in search space 0. This is in Figure 17 As shown in the image.
[0230] In one example, the beam indication channel is CORESET0 in the SSB and the PDCCH channel with DCI format in search space 0. The SSB and the CSI-RS resource corresponding to the indicated beam are QCL-Type-D. The association between the SSB and the CSI-RS resource can be achieved through, for example... Figure 14 The hierarchical relationship shown is used to establish this.
[0231] In one example of this disclosure and in the examples described herein, CORESET can be a CORESET configured for beam indication, and / or the search space can be a search space configured for beam indication.
[0232] In one example of this disclosure and in the examples described herein, the CORESET may be a public CORESET or a UE-specific CORESET, and / or the search space may be a public search space or a UE-specific search space.
[0233] In one example of this disclosure and in the example described herein, the beam indication channel is transmitted every Nth occurrence of a candidate resource, where N is an integer equal to or greater than 1.
[0234] In one example, the beam indication channel is a PDCCH channel in DCI format within the CORESET and search space, which is configured and associated with the corresponding CSI-RS used for beam indication.
[0235] In one example, the beam indication channel is a DCI-formatted PDCCH channel in the CORESET and search space. The CORESET and search space are configured and associated with a CSI-RS used for beam indication, and this CSI-RS is QCL-Type-D, corresponding to the CSI-RS of the indicated beam. The association between two CSI-RS resources can be achieved through methods such as... Figure 14 The hierarchical relationship shown is used to establish this.
[0236] In one example of this disclosure and in the example described herein, CORESET can be CORESET 0.
[0237] In one example of this disclosure and in the examples described herein, the search space may be search space 0.
[0238] In one example of this disclosure and in the examples described herein, the CORESET may be a public CORESET or a UE-specific CORESET, and / or the search space may be a public search space or a UE-specific search space.
[0239] In one example of this disclosure and in the example described herein, the beam indication channel is transmitted every Nth occurrence of the candidate resource, where N is an integer equal to or greater than 1.
[0240] In one example, CORESET can be configured for a group of UEs.
[0241] In one example, the search space can be configured for a set of UEs.
[0242] In one example, CORESET can be configured based on association with multiple SSBs and / or multiple CSI-RS resources.
[0243] In one example, the search space can be configured based on associations with multiple SSBs and / or multiple CSI-RS resources.
[0244] In one example, the beam indication channel is a PDSCH channel scheduled by CORESET 0 in the SSB corresponding to the indicated beam and the DCI format in search space 0. This is in Figure 18 The example is shown.
[0245] In one example, the beam indication channel is a PDSCH channel scheduled in CORESET0 of the SSB and DCI format in search space 0. The SSB and the CSI-RS resource corresponding to the indicated beam are QCL-Type-D. The association between the SSB and the CSI-RS resource can be achieved through, for example... Figure 14 The hierarchical relationship shown is used to establish this.
[0246] In one example of this disclosure and in the examples described herein, the CORESET may be a CORESET configured for beam indication, and / or the search space may be a search space configured for beam indication.
[0247] In one example of this disclosure and in the examples described herein, the CORESET may be a public CORESET or a UE-specific CORESET, and / or the search space may be a public search space or a UE-specific search space.
[0248] In one example of this disclosure and in the example described herein, the beam indication channel is transmitted every Nth occurrence of the candidate resource, where N is an integer equal to or greater than 1.
[0249] In one example, the beam indication channel is a PDSCH channel scheduled in DCI format in the CORESET and search space, which is configured and associated with the corresponding CSI-RS used for beam indication.
[0250] In one example, the beam indication channel is a PDSCH channel scheduled in DCI format within a CORESET and search space. This CORESET and search space are configured and associated with a CSI-RS used for beam indication, wherein the CSI-RS corresponding to the indicated beam is QCL-Type-D. The association between two CSI-RS resources can be achieved through methods such as... Figure 14 The hierarchical relationship shown is used to establish this.
[0251] In one example, the beam indication may be included in the remaining minimal system information (RMSI), also known as SIB1.
[0252] In one implementation, timing of the beam indication channel is provided.
[0253] In one example, the beam indication channel for a UE and / or a group of UEs can be triggered by an event when the gNB determines that a new beam is available for communication with the UE.
[0254] In one example, the beam indication channel for a UE and / or a group of UEs may be periodically transmitted on configured time, frequency and / or code resources.
[0255] In one example, the beam indication channel for a UE and / or a group of UEs can be periodically transmitted on configured time, frequency and / or code resources, and the beam indication channel can also be triggered by an event when the gNB determines that a new beam is available for communication with the UE.
[0256] In one example, periodic beam indication and event-triggered beam indication are transmitted on the same set of beam indication channels corresponding to SSB and / or CSI-RS resources.
[0257] In one example, periodic beam indication and event-triggered beam indication are transmitted on different groups of beam indication channels corresponding to SSB and / or CSI-RS resources.
[0258] In one implementation, the payload and resources of the beam indication channel are provided.
[0259] In one example, the beam indicator channel is UE-specific.
[0260] In one example, the beam indication channel includes DL TCI status.
[0261] In one example, the beam indicator channel includes UL TCI status.
[0262] In one example, the beam indication channel includes DL TCI state and / or UL TCI state and / or combined TCI state.
[0263] In one example, the beam indicates that the channel is transmitted on UE-specific time and / or frequency and / or code resources.
[0264] In one example, the beam indication channel has a CRC scrambled by the UE-specific radio network temporary identifier (RNTI).
[0265] In one example, the beam indication channel is a PDCCH channel with DCI format.
[0266] In one example, the beam indicator channel includes the UE ID.
[0267] In one example, the beam indication channel has a CRC scrambled by the beam indication RNTI.
[0268] In one example, a channel transmitting beam indication (e.g., TCI status or spatial relationship indication) is reused for scheduling PDSCH in DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2), and / or reused for scheduling PUSCH in DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2), wherein the corresponding DCI format does not include DL allocation or UL authorization.
[0269] In one example, the CRC of the DCI format for transmit beam indication is scrambled by a UE-specific RNTI (such as C-RNTI, CS-RNTI, or MCS-C-RNTI), and this DCI format has no DL assignment and no UL authorization.
[0270] In one example, the CRC of the DCI format for transmitting beam indication is scrambled by the UE-specific RNTI used for beam indication, and the DCI format has no DL allocation and no UL authorization.
[0271] In one example, the CRC of the DCI format for transmitting beam indication is scrambled by a UE group-specific RNTI for beam indication, and the DCI format has no DL allocation and no UL authorization.
[0272] In one example, some bits or fields in the DCI format are set to predetermined values to indicate a DCI format for beam indication without DL allocation or UL authorization. For example, for DCI format 1_1 or DCI format 1_2, the frequency domain resource allocation field may be set to: (1) all 0 for resource allocation type 0; (2) all 1 for resource allocation type 1; and / or (3) all 1 or all 0 in the case of resource allocation for dynamically switched types.
[0273] The remaining bits or fields in the DCI format can be reused for TCI status indication, for example, to indicate one or more of the following: (1) DL TCI status; (2) UL TCI status; (3) combined UL / DL TCI status; and / or (4) separate DL TCI status and UL TCI status.
[0274] After indicating one or more TCI states, if there are remaining bits or fields in the DCI format, these bits can be one of the following: (1) reserved, for example for future use; (2) set to a predetermined value; and / or (3) a combination of some reserved bits and some bits set to predetermined values.
[0275] Figure 20 An exemplary component 2000 of the DCI format according to an embodiment of this disclosure is shown. Figure 20 The implementation of the components of DCI Format 2000 shown is for illustrative purposes only.
[0276] Figure 20 Examples of components of a DCI format (e.g., DCI format 1_0, 1_1, 1_2, 0_0, 0_1, or 0_2) used for transmitting beam indication without DL allocation and UL authorization. Components of a DCI format may include: (1) one or more fields or bits having specific values indicating a DCI format used for beam indication without DL allocation and UL authorization; (2) one or more beam indicators (e.g., TCI status or spatial relationship indicators); (3) reserved and / or remaining fields or bits set to predetermined values; and / or (4) a CRC having some or all of its bits scrambled by a UE-specific RNTI.
[0277] In one example, a field is added to the DCI format indicating whether the DCI format indicates one or more TCI states without DL allocation or UL authorization, or whether the DCI format is used to schedule PDSCH or PUSCH or other uses as described in the specification (e.g., SPS release, UL authorization type 2 release, SCell hibernation). If the field indicates that beam indication is being transmitted in a DCI format without DL allocation or UL authorization (e.g., TCI state or spatial relationship indication), the remaining bits or fields in the DCI format may be reused for TCI state indication, such as indicating one or more of the following: (1) DL TCI state; (2) UL TCI state; (3) combined UL / DL TCI state; and / or (4) separate DL TCI state and UL TCI state.
[0278] After indicating one or more TCI states, if there are remaining bits or fields in the DCI format, these bits can be one of the following: reserved, for example for future use; set to a predetermined value; and / or a combination of some reserved bits and some bits set to predetermined values.
[0279] Figure 21 Another exemplary component 2100 illustrating the DCI format according to an embodiment of this disclosure is shown. Figure 21The implementation of component 2100 of the DCI format shown is for illustrative purposes only.
[0280] Figure 21 Examples are components of a DCI format (e.g., DCI format 1_0, 1_1, 1_2, 0_0, 0_1, or 0_2) used for transmitting beam indication without DL assignment and UL authorization.
[0281] The components of a DCI format may include: (1) a marker indicating a DCI format for beam indication without DL allocation or UL authorization (e.g., if the marker does not indicate a DCI format for beam indication without DL allocation or UL authorization, the remaining fields or bits are as defined for the corresponding DCI format. Otherwise, if the DCI format is for beam indication without DL allocation or UL authorization, the remaining fields or bits may be defined as described below); (2) one or more beam indicators (e.g., TCI status or spatial relationship indicators); (3) reserved and / or remaining fields or bits set to predetermined values; and / or (4) a CRC with some or all of the bits scrambled by a UE-specific RNTI.
[0282] In one example, the UE may send a HARQ-ACK feedback (e.g., on the PUCCH, or on the PUSCH if the PUCCH overlaps with the PUSCH) in response to a DCI format without DL allocation or UL authorization for a transmit beam indication (e.g., TCI status or spatial relationship indication).
[0283] In one example, a channel transmitting beam indication (e.g., TCI status or spatial relationship indication) is reused for scheduling PDSCH in a DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) and / or reused for scheduling PUSCH in a DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2), wherein the corresponding DCI format includes DL allocation for pseudo data (e.g., pseudo PDSCH) or UL authorization for pseudo data (e.g., pseudo PUSCH).
[0284] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB does not send PDSCH, the UE does not attempt to decode PDSCH, and it is assumed that a positive HARQ_ACK is indicated to the gNB.
[0285] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB does not send PDSCH, the UE does not attempt to decode PDSCH, and it is assumed that a negative HARQ_ACK is indicated to the gNB.
[0286] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB does not send PDSCH. The UE attempts to decode the PDSCH, generates HARQ_ACK feedback based on the decoding result, and indicates the HARQ_ACK status to the gNB.
[0287] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB sends the PDSCH, the UE does not attempt to decode the PDSCH and assumes to indicate a positive HARQ_ACK to the gNB.
[0288] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB sends the PDSCH, the UE does not attempt to decode the PDSCH and assumes to indicate a negative HARQ_ACK to the gNB.
[0289] In one example, the DCI format used for scheduling PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation for pseudo data, and the gNB sends PDSCH, the UE attempts to decode PDSCH, generates HARQ_ACK feedback based on the decoding result, and indicates the HARQ_ACK status to the gNB.
[0290] In one example, the DCI format used to schedule PUSCH (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) includes UL authorization for pseudo data, and the UE does not send PUSCH.
[0291] In one example, the UE may send a HARQ-ACK feedback in response to the DCI format (e.g., on the PUCCH, or on the PUSCH if the PUCCH and PUSCH overlap).
[0292] In one example, the DCI format used for scheduling the PUSCH (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) includes a UL authorization for pseudo data, and the UE transmits the PUSCH. In one instance, the UE may transmit a HARQ-ACK feedback in response to the DCI format (e.g., on the PUCCH, or on the PUSCH if the PUCCH and PUSCH overlap). In another instance, the UE may respond to the DCI format without transmitting a HARQ-ACK feedback.
[0293] In one example, the CRC of the DCI format used for transmitting beam indication, which has DL allocation for pseudo data or UL authorization, is scrambled by the UE-specific RNTI (e.g., C-RNTI, CS-RNTI, or MCS-C-RNTI).
[0294] In one instance, the CRC in DCI format used for transmitting beam indication, which has DL allocation or UL authorization for pseudo data, is scrambled by the UE-specific RNTI used for beam indication.
[0295] In one example, certain bits or fields of the DCI format are set to predetermined values that indicate whether the DCI format includes DL allocation or UL authorization for pseudo data. For example, a combination of specific values for the HARQ-ID and / or New Data Indicator and / or MCS and / or PUCCH Resource Indicator and / or PDSCH to HARQ Feedback Timing Indicator can indicate that DL allocation or UL authorization is for pseudo data.
[0296] In one example, a field is added to the DCI format that indicates whether the DCI format includes DL assignment or UL authorization for pseudo data.
[0297] In one example, the DCI format used for scheduling the PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation, and the gNB transmits the PDSCH. The PDSCH includes a DL shared channel with a specific positioning mode (e.g., 0xAAAa...) that indicates to the UE that this is negligible pseudo data.
[0298] In one example, the DCI format used to schedule the PDSCH (e.g., DCI format 1_0, DCI format 1_1, or DCI format 1_2) includes DL allocation, and the gNB transmits the PDSCH. The PDSCH includes a MAC CE that indicates to the UE that this is a dummy PDSCH that can be ignored.
[0299] In one example, the DCI format used to schedule the PUSCH (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) includes UL authorization for pseudo data, and the UE transmits the PUSCH. The PUSCH includes a UL shared channel with a specific positioning mode (e.g., 0xAAAa...).
[0300] In one example, the DCI format used to schedule the PUSCH (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) includes a UL authorization for pseudo data, and the UE transmits the PUSCH. The PUSCH includes a MACCE for pseudo PUSCH transmission.
[0301] In one example, the beam indication channel is for a group of UEs.
[0302] In one example, the beam indicator channel includes the DL TCI status of one or more UEs in the group.
[0303] In one example, the beam indication channel includes the UL TCI status of one or more UEs in the group.
[0304] In one example, the beam indication channel includes the DL TCI state and / or ULTCI state and / or combined TCI state of one or more UEs in the group.
[0305] In one example, the UE ID of the DL TCI state and / or UL TCI state and / or combined TCI state is determined based on the order of the DL TCI state and / or UL TCI state and / or combined TCI state in the payload of the beam indication channel.
[0306] In one example, the beam indication channel includes the UE IDs of one or more UEs in the group.
[0307] In one example, the beam indicates that the channel is transmitted on UE-group-specific time and / or frequency and / or code resources.
[0308] In one example, the beam indicator channel has a CRC scrambled by a UE group-specific RNTI.
[0309] In one example, the beam indication channel is a PDCCH channel with DCI format.
[0310] In one example, the beam indicator channel includes the UE group ID.
[0311] In one example, the beam indication channel has a CRC scrambled by the beam indication RNTI.
[0312] In one example, the beam indicator channel is for the UE in the cell.
[0313] In one example, the beam indication channel includes the DL TCI status of one or more UEs in the cell.
[0314] In one example, the beam indication channel includes the UL TCI status of one or more UEs in the cell.
[0315] In one example, the beam indication channel includes the DL TCI state and / or ULTCI state and / or combined TCI state of one or more UEs in the cell.
[0316] In one example, the UE ID of the DL TCI state and / or UL TCI state and / or combined TCI state is determined based on the order of the DL TCI state and / or UL TCI state and / or combined TCI state in the payload of the beam indication channel.
[0317] In one example, the beam indication channel includes the UE IDs of one or more UEs in the cell.
[0318] In one example, the UE ID for the DL TCI state and / or UL TCI state and / or combined TCI state is determined based on the time and / or frequency and / or code resources of the beam indication channel.
[0319] In one example, the beam indication channel has a CRC scrambled by the beam indication RNTI.
[0320] In one example, the beam indication channel is a PDCCH channel with DCI format.
[0321] In one example, the beam indication channel is for a UE within a portion of the cell.
[0322] In one example, the beam indication channel includes the DL TCI status of one or more UEs within a portion of the cell.
[0323] In one example, the beam indication channel includes the UL TCI status of one or more UEs within a portion of the cell.
[0324] In one example, the beam indication channel includes the DL TCI status and / or UL TCI status and / or combined TCI status of one or more UEs in a portion of the cell.
[0325] In one example, the UE ID of the DL TCI state and / or UL TCI state and / or combined TCI state is determined based on the order of the DL TCI state and / or UL TCI state and / or combined TCI state in the payload of the beam indication channel.
[0326] In one example, the beam indication channel includes the UE IDs of one or more UEs within a portion of the cell.
[0327] In one example, the UE ID of the DL TCI state and / or UL TCI state and / or joint TCI state is determined based on the time and / or frequency and / or code resources of the beam indication channel.
[0328] In one example, the beam indication channel has a CRC scrambled by the beam indication RNTI.
[0329] In one example, the beam indication channel is a PDCCH channel with DCI format.
[0330] In one example, the beam indication channel has a CRC scrambled by the cell area-specific beam indication RNTI.
[0331] In one implementation, a channel structure for a beam indication channel is provided.
[0332] In one example, the payload encoding of the beam indication channel follows the polar coding of the NR control channel as described in LTE standard specification 38.212.
[0333] In one example, Polar encoding is used when the payload is greater than 11 bits.
[0334] In one example, the CRC is appended to or pre-added to the payload.
[0335] In one example, the CRC, or a portion thereof, is scrambled by RNTI.
[0336] In one example, the encoding of the beam-indicating payload follows a block-length encoding as described in TS 38.212, which uses the basic sequence provided in TS 38.212.
[0337] In one example, when the payload is between 3 and 11 bits, small block length encoding is used.
[0338] In one example, no CRC is added to the payload before encoding.
[0339] In one example, the beam indication channel is a pseudo-random sequence transmitted in one or more PRBs transmitted on one or more symbols.
[0340] In one example, the payload, or a portion of the payload, is used to initialize a pseudo-random sequence.
[0341] In one example, the payload, or a portion of the payload, is used to determine the frequency comb. For instance, a pseudo-random sequence is transmitted every other subcarrier, and one bit is used to determine whether the comb is even or odd; or a pseudo-random sequence is transmitted every four subcarriers, and two bits are used to determine the comb.
[0342] In one example, the payload, or a portion of the payload, is used to determine the frequency domain orthogonal code coverage.
[0343] In one example, the payload, or a portion thereof, is used to determine the time-domain orthogonal code coverage.
[0344] In one example, the payload, or a portion of the payload, is used to determine the time-domain symbol.
[0345] In one example, the payload, or a portion of the payload, is used to determine the frequency domain PRB.
[0346] In one example, some or all of the examples described in this disclosure may be used.
[0347] In one implementation, activation timing for the beam indication channel is provided.
[0348] In one example, the beam indicated by the beam indication channel is activated after a time specified in the specification elapses from the beam indication channel.
[0349] In one example, after a specified time elapsed from the beam indication channel, the beam indicated by the beam indication channel is activated based on the UE capability.
[0350] In one example, the beam indicated by the beam indication channel is activated after a time configured by the higher layers, starting from the beam indication channel.
[0351] In one example, the beam indicated by the beam indication channel is activated after a time depending on the subcarrier spacing, starting from the beam indication channel. The subcarrier spacing can be the subcarrier spacing of the channel transmitting the beam indication, the subcarrier spacing of the active bandwidth portion, the subcarrier spacing of the active DL bandwidth portion, the subcarrier spacing of the active UL bandwidth portion, the subcarrier spacing of the bandwidth portion to which the beam indication is applied, the subcarrier spacing of the DL bandwidth portion to which the beam indication is applied, the subcarrier spacing of the UL bandwidth portion to which the beam indication is applied, the subcarrier spacing of one or more channels to which the beam indication is applied, or the subcarrier spacing is determined based on previously mentioned subcarrier spacings (e.g., the minimum or maximum subcarrier spacing among some or all of the previously mentioned subcarrier spacing values).
[0352] In one example, the configured time is to use cell public signaling to send a signal notification.
[0353] In one example, the configured time is to use UE-specific signaling to send a signal notification.
[0354] In one example, the configured time uses UE group-specific signaling to send a signal notification.
[0355] In one example, the configured time depends on one or more of the subcarrier spacing, the value specified in the specification, the signaling value, and the UE capability.
[0356] In one example, the UE sends a positive acknowledgment after receiving the beam indication channel.
[0357] In one example, the UE sends a positive acknowledgment after receiving a beam indication channel with a new beam.
[0358] In one example, the gNB receives / monitors a channel with beam-indicating channel acknowledgments.
[0359] In one example, the beam indicated by the beam indication channel is activated after a time specified in the specification has elapsed since the confirmation from the beam indication channel.
[0360] In one example, after a time specified in the specification has elapsed since the beam indication channel was confirmed, the beam indicated by the beam indication channel is activated based on the UE capability.
[0361] In one example, the beam indicated by the beam indication channel is activated after a time configured by the higher layer has elapsed since the confirmation from the beam indication channel.
[0362] In one example, the beam indicated by the beam indication channel is activated after a time depending on the subcarrier spacing elapsed since confirmation from the beam indication channel. The subcarrier spacing can be the subcarrier spacing of the channel transmitting the beam indication, the subcarrier spacing of the active bandwidth portion, the subcarrier spacing of the active DL bandwidth portion, the subcarrier spacing of the active UL bandwidth portion, the subcarrier spacing of the bandwidth portion to which the beam indication is applied, the subcarrier spacing of the DL bandwidth portion to which the beam indication is applied, the subcarrier spacing of the UL bandwidth portion to which the beam indication is applied, the subcarrier spacing of one or more channels to which the beam indication is applied, or the subcarrier spacing is determined based on previously mentioned subcarrier spacings (e.g., the minimum or maximum subcarrier spacing among some or all of the previously mentioned subcarrier spacing values).
[0363] In one example, the configured time is to use cell public signaling to send a signal notification.
[0364] In one example, the configured time is to use UE-specific signaling to send a signal notification.
[0365] In one example, the configured time uses UE group-specific signaling to send a signal notification.
[0366] In one example, the configured timing depends on one or more of the following: subcarrier spacing, values specified in the specification, signaling notification values, and UE capabilities.
[0367] This disclosure provides further aspects to enhance the operational efficiency of beam indication by using two-level or two-part beam indication. Two-level / two-part beam indication includes a first-level / partial beam indication and a second-level / partial beam indication. The first-level / partial beam indication may be carried by a first channel having a light payload signal (e.g., based on the number of payload bits) with potentially lower processing requirements, indicating to one or more UEs within a group whether beam indication information for one or more UEs is included in the second-level / partial beam indication carried by the second channel. Furthermore, since the first-level / partial beam indication carried by the first channel is a light payload signal, it can be transmitted on a wider beam than the second-level / partial beam indication carried by the second channel, wherein the beam for the second-level beam indication channel may be included in the first-level beam indication channel.
[0368] This disclosure provides a two-level beam indication. The two-level beam indication includes a first-level beam indication carried on a first channel or signal, and a second-level beam indication carried on a second channel or signal. The first-level beam indication carried on the first channel is a lightweight payload signal with potentially low processing requirements, indicating to one or more UEs within a group of UEs whether the beam indication information of one or more UEs is included in the second-level beam indication carried on the second channel. Furthermore, since the first-level beam indication carried on the first channel is a lightweight payload signal, it can be transmitted on a wider beam than the second-level beam indication carried on the second channel, wherein the beam used for the second-level beam indication channel can be included in the first-level beam indication channel.
[0369] Figure 22 An exemplary two-stage beam indication 2200 according to an embodiment of the present disclosure is shown. Figure 22 The embodiment of the two-stage beam indicator 2200 shown is for illustrative purposes only.
[0370] like Figure 22 As shown, the beam indication (2201) may include two levels / parts: a first-level / part beam indication (2202) and a second-level beam indication (2203). The beam indication can be signaled using channels / signals, one channel for the first-level / part beam indication and a second channel for the second-level / part beam indication. In one example, the second-level beam indication may not exist. When the second-level beam indication is absent, the Tx beam remains unchanged and is either the same as the last reported Tx beam (e.g., indicated via the last reported second-level beam indication) or the same as the Tx beam corresponding to the default beam.
[0371] In one implementation, a beam pointing structure is provided.
[0372] In one example, the beam indication is always two levels / two parts.
[0373] In one example, (1) based on fixed conditions; for example, depending on UE speed, location, etc.; (2) based on configuration (e.g., implicitly using another parameter or explicitly using a separate parameter via higher-layer RRC signaling); and / or (3) based on dynamic configuration updates (e.g., implicitly using another parameter or explicitly using a separate parameter via MAC layer signaling, or implicitly using another parameter or explicitly using a separate parameter via physical layer control signaling), the beam indication is level 1 / partial or level 2 / partial.
[0374] In one example, the first-level / partial beam indication and the corresponding second-level / partial beam indication channels can be performed sequentially in time.
[0375] In one example, the physical channel carrying the first-level / partial beam indication may begin before the corresponding physical channel carrying the second-level / partial beam indication, wherein the physical channels of the first-level / partial beam indication channel and the corresponding physical channels of the second-level / partial beam indication do not overlap in time.
[0376] In one example, the physical channel carrying the first-level / partial beam indication may begin before the corresponding physical channel carrying the second-level / partial beam indication, wherein the physical channel carrying the first-level / partial beam indication and the corresponding physical channel carrying the second-level / partial beam indication partially overlap in time.
[0377] In one example, the first-level / partial beam indication and the corresponding second-level / partial beam indication can be transmitted in parallel, for example, on different frequency resources.
[0378] In one example, the physical channel carrying the first-level / partial beam indication and the corresponding physical channel carrying the second-level / partial beam indication can be started simultaneously.
[0379] In one example, the physical channel carrying the first-level / partial beam indication and the corresponding physical channel carrying the second-level / partial beam indication can terminate simultaneously.
[0380] In one example, the physical channel carrying the first-level / partial beam indication and the corresponding physical channel carrying the second-level / partial beam indication may partially or completely overlap in time.
[0381] In one implementation, a first-level / partial beam indication is provided.
[0382] In one example, the first-level / partial beam indication may be included in the DL control channel, such as the PDCCH / DCI channel transmitted in the search space and CORESET.
[0383] In one example, the UE monitors the PDCCH / DCI channels, including Level 1 / partial beam indication, in the search space and CORESET.
[0384] In one example, the search space used to carry the PDCCH / DCI channel for first-level / partial beam indication is the common search space (CSS).
[0385] In one example, the search space used to carry the PDCCH / DCI channel for first-level / partial beam indication is the UE-specific search space (USS).
[0386] In one example, the search space used to carry the PDCCH / DCI channel for first-level / partial beam indication is a UE group-specific search space.
[0387] In one example, the CORESET used to carry the PDCCH / DCI channel for first-level / partial beam indication is a common CORESET.
[0388] In one example, the CORESET used to carry the Level 1 PDCCH / DCI channel for Level 1 / partial beam indication is a UE-specific CORESET.
[0389] In one example, the CORESET used to carry the Level 1 PDCCH / DCI channel for Level 1 / partial beam indication is a UE group-specific CORESET.
[0390] In one example, the PDCCH / DCI can be a DCI related to DL, a DCI related to UL, or a PDCCH / DCI that provides other L1 control information to the UE.
[0391] In one example, a first-level / partial beam indication may be included in the DL control channel, for example, a PDCCH / DCI channel transmitted in multiple search spaces and / or multiple CORESETs. The payload size for each search space and / or CORESET may be different.
[0392] In one example, the UE monitors PDCCH / DCI channels, including Level 1 / partial beam indication, across multiple search spaces and CORESETs. The UE determines the payload size based on the detected search spaces and / or CORESETs containing PDCCH / DCI channels, including Level 1 / partial beam indication.
[0393] In one example, the search space for the PDCCH / DCI channel carrying the first-level / partial beam indication is the CSS.
[0394] In one example, the multiple search spaces used to carry the PDCCH / DCI channel for first-level / partial beam indication are USS.
[0395] In one example, the multiple search spaces used to carry the PDCCH / DCI channel for first-level / partial beam indication are UE group-specific search spaces.
[0396] In one example, the multiple search spaces used to carry the PDCCH / DCI channel for first-level / partial beam indication are a combination of at least two of the examples described in this disclosure.
[0397] In one example, the multiple CORESETs used to carry the PDCCH / DCI channels for first-level / partial beam indication are common CORESETs.
[0398] In one example, the multiple CORESETs used to carry the Level 1 PDCCH / DCI channel for Level 1 / partial beam indication are UE-specific CORESETs.
[0399] In one example, the multiple CORESETs used to carry the Level 1 PDCCH / DCI channel for Level 1 / partial beam indication are UE group-specific CORESETs.
[0400] In one example, the multiple CORESETs used to carry the first-level PDCCH / DCI channel for first-level / partial beam indication are a combination of at least two of the examples described in this disclosure.
[0401] In these examples, the PDCCH / DCI can be a DCI related to DL, a DCI related to UL, or a PDCCH / DCI that provides other L1 control information to the UE.
[0402] In one example, the first-level / partial beam indication (such as...) Figure 22 (As shown in 2202) can be included in the reference signal.
[0403] In one example, the reference signal used for first-level / partial beam indication can be transmitted in a resource configured by higher layers.
[0404] In one example, the UE monitors a reference signal configured by a higher layer for Level 1 / partial beam indication. These resources include time / frequency and / or code resources.
[0405] In one example, the resources used for Level 1 / partial beam indication can be configured by public / cell-specific higher-layer signaling.
[0406] In one example, the resources used for Level 1 / partial beam indication can be configured by UE-specific higher-layer signaling.
[0407] In one example, the resources used for Level 1 / partial beam indication can be configured by UE group-specific higher-layer signaling.
[0408] In one implementation, a second-level / partial beam indication is provided.
[0409] In one example, the second-level / partial beam indication is the PDCCH / DCI transmitted in the search space and CORESET.
[0410] In one example, after receiving a first-level / partial beam indication indicating the presence of a PDCCH / DCI channel carrying a second-level / partial beam indication, the UE monitors the PDCCH / DCI channel carrying the second-level / partial beam indication in the search space and CORESET.
[0411] In one example, the search space for the PDCCH / DCI channel carrying the second-level / partial beam indication is the CSS.
[0412] In one example, the search space for the PDCCH / DCI channel carrying the second-level / partial beam indication is USS.
[0413] In one example, the search space used to carry the PDCCH / DCI channel for Level 2 / partial beam indication is a UE group-specific search space.
[0414] In one example, the CORESET used to carry the PDCCH / DCI channel for second-level / partial beam indication is a common CORESET.
[0415] In one example, the CORESET used to carry the PDCCH / DCI channel for Level 2 / partial beam indication is a UE-specific CORESET.
[0416] In one example, the CORESET used to carry the PDCCH / DCI channel for Level 2 / partial beam indication is a UE group-specific CORESET.
[0417] In such an example, the PDCCH / DCI can be a DCI related to DL, a DCI related to UL, or a PDCCH / DCI that provides other L1 control information to the UE.
[0418] In one example, the PDCCH / DCI carrying the second-level / partial beam indication during the search space monitoring timing may have a fixed frequency offset between it and the physical channel carrying the first-level beam indication.
[0419] In such an example, the frequency offset can be: (1) from the start frequency of the physical channel indicated by the first-level / partial beam to the start frequency of the PDCCH / DCI carrying the second-level / partial beam; (2) from the start frequency of the physical channel indicated by the first-level / partial beam to the end frequency of the PDCCH / DCI carrying the second-level / partial beam; (3) from the end frequency of the physical channel indicated by the first-level / partial beam to the start frequency of the PDCCH / DCI carrying the second-level / partial beam; or (4) from the end frequency of the physical channel indicated by the first-level / partial beam to the end frequency of the PDCCH / DCI carrying the second-level / partial beam. In some cases, the frequency offset can be 0.
[0420] In one example, the physical channel of the first-level beam indication can be used to indicate the monitoring timing and time / or frequency resources within the monitoring timing for the PDCCH / DCI carrying the second-level / partial beam indication.
[0421] In one example, the time and / or frequency resources of the PDCCH / DCI carrying the second-level / partial beam indication in the example described in this disclosure may be indicated as a time and / or frequency offset relative to the physical channel of the first-level / partial beam indication.
[0422] In one example, the time and / or frequency resources of the PDCCH / DCI carrying the second-level / partial beam indication are configured by the higher layers.
[0423] In one example, multiple search spaces and / or CORESETs are configured for the PDCCH / DCI carrying second-level / partial beam indication, wherein the search spaces and / or CORESETs depend on the payload size indicated by the first-level / partial beam indication. Furthermore, in some examples, the time and / or frequency of the channel carrying the second-level beam indication may be indicated as shown in the examples described in this disclosure.
[0424] In one example, the DL control channel carrying the second-level / partial beam indication is a PDCCH / DCI transmitted with a fixed time and frequency offset relative to the physical channel of the first-level / partial beam indication. This is in Figure 23 As shown in the image.
[0425] Figure 23 An exemplary time and frequency offset of 2300 is shown according to an embodiment of this disclosure. Figure 23 The implementation shown with a time and frequency offset of 2300 is for illustrative purposes only.
[0426] In one example, after receiving a first-level / partial beam indication indicating the presence of a PDCCH / DCI carrying a second-level / partial beam indication, the UE monitors and receives the PDCCH / DCI carrying the second-level / partial beam indication at a fixed time and frequency offset relative to the physical channel of the first-level / partial beam indication.
[0427] In one example, the time and / or frequency offsets are indicated in the first-level / partial beam indication based on a set of values configured by higher layers or specified in the standard.
[0428] In one example, the offset value may depend on the payload size of the first-level / partial beam indication and / or the second-level / partial beam indication.
[0429] In one example, the time and / or frequency offsets are configured by a higher layer.
[0430] In one example, the time and / or frequency offset depends on the subcarrier spacing, which is a function of the first-level / partial beam-indicated subcarrier spacing, or the second-level / partial beam-indicated subcarrier spacing, or the first-level / partial beam-indicated and second-level / partial beam-indicated subcarrier spacing (e.g., minimum or maximum value).
[0431] In one example, the offset value may depend on the payload size of the first-level / partial beam indication and / or the second-level / partial beam indication.
[0432] In one example, the DL control channel carrying the second-level / partial beam indication is a PDCCH / DCI transmitted in one of several resources configured by the higher layers.
[0433] In one example, after receiving a Level 1 / partial beam indication indicating the presence of a PDCCH / DCI carrying a Level 2 / partial beam indication, the UE monitors and receives the PDCCH / DCI carrying the Level 2 / partial beam indication across multiple resources configured by higher layers. In some instances, the UE may determine the resource from the configured multiple resources for carrying the PDCCH / DCI carrying the Level 2 / partial beam indication, and then monitor and receive the PDCCH / DCI carrying the Level 2 / partial beam indication.
[0434] In one example, the second-level / partial beam indication is downlink control information (DCI) multiplexed with other downlink data on the PDSCH.
[0435] In one example, the number of resource elements (REs) allocated to the DCI carrying the second-level / partial beam indication is determined based on at least some of the following: the configurable or (in the first-level / partial beam indication) dynamically indicated β offset, the payload of the second-level / partial beam indication, the payload of the data multiplexed on the PDSCH (e.g., the data of the downlink shared channel (DL-SCH)), the modulation scheme of the PDSCH, the number of layers of the PDSCH, the resource blocks and symbols allocated to the PDSCH, and the number of other signals multiplexed on the PDSCH.
[0436] In one example, the data RE carrying the DL-SCH is rate-matched around the RE carrying the DCI carrying the second-level / partial beam indication.
[0437] In one example, the DCI RE carrying the second-level / partial beam indication punches the data RE carrying the DL-SCH.
[0438] In one example, the DCI RE carrying the second-level / partial beam indication avoids the PDSCH DM-RS RE.
[0439] In one example, a DCI RE carrying a second-level / partial beam indication can be mapped to a symbol near a PDSCH DM-RS symbol.
[0440] In one example, the DCI RE carrying the second-level / partial beam indication may not be mapped to the PDSCH DM-RS symbol.
[0441] In one example, a DCI RE carrying a second-level / partial beam indication can be mapped to a PDSCH DM-RS symbol that is not used for PDSCH DM-RS.
[0442] In one example, the second-level / partial beam indication is part of the DL-SCH payload multiplexed on the PDSCH channel.
[0443] In one example, the PDSCH only carries the second-level / partial beam indication.
[0444] In one example, the second-level / partial beam indication channel is multiplexed with other data on the DL-SCH.
[0445] In one example, the second-level / partial beam indication channel is the MAC control element (MAC CE) in the DL-SCH.
[0446] In one implementation, the content of the first-level / partial beam indication is provided.
[0447] In one example, a first-level / partial beam indication addressing a group of UEs may include a bitmap, where each UE in the group addressed by the beam indication has a corresponding bit. Each bit corresponding to a UE indicates whether beam indication information (e.g., TCI status) for that UE is present in the second-level / partial beam indication. This is in Figure 24 As shown in the image.
[0448] Figure 24 An exemplary beam indicator 2400 according to an embodiment of this disclosure is shown. Figure 24 The implementation of the beam indicator 2400 shown is for illustrative purposes only.
[0449] like Figure 24 As shown, the first-level / partial beam indication (2401) includes bits for each UE in a UE group of size “n”, represented as bit 0 (2403) for UE 0, bit 1 (2404) for UE 1, ..., bit n-1 (2405) for UE n-1. In this example, bit 0 (2403) has a value of 0, bit 1 (2404) has a value of 1, and bit n-1 (2405) for UE n-1 has a value of 1.
[0450] The second-level / partial beam indication (2402) includes a beam indication (e.g., TCI state) for a UE, which has a corresponding bit set to 1 in the first-level / partial beam indication (2401). In this example, the second-level / partial beam indication (2402) includes a beam indication (e.g., TCI state) for TCI state (2406) for UE 1 and a beam indication (e.g., TCI state) for TCI state (2407) for UE n-1.
[0451] In one example, the first-level / partial beam indication may include the type of beam indication information in the second-level / partial beam indication. The type of beam indication information may be DL TCI status and / or UL TCI status and / or combined TCI status.
[0452] In one example, the first-level / partial beam indication may include a beam (i.e., a spatial filter or TCI state) used to transmit the physical channel carrying the second-level / partial beam indication.
[0453] In one example, when the UE receives a first-level / partial beam indication with a beam ID, spatial filter ID, or TCI state, it receives the physical channel carrying the corresponding second-level / partial beam indication based on the assumption that the beam ID, spatial filter ID, or TCI state ID indicated in the first-level / partial beam indication.
[0454] In one example, the first-level / partial beam indicator could be an presence indicator that indicates the presence of the second-level / partial beam indicator.
[0455] In one example, the UE receives a second-level / partial beam indication when it receives a first-level / partial beam indication with an presence indicator.
[0456] In one example, the presence indicator can be detected by the presence (i.e., detection) of the following: the channel / signal carrying the first-level / partial beam indication, the RNTI scrambled with the CRC used in the physical channel carrying the first-level / partial beam indication, the scrambling sequence of the signal / channel carrying the first-level / partial beam indication, or the field within the physical channel carrying the first-level beam indication.
[0457] In one example, the first-level / partial beam indication can be carried by a physical channel with a CRC field scrambled by RNTI.
[0458] In one example, RNTI could be a beam indicator specific RNTI.
[0459] In one example, the RNTI can be a UE group-specific RNTI.
[0460] In one example, some or all of the previous fields may be included in the physical channel carrying the first-level / partial beam indication, or indicated by the physical channel carrying the first-level / partial beam indication.
[0461] In one example, the first-level / partial beam indication may include an indicator I indicating the presence / absence of a Tx beam for a multi-panel UE equipped with Z > 1 antenna panels. In one example, the indicator I is a bitmap of length Z, where bit b_i in the bitmap is associated with the i-th antenna panel at the UE. When bit b_i = 1, the Tx beam for the i-th antenna panel is indicated via the second-level / partial beam indication. When bit b_i = 0, the Tx beam for the i-th antenna panel is not indicated.
[0462] In one example, indicator I corresponds to the panel ID of Z antenna panels.
[0463] In one example, the first-level / partial beam indication is for a group of n UEs, each with an indicator I of length Z. In this case, the bitmap size is n × Z bits.
[0464] In one example, the first-level / partial beam indication is a group of n UEs, each UE having an indicator I of length Z(i), where Z(i) is the number of bits assigned to UE i, where i is between 1 and n. In this case, the size of the bitmap is... ∑_(i=1)^n▒?Z(i)?position.
[0465] In one example, the first-level / partial beam indication may include an indicator I indicating the presence / absence of a Tx beam across multiple panels / TRPs. In one example, indicator I is a bitmap of length Z, where bit b_i in the bitmap is associated with the i-th antenna panel / TRP. When bit b_i = 1, the Tx beam for the i-th antenna panel / TRP is indicated via the second-level / partial beam indication. When bit b_i = 0, the Tx beam for the i-th antenna panel / panel is not indicated.
[0466] In one example, the first-level / partial beam indication is for a group of n UEs, each UE having an indicator I of length Z. In this case, the bitmap size is n×Z bits.
[0467] In one example, the first-level / partial beam indication channel / signal may include indications of the presence / absence of other parameters (different from Tx beam indication). For example, for UL beam indication, the first-level / partial beam indication may include indications of the presence / absence of UL-related parameters (such as power control, timing advance, etc.), which may be panel-specific (each panel has its own parameter) or panel-common (all panels share a single parameter).
[0468] In one example, the payload of the first-level / partial beam indication can vary. This requires the UE to make multiple decoding assumptions about the physical channel carrying the first-level / partial beam indication.
[0469] In one example, different physical resources are used to carry the physical channel for the first-level / partial beam indication.
[0470] In one example, identical or partially overlapping physical resources are used to carry the physical channel indicated by the first-level / partial beam.
[0471] In one implementation, the content of a second-level / partial beam indication is provided.
[0472] In one example, the second-level / partial beam indication includes the beam indication for one or more UEs indicated in the corresponding first-level beam indication. The beam indication may be a DL TCI state and / or a UL TCI state and / or a combined TCI state.
[0473] In one example, the beam indication type included in the second-level / partial beam indication can be indicated in the first-level / partial beam indication.
[0474] In one example, beam indication (e.g., DL TCI status and / or UL TCI status and / or combined TCI status) is configured by a higher layer, and the second-level / partial beam indication includes an index of the configured values.
[0475] In one example, the second-level / partial beam indication includes the time offset for applying the beam indication.
[0476] In one example, the beam time offset is configured by the higher layers, and the second-level / partial beam indication includes an index to the configured time offset.
[0477] In one example, the second-level / partial beam indication may include a beam indication for one or more antenna panels indicated in the corresponding first-level / partial beam indication. The beam indication may be a DL TCI state and / or a UL TCI state and / or a combined TCI state.
[0478] In one example, the beam indication type of the antenna panel included in the second-level / partial beam indication can be indicated in the first-level / partial beam indication.
[0479] In one example, beam indication (e.g., DL TCI status and / or UL TCI status and / or combined TCI status) is configured by a higher layer, and the second-level / partial beam indication includes an index of the configured values.
[0480] In one example, the second-level / partial beam indication may include the beam indication for the antenna panel / UE pair indicated in the corresponding first-level / partial beam indication.
[0481] In one example, the second-level / partial beam indication may include a beam indication for multi-panel / multi-TRP indicated in the corresponding first-level / partial beam indication. The beam indication may be a DL TCI state and / or a UL TCI state and / or a combined TCI state.
[0482] In one example, the beam indication type for multi-panel / multi-TRP included in the second-level / partial beam indication can be indicated in the first-level / partial beam indication.
[0483] In one example, beam indication (e.g., DL TCI status and / or UL TCI status and / or combined TCI status) is configured by a higher layer, and the second-level / partial beam indication includes an index of the configured values.
[0484] In one example, the second-level / partial beam indication may include the beam indication for the TRP / panel / UE group indicated in the corresponding first-level / partial beam indication.
[0485] In one example, the second-level / partial beam indication may include parameters (other than the Tx beam indication) that indicate their presence in the corresponding first-level / partial beam indication. For example, parameters such as power control, timing advance, etc., may be indicated in the second-level / partial beam indication. These parameters may be panel-specific (each panel has its own parameter) or panel-common (all panels share a single parameter).
[0486] In one implementation, a beam indication channel is provided.
[0487] In one example, the first-level / partial beam indication is the first-level beam indication channel / signal ( Figure 22 (2202), while the second-level / partial beam indication is the second-level beam indication channel / signal ( Figure 22 (2203).
[0488] In one example, the first-stage beam indicates the channel / signal ( Figure 222202) is the first DL control channel, while the second-level beam indication channel / signal ( Figure 22 2203) is the second DL control channel.
[0489] In one example, the first-stage beam indicates the channel / signal ( Figure 22 2202) is the reference signal, while the second-level beam indicator channel / signal ( Figure 22 2203) is the DL control channel.
[0490] In one example, the first-stage beam indicates the channel / signal ( Figure 22 2202) is the DL control channel, while the second-level beam indication channel / signal ( Figure 22 2203) is downlink control information multiplexed in the Physical Downlink Shared Channel (PDSCH).
[0491] In one example, the first-stage beam indicates the channel / signal ( Figure 22 2202) is the DL control channel, while the second-level beam indication channel / signal ( Figure 22 2203) is the downlink data channel.
[0492] Figure 25 A flowchart of a gNB method 2500 for beam processing according to an embodiment of the present disclosure is shown. Figure 25 The implementation of method 2500 shown is for illustrative purposes only. Figure 25 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or the one or more components may be implemented by one or more processors that execute instructions to perform the function.
[0493] like Figure 25 As shown, in step 2501, the higher layer configures a two-level / partial beam indication. Examples of configuration include: (1) resource allocation for physical channels used to carry the first-level / partial beam indication and the second-level / partial beam indication, including any potential mapping between the resource allocation of physical channels for the first-level / partial beam indication and the resource allocation of physical channels for the second-level / partial beam indication; (2) parameters to be indicated using the two-level / partial beam indication; (3) the number of UEs in the UE group using the two-level / partial beam indication; (4) mapping UEs / TRPs / antenna panels to the corresponding bits in the first-level / partial beam indication; and / or (5) other configuration parameters following the examples given in this disclosure.
[0494] The higher-layer configuration of two-level / partial beam indication can use public / cell-specific signaling and / or UE-specific signaling and / or UE group-specific signaling. In addition, some configuration parameters can be updated using RRC signaling, MAC layer signaling, and / or physical layer control signaling.
[0495] In step 2502, the gNB determines whether it can signal parameters indicated by the two-stage / partial beam instruction. These parameters can be, for example, beam, TPC command, TA, power control parameters, etc. If yes, proceed to step 2503; otherwise, hold step 2502.
[0496] In step 2503, the gNB sends a first-level / partial beam indication for the UE and / or panel and / or TRP, and in the second-level / partial beam indication parameters for the UE and / or panel and / or TR.
[0497] In step 2504, the gNB transmits a second-level / partial beam indication, including parameters indicating its presence in the corresponding first-level / partial beam indication. Then proceed to step 2502.
[0498] For illustrative purposes, the steps of the algorithm are described sequentially; however, some of these steps can be performed in parallel with each other.
[0499] Figure 26 A flowchart of a method 2600 for beam processing of a UE according to an embodiment of the present disclosure is shown. Figure 26 The implementation of method 2600 shown is for illustrative purposes only. Figure 26 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or the one or more components may be implemented by one or more processors that execute instructions to perform the function.
[0500] like Figure 26 As shown, in step 2601, the higher layer configures the UE for the two-level / partial beam indication. Examples of configuration include: (1) resource allocation for the physical channels used for the first-level / partial beam indication and the second-level / partial beam indication, including any potential mapping between the resource allocation of the physical channels for the first-level / partial beam indication and the resource allocation of the physical channels for the second-level / partial beam indication; (2) parameters to be indicated using the two-level / partial beam indication; (3) the number of UEs in the UE group using the two-level / partial beam indication; (4) mapping the UEs and TRPs / antenna panels to the corresponding bits in the first-level / partial beam indication; and / or (5) other configuration parameters following the examples given in the disclosure.
[0501] The higher-layer configuration of two-level / partial beam indication can use public / cell-specific signaling and / or UE-specific signaling and / or UE group-specific signaling. In addition, some configuration parameters can be updated using MAC layer signaling and / or physical layer control signaling.
[0502] In step 2602, the UE monitors the physical channel indicated by the first-level / partial beam, and if the UE receives the corresponding channel, the UE proceeds to step 2603; otherwise, the UE remains in step 2602. Examples of the UE receiving the physical channel indicated by the first-level / partial beam include: (1) correctly decoding the CRC with the corresponding RNTI in the physical channel; and / or (2) threshold detection of the channel / signal carrying the first-level / partial beam indication.
[0503] In step 2603, the UE decodes the first-level / partial beam indication. If the UE finds or determines the presence indicator of the UE, the UE proceeds to step 2604; otherwise, the UE returns to step 2602.
[0504] In step 2604, the UE decodes the second-level / partial beam indication, takes action based on the received parameters, and returns to step 2602.
[0505] For illustrative purposes, the steps of the algorithm are described sequentially; however, some of these steps can be performed in parallel with each other.
[0506] 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 shown 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, these steps may be omitted or replaced by other steps.
[0507] Figure 27 A base station according to an embodiment of the present disclosure is shown.
[0508] refer to Figure 27 The base station 2700 may include a processor 2710, a transceiver 2720, and a memory 2730. However, not all of the components shown are essential. The base station 2700 may be composed of... Figure 27 The 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.
[0509] Base station 2700 may correspond to the aforementioned gNB. For example, base station 2700 may correspond to... Figure 2 The gNB 102 shown.
[0510] The above-mentioned components will now be described in detail.
[0511] Processor 2710 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of base station 2700 may be implemented by processor 2710.
[0512] Transceiver 2720 may include an RF transmitter that up-converts and amplifies the transmitted signal, and an RF receiver that down-converts the received signal. However, according to another embodiment, transceiver 2720 may be implemented with more or fewer components than those shown in the components.
[0513] Transceiver 2720 can be connected to processor 2710 and send and / or receive signals. These signals may include control information and data. Furthermore, transceiver 2720 can receive signals via a wireless channel and output those signals to processor 2710. Transceiver 2720 can also transmit signals output from processor 2710 via a wireless channel.
[0514] The memory 2730 may store control information or data included in the signals obtained by the base station 2700. The memory 2730 may be connected to the processor 2710 and store at least one instruction, protocol, or parameter for the proposed function, process, and / or method. The 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.
[0515] Figure 28 A user equipment (UE) according to an embodiment of the present disclosure is shown.
[0516] refer to Figure 28 UE 2800 may include a processor 2810, a transceiver 2820, and a memory 2830. However, not all of the components shown are essential. UE 2800 may be made from... Figure 28 The components shown can be implemented with more or fewer components. Furthermore, according to another embodiment, the processor 2810, transceiver 2820, and memory 2830 can be implemented as a single chip.
[0517] UE 2800 may correspond to the UE described above. For example, UE 2800 may correspond to... Figure 3 The UE 116 shown.
[0518] The above-mentioned components will now be described in detail.
[0519] Processor 2810 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of UE 2800 may be implemented by processor 2810.
[0520] 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 shown in the components.
[0521] Transceiver 2820 can be connected to processor 2810 and send and / or receive signals. These signals may include control information and data. Furthermore, transceiver 2820 can receive signals via a wireless channel and output those signals to processor 2810. Transceiver 2820 can also transmit signals output from processor 2810 via a wireless channel.
[0522] Memory 2830 may store control information or data included in signals obtained by UE 2800. Memory 2830 may be connected to processor 2810 and store at least one instruction or protocol or parameter for the proposed function, process, and / or method. 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.
[0523] Although this disclosure has been described using exemplary embodiments, various changes and modifications may be suggested by those skilled in the art. This disclosure is intended to cover such 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 the patent subject matter is defined by the claims.
Claims
1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive higher-layer signaling messages from the base station, wherein the higher-layer signaling messages configure the transmission configuration indication TCI status; The base station receives downlink control information (DCI), which includes a TCI status indication associated with the beam to be applied. as well as Send a positive HARQ acknowledgment for the DCI containing the TCI status indication. Specifically, after a time period based on higher-layer signaling configuration following a positive HARQ acknowledgment of the DCI containing the TCI status indication, the beam associated with the TCI status indication contained in the DCI is activated.
2. The method according to claim 1, further comprising: When the DCI format corresponding to the DCI including the TCI status indication is configured to have no downlink DL allocation, the value of the frequency domain resource allocation field in the DCI is identified as follows: When resource allocation type 0 is 0, all values are 0. In resource allocation type 1, all values are 1, or In the case of dynamically switching resource allocation types, all values are 0. The DCI format is at least one of DCI format 1_1 or DCI format 1_2.
3. A method performed by a base station (BS) in a wireless communication system, the method comprising: Send a higher-layer signaling message to the user equipment (UE), wherein the higher-layer signaling message configures the transmission configuration indication (TCI) status; Send downlink control information (DCI) to the UE, the DCI including a TCI status indication, the TCI status indication being associated with the beam to be applied; as well as Receive a positive HARQ acknowledgment from the UE for the DCI containing the TCI status indication. Specifically, after a time period based on higher-layer signaling configuration following a positive HARQ acknowledgment of the DCI containing the TCI status indication, the beam associated with the TCI status indication contained in the DCI is activated.
4. The method according to claim 3, in, When the DCI format corresponding to the DCI including the TCI status indication is configured to have no downlink DL allocation, the value of the frequency domain resource allocation field in the DCI identified on the UE side is set as follows: When resource allocation type 0 is 0, all values are 0. In resource allocation type 1, all values are 1, or In the case of dynamically switching resource allocation types, all values are 0. The DCI format is at least one of DCI format 1_1 or DCI format 1_2.
5. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: Control the transceiver to: Receives higher-layer signaling messages from the base station, wherein the higher-layer signaling messages configure the transmission configuration indication (TCI) status. Receive downlink control information (DCI) from the base station, the DCI including a TCI status indication associated with the beam to be applied; and Send a positive HARQ acknowledgment for the DCI containing the TCI status indication. Specifically, after a time period based on higher-layer signaling configuration following a positive HARQ acknowledgment of the DCI containing the TCI status indication, the beam associated with the TCI status indication contained in the DCI is activated.
6. The UE according to claim 5, wherein, The at least one processor is further configured to: When the DCI format corresponding to the DCI including the TCI status indication is configured to have no downlink DL allocation, the value of the frequency domain resource allocation field in the DCI is identified as follows: When resource allocation type 0 is 0, all values are 0. In resource allocation type 1, all values are 1, or In the case of dynamically switching resource allocation types, all values are 0. The DCI format is at least one of DCI format 1_1 or DCI format 1_2.
7. A base station (BS) in a wireless communication system, the BS comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: Send a higher-layer signaling message to the user equipment (UE), wherein the higher-layer signaling message configures the transmission configuration indication (TCI) status; Send downlink control information (DCI) to the UE, the DCI including a TCI status indication, the TCI status indication being associated with the beam to be applied; as well as Receive a positive HARQ acknowledgment from the UE for the DCI containing the TCI status indication. Specifically, after a time period based on higher-layer signaling configuration following a positive HARQ acknowledgment of the DCI containing the TCI status indication, the beam associated with the TCI status indication contained in the DCI is activated.
8. The BS according to claim 7, in, When the DCI format corresponding to the DCI including the TCI status indication is configured to have no downlink DL allocation, the value of the frequency domain resource allocation field in the DCI identified on the UE side is set as follows: When resource allocation type 0 is 0, all values are 0. In resource allocation type 1, all values are 1, or In the case of dynamically switching resource allocation types, all values are 0. The DCI format is at least one of DCI format 1_1 or DCI format 1_2.
Citation Information
Patent Citations
TCI (Transmission Configuration Indication) state update method, base station and terminal
CN109587793A
Transmission indication method and device
CN110089181A