Beam reporting method and apparatus therefor

Abstract

The invention provides a beam reporting method and equipment thereof. The device may measure at least one reference signal from the network node. The device may send a beam report to a network node. The beam report may indicate at least one beam that has been synchronized by the device. The beam reporting may include a reporting order to determine at least one code point of a transmission configuration indicator field.

Description

Technical Field

[0001] The present invention generally relates to mobile communications, and more particularly to beam indication based on beam reporting involving a user equipment (UE) and a network device in mobile communications. Background Art

[0002] Unless otherwise indicated, the approaches described in this section are not prior art to the claims and are not admitted to be prior art by inclusion in this section.

[0003] In a conventional beam management process, a network node may send at least one downlink (DL) reference signal (RS) to a user equipment (UE). The UE may then perform measurements based on the DL RS to generate a beam report. After the UE sends the beam report to the network node, the network node may need to perform a beam activation process to determine the beam. The UE may then need to perform additional measurements based on further reference signals of the beam indicated in a beam activation command (e.g., a medium access control (MAC) control element (MAC-CE)) from the network node to complete synchronization of the beam. After measuring the beam, the network node may send a beam indication for beam switching to the UE. Therefore, the beam switching delay in the current beam management process can be very long and inefficient.

[0004] In addition, in the conventional beam indication process, the beam indication is usually provided by the transmission configuration indicator (TCI) field in the downlink control information (DCI) in the network node or the MAC-CE. The codepoint interpretation of the TCI field can be determined based on the MAC-CE for TCI state activation from the network node. Specifically, the network node can activate or deactivate at least one TCI state or a pair of TCI states through MAC-CE. The activated TCI state or a pair of activated TCI states can be mapped to the codepoint of the TCI field in the DCI. For example, if multiple codepoints are activated by MAC-CE (ie, the codepoint is mapped to multiple TCI states), a DCI with a TCI field can be used to indicate one of the activated codepoints. The UE can use the activated TCI state corresponding to the indicated codepoint as the service TCI state. If the MAC-CE activates a single codepoint, the UE can use the activated TCI state corresponding to the single codepoint as the service TCI state without waiting for the beam indication through the TCI field in the DCI.

[0005] Therefore, how to determine the code point for beam indication when there is no MAC-CE based TCI state activation from the network node becomes an important issue in the newly developed wireless communication network. Therefore, it is necessary to provide an appropriate scheme to shorten the overall beam switching delay and determine the code point without MAC-CE based TCI state activation. Summary of the invention

[0006] The following summary of the invention is illustrative only and is not intended to be limiting in any way. That is, the following summary of the invention is provided to introduce the concepts, key points, benefits and beneficial effects of the novel and non-obvious technologies described herein. Selected embodiments are further described in the detailed description below. Therefore, the following summary of the invention is not intended to identify the essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0007] An object of the present invention is to propose a scheme, concept, design, system, method and apparatus for beam indication based on beam reporting related to user equipment and network equipment in mobile communications. It is believed that by implementing one or more of the proposed schemes described herein, the above problems will be avoided or otherwise alleviated.

[0008] In one aspect, a method may include a device measuring at least one reference signal from a network node. The method may also include the device sending a beam report to the network node, wherein the beam report may indicate at least one beam synchronized by the device, and wherein the beam report may include a reporting order to determine at least one code point of a transmission configuration indicator (TCI) field.

[0009] In another aspect, a device may include a transceiver for wirelessly communicating with at least one network node during operation. The device may also include a processor communicatively coupled to the transceiver such that during operation, the processor may measure at least one reference signal from the network node. The processor may also send a beam report to the network node via the transceiver, wherein the beam report may indicate at least one beam synchronized by the device, and wherein the beam report may include a reporting order to determine at least one code point of a TCI field.

[0010] In another aspect, a method may include a network node sending at least one reference signal to a user equipment (UE). The method may also include the network node receiving a beam report from the UE, wherein the beam report may indicate at least one beam synchronized by the UE. The method may also include the network node determining at least one code point of a TCI field according to a reporting order in the beam report.

[0011] The beam reporting method and device provided by the present invention can shorten the overall beam switching delay.

