Method for processing double event conditional trigger

Abstract

The embodiment of the application provides a kind of double event condition trigger processing method, this method includes: terminal UE is according to the time when the first event trigger condition is satisfied and the time when the second event trigger condition is satisfied, the first event and / or second event triggered are executed;Wherein, the first event includes conditional switching event, and the second event includes conditional primary / secondary cell addition change event.By the embodiment of the application, the problem that flexibility is poor and efficiency is low in the UE switching and management process in the related art is solved.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a processing method for dual-event condition triggering. Background Technology

[0002] In 5G NR (new radio), with increasing network complexity and user demands, conditional handover (CHO), conditional primary / secondary cell (PSCell) addition / change (CPA / C), and subsequent addition / change are crucial functions for both the network and the user side, enhancing the reliability and efficiency of user mobility management. These mechanisms, by pre-configuring candidate targets and triggering conditions, ensure reliable handover in highly dynamic scenarios, significantly improving the mobility management capabilities of 5G networks.

[0003] In LTE and early 5G, handover is typically network-triggered. The user equipment (UE) executes the handover command immediately upon receiving it. This network-triggered handover is prone to failure in highly dynamic scenarios, especially under conditions of rapid signal fading or significant interference. Handover Notice (CHO), introduced in 5G NR, is an enhanced handover mechanism designed to reduce the likelihood of failure by pre-configuring multiple handover candidate targets. Specifically, the UE autonomously decides to perform a handover when specific conditions (such as signal thresholds or timing requirements) are met. First, the network configures CHO information, including a list of candidate cells, handover triggering conditions, and handover commands. Then, the UE periodically evaluates the signal quality of the current serving cell and candidate cells according to the network-configured measurement rules. Once the conditions are met, the UE stops communication with the source cell and performs random access to the target cell to complete the handover. After the handover is complete, the UE sends a handover completion message to the network.

[0004] In traditional primary SCell (PSCell) management, PSCell handover requires active network triggering, resulting in high signaling overhead and insufficient timeliness. In fast-moving or complex wireless environments, the signal quality of PSCell may degrade rapidly, leading to a decline in user experience or even connection interruption. In addition, in high-load or high-speed moving scenarios, secondary nodes (SNs) may need to dynamically replace PSCells or add new PSCells. Summary of the Invention

[0005] This application provides a dual-event condition-triggered processing method to at least solve the problems of poor flexibility and low efficiency in UE handover and management processes in related technologies.

[0006] According to one embodiment of this application, a dual-event condition-triggered processing method is provided, comprising: a terminal UE executing a triggered first event and / or a second event based on the satisfaction time of a first event triggering condition and the satisfaction time of a second event triggering condition; wherein the first event includes a condition switching event and the second event includes a condition primary / secondary cell addition / change event.

[0007] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the steps in the above method embodiments when it is run.

[0008] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in the above method embodiments.

[0009] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0010] Through the above embodiments of this application, due to the dynamic changes in channel conditions, the triggering conditions of the first event and the second event may not be met at the same time. This allows the UE to execute the first event and / or the second event according to the time when the triggering conditions of the first event and the second event are met, which solves the problem of poor flexibility and low efficiency in the UE handover and management process in related technologies. It enables more flexible execution of the first event and the second event, thereby improving the timeliness and accuracy of handover decisions. Attached Figure Description

[0011] Figure 1 This is a hardware structure block diagram of a computer terminal for a dual-event condition-triggered processing method according to an embodiment of this application.

[0012] Figure 2 This is a flowchart of a dual-event condition triggering processing method according to an embodiment of this application;

[0013] Figure 3 This is a structural block diagram of a dual-event condition-triggered processing device according to an embodiment of this application;

[0014] Figure 4 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 1 ;

[0015] Figure 5 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 2 ;

[0016] Figure 6 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 3 ;

[0017] Figure 7 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 4 ;

[0018] Figure 8 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 5 ;

[0019] Figure 9 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 6 ;

[0020] Figure 10 This is a schematic diagram of a dual-event condition-triggered processing method according to an embodiment of this application. Figure 7 . Detailed Implementation

[0021] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0022] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0023] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of the mobile terminal used in the embodiments of the method of this application. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0024] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the dual-event condition-triggered processing method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the aforementioned method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0025] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0026] This embodiment provides a dual-event condition triggering processing method running on the aforementioned mobile terminal. Figure 2 This is a flowchart of a dual-event condition-triggered processing method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0027] Step S202: The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition is met and the time when the second event triggering condition is met; wherein, the first event includes a condition handover event and the second event includes a condition primary / secondary cell addition / change event.

[0028] In an exemplary embodiment of this application, the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: when the first event triggering condition and the second event triggering condition are met at different times, and the time difference between the time when the first event triggering condition is met and the time when the second event triggering condition is met does not exceed a preset time window, the UE executes the triggered first event and second event.

[0029] In an exemplary embodiment of this application, the UE executes the triggered first event and second event, including: if the first event triggering condition is met, the UE temporarily does not execute the first event and evaluates whether the second event triggering condition is met; if the second event triggering condition is met within a first preset time window, the UE executes the first event and the second event; if the second event triggering condition is not met within the first preset time window, the UE stops evaluating the second event triggering condition; if the second event triggering condition is met, the UE temporarily does not execute the second event and evaluates whether the first event triggering condition is met; if the first event triggering condition is met within a second preset time window, the UE executes the first event and the second event; if the first event triggering condition is not met within the second preset time window, the UE stops evaluating the first event triggering condition.

