Mobility management method and device, storage medium and program product

Abstract

The invention provides a mobility management method and device, a storage medium and a program product, relates to the technical field of communication, and can enable a network side to sense the reason for performance reduction or switching failure of a terminal side. The method comprises the following steps: a first node executes a first operation under the condition that a first condition is met in a switching process without random access; the first operation comprises at least one of the following items: reporting mobility related information and triggering a random access process; wherein the first condition is a condition which causes performance reduction or switching failure of the first node; the mobility related information is used for indicating a reason for performance reduction or a reason for switching failure of the first node.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a mobility management method, device, storage medium, and program product. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) New Radio (NR) system introduces a design of random access channel less (RACH-less) handover, that is, the user terminal (UE) can skip the random access process and directly access the target cell during mobility. However, in this process, performance may be degraded due to improper network configuration or other reasons, or even radio link failure (RLF) or handover failure (HOF).

[0003] Currently, relevant technologies do not support the network side to identify the above scenarios. Summary of the invention

[0004] The embodiments of the present disclosure provide a mobility management method, an apparatus, a storage medium, and a program product, which enable the network side to perceive the reasons for the performance degradation or switching failure on the terminal side.

[0005] On the one hand, a mobility management method is provided, which is applied to a first node, including: when the first node satisfies a first condition during a switching process without random access, the first node performs a first operation; the first operation includes at least one of the following: reporting mobility-related information, triggering a random access process; wherein the first condition is a condition that causes performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

[0006] On the other hand, a mobility management method is provided, which is applied to a second node, including: receiving mobility-related information reported by a first node; the mobility-related information is reported by the first node when a first condition is satisfied during a switching process without random access, wherein the first condition is a condition causing performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

[0007] On the other hand, a mobility management device is provided, which is applied to a first node, including: a processing module, used to perform a first operation when a first condition is met during a switching process without random access; the first operation includes at least one of the following: reporting mobility-related information, triggering a random access process; wherein the first condition is a condition that causes performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

[0008] On the other hand, a mobility management device is provided, which is applied to a second node, including: a communication module, used to receive mobility-related information reported by a first node; the mobility-related information is reported by the first node when a first condition is satisfied during a switching process without random access, wherein the first condition is a condition causing performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

[0009] On the other hand, a communication device is provided, comprising: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; and the processor implements the mobility management method of any of the above embodiments when executing the computer program.

[0010] On the other hand, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the mobility management method of any of the above embodiments is implemented.

[0011] On the other hand, a computer program product is provided. The computer program product includes computer program instructions. When the computer program instructions are executed by a processor, the mobility management method of any of the above embodiments is implemented.

[0012] The disclosed embodiment provides a mobility management method, which can enable the first node to report mobility-related information and / or trigger a random access process when performance degradation or switching failure occurs in a switching process without random access. In this way, the second node can perceive the performance degradation or switching failure of the first node, and then analyze the reasons for the performance degradation or switching failure of the first node. At the same time, by triggering the random access process, the waiting time of the first node can be reduced and the latency can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the present disclosure, the drawings required for use in some embodiments of the present disclosure will be briefly introduced below. Obviously, the drawings described below are only drawings of some embodiments of the present disclosure, and a person skilled in the art can also obtain other drawings based on these drawings.

[0014] Figure 1 A schematic diagram of a communication system architecture provided in some embodiments of the present disclosure Figure 1 ;

[0015] Figure 2 A schematic diagram of a communication system architecture provided in some embodiments of the present disclosure Figure 2 ;

[0016] Figure 3 A flow chart of a mobility management method provided in some embodiments of the present disclosure;

[0017] Figure 4 A schematic diagram of a mobility management device provided in some embodiments of the present disclosure Figure 1 ;

[0018] Figure 5 A schematic diagram of a mobility management device provided in some embodiments of the present disclosure Figure 2 ;

[0019] Figure 6 A schematic diagram of the structure of a communication device provided in some embodiments of the present disclosure. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the present disclosure to clearly and completely describe the technical solutions in the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0021] It should be noted that, in the present disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present disclosure should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0022] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0023] In the description of the present disclosure, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more.

[0024] First, the technical terms involved in the embodiments of the present disclosure are introduced.

[0025] 1. RACH-less refers to a technology used to reduce switching delays and data transmission interruptions in mobile communication networks.

[0026] In the traditional handover process, the UE needs to synchronize and request resources with the target node through the RACH process before switching to a new node (e.g., base station, cell, satellite, etc.). However, the RACH process may introduce additional delays and data transmission interruptions. RACH-less technology avoids these problems in the following ways:

[0027] Pre-allocated resources: Before handover, the source node sends a handover request to the target node and instructs the target node to pre-allocate necessary uplink (UL) resources for the UE. These resources can be used by the UE immediately after the handover is completed without waiting for the RACH process.

[0028] Direct synchronization: The UE can use the information received from the source node (such as the timing advance (TA) amount, etc.) to synchronize with the target node, thereby avoiding the synchronization step in the RACH process.

[0029] Reduced signaling overhead: Since there is no need to perform the RACH process, the RACH-less technology significantly reduces the signaling overhead during the handover process and further shortens the handover time.

[0030] 2. Layer 1 / Layer 2 Triggered Mobility (L1 / L2 Triggered Mobility, LTM) is a mobility management mechanism introduced by 3GPP in Release 18. It aims to directly trigger cell switching through physical layer (L1) or link layer (L2) signaling without waiting for the reconfiguration of the Radio Resource Control (RRC) layer. In LTM, the Physical Downlink Control Channel (PDCCH) triggered RACH (PDCCH ordered RACH) mechanism is introduced, that is, before switching, the network triggers the terminal to obtain the TA of the target cell through PDCCH and complete the uplink synchronization in advance. In this way, after receiving the switching command (MAC CE corresponding to the LTM cell switch command), the terminal can quickly establish a connection with the target node, thereby reducing the switching delay and interruption time.

[0031] 3. The RACH based handover (HO) process (RACH based HO) refers to the process in mobility management in which, when a UE needs to switch from one node to another, it re-establishes uplink synchronization and connection with the target node through the RACH process.

[0032] 4. Mobile Integrated Access and Backhaul (mIAB) is a wireless communication technology in 5G networks that combines the functions of access network and backhaul network, enabling base stations to provide access services and backhaul transmission services for user equipment at the same time.

[0033] 5. Fallback: In signal processing and communication protocols, fallback means that under certain conditions, the system or device automatically adopts a simpler or more reliable communication method or protocol to ensure effective transmission of information. For example, during the RACH process, if the RACH-less method fails or the conditions are not met, the system may fall back to RACH based HO.

[0034] 6. Resynchronization. In a communication system, resynchronization generally refers to the process of reestablishing or restoring synchronization through a series of operations when the synchronization state between the UE and the network is lost or becomes unstable. In a quasi-Earth fixed scenario, satellite switch with re-synchronization in NTN is supported when hard and soft handovers are performed using the same Synchronization Signal Block (SSB) frequency and the same gNB. Satellite switch with resynchronization avoids L3 mobility of the UE within the cell by maintaining the same PCI within the geographical area covered by the quasi-Earth fixed beam. In this process, the UE synchronizes with the target satellite at a time point or within a time range configured by the network. There are two types of mechanisms, soft satellite switch over and hard satellite switch over: For soft satellite switch over, the UE can start synchronizing with the target satellite before the source satellite ends the service cell. When the UE switches to the target satellite, the UE does not need to be still connected to the source satellite. For hard satellite switch over, the UE can only start synchronizing with the target satellite after the switch to the target satellite is initiated.