[0012] It is worth noting that, although the description provided herein may be in the context of certain radio access technologies, networks and network topologies (e.g., the fifth generation system (5GS) and 4G EPS mobile networks), the proposed concepts, schemes and any variations / derivations thereof may be implemented on, for and through any other type of radio access technologies, networks and network topologies, such as but not limited to Ethernet, Universal Terrestrial Radio Access Network (UTRAN), E-UTRAN, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS) / Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network (GERAN), Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial Internet of Things (IIoT), Narrowband Internet of Things (NB-IoT), 6G and any future developed network technologies. Therefore, the scope of the present invention is not limited to the examples described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are included to provide a further understanding of the invention and are incorporated into and constitute a part of the present invention. The accompanying drawings illustrate embodiments of the invention and together with the description are used to explain the principles of the invention. It is understood that in order to clearly illustrate the concepts of the present invention, the accompanying drawings are not necessarily drawn to scale, and some components shown may be shown in a scale that exceeds the size in the actual embodiment.

[0014] Figure 1 is an example scenario diagram describing a communication environment that can be implemented according to various solutions and schemes of the present invention.

[0015] Figure 2 is an example scenario diagram describing beam reporting and TCI fields according to an embodiment of the present invention.

[0016] Figure 3 is an example scenario diagram describing another beam report and TCI field according to an embodiment of the present invention.

[0017] Figure 4 is an example scenario diagram describing the beam management process according to an embodiment of the present invention.

[0018] Figure 5 is a block diagram depicting an example communication system according to an embodiment of the present invention.

[0019] Figure 6 is a flow chart describing an example process according to an embodiment of the present invention.

[0020] Figure 7 is a flow chart describing an example process according to another embodiment of the present invention. DETAILED DESCRIPTION

[0021] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrations of the claimed subject matter, which can be implemented in various forms. However, the present invention can be implemented in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. On the contrary, these multiple exemplary embodiments and implementations are provided so that the description of the present invention is comprehensive and complete, and will fully convey the scope of the present invention to those skilled in the art. In the following description, the details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0022] Overview

[0023] Embodiments of the present invention relate to various technologies, methods, schemes and / or solutions for beam indication based on beam reporting related to user equipment and network equipment in mobile communications. According to the present invention, multiple possible solutions are implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of these possible solutions may also be implemented in combination or in another manner.

[0024] Figure 1 1 is a diagram of an example scenario 100 that describes a communication environment that can be implemented according to various solutions and schemes of the present invention. Scenario 100 involves a user equipment (UE) 110 wirelessly communicating with a network 120 (e.g., a wireless network including a non-terrestrial network (NTN) and a terrestrial network (TN)) through a terrestrial network node 125 (e.g., an evolved Node B (eNB), a next generation Node B (gNB), or a transmission / reception point (TRP)) and / or a non-terrestrial network node 128 (e.g., a satellite). For example, the terrestrial network node 125 and / or the non-terrestrial network node 128 can form a non-terrestrial network (NTN) serving cell to wirelessly communicate with the UE 110. In some implementations, the UE 110 can be an Internet of Things (IoT) device, such as a narrowband Internet of Things (NB-IoT) UE or an enhanced machine type communication (eMTC) UE (e.g., a bandwidth reduced low complexity (BL) UE or a coverage enhancement (CE) UE). In such a communication environment, UE 110, network 120, ground network node 125 and non-ground network node 128 may implement various solutions related to the improved beam indication process according to the present invention as described below. It is worth noting that, although various proposed solutions may be described separately below, some or all of the proposed solutions may be used in conjunction or otherwise implemented in conjunction in actual implementation. Of course, each proposed solution may also be used or implemented separately or individually.

[0025] According to implementations of the present invention, a UE (eg, UE 110) may measure at least one reference signal (eg, a downlink (DL) reference signal (RS)) from a network node (eg, ground network node 125).

[0026] Specifically, the UE may receive at least one reference signal from the network node, and the UE may synchronize at least one beam based on the reference signal before sending a beam report to the network node. During the synchronization process, the UE may perform measurements based on a reference signal (or reference signals) from the network node to select a beam with better signal quality (e.g., a reference signal received power (RSRP) of the beam is greater than a threshold). The UE may then perform time and frequency tracking for the beam based on a synchronization signal block (SSB) to synchronize the selected beam before sending a beam report to the network node. That is, the UE may pre-synchronize the beam before a network (NW) initiated beam activation or a network initiated beam indication to reduce delays during the beam management process.

