Measurement report transmission method and device

Abstract

Provided are a measurement report transmission method and apparatus, which relate to the field of communications, and which enable a terminal device to monitor a PDCCH, so that the terminal device can determine whether a network device successfully receives a measurement report, contributing to normal proceeding of a measurement report reporting process, and contributing to maintaining the stability of a communication system. The method comprises: in a discontinuous reception (DRX) mode, sending a first report, the first report being used for indicating a measurement result of one or more beams, the first report being carried in a UCI; and after the first report is sent, monitoring the PDCCH within a first duration.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a measurement report transmission method and apparatus in the field of communications. Background Technology

[0002] Mobility measurement and reporting are fundamental to beam management. In communication systems, terminal devices can perform beam-level measurements based on measurement configurations issued by network devices, and can report beam-level measurement reports to network devices via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). Beam-level measurement reports include measurement results of the signal quality of one or more beams.

[0003] However, when the terminal device is in discontinuous reception (DRX) mode, it may affect the normal progress of the measurement report reporting process, thereby affecting the stability of the communication system. Summary of the Invention

[0004] This application provides a measurement report transmission method and apparatus, which enables terminal devices to listen to the PDCCH after reporting beam measurement reports, thereby receiving responses from network devices, thus facilitating the normal progress of the measurement report reporting process and helping to maintain the stability of the communication system.

[0005] In a first aspect, a measurement report transmission method is provided, the method comprising: in discontinuous reception DRX mode, transmitting a first report, the first report being used to indicate the measurement results of one or more beams, the first report being carried in uplink control information (UCI); and after transmitting the first report, listening to the PDCCH for a first duration.

[0006] In one possible implementation, the method is performed by a first communication device. The first communication device may be a terminal device or a chip or circuit that can be applied to the terminal device.

[0007] The measurement report transmission method of this application allows a terminal device in DRX mode to start timing after sending a UCI carrying a beam measurement report to the network device. The timing duration is a first time period, during which the terminal device listens to the PDCCH. This allows the terminal device to receive a response from the network device while listening to the PDCCH. This response can indicate whether the network device has successfully received the beam measurement report, enabling the terminal device to determine whether to resubmit the beam measurement report based on the network device's response. This facilitates the normal operation of the measurement report reporting process and helps maintain the stability of the communication system.

[0008] In conjunction with the first aspect, in some embodiments of the first aspect, listening to the PDCCH during a first duration includes: starting a first timer and listening to the PDCCH during the operation of the first timer, wherein the duration of the first timer is the first duration.

[0009] The first timer, also known as the first timer, drx-RetransmissionTimerUL, or Active-TimerUL, is used to time the active period, which is the time period during which the terminal device listens to the PDCCH. The first timer can be drx-RetransmissionTimerUL, or it can be a new predefined timer.

[0010] In conjunction with the first aspect, in some embodiments of the first aspect, the starting position of the first duration is the first time unit after the first report is sent; or, the time interval between the starting position of the first duration and the sending of the first report is the second duration.

[0011] The first time unit can be, for example, the first symbol.

[0012] Thus, when the starting position of the first duration is the first time unit after sending the first report, the terminal device starts timing the first duration earlier, making it less likely to miss responses from network devices. When the time interval between the starting position of the first duration and sending the first report is the second duration, the terminal device starts timing the first duration later. The second duration can be, for example, a reserved time period for network devices to receive and process the UCI reported by the terminal device. During this time period, the terminal device does not need to listen to the PDCCH, which reduces the power consumption of the terminal device.

[0013] In conjunction with the first aspect, in some embodiments of the first aspect, listening to the PDCCH includes: after sending a first report, starting a second timer, and listening to the PDCCH for a first duration after the second timer expires, wherein the duration of the second timer is a second duration.

[0014] The second timer can also be called a second timer, drx-HARQ-RTT-TimerUL, or RTT-TimerUL, etc. The second timer can be used to determine the start position of the first duration. The second timer can be drx-HARQ-RTT-TimerUL, or it can be a new predefined timer.

[0015] Furthermore, when timing the first duration using the first timer, listening to the PDCCH during the first duration after the second timer expires can also be replaced by: starting the first timer when the second timer expires, and listening to the PDCCH during the operation of the first timer.

[0016] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: within a first duration, receiving first information or second information, the first information indicating that a first report was not successfully received, and the second information indicating that a measurement report is sent; based on the first information or the second information, sending a second report, the second report indicating the measurement results of one or more beams, the second report being carried in the UCI.

[0017] The first piece of information could be, for example, a NACK message, and the second piece of information could be, for example, a DCI message. The second report may be the same as or different from the first report.

[0018] It is understandable that during the first time period, the terminal device listens to the PDCCH. Since the network device can send responses to the terminal device via the PDCCH, such as first information or second information, the terminal device can listen to the first information or second information from the network device during the first time period.

[0019] In this way, if the terminal device determines that the network device has not successfully received the first report, the terminal device can report the beam measurement report again, which increases the probability that the network device will successfully receive the beam measurement report from the terminal device. This helps the measurement report reporting process to proceed normally and helps maintain the stability of the communication system.

[0020] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: stopping monitoring the PDCCH based on the first information or the second information.

[0021] Stopping PDCCH listening can also be understood as turning off the first timer. Turning off the first timer can also be replaced with stopping or ending the first timer.

[0022] In this way, since the terminal device has determined that the network device has not successfully received the first report, the terminal device can stop listening to the PDCCH. This also allows the terminal device to consume less power.

[0023] In conjunction with the first aspect, in some embodiments of the first aspect, the time-frequency domain resources for sending the first report and the time-frequency domain resources for sending the second report are pre-configured or indicated by signaling.

[0024] The pre-configuration can indicate that the first and second reports are reported by the terminal device according to mode B, while the signaling indication can indicate that the first and second reports are reported by the terminal device according to mode A.

[0025] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: during a first duration, if no response to the first report is detected; after the first duration expires, sending a second report indicating the measurement results of one or more beams, the second report being carried in the UCI.

[0026] In this way, if the terminal device is unsure whether the network device has successfully received the first report, the terminal device can report the beam measurement report again, which increases the probability that the network device will successfully receive the beam measurement report from the terminal device. This helps the measurement report reporting process to proceed normally and helps maintain the stability of the communication system.

[0027] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: receiving third information within a first duration, the third information indicating successful reception of the first report; and stopping monitoring the PDCCH based on the third information.

[0028] The third piece of information could be, for example, an ACK message. Stopping PDCCH monitoring could be achieved by, for example, disabling the first timer.

[0029] It is understandable that during the first time period, the terminal device listens to the PDCCH. When the network device successfully receives the first report, it can send the third information to the terminal device through the PDCCH. Therefore, during the first time period, the terminal device can listen to the third information.

[0030] In this way, once the network device successfully receives the first report, the terminal device can stop listening to the PDCCH, ensuring that the measurement report reporting process is proceeding normally while minimizing the power consumption of the terminal device.

[0031] In conjunction with the first aspect, in some embodiments of the first aspect, the first duration is pre-configured or indicated by signaling.

[0032] Pre-configuration could be, for example, pre-configured by the network device via RRC signaling before the current measurement report reporting process is triggered. Signaling indication could, for example, be indicated by the network device via DCI after the current measurement report reporting process is triggered.

[0033] Secondly, another measurement report transmission method is provided, the method comprising: sending fourth information, the fourth information being used to indicate a first duration; receiving a first report from a first communication device, the first report being used to indicate measurement results of one or more beams, the first report being carried in uplink control information (UCI), wherein the first duration is initiated based on the transmission of the UCI and is used to listen to the physical downlink control channel (PDCCH) corresponding to the first report.

[0034] The fourth piece of information can be, for example, information 1 and / or information 2 as described below.

[0035] It should be noted that the initiation of the first duration based on the transmission of the UCI does not limit the first duration to start immediately after the transmission of the UCI. The start position of the first duration can also be spaced apart from the end position (time domain end position) of the UCI transmission. The PDCCH corresponding to the first report can be understood as the PDCCH used by the network device receiving the first report to send a response to the terminal device.

[0036] In one possible implementation, the method is performed by a second communication device. The second communication device may be a network device or a chip or circuit that can be applied to a network device.

[0037] Thirdly, a communication device is provided for performing the method in any possible implementation of the first or second aspect described above. Specifically, the communication device includes a module for performing the method in any possible implementation of the first or second aspect described above.

[0038] Fourthly, this application provides another communication device, including a processor coupled to a memory, which can be used to execute instructions in the memory to implement the method in any of the possible implementations of the first or second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, to which the processor is coupled.

[0039] In one implementation, the communication device is a terminal device or a network device. When the communication device is a terminal device or a network device, the communication interface can be a transceiver, or an input / output interface.

[0040] In another implementation, the communication device is a chip applicable to terminal devices or network devices. When the communication device is a chip applicable to terminal devices or network devices, the aforementioned communication interface can be an input / output interface.

[0041] Fifthly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any possible implementation of the first or second aspect described above.

[0042] In the specific implementation process, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0043] In a sixth aspect, a communication device is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of the first or second aspect described above.

[0044] Optionally, the processor may be one or more, and the memory may be one or more.

[0045] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0046] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. This application does not limit the type of memory or the way the memory and processor are set.

[0047] It should be understood that the relevant data interaction process, such as sending instruction information, can be a process of outputting instruction information from the processor, and receiving capability information can be a process of the processor receiving input capability information. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as transceivers.

[0048] The communication device in the sixth aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0049] In a seventh aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the method in any possible implementation of the first or second aspect described above.

[0050] Eighthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any possible implementation of the first or second aspect described above. Attached Figure Description

[0051] Figure 1 A schematic block diagram of the RAN architecture provided in the embodiments of this application;

