Method and communication apparatus for reporting a beam report

Abstract

Provided are a method for reporting a beam report and a communication device, which are applied to the field of communication. The method comprises the following steps: a UE sends a first scheduling request (SR) to a network device to request reporting of a beam report, and carries one or more of the following in the first SR: first indication information, priority information of the beam report; so that the network device can accurately learn the demand of the UE for sending the beam report, thereby improving the reliability of transmitting the beam report. Compared with the traditional SR which is only used for requesting uplink scheduling resources, the first SR introduced in the embodiment of the present application supports requesting uploading of the beam report, which helps to improve the flexibility and accuracy of beam management.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular, to a method and a communication device for reporting beam reports. Background Art

[0002] In fifth-generation (5G) communication systems, network equipment (e.g., next-generation base stations (gNBs)) can interact with user equipment (UEs) using beamforming technology. UEs measure beams and report beam reports to the network equipment. Furthermore, UEs can send scheduling requests (SRs) to the network equipment to request uplink transmission resources. However, current methods for UEs to report beam reports have limitations. Therefore, enhancing traditional scheduling requests (SRs) is an urgent issue. Summary of the Invention

[0003] In view of this, the present application provides a method for reporting beam reports, a communication device, a chip system, a computer-readable storage medium, a computer program product and a communication system, so that the network equipment can accurately know the UE's need to send beam reports, thereby improving the reliability of the transmission beam reports.

[0004] In a first aspect, a method for reporting a beam report is provided. The method may be performed, for example, by a UE, or by a component configured in the UE (such as a circuit, chip, or chip system), or may be implemented by a logic module or software capable of implementing all or part of the UE's functions. This application is not limited thereto.

[0005] Specifically, the method includes: the UE sends a first scheduling request SR to the network device, the first SR is used to request reporting of a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; the first indication information is used to indicate the request type of the first SR; and reporting the beam report.

[0006] In some embodiments, after the UE sends the first SR, the transmission resources used by the UE to report the beam report can be pre-configured resources or configured by the network device, without specific limitation. For example, after the UE sends the first SR to the network device, it receives DCI issued by the network device, where the DCI is used to indicate the transmission resources; the UE uses the transmission resources indicated by the DCI to report the beam report. For another example, after sending the first SR, the UE reports the beam report after an interval of preset time domain resources.

[0007] Based on the above technical solution, the UE sends a first scheduling request SR to the network device to request the reporting of a beam report, and the first SR carries one or more of the following: first indication information and beam report priority information; this enables the network device to accurately understand the UE's need to send a beam report, thereby improving the reliability of the transmission beam report. Compared to the traditional SR that is only used to request uplink scheduling resources, the first SR introduced in the embodiment of the present application supports requesting uplink beam reports, which helps to improve the flexibility and accuracy of beam management.

[0008] It should be noted that the UE reports beam reports in either the first or second mode. The first mode refers to a mode in which the UE reports beam reports using uplink control information (UCI) in pre-configured resources, independent of network device scheduling. The second mode refers to a mode in which the UE reports beam reports based on resources dynamically scheduled by the network device. For example, the first mode is Mode B in the 3GPP standard, and the second mode is Mode A in the 3GPP standard.

[0009] The embodiments of the present application provide solutions for reporting beam reports using the first mode or the second mode.

[0010] In one possible implementation, when the UE reports a beam report in the first mode, the first SR includes at least the first indication information; the first indication information is used to indicate that the request type of the first SR is a first type, where the first type is an SR for requesting the transmission of a beam report. The first type is an extended SR type (or enhanced SR) in this embodiment of the present application. Therefore, this embodiment of the present application introduces an extended SR type that supports the UE's request to upload a beam report, thereby more accurately reflecting the UE's resource requirements.

[0011] Optionally, the first indication information is encoded using a first number of bits, where the value of the first number of bits is used to indicate the type of the first SR. For example, the first number is 1; a 1-bit encoding scheme can reuse a first PUCCH channel resource (e.g., the first PUCCH channel in step 1 in mode B) to save channel overhead.

[0012] Optionally, the first indication information is further used to indicate whether the first SR requests uplink shared channel resources.

[0013] Optionally, the first indication information is encoded using a second number of bits, where different values ​​of the second number of bits are used to indicate whether the first SR is an SR for sending a beam report and / or whether the first SR requests uplink shared channel resources. For example, the second number is 2. Therefore, the second number of bits encoding scheme can enhance the flexibility of the first indication information, thereby indicating more meanings.

[0014] In one possible implementation, before sending the first SR, the method further includes: the UE receiving RRC signaling from a network device, where the RRC signaling includes a coding scheme configuration for the first indication information. Therefore, the UE can obtain the coding scheme for the first indication information by receiving the RRC signaling sent by the network device, so that the UE can subsequently use the coding scheme to send the first indication information and flexibly determine the meaning of the first indication information based on its own needs, thereby indicating the request type of the SR, for example, for requesting uplink resources or for requesting an upload beam report.

[0015] Exemplarily, the first indication information is a scheduling request beam report indication (SR beam report indicator, SRBRI).

[0016] The following describes a solution for the second mode. In one possible implementation, when the UE uses the second mode to report the beam report, the first SR includes at least the priority information of the beam report; the method further includes: the UE receives downlink control information DCI from the network device, and the DCI is used to schedule uplink transmission resources for transmitting the beam report based on the priority information; the UE reports the beam report on the uplink transmission resources based on the scheduling of the DCI. Therefore, by adding the priority information of the beam report to the first SR, the network device can allocate transmission resources to the UE according to the priority information, thereby ensuring the smooth transmission of high-priority beam reports.

[0017] In one possible implementation, the priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report. For example, the third number is 2.

[0018] To further dynamically guide network devices in dynamically allocating appropriate resources for UEs, embodiments of the present application also propose the introduction of resource indication information in the SR. The first SR also includes resource indication information, which indicates whether uplink shared channel resources are required. Therefore, by adding resource indication information to the first SR, network devices can accurately understand the UE's resource requirements.

[0019] Optionally, the resource indication information is encoded using a fourth number of bits, where different values ​​of the fourth number of bits are used to indicate whether uplink shared channel resources are required. For example, the fourth number is 1. Therefore, by introducing one bit of information to indicate resource requirements, excessive overhead is avoided, thereby helping to save channel overhead.

[0020] In some application scenarios, the method is applied to a vehicle-to-everything (V2X) communication scenario; the UE is a vehicle-to-everything (UE) device. The V2X device sends a first SR to a network device or another V2X device, where the first SR is used to request a beam report. The first SR includes one or more of the following: first indication information and beam report priority information; the first indication information indicates the request type of the first SR; and the V2X device reports the beam report. Optionally, the first indication information indicates the request type of the first SR, and the first indication information occupies a small number of bits (e.g., 1 or 2 bits), thereby reducing signaling overhead.

[0021] In other application scenarios, the method is applied to industrial Internet of Things (IIOT) or high-reliability, low-latency industrial automation communication scenarios; the UE is an IIOT device; the IIOT device sends a first scheduling request SR to a network device, and the first SR is used to request a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; wherein the first indication information is used to indicate the request type of the first SR; the IIOT device reports the beam report. Optionally, the first SR includes priority information of the beam report. Therefore, the IIOT device can ensure the transmission priority of critical signals by sending the priority information of the beam report to the network device so that the network device can use the priority information to respond or schedule resources.

[0022] In some other application scenarios, the method is applied to smart manufacturing scenarios based on a communication network (such as 5G); the UE is a machine device; the machine device sends a first scheduling request SR to a network device or a management device, and the first SR is used to request a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; wherein the first indication information is used to indicate the request type of the first SR; the machine device reports a beam report. The method for reporting a beam report in the embodiment of the present application enables a device or network to accurately understand the needs of the machine device, which helps to optimize the communication scheduling between machine devices in a communication network (such as a 5G network), thereby improving production efficiency.

[0023] It should be understood that in the above-mentioned application scenarios, various specific implementation methods of the first SR can be referred to the above description. For the sake of brevity, they will not be elaborated here one by one.

[0024] In a second aspect, a method for reporting beam reports is provided. This method can be performed, for example, by a network device, or by a component configured in the network device (such as a circuit, chip, or chip system), or by a logic module or software that implements all or part of the network device's functions. This application is not limited thereto.

[0025] Specifically, the method includes: the network device receives a first scheduling request SR from the UE, the first SR is used to request reporting of a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; the first indication information is used to indicate the request type of the first SR; and receives the beam report.

[0026] Based on the above technical solution, the network device can accurately know the UE's need to send a beam report based on one or more of the following carried in the first SR: first indication information, priority information of the beam report, by receiving the first SR sent by the UE, thereby improving the reliability of the transmission beam report. That is, after receiving the first SR sent by the UE, the network device can identify the request type of the first SR based on the first indication information in the first SR; thereby ensuring that the beam report triggered by the UE through mode B is correctly processed. At the same time, since no new signaling is introduced, additional signaling overhead can be reduced. Compared with the traditional SR that is only used to request uplink scheduling resources, the first SR introduced in the embodiment of the present application supports requesting uplink beam reports, which helps to improve the flexibility and accuracy of beam management.