[0027] After synchronizing at least one beam, the UE may send a beam report to the network node. The beam report may indicate the beam (or beams) that have been synchronized by the device. In one example, all beams indicated in the beam report have been synchronized by the device. In another example, the beam report may include an indicator. The indicator may indicate the beams that have been synchronized by the device and the beams that have not been synchronized by the device.

[0028] A beam report may contain at least one reference signal index (or reference signal identification (ID)) or at least one transmission configuration indicator (TCI) state index (or TCI state ID) associated with the beam. That is, the UE may report (or indicate) a beam in a beam report by its associated reference signal index or TCI state index. Each beam in a beam report may be indicated by its associated reference signal index or TCI state index. Each reference signal index may be associated with a different TCI state index. In one example, when the reference signal or TCI state reported in the beam report is indicated as "synchronized", this means that the UE has synchronized the beam associated with the TCI state or reference signal. In another example, when the reference signal or TCI state reported in the beam report is indicated as "unsynchronized", this means that the UE has not synchronized the beam associated with the TCI state or reference signal.

[0029] In one example, according to a quasi co-location (QCL) configuration (e.g., QCL type) or a radio resource control (RRC) configuration in a TCI state, an association between a reference signal corresponding to a reference signal index and a TCI state corresponding to a TCI state index may be determined. Specifically, the UE may determine an association between a reference signal index and a TCI state index according to a source reference signal of QCL-TypeD or an RRC configuration from a network node.

[0030] The beam report may also include a reporting order to determine at least one code point of the TCI field. Each code point can be mapped to a reference signal index or a TCI state index according to the reporting order in the beam report. That is, when the network node receives a beam report from the UE, the network node can determine which TCI state the code point should be associated with according to the reporting order in the beam report. Therefore, the network node can determine the code point of the TCI field according to the reporting order in the beam report. In one example, the network node can determine the code point based on the latest beam report from the UE. In another example, the network node can determine the code point based on the beam report that has been confirmed by the network node.