[0052] Figure 2 This is a schematic diagram of a terminal device listening to the PDCCH in DRX mode;

[0053] Figure 3 This is a schematic diagram of a communication system to which the embodiments of this application apply;

[0054] Figure 4 This is a schematic diagram of a network device and a terminal device communicating via beams.

[0055] Figure 5 A schematic diagram illustrating the process of a terminal device reporting a beam measurement report via Mode A;

[0056] Figure 6 A schematic diagram illustrating the process of a terminal device reporting a beam measurement report via Mode B.

[0057] Figure 7 A comparative diagram showing the process of terminal devices reporting beam measurement reports via mode A and mode B;

[0058] Figure 8 This is a schematic diagram illustrating the process of sending uplink data in DRX mode.

[0059] Figure 9 This application provides a schematic diagram illustrating the process of a terminal device reporting a beam measurement report.

[0060] Figure 10 A schematic flowchart illustrating the measurement report transmission method provided in this application embodiment;

[0061] Figure 11 This application provides an embodiment of a process in which a terminal device reports a first report via Mode B, indicating that the terminal device has received a NACK message / DCI or has not received a response.

[0062] Figure 12 This is a schematic diagram illustrating the process by which a terminal device reports a first report via Mode A and receives a NACK message / DCI or does not receive a response, as provided in an embodiment of this application.

[0063] Figure 13 A schematic diagram illustrating the process by which a terminal device, as provided in this embodiment of the application, reports a first report through mode A and mode B and receives an ACK message;

[0064] Figure 14 A schematic diagram illustrating the process of a terminal device reporting a first report when the starting position of the first duration is the first time unit after the first report is reported, provided for an embodiment of this application;

[0065] Figure 15 A schematic diagram illustrating the process of a terminal device reporting a first report when the start position of the first duration is the end position of the second duration, provided for an embodiment of this application;

[0066] Figure 16 A schematic diagram illustrating the process of a terminal device reporting a first report and a second report when the start position of the first duration is the end position of the second duration, provided for an embodiment of this application;

[0067] Figure 17 A flowchart illustrating the method for a network device to send a response provided in an embodiment of this application;

[0068] Figure 18 A schematic block diagram of a communication device provided in an embodiment of this application;

[0069] Figure 19 A schematic block diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0070] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0071] To facilitate understanding of the embodiments of this application, the following points are explained first:

[0072] First, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. For example, the first value and the second value are only used to distinguish different values, and do not limit their sequence. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and these terms such as "first" and "second" do not necessarily limit differences.

[0073] It should be noted that in the embodiments of the present application, words such as "exemplarily" or "for example" are used to give examples, illustrations or explanations. Any embodiments or design solutions described as "exemplarily" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, the use of words such as "exemplarily" or "for example" aims to present relevant concepts in a specific way.

[0074] In the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents that the front and rear associated objects are in an "or" relationship. "At least one (item)" or its similar expressions refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c can be single or multiple.

[0075] Second, "send" and "receive" in the embodiments of the present application represent the direction of signal transmission. For example, "send information to the second device" can be understood as the destination of the information is the second device, which can include direct transmission through the air interface, and also include indirect transmission through the air interface by other units or modules. "Receive configuration information from the charging" can be understood as the source of the configuration information is the second device, which can include directly receiving from the second device through the air interface, and can also include indirectly receiving from the second device through the air interface from other units or modules. "Send" can also be understood as "output" of the chip interface, and "receive" can also be understood as "input" of the chip interface.

[0076] In other words, sending and receiving can be carried out between devices. For example, between the second device and the first device; it can also be carried out within a device. For example, sending or receiving between components, modules, chips, software modules or hardware modules within a device through a bus, trace or interface.

[0077] It is understandable that information may undergo necessary processing, such as encoding and modulation, before being sent from the source to the destination. Similarly, the destination, upon receiving information from the source, can also perform corresponding processing, such as decoding and demodulation, to interpret the valid information from the source. Similar expressions in this application can be understood in a similar way and will not be elaborated further.

[0078] Third, for ease of understanding, this document provides several examples of message structures, such as RRC messages and UE capability information. The positions, names, and data types of the fields shown in these examples are merely illustrative and should not constitute any limitation on this application.

[0079] Furthermore, RRC messages and UE capability information are just examples; these messages can be replaced by other signaling. For instance, UE capability information can be replaced by uplink control information (UCI), and so on. This application does not limit the names of the signaling messages.

[0080] Fourth, in the embodiments of this application, "instruction" can include direct instruction and indirect instruction, as well as explicit instruction and implicit instruction. The information indicated by a certain piece of information (as described below, the instruction information) is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a correlation between the other information and the information to be instructed; or it can only indicate a part of the information to be instructed, while the other parts of the information to be indicated are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol predefined) arrangement of various pieces of information, thereby reducing the instruction overhead to a certain extent. This application does not limit the specific method of instruction.

[0081] It is understandable that, for the sender of the instruction information, the instruction information can be used to indicate the information to be indicated, and for the receiver of the instruction information, the instruction information can be used to determine the information to be indicated.

[0082] Fifth, the tables in the embodiments of this application are merely examples. The values ​​of the information in each table are only examples and can be configured to other values; this application is not limited thereto. The tables do not limit the scope of protection of this application. For example, appropriate modifications and adjustments can be made based on the tables described above, such as splitting, merging, etc. Furthermore, the parameter names shown in the headings of each table can also use other names understandable to the communication device, and the values ​​or representations of the parameters can also be other values ​​or representations understandable to the communication device. Moreover, in the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0083] Sixth, in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the fact that the device (e.g., network device or terminal device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., network device or terminal device) to make a judgment action when implementing it, nor do they mean that there are other limitations.

[0084] Seventh, the predefined terms in this application can be understood as: definition, pre-defined, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-firing.

[0085] Eighth, the term "storage" in this application can refer to storage in one or more memory devices. These memory devices can be separate installations or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memory devices can be separately installed, while others can be integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0086] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) systems or New Radio (NR) systems, and future communication systems.

[0087] The terminal equipment in this application embodiment can also be referred to as: user equipment (UE), 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.

[0088] Terminal devices can be devices that provide voice / data connectivity to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. This application does not limit the scope to terminal devices in networS (PLMN), etc.

[0089] By way of example and not limitation, in this application, the terminal device can be a terminal device in an Internet of Things (IoT) system. The Internet of Things is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. Exemplarily, the terminal device in the embodiments of this application can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that apply wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that can be worn directly on the body or integrated into a user's clothing or accessories. Wearable devices are not merely hardware devices; they can also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large size, and the ability to achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function and requiring the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0090] By way of example and not limitation, in the embodiments of this application, the terminal device can also be a terminal device in machine-type communication (MTC). Furthermore, the terminal device can also be an on-board module, on-board component, on-board chip, or on-board unit, etc., built into a vehicle as one or more components or units. The vehicle can implement the methods provided in this application through the built-in on-board module, on-board component, on-board chip, or on-board unit, etc. Therefore, the embodiments of this application can also be applied to vehicle networking, such as vehicle-to-everything (V2X), long-term evolution-vehicle (LTE-V) technology, and vehicle-to-vehicle (V2V) technology.

[0091] The network device involved in this application can be a device that communicates with terminal devices. This network device can also be referred to as an access network device or a radio access network (RAN) device. The radio access network device can be a node in the radio access network, or simply a RAN node.

[0092] In one possible scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), a transmission reception point (TRP), a home evolved NodeB (or home Node B, HNB), a Wi-Fi access point (AP), a mobile switching center, a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, or a base station in a future mobile communication system. A RAN node can also be a device that performs base station functions in device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-to-machine (M2M) communication systems, and internet-to-things (IoT) communication systems. A RAN node can also be a RAN node in a non-terrestrial network (NTN), meaning that a RAN node can be deployed on a high-altitude platform or a satellite. RAN nodes can be macro base stations, micro base stations, indoor stations, relay nodes, donor nodes, etc., or radio controllers in cloud radio access network (CRAN) scenarios, or nodes in open radio access network (O-RAN or ORAN) scenarios. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, RAN nodes can be roadside units (RSUs). Of course, RAN nodes can also be nodes in the core network.

[0093] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0094] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in the ORAN system, CU can also be called open CU (O-CU), DU can also be called open DU (O-DU), CU-CP can also be called open CU-CP (O-CU-CP), CU-UP can also be called open CU-UP (O-CU-UP), and RU can also be called open RU (O-RU).

[0095] Any one of the CU (or CU-CP, CU-UP), DU, and RU units can be implemented through software modules, hardware modules, or a combination of software and hardware modules. That is, the wireless access network device in this application can be a virtualized device, for example, implemented through general-purpose hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions. The general-purpose hardware can be a server, such as a cloud server.

[0096] In this embodiment of the application, the RAN node can adopt a CU-DU separation architecture, which can also be referred to as a distributed deployment architecture. For example, Figure 1 This is a schematic diagram of a CU-DU separation architecture used in a RAN node according to an embodiment of this application, as shown below. Figure 1As shown, a RAN node logically includes one CU and one or more DUs. Each DU can connect to the CU via an F1 interface, and information exchange between different DUs can be completed based on CU forwarding. The CU and DU can be physically set together or physically separated, without limitation. The CU can support the functions of the radio resource control (RRC) layer, packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU can support the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer protocols.

[0097] First, let's introduce some of the technical terms and symbols used in this application.

[0098] 1. Hybrid Automatic Repeat Request (HARQ)

[0099] Also known as a HARQ process, it is a mechanism in wireless communication systems used to manage the transmission and retransmission of data packets to improve the reliability and efficiency of packet transmission. Each HARQ process handles data packets independently, and each HARQ process may include processes from initial transmission of data packets to retransmission and final acknowledgment, or from initial transmission of data packets to discarding data packets.

