Beam report response method and equipment thereof

Abstract

The invention discloses a beam report response method and equipment thereof. Various solutions for beam report response of user equipment and a network node in mobile communication are described. A device may send a report indicating at least one beam to a network node. The device may receive downlink control information (DCI) indicating an indicator from the network node within an effective duration corresponding to the report. The device may determine whether the report has been received or confirmed according to the indicator. If the report is received or acknowledged by the network node, the device may perform beam switching or beam synchronization based on the at least one beam indicated in the report.

Description

Technical Field

[0001] The present application relates to the field of mobile communications, and in particular to beam reporting responses of user equipment (UE) and network equipment in mobile communications. Background Art

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

[0003] In the traditional beam management process, a network node may transmit 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. However, when the network node fails to successfully receive the beam report, the UE cannot know whether the network node has received or confirmed the beam report. Therefore, ambiguity may occur between the UE and the network node due to the loss / failure of the beam report.

[0004] Therefore, how to respond to beam reports becomes an important issue in newly developed wireless communication networks. Therefore, it is necessary to provide an appropriate solution to reduce the ambiguity of whether the network node successfully receives the beam report from the UE. Summary of the invention

[0005] The following summary of the invention is merely illustrative 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 in this application. 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.

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

[0007] In one aspect, a method may involve a device sending a report indicating at least one beam to a network node. The report may be a single report. The method may also involve the device receiving downlink control information (DCI) indicating an indicator from the network node within a valid duration corresponding to the report. The method may also involve the device determining, based on the indicator, whether the report is received or acknowledged by the network node. The method may further involve the device performing beam switching or beam synchronization based on the at least one beam indicated in the report if the report is received or acknowledged by the network node.

[0008] In another aspect, a device may involve a transceiver that wirelessly communicates with at least one network node during operation. The device may also involve a processor that is communicatively coupled to the transceiver, so that during operation, the processor may send a report indicating at least one beam to the network node through the transceiver. The processor may also receive a DCI indicating an indicator from the network node through the transceiver within a valid duration corresponding to the report. The processor may also determine whether the report is received or acknowledged by the network node based on the indicator. The processor may further perform beam switching or beam synchronization based on the at least one beam indicated in the report if the report is received or acknowledged by the network node.

[0009] In another aspect, a method may involve a network node receiving a report indicating at least one beam from a user equipment (UE). The method may also involve the network node determining DCI related to the report. The method may further involve the network node sending a DCI indicating an indicator to the UE within a valid duration corresponding to the report, wherein the indicator indicates whether the report is received or acknowledged by the network node.

[0010] The beam report response method and device provided by the present invention can achieve the beneficial effect of reducing the ambiguity of whether a network node successfully receives a beam report from a UE.

[0011] It is worth noting that although the description provided in this application may be in the context of certain radio access technologies, networks and network topologies (such as the fifth generation system (5GS) and 4G EPS mobile network), the proposed concepts, schemes and any variations / derivatives thereof can be implemented in, for and through any other type of radio access technology, network and network topology, 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 technology. Therefore, the scope of the present invention is not limited to the examples described in this application. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0014] Figure 2 is an example scenario diagram describing the beam reporting process according to an embodiment of the present invention.

[0015] Figure 3 is an example scenario diagram describing another beam reporting process according to an embodiment of the present invention.

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

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

[0018] Figure 6 is an example scenario diagram describing another beam reporting process according to an embodiment of the present invention.

[0019] Figure 7 is an example scenario diagram describing another beam reporting process according to an embodiment of the present invention.

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

[0021] Fig. 9 is a flow chart describing an example process according to an embodiment of the present invention.

[0022] Fig.10 is a flow chart describing an example process according to another embodiment of the present invention. DETAILED DESCRIPTION

[0023] The present application discloses detailed embodiments and implementations of the claimed subject matter. 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 in the present application. 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 with ordinary knowledge in the art. In the following description, the details of known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0024] Overview

[0025] Embodiments of the present invention relate to various technologies, methods, schemes and / or solutions for beam report responses 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.

[0026] 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 reporting process response according to the content of 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 separately.

[0027] According to an implementation of the present invention, a UE (eg, UE 110) may send a report (or beam report) indicating at least one beam to a network node (eg, ground network node 125).

