Mobility operation method, communication device and system, storage medium and program product

Abstract

The present disclosure relates to a mobility operation method, a communication device and system, a storage medium and a program product. The method comprises: receiving configuration information, wherein the configuration information is used for determining a configuration that needs to be satisfied for triggering a first behavior, and the first behavior comprises early synchronization related to a height-based mobility operation. In the embodiments of the present disclosure, relevant information for triggering early synchronization related to a height-based mobility operation is configured for a terminal, such that the height-based mobility management of the terminal can be optimized, the height-based mobility handover performance thereof can be improved, and the signaling overhead can be reduced.

Description

Mobility operating methods, communication devices, systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to mobility operation methods, communication devices, systems, storage media, and program products. Background Technology

[0002] The mobility operation of related technologies does not fully take into account the mobility characteristics of air terminals, and cannot provide effective mobility management for air terminals, resulting in poor mobility handover performance. Summary of the Invention

[0003] In order to provide better mobility management to over-the-air terminals, embodiments of this disclosure provide mobility operation methods, communication devices, systems, storage media, and program products.

[0004] According to a first aspect of the present disclosure, a mobility operation method is proposed, executed by a terminal, the method comprising: receiving configuration information for determining configurations required to trigger a first action, the first action including advance synchronization related to altitude-based mobility operation.

[0005] According to a second aspect of the present disclosure, a mobility operation method is proposed, performed by a network device, the method comprising sending configuration information for determining to a terminal a configuration required to trigger a first action, the first action including advance synchronization related to altitude-based mobility operation.

[0006] According to a third aspect of the present disclosure, a terminal is provided, comprising: a transceiver module for receiving configuration information; and a processing module for determining, based on the configuration information, a configuration that needs to be satisfied to trigger a first action, the first action including advance synchronization related to altitude-based mobility operations.

[0007] According to a fourth aspect of the present disclosure, a network device is provided, comprising: a processing module for determining configuration information, the configuration information being used to determine configurations that need to be satisfied to trigger a first action, the first action including advance synchronization related to altitude-based mobility operations; and a transceiver module for transmitting the configuration information.

[0008] According to a fifth aspect of the present disclosure, a communication device is provided for performing the mobility operation method described in either the first or second aspect.

[0009] According to a sixth aspect of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the mobility operation method described in the first aspect, and the network device is configured to implement the mobility operation method described in the second aspect.

[0010] According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform the mobility operation method as described in the first or second aspect.

[0011] According to an eighth aspect of the present disclosure, a program product is provided, comprising at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the steps of the method described in the first or second aspect.

[0012] In this embodiment of the disclosure, by configuring the terminal with information related to the advance synchronization of altitude-based mobility operations, the terminal's altitude-based mobility management can be optimized, its altitude-based mobility handover performance can be improved, and signaling overhead can be reduced. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for describing the embodiments are introduced below. These drawings are merely some embodiments of this disclosure and do not impose specific limitations on the scope of protection of this disclosure. Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of this disclosure. Figure 2A is an exemplary interactive schematic diagram of a mobility operation method provided according to an embodiment of this disclosure. Figure 2B is a schematic diagram of the signaling flow of LTM according to an embodiment of this disclosure. Figure 2C is a schematic diagram of TA acquisition based on random access according to an embodiment of this disclosure. Figure 2D is one of the schematic diagrams of TA calculation based on terminal measurements according to an embodiment of this disclosure. Figure 2E is another schematic diagram of TA calculation based on terminal measurements according to an embodiment of this disclosure. Figure 2F is a schematic diagram of the result of activation or deactivation of MAC CE in candidate cell TCI state according to an embodiment of this disclosure. Figure 2G is one of the flowchart schematic diagrams of a mobility operation method according to an embodiment of this disclosure. Figure 2H is another flowchart schematic diagram of a mobility operation method according to an embodiment of this disclosure. Figure 2I is a third flowchart schematic diagram of a mobility operation method according to an embodiment of this disclosure. Figure 2J is a fourth flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. Figure 2K is a fifth flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. Figure 2L is a sixth flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. Figure 3A is a schematic block diagram of a terminal device structure according to an embodiment of the present disclosure. Figure 3B is a schematic block diagram of a network device structure according to an embodiment of the present disclosure. Figure 4A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure. Figure 4B is a schematic structural diagram of a chip proposed in an embodiment of the present disclosure. Detailed Implementation

[0014] This disclosure provides embodiments of mobility operation methods, communication devices, systems, storage media, and program products.

[0015] In a first aspect, embodiments of this disclosure propose a mobility operation method, executed by a terminal, comprising:

[0016] Receive configuration information, which is used to determine the configuration that needs to be met to trigger the first action, which includes advance synchronization related to altitude-based mobility operations.

[0017] In the above embodiments, by obtaining relevant information configured by the network device for triggering altitude-based mobility operations related to advance synchronization, the terminal can optimize altitude-based mobility management, improve its altitude-based mobility handover performance, and reduce signaling overhead.

[0018] In conjunction with some embodiments of the first aspect, in some embodiments, advance synchronization includes at least one of the following:

[0019] The first is advance synchronization, including advance synchronization related to downlink;

[0020] The second type of advance synchronization includes advance synchronization related to uplink.

[0021] In the above embodiments, by obtaining relevant information configured by the network device for triggering altitude-based early uplink synchronization and early downlink synchronization, the terminal can optimize its altitude-based mobility management and improve its altitude-based mobility handover performance.

[0022] In conjunction with some embodiments of the first aspect, in some embodiments, the first advance synchronization includes activating the Transmission Configuration Indication (TCI) state of the candidate cell.

[0023] In the above embodiments, the terminal can obtain the relevant information configured by the network device for triggering the activation of the early TCI state, and can activate the candidate cell in advance based on altitude. This can prepare the downlink transmission configuration for the terminal in advance, thereby optimizing the mobility handover process based on altitude, reducing latency, and improving the handover success rate.

[0024] In conjunction with some embodiments of the first aspect, in some embodiments, the second advance synchronization includes obtaining the timing advance (TA) of the candidate cell.

[0025] In the above embodiments, by obtaining the relevant information configured by the network device for triggering early uplink synchronization, the timing advance (TA) of the candidate cell is obtained in advance, enabling the terminal to make timely time synchronization preparations during altitude-based mobility operations, reducing signal interference and improving handover stability.

[0026] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is used to indicate at least one of the following: the altitude range required to trigger the first action; altitude-based execution conditions that need to be evaluated to trigger the first action; and the configuration of candidate cells associated with the first action.

[0027] In the above embodiments, the network device configures the terminal with a height range and height-based execution conditions associated with the first action, enabling the terminal to perform the first action on candidate cells that meet the height range and / or execution conditions during height-based mobility operations, thereby improving its height-based mobility handover performance.

[0028] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration of different candidate cells is associated with different altitude ranges.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration of different candidate cells is associated with different execution conditions.

[0030] In the above embodiments, the network device configures candidate cells related to mobility operations based on altitude to the terminal and associates each candidate cell with the configured altitude range and / or execution conditions, so that the terminal can synchronize with the candidate cells that meet the requirements in advance, thereby improving the performance of altitude-based mobility handover.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration of the candidate cell is used to indicate at least one of the following: the candidate cell; the beam of the candidate cell; the TCI state of the candidate cell.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration of a candidate cell includes at least one of the following: a configuration identifier for the candidate cell; an identifier for the candidate cell; an identifier for the candidate beam; an identifier for the synchronization signal block (SSB) corresponding to the candidate beam; and an identifier for the TCI state of the candidate cell.

[0033] In the above embodiments, the configuration of candidate cells provides the key information required by the terminal during mobility operations, ensuring that the terminal can quickly and accurately select the appropriate cell and reduce operation delays during handover.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: obtaining the terminal height; determining a first candidate cell from candidate cells associated with the first action based on the terminal height; wherein the first candidate cell includes candidate cells associated with a first height range and / or a first execution condition, the first height range being the height range in which the terminal height is located, and the first execution condition being an execution condition satisfied by the terminal height; and performing the first action on the first candidate cell.

[0035] In the above embodiments, by obtaining the terminal altitude and determining candidate cells related to the altitude, the terminal can perform altitude-based synchronization and handover operations more accurately, thereby improving the efficiency of mobility operations.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, performing a first action on the first candidate cell includes at least one of the following: activating the TCI state of the first candidate cell; obtaining the TA value of the first candidate cell; and maintaining the TA value of the first candidate cell.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the TCI state includes at least one of the following: an uplink TCI state; a downlink TCI state; and a combined TCI state.

[0038] In the above embodiments, by performing operations such as activation and TA acquisition on candidate cells, the terminal can ensure that its synchronization state is adjusted and maintained in a timely manner during mobility operations, thereby improving the reliability and success rate of handover.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is also used to determine the configuration that needs to be met to trigger the second action: the second action includes at least one of the following: deactivation of the TCI state of the candidate cell; deletion of the TA value of the candidate cell.

[0040] In the above embodiments, the configuration that triggers the second action ensures that the terminal performs operations such as deactivation under specific conditions, thereby reducing unnecessary signaling overhead and optimizing performance after handover.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining, based on the terminal height, that the terminal has left a second height range, and / or the terminal height no longer meets the second execution condition, and performing the second action on a second candidate cell; wherein the second candidate cell includes candidate cells associated with the second height range and / or the second execution condition.

[0042] In the above embodiments, by determining that the terminal has left the second height range or no longer meets the execution conditions based on the terminal height, the terminal can promptly delete unnecessary maintenance information and save resources.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the height range that triggers the first behavior is determined by at least one of the following parameters: a first threshold value, used to indicate the lower limit of the height range; a second threshold value, used to indicate the upper limit of the height range; and a hysteresis value, used to assess whether the terminal is located at or away from the reserved height of the height range.

[0044] In the above embodiments, by determining the threshold value and hysteresis value of the height range, it is possible to effectively assess whether the terminal enters or leaves a specific mobility operation range, thereby optimizing the timing and efficiency of handover.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is further used to indicate a third threshold value, which is a threshold value for the measurement result that needs to be evaluated to trigger the first action; the measurement result of the first candidate cell satisfies the third threshold value.

[0046] In the above embodiments, by configuring the third threshold value, the actual situation of the terminal can be accurately determined, ensuring that altitude-based mobility operations are triggered under predetermined conditions, thereby improving the accuracy of handover.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the altitude-based execution conditions include at least one of the following: the terminal altitude exceeds a first altitude threshold; the terminal altitude is lower than a second altitude threshold; the signal quality of the serving cell is lower than a first quality threshold; the signal quality of the candidate cell is better than the signal quality of the serving cell by a first offset; the signal quality of the candidate cell exceeds a second quality threshold.

[0048] In the above embodiments, by setting threshold values ​​for conditions such as terminal altitude and signal quality, appropriate candidate cells can be accurately selected for handover operations, thereby improving the success rate of altitude-based mobility operations.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is also used to indicate the time window that needs to be met to trigger the first behavior.

[0050] In the above embodiments, by configuring a time window, precise timing control can be achieved for altitude-based mobility operations, thereby optimizing handover timing, improving handover success rate, and reducing unnecessary signaling overhead.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration information is further used to instruct the terminal to trigger at least one of the following mobility operations based on altitude: altitude information of the terminal; measurement of a first candidate cell or the beam of a first candidate cell; the first candidate cell being a candidate cell for performing the first action; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation.

[0052] In the above embodiments, by configuring different mobility operations, the terminal can selectively trigger different types of operations based on its altitude and environmental conditions. This allows for flexible responses to the terminal's actual mobility needs, reducing signaling burden and improving the overall handover efficiency of the terminal, especially in complex environments such as high-speed or rapidly changing mobile scenarios.

[0053] Secondly, embodiments of this disclosure propose a mobility operation method executed by a network device, the method comprising: sending configuration information, the configuration information being used to determine to a terminal the configuration required to trigger a first action, the first action including advance synchronization related to altitude-based mobility operation.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, advance synchronization includes at least one of the following: first advance synchronization, including downlink-related advance synchronization; second advance synchronization, including uplink-related advance synchronization.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first advance synchronization includes activating the Transmission Configuration Indication (TCI) state of the candidate cell.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the second advance synchronization includes obtaining the timing advance of the candidate cells.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is used to indicate at least one of the following: the altitude range required to trigger the first action; the altitude-based execution conditions that need to be evaluated to trigger the first action; and the configuration of candidate cells associated with the first action.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration of the candidate cell is used to indicate at least one of the following: the candidate cell; the beam of the candidate cell; the TCI state of the candidate cell.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration of the candidate cell includes at least one of the following: a configuration identifier for the candidate cell; an identifier for the candidate cell; an identifier for the candidate beam; an identifier for the synchronization signal block (SSB) corresponding to the candidate beam; and an identifier for the TCI state of the candidate cell.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is also used to determine for the terminal the configuration that needs to be met to trigger the second action: the second action includes at least one of the following: deactivation of the TCI state of the candidate cell; deletion of the TA value of the candidate cell.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the height range that triggers the first behavior is determined by at least one of the following parameters: a first threshold value, used to indicate the lower limit of the height range; a second threshold value, used to indicate the upper limit of the height range; and a hysteresis value, used to assess whether the terminal is located at or away from the reserved height of the height range.