[0100] 2. HARQ process identifier

[0101] It is a unique identifier used to identify a HARQ process. In wireless communication, multiple HARQ processes typically work in parallel, with each process independently handling data transmission and retransmission. The HARQ process ID is used to distinguish different HARQ processes.

[0102] 3. Acknowledgment (ACK)

[0103] It can also be called an ACK message or ACK information. After successfully receiving a data packet, the receiving end can send an ACK message to the sending end to indicate that the data packet has been received correctly (or successfully) and that the data packet has no errors.

[0104] 4. Negative acknowledgment (NACK)

[0105] It can also be called a NACK message or NACK information. When the receiving end fails to receive a data packet, or detects that the data packet is corrupted or lost, it can send a NACK message to the sending end to instruct the sending end to retransmit the data packet.

[0106] 5. Discontinuous reception (DRX)

[0107] It's an energy-saving mechanism. In DRX mode, the UE periodically "wakes up" to check if there is data to receive. Furthermore, in DRX mode, the terminal device can enter a low-power state when it doesn't need to continuously receive data, thereby extending battery life.

[0108] For example, Figure 2 This is a schematic diagram illustrating how a terminal device listens to the physical downlink control channel (PDCCH) in DRX mode. Figure 2 As shown, when the terminal device is configured in DRX mode, each DRX cycle includes an active period and a sleep period. During the active period, the terminal device can listen to the PDCCH. During the sleep period, the terminal device can enter a low-power state and stop listening to the PDCCH.

[0109] It should be understood that active time can also be referred to as DRX on-time, activation time, active period, or the time during which the terminal device is in an active or activated state; sleep time can also be referred to as DRX off-time, sleep period, or the time during which the terminal device is in a sleep state. This application does not specifically limit these terms.

[0110] 6. DRX-HARQ - Round-Trip Time Uplink Timer (drx-HARQ-RTT-TimerUL)

[0111] This is a timer for the HARQ process used in the uplink (UL). When the terminal device is in DRX mode, it can start drx-HARQ-RTT-TimerUL after sending a data packet to the network device. After drx-HARQ-RTT-TimerUL times out, the terminal device can "wake up" and listen to the PDCCH.

[0112] Round-trip time (RTT) can be understood as the time required for the sender to receive an acknowledgment (ACK) or denial (NACK) message from sending a data packet.

[0113] Normally, drx-HARQ-RTT-TimerUL can be activated in the following two situations: when the time-frequency domain resources used by the uplink first transmission data packet are available; when the time-frequency domain resources used by the uplink retransmission data packet are available.

[0114] 7. DRX Retransmission Uplink Timer (drx-RetransmissionTimerUL)

[0115] A timer indicates the maximum time a terminal device can wait for an uplink retransmission instruction from a network device. This maximum waiting time can also be understood as the period during which the terminal device listens to the downlink channel (e.g., PDCCH). This timer starts when the drx-HARQ-RTT-TimerUL times out. During the timer's operation, the terminal device needs to listen to the PDCCH.

[0116] Therefore, when the terminal device is in DRX mode, the terminal device starts drx-RetransmissionTimerUL when drx-HARQ-RTT-TimerUL times out; and during the operation of drx-RetransmissionTimerUL, the terminal device listens to PDCCH, which corresponds to the active time within the DRX cycle.

[0117] 8. Idle mode

[0118] Also known as idle mode or IDLE state, this means that the terminal device has not established an active connection with the network, but still maintains a basic connection with the network so that it can quickly establish a connection when needed.

[0119] 9. Inactive mode

[0120] Also known as deactivation mode, this means that the connection between the terminal device and the network is temporarily suspended, but the context information is still maintained so that the connection can be quickly restored when needed.

[0121] 10. Connected mode

[0122] Also known as connection mode, it refers to the active connection established between the terminal device and the network, enabling data transmission and communication.

[0123] 11. Beam Measurement

[0124] This refers to the measurement of signal quality of a specific beam by terminal equipment, usually using indicators such as signal to interference plus noise ratio (SINR) and secondary synchronization signal-reference signal received power (SS-RSRP).

[0125] 12. Beam Reporting

[0126] Also known as beam measurement report submission, beam measurement report reporting, or beam report submission, this refers to the process of submitting a beam measurement report. The beam measurement report includes signal quality metrics for a specific beam (one or more beams). It can be used for beam management and switching, helping network devices understand the specific signal quality of the beam in which a terminal device is located, thereby enabling more precise resource allocation and beam adjustment.

[0127] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 3 The communication system applicable to the embodiments of this application will be described in detail.

[0128] Figure 3 This is a schematic diagram of a communication system 300 used in an embodiment of this application. The communication system 300 may include at least one network device, such as... Figure 3 The network device 310 shown; the communication system 300 may also include at least one terminal device, such as Figure 3 The terminal device 320 shown.

[0129] In this configuration, terminal device 320 may be located within a cell (carrier) managed by network device 310. Network device 310 and terminal device 320 can communicate via a wireless link. In one possible scenario, network device 310 can act as a transmitter, and terminal device 320 can act as a receiver, with network device 310 sending signals to terminal device 320; in another possible scenario, network device 310 can act as a receiver, and terminal device 320 can act as a transmitter, with terminal device 320 sending signals to network device 310.

[0130] The communication system 300 may also include multiple network devices and / or multiple terminal devices. For example, the communication system 300 may also include network devices 330 and 340. Network device 310 may be, for example, a macro base station (macro gNB or macro g-NodeB), and network devices 330 and 340 may be, for example, small gNBs or small g-NodeBs. When terminal device 320 is simultaneously located in a cell managed by network device 310, a cell managed by network device 330, and a cell managed by network device 340, terminal device 320 may operate in carrier aggregation (CA), dual connectivity (DC), or cooperative multipoint transmission modes. At least one of the multiple cells in which terminal device 320 is located may provide terminal device 320 with at least two sets of parameters (numerology) to simultaneously provide radio resources to terminal device 320.

[0131] It should be understood that Figure 3 The communication system 300 shown is merely an example; the communication system 300 may also include more or fewer network devices, or more or fewer terminal devices. This application does not limit the specific number or form of the network devices or terminal devices.

[0132] Each communication device in the aforementioned communication system 300 can be configured with multiple antennas. These multiple antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. Additionally, each communication device also includes a transmitter chain and a receiver chain, which, as will be understood by those skilled in the art, may include multiple components related to signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, or antennas). Therefore, network devices and terminal devices 320 in the communication system 300 can communicate via multi-antenna technology.

[0133] Optionally, the communication system 300 may also include other network entities such as a network controller and a mobility management entity, but the embodiments of this application are not limited thereto.

[0134] It should also be understood that the method provided in this application embodiment can be applied to a variety of communication systems, including 5G new radio (NR) systems. Communication system 300 is only an example. This application does not limit the specific architecture of the applicable system, nor does it limit the number and form of various devices contained in each communication system.

[0135] Beam management is a crucial component of wireless communication systems, designed to enable terminal devices to smoothly switch and maintain stable connections between different cells and beams. Beam management involves the reporting of beam measurement measurements.

[0136] It is understood that a beam measurement report can also be called a beam-level measurement result, beam measurement report, or beam report, etc., which refers to information including the measurement results of one or more beams. This application does not specifically limit the name of the beam measurement report.

[0137] For ease of description, the following description uses a beam measurement report as an example to illustrate the embodiments of this application.

[0138] In mobility management, Layer Triggered Mobility (LTM) technology refers to the technology that uses information from Layer 1 (L1) and Layer 2 (L2) to trigger and manage the mobility of terminal devices. LTM technology can also be called L1 / L2 triggered mobility, etc.

[0139] In this context, L1 refers to the PHY layer, and L2 refers to the MAC layer, RLC layer, PDCP layer, and SDAP layer. However, in LTM technology, L2 primarily refers to the MAC layer. Therefore, in LTM technology, the measurement reports reported by the terminal device mainly include L1 (PHY layer) measurement reports and L2 (MAC layer) measurement reports.

[0140] For L1 (PHY layer) measurement reports, the terminal device can carry the L1 measurement report in the UCI and send the UCI carrying the L1 measurement report to the network device through the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH).

[0141] In wireless communication systems, terminal devices and network devices transmit information via beams. Therefore, beam management is crucial for improving signal coverage and communication quality. Mobility measurement and reporting are fundamental to beam management. Mobility measurement and reporting can include beam measurement reports submitted by terminal devices.

[0142] For example, combined Figure 4The network device and the terminal device communicate based on multiple beams. The network device can send a measurement configuration to the terminal device, which may include resources or information for measuring the multiple beams. The terminal device can perform beam-level measurements based on the measurement configuration from the network device and determine whether to trigger a beam measurement report based on the measurement results. If the terminal device determines that a beam measurement report needs to be triggered based on the beam-level measurement results, it can send a beam measurement report to the network device. The network device can then perform mobility decisions or carrier management based on the beam measurement report from the terminal device.

[0143] For L1 (PHY) layer beam-level measurements, terminal devices can currently report beam measurement reports through several mechanisms: periodic reporting, semi-persistent reporting, and aperiodic reporting. After receiving beam measurement reports from terminal devices, network devices can make handover decisions based on these reports. Handover decisions can be based on multiple-input multiple-output (MIMO) beam switching strategies. Network devices can send handover decisions to terminal devices via L1 handover commands.

[0144] In addition, in order to reduce the signaling overhead of terminal devices reporting beam measurement reports, 3GPP Release 19 introduced an event-driven beam management method for reporting beam measurement reports in the L1 beam management mechanism, which can reduce unnecessary reporting times and reduce reporting overhead.