[0031] Figure 2 An example scenario 200 of beam reporting and TCI fields according to an embodiment of the present invention is described. Scenario 200 involves a UE and a network node (e.g., a (macro / micro) base station) of a serving cell, which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 2 , the beam report may indicate the RS ID or TCI state ID associated with the beam selected by the UE (i.e., RS ID#1 to RS ID#4 or TCI state#A to TCI state#D). Figure 2 , the reporting order is from the beam associated with RS ID#1 (or TCI state #A) to the beam associated with RS ID#4 (or TCI state #D). The UE and the network node can determine or interpret the order of the code points (i.e., "00", "01", "10", "11") of the TCI field based on the reporting order in the beam report. Therefore, the code point "00" can be associated with TCI state ID TCI state #A. The code point "01" can be associated with TCI state ID TCI state #B. The code point "10" can be associated with TCI state ID TCI state #C. The code point "11" can be associated with TCI state ID TCI state #D.

[0032] Figure 3Another example scenario 300 of beam reporting and TCI fields according to an embodiment of the present invention is shown. Scenario 300 involves a UE and a network node (e.g., a (macro / micro) base station) of a serving cell, which may be part of a wireless network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 3 , the beam report may indicate only one RS ID or TCI state ID associated with the beam selected by the UE (i.e., RS ID #1 or TCI state #A). Therefore, the UE and the network node may determine or interpret the code point associated with the TCI field (i.e., "00") based on the beam report. That is, the code point "00" may be associated with the TCI state ID TCI state #A.

[0033] According to the proposed scheme of the beam management process of the present invention, after the UE sends a beam report to the network node, the UE can receive a beam indication for beam switching through downlink control information (DCI) from the network node. That is, in the proposed scheme, the network node may not need to perform the beam activation process. The beam indication may indicate at least one service TCI state associated with at least one code point of the TCI field. Specifically, the network node may select a beam for beam switching from the beams in the beam report. The network node may then send a code point associated with the service TCI state associated with the selected beam to the UE through the beam indication. In one example, when the UE receives the beam indication, the UE may use the TCI state corresponding to the indicated code point as the service TCI state. In another example, if there is only one RS ID or TCI state ID in the beam report (such as Figure 3 As shown), the UE can directly use the TCI state associated with the RS ID or TCI state ID in the beam report as the service TCI state.

[0034] In one example, when the serving TCI state is associated with a beam that has been synchronized by the UE, a beam applicable time (BAT) may be started after the beam report is reported (or sent) (e.g., Figure 4 BAT shown in timeline A of ). That is, after the beam report is sent, the beam synchronized by the UE is suitable for DL ​​reception. In other words, after the beam report is reported (or sent), the beam is ready for transmission / reception (for example, performing data channel transmission / reception or control channel transmission / reception). Therefore, after the UE receives the service TCI state indicated in the beam indication of beam switching, the UE can directly switch to the beam associated with the service TCI state for transmission / reception.

[0035] In another example, when the serving TCI state is associated with a beam that is not synchronized by the user equipment (UE), the beam activation time (BAT) of the beam may start after receiving another reference signal from the network node (e.g., Figure 4 BAT shown in timeline B of ). That is, a beam that is not synchronized by the UE may be suitable for downlink reception after receiving another reference signal related to the beam. In other words, the UE may need to synchronize the beam that is not synchronized by the UE based on the reference signal related to the service TCI state. For example, the UE may receive a synchronization signal block (SSB) or a tracking reference signal (TRS) related to the service TCI state from the network node, and perform measurements (i.e., time and frequency tracking) on ​​the SSB or TRS to synchronize the beam. After the UE synchronizes the beam, the UE may switch to the beam related to the service TCI state for transmission / reception. In this example, when the network node decides to select the service TCI state related to the beam that is not synchronized by the UE, the network node may trigger the reception of the SSB or TRS related to the service TCI state through the same downlink control information (DCI) in the beam indication for beam switching. Therefore, the network node can advance the time of the SSB or TRS.

[0036] Figure 4 An example scenario 400 of a beam management process according to an embodiment of the present invention is shown. Scenario 400 involves a UE and a network node (e.g., a (macro / micro) base station) of a wireless network (e.g., an LTE network, a 5G / NR network, an Internet of Things (IoT) network, or a 6G network). Figure 4 , the network node may send a downlink reference signal (DL RS) for measurement to the UE. The UE may then perform measurement based on the DL RS and perform synchronization on at least one beam before sending a beam report to the network node. After the UE sends the beam report to the network node, the UE may receive a beam indication for beam switching through DCI from the network node and send a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback for the beam indication to the network node. The beam indication may indicate at least one code point corresponding to at least one service TCI state. If the service TCI state is associated with a beam that has been synchronized by the UE, the UE may directly switch to the beam associated with the service TCI state to transmit data. If the service TCI state is associated with a beam that has not been synchronized by the UE, the UE may further receive an SSB or TRS associated with the beam to synchronize the beam, and then switch to the beam associated with the service TCI state for transmission / reception.

[0037] Illustrative Embodiments

[0038] Figure 2According to an embodiment of the present invention, an example communication system 200 having an example device 210 and an example device 220 is shown. Each of the devices 210 and 220 can perform various functions to implement schemes, technologies, processes and methods for SL-U power control in mobile communications, including various schemes described above as described in the following process.

[0039] Figure 5 An example communication system 500 having at least one example communication device 510 and an example network device 520 according to an embodiment of the present invention is shown. Each of the communication device 510 and the network device 520 can perform various functions to implement the beam indication-related schemes, technologies, processes and methods described herein, including the above-mentioned various proposed designs, concepts, schemes and methods, as well as user equipment and network equipment in mobile communications, including the above-mentioned scenarios / schemes and processes 600 and 700 described below.

[0040] The communication device 510 may be part of an electronic device, which may be a UE, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 510 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing device such as a tablet or a laptop. The communication device 510 may also be part of a machine type device, which may be an Internet of Things (IoT), a narrowband Internet of Things (NB-IoT), an enhanced machine type communication (eMTC), an industrial Internet of Things (IIoT) UE, such as a fixed or stationary device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, the communication device 510 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 510 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors. The communication device 510 may include Figure 5 The communication device 510 may also include one or more other components not related to the proposed solution of the present invention (e.g., an internal power supply, a display device and / or a user interface device), so for the sake of brevity and simplicity, Figure 5 These components are not shown in the figure or described below.

[0041] The network device 520 may be part of an electronic device, which may be a network node, such as a satellite, a base station (BS), a small cell, a router, or a gateway of an Internet of Things (IoT) network. For example, the network device 520 may be implemented in a satellite or an eNB / gNB / TRP in a 4G / 5G / B5G / 6G, NR, IoT, NB-IoT, or IIoT network. Alternatively, the network device 520 may be implemented in the form of one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more reduced instruction set computer (RISC) or complex instruction set computer (CISC) processors. The network device 520 may include Figure 5 The network device 520 may also include one or more other components not related to the proposed solution of the present invention (e.g., an internal power supply, a display device, and / or a user interface device), and therefore, for the sake of brevity and simplicity, these components are not shown in the figure. Figure 5 is not shown in the figure and is not described below.

[0042] In one aspect, each of processor 512 and processor 522 can be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processor 512 and processor 522, in some implementations, each of processor 512 and processor 522 can include multiple processors, and in other implementations can be a single processor. On the other hand, each of processor 512 and processor 522 can be implemented in the form of hardware (and, optionally, firmware), including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors, and these electronic components are configured and arranged to achieve the specific purpose of the present invention. In other words, in at least some implementations, each of processor 512 and processor 522 is a special-purpose machine, specially designed, arranged and configured to perform specific tasks in a device (e.g., represented by communication device 510) and a network node (e.g., represented by network device 520), including a PHR for MTRP operation.

[0043] In some implementations, the communication device 510 may also include a transceiver 516 coupled to the processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 516 may be capable of wirelessly communicating with different types of user equipment (UE) and / or wireless networks of different radio access technologies (RATs). In some implementations, the transceiver 516 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 516 may be equipped with multiple transmit antennas and multiple receive antennas for multiple input multiple output (MIMO) wireless communication. In some implementations, the network device 520 may also include a transceiver 526 coupled to the processor 522. The transceiver 526 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 526 may be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations, the transceiver 526 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 526 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0044] In some implementations, the communication device 510 may also include a memory 514 coupled to the processor 512 and capable of being accessed and storing data by the processor 512. In some implementations, the network device 520 may also include a memory 524 coupled to the processor 522 and capable of being accessed and storing data by the processor 522. Each of the memory 514 and the memory 524 may include a type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and / or zero capacitance RAM (Z-RAM). Alternatively, each of the memory 514 and the memory 524 may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM). Alternatively, each of the memory 514 and the memory 524 may include a type of non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and / or phase change memory.