[0035] The above is an introduction to the technical terms involved in the embodiments of the present disclosure, which will not be repeated below.

[0036] As mentioned in the background technology, the 3GPP NR system introduces the RACH-less design, that is, the UE can skip the random access process and directly access the target cell during mobility. Among them, RACH-less can be used in at least one of the following scenarios: LTM scenario, non-terrestrial network (NTN) scenario, mIAB scenario, etc.

[0037] Exemplarily, the RACH-less mobility process needs to help the UE obtain the following information:

[0038] 1. Whether the TA value exists or is available.

[0039] For example, if the network side does not configure TA, or the UE fails to obtain TA (for LTM, the UE should not enter the RACH-less process at the beginning, so there will be no fallback process), the information obtained by the UE may be that TA does not exist.

[0040] 2. The resources used by the UE after accessing the target cell, namely the Grant resources.

[0041] Exemplarily, Grants can be divided into two categories: configured grants (CG) or dynamic grants (DG).

[0042] Exemplarily, the network side configures CG resources for RACH-less, and the CG resources are configured to the UE or DG through RRC, but the CG resources can only be used if the preset conditions are met. For example, the preset conditions may include: whether the reference signal received power (RSRP) of the beam or SSB associated with the CG resources is greater than or equal to the preset threshold. If the CG resources do not meet the preset conditions, the CG resources are not available, and the UE may also fall back to the RACHbased HO process.

[0043] However, in this process, performance may be degraded or even RLF or HOF may occur due to improper network configuration or other reasons.

[0044] Currently, the mobility robustness optimization (MRO) in the self-organizing network (SON) or the minimization of drive tests (MDT) technology does not support the network side to identify the above scenarios.

[0045] Therefore, how to enable the network side to perceive the cause of performance degradation or failure is an urgent problem to be solved.

[0046] In response to the above technical problems, an embodiment of the present disclosure provides a mobility management method, the idea of ​​which is that: when a first node satisfies a first condition during a switching process without random access, the first node performs a first operation; the first operation includes at least one of the following: reporting mobility-related information, triggering a random access process; wherein the first condition is a condition that causes performance degradation or switching failure of the first node; the mobility-related information is used to indicate the reason for the performance degradation or switching failure of the first node.

[0047] It can be understood that the embodiments of the present disclosure can enable the first node to report mobility-related information and / or trigger a random access process when performance degradation or switching failure occurs during a switching process without random access. In this way, the second node can perceive the performance degradation or switching failure of the first node, and then analyze the reasons for the performance degradation or switching failure of the first node. At the same time, by triggering the random access process, the waiting time of the first node can be reduced and the latency can be reduced.

[0048] To facilitate understanding of the embodiments of the present disclosure, first Figure 1 The communication system shown in FIG. 1 is used as an example to describe in detail a communication system applicable to an embodiment of the present disclosure. For example, Figure 1 A schematic diagram of the architecture of a communication system to which the mobility management method provided in the embodiment of the present disclosure is applicable. Figure 1 As shown, the communication system includes terminal equipment and network equipment.

[0049] Among them, the terminal device is a terminal device that accesses the above-mentioned communication system and has a wireless transceiver function or a chip or chip system that can be set in the terminal device. The terminal device can also be called a user device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal in the embodiment of the present disclosure can be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a vehicle-mounted terminal, an RSU with terminal function, a physical network terminal, etc. The terminal device disclosed herein may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit that is built into the vehicle as one or more components or units. The vehicle may implement the mobility management method provided by the present disclosure through the built-in vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit.

[0050] The network device is a device located at the network side of the communication system and having a wireless transceiver function, or a chip or chip system that can be set in the device. The network device includes but is not limited to: Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless relay node, wireless backhaul node, transmission point (TRP or transmission point, TP), etc., and can also be 5G, such as gNB in ​​the new radio (NR) system, or transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in the 5G system, or network nodes constituting gNB or transmission point, such as baseband unit (BBU), or distributed unit (DU), road side unit (RSU) with base station function, etc.

[0051] Exemplarily, the above communication system may be applied to a new radio (NR) terrestrial network (TN), wherein the terminal device in the communication system may be a first node, and the network device may be a second node.

[0052] In some other embodiments, the communication system may further include: a flying platform. Figure 2 As shown, the communication system may include: network equipment, terminal equipment, and a flight platform.

[0053] Among them, the network device is an access network device set on the ground, and the terminal device and the access network device can communicate through the flight platform to forward signals. Specifically, the flight platform and the access network device can communicate through the next generation (NG) interface. Among them, the communication link between the flight platform and the access network device can be called a feeder link. The flight platform can provide a wireless access transmission / reception point (TRP) for the terminal device, and the TRP can perform data transparent transmission between the terminal device and the access network device, thereby realizing the communication connection between the terminal device and the access network device. At this time, it can be described as the flight platform working in transparent mode (transparent). It should be noted that the access network device can also be described as a gateway station, a ground station, etc., without limitation.

[0054] In some embodiments, the flying platform may be equipped with an access network device. When the access network device is mounted on the flying platform, the access network device moves synchronously with the flying platform, and the access network device and the flying platform can be regarded as a whole. At this time, the flying platform can be regarded as an access network device, or it can be described as the flying platform working in a regenerative mode, that is, the flying platform has the function of an access network device. In addition, the communication link between the flying platform and the terminal device can be called a service link.

[0055] It should be noted that the flight platform may be a satellite, an unmanned aerial vehicle, or other aircraft. Exemplarily, the flight platform may include a geostationary orbit satellite, a non-geostationary orbit satellite, a low-orbit satellite, a medium-orbit satellite, a geosynchronous orbit satellite, an unmanned aerial system platform, or a high-orbit satellite, etc., without limitation.

[0056] Alternatively, the access network equipment can be distributedly carried on the flight platform based on distributed units (DU). When the access network equipment is distributedly carried on the flight platform based on DU, the flight platform can be regarded as part of the access network equipment, or it can be described as the flight platform working in regeneration mode, that is, the flight platform has the functions of part of the access network equipment.

[0057] Exemplarily, the above communication system can be applied to the NTN of NR. In which, the terminal device in the communication system can be the first node, and the network device or the flight platform can be the second node.

[0058] It should be noted that the methods in the following embodiments can all be implemented in the above communication system. The solutions in the embodiments of the present disclosure can also be applied to other communication systems, and the corresponding names can also be replaced by the names of corresponding functions in other communication systems.

[0059] After introducing the application scenario and implementation environment of the embodiment of the present disclosure, the mobility management method provided by the embodiment of the present disclosure is described in detail below in combination with the above implementation environment.

[0060] like Figure 3 As shown, the present disclosure provides a mobility management method, which is applied to Figure 1 or Figure 2 The communication system shown in , the method comprises the following steps:

[0061] S201: When a first condition is satisfied during a handover process without random access, a first node performs a first operation.

[0062] The first condition is a condition that causes performance degradation or switching failure of the first node.

[0063] In some embodiments, the first operation includes at least one of the following: reporting mobility-related information, triggering a random access process.

[0064] The mobility-related information is used to indicate at least one of the following: a reason why the performance of the first node is degraded, a reason why the switching of the first node fails, and related context information.

[0065] The above-mentioned relevant context information is context information related to handover, or context information related to mobility.

[0066] In some embodiments, the mobility-related information is carried in at least one of the following reports: a radio link failure RLF report, a RACH report, and a successful handover report (Successful Handover Report, SHR).