[0027] In one possible implementation, when the UE adopts the first mode to report the beam report, the first SR includes at least: the first indication information; the first indication information is used to indicate that the request type of the first SR is the first type, and the first type is an SR for requesting to receive the beam report.

[0028] In one possible implementation, the first indication information is encoded using a first number of bits, and the value of the first number of bits is used to indicate the type of the first SR. Therefore, after receiving the first SR sent by the UE, the network device can accurately identify the request type of the first SR based on the value of the first indication information (e.g., SRBRI) in the first SR, and thus respond to the UE based on the request type, for example, ensuring that a beamforming report triggered by the UE via Mode B is correctly processed.

[0029] In a possible implementation manner, the first indication information is further used to indicate whether the first SR requests uplink shared channel resources.

[0030] In one possible implementation, the first indication information is encoded using a second number of bits, and different values ​​of the second number of bits are used to indicate whether the first SR is an SR reported by a received beam, and / or whether the first SR requests uplink shared channel resources.

[0031] In one possible implementation, before receiving the first SR, the method further includes: the network device sending RRC signaling to the UE, where the RRC signaling includes a configuration of a coding scheme for the first indication information. Therefore, the network device configures the coding scheme for the first indication information to the UE in advance, so that the UE can subsequently use the coding scheme to send the first indication information.

[0032] In one possible implementation, when the UE adopts the second mode to report the beam report, the first SR includes at least the priority information of the beam report; the method also includes: the network device sends downlink control information DCI, and the DCI is used to schedule uplink transmission resources for transmitting the beam report based on the priority information; and receives the beam report on the uplink transmission resources.

[0033] Optionally, the priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

[0034] In a possible implementation manner, the first SR further includes resource indication information, where the resource indication information is used to indicate whether uplink shared channel resources are required.

[0035] Optionally, the resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are used to indicate whether uplink shared channel resources are required.

[0036] In some application scenarios, the method is applied to a vehicle-to-vehicle communication scenario; the network device is a device in the vehicle-to-vehicle communication scenario; the network device receives a first scheduling request (SR) from a V2X device, the first SR being used to request a beam report; the first SR including one or more of the following: first indication information, priority information for the beam report; wherein the first indication information is used to indicate the request type of the first SR; and the network device receives the beam report reported by the V2X device. Based on this, the network device can accurately identify the needs of the V2X device, thereby improving transmission reliability. Furthermore, for inter-device communication scenarios (e.g., between one V2X device and another V2X device), this method also helps improve the reliability of inter-vehicle collaborative communication.

[0037] In other application scenarios, the method is applied to industrial Internet of Things IIOT or high-reliability, low-latency industrial automation communication scenarios; the network device is a network device in the industrial Internet of Things IIOT or high-reliability, low-latency industrial automation communication scenarios; the network device receives a first scheduling request SR sent by the IIOT device, and the first SR is used to request a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; wherein the first indication information is used to indicate the request type of the first SR; and receives the beam report from the IIOT device. Optionally, the first SR includes priority information of the beam report. Therefore, the network device can ensure the transmission priority of critical signals by obtaining the priority information of the beam report in the first SR and using the priority information to respond or schedule resources.

[0038] In some other application scenarios, the method is applied to a smart manufacturing scenario based on a communication network (such as 5G); the network device is a network device or a management device in the smart manufacturing scenario; the network device receives a first scheduling request SR from a machine device, the first SR is used to request a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; wherein the first indication information is used to indicate the request type of the first SR; and the beam report from the machine device is received. The method for reporting beam reports in the embodiment of the present application enables the network to accurately understand the needs of the machine device, which helps to optimize the communication scheduling between machine devices in the communication network (such as a 5G network), thereby improving production efficiency.

[0039] It should be noted that the second aspect is the implementation of the first aspect on the network device side. The explanations (such as the explanation of terms and description of specific implementations), supplements, and descriptions of beneficial effects regarding the first aspect also apply to the second aspect. For the sake of brevity, the various specific implementations of the second aspect will not be detailed.

[0040] In a third aspect, a communication device is provided, comprising modules or units for executing the method in any possible implementation of the first aspect.

[0041] In one design, the communication device may include a module that executes the methods / operations / steps / actions described in each of the above aspects. The module may be a hardware circuit, software, or a combination of hardware circuit and software.

[0042] In one design, the communication device is a communication chip, which may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0043] In another design, the communication apparatus is a communication device, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0044] In another design, the communication device is used to execute the method in the above-mentioned first aspect or any possible implementation of the first aspect. The communication device can be configured in the above-mentioned UE, or the communication device itself is the UE.

[0045] Alternatively, the communication device may be configured in a V2X device, or the communication device itself may be a V2X device. Alternatively, the communication device may be configured in an IIOT device, or the communication device itself may be an IIOT device. Alternatively, the communication device may be configured in a machine device in a smart manufacturing scenario, or the communication device itself may be a machine device in a smart manufacturing scenario.

[0046] In a fourth aspect, a communication device is provided, comprising modules or units for executing the method in any possible implementation of the second aspect.

[0047] In one design, the communication device may include a module that executes the methods / operations / steps / actions described in each of the above aspects. The module may be a hardware circuit, software, or a combination of hardware circuit and software.

[0048] In one design, the communication device is a communication chip, which may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0049] In another design, the communication apparatus is a communication device, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0050] In another design, the communication device is used to execute the method in any possible implementation of the above-mentioned network device. The communication device can be configured in the above-mentioned network device, or the communication device itself is the network device.

[0051] Optionally, the network device may be an access network device (e.g., a gNB) or a core network device (e.g., an AMF network element, an AF network element, or a NEF network element). Alternatively, the network device may be a device in an Internet of Vehicles (IoV) communication scenario. Alternatively, the network device may be a network device in an Industrial Internet of Things (IIoT) or high-reliability, low-latency industrial automation communication scenario. Alternatively, the network device may be a network device or management device in an intelligent manufacturing scenario.

[0052] In a fifth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be configured to execute instructions or data in the memory to implement the method of any possible implementation of the first aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0053] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0054] In another implementation, the communication device is a chip configured in a UE. When the communication device is a chip configured in a UE, the communication interface may be an input / output interface.

[0055] In a sixth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be configured to execute instructions or data in the memory to implement the method of any possible implementation of the second aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0056] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0057] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface may be an input / output interface.

[0058] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation of any aspect.

[0059] In a specific implementation, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0060] In an eighth aspect, a communication device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any possible implementation of any of the above aspects.

[0061] Optionally, there are one or more processors and one or more memories.

[0062] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0063] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated on the same chip as the processor or be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0064] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, data output by the processor can be output to the transmitter, and input data received by the processor can be received from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0065] The processing device in the eighth aspect may be one or more chips. The processor in the processing device may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated into the processor or located independently of the processor.

[0066] In a ninth aspect, a computer program product is provided, comprising: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute a method in any possible implementation of any of the above aspects.

[0067] In the tenth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute a method in any possible implementation of any of the above aspects.

[0068] In an eleventh aspect, embodiments of the present application provide a chip system comprising one or more processors configured to retrieve and execute instructions stored in a memory, thereby executing the method of any of the above aspects or any possible implementations of each aspect. The chip system may be composed of a chip or may include a chip and other discrete devices.

[0069] Among them, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0070] In the twelfth aspect, a communication system is provided, including the aforementioned UE and network equipment.

[0071] Optionally, the communication system may further include other devices communicating with the UE and / or network devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 is an example diagram of a communication system;

[0073] Figure 2 This is an example diagram of access network equipment;

[0074] Figure 3A This is an example diagram of a UE sending a beam report using mode A in an existing solution;

[0075] Figure 3B This is an example diagram of a UE sending a beam report using mode B in an existing solution;

[0076] Figure 4 This is an example interaction diagram of a method for reporting a beam report according to an embodiment of the present application;

[0077] Figure 5 This is an example diagram of a UE sending a beam report using mode B in an embodiment of the present application;

[0078] Figure 6 This is an example diagram of a UE sending a beam report using mode A in an embodiment of the present application;

[0079] Figure 7 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0080] Figure 8 This is another schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0081] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0082] In the embodiments of the present application, “multiple” can be understood as “at least two”, and “multiple items” can be understood as “at least two items”.

[0083] The present application can be applied to a communication system. The mobile communication system includes, but is not limited to, the following systems, for example: a long term evolution (LTE) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system or new radio (NR), a 5.5G system, and a future mobile communication system, vehicle-to-X (V2X), which can include vehicle to network (V2N), vehicle to vehicle (V2V), vehicle to infrastructure (V2I), vehicle to pedestrian (V2P), etc., LTE-V, Internet of Vehicles, machine type communication (MTC), Internet of Things (IoT), long term evolution-machine (LTE-M), machine to machine (M2M), etc. The 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA). The technical solutions provided by the present application can also be applied to future communication systems. The present application is not limited in this regard.