[0045] Each of the communication device 510 and the network device 520 may be a communication entity capable of communicating using various proposed schemes of the present invention. For illustrative purposes and without limitation, the following provides a description of the capabilities of the communication device 510 as a UE and the network device 520 as a network node (e.g., TRP) in conjunction with the process 600 and the process 700.

[0046] Illustrative Process

[0047] Figure 3 600 is an example process 600 shown according to an embodiment of the present invention. Whether in part or in whole, process 600 may represent an aspect of implementing the various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 600 may represent an aspect of a feature implementation of communication device 510. Process 600 may include one or more operations, actions or functions shown by one or more of blocks 610, 620. Although the blocks shown are discrete, the blocks in process 600 may be split into more blocks, combined into fewer blocks or some blocks may be deleted depending on the desired implementation. In addition, the blocks of process 600 may be arranged according to Figure 6 The process 600 may be performed in the order shown, or, alternatively, may be performed in a different order. The process 600 may be implemented by the communication device 510 or any suitable user equipment (UE) or machine type device. For purposes of illustration only and without limitation, the process 600 is described below in the context of the communication device 510. The process 600 may begin at block 610.

[0048] At block 610, process 600 may involve processor 512 of communication device 510 measuring at least one reference signal from a network node. Process 600 may continue from block 610 to block 620.

[0049] At block 620, process 600 may involve processor 512 sending a beam report to a network node via transceiver 516 of communication device 510, wherein the beam report may indicate at least one beam that has been synchronized by communication device 510, and wherein the beam report may include a reporting order to determine at least one code point of a TCI field.

[0050] In some embodiments, at least one beam in the beam report may be indicated by at least one reference signal index or at least one TCI state index.

[0051] In some embodiments, an association between a reference signal corresponding to a reference signal index and a TCI state corresponding to a TCI state index is determined according to a QCL configuration or an RRC configuration in the TCI state.

[0052] In some embodiments, at least one code point of the TCI field is mapped to at least one reference signal index or at least one TCI state index according to a reporting order in a beam report.

[0053] In some embodiments, the beam report may be a latest beam report or a beam report that has been confirmed by a network node.

[0054] In some embodiments, process 600 may involve processor 512 receiving, via transceiver 516, a beam indication from a network node via DCI, wherein the beam indication may indicate a serving TCI state associated with a codepoint of a TCI field.