[0145] For example, the terminal device may trigger event reporting based on the measured physical layer reference signal received power (L1-RSRP) falling below a certain threshold; and / or, the terminal device may trigger event reporting periodically. Event reporting can also be understood as reporting measurement reports.

[0146] However, not every triggered event report requires executing the measurement report submission process. For example, to reduce the number of beam measurement reports submitted by the terminal device, a built-in counter can be incorporated. After triggering an event report, the terminal device increments the counter by 1. When the counter count exceeds a certain number, the terminal device can trigger the measurement report submission process. Furthermore, the terminal device can reset the counter (set counter to 0 or reset counter) so that the counter can start counting again, allowing the terminal device to correctly trigger the next beam measurement report submission process based on the counter count.

[0147] After the terminal device triggers the measurement report reporting process, it can report the beam measurement report in two modes. These two modes can be referred to as Mode A and Mode B, respectively. The process of reporting the beam measurement report through Mode A and Mode B is described in detail below.

[0148] It should be understood that, in this embodiment of the application, the terminal device triggering the measurement report reporting process can be interpreted as the terminal device triggering an event to report a beam measurement report. That is, the terminal device is about to send a beam measurement report to the network device.

[0149] I. Submit beam measurement reports via Mode A

[0150] Combination Figure 5 When a terminal device triggers the measurement report reporting process, it sends indication information 1 to the network device via PUCCH. Indication information 1 can be 1 bit, such as 0 or 1. Indication information 1 is used to request uplink channel resources to carry beam reports. These resources can be understood as time-frequency domain resources used to report UCIs carrying beam measurement reports.

[0151] After receiving indication information 1 from the terminal device, the network device sends downlink control information (DCI) to the terminal device based on indication information 1. The DCI is used to indicate time-frequency domain resource 1, which is the time-frequency domain resource (also called time-frequency domain resource location) used by the terminal device to report beam measurement reports through UCI.

[0152] Based on the time-frequency domain resource 1 indicated by the DCI, the terminal device can send a UCI to the network device on the time-frequency domain resource 1. The UCI carries a beam measurement report. The UCI can be sent through the PUSCH, and the beam measurement report carried by the UCI may include, but is not limited to, the physical layer reference signal received power (L1-RSRP), where layer 1 is the physical layer.

[0153] It should be understood that, in the embodiments of this application, the beam measurement reports reported by the terminal device through UCI may include, but are not limited to, L1-RSRP. For the sake of brevity, this will not be elaborated upon below.

[0154] II. Reporting beam measurement reports via Mode B

[0155] The difference from Mode A is that the time-frequency domain resources used by the terminal device to send the UCI carrying the beam measurement report to the network device can be pre-configured by the network device. For example, combined with... Figure 6 The upward arrow indicates the transmission of PUCCH. The box corresponding to UCI represents multiple time-frequency domain resources pre-configured by the network device for transmitting UCI. The network device can pre-configure these time-frequency domain resources, for example, through RRC signaling. When the terminal device needs to report a beam measurement report via UCI, it can activate some of these time-frequency domain resources and send the UCI to the network device on the activated time-frequency domain resources.

[0156] For example, when a terminal device triggers a measurement report submission process, the terminal device sends indication information 2 to the network device via PUCCH. Indication information 2 can be 1 bit, such as 0 or 1, and is used to indicate that the terminal device is about to submit a beam measurement report. Indication information 2 can be sent, for example, at position t1.

[0157] Based on the triggered measurement report reporting process, the terminal device can activate some of the time-frequency domain resources among the multiple time-frequency domain resources pre-configured by the network device. For example, the terminal device can activate a time-frequency domain resource after position t1 and send a UCI carrying a beam measurement report to the network device on that time-frequency domain resource. This UCI can be sent via PUSCH or PUCCH.

[0158] Regardless of whether the terminal device reports the beam measurement report through mode A or mode B, it needs to determine whether the network device has successfully (or correctly) received the beam measurement report reported by the terminal device based on the response from the network device.

[0159] For example, combined Figure 7 , Figure 7Image (a) illustrates the process by which a terminal device reports a beam measurement report via Mode A, compared to... Figure 5 The difference lies in that, after the terminal device sends a UCI carrying a beam measurement report to the network device, the terminal device can receive an ACK message from the network device. This ACK message indicates successful reception of the beam measurement report. It should be understood that, in this embodiment, successful reception of the beam measurement report can also be understood as: the network device successfully receives the UCI and correctly parses it, thereby obtaining the correct beam measurement report based on the correctly parsed UCI. For simplicity, this will not be elaborated further below.

[0160] Figure 7 (b) illustrates the process by which the terminal device reports a beam measurement report via Mode B, which is consistent with... Figure 6 The difference is that after the terminal device sends a UCI carrying a beam measurement report to the network device, the terminal device can receive an ACK message from the network device, which is used to indicate that the beam measurement report has been successfully received.

[0161] In this way, after the terminal device reports the beam measurement report via UCI, the ACK message from the network device can confirm that the network device has successfully received the beam measurement report, thus indicating the end of the current measurement report reporting process. Afterwards, the terminal device can trigger the next measurement report reporting process.

[0162] Furthermore, the terminal device can have a built-in counter to record the number of times each event reporting is triggered. That is, the terminal device can preset a threshold, such as threshold 1, and the reporting of a beam measurement report is triggered based on the counter count being greater than or equal to threshold 1. In other words, an event reporting can be triggered multiple times, but a beam measurement report is not reported after each event reporting is triggered. Instead, each time an event reporting is triggered, the counter in the terminal device can be incremented by 1. If the counter count is greater than or equal to threshold 1, the terminal device executes the beam measurement report reporting process, i.e., the measurement report reporting process. Figure 7 In (b), the terminal device sends indication information 2 at position t1 based on the counter count being greater than or equal to the threshold 1.

[0163] Therefore, upon receiving an ACK message from the network device, the beam measurement report reporting process ends. The terminal device can reset the counter (set counter to 0 or reset counter) so that the counter can start counting again, allowing the terminal device to trigger the next beam measurement report reporting process normally based on the counter count.

[0164] Figure 7As an example only, if a network device fails to receive a beam measurement report from a terminal device, the network device can send a NACK message to the terminal device to indicate that the terminal device has not successfully received the beam measurement report. Based on the NACK message from the network device, the terminal device can then resubmit the beam measurement report via UCI.

[0165] It should be understood that, in Mode A, the time-frequency domain resources used to re-report beam measurement reports via UCI can be those indicated by the network device via DCI, specifically related to... Figure 5 The process shown is similar; in Mode B, the time-frequency domain resources used to re-report beam measurement reports via UCI can be pre-configured by the network device, specifically... Figure 6 The process shown is similar, as described above, and will not be repeated here.

[0166] Therefore, the response of network devices is crucial for the normal operation of beam measurement report reporting.

[0167] To reduce power consumption, the terminal device can also report beam measurement reports in DRX mode. Typically, a terminal device in DRX mode can report beam measurements via methods such as... Figure 8 The process shown sends uplink data to the network device.

[0168] like Figure 8 As shown, after the terminal device sends uplink (UL) data to the network device, the terminal device initiates drx-HARQ-RTT-TimerUL on the physical uplink shared channel (PUSCH). The starting position for initiating drx-HARQ-RTT-TimerUL can be the first orthogonal frequency division multiplexing (OFDM) symbol after sending uplink data. Furthermore, when drx-HARQ-RTT-TimerUL times out, the terminal device can initiate drx-RetransmissionTimerUL, and during the operation of drx-RetransmissionTimerUL, the terminal device listens to the PDCCH.

[0169] That is, during the operation of drx-RetransmissionTimerUL, the terminal device is in an active time (or active period), the terminal device listens to the PDCCH, and can receive information sent by the network device through the PDCCH.

[0170] Understandable, Figure 8 In the process illustrated, the uplink data sent by the terminal device can be a MAC Protocol Data Unit (PDU). A MAC PDU can be associated with a HARQ process, allowing the terminal device to start drx-HARQ-RTT-TimerUL for the HARQ process associated with the MAC PDU after sending it to the network device. Furthermore, drx-RetransmissionTimerUL can be started when drx-HARQ-RTT-TimerUL times out, enabling the terminal device to listen to the PDCCH during the execution of drx-RetransmissionTimerUL after sending the MAC PDU to the network device, in order to receive a response from the network device. The terminal device can identify the HARQ process associated with the MAC PDU it sent by using the HARQ process ID.

[0171] However, considering the way the terminal device reports beam measurement reports via mode A or mode B as described above, since the beam measurement report reported by the terminal device is carried in the UCI, and the UCI is not associated with or does not include the HARQ process, the terminal device may not be able to start drx-HARQ-RTT-TimerUL after reporting the UCI, and thus the terminal device may also not be able to start drx-RetransmissionTimerUL.

[0172] In addition, Figure 8 In the process shown, the terminal device initiates drx-HARQ-RTT-TimerUL via PUSCH; that is, the terminal device sends a MAC PDU to the network device via PUSCH and initiates drx-HARQ-RTT-TimerUL after sending the MAC PDU. However, the UCI for reporting beam measurement reports by the terminal device can be transmitted via either PUSCH or PUCCH. If the UCI for reporting beam measurement reports is transmitted via PUCCH, the terminal device cannot initiate drx-HARQ-RTT-TimerUL via PUCCH, which may also prevent the terminal device from initiating drx-RetransmissionTimerUL.