[0084] Figure 1 FIG. 1 is a schematic diagram of a communication system 100 to which embodiments of the present application are applied. The communication system 100 can include a network device, such as the network device 110 shown in FIG. 1. The communication system 100 can also include a terminal device, such as the terminal device 120 shown in FIG. 1. The network device 110 and the terminal device 120 can communicate through a wireless link. Figure 1 Figure 1 The network device 110 and the terminal device 120 can communicate through a wireless link.

[0085] Figure 1 ​The example shows one network device 110 and one terminal device 120. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.

[0086] The network devices in this application may be network-side devices such as access networks and core network devices. Access network devices are sometimes also referred to as access nodes. Access network devices have wireless transceiver functions and are used to communicate with terminals. Access network devices include but are not limited to base stations (base stations), evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in open access networks (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices may also be modules or units that can implement some of the functions of a base station. Access network devices may be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network devices may also be servers, wearable devices, or vehicle-mounted devices. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. A base station can communicate with a terminal or through a relay station. A terminal can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology or device form used by the access network device. In this application, the access network device is referred to as a network device.

[0087] In this application, the device for implementing the function of a network device can be a network device, or a device that can support the network device to implement the function, such as a processor, circuit, chip, or chip system, etc. The device can be installed in the network device or connected to the network device for use. In the technical solution provided in this application, the technical solution provided in this application is described by taking the device for implementing the function of a network device as an example.

[0088] The terminal device in this application may be a wireless terminal device capable of receiving network device scheduling and instruction information. A wireless terminal device may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. For example, a terminal device may communicate with one or more core networks or the Internet via a radio access network (RAN). A terminal device may also be referred to as a terminal, user equipment (UE), mobile station, or mobile terminal. The terminal device can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, or satellite communication. The terminal may be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of the present application do not limit the form of the terminal device.

[0089] As an example and not a limitation, in the embodiments of the present application, the UE may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0090] In addition, in the embodiments of the present application, the UE may also be a terminal device in the Internet of Things (IoT) system. The IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things and things. The embodiments of the present application do not limit the specific technology and specific device form used by the terminal device.

[0091] In an embodiment of the present application, a UE may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system may be any one or more computer operating systems that implement service processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as a browser, an address book, word processing software, and instant messaging software. Furthermore, the embodiments of the present application do not specifically limit the specific structure of the execution entity of the method provided in the embodiments of the present application; as long as it is capable of communicating according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, it is sufficient. For example, the execution entity of the method provided in the embodiments of the present application may be a terminal device, or a functional module in the terminal device that is capable of calling and executing a program.

[0092] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing portions of a base station's functionality. For example, a network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate or included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0093] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in the ORAN system, the CU may also be called an O-CU (Open CU), the DU may also be called an O-DU, the CU-CP may also be called an O-CU-CP, the CU-UP may also be called an O-CU-UP, and the RU may also be called an O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented as a software module, a hardware module, or a combination of software and hardware modules. The CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0094] In addition, the access network device in the embodiments of the present application is also referred to as an access node. The access network device has wireless transceiver functions and is used to communicate with the terminal. Access network devices include, but are not limited to, base stations (basestations), evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in open access networks (ORAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems. The access network device may also be a module or unit that can implement some of the functions of a base station. For example, the access network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU) described below. In the ORAN system, the CU can also be referred to as the O-CU, the DU can also be referred to as the open (O)-DU, the CU-CP can also be referred to as the O-CU-CP, the CU-UP can also be referred to as the O-CUP-UP, and the RU can also be referred to as the O-RU. The access network device can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, a wearable device, or an in-vehicle device. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. A base station can communicate with a terminal or communicate with the terminal through a relay station. A terminal can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technology and device form used by the access network device.

[0095] The UE of the embodiment of the present application may also be referred to as: terminal equipment, station, mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0096] The access network equipment and / or the terminal can be fixed or movable. The access network equipment and / or the terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the access network equipment and terminals. The access network equipment and the terminal equipment can be deployed in the same scenario or different scenarios. For example, the access network equipment and the terminal equipment are deployed on land at the same time; or, the access network equipment is deployed on land and the terminal equipment is deployed on the water surface, etc., and no further examples are given.

[0097] In the present application, the device for realizing the function of the network device can be a network device, or a device that can support the network device to realize the function, such as a processor, circuit, chip, or chip system, etc. The device can be installed in the network device or connected to the network device for use. For example, the device for realizing the function of the network device can be an access network device, or a module in the access network device (such as a chip, chip system, or software module, etc.), or a control subsystem that includes the function of the access network device. For example, the control subsystem that includes the function of the access network device can be a control center in a scenario where the terminal can be applied, such as a smart grid, industrial control, intelligent transportation, or a smart city. In the technical solution provided in the present application, the technical solution provided in the present application is described by taking the device for realizing the function of the network device as an example, which is a network device.

[0098] In this application, the device for implementing the function of a terminal device can be a terminal device, or a device that can support the terminal device to implement the function, such as a processor, circuit, chip, or chip system, etc. The device can be installed in the terminal device or connected to the terminal device for use. In the technical solution provided in this application, the technical solution provided in this application is described by taking the terminal device as an example in which the device for implementing the function of the terminal device is a terminal device.

[0099] Communication between access network equipment and terminal devices may follow a certain protocol layer structure. Exemplarily, the protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure may include at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, or a physical (PHY) layer. For example, the user plane protocol layer structure may include at least one of the following: a service data adaptation protocol (SDAP) layer, a PDCP layer, an RLC layer, a MAC layer, or a physical layer.

[0100] Figure 2 This is a schematic diagram of the structure of an access network device. As an implementation example, Figure 2 As shown, the access network device may include at least one CU and at least one DU. This design can be referred to as CU-DU separation. A CU can be connected to one or more DUs. The CU and DU can be divided according to the protocol layers of the wireless network: for example, the functions of the PDCP layer and above (such as the RRC layer and SDAP layer) are located in the CU, while the functions of the protocol layers below the PDCP layer (such as the RLC layer, MAC layer, and PHY layer) are located in the DU. Another example is that the functions of the protocol layers above the PDCP layer are located in the CU, while the functions of the protocol layers below the PDCP layer are located in the DU, without limitation. When the CU includes a CU-CP and a CU-UP, the CU-CP implements the control plane functions of the CU, and the CU-UP implements the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, the CU-CP implements the RRC layer functions and the control plane functions of the PDCP layer, and the CU-UP implements the SDAP layer functions and the user plane functions of the PDCP layer. This application does not limit the names of the CU and DU. The above division of the processing functions of the CU and DU according to protocol layers is merely an example; other divisions are also possible.

[0101] The CU can be connected to the core network. Optionally, the CU can have some of the functions of the core network.

[0102] Furthermore, some functions of DU can be separated and set up. Figure 2As shown, these functions can be implemented by a radio unit (RU). The RU can have radio frequency functions. This application does not limit the name of the RU. The DU and RU can be split or separated at the PHY layer. For example, the DU can implement high-level functions in the PHY layer, and the RU can implement low-level functions in the PHY layer, or implement these low-level functions and radio frequency functions. High-level functions in the PHY layer include functions closer to the MAC layer, and low-level functions in the PHY layer include functions closer to the radio frequency. For example, high-level functions in the PHY layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling, or modulation / demodulation. Low-level functions in the PHY layer include one or more of the following: fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT), beamforming, or physical random access channel (PRACH) extraction and filtering. The RU can communicate radio frequency signals with terminal devices over the air interface. The PHY layer code precoding function can be located in the DU or the RU. The DU and RU can be split in various ways, without limitation. An interface exists between the DU and RU. For example, depending on the split method, the interface between the DU and RU can be a common public radio interface (CPRI) or an enhanced common public radio interface (eCPRI).

[0103] Optionally, any one of the above-mentioned CU, CU-CP, CU-UP, DU and RU can be a software module, a hardware structure, or a software module plus a hardware structure, without limitation. The existence forms of different entities can be the same or different. For example, CU, CU-CP, CU-UP and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here one by one. These modules and their execution methods are also within the scope of protection of the embodiments of the present application. For example, when the method of the embodiment of the present application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0104] To facilitate understanding by those skilled in the art, the following explains the terms and related technologies that may be involved in the embodiments of this application. For example, the description of some terms and technologies may also refer to the descriptions in the 3rd Generation Partnership Project (3GPP) standard protocols.

[0105] Beam: A beam is a communication resource. A beam can be wide, narrow, or other types of beams. Beam formation can be achieved through beamforming or other techniques. Beamforming techniques include digital beamforming, analog beamforming, and hybrid digital / analog beamforming. Different beams can be considered different resources. Different beams can transmit the same or different information. Alternatively, multiple beams with the same or similar communication characteristics can be considered a single beam. A beam can include one or more antenna ports for transmitting data channels, control channels, and sounding signals. For example, a transmit beam refers to the distribution of signal strength in different spatial directions after a signal is transmitted by an antenna, while a receive beam refers to the distribution of signal strength in different spatial directions of a wireless signal received by an antenna. It is understood that the one or more antenna ports that form a beam can also be considered an antenna port set.