[0030] By allowing the UE to temporarily not execute the event immediately after the first event triggering condition is met, but instead continue to evaluate the triggering condition of the second event, the UE has the opportunity to wait for the second event to also meet the condition within a short period of time (within the first preset time window), so that the handover can be performed simultaneously when both event conditions are met, avoiding the additional delay caused by step-by-step operation.

[0031] The introduction of a time window mechanism allows the UE to flexibly evaluate and wait for the triggering conditions of the second event within a certain time range. This flexibility increases the possibility of simultaneously meeting the conditions of both events under non-ideal conditions (such as rapid signal changes or coverage edge handover), thereby enhancing the reliability and success rate of dual-event triggered handover.

[0032] In one embodiment, the first preset time window is Xs and the second preset time window is Ys.

[0033] In an exemplary embodiment of this application, the UE executes a triggered first event and a second event, including: if the triggering condition of the first event is met, the UE executes the first event and evaluates whether the triggering condition of the second event is met; if the triggering condition of the second event is met within a first preset time window, the UE executes the second event; if the triggering condition of the second event is not met within the first preset time window, the UE stops evaluating the second event.

[0034] In an exemplary embodiment of this application, the UE executes a triggered first event and a second event, including: if the triggering condition of the second event is met, the UE executes the second event and evaluates whether the triggering condition of the first event is met; if the triggering condition of the first event is met within a second preset time window, the UE executes the first event; if the triggering condition of the first event is not met within the second preset time window, the UE stops evaluating the first event.

[0035] In an exemplary embodiment of this application, the method further includes: the UE receiving Radio Resource Control (RRC) signaling sent by the Network (NW) side, wherein the RRC signaling is used to indicate a first preset time window and a second preset time window, the values ​​of the first preset time window and the second preset time window are determined by the NW according to the current channel state, and the values ​​are not greater than the cell measurement period; wherein the cell measurement period includes at least one of the following: co-frequency cell with index identification period, co-frequency cell without index identification period, inter-frequency cell without index identification period, and inter-frequency cell with index identification period.

[0036] In an exemplary embodiment of this application, the method further includes: the UE receiving Medium Access Control (MAC) Control Element (CE) signaling sent by the NW side, wherein the MAC CE signaling is used to indicate a first preset time window and a second preset time window, and one or two fields of the MAC CE signaling are used together or separately to indicate the values ​​of the first preset time window and the second preset time window.

[0037] In an exemplary embodiment of this application, the method further includes: the UE receiving UE function signaling sent by the NW side, wherein one or two components of the UE function signaling are used to indicate a first preset time window and a second preset time window.

[0038] In an exemplary embodiment of this application, the method further includes: the UE receiving downlink control information (DCI) signaling sent by the NW side, wherein the DCI signaling is used to indicate a first preset time window and a second preset time window.

[0039] In an exemplary embodiment of this application, the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: when the first event condition and the second event condition are met at the same time, the UE executes the triggered first event and second event at the next time.

[0040] In an exemplary embodiment of this application, the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: when the first event triggering condition is met and the second event triggering condition is not met at the same time, the UE executes the triggered first event and ends the evaluation of the execution conditions of the second event.

[0041] In an exemplary embodiment of this application, the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: when the first event triggering condition is not met and the second event triggering condition is met at the same time, the UE executes the triggered second event and ends the evaluation of the first event execution condition.

[0042] In an exemplary embodiment of this application, the method further includes: if the first event triggering condition or the second event triggering condition is not met at the same time, the evaluation of the first event and the second event execution conditions is terminated.

[0043] In an exemplary embodiment of this application, the terminal UE executes a triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: when the first event triggering condition and the second event triggering condition are met at different times, the UE executes the first event or the second event according to NW signaling sent by the NW side; wherein, the NW signaling includes at least one of the following: RRC signaling, MAC CE signaling, DCI signaling and UE function signaling.

[0044] In an exemplary embodiment of this application, the UE executes a first event or a second event according to NW signaling sent by the NW side, including: when the NW signaling indicates that only the first event is to be executed, the UE executes the first event when the triggering condition of the first event is met; when the NW signaling indicates that only the second event is to be executed, the UE executes the second event when the triggering condition of the second event is met; when the NW signaling indicates that only events that meet the conditions are to be executed, the UE executes the first event or the second event according to the principle of first-to-first-to-be-met.

[0045] In an exemplary embodiment of this application, the method further includes: when there is no event execution indication in the NW signaling, the UE executes the first event and the second event when both the first event triggering condition and the second event triggering condition are met simultaneously.

[0046] In an exemplary embodiment of this application, before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, the method further includes: the UE performing early synchronization according to the received DCI command; wherein, the DCI command is used to instruct early synchronization of the Master Cell Group (MCG) and the Secondary Cell Group (SCG), the DCI command includes a cell indicator field and a master / secondary cell indicator field, the master / secondary cell indicator field is used to indicate the cell number in the SCG that needs to perform early synchronization, and the number of bits occupied by the master / secondary cell indicator field is [number missing]. C1 represents the number of cells in the SCG that require early synchronization.