[0067] In some embodiments, the above-mentioned switching process further includes: an NTN resynchronization process. For example, the description of the NTN resynchronization process is as follows and will not be repeated here.

[0068] In some embodiments, when the first operation includes reporting mobility-related information, the second node receives the mobility-related information reported by the first node.

[0069] In some embodiments, the first condition includes at least one of the following:

[0070] The first node is configured with CG resources but switches to the target cell based on DG resources;

[0071] The first node fails to switch or RLF occurs within a first preset time period after the switch is successful; that is, the first node quickly experiences RLF after the switch is successful;

[0072] The first timer in the first scenario times out, and the first timer is used to maintain uplink time synchronization;

[0073] The first node falls back from a handover process without random access to a handover process with random access;

[0074] During NTN resynchronization, the first node link fails;

[0075] During the NTN resynchronization process, the number of resynchronizations is greater than the resynchronization threshold.

[0076] During NTN resynchronization, the resynchronization time is greater than the resynchronization time threshold.

[0077] The first scenario includes at least one of the following: LTM, a switching process without random access (ie, RACH-less), and NTN resynchronization.

[0078] Exemplarily, the first timer may be a time alignment timer (TAT).

[0079] The following describes different situations in the first condition.

[0080] In some embodiments, when the first condition includes: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or, when a switching failure occurs in the first node or an RLF occurs within a first preset time period after a successful switching, the first operation includes: reporting mobility-related information.

[0081] The mobility-related information includes at least one of the following:

[0082] CG resources configured by the second node;

[0083] The cell and beam information corresponding to the CG resources;

[0084] Information of the target cell and target beam configured by the first node during the LTM process;

[0085] The type of resources used by the first node.

[0086] It is understandable that during the LTM process, the first node switches to the target cell based on the DG resources, which will result in the configured CG resources not being well utilized, and the use of DG resources may result in a higher access delay, resulting in performance degradation of the first node. In this regard, the embodiment of the present disclosure enhances the existing MRO mechanism so that the first node can report the above mobility-related information to the second node, so that the second node can perceive the performance degradation of the first node and analyze the reasons for the performance degradation of the first node.

[0087] In some embodiments, when the first condition includes: when a first timer in a first scenario times out, the first operation includes: reporting mobility-related information and / or triggering a random access process.

[0088] The mobility related information includes at least one of the following:

[0089] Indication information of timeout of the first timer;

[0090] Configuration of the first timer;

[0091] Configuration of the second timer; the second timer is used to control the time of the switching process;

[0092] Configuration of T304 timer;

[0093] The reason why the first node initiates the RACH procedure.

[0094] It is understandable that the timeout of the first timer in the first scenario will cause the service of the first node to be interrupted, and unnecessary waiting time will be incurred, the access delay will increase, and the performance of the first node will be degraded or the access will fail. In this regard, the embodiment of the present disclosure enhances the existing MRO mechanism so that the first node can report the above mobility-related information to the second node, so that the second node can perceive the performance degradation or access failure of the first node and analyze the reasons for the performance degradation or access failure of the first node.

[0095] In some embodiments, when the first condition includes: the first node falls back from a handover procedure without random access to a handover procedure with random access, the first operation includes: reporting mobility-related information.

[0096] The mobility related information includes at least one of the following:

[0097] An event in which the first node falls back from the RACH-less procedure to the RACH switching procedure;

[0098] The reason why the first node falls back from the RACH-less procedure to the RACH switching procedure;

[0099] List of CG resources configured by the first node;

[0100] Information of the beam corresponding to the CG resource configured by the first node;

[0101] The measurement value of the beam corresponding to the CG resource configured by the first node;

[0102] A beam quality threshold configured by the second node for a backoff event;

[0103] The first node measures the selected beam;

[0104] Configuration information of RACH-less process;

[0105] Application scenarios of RACH-less.

[0106] Exemplarily, the configuration information of the RACH-less process includes at least one of the following: timing advance, beam configuration information, and CG configuration information.

[0107] Exemplarily, the application scenarios of RACH-less include at least one of the following: NTN, mIAB.

[0108] It is understandable that, in the fallback process, the RACH based HO process introduces additional access delay, thereby increasing the service interruption time, resulting in performance degradation or access failure of the first node. In this regard, the embodiment of the present disclosure enhances the existing MRO mechanism so that the first node can report the above mobility related information to the second node, so that the second node can perceive the performance degradation or access failure of the first node and analyze the reasons for the performance degradation or access failure of the first node.

[0109] In some embodiments, when the first condition includes: a first node link fails during NTN resynchronization, the first operation includes: reporting mobility related information.

[0110] The mobility related information includes at least one of the following:

[0111] Satellite position and velocity vector information;

[0112] Satellite orbit information;

[0113] Reference time;

[0114] The time when the source satellite was taken out of service;

[0115] The time when the target satellite will start service;

[0116] The time configured by the third timer, the third timer is used to control the time of the resynchronization process;

[0117] The time configured by T430 timer;

[0118] Parameters for assisting the first node in resynchronization in a non-terrestrial network scenario;

[0119] The first node's measurements of the source beam and the target beam;

[0120] Service interruption time: The service interruption time is used to indicate the time of service interruption caused by resynchronization in the NTN scenario.

[0121] It is understandable that, during the NTN resynchronization process, if the resync time is too long, the first node may have a link failure, which in turn triggers the UE to re-access and RRC reconstruction, causing the first node to have performance degradation or access failure. In this regard, the embodiment of the present disclosure enhances the existing MRO mechanism so that the first node can report the above mobility-related information to the second node, so that the second node can perceive the performance degradation or access failure of the first node and analyze the reasons for the performance degradation or access failure of the first node.

[0122] In some embodiments, when the first condition includes: the number of resynchronizations during NTN resynchronization is greater than a resynchronization number threshold; and / or the resynchronization time during NTN resynchronization is greater than a resynchronization time threshold, the first operation includes: reporting mobility related information.

[0123] The mobility related information includes at least one of the following:

[0124] An event in which the number of resynchronizations is greater than the resynchronization threshold;

[0125] An event in which the resynchronization time is greater than the resynchronization time threshold;

[0126] The resynchronization number threshold configured by the second node;

[0127] The resynchronization time threshold configured by the second node;

[0128] The number of resynchronizations actually performed by the first node;

[0129] The actual resynchronization time of the first node.

[0130] It is understandable that during the NTN resynchronization process, the first node may generate a link failure due to a long resync time, which in turn triggers the UE to re-access and RRC reconstruction, causing the first node to experience performance degradation. This requires the first node to assist the network in identifying the problem. In this regard, the disclosed embodiment introduces an SHR enhancement method, in which the first node can report the above mobility-related information to the second node when the number of resynchronizations during the NTN resynchronization process is greater than the resynchronization number threshold; and / or when the resynchronization time during the NTN resynchronization process is greater than the resynchronization time threshold, the second node can perceive the performance degradation of the first node and analyze the reasons for the performance degradation of the first node.

[0131] For ease of understanding, the mobility management method provided by the embodiment of the present disclosure is described below using different scenarios as examples.

[0132] Scenario 1: In the scenario where RACH-less is used for LTM, the first node selects DG resources.

[0133] Exemplarily, the implementation process of RACH-less for LTM may include the following steps:

[0134] Sa1. After obtaining a valid TA value, the first node enters an ongoing RACH-less LTM process triggered by the L1 / L2 layer without a random access channel.

[0135] Exemplarily, the above-mentioned valid TA value may be configured by the network, or obtained by detection by the first node, which is not limited in the embodiments of the present disclosure.