[0055] In some embodiments, process 600 may involve processor 512 determining a serving TCI state based on a beam report when only one beam is indicated in the beam report.

[0056] Figure 7 An example process 700 is illustrated according to another embodiment of the present invention. Process 700 may be an example implementation of the above scenario / scheme, whether in part or in full, involving beam indication of the present invention. Process 700 may represent one aspect of a feature implementation of network device 520. Process 700 may include one or more operations, actions, or functions as shown in blocks 710, 720, and 730. Although shown as discrete blocks, the various blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into fewer blocks, or eliminated depending on the desired implementation. In addition, the blocks of process 700 may be divided into more blocks, combined into more ... Figure 7 The process 700 may be performed in the order shown, or in a different order. The process 700 may be implemented by the network device 520 or any base station or network node. For illustration purposes only and without limitation, the process 700 is described below in the context of the network device 520. The process 700 may begin at block 710.

[0057] At block 710, process 700 may involve sending, by processor 522 of network device 520, at least one reference signal to a UE via transceiver 526 of network device 520. Process 700 may continue from block 710 to block 720.

[0058] At block 720 , process 700 may involve processor 522 receiving a beam report from the UE via transceiver 526 , wherein the beam report indicates at least one beam to which the UE is synchronized. Process 700 may continue from block 720 to block 730 .

[0059] At block 730, process 700 may involve processor 522 determining at least one code point of the TCI field according to a reporting order in the beam report.

[0060] In some embodiments, process 700 may involve processor 522 sending a beam indication to a UE via DCI via transceiver 526, wherein the beam indication indicates a serving TCI state associated with a code point of a TCI field.

[0061] Additional Notes

[0062] The subject matter described herein sometimes shows different components contained in or connected to different other components. However, it should be understood that the multiple depicted architectures are only examples, and in fact many other architectures that implement the same function can be implemented. In a conceptual sense, any arrangement of components that implement the same function is effectively "associated", so that the desired function is realized. Therefore, regardless of the architecture or intermediate components, any two components combined to implement a specific function herein can be regarded as "associated" with each other, so that the desired function is realized. Similarly, any two components so associated can also be regarded as "operationally connected" or "operationally coupled" to each other to achieve the desired function, and any two components that can be so associated can also be regarded as "operationally connected" to each other to achieve the desired function. The specific examples of coupling in operation include but are not limited to components that can be matched and / or physically interact and / or components that can interact wirelessly and / or wirelessly interact and / or components that can interact logically and / or logically interact.

[0063] Further, with respect to any plural and / or singular terms used in this article, those skilled in the art may convert from plural to singular and / or from singular to plural when appropriate for context and / or application. For clarity, various singular / plural reciprocities may be explicitly described herein.