[0106] Beam reporting refers to the process by which the UE reports beam quality and beam decision results to network equipment (e.g., the RAN). Beam determination refers to the measurement results obtained through beam measurement, such as selecting one or more beams with good beam quality from multiple beams. Beam measurement is the evaluation of the quality of the received signal by the communication device.

[0107] Beam quality: This can be measured using metrics such as reference signal received power (RSRP), block error rate (BLER), reference signal received quality (RSRQ), reference signal strength indicator (RSSI), signal to interference and noise ratio (SINR), signal to noise ratio (SNR), channel quality indicator (CQI), and correlation. It should be understood that the beam quality metrics used in the present embodiment are not limited.

[0108] The embodiment of the present application does not specifically limit the triggering event (EVENT) of the beam report. For example, the triggering event of the beam report is a triggering event defined in 3GPP.

[0109] Exemplarily, the triggering events of the beam report include the following:

[0110] Event 1: the quality of the current beam is worse than a certain threshold;

[0111] Event 2: The quality of at least one new beam (such as L1-RSRP value) is higher than a certain threshold of the quality of the current beam;

[0112] Event 7: The quality (e.g., L1-RSRP value) of at least one new beam exceeds a threshold relative to the quality of a reference signal (RS) derived from the Mth-best quality activated transmission configuration indicator (TCI) state. The Mth-best quality activated TCI state is determined based on a beam pool, where the beams are ranked from best to worst quality.

[0113] It should be understood that the values ​​of the thresholds involved in the above-mentioned events, or the quantitative indicators of signal quality, can refer to the description in the protocol, or can be set based on actual application scenarios, and the embodiments of the present application do not specifically limit this.

[0114] The UE supports the following two modes for transmission of beam reports. Figure 3A and Figure 3B Describe them separately.

[0115] refer to Figure 3A , Figure 3A FIG1 shows an example flow chart of a UE reporting a beam report based on mode A. Figure 3A As shown, it includes the following three steps:

[0116] Step 1: The UE sends a first physical uplink control channel (PUCCH) to the network device. In response, the network device receives the first PUCCH. The first PUCCH is used to request that a beam report be carried on resources of a second uplink (UL) channel.

[0117] For example, the first PUCCH occupies 1 bit. The first PUCCH includes a scheduling request SR, which is used to request a second UL channel resource to transmit a beam report.

[0118] Step 2: The network device sends downlink control information (DCI) to the UE. Correspondingly, the UE receives the DCI, which is used to indicate the second UL channel resource.

[0119] After receiving the DCI, the UE detects the DCI format to obtain the resources used to transmit the beam report, such as the second uplink channel resources.

[0120] Step 3: The UE reports a beam report via the second UL channel. Correspondingly, the network device receives the beam report sent by the UE via the second UL channel.

[0121] For example, the second UL channel is a physical uplink shared channel (PUSCH).

[0122] In Mode A, network devices dynamically schedule uplink control information (UCI) to transmit beam reports. However, because the urgency and / or resource requirements of each beam report may vary, traditional SR mechanisms cannot effectively guide network devices to dynamically allocate resources (for example, the second uplink channel). Therefore, a method that can dynamically allocate resources to transmit beam reports is urgently needed.

[0123] refer to Figure 3B , Figure 3B FIG1 shows an example flow chart of a UE reporting a beam report based on mode B. Figure 3B As shown, it includes the following two steps:

[0124] Step 1: The UE sends a first PUCCH to a network device. Correspondingly, the network device receives the first PUCCH.

[0125] For example, the first PUCCH occupies 1 bit. The first PUCCH includes a scheduling request SR, which is used to notify the network device to transmit a beam report through the second UL channel resource.

[0126] Step 2: The UE reports a beam report via the second UL channel. Correspondingly, the network device receives the beam report sent by the UE via the second UL channel.

[0127] Optionally, a fixed time domain resource is spaced between the UE executing step 1 and the UE executing step 2. For example, the UE executes step 2 a plurality of time slots after executing step 1.

[0128] In step 2 of Mode B, the UE uses the uplink control information (UCI) in the preconfigured resources of the second UL channel to transmit the beam report. This means the UE does not rely on the network device's scheduled resources to transmit the beam report. However, since traditional SR is currently used to request uplink resources, using it to transmit beam reports will cause SR functionality conflicts, making it impossible for the network device to accurately detect the SR request, thus affecting the reliability of beam report transmission.

[0129] For example, the explanations of the above-mentioned mode A and mode B may also refer to the description in the 3GPP standard protocol.

[0130] As can be seen from the above, there are certain limitations in reporting beam reports based on both Mode A and Mode B. Currently, there is no optimized solution for reporting beam reports through scheduling requests (SRs) in Mode A or Mode B.

[0131] In view of this, an embodiment of the present application provides a method for reporting a beam report, where the UE sends a first SR, which is used to request reporting a beam report, and transmits the beam report based on the first SR, thereby improving the transmission reliability of the beam report.

[0132] The following describes the solution provided by this application in detail in conjunction with the corresponding flowcharts. It will be understood that the schematic flowcharts provided in this application primarily illustrate the method using different devices (e.g., UE or network devices) as examples of the execution entities of the interaction diagrams, but this application does not limit the execution entities of the interaction diagrams. For example, the device (e.g., UE or network device) in the schematic flowcharts may also be a chip, chip system, or processor that supports the device to implement the method, or may be a logic module or software that can implement all or part of the functions of the device.

[0133] For a unified explanation here, in the interaction process of the embodiment of the present application, the message or signaling interaction involved can adopt the message or signaling in the standard, or it can be a newly introduced message or signaling, and the embodiment of the present application does not make specific limitations on this.

[0134] Figure 4 This is an example flow chart of a method for reporting beam reports in an embodiment of the present application. It can be understood that Figure 4 The UE in can be Figure 1 The UE in the UE can also refer to the device in the UE (such as a processor, chip, or chip system, etc.). The network equipment can be Figure 1 or Figure 2 The network device in the network device can also refer to the device in the network device (such as a processor, chip, or chip system, etc.). Figure 4 As shown, the method includes:

[0135] In step 401, the UE sends a first SR to the network device. In response, the network device receives the first SR, which is used to request a beam report.

[0136] The first SR includes one or more of the following: first indication information, priority information of beam report; the first indication information is used to indicate the request type of the first SR.

[0137] Optionally, the first SR includes at least first indication information. The first indication information is used to indicate the request type of the first SR. Exemplarily, by introducing a 1-bit indication information, different values ​​of this 1 bit represent different meanings. The first SR can be a traditional SR, i.e., an SR for requesting uplink channel resources, or an SR for requesting an uplink beam report, i.e., an extended SR (or enhanced SR) in this application.

[0138] For example, when the UE sends a beam report in mode B, the UE sends the first SR carrying the first indication information. Upon receiving the first SR, the network device identifies the request type of the first SR based on the first indication information included in the first SR, thereby accurately identifying the UE request and correctly processing the beam report. Furthermore, this can reduce the overhead of additional signaling.

[0139] Optionally, the first SR includes priority information for the beam report. This priority information may indicate the urgency of the beam report and may implicitly indicate whether the first SR is a traditional SR or an SR for requesting the upload of a beam report. For example, by extending the additional information in the SR, the SR payload can carry more UCI.

[0140] For example, when a UE sends a beam report using mode A, the UE sends the first SR carrying the priority information. Upon receiving the first SR, the network device identifies the urgency of the first SR based on the priority information included in the first SR, thereby accurately identifying the UE's needs and correctly processing the beam report. This also reduces the overhead of additional signaling.

[0141] For example, if the priority information of the beam report indicates non-priority, it means that the first SR is a traditional SR. In this case, the network device can process the first SR according to the traditional SR after receiving it. If the priority information of the beam report indicates the first priority, it means that the first SR is an enhanced SR, that is, an SR requesting the transmission of a beam report. In this case, the network device can know that the UE requests the transmission of a beam report. In the case where the first SR is an enhanced SR, if the UE uses mode B to transmit the beam report, the network device receives the beam report reported by the UE after several time domain resources. If the UE uses mode A to transmit the beam report, the network device sends DCI to the UE after receiving the first SR. The DCI is used to schedule uplink transmission resources so that the UE can use uplink transmission resources to report the beam report.

[0142] It should be understood that the above description of the content included in the first SR is merely exemplary and the embodiments of the present application are not limited thereto. In practice, the first SR may also include other information elements indicating whether a beam report transmission request is requested, or the first SR may include a greater or fewer number of information elements. For example, the first SR includes both the first indication information and beam report priority information.

[0143] It should be noted that step 410 may be step 1 in the aforementioned mode A or step 1 in mode B, and there is no specific limitation thereto. Exemplarily, the first SR is carried in the aforementioned first PUCCH.

[0144] Step 402: The UE reports a beam report. Correspondingly, the network device receives the beam report reported by the UE.

[0145] In some embodiments, after the UE sends the first SR, the transmission resources used to report the beam report can be pre-configured resources or configured by the network device, without specific limitation. That is, after sending the first SR, the UE may not require a reply or response from the network device, but instead report the beam report after a preset time domain resource, or report the beam report using pre-configured resources. Alternatively, after sending the first SR, the UE may receive the transmission resources sent by the network device and then use the transmission resources to send the beam report.