[0136] Sa2. The first node determines whether the network has configured an associated CG for the beam indicated by the LTM cell switch command. If the beam has valid CG resources, the CG resources corresponding to the beam are selected as resources for accessing the target cell.

[0137] Sa3: When the first node fails to find valid CG resources, the first node schedules DG resources as resources for accessing the target cell.

[0138] According to the above process, the following situation may exist: the second node configures multiple beams (carried in the LTM candidate list) for the first node in the RRC (Radio Resource Control) signaling before the LTM cell switch command, where some beams are configured with CG resources and other beams are not configured with CG resources. The second node finally selects the beam without CG resources as the target beam, which will result in the configured CG resources not being well utilized, and the UE will also choose to schedule DG resources as the resources for accessing the target cell because there are no CG resources on the target beam, which may result in higher access delay.

[0139] For example, assuming that among beam 1, beam 2 and beam 3, CG resources are configured on beam 1 and beam 2, but the second node finally selects beam 3 as the target beam of the LTM cell switch. At this time, the configured CG resources are not well utilized, and the first node uses DG resources because there are no CG resources on beam 3, which may result in higher access delay.

[0140] It can be seen that in scenario 1, there are technical problems such as low CG resource utilization and increased access delay, which leads to LTM performance degradation in the first node.

[0141] In this regard, the embodiments of the present disclosure enhance the existing MRO mechanism so that the first node can report the reason for the performance degradation of the first node or related context information to the second node. In this way, the second node can perceive the performance degradation of the first node and analyze the reason for the performance degradation of the first node.

[0142] Exemplarily, in scenario one, the mobility management method provided by the embodiment of the present disclosure may include: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or, when a switching failure occurs in the first node or an RLF occurs within a first preset time period after a successful switching, the first node reports mobility-related information to the second node.

[0143] The mobility-related information may include at least one of the following:

[0144] CG resources configured by the second node;

[0145] The cell and beam information corresponding to the CG resources;

[0146] Information of the target cell and target beam configured by the first node during the LTM process;

[0147] The type of resources used by the first node.

[0148] Exemplarily, the resource type used by the first node may be a CG resource or a DG resource.

[0149] In some embodiments, the above mobility related information may be carried in the RLF report or SHR. For example, if the above process times out and causes HOF, the first node is prompted to update the RLF report.

[0150] Scenario 2: The first timer in the first scenario times out.

[0151] The first timer is used to maintain uplink time synchronization; illustratively, the first timer may be TAT.

[0152] Exemplarily, the first scenario includes at least one of the following: LTM, a switching process without random access, NTN resynchronization, and mIAB.

[0153] In some embodiments, in the first scenario, after receiving the cell switch command or starting the handover process without random access, the first node starts the timer TAT for the valid TA configured or provided by the second node. However, under certain network configurations, the timer TAT in the first scenario may time out. That is, the above mobility process has not been completed, and the TAT times out.

[0154] After TAT times out, the first node cannot send any uplink data and can only wait for the second timer (the second timer is used to control the time of the switching process, for example, the second timer can be timer T304) to time out before reestablishing through RACH or LTM recovery process. Therefore, the first node bears unnecessary waiting time and service interruption in this process, resulting in a high delay in the mobility process.

[0155] It can be seen that in scenario 2, the service of the first node is interrupted due to the timeout of the timer TAT, and unnecessary waiting time is incurred, the delay of the mobility process is increased, and the performance of the first node is degraded or the access fails.

[0156] In this regard, the embodiments of the present disclosure enhance the existing MRO mechanism so that the first node can report the reason for the performance degradation of the first node, the reason for the access failure, or related context information to the second node. In this way, the second node can perceive the performance degradation or access failure of the first node and analyze the reason for the performance degradation or access failure of the first node.

[0157] In some embodiments, in scenario 2, the mobility management method provided by the embodiment of the present disclosure may include: when the first timer in the first scenario times out, the first node reports mobility-related information to the second node.

[0158] The mobility-related information includes at least one of the following:

[0159] Indication information of timeout of the first timer;

[0160] Configuration of the first timer;

[0161] Configuration of the second timer; the second timer is used to control the time of the switching process;

[0162] Configuration of T304 timer;

[0163] The reason why the first node initiates the RACH process is that the first timer expires.

[0164] As a possible implementation, the above mobility related information may be carried in the RLF report. For example, if T304 times out, the first node will perform RRC reestablishment and generate a corresponding RLF report.

[0165] As another possible implementation, the above mobility related information may be carried in a RACH report. For example, if T304 times out, the first node performs RACH based cell access, thus having a RACH process, and therefore the first node may carry the above mobility related information in a RACH report.

[0166] In some embodiments, in scenario two, the mobility management method provided by the embodiment of the present disclosure may further include: when the first timer in the first scenario times out, the first node triggers a random access process.

[0167] It is understandable that the embodiment of the present disclosure may also introduce corresponding enhancement means, that is, when the timer TAT in the first scenario times out, the RACH process is directly triggered. For example, the first node exits from the LTM or the mobility process without random access, directly enters the RRC reestablishment process, and triggers the RACH process.

[0168] In some embodiments, in scenario two, the mobility management method provided by the embodiment of the present disclosure may further include: when the first timer in the first scenario times out, the first node reports mobility-related information and triggers a random access process.

[0169] It is understandable that when the timer TAT in the first scenario times out, in addition to simply allowing the network side to perceive the reason for the performance degradation or access failure of the first node, the embodiment of the present disclosure can also trigger the RACH process. In this way, the unnecessary waiting time of the first node can be reduced and the delay can be reduced.

[0170] Scenario 3: The first node falls back from the handover process without random access to the handover process with random access.

[0171] Exemplarily, the first node falls back from a handover process without random access (for example, in a non-LTM scenario, that is, an NTN and / or mAB scenario) to a handover process with random access, that is, a fallback process of the access mode, may include the following steps:

[0172] Sc1. After the mobility without random access is triggered, the first node checks whether there are CG resources that meet the conditions (that is, whether the beam quality associated with the CG resources is higher than the configured beam quality threshold). If so, it selects a suitable beam from the corresponding beams of these qualified CG resources and starts transmitting service data.

[0173] Sc2. If the first node is not configured with CG resources, the first node operates based on the DG resources that may be indicated by the second node, that is, the first node monitors PDCCH according to the beam information indicated by the second node.

[0174] For the handover process without random access in non-LTM scenarios, if the second node configures CG resources for the first node, the first node directly skips the DG behavior. The first node starts to check whether the CG is configured: if the first node is configured with CG resources, it will determine whether there are available CG resources when selecting CG resources. If there are no available and qualified CG resources (that is, whether the beam quality associated with the CG resource is higher than the configured beam quality threshold), the first node falls back to the RACH based HO process; if the second node configures DG for the first node (that is, the beam corresponding to DG), the first node starts to monitor PDCCH based on DG.

[0175] When the first node determines whether the CG resource is available, it can make a judgment based on the beam quality corresponding to the CG resource. For example, the first node determines whether the measured value of the beam corresponding to the CG resource (for example, the above beam can be an SSB beam, and the beam measurement value can be an SSB measurement value) is greater than or equal to the beam quality threshold (the beam quality threshold can be pre-configured on the network side). If the measured values ​​of the beams corresponding to the CG resources are all less than the beam quality threshold, the first node falls back to the RACHbased HO process. For example, the measured value of the beam can be an RSRP value, and the beam quality threshold can be an RSRP threshold.

[0176] It is understandable that, during the fallback process, the RACH based HO process introduces an additional access delay, thereby increasing the service interruption time, resulting in performance degradation or access failure of the first node.