[0028] The beam report may indicate the beams that the device has synchronized. 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 the device has synchronized and indicate the beams that the device has not synchronized. In addition, the beam report may include at least one reference signal (RS) index (or RS identification (ID)) associated with the beam or at least one transmission configuration indicator (TCI) state index (or TCI state ID). The beam indicated in the beam report may be indicated by a reference signal index or a transmission configuration indicator (TCI) state index. That is, the UE may report (or indicate) a beam by its associated RS index or TCI state index in the beam report. Each beam in the beam report may be indicated by its associated RS index or TCI state index. Each RS index may be associated with a different TCI state index. In one example, when the RS 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 RS. In another example, when the RS or TCI status reported in the beam report is indicated as "unsynchronized", it means that the UE is not synchronized to the beam related to the TCI status or RS.

[0029] After sending a beam report to a network node, the UE may determine whether downlink control information (DCI) related to the beam report is received from the network node within a valid duration corresponding to the beam report. In the event that the UE receives DCI from the network node within a valid duration corresponding to the beam report, the UE may determine whether the beam report is received or confirmed by the network node based on the DCI.

[0030] After the UE sends a beam report to the network node, the beam report may be effective after an interval duration. That is, the effective duration corresponding to the beam report may start after an interval duration, and the interval duration may start after the beam report is transmitted to the network node. Figure 2As shown, the beam report (report #1) transmitted to the network node at time point t1 can take effect after time point t1+Y, until the new beam report (report #2) transmitted to the network node at time point t2 takes effect at time point t2+Y, that is, the effective duration of the beam report (report #1) is from time point t1+Y to time point t2+Y. According to the implementation of the content of the present invention, the interval duration can be determined based on the UE capability, configured by the network node, or configured by the network node based on the UE capability. In one example, the length of the interval duration can be zero.

[0031] The DCI from the network node may include an indicator (e.g., a new beam indicator (NBI)) to indicate whether the beam report is received or acknowledged by the network node.

[0032] In one example, in the case where the beam report is received or confirmed by the network node within the valid duration corresponding to the beam report, the network node may set the indicator to a value different from the previous value of the previous indicator. For example, if the previous value of the previous indicator is a first value (e.g., the previous NBI=1), in the case where the beam report is received or confirmed by the network node within the valid duration corresponding to the beam report, the network node may set the indicator to a second value (e.g., NBI=0, i.e., switching or changing the value of the NBI).

[0033] In another example, when the beam report is not received or confirmed by the network node, the network node may set the indicator to the same value as the previous value of the previous indicator. For example, if the previous value of the previous indicator is a first value (e.g., previous NBI=1), when the beam report is not received or confirmed by the network node within the valid duration corresponding to the beam report, the network node may set the indicator to the first value (e.g., NBI=1, i.e., the value of the NBI is not switched or changed).

[0034] In the case where the network node has not received a new beam report from a user equipment (UE), the network node may determine not to change the value of the indicator in the new downlink control information (DCI). Specifically, if the network node has not received a new beam report from the UE and the network node needs to send a new DCI to the UE, the network node may not change the value of the indicator in the new DCI (e.g., send a new DCI with an unswitched NBI). In other words, if a new beam report is not received from the UE, the network node cannot send a new DCI with a switched NBI to the UE within the valid duration corresponding to the new beam report.

[0035] In another example, if the network node does not receive a beam report from the UE, the network node may determine not to send DCI to the UE.

[0036] When the UE determines that DCI related to the beam report is received from the network node within the valid duration corresponding to the beam report, the UE can determine whether to perform beam switching or beam synchronization based on the beam report according to the DCI. In one example, in the case where the beam report is received or confirmed by the network node (i.e., the value of the indicator in the DCI is different from the previous value (e.g., DCI with switched NBI)), the UE can determine to perform beam switching or beam synchronization based on the beam indicated in the beam report. In another example, in the case where the beam report is not received or confirmed by the network node (i.e., the value of the indicator in the DCI is the same as the previous value (e.g., DCI with unswitched NBI)), the UE can maintain at least one beam in the previous beam report.

[0037] When the UE determines that DCI related to the beam report is not received from the network node within the valid duration corresponding to the beam report, the UE may maintain at least one beam in the previous beam report.

[0038] Figure 2 An example scenario 200 of a beam reporting process is described according to an embodiment of the present invention. Scenario 200 involves a UE and a network node of a serving cell (e.g., a (macro / micro) base station), 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 UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after the interval duration GAP Y). In addition, Report #1 may be effective between time point t1+Y and time point t2+Y (i.e., the effective duration of Report #1). During the effective duration of Report #1, the UE receives a DCI with a switched NBI (i.e., the value of the NBI changes from "0" to "1"). Therefore, the UE may know that Report #1 has been confirmed by the network node. The UE may perform beam switching or beam synchronization (e.g., apply or synchronize the beam in Report #1) based on Report #1 after receiving the DCI. Then, the UE may send the next beam report (i.e., Report #2) to the network at time point t2. Report #2 may be effective at time point t2+Y (i.e., after the interval duration GAP Y). In addition, Report #2 may be effective between time point t2+Y and the time point when the next beam report becomes effective (i.e., the effective duration of Report #2). During the valid duration of Report #2, the UE receives a new DCI with a switched NBI (i.e., the value of the NBI changes from "1" to "0"). Therefore, the UE can know that Report #2 has been confirmed by the network node. The UE can perform beam switching or beam synchronization based on Report #2 after receiving the new DCI (e.g., apply or synchronize the beam in Report #2).