[0146] For example, after sending the first SR to the network device, the UE receives the DCI sent by the network device, where the DCI is used to indicate transmission resources; the UE uses the transmission resources indicated by the DCI to report a beam report. For another example, after sending the first SR, the UE reports a beam report after an interval of preset time domain resources. The embodiment of the present application does not specifically limit the mode adopted by the UE to report the beam report. Optionally, the UE adopts the first mode or the second mode to report the beam report.

[0147] It should be understood that the embodiments of the present application do not specifically limit the triggering conditions or events for reporting beam reports, and reference may be made to the descriptions in the relevant technologies. In other words, no matter what method is used to trigger reporting beam reports, the methods of the embodiments of the present application are applicable.

[0148] Optionally, the first mode refers to a mode in which the UE does not rely on the scheduling of the network device, but uses the uplink control information UCI in the pre-configured resources to report the beam report. For example, the first mode is mode B in the 3GPP standard. For a detailed description of mode B, please refer to the previous article. Figure 3B For the sake of brevity, the explanation is not repeated here.

[0149] Optionally, the second mode refers to a mode in which the UE reports a beam report based on resources dynamically scheduled by the network device. For example, the second mode is Mode A in the 3GPP standard. For a detailed description of Mode A, please refer to the previous article. Figure 3A For the sake of brevity, the explanation is not repeated here.

[0150] Exemplarily, step 420 may be step 3 in the aforementioned mode A, or may be step 2 in mode B. The beam report is carried in the aforementioned second UL channel.

[0151] In this embodiment of the present application, the UE sends a first scheduling request (SR) to the network device to request a beam report, and the first SR carries one or more of the following: first indication information and beam report priority information. This allows the network device to accurately understand the UE's need to send a beam report, thereby improving the reliability of beam report transmission. Compared to traditional SRs that are only used to request uplink scheduling resources, the first SR introduced in this embodiment of the present application supports requests for uplink beam reports, which helps to improve the flexibility and accuracy of beam management.

[0152] The embodiments of the present application provide solutions for reporting beam reports in the first mode or the second mode. Figure 5 and Figure 6 Describe them separately.

[0153] In a possible embodiment, when the UE reports the beam report in the first mode, the first SR includes at least the first indication information.

[0154] Taking the first mode as mode B, for ease of understanding, we introduce Figure 5 The following describes the method flow of the UE using mode B to transmit beam reports in an embodiment of the present application. Figure 5 As shown, it at least includes the following steps:

[0155] Step 501: A UE sends a first PUCCH to a network device. Correspondingly, the network device receives the first PUCCH. The first PUCCH includes a first SR, which includes first indication information.

[0156] For the description of the first SR, please refer to the previous text and will not be repeated here for the sake of brevity.

[0157] Optionally, the first indication information is used to indicate that the request type of the first SR is a first type, where the first type is an SR for requesting the transmission of a beam report. The first type is an extended SR type (or enhanced SR) in the embodiment of the present application. By extending the SR type, the extended SR type supports the UE's request to upload a beam report, which can more accurately reflect the UE's resource requirements.

[0158] It should be noted that the first indication information may adopt different coding schemes to express different meanings. Optionally, the first indication information occupies a certain number of bits, and the different values ​​of the certain number of bits are used to characterize the type of SR, and / or to characterize other requirements such as whether to request uplink shared channel resources. For example, the first indication information is coded with 1 bit, and different values ​​of the 1 bit represent different SR types. For another example, the first indication information is coded with 2 bits, and the different values ​​of the 2 bits can refer to more meanings than 1 bit. The coding scheme for the first indication information can be predefined by the protocol or configured by the network device to the UE, and there is no specific limitation on this. This will be explained later with reference to the examples in Table 1 and Table 2.

[0159] For unified explanation here, the specific implementation methods of "predefined" may include any of the following: predefined by the protocol, or specified by the manufacturer of the communication equipment, defined by the communication operator, pre-installed in the communication equipment when it leaves the factory, or agreed in advance by other agreed methods.

[0160] In step 502, the UE sends a second UL channel to the network device. In response, the network device receives the second UL channel, wherein the second UL channel includes a beam report.

[0161] For the execution order between step 501 and step 502, please refer to the previous text. Figure 3B For the sake of brevity, the description will not be elaborated here.

[0162] Optionally, before the UE sends the first SR (or before step 501), the method further includes: step 500, the network device sends RRC signaling to the UE. Correspondingly, the UE receives the RRC signaling. The RRC signaling includes the encoding scheme configuration of the first indication information.

[0163] Optionally, the encoding scheme configuration of the first indication information includes the number of bits occupied by the first indication information, and / or the meaning corresponding to the value of the bit.

[0164] Exemplarily, the RRC signaling includes a scheduling request beam report indicator (SR beam report indicator, SRBRI). By introducing the SRBRI, the traditional SR and the enhanced SR are distinguished. That is, the network device informs the UE of the related reporting information of the beam report indicator through the information element (Information Element, IE) of the SRBRI included in the RRC signaling.

[0165] That is, the network device can configure the encoding scheme of the first indication information for the UE in advance, so that the UE can subsequently send the first indication information using the encoding scheme, and flexibly determine the meaning represented by the first indication information based on its own needs, and then indicate the request type of the SR, such as being used for requesting uplink resources or being used for requesting to upload the beam report. After receiving the first SR sent by the UE, the network device can identify the request type of the first SR based on the first indication information in the first SR, and can distinguish whether the SR is the SR for requesting uplink resources or the SR for requesting to report the beam report, which helps to reduce the uncertainty of scheduling; thereby ensuring that the beam report triggered by the UE (such as the beam report triggered by using mode B; or the beam report triggered by using beam A) is correctly processed. That is, as long as the first indication information is carried in the first SR, the beam report triggered by the UE can be ensured to be correctly processed regardless of the mode used by the UE to report the beam report. At the same time, since no new signaling is introduced, the additional signaling overhead can be reduced.

[0166] The present embodiment does not limit the specific encoding scheme of the first indication information. Optionally, in an implementation manner, the first indication information is encoded by using a first number of bits, and the value of the first number of bits is used to indicate the type of the first SR.

[0167] The present embodiment does not limit the value of the first number. Exemplarily, the value of the first number is 1, that is, the type of the SR is indicated by using a 1-bit encoding scheme. By using the 1-bit encoding scheme to indicate the type of the SR, a large number of bits do not need to be occupied, and the purpose of indicating the type of the SR can be achieved, and the number of bits can be saved. The 1-bit encoding scheme is described by combining with the example in the following Table 1.

[0168] Table 1

[0169]

[0170] In the above Table 1, the SRBRI occupies 1 bit. When the SRBRI takes value 0, it represents that the SR is used to request uplink shared channel resource (such as PUSCH), i.e. the first SR is the traditional SR; when the SRBRI takes value 1, it represents that the SR is used to request sending beam report, i.e. the first SR is the extended SR. It should be understood that the meaning represented by each value in the example of Table 1 is only an exemplary description, and the embodiments of the present application are not limited thereto.

[0171] The above 1-bit encoding scheme can multiplex the first PUCCH channel resource (i.e. the first PUCCH channel in step 1 in the aforementioned mode B), so as to save channel overhead.

[0172] Therefore, after receiving the first SR sent by the UE, the network device can accurately identify the request type of the first SR based on the value of the SRBRI in the first SR, so as to respond to the UE based on the request type, such as ensuring that the beam report triggered by the UE through mode B is correctly processed.

[0173] The above first indication information realizes the indication of the SR request type through the 1-bit encoding scheme. In order to further enhance the flexibility of the first indication information, the present application also provides another encoding scheme. Optionally, the first indication information is also used to indicate whether the first SR requests uplink shared channel resource.

[0174] Optionally, the first indication information is encoded by a second number of bits, and different values of the second number of bits are respectively used to indicate whether the first SR is the SR for sending beam report, and / or whether the first SR requests uplink shared channel resource.

[0175] Exemplarily, the second number takes value 2. That is, the first indication information includes two bits, which respectively represent SR and SRBRI. There are 4 possibilities for the values of the two bits, which respectively represent different meanings, so that the UE can explicitly express whether to only send beam report or whether additional uplink shared channel resource is needed, which improves the flexibility of the first indication information. As shown in the following Table 2:

[0176] Table 2

[0177]

[0178] In Table 2 above, 01 is used as an example to indicate that the UE requests a beam report but does not request additional uplink shared channel resources. When the two-bit value is 11, it indicates that the UE requests not only a beam report but also additional uplink shared channel resources. This 2-bit value of 11 is applicable to scenarios where the UE sends multiple beam reports, which require more uplink shared channel resources to transmit. Of course, if the UE has sufficient resources to send beam reports using the aforementioned second UL channel, no additional uplink shared channel resources are required.