[0177] In this regard, the embodiments of the present disclosure enhance the existing MRO mechanism so that the first node can report the reason for the performance degradation of the first node, the reason for the access failure, or related context information to the second node. In this way, the second node can perceive the performance degradation or access failure of the first node and analyze the reason for the performance degradation or access failure of the first node.

[0178] In some embodiments, in scenario three, the mobility management method provided by the embodiment of the present disclosure may include: when the first node falls back from a switching process without random access to a switching process with random access, the first node reports mobility-related information to the second node.

[0179] The mobility related information includes at least one of the following:

[0180] An event in which the first node falls back from the RACH-less procedure to the RACH switching procedure;

[0181] The reason why the first node falls back from the RACH-less procedure to the RACH switching procedure;

[0182] List of CG resources configured by the first node;

[0183] Information of the beam corresponding to the CG resources configured by the first node; for example, the SSB beam.

[0184] A measurement value of a beam corresponding to the CG resource configured by the first node; for example, an RSRP value;

[0185] A beam quality threshold configured by the second node for a backoff event; for example, an RSRP threshold;

[0186] The first node measures the selected beam;

[0187] Configuration information of RACH-less process;

[0188] Application scenarios of RACH-less.

[0189] Exemplarily, the configuration information of the RACH-less process includes at least one of the following: timing advance, beam configuration information, and CG configuration information.

[0190] Exemplarily, the application scenarios of RACH-less include at least one of the following: NTN, mIAB.

[0191] As a possible implementation, the information may be carried in the RLF report. For example, if the above RACH handover process fails, ie, HOF, the first node will perform RRC reconstruction and generate a corresponding RLF report.

[0192] As another possible implementation, the above mobility related information may be carried in a RACH report. Meanwhile, the above mobility related information may include the reason (RACH cause) for the first node to fall back from the RACH-less process to the RACH switching process.

[0193] As another possible implementation, the above mobility-related information may be carried in SHR. Exemplarily, the above event (i.e., the event in which the first node falls back from the RACH-less process to the RACH switching process) may also be a triggering event for SHR. Once the conditions are met (the first node is configured with CG resources, but the conditions are not met, causing the first node to fall back from the RACH-less process to the RACH based HO process), the first node generates an SHR report including the above mobility-related information and uploads it to the second node.

[0194] Scenario 4: The first node link fails during NTN resynchronization.

[0195] In the NTN scenario, there is a deployment method called Quasi-Earth-fixed, in which a geographical area is covered by one beam for a period of time, and after a certain point in time, it is covered by another beam. The first node needs to synchronize with the configured target beam at a given time point or time zone without involving RRC reconfiguration or even reconstruction process.

[0196] Exemplarily, the NTN resynchronization process may include the following steps:

[0197] Sd1, the first node receives the 19th system information block (System information block 19, SIB19) in the source satellite (called SAT-1).

[0198] Among them, SIB19 includes the information required for switching the RACH-less satellite to the target satellite. For example, SIB19 may include at least one of the following information: NTN configuration of the target satellite, SSB index, and SSB time offset.

[0199] Sd2. The first node determines the time point for performing resynchronization (i.e., T-switch, which determines the satellite switching time) at the RRC layer, and then notifies the Medium Access Control (MAC) layer; accordingly, after receiving the time point for performing resynchronization, the MAC layer clears the Hybrid Automatic Repeat reQuest (HARQ) buffer and stops uplink transmission to prepare for switching.

[0200] Exemplarily, RACH-less satellite switching includes hard switching or soft switching. Among them, hard switching means that during the switching process, the first node needs to disconnect from the source node first and then establish a connection with the target node. For soft satellite switching, the first node can start synchronizing with the target satellite before the source satellite ends the service cell. When the first node switches to the target satellite, it is not necessary for the first node to remain connected to the source satellite.

[0201] Exemplarily, the first node may determine whether to perform soft switching based on the capability and whether corresponding variables are configured.

[0202] For hard switching, the time point T-switch for executing resynchronization is T-service, which corresponds to the time when the source satellite stops service (resynchronizes to the target satellite and starts data transmission and reception); for soft switching, the first node obtains the downlink synchronization of the target satellite within the time period between [t-ServiceStart, t-Service], that is, [the time when the target satellite starts service, the time when the source satellite stops service].

[0203] In some embodiments, once it is determined to start switching, the third timer is considered to have expired until switching to the target satellite. The third timer is used to control the time of resynchronization. Exemplarily, the third timer may be timer T430.

[0204] In some embodiments, after the RRC layer determines the time point (ie, T-switch) for performing resynchronization, the first node notifies the MAC layer, and the MAC layer performs the specific switching.

[0205] Exemplarily, after receiving the satellite switching start indication from the upper layer, the MAC layer clears the HARQ buffer, suspends uplink transmission (the operation corresponding to the expiration of timer T430), and the first node performs subsequent downlink synchronization based on the provided SSB time offset (pending whether to reuse the SSB block measurement time configuration (SSB Measurement Timing Configuration, SMTC) or use a new information element).

[0206] Sd3: The first node starts to detect the downlink synchronization of the target satellite and makes SMTC adjustments (when SSB time offset is configured, SSB time offset must also be considered).

[0207] Exemplarily, the first node detects the SSB of the target satellite, that is, the first node detects the SSB of the target satellite within the adjusted SMTC window, and if the second node does not provide the SSB information of the target satellite in SIB19, the SSB of the source satellite is used.

[0208] Sd4. After acquiring the downlink synchronization of the target satellite, the first node starts timer T430 in t-Service, determines that the uplink synchronization is completed, determines the validity of the target side configuration, and resumes uplink transmission.

[0209] Exemplarily, the behavior of the first node at the MAC layer includes at least one of the following: clearing a local Network Timing Advance (NTA) value, clearing a Koffset dedicated to the first node, and allowing uplink transmission.

[0210] Exemplarily, after completing downlink synchronization with the target satellite, the first node obtains SIB19, which means that the uplink synchronization with the target satellite is completed. If the first node supports Timing Advance Reporting (TAR), TAR and TAR Scheduling Request (TAR-SR) on TAR are triggered.

[0211] Sd5. The first node starts uplink transmission and uses the TA report transmission as the first uplink transmission.

[0212] Exemplarily, at the MAC layer, if the timer TAT is running, the first node sends a TA through the uplink physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) or triggers a scheduling request (Scheduling Request, SR) on the physical uplink control channel (Physical Uplink Control Channel, PUCCH); if the timer TAT expires, the first node starts uplink transmission through RACH.

[0213] In the above scenario 4, ideally (that is, the parameters of the network configuration are completely accurate, and the first node is at the corresponding time point, such as t-ServiceStart, t-Service), the first node can successfully complete the resync of the target satellite. However, in actual deployment, there are errors in the orbit calculation of the satellite (because the satellite orbit may shift with operation), and the handover of the coverage interval may not be ideal, which may cause the first node to need to interrupt the service for too long, RLF, the first node needs to re-randomly access the network, RRC reconstruction, etc. during the resync process. This requires the first node to assist the network in identifying the problem.

[0214] It is understandable that the event or cause leading to the service interruption can be recorded. For example, based on the impact of the communication protocol (spec impacts), the first node can record the time interval from t-service to uplink recovery to help the network side perform evaluation.

[0215] It can be seen that in scenario 4, if the resync time is too long, it may cause a link failure in the first node, thereby triggering the UE to re-access and RRC reconstruction, causing performance degradation or access failure in the first node.