[0173] Therefore, when the terminal device is in DRX mode, after sending a beam measurement report to the network device via UCI, the terminal device may fail to activate drx-RetransmissionTimerUL. This prevents the terminal device from listening to the PDCCH, meaning it cannot receive a response from the network device for the beam measurement report, making it unable to determine whether the network device has successfully received the report. Consequently, the terminal device cannot end the current measurement report reporting process based on successful reception of the report by the network device. For example, the counter used to record the number of event reporting triggers in the terminal device may be incorrect, leading to abnormalities in the measurement report reporting process. The terminal device may also be unable to re-report the beam measurement report based on the network device's failure to receive it, thus affecting the network device's ability to successfully acquire the report, impacting the normal progress of the measurement report reporting process, and affecting the stability of the communication system. For example, poor beam quality of the terminal device may lead to link failure, affecting normal communication between the terminal device and the network device.

[0174] In view of this, a measurement report transmission method is provided. After a terminal device in DRX mode sends a UCI carrying a beam measurement report to a network device, the terminal device listens to the PDCCH for a first time period. This allows the terminal device to receive a response from the network device during this first time period, enabling it to determine whether the network device has successfully received the beam measurement report based on the response. This facilitates the normal operation of the measurement report reporting process and helps maintain the stability of the communication system.

[0175] For example, such as Figure 9 As shown, after the terminal device sends a UCI carrying a beam measurement report to the network device, the terminal device listens to the PDCCH for a first duration. During this first duration, the terminal device can receive a response from the network device. This response can be, but is not limited to, an ACK message, a NACK message, or a DCI, etc. Specifically, an ACK message can indicate that the network device has successfully received the beam measurement report; a NACK message can indicate that the network device has not successfully received the beam measurement report; and a DCI can instruct the terminal device to send (or resend) the beam measurement report, etc.

[0176] It should be understood that, in the embodiments of this application, when the DCI is a response of the network device to a beam measurement report, the DCI can be used to instruct the transmission or retransmission of the measurement report, etc. It is not limited that all DCIs in the embodiments of this application instruct the transmission or retransmission of the measurement report.

[0177] Below, in conjunction with Figures 10 to 17This application provides a detailed description of the measurement report transmission method. The embodiments shown in this application illustrate the measurement report transmission method from the perspective of device interaction. The specific forms and numbers of the devices shown are merely examples and should not be construed as limiting the implementation of the method provided in this application. Below, using network devices and terminal devices as examples, the measurement report transmission method of the embodiments of this application will be described in detail.

[0178] It should be understood that the terminal device can be the terminal device itself, or a chip, chip system, or processor that supports the terminal device in implementing the measurement report transmission method, or a logic module or software that can implement all or part of the terminal device; the network device can be the network device itself, or a chip, chip system, or processor that supports the network device in implementing the measurement report transmission method, or a logic module or software that can implement all or part of the network device, and this application does not make any specific limitations in this regard.

[0179] Figure 10 This is a flowchart illustrating a measurement report transmission method 1000 provided in an embodiment of this application. Method 1000 is applicable to system 300 and includes the following steps:

[0180] S1001. In DRX mode, the terminal device sends a first report to the network device. The first report indicates the measurement results of one or more beams and is carried in the UCI. Correspondingly, the network device receives the UCI from the terminal device, which includes the first report.

[0181] DRX mode can also be understood as the terminal device being in DRX mode, the terminal device configuring DRX mode, the terminal device starting DRX mode, or the terminal device activating DRX mode. In DRX mode, the terminal device may be in a sleep period, i.e., a period during which it does not listen to the PDCCH; the terminal device may also be in an active period, i.e., a period during which it listens to the PDCCH. The first report can be understood as the beam measurement report mentioned above. The measurement results of one or more beams may include, for example, the RSRP measured for each of the one or more beams. The first report may include, but is not limited to, L1-RSRP.

[0182] It should be understood that UCI can be interpreted as control information carried in signaling at the PHY layer. UCI can be transmitted, for example, but not limited to, via PUSCH and PUCCH. In future communication systems, UCI may also be replaced with other names, and this application embodiment does not specifically limit the name of the control information carrying the first report.

[0183] S1002. After the terminal device sends the first report, the terminal device listens to the PDCCH within a first time period.

[0184] The first duration begins after the terminal device sends the first report. The first duration can also be understood as the length of time the terminal device remains active. The first duration is the time the terminal device uses to listen to the PDCCH, and this timing can be triggered by the terminal device sending the first report.

[0185] Optionally, the first duration is pre-configured or indicated by signaling.

[0186] It should be understood that the first duration is pre-configured. For example, it can be understood as the duration pre-configured by the network device before triggering the current measurement report reporting process.

[0187] For example, method 1000 further includes: the network device sending information 1 to the terminal device, information 1 indicating a first duration. Correspondingly, the terminal device receives information 1 from the network device. Information 1 may be carried, for example, in RRC signaling.

[0188] Alternatively, information 1 can be used to indicate multiple durations, including a first duration. The first duration is the duration from which the network device is activated among the multiple durations, for example, the network device instructs the terminal device to activate the first duration via signaling, or the first duration is the duration from which the terminal device is activated among the multiple durations, etc.

[0189] Furthermore, the first duration indicated by signaling can be understood as the duration indicated by the network device via signaling after the current measurement report reporting process is triggered.

[0190] For example, method 1000 further includes: the network device sending information 2 to the terminal device, the information 2 indicating a first duration. Correspondingly, the terminal device receives information 2 from the network device. Information 2 may be carried in DCI, for example.

[0191] Alternatively, the network device sends information 1 to the terminal device, where information 1 indicates multiple durations; then, the network device sends information 2 to the terminal device, where information 2 indicates a first duration or indicates activation of a first duration.

[0192] In this way, the terminal device can determine the first duration for listening to the PDCCH.

[0193] It is understandable that, regardless of how the initial duration is determined, the triggering method for the current measurement report submission process mentioned above is consistent with... Figure 6 or Figure 7The triggering method for the illustrated process is similar. That is, the current measurement report submission process can be triggered as follows: the terminal device sends information 3 to the network device, where information 3 indicates that a beam measurement report is about to be submitted; correspondingly, the network device receives information 3 from the terminal device. Information 3 is similar to the indication information 1 or indication information 3 mentioned above, and information 3 can be transmitted via PUCCH, for example. Information 1 mentioned above can be sent before information 3; information 2 can be sent after information 3.

[0194] Based on the above embodiments, the first duration can be understood as either a fixed time period or a timer with a timing length of the first duration. When the first duration is a timer with a timing length of the first duration, S1002 can be implemented as follows: after the terminal device sends the first report, the first timer is started, and the PDCCH is listened to during the operation of the first timer, where the timing length of the first timer is the first duration.

[0195] Listening to the PDCCH during the first timer's operation can also be understood as: the terminal device listens to the PDCCH after the first timer starts and before it times out. The first timer is similar to drx-RetransmissionTimerUL mentioned above, and can be understood as a timer used to count the duration of the terminal device's active time, or it can be understood as the terminal device being active during the first timer's timing or operation.

[0196] It should be understood that the first timer may be called drx-RetransmissionTimerUL, or uplink active time timer (Active-TimerUL), etc. This application does not specifically limit the name of the first timer.

[0197] It should also be noted that the first timer can be a forward timer, meaning that the first timer can start counting from 0 and end when the first duration is reached; or, the first timer can be a reverse timer, meaning that the first timer can count down from the first duration and end when the first duration is reached. This application does not specifically limit the type of the first timer.

[0198] The measurement report transmission method of this application, when the terminal device is in DRX mode and after the terminal device sends a UCI carrying a beam measurement report to the network device, allows the terminal device to listen to the PDCCH for a first duration. This allows the terminal device to receive a response from the network device while listening to the PDCCH, thereby determining whether the network device has successfully received the first report based on the response. This enables the terminal device to, for example, end the current measurement report reporting process or re-report the beam measurement report based on the response, facilitating the normal operation of the measurement report reporting process and contributing to the stability of the communication system.

[0199] The following details the steps that the terminal device should take in several scenarios, including when the terminal device does not receive a response from the network device within the first time period or receives different responses from the network device.

[0200] In the first scenario, the network device's response indicates that the first report was not successfully received; this response is, for example, a NACK message.

[0201] As an optional embodiment, method 1000 further includes: the network device sending first information to the terminal device, the first information indicating that a first report was not successfully received; correspondingly, within a first duration, the terminal device receives the first information from the network device. Based on the first information, the terminal device sends a second report to the network device, the second report indicating the measurement results of one or more beams, the second report being carried in the UCI; correspondingly, the network device receives the second report from the terminal device.

[0202] The first information may be, for example, a NACK message, or it may be understood as information carried in other signaling or messages to indicate that the network device has not successfully received the first report.

[0203] It should be understood that, in the embodiments of this application, the failure of the network device to successfully receive the first report can also be interpreted as: the network device failing to successfully decode the UCI carrying the first report, the network device failing to successfully receive the UCI carrying the first report, or the network device failing to successfully decode the first report, etc. This application does not specifically limit this.