[0179] It should be understood that the meanings of the values ​​in Table 2 are merely illustrative and are not intended to limit the present application. In fact, the values ​​may have other possible meanings. It should also be understood that the encoding schemes shown above (such as Table 1 or Table 2) may be pre-configured by network devices or pre-defined by protocols, and this is not specifically limited.

[0180] Therefore, after receiving the first SR sent by the UE, the network device can accurately identify the request type of the first SR based on the value of the SRBRI in the first SR, and thus respond to the UE based on the request type. For example, it can ensure that the beam report triggered by the UE through Mode B is correctly processed. In addition, based on the encoding method of the second number, more information about the UE behavior can be obtained, which helps to more accurately identify the UE's needs and make appropriate responses.

[0181] For example, the various implementations described in the above possible embodiments can be understood as adopting the first mode (such as the aforementioned Figure 3B Mode B) shows an improved solution for reporting beam reports.

[0182] In the above possible embodiments, by introducing the first indication information in the first SR, the conflict problem of the traditional SR function mentioned above is solved, so that the network device can clearly know the scheduling request SR sent by the UE, thereby improving the transmission reliability of the beam report.

[0183] In another possible embodiment, when the UE adopts the second mode to report the beam report, the first SR includes at least priority information of the beam report.

[0184] Taking the second mode as mode A, for ease of understanding, we introduce Figure 6 The following describes the method flow of the UE using mode A to transmit beam reports in an embodiment of the present application. Figure 6 As shown, it at least includes the following steps:

[0185] Step 601: The UE sends a first PUCCH to a network device. In response, the network device receives the first PUCCH. The first PUCCH includes a first SR, which includes priority information of a beam report.

[0186] For the description of the first SR, please refer to the previous text and will not be repeated here for the sake of brevity.

[0187] The beam report priority information is used to indicate the priority of the beam report, or the urgency of the triggering event. For example, if multiple UEs simultaneously request beam reports, and different beam reports have different priorities, the network device will prioritize allocating transmission resources to UEs requesting high-priority beam reports, thereby ensuring smooth transmission of these high-priority reports.

[0188] Mode A relies on the network device to configure resources for the UE to transmit a beam report. Optionally, when the UE uses the second mode to report a beam report, the method further includes: Step 602: the network device transmits downlink control information (DCI) to the UE. In response, the UE receives the DCI. The DCI is used to schedule uplink transmission resources based on the priority information (the uplink transmission resources are used by the UE to transmit the beam report).

[0189] Step 603: The UE reports the beam report on the uplink transmission resource based on the DCI scheduling.

[0190] That is to say, when the UE uses mode A to report the beam report, the UE carries the priority information of the beam report through the SR, so that the network device can process the UE's request based on the priority information, thereby meeting the UE's business needs.

[0191] The embodiment of the present application does not specifically limit the encoding scheme for the priority information of the beam report. Optionally, the priority information of the beam report is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

[0192] Table 3

[0193]

[0194] Table 3 above uses a 2-bit encoding scheme, with different values ​​representing different priorities. For example, a priority value of 00 represents non-priority, or traditional SR; another example is a priority value of 01, which represents low priority. Low, medium, and high priorities can represent priorities of varying urgency. Of course, different priorities can also be determined based on beam quality. For example, the lower the beam quality, the higher the priority of the beam report.

[0195] It should be understood that the encoding scheme in Table 3 is merely an example, and the present invention is not limited thereto. In fact, a greater or lesser number of bits may be used to represent the priority of the beam report, as shown in Table 4 below:

[0196] Table 4

[0197]

[0198] In Table 4 above, one bit can be used to represent priority information, further saving bits and simplifying implementation. The coding scheme in Table 4 is applicable when the UE reports a small number of beam reports (e.g., a single beam report). If the UE needs to report multiple beam reports, the coding scheme in Table 3 above or a coding scheme that uses more bits to indicate priority information can be used to ensure that the highest-priority beam report is transmitted first.

[0199] In order to further dynamically guide the network device to dynamically configure appropriate resources for the UE, the embodiment of the present application also proposes to introduce resource indication information in the SR. Optionally, the first SR also includes resource indication information, which is used to indicate whether uplink shared channel resources, such as PUSCH resources, are required.

[0200] The embodiment of the present application does not specifically limit the coding scheme of the resource indication information. Optionally, the resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are used to indicate whether uplink shared channel resources are required.

[0201] The embodiment of the present application does not specifically limit the value of the fourth number. Exemplarily, the value of the fourth number is 1, that is, a bit is used to indicate whether additional uplink shared channel resources are required. This is described in conjunction with the example in Table 5 below.

[0202] Table 5

[0203]

[0204] In Table 5 above, resource indication information occupies one bit. When the resource indication information value is 0, it indicates that the UE does not require additional uplink shared channel resources; when the resource indication information value is 1, it indicates that the UE requires additional uplink shared channel resources. It should be understood that the meanings of the various values ​​​​in Table 5 are merely illustrative descriptions and the embodiments of the present application are not limited thereto. By introducing one bit of resource indication information, excessive overhead is not occupied, which helps to save channel overhead.

[0205] Therefore, after receiving the first SR sent by the UE, the network device can accurately know whether the UE needs uplink shared channel resources based on the value of the resource indication information in the first SR, and thus respond to the UE based on the request type, for example, dynamically configuring resources for the UE, ensuring accurate scheduling of the network device, and helping to improve the transmission reliability of the beam report.

[0206] It should be noted that if the UE indicates more information, such as the specific amount of resource requirements, additional bits can be added for indication, which is more flexible.

[0207] It should also be noted that the encoding schemes shown above (such as one or more items in Table 3, Table 4 and Table 5) can be pre-configured by the network device or pre-defined by the protocol, and there is no specific limitation on this.

[0208] In the second mode, taking Table 3 and Table 4 above as an example, when the first SR includes both the priority information and the resource indication information, it can be understood as an extension of the load information of the traditional SR. For example, 3 bits of information are added to inform the network device of the priority and resource requirements of the beam report, thereby helping to avoid competitive scheduling delays and improve scheduling accuracy and resource utilization. The embodiment of the present application does not specifically limit the location of the added 3 bits of information. For example, by adding 3 bits of additional information to the load field in the original SR; or by extending the PUCCHSR load, 3 bits of information are appended to the original PUCCH SR, wherein the SR is transmitted via PUCCH, and the aforementioned PUCCHSR can be understood as the PUCCH used to transmit the SR.

[0209] Of course, the above description uses the example of the first SR including both the priority information and the resource indication information. The embodiments of the present application are not limited to this. For example, the first SR may include priority information but not resource indication information. Another example is the first SR including resource indication information but not priority information.

[0210] In the above embodiment, by introducing priority information and / or resource indication information in the first SR, the problem mentioned above that the traditional SR mechanism cannot effectively guide network devices to dynamically configure resources is solved, so that network devices can dynamically configure resources based on the urgency and / or resource requirements of beam reports, which helps to improve the reliability of transmission beam reports.

[0211] It should be understood that the foregoing is described separately in terms of the first mode and the second mode. In fact, the embodiments of the present application are not limited to this. In some cases, the first mode and the second mode may not be distinguished, that is, the various implementation methods shown above can be implemented in combination. Or, in some cases, the various implementation methods mentioned above can be applicable in either the first mode or the second mode, that is, there is no restriction on which implementation method must be implemented in a certain mode. For example, the first SR includes the first indication information and the priority information of the beam report. For another example, the first SR also includes the first indication information, the priority information of the beam report, and the resource indication information. For the implementation methods of each information, please refer to the previous description.

[0212] For unified explanation here, each coding scheme shown in the embodiment of the present application is illustrative description, and the embodiment of the present application is not limited to this. For example, the meaning represented by the value of the bit involved in the above coding scheme may be different from the meaning shown in the above table. For another example, the above coding scheme can be equivalently replaced with other coding schemes.

[0213] It should be understood that Figures 1 to 6 The flowcharts or scenario diagrams shown are only for ease of understanding and are not intended to limit the embodiments of the present application to the examples shown in the diagrams. In fact, those skilled in the art will Figures 1 to 6 The examples in can be equivalently transformed to obtain more implementation methods.

[0214] The embodiments of the present application do not specifically limit the communication scenarios of application, and are applicable to any communication scenarios or communication equipment involving reporting beam reports.

[0215] In some application scenarios, the embodiments of the present application can be applied to vehicle-to-vehicle communication scenarios. Optionally, the UE is a vehicle-to-everything (V2X) device. The V2X device uses the beam reporting method of the embodiments of the present application to reduce signaling overhead by introducing a small amount of indication information (e.g., 1 or 2 bits) to indicate the request type of the first SR. Furthermore, based on the first indication information in the first SR reported by the V2X device, the network device can accurately identify the V2X device's requirements, thereby improving transmission reliability. Furthermore, in inter-device communication scenarios (e.g., between one V2X device and another), this helps improve the reliability of inter-vehicle collaborative communication.

[0216] In other application scenarios, the present invention can be applied to the Industrial Internet of Things (IIOT) or high-reliability, low-latency industrial automation communication scenarios. Optionally, the UE is an IIOT device; the IIOT device uses the beam reporting method of the present invention to ensure the transmission priority of critical signals by introducing beam report priority information.