[0216] In this regard, the embodiments of the present disclosure enhance the existing MRO mechanism so that the first node can report the reason for the performance degradation of the first node, the reason for the access failure, or related context information to the second node. In this way, the second node can perceive the performance degradation or access failure of the first node and analyze the reason for the performance degradation or access failure of the first node.

[0217] In some embodiments, in scenario four, the mobility management method provided by the embodiment of the present disclosure may include: when a link of the first node fails during NTN resynchronization, the first node reports mobility-related information to the second node.

[0218] The mobility related information includes at least one of the following:

[0219] Satellite position and velocity vector information;

[0220] Satellite orbit information;

[0221] Reference time;

[0222] The time when the source satellite was taken out of service;

[0223] The time when the target satellite will start service;

[0224] The time configured by the third timer, the third timer is used to control the time of the resynchronization process;

[0225] The time configured by T430 timer;

[0226] Parameters for assisting the first node in resynchronization in a non-terrestrial network scenario;

[0227] The first node's measurements of the source beam and the target beam;

[0228] Service interruption time: The service interruption time is used to indicate the time of service interruption caused by resynchronization in the NTN scenario.

[0229] Exemplarily, the service interruption time may be an interval from the start of t-Service of the first node to the restoration of uplink of the first node.

[0230] In some embodiments, the above mobility related information can be carried in the RLF report or RACH report. For example, if the resync time in scenario 4 is too long, it may cause the first node to have a link failure, thereby triggering the first node to re-access and RRC reconstruction, and then the first node will generate a corresponding RLF report or RACH report, then the mobility related information can be carried in the RLF report or RACH report.

[0231] In the above embodiments (for scenarios 1 to 4), for a RACH-less mobility process, that is, a mobility process without random access, a corresponding RACH report will be generated even if there is no actual random access process.

[0232] Scenario 5: During the NTN resynchronization process, the number of resynchronization times is greater than the resynchronization time threshold; and / or, during the NTN resynchronization process, the resynchronization time is greater than the resynchronization time threshold.

[0233] During the NTN resynchronization process (for the NTN resynchronization process, please refer to the above scenario 4, which will not be repeated here), the first node may have a link failure due to a long resync time, which in turn triggers the UE to re-access and RRC reconstruction, causing the first node to have performance degradation. This requires the first node to assist the network in identifying the problem.

[0234] For example, the first node may report the reason for the performance degradation, access failure or related context information of the first node to the second node. In this way, the second node may perceive the performance degradation or access failure of the first node and analyze the reason for the performance degradation or access failure of the first node.

[0235] In this regard, an embodiment of the present disclosure introduces an SHR enhancement method, in which the second node can configure at least one of the following information to the first node: a resynchronization number threshold and a resynchronization time threshold.

[0236] Furthermore, when the number of resynchronizations of the first node during the NTN resynchronization process is greater than the resynchronization number threshold; and / or when the resynchronization time during the NTN resynchronization process is greater than the resynchronization time threshold, the first node reports mobility related information to the second node.

[0237] The mobility related information includes at least one of the following:

[0238] An event in which the number of resynchronizations is greater than the resynchronization threshold;

[0239] An event in which the resynchronization time is greater than the resynchronization time threshold;

[0240] The resynchronization number threshold configured by the second node;

[0241] The resynchronization time threshold configured by the second node;

[0242] The number of resynchronizations actually performed by the first node;

[0243] The actual resynchronization time of the first node;

[0244] Satellite position and velocity vector information;

[0245] Satellite orbit information;

[0246] Reference time;

[0247] The time when the source satellite was taken out of service;

[0248] The time when the target satellite will start service;

[0249] The time configured by the third timer, the third timer is used to control the time of the resynchronization process;

[0250] The time configured by T430 timer;

[0251] Parameters for assisting the first node in resynchronization in a non-terrestrial network scenario;

[0252] The first node's measurements of the source beam and the target beam;

[0253] Service interruption time: The service interruption time is used to indicate the time of service interruption caused by resynchronization in the NTN scenario.

[0254] Exemplarily, the above-mentioned NTN resynchronization process may be a process starting from the first node attempting to resynchronize to the target satellite until the resynchronization is successful.

[0255] The above mainly introduces the scheme of the embodiment of the present disclosure from the perspective of method. It can be understood that in order to realize the above functions, the mobility management device includes at least one of the hardware structure and software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed in this article, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiment of the present disclosure.

[0256] The disclosed embodiment can divide the mobility management device into functional modules according to the above method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the disclosed embodiment is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0257] Figure 4 is a schematic diagram of the structure of a mobility management device provided by an embodiment of the present disclosure. The mobility management device is applied to a first node and can execute the mobility management method provided by the above method embodiment. Figure 4 As shown, the mobility management device 600 includes: a processing module 601.

[0258] Processing module 601 is used for the first node to perform a first operation when a first condition is met during a switching process without random access; the first operation includes at least one of the following: reporting mobility-related information and triggering a random access process; wherein the first condition is a condition that causes performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: the reason for the performance degradation of the first node, the reason for the switching failure of the first node, and related context information.

[0259] In some embodiments, the first condition includes at least one of the following:

[0260] The first node is configured with CG resources but switches to the target cell based on DG resources;

[0261] A handover failure occurs at the first node or an RLF occurs within a first preset time period after a successful handover;

[0262] The first timer in the first scenario times out, and the first timer is used to maintain uplink time synchronization;

[0263] The first node falls back from a handover process without random access to a handover process with random access;

[0264] During NTN resynchronization, the first node link fails;

[0265] During the NTN resynchronization process, the number of resynchronizations is greater than the resynchronization threshold.

[0266] During NTN resynchronization, the resynchronization time is greater than the resynchronization time threshold.

[0267] In some embodiments, the first scenario includes at least one of the following: LTM, a handover procedure without random access, and NTN resynchronization.

[0268] In some embodiments, when the first condition includes: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or, when a switching failure occurs in the first node or an RLF occurs within a first preset time period after a successful switching, the first operation includes: reporting mobility-related information.

[0269] In some embodiments, the mobility-related information includes at least one of the following: CG resources configured by the second node; cell and beam information corresponding to the CG resources; information on the target cell and target beam configured by the first node during the LTM process; and the type of resources used by the first node.

[0270] In some embodiments, when the first condition includes: when a first timer in a first scenario times out, the first operation includes: reporting mobility-related information and / or triggering a random access process.

[0271] In some embodiments, the mobility-related information includes at least one of the following: indication information of the first timer expiration; configuration of the first timer; configuration of the second timer; the time of the second timer for controlling the switching process; configuration of the T304 timer; the reason why the first node initiates the RACH process is the expiration of the first timer.

[0272] In some embodiments, when the first condition includes: the first node falls back from a handover procedure without random access to a handover procedure with random access, the first operation includes: reporting mobility-related information.

[0273] In some embodiments, the mobility-related information includes at least one of the following: an event in which the first node falls back from the RACH-less process to the RACH switching process; the reason why the first node falls back from the RACH-less process to the RACH switching process; a list of CG resources configured by the first node; information on the beam corresponding to the CG resources configured by the first node; measured values ​​of the beam corresponding to the CG resources configured by the first node; a beam quality threshold configured by the second node for the fallback event; the measured value of the selected beam by the first node; configuration information of the RACH-less process; and application scenarios of RACH-less.

[0274] In some embodiments, the configuration information includes at least one of the following: timing advance, beam configuration information, and CG configuration information.

[0275] In some embodiments, the application scenario includes at least one of the following: NTN, mIAB.

