A communication method, apparatus and storage medium
Patent Information
- Application Number
- CN202510417091.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-02
- Publication Date
- 2026-10-16
AI Technical Summary
[0003]LTM事件型测量报告触发后,当UE端不存在可用的上行资源时,UE需要触发调度请求(scheduling request,SR)以获取用于发送测量报告的上行资源,SR过程涉及到SR重传或SR失败,而测量结果可能随时间发生变化,因此现有的方案测量报告可能出现准确性低的问题
Smart Images

Figure CN122934296A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus and storage medium. Background Technology
[0002] The 3rd Generation Partnership Project (3GPP) Release 19 standard proposes the reporting of Layer 1 / Layer 2 triggered mobility (LTM) event-based measurement reports (MRs). When user equipment (UE) detects a preset event (such as the quality of the serving cell falling below a certain threshold), it automatically triggers the reporting of Layer 1 / Layer 2 measurement data. Compared to traditional measurement reporting schemes, this can shorten terminal handover latency and interruption latency, thereby improving the user experience.
[0003] When an LTM event-based measurement report is triggered, if there are no available uplink resources at the UE, the UE needs to trigger a scheduling request (SR) to obtain uplink resources for sending the measurement report. The SR process involves SR retransmission or SR failure, and the measurement results may change over time. Therefore, the existing solution may have problems with low accuracy in measurement reports. Summary of the Invention
[0004] This application provides a communication method, apparatus, and storage medium that can improve the accuracy of LTM event-based measurement reports.
[0005] Firstly, a communication method is provided. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this approach. The following description uses a terminal device as an example.
[0006] The method includes: if no first uplink resource exists for carrying the first measurement report, sending a first scheduling request to request the first uplink resource, wherein the first measurement report includes a layer 1 / layer 2 triggered mobility (LTM) event measurement report (MR); if the reporting cancellation conditions are met, canceling the reporting of the first measurement report, wherein the reporting cancellation conditions include one or more of the following: sending at least one first scheduling request but failing to obtain the first uplink resource, and meeting the measurement event departure condition; sending the first scheduling request a preset number of times but failing to obtain the first uplink resource, and failing to obtain the first uplink resource based on the random access procedure.
[0007] Among them, LTM Event MR refers to the automatic triggering of the reporting of Layer 1 / Layer 2 measurement data when the terminal device detects a preset event (such as the quality of the serving cell being lower than a certain threshold) based on LTM technology.
[0008] It should be noted that the measurement event departure condition is pre-configured by the terminal device. For example, the terminal device configures the measurement event departure condition based on the radio resource control (RRC) reconfiguration message sent by the network device. The measurement event departure condition may include, for example, the quality of the serving cell being higher than a preset threshold. In this embodiment, the specific content of the measurement event departure condition is not limited. Those skilled in the art can make selections based on actual business scenarios and business needs.
[0009] It should be noted that the preset number of times is pre-configured by the terminal device. For example, the terminal device configures the preset number of times based on the radio resource control (RRC) reconfiguration message sent by the network device. In this embodiment, no specific value of the preset number of times is limited. Those skilled in the art can make the selection based on the actual business scenario and business requirements.
[0010] In this embodiment of the application, when the UE does not currently have a first uplink resource for reporting the first measurement report, it requests the first uplink resource from the network device through a first scheduling request (SR), and cancels the reporting of the first measurement report when the reporting cancellation condition is met. For example, when the terminal device sends at least one first scheduling request but fails to obtain the first uplink resource, and the measurement event departure condition is met, the terminal can cancel the reporting of the first measurement report; or, for example, when the terminal device sends the first scheduling request a preset number of times but fails to obtain the first uplink resource, and fails to obtain the first uplink resource based on the random access procedure, the terminal can also cancel the reporting of the first measurement report.
[0011] Based on the above scheme, this application provides a cancellation reporting mechanism in the LTM Event MR reporting scenario. When the terminal device sends at least one first scheduling request but fails to obtain the first uplink resource, and meets the measurement event departure condition (e.g., the quality of the serving cell is higher than a preset threshold), it indicates that there is currently no need for measurement reporting. The terminal device cancels the reporting of the first measurement report to avoid reporting inaccurate measurement reports, thereby improving the accuracy of LTM Event MR. When the terminal device sends the first scheduling request a preset number of times but fails to obtain the first uplink resource, and fails to obtain the first uplink resource based on the random access procedure, it indicates that the measurement report has not been reported for a relatively long period of time. At this time, the result of the measurement report may have changed. The terminal device cancels the reporting of the first measurement report to avoid reporting inaccurate measurement reports, thereby improving the accuracy of LTM Event MR.
[0012] In one possible implementation of the first aspect, the method further includes: if the number of times the first scheduling request is sent has not reached a preset number and the first uplink resource has not been obtained, and the measurement event reporting condition is met, then the first scheduling request is sent again.
[0013] The measurement event reporting conditions are pre-configured by the terminal device. For example, the terminal device configures the measurement event reporting conditions based on the Radio Resource Control (RRC) reconfiguration message sent by the network device. The measurement event reporting conditions may include, for example, the quality of the serving cell being lower than a preset threshold. In this embodiment, the specific content of the measurement event reporting conditions is not limited. Those skilled in the art can make selections based on actual business scenarios and business needs.
[0014] In this embodiment, if the terminal device sends the first scheduling request less than a preset number of times and fails to acquire the first uplink resource, but meets the measurement event reporting conditions, it indicates that there is still a need for measurement reporting. The terminal device can retransmit the first scheduling request to acquire the first uplink resource until the number of times the first scheduling request is sent reaches the preset number. Therefore, this application only retransmits the scheduling request when the measurement event reporting conditions are met, improving the accuracy of LTM Event MR. Furthermore, the preset retransmission threshold prevents the terminal device from getting stuck in a loop of retransmitting scheduling requests, reducing communication overhead.
[0015] In one possible implementation of the first aspect, the method further includes: if at least one first scheduling request is sent and a first uplink resource is obtained, reporting a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
[0016] In this embodiment of the application, when the terminal device obtains the first uplink resource based on the first scheduling request, the terminal device can directly report the second measurement report based on the first uplink resource. The second measurement report is of the same type as the first measurement report, except that the second measurement report is the latest measurement report at the time when the first uplink resource is obtained.
[0017] Understandably, since LTM Event MR reports based on preset events, it can achieve millisecond-level response times. The terminal device continuously acquires new measurement reports periodically when triggered by a preset event. Therefore, after acquiring the first uplink resource, the terminal device can report the latest measurement report. That is, the reported second measurement report includes the latest LTM event-type measurement result corresponding to the moment the first uplink resource was acquired, avoiding the reporting of inaccurate measurement reports and further improving the accuracy of LTM Event MR.
[0018] In one possible implementation of the first aspect, the method further includes: if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on a random access procedure, a second measurement report is reported based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
[0019] In this embodiment, when the terminal device sends a first scheduling request a preset number of times but fails to acquire the first uplink resource, and acquires the first uplink resource based on a random access procedure, the terminal device can report a second measurement report based on the first uplink resource. The second measurement report is the latest measurement report corresponding to the moment the first uplink resource is acquired based on the random access procedure. Therefore, after acquiring the first uplink resource based on the random access procedure, the terminal device can report the latest measurement report, avoiding the reporting of inaccurate measurement reports and further improving the accuracy of LTM Event MR.
[0020] In one possible implementation of the first aspect, the method further includes: receiving a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including measurement event reporting conditions and measurement event departure conditions.
[0021] In this embodiment of the application, the terminal device can receive a radio resource control (RRC) reconfiguration message sent by the network device to preconfigure the measurement event reporting conditions and the measurement event departure conditions.
[0022] Secondly, a communication device is provided, comprising a report processing module, a resource scheduling module, and a report sending module. The resource scheduling module is configured to send a first scheduling request for the first uplink resource if no first uplink resource for carrying the first measurement report exists. The first measurement report includes a Layer 1 / Layer 2 triggered mobility LTM event-type measurement report. The processing module is configured to cancel the reporting of the first measurement report if reporting cancellation conditions are met. The reporting cancellation conditions include one or more of the following: sending at least one first scheduling request but failing to obtain the first uplink resource, and meeting the measurement event departure condition; sending the first scheduling request a preset number of times but failing to obtain the first uplink resource, and failing to obtain the first uplink resource based on a random access procedure.
[0023] In one possible implementation of the second aspect, the resource scheduling module is further configured to send the first scheduling request again if the number of times the first scheduling request has been sent has not reached a preset number and the first uplink resource has not been obtained, and the measurement event reporting condition is met.
[0024] In one possible implementation of the second aspect, the apparatus further includes: a report sending module, configured to send at least one first scheduling request and obtain a first uplink resource, and report a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
[0025] In one possible implementation of the second aspect, the report sending module is further configured to, if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on a random access procedure, report a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time when the first uplink resource is obtained.
[0026] In one possible implementation of the second aspect, the apparatus further includes: a receiving module for receiving a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including measurement event reporting conditions and measurement event departure conditions.
[0027] The second aspect is the implementation on the device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.
[0028] Thirdly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.
[0029] In one implementation, the communication interface may be a transceiver, or an input / output interface.
[0030] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.
[0031] Fourthly, 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 a method in any possible implementation of any aspect.
[0032] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, 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, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.
[0033] Fifthly, a communication device is provided, including a processor and a memory. The processor is used 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 any of the above aspects.
[0034] Optionally, the processor may be one or more, and the memory may be one or more.
[0035] In a sixth 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 a method in any possible implementation of any of the above aspects.
[0036] In a seventh aspect, 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 any of the preceding aspects.
[0037] Eighthly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0038] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.
[0039] In a ninth aspect, a communication system is provided, including the aforementioned terminal device. Optionally, the communication system may further include other devices that communicate with the terminal device, such as network devices.
[0040] It is understood that the beneficial effects of the third to ninth aspects mentioned above can be found in the relevant descriptions of the first aspect and any implementation thereof, and will not be repeated here. Attached Figure Description
[0041] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application;
[0042] Figure 2 A flowchart illustrating a communication method provided in an embodiment of this application;
[0043] Figure 3 A flowchart illustrating another communication method provided in an embodiment of this application;
[0044] Figure 4 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0045] Figure 5 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation
[0046] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.
[0047] The technical solutions provided in this application can be applied to 5G communication systems, such as 5th generation (5G) mobile communication systems or new radio access technology (NR). The 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of such applications.
[0048] Figure 1 This is a schematic diagram of a communication system 100 used in an embodiment of this application. The communication system 100 may include network devices, such as... Figure 1 The network device 110 is shown. The communication system 100 may also include terminal devices, such as... Figure 1 The terminal device 120 is shown. The network device 110 and the terminal device 120 can communicate via a wireless link.
[0049] Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.
[0050] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called an access node. Access network equipment has wireless transceiver capabilities for communicating with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be a macro base station (such as...). Figure 1 110a), micro base stations or indoor stations (such as Figure 1 In the context of 110b), the access network device can be a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, wearable device, or vehicle-mounted device, etc. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations in different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network device. In this application, the access network device is referred to as a network device.
[0051] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.
[0052] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.
[0053] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.
[0054] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.
[0055] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices 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).
[0056] 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 an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.
[0057] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.
[0058] 1. Layer 1 / Layer 2 Triggered Mobility (LTM)
[0059] The mobility management technology introduced in the 3GPP R18 standard enables fast cell handover by directly utilizing Layer 1 (L1) and Layer 2 (L2) information, significantly reducing latency and signaling overhead.
[0060] For example, handover decisions can be triggered directly by L1 radio signal quality measurements, such as the reference signal received power (RSRP) or reference signal received quality (RSRQ) of the synchronization signal block (SSB), or by L2 scheduling information, without the involvement of the radio resource control (RRC) layer, which can significantly reduce latency and signaling overhead.
[0061] Layer 1 includes the physical layer (PHY), and Layer 2 includes the media access control (MAC) layer, the radio link control (RLC) layer, and the packet data convergence protocol (PDCP) layer.
[0062] 2. LTM Event Measurement Report (MR)
[0063] Based on LTM technology, when a terminal device detects a preset event (such as the quality of the serving cell falling below a certain threshold), it automatically triggers the reporting of Layer 1 / Layer 2 measurement data. Compared to the periodic measurements of traditional L3 (RRC layer), LTM event triggering can shorten the measurement cycle to the millisecond level, reducing handover latency.
[0064] For example, Layer 1 (physical layer) dynamically determines event conditions (such as a sudden drop in signal quality or the quality of a neighboring cell being better than that of the serving cell) based on real-time beam measurement results (such as RSRP / RSRQ) and directly triggers measurement reporting.
[0065] 3. Conditions for reporting measurement events
[0066] 3GPP defines a predefined measurement reporting mechanism called "Events". Event types include A1 to A6 and B1 to B2, where A-type events are used for intra-system handovers and B-type events are used for inter-system handovers. For example, event A2 indicates that the quality of the serving cell is below a certain threshold, triggering a measurement report.
[0067] 4. Measurement event exit conditions
[0068] Corresponding to the reporting conditions of measurement events, for example: Event A1 is used to stop measurement, which is triggered when the quality of the serving cell is higher than a preset threshold. For example: when the quality index of the serving cell returns to above the preset threshold, the relevant quality measurement report will stop being reported. For example: the departure condition of event A2 is that the quality of the serving cell is higher than the preset threshold, at which point the measurement report will stop being reported.
[0069] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.
[0070] After an LTM event-based measurement report is triggered, if the terminal device has available uplink resources, it directly uses those resources to send the measurement report to the network device. If no uplink resources are available, the terminal device triggers a scheduling request (SR) to acquire uplink resources for sending the measurement report. The SR process involves SR retransmission or SR failure. If uplink resources are not acquired for an extended period, the measurement report may change, or it may not even need to be sent. For example, the measurement results may change over time, or the signal measurement value of the serving cell may recover to above the threshold. In such cases, if the terminal device waits until it acquires uplink resources before sending the measurement report, inaccurate measurement reports may occur.
[0071] In view of this, this application provides a communication method for improving the accuracy of LTM event-based measurement reports.
[0072] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.
[0073] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.
[0074] Figure 2 This is a flowchart illustrating a communication method according to an embodiment of this application. It can be understood that... Figure 2 The terminal device in the middle can be Figure 1 Any terminal device in the context of network equipment can also refer to a component within that terminal device (such as a processor, chip, or chip system). Network equipment can be... Figure 1 Any access network device, or a component within an access network device (such as a processor, chip, or chip system). Figure 2 As shown, the method includes the following steps:
[0075] Step S201: The terminal device receives a Radio Resource Control (RRC) reconfiguration message sent by the network device. This RRC reconfiguration message is used by the terminal device to configure the measurement event reporting conditions and the measurement event departure conditions.
[0076] The explanations regarding the conditions for reporting and leaving measurement events can be found in the aforementioned terminology descriptions, and will not be repeated here.
[0077] The RRC reconfiguration message may also include a preset number of times. The terminal device can configure the preset number of times based on the RRC reconfiguration message. The preset number of times is used to indicate the maximum number of times the terminal device sends the first scheduling request.
[0078] It should be noted that step S201 is an optional step, indicated by a dashed line.
[0079] Step S202: The terminal device obtains a first measurement report, which includes an LTM event-type measurement report.
[0080] Specifically, when a terminal device responds to a preset event (such as the quality of the serving cell falling below a certain threshold), it automatically triggers the reporting of Layer 1 / Layer 2 measurement data. In this step, the terminal device obtaining the first measurement report can be understood as the terminal device triggering the measurement and receiving the first measurement report.
[0081] Step S203: If a first uplink resource exists, the terminal device reports a first measurement report based on the first uplink resource.
[0082] The first uplink resource can be used to carry the first measurement report. When the terminal device obtains the first measurement report and the terminal device has the first uplink resource, it directly sends the first measurement report to the network device through the first uplink resource.
[0083] The first uplink resource is the physical uplink shared channel (PUSCH) resource.
[0084] Step S204: If no first uplink resource exists, the terminal device sends a first scheduling request to the network device. The first scheduling request is used to request the first uplink resource.
[0085] When the terminal device obtains the first measurement report, but the terminal device does not have the first uplink resource to send the first measurement report, the terminal device requests the first uplink resource from the network device through a first scheduling request (SR).
[0086] It should be noted that steps S203 and S204 are condition-selective steps. That is, only step S203 needs to be executed when the first uplink resource exists, and only step S204 needs to be executed when the first uplink resource does not exist. The simultaneous presentation of steps S203 and S204 in the schematic diagram does not mean that both steps need to be executed in the embodiments of this application.
[0087] Step S205: If the reporting cancellation conditions are met, cancel the reporting of the first measurement report. The reporting cancellation conditions include one or more of the following: sending at least one first scheduling request but failing to obtain the first uplink resource, and meeting the measurement event departure conditions; sending the first scheduling request a preset number of times but failing to obtain the first uplink resource, and failing to obtain the first uplink resource based on the random access procedure.
[0088] Specifically, during the process of a terminal device requesting the first uplink resource from a network device via a first scheduling request, it may fail to obtain the first uplink resource. The terminal device can then resend the first scheduling request (i.e., retransmit the SR) to request the first uplink resource again. However, the terminal device may or may not obtain the first uplink resource. During the process of the terminal device requesting the first uplink resource, the results of the measurement report may no longer be applicable, or the measurement report may no longer be required under the current network conditions.
[0089] It should be noted that when the terminal device requests the first uplink resource but has not yet obtained it, the terminal device will continuously evaluate the measurement report, update the measurement report periodically, and determine the necessity of reporting the measurement report based on the measurement event departure conditions.
[0090] Therefore, in this embodiment, the terminal device cancels the reporting of the first measurement report when the reporting cancellation conditions are met, to ensure the accuracy of the reported measurement report. For example, if the terminal device sends at least one first scheduling request but fails to obtain the first uplink resource, and the measurement event departure condition is met, the terminal can cancel the reporting of the first measurement report; or, for example, if the terminal device sends the first scheduling request a preset number of times but fails to obtain the first uplink resource, and fails to obtain the first uplink resource based on the random access procedure, the terminal can also cancel the reporting of the first measurement report.
[0091] Therefore, this application provides a cancellation reporting mechanism in the LTM Event MR reporting scenario. When the terminal device sends at least one first scheduling request but fails to obtain the first uplink resource, and meets the measurement event departure condition (e.g., the quality of the serving cell is higher than a preset threshold), it indicates that there is currently no need for measurement reporting. The terminal device cancels the reporting of the first measurement report to avoid reporting inaccurate measurement reports, thereby improving the accuracy of LTM Event MR. When the terminal device sends the first scheduling request a preset number of times but fails to obtain the first uplink resource, and fails to obtain the first uplink resource based on the random access procedure, it indicates that the measurement report has not been reported for a relatively long period of time. At this time, the result of the measurement report may have changed. The terminal device cancels the reporting of the first measurement report to avoid reporting inaccurate measurement reports, thereby improving the accuracy of LTM Event MR.
[0092] In one optional implementation of the embodiments of this application, the communication method provided in the embodiments of this application further includes: if the number of times the first scheduling request is sent does not reach a preset number and the first uplink resource is not obtained, and the measurement event reporting conditions are met, the first scheduling request is sent again.
[0093] Specifically, if the terminal device sends the first scheduling request less than a preset number of times and fails to acquire the first uplink resource, but meets the measurement event reporting conditions, it indicates that there is still a need for measurement reporting. The terminal device can retransmit the first scheduling request to acquire the first uplink resource until the number of times the first scheduling request is sent reaches the preset number. Therefore, this application only retransmits the scheduling request when the measurement event reporting conditions are met, improving the accuracy of LTM Event MR. Furthermore, the preset retransmission threshold prevents the terminal device from getting stuck in a loop of retransmitting scheduling requests, reducing communication overhead.
[0094] In an optional implementation of the embodiments of this application, the communication method provided in the embodiments of this application further includes: if at least one first scheduling request is sent and a first uplink resource is obtained, a second measurement report is reported based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time when the first uplink resource is obtained.
[0095] Specifically, when the terminal device obtains the first uplink resource based on the first scheduling request, the terminal device can directly report the second measurement report based on the first uplink resource. The second measurement report is of the same type as the first measurement report, except that the second measurement report is the latest measurement report corresponding to the moment the first uplink resource is obtained.
[0096] Understandably, since LTM Event MR reports based on preset events, it can achieve millisecond-level response times. The terminal device continuously acquires new measurement reports periodically when triggered by a preset event. Therefore, when the terminal device acquires the first uplink resource, it can report the latest measurement report. That is, the reported second measurement report includes the latest LTM event-type measurement result corresponding to the moment the first uplink resource was acquired, avoiding the reporting of inaccurate measurement reports and further improving the accuracy of LTM Event MR.
[0097] In an optional implementation of the embodiments of this application, the communication method provided in the embodiments of this application further includes: if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on a random access procedure, a second measurement report is reported based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time when the first uplink resource is obtained.
[0098] Specifically, when the number of times the terminal device sends the first scheduling request reaches a preset number but fails to obtain the first uplink resource, and obtains the first uplink resource based on the random access procedure, the terminal device can report a second measurement report based on the first uplink resource. The second measurement report is the latest measurement report corresponding to the moment when the first uplink resource is obtained based on the random access procedure.
[0099] Therefore, after the terminal device obtains the first uplink resource based on the random access procedure, the terminal device can report the latest measurement report, avoiding the reporting of inaccurate measurement reports and further improving the accuracy of LTM Event MR.
[0100] Figure 3 This is a flowchart illustrating another communication method provided in an embodiment of this application. The flowchart is described below:
[0101] First, the terminal device triggers an LTM event-type MR report. The terminal determines whether it has obtained uplink scheduling (whether there are available uplink resources). If so, the terminal device directly reports the MR. If not, the terminal device will continuously evaluate the measurement results and make a judgment based on the departure conditions of the measurement event report. If the departure conditions of the measurement event report are met, the terminal device sets the MR reporting flag to FALSE. If the measurement event reporting conditions are met, the terminal device sets the MR reporting flag to TRUE. On the other hand, the terminal device will trigger the sending of a scheduling request (SR) based on the LTM event-type MR and increment the sending count by 1 after each SR is sent.
[0102] Then, if the terminal device obtains uplink scheduling, it directly reports the latest MR; if it does not obtain uplink scheduling, the terminal device makes a further judgment based on the MR reporting Flag. If the Flag is FALSE, the terminal device cancels the MR reporting and cancels the SR; if the Flag is TRUE, the terminal device retransmits the SR and increments the number of transmissions by 1.
[0103] Next, after the number of scheduling requests reaches the maximum threshold, the terminal device triggers a random access procedure based on the random access channel (RACH) to request uplink scheduling from the network device.
[0104] Finally, if the terminal device obtains uplink scheduling based on the random access procedure, the terminal device reports the latest MR; if the terminal device still does not obtain uplink scheduling, the terminal device cancels the reporting of MR and performs random access failure processing.
[0105] In summary, the embodiments of this application can flexibly report updated measurement results or cancel measurement reporting based on measurement evaluation results when the terminal cannot obtain uplink scheduling for a long period of time, thereby improving the accuracy of the final measurement reporting.
[0106] It should be understood that Figures 1 to 3 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 3 The examples in the document can be transformed into equivalent ways to obtain more implementations.
[0107] The above text combined Figures 1 to 3 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 4 to 5 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.
[0108] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0109] Figure 4 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 4 As shown, the communication device 400 may include a resource scheduling module 401 and a processing module 402. Wherein,
[0110] Resource scheduling module 401 is used to send a first scheduling request for the first uplink resource if there is no first uplink resource for carrying the first measurement report. The first measurement report includes a Layer 1 / Layer 2 triggered mobility LTM event type measurement report.
[0111] The processing module 402 is used to cancel the reporting of the first measurement report if the reporting cancellation conditions are met. The reporting cancellation conditions include one or more of the following: sending at least one first scheduling request but failing to obtain the first uplink resource, and meeting the measurement event departure condition; sending the first scheduling request a preset number of times but failing to obtain the first uplink resource, and failing to obtain the first uplink resource based on the random access procedure.
[0112] In one possible design, the communication device 400 may correspond to the terminal device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 400 can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.
[0113] For example, the resource scheduling module is also used to send the first scheduling request again if the number of times the first scheduling request is sent has not reached a preset number and the first uplink resource has not been obtained, but the measurement event reporting conditions are met.
[0114] For example, the communication device further includes a report sending module for sending a second measurement report based on the first uplink resource if at least one first scheduling request is sent and the first uplink resource is obtained. The measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
[0115] For example, the report sending module is further configured to, if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on a random access procedure, report a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
[0116] For example, the device further includes a receiving module for receiving a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including measurement event reporting conditions and measurement event departure conditions.
[0117] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.
[0118] Figure 5 This is another schematic block diagram of the communication device 500 provided in the embodiments of this application. The communication device 500 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The communication device 500 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.
[0119] like Figure 5 As shown, the communication device 500 may include one or more processors 510, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 510 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 500 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.
[0120] In an alternative design, the processor 510 may also store instructions and / or data that can be executed by the processor 510 to cause the communication device 500 to perform the methods described in the above method embodiments.
[0121] In another alternative design, the communication device 500 may include a communication interface 520 for implementing receiving and transmitting functions. For example, the communication interface 520 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.
[0122] Optionally, the communication device 500 may include one or more memories 530, which may store instructions that can be executed on the processor 510, causing the communication device 500 to perform the methods described in the above method embodiments. Optionally, the memories 530 may also store data. Optionally, the processor 510 may also store instructions and / or data. The processor 510 and the memories 530 may be provided separately or integrated together.
[0123] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in 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 reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.
[0124] In one implementation, the communication device 500 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 510 may be used to execute instructions stored in the memory 530, and when the processor 510 executes the instructions stored in the memory, the processor 510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.
[0125] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.
[0126] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0127] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0128] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.
[0129] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.
[0130] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.
[0131] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.
[0132] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.
[0133] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.
[0134] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.
[0135] 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 units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units 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 units may be electrical, mechanical, or other forms.
[0136] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0137] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A communication method, characterized in that, The method includes: If no first uplink resource exists to carry the first measurement report, a first scheduling request is sent to request the first uplink resource. The first measurement report includes a Layer 1 / Layer 2 triggered mobility LTM event-type measurement report. If the reporting cancellation conditions are met, the first measurement report will be cancelled. The reporting cancellation conditions include one or more of the following: Sending the first scheduling request at least once but failing to acquire the first uplink resource, and satisfying the measurement event departure condition; The first scheduling request has been sent a preset number of times but the first uplink resource has not been obtained, and the first uplink resource has not been obtained based on the random access procedure.
2. The method according to claim 1, characterized in that, The method further includes: if the number of times the first scheduling request is sent does not reach a preset number and the first uplink resource is not obtained, and the measurement event reporting conditions are met, then the first scheduling request is sent again.
3. The method according to claim 1 or 2, characterized in that, The method further includes: if the first scheduling request is sent at least once and the first uplink resource is obtained, reporting a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on the random access procedure, a second measurement report is reported based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time when the first uplink resource is obtained.
5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: receiving a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes measurement event reporting conditions and measurement event departure conditions.
6. A communication device, characterized in that, The device includes: The resource scheduling module is used to send a first scheduling request for the first uplink resource if there is no first uplink resource for carrying the first measurement report. The first measurement report includes a Layer 1 / Layer 2 triggered mobility LTM event-type measurement report. The processing module is configured to cancel the reporting of the first measurement report if the reporting cancellation conditions are met, wherein the reporting cancellation conditions include one or more of the following: sending the first scheduling request at least once but failing to obtain the first uplink resource, and meeting the measurement event departure condition; sending the first scheduling request a preset number of times but failing to obtain the first uplink resource, and failing to obtain the first uplink resource based on the random access procedure.
7. The apparatus according to claim 6, characterized in that, The resource scheduling module is further configured to send the first scheduling request again if the number of times the first scheduling request has been sent has not reached a preset number and the first uplink resource has not been obtained, and the measurement event reporting conditions are met.
8. The apparatus according to claim 6 or 7, characterized in that, The apparatus further includes a report sending module, configured to, if the first scheduling request is sent at least once and the first uplink resource is obtained, report a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
9. The apparatus according to any one of claims 6 to 8, characterized in that, The device further includes: a report sending module, configured to, if the number of times the first scheduling request is sent reaches a preset number but the first uplink resource is not obtained, and the first uplink resource is obtained based on a random access procedure, report a second measurement report based on the first uplink resource, wherein the measurement value of the second measurement report includes the latest LTM event-type measurement result at the time the first uplink resource is obtained.
10. The apparatus according to any one of claims 6 to 9, characterized in that, The device further includes a receiving module for receiving Radio Resource Control (RRC) reconfiguration messages, wherein the RRC reconfiguration messages include measurement event reporting conditions and measurement event departure conditions.
11. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, the processor executing the program or instructions to cause the device to perform the method as described in any one of claims 1 to 5.
12. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 5.
13. A computer program product comprising instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 5.
14. A communication system, characterized in that, Includes the communication device as described in any one of claims 6 to 11.
15. A chip system comprising one or more processors, the one or more processors being configured to retrieve and execute instructions stored in memory, such that the method of any one of claims 1 to 5 is performed.