Beam determination method and apparatus, and timing advance determination method and apparatus
By configuring beam determination and timing advance determination devices in the terminal equipment, the problems of inaccurate beam determination and inconsistent timing advance in LTM cell handover are solved, realizing efficient cell handover without random access and reducing downtime and UL interference.
Patent Information
- Application Number
- PCT/CN2025/093621
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
The existing Layer 1/Layer 2 triggered mobility (LTM) suffers from inaccurate beam determination and inconsistent timing advance during cell handover between different base stations, which makes it impossible to skip the random access process, increasing downtime and UL interference.
A beam determination device and a timing advance determination device are provided, configured in a terminal device, for determining the target beam and obtaining a consistent timing advance when a mobile cell handover is triggered at condition layer 1/2, ensuring a handover process that does not require random access.
It enables accurate determination of the target beam during conditional LTM cell handover, reduces downtime, ensures consistent TA acquisition behavior of terminal equipment, and avoids UL interference.
Smart Images

Figure CN2025093621_12112026_PF_FP_ABST
Abstract
Description
Beam determination method, timing advance determination method and device Technical Field
[0001] The embodiments of this application relate to the field of communication technology. Background Technology
[0002] Rel-18 (version 18) introduced Layer 1 / Layer 2 Triggered Mobility (LTM), which offers improved handover latency and downtime compared to Layer 3 (L3) based mobility. However, LTM introduced in Rel-18 also has some limitations compared to L3 based mobility. The goal of the Rel-19 (version 19) work project is to eliminate these limitations.
[0003] Currently, LTM operation only supports mobility between cells within the same gNB (referred to as base station, network equipment, network, etc.) (or the same CU (Centralized Unit)). 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 will be able to enable more handovers to benefit from LTM.
[0004] L3-based mobility uses L3 measurement reporting, which allows UE (User Equipment) to evaluate events to trigger measurement reports, reducing signaling overhead compared to periodic measurement reporting. L1 measurements used for LTM mobility in Rel-18 do not support such event triggering.
[0005] Furthermore, L1 measurements in the LTM process are limited to SSB (Synchronization Signal and PBCH block) measurements. Extending L1 measurements to include CSI-RS (Channel State Information-Reference Signal) can overcome this limitation and promises to achieve greater throughput on the target cell immediately after cell handover.
[0006] 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
[0007] The inventors discovered that for Conditional LTM (CLTM) cell handover (CS) procedures, the following two methods can be used to trigger Conditional LTM cell handover:
[0008] L1 Measurement-Based Triggering: The UE's MAC (Media Access Control) entity determines the triggering event requirements for conditional LTM based on L1 measurement results. The network can configure connected (RRC_CONNECTED) UEs to perform L1 beam-level measurements of special cells (SpCell) and conditional LTM candidate cells to measure the L1-RSRP (Reference Signal Receiving Power / Reference Signal Received Power) and / or SINR (Signal to Interference plus Noise Ratio) of the beams. Based on these L1 measurement results, the UE determines the beams that meet the conditional LTM execution conditions. If only one beam meets the conditional LTM execution conditions, RACH-less LTM / CLTM cell handover is performed based on that beam. If multiple beams meet the conditional LTM execution conditions, the UE selects one beam and performs conditional RACH-less LTM / CLTM cell handover.
[0009] L3 measurement-based triggering: After the UE performs L3 measurement, the upper layer determines the triggering event requirements of conditional LTM based on the L3 measurement results.
[0010] However, for L3-triggered conditional LTM cell handover processes, such as events A3 or A5, because cell-level execution conditions are used, the current upper-layer determination process can only determine the target cell that meets the conditional LTM triggering conditions, but cannot determine the target beam that meets the triggering conditions. In this case, if RACH-based LTM / CLTM is executed, the UE can determine the target beam during the random access process through the existing mechanism; however, if RACH-less LTM / CLTM is executed, the MAC layer cannot determine the target beam. This makes it impossible for L3 measurement-triggered conditional LTM cell handover processes to skip the random access process, resulting in greater interruption.
[0011] In addition, the network may send an LTM cell handover command MAC CE to the terminal device to indicate a CLTM candidate configuration or a CLTM candidate cell. On one hand, according to the mechanism in version 18, the LTM cell handover command MAC CE includes a Timing Advance Command (TAC) to indicate whether the Time Advance (TA) value associated with a specific cell in the CLTM candidate configuration that is the target cell / target configuration is valid. If the TAC value is set to FFF, it indicates that no valid timing adjustment is available; otherwise, the TAC indicates the index value T used to control the amount of timing adjustment. A Terminal devices can skip the random access process.
[0012] On the other hand, for CLTM candidate configurations or CLTM candidate cells, PDCCH ordered early RACH is supported to achieve early uplink synchronization. In this case, the network device indicates the timing advance of the CLTM candidate configuration or CLTM candidate cell by sending an LTM Candidate Timing Advance Command MAC CE.
[0013] This means that when a network device might send an LTM Cell Switch Command MAC CE indicating a CLTM candidate configuration or CLTM candidate cell, the terminal device has three ways to obtain the TA: the TA value in the LTM Cell Switch Command MAC CE, the TA value in the LTM Candidate Timing Advance Command MAC CE, and the timing advance measured by the terminal device (UE measured TA). The TA value indicated by the MAC CE is preferred over the UE measured TA. However, according to the existing Rel-18 mechanism, if the TA value in the LTM Cell Switch Command MAC CE is set to FFF, the terminal device or MAC entity will attempt to obtain the UE measured TA, which is inconsistent with the TA value indicated by the MAC CE taking precedence over the UE measured TA. This inconsistency may lead to different implementations of UEs from different vendors, thus affecting UL transmission and even causing UL interference.
[0014] To address at least one of the above-mentioned problems or other similar problems, embodiments of this application provide a beam determination method and apparatus.
[0015] According to one aspect of the embodiments of this application, a beamforming device is provided, configured in a terminal device, the device comprising:
[0016] The processor determines the first beam when a Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered;
[0017] The transmitter performs an initial uplink transmission to the target cell based on the first beam.
[0018] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method and apparatus for determining timing advance.
[0019] According to another aspect of the embodiments of this application, a timing advance determination device is provided, configured in a terminal device, the device comprising:
[0020] The receiver receives an LTM cell handover command MAC CE, which indicates a conditional LTM candidate cell.
[0021] The processor applies one of the timing advance indicated by the LTM cell handover command MAC CE to the primary timing advance group (PTAG), or the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device.
[0022] One of the beneficial effects of the embodiments of this application is that, according to the embodiments of this application, when a conditional LTM cell handover is triggered, the target beam used to perform the initial uplink transmission to the target cell can be determined, ensuring that the terminal device can determine the target beam used to perform conditional LTM cell handover, thereby performing cell handover without a random access process, reducing interruptions, and the method is simple and easy to implement.
[0023] One of the beneficial effects of the embodiments of this application is that, according to the embodiments of this application, it is possible to determine one of the timing advance indicated by the PTAG application LTM cell handover command MAC CE, the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device. Thus, it is possible to ensure that the behavior of the terminal device or MAC entity in obtaining TA is consistent and to avoid UL interference.
[0024] 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.
[0025] 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.
[0026] 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
[0027] 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.
[0028] Figure 1 is a schematic diagram of the communication system of this application;
[0029] Figure 2 is a schematic diagram of an inter-cell mobility scenario under the same gNB-CU;
[0030] Figure 3 is a schematic diagram of the LTM cell change process;
[0031] Figure 4 is a schematic diagram of contention-free random access (CFRA) for early uplink synchronization;
[0032] Figure 5 is a schematic diagram of the measurement model;
[0033] Figure 6 is a schematic diagram of a beam determination method according to an embodiment of this application.
[0034] Figure 7 is a schematic diagram of the first MAC CE format according to an embodiment of this application;
[0035] Figure 8 is another schematic diagram of the first MAC CE format according to an embodiment of this application;
[0036] Figure 9 is another schematic diagram of the first MAC CE format according to an embodiment of this application;
[0037] Figure 10 is another schematic diagram of the first MAC CE format according to an embodiment of this application;
[0038] Figure 11 is another schematic diagram of the first MAC CE format according to an embodiment of this application;
[0039] Figure 12 is a schematic diagram of a timing advance method according to an embodiment of this application;
[0040] Figure 13 is a schematic diagram of a beam determination device according to an embodiment of this application;
[0041] Figure 14 is a schematic diagram of a timing advance determination device according to an embodiment of this application;
[0042] Figure 15 is a schematic diagram of a beam determination method according to an embodiment of this application;
[0043] Figure 16 is a schematic diagram of a beam determination device according to an embodiment of this application;
[0044] Figure 17 is a schematic diagram of a terminal device according to an embodiment of this application;
[0045] Figure 18 is a schematic diagram of a network device according to an embodiment of this application;
[0046] Figure 19 is a schematic diagram of the LTM cell handover command MAC CE;
[0047] Figure 20 is a schematic diagram of the LTM candidate timing advance command MAC CE;
[0048] Figure 21 is a schematic diagram of the CLTM cell change process. Detailed Implementation
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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 Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0053] 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.
[0054] 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: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
[0055] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (or eNodeBs or eNBs), and 5G base stations (gNBs), etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, or IAB-DUs or IAB-donors. The term "base station" can include some or all of their 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. Without causing confusion, the terms "cell" and "base station" are used interchangeably.
[0056] 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. Terminal equipment can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), IAB-MT (Mobile Terminal), station, etc.
[0057] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.
[0058] 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.
[0059] 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. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.
[0060] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.
[0061] 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.
[0062] (1) Define support for inter-CU layer 2 mobility (LTM). For example, it may include the following.
[0063] Prioritize the case where CU acts as MN when DC is not configured;
[0064] As a secondary priority, it supports the case where NR-DC and CU are configured as SN and MN remains unchanged;
[0065] 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).
[0066] According to Rel-18 LTM, support for subsequent LTM mobility procedures is defined with the goal of avoiding RRC configuration between cell handovers;
[0067] In terms of secure key processing, SA3 is scheduled for negotiation (the Rel-18 intra-CU LTM process is considered as the baseline for adding inter-CU support).
[0068] (2) Measurement-related enhancements to support LTM. For example, these may include the following.
[0069] Measurement-related enhancements are applicable to both intra-CU MCG / SCG LTM and inter-CU MCG / SCG LTM;
[0070] Define the necessary components to support event-triggered L1 measurement reporting;
[0071] 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;
[0072] Define the acquisition of CSI on candidate cells based on CSI-RS before or during LTM cell handover.
[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] The scenario for limiting the definition of LTM is when the UE is not in a DC state.
[0077] (4) Define the RRM requirements related to the above objectives if necessary.
[0078] 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).
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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:
[0087] 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.
[0088] 2. The source gNB determines the LTM configuration;
[0089] 3. The source gNB requests LTM configuration for one or more candidate cells belonging to itself, and / or one or more candidate gNBs. In 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.
[0090] 4. Candidate cells or gNBs implement access control;
[0091] 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;
[0092] 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;
[0093] 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;
[0094] 8. The source gNB sends an RRC reconfiguration message to the user equipment;
[0095] 9. The user equipment stores the LTM candidate configuration and sends an RRC reconfiguration complete message to the source gNB;
[0096] 9a. If early data forwarding is applied, the source gNB sends an early state transition message to the candidate gNB;
[0097] 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;
[0098] 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.
[0099] 13. The source gNB decides to initiate LTM. L3 measurements can also be used to assist in making this decision.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] 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 the AMF / User Plane Function (UPF) handover in clause 9.2.3.2.1 of TS 38.300;
[0104] 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 random access, 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.
[0105] 20. The new source gNB (i.e., the target gNB) sends an LTM configuration update message to the candidate gNB;
[0106] 21. The candidate gNB replies with an LTM configuration update confirmation message to the new source gNB;
[0107] 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.
[0108] 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). Figure 4 is a schematic diagram of contention-free random access (CFRA). 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.
[0109] For subsequent LTMs, the LTM candidate configurations provided in step 8 can be used to execute steps 9a-22 multiple times.
[0110] LTM can be based on L1 or L3 measurement reports, where, regarding Layer 1 measurements and reporting:
[0111] For event-triggered L1 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:
[0112] Event LTM2: The beam of the serving cell becomes worse than the absolute threshold.
[0113] Event LTM3: The beam of the candidate cell becomes an offset better than the beam of the serving cell.
[0114] Event LTM4: The beam of candidate cell becomes better than the absolute threshold.
[0115] Event LTM5: The beam of the serving cell becomes worse than absolute threshold 1 and the beam of the candidate cell becomes better than another absolute threshold 2.
[0116] Figure 21 is a schematic diagram of the CLTM cell change process. As shown in Figure 3, the CLTM process includes the following steps:
[0117] 1. The user equipment sends a measurement report message to the gNB. The gNB decides to configure CLTM and initiates CLTM preparation.
[0118] 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.
[0119] 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;
[0120] 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.
[0121] 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 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.
[0122] 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.
[0123] 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.
[0124] Regarding Layer 3 measurements and reporting:
[0125] In Radio Resource Control (RRC_CONNECTED) connected mode, the UE measures multiple beams or at least one beam of a cell and averages the measurement results (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 results are a selection and / or set of multiple beam-level L3 measurements. Cell quality is obtained from beam measurements in the same manner for both serving and non-serving cells.
[0126] 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.
[0127] 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.
[0128] A: Measurements within the physical layer (beam-specific samples).
[0129] Layer 1 filtering: Internal layer 1 filtering of the inputs measured at point A; the accuracy of the filtering depends on the implementation.
[0130] A1: Measurements reported by layer 1 to layer 3 after layer 1 filtering (i.e., beam-specific measurements).
[0131] 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 one measurement period at A1.
[0132] B: A measurement (i.e., cell quality) obtained from beam-specific measurements reported to layer 3 after beam consolidation or beam selection.
[0133] Layer 3 filtering for cell quality: Filtering is performed on the measurements provided at point B. The behavior of 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.
[0134] 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.
[0135] Evaluation of reporting criteria: This examines 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, as illustrated by inputs C and C1, the UE evaluates the reporting criteria at least each time a new measurement result is reported at point C,C1. The behavior of these reporting criteria is standardized, and this configuration is provided by RRC signaling.
[0136] D: Send measurement report information or measurement report messages on the wireless interface.
[0137] Layer 3 beam filtering: Filtering is performed on the measurements provided at point A1. Filtering 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 one measurement period at A1.
[0138] E: A measurement after processing in the beam filter, such as an iebeam-specific measurement. The reporting rate is identical to the reporting rate at point A1. This beam-filtered measurement is used as input to select the X measurements to be reported.
[0139] 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.
[0140] F: Beam measurement information is included in the measurement report (transmitted) on the wireless interface.
[0141] L3 measurement reports have the following characteristics:
[0142] The measurement report includes the measurement identity associated with the measurement configuration that triggered the report;
[0143] Cell and beam measurements included in the measurement report are configured by the network;
[0144] The number of non-serving cells that can be reported can be limited through network configuration;
[0145] 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.
[0146] 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.
[0147] The embodiments of this application will now be described in conjunction with the accompanying drawings and specific implementation details. In the following description, without causing confusion, "if…", "in the case of…", and "when…" can be used interchangeably. "Available beam" and "target beam" can be used interchangeably. "Candidate cell" and "target cell" can be used interchangeably.
[0148] First aspect of the embodiments
[0149] This application provides a beam determination method, which is described from the perspective of a terminal device.
[0150] Figure 6 is a schematic diagram of a beam determination method according to an embodiment of this application. As shown in Figure 6, the method includes:
[0151] 601. When a Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered, the terminal device determines the first beam;
[0152] 602. The terminal device performs an initial uplink transmission to the target cell according to the first beam.
[0153] It is worth noting that Figure 6 above is only a schematic illustration of an embodiment of this application, but this application is not limited thereto. For example, other operations may be added or some operations may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 6 above.
[0154] In some embodiments, CLTM cell handover can be triggered based on Layer 1 measurements or Layer 3 measurements. The first beam is the target beam for CLTM cell handover, or in other words, the first beam used to perform CLTM cell handover. When CLTM cell handover is triggered by Layer 1 measurements, if a candidate beam meets the CLTM conditions, that candidate beam becomes the first beam. If multiple candidate beams meet the CLTM conditions, the UE selects one beam as the first beam.
[0155] In the case of CLTM cell handover triggered by Layer 3 measurement, the following explains how to determine the first beam.
[0156] In step 601, in some embodiments, the first beam is determined by the terminal device. For example, the terminal device can determine the first beam based on implementation; and / or, the terminal device can determine the first beam based on beam quality; and / or, the terminal device can select a beam associated with an active Transmission Configuration Indicator state (TCI state) as the first beam; and / or, the terminal device can select a beam configured with a Configuration Grant occasion (CG occasion) as the first beam. The Candidate Cell TCI States Activation / Deactivation MAC CE is used to activate the TCI State.
[0157] Specifically, for determining the first beam based on beam quality, the terminal device can select the best beam, that is, the beam with the best measurement quality of the reference signal corresponding to the beam, or the beam with the best measurement result at the layer 3 beam level, as the first beam; or, the network device can configure a first threshold for the terminal device, and the UE can select a beam with beam quality higher than the first threshold as the first beam.
[0158] In some embodiments, the first threshold can be configured by the network device. For example, the first threshold is a Reference Signal Received Power (RSPR) threshold configured by the network device for the terminal device, and / or, the first threshold is related to a preset threshold of a Layer 3 measurement event that triggers cell handover. For example, the first threshold is related to a preset threshold in condEventA5, where condEventA5 indicates that the RSPR value of the serving cell is lower than threshold 1, and the RSPR value of the conditional reconfiguration candidate cell / LTM candidate cell is higher than threshold 2. In this case, the first threshold can be set to threshold 1 or threshold 2. Alternatively, the first threshold can be related to preset thresholds of other Layer 3 measurement events that trigger cell handover, such as condEventA3. Examples are not provided here. The first threshold can be carried by RRC or MAC CE, but this embodiment does not limit it.
[0159] In the above embodiments, the terminal device may determine the first beam based on only one of the above conditions, or it may determine the first beam based on multiple conditions. For example, the terminal device may select one beam as the first beam from multiple beams whose beam quality is higher than a first threshold, based on UE implementation; or, the terminal device may select the beam with the best quality from multiple beams associated with / active TCI states or multiple beams configured with CG occasions; or, the terminal device may select one beam as the first beam from multiple beams configured with CG occasions and whose quality is better than the first threshold, based on UE implementation. This application does not impose any limitations.
[0160] In step 601, in some embodiments, the first beam may also be indicated to the terminal device by the network device. The terminal device receives a first Media Access Control (MAC) Element (CE), which includes information for indicating the first beam. The information for indicating the first beam includes a TCI state identifier (ID), and the first beam is the beam corresponding to the TCI state indicated by the TCI state ID. The correspondence between the TCI state and the beam is determined according to the candidate cell configuration in step 3 of Figure 21.
[0161] For example, the information of the first beam is at least one of the following fields in MAC CE:
[0162] The TCI state identifier (ID) field indicates and activates the TCI state of the LTM candidate cell, which is the TCI state of the specific cell in the candidate configuration indicated by the candidate configuration ID field. The first beam is the beam corresponding to the TCI state indicated by the TCI state ID. This TCI state is determined by the TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList. If the value of unifiedTCI-StateType in ltm-TCI-Info of the configuration indicated by the candidate configuration ID field is joint, this field is a joint TCI state; otherwise, this field is a downlink TCI state. The length of this field is 7 bits.
[0163] The UL TCI state ID field indicates and activates the uplink TCI state of the LTM candidate cell, i.e., the uplink TCI state of the specific cell in the candidate configuration indicated by the candidate ID field. This UL TCI state is determined by the UL-StateId in ltm-UL-TCI-StateToAddModList. If the value of unifiedTCI-StateType in the configuration ltm-TCI-Info indicated by the candidate configuration ID field is separate, including the bytes of this field or if this field exists / is included in the MAC CE, the length of this field is 6 bits.
[0164] The following describes the format of the first MAC CE.
[0165] In some embodiments, the first MAC CE may be an LTM candidate timing advance command MAC CE, that is, the first MAC CE includes information for indicating the timing advance amount as well as information for indicating the first beam.
[0166] Figure 7 is a schematic diagram of the first MAC CE format according to an embodiment of this application.
[0167] In some examples, the first MAC CE can be the LTM candidate timing advance command MAC CE shown in Figure 7. As shown in Figure 7, the size of the first MAC CE is variable, including a Candidate Config ID field, which represents the index of the corresponding CLTM candidate configuration and has a length of 3 bits. The first MAC CE also includes a Timing Advanced Group (TI) identifier. If two Timing Advanced Groups (TAGs) are configured for the CLTM candidate cell corresponding to the candidate configuration identifier, this field indicates the application of one of the two TAGs. If no two TAGs are configured, this field is set to a reserved bit (R bit). The MAC CE also includes a Timing Advanced Command field, which has a length of 12 bits. In addition, for the TCI state ID field and the UL TCI state ID field, please refer to the above content, which will not be repeated here.
[0168] Figure 8 is another schematic diagram of the first MAC CE format according to an embodiment of this application.
[0169] In some examples, the first MAC CE can be the LTM candidate timing advance command MAC CE shown in Figure 8. As shown in Figure 8, the size of this MAC CE is variable. Unlike Figure 7, it also includes a C field, which indicates whether the contention-free random access resource field exists. If the value of this field is 1, the following fields exist: Random Access Preamble index field, Synchronization Signal / Physical Broadcast Channel (SS / PBCH) index field, repeating word number field, and reserved bits in the same byte. If the value of this field is set to 0, the above fields do not exist. The length of the Random Access Preamble index field is 6 bits, the length of the SS / PBCH index field is 6 bits, and the length of the PRACH mask index field is 4 bits.
[0170] In some embodiments, the first MAC CE may also be different from the LTM candidate timing advance command MAC CE, and may be a newly designed MAC CE used to indicate information about the first beam, excluding information used to indicate timing advance.
[0171] Figure 9 is another schematic diagram of the first MAC CE format according to an embodiment of this application. In some examples, the first MAC CE can be a MAC CE for indicating information of the first beam, as shown in Figure 9. For the candidate configuration identifier field, TCI state ID field, and UL TCI state ID field in the MAC CE, refer to the above content, which will not be repeated here.
[0172] Figure 10 is another schematic diagram of the first MAC CE format according to an embodiment of this application. In some examples, the first MAC CE can be a MAC CE for indicating information of the first beam, as shown in Figure 10. The size of the MAC CE is variable. The length of the S / U field in the MAC CE is 1 bit, and the length of the repetition number field is 2 bits. For the candidate configuration identifier field, C field, TCI state ID field, UL TCI state field, random access preamble index field, SS / PBC index field, SS / PBCH index field, and PRACH mask index field in the MAC CE, please refer to the above content, which will not be repeated here.
[0173] Figure 11 is another schematic diagram of the first MAC CE format according to an embodiment of this application. In some examples, the first MAC CE can be a MAC CE for indicating information of the first beam, as shown in Figure 11. The size of the MAC CE is variable, wherein the L in the MAC CE... iThe (L0~L7) fields indicate whether the TCI state ID field corresponding to the corresponding candidate configuration identifier exists or whether the byte containing the TCI state ID field corresponding to the corresponding candidate configuration identifier exists; for example, L i A value of 1 indicates that the TCI state ID field / byte containing the TCI state ID field of the candidate configuration with candidate configuration identifier (corresponding to ltm-CandidateId-1) i exists. For other fields in this MAC CE, please refer to the above content; further details are omitted here.
[0174] The following describes how the terminal device performs the initial uplink transmission to the target cell based on the first beam.
[0175] In some embodiments, the terminal device determines the CG occasion based on the first beam, and performs the initial uplink transmission for RACH-less CLTM cell handover on the CG occasion.
[0176] In some examples, when the first beam is indicated to the terminal device by the network device, upon receiving the first MAC CE, the terminal device or MAC entity determines the CG occasion based on the uplink grant associated with the reference signal associated with the TCI state indicated by the first MAC CE. Specifically, it considers the reference signal (SSB) associated with the TCI state indicated by the TCI state ID field as the reference signal (SSB) for configuring uplink grant selection, which is the initial or first uplink transmission to the target cell for RACH-less CLTM cell handover. Furthermore, the terminal device or MAC entity can also indicate information related to the TCI state information included in the MAC CE to the lower layers.
[0177] In other examples, when the first beam is determined by the terminal device, the uplink grant associated with the reference signal associated with the first beam by the terminal device or MAC entity determines the CG occasion, i.e., the first beam (e.g., SSB), or the SSB associated with the first beam (e.g., CSI-RS) is considered as the SSB for configuring uplink grant selection for the initial uplink transmission to the target cell for RACH-less CLTM cell handover.
[0178] In some embodiments, if the first beam (e.g., SSB), or the SSB associated with the first beam (e.g., CSI-RS), is not configured with a CG occasion, the terminal device performs a random access procedure, i.e., performs a RACH-based LTM cell handover.
[0179] For example, if the first MAC CE also indicates random access related information, the terminal device or MAC entity can use the indicated random access resources and / or preamble to perform the random access procedure; or, the terminal device or MAC entity performs the random access procedure on the first beam; or, the terminal device or MAC entity selects a second beam different from the first beam and performs the random access procedure on the second beam. For details on the random access procedure, please refer to relevant technologies, which will not be elaborated here. Regarding whether the reference signal associated with the first beam is configured with a CG occasion, this can be determined based on the candidate configuration in step 2 of Figure 3, which will not be elaborated here.
[0180] The execution process of Conditional LTM is shown in Table 1 below:
[0181] Table 1
[0182] In other words, when the upper layers indicate that the LTM event is met, i.e., when CLTM cell handover is triggered, the MAC entity obtains the Target Configuration ID from the upper layers. This ID corresponds to the candidate configuration for LTM / CLTM cell handover triggered by an event based on L3 measurement. Based on step 601, the first beam is determined, and it is decided whether to perform random access (RACH-based LTM) or RACH-less LTM. This includes determining whether the ltm-Candidate-TimeAlignmentTimer associated with the Target Configuration ID is running; or in other words, whether the ltm-Candidate-TimeAlignmentTimer corresponding to the TAG to which the first beam belongs is running. If it is running, RACH-less CLTM is executed. If it is not running, a TA that can be measured by the UE is determined. If the measurement is valid, RACH-less CLTM is executed. It is determined whether the first beam is configured with cg-RRC-Configuration. If it is configured, an available Configured Grant (CG occasion) associated with the first beam is selected; and the initial uplink transmission is initiated on the first available CG occasion (completing the RACH-less handover). If not configured, random access (RACH-based LTM) will be performed.
[0183] It is worth noting that Figures 7-11 above are only schematic illustrations of embodiments of this application, but this application is not limited thereto. For example, other operations may be added or some operations may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figures 7-11 above.
[0184] According to the method in the embodiments of this application, when a conditional LTM cell handover is triggered, the target beam used to perform the initial uplink transmission to the target cell can be determined, ensuring that the terminal device can determine the target beam used for conditional LTM cell handover, avoiding interruption, and the method is simple and easy to implement.
[0185] Second aspect of the embodiments
[0186] This application provides a method for determining timing advance, which is described from the perspective of the terminal device.
[0187] Figure 12 is a schematic diagram of a timing advance determination method according to an embodiment of this application. As shown in Figure 12, the method includes:
[0188] 1201. The terminal device receives an LTM cell handover command MAC CE, which is used to indicate a conditional LTM candidate cell;
[0189] 1202. The terminal device applies one of the timing advance amount indicated by the LTM cell handover command MAC CE, the timing advance amount indicated by the LTM candidate timing advance command MAC CE, or the timing advance amount measured by the terminal device to the primary timing advance group (PTAG).
[0190] It is worth noting that Figure 12 above is only a schematic illustration of an embodiment of this application, but this application is not limited thereto. For example, other operations may be added or some operations may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 12 above.
[0191] Figure 19 is a schematic diagram of the LTM cell handover command MAC CE. Figure 20 is a schematic diagram of the LTM candidate timing advance command MAC CE.
[0192] In some embodiments, the LTM cell handover command MAC CE includes a target configuration ID, which corresponds to a conditional LTM candidate cell (i.e., an LTM candidate cell configured with L1 or L3 events). The LTM cell handover command MAC CE indicating a conditional LTM candidate cell can also be understood as indicating a conditional LTM candidate configuration. The following terminal devices can be replaced with MAC entities.
[0193] In some embodiments, as shown in FIG19, the timing advance indicated by the LTM cell handover command MAC CE is the TA value indicated by the timing advance command field in FIG19. As shown in FIG20, the timing advance indicated by the LTM candidate timing advance command MAC CE is the TA value indicated by the timing advance command field in FIG20. Whether the terminal device is allowed to measure the timing advance is configured by the network device through the ue-TimingAdvanceMeasurement parameter in RRCReconfiguration in step 3 of FIG21. The terminal device measures the timing advance by receiving and processing the downlink reference signal. Specific measurement implementation methods can be referred to related technologies, which will not be elaborated here. In addition, the target configuration indicated by the LTM cell handover command MAC CE mentioned below is indicated by the target configuration identifier field in FIG19, and the candidate configuration indicated by the LTM candidate timing advance command MAC CE is indicated by the candidate configuration identifier field in FIG20.
[0194] In some examples (i), the timing advance indicated by the LTM cell handover command MAC CE is better than the timing advance indicated by the LTM candidate timing advance command MAC CE and the timing advance measured by the terminal device.
[0195] When the timing advance indicated by the LTM cell handover command MAC CE is not set to the first value, the terminal device applies the timing advance indicated by the LTM cell handover command MAC CE to the primary timing advance group (PTAG), where the first value is FFF.
[0196] In some examples (ii), when the timing advance indicated by the LTM cell handover command MAC CE is set to a first value, the terminal device applies the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device, to the primary timing advance group (PTAG), where the first value is FFF.
[0197] Example 1: When the timing advance indicated by the LTM cell handover command MAC CE is set to a first value: the timing advance indicated by the LTM candidate timing advance command MAC CE takes precedence over the timing advance measured by the terminal device.
[0198] Specifically, when the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is running, the terminal device applies the timing advance amount indicated by the LTM candidate timing advance command MAC CE to the PTAG; wherein, upon receiving the LTM candidate timing advance command MAC CE, the terminal device starts or restarts the candidate time alignment timer associated with the special cell of the candidate configuration indicated by the LTM candidate timing advance command MAC CE, and stores the timing advance amount indicated by the LTM candidate timing advance command MAC CE.
[0199] In other words, upon receiving the LTM Candidate Timing Advance Command MAC CE, the terminal device starts or restarts the candidate time alignment timer associated with the special cell of the candidate configuration indicated by the LTM Candidate Timing Advance Command MAC CE. Subsequently, upon receiving an LTM Cell Handover Command MAC CE, the target configuration indicated by the command is exactly the candidate configuration indicated by the LTM Candidate Timing Advance Command MAC CE, or the special cell of the target configuration indicated by the command is exactly the special cell of the candidate configuration indicated by the LTM Candidate Timing Advance Command MAC CE, or the candidate time alignment timer associated with the special cell of the target configuration indicated by the command is exactly the candidate time alignment timer associated with the special cell of the candidate configuration indicated by the LTM Candidate Timing Advance Command MAC CE (already started or restarted and running), then the terminal device applies the timing advance amount indicated by the LTM Candidate Timing Advance Command MAC CE to the PTAG.
[0200] Otherwise, if the candidate time aligner associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is not running, and the terminal device has successfully measured the timing advance of the special cell of the target configuration, the terminal device applies the timing advance measured by the terminal device to the PTAG. Wherein, the candidate time aligner associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is not running includes not receiving the LTM candidate timing advance command MAC CE, or receiving the LTM candidate timing advance command MAC CE, but subsequently receiving an LTM cell handover command MAC CE whose indicated candidate time aligner associated with the special cell of the target configuration is not the candidate time aligner associated with the special cell of the candidate configuration indicated by the LTM candidate timing advance command MAC CE.
[0201] The terminal device believes that RACH-less LTM is in progress.
[0202] Alternatively, for example 2, when the timing advance indicated by the LTM cell handover command MAC CE is set to a first value: the timing advance measured by the terminal device takes precedence over the timing advance indicated by the LTM candidate timing advance command MAC CE.
[0203] If the terminal device has successfully measured the timing advance of the target configuration special cell indicated by the LTM cell handover command MAC CE, the terminal device applies the timing advance measured by the terminal device to the PTAG.
[0204] Otherwise, if the terminal device is not configured with timing advance measurement based on the terminal device, or if the terminal device cannot / has not successfully measured the timing advance of the target configuration special cell indicated by the LTM cell handover command MAC CE, and the candidate time alignment timer associated with the special cell is running, the terminal device applies the timing advance indicated by the LTM candidate timing advance command MAC CE to the PTAG. Specifically, upon receiving the LTM candidate timing advance command MAC CE, the terminal device starts or restarts the candidate time alignment timer associated with the candidate configuration special cell indicated by the LTM candidate timing advance command MAC CE, and stores the timing advance indicated by the LTM candidate timing advance command MAC CE.
[0205] The terminal device believes that RACH-less LTM is in progress.
[0206] In some embodiments, the method may further include:
[0207] The terminal device starts or restarts the time alignment timer associated with the PTAG. The time alignment timer uses the length of the remaining time until expiry of the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) of the special cell configured for the target, or uses the length configured by the network device.
[0208] In some embodiments, when the MAC entity reset is a request from an upper layer, the terminal device or the MAC entity performs at least one of the following:
[0209] Stop ltm-Candidate-TimeAlignmentTimers;
[0210] Stop the ltm-Candidate-TimeAlignmentTimer for the specific cell configured for the target;
[0211] Stop ltm-Candidate-TimeAlignmentTimers for LTM candidate configurations;
[0212] Do not stop ltm-Candidate-TimeAlignmentTimers or keep them running;
[0213] The ltm-Candidate-TimeAlignmentTimer for the specific cell configured for the target will either be stopped or kept running.
[0214] Do not stop ltm-Candidate-TimeAlignmentTimers for LTM candidate configurations or keep them running.
[0215] The following example illustrates this.
[0216] Example 1 in Examples (I) and (II) can be represented using Table 2 or Table 3 as follows:
[0217] Table 2
[0218] Table 3
[0219] Example 2 in Examples (I) and (II) can be represented using Table 4 or Table 5 as follows:
[0220] Table 4
[0221] Table 5
[0222] In addition, Table 6 needs to be added to Tables 2 and 3:
[0223] Table 6
[0224] In addition, Table 7 needs to be added to Tables 4 and 5:
[0225] Table 7
[0226] The statements within the parentheses above can be deleted or replaced. Other content is not a limitation and does not need to include all content; this is just an example.
[0227] It is worth noting that Figure 12 above is only a schematic illustration of an embodiment of this application, but this application is not limited thereto. For example, other operations may be added or some operations may be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 12 above.
[0228] According to the method of the embodiments of this application, the timing advance can be determined as one of the timing advance indicated by the PTAG application LTM cell handover command MAC CE, the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device. Thus, it can ensure that the behavior of the terminal device or MAC entity in obtaining TA is consistent and avoid UL interference.
[0229] The embodiments of the first and second aspects described above can be implemented individually or in combination, and the embodiments of this application are not intended to limit them.
[0230] Third aspect of the embodiments
[0231] This application provides a beamforming device, which may be, for example, a terminal device, or one or more components or parts configured in a terminal device. Since the principle by which this device solves the problem is the same as the method shown in FIG. 6 of the first aspect embodiment, its specific implementation can refer to the implementation of the method shown in FIG. 6 of the first aspect embodiment, and the similarities will not be repeated.
[0232] Figure 13 is a schematic diagram of a beam determination device according to an embodiment of this application. As shown in Figure 13, the device 1300 includes:
[0233] The processor 1301 determines the first beam when a Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered;
[0234] Transmitter 1302 performs an initial uplink transmission to the target cell based on the first beam.
[0235] In some embodiments, the processor 1301 determines the first beam based on an implementation; and / or,
[0236] Processor 1301 determines the first beam based on beam quality; and / or,
[0237] Processor 1301 selects the beam associated with the active Transmission Configuration Indicator state (TCI state) as the first beam; and / or,
[0238] The processor 1301 selects the beam that has been configured with a Configuration Grant occasion (CG occasion) as the first beam.
[0239] In some embodiments, the processor 1301 determines the first beam based on beam quality, including:
[0240] The processor 1301 selects the beam with the best beam quality or the beam with a beam quality higher than a first threshold as the first beam.
[0241] In some embodiments, the first threshold is configured by the network device, and / or the first threshold is related to a preset threshold of a Layer 3 measurement event that triggers cell handover.
[0242] In some embodiments, the device 1300 further includes:
[0243] Receiver 1303 receives a first Media Intervention Control Element (MAC CE), the first MAC CE including information for indicating the first beam.
[0244] In some embodiments, the information used to indicate the first beam includes a TCI state identifier (ID), and the first beam is the beam corresponding to the TCI state indicated by the TCI state ID.
[0245] In some embodiments, the first MAC CE is the LTM candidate timing advance command MAC CE.
[0246] In some embodiments, CLTM cell handover is triggered by Layer 3 measurements.
[0247] In some embodiments, the processor 1301 determines the CG occasion based on the first beam, and the transmitter 1302 performs the initial uplink transmission for RACH-less CLTM cell handover on the CG occasion.
[0248] In some embodiments, the processor 1301 determines the CG occasion based on the uplink grant associated with the reference signal associated with the TCI state indicated by the first MAC CE; or the processor 1301 determines the CG occasion based on the uplink grant associated with the reference signal associated with the first beam.
[0249] In some embodiments, when the reference signal associated with the first beam is not configured with a CG, the processor 1301 performs a random access procedure.
[0250] In some embodiments, the transmitter 1302 performs a random access procedure on the first beam or a second beam different from the first beam, or the processor 1301 performs a random access procedure based on the random access resources and / or preamble indicated by the first MAC CE.
[0251] In the above embodiments, the content and format of the first MAC CE have been described in the previous embodiments and will not be repeated here.
[0252] 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 aforementioned apparatus may also include other components or modules, and for details regarding these components or modules, please refer to related technologies. Furthermore, the aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not impose any limitations on this.
[0253] The apparatus according to the embodiments of this application can determine the target beam used to perform initial uplink transmission to the target cell when conditional LTM cell handover is triggered, ensuring that the terminal device can determine the target beam used for conditional LTM cell handover, avoiding interruptions caused by the inability to determine the target beam, and the method is simple and easy to implement.
[0254] Fourth aspect of the embodiment
[0255] This application provides a timing advance determination device, which may be, for example, a terminal device, or one or more components or parts configured in a terminal device. Since the principle by which this device solves the problem is the same as the method shown in FIG. 12 of the second aspect embodiment, its specific implementation can refer to the implementation of the method shown in FIG. 12 of the second aspect embodiment, and the similarities will not be repeated.
[0256] Figure 14 is a schematic diagram of a timing advance determination device according to an embodiment of this application. As shown in Figure 14, the device 1400 includes:
[0257] Receiver 1401 receives LTM cell handover command MAC CE, which is used to indicate conditional LTM candidate cells;
[0258] The processor 1402 applies one of the timing advance amounts indicated by the LTM cell handover command MAC CE, the timing advance amounts indicated by the LTM candidate timing advance command MAC CE, or the timing advance amounts measured by the terminal equipment to the primary timing advance group (PTAG).
[0259] In some embodiments, when the timing advance indicated by the LTM cell handover command MAC CE is not set to a first value, the processor 1402 applies the timing advance to the primary timing advance group (PTAG), where the first value is FFF.
[0260] In some embodiments, when the timing advance indicated by the LTM cell handover command MAC CE is set to a first value, the processor 1402 applies the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device, to the primary timing advance group (PTAG), where the first value is FFF.
[0261] In some embodiments, when the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is running, the processor 1402 applies the timing advance amount indicated by the LTM candidate timing advance command MAC CE to the PTAG; and / or when the candidate time alignment timer associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is not running, and the terminal device has successfully measured the timing advance amount of the special cell of the target configuration, the processor 1402 applies the timing advance amount measured by the terminal device to the PTAG.
[0262] In some embodiments, if the terminal device has successfully measured the timing advance of the target configuration special cell indicated by the LTM cell handover command MAC CE, the processor 1402 applies the timing advance measured by the terminal device to the PTAG; and / or
[0263] If the terminal device is not configured to perform timing advance measurement based on the terminal device, or if the terminal device fails to successfully measure the timing advance of the target configured special cell indicated by the LTM cell handover command MAC CE, and the candidate time alignment timer associated with the special cell is running, the processor 1402 applies the timing advance indicated by the LTM candidate timing advance command MAC CE to the PTAG.
[0264] In some embodiments, upon receiving the LTM Candidate Timing Advance Command (MAC CE), the processor 1402 starts or restarts the candidate time alignment timer associated with the special cell of the candidate configuration indicated by the LTM Candidate Timing Advance Command (MAC CE), and stores the timing advance amount indicated by the LTM Candidate Timing Advance Command (MAC CE). In some embodiments, the processor 1402 determines that RACH-less LTM is in progress.
[0265] In some embodiments, when the reset of the MAC entity is a request from an upper layer, the processor performs at least one of the following:
[0266] Stop ltm-Candidate-TimeAlignmentTimers;
[0267] Stop the ltm-Candidate-TimeAlignmentTimer for the specific cell configured for the target;
[0268] Stop ltm-Candidate-TimeAlignmentTimers for LTM candidate configurations;
[0269] Do not stop ltm-Candidate-TimeAlignmentTimers or keep them running;
[0270] The ltm-Candidate-TimeAlignmentTimer for the specific cell configured for the target will either be stopped or kept running.
[0271] Do not stop ltm-Candidate-TimeAlignmentTimers for LTM candidate configurations or keep them running.
[0272] In the above embodiments, the content and format of the first MAC CE have been described in the previous embodiments and will not be repeated here.
[0273] 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 aforementioned apparatus may also include other components or modules, and for details regarding these components or modules, please refer to related technologies. Furthermore, the aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not impose any limitations on this.
[0274] The apparatus according to the embodiments of this application can be determined as one of the timing advance indicated by the PTAG application LTM cell handover command MAC CE, the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device. Thus, it can ensure that the behavior of the terminal device or MAC entity in obtaining TA is consistent and avoid UL interference.
[0275] Fifth aspect of the embodiment
[0276] This application also provides a beam determination method applied to network devices.
[0277] Figure 15 is a schematic diagram of a beam determination method according to an embodiment of this application. As shown in Figure 15, the method includes:
[0278] 1501, the network device sends information about a first beam, the information of which is included in a first media access control element (MAC CE) or F1 signaling message, and the first beam is the target beam for CLTM cell handover.
[0279] The network devices include: a gNB-CU, a source gNB-DU or serving gNB-DU, and a target gNB-DU or candidate gNB-DU. When the network device is a source gNB-DU or serving gNB-DU, it sends a first MAC CE to the UE to carry information about the first beam, and receives the initial uplink transmission or preamble from the UE from the first beam. When the network device is a gNB-CU, it sends an F1 signaling message to the source gNB-DU or serving gNB-DU, carrying information about the first beam.
[0280] The implementation method of the first MAC CE can be referred to the embodiment of the first aspect, and will not be repeated here.
[0281] 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.
[0282] This application also provides a beamforming device that can be applied to network devices. This measuring device can correspond to the method of the fifth aspect embodiment. Figure 16 is a schematic diagram of a beamforming device according to an embodiment of this application. As shown in Figure 16, the beamforming device 1600 may include:
[0283] Transmitter 1601 transmits information about a first beam, which is included in a first media access control element (MAC CE). The first beam is the target beam for CLTM cell handover. Transmitter 1601 transmits the information over the air interface.
[0284] Transmitter 1602 transmits information about a first beam, which is included in an F1 signaling message. The first beam is the target beam for CLTM cell handover. Transmitter 1602 transmits via the F1 interface. For example, it can be transmitted from the gNB-CU to (e.g., source, serving, target, or candidate) the gNB-DU, or vice versa. Implementation details can be found in the method of the fifth aspect embodiment, and will not be repeated here.
[0285] 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 beamforming device 1600 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.
[0286] Furthermore, for simplicity, Figure 16 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.
[0287] 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.
[0288] Through the above embodiments, when a conditional LTM cell handover is triggered, the target beam used to perform the initial uplink transmission to the target cell can be determined, ensuring that the terminal device can determine the target beam used for conditional LTM cell handover, avoiding interruption, and the method is simple and easy to implement.
[0289] Implementation of the sixth aspect
[0290] This application also provides a communication system, including network equipment and terminal equipment.
[0291] Referring to Figure 1, the terminal device includes the beam determination device of the third aspect embodiment and / or the timing advance determination device of the fourth aspect embodiment, and the network device includes the beam determination device of the fifth aspect embodiment. The contents that are the same as those in the embodiments of the first to fifth aspects will not be described again.
[0292] This application also provides a terminal device, which may be a UE, but this application is not limited to this and may also be other terminal devices.
[0293] Figure 17 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 17, the terminal device 1700 may include a processor 1701 and a memory 1702; the memory 1702 stores data and programs and is coupled to the processor 1701. 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.
[0294] In some embodiments, the functions of the apparatus 1300 of the third aspect embodiment and / or the apparatus 1400 of the fourth aspect embodiment can be integrated into the processor 1701, wherein the processor 1701 can be configured to execute a program to implement the method described in FIG. 6 of the first aspect embodiment and / or FIG. 12 of the second aspect embodiment, the contents of which are incorporated herein and will not be repeated here.
[0295] In other embodiments, the apparatus 1300 of the third aspect embodiment and / or the apparatus 1400 of the fourth aspect embodiment may be configured separately from the processor 1701. For example, the apparatus 1300 of the third aspect embodiment and / or the apparatus 1400 of the fourth aspect embodiment may be configured as a chip connected to the processor 1701, and the functions of the apparatus 1300 of the third aspect embodiment and / or the apparatus 1400 of the fourth aspect embodiment may be implemented by the control of the processor 1601.
[0296] As shown in Figure 17, the terminal device 1700 may further include: a communication module 1703, an input unit 1704, a display 1705, and a power supply 1706. 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 1700 does not necessarily include all the components shown in Figure 17; these components are not essential. Furthermore, the terminal device 1700 may also include components not shown in Figure 17, which can be referred to in related technologies.
[0297] This application also provides a network device, which may be, for example, a base station, but this application is not limited to this and may also be other network devices.
[0298] Figure 18 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 18, the network device 1800 may include a processor 1801 and a memory 1802; the memory 1802 is coupled to the processor 1801. The memory 1802 can store various data; in addition, it also stores information processing programs, and executes the programs under the control of the processor 1801.
[0299] In some embodiments, the functionality of the apparatus 1600 of the fifth aspect embodiment can be integrated into the processor 1801, wherein the processor 1801 can be configured to execute a program to implement the method described in FIG. 15 of the fifth aspect embodiment, the contents of which are incorporated herein and will not be repeated here.
[0300] In other embodiments, the apparatus 1600 of the fifth aspect embodiment may be configured separately from the processor 1801. For example, the apparatus 1600 of the fifth aspect embodiment may be configured as a chip connected to the processor 1801, and the functions of the apparatus 1600 of the fifth aspect embodiment may be implemented by the control of the processor 1701.
[0301] In addition, as shown in Figure 18, network device 1800 may also include transceivers 1803 and 1804. The functions of these components are similar to those in the prior art and will not be described again here. It is worth noting that network device 1800 does not necessarily need to include all the components shown in Figure 18; furthermore, network device 1800 may also include components not shown in Figure 18, which can be referred to in the prior art.
[0302] 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 method described in FIG. 6 of the first aspect embodiment and / or FIG. 12 of the second aspect embodiment.
[0303] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to perform the method described in FIG. 6 of the first aspect embodiment and / or FIG. 12 of the second aspect embodiment.
[0304] 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 FIG. 6 of the first aspect embodiment and / or FIG. 12 of the second aspect embodiment.
[0305] 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 FIG. 6 of the first aspect embodiment and / or FIG. 12 of the second aspect embodiment.
[0306] 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.
[0307] 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.
[0308] 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.
[0309] 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.
[0310] 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.
[0311] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:
[0312] 1. A beam determination method, applied to a terminal device, wherein the method includes:
[0313] When a Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered, the terminal device determines the first beam.
[0314] The terminal device performs an initial uplink transmission to the target cell according to the first beam.
[0315] 2. A method for determining timing advance, applied to a terminal device, wherein the method includes:
[0316] The terminal device receives an LTM cell handover command MAC CE, which is used to indicate a conditional LTM candidate cell.
[0317] The terminal device applies the timing advance indicated by the LTM cell handover command MAC CE to the primary timing advance group (PTAG), or the timing advance indicated by the LTM candidate timing advance command MAC CE.
[0318] 3. The method according to Appendix 2, wherein the terminal device determines that RACH-less LTM is in progress.
[0319] 4. A beam determination method applied to a network device, wherein the method includes:
[0320] The network device sends information about a first beam, which is included in a first media access control element (MAC CE) or F1 signaling message. The first beam is the target beam for CLTM cell handover.
[0321] 5. The method according to Appendix 4, wherein the method further comprises:
[0322] The network device receives the initial uplink transmission or preamble sent by the terminal device according to the first beam.
[0323] 6. A terminal device, comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement the following method:
[0324] When Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered, determine the first beam;
[0325] The initial uplink transmission is performed to the target cell based on the first beam.
[0326] 7. A terminal device, comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement the following method:
[0327] Receive LTM cell handover command MAC CE, which is used to indicate conditional LTM candidate cells;
[0328] The timing advance is one of the following: the timing advance indicated by the LTM cell handover command MAC CE, the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal equipment.
[0329] 8. A network device comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement the following method:
[0330] Send information about the first beam, which is included in the first media access control element (MAC CE) or F1 signaling message. The first beam is the target beam for CLTM cell handover.
[0331] 9. A communication system, wherein the communication system includes the terminal equipment described in Appendix 6 and / or Appendix 7 and the network equipment described in Appendix 8.
Claims
1. A beamforming device, configured in a terminal device, wherein, The device includes: The processor determines the first beam when a Conditional Layer 1 / 2 Triggered Mobility (CLTM) cell handover is triggered; The transmitter performs an initial uplink transmission to the target cell based on the first beam.
2. The apparatus according to claim 1, wherein, The processor determines the first beam based on implementation; and / or, The processor determines the first beam based on beam quality; and / or, The processor selects the beam associated with the active Transmission Configuration Indicator state (TCI state) as the first beam; and / or, The processor selects the beam configured with the Configuration Grant occasion (CG occasion) as the first beam.
3. The apparatus according to claim 2, wherein, The processor determines the first beam based on beam quality, including: The processor selects the beam with the best beam quality or the beam with a beam quality higher than a first threshold as the first beam.
4. The apparatus according to claim 3, wherein, The first threshold is configured by the network device, and / or the first threshold is related to a preset threshold for a Layer 3 measurement event that triggers cell handover.
5. The apparatus according to claim 1, wherein, The device further includes: The receiver receives a first Media Intervention Control Element (MAC CE), the first MAC CE including information for indicating the first beam.
6. The apparatus according to claim 5, wherein, Information used to indicate the first beam includes a TCI state identifier (ID), wherein the first beam is the beam corresponding to the TCI state indicated by the TCI state ID.
7. The apparatus according to claim 5, wherein, The first MAC CE is the LTM candidate timing advance command MAC CE.
8. The apparatus according to claim 1, wherein, The CLTM cell handover is triggered by Layer 3 measurement.
9. The apparatus according to claim 1, wherein, The processor determines the CG occasion based on the first beam, and the transmitter performs the initial uplink transmission for RACH-less CLTM cell handover on the CG occasion.
10. The apparatus according to claim 9, wherein, The processor determines the CG occasion based on the first beam, including: The processor determines the CG occasion based on the uplink grant associated with the reference signal associated with the TCI state indicated by the first MAC CE; or The processor determines the CG occasion based on the uplink grant associated with the reference signal associated with the first beam.
11. The apparatus according to claim 1, wherein, When the reference signal associated with the first beam is not configured with a CG, the processor executes a random access procedure.
12. The apparatus according to claim 11, wherein, The transmitter performs a random access procedure on the first beam or a second beam different from the first beam, or the processor performs a random access procedure based on the random access resources and / or preamble indicated by the first MAC CE.
13. A timing advance determination device, configured in a terminal device, the device comprising: The receiver receives an LTM cell handover command MAC CE, which indicates a conditional LTM candidate cell. The processor applies one of the timing advance indicated by the LTM cell handover command MAC CE to the primary timing advance group (PTAG), or the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device.
14. The apparatus according to claim 13, wherein, When the timing advance indicated by the LTM cell handover command MAC CE is not set to the first value, the processor applies the timing advance to the primary timing advance group (PTAG), where the first value is FFF.
15. The apparatus according to claim 13, wherein, When the timing advance indicated by the LTM cell handover command MAC CE is set to a first value, the processor applies the timing advance indicated by the LTM candidate timing advance command MAC CE, or the timing advance measured by the terminal device, to the primary timing advance group (PTAG), where the first value is FFF.
16. The apparatus according to claim 15, wherein, When the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) associated with the specific cell of the target configuration indicated by the LTM cell handover command MAC CE is running, the processor applies the timing advance amount indicated by the LTM candidate timing advance command MAC CE to the PTAG; and / or If the candidate time aligner associated with the special cell of the target configuration indicated by the LTM cell handover command MAC CE is not running, and the terminal device has successfully measured the timing advance of the special cell of the target configuration, the processor applies the timing advance measured by the terminal device to the PTAG.
17. The apparatus according to claim 15, wherein, If the terminal device has successfully measured the timing advance of the target configured special cell indicated by the LTM cell handover command MAC CE, the processor applies the timing advance measured by the terminal device to the PTAG; and / or If the terminal device is not configured to perform timing advance measurement based on the terminal device, or if the terminal device fails to successfully measure the timing advance of the target configured special cell indicated by the LTM cell handover command MAC CE, and the candidate time alignment timer associated with the special cell is running, the processor applies the timing advance indicated by the LTM candidate timing advance command MAC CE to the PTAG.
18. The apparatus according to claim 16 or 17, wherein, Upon receiving the LTM Candidate Timing Advance Command (MAC CE), the processor starts or restarts the candidate time alignment timer associated with the special cell of the candidate configuration indicated by the LTM Candidate Timing Advance Command (MAC CE), and stores the timing advance amount indicated by the LTM Candidate Timing Advance Command (MAC CE).
19. The apparatus according to claim 16 or 17, wherein, The processor starts or restarts the time alignment timer associated with the PTAG, which uses the length of the remaining time until the timeout of the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) of the special cell configured for the target, or uses the length configured by the network device.
20. The apparatus according to claim 13, wherein, If the reset of the MAC entity is a request from an upper layer, the processor performs at least one of the following: Stop the candidate time alignment timers (ltm-Candidate-TimeAlignmentTimers); Stop the candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) for the special cell configured for the target. Stop the candidate time alignment timers (ltm-Candidate-TimeAlignmentTimers) for LTM candidate configurations; Do not stop the candidate time alignment timers (ltm-Candidate-TimeAlignmentTimers) or keep them running; The candidate time alignment timer (ltm-Candidate-TimeAlignmentTimer) for the special cell configured for the target should either not be stopped or should be kept running. Do not stop the candidate time alignment timers (ltm-Candidate-TimeAlignmentTimers) for the LTM candidate configuration, or keep them running.