[0217] In some other application scenarios, the embodiments of the present application can be applied to smart manufacturing scenarios, so that machine equipment or networks can accurately understand the needs of the equipment, which helps to optimize the communication scheduling between machine equipment in the communication network (such as the 5G network), thereby improving production efficiency.

[0218] Combined with the above Figures 1 to 6 , describes in detail the method for reporting beam reports provided by the embodiment of the present application. Figure 7 and Figure 8 The device embodiments of the present application are described in detail. It should be understood that the communication device of the embodiment of the present application can execute the various methods of reporting beam reports in the aforementioned embodiments of the present application, that is, the specific working processes of the following various products can refer to the corresponding processes in the aforementioned method embodiments.

[0219] In each of the above embodiments, the UE may perform some or all of the steps in each embodiment; the network device may perform some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the various steps may be performed in a different order as presented in the embodiments, and it may not be necessary to perform all of the operations in the embodiments of the present application. Moreover, the size of the sequence number of each step does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0220] Figure 7 : is a schematic block diagram of a communication device provided in an embodiment of the present application. Figure 7 As shown, the communication device 1300 may include a communication module 1320. The communication module 1320 may implement corresponding communication functions, which may be internal communication functions within the communication device 1300 or communication functions between the communication device 1300 and other devices. Optionally, the communication module 1320 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 1300 also includes a processing module 1310. The processing module 1310 may implement corresponding processing functions.

[0221] Optionally, the communication device 1300 further includes a storage module, which can be used to store instructions and / or data; the processing module 1310 can read the instructions and / or data in the storage module to enable the communication device 1300 to implement the aforementioned method embodiment.

[0222] In one possible design, the communication device 1300 may correspond to the UE in the above method embodiments, or a component configured in the UE (such as a circuit, chip, or chip system). The communication device 1300 can be used to execute the steps or processes executed by the UE in any of the above method embodiments.

[0223] In a possible design of the present disclosure, the communication module 1320 is configured to send a first scheduling request (SR), where the first SR is used to request reporting of a beam report; and the first SR includes one or more of the following: first indication information, priority information of the beam report; and the first indication information is used to indicate a request type of the first SR.

[0224] The communication module 1320 is further configured to report the beam report.

[0225] Optionally, as an embodiment, in the case where the UE reports the beam report in a first mode, the first SR at least includes the first indication information; and the first indication information is used to indicate that the request type of the first SR is a first type, and the first type is an SR used to request sending of a beam report.

[0226] Optionally, as an embodiment, the first indication information is encoded by using a first number of bits, and a value of the first number of bits is used to indicate the type of the first SR.

[0227] Optionally, as an embodiment, the first indication information is further used to indicate whether the first SR requests an uplink shared channel resource.

[0228] Optionally, as an embodiment, the first indication information is encoded by using a second number of bits, and different values of the second number of bits are respectively used to indicate whether the first SR is an SR used to send a beam report, and / or whether the first SR requests an uplink shared channel resource.

[0229] Optionally, as an embodiment, the communication module 1320 is further configured to receive RRC signaling from a network device, and the RRC signaling includes a configuration of an encoding scheme of the first indication information.

[0230] Optionally, as an embodiment, in the case where the UE reports the beam report in a second mode, the first SR at least includes the priority information of the beam report.

[0231] The communication module 1320 is further configured to receive downlink control information (DCI) from a network device, and the DCI is used to schedule an uplink transmission resource used to transmit a beam report based on the priority information.

[0232] The processing module 1310 is configured to invoke the communication module 1320 to report the beam report on the uplink transmission resource based on the scheduling of the DCI.

[0233] Optionally, as an embodiment, the priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

[0234] Optionally, as an embodiment, the first SR further includes resource indication information, where the resource indication information is used to indicate whether uplink shared channel resources are required.

[0235] Optionally, as an embodiment, the resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are used to indicate whether uplink shared channel resources are required.

[0236] It should be understood that the communication device 1300 may correspond to the embodiment of the present application. Figures 1 to 6 UE in; the communication device 1300 may include a Figures 1 to 6 Furthermore, the modules and other operations and / or functions in the communication device 1300 are respectively for implementing Figures 1 to 6 The corresponding process.

[0237] It should also be understood that when the communication device 1300 is a UE, the processing module 1310 in the communication device 1300 may be implemented by at least one processor, for example, corresponding to Figure 8 For example, the communication module 1320 may correspond to the processor 1410 in the communication device 1400 shown in FIG. Figure 8 The communication interface 1420 in the communication device 1400 is shown in FIG.

[0238] It should also be understood that when the communication device 1300 is a chip or chip system configured in the above-mentioned UE, the processing module 1310 of the communication device 1300 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0239] Alternatively, in one possible design, the communication device 1300 may correspond to the network device in the above method embodiments, or a component configured in the network device (such as a circuit, chip, or chip system). The communication device 1300 can be used to execute the steps or processes executed by the network device in any of the above method embodiments.

[0240] In one possible design, the communication module 1320 is configured to receive a first scheduling request SR, where the first SR is used to request reporting of a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; the first indication information is used to indicate a request type of the first SR;

[0241] The communication module 1320 is further configured to receive the beam report.

[0242] Optionally, as an embodiment, when the UE reports the beam report in the first mode, the first SR includes at least: the first indication information;

[0243] The first indication information is used to indicate that the request type of the first SR is a first type, and the first type is an SR used to request a reception beam report.

[0244] Optionally, as an embodiment, the first indication information is encoded using a first number of bits, and the value of the first number of bits is used to indicate the type of the first SR.

[0245] Optionally, as an embodiment, the first indication information is further used to indicate whether the first SR requests uplink shared channel resources.

[0246] Optionally, as an embodiment, the first indication information is encoded using a second number of bits, and different values ​​of the second number of bits are used to indicate whether the first SR is an SR reported by a receiving beam, and / or whether the first SR requests uplink shared channel resources.

[0247] Optionally, as an embodiment, the communication module 1320 is further used to send RRC signaling to the UE, where the RRC signaling includes the coding scheme configuration of the first indication information.

[0248] Optionally, as an embodiment, when the UE reports the beam report in the second mode, the first SR includes at least priority information of the beam report;

[0249] The communication module 1320 is further configured to send downlink control information DCI, where the DCI is used to schedule uplink transmission resources for transmitting beam reports based on the priority information;

[0250] The processing module 1310 is used to call the communication module 1320 to receive the beam report in the uplink transmission resource.

[0251] Optionally, as an embodiment, the priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

[0252] Optionally, as an embodiment, the first SR further includes resource indication information, where the resource indication information is used to indicate whether uplink shared channel resources are required.

[0253] Optionally, as an embodiment, the resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are used to indicate whether uplink shared channel resources are required.

[0254] It should be understood that the communication device 1300 may correspond to the embodiment of the present application. Figures 1 to 6 The communication device 1300 may include a network device for performing Figures 1 to 6 Furthermore, each module in the communication device 1300 and the above-mentioned other operations and / or functions are respectively for implementing Figures 1 to 6 The corresponding process.

[0255] It should also be understood that when the communication device 1300 is a network device, the processing module 1310 in the communication device 1300 can be implemented by at least one processor, for example, corresponding to Figure 8 For example, the communication module 1320 may correspond to the processor 1410 in the communication device 1400 shown in FIG. Figure 8 The communication interface 1420 in the communication device 1400 is shown in FIG.

[0256] It should also be understood that when the communication device 1300 is a chip or chip system configured in the above-mentioned network device, the processing module 1310 of the communication device 1300 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0257] Figure 8 This is another schematic block diagram of a communication device 1400 provided in an embodiment of the present application. The communication device 1400 may be a UE or a network device; it may also be a chip, a chip system, or a processor that supports the UE or network device in implementing the above-mentioned method. The communication device 1400 may be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0258] like Figure 8 As shown, the communication device 1400 may include one or more processors 1410, which may also be referred to as a processing unit or processing module, and may implement certain control functions. The processor 1410 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device 1400 (e.g., base station, baseband chip, user, user chip), execute software programs, and process software program data.

[0259] In an optional design, the processor 1410 may also store instructions and / or data, which can be executed by the processor 1410 to enable the communication device 1400 to perform the method described in the above method embodiment.

[0260] In another optional design, the communication device 1400 may include a communication interface 1420 for implementing receiving and transmitting functions. For example, the communication interface 1420 may be a transceiver circuit, an interface, an interface circuit, or a transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or the transceiver circuit, interface, interface circuit, or transceiver may be used for transmitting or delivering signals.

[0261] Optionally, the communication device 1400 may include one or more memories 1430, which may store instructions. These instructions may be executed on the processor 1410, causing the communication device 1400 to perform the method described in the above method embodiment. Optionally, the memory 1430 may also store data. Optionally, the processor 1410 may also store instructions and / or data. The processor 1410 and memory 1430 may be provided separately or integrated together.