[0204] It should also be understood that, in this embodiment of the application, the NACK message (the network device's response) used to indicate that the first report was not successfully received is merely an example. The NACK message can also be used to indicate sending or retransmitting the beam measurement report, etc. That is, the NACK message can be used to indicate: the first report was not successfully received, and / or, to send or retransmit the beam measurement report. Based on the NACK message, the terminal device can determine that the network device has not successfully received the first report and that the beam measurement report needs to be retransmitted.

[0205] If the terminal device determines that the network device has not successfully received the first report, in order to enable the network device to successfully obtain the beam measurement report, the terminal device can resend the beam measurement report to the network device; that is, the terminal device can send a second report to the network device based on the first information. The second report may be the same as or different from the first report. If the second report is different from the first report, the second report may include the latest measurement results of the terminal device for S beams, where S is a positive integer. The S beams may be the same as or different from one or more beams in the first report.

[0206] In the second scenario, the network device's response instructs the terminal device to send or resend the measurement report; this response could be, for example, a DCI (Digital Curve Interchange). The measurement report here could also be replaced with a beam measurement report.

[0207] As an optional embodiment, method 1000 further includes: the network device sending second information to the terminal device, the second information indicating the sending of a measurement report; correspondingly, within a first duration, the terminal device receives the second information from the network device. Based on the second information, the terminal device sends a second report to the network device, the second report indicating the measurement results of one or more beams, the second report being carried in the UCI; correspondingly, the network device receives the second report from the terminal device.

[0208] The second information can be, for example, DCI, or it can be carried in DCI, or it can be information carried in other signaling. The second information is used to indicate that the network device has not successfully received the first report, and the terminal device needs to send the beam measurement report to the network device again.

[0209] It should be understood that the second information used to instruct the sending of the measurement report can also be replaced by: the second information used to instruct the terminal device to resend the measurement report; the second information used to instruct the network device to fail to receive (or decode) the first report (or measurement report); the second information used to instruct the network device to fail to receive (or decode) the UCI; or the second information used to instruct the network device to fail to receive (or decode) the UCI carrying the first report, etc. This application does not specifically limit this.

[0210] It should also be understood that the implementation method of the terminal device sending the second report in the second case is similar to that in the first case, as described above, and will not be repeated here.

[0211] For the first and second scenarios described above, after the terminal device receives the first or second information within a first time period, the terminal device can continue to listen to the PDCCH; or, method 1000 may further include: the terminal device stopping listening to the PDCCH based on the first or second information from the network device. This results in lower power consumption for the terminal device.

[0212] It should be understood that stopping PDCCH listening can also be interpreted as the terminal device stopping the timing of the first duration. That is, the first duration is the duration of the active time (listening to PDCCH). If the terminal device no longer needs to listen to PDCCH, it can stop timing the first duration.

[0213] Furthermore, when the first duration is timed using the first timer, stopping PDCCH monitoring can also be understood as: the terminal device turning off the first timer or stopping the first timer, etc. For the sake of brevity, this will not be elaborated further below.

[0214] The third scenario is that the terminal device does not receive a response from the network device.

[0215] As an optional embodiment, method 1000 further includes: the terminal device not receiving a response from the network device to the first report within a first duration; and sending a second report after the first duration has expired, the second report indicating the measurement results of one or more beams, the second report being carried in the UCI.

[0216] The second report can be sent when the first timeout period expires, that is, the second report can be sent after the first timeout period expires or it can be replaced by sending the second report when the first timeout period expires; or, the second report can be sent after a certain period of time after the first timeout period expires.

[0217] It should be understood that the implementation method of the terminal device sending the second report in the third case is similar to that in the first case, as described above, and will not be repeated here.

[0218] A response can be understood as a network device's response to a first report or a UCI carrying the first report. A response can also be understood as the first, second, and third information in the embodiments of this application. Exemplarily, a response may include, but is not limited to, one or more of the following: an ACK message (indicating successful reception of the first report), a NACK message (indicating unsuccessful reception of the first report), or a DCI (indicating the transmission of a measurement report). That is, within the first time period, the terminal device does not receive an ACK message, NACK message, or DCI from the network device, nor does it receive any other information indicating successful or unsuccessful reception of the first report. Therefore, the terminal device can report the beam measurement report again, i.e., report a second report.

[0219] Combining the first to third scenarios above, it can be seen that if the terminal device determines, based on the response from the network device, that the network device has not successfully received the first report, or if the terminal device has not received a response from the network device, the terminal device can send a second report to the network device again or send a PUCCH to request uplink channel resources to carry the beam report.

[0220] Optionally, the time-frequency domain resources for the terminal device to send the second report are pre-configured or indicated by signaling.

[0221] The time-frequency domain resource used to send the second report is pre-configured, which can also be understood as the second report being submitted by the terminal device according to Mode B. That is, the time-frequency domain resource used to send the second report is one of multiple time-frequency domain resources pre-configured by the network device before the current measurement report submission process is triggered. These multiple pre-configured time-frequency domain resources can be multiple time-frequency domain resources with the same time interval, for example... Figure 7 The image shows several time-frequency domain resources.

[0222] For example, method 1000 further includes: the network device sending information 4 to the terminal device, information 4 indicating multiple time-frequency domain resources; correspondingly, the terminal device receiving information 4 from the network device. Information 4 may, for example, be carried in RRC signaling.

[0223] It should be noted that if the second report is submitted in accordance with Mode B (the time-frequency domain resources for sending the second report are pre-configured), the first report can also be submitted in accordance with Mode B, that is, the time-frequency domain resources for submitting the first report are also pre-configured.

[0224] For example, combined Figure 11 ,like Figure 11 As shown in (a), the network device pre-configures multiple time-frequency domain resources for reporting UCIs carrying beam measurement reports via signaling such as RRC signaling. After the terminal device sends a UCI carrying the first report to the network device on one of the time-frequency domain resources, it listens to the PDCCH for a first duration. Before the first duration expires, if the terminal device receives a response from the network device, such as a NACK message or DCI, the terminal device can determine that the network device has not successfully received the first report or has not successfully decoded the first report, and the terminal device needs to report the beam measurement report again. The terminal device can send a UCI carrying the second report to the network device on the pre-configured time-frequency domain resources after receiving a response such as a NACK message or DCI.

[0225] Alternatively, the first report may be reported according to Mode B, meaning the time-frequency domain resources for reporting the first report are pre-configured, and the time-frequency domain resources for reporting the second report may also be indicated by the network device's response to the first report. For example, combined with... Figure 11 In (a), the response from the network device, such as a NACK message or DCI, can carry information indicating time-frequency domain resource A. Then, the terminal device can send a second report to the network device on time-frequency domain resource A based on the information indicating time-frequency domain resource A.

[0226] If the terminal device does not receive a response from the network device within the first time period, the process of the terminal device sending a second report can be as follows: Figure 11 As shown in (b) above. After the terminal device sends a UCI carrying a first report to the network device on one of the pre-configured time-frequency domain resources, the terminal device listens to the PDCCH for a first duration. If the terminal device does not receive a response from the network device when the first duration expires, the terminal device can determine that it needs to report the beam measurement report again. The terminal device can send a UCI carrying a second report to the network device on the pre-configured time-frequency domain resources after the first duration expires.

[0227] It should be understood that Figure 11 (b) The terminal device determines the time-frequency domain resources for reporting the first and second reports and Figure 11 The method by which the terminal device determines the time-frequency domain resources for reporting the first and second reports in (a) is similar, as described above, and will not be repeated here.

[0228] The time-frequency domain resources for sending the second report are indicated by signaling, which can also be understood as the second report being submitted in mode A. That is, the time-frequency domain resources for sending the second report are the time-frequency domain resources indicated by the network device via signaling after the current measurement report submission process is triggered.

[0229] For example, method 1000 further includes: the network device sending information 5 to the terminal device, information 5 indicating time-frequency domain resources for sending the second report; correspondingly, the terminal device receiving information 5 from the network device. Information 5 may, for example, be carried in DCI.

[0230] It should be noted that if the second report is submitted in accordance with Mode A (the time and frequency domain resources for sending the second report are indicated by signaling), the first report can also be submitted in accordance with Mode A, that is, the time and frequency domain resources for submitting the first report are also indicated by signaling.

[0231] For example, combined Figure 12 ,like Figure 12As shown in (a), before reporting the first report, the network device indicates time-frequency domain resource 2 via DCI, and the terminal device sends a UCI carrying the first report to the network device on time-frequency domain resource 2. Afterwards, the terminal device listens to the PDCCH for a first duration; if the terminal device receives a response from the network device before the first duration expires, such as a NACK message or DCI, the terminal device can determine that the network device has not successfully received or decoded the first report, and the terminal device needs to report the beam measurement report again. At this time, the terminal device can send indication information 1 to the network device via PUCCH. Indication information 1 is used to request uplink channel resources to carry the beam report. After the network device indicates time-frequency domain resource 3 to the terminal device via DCI, the terminal device can send a UCI carrying the second report to the network device on time-frequency domain resource 3.

[0232] Alternatively, the time-frequency domain resources reported in the first report and the time-frequency domain resources reported in the second report are indicated by the network device through the same DCI. For example, combining... Figure 12 In (a), the DCI used to indicate time-frequency domain resource 3 is optional, meaning that both time-frequency domain resource 2 and time-frequency domain resource 3 can be accessed via... Figure 12 (a) is used to indicate the DCI indication of time-frequency domain resource 2.

[0233] If the terminal device does not receive a response from the network device within the first time period, the process of the terminal device sending a second report can be as follows: Figure 12 As shown in (b) above. Before reporting the first report, the network device indicates time-frequency domain resource 4 to the terminal device via DCI, and the terminal device sends a UCI carrying the first report to the network device on time-frequency domain resource 4. Afterwards, the terminal device listens to the PDCCH for a first duration; if the terminal device does not receive a response from the network device when the first duration expires, the terminal device can determine that it needs to report the beam measurement report again. At this time, the terminal device can send indication information 1 to the network device via PUCCH. Indication information 1 is used to request uplink channel resources to carry the beam report. If the network device indicates time-frequency domain resource 5 to the terminal device via DCI, the terminal device sends a UCI carrying the second report to the network device on time-frequency domain resource 5.

[0234] It should be understood that Figure 12 (b) The terminal device determines the time-frequency domain resources for reporting the first and second reports and Figure 12 The terminal device in (a) determines the time-frequency domain resources for reporting the first and second reports in a similar way. That is, the network device can also indicate time-frequency domain resources 4 and 5 through the same DCI. Please refer to the description above, which will not be repeated here.

[0235] In the fourth scenario, the network device's response indicates successful reception of the first report; this response is, for example, an ACK message.

[0236] As an optional embodiment, method 1000 further includes: the network device sending third information to the terminal device, the third information indicating successful reception of the first report; correspondingly, within a first duration, the terminal device receives the third information from the network device. Based on the third information, the terminal device stops listening to the PDCCH.

[0237] The third piece of information can be, for example, an ACK message.

[0238] It should be understood that the third information used to indicate successful reception of the first report can also be interpreted as: the third information used to indicate successful reception of the UCI carrying the first report, the third information used to indicate successful decoding of the UCI carrying the first report, or the third information used to indicate successful decoding of the first report, etc., indicating that the network device can obtain the correct first report. This application does not specifically limit this.

[0239] Once the network device successfully receives the first report, the terminal device can stop listening to the PDCCH, for example, by turning off the first timer. Furthermore, the terminal device can reset the counter (set counter to 0 or reset counter) so that the counter can start counting again the next time the terminal device triggers an event report. This allows the terminal device to correctly trigger the beam measurement report reporting process based on the counter count, thus facilitating the normal operation of beam measurement report reporting.

[0240] In the fourth scenario, the time-frequency domain resources for reporting the first report can be pre-configured or indicated by the network device via signaling.

[0241] It should be understood that the determination method for the time-frequency domain resources in the first report is similar to that in the second report, as described above, and will not be repeated here.

[0242] For example, when the first report is reported according to Mode B (the time-frequency domain resources for reporting the first report are pre-configured), the process of the terminal device reporting the first report can be as follows: Figure 13 As shown in (a) in the figure.

[0243] Network devices pre-configure multiple time-frequency domain resources for reporting UCIs carrying beam measurement reports via signaling such as RRC signaling. After a terminal device sends a UCI carrying the first report to the network device on one of the time-frequency domain resources, it listens for the PDCCH for a first duration. If the terminal device receives a response from the network device, such as an ACK message, before the first duration expires, the terminal device can determine that the network device has successfully received or successfully decoded the first report. The terminal device can then stop timing the first duration, for example, by turning off the first timer.

[0244] When the first report is submitted according to Mode A (the time-frequency domain resources for submitting the first report are indicated via signaling), the process of the terminal device submitting the first report can be as follows: Figure 13 As shown in (b) of the diagram.

[0245] Before submitting the first report, the terminal device can send indication information 1 to the network device via PUCCH. Indication information 1 is used to request uplink channel resources to carry the beam report. After the network device indicates time-frequency domain resource 6 to the terminal device via DCI, the terminal device can send a UCI carrying the first report to the network device on time-frequency domain resource 6. Afterwards, the terminal device listens to the PDCCH for the first duration. Before the first duration expires, if the terminal device receives a response from the network device, such as an ACK message, the terminal device can determine that the network device has successfully received or successfully decoded the first report. The terminal device can then stop timing the first duration, for example, by turning off the first timer.

[0246] Based on the above embodiments, the starting position of the first duration can be determined in the following two ways.

[0247] In the first method, since PDCCH monitoring is triggered by sending the first report, the starting position of the first duration can be determined based on sending the first report.

[0248] The starting position of the first duration is determined based on the sending of the first report, which can also be understood as: the starting position of the first duration can be determined based on the ending position of the sending of the first report. For example, the starting position of the first duration can be the first time unit after the sending of the first report, etc.

[0249] The starting position of the first duration can also be understood as the moment or position at which the first timer begins counting. The first time unit after sending the first report could be, for example, the first symbol after sending the first report.

[0250] It should be understood that, in the embodiments of this application, the time unit may include, but is not limited to, one or more of the following: OFDM symbol (also referred to as a symbol), time slot, subframe, or frame, etc. This application does not specifically limit this.

[0251] When the starting position of the first duration is the first time unit after the first report is sent, the process of the terminal device reporting the beam measurement report can be as follows: Figure 14 As shown. Combined with Figure 14 In (a), in the first time unit (e.g., the first symbol) after the terminal device sends a UCI carrying the first report to the network device, the timing of the first duration begins, for example, starting a first timer; before the first duration expires, for example, before the first timer expires, if the terminal device receives a response from the network device (e.g., a NACK message or DCI), the terminal device can determine that the network device has not successfully received the first report or has not successfully decoded the first report, and needs to report the beam measurement report again; when the first duration expires, for example, when the first timer expires, the terminal device sends a UCI carrying the second report to the network device.

[0252] or, Figure 14 The response (e.g., NACK message or DCI) received by the terminal device in (a) can be optional, that is, if the terminal device does not receive a response from the network device when the first timeout period expires, the terminal device may also send a UCI carrying a second report to the network device when the first timeout period expires, such as when the first timer expires.

[0253] Before the first timeout, if the terminal device receives an ACK message from the network device, the process of the terminal device reporting a beam measurement report can be as follows: Figure 14 As shown in (b) above, after receiving an ACK message from the network device, the terminal device can stop timing for the first duration, i.e., turn off the first timer and stop listening to the PDCCH.

[0254] It should be understood that Figure 14 For illustrative purposes only, the terminal device may also stop timing the first duration after receiving a response (such as a NACK message or DCI) from the network device, for example, by turning off the first timer; and the time-frequency domain resources sent by the terminal device carrying the UCI with the second report may also be in other locations, as described above, and will not be repeated here.

[0255] In the second method, the time interval between the start position of the first duration and the sending of the first report is the second duration.

[0256] The second duration can be the same as or different from the first duration. The second duration can be a fixed time period or a timer with a duration equal to the second duration. The second duration is used to determine the starting position of the first duration. That is, the starting position of the first duration can be the ending position of the second duration.

[0257] When the second duration is the second timer, S1002 can be implemented as follows: after the terminal device sends the first report to the network device, the second timer is started, and during the first duration after the second timer expires, the PDCCH is listened to, and the duration of the second timer is the second duration.

[0258] Since the first duration can also be understood as the duration of the first timer, S1002 can also be implemented in the following way: after the terminal device sends the first report to the network device, the second timer is started, and the first timer is started when the second timer times out. During the operation of the first timer, the terminal device listens to the PDCCH. The duration of the second timer is the second duration, and the duration of the first timer is the first duration.

[0259] The phrase "when the second timer times out" can also be replaced with "after the second timer times out". This application does not impose specific limitations on this.

[0260] When the time interval between the start of the first duration and the transmission of the first report is the second duration, the process of the terminal device reporting the beam measurement report can be as follows: Figure 15 As shown. Combined with Figure 15 In (a), after the terminal device sends a UCI carrying the first report to the network device, it starts timing for the second duration, for example, by starting a second timer; when the second duration expires, for example, when the second timer expires, it starts timing for the first duration, for example, by starting a first timer; before the first duration expires, for example, before the first timer expires, if the terminal device receives a response from the network device (e.g., a NACK message or DCI), the terminal device can determine that the network device has not successfully received the first report or has not successfully decoded the first report, and needs to report the beam measurement report again; when the first duration expires, for example, when the first timer expires, the terminal device sends a UCI carrying the second report to the network device.

[0261] or, Figure 15 The response (e.g., NACK message or DCI) received by the terminal device in (a) can be optional, that is, if the terminal device does not receive a response from the network device when the first timeout period expires, the terminal device may also send a UCI carrying a second report to the network device when the first timeout period expires, such as when the first timer expires.

[0262] Before the first timeout, if the terminal device receives an ACK message from the network device, the process of the terminal device reporting a beam measurement report can be as follows: Figure 15 As shown in (b) above, after receiving an ACK message from the network device, the terminal device can stop timing the first duration, for example, by turning off the first timer.

[0263] It should be understood that Figure 15 For illustrative purposes only, the terminal device may also stop timing the first duration after receiving a response (such as a NACK message or DCI) from the network device; and the time-frequency domain resources sent by the terminal device carrying the UCI with the second report may also be in other locations, as described above, and will not be repeated here.

[0264] For example, such as Figure 16 As shown, after the terminal device sends a UCI carrying the first report to the network device, it starts timing for the second duration, for example, by starting a second timer; when the second duration times out, for example, when the second timer times out, it starts timing for the first duration, for example, by starting a first timer; before the first duration times out, for example, before the first timer times out, the terminal device receives a response from the network device (e.g., a NACK message or DCI), and the terminal device stops timing for the first duration, for example, by turning off the first timer; and when the first duration times out, for example, when the first timer times out, it sends a UCI carrying the second report to the network device; after sending the UCI carrying the second report, the terminal device starts timing for the second duration again, for example, by starting a second timer; when the second duration times out, for example, when the second timer times out, the terminal device starts timing for the first duration again, for example, by starting a first timer; before the first duration times out, for example, before the first timer times out, the terminal device receives an ACK message from the network device, the terminal device stops timing for the first duration, for example, by turning off the first timer, and the measurement report reporting process ends. The terminal device can reset the counter used to record the number of event reporting triggers (set counter to 0 or reset counter) so that the counter can correctly record the number of event reporting triggers, so that the subsequent measurement report reporting process can proceed normally.

[0265] It should be understood that in the second method, the starting position of the second duration or the starting position or time of the second timer can be understood as the first time unit after the terminal device sends the first report. The method of determining the starting position of the second duration is similar to the method of determining the starting position of the first duration in the first method, which can be referred to in the above description and will not be repeated here.

[0266] It should also be understood that, in the embodiments of this application, the second timer may also be referred to as a second timer, a round-trip time uplink timer (RTT-TimerUL), or drx-HARQ-RTT-TimerUL, etc. This application does not specifically limit the name of the second timer.

[0267] Based on the above embodiments, the responses sent by the network device to the terminal device, such as first information (NACK message) or second information (DCI), can be sent in the following manner.

[0268] Figure 17 This is a flowchart illustrating a method 1700 for a network device to send a response to a terminal device, as provided in an embodiment of this application. Method 1700 can be applied to a communication system 300. Furthermore, the network device in the communication system 300 can adopt a CU-DU separation architecture. Method 1700 includes:

[0269] S1701, the DU sends a fifth message to the CU based on the failure to successfully parse the UCI carrying the first report. The fifth message can be used to indicate that the first report was not successfully received, and the fifth message can be, for example, the first message or the second message. Correspondingly, the CU receives the fifth message from the DU.

[0270] S1702. Based on the fifth piece of information, the CU generates and sends a response (NACK message or DCI) to the DU. Correspondingly, the DU receives the response from the CU.

[0271] S1703, DU sends a response (NACK message or DCI) to the terminal device. Correspondingly, the terminal device receives the response from DU.

[0272] As can be seen from method 1700, the NACK message (a response to the beam measurement report reported by the terminal device) can be generated by the DU, that is, the generation and processing of the NACK message can be performed at the MAC layer.

[0273] It should be noted that, in addition to the response shown in method 1700, other information sent from the CU to the terminal device can also be sent via the DU. That is, communication between the terminal device and the CU can be achieved through the DU. For the sake of brevity, these will not be shown one by one here.

[0274] It should be noted that the order of the methods listed above does not imply the order of execution. The execution order of each process should be determined by its function and internal logic.

[0275] The above text combined Figures 9 to 17 The measurement report transmission method of the embodiments of this application is described in detail below, in conjunction with Figures 18 to 19This application describes in detail the communication apparatus according to embodiments of the present application. The communication apparatus includes modules or units for performing each part of the above embodiments. The modules or units may be software, hardware, or a combination of software and hardware. The following is only a brief illustrative example of the communication apparatus; for details of the implementation, please refer to the description of the foregoing method embodiments, which will not be repeated below.

[0276] Figure 18 This is a schematic block diagram of a communication device 1800 provided for an embodiment of this application. Figure 18 As shown, the communication device 1800 includes a transceiver module 1801 and a processing module 1802.

[0277] In one possible implementation, the communication device 1800 is used to implement the steps of the terminal device in the methods 1000 and 1700 described above.

[0278] The transceiver module 1801 is used to send a first report in discontinuous reception DRX mode. The first report is used to indicate the measurement results of one or more beams and is carried in the uplink control information UCI. The processing module 1802 is used to listen to the physical downlink control channel PDCCH for a first duration after sending the first report.

[0279] Optionally, the transceiver module 1801 is specifically used to: start a first timer and listen to the PDCCH during the operation of the first timer, wherein the timing length of the first timer is a first duration.

[0280] Optionally, the starting position of the first duration is the first time unit after the first report is sent; or, the time interval between the starting position of the first duration and the sending of the first report is the second duration.

[0281] Optionally, the processing module 1802 is specifically used to: after sending the first report, start the second timer, and listen to the PDCCH for a first duration after the second timer expires, wherein the duration of the second timer is the second duration.

[0282] Optionally, the transceiver module 1801 is further configured to: receive a first message or a second message within a first duration, wherein the first message indicates that the first report was not successfully received and the second message indicates that a measurement report is to be sent; and send a second report based on the first message or the second message, wherein the second report indicates the measurement results of one or more beams and is carried in the UCI.

[0283] Optionally, the processing module 1802 is also used to: stop listening to the PDCCH based on the first information or the second information.

[0284] Optionally, the time-frequency domain resources for sending the first report and the time-frequency domain resources for sending the second report are pre-configured or indicated by signaling.

[0285] Optionally, the transceiver module 1801 is further configured to: if no response to the first report is received within a first duration; and after the first duration expires, send a second report, which indicates the measurement results of one or more beams, and the second report is carried in the UCI.

[0286] Optionally, the transceiver module 1801 is further configured to: receive third information within a first duration, the third information being used to indicate successful reception of the first report; the processing module 1802 is further configured to: stop listening to the PDCCH based on the third information.

[0287] Optionally, the first duration is pre-configured or indicated by signaling.

[0288] In another possible implementation, the communication device 1800 is used to implement the steps corresponding to the network device in the above-described method 1000 or method 1700.

[0289] The transceiver module 1801 is used to: send fourth information, which is used to indicate a first duration; receive a first report from the terminal device, which is used to indicate the measurement results of one or more beams. The first report is carried in uplink control information (UCI), wherein the first duration is started based on the transmission of uplink control information (UCI) and is used to listen to the physical downlink control channel (PDCCH) corresponding to the first report.

[0290] It should be understood that the communication device 1800 here is embodied in the form of a functional module. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the communication device 1800 can specifically be a terminal device or network device as described in the above embodiments. The communication device 1800 can be used to execute the various processes and / or steps corresponding to the terminal device or network device in the above method embodiments; to avoid repetition, these will not be described further here.

[0291] The aforementioned communication device 1800 has the function of implementing the corresponding steps performed by the terminal device or network device in the above method; the above functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In embodiments of this application, Figure 18The communication device 1800 in the text can also be a chip, such as a SOC.

[0292] Figure 19 A schematic diagram of the communication device 1900 provided in an embodiment of this application is shown. The communication device 1900 includes a processor 1901, a transceiver 1902, and a memory 1903. The processor 1901, transceiver 1902, and memory 1903 communicate with each other via internal interconnection. The memory 1903 stores instructions, such as computer-defined code. The processor 1901 executes the instructions stored in the memory 1903 to control the transceiver 1902 to transmit and / or receive signals.

[0293] It should be understood that the communication device 1900 may specifically be a network device or a terminal device in the above embodiments, and may be used to execute the various steps and / or processes corresponding to the network device or terminal device in the above method embodiments. Optionally, the memory 1903 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 non-volatile random access memory. For example, the memory may also store device type information. The processor 1901 may be used to execute instructions stored in the memory, and when the processor 1901 executes instructions stored in the memory, the processor 1901 is used to execute the various steps and / or processes of the above method embodiments. The transceiver 1902 may include a transmitter 19021, a receiver 19022, and an antenna 19023. The transmitter 19021 may be used to implement the various steps and / or processes corresponding to the transceiver for performing the transmission action. For example, the transmitter 19021 may be used to transmit information to another device through the antenna 19023. Receiver 19022 can be used to implement the various steps and / or processes corresponding to the transceiver described above for performing the receiving action. For example, receiver 19022 can be used to receive information from another device via antenna 19023.

[0294] It should be understood that, in the embodiments of this application, the processor may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0295] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0296] This application also provides a computer-readable storage medium for storing a computer program for implementing the methods shown in the above-described method embodiments.