[0276] In some embodiments, when the first condition includes: a first node link fails during NTN resynchronization, the first operation includes: reporting mobility related information.

[0277] In some embodiments, the mobility-related information includes at least one of the following: position and velocity vector information of the satellite; orbital information of the satellite; reference time; time when the source satellite stops service; time when the target satellite starts service; time configured by a third timer, the time when the third timer is used to control the time of the resynchronization process; time configured by the T430 timer; parameters used to assist the first node in resynchronizing in a non-terrestrial network scenario; measurement values ​​of the source beam and the target beam by the first node; service interruption time, the service interruption time is used to characterize the time of service interruption caused by resynchronization in the NTN scenario.

[0278] In some embodiments, when the first condition includes: the number of resynchronizations during NTN resynchronization is greater than a resynchronization number threshold; and / or the resynchronization time during NTN resynchronization is greater than a resynchronization time threshold, the first operation includes: reporting mobility related information.

[0279] In some embodiments, the mobility-related information includes at least one of the following: an event in which the number of resynchronizations is greater than a resynchronization number threshold; an event in which the time of resynchronization is greater than a resynchronization time threshold; the resynchronization number threshold configured by the second node; the resynchronization time threshold configured by the second node; the number of resynchronizations actually performed by the first node; and the resynchronization time actually performed by the first node.

[0280] In some embodiments, the mobility-related information is carried in at least one of the following reports: RLF report, RACH report, SHR.

[0281] Figure 5 is a schematic diagram of the structure of another mobility management device provided by an embodiment of the present disclosure. The mobility management device is applied to a second node and can execute the mobility management method provided by the above method embodiment. Figure 5 As shown, the mobility management device 700 includes: a communication module 701.

[0282] The communication module 701 is used to receive mobility-related information reported by the first node; the mobility-related information is reported by the first node when a first condition is met during a switching process without random access, wherein the first condition is a condition causing performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

[0283] In some embodiments, the first condition includes at least one of the following:

[0284] The first node is configured with CG resources but switches to the target cell based on DG resources;

[0285] A handover failure occurs at the first node or an RLF occurs within a first preset time period after a successful handover;

[0286] The first timer in the first scenario times out, and the first timer is used to maintain uplink time synchronization;

[0287] The first node falls back from a handover process without random access to a handover process with random access;

[0288] During NTN resynchronization, the first node link fails;

[0289] During the NTN resynchronization process, the number of resynchronizations is greater than the resynchronization threshold.

[0290] During NTN resynchronization, the resynchronization time is greater than the resynchronization time threshold.

[0291] In some embodiments, the first scenario includes at least one of the following: LTM, a handover procedure without random access, and NTN resynchronization.

[0292] In some embodiments, the first condition includes: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or, when the first node fails to switch or RLF occurs within a first preset time period after the switch is successful, the mobility-related information includes at least one of the following: CG resources configured by the second node; cell and beam information corresponding to the CG resources; information on the target cell and target beam configured by the first node during the LTM process; and the type of resources used by the first node.

[0293] In some embodiments, the first condition includes: when the first timer in the first scenario times out, the mobility-related information includes at least one of the following: indication information of the first timer timeout; configuration of the first timer; configuration of the second timer; time for the second timer to control the switching process; configuration of the T304 timer; the reason why the first node initiates the RACH process is the timeout of the first timer.

[0294] In some embodiments, when the first condition includes: the first node falls back from a switching process without random access to a switching process with random access, the mobility-related information includes at least one of the following: an event in which the first node falls back from a RACH-less process to a RACH switching process; a reason why the first node falls back from a RACH-less process to a RACH switching process; a list of CG resources configured by the first node; information on beams corresponding to the CG resources configured by the first node; measured values ​​of beams corresponding to the CG resources configured by the first node; a beam quality threshold configured by the second node for the fallback event; the measured value of the selected beam by the first node; configuration information of the RACH-less process; and application scenarios of RACH-less.

[0295] In some embodiments, the first condition includes: when the link of the first node fails during the NTN resynchronization process, the mobility-related information includes at least one of the following: satellite position and velocity vector information; satellite orbit information; reference time; time when the source satellite stops service; time when the target satellite starts service; time configured by a third timer, the time when the third timer is used to control the resynchronization process; time configured by the T430 timer; parameters used to assist the first node in resynchronization in a non-terrestrial network scenario; measurement values ​​of the first node on the source beam and the target beam; service interruption time, the service interruption time is used to characterize the time of service interruption caused by resynchronization in the NTN scenario.

[0296] In some embodiments, when the first condition includes: the number of resynchronizations during the NTN resynchronization process is greater than the resynchronization number threshold; and / or the resynchronization time during the NTN resynchronization process is greater than the resynchronization time threshold, the mobility-related information includes at least one of the following: an event in which the number of resynchronizations is greater than the resynchronization number threshold; an event in which the resynchronization time is greater than the resynchronization time threshold; the resynchronization number threshold configured by the second node; the resynchronization time threshold configured by the second node; the number of resynchronizations actually performed by the first node; and the resynchronization time actually performed by the first node.

[0297] In the case of implementing the functions of the above-mentioned integrated modules in the form of hardware, the embodiments of the present disclosure provide a possible structure of the communication device involved in the above-mentioned embodiments. Figure 6 As shown, the communication device 800 includes: a processor 802 and a bus 804. Optionally, the communication device may further include a memory 801; optionally, the communication device 800 may further include a communication interface 803.

[0298] The processor 802 may be a processor that implements or executes various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 802 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 802 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0299] The communication interface 803 is used to connect with other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0300] The memory 801 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0301] As a possible implementation, the memory 801 may exist independently of the processor 802, and the memory 801 may be connected to the processor 802 via a bus 804 to store instructions or program codes. When the processor 802 calls and executes the instructions or program codes stored in the memory 801, the mobility management method provided by the embodiment of the present disclosure can be implemented. In another possible implementation, the memory 801 may also be integrated with the processor 802.

[0302] The bus 804 may be an extended industry standard architecture (EISA) bus, etc. The bus 804 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0303] Some embodiments of the present disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium), in which computer program instructions are stored. When the computer program instructions are executed on a computer, the computer executes a mobility management method as in any of the above-mentioned embodiments.

[0304] Exemplarily, the above-mentioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or magnetic tapes, etc.), optical disks (e.g., compact disks (CD), digital versatile disks (DVD), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). The various computer-readable storage media described in the present disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0305] The embodiments of the present disclosure provide a computer program product including instructions. When the computer program product is executed on a computer, the computer is enabled to execute the mobility management method of any one of the above embodiments.

[0306] The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present disclosure should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A mobility management method, characterized in that: Applied to the first node, the method comprises: A first node performs a first operation when a first condition is satisfied during a switching process without random access; the first operation includes at least one of the following: reporting mobility-related information and triggering a random access process; wherein the first condition is a condition causing performance degradation or switching failure of the first node; the mobility-related information is used to indicate at least one of the following: a reason for the performance degradation of the first node, a reason for the switching failure of the first node, and related context information.

2. The method according to claim 1, characterized in that The first condition includes at least one of the following: The first node is configured with configuration authorized CG resources but switches to the target cell based on dynamic authorized DG resources; The first node fails to switch or a radio link interruption RLF occurs within a first preset time period after the switch is successful; A first timer in the first scenario times out, the first timer being used to maintain uplink time synchronization; The first node falls back from a handover process without random access to a handover process with random access; The first node link fails during NTN resynchronization; During the NTN resynchronization process, the number of resynchronizations is greater than the resynchronization threshold. During NTN resynchronization, the resynchronization time is greater than the resynchronization time threshold.