[0262] It should be understood that, in one possible design, each step in the method embodiment provided in the present application can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0263] Optionally, if the communication device 1400 includes a processor 1410 , a communication interface 1420 , and a memory 1430 , the processor 1410 , the communication interface 1420 , and the memory 1430 communicate with each other through an internal connection path.

[0264] Optionally, the memory 1430 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. The memory 1430 may be a separate device or integrated into the processor 1410.

[0265] In one implementation, the communication device 1400 may correspond to the UE in the above-mentioned method embodiment, and may be used to execute the various steps and / or processes performed by the UE in the above-mentioned method embodiment. The processor 1410 may be used to execute instructions stored in the memory 1430, and when the processor 1410 executes the instructions stored in the memory, the processor 1410 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the UE.

[0266] In another implementation, the communication device 1400 may correspond to the network device in the above-mentioned method embodiment, and may be used to execute the various steps and / or processes performed by the network device in the above-mentioned method embodiment. The processor 1410 may be used to execute instructions stored in the memory 1430, and when the processor 1410 executes the instructions stored in the memory, the processor 1410 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the network device.

[0267] Optionally, the communication interface 1420 is a transceiver, which may include a transmitter and a receiver. The transceiver may further include an antenna, which may be one or more. The processor 1410, memory 1430, and communication interface 1420 may be integrated on different chips. For example, the processor 1410 and memory 1430 may be integrated in a baseband chip, and the communication interface 1420 may be integrated in a radio frequency chip. The processor 1410, memory 1430, and communication interface 1420 may also be integrated on the same chip. This application is not limited to this.

[0268] An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is used to execute the method for reporting beam reports in any of the above method embodiments.

[0269] It should be understood that the processing device may be one or more chips. For example, the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0270] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0271] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-described method embodiments can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-described processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-described method.

[0272] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0273] According to the method provided in the embodiments of the present application, the present application further provides a chip system, which comprises one or more processors, and is configured to call and run instructions stored in a memory, so that the method provided in the embodiments of the present application is executed. The chip system can be composed of a chip, or can comprise a chip and other discrete devices.

[0274] In some embodiments, the chip system can comprise an input circuit or interface configured to send information or data, and an output circuit or interface configured to receive information or data.

[0275] According to the method provided in the embodiments of the present application, the present application further provides a communication system, which comprises the UE and the network device.

[0276] Optionally, the communication system further comprises other devices in communication with the UE. Optionally, the communication system further comprises other devices in communication with the network device.

[0277] According to the method provided in the embodiments of the present application, the present application further provides a computer program product, which comprises computer program codes, and when the computer program codes are run on a computer, the computer is caused to execute each step or process performed by the UE or the network device in any of the method embodiments.

[0278] According to the method provided in the embodiments of the present application, the present application further provides a computer readable storage medium, which stores program codes, and when the program codes are run on a computer, the computer is caused to execute each step or process performed by the UE or the network device in any of the method embodiments.

[0279] The computer-readable storage medium may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM).

[0280] The above-mentioned device embodiments and method embodiments are completely corresponding, and the corresponding steps are performed by the corresponding modules or units. For example, the communication unit or communication interface performs the receiving or sending steps in the method embodiment. Other steps except sending and receiving can be performed by the processing unit or processor.

[0281] In the embodiments of this application, each term and English abbreviation is provided for convenience of description and shall not constitute any limitation to this application. This application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0282] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0283] It should be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0284] Additionally, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the related objects. For example, "A / B" can mean either A or B.

[0285] The terms (or numbers) "first," "second," ..., etc. that appear in the embodiments of this application are used for descriptive purposes only, that is, they are only used to distinguish different objects and should not be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, features defined as "first," "second," ..., etc. may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "at least one (item)" means one or more. "Multiple" means two or more. "At least one of the following (items)" or similar expressions refers to any combination of these items, including any combination of a single (item) or plural (items).

[0286] For example, the meaning of the expression similar to "the item includes at least one of A, B, and C" in the embodiments of the present application, if not specifically stated, generally means that the item can be any one of A, B, C, A and B, A and C, B and C, A, B and C, A and A, A, A and A, A, A and B, A, A and C, A, B and B, A, C and C, B and B, B, B and B, B, B and C, C and C, C, C and C, and other combinations of A, B, and C. The above is an example of 3 elements A, B, and C to illustrate the optional entries of the item. When the expression is "the item includes at least one of A, B,..., and X", that is, the expression has more elements, the applicable entries of the item can also be obtained according to the foregoing rules.

[0287] In conclusion, the above only describes the preferred embodiments of the technical solutions of the present application, and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for reporting a beam report, characterized in that: Applied to user equipment UE, the method includes: Sending a first scheduling request SR, where the first SR is used to request reporting of a beam report; the first SR includes one or more of the following: first indication information, and priority information of the beam report; wherein the first indication information is used to indicate a request type of the first SR; reporting the beam report; In the case where the UE adopts the first mode to report the beam report, the first SR includes at least: the first indication information; the first indication information is used to indicate that the request type of the first SR is the first type, and the first type is the SR used to request to send a beam report; the first indication information is encoded using a first number of bits, and the value of the first number of bits is used to indicate the type of the first SR.

2. The method according to claim 1, characterized in that The first indication information is further used to indicate whether the first SR requests uplink shared channel resources.

3. The method according to claim 2, characterized in that The first indication information is encoded using a second number of bits, and different values ​​of the second number of bits are used to indicate whether the first SR is an SR for sending a beam report, and / or whether the first SR requests uplink shared channel resources.

4. The method according to any one of claims 1 to 3, characterized in that Before sending the first SR, the method further includes: Receive radio resource control RRC signaling from a network device, where the RRC signaling includes a coding scheme configuration of the first indication information.

5. The method according to claim 1, wherein In a case where the UE reports the beam report in the second mode, the first SR includes at least priority information of the beam report; The method further comprises: receiving downlink control information (DCI) from a network device, where the DCI is used to schedule uplink transmission resources for transmitting a beam report based on the priority information; The reporting of the beam report includes: reporting the beam report on the uplink transmission resource based on the scheduling of the DCI.

6. The method according to claim 5, characterized in that The priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

7. The method according to claim 5 or 6, characterized in that The first SR further includes resource indication information, where the resource indication information is used to indicate whether uplink shared channel resources are required.

8. The method according to claim 7, characterized in that The resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are respectively used to indicate whether uplink shared channel resources are required.

9. A method for reporting a beam report, characterized in that: Applied to a network device, the method includes: receiving a first scheduling request SR, where the first SR is used to request reporting of a beam report; the first SR includes one or more of the following: first indication information, priority information of the beam report; and the first indication information is used to indicate a request type of the first SR; receiving the beam report; When the UE adopts the first mode to report the beam report, the first SR includes at least: the first indication information; the first indication information is used to indicate that the request type of the first SR is the first type, and the first type is the SR for requesting to receive the beam report; the first indication information is encoded using a first number of bits, and the value of the first number of bits is used to indicate the type of the first SR.

10. The method according to claim 9, characterized in that The first indication information is further used to indicate whether the first SR requests uplink shared channel resources.

11. The method according to claim 10, characterized in that The first indication information is encoded using a second number of bits, and different values ​​of the second number of bits are used to indicate whether the first SR is an SR reported by a received beam, and / or whether the first SR requests uplink shared channel resources.

12. The method according to any one of claims 9 to 11, characterized in that Before receiving the first SR, the method further includes: Sending radio resource control RRC signaling to the UE, where the RRC signaling includes a coding scheme configuration of the first indication information.

13. The method according to claim 9, characterized in that When the UE reports the beam report in the second mode, the first SR includes at least priority information of the beam report; The method further comprises: Sending downlink control information (DCI), where the DCI is used to schedule uplink transmission resources for transmitting the beam report based on the priority information; The receiving the beam report includes: receiving the beam report in the uplink transmission resource.

14. The method according to claim 13, characterized in that The priority information is encoded using a third number of bits, and different values ​​of the third number of bits are used to indicate different reporting priorities of the beam report.

15. The method according to claim 13 or 14, characterized in that The first SR further includes resource indication information, where the resource indication information is used to indicate whether uplink shared channel resources are required.

16. The method according to claim 15, characterized in that The resource indication information is encoded using a fourth number of bits, and different values ​​of the fourth number of bits are respectively used to indicate whether uplink shared channel resources are required.

17. A communication system, characterized in that: Including user equipment UE and network equipment; The UE is configured to perform the method according to any one of claims 1 to 8; The network device is configured to execute the method according to any one of claims 9 to 16.

18. A communication device, characterized in that: The device comprises at least one processor, the at least one processor being coupled to a memory, the memory being used to store programs or instructions, the processor executing the programs or instructions so that the device is used to perform the method according to any one of claims 1 to 8, or the device is used to perform the method according to any one of claims 9 to 16.

19. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the computer is caused to execute the method according to any one of claims 1 to 8, or the computer is caused to execute the method according to any one of claims 9 to 16.

20. A chip system, characterized in that: The chip system includes one or more processors, which are used to call and execute instructions stored in the memory from the memory, so that the method as described in any one of claims 1 to 8 is executed; or, so that the method as described in any one of claims 9 to 16 is executed.

Images