[0039] Figure 3 Another example scenario 300 of a beam reporting process is described according to an embodiment of the present invention. Scenario 300 involves a user equipment (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 UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after the interval duration GAP Y). In addition, Report #1 may be effective from time point t1+Y to time point t2+Y (i.e., the effective duration of Report #1). During the effective duration of Report #1, the UE receives downlink control information (DCI) with an unswitched NBI (i.e., the value of the NBI has not changed). Therefore, the UE may know that Report #1 may not be confirmed by the network node. The UE may perform beam switching or beam synchronization based on Report #0 (e.g., maintaining at least one beam in Report #0). Then, the UE may send the next beam report (i.e., Report #2) to the network at time point t2. Report #2 may be effective at time point t2+Y (i.e., after the interval duration GAP Y). In addition, Report #2 may be effective from time point t2+Y to the time point when the next beam report is effective (i.e., the effective duration of Report #2). During the valid duration of Report #2, the UE receives a new DCI with a switched NBI (i.e., the value of the NBI changes from "1" to "0"). Therefore, the UE can know that Report #2 has been confirmed by the network node. The UE can perform beam switching or beam synchronization based on Report #2 (e.g., apply or synchronize the beam in Report #2) after receiving the new DCI.

[0040] Figure 4 Another example scenario 400 of a beam reporting process is described according to an embodiment of the present invention. Scenario 400 involves a user equipment (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 4, the UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after gap duration GAP Y). In addition, Report #1 may be effective from time point t1+Y to time point t2+Y (i.e., the effective duration of Report #1). During the effective duration of Report #1, the UE receives a DCI with a switched NBI (i.e., the value of the NBI changes from "0" to "1"). Therefore, the UE may know that Report #1 has been confirmed by the network node. After receiving the DCI, the UE may perform beam switching or beam synchronization (e.g., apply or synchronize the beam in Report #1) based on Report #1. In this example, the UE receives the DCI after sending the next beam report (i.e., Report #2), but Report #2 has not yet taken effect (i.e., is not within the effective duration of Report #2). Therefore, the UE may perform beam switching or beam synchronization based on Report #1.

[0041] Figure 5 Another example scenario 500 of a beam reporting process is described according to an embodiment of the present invention. Scenario 500 involves a user equipment (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 5 , the UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after gap duration GAP Y). In addition, Report #1 may be effective from time point t1+Y to time point t2+Y (i.e., the effective duration of Report #1). During the effective duration of Report #1, the UE receives a DCI with a switched NBI (i.e., the value of the NBI changes from "0" to "1"). Therefore, the UE may know that Report #1 has been confirmed by the network node. After receiving the DCI, the UE may perform beam switching or beam synchronization based on Report #1 (e.g., apply or synchronize the beam in Report #1). Then, the UE may send the next beam report (i.e., Report #2) to the network at time point t2. However, the network node does not successfully receive Report #2. Therefore, when the network node sends a new DCI to the UE during the effective duration of Report #2, the NBI value in the new DCI does not change (i.e., the NBI value is the same as the previous value), i.e., the new DCI has an unswitched NBI. Therefore, during the valid duration of Report #2, the UE can perform beam switching or beam synchronization based on Report #1 (e.g., maintain at least one beam in Report #1) after receiving new DCI.