3. The method according to claim 2, characterized in that The first scenario includes at least one of the following: LTM, handover process without random access, and resynchronization in non-terrestrial networks (NTN).

4. The method according to claim 2, characterized in that: When the first condition includes: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or the first node fails to switch or RLF occurs within a first preset time period after successful switching, the first operation includes: reporting mobility-related information.

5. The method according to claim 4, characterized in that The mobility related information includes at least one of the following: CG resources configured by the second node; The cell and beam information corresponding to the CG resource; Information of a target cell and a target beam configured by the first node during the LTM process; The type of resources used by the first node.

6. The method according to claim 1, characterized in that When the first condition includes: when a first timer in a first scenario times out, the first operation includes: reporting mobility-related information and / or triggering a random access process.

7. The method according to claim 6, characterized in that The mobility related information includes at least one of the following: Indication information of timeout of the first timer; Configuration of the first timer; Configuration of a second timer; the second timer is used to control the time of the switching process; Configuration of T304 timer; The reason why the first node initiates the RACH process is that the first timer times out.

8. The method according to claim 1, characterized in that In a case where the first condition includes: the first node falls back from a handover procedure without random access to a handover procedure with random access, the first operation includes: reporting mobility-related information.

9. The method according to claim 8, characterized in that The mobility related information includes at least one of the following: An event in which the first node falls back from a RACH-less process to a RACH switching process; A reason why the first node falls back from the RACH-less process to the RACH switching process; A list of CG resources configured by the first node; Information of the beam corresponding to the CG resources configured by the first node; a measurement value of a beam corresponding to the CG resource configured by the first node; A beam quality threshold configured by the second node for a backoff event; A measurement value of the selected beam by the first node; Configuration information of RACH-less process; Application scenarios of RACH-less.

10. The method according to claim 9, characterized in that The configuration information includes at least one of the following: timing advance, beam configuration information, and CG configuration information.

11. The method according to claim 9, characterized in that The application scenario includes at least one of the following: NTN, mobile integrated access and backhaul mIAB.

12. The method according to claim 1, characterized in that When the first condition includes: the first node link fails during NTN resynchronization, the first operation includes: reporting mobility related information.

13. The method according to claim 12, characterized in that The mobility related information includes at least one of the following: Satellite position and velocity vector information; Satellite orbit information; Reference time; The time when the source satellite was taken out of service; The time when the target satellite will start service; A time configured by a third timer, wherein the third timer is used to control the time of the resynchronization process; The time configured by T430 timer; Parameters for assisting the first node in resynchronizing in a non-terrestrial network scenario; The measurement values ​​of the first node on the source beam and the target beam; The service interruption time is used to indicate the time of service interruption caused by resynchronization in the NTN scenario.

14. The method according to claim 1, characterized in that When the first condition includes: the number of resynchronizations during NTN resynchronization is greater than a resynchronization number threshold; and / or the resynchronization time during NTN resynchronization is greater than a resynchronization time threshold, the first operation includes: reporting mobility related information.

15. The method according to claim 14, characterized in that The mobility related information includes at least one of the following: An event in which the number of resynchronizations is greater than the resynchronization threshold; An event in which the resynchronization time is greater than the resynchronization time threshold; The resynchronization number threshold configured by the second node; The resynchronization time threshold configured by the second node; The number of resynchronizations actually performed by the first node; The actual resynchronization time of the first node.

16. The method according to claim 1, characterized in that The mobility related information is carried in at least one of the following reports: Radio link failure RLF report, RACH report, successful handover report SHR.

17. A mobility management method, characterized in that: Applied to the second node, the method comprises: Receive mobility-related information reported by a first node; the mobility-related information is reported by the first node when a first condition is satisfied during a switching process without random access, wherein the first condition is a condition causing performance degradation or switching failure of the first node; the mobility-related information is used to indicate a reason for the performance degradation or switching failure of the first node.

18. The method according to claim 17, characterized in that The first condition includes at least one of the following: The first node is configured with configuration authorized CG resources but switches to the target cell based on dynamic authorized DG resources; A handover failure occurs to the first node, or a radio link interruption RLF occurs within a first preset time period after a successful handover; A first timer in the first scenario times out, the first timer being used to maintain uplink time synchronization; The first node falls back from a handover process without random access to a handover process with random access; The first node link fails during NTN resynchronization; During the NTN resynchronization process, the number of resynchronizations is greater than the resynchronization threshold. During NTN resynchronization, the resynchronization time is greater than the resynchronization time threshold.

19. The method according to claim 18, characterized in that The first scenario includes at least one of the following: LTM, handover process without random access, and resynchronization in non-terrestrial networks (NTN).

20. The method according to claim 18, characterized in that When the first condition includes: the first node is configured with CG resources but switches to the target cell based on DG resources; and / or, the first node fails to switch or RLF occurs within a first preset time period after the switch is successful, the mobility-related information includes at least one of the following: CG resources configured by the second node; The cell and beam information corresponding to the CG resource; Information of a target cell and a target beam configured by the first node during the LTM process; The type of resources used by the first node.

21. The method according to claim 18, characterized in that When the first condition includes: when a first timer in the first scenario times out, the mobility related information includes at least one of the following: Indication information of timeout of the first timer; Configuration of the first timer; Configuration of a second timer; the second timer is used to control the time of the switching process; Configuration of T304 timer; The reason why the first node initiates the RACH process is that the first timer times out.

22. The method according to claim 18, characterized in that In a case where the first condition includes: the first node falls back from a handover procedure without random access to a handover procedure with random access, the mobility-related information includes at least one of the following: An event in which the first node falls back from a RACH-less process to a RACH switching process; A reason why the first node falls back from the RACH-less process to the RACH switching process; A list of CG resources configured by the first node; Information of the beam corresponding to the CG resources configured by the first node; a measurement value of a beam corresponding to the CG resource configured by the first node; a beam quality threshold configured by the second node for a backoff event; A measurement value of the selected beam by the first node; Configuration information of RACH-less process; Application scenarios of RACH-less.

23. The method according to claim 18, characterized in that When the first condition includes: the first node link fails during NTN resynchronization, the mobility related information includes at least one of the following: Satellite position and velocity vector information; Satellite orbit information; Reference time; The time when the source satellite was taken out of service; The time when the target satellite will start service; A time configured by a third timer, wherein the third timer is used to control the time of the resynchronization process; The time configured by T430 timer; Parameters for assisting the first node in resynchronizing in a non-terrestrial network scenario; The measurement values ​​of the first node on the source beam and the target beam; The service interruption time is used to indicate the time of service interruption caused by resynchronization in the NTN scenario.

24. The method according to claim 18, characterized in that In the case where the first condition includes: the number of resynchronizations during the NTN resynchronization process is greater than the resynchronization number threshold; and / or the resynchronization time during the NTN resynchronization process is greater than the resynchronization time threshold, the mobility related information includes at least one of the following: An event in which the number of resynchronizations is greater than the resynchronization threshold; An event in which the resynchronization time is greater than the resynchronization time threshold; The resynchronization number threshold configured by the second node; The resynchronization time threshold configured by the second node; The number of resynchronizations actually performed by the first node; The actual resynchronization time of the first node.

25. A communication device, characterized in that: include: Memory and processor; Memory and processor coupling; The memory is used to store instructions executable by the processor; When the processor executes the instructions, the method according to any one of claims 1 to 24 is performed.

26. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 24.

27. A computer program product, characterized in that The computer program product comprises computer instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 24.

Images