[0064] Furthermore, those skilled in the art will understand that, in general, the terms used herein and particularly in the appended claims (e.g., the bodies of the appended claims) are generally intended to be "open" terms, e.g., the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," etc. Those skilled in the art will also understand that if a specific number of an introduced claim recitation is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation, such intent is absent. For example, to aid understanding, the appended claims may contain use of the introductory phrases "at least one" and "one or more." However, the use of such phrases should not be interpreted as implying that any particular claim included in a claim recitation through the introduction of the indefinite article "a" or "an" will be limited to embodiments containing only one such recitation, even when the same claim contains the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an", for example, "a and / or an" should be interpreted as meaning "at least one" or "one or more", and the same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, a person skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number, for example, the unmasked recitation of "two recitations" means at least two recitations or two or more recitations in the absence of other modifiers. Furthermore, where a convention similar to “at least one of A, B, and C, etc.” is used, a person skilled in the art will understand that in the sense of this convention, it is generally intended to be interpreted as such (e.g., “a system having at least one of A, B, and C” will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Where a convention similar to “at least one of A, B, or C, etc.” is used, a person skilled in the art will understand that in the sense of this convention, it is generally intended to be interpreted as such (e.g., “a system having at least one of A, B, or C” will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). A person skilled in the art will also understand that any transitional words and / or phrases that actually indicate two or more alternatives, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of such items, any of such items, or both of such items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

[0065] As can be seen from the above, it can be understood that various embodiments of the present invention have been described herein for illustrative purposes, and various modifications can be made without departing from the scope and spirit of the present invention. Therefore, the various embodiments disclosed herein are not meant to be restrictive, and the true scope and spirit are determined by the appended claims.

Claims

1. A beam reporting method, characterized in that: include: measuring, by a processor of the device, at least one reference signal from a network node; as well as A beam report is sent by the processor to the network node, wherein the beam report indicates at least one beam synchronized by the device, and wherein the beam report includes a reporting order to determine at least one code point of a transmission configuration indicator (TCI) field.

2. The beam reporting method according to claim 1, characterized in that: The at least one beam in the beam report is indicated by at least one reference signal index or at least one TCI state index.

3. The beam reporting method according to claim 2, characterized in that: According to the quasi-co-site QCL configuration or the radio resource control RRC configuration in the TCI state, determine the association between the reference signal corresponding to the reference signal index and the TCI state corresponding to the TCI state index.

4. The beam reporting method according to claim 2, wherein: According to the reporting order in the beam report, the at least one code point of the TCI field is mapped to the at least one reference signal index or the at least one TCI state index.

5. The beam reporting method according to claim 4, characterized in that: The beam report is the latest beam report sent by the device or the beam report that has been confirmed by the network node.

6. The beam reporting method according to claim 1, characterized in that: Further including: The processor receives a beam indication through downlink control information DCI from the network node, wherein the beam indication indicates a service TCI state associated with a code point of the TCI field.

7. The beam reporting method according to claim 1, wherein: Further including: In the case that only one beam is indicated in the beam report, the processor determines the service TCI status based on the beam report.

8. A device for beam reporting, characterized in that: include: a transceiver for wirelessly communicating with at least one network node during operation; as well as A processor is communicatively coupled to the transceiver such that during operation, the processor performs operations including: measuring at least one reference signal from the network node; as well as A beam report is sent, via the transceiver, to the network node, wherein the beam report indicates at least one beam synchronized by the device, and wherein the beam report includes a reporting order to determine at least one code point of a transmission configuration indicator (TCI) field.

9. The device for beam reporting according to claim 8, characterized in that The at least one beam in the beam report is indicated by at least one reference signal index or at least one TCI state index.

10. The device for beam reporting according to claim 9, characterized in that: According to the quasi-co-site QCL configuration or the radio resource control RRC configuration in the TCI state, determine the association between the reference signal corresponding to the reference signal index and the TCI state corresponding to the TCI state index.

11. The device for beam reporting according to claim 10, characterized in that: According to the reporting order in the beam report, the at least one code point of the TCI field is mapped to the at least one reference signal index or the at least one TCI state index.

12. The device for beam reporting according to claim 11, characterized in that The beam report is the latest beam report sent by the device or the beam report that has been confirmed by the network node.

13. The device for beam reporting according to claim 8, characterized in that The processor is further configured to perform the following operations: The transceiver receives a beam indication via downlink control information DCI from the network node, wherein the beam indication indicates a service TCI state associated with a code point of the TCI field.

14. The device for beam reporting according to claim 8, characterized in that: The processor is further configured to perform the following operations: In the case that only one beam is indicated in the beam report, the service TCI status is determined based on the beam report.

15. A beam reporting method, characterized in that: include: Sending, by a processor of the network node, at least one reference signal to a user equipment UE; Receiving, by the processor, a beam report from the UE, wherein the beam report indicates at least one beam synchronized by the UE; as well as The processor determines at least one code point of the transmission configuration indicator TCI field according to the reporting order in the beam report.

16. The beam reporting method according to claim 15, characterized in that: The at least one beam in the beam report is indicated by at least one reference signal index or at least one TCI state index.

17. The beam reporting method according to claim 16, wherein: According to the quasi-co-site QCL configuration or the radio resource control RRC configuration in the TCI state, determine the association between the reference signal corresponding to the reference signal index and the TCI state corresponding to the TCI state index.

18. The beam reporting method according to claim 16, wherein: According to the reporting order in the beam report, the at least one code point of the TCI field is mapped to the at least one reference signal index or the at least one TCI state index.

19. The beam reporting method according to claim 18, wherein: The beam report is the latest beam report sent by the UE or the beam report confirmed by the network node.

20. The beam reporting method according to claim 15, characterized in that: Further including: the processor sending a beam indication to the UE via downlink control information DCI, wherein the beam indication indicates a service TCI state associated with a code point of the TCI field.

Images