[0297] This application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run on a computer, allows the computer to perform the methods shown in the above-described method embodiments.

[0298] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0299] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0300] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0301] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0302] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0303] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0304] The above description is merely a specific embodiment of this application, but the protection scope of the embodiments of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of this application should be included within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A measurement report transmission method, characterized by, Comprising: transmitting a first report, the first report being used for indicating measurement results of one or more beams, the first report being carried in uplink control information (UCI); after transmitting the first report, listening to a physical downlink control channel (PDCCH) in a first time duration.

2. The method of claim 1, wherein, The listening to the PDCCH in the first time duration comprises: starting a first timer and listening to the PDCCH during running of the first timer, a time length of the first timer being the first time duration.

3. The method according to claim 1 or 2, characterized in that, A starting position of the first time duration is a first time unit after transmitting the first report; or a time interval between the starting position of the first time duration and transmitting the first report is a second time duration.

4. The method of claim 3, wherein, The listening to the PDCCH comprises: after transmitting the first report, starting a second timer and listening to the PDCCH in the first time duration after expiration of the second timer, a time length of the second timer being the second time duration.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: receiving first information or second information in the first time duration, the first information being used for indicating that the first report is not successfully received, and the second information being used for indicating transmitting a measurement report; based on the first information or the second information, transmitting a second report, the second report being used for indicating measurement results of one or more beams, the second report being carried in UCI.