[0042] Figure 6Another example scenario 600 of a beam reporting process is described according to an embodiment of the present invention. Scenario 600 involves a user equipment (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 6 , the UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after gap duration GAP Y). In addition, Report #1 may be effective between time point t1+Y and time point t2+Y (i.e., the valid duration of Report #1). However, the network node failed to successfully receive Report #1. Therefore, when the network node sends DCI to the UE during the valid duration of Report #1, the NBI value in the new DCI cannot be changed (i.e., the DCI cannot contain the switched NBI). That is, in this example, it is an error condition for the UE to receive a DCI containing a switched NBI (i.e., the value of the NBI changes from "0" to "1") during the valid duration of Report #1.

[0043] Figure 7 Another example scenario 700 of a beam reporting process is described according to an embodiment of the present invention. Scenario 700 involves a user equipment (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 7 , the UE may send a beam report (i.e., Report #1) to the network at time point t1. Report #1 may be effective at time point t1+Y (i.e., after gap duration GAP Y). In addition, Report #1 may be effective between time point t1+Y and time point t2+Y (i.e., the effective duration of Report #1). During the effective duration of Report #1, the UE does not receive DCI from the network node. Therefore, the UE may perform beam switching or beam synchronization based on Report #0 (e.g., maintain at least one beam in Report #0). Then, the UE may send the next beam report (i.e., Report #2) to the network at time point t2. However, the network node fails to successfully receive Report #2. Therefore, when the network node sends DCI to the UE during the effective duration of Report #2, the NBI value in the new DCI cannot be changed (i.e., the DCI cannot contain the switched NBI). That is, in this example, it is an error condition that the UE receives DCI containing the switched NBI (i.e., the value of the NBI changes from "0" to "1") during the effective duration of Report #2.

[0044] Illustrative Embodiments

[0045] Figure 8An example communication system 800 according to an embodiment of the present invention is illustrated, and the communication system includes at least an example communication device 810 and an example network device 820. The communication device 810 and the network device 820 can perform various functions to implement the schemes, techniques, processes and methods related to beam report response described in the present application, including the above-mentioned various proposed designs, concepts, schemes and methods, and scenarios / schemes of user equipment and network equipment in mobile communications, including the above-mentioned scenarios / schemes and processes 900 and 1000 described below.

[0046] The communication device 810 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 810 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 810 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 810 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 810 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 810 may include Figure 8 The communication device 810 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 8 These components are not shown in the figure or described below.

[0047] The network device 820 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 820 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 820 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 820 may include Figure 8 The network device 820 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 8 is not shown in the figure and is not described below.

[0048] In one aspect, each of the processor 812 and the processor 822 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 the processor 812 and the processor 822, in some implementations, each of the processor 812 and the processor 822 can include multiple processors, and in other implementations, it can be a single processor. On the other hand, each of the processor 812 and the processor 822 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 the processor 812 and the processor 822 is a special-purpose machine, specially designed, arranged and configured to perform specific tasks in a device (e.g., represented by the communication device 810) and a network node (e.g., represented by the network device 820), including a PHR for MTRP operation.

[0049] In some implementations, the communication device 810 may also include a transceiver 816 coupled to the processor 812 and capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 816 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 816 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 816 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 820 may also include a transceiver 826 coupled to the processor 822. The transceiver 826 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 826 may be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations, the transceiver 826 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 826 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0050] In some implementations, the communication device 810 may also include a memory 814 coupled to the processor 812 and capable of being accessed and storing data by the processor 812. In some implementations, the network device 820 may also include a memory 824 coupled to the processor 822 and capable of being accessed and storing data by the processor 822. Each of the memory 814 and the memory 824 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 814 and the memory 824 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 814 and the memory 824 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.

[0051] Each of the communication device 810 and the network device 820 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 810 as a UE and the network device 820 as a network node (e.g., TRP) in conjunction with the process 900 and the process 1000.

[0052] Illustrative Process

[0053] Fig. 9 Example process 900 is described according to an embodiment of the present invention. Process 900 may be an example implementation of the above-described scenario / scheme involving the beam report response of the present invention, whether in part or in full. Process 900 may represent one aspect of a feature implementation of communication device 810. Process 900 may include one or more operations, actions, or functions as shown in blocks 910, 920, 930, and 940. Although shown as discrete blocks, the various blocks of process 900 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 900 may be divided into more blocks, combined into fewer blocks, or omitted. Fig. 9 The process 900 may be performed in the order shown, or in a different order. The process 900 may be implemented by the communication device 810 or any suitable user equipment (UE) or machine type device. For illustration purposes only and without limitation, the process 900 is described below in the context of the communication device 810. The process 900 may start at block 910.

[0054] At block 910, process 900 may involve processor 812 of communication device 810 sending a report indicating at least one beam to a network node via transceiver 816 of communication device 810. Process 900 may continue from block 910 to block 920.

[0055] At block 920, process 900 may involve processor 812 receiving, via transceiver 816, downlink control information (DCI) indicating an indicator from a network node during a valid duration corresponding to the report. Process 900 may continue from block 920 to block 930.

[0056] At block 930 , process 900 may involve processor 812 determining, based on the indicator, whether the report is received or acknowledged by the network node. Process 900 may continue from block 930 to block 940 .

[0057] At block 940, process 900 may involve processor 812 performing beam switching or beam synchronization based on the at least one beam indicated in the report if the report is received or acknowledged by the network node.

[0058] In some embodiments, the report may be determined to be received or acknowledged if the value of the indicator is different from a previous value.

[0059] In some embodiments, the valid duration corresponding to the report may begin after an interval duration, and the interval duration may begin after the report is transmitted to the network node.

[0060] In some embodiments, the interval duration may be determined based on user equipment (UE) capabilities or configured by the network node.

[0061] In some embodiments, the valid duration corresponding to the report may be ended when the valid duration of the next report begins.

[0062] In some embodiments, the at least one beam in the report may be indicated by a reference signal index or a transmission configuration indicator (TCI) state index.

[0063] Fig.10 An example process 1000 is described according to another embodiment of the present invention. Process 1000 may be an example implementation of the above scenario / scheme, whether in part or in full, involving the beam report response of the present disclosure. Process 1000 may represent one aspect of a feature implementation of network device 820. Process 1000 may include one or more operations, actions, or functions as shown in blocks 1010, 1020, and 1030. Although shown as discrete blocks, various blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into fewer blocks, or omitted depending on the desired implementation. In addition, the blocks of process 1000 may be divided into more blocks, combined into more ... Fig.10 The process 1000 may be performed in the order shown, or in a different order. The process 1000 may be implemented by the network device 820 or any base station or network node. For illustration purposes only and without limitation, the process 1000 is described below in the context of the network device 820. The process 1000 may begin at block 1010.

[0064] At block 1010, process 1000 may involve processor 822 of network device 820 receiving a report indicating at least one beam from a user equipment (UE) via transceiver 826 of network device 820. Process 1000 may continue from block 1010 to block 1020.

[0065] At block 1020 , process 1000 may involve processor 822 determining downlink control information (DCI) associated with the report. Process 1000 may continue from block 1020 to block 1030 .

[0066] At block 1030, process 1000 may involve processor 822 sending the downlink control information indicating an indicator to the user equipment during a valid duration corresponding to the report via transceiver 826. The indicator may indicate whether the report is received or acknowledged by the network node.

[0067] In some embodiments, the report may be determined to be received or acknowledged if the value of the indicator is different from a previous value.

[0068] In some embodiments, the valid duration corresponding to the report may start after an interval duration, and the interval duration may start after the report is received from the user equipment.

[0069] In some embodiments, the interval duration may be determined based on user equipment capabilities, or may be configured by the network node.

[0070] In some embodiments, the valid duration corresponding to the report may be ended when the valid duration of the next report begins.

[0071] In some embodiments, the at least one beam in the report may be indicated by a reference signal index or a transmission configuration indicator (TCI) state index.

[0072] In some embodiments, process 1000 may involve processor 822 determining not to change the value of the indicator in the new downlink control information if no new report is received from the user equipment.

[0073] In some embodiments, process 1000 may involve processor 822 determining not to send the downlink control information to the user equipment if the network node does not receive the report from the user equipment.

[0074] Additional Notes

[0075] The subject matter described in this application sometimes shows different components contained in or connected to different other components. But it should be understood that the multiple depicted architectures are only examples, and in fact many other architectures that realize the same function can be implemented. In a conceptual sense, any arrangement of components that realize the same function is effectively "associated", so that the desired function can be realized. Therefore, regardless of the architecture or intermediate components, any two components combined in this application to realize a specific function can be regarded as "associated" with each other, so that the desired function can be realized. Similarly, any two components so associated can also be regarded as "operationally connected" or "operationally coupled" to each other to realize the desired function, and any two components that can be so associated can also be regarded as "operationally connected" to each other to realize 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.

[0076] Further, with respect to any plural and / or singular terms used in the present application, those skilled in the art may convert from plural to singular and / or from singular to plural when appropriate for the context and / or application. For the sake of clarity, various singular / plural interchanges may be explicitly set forth in the present application.

[0077] Furthermore, those skilled in the art will understand that, in general, the terms used in this application and especially 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", the term "including" should be interpreted as "including but not limited to", 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 the 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, those 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, it is generally intended to be interpreted in the sense that a person skilled in the art will understand this convention (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, it is generally intended to be interpreted in the sense that a person skilled in the art will understand this convention (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."

[0078] As can be seen from the above, it can be understood that various embodiments of the present invention have been described in this application 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 in this application are not meant to be restrictive, and the true scope and spirit are determined by the appended claims.

Claims

1. A beam report response method, characterized in that: include: sending, by the processor, a report indicating at least one beam to a network node; receiving, by the processor, downlink control information indicating an indicator from the network node during a valid duration corresponding to the report; determining, by the processor, based on the indicator, whether the report is received or acknowledged by the network node; as well as By the processor, in a case where the report is received or confirmed by the network node, beam switching or beam synchronization is performed based on the at least one beam indicated in the report.

2. The beam report response method according to claim 1, characterized in that: In case the value of the indicator is different from a previous value, the report is determined to be received or acknowledged.

3. The beam report response method according to claim 1, characterized in that: The validity duration corresponding to the report starts after an interval duration, and wherein the interval duration starts after the report is transmitted to the network node.

4. The beam report response method according to claim 3, characterized in that: The interval duration is determined based on user equipment capabilities, or is configured by the network node.

5. The beam report response method according to claim 1, characterized in that: In case the validity duration of the next report starts, the validity duration corresponding to the report is ended.

6. The beam report response method according to claim 1, characterized in that: The at least one beam in the report is indicated by a reference signal index or a transmission configuration indicator state index.

7. A device for beam reporting response, 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: sending, by the transceiver, a report indicating at least one beam to a network node; receiving, by the transceiver, downlink control information indicating an indicator from the network node during a valid duration corresponding to the report; determining, based on the indicator, whether the report is received or acknowledged by the network node; as well as In a case where the report is received or confirmed by the network node, beam switching or beam synchronization is performed based on the at least one beam indicated in the report.

8. The device for beam reporting response according to claim 7, characterized in that: In case the value of the indicator is different from a previous value, the report is determined to be received or acknowledged.

9. The device for beam reporting response according to claim 7, characterized in that: The validity duration corresponding to the report starts after an interval duration, and wherein the interval duration starts after the report is transmitted to the network node.

10. The device for beam reporting response according to claim 9, characterized in that: The interval duration is determined based on user equipment capabilities, or is configured by the network node.

11. The device for beam reporting response according to claim 7, characterized in that: In case the validity duration of the next report starts, the validity duration corresponding to the report is ended.

12. The device for beam reporting response according to claim 7, characterized in that: The at least one beam in the report is indicated by a reference signal index or a transmission configuration indicator state index.

13. A beam reporting response method, characterized in that: include: receiving, by a processor of the network node, from a user equipment a report indicating at least one beam; determining, by the processor, downlink control information associated with the report; as well as sending, by the processor, the downlink control information indicating an indicator to the user equipment within a valid duration corresponding to the report, The indicator indicates whether the report is received or confirmed by the network node.

14. The beam reporting response method according to claim 13, characterized in that: In case the value of the indicator is different from a previous value, the report is determined to be received or acknowledged.

15. The beam reporting response method according to claim 13, characterized in that: The validity duration corresponding to the report starts after a gap duration, and wherein the gap duration starts after the report is received from the user equipment.

16. The beam reporting response method according to claim 15, characterized in that: The interval duration is determined based on user equipment capabilities, or is configured by the network node.

17. The beam reporting response method according to claim 13, characterized in that: In case the validity duration of the next report starts, the validity duration corresponding to the report is ended.

18. The beam reporting response method according to claim 13, characterized in that: The at least one beam in the report is indicated by a reference signal index or a transmission configuration indicator state index.

19. The beam reporting response method according to claim 13, characterized in that: Further including: The processor determines, in the case where no new report is received from the user equipment, not to change the value of the indicator in the new downlink control information.

20. The beam reporting response method according to claim 13, characterized in that: Further including: The processor determines, in a case where the network node does not receive the report from the user equipment, not to transmit the downlink control information to the user equipment.

Images