[0047] In an exemplary embodiment of this application, before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, the method further includes: the UE performing early synchronization according to the received first DCI command and second DCI command; wherein, the first DCI command is used to indicate the early synchronization of the MCG, the first DCI command includes a first cell indicator field, the first cell indicator field is used to indicate the cell number in the MCG that needs to perform early synchronization, and the first cell indicator field occupies 100 bits. C represents the number of cells in the MCG that require early synchronization; wherein, the second DCI command is used to indicate early synchronization of the SCG, and the second DCI command includes a second cell indicator field, which is used to indicate the cell number in the SCG that requires early synchronization, and the second cell indicator field occupies 100 bits. C is the number of cells in the SCG that need to perform early synchronization.

[0048] In an exemplary embodiment of this application, the first event further includes at least one of the following: a Conditional LTM PCell switch (CLPS) event triggered by the Conditional Physical Layer / Radio Resource Control Layer, a subsequent Conditional Switching SCHO event, and a subsequent Conditional (L1 / L2 triggered mobility, LTM) Primary Cell Switching SCLPS event; wherein the second event further includes at least one of the following: a Conditional LTM Primary / Secondary Cell Switching CLPSS event, a subsequent Conditional Primary / Secondary Cell Addition / Change SCPA / C event, and a subsequent Conditional LTM Primary / Secondary Cell Switching SCLPSS event.

[0049] In an exemplary embodiment of this application, before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, the method further includes: receiving a configuration from the network side that supports the parallel triggering and execution of the first event and the second event.

[0050] This application provides a method for handling situations where the conditions for two events are met with a time difference when the events are triggered by dual events. Additionally, it describes how to configure early synchronization of dual events when early synchronization is supported.

[0051] Through the above embodiments of this application, due to the dynamic changes in channel conditions, the triggering conditions of the first event and the second event may not be met at the same time. This allows the UE to execute the first event and / or the second event according to the time when the triggering conditions of the first event and the second event are met, which solves the problem of poor flexibility and low efficiency in the UE handover and management process in related technologies. It enables more flexible execution of the first event and the second event, thereby improving the timeliness and accuracy of handover decisions.

[0052] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0053] This embodiment also provides a dual-event condition-triggered processing device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0054] Figure 3 This is a structural block diagram of a dual-event condition-triggered processing apparatus according to an embodiment of this application, such as... Figure 3 As shown, the device includes an execution module 10, which is used to execute the triggered first event and / or second event according to the time when the first event triggering condition is met and the time when the second event triggering condition is met; wherein, the first event includes a condition switching event and the second event includes a condition primary / secondary cell addition / change event.

[0055] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to these: the above modules are located in the same processor.

[0056] To facilitate understanding of the technical solutions provided in the application embodiments, the following description is based on specific scenario embodiments.

[0057] To improve network performance and user experience, in 5G NR dual-connectivity or MR-DC scenarios, the primary cell (PCell) and / or (primary SCG cell) PSCell may handover when signal quality falls below a certain threshold. For example, when a UE moves to the coverage edge of its current PCell and / or PSCell, it needs to hand over to a cell with better signal. Simultaneously, to reduce handover latency and the ping-pong effect, conditional handover is typically used in high-mobility and complex environments. The UE pre-configures multiple candidate target cells and autonomously hands over when conditions are met, comprehensively considering signal quality and load conditions to select the most suitable target cell. Based on these two technologies, to further improve service performance in mobile scenarios, it is necessary to consider situations where the PCell and PSCell need to change simultaneously under conditional handover, such as when conditional PCell handover and conditional PSCell addition / change are configured simultaneously. For such dual-event triggered measurements, it is necessary to consider how the UE performs measurements when both conditions are not simultaneously met. Furthermore, in current LTM measurements, to reduce handover latency, early synchronization (early sync) is supported before cell handover is triggered. Specifically, this includes early DL sync and early UL sync, triggered by the TCI state activation command and PDCCH order, respectively. However, currently only the early synchronization configuration of one cell group (MCG or SCG) is considered. To further reduce latency and signaling overhead, we can consider how to complete the early synchronization configuration when two cell groups change.

[0058] CPAC, a condition-driven mechanism for adding or replacing PSCells, has been introduced into 5G NR. This mechanism allows the network to pre-configure multiple candidate PSCells, with the UE (User Equipment) autonomously triggering corresponding operations based on predefined conditions. By implementing dynamic addition or replacement of PSCells through this condition-triggered mechanism, the limitations of traditional PSCell management in dynamic scenarios are overcome, significantly improving network reliability and user experience.

[0059] Based on the aforementioned technologies, the R18 mobility study considered dual-event triggered handover based on Layer 3 measurements, namely conditional handover with candidate PSCell addition / change. In the DC scenario, PCell and PSCell work together, combined with CHO and CPA / C, to ensure that the UE maintains a connection with the optimal PSCell throughout the handover process. However, the current requirements for dual-event triggered scenarios are quite strict; both events must be met simultaneously to trigger the overall process. This can easily lead to situations where the UE does not execute the network configuration for an extended period, failing to achieve the goal of shortening handover latency. Furthermore, with the introduction of Layer 1 measurements (LTM), conditional handover should also be considered to ensure network performance and user experience, i.e., CLTM or subsequent CLTM (subsequent conditional Layer 1 triggered mobility management).

[0060] In addition, in the discussion of R18 LTM, in order to reduce cell handover latency, uplink and downlink synchronization is completed in advance based on UE capabilities before receiving the cell handover command, avoiding timing operations and RACH transmission in subsequent handover operations, effectively shortening the interruption time. Currently, only the early synchronization configuration of one cell group (MCG or SCG) is considered. To further reduce latency and signaling overhead, we can consider how to complete the early synchronization configuration when two cell groups change.

[0061] Scenario Example 1

[0062] This scenario example involves switching of layer 3 conditional PCells and adding / changing conditional PSCells.

[0063] In this scenario embodiment, after the network completes the configuration of conditional PCell handover with conditional PSCell addition / change via RRC command, it means that the network supports the parallel triggering and execution of the CHO and CPA / C events. However, due to changes in channel conditions or factors such as PCell and PSCell measurement offsets, the condition fulfillment points of these two processes may not be aligned in the time domain. Possible scenarios include: 1) simultaneous fulfillment, 2) CHO event condition fulfillment first, and 3) CPA / C event condition fulfillment first. For these possible scenarios, it is necessary to standardize the UE's behavior to ensure that both the UE and NW sides have the same understanding of the event progression. The following methods can be used to standardize the UE's behavior:

[0064] Method 1: The conditions for both events must be met at the same time;

[0065] Method 2: The conditions for the two events are met at different times and are handled according to the time priority principle;

[0066] Method 3: The two event conditions are met at different times and processed according to the NW configuration;

[0067] Method 4: The two event conditions are met at different times, and a time window is set for constraint;

[0068] Method 5: Depends on the UE implementation.

[0069] Regarding Method 1, its use cases are strictly limited. The two processes are only allowed to be executed when the conditions of the two events are met simultaneously at the same time.

[0070] Specifically, such as Figure 4 As shown, at time t0, handover conditions are configured, including the conditions that must be met for CHO and CPAC triggering. After the conditions are configured, the NW monitors the channel and evaluates whether the event triggering conditions are met based on the measurement results reported by the UE. For example, at time t1, the CHO condition is met, but the CPA / C condition is not met. According to Method 1, no procedure can be triggered at this time (here, the procedure refers to the measurement of the target PCell after the CHO condition is met and the measurement of the target PSCell after the CPA / C condition is met). The NW continues to monitor the channel and evaluate. At time t2, the CPA / C condition is met, but the CHO condition is not met. At this time, no procedure can be triggered. At time t3, both the CHO and CPA / C conditions are met, triggering the overall procedure. The UE can then perform the measurement of the target PCell and the target PSCell at the next time step.

[0071] Regarding Method 2, the restrictions on the measurement scenario are relaxed, and the two events can be met at different times, with one of them selected for target cell measurement based on the time priority principle.

[0072] If the triggering conditions for both events are met simultaneously, subsequent measurements for the events can be executed directly. If the triggering conditions for both events are not met simultaneously, a first-come, first-served principle applies. Once either event meets its triggering condition, the measurement of the corresponding target cell is performed directly, and events that do not meet their conditions will not undergo further condition evaluation. Specifically, if the CHO is met first, the UE directly executes the measurement of the target PCell and ends the condition evaluation for the CPA / C; if the CPA / C is met first, the UE directly executes the measurement of the target PSCell and ends the condition evaluation for the CHO.

[0073] like Figure 5As shown, at time t0, condition configuration is performed, including the conditions that must be met for CHO and CPA / C triggering. After the condition configuration is completed, the NW performs channel monitoring and evaluates whether the event triggering conditions are met based on the measurement results reported by the UE. For example, at time t1, the CHO condition is met, but the CPA / C condition is not met. According to the current method, the UE directly executes the measurement of targetPCell and ends the evaluation of the CPA / C execution conditions. The measurement evaluation of this process ends. If a re-evaluation is required, the NW needs to reconfigure. Similarly, if the CPA / C condition is met, but the CHO condition is not met, the UE directly executes the measurement of targetPSCell and ends the evaluation of the CHO execution conditions.

[0074] Regarding method 3, if the conditions of the two events are not met at the same time, you can fall back to single-event according to the NW configuration, that is, only one event needs to be executed at present, CHO or CPA / C.

[0075] If the triggering conditions for both events are met simultaneously, subsequent measurements can be executed directly. If the triggering conditions for both events are not met simultaneously, a command needs to be designed to indicate whether a fallback from dual-event triggering to single-event triggering is possible if the conditions are not met. This command can be carried by RRC signaling, MAC CE, or DCI, or it can be designed as a UE capability (function). Specifically, when configuring / after configuring the event triggering conditions, the NW sends a command to the UE to control the UE's measurement behavior based on factors such as service priority or channel conditions. This command contains four fields: CHO-only, CPAC-only, Execute-only, and Execute-both. The UE completes the subsequent measurement process according to the field indications in the command.

[0076] Specifically, the possible states and UE behaviors are as follows:

[0077] If the command indicates CHO-only, the UE will directly perform the measurement of the target PCell if the CHO is satisfied, without enabling / disabling the evaluation of the execution conditions of the CPAC.

[0078] If the command indicates CPAC-only, the UE will directly perform the measurement of the target PSCell if CPA / C is satisfied, without enabling / disabling the evaluation of the execution conditions of CPAC.

[0079] If the command specifies Execute-only, it will be executed according to the first-come-first-served principle.

[0080] If the command specifies Execute-both, it will be executed according to the principle of simultaneous satisfaction.

[0081] Regarding method 4, if the two event conditions are not met at the same time, but the time difference between the two condition fulfillment points does not exceed a certain value, parallel processing can still be performed. The NW has already configured the trigger conditions for both events. If they can be met simultaneously, the overall process can begin at the same time, i.e., the measurement of target PCell and target PSCell. If they cannot be met simultaneously, a time window can be introduced. By setting the length of the time window, the validity of the event that meets the condition first can be guaranteed, while the probability of the event that meets the condition later can be increased, minimizing the possibility of the NW being configured but the UE not executing the process. Specifically, the time window design can include the following two cases:

[0082] If the condition for a certain event is met first, the measurement of the UE in that event is postponed for no more than X seconds, and the measurement and condition evaluation of the other event continue. If the subsequent event also meets the condition within X seconds, the two events can be executed simultaneously. Specifically, for example... Figure 6 and Figure 7 As shown:

[0083] If the CHO trigger condition is met, the measurement of the target PCell is postponed and the evaluation of the CPA / C event continues. Within Xs, if the CPA / C trigger condition is met, the measurement of both the target PCell and the target PSCell begins; otherwise, the measurement of the target PCell is performed and the evaluation of the CPA / C event stops.

[0084] If the triggering condition of CPA / C is met first, the measurement of the target PSCell is postponed and the evaluation of the CHO event continues. Within Ys, if the triggering condition of CHO is met, the measurement of both the target PCell and the target PSCell begins; otherwise, the measurement of the target PSCell is performed and the evaluation of the CHO event stops.

[0085] If the conditions for a certain event are met first, the UE measurement for that event is executed, and the measurement and condition evaluation for the next event continue. If the conditions for a subsequent event are also met within Xs, the UE measurement for the subsequent event is executed directly. Specifically, for example... Figure 8 and 9 As shown:

[0086] If the CHO trigger condition is met, the measurement of the target PCell is executed, and the evaluation of the CPA / C event continues. Within Xs, if the CPA / C trigger condition is met, the measurement of the target PSCell is executed; otherwise, the measurement of the target PCell continues and the evaluation of the CPA / C event stops.

[0087] If the triggering condition of CPA / C is met first, the measurement of the target PSCell is executed and the evaluation of the CHO event continues. Within Ys, if the triggering condition of CHO is met, the measurement of the target PCell is executed; otherwise, the measurement of the target PSCell is executed and the evaluation of the CHO event is stopped.

[0088] Specifically, the design of time windows Xs and Ys can refer to the following methods:

[0089] Method 4-1: RRC;

[0090] Method 4-2: MAC CE;

[0091] Method 4-3: UE capability (functionality);

[0092] Method 4-4: DCI.

[0093] Regarding method 4-1, design an RRC signaling message for downlink message transmission according to the ASN.1 protocol requirements to complete the reporting of Xs and Ys values. Design a signaling message containing the following information:

[0094] Validity-duration-X — This represents the time Xs that the CHO can wait for the CPAC, i.e., the maximum remaining evaluation time of the CPA / C after the CHO conditions are met / executed.

[0095] Validity-duration-Y — This represents the time Ys that CPAC can wait for CHO, i.e., the maximum remaining evaluation time for CHO after the CPA / C conditions are met / executed.

[0096] Xs refers to PCcell, and Ys refers to PSCell.

[0097] The network can determine the values ​​based on the current channel conditions. If the channel conditions change rapidly, the values ​​of Xs and Ys can be reduced. Typically, a measurement period is adopted, which is less than Tidentify intra with index (intra-frequency cell identification period with index), Tidentify_intra_without_index (intra-frequency cell identification period without index), Tidentify_inter_without_index (inter-frequency cell identification period without index), or Tidentify_inter_with_index (inter-frequency cell identification period with index).

[0098] Regarding method 4-2, the NW can configure the Xs and Ys values ​​via the MAC CE carrying relevant commands. First, the values ​​of Xs and Ys are related to the measurement period, with selectable values ​​including [0, 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, 320ms], and other values ​​are not excluded. One or two fields are set in the MAC CE to indicate the Xs and Ys values ​​together or separately. After receiving the MAC CE, the UE decodes it to obtain the Xs and Ys values ​​and operates according to the NW configuration. Specifically, the above information can be reported by setting a new MAC CE format or by utilizing reserved bits in an existing MAC CE.

[0099] Regarding method 4-3, a UE capability is introduced, which can be named TimeWaitForBothExecute (the time to wait for both to execute). This capability contains two components: one for representing the value of Xs, and the other for representing the value of Ys. The candidate values ​​for Xs and Ys are [0, 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, 320ms], and other values ​​are not excluded. Alternatively, a single component can be used to indicate both the values ​​of Xs and Ys.

[0100] Regarding method 4-4, the UE can send configuration information for the Xs and Ys values ​​to the UE via the DCI carried on the downlink control channel or downlink data channel. After receiving the DCI, the UE obtains the Xs and Ys values ​​and operates according to the NW configuration.

[0101] Regarding method 5, it depends on the UE implementation:

[0102] Regarding dual-event triggering, if the conditions for both events are met simultaneously, the execution of both events will begin at the same time; if the conditions are not met simultaneously, whether to wait or execute according to priority depends on the UE implementation. The UE can choose to execute one or all of the processes, and the NW will judge the UE behavior based on the UE's reported results.

[0103] In current LTM measurements, to reduce handover latency, early synchronization (early sync) is supported before cell handover is triggered. This includes early DL sync (early downlink synchronization) and early UL sync (early uplink synchronization), triggered by the TCI state activation command (Transmission Configuration Indicator, TCI) and PDCCH order, respectively. However, currently only early synchronization configuration for one cell group (MCG or SCG) is considered. To further reduce latency and signaling overhead, we can consider how to complete early synchronization configuration when two cell groups change. Specifically, the following two configurations can be considered:

[0104] MCG and SCG communicate using the same command. Specifically, in the current DCI format 1-0 design, in addition to the existing cell indicator, a PSCell indicator field (primary / secondary cell indicator field) is added to indicate the cell number in the SCG that needs to perform early synchronization. The design concept of the PSCell indicator field is the same as that of the Cell indicator field, occupying 100 bits. C1 represents the number of cells in the SCG that need to perform early synchronization.

[0105] The MCG and SCG communicate via different commands. Specifically, two commands are sent to indicate the cell numbers in the MCG and SCG that require early synchronization, without occupying reserved fields in the current DCI format 1-0. The cell indicator in both commands follows the current TS 38.212 protocol design, occupying [number] bits. For MCG, C is the number of cells in MCG that need to perform early sync; for SCG, C is the number of cells in SCG that need to perform early sync.

[0106] The above methods can be applied to: switching triggered by L1 measurement, switching of (subsequent) conditions triggered by L1 measurement, switching triggered by L3 measurement, and switching of (subsequent) conditions triggered by L3 measurement.

[0107] Scenario Example 2

[0108] This scenario embodiment involves switching of layer 1 conditional PCells and adding / changing of conditional PSCells.

[0109] Regarding L1, the current terminology for handover is LTM PCell / PSCell cell switch, and conditional handover is collectively referred to as Conditional LTM. Once the network completes the configuration of conditional PCell cell switch with conditional PSCell cell switch via RRC or MAC CE, it means that the network supports the parallel triggering and execution of both CLPS (conditional PCell cell switch) and CLPSS (conditional PSCell cell switch) events. However, due to changes in channel conditions or factors such as PCell and PSCell measurement offsets, the condition fulfillment points of these two processes may not be aligned in the time domain. Possible scenarios include: 1) simultaneous fulfillment, 2) CLPS event condition fulfillment first, and 3) CLPSS event condition fulfillment first. For these possible scenarios, it is necessary to standardize UE behavior to ensure that the UE and NW sides have the same understanding of the event progression. The following methods can be used to standardize UE behavior:

[0110] Method 1: The two event conditions must be met at the same time;

[0111] Method 2: The conditions for the two events are met at different times and are handled according to the time priority principle;

[0112] Method 3: The two event conditions are met at different times and processed according to the NW configuration;

[0113] Method 4: The two event conditions are met at different times, and a time window is set for constraint;

[0114] Method 5: Depends on the UE implementation.

[0115] Compared to Layer 3 conditional PCell switching and conditional PSCell addition / change, the main feature of this embodiment is that whether the triggering event condition is met is evaluated based on L1 measurement results, rather than L3 measurement results, thereby saving measurement latency. Similar to Layer 3 conditional PCell switching and conditional PSCell addition / change, the above method is also applicable to Layer 1 conditional PCell switching and conditional PSCell addition / change.

[0116] The specific difference is that CHO and CPA / C are replaced with CLPS and CLPSS, which will not be elaborated here.

[0117] It's important to note that the time window length setting in Method 4 needs to be related to the L1 measurement period. That is, compared to L3, the candidate value here can be smaller. Additionally, considering design overhead, there are two ways to configure the time window:

[0118] L1 and L3 use a single signaling or a set of UE capabilities, which includes all window length configurations for L1 and L3.

[0119] L1 is defined separately from L3, and the window length is configured independently using the steps of method four in scenario example one.

[0120] Consider how to configure early synchronization when two cell groups change. Specifically, consider the following two configurations: MCG and SCG are instructed by the same command; MCG and SCG are instructed by different commands.

[0121] Scenario Example 3

[0122] This scenario example involves switching of Layer 3 Subsequent conditional PCells and adding / changing of conditional Subsequent PSCells.

[0123] If the network supports subsequent conditional PCell handover with subsequent conditional PSCell addition / change in its initial configuration, it means that the network supports the parallel triggering and execution of two events: SCHO (subsequent conditional PCell handover) and SCPA / C (subsequent conditional PSCell addition / change). However, due to changes in channel conditions or measurement offsets between PCell and PSCell, the condition fulfillment points of these two processes may not be aligned in the time domain. Possible scenarios include: 1) simultaneous fulfillment, 2) SCHO event condition fulfillment first, and 3) SCPA / C event condition fulfillment first. For these possible scenarios, it is necessary to standardize the UE's behavior to ensure that both the UE and NW sides have the same understanding of the event progression. The following methods can be used to standardize the UE's behavior:

[0124] Method 1: The conditions for both events must be met at the same time;

[0125] Method 2: The conditions for the two events are met at different times and are handled according to the time priority principle;

[0126] Method 3: The two event conditions are met at different times and processed according to the NW configuration;

[0127] Method 4: The two event conditions are met at different times, and a time window is set for constraint;

[0128] Method 5: Depends on the UE implementation.

[0129] Compared to Layer 3 conditional PCell switching and conditional PSCell addition / change, the main feature of this embodiment is that it does not require event trigger condition configuration, but directly uses the existing condition configuration, thereby saving signaling overhead. Similar to Layer 3 conditional PCell switching and conditional PSCell addition / change, the above method also applies to Layer 3 Subsequent conditional PCell switching and conditional Subsequent PSCell addition / change. The specific difference is that CHO and CPA / C are replaced with SCHO and SCPA / C, and event trigger condition configuration is not considered in subsequent processes; this will not be elaborated further here.

[0130] like Figure 10 As shown, the time difference between the first event fulfillment time and the end point of the preceding process in subsequent evaluations also needs to be considered. If, in subsequent evaluations, the time interval between the first event condition fulfillment time and the handover completion time of the previous process exceeds Zs, the initial condition configuration may no longer be applicable, and all subsequent evaluations must be abandoned. Specifically, during subsequent evaluations, if the time t3 between the CHO condition fulfillment time or the CPAC condition fulfillment time and the previous process completion time t2 is less than Zs, then subsequent operations can continue; otherwise, evaluations and subsequent operations will not be performed. Zs can be configured via RRC signaling, MACCE, UE capability, or DCI.

[0131] Consider how to configure early synchronization when two cell groups change. Specifically, consider the following two configurations: MCG and SCG are instructed by the same command; MCG and SCG are instructed by different commands.

[0132] Scenario Example 4

[0133] This scenario example involves switching of Layer 1 Subsequent conditional PCells and adding / changing of conditional Subsequent PSCells.

[0134] If the network supports subsequent conditional PCell cell switch with subsequent conditional PSCell cell switch in its initial configuration, it means that the network supports the parallel triggering and execution of two events: SCLPS (subsequent conditional LTM PCell cell switch) and SCLPSS (subsequent conditional PSCell cell switch). However, due to changes in channel conditions or measurement offsets between PCell and PSCell, the condition fulfillment points of these two processes may not be aligned in the time domain. Possible scenarios include: 1) simultaneous fulfillment, 2) SCLPS event condition fulfillment first, and 3) SCLPSS event condition fulfillment first. For these possible scenarios, it is necessary to standardize the UE's behavior to ensure that both the UE and NW sides have the same understanding of the event progression. The following methods can be used to standardize the UE's behavior:

[0135] Method 1: The two event conditions must be met at the same time;

[0136] Method 2: The conditions for the two events are met at different times and are handled according to the time priority principle;

[0137] Method 3: The two event conditions are met at different times and processed according to the NW configuration;

[0138] Method 4: The two event conditions are met at different times, and a time window is set for constraint;

[0139] Method 5: Depends on the UE implementation.

[0140] Compared to Layer 1 conditional PCell switching and conditional PSCell addition / change, the main feature of this embodiment is that it does not require event trigger condition configuration, but directly uses the existing condition configuration to save signaling overhead. Similar to Layer 1 conditional PCell switching and conditional PSCell addition / change, the above method also applies to Layer 1 Subsequent conditional PCell switching and conditional Subsequent PSCell addition / change. The specific difference is that CLPS and CLPSS are replaced with SCLPS and SCLPSS, and event trigger condition configuration is not considered in subsequent processes; this will not be elaborated further here.

[0141] It's important to note that the time difference between the first event fulfillment time and the end point of the preceding process in subsequent evaluations also needs to be considered. If, in subsequent evaluations, the time interval between the first event fulfillment time and the completion time of the previous process handover exceeds Zs, the initial condition configuration may no longer be applicable, and all subsequent evaluations must be abandoned. Specifically, during subsequent evaluations, if the CLPS condition is met or the time t3 for the CLPSS condition to be met is less than Ts from the completion time t2 of the previous process, then subsequent operations can continue; otherwise, evaluations and subsequent operations will not be performed. The configuration of T can be completed through RRC signaling, MAC CE, UE capability, or DCI.

[0142] Consider how to configure early synchronization when two cell groups change. Specifically, consider the following two configurations: MCG and SCG are instructed by the same command; MCG and SCG are instructed by different commands.

[0143] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0144] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0145] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0146] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0147] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0148] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0149] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for processing dual-event condition triggers, characterized in that, include: The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition is met and the time when the second event triggering condition is met; The first event includes a conditional handover event, and the second event includes a conditional primary / secondary cell addition / change event.

2. The method according to claim 1, characterized in that, The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: If the first event triggering condition and the second event triggering condition are met at different times, and the time difference between the time when the first event triggering condition is met and the time when the second event triggering condition is met does not exceed a preset time window, the UE executes the triggered first event and the second event.

3. The method according to claim 2, characterized in that, The UE executes the triggered first event and second event, including: If the first event triggering condition is met, the UE temporarily does not execute the first event and evaluates whether the second event triggering condition is met. If the second event triggering condition is met within the first preset time window, the UE executes the first event and the second event. If the second event triggering condition is not met within the first preset time window, the UE stops evaluating the second event triggering condition. If the second event triggering condition is met, the UE temporarily does not execute the second event and evaluates whether the first event triggering condition is met. If the first event triggering condition is met within the second preset time window, the UE executes the first event and the second event. If the first event triggering condition is not met within the second preset time window, the UE stops evaluating the first event triggering condition.

4. The method according to claim 2, characterized in that, The UE executes the triggered first event and second event, including: If the first event triggering condition is met, the UE executes the first event and evaluates whether the second event triggering condition is met; If the triggering condition of the second event is met within the first preset time window, the UE executes the second event; if the triggering condition of the second event is not met within the first preset time window, the UE stops evaluating the second event.

