Report transmission method and apparatus
By maintaining a periodic reporting timer and encapsulating multiple measurement report MAC CEs during the LTM process, the problem of redundant reporting during LTM is solved, and uplink transmission overhead is reduced.
Patent Information
- Application Number
- PCT/CN2025/093620
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
In the prior art, redundant L1 measurement reports in the LTM process lead to increased uplink transmission overhead, and the issue of how to send multiple measurement reports (MAC CE) is not discussed.
When an L1 measurement report is triggered and not canceled, the terminal device maintains the timer according to the reporting configuration identifier and encapsulates multiple measurement report MAC CEs into a MAC PDU for transmission.
This avoids multiple L1 beams triggering measurement reports in a short period of time, reducing uplink transmission overhead.
Smart Images

Figure CN2025093620_12112026_PF_FP_ABST
Abstract
Description
Report sending method and device Technical Field
[0001] The embodiments of this application relate to the field of communication technology. Background Technology
[0002] Network-controlled mobility applies to connected terminals and can be divided into two types: cell-level mobility and beam-level mobility.
[0003] Rel-18 introduced Layer 1 / Layer 2 Triggered Mobility (LTM), which offers improvements in handover latency and downtime compared to Layer 3-based mobility. However, LTM introduced in Rel-18 also has some limitations compared to Layer 3 mobility. The goal of the Rel-19 project is to eliminate these limitations.
[0004] LTM operation only supports mobility between cells within the same gNB (same CU). Depending on the network deployment scenario, this greatly limits the opportunities to use LTM. By ensuring LTM operation between cells of different gNBs (i.e., inter-CUs), the network can achieve the benefits of LTM with a much greater number of handovers.
[0005] Layer 3 mobility uses Layer 3 measurement reporting, which supports events assessed by the terminal device (UE) to trigger measurement reports, reducing signaling overhead compared to periodic measurement reporting. Layer 1 measurements used for LTM mobility do not support such triggering events.
[0006] Layer 1 measurements in the LTM process are limited to SSB measurements. Extending L1 measurements to include CSI-RS can overcome this limitation and promises to achieve greater throughput on the target cell immediately after cell handover.
[0007] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention
[0008] Currently, the network can configure connected-state (RRC_CONNECTED) terminal devices to perform L1 beam-level measurements for LTM candidate cells, including Layer 1 (L1) Reference Signal Received Power (RSPR) and / or Signal to Interference plus Noise Ratio (SINR). The network can configure terminal devices to report based on event-triggered Layer 1 measurement configurations. When an event-triggered L1 condition is met, this measurement report is used to indicate the L1 measurement results of the serving cell and / or candidate cells to the serving gNB, and the measurement configuration is provided via RRC-specific signaling.
[0009] For LTM candidate cells with candidate IDs configured in the reporting configuration list ltm-CandidateReportConfigList, connected terminal devices obtain L1 beam-level measurement results by measuring one or more beams configured in the network. The Media Access Control (MAC) entity performs an evaluation of the reporting criteria based on the L1 measurement results from the lower layer.
[0010] For serving cells that have configured the LTM event evaluation process, periodic measurement result reporting is also supported. When each reporting configuration identifier ltm-CSI-ReportConfigId of the serving cell included in the reporting configuration LTM-CSI-ReportConfig is configured for periodic reporting, when the periodic reporting timer of ltm-CSI-ReportConfigId expires, the MAC entity initiates the measurement reporting process to transmit L1 measurement results from the UE to the network.
[0011] Whenever the measurement of a beam in a reporting configuration ID meets the corresponding event condition TTT, an L1 measurement report is triggered. That is, L1 measurement reports are triggered per beam. If the reporting configuration ID is configured for periodic reporting, it means that when the periodic reporting timer expires, an L1 measurement report will be triggered again. The inventors discovered that when multiple beams in a reporting configuration ID trigger L1 measurement reports consecutively at the same time, if the reporting configuration ID is configured for periodic reporting, it means that multiple L1 measurement reports will be sent within a short period of time, and these multiple L1 measurement reports will carry the same or similar beams and measurement results, resulting in redundant reporting.
[0012] Additionally, an existing measurement report MAC CE includes a beam-triggered measurement report that reports a configuration ID. The inventors have discovered that multiple measurement report MAC CEs may be triggered before UL resources arrive. How to send one or more triggered / generated measurement report MAC CEs has not yet been discussed.
[0013] To address at least one of the above-mentioned problems or other similar problems, embodiments of this application provide a report sending method and apparatus.
[0014] According to one aspect of the embodiments of this application, a report sending apparatus is provided, configured in a terminal device, wherein the apparatus includes:
[0015] The processor, when an L1 measurement report is triggered and not canceled, maintains the periodic reporting timer according to the reporting configuration identifier, or according to the candidate cell in the reporting configuration identifier, or according to the beam or reference signal in the reporting configuration identifier.
[0016] According to another aspect of the embodiments of this application, a report sending apparatus is provided, configured in a terminal device, wherein the apparatus includes:
[0017] The processor encapsulates one or N measurement report MAC CEs from multiple measurement report MAC control units into a MAC protocol data unit (MAC PDU), where N is an integer greater than 1;
[0018] A transmitter that sends the MAC PDU to a network device.
[0019] One of the beneficial effects of this application embodiment is that the terminal device maintains a periodic reporting timer according to the reporting configuration identifier, or the candidate cell in the reporting configuration identifier, or the beam or reference signal in the reporting configuration identifier. As a result, it is possible to avoid the sending of multiple L1 beam-triggered measurement reports in a short period of time, thus avoiding redundant reporting.
[0020] One of the beneficial effects of the embodiments of this application is that the terminal device encapsulates one or more measurement reports (MAC CEs) into a MAC PDU, thereby reducing uplink transmission overhead.
[0021] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.
[0022] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.
[0023] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description
[0024] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.
[0025] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;
[0026] Figure 2 is a schematic diagram of inter-cell mobility scenarios under the same gNB(-CU);
[0027] Figure 3 is a schematic diagram of the LTM cell change process;
[0028] Figure 4 is a schematic diagram of contention-free random access (CFRA) for early uplink synchronization;
[0029] Figure 5 is a schematic diagram of the measurement model;
[0030] Figure 6 is a schematic diagram of the relevant parameters measured in Layer 1;
[0031] Figure 7 is a schematic diagram of multiple L1 measurement reports carrying repeated measurement results;
[0032] Figure 8 is a schematic diagram of a report sending method according to an embodiment of this application;
[0033] Figure 9 is a schematic diagram of a report sending method according to an embodiment of this application;
[0034] Figure 10 is a schematic diagram of the L1 measurement report triggering process;
[0035] Figure 11 is a schematic diagram of a beam management method according to an embodiment of this application;
[0036] Figure 12 is a schematic diagram of the beam management method implemented in this application;
[0037] Figure 13 is a schematic diagram of a report sending device in an embodiment of this application;
[0038] Figure 14 is a schematic diagram of a report sending device in an embodiment of this application;
[0039] Figure 15 is a schematic diagram of a beam management device in an embodiment of this application;
[0040] Figure 16 is a schematic diagram of a beam management device in an embodiment of this application;
[0041] Figure 17 is a schematic diagram of a report receiving method according to an embodiment of this application;
[0042] Figure 18 is a schematic diagram of a report receiving device according to an embodiment of this application;
[0043] Figure 19 is a schematic diagram of a terminal device according to an embodiment of this application;
[0044] Figure 20 is a schematic diagram of a network device according to an embodiment of this application;
[0045] Figure 21 is a schematic diagram of the CLTM cell change process. Detailed Implementation
[0046] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.
[0047] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.
[0048] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.
[0049] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0050] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other currently known or future communication protocols.
[0051] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: integrated access and backhaul node (IAB-node), base station (BS), access point (AP), transmission and reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
[0052] The term "base station" can include, but is not limited to, NodeBs (or NBs), evolved NodeBs (or eNodeBs or eNBs), and 5G base stations (gNBs), etc. It can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (such as femeto, pico, etc.). The term "base station" can encompass some or all of its functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.
[0053] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.
[0054] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.
[0055] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.
[0056] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above.
[0057] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.
[0058] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.
[0059] Furthermore, sending or receiving a PUSCH can be understood as sending or receiving uplink data carried by the PUSCH; sending or receiving a PUCCH can be understood as sending or receiving uplink information carried by the PUCCH; and sending or receiving a PRACH can be understood as sending or receiving a preamble carried by the PRACH. Uplink signals can include uplink data signals and / or uplink control signals, and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending an uplink transmission on uplink resources can be understood as using those uplink resources to send the uplink transmission. Similarly, downlink data / signals / channels / information can be understood accordingly.
[0060] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.
[0061] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.
[0062] Layer 3 mobility has undergone several releases. Conditional handover (CHO) and other conditional mobility procedures (CPAC, SCPAC) have been defined to achieve high robustness by ensuring that the procedure is performed without prior signaling interaction with the source cell. LTM, introduced in Rel-18, provides short downtime, but its robustness is inferior to conditional Layer 3 mobility procedures. In Rel-19, enhancements should be defined so that the system can benefit from high robustness and short downtime. The goals of the Rel-19 work project include the following.
[0063] (1) Define support for inter-CU layer 2 mobility (LTM). For example, it may include the following.
[0064] Prioritize the case where CU acts as MN when DC is not configured;
[0065] As a secondary priority, it supports the case where NR-DC and CU are configured as SN and MN remains unchanged;
[0066] As a secondary priority, it supports the case where NR-DC and CU are configured as MN and SCG remains unchanged or is released (excluding the case where both MCG and SCG are configured with LTM).
[0067] According to Rel-18 LTM, support for subsequent LTM mobility procedures is defined, with the goal of avoiding RRC configuration between cell handovers;
[0068] In terms of secure key processing, SA3 is scheduled for negotiation (the Rel-18 intra-CU LTM process is considered the baseline for adding inter-CU support).
[0069] (2) Measurement-related enhancements to support LTM. These may include, for example, the following.
[0070] Measurement-related enhancements are applicable to both intra-CU MCG / SCG LTM and inter-CU MCG / SCG LTM;
[0071] Define the necessary components to support event-triggered L1 measurement reporting;
[0072] Define CSI-RS measurements to support the LTM process and ensure necessary physical layer operations on CSI-RS-based beam management and / or other LTM pre-candidate cells.
[0073] (3) Define the supporting conditional LTM. For example, it may include the following.
[0074] Define the conditions for triggering LTM in UE evaluation;
[0075] The goal is to support conditional LTM, including subsequent LTM.
[0076] Prioritize intra-CU LTM;
[0077] RAN#105 is the checkpoint for the review target. No RAN WG work will begin before this checkpoint.
[0078] (4) Define the RRM requirements related to the above objectives if necessary.
[0079] Figure 1 is a schematic diagram of the communication system of this application, illustrating the case with terminal devices and network devices as examples. As shown in Figure 1, the communication system 100 may include network devices 101 and 103 and terminal device 102 (for simplicity, Figure 1 only uses one terminal device as an example for illustration).
[0080] In this embodiment, terminal device 102 can communicate sequentially with either network device 101 or 103. Taking communication between terminal device 102 and network device 101 as an example, existing services or future services can be performed between network device 101 and terminal device 102. These services include, but are not limited to, enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.
[0081] In this configuration, terminal device 102 can send data to network device 101, for example, using authorized (e.g., configured grant) or unauthorized transmission methods. In authorized mode, network device 101 can receive data sent by one or more terminal devices 102 within the authorized range and provide feedback to terminal device 102, such as ACK / NACK confirmation messages, or indicate a new grant to terminal device 102. Based on the feedback information or the new grant, terminal device 102 can either confirm the end of the transmission process, initiate new data transmission, or retransmit data. In unauthorized transmission mode, terminal device 102 can transmit new data within the configured grant range or retransmit data.
[0082] Figure 2 illustrates a schematic diagram of inter-cell mobility scenarios under the same gNB-CU. As shown in Figure 2, when a terminal moves from the coverage area of one cell to the coverage area of another cell, a serving cell change needs to be performed at a certain point. Referring to Figure 2, a gNB-CU can be connected to multiple gNB-DUs. These multiple gNB-DUs can include the gNB-DU currently providing service to the terminal device (Serving DU) and a backup gNB-DU. The backup gNB-DU can include Candidate DU1 and Candidate DU2. At location A, the Serving DU can provide service; at location B, the Serving DU and Candidate DU1 can provide service; at location C, the Serving DU can provide service; and at location D, Candidate DU1 can provide service.
[0083] When the terminal device is at location A, its primary cell (PCell) is cell 1. When the mobile terminal moves from location A to location B, the serving cell changes. When the terminal device is at location B, its primary cell is cell 2, and its secondary cell (SCell) is cell 1. When the mobile terminal moves from location B to location C, the serving cell changes again. When the terminal device is at location C, its primary cell is cell 1. When the mobile terminal moves from location B to location D, the serving cell changes again. When the terminal device is at location D, its primary cell is cell 3, and its secondary cell is cell 4.
[0084] Currently, serving cell changes can be triggered by L3 measurements and completed via RRC signaling, including reconfiguration with synchronization triggered by changes in the primary cell (PCell) and primary / secondary cell (PSCell), and the release of applicable secondary cells (SCells). Cell-level mobility is triggered by explicit RRC signaling, i.e., handover. RRC-triggered handover mechanisms require the UE to at least reset the MAC entity and rebuild Radio Link Control (RLC). RRC-managed handovers with and without PDCP entity rebuilding are supported. For DRBs using RLC AM mode, PDCP can be rebuilt with a security key update or a data recovery process can be initiated without a key update. For DRBs using RLC UM mode, PDCP can be rebuilt with a security key update or remain unchanged without a key update. For SRBs, PDCP can remain unchanged without a key update, discard stored PDCP PDUs / SDUs, or be rebuilt with a security key update.
[0085] For RRC-triggered handover mechanisms, all cases involve a complete L2 (and L1) reset, resulting in longer latency, greater overhead, and longer downtime compared to beam-switching mobility. The goal of Layer L1 / L2 mobility enhancement is to ensure that serving cell changes are handled via L1 / L2 signaling to reduce latency, overhead, and downtime.
[0086] LTM is a process in which the gNB receives an L1 or L3 measurement report from the UE, and based on this, the gNB changes the UE's serving cell via a cell change command sent through the MAC CE. The MAC-triggered cell switch mechanism (i.e., LTM cell handover) requires the UE to at least reset the MAC entity. RLC and PDCP processing depend on the network configuration.
[0087] The LTM cell change process is shown in Figure 3. Subsequent LTM is achieved by repeating the early synchronization, LTM cell handover execution, and LTM cell handover completion steps, without releasing, reconfiguring, or adding other LTM candidate configurations after each LTM cell handover. The basic process on the air interface applies to Primary Cell Group (MCG) LTM or Secondary Cell Group (SCG) LTM. As shown in Figure 3, the LTM process includes the following steps:
[0088] 1. A UE in RRC_CONNECTED state sends a MeasurementReport message to the source gNB. The gNB then decides to configure LTM and initiates LTM candidate cell configuration.
[0089] 2. The source gNB determines the LTM configuration;
[0090] 3. The source gNB requests LTM configuration for one or more candidate cells belonging to itself, and / or one or more candidate gNBs. For cross-gNB LTM scenarios, the source gNB initiates a handover request message containing the candidate cell ID for each candidate cell. Whether in intra-gNB or cross-gNB LTM scenarios, the source gNB can request Channel Status Information (CSI) resource configuration from candidate cells or candidate gNBs.
[0091] 4. Candidate cells or gNBs implement access control;
[0092] 5. The candidate cell prepares its LTM configuration and provides it to the source gNB. For LTM across gNBs, the candidate gNB replies to the source gNB (carrying a handover request confirmation message), which includes the Radio Resource Control (RRC) configuration generated for the accepted candidate cell. For LTMs within and across gNBs, the candidate cell may also include additional information related to CSI configuration and early synchronization information;
[0093] 6. The source gNB sends an LTM configuration update message to the candidate gNB to update the LTM configuration of the candidate cell. The source gNB may include common channel state information resource configuration;
[0094] 7. The candidate gNB sends an LTM configuration update confirmation message to the source gNB. The candidate gNB can also provide channel state information reporting configuration;
[0095] 8. The source gNB sends an RRC reconfiguration message to the user equipment;
[0096] 9. The user equipment stores the LTM candidate configuration and sends an RRC reconfiguration complete message to the source gNB;
[0097] 9a. If early data forwarding is applied, the source gNB sends an early state transition message to the candidate gNB;
[0098] 10 / 11. Early downlink and uplink synchronization can be performed on some LTM candidate cells. The source gNB can activate or deactivate the Transmission Configuration Indicator (TCI) state of the candidate LTM cell. Depending on the network configuration, if a UE-based Time Advance (TA) measurement is configured, the UE can use this measurement to perform early uplink (UL) synchronization with the LTM candidate cell and / or send a preamble to the candidate cell at the trigger of the source gNB. In the case of network-triggered uplink synchronization, the UE receives a Physical Downlink Control Channel (PDCCH) command from the source cell to trigger Contention-Free Random Access (CFRA) to the candidate cell, and acquires the early timing advance by sending a preamble to the designated candidate cell. To minimize data interruption in the source cell due to contention-free random access to the designated candidate cell, the UE does not receive a random access response from the network to acquire the timing advance value. Instead, the candidate gNB sends a timing advance information transfer message to the source gNB;
[0099] 12. The user equipment performs Layer 1 (L1) measurements on the configured LTM candidate cells and, if configured, sends an L1 measurement report to the source gNB. L1 measurements should be performed whenever Radio Resource Control reconfiguration (step 8) is applicable.
[0100] 13. The source gNB decides to initiate LTM. L3 measurements can also be used to assist in making this decision.
[0101] 14. The source gNB decides to perform a cell handover to the target cell and sends an LTM cell handover command MAC CE to trigger the handover. This command includes a target configuration ID indicating the index of the candidate configuration; a beam indicating the transmission configuration status, or a beam indicating the downlink and uplink transmission configuration status; and a timing advance command for the target cell. If the security context changes, the LTM cell handover command MAC CE will also include a New Cell Counter (NCC) value. The user equipment switches to the target cell and applies the candidate configuration indicated by the target configuration ID. In the event of a change in the security context, the user equipment generates and applies a new security key based on the received New Cell Counter value.
[0102] 15. The source gNB sends a cell handover notification message to the target gNB to indicate that it has initiated a cell handover command to the user equipment.
[0103] 16. If the user equipment does not have the effective timing advance for the target cell as specified in Clause 5.18.35 of TS 38.321, the UE shall perform a random access procedure for the target cell.
[0104] 17 / 18. The target gNB sends a handover success message to the source gNB, informing the source gNB that the user equipment has successfully accessed the target cell. In response, the source gNB sends a serial number (SN) state transition message according to the principles described in step 7 of section 9.2.3.2.1 of TS 38.300 for in-cell / user plane function (UPF) handover.
[0105] 19. The User Equipment (UE) completes the LTM cell handover process by sending a Radio Resource Control (RRC) reconfiguration completion message to the target cell. If the UE performed a random access procedure in step 16, the UE considers the LTM cell handover to have been successfully performed when the random access procedure is successfully completed. For LTM without a random access channel, the UE considers the LTM cell handover to have been successfully performed when it determines that the network has successfully received its first uplink data.
[0106] 20. The new source gNB (i.e., the target gNB) sends an LTM configuration update message to the candidate gNB;
[0107] 21. The candidate gNB replies with an LTM configuration update confirmation message to the new source gNB;
[0108] 22. If no LTM candidate cell exists in the old source gNB, the new source gNB may send a UE context release message, notifying the old source gNB to release radio and control plane resources associated with the UE context. Any ongoing data forwarding can continue.
[0109] For random access procedures on LTM candidate cells used for early uplink timing advance (UL TA) acquisition, contention-free random access (CFRA) is triggered by the physical downlink control channel order (PDCCH). As shown in Figure 4, the UE sends MSG1 to the cell and does not listen for responses from the cell. To support UE power ramp-up, the UE can retransmit MSG1 as instructed by the network.
[0110] Figure 21 is a schematic diagram of the CLTM cell change process. As shown in Figure 21, the CLTM process includes the following steps:
[0111] 1. The user equipment sends a measurement report message to the gNB. The gNB decides to configure CLTM and initiates CLTM preparation.
[0112] 2. The source gNB can request candidate cells to provide conditional execution configurations. The candidate cells provide conditional configurations that include their own execution conditions for subsequent CLTM use.
[0113] 3. The source gNB sends an RRC reconfiguration message to the UE, which contains the CLTM configuration of the candidate cell and the execution conditions of CLTM;
[0114] 4. The UE stores the CLTM candidate configuration and sends an RRC reconfiguration complete message to the gNB. The UE then begins to evaluate the execution conditions based on the provided configuration.
[0115] 5 / 6. The source gNB can (e.g., based on L1 or L3 measurement reports from the UE, if configured) trigger the UE to perform early synchronization, and step 10 / 11 in clause 9.2.3.5 of TS 38.300 also applies here. Furthermore, the source gNB can provide a timing advance value for each candidate cell for which the UE has performed uplink synchronization.
[0116] 7. If the CLTM execution conditions are met at the UE, and on a candidate LTM cell that meets the conditions, the UE performs a CLTM handover by applying the configuration of the candidate LTM cell that meets the conditions. If the UE has a valid timing advance value in the uplink early synchronization in step 6, the UE will skip the random access procedure. Otherwise, the random access procedure will be performed as part of the CLTM cell handover.
[0117] 8. The UE completes the CLTM cell handover process by sending a Radio Resource Control reconfiguration complete message to the LTM cell that has been handed over. The UE does not release any valid timing advance value of the LTM candidate cell with CLTM configuration.
[0118] Regarding Layer 3 measurements and reporting:
[0119] In Radio Resource Control (RRC_CONNECTED) connected mode, the UE measures multiple beams or at least one beam of a cell and averages the measurements (power values) of these beams to obtain cell quality. During this process, the UE is configured to consider a subset of the detected beams. Beam filtering is performed at the RRC level to obtain L3 measurements at both the beam and cell levels, where the cell-level L3 measurement is a collection of multiple beam-level L3 measurements. Cell quality is obtained from beam measurements in the same manner for both serving and non-serving cells.
[0120] The measurement report may include the measurement results of the X best beams, if the UE has been configured to do so by the gNB.
[0121] The corresponding measurement model is shown in Figure 5. In Figure 5, the K beams correspond to the measurements of SSB or CSI-RS resources detected by the UE in L1 when the gNB is configured for L3 mobility. The following is a description of each part in Figure 5.
[0122] A: Measurements within the physical layer (beam-specific samples).
[0123] Layer 1 filtering: Internal layer 1 filtering of the inputs measured at point A; the accuracy of the filtering depends on the implementation.
[0124] A 1 After layer 1 filtering, the measurements reported by layer 1 to layer 3 (i.e., beam-specific measurements).
[0125] Beam Consolidation / Selection: Combines beam-specific measurements to obtain cell quality. The behavior of beam consolidation or selection is standardized, and the configuration of this module is provided by RRC signaling. The reporting period at B is equal to that at A. 1 Measurement period (one measurement period at A) 1 ).
[0126] B: A measurement (i.e., cell quality) obtained from beam-specific measurements reported to layer 3 after beam consolidation or beam selection.
[0127] Layer 3 filtering for cell quality: Filtering is performed on the measurements provided at point B. The behavior of the layer 3 filters is normalized, and the configuration of the layer 3 filters is provided by RRC signaling. The filtering reporting period at C is equal to one measurement period at B.
[0128] C: Measurement after processing in the layer 3 filter. The reporting rate is identical to the reporting rate at point B. This measurement after layer 3 filter processing is used as input to one or more evaluations of reporting criteria.
[0129] Evaluation of reporting criteria: This involves examining whether an actual measurement report at point D is necessary. This evaluation can be based on more than one flow of measurements at reference point C, for example, comparing different measurements. For instance, inputting measurements at C and C... 1 This is illustrated by input C and C 1 The UE utilizes C,C at least each time. 1 A new measurement result is reported at point C,C. 1 Evaluate the reporting criteria. Standardize the behavior of the reporting criteria and provide this configuration via RRC signaling.
[0130] D: Send measurement report information or measurement report messages on the wireless interface.
[0131] Layer 3 beam filtering: for A 1 Filtering was performed on the measurements provided at point A. 1 Filtering the measured values involves performing specific measurements on the beam, standardizing the behavior of the beam filters, and providing the beam filters via RRC signaling. The filtering reporting period at E is equal to A. 1 Measurement period (one measurement period at A) 1 ).
[0132] E: Measurement after beam filtering, such as beam-specific measurement. Reporting rate and A 1 The reporting rate is identical to the reporting rate at point A. 1 The measurement after beam filtering is used as input to select the X measurements to be reported.
[0133] Beam selection for beam reporting: Select the X measurements from the measurements provided at point E. This beam selection behavior is standardized, and the configuration of this module is provided by RRC signaling.
[0134] F: Beam measurement information is included in the measurement report (transmitted) on the wireless interface.
[0135] Measurement reports have the following characteristics:
[0136] The measurement report includes the measurement identity associated with the measurement configuration that triggered the report;
[0137] Cell and beam measurements included in the measurement report are configured by the network;
[0138] The number of non-serving cells that can be reported can be limited through network configuration;
[0139] Cells that are in the network's exclusion list are not used for event assessment and reporting. Conversely, when the network is configured with an allow list, only cells that are in the allow list are used for event assessment and reporting.
[0140] The beam measurements to be included in the measurement report are configured by the network, which may include: only the beam identifier, or the measurement result and the beam identifier, or no beam reporting.
[0141] Layer 1 Measurement and Reporting:
[0142] For event-triggered Layer 1 measurement reporting, the following LTM events based on beam-specific quality of the serving cell and candidate cells are supported as L1 LTM measurement events:
[0143] Event LTM2: The serving cell's beam becomes worse than the absolute threshold;
[0144] Event LTM3: The candidate cell's beam becomes one offset better than the serving cell's beam;
[0145] Event LTM4: The beam of the candidate cell becomes better than the absolute threshold;
[0146] Event LTM5: The serving cell’s beam becomes worse than absolute threshold 1 and the candidate cell’s beam becomes better than absolute threshold 2.
[0147] For Layer 1 measurement and reporting, as shown in Figure 6, the network device configuration parameters include: RS configuration and reporting configuration.
[0148] The RS configuration includes: IE LTM-CSI-ResourceConfig (included in LTM-Config) defines a set of resources for one or more LTM candidate configurations, which includes one or more CSIs (wherein, IE LTM-CSI-ResourceConfig (included in LTM-Config) defines one or more CSI resources for one or more LTM candidate configurations).
[0149] The reported configuration includes:
[0150] IE LTM-CSI-ReportConfig is used to configure reports on cells that contain LTM CSI ReportConfig;
[0151] The details are shown in Table 1 below:
[0152] Table 1
[0153] For event-triggered L1 measurement and reporting processes, the terminal device / MAC entity needs to maintain the following variables:
[0154] Measurement Report List (MR_LIST): Includes L1 measurement report information triggered by the event, where the triggering condition for the L1 measurement report has been met by the time-to-trigger (TTT).
[0155] Measurement Sent Counter (MR_SENT_COUNTER): If the triggering condition of the event corresponding to each ltm-CSI-ReportConfigId meets TTT (time to trigger), it represents the number of L1 measurement reports triggered by the event executed by the terminal device; it supports scenarios where L1 measurement reports are triggered periodically.
[0156] Beam Trigger List (BEAM_TRIGGERED_LIST): Includes reference signal resource indications / indexes for each LTM candidate cell with reporting configuration identifier ltm-CSI-ReportConfigId, where the L1 measurement report triggering condition has been met by TTT.
[0157] The current standard for triggering measurement reports includes: for serving cells configured with an LTM event assessment process, the MAC entity initiates a measurement reporting process when the event entry / exit conditions are met. For each ltm-CSI-ReportConfigId of the serving cell included in LTM-CSI-ReportConfig, the MAC entity initiates a measurement reporting process when the periodic reporting timer of that ltm-CSI-ReportConfigId times out.
[0158] The details are shown in Table 2 below:
[0159] Table 2
[0160] In addition, RRC controls the L1 beam-level measurement reporting triggered by this event by configuring at least the following parameters:
[0161] reportInterval: The reporting cycle for event-triggered periodic measurement reports;
[0162] reportAmount: The number of measurement reports to be transmitted after the event is triggered;
[0163] The measurement reporting process is as follows: If an L1 measurement report is triggered and not canceled, a (truncated) L1 measurement report MAC CE is generated or a scheduling request (SR) is triggered based on uplink (UL) resources. Once a (truncated) L1 measurement report MAC CE is generated or sent, the measurement report sending counter is incremented by 1. If the maximum number of transmissions is not reached, a periodic reporting timer is started. When the periodic reporting timer expires, an L1 measurement report is triggered. See Table 3 for details:
[0164] Table 3
[0165] Figure 7 is a schematic diagram of multiple L1 measurement reports carrying duplicate measurement results. As shown in Figure 7, when an L1 measurement report (MAC CE) is generated or sent (truncated), the MR transmission counter increments by 1. If the MR transmission counter has not reached the maximum number of transmissions, a periodic reporting timer is started. When the periodic reporting timer expires, an L1 measurement report is triggered. Taking Figure 7 as an example, if beam 1 and beam 2 trigger L1 measurement reports consecutively and periodic reporting is configured, then after time period t, the L1 measurement reports triggered by beam 1 and beam 2 will be sent within a short period of time, resulting in redundant reporting. To address this problem, the embodiments of this application will be described below with reference to the accompanying drawings and specific implementation methods. In the following description, "if…", "in the case of…", and "when…" can be used interchangeably without causing confusion. "Report" can be replaced with "report".
[0166] First aspect of the embodiments
[0167] This application provides a report sending method, which is applied to a terminal device. Figure 8 is a schematic diagram of the report sending method according to an embodiment of this application. As shown in Figure 8, the method includes:
[0168] 801. When the L1 measurement report is triggered and not canceled, the terminal device maintains the cycle reporting timer according to the reporting configuration identifier, or according to the candidate cell in the reporting configuration identifier, or according to the beam or reference signal in the reporting configuration identifier.
[0169] In some embodiments, the method by which 801 determines that the L1 measurement report is triggered can be referred to Table 2 above, and will not be repeated here.
[0170] In some embodiments, in step 801, when an L1 measurement report is triggered and not canceled, a timer is reported according to the reporting configuration identifier, or according to the candidate cell within the reporting configuration identifier, or according to the beam or reference signal maintenance cycle within the reporting configuration identifier. The maintenance actions include starting, not starting, stopping, restarting, etc. The following explains how to maintain the periodic reporting timer.
[0171] In some embodiments, the terminal device can maintain the periodic reporting timer according to the reporting configuration identifier or the candidate cells within the reporting configuration identifier. This avoids the transmission of L1 measurement reports triggered by multiple beams of a reporting configuration identifier or a candidate cell within a reporting configuration identifier within a short period, thereby preventing redundant reporting.
[0172] In some examples, if the periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is not running, a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is started.
[0173] In some examples, if a periodic reporting timer corresponding to a reporting configuration identifier is already running, the periodic reporting timer corresponding to that reporting configuration identifier will not be started.
[0174] In some examples, if the periodic reporting timer for a candidate cell within a reporting configuration identifier is already running, the periodic reporting timer for that candidate cell within the reporting configuration identifier will not be started.
[0175] In other words, when an L1 measurement report is triggered and not canceled, and the value of the measurement report sending counter (MR_SENT_COUNTER) corresponding to a reporting configuration identifier has not reached the maximum number of transmissions (reportAmount), if the periodic reporting timer corresponding to the reporting configuration identifier is not running, then a periodic reporting timer corresponding to that reporting configuration identifier will be started; or, if the periodic reporting timer corresponding to a candidate cell within the reporting configuration identifier is not running, then the periodic reporting timer corresponding to that candidate cell within the reporting configuration identifier will be started. If the periodic reporting timer corresponding to the reporting configuration identifier is running, then a periodic reporting timer corresponding to that reporting configuration identifier will not be started; or, if the periodic reporting timer corresponding to a candidate cell within the reporting configuration identifier is running, then the periodic reporting timer corresponding to that candidate cell within the reporting configuration identifier will not be started.
[0176] Therefore, the periodic reporting timer is maintained for each reporting configuration identifier or each candidate cell within a reporting configuration identifier. In other words, beams or reference signals of reporting configuration identifiers or candidate cells within them share the same periodic reporting timer. For the same reporting configuration identifier or the same candidate cell within a reporting configuration identifier, if a beam or reference signal triggers an L1 measurement report, the corresponding periodic reporting timer is started only if the periodic reporting timer of the same candidate cell or reporting configuration identifier belonging to that beam has not yet run. If the periodic reporting timer of the same candidate cell or reporting configuration identifier belonging to that beam is running, the corresponding periodic reporting timer is not started. Therefore, when determining whether to start a periodic reporting timer, it is also necessary to consider whether the periodic reporting timer corresponding to the same reporting configuration identifier or candidate cell within a reporting configuration identifier is running. This avoids the situation where multiple L1 measurement reports triggered by a reporting configuration identifier or a candidate cell within a reporting configuration identifier are sent in a short period of time, thus avoiding redundant reporting.
[0177] For example, at time t1, beam 1 of candidate cell 1 within the reporting configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated. If there is no corresponding periodic reporting timer T1 running for this reporting configuration identifier, the periodic reporting timer corresponding to this reporting configuration identifier is started. At time t2, beam 2 of candidate cell 1 within the reporting configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated. If the corresponding periodic reporting timer started for this reporting configuration identifier at time t1 is running, another periodic reporting timer T2 corresponding to this reporting configuration identifier will not be started.
[0178] In some examples, if a periodic reporting timer corresponding to a reporting configuration identifier is running, the periodic reporting timer corresponding to the reporting configuration identifier is stopped.
[0179] In some examples, if the periodic reporting timer for a candidate cell within a reporting configuration identifier is running, the periodic reporting timer for that candidate cell within the reporting configuration identifier is stopped.
[0180] In this example, if the UL-SCH resources are available for new transmission and can accommodate an L1 Measurement Report MAC CE plus its header as a result of logical channel priority, the multiplexing and encapsulation process is instructed to generate the L1 Measurement Report MAC CE. When the multiplexing and encapsulation process is instructed to generate an L1 Measurement Report MAC CE, a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within the reporting configuration identifier is started.
[0181] In other words, when an L1 measurement report is triggered and not canceled, and the value of the measurement report transmission counter (MR_SENT_COUNTER) corresponding to a reporting configuration identifier has not reached the maximum transmission count (reportAmount), if the periodic reporting timer corresponding to the reporting configuration identifier is running, then the periodic reporting timer corresponding to that reporting configuration identifier is stopped first; or, if the periodic reporting timer corresponding to a candidate cell within the reporting configuration identifier is running, then the periodic reporting timer corresponding to that candidate cell within the reporting configuration identifier is stopped first. After stopping the periodic reporting timer, if the multiplexing and encapsulation process generates an L1 measurement report MAC CE, then the periodic reporting timer corresponding to the reporting configuration identifier or the candidate cell within the reporting configuration identifier is restarted.
[0182] In some examples, if a periodic reporting timer corresponding to a reporting configuration identifier is already running, the periodic reporting timer corresponding to the reporting configuration identifier is restarted.
[0183] In some examples, if the periodic reporting timer for a candidate cell within the reporting configuration identifier is running, the periodic reporting timer for that candidate cell within the reporting configuration identifier is restarted.
[0184] Therefore, the periodic reporting timer is maintained for each reporting configuration identifier or each candidate cell within a reporting configuration identifier. In other words, beams or reference signals of reporting configuration identifiers or candidate cells within them share the same periodic reporting timer. For the same reporting configuration identifier or the same candidate cell within a reporting configuration identifier, if a beam or reference signal triggers an L1 measurement report, and if the periodic reporting timer for that beam belongs to the same candidate cell or reporting configuration identifier is running, the corresponding periodic reporting timer is stopped or restarted, and the previously started periodic reporting timer becomes invalid. This avoids the situation where multiple L1 measurement reports triggered by a reporting configuration identifier or a candidate cell within a reporting configuration identifier are sent in a short period of time, thus preventing redundant reporting.
[0185] In the above embodiments, to further avoid redundancy, a measurement report transmission counter can be maintained according to the reported configuration identifier or according to the candidate cells within the reported configuration identifier. For example, beam 1 of candidate cell 1 within the reported configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated, and the measurement report transmission counter corresponding to the reported configuration identifier maintained according to the reported configuration identifier is incremented by 1. Then, beam 2 of candidate cell 1 within the reported configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated, and the measurement report transmission counter corresponding to the reported configuration identifier maintained according to the reported configuration identifier is not incremented by 1. For example, beam 1 of candidate cell 1 within the reported configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated, and the measurement report transmission counter corresponding to candidate cell 1 within the reported configuration identifier maintained according to the candidate cells within the reported configuration identifier is incremented by 1. Subsequently, beam 2 of candidate cell 2 within the reporting configuration identifier triggers an L1 measurement report. If the L1 measurement report is triggered and not canceled, a corresponding measurement report MAC CE is generated, and the measurement report transmission counter corresponding to candidate cell 2 within the reporting configuration identifier, maintained by the candidate cells within the reporting configuration identifier, is incremented by 1. Examples are not provided here.
[0186] Alternatively, you can maintain the measurement report transmission counter according to the beam or reference signal in the reported configuration identifier (see Tables 2 and 3 for details).
[0187] For example, if the UL-SCH resource is available for new transmission and the UL-SCH resource is capable of accommodating a (truncated) L1 measurement report MAC CE plus its header as a result of logical channel priority, the instruction multiplexing and encapsulation process generates a (truncated) L1 measurement report MAC CE. Upon generating the (truncated) L1 measurement report MAC CE, the measurement report transmission counter is incremented by 1.
[0188] For example, if UL-SCH resources are available for new transmission and can accommodate a truncated L1 measurement report MAC CE plus its header as a result of logical channel priority, the multiplexing and encapsulation process is instructed to generate a truncated L1 measurement report MAC CE. When a truncated L1 measurement report MAC CE is generated, the measurement report transmission counter is not incremented by 1. Similarly, if UL-SCH resources are available for new transmission and can accommodate an L1 measurement report MAC CE plus its header as a result of logical channel priority, the multiplexing and encapsulation process is instructed to generate an L1 measurement report MAC CE. When an L1 measurement report MAC CE is generated, the measurement report transmission counter is incremented by 1. Since a truncated measurement report MAC CE cannot cover all measurement information, not incrementing the measurement report transmission counter when a truncated L1 measurement report MAC CE is generated allows for more opportunities to send longer measurement report MAC CEs, potentially increasing the measurement report transmission interval and further reducing the possibility of redundancy.
[0189] In some embodiments, the terminal device can maintain the timer according to the beam or reference signal in the reporting configuration identifier and the maintenance cycle (the specific maintenance method can be found in Tables 2 and 3).
[0190] In some examples, a first timer disable mechanism can be introduced to reduce redundancy. Based on the first timer, it is determined whether to generate a (truncated) L1 measurement report MAC CE.
[0191] In the example above, the first timer is started when a (truncated) L1 measurement report MAC CE is generated or sent.
[0192] While the first timer is running, no (truncated) L1 measurement report MAC CE is generated, nor is SR triggered.
[0193] If the first timer is not running, a (truncated) L1 measurement report MAC CE is generated according to the UL resource; that is, if an L1 measurement report is triggered and not canceled when the first timer is not running, a (truncated) L1 measurement report MAC CE is generated according to the UL resource (if the UL-SCH resource is available for new transmission and the UL-SCH resource can accommodate the L1 measurement report MAC CE plus its header as a result of logical channel priority, an L1 measurement report MAC CE is generated; if the UL-SCH resource is available for new transmission and the UL-SCH resource can accommodate the truncated L1 measurement report MAC CE plus its header as a result of logical channel priority, a truncated L1 measurement report MAC CE is generated); or, according to the UL resource, if the first timer is not running, a (truncated) L1 measurement report MAC CE is generated, or a scheduling request SR is triggered; that is, if an L1 measurement report is triggered and not canceled, according to the UL resource, if the first timer is not running, a (truncated) L1 measurement report MAC CE is generated, or an SR is triggered.
[0194] In other words, not all conditions in Table 3 will generate a (truncated) L1 measurement report MAC CE. By adding a first timer as a condition for whether to generate a (truncated) L1 measurement report MAC CE, even if the conditions in Table 3 are met when the first timer is running, a (truncated) L1 measurement report MAC CE will not be generated, and the SR will not be triggered. This avoids the transmission of multiple L1 beam-triggered measurement reports in a short period, preventing redundant reporting.
[0195] In some examples, a disable mechanism for the first timer can be introduced to reduce redundancy. Based on the first timer, it is determined whether to trigger the L1 measurement report.
[0196] In this example, the first timer is started when an L1 measurement report is triggered, or when an L1 measurement report is triggered due to the fulfillment of an event entry or exit condition reaching TTT, or when the periodic reporting timer times out.
[0197] The L1 measurement report is not triggered while the first timer is running. The L1 measurement report is triggered when the event entry or exit condition is met (TTT), or when the periodic reporting timer times out, even when the first timer is not running.
[0198] In other words, existing methods for triggering L1 measurement reports include two scenarios: one is when an event entry or exit condition is met, and the time for meeting the event condition reaches TTT (Time To Day), in which case an L1 measurement report is triggered; the other is when the periodic reporting timer expires, in which case an L1 measurement report is triggered. In this application, a first timer is added as a condition for triggering an L1 measurement report. When the first timer is running, an L1 measurement report is not triggered even if the aforementioned two scenarios are met. This avoids the transmission of multiple L1 beam-triggered measurement reports in a short period, preventing redundant reporting.
[0199] In the example above, the first timer can be a disabled timer, which can be configured by the network device. The first timer not running includes: the first timer not being configured, and / or, the first timer not being started, and / or, the first timer timing out.
[0200] In some examples, the terminal device sends one of the generated multiple measurement reports or (truncated) L1 measurement report MAC CEs, meaning one of the generated multiple (truncated) L1 measurement report MAC CEs is included in a single MAC PDU. These multiple measurement reports are generated within time T, thereby avoiding the transmission of multiple L1 beam-triggered measurement reports in a short period and preventing redundant reporting. In other words, of the multiple measurement reports generated within T, the terminal device only sends one of the measurement report MAC CEs.
[0201] In the example above, the L1 measurement report MAC CE included in the MAC PDU is one of the following among the generated (truncated) L1 measurement reports MAC CE:
[0202] The L1 measurement report with the largest number of beams included is MAC CE;
[0203] The L1 measurement report MAC CE, which includes the largest number of beams that meet the event entry conditions;
[0204] The L1 measurement report MAC CE includes the largest number of beams that meet the event entry or exit conditions.
[0205] The L1 measurement report MAC CE with the fewest number of beams that do not meet the event entry / exit conditions;
[0206] L1 measurement report MAC CE with the fewest number of beams including beam type changes;
[0207] The first / last generated L1 measurement report MAC CE.
[0208] It should be noted that in the above embodiments, the (truncated) L1 measurement report MAC CE refers to one of the following: truncated L1 measurement report MAC CE, L1 measurement report MAC CE, L1 measurement report MAC CE, and truncated L1 measurement report MAC CE.
[0209] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.
[0210] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0211] Through the above embodiments, the terminal device maintains the periodic reporting timer according to the reporting configuration identifier, or the candidate cell in the reporting configuration identifier, or the beam or reference signal in the reporting configuration identifier. As a result, it can avoid the sending of multiple L1 beam-triggered measurement reports in a short period of time, thus avoiding redundant reporting.
[0212] Second aspect of the embodiments
[0213] A current measurement report MAC CE includes a beam-triggered measurement report with a reporting configuration ID. The inventors have discovered that multiple measurement report MAC CEs may be triggered before UL resources arrive, and how to send one or more triggered measurement report MAC CEs has not yet been discussed. To address this issue, embodiments of this application provide a report sending method applied to a terminal device.
[0214] Figure 9 is a schematic diagram of a report sending method according to an embodiment of this application. As shown in Figure 9, the method includes:
[0215] 901, the terminal device encapsulates one or N measurement report MAC CEs from multiple measurement report MAC control units into a MAC protocol data unit (MAC PDU), where N is an integer greater than 1; 902, the terminal device sends the MAC PDU to the network device.
[0216] In some embodiments, prior to the arrival of UL resources, one or more beams reporting configuration IDs satisfy one or more LTM events, triggering multiple Measurement Report MAC CEs. These multiple Measurement Report MAC CEs include: event-triggered MR MAC CEs; event-triggered periodic MR MAC CEs; event-triggered truncated MR MAC CEs; event-triggered periodic truncated MR MAC CEs; MR MAC CEs with the same or different reporting configuration IDs; and MR MAC CEs triggered by the same or different LTM events.
[0217] In some embodiments, the MAC PDU may include only one of a plurality of measurement report MAC CEs. This measurement report MAC CE may be the first generated measurement report MAC CE, the latest generated measurement report MAC CE, the largest measurement report MAC CE that the MAC PDU can include or that UL resources can accommodate, or a measurement report MAC CE determined based on the terminal device implementation. Alternatively, the measurement report MAC CE may also be determined based on information configured by the network device.
[0218] The network device configuration information includes priority, and / or, the reporting configuration ID corresponding to the MAC CE, such as the minimum reporting ID or one or more indicated reporting IDs, and / or, the triggering LTM event identifier corresponding to the MAC CE, i.e., one or more LTM event identifiers among LTM2 / LTM3 / LTM4 / LTM5, and / or, the candidate identifier corresponding to the MAC CE, and / or, the resource indication corresponding to the MAC CE. The terminal device can select one measurement report MAC CE from multiple measurement report MAC CEs based on one or more of the above information. For example, multiple measurement report MAC CEs may include a measurement report MAC CE1 that satisfies event LTM2 and a measurement report MAC CE2 that satisfies event LTM3. When the network configuration information is to trigger LTM event LTM2, the MAC PDU includes measurement report MAC CE1. For example, multiple measurement report MAC CEs may include a measurement report MAC CE1 that satisfies event LTM2 for reference signal 1, a measurement report MAC CE2 that satisfies event LTM2 for reference signal 2, and a measurement report MAC CE3 that satisfies event LTM3 for reference signal 3. When the network configuration information is to trigger LTM event LTM2 and reference signal 2, the MAC PDU includes measurement report MAC CE2. Examples of these are not provided here.
[0219] In some cases, the MAC PDU may include N measurement report MAC CEs from multiple measurement report MAC CEs; that is, N measurement report MAC CEs can be multiplexed within a single MAC PDU. These N measurement report MAC CEs can be pre-generated N MAC CEs, newly generated N MAC CEs, the largest N MAC CEs, N MAC CEs determined based on the terminal device implementation, or N measurement report MAC CEs determined based on network device configuration information.
[0220] The network device configuration information may include priority, and / or, the reporting configuration ID corresponding to the MAC CE, such as the minimum reporting ID or one or more reporting IDs indicated, and / or, the triggering LTM event identifier corresponding to the MAC CE, i.e., one or more LTM event identifiers among LTM2 / LTM3 / LTM4 / LTM5, and / or, the candidate identifier corresponding to the MAC CE, and / or, the resource indication corresponding to the MAC CE, and / or, the information indicating N. In other words, the terminal device can determine the N measurement reports MAC CEs contained in the MAC PDU based on one or more of the above information. For example, multiple measurement report MAC CEs may include a measurement report MAC CE1 triggered by reference signal 1 satisfying event LTM2, a measurement report MAC CE2 triggered by reference signal 2 satisfying event LTM2, and a measurement report MAC CE3 triggered by reference signal 3 satisfying event LTM3. The network device configuration information includes an indication N value of 2, indicating that when the LTM event LTM2 is triggered, the MAC PDU includes measurement reports MAC CE1 and MAC CE2. Examples are not provided here.
[0221] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.
[0222] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0223] Through the above embodiments, multiple measurement report MAC CEs can be encapsulated into a single MAC PDU, thereby reducing uplink transmission overhead.
[0224] Third aspect of the embodiments
[0225] Figure 10 is a schematic diagram of the L1 measurement report triggering process. Referring to Table 2, as shown in Figure 10, steps 1001-1007 represent the measurement report triggering process when the event entry condition is met. Specifically, during the L1 measurement report triggering process, as shown in step 1003, when the event entry condition is met, the beam information is included in the BEAM_TRIGGERED_LIST (include the SSBRI or CRI of the concerned beam(s) in the BEAM_TRIGGERED_LIST for this ltm-CSI-ReportConfigId). At this time, the MR_LIST does not include or has no beam information. Steps 1008-1013 represent the measurement report triggering process when the time departure condition is met. Specifically, when the event departure condition is met, as shown in step 1009, the beam is removed from the MR_LIST (remove the concerned beam(s) in the MR_LIST for this ltm-CSI-ReportConfigId). The code snippet describes a process where, as shown in steps 1012-1013, when the BEAM_TRIGGERED_LIST is empty, the measurement reporting entry within the MR_LIST is removed. However, the inventors have discovered that currently only the behavior of including beam information in the BEAM_TRIGGERED_LIST is defined; the action of removing beam information from the BEAM_TRIGGERED_LIST is not defined. In other words, the BEAM_TRIGGERED_LIST will not be empty, and therefore, the removal of measurement reporting entries from the MR_LIST cannot be triggered. Furthermore, the action of adding beam information to the MR_LIST is not defined. Therefore, it is unclear how to remove the beam from the MR_LIST when the event departure condition is met.
[0226] To address at least one of the aforementioned problems or other similar problems, a beam management method is provided, applied to a terminal device. Figure 11 is a schematic diagram of a beam management method according to an embodiment of this application. As shown in Figure 11, the beam management method 1100 includes:
[0227] 1101. When the first beam meets the departure condition of the LTM event associated with the reporting configuration, the terminal device removes the information of the first beam from the beam trigger list (BEAM_TRIGGERED_LIST) corresponding to the reporting configuration.
[0228] Therefore, when the first beam meets the event entry condition, its information is included in BEAM_TRIGGERED_LIST. When the first beam meets the event exit condition, its information is removed from BEAM_TRIGGERED_LIST, instead of being removed from MR_LIST. That is, step 1009, "remove the concerned beam(s) in the MR_LIST for this ltm-CSI-ReportConfigId," as shown in Figure 10, is replaced with "remove the concerned beam(s) in the BEAM_TRIGGERED_LIST for this ltm-CSI-ReportConfigId." This eliminates the possibility of BEAM_TRIGGERED_LIST being empty, thus resolving the aforementioned technical problem.
[0229] This application also provides a beam management method applied to a terminal device. Figure 12 is a schematic diagram of a beam management method implemented in this application. As shown in Figure 12, the beam management method 1200 includes:
[0230] 1201. When the first beam meets the entry conditions of the LTM event associated with the reporting configuration, the terminal device includes the information of the first beam in the beam trigger list (BEAM_TRIGGERED_LIST) and the measurement report list (MR_LIST) corresponding to the reporting configuration.
[0231] In some embodiments, if the first beam satisfies the departure condition of the LTM event associated with the reporting configuration, a measurement reporting entry is removed from the measurement report list if a measurement reporting entry in the measurement report list does not contain / does not contain any information about any beam.
[0232] Therefore, when the first beam meets the event entry condition, its information must be included not only in the BEAM_TRIGGERED_LIST but also in the measurement report list (MR_LIST). That is, replace step 1003 in Figure 10, "BEAM_TRIGGERED_LIST includes the SSBRI or CRI of the concerned beam(s) in the BEAM_TRIGGERED_LIST for this ltm-CSI-ReportConfigId," with "BEAM_TRIGGERED_LIST and MR_LIST include the information of beam(s) in the BEAM_TRIGGERED_LIST and MR_LIST for this ltm-CSI-ReportConfigId." Thus, when the event exit condition is met, beam information can be removed from the MR_LIST. This occurs when a measurement report entry in the MR_LIST does not contain any beam information when the first beam meets the event exit condition. Only then is the reported entry removed from MR_LIST. This avoids using an empty BEAM_TRIGGERED_LIST as a condition for removing reported entries.
[0233] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.
[0234] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0235] The above three embodiments can be implemented individually or in combination, and the embodiments of this application are not intended to limit them.
[0236] Fourth aspect of the embodiment
[0237] This application provides a report sending apparatus configured with a terminal device. This report sending apparatus corresponds to the method of the first aspect embodiment.
[0238] Figure 13 is a schematic diagram of a report sending device in an embodiment of this application. As shown in Figure 13, the report sending device 1300 may include:
[0239] The processor 1301 maintains the periodic reporting timer according to the reporting configuration identifier, or the candidate cell in the reporting configuration identifier, or the beam or reference signal in the reporting configuration identifier when the L1 measurement report is triggered and not canceled.
[0240] In some embodiments, the maintenance cycle reporting timer includes the following based on the reported configuration identifier, or based on the candidate cells within the reported configuration identifier:
[0241] If the periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is not running, start the periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier.
[0242] In some embodiments, the maintenance cycle reporting timer includes the following based on the reported configuration identifier and the candidate cells within the reported configuration identifier:
[0243] If a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is running, the reporting configuration identifier or the periodic reporting timer corresponding to a candidate cell within a reporting configuration identifier shall not be started, stopped, or restarted.
[0244] In some embodiments, when the multiplexing and encapsulation process generates an L1 measurement report MAC CE, a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within the reporting configuration identifier is started.
[0245] In some embodiments, when UL-SCH resources are available for new transmission and the UL-SCH resources are capable of accommodating an L1 Measurement Report MAC CE plus its header as a result of logical channel priority, the multiplexing and encapsulation process is instructed to generate the L1 Measurement Report MAC CE, and a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within the reporting configuration identifier is started.
[0246] In some embodiments, the processor 1301 also maintains a measurement report transmission counter according to a reporting configuration identifier, or according to a candidate cell within the reporting configuration identifier, or according to a beam or reference signal within the reporting configuration identifier. The measurement report transmission counter is used for counting L1 measurement reports triggered by events.
[0247] In some embodiments, maintaining a measurement report sending counter includes:
[0248] In the case of generating a (truncated) L1 measurement report MAC CE, the measurement report transmission counter is incremented by 1; or
[0249] In the case of generating a truncated L1 measurement report MAC CE, the measurement report transmission counter does not increment by 1; or
[0250] When an L1 measurement report MAC CE is generated, the measurement report sending counter is incremented by 1.
[0251] In some embodiments, the maintenance cycle reporting timer further includes, according to the beam or reference signal in the reporting configuration identifier:
[0252] Based on the first timer, determine whether to generate a (truncated) L1 measurement report MAC CE; or
[0253] Based on the first timer, determine whether to trigger the L1 measurement report.
[0254] In some embodiments, determining whether to generate a (truncated) L1 measurement report MAC CE based on a first timer includes:
[0255] If the first timer does not run, generate a (truncated) L1 measurement report MAC CE based on UL resources; or
[0256] According to UL resources, if the first timer does not run, generate a (truncated) L1 measurement report MAC CE, or trigger a scheduling request SR; or
[0257] While the first timer is running, no (truncated) L1 measurement report MAC CE is generated, nor is SR triggered.
[0258] In some embodiments, determining whether to generate a (truncated) L1 measurement report MAC CE based on a first timer includes:
[0259] In the event of generating or sending a (truncated) L1 measurement report MAC CE, start the first timer.
[0260] In some embodiments, determining whether to trigger an L1 measurement report based on a first timer includes:
[0261] The L1 measurement report is triggered when the event entry or exit conditions are met for a timeout (TTT), or when the periodic reporting timer times out and the first timer has not run; or,
[0262] The L1 measurement report is not triggered while the first timer is running.
[0263] In some embodiments, determining whether to trigger an L1 measurement report based on a first timer includes:
[0264] The L1 measurement report is triggered either by meeting the event entry or exit conditions (TTT) or by the periodic reporting timer timeout, and the first timer is started.
[0265] In some embodiments, the first timer not running includes at least one of the following:
[0266] The first timer was not configured;
[0267] The first timer was not started;
[0268] The first timer timed out.
[0269] In some embodiments, the maintenance cycle reporting timer further includes, according to the beam or reference signal in the reporting configuration identifier:
[0270] One of the generated (truncated) L1 measurement reports in the MAC CE is included in a single MAC PDU.
[0271] In some embodiments, multiple (truncated) L1 measurement reports MAC CE are generated within time T.
[0272] In some embodiments, the L1 measurement report MAC CE included in the MAC PDU is one of the following generated (truncated) L1 measurement reports MAC CE:
[0273] The L1 measurement report with the largest number of beams included is MAC CE;
[0274] The L1 measurement report MAC CE, which includes the largest number of beams that meet the event entry conditions;
[0275] The L1 measurement report MAC CE includes the largest number of beams that meet the event entry or exit conditions.
[0276] The L1 measurement report MAC CE with the fewest number of beams that do not meet the event entry / exit conditions;
[0277] L1 measurement report MAC CE with the fewest number of beams including beam type changes;
[0278] The first / last generated L1 measurement report MAC CE.
[0279] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The report sending device 1300 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0280] Furthermore, for simplicity, Figure 13 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0281] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0282] Fifth aspect of the embodiment
[0283] This application provides a report sending device configured on a terminal device. This report sending device corresponds to the method of the second aspect embodiment.
[0284] Figure 14 is a schematic diagram of a report sending device in an embodiment of this application. As shown in Figure 14, the report sending device 1400 may include:
[0285] Processor 1401 encapsulates one or N measurement report MAC CEs from multiple measurement report MAC control units into a MAC protocol data unit (MAC PDU), where N is an integer greater than 1;
[0286] Transmitter 1402 sends the MAC PDU to the network device.
[0287] In some embodiments, a MAC PDU includes a measurement report MAC CE. A measurement report MAC CE is the earliest generated MAC CE, the latest generated MAC CE, the largest MAC CE, a MAC CE determined based on the terminal device implementation, or a MAC CE determined based on network device configuration information, or...
[0288] A MAC PDU includes N measurement report MAC CEs. These N measurement report MAC CEs can be the N MAC CEs generated earlier, the N MAC CEs that are newly generated, the N largest MAC CEs, the N MAC CEs determined based on the terminal device implementation, or the N MAC CEs determined based on the network device configuration information.
[0289] In some embodiments, the network device configuration information includes the priority of the MAC CE, and / or the reporting configuration identifier corresponding to the MAC CE, and / or the triggering LTM event identifier corresponding to the MAC CE, and / or the candidate identifier corresponding to the MAC CE, and / or the resource indication corresponding to the MAC CE, and / or information for indicating N.
[0290] In some embodiments, the measurement report MAC CE (MR MAC CE) includes at least one of the following:
[0291] Event-triggered MR MAC CE;
[0292] The event triggering cycle is MR MAC CE;
[0293] Event-triggered truncated MR MAC CE;
[0294] The truncated MR MAC CE of the event triggering period;
[0295] MR MAC CE with the same or different reporting configuration identifiers;
[0296] The implementation of the processor 1401 and the transmitter 1402 can be referred to the embodiments in the second aspect, and will not be repeated here.
[0297] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The report sending device 1400 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0298] Furthermore, for simplicity, Figure 14 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0299] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0300] Implementation of the sixth aspect
[0301] This application provides a beam management device configured on a terminal device. This report sending device corresponds to the method of the third aspect embodiment.
[0302] Figure 15 is a schematic diagram of a beam management device in an embodiment of this application. As shown in Figure 15, the beam management device 1500 may include:
[0303] The processor 1501 removes the information of the first beam from the beam trigger list (BEAM_TRIGGERED_LIST) corresponding to the reporting configuration when the first beam satisfies the departure condition of the LTM event associated with the reporting configuration.
[0304] Figure 16 is a schematic diagram of a beam management device in an embodiment of this application. As shown in Figure 16, the beam management device 1600 may include:
[0305] The processor 1601 includes information about the first beam in the beam trigger list (BEAM_TRIGGERED_LIST) and the measurement report list (MR_LIST) corresponding to the reporting configuration when the first beam meets the entry conditions of the LTM event associated with the reporting configuration.
[0306] In some embodiments, if the first beam satisfies the departure condition of the LTM event associated with the reporting configuration, a measurement reporting entry is removed from the measurement reporting list if a measurement reporting entry in the measurement reporting list does not contain information about any beam.
[0307] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The beam management devices 1500 and 1600 in the embodiments of this application may also include other components or modules. For details regarding these components or modules, please refer to related technologies.
[0308] Furthermore, for simplicity, Figures 15 and 16 only illustrate the connection relationships or signal flows between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0309] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0310] Seventh aspect of the embodiment
[0311] This application provides a report receiving method applied to network devices.
[0312] Figure 17 is a schematic diagram of a report receiving method according to an embodiment of this application. As shown in Figure 17, the method includes:
[0313] 1701, the network device receives a MAC PDU sent by the terminal device, the MAC PDU including one or N measurement reports MAC CE, wherein N is an integer greater than 1.
[0314] In some embodiments, the network device sends information to the terminal device for identifying the one or N MAC CEs, or sends information for indicating N.
[0315] In some embodiments, the information used to determine the one or N MAC CEs includes:
[0316] The priority of the MAC CE, and / or the reporting configuration identifier corresponding to the MAC CE, and / or the triggering LTM event identifier corresponding to the MAC CE, and / or the candidate identifier corresponding to the MAC CE, and / or the resource indicator corresponding to the MAC CE.
[0317] For details on the implementation of 1701, please refer to the embodiments in the second aspect, which will not be repeated here.
[0318] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.
[0319] This application also provides a report receiving device. This report receiving device can be configured in a network device and corresponds to the method of the seventh aspect embodiment. Figure 18 is a schematic diagram of a report receiving device according to an embodiment of this application. As shown in Figure 18, the report receiving device 1800 may include:
[0320] Receiver 1801 receives a MAC PDU sent by a terminal device, the MAC PDU including one or N measurement reports MAC CE, wherein N is an integer greater than 1.
[0321] In some embodiments, the report receiving device 1800 further includes a transmitter 1802, which sends information to the terminal device for determining the one or N MAC CEs, or sends information for indicating N.
[0322] In some embodiments, the information used to determine one or N MAC CEs includes:
[0323] The priority of the MAC CE, and / or the reporting configuration identifier corresponding to the MAC CE, and / or the triggering LTM event identifier corresponding to the MAC CE, and / or the candidate identifier corresponding to the MAC CE, and / or the resource indicator corresponding to the MAC CE.
[0324] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The report receiving device 1800 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0325] Furthermore, for simplicity, Figure 18 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.
[0326] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.
[0327] Eighth aspect of the embodiment
[0328] This application provides a communication system that may include network devices and terminal devices.
[0329] Referring to Figure 1, the terminal device includes the report sending device of the fourth and fifth aspect embodiments and the beam management device of the sixth aspect embodiment, and the network device includes the report receiving device of the seventh aspect embodiment. The contents that are the same as those in the embodiments of the first to seventh aspects will not be described again.
[0330] This application also provides a terminal device.
[0331] Figure 19 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 19, the terminal device 1900 may include a processor 1910 and a memory 1920; the memory 1920 stores data and programs and is coupled to the processor 1910. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.
[0332] For example, processor 1910 can be configured to execute programs to implement the methods described in the embodiments of the first, second, and third aspects.
[0333] As shown in Figure 19, the terminal device 1900 may further include: a communication module 1930, an input unit 1940, a display 1950, and a power supply 1960. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1900 does not necessarily include all the components shown in Figure 19; these components are not essential. Furthermore, the terminal device 1900 may also include components not shown in Figure 19, which can be referred to in the prior art.
[0334] This application also provides a network device.
[0335] Figure 20 is a schematic diagram of the network device configuration according to an embodiment of this application. As shown in Figure 20, the network device 2000 may include: a processor 2001 (e.g., a central processing unit CPU) and a memory 2002; the memory 2002 is coupled to the processor 2001. The memory 2002 can store various types of data; in addition, it also stores an information processing program 2003, and executes the program 2003 under the control of the processor 2001.
[0336] For example, processor 2001 may be configured to execute a program to implement the method described in the embodiment of the seventh aspect.
[0337] In addition, as shown in Figure 20, device 2000 may also include a communication module 2004, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that device 2000 does not necessarily include all the components shown in Figure 20; furthermore, device 2000 may also include components not shown in Figure 20, which can be referred to in the prior art.
[0338] It is worth noting that the device does not necessarily include all the components shown in the figure; the aforementioned components are not required. In addition, the device may also include components not shown in the figure, which can be referred to in the prior art.
[0339] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the methods in the first, second, and third aspect embodiments.
[0340] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the methods in the first, second, and third aspects of the embodiments.
[0341] This application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the method described in the seventh aspect embodiment.
[0342] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the method described in the seventh aspect embodiment.
[0343] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.
[0344] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.
[0345] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.
[0346] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
[0347] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.
[0348] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:
[0349] 1. A report receiving device configured in a network device, wherein the device comprises:
[0350] A receiver that receives a MAC PDU sent by a terminal device, the MAC PDU including one or N measurement reports MAC CE, wherein N is an integer greater than 1.
[0351] 2. The apparatus according to Appendix 1, wherein the apparatus further comprises:
[0352] A transmitter that sends information to the terminal device to identify one or N MAC CEs, or sends information to indicate the N.
[0353] 3. The apparatus according to Appendix 2, wherein the information for determining the one or N MAC CEs includes:
[0354] The priority of the MAC CE, and / or the reporting configuration identifier corresponding to the MAC CE, and / or the triggering LTM event identifier corresponding to the MAC CE, and / or the candidate identifier corresponding to the MAC CE, and / or the resource indicator corresponding to the MAC CE.
[0355] 4. A beam management device, configured in a terminal device, wherein the device comprises:
[0356] The processor removes the information of the first beam from the beam trigger list (BEAM_TRIGGERED_LIST) corresponding to the reporting configuration when the first beam satisfies the departure condition of the LTM event associated with the reporting configuration.
[0357] 5. A beam management device, configured in a terminal device, wherein the device comprises:
[0358] The processor, when the first beam satisfies the entry condition of the LTM event associated with the reporting configuration, includes the information of the first beam in the beam trigger list (BEAM_TRIGGERED_LIST) and the measurement report list (MR_LIST) corresponding to the reporting configuration.
[0359] 6. The apparatus according to Appendix 5, wherein, when the first beam satisfies the departure condition of the LTM event associated with the reporting configuration, the measurement reporting entry is removed from the measurement report list if a measurement reporting entry in the measurement report list does not contain information about any beam.
[0360] 7. A terminal device comprising the apparatus described in Appendix 5 or 6.
[0361] 8. A network device comprising the means described in any one of Appendices 1 to 3.
[0362] 9. A communication system comprising the terminal equipment described in Appendix 7 and / or the network equipment described in Appendix 8.
Claims
1. A report sending device, configured in a terminal device, wherein, The device includes: The processor, when an L1 measurement report is triggered and not canceled, maintains the periodic reporting timer according to the reporting configuration identifier, or according to the candidate cell in the reporting configuration identifier, or according to the beam or reference signal in the reporting configuration identifier.
2. The apparatus according to claim 1, wherein, The maintenance cycle reporting timer, based on the reported configuration identifier or the candidate cells within the reported configuration identifier, includes: If the periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is not running, start the periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier.
3. The apparatus according to claim 1, wherein, According to the reported configuration identifier, or according to the candidate cells within the reported configuration identifier, the maintenance cycle reporting timer includes: If a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within a reporting configuration identifier is running, the reporting configuration identifier or the periodic reporting timer corresponding to a candidate cell within a reporting configuration identifier shall not be started, stopped, or restarted.
4. The apparatus according to claim 3, wherein, When the L1 Measurement Report MAC CE is generated during the instruction multiplexing and encapsulation process, a periodic reporting timer corresponding to a reporting configuration identifier or a candidate cell within the reporting configuration identifier is started.
5. The apparatus according to claim 3, wherein, When UL-SCH resources are available for new transmission and the UL-SCH resources are capable of accommodating an L1 Measurement Report MAC CE plus its header as a result of logical channel priority, the multiplexing and encapsulation process is instructed to generate the L1 Measurement Report MAC CE and start a reporting configuration identifier or a periodic reporting timer corresponding to a candidate cell within the reporting configuration identifier.
6. The apparatus according to claim 1, wherein, The processor also maintains a measurement report transmission counter according to the reporting configuration identifier, or according to the candidate cells within the reporting configuration identifier, or according to the beam or reference signal within the reporting configuration identifier. The measurement report transmission counter is used to count L1 measurement reports triggered by events.
7. The apparatus according to claim 6, wherein, The maintenance measurement report sending counter includes: In the case of generating a (truncated) L1 measurement report MAC CE, the measurement report transmission counter is incremented by 1; or In the case of generating a truncated L1 measurement report MAC CE, the measurement report transmission counter is not incremented by 1; or When an L1 measurement report MAC CE is generated, the measurement report sending counter is incremented by 1.
8. The apparatus according to claim 1, wherein, The maintenance cycle reporting timer, based on the beam or reference signal within the reported configuration identifier, further includes: Based on the first timer, determine whether to generate a (truncated) L1 measurement report MAC CE; or Based on the first timer, determine whether to trigger the L1 measurement report.
9. The apparatus according to claim 8, wherein, The determination of whether to generate a (truncated) L1 measurement report MAC CE based on the first timer includes: If the first timer is not running, generate the (truncated) L1 measurement report MAC CE based on the UL resources; or Based on UL resources, if the first timer is not running, generate the (truncated) L1 measurement report MAC CE, or trigger a scheduling request SR; or While the first timer is running, the (truncated) L1 measurement report MAC CE is not generated, nor is the SR triggered.
10. The apparatus according to claim 8, wherein, The determination of whether to generate a (truncated) L1 measurement report MAC CE based on the first timer includes: In the event of generating or sending the (truncated) L1 measurement report MAC CE, the first timer is started.
11. The apparatus according to claim 8, wherein, The process of determining whether to trigger an L1 measurement report based on a first timer includes: The L1 measurement report is triggered when the event entry or exit condition is met for a timeout (TTT), or when the periodic reporting timer times out and the first timer has not run; or, The L1 measurement report is not triggered while the first timer is running.
12. The apparatus according to claim 8, wherein, The process of determining whether to trigger an L1 measurement report based on a first timer includes: The L1 measurement report is triggered either by meeting the event entry or exit conditions (TTT) or by the periodic reporting timer timeout, and the first timer is started.
13. The apparatus according to claim 9 or 11, wherein, The first timer not running includes at least one of the following: The first timer was not configured; The first timer was not started; The first timer timed out.
14. The apparatus according to claim 1, wherein, The maintenance cycle reporting timer, based on the beam or reference signal within the reported configuration identifier, further includes: One of the generated (truncated) L1 measurement reports in the MAC CE is included in a single MAC PDU.
15. The apparatus according to claim 14, wherein, The multiple (truncated) L1 measurement reports MAC CE are generated within time T.
16. The apparatus according to claim 14, wherein, The L1 measurement report MAC CE included in the MAC PDU is one of the following among the generated (truncated) L1 measurement reports MAC CE: The L1 measurement report with the largest number of beams included is MAC CE; The L1 measurement report MAC CE, which includes the largest number of beams that meet the event entry conditions; The L1 measurement report MAC CE containing the largest number of beams that meet the event entry or exit conditions; The L1 measurement report MAC CE with the fewest number of beams that do not meet the event entry / exit conditions; L1 measurement report MAC CE with the fewest number of beams including beam type changes; The first / last generated L1 measurement report MAC CE.
17. A report sending device, configured in a terminal device, wherein, The device includes: The processor encapsulates one or N measurement report MAC CEs from multiple measurement report MAC control units into a MAC protocol data unit (MAC PDU), where N is an integer greater than 1; A transmitter that sends the MAC PDU to a network device.
18. The apparatus according to claim 17, wherein, The MAC PDU includes a measurement report MAC CE, which is either the earliest generated MAC CE, the latest generated MAC CE, the largest MAC CE, a MAC CE determined based on the terminal device implementation, or a MAC CE determined based on the network device configuration information, or... The MAC PDU includes the N Measurement Reports (MAC CEs). The N Measurement Reports (MAC CEs) are either the N MAC CEs generated earlier, the N MAC CEs newly generated, the N largest MAC CEs, the N MAC CEs determined based on the terminal device implementation, or the N MAC CEs determined based on the network device configuration information.
19. The apparatus according to claim 18, wherein, The information configured in the network device includes the priority of the MAC CE, and / or the reporting configuration identifier corresponding to the MAC CE, and / or the triggering LTM event identifier corresponding to the MAC CE, and / or the candidate identifier corresponding to the MAC CE, and / or the resource indication corresponding to the MAC CE, and / or information used to indicate the N.
20. The apparatus according to claim 17, wherein, The measurement report MAC CE (MR MAC CE) includes at least one of the following: Event-triggered MR MAC CE; The event triggering cycle is MR MAC CE; Event-triggered truncated MR MAC CE; The truncated MR MAC CE of the event triggering period; MR MAC CE with the same or different reporting configuration identifiers; MR MAC CE triggered by the same or different LTM events.