6. The method of claim 5, wherein, The method further comprises: based on the first information or the second information, stopping listening to the PDCCH.

7. The method according to claim 5 or 6, characterized in that, A time-frequency domain resource for transmitting the first report and a time-frequency domain resource for transmitting the second report are pre-configured or indicated by signaling.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises: in the first time duration, not listening to a response to the first report; after expiration of the first time duration, transmitting a second report, the second report being used for indicating measurement results of one or more beams, the second report being carried in UCI.

9. The method according to any one of claims 1 to 8, characterized in that, The method further comprises: in the first time duration, receiving third information, the third information being used for indicating that the first report is successfully received; based on the third information, stopping listening to the PDCCH.

10. The method according to any one of claims 1 to 9, characterized in that, The first time duration is pre-configured or indicated by signaling.

11. A measurement report transmission method, characterized by, Comprising: transmitting fourth information, the fourth information being used for indicating a first time duration; receiving a first report from a first communication device, the first report being used for indicating measurement results of one or more beams, the first report being carried in uplink control information (UCI), wherein the first time duration is started based on transmission of the UCI, and used for listening to a physical downlink control channel (PDCCH) corresponding to the first report.

12. A communications device, characterized by Comprising: a module for performing the method of any one of claims 1 to 10, or the method of claim 11.

13. A communications device, characterized by Comprising: a processor coupled to a memory, the memory being used for storing a computer program, when the processor invokes the computer program, causing the apparatus to perform the method of any one of claims 1 to 10, or the method of claim 11.

14. A computer-readable storage medium, characterized in that, A computer program product for storing a computer program comprising instructions for implementing the method according to any one of claims 1 to 10, or the method according to claim 11.

15. A computer program product, comprising instructions therein, wherein the computer program product is characterised in that, The instructions, when run on a computer, cause the computer to implement the method according to any one of claims 1 to 10, or the method according to claim 11.

Images