5. The method according to claim 2, characterized in that, The UE executes the triggered first event and second event, including: If the second event triggering condition is met, the UE executes the second event and evaluates whether the first event triggering condition is met. If the triggering condition of the first event is met within the second preset time window, the UE executes the first event; if the triggering condition of the first event is not met within the second preset time window, the UE stops evaluating the first event.

6. The method according to any one of claims 3 to 5, characterized in that, The method further includes: The UE receives Radio Resource Control (RRC) signaling sent by the Network NW side, wherein the RRC signaling is used to indicate a first preset time window and a second preset time window, the values ​​of the first preset time window and the second preset time window are determined by the NW according to the current channel state, and the values ​​are not greater than the cell measurement period. The cell measurement cycle includes at least one of the following: intra-frequency cell identification cycle with index, intra-frequency cell identification cycle without index, inter-frequency cell identification cycle without index, and inter-frequency cell identification cycle with index.

7. The method according to any one of claims 3 to 5, characterized in that, The method further includes: The UE receives a Medium Access Control (MAC) control element (CE) signaling sent by the NW side, wherein the MAC CE signaling is used to indicate a first preset time window and a second preset time window, and one or two fields of the MAC CE signaling are used together or separately to indicate the values ​​of the first preset time window and the second preset time window.

8. The method according to any one of claims 3 to 5, characterized in that, The method further includes: The UE receives UE function signaling sent by the NW side, wherein one or two components of the UE function signaling are used to indicate a first preset time window and a second preset time window.

9. The method according to any one of claims 3 to 5, characterized in that, The method further includes: The UE receives downlink control information (DCI) signaling sent by the NW side, wherein the DCI signaling is used to indicate a first preset time window and a second preset time window.

10. The method according to claim 1, characterized in that, The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: If the first event condition and the second event condition are met at the same time, the UE executes the triggered first event and second event at the next time.

11. The method according to claim 1, characterized in that, The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: If the first event triggering condition is met and the second event triggering condition is not met at the same time, the UE executes the triggered first event and ends the evaluation of the execution conditions for the second event.

12. The method according to claim 1, characterized in that, The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: If the first event triggering condition is not met and the second event triggering condition is met at the same time, the UE executes the triggered second event and ends the evaluation of the first event execution condition.

13. The method according to claim 1, characterized in that, The method further includes: if the first event triggering condition or the second event triggering condition is not met at the same time, ending the evaluation of the execution conditions of the first event and the second event.

14. The method according to claim 1, characterized in that, The terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, including: If the first event triggering condition and the second event triggering condition are met at different times, the UE executes the first event or the second event according to the NW signaling sent by the NW side; The NW signaling includes at least one of the following: RRC signaling, MAC CE signaling, DCI signaling, and UE function signaling.

15. The method according to claim 14, characterized in that, The UE executes the first event or the second event according to the NW signaling sent by the NW side, including: If the NW signaling indicates that only the first event will be executed, the UE will execute the first event if the first event triggering condition is met. If the NW signaling indicates that only the second event will be executed, the UE will execute the second event if the second event triggering condition is met. If the NW signaling indicates that only events that meet the conditions will be executed, the UE will execute either the first event or the second event according to the first-to-first-to-execute principle.

16. The method according to claim 15, characterized in that, The method further includes: If the NW signaling does not include an event execution indication, the UE executes the first event and the second event if both the first event triggering condition and the second event triggering condition are met simultaneously.

17. The method according to claim 1, characterized in that, Before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, the method further includes: The UE performs early synchronization based on the received DCI command; The DCI command is used to instruct the primary cell group (MCG) and secondary cell group (SCG) for early synchronization. The DCI command includes a cell indicator field and a primary / secondary cell indicator field. The primary / secondary cell indicator field indicates the cell number in the SCG that requires early synchronization. The number of bits occupied by the primary / secondary cell indicator field is [number missing]. C1 represents the number of cells in the SCG that require early synchronization.

18. The method according to claim 1, characterized in that, Before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, the method further includes: The UE performs early synchronization based on the received first DCI command and second DCI command; The first DCI command is used to instruct early synchronization of the MCG. The first DCI command includes a first cell indicator field, which indicates the cell number in the MCG that requires early synchronization. The first cell indicator field occupies [number] bits. C is the number of cells in the MCG that need to perform early synchronization; The second DCI command is used to indicate early synchronization of the SCG. The second DCI command includes a second cell indicator field, which indicates the cell number in the SCG that requires early synchronization. The second cell indicator field occupies [number] bits. C is the number of cells in the SCG that need to perform early synchronization.

19. The method according to claim 1, characterized in that, in, The first event also includes at least one of the following: a Conditional Physical Layer / Radio Resource Control Layer triggered Mobile LTM Primary Cell Handover CLPS event, a Subsequent Conditional Handover SCHO event, and a Subsequent Conditional LTM Primary Cell Handover SCLPS event; The second event further includes at least one of the following: Conditional LTM Primary / Secondary Cell Handover CLPSS event, Subsequent Conditional Primary / Secondary Cell Addition / Change SCPA / C event, and Subsequent Conditional LTM Primary / Secondary Cell Handover SCLPSS event.

20. The method according to claim 1, characterized in that, Before the terminal UE executes the triggered first event and / or second event according to the time when the first event triggering condition and the second event triggering condition are met, it also includes: receiving a configuration from the network side that supports the first event and the second event being triggered and executed in parallel.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 5 or 10 to 20.

22. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 5 or 10 to 20.

23. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 5 or 10 to 20.

Images