[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is further used to indicate a third threshold value to the terminal, the third threshold value being a threshold value of the measurement result that needs to be evaluated to trigger the first action; the measurement result of the first candidate cell satisfies the third threshold value.

[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the altitude-based execution conditions include at least one of the following: the terminal altitude exceeds a first altitude threshold; the terminal altitude is lower than a second altitude threshold; the signal quality of the serving cell is lower than a first quality threshold; the signal quality of the candidate cell is better than the signal quality of the serving cell by a first offset; the signal quality of the candidate cell exceeds a second quality threshold.

[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is also used to indicate the time window that needs to be met to trigger the first behavior.

[0065] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration information is also used to instruct the terminal to trigger at least one of the following mobility operations based on altitude: sending altitude information of the terminal; measuring a first candidate cell or the beam of a first candidate cell; the first candidate cell being a candidate cell for performing the first action; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation.

[0066] Thirdly, embodiments of this disclosure propose a terminal, including: a transceiver module for receiving configuration information; and a processing module for determining, based on the configuration information, the configuration required to trigger a first action, the first action including advance synchronization related to altitude-based mobility operations.

[0067] Fourthly, embodiments of this disclosure provide a network device, comprising: a processing module for determining configuration information, the configuration information being used to determine configurations that need to be satisfied to trigger a first action, the first action including advance synchronization related to altitude-based mobility operations; and a transceiver module for transmitting the configuration information.

[0068] Fifthly, embodiments of this disclosure provide a communication device for performing the mobility operation method described in either the first or second aspect.

[0069] In a sixth aspect, embodiments of this disclosure provide a communication system including a terminal and a network device, wherein the terminal is configured to implement the mobility operation method described in the first aspect, and the network device is configured to implement the mobility operation method described in the second aspect.

[0070] In a seventh aspect, embodiments of this disclosure propose a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the mobility operation method as described in the first or second aspect.

[0071] Eighthly, embodiments of this disclosure propose a program product comprising at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, the program or instructions implement the method described in the first or second aspect.

[0072] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0073] This disclosure provides embodiments of mobility operation methods, communication devices, systems, storage media, and program products. In some embodiments, the terms mobility operation method, information processing method, and communication method may be used interchangeably.

[0074] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0075] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0076] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0077] In the embodiments disclosed herein, "multiple" refers to two or more.

[0078] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0079] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0080] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0081] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0082] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0083] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0084] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0085] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0086] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0087] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0088] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0089] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0090] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0091] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0092] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0093] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0094] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0095] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0096] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0097] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0098] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0099] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.

[0100] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0101] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0102] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0103] In some embodiments, the core network device 103 may be a single device, including a first network element 1031, a second network element 1032, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1031, the second network element 1032, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0104] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0105] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0106] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0107] In the future, 6G will need to achieve seamless, three-dimensional super connectivity, enabling broadband access capabilities across all times and regions. This will provide broadband access services to remote areas, aircraft, unmanned aerial vehicles (UAVs), automobiles, and ships; provide wide-area IoT access to regions worldwide without terrestrial network coverage, ensuring services such as emergency communication, crop monitoring, monitoring of rare animals in uninhabited areas, collection of information from maritime buoys, and collection of information from ocean-going containers; provide high-precision positioning with centimeter-level accuracy, enabling services such as high-precision navigation and precision agriculture; and, through high-precision imaging of the Earth's surface, enable services such as emergency rescue and traffic dispatch.

[0108] In recent years, global interest in drone-based services has increased dramatically, encompassing various drone operations, personal entertainment through flight experiences, and cargo delivery. Remote control and data transmission capabilities are key enhancements underlying these services, attracting interest from both service providers / operators and drone manufacturers.

[0109] In some embodiments, the feasibility and required enhancements of UAV connectivity via terrestrial cellular systems have been demonstrated, with LTE providing corresponding enhancements in terms of UL and DL interference and mobility.

[0110] In some embodiments, altitude-based measurement reporting events and altitude reporting are introduced.

[0111] Introduced altitude-based measurement reporting events and altitude reporting:

[0112] Event H1: The flight altitude of the air terminal exceeds a certain threshold.

[0113] Event H2: The air terminal's altitude falls below a certain threshold.

[0114] Furthermore, measurement reporting events based on altitude and measurement results were implemented.

[0115] Event A3H1: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes higher than athreshold.

[0116] Event A3H2: Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than athreshold.

[0117] Event A4H1: The signal quality of the neighboring cell is better than threshold 1, and the flight altitude of the air terminal exceeds threshold 2.

[0118] Event A4H2: The signal quality of the neighboring cell is better than threshold 1, and the flight altitude of the air terminal is lower than threshold 2.

[0119] Event A5H1: The signal quality of the primary cell is lower than threshold 1, the signal quality of the neighboring cell is better than threshold 2, and the flight altitude of the air terminal exceeds threshold 3.

[0120] Event A5H2: The signal quality of the primary cell is lower than threshold 1, the signal quality of the neighboring cell is better than threshold 2, and the flight altitude of the air terminal is lower than threshold 3.

[0121] In some embodiments, the UAV introduces a highly correlated measurement resource configuration in Radio Resource Management (RRM) measurements to indicate specific measurement resources within different altitude ranges.

[0122] In implementation, some gNBs may deploy dedicated resources (such as upward beams) to provide better coverage for drone terminals.

[0123] Given that LTM enables fast, low-latency handover, applying LTM to UAV UEs can effectively improve the mobility performance of UAV UEs, reduce handover interruptions, lower handover latency, and achieve fast and efficient handover.

[0124] Layer 1 / L2-triggered Mobility (LTM)

[0125] In a communication system, the network side can provide the terminal with one or more candidate configurations, where each candidate configuration can include one or more "cells (or cell groups)". The network side can subsequently control the terminal to change among these candidate configurations (e.g., changing the working cell (or cell group) from "cell (or cell group)-1" to "cell (or cell group)-2") via L1 (e.g., Downlink Control Information (DCI)) or L2 (MAC CE) signaling. This control signaling can be called "cell change control signaling".

[0126] This process can also be called a network-triggered LTM process.

[0127] LTM definition:

[0128] LTM refers to a process in which a primary cell (PCell) or primary secondary cell (PSCell) is switched via MAC CE based on L1 measurement results in a network. This may be accompanied by a change in the master cell group (MCG) or secondary cell group (SCG).

[0129] In LTM, the gNB receives L1 measurement reports from the UE. Based on these reports, the gNB changes the UE's serving cell via a cell switch command issued by the MAC CE. The cell switch command indicates an LTM candidate cell configuration that the gNB has pre-provided to the UE via RRC signaling. The UE then accesses the target cell indicated in this cell switch command based on the received cell switch command. LTM can be used to reduce mobility latency.

[0130] In this context, LTM candidate cell configurations can only be added, modified, and released by the network via RRC signaling. The LTM process can be used to reduce mobility latency.

[0131] For LTM, LTM supports subsequent LTM (subsequent LTM), where the subsequent LTM cell switch procedure is performed between candidate cells without the network performing RRC reconfiguration in between. In other words, after performing mobility operations, the UE will not delete the LTM configuration information on its own. The LTM configuration information can continue to be used to trigger subsequent LTM even without RRC reconfiguration and updates.

[0132] LTM supported scenarios

[0133] LTM supports mobility within a network device distributed unit (intra-gNB-DU), within a network device centralized unit (intra-gNB-CU), and between network device distributed units (inter-gNB-DU). LTM also supports intra-frequency and inter-frequency mobility, including mobility to inter-frequency cells that are not currently serving cells. Specifically, it includes the following scenarios:

[0134] PCell change in non-CA and non-DC scenarios;

[0135] PCell change in CA scenario;

[0136] In dual connectivity scenarios, changes to the MCG PCell and SCGPSCell occur without MN involvement (i.e., PSCell changes within the SN). LTM does not support simultaneous PCell and PSCell changes.

[0137] In communication, LTM can be supported only within a distributed unit (intra DU) and between distributed units within a centralized unit (inter-DU intra-CU), but it can also be extended to support LTM between centralized units (inter-CU (inter-node / gNB)). In inter-CU (inter-node / gNB) LTM for SCG PSCell change, a Management Provider (MN) is involved. The MN is responsible for coordinating the configuration between candidate PSCells of different CUs.

[0138] LTM configuration:

[0139] LTM configuration information can be configured through LTM configuration (LTM-Config).

[0140] The LTM configuration information may include, but is not limited to, one or more of the following: LTM reference configuration; one or more candidate cell configurations (candidate cell configurations can be added, modified, or deleted by adding / modifying / removing lists: for example, LTM candidate cell removal list ltm-CandidateToReleaseList, LTM candidate cell addition / modification list ltm-CandidateToAddModList); LTM CSI resource configuration; etc.

[0141] The candidate cell configuration can be configured through LTM candidate configuration (LTM-Candidate), which includes, but is not limited to, one or more of the following information: configuration identifier; candidate cell identifier; candidate configuration (represented by Radio Resource Control Reconfiguration (RRCReconfiguration)); etc.

[0142] The LTM candidate configuration is the configuration part of an RRCReconfiguration message associated with a candidate cell, e.g., for LTM or subsequent CPAC. A candidate configuration can be a complete candidate configuration or an incremental configuration relative to a reference configuration.

[0143] The LTM reference configuration is a configuration provided by the network to the UE that is common within the same cell group, to a group of configured non-complete candidate configurations.

[0144] LTM execution flow:

[0145] The overall process of LTM is shown in Figure 2B below. Subsequent LTM is completed by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate configurations after each LTM cell switch completion. The general procedure over the air interface is applicable to SCG LTM.

[0146] As shown in Figure 2B, the LTM process is as follows:

[0147] 1. The UE sends a MeasurementReport message to the gNB. The gNB decides to configure LTM and initiates LTM preparation.

[0148] 2. The gNB sends an RRCReconfiguration message to the UE, which includes the LTM candidate configurations.

[0149] 3. The UE stores the LTM candidate configurations and sends an RRCReconfigurationComplete message to the gNB.

[0150] 4a. The UE performs DL synchronization with the candidate cell(s) before receiving the cell switch command.

[0151] 4b. When UE-based TA measurement is configured, the UE obtains the TA value of the candidate cell through measurement. Before the specified cell handover command, the UE performs early TA acquisition with the candidate cell as required by the network. This is accomplished via Contention-Free Random Access (CFRA) triggered by a command from the Physical Downlink Control Channel (PDCCH) of the source cell, after which the UE sends a preamble to the indicated candidate cell. To minimize source cell data interruption caused by CFRA to the candidate cell, the UE does not receive a random access response from the network for obtaining the TA value, and the TA value of the candidate cell is indicated in the cell handover command.The UE does not maintain a TA timer for the candidate cell, but relies on network implementation to ensure the TA validity (When UE-based TA measurement is configured, UE acquires the TA value(s) of the candidate cell(s) by measurement. UE performs early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command. This is done via CFRA triggered by a PDCCH order from the source cell, following which the UE sends preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE doesn't receive random access response from the network for the purpose of TA value acquisition and the TA value of the candidate cell is indicated in the cell switch command. The UE doesn't maintain the TA timer for the candidate cell and relies on network implementation to guarantee the TA validity).

[0152] 5. The UE performs L1 measurements on the configured candidate cell(s) and sends L1 measurement reports to the gNB. L1 measurement should be performed as long as RRC reconfiguration (step 2) is applicable.

[0153] 6. The gNB decides to execute a cell switch to a target cell and transmits a MAC CE triggering the cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by the candidate configuration index.

[0154] 7. If the UE does not have a valid TA for the target cell, the UE performs the random access procedure toward the target cell.

[0155] 8. The UE completes the LTM cell switch procedure by sending an RRCReconfigurationComplete message to the target cell. If the UE has performed an RA procedure in step 7, the UE considers that the LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that the LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data.

[0156] Using the LTM candidate configuration(s) provided in step 2, steps 4-8 can be performed multiple times for subsequent LTMs.

[0157] The air interface procedure described in Figure 2B is applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM.

[0158] Early uplink synchronization and TA acquisition

[0159] When the network is configured, it can initiate an uplink TA acquisition (called early TA) procedure for one or more candidate cells that are different from the current serving cells. If the timing advance of the candidate cell is the same as that of the current serving cell, or if TA = 0, an early TA acquisition procedure is not required. Before a cell handover, the network may request the UE to perform an early TA acquisition procedure for a candidate cell.

[0160] The advance TA acquisition procedure can be triggered via a PDCCH command or implemented through UE-based TA measurement configured by RRC (Radio Resource Control). In the former case, the gNB of the candidate cell calculates the TA value and sends it to the gNB of the current serving cell. The serving cell then sends the TA value in the MAC CE of the LTM cell handover command. When an LTM cell handover is triggered, the TA value is sent along with the LTM handover command. In the latter case, the UE performs TA measurement on the candidate cell after RRC configuration, but the specific timing of the TA measurement is determined by the UE's implementation. The UE applies its own measured TA value upon receiving the cell handover command and performs an LTM handover without random access (RACH). If advance TA acquisition is not performed, the network can also directly send the TA value in the MAC CE of the LTM cell handover command.(The early TA acquisition procedure is triggered by PDCCH order or realized through UE-based TA measurement as configured by RRC. In the former case, the gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE performs TA measurement for the candidate cells after being configured by RRC but the exact time the UE performs TA measurement is up to UE implementation. The UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command. The network may also send a TA value in the LTM cell switch command MAC CE without early TA acquisition)。

[0161] a) RACH-based TA acquisition

[0162] For the random access procedure towards an LTM candidate cell for early UL TA acquisition, Contiguous Frequency Random Access (CFRA) triggered by a PDCCH order is used. The UE sends Message 1 (MSG1) (Random Access Preamble) to the cell without monitoring for a response from the candidate cell, as shown in Figure 2C. To support UE power ramping, the UE may perform MSG1 retransmission as indicated by the network.

[0163] b) TA calculation based on terminal measurement

[0164] The terminal can calculate and obtain its uplink timing in cell 2 based on the downlink reception timing offset between cell 1 and cell 2, and the uplink timing of the terminal in cell 1. As shown in Figure 2D, the calculation method is as follows:

[0165] (TA_Cell_2) / 2=(TA_Cell_1) / 2+Rx_Diff;

[0166] TA_Cell_1: The TA value for cell 1;

[0167] TA_Cell_2: The TA value for cell 2;

[0168] Rx_Diff: The downlink reception timing offset between cell 1 and cell 2.

[0169] In some embodiments, the terminal obtains the TA value using the method shown in Figure 2E. Based on the downlink reception timing deviation between cell 1 and cell 2, the uplink timing of the terminal in cell 1, and the downlink transmission time difference between cell 1 and cell 2, the terminal can calculate and obtain the uplink timing in cell 2. The calculation method is as follows:

[0170] (TA_Cell_2) / 2=(TA_Cell_1) / 2+Rx_Diff-Tx_Diff;

[0171] Where TA_Cell_1 is the TA value of cell 1;

[0172] TA_Cell_2: The TA value for cell 2;

[0173] Rx_Diff: The downlink reception timing deviation between cell 1 and cell 2;

[0174] Tx_Diff: The downlink transmission time difference between cell 1 and cell 2.

[0175] After receiving the TA value indicated by the network, the terminal will start a timer, such as a time alignment timer (TAT). During the operation of this timer, the terminal will consider the TA value to be valid and use the TA value for uplink transmission.

[0176] Early downlink synchronization

[0177] During LTM, early downlink synchronization for candidate cells is supported.

[0178] The UE can activate the TCI state of one or more cells that are different from the current serving cell, based on network configuration or other schemes. For example, the TCI state of these cells can be activated in advance before any LTM candidate cell becomes the serving cell. This allows the UE to perform downlink synchronization with these candidate cells in advance, thereby enabling a faster handover to one of the candidate cells when a cell switch is triggered.

[0179] Supporting early uplink and downlink synchronization can effectively reduce handover interruption time.

[0180] 1) Network-triggered activation or deactivation of candidate cell TCI states.

[0181] In the existing network-triggered LTM process, the network side activates / deactivates the TCI states of one or more cells by sending MAC CEs (Candidate Cell TCI States Activation / Deactivation MAC CEs) to activate or deactivate the TCI states. Before receiving a cell handover command, the UE performs DL synchronization with the LTM candidate cells. The UE can activate and deactivate the TCI states of LTM candidate cells, which is triggered by the gNB.

[0182] Candidate Cell TCI States Activation / Deactivation

[0183] The network can activate and deactivate the TCI states of LTM candidate cells configured in CandidateTCI-State and CandidateTCI-UL-State by sending the Candidate Cell TCI States Activation / Deactivation MAC CE. The network deactivates the TCI state(s) for one LTM candidate cell by not including the corresponding TCI state ID field(s) in the Candidate Cell TCI States Activation / Deactivation MAC CE.

[0184] The Media Access Control (MAC) entity should:

[0185] 1> If the MAC entity receives a Candidate Cell TCI States Activation / Deactivation MAC CE on a Serving Cell:

[0186] 2> This indicates to lower layers the information regarding the Candidate Cell TCI States Activation / Deactivation MAC CE.

[0187] The MAC CE for the candidate cell TCI states activation / deactivation is identified by a MAC subheader with eLCID, as shown in Figure 2F. Its size is variable and consists of the following fields:

[0188] - Candidate Cell ID: This field indicates the identity of an LTM candidate cell for which the MAC CE applies, corresponding to the specified ltm-CandidateId minus 1. The length of the field is 3 bits.

[0189] -Pi: This field indicates whether each TCI codepoint has multiple TCI states or a single TCI state. If the Pi field is set to 1, the i-th TCI codepoint includes the DL TCI state and the UL TCI state. If the Pi field is set to 0, the i-th TCI codepoint includes only the DL / joint TCI state or the UL TCI state. The codepoint to which a TCI state is mapped is determined by its ordinal position among all the TCI state ID fields.

[0190] -D / U: This field indicates whether the TCI state ID in the same octet is for a joint / downlink TCI state or an uplink TCI state. If this field is set to 1, the TCI state ID in the same octet is for a joint / downlink TCI state. If this field is set to 0, the TCI state ID in the same octet is for an uplink TCI state.

[0191] -TCI State Identifier: This field indicates the TCI state identified by TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList or TCI-UL-StateId in ltm-UL-TCI-StatesToAddModList. If D / U is set to 1, a 7-bit TCI state ID is used. If D / U is set to 0, the most significant bit of the TCI state ID is treated as a reserved bit, and the remaining 6 bits represent the TCI-UL-StateId. The maximum number of activated TCI states is 16 (TCI state ID: This field indicates the TCI state identified by TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList or TCI-UL-StateId in ltm-UL-TCI-StatesToAddModList.If D / U is set to 1,7-bits length TCI state ID.If D / U is set to 0,the most significant bit of TCI state ID is considered as the reserved bit and remaining 6bits indicate the TCI-UL-StateId.The maximum number of activated TCI states is 16);

[0192] -R: Reserved bit, set to 0.

[0193] Figure 2A is an interactive schematic diagram of a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a mobility operation method, which includes:

[0194] Step S201: Network device 102 sends configuration information to terminal 101.

[0195] The configuration information is used to determine the configuration that the terminal needs to meet to trigger the first action (or first operation, or first process); the first action includes advance synchronization related to altitude-based mobility operations.

[0196] In some embodiments, terminal 101 may receive configuration information sent by network device 102, and based on the configuration information, determine the configuration that needs to be met to trigger the first action.

[0197] By configuring the terminal with information related to the advance synchronization of altitude-based mobility operations, the terminal's altitude-based mobility management can be optimized, its altitude-based mobility handover performance can be improved, and signaling overhead can be reduced.

[0198] In some embodiments, advance synchronization may include: a first advance synchronization and / or a second advance synchronization; wherein, the first advance synchronization includes downlink-related advance synchronization, also referred to as advance downlink synchronization. The second advance synchronization may include uplink-related advance synchronization, also referred to as uplink advance synchronization.

[0199] In some embodiments, the first early synchronization (early downlink synchronization) may include activating or deactivating the Transmission Configuration Indicator (TCI) state of the candidate cell.

[0200] In mobility operations, such as LTM, early downlink synchronization with candidate cells is supported. The UE can activate the TCI state of one or more candidate cells that are different from the current serving cell, based on network configuration or other schemes. For example, the TCI state of these candidate cells can be activated before any candidate cell becomes the serving cell. This allows the UE to perform early downlink synchronization with these candidate cells, enabling a faster handover to one of the candidate cells when a cell switch is triggered. Supporting early downlink synchronization can effectively reduce handover interruption time.

[0201] In some embodiments, the second advance synchronization (advance uplink synchronization) may include obtaining the time advance (TA) of the candidate cell, for example, obtaining the TA based on advance random access.

[0202] When the network is configured, it can initiate an uplink TA acquisition process (called early TA acquisition) for one or more candidate cells that are different from the current serving cell. If the timing advance TA of a candidate cell is the same as that of the current serving cell, or if the TA of the candidate cell is 0, early TA acquisition does not need to be triggered. Before cell handover, the network device can request the UE to perform early TA acquisition for candidate cells.

[0203] In some embodiments, advance TA acquisition can be triggered by a Physical downlink control channel (PDCCH) command or by UE-based TA measurement configured by Radio Resource Control (RRC). In the former case, the gNB of the candidate cell calculates the TA value and sends it to the gNB of the current serving cell. The serving cell then sends the TA value in the Medium Access Control Control Element (MAC CE) of the LTM cell handover command. When an LTM cell handover is triggered, the TA value is sent along with the LTM handover command. In the latter case, the UE performs TA measurement on the candidate cell after RRC configuration, but the specific timing of the TA measurement is determined by the UE's implementation. For example, after receiving the cell handover command, the UE applies its own measured TA value and performs LTM without RACH. The network can also send the TA value in the candidate cell handover command MAC CE without prior TA acquisition.

[0204] In some embodiments, the terminal may acquire TA based on RACH, or it may acquire TA based on TA calculated by the terminal.

[0205] In some embodiments, the first action may include activating the TCI stater of the candidate cell and / or performing uplink advance synchronization TA acquisition.

[0206] In some embodiments, the configuration information can be used to instruct the terminal to perform the configuration required for TCI state activation of the candidate cell, for example, to configure TCI-related information of the candidate cell for use when activating the TCI state.

[0207] In some embodiments, configuration information can be used to instruct the terminal on the configuration required to perform uplink early synchronization, for example, the configuration required when the UE performs early RACH to obtain the TA of the candidate cell.

[0208] In some embodiments, the configuration information can be used to instruct the terminal on the configuration required to perform TCI state activation of the candidate cell and the configuration required to perform the second advance synchronization.

[0209] In some embodiments, configuration information may be used to indicate to the terminal the height range that needs to be met to trigger the first behavior, and may include one or more height ranges.

[0210] In some embodiments, configuration information may be used to indicate to the terminal the height-based execution conditions that need to be evaluated to trigger the first action, and may include one or more execution conditions.

[0211] In some embodiments, configuration information may be used to indicate to the terminal the altitude range that needs to be met to trigger the first action and the altitude-based execution conditions that need to be evaluated.

[0212] For example, a height-based execution condition may include one or more height-based events and / or events based on both height and measurement results.

[0213] In some embodiments, configuration information may be used to indicate to the terminal the configuration of candidate cells associated with the first line.

[0214] In some embodiments, the configuration of a candidate cell may be used to indicate one or more of the candidate cell, the candidate cell's beam, and the candidate cell's TCI state.

[0215] In some embodiments, the configurations of different candidate cells may correspond to the same or different altitude ranges required to trigger the first action. For example, any one or more of different candidate cells, candidate cell beams, and candidate cell TCI states(s) may correspond to the same or different altitude ranges.

[0216] In some embodiments, the configurations of different candidate cells may correspond to the same or different altitude-based execution conditions that need to be evaluated to trigger the first action. For example, different candidate cells, candidate cell beams, and any one or more of the candidate cell TCI states(s) may correspond to the same or different altitude-based execution conditions.

[0217] In some embodiments, the configuration information may include at least one of the following to indicate the configuration of the candidate cell associated with the first row: candidate cell identifier (ID), candidate cell beam identifier, synchronization signal and PBCH block (SSB) identifier corresponding to the candidate cell beam, and TCI state ID. Thus, different candidate cells, candidate cell beams, and candidate cell TCI states(s) can be represented by the candidate cell identifier, candidate cell beam identifier, SSB identifier corresponding to the candidate cell beam, and TCI state ID.

[0218] In some embodiments, the configuration of multiple different candidate cells, such as different candidate cells, candidate cell beams, and any one or more candidate cell TCI states(s), may correspond to the same or different altitude ranges.

[0219] In some embodiments, a height range may correspond to any one or more of a plurality of different candidate cells, candidate cell beams, and candidate cell TCI states(s).

[0220] In some embodiments, the configuration of multiple different candidate cells, such as different candidate cells, candidate cell beams, and any one or more candidate cell TCI states(s), may correspond to the same or different altitude-based execution conditions.

[0221] In some embodiments, a height-based execution condition may correspond to any one or more of multiple different candidate cells, candidate cell beams, and candidate cell TCI states(s).

[0222] In some embodiments, the altitude range required to trigger the first action is determined by a first threshold value and / or a second threshold value. The first threshold value indicates the lower limit of the altitude range, also known as the minimum altitude threshold value (altitudeMin); the second threshold value indicates the upper limit of the altitude range, also known as the maximum altitude threshold value (altitudeMax).

[0223] In some embodiments, if a first threshold value is configured, the altitude range can be greater than or equal to the first threshold value, which can be expressed as altitudeMin≤UE altitude.

[0224] In some embodiments, if a second threshold is configured, the altitude range can be less than or equal to the second threshold, which can be expressed as UE altitude≤altitudeMax.

[0225] In some embodiments, if a first threshold value and a second threshold value are configured, the altitude range may be greater than or equal to the first threshold value and less than or equal to the second threshold value, which can be expressed as altitudeMin≤UE altitude≤altitudeMax.

[0226] In some embodiments, configuration information is used to determine the altitude range that triggers the first action. A hysteresis value (altitudeHyst) corresponding to the altitude range can also be configured for the terminal. The hysteresis value can be used to assess whether the terminal is within or outside a reserved altitude range. In other words, the hysteresis value acts as a buffer to further determine whether the terminal is within or outside a certain altitude range, thereby preventing the first action from being repeatedly triggered when the terminal is at the edge of the altitude range. For example, when assessing whether the terminal is within a certain altitude range (altitudeMin ≤ UE altitude ≤ altitudeMax), after determining that the altitude range is met, the altitude range can be further narrowed based on the hysteresis value: (altitudeMin – altitudeHyst) ≤ UE altitude ≤ (altitudeMax + altitudeHyst). Only when the terminal is determined to be within the narrowed altitude range is it considered to be within that altitude range; otherwise, it is considered that the terminal is not within this altitude range or has left the altitude range.

[0227] In some embodiments, the height-based execution conditions that need to be evaluated to trigger the first action may include at least one of the following events: a height-based event; a measurement-based event; or a combination of height and measurement results.

[0228] In some embodiments, height-based events may include at least one of the following: the terminal height exceeds a first height threshold; the terminal height is lower than a second height threshold; the terminal height exceeds the first height threshold and is lower than the second height threshold.

[0229] In some embodiments, height-based events may include:

[0230] Event H1: Aerial UE altitude exceeds a threshold.

[0231] Event H2: Aerial UE altitude becomes lower than a threshold.

[0232] Event H3: Aerial UE altitude becomes higher than a threshold 1 and aerial UE altitude becomes lower than a threshold 2.

[0233] In some embodiments, events based on measurement results may include any combination of at least one or more of the following: the signal quality of the serving cell is lower than a first quality threshold; the signal quality of the candidate cell is better than the signal quality of the serving cell by a first offset; the signal quality of the candidate cell exceeds a second quality threshold.

[0234] In some embodiments, events based on measurement results may include:

[0235] Event LTM2: The signal quality of the serving cell falls below the absolute threshold.

[0236] Event LTM3: The signal quality of the candidate cell is better than that of the serving cell by an offset.

[0237] Event LTM4: The signal quality of the candidate cell exceeds the absolute threshold.

[0238] Event LTM5: The signal quality of the serving cell is lower than the absolute threshold 1, and the signal quality of the candidate cell is higher than the absolute threshold 2.

[0239] In some embodiments, events based on height and measurement results may include any combination of the aforementioned events based on height and events based on measurement results.

[0240] In some embodiments, events based on height and measurement results may include:

[0241] Event LTM2H1: The signal quality of the serving cell is lower than threshold 1 and the terminal altitude is higher than threshold 2.

[0242] Event LTM2H2: The signal quality of the serving cell is lower than threshold 1 and the terminal altitude is lower than threshold 2.

[0243] Event LTM2H3: The signal quality of the serving cell is lower than threshold 1, and the terminal altitude is higher than threshold 2 and lower than threshold 3.

[0244] Event LTM3H1: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude exceeds a threshold.

[0245] Event LTM3H2: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude is lower than a threshold.

[0246] Event LTM3H3: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude exceeds threshold 1 but is lower than threshold 2.

[0247] Event LTM4H1: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude exceeds threshold 2.

[0248] Event LTM4H2: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude is lower than threshold 2.

[0249] Event LTM4H3: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude exceeds threshold 2 but is lower than threshold 3.

[0250] Event LTM5H1: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is higher than threshold 3.

[0251] Event LTM5H2: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is lower than threshold 3.

[0252] Event LTM5H3: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is higher than threshold 3 and lower than threshold 4.

[0253] In some embodiments, the height-based execution conditions that need to be evaluated to trigger the first action may include any combination of one or more of the height-based events and measurement-based events described above.

[0254] In some embodiments, the configuration information is also used to indicate the time window that needs to be met to trigger the first behavior.

[0255] In some embodiments, corresponding time windows can be configured for each event included in the above execution conditions. An event is considered satisfied only if all entry conditions for the event are met within the time window. Once an event is satisfied, if the event's exit conditions are met continuously within the time window, the event is considered no longer satisfied. The entry and exit conditions of the event are related to the network configuration thresholds, hysteresis values, offsets, etc.

[0256] In some embodiments, TCI State activation may also be referred to as early candidate cell synchronization, and / or fine synchronization, and / or fine tracking, and / or acquiring full timing information, and / or downlink synchronization, and / or pre-synchronization, etc.; TCI State may also be referred to as beam, and / or beam group, and / or beam pair, etc.

[0257] Step S202: Terminal 101 executes the first action.

[0258] In some embodiments, the terminal obtains its height; based on the height, it determines a first candidate cell from candidate cells associated with a first action; and then performs a first action on the first candidate cell; wherein the first candidate cell includes candidate cells associated with a first height range and / or a first execution condition, the first height range being the height range in which the current terminal height is located, and the first execution condition being an execution condition satisfied by the terminal height.

[0259] In some embodiments, if it is determined that the terminal altitude is within a first altitude range that needs to be satisfied to trigger the first action, the terminal may perform the first action on the first candidate cell corresponding to the first altitude range, wherein the first action includes a first advance synchronization and / or a second advance synchronization.

[0260] In some embodiments, if it is determined that the terminal height meets the first execution condition that needs to be evaluated to trigger the first action, the terminal may perform the first action on the first candidate cell corresponding to the first execution condition, wherein the first action includes a first advance synchronization and / or a second advance synchronization.

[0261] In some embodiments, if it is determined that the terminal height is within a first height range that needs to be met to trigger the first action, and the first execution condition that needs to be evaluated to trigger the first action is met, the terminal may perform the first action on the first candidate cell corresponding to the first height range and the first execution condition, wherein the first action includes a first advance synchronization and / or a second advance synchronization.

[0262] In some embodiments, the terminal may determine, based on configuration information received from the network device, several altitude ranges that need to be satisfied to trigger TCI state activation. If the terminal's altitude is determined to be within a first altitude range of several altitude ranges, the terminal may activate the TCI state of a first candidate cell corresponding to the first altitude range.

[0263] The TCI state can include one or more of the following: UL TCI state, DL TCI state, or joint TCI state. The first altitude range can correspond to multiple TCI states of a single candidate cell, or the first altitude range can correspond to multiple TCI states of different candidate cells.

[0264] In some embodiments, the terminal may determine, based on configuration information received from the network device, several execution conditions that need to be evaluated to trigger TCI state activation. If the terminal determines that it highly satisfies a first execution condition among the several execution conditions, the terminal may activate the TCI state of the first candidate cell corresponding to the first execution condition.

[0265] In some embodiments, the terminal can determine several altitude ranges that need to be satisfied to trigger uplink early synchronization based on configuration information received from the network device. If the terminal's altitude is determined to be within a first altitude range of several altitude ranges, the terminal can perform uplink early synchronization on a first candidate cell corresponding to the first altitude range and obtain the TA value of the first candidate cell. The terminal can obtain the TA value by sending a preamble to the first candidate cell or by calculating the TA value based on the terminal's TA.

[0266] In some embodiments, after obtaining the TA value of the first candidate cell, the obtained TA value can also be maintained, for example, by using a TA timer to maintain the obtained TA value.

[0267] In some embodiments, the terminal can determine several execution conditions that need to be evaluated to trigger uplink early synchronization based on configuration information received from the network device. If the terminal determines that it highly satisfies a first execution condition among the several execution conditions, the terminal can perform uplink early synchronization on a first candidate cell corresponding to the first execution condition and obtain the TA value of the first candidate cell. The terminal can also maintain the obtained TA value.

[0268] In some embodiments, the first action may further include deactivating the TCI state of the candidate cell and deleting the TA value of the candidate cell.

[0269] In some embodiments, if it is determined that the terminal height is not located in a second height range among several height ranges, and if the TCI state of the second candidate cell corresponding to the second height range was previously activated, the TCI state of the second candidate cell can be deactivated.

[0270] In some embodiments, if it is determined that the terminal height does not meet the second execution condition among several execution conditions, and if the TCI state of the second candidate cell corresponding to the second execution condition was previously activated, the TCI state of the second candidate cell can be deactivated.

[0271] In some embodiments, if it is determined that the terminal height is not within a second height range of several height ranges, and if the terminal maintains a TA value for a second candidate cell corresponding to the second height range, the TA value of the second candidate cell can be deleted.

[0272] In some embodiments, if it is determined that the terminal height does not meet the second execution condition among several execution conditions, and if the terminal maintains a TA value for a second candidate cell corresponding to the second height range, the TA value of the second candidate cell can be deleted.

[0273] The condition that the terminal height is not within the second height range can include at least one of the following two situations: the terminal height is not within the second height range; or the terminal height leaves the second height range (or the terminal moves out of the second height range).

[0274] The terminal height not meeting the second execution condition may include at least one of the following two situations: the terminal does not meet the second execution condition; the terminal changes from meeting the second execution condition to no longer meeting the second execution condition.

[0275] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal may activate the TCI state of the first candidate cell corresponding to the first altitude range, and may deactivate the TCI state of other candidate cells besides the first candidate cell if the TCI state of other candidate cells has been activated previously.

[0276] In some embodiments, when it is determined that the terminal height meets the first execution condition, the terminal may activate the TCI state of the first candidate cell corresponding to the first execution condition, and may deactivate the TCI state of other candidate cells other than the first candidate cell if the TCI state of other candidate cells was previously activated.

[0277] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal can perform early uplink synchronization on a first candidate cell corresponding to the first altitude range, obtain the TA value of the first candidate cell, and maintain the TA value of the first candidate cell. Simultaneously, the terminal can also delete the TA values ​​of other candidate cells it maintains besides the first candidate cell.

[0278] In some embodiments, when it is determined that the terminal height meets the first execution condition, the terminal can perform early uplink synchronization on the first candidate cell corresponding to the first execution condition, obtain the TA value of the first candidate cell, and maintain the TA value of the first candidate cell. Simultaneously, the terminal can also delete the TA values ​​of other candidate cells it maintains besides the first candidate cell.

[0279] In some embodiments, the configuration information sent by the network device to the terminal, indicating the configuration for triggering the first action, may include at least one of the following: triggering a third altitude range for deactivating the TCI state of the candidate cell, for example, the terminal altitude is higher than altitude threshold 2 or lower than altitude threshold 1; triggering a third execution condition for deactivating the TCI state of the candidate cell; triggering a fourth altitude range for deleting the TA value of the candidate cell; and triggering a fourth execution condition for deleting the TA value of the candidate cell.

[0280] The third and fourth altitude ranges can be the same, and identical third and fourth altitude ranges can correspond to the same candidate cells. Similarly, the third and fourth execution conditions can be the same, and identical third and fourth execution conditions can correspond to the same candidate cells.

[0281] In some embodiments, if it is determined that the terminal altitude is within a third altitude range, the terminal may deactivate the TCI state of the third candidate cell corresponding to the third altitude range.

[0282] In some embodiments, if it is determined that the terminal height meets the third execution condition, the terminal may deactivate the TCI state of the third candidate cell corresponding to the third execution condition.

[0283] In some embodiments, if it is determined that the terminal altitude is within the fourth altitude range, and if the terminal maintains a TA value for a fourth candidate cell corresponding to the fourth altitude range, then the TA value of the fourth candidate cell is deleted.

[0284] In some embodiments, if the terminal height satisfies the fourth execution condition, and the terminal maintains a TA value for a fourth candidate cell corresponding to the fourth height range, then the TA value of the fourth candidate cell is deleted.

[0285] In the above embodiments, the network device can configure the terminal with the altitude range and / or execution conditions required to perform altitude-based advance synchronization. This allows the terminal to perform advance synchronization on the corresponding candidate cells when the terminal altitude meets the configured altitude range and / or execution conditions, thereby optimizing the terminal's altitude-based mobility management, improving its altitude-based mobility handover performance, and reducing signaling overhead.

[0286] In some embodiments, the configuration information sent by the network device to the terminal can also be used to determine for the terminal the configuration required to trigger the second action. The second action may include deactivating the TCI state of the candidate cell and / or deleting the TA value of the candidate cell, which is equivalent to using a portion of the first action described in the above embodiments as the second action. In this case, the configuration information sent by the network device to the terminal can be used to determine for the terminal the configuration required to trigger the first action and / or the second action. The terminal can use the received configuration information to determine the configuration required to trigger the first action and the second action.

[0287] In some embodiments, the configuration information sent by the network device to the terminal may include configuration information related to the first action, used to determine for the terminal the configuration that needs to be satisfied to trigger the first action. The terminal may determine the configuration that needs to be satisfied to trigger the first action based on the configuration information, and further determine the configuration that needs to be satisfied to trigger the second action.

[0288] In some embodiments, the configuration information sent by the network device to the terminal may include configuration information related to the first action and configuration information related to the second action, which are used to determine for the terminal the configuration required to trigger the first action and the configuration required to trigger the second action, respectively.

[0289] Accordingly, in step S202 above, the terminal may perform the first action and / or the second action.

[0290] The first action may include: activating the TCI state of the candidate cell; obtaining the TA value of the candidate cell; and maintaining at least one of the TA values ​​of the candidate cell. The second action may include: deactivating the TCI state of the candidate cell, and / or deleting the TA value of the candidate cell.

[0291] In some embodiments, if it is determined that the terminal height is within a first height range of several height ranges, a first action may be performed on a first candidate cell corresponding to the first height range.

[0292] In some embodiments, if it is determined that the terminal height is not located in a second height range among several height ranges, a second action is performed on the second candidate cell corresponding to the second height range.

[0293] The condition that the terminal height is not within the second height range can include at least one of the following two situations: the terminal height is not within the second height range; or the terminal height leaves the second height range (or the terminal moves out of the second height range).

[0294] In some embodiments, if it is determined that the terminal height does not meet the second execution condition among several execution conditions, a second action is performed on the second candidate cell corresponding to the second execution condition.

[0295] The terminal height not meeting the second execution condition may include at least one of the following two situations: the terminal does not meet the second execution condition; the terminal changes from meeting the second execution condition to no longer meeting the second execution condition.

[0296] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal may activate the TCI state of the first candidate cell corresponding to the first altitude range, and may deactivate the TCI state of other candidate cells besides the first candidate cell if the TCI state of other candidate cells has been activated previously.

[0297] In some embodiments, when it is determined that the terminal height meets the first execution condition, the terminal may activate the TCI state of the first candidate cell corresponding to the first execution condition, and may deactivate the TCI state of other candidate cells other than the first candidate cell if the TCI state of other candidate cells was previously activated.

[0298] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal can perform early uplink synchronization on a first candidate cell corresponding to the first altitude range, obtain the TA value of the first candidate cell, and maintain the TA value of the first candidate cell. Simultaneously, the terminal can also delete the TA values ​​of other candidate cells it maintains besides the first candidate cell.

[0299] In some embodiments, when it is determined that the terminal height meets the first execution condition, the terminal can perform early uplink synchronization on the first candidate cell corresponding to the first execution condition, obtain the TA value of the first candidate cell, and maintain the TA value of the first candidate cell. Simultaneously, the terminal can also delete the TA values ​​of other candidate cells it maintains besides the first candidate cell.

[0300] In some embodiments, the configuration information related to the second action sent by the network device to the terminal may be used to indicate the configuration that triggers the second action, and may include at least one of the following: triggering a third altitude range for deactivating the TCI state of the candidate cell, for example, the terminal altitude is higher than altitude threshold 2 or lower than altitude threshold 1; triggering a third execution condition for deactivating the TCI state of the candidate cell; triggering a fourth altitude range for deleting the TA value of the candidate cell; triggering a fourth execution condition for deleting the TA value of the candidate cell.

[0301] The third and fourth altitude ranges can be the same, and identical third and fourth altitude ranges can correspond to the same candidate cells. Similarly, the third and fourth execution conditions can be the same, and identical third and fourth execution conditions can correspond to the same candidate cells.

[0302] In some embodiments, if it is determined that the terminal altitude is within a third altitude range, the terminal may deactivate the TCI state of the third candidate cell corresponding to the third altitude range.

[0303] In some embodiments, if it is determined that the terminal height meets the third execution condition, the terminal may deactivate the TCI state of the third candidate cell corresponding to the third execution condition.

[0304] In some embodiments, if it is determined that the terminal altitude is within the fourth altitude range, and if the terminal maintains a TA value for a fourth candidate cell corresponding to the fourth altitude range, then the TA value of the fourth candidate cell is deleted.

[0305] In some embodiments, if the terminal height satisfies the fourth execution condition, and the terminal maintains a TA value for a fourth candidate cell corresponding to the fourth height range, then the TA value of the fourth candidate cell is deleted.

[0306] In the above embodiments, the terminal can determine the altitude range and / or execution conditions required to execute the first and second actions based on the configuration information received from the network device. Thus, when the terminal altitude meets the configured altitude range and / or execution conditions, the terminal can execute the first and / or second actions on the corresponding candidate cells, thereby optimizing the terminal's altitude-based mobility management, improving its altitude-based mobility handover performance, and reducing signaling overhead.

[0307] In some embodiments, the configuration information is further used to indicate a third threshold value, which is a threshold value for the measurement result that needs to be evaluated to trigger the first action and / or the second action.

[0308] The measurement results may include at least one of the following: measurement results for the candidate cell, the candidate cell's beam, and the candidate cell's TCI state. Correspondingly, the third threshold may be a threshold value for the measurement results for the candidate cell, the candidate cell's beam, and the candidate cell's TCI state that need to be evaluated to trigger the first and / or second actions.

[0309] In some embodiments, before performing the first action on the first candidate cell, the terminal needs to evaluate the measurement results of the first candidate cell. If the measurement results meet the corresponding third threshold value, the first action can be performed; otherwise, the first action is not performed and / or the second action on the first candidate cell is performed.

[0310] In some embodiments, the terminal may perform a first action on the first candidate cell if it determines that the terminal height is within a first height range and / or the measurement result of the first candidate cell corresponding to the first height range meets a third threshold value.

[0311] In some embodiments, the terminal may perform a second action on the third candidate cell (or the fourth candidate cell) if it determines that the terminal height is within a third height range (or a fourth height range) and / or the measurement result of the third candidate cell (or the fourth candidate cell corresponding to the third height range) does not meet a third threshold value.

[0312] In some embodiments, the terminal may perform a first action on the first candidate cell if it determines that the terminal height meets a first execution condition and / or the measurement result of the first candidate cell corresponding to the first height range meets a third threshold value.

[0313] In some embodiments, the terminal may perform a second action on the third candidate cell (or the fourth candidate cell) if it is determined that the terminal height meets the third execution condition (or the fourth execution condition) and / or the measurement result of the third candidate cell (or the fourth candidate cell corresponding to the fourth execution condition) does not meet the third threshold value.

[0314] By setting a threshold value corresponding to the measurement results of candidate cells, unnecessary advance synchronization can be reduced, thus lowering signaling consumption.

[0315] In some embodiments, the configuration information is further used to instruct the terminal to trigger at least one of the following mobility operations based on altitude: sending the terminal's altitude information; measuring a first candidate cell or the beam of a first candidate cell; the first candidate cell being a candidate cell for performing the first action; mobility measurement; sending a measurement report of the mobility measurement; and conditional mobility operation.

[0316] In some implementations, the terminal can send altitude information to the network device based on its altitude. For example, when the change in the terminal's altitude reaches a certain threshold, the terminal sends its altitude information to the network device; or after triggering LTM measurement based on altitude, the terminal's altitude information is included in the measurement report sent to the network device.

[0317] In some embodiments, the terminal can perform measurements of the corresponding LTM candidate cell or the beam corresponding to the candidate cell based on altitude. Different altitude ranges can be associated with different cells under test or beams under test. If the terminal's altitude is within the corresponding altitude range, the terminal performs LTM measurements on the corresponding cell under test or beam under test; otherwise, the corresponding LTM measurements are not performed (or are stopped).

[0318] In some embodiments, the terminal may trigger LTM measurement reporting based on altitude. The terminal may evaluate altitude-based LTM measurement events to determine whether to trigger the corresponding LTM measurement reporting.

[0319] Among them, height-based LTM measurement events can be height-based LTM measurement events, or LTM measurement events based on both height and measurement results; or a combination of height-based LTM events and measurement-based LTM events.

[0320] In some embodiments, the terminal may trigger a conditional LTM (C-LTM) based on the height.

[0321] In some embodiments, the terminal can select the target beam for C-LTM based on altitude. Different altitude ranges are associated with different beams; if the terminal's altitude falls within a corresponding altitude range, the terminal selects the appropriate beam to perform C-LTM. For example, if multiple beams meet the C-LTM execution conditions, the beam corresponding to the terminal's altitude range is selected as the target beam. Alternatively, the terminal may only evaluate the C-LTM execution conditions for the beam corresponding to its altitude range.

[0322] In some embodiments, the terminal evaluates height-based C-LTM execution conditions to determine whether to execute C-LTM. These height-based C-LTM execution conditions can be height-based C-LTM events, height- and measurement-based C-LTM events, or a combination of height-based and measurement-based C-LTM events.

[0323] It should be noted that the LTM measurement in the above embodiments can be any one or more of the following: Layer 1 L1 measurement, Channel State Information (CSI) measurement, LTM measurement, Layer 2 L2 measurement, measurement results reported through Uplink Control Information (UCI), and measurement results reported through MAC CE.

[0324] C-LTM can be referred to as any one or more of the following: condition-triggered mobility, condition-triggered L1 mobility, and condition-triggered beam-level mobility.

[0325] In some embodiments, C-LTM can also be a conditional handover CHO.

[0326] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0327] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.

[0328] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0329] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0330] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0331] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0332] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0333] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0334] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0335] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0336] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0337] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0338] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0339] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0340] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0341] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0342] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0343] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0344] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0345] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0346] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S202. For example, step 201 may be implemented as a standalone embodiment, step 202 may be implemented as a standalone embodiment, and steps 201 and 202 may be implemented as standalone embodiments, but are not limited thereto. FIG2G is a schematic flowchart of a mobility operation method according to an embodiment of this disclosure. As shown in FIG2G, the embodiments of this disclosure relate to a mobility operation method, which includes the following steps:

[0347] Step S211: The terminal receives configuration information, which is used to determine the first altitude range that needs to be met to trigger TCI state activation of the candidate cell, and / or the first execution condition that needs to be evaluated to trigger TCI state activation of the candidate cell.

[0348] Step S212: When the terminal determines that the terminal height is within the first height range and / or the terminal height meets the first execution condition, the terminal performs TCI state activation for the candidate cell.

[0349] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal may activate the TCI state of the first candidate cell corresponding to the first altitude range.

[0350] In some embodiments, if it is determined that the terminal height meets the first execution condition, the terminal may activate the TCI state of the first candidate cell corresponding to the first execution condition.

[0351] Figure 2H is a flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2G, the present disclosure relates to a mobility operation method, which includes the following steps:

[0352] Step S221: The terminal receives configuration information, which is used to determine the first altitude range that needs to be met to trigger TCI state activation of the candidate cell, and / or the first execution condition that needs to be evaluated to trigger TCI state activation of the candidate cell.

[0353] Step S222: When the terminal determines that the terminal height is within the first height range and / or the terminal height meets the first execution condition, the terminal performs TCI state activation for the candidate cell.

[0354] Step S223: If the terminal determines that the terminal height is not within the first height range and / or the terminal height does not meet the first execution condition, the terminal performs TCI state activation for the candidate cell.

[0355] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal may activate the TCI state of the first candidate cell corresponding to the first altitude range; if the terminal altitude range subsequently leaves the first altitude range, the TCI state of the first candidate cell may be deactivated.

[0356] In some embodiments, if the terminal height is determined to meet the first execution condition, the terminal may activate the TCI state of the first candidate cell corresponding to the first execution condition; if the terminal height range no longer meets the first execution condition, the TCI state of the first candidate cell may be deactivated.

[0357] Figure 2I is a flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2G, the present disclosure relates to a mobility operation method, which includes the following steps:

[0358] Step S231: The terminal receives configuration information, which is used to determine the third height range that needs to be met to trigger the TCI state deactivation of the candidate cell, and / or the third execution condition that needs to be evaluated to trigger the TCI state deactivation of the candidate cell.

[0359] Step S232: When the terminal determines that the terminal height is within the third height range and / or the terminal height meets the third execution condition, the terminal performs TCI state deactivation on the candidate cell.

[0360] In some embodiments, if it is determined that the terminal altitude is within a third altitude range, and the TCI state of the third candidate cell corresponding to the third altitude range has been activated before, the terminal may deactivate the TCI state of the third candidate cell.

[0361] In some embodiments, if it is determined that the terminal height satisfies the third execution condition, and the TCI state of the third candidate cell corresponding to the third execution condition has been activated before, the terminal may deactivate the TCI state of the third candidate cell.

[0362] Figure 2J is a flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2G, the present disclosure relates to a mobility operation method, which includes the following steps:

[0363] Step S241: The terminal receives configuration information, which is used to determine the first altitude range that needs to be met to trigger TA acquisition of the candidate cell, and / or the first execution condition that needs to be evaluated to trigger TA acquisition of the candidate cell.

[0364] Step S242: When the terminal determines that its height is within the first height range and / or its height meets the first execution condition, the terminal performs TA acquisition for the candidate cell.

[0365] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal can obtain the TA value of the first candidate cell corresponding to the first altitude range and maintain the TA value of the first candidate cell.

[0366] In some embodiments, when it is determined that the terminal altitude meets the first execution condition, the terminal can obtain the TA value of the first candidate cell corresponding to the first altitude range and maintain the TA value of the first candidate cell. Figure 2K is a flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2G, an embodiment of the present disclosure relates to a mobility operation method, which includes the following steps:

[0367] Step S251: The terminal receives configuration information, which is used to determine the first altitude range that needs to be met to trigger TA acquisition of the candidate cell, and / or the first execution condition that needs to be evaluated to trigger TA acquisition of the candidate cell.

[0368] Step S252: When the terminal determines that its height is within the first height range and / or its height meets the first execution condition, the terminal performs TA acquisition for the candidate cell.

[0369] Step S253: If the terminal determines that the terminal height is not within the first height range and / or the terminal height does not meet the first execution condition, the terminal deletes the TA value of the maintained candidate cell.

[0370] In some embodiments, when it is determined that the terminal altitude is within a first altitude range, the terminal can obtain the TA value of the first candidate cell corresponding to the first altitude range and maintain the TA value of the first candidate cell; if the terminal altitude range subsequently leaves the first altitude range, the maintained TA value of the first candidate cell can be deleted.

[0371] In some embodiments, when it is determined that the terminal height meets the first execution condition, the terminal can obtain the TA value of the first candidate cell corresponding to the first height range and maintain the TA value of the first candidate cell; if the terminal height range subsequently leaves the first height range, the maintained TA value of the first candidate cell can be deleted.

[0372] Figure 2L is a flowchart illustrating a mobility operation method according to an embodiment of the present disclosure. As shown in Figure 2G, the present disclosure relates to a mobility operation method, which includes the following steps:

[0373] Step S261: The terminal receives configuration information, which is used to determine the third altitude range that the TA value for triggering the deletion of candidate cells needs to meet, and / or the third execution condition that needs to be evaluated for the TA value for triggering the deletion of candidate cells.

[0374] Step S262: When the terminal determines that the terminal height is within the third height range and / or the terminal height meets the third execution condition, the terminal deletes the TA value of the candidate cell.

[0375] In some embodiments, if it is determined that the terminal altitude is within a third altitude range, and if the terminal maintains a TA value for a third candidate cell corresponding to the third altitude range, the terminal may delete the TA value of the first candidate cell it maintains.

[0376] In some embodiments, if it is determined that the terminal height meets the third execution condition, and if the terminal maintains a TA value for a third candidate cell corresponding to the third height range, the terminal may delete the TA value of the first candidate cell it maintains.

[0377] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0378] This disclosure relates to a mobility operation method, the main inventive points of which are:

[0379] In some embodiments 1: the UE, based on the TCI State of the highly activated / deactivated candidate cell, includes any one or more of the following methods:

[0380] Method 1: The network side associates the UE's altitude range with the TCI State. When the UE is in a specific altitude range, the UE activates the TCI State corresponding to this altitude range. When the UE leaves the corresponding altitude range, the UE deactivates the TCI State corresponding to this altitude range.

[0381] Method 2: Configure height-based TCI state activation / deactivation conditions on the network side. Different TCI states are associated with different height conditions. When the UE's height meets the height-based conditions, the UE activates the corresponding TCI state. When the UE's height no longer meets the conditions, the UE deactivates the corresponding TCI state.

[0382] In some embodiments: the UE performs early synchronization of candidate cells based on altitude: early uplink synchronization and TA acquisition and corresponding TA maintenance, including any one or more of the following methods:

[0383] Method 1: The network side associates the UE's altitude range with candidate cells. When the UE is in a specific altitude range, the UE performs advance TA acquisition for the corresponding candidate cells and maintains TA values ​​for the candidate cells. When the UE leaves the corresponding altitude range, the UE deletes the TA values ​​maintained for the candidate cells.

[0384] Method 2: Configure the activation conditions for altitude-based TA acquisition on the network side. Different candidate cells are associated with different altitude conditions. When the UE's altitude meets the altitude-based conditions, the UE performs early TA acquisition for the corresponding candidate cell and maintains the TA value for the candidate cell. When the UE's altitude no longer meets the conditions, the UE deletes the TA value maintained for this candidate cell.

[0385] In some embodiments, the specific related methods are as follows, each sentence in the following text can correspond to an independent embodiment, and each line in the following text can correspond to an independent embodiment or implementation.

[0386] Specifically, this disclosure includes, but is not limited to, any one or more of the following (where a point refers to x, xx, xxx, where x can be any integer), for example, points 1, 2, and 3; for example, points 1.1.1 and 3.2:

[0387] 1. Mobility configuration configured by the network side for the UE, wherein the mobility configuration information includes the configuration information required for the UE to perform the first action (or the first operation or the first procedure), and the configuration information of the mobility candidate cells (the network side can configure multiple candidate cells and their corresponding configurations required for the first action for the UE at the same time).

[0388] 1.1 The configuration information required to execute the first action (or first operation) includes any one or more of the following:

[0389] 1.1.1 The UE executes the information required for the activation of the candidate cell's TCI state(s), such as the information used to configure the candidate cell's TCI-related information for use when activating the TCI state.

[0390] 1.1.2 Configuration required for UE to perform advance synchronization: For example, the configuration required when the UE performs advance RACH to obtain TA information of candidate cells.

[0391] 2. The network side configures the first line for the UE and the associated altitude range or the altitude-based first line is the execution condition. Different candidate cells / candidate cell beams / candidate cell TCI State(s) correspond to different altitude ranges or altitude-based first line execution conditions. Different candidate cells / candidate cell beams / candidate cell TCI State(s) can be represented by candidate configuration identifier, candidate cell identifier, candidate beam identifier, SSB identifier corresponding to the candidate beam, and TCI state ID.

[0392] 2.1 In some embodiments, multiple different candidate cells / candidate cell beams / candidate cell TCI State(s) may correspond to the same or different altitude ranges or altitude-based first behavior execution conditions; that is, one altitude range or altitude-based first behavior execution condition may correspond to multiple candidate cells / candidate cell beams / candidate cell TCI State(s).

[0393] 3. Based on 1 to 2, when the UE's altitude is within the associated altitude range or the UE meets the altitude-based execution conditions, the UE executes the first action, wherein the first action includes any one or more of the following UE actions:

[0394] 3.1 UE activates candidate cell's TCI state.

[0395] 3.1.1 The TCI state of the candidate cell corresponding to the altitude range where the UE is activated (the execution conditions are met), where the TCI state may include UL TCI state and / or DL ​​or joint TCI state; an altitude range may correspond to multiple TCI states of one candidate cell or multiple TCI states of different candidate cells.

[0396] 3.1.2 The UE deactivates all TCI states except for the TCI state of the candidate cell corresponding to its altitude range (the execution conditions are met), if these TCI states were previously activated (this can also be described by the second line in 4).

[0397] 3.2 The UE performs advance synchronization for candidate cells.

[0398] 3.2.1 The UE performs advance synchronization for candidate cells corresponding to its altitude range (the execution conditions are met), including performing advance uplink synchronization to obtain the TA value of the candidate cell and maintaining the obtained TA value through the TA timer; wherein the UE can obtain the TA by sending a preamble to the candidate cell or by calculating the TA value based on the UE's TA.

[0399] 3.2.2 The UE deletes the TA values ​​of the candidate cells it maintains, except for those corresponding to its altitude range (the execution conditions it meets), if any. (This can also be described by the second line in section 4).

[0400] 4. Based on 1 to 2, if the UE's height is not within the height range or the UE does not meet the height-based execution conditions, the UE will execute the second action.

[0401] 4.1 Wherein, when the UE's height is not within the height range or the UE does not meet the height-based execution conditions, it includes any one or more of the following two cases:

[0402] 4.1.1 The UE's height is not within the height range or the UE does not meet the height-based execution conditions.

[0403] 4.1.2 The UE's height leaves the height range (or the UE moves out of the height range) or the UE changes from meeting the height-based execution conditions to not meeting the execution conditions.

[0404] 4.2 The second behavior includes any one or more of the following UE behaviors:

[0405] 4.2.1 The UE deactivates the TCI state of the candidate cell corresponding to the height range (if the execution conditions are not met), wherein the TCI state may include UL TCI state and / or DL ​​or joint TCI state; a height range may correspond to multiple TCI states of one candidate cell or multiple TCI states of different candidate cells.

[0406] 4.2.2 The UE deletes the TA value of the candidate cell corresponding to the height range (the execution condition is not met), if any.

[0407] 5. Based on 2, the height range associated with the first behavior in 2 can be configured by any one or more of the following parameters:

[0408] 5.1 Minimum altitude threshold: 1altitudeMin;

[0409] 5.2 Maximum altitude threshold value 2altitudeMax;

[0410] 5.3 Hysteresis value (altitudeHyst);

[0411] If both 5.1 and 5.2 are configured, the altitude range is altitudeMin≤UE altitude≤altitudeMax;

[0412] If configured in 5.1, the altitude range is altitudeMin ≤ UE altitude;

[0413] If 5.2 is configured, the altitude range is UE altitude≤altitudeMax;

[0414] The hysteresis value is used to assess whether the UE has left this altitude range. When the UE altitude satisfies altitudeMin≤UE altitude≤altitudeMax, if the UE altitude satisfies (altitudeMin–altitudeHyst)≤UE altitude≤(altitudeMax+altitudeHyst), then the UE is considered to be in this altitude range; otherwise, the UE is considered to have left this altitude range (or is not in this altitude range).

[0415] In addition, the first action can also be associated with the corresponding measurement result threshold value. Only when the UE's height meets the height range and the measurement result of the candidate cell / candidate cell's beam / candidate cell's TCI State(s) corresponding to the height range meets the threshold value, the UE performs the first action for the corresponding candidate cell / candidate cell's beam / candidate cell's TCI State(s). If the conditions are not met, the first action is not performed or the second action is performed.

[0416] 6 is based on 2, where the first behavior execution condition based on height can be configured through any one or more of the following events:

[0417] 6.1 Height-based events:

[0418] 6.1.1 Event H1: Aerial UE altitude exceeds a threshold.

[0419] 6.1.2 Event H2: Aerial UE altitude becomes lower than a threshold;

[0420] 6.1.3 The terminal altitude exceeds threshold 1 and is lower than threshold 2 (Event H3: Aerial UE altitude becomes higher than a threshold 1 and aerial UE altitude becomes lower than a threshold 2);

[0421] 6.2 Events based on altitude and measurement results:

[0422] 6.2.1 Event LTM2H1: The signal quality of the serving cell is lower than threshold 1 and the terminal altitude exceeds threshold 2.

[0423] 6.2.2 Event LTM2H2: The signal quality of the serving cell is lower than threshold 1 and the terminal altitude is lower than threshold 2.

[0424] 6.2.3 Event LTM2H3: The signal quality of the serving cell is lower than threshold 1, and the terminal altitude is higher than threshold 2 and lower than threshold 3.

[0425] 6.2.4 Event LTM3H1: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude exceeds a threshold.

[0426] 6.2.5 Event LTM3H2: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude is lower than a threshold.

[0427] 6.2.6 Event LTM3H3: The signal quality of the candidate cell is better than that of the serving cell by an offset, and the terminal altitude exceeds threshold 1 but is lower than threshold 2.

[0428] 6.2.7 Event LTM4H1: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude exceeds threshold 2.

[0429] 6.2.8 Event LTM4H2: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude is lower than threshold 2.

[0430] 6.2.9 Event LTM4H3: The signal quality of the candidate cell exceeds threshold 1, and the terminal altitude exceeds threshold 2 but is lower than threshold 3.

[0431] 6.2.10 Event LTM5H1: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is higher than threshold 3.

[0432] 6.2.11 Event LTM5H2: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is lower than threshold 3.

[0433] 6.2.12 Event LTM5H3: The signal quality of the serving cell is lower than threshold 1 and the signal quality of the candidate cell is higher than threshold 2, and the terminal altitude is higher than threshold 3 and lower than threshold 4.

[0434] 6.3 Measurement-based execution conditions:

[0435] 6.3.1 Event LTM2: The signal quality of the serving cell is lower than the absolute threshold.

[0436] 6.3.2 Event LTM3: The signal quality of the candidate cell is better than that of the serving cell by an offset.

[0437] 6.3.3 Event LTM4: The signal quality of the candidate cell exceeds the absolute threshold.

[0438] 6.3.4 Event LTM5: The signal quality of the serving cell is lower than the absolute threshold 1, and the signal quality of the candidate cell is higher than the absolute threshold 2.

[0439] 6.4 Among them, the execution conditions based on height can be associated with any one or more of the events described in 6.1 and 6.3 simultaneously:

[0440] In addition to the corresponding height-based and measurement-based thresholds, the configuration for the aforementioned events also includes height, hysteresis value corresponding to the measurement result, and offset. Furthermore, a trigger time is configured for each event. An event is considered satisfied if its entry conditions are met within the trigger time TTT. If, after the event is satisfied, its exit conditions are met within the TTT, the event is considered no longer satisfied. The entry and exit conditions of the events are related to the network-configured thresholds, hysteresis values, and offsets.

[0441] In some embodiments, TCI State(s) activation may also be referred to as early candidate cell synchronization / fine synchronization / fine tracking and acquiring full timing information / downlink synchronization / pre-synchronization, etc.; TCI State(s) may also be referred to as beam / beam group / beam pair, etc.

[0442] In some embodiments, the UE performs any one or more of the following mobility operations based on altitude:

[0443] Each sentence below can correspond to an independent embodiment, and each line below can correspond to an independent embodiment or implementation.

[0444] Specifically, this embodiment includes, but is not limited to, any one or more points from the following (where a point refers to x, xx, xxx, where x can be any integer), for example, points 1, 2, and 3; for example, points 1.1.1 and 3.2.

[0445] 1. UE reports altitude information based on altitude:

[0446] 1.1 When the change in the UE's altitude information reaches a certain threshold, the UE reports its altitude;

[0447] 1.2 The measurement report for height-triggered measurement reporting in section 3> includes the UE's height information;

[0448] 2. The UE performs measurements of the corresponding LTM candidate cells or the beams corresponding to the candidate cells based on the altitude:

[0449] 2.1 Different altitude ranges are associated with different cells under test / beams under test. If the UE's altitude is within the corresponding altitude range, the UE performs LTM measurements on the corresponding cell under test / beam under test; otherwise, the corresponding LTM measurements are not performed (or are stopped).

[0450] 3. UE measurement reporting based on height-triggered LTM measurements:

[0451] 3.1 UE assessment uses altitude-based LTM measurement events to determine whether to trigger corresponding LTM measurement reporting;

[0452] 3.1.1 Among them, the height-based LTM measurement event can be a height-based LTM measurement event, or an LTM measurement event based on both height and measurement results; or a combination of height-based LTM events and measurement-based LTM events;

[0453] 4. UE-based height-triggered C-LTM (Conditional LTM):

[0454] 4.1 UE-based altitude-selective C-LTM target beam;

[0455] 4.1.1 Different altitude ranges are associated with different beams. If the UE's altitude is within the corresponding altitude range, the UE selects the corresponding beam to perform CLTM.

[0456] 4.1.1.1 For example, if multiple beams meet the execution conditions of C-LTM, the beam corresponding to the altitude range where the UE is located is selected as the target beam;

[0457] 4.1.1.2 For example, the UE only evaluates the C-LTM execution conditions for the beam corresponding to the altitude range where the UE is located;

[0458] 4.2 UE evaluation determines whether to execute C-LTM based on the high level of C-LTM execution conditions;

[0459] 4.2.1 The execution conditions for height-based C-LTM can be height-based C-LTM events, or C-LTM events based on both height and measurement results; or a combination of height-based C-LTM events and measurement-based C-LTM events.

[0460] The configuration methods associated with different altitude ranges and different cells / beams under test in the above-mentioned inventive points are described in other embodiments. Details of altitude-based events are described in the invention description, and details of events based on both altitude and measurement results are described in other embodiments. Altitude-based LTM measurement events and / or altitude-based C-LTM events are described in other embodiments; wherein altitude-based LTM measurement events and / or altitude-based C-LTM events are described in other embodiments.

[0461] In some embodiments, an LTM measurement can be any one or more of the following: an L1 measurement, a CSI measurement, an LTM measurement, an L2 measurement, a measurement result reported via UCI, or a measurement result reported via MAC CE.

[0462] In some embodiments, C-LTM may be referred to as any one or more of condition-triggered mobility, condition-triggered L1 mobility, and condition-triggered beam-level mobility.

[0463] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0464] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0465] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0466] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0467] Figure 3A is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. The terminal 3100 is used to execute any of the above methods. In some embodiments, as shown in Figure 3A, the terminal 3100 may include at least one of a transceiver module 3101, a processing module 3102, etc.

[0468] In some embodiments, the transceiver module 3101 is used to receive configuration information; the processing module 3102 is used to determine, based on the configuration information, the configuration required to trigger the first action, the first action including advance synchronization related to altitude-based mobility operations.

[0469] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., steps S201, S211, S221, S231, S241, S251, S261, but not limited thereto), which will not be elaborated here.

[0470] Optionally, the above processing module is used to execute at least one of the other steps executed by the terminal 101 in any of the above methods (e.g., step 202, step S212, step S222, step S232, step S242, step S252, step S262, but not limited thereto), which will not be elaborated here.

[0471] Optionally, advance synchronization includes at least one of the following: a first advance synchronization, including advance synchronization related to downlink; and a second advance synchronization, including advance synchronization related to uplink.

[0472] Optionally, the first advance synchronization includes activating the Transmission Configuration Indication (TCI) state of the candidate cell.

[0473] Optionally, the second advance synchronization includes obtaining the timing advance (TA) of the candidate cell.

[0474] Optionally, the configuration information is used to indicate at least one of the following: the altitude range that needs to be met to trigger the first action; the altitude-based execution conditions that need to be evaluated to trigger the first action; and the configuration of the candidate cells associated with the first action.

[0475] Optionally, the candidate cell configuration is used to indicate at least one of the following: the candidate cell; the candidate cell's beam; the candidate cell's TCI state.

[0476] Optionally, the configuration of a candidate cell may include at least one of the following: a configuration identifier for the candidate cell; an identifier for the candidate cell; an identifier for the candidate beam; an identifier for the synchronization signal block (SSB) corresponding to the candidate beam; or an identifier for the TCI state of the candidate cell.

[0477] Optionally, the processing module is further configured to obtain the terminal height; determine a first candidate cell from the candidate cells associated with the first action based on the terminal height; wherein the first candidate cell includes candidate cells associated with a first height range and / or a first execution condition, the first height range being the height range in which the terminal height is located, and the first execution condition being the execution condition satisfied by the terminal height; and execute the first action on the first candidate cell.

[0478] Optionally, the first action is performed on the first candidate cell, including at least one of the following: activating the TCI state of the first candidate cell; obtaining the TA value of the first candidate cell; and maintaining the TA value of the first candidate cell.

[0479] Optionally, the configuration information is also used to determine the configuration that needs to be met to trigger the second action: the second action includes at least one of the following: deactivation of the TCI state of the candidate cell; deletion of the TA value of the candidate cell.

[0480] Optionally, the processing module is further configured to determine, based on the terminal height, that the terminal has left the second height range, and / or the terminal height no longer meets the second execution condition, and to perform the second action on the second candidate cell; wherein the second candidate cell includes candidate cells associated with the second height range and / or the second execution condition.

[0481] Optionally, the height range that triggers the first behavior is determined by at least one of the following parameters: a first threshold value, used to indicate the lower limit of the height range; a second threshold value, used to indicate the upper limit of the height range; and a hysteresis value, used to assess whether the terminal is located at or away from the reserved height of the height range.

[0482] Optionally, the configuration information is further used to indicate a third threshold value, which is a threshold value of the measurement result that needs to be evaluated to trigger the first action; the measurement result of the first candidate cell satisfies the third threshold value.

[0483] Optionally, the altitude-based execution conditions include at least one of the following: the terminal altitude exceeds a first altitude threshold; the terminal altitude is lower than a second altitude threshold; the signal quality of the serving cell is lower than a first quality threshold; the signal quality of the candidate cell is better than the signal quality of the serving cell by a first offset; or the signal quality of the candidate cell exceeds a second quality threshold.

[0484] Optionally, the configuration information is also used to indicate the time window that needs to be met to trigger the first action.

[0485] Optionally, the configuration information is also used to instruct the terminal to trigger at least one of the following mobility operations based on altitude: sending altitude information of the terminal; measuring a first candidate cell or the beam of a first candidate cell; the first candidate cell being a candidate cell for performing the first action; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation.

[0486] Figure 3B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 3200 is used to perform any of the above methods. In some embodiments, as shown in Figure 3B, the network device 3200 may include at least one of a transceiver module 3201, a processing module 3202, etc.

[0487] In some embodiments, the transceiver module 3201 is used to send configuration information; the processing module 3202 is used to determine the configuration information, which is used to determine the configuration that needs to be met to trigger the first action, the first action including advance synchronization related to altitude-based mobility operations.

[0488] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., steps S201, S211, S221, S231, S241, S251, S261, but not limited thereto), which will not be elaborated here.

[0489] Optionally, the above processing module is used to perform at least one of the other steps executed by terminal 101 in any of the above methods, which will not be elaborated here.

[0490] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0491] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0492] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0493] Optionally, advance synchronization includes at least one of the following: a first advance synchronization, including advance synchronization related to downlink; and a second advance synchronization, including advance synchronization related to uplink.

[0494] Optionally, the first advance synchronization includes activating the Transmission Configuration Indication (TCI) state of the candidate cell.

[0495] Optionally, the second advance synchronization includes obtaining the timing advance (TA) of the candidate cell.

[0496] Optionally, the configuration information is used to indicate at least one of the following: the altitude range that needs to be met to trigger the first action; the altitude-based execution conditions that need to be evaluated to trigger the first action; and the configuration of the candidate cells associated with the first action.

[0497] Optionally, the candidate cell configuration is used to indicate at least one of the following: the candidate cell; the candidate cell's beam; the candidate cell's TCI state.

[0498] Optionally, the configuration of a candidate cell may include at least one of the following: a configuration identifier for the candidate cell; an identifier for the candidate cell; an identifier for the candidate beam; an identifier for the synchronization signal block (SSB) corresponding to the candidate beam; or an identifier for the TCI state of the candidate cell.

[0499] Optionally, the configuration information is also used to determine the configuration that needs to be met to trigger the second action: the second action includes at least one of the following: deactivation of the TCI state of the candidate cell; deletion of the TA value of the candidate cell.

[0500] Optionally, the height range that triggers the first behavior is determined by at least one of the following parameters: a first threshold value, used to indicate the lower limit of the height range; a second threshold value, used to indicate the upper limit of the height range; and a hysteresis value, used to assess whether the terminal is located at or away from the reserved height of the height range.

[0501] Optionally, the configuration information is also used to indicate a third threshold value, which is a threshold value of the measurement result that needs to be evaluated to trigger the first action; the measurement result of the first candidate cell satisfies the third threshold value.

[0502] Optionally, the altitude-based execution conditions include at least one of the following: the terminal altitude exceeds a first altitude threshold; the terminal altitude is lower than a second altitude threshold; the signal quality of the serving cell is lower than a first quality threshold; the signal quality of the candidate cell is better than the signal quality of the serving cell by a first offset; or the signal quality of the candidate cell exceeds a second quality threshold.

[0503] Optionally, the configuration information is also used to indicate the time window that needs to be met to trigger the first action.

[0504] Optionally, the configuration information is also used to instruct the terminal to trigger at least one of the following mobility operations based on altitude: sending altitude information of the terminal; measuring a first candidate cell or the beam of a first candidate cell; the first candidate cell being a candidate cell for performing the first action; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation.

[0505] Figure 4A is a schematic diagram of the structure of the communication device 4100 proposed in an embodiment of this disclosure. The communication device 4100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 4100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0506] As shown in Figure 4A, the communication device 4100 is used to execute any of the above methods. In some embodiments, the communication device 4100 includes one or more processors 4101. The processor 4101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 4100 is used to execute any of the above methods. Optionally, one or more processors 4101 are used to invoke instructions to cause the communication device 4100 to execute any of the above methods.

[0507] In some embodiments, the communication device 4100 further includes one or more transceivers 4102. When the communication device 4100 includes one or more transceivers 4102, the transceiver 4102 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201, S211, S221, S231, S241, S251, S261, but not limited thereto), and the processor 4101 performs at least one of other steps (e.g., steps 202, S212, S222, S232, S242, S252, S262, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0508] In some embodiments, the communication device 4100 further includes one or more memories 4103 for storing data and / or instructions. Optionally, one or more processors 4101 are used to invoke instructions stored in the memory 4103 to cause the communication device 4100 to perform any of the above methods. Optionally, all or part of the memory 4103 may also be located outside the communication device 4100. In an optional embodiment, the communication device 4100 may include one or more interface circuits 4104. Optionally, the interface circuit 4104 is connected to the memory 4102 and can be used to receive data and / or instructions from the memory 4102 or other devices, and can be used to send data and / or instructions to the memory 4102 or other devices. For example, the interface circuit 4104 can read data and / or instructions stored in the memory 4102 and send the data and / or instructions to the processor 4101.

[0509] The communication device 4100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 4100 described in this disclosure is not limited thereto, and the structure of the communication device 4100 may not be limited by FIG4A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0510] Figure 4B is a schematic diagram of the structure of chip 4200 according to an embodiment of this disclosure. For cases where the communication device 4100 can be a chip or a chip system, please refer to the schematic diagram of chip 4200 shown in Figure 4B, but it is not limited thereto.

[0511] Chip 4200 includes one or more processors 4201. Chip 4200 is used to perform any of the above methods.

[0512] In some embodiments, chip 4200 further includes one or more interface circuits 4202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 4200 further includes one or more memories 4203 for storing data and / or instructions. Optionally, all or part of the memories 4203 may be located outside of chip 4200. Optionally, the interface circuits 4202 are connected to the memories 4203, and the interface circuits 4202 can be used to receive data and / or instructions from the memories 4203 or other devices, and can be used to send data and / or instructions to the memories 4203 or other devices. For example, the interface circuits 4202 can read data and / or instructions stored in the memories 4203 and send the data and / or instructions to the processor 4201.

[0513] In some embodiments, the interface circuit 4202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201, S211, S221, S231, S241, S251, S261, but not limited thereto). The interface circuit 4202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 4202 performing data and / or instruction interaction between the processor 4201, the chip 4200, the memory 4203, or the transceiver device. In some embodiments, the processor 4201 performs at least one of other steps (e.g., steps 202, S212, S222, S232, S242, S252, S262, but not limited thereto).

[0514] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0515] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0516] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0517] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A mobility operation method, performed by a terminal, the method comprising: The method comprises: receiving configuration information, the configuration information being used to determine configuration required to trigger a first behavior, the first behavior comprising an early synchronization related to a height-based mobility operation.

2. The method of claim 1, wherein, The early synchronization comprises at least one of: a first early synchronization, comprising a downlink-related early synchronization; a second early synchronization, comprising an uplink-related early synchronization.

3. The method of claim 2, wherein, The first early synchronization comprises activation of a transmission configuration indication state (TCI state) of a candidate cell.

4. The method of claim 2, wherein, The second early synchronization comprises acquisition of a timing advance (TA) of a candidate cell.

5. The method according to any one of claims 1 to 4, characterized in that, The configuration information is used to indicate at least one of: a height range required to trigger the first behavior; a height-based execution condition to be evaluated to trigger the first behavior; configuration of a candidate cell associated with the first behavior.

6. The method of claim 5, wherein, The configuration of the candidate cell is used to indicate at least one of: a candidate cell; a beam of a candidate cell; a TCI state of a candidate cell.

7. The method of claim 5, wherein, The configuration of the candidate cell comprises at least one of: a configuration identifier of a candidate cell; an identifier of a candidate cell; an identifier of a candidate beam; a synchronization signal block (SSB) identifier corresponding to a candidate beam; a TCI state identifier of a candidate cell.

8. The method according to any one of claims 5-7, characterized in that, The method further comprises: acquiring a terminal height; based on the terminal height, determining a first candidate cell from candidate cells associated with the first behavior, wherein the first candidate cell comprises a candidate cell associated with a first height range and / or a first execution condition, the first height range being a height range in which the terminal height is located, and the first execution condition being an execution condition satisfied by the terminal height; performing the first behavior on the first candidate cell.

9. The method of claim 8, wherein, The performing of the first behavior on the first candidate cell comprises at least one of: activation of a TCI state of the first candidate cell; acquisition of a TA value of the first candidate cell; maintenance of a TA value of the first candidate cell.

10. The method of any one of claims 1-9, wherein, The configuration information is further used to determine configuration required to trigger a second behavior: The second behavior comprises at least one of: deactivation of a TCI state of a candidate cell; deletion of a TA value of a candidate cell.

11. The method of claim 10, wherein, The method further comprises: based on the terminal height, determining that the terminal leaves a second height range and / or that the terminal height no longer satisfies a second execution condition, performing the second behavior on a second candidate cell, wherein the second candidate cell comprises a candidate cell associated with the second height range and / or the second execution condition.

12. The method of any one of claims 5-11, wherein, The height range required to trigger the first behavior is determined by at least one of: a first threshold value, used to indicate a lower limit value of the height range; a second threshold value, used to indicate an upper limit value of the height range; a hysteresis value, used to evaluate whether the terminal is located in or leaves a reserved height of the height range.

13. The method of any one of claims 5-12, wherein, The configuration information is further used to indicate a third threshold value, the third threshold value being a threshold value of a measurement result required to evaluate to trigger the first behavior; a measurement result of the first candidate cell satisfies the third threshold value.

14. The method of any one of claims 5-13, wherein, The height-based execution condition comprises at least one of: the terminal height exceeding a first height threshold value; the terminal height is lower than a second height threshold; a signal quality of the serving cell is lower than a first quality threshold; a signal quality of the candidate cell is better than a signal quality of the serving cell by a first offset; a signal quality of the candidate cell exceeds a second quality threshold.

15. The method of any one of claims 5-14, wherein, the configuration information is further used to indicate a time window required to be satisfied to trigger the first behavior.

16. The method of any one of claims 1-15, wherein, the configuration information is further used to indicate that the terminal triggers at least one of the following mobility operations based on the height: sending height information of the terminal; performing measurement on a first candidate cell or a beam of the first candidate cell, the first candidate cell being a candidate cell performing the first behavior; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation. 17.A mobility operation method, performed by a network device, the method comprising: the method comprises: sending configuration information, the configuration information being used to determine, for a terminal, a configuration required to be satisfied to trigger a first behavior, the first behavior comprising an early synchronization related to a height-based mobility operation.

18. The method of claim 17, wherein, the early synchronization comprises at least one of the following: a first early synchronization, comprising a downlink-related early synchronization; a second early synchronization, comprising an uplink-related early synchronization.

19. The method of claim 18, wherein, the first early synchronization comprises activation of a transmission configuration indication state (TCI state) of a candidate cell.

20. The method of claim 18, wherein, the second early synchronization comprises acquisition of a timing advance of a candidate cell.

21. The method of any one of claims 17-20, wherein, the configuration information is used to indicate at least one of the following: a height range required to be satisfied to trigger the first behavior; a height-based execution condition required to be evaluated to trigger the first behavior; a configuration of a candidate cell associated with the first behavior.

22. The method of claim 21, wherein, the configuration of the candidate cell is used to indicate at least one of the following: a candidate cell; a beam of a candidate cell; a TCI state of a candidate cell.

23. The method of claim 21, wherein, the configuration of the candidate cell comprises at least one of the following: a configuration identifier of a candidate cell; an identifier of a candidate cell; an identifier of a candidate beam; a synchronization signal block (SSB) identifier corresponding to a candidate beam; a TCI state identifier of a candidate cell.

24. The method of any one of claims 17-23, wherein, the configuration information is further used to determine, for the terminal, a configuration required to be satisfied to trigger a second behavior: the second behavior comprises at least one of the following: deactivation of a TCI state of a candidate cell; deletion of a TA value of a candidate cell.

25. The method of any one of claims 21-24, wherein, the height range triggering the first behavior is determined by at least one of the following parameters: a first threshold value, used to indicate a lower limit value of the height range; a second threshold value, used to indicate an upper limit value of the height range; a hysteresis value, used to evaluate whether the terminal is located in or leaves a reserved height of the height range.

26. The method of any one of claims 21-23, wherein, the configuration information is further used to indicate, for the terminal, a third threshold value, the third threshold value being a threshold value of a measurement result required to be evaluated to trigger the first behavior; a measurement result of the first candidate cell satisfies the third threshold value.

27. The method of any one of claims 21-26, wherein, the height-based execution condition comprises at least one of the following: the terminal height exceeds a first height threshold; the terminal height is lower than a second height threshold; a signal quality of the serving cell is below a first quality threshold; a signal quality of the candidate cell is better than a signal quality of a serving cell by a first offset; a signal quality of the candidate cell exceeds a second quality threshold.

28. The method of any one of claims 21-27, wherein, The configuration information is further used to indicate a time window required to be satisfied for triggering the first behavior.

29. The method of any one of claims 17-28, wherein, The configuration information is further used to indicate the terminal to trigger at least one of the following mobility operations based on the height: sending height information of the terminal; performing measurement on a first candidate cell or a beam of the first candidate cell, the first candidate cell being a candidate cell for performing the first behavior; mobility measurement; sending a measurement report of the mobility measurement; conditional mobility operation.

30. A terminal, characterized by comprising: a transceiver module, configured to receive configuration information; a processing module, configured to determine, based on the configuration information, a configuration required to be satisfied for triggering a first behavior, the first behavior comprising early synchronization related to a height-based mobility operation.

31. A network device, comprising: comprising: a processing module, configured to determine configuration information, the configuration information being used to determine a configuration required to be satisfied for triggering a first behavior, the first behavior comprising early synchronization related to a height-based mobility operation; a transceiver module, configured to send the configuration information.

32. A communications device, characterized by The communication device is configured to perform the mobility operation method in any of claims 1-16, 17-29.

33. A communication system, characterized by comprising a terminal and a network device, wherein the terminal is configured to implement the mobility operation method in any of claims 1-16, and the network device is configured to implement the mobility operation method in any of claims 17-29.

34. A storage medium, the storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to perform the mobility operation method in any of claims 1-16, 17-29.

35. A program product comprising at least one of a program, instructions, characterized in that The program, at least one of the instructions, when executed on the communication device, implements the steps of the method in any of claims 1-16, 17-29.

Images