Mobility management method and apparatus

Abstract

Embodiments of the present application provide a mobility management method and apparatus. The method comprises: a terminal device receives configuration information sent by a first network device and used for configuring a layer 1 / layer 2 triggered mobility (LTM) candidate cell; the terminal device determines that an LTM connection failure occurs; and the terminal device records connection failure information, the connection failure information comprising at least one of the following: information for indicating a duration from the last time the terminal device receives the configuration information to the occurrence of the connection failure; and information for determining that the mobility type related to the connection failure is LTM. According to the embodiments of the present application, an SON enhancement scheme under LTM scenarios is introduced, so that a terminal device can report LTM-related connection failure information, and thus a network device can perform corresponding parameter adjustment according to the connection failure information, thereby improving LTM robustness.

Description

Mobility management method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Mobility scenarios in wireless communication systems include layer-triggered mobility (L1 / L2 triggered mobility, also known as layer 1 / layer 2 triggered mobility) scenarios. In LTM, the network device sends LTM candidate cell configuration information to the terminal device, and the terminal device performs downlink and / or uplink synchronization procedures with the LTM candidate cell. The terminal device performs Layer 1 (L1) measurements and sends the L1 measurement results corresponding to the LTM candidate cell to the network device. Based on the L1 measurement results, the network device determines the LTM target cell for the terminal device to change to and sends this information to the terminal device via Layer 2 signaling. In response, the terminal device executes the LTM cell change procedure to the LTM target cell.

[0003] Figure 1 is a possible schematic diagram of the LTM process. As shown in Figure 1, the process may include the following steps:

[0004] Step 1: The user equipment (UE) sends a measurement report to the gNB.

[0005] Step 2: The UE receives configuration information of one or more LTM candidate cells sent by the base station;

[0006] Step 3: The UE stores the received configuration information of the LTM candidate cell and sends a response message to the base station;

[0007] Step 4a: The UE performs downlink synchronization with the LTM candidate cell;

[0008] Step 4b (optional): The UE performs uplink synchronization with the corresponding LTM candidate cell according to the configuration information of the base station;

[0009] Step 5: The UE performs L1 measurement and sends the L1 measurement result to the base station;

[0010] Step 6: The UE receives a MAC CE (Media Access Control) control element) sent by the base station to indicate a cell change command. The MAC CE includes indication information of the LTM target cell.

[0011] In step 6, optionally, the MAC CE may include TA (Timing Advance) information of the LTM target cell;

[0012] Step 7 (optional): If the UE does not have a valid TA corresponding to the LTM target cell, the UE performs a random access procedure with the LTM target cell when performing the LTM cell change procedure with the LTM target cell;

[0013] Step 8: The UE completes the LTM cell change procedure with the LTM target cell.

[0014] In the above process, if step 7 is performed, when the UE successfully completes the random access process with the LTM target cell, it can be considered that the UE has successfully completed the LTM cell change process.

[0015] In the above process, if step 7 is not performed, the UE can be considered to have successfully completed the LTM cell change process when it determines that the network equipment to which the LTM target cell belongs has successfully received the first uplink data sent by the UE. For example, when the UE receives a Physical Downlink Control Channel (PDCCH) addressed with the UE's Cell Radio-Network Temporary Identifier (C-RNTI) in the LTM target cell, which is used to schedule new data transmission, the UE believes that the network equipment has successfully received the first uplink data sent by the UE.

[0016] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0017] Summary of the Invention

[0018] The inventors discovered that if a connection failure occurs during the LTM process, it is necessary to consider optimizing LTM-related configurations for subsequent mobility management. Connection failures include radio link failure (RLF), handover failure (HOF), timer expiration, or other reasons that lead to a connection failure between the terminal device and the current serving cell.

[0019] Currently, self-organizing networks (SON) have introduced network optimization mechanisms, including mobility robustness optimization (MRO). The existing MRO mechanism records mobility parameters on terminal devices, generates corresponding mobility reports, and reports them to network devices, allowing them to better adjust mobility-related parameters.

[0020] The mobility report may include at least one of the following reports: a failure report, a success mobility report, a random access report (RA report), a connection establishment failure report (CEF report) or other reports. Among them, the failure report includes a radio link failure report (RLF report) or any one or more of other failure reports, and the successful mobility report includes various successful mobility reports, such as a successful handover report, a successful secondary cell addition or change report, or any one or more of other success reports.

[0021] However, in the existing SON mechanism, there is no LTM-related optimization operation. Therefore, it is necessary to consider recording LTM mobility-related failure information to assist network devices in optimizing corresponding configuration parameters.

[0022] To address at least one of the above problems or other similar problems, embodiments of the present application provide a method and apparatus for mobility management.

[0023] According to one aspect of an embodiment of the present application, a method for mobility management is provided, wherein the method includes:

[0024] The terminal device receives configuration information for configuring a layer 1 / layer 2 triggered mobility (LTM) candidate cell sent by the first network device;

[0025] The terminal device determines that an LTM connection failure occurs;

[0026] The terminal device records connection failure information, where the connection failure information includes at least one of the following:

[0027] Information indicating the length of time between the last time the terminal device received the configuration information and the occurrence of the connection failure;

[0028] Information used to determine that the mobility type related to the connection failure is LTM.

[0029] According to another aspect of an embodiment of the present application, there is provided a mobility management apparatus configured in a terminal device, wherein the apparatus includes:

[0030] a receiving unit configured to receive configuration information for configuring a layer 1 / layer 2 triggered mobility (LTM) candidate cell sent by a first network device;

[0031] a determining unit that determines that an LTM connection failure occurs; and

[0032] A processing unit is configured to record connection failure information, wherein the connection failure information includes at least one of the following:

[0033] Information indicating the length of time between the last time the terminal device received the configuration information and the occurrence of the connection failure;

[0034] Information used to determine that the mobility type related to the connection failure is LTM.

[0035] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, a SON enhancement solution in the LTM scenario is introduced, so that the UE can report LTM-related failure information, so that the network device can make corresponding parameter adjustments based on the LTM-related failure information, thereby improving LTM robustness.

[0036] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0037] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0038] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0040] FIG1 is a schematic diagram of the LTM process;

[0041] FIG2 is a schematic diagram of the forwarding process of the RLF report between the terminal device and the network device;

[0042] FIG3 is a schematic diagram of a method for mobility management according to an embodiment of the first aspect of the present application;

[0043] FIG4 is a schematic diagram of a time point at which a connection failure occurs between a terminal device and a serving cell;

[0044] FIG5 is a schematic diagram of a time point at which a connection failure occurs between a terminal device and an LTM target cell;

[0045] FIG6 is a schematic diagram of the information interaction process between the terminal device and the network device in the scenario shown in FIG4 ;

[0046] FIG7 is a schematic diagram of the information interaction process between the terminal device and the network device in the scenario shown in FIG5 ;

[0047] FIG8 is a schematic diagram of a method for mobility management according to an embodiment of the second aspect of the present application;

[0048] FIG9 is a schematic diagram of a mobility management apparatus according to an embodiment of the present application;

[0049] FIG10 is another schematic diagram of the apparatus for mobility management according to an embodiment of the present application;

[0050] FIG11 is a schematic diagram of a communication system according to an embodiment of the present application;

[0051] FIG12 is a schematic diagram of a network device according to an embodiment of the present application;

[0052] FIG13 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0053] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0054] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0055] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0056] In the embodiments of the present application, a scenario involving network devices and / or terminal devices is taken as an example.

[0057] In the above scenario, the network device may include at least one of a core network device, a third-party application device, an operation administration and maintenance (OAM), and an access network device.

[0058] The core network device may refer to a device in the core network (CN) that provides service support for the terminal device. As some examples, the core network device may be at least one of the following: a mobility and management entity (MME), an access and mobility management function (AMF) entity, a session management function (SMF) entity, a user plane function (UPF) entity, a location management function (LMF) entity, and the like, which are not listed here one by one. Among them, the AMF entity may be responsible for the access management and mobility management of the terminal, the SMF entity may be responsible for session management, such as the establishment of a user session, and the UPF entity may be a functional entity of the user plane, mainly responsible for connecting to the external network. The LMF entity may manage the overall coordination and scheduling of resources required for the location of the terminal device registered with the core network device or accessing the core network device. It should be noted that in the embodiments of the present application, the entity may also be referred to as a network element or a functional entity, such as the AMF entity may also be referred to as an AMF network element or an AMF functional entity, and so on.

[0059] The third-party application device can be an OTT service (over the top server) or other third-party device.

[0060] OAM is a network device that performs operations, management, and maintenance on the network according to the actual needs of the operator's network operations.

[0061] The access network device is an access device that the terminal device uses to access the communication system wirelessly. The access network device can be a base station (BS), an evolved NodeB (eNodeB), a transmission reception point (TRP), a base station (next generation NodeB, gNB) in the fifth generation (5G) mobile communication system, a base station in the sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The access network device can also be a module or unit that completes part of the functions of the base station. For example, it can be at least one of the following modules or units: a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU control plane, CU-CP), a centralized unit user plane (CU user plane, CU-CP), an integrated access backhaul (IAB) or other modules or units. The embodiments of the present application do not limit the specific technology and / or specific device form adopted by the access network device. The access network equipment can be deployed on land, including indoors / outdoors, and can be handheld or vehicle-mounted; it can also be deployed on the water, on an airplane, on a balloon or on a satellite; the access network equipment can be deployed in a fixed location or on a mobile carrier, and the embodiments of the present application do not limit this.

[0062] In the above scenarios, a terminal device can be a device with wireless transceiver capabilities that can send signals to and / or receive signals from an access network device. A terminal device can also be referred to as a terminal, mobile station, or mobile terminal. A terminal device can be a mobile phone, tablet, or other device with wireless intelligent transceiver capabilities. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, and various smart scenarios.

[0063] In the above scenarios, access network devices and terminal devices, and terminal devices and terminal devices can communicate via licensed spectrum, unlicensed spectrum, or both. The embodiments of this application do not limit the spectrum resources used for wireless communications.

[0064] The following description is made by taking an example where a terminal device fails to connect to the current serving cell and the mobility report is an RLF report.

[0065] In this example, the terminal device may record relevant information in the RLF report, generate, and send the RLF report. FIG2 is a schematic diagram of a forwarding process of the RLF report between the terminal device and the network device. As shown in FIG2 , the forwarding process may include:

[0066] 210: The terminal device detects that a connection failure occurs in the current serving cell, and the terminal device generates an RLF report. Exemplarily, the RLF report may include at least one of the following information:

[0067] · Failed cell information: The failed cell is a cell where the terminal device detects a connection failure. The failed cell information may include at least one of the following information: a cell global identifier (CGI), a physical cell identifier (PCI) and frequency information, a cell identifier (cell ID), a non-public network identifier (NPN ID), a non-terrestrial network identifier (NTN ID) or other cell identifiers. Among them, the CGI may include a public land mobile network (PLMN ID) and a cell ID. Optionally, the failed cell information may also include a tracking area code (TAC) and / or identification information of the network device to which the failed cell belongs, such as a global network device identifier. In the mobility process, the failed cell may also be referred to as a target cell.

[0068] Previous serving cell information: The previous serving cell is the primary cell (former primary cell) from which the terminal device last received a mobility command. In the mobility process, the previous serving cell may also be referred to as a source cell.

[0069] Failure type information: such as RLF and HOF.

[0070] Re-established cell information: The re-established cell can be the cell where the terminal device attempts to initiate the re-establishment process after detecting a connection failure.

[0071] Time after failure: This time after failure information can be used to indicate the length of time after the terminal device detects the connection failure. Generally, it refers to the length of time from the terminal device detecting the connection failure to reporting the RLF report.

[0072] Connection failure time information: The connection failure time information may be used to indicate the length of time from the last (or most recent) receipt of a handover command (or reconfiguration message) by the terminal device to the detection of a connection failure by the terminal device.

[0073] Failure reason information: The failure reason information is used to indicate at least one of the following failure reasons: expired timer type information (e.g., T312 timer expiration), listen before talk (LBT) failure, integrity check failure, handover to another system, resynchronization failure, RRC connection reconfiguration failure, or other possible failure reasons;

[0074] Conditional handover (CHO) configuration trigger information: The CHO configuration trigger information is used to indicate the time length between the CHO configuration executed by the terminal device and the receipt of the CHO configuration.

[0075] CHO cell information: This CHO cell information is used to indicate the cell where the terminal device has successfully completed CHO configuration;

[0076] Handover type information: CHO or dual active protocol stack (DAPS) handover DAPS HO;

[0077] 220: The terminal device sends RLF report presence indication information to the connected network device (receiving node). The connected network device may be referred to as the receiving network device.

[0078] 230: The terminal device receives the RLF report request sent by the network device;

[0079] 240: The terminal device sends an RLF report to the receiving network device.

[0080] The following describes embodiments of the present application with reference to the accompanying drawings and detailed descriptions. For ease of description, the following description uses a base station as an example of an access network device. In the following description, "if," "under the circumstances," and "when" can be used interchangeably to avoid confusion.

[0081] It is understood that in the embodiments of the present application, the terminal device and / or the network device may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the various steps may be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all of the operations in the embodiments of the present application may be performed.

[0082] Embodiments of the first aspect

[0083] An embodiment of the present application provides a method for mobility management, which is described from the perspective of a terminal device.

[0084] FIG3 is a schematic diagram of a method for mobility management according to an embodiment of the present application. As shown in FIG3 , the method includes:

[0085] 310: The terminal device receives configuration information for configuring an LTM candidate cell sent by the first network device;

[0086] 320: The terminal device determines that an LTM connection failure has occurred;

[0087] 330: The terminal device records the connection failure information, where the connection failure information includes at least one of the following: information indicating the length of time from the last time the terminal device received the configuration information to the occurrence of the connection failure; information determining that the mobility type associated with the connection failure is LTM.

[0088] It is worth noting that FIG3 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG3 above.

[0089] According to the embodiment of the present application, a SON enhancement solution in the LTM scenario is introduced, so that the UE can report LTM-related failure information, so that the network equipment can make corresponding parameter adjustments based on the LTM-related failure information, thereby improving the robustness of LTM.

[0090] In operation 310, the configuration information of the LTM candidate cell may include cell information of the LTM candidate cell. Thus, the first network device may configure the LTM candidate cell for the terminal device through the configuration information of the LTM candidate cell.

[0091] In operation 320, the terminal device may determine that a connection failure has occurred between the terminal device and the serving cell. The connection failure may occur in at least one of the following scenarios:

[0092] In scenario a, the connection failure (e.g., RLF) may occur at any time point before the terminal device receives the above-mentioned LTM candidate cell configuration information and receives the LTM cell change message (e.g., the LTM cell change message sent by the layer 2 MAC CE), as shown in FIG4 ;

[0093] In scenario b, the connection failure (e.g., HOF, or LTM failure (LTM failure, LTM), or LTM cell change failure) may also occur during the cell change process between the terminal device and the LTM target cell. For example, the terminal device receives an LTM cell change message, and the terminal device performs a cell change between the terminal device and the LTM target cell. The connection failure may occur before the random access (RA) process is successful, or before the terminal device successfully sends the first uplink data of the terminal device, as shown in Figure 5; as a possible example, the first uplink data may be an L3 handover completion message, such as an RRC reconfiguration complete message;

[0094] In scenario c, the connection failure (e.g., RLF) may also occur after the terminal device and the LTM target cell successfully complete the LTM cell change. For example, the terminal device successfully sends the first uplink data, or the terminal device determines that the network device successfully receives the first uplink data sent by the terminal device, for example, the terminal device receives data transmission scheduling information sent to the terminal device by the LTM target cell, as shown in Figure 5.

[0095] In operation 330 , after determining that an LTM connection failure occurs, the terminal device may record connection failure information, and the terminal device may generate a mobility report based on the connection failure information.

[0096] In an embodiment of the present application, as shown in FIG3 , the method may further include:

[0097] 340: The terminal device sends a mobility report to the second network device, where the mobility report includes connection failure information.

[0098] In the above embodiment, the second network device may be a network device to which the terminal device accesses after the above-mentioned LTM connection fails, such as the receiving node shown in Figure 2. After the terminal device accesses the cell under the receiving node, the receiving node sends a mobility report (such as an RLF report) request to the terminal device, and the terminal device sends a mobility report to the receiving node.

[0099] In the above embodiment, the terminal device sends a mobility report to the connected network device (called the second network device), so that the corresponding network device (called the third network device) can make corresponding parameter adjustments based on the connection failure information to improve the robustness of LTM.

[0100] It can be understood that the mobility report may include all or part of the connection failure information. The third network device may be at least one of the following network devices in the LTM process corresponding to the mobility report: a source network device, a target network device, and a network device to which the LTM candidate cell belongs. The source network device is the network device to which the previous service cell belonged (for example, the network device that sends the configuration information of the LTM candidate cell to the terminal device in scenario a, that is, the network device to which the service cell (also referred to as the failed cell) belongs when the connection failure occurs) or the network device to which the failed cell belongs (for example, the network device that sends the LTM cell change message to the terminal device in scenario b), and the target network device is the network device to which the LTM target cell belongs.

[0101] As an example, when the connection failure in the mobility report occurs in scenario a or b above, the third network device is the source network device; when the connection failure in the mobility report occurs in scenario c above, the third network device is the target network device, or both the target network device and the source network device. It will be understood that in scenario b or c above, the first network device is the source network device. In scenario a above, the first network device is the network device to which the cell that failed in the mobility report belongs.

[0102] In the above example, the second network device and the third network device may be the same or different. When the third network device is different from the second network device, the embodiment of the present application may further include: the second network device forwarding the mobility report to the third network device.

[0103] In the above scenario c, if the third network device includes a target network device and a source network device, and the target network device is different from the source network device, this embodiment of the present application may further include: the target network device sending the above-mentioned mobility report to the source network device. Optionally, if in the above scenario a, b, or c, the third network device also includes a network device to which the LTM candidate cell belongs, this embodiment of the present application may further include: the source network device sending the above-mentioned mobility report to the network device to which the LTM candidate cell belongs.

[0104] In some embodiments, the connection failure information includes information indicating the length of time from the last time (i.e., the latest or most recent time) the terminal device received the configuration information of the LTM candidate cell to the occurrence of the connection failure. This information may also be referred to as first time information. As an example, the first time information may be used by a third network device to optimize the timing of sending the configuration information of the LTM candidate cell and / or to optimize the timing of sending an LTM cell change message (e.g., an LTM cell change command) by the third network device, thereby improving LTM robustness.

[0105] In other embodiments, the connection failure information includes information for determining that the mobility type associated with the connection failure is LTM. This information may also be referred to as handover type information. As an example, the handover type information is used by the third network device to determine that the mobility type associated with the connection failure is LTM. For example, the handover type information may be LTM, thereby determining the mobility type associated with the connection failure and performing subsequent processing to improve LTM robustness.

[0106] In some further embodiments, the connection failure information includes information indicating the length of time between the terminal device reporting the L1 measurement result information and the occurrence of the connection failure. This information may also be referred to as second time information. As an example, the second time information may be used by the third network device to optimize the configuration of L1 measurement result information reporting and / or to optimize the transmission time of an LTM cell change message (e.g., an LTM cell change command) by the third network device, thereby improving LTM robustness.

[0107] In some further embodiments, the connection failure information includes information indicating the length of time from when the terminal device receives the configuration information of the LTM candidate cell or the most recent receipt of the configuration information of the LTM candidate cell to when the L1 measurement result information is reported. This information may also be referred to as third time information. As an example, the third time information may be used by a third network device to optimize the timing of sending the configuration information of the LTM candidate cell and / or by the network device to optimize the configuration of reporting the L1 measurement result information, thereby improving LTM robustness.

[0108] In some further embodiments, the connection failure information includes information indicating downlink synchronization information between the terminal device and the LTM candidate cell. This information may also be referred to as first downlink synchronization information. As a possible example, the first downlink synchronization information may include whether the terminal device and the LTM candidate cell have completed downlink synchronization, and / or downlink synchronization time information between the terminal device and the LTM candidate cell. As an example, the first downlink synchronization information may be used by a third network device to optimize the selection of the LTM candidate cell, thereby improving LTM robustness.

[0109] In some further embodiments, the connection failure information includes information for indicating uplink synchronization information between the terminal device and the LTM candidate cell. This information may also be referred to as first uplink synchronization information. As a possible example, the first uplink synchronization information may be whether the terminal device and the LTM candidate cell have completed uplink synchronization, such as whether a random access process has been initiated; optionally, the first uplink synchronization information may be LTM candidate cell information that has completed uplink synchronization, or uplink synchronization completion indication information, used to indicate whether uplink synchronization with a certain LTM candidate cell is completed. As an example, the third network device may optimize the selection of LTM candidate cells, thereby improving LTM robustness.

[0110] In some further embodiments, the connection failure information includes information indicating the LTM candidate cell in the LTM candidate cell configuration information last received by the terminal device, or information indicating the latest LTM candidate cell stored by the terminal device. This information can be referred to as cell information of the LTM candidate cell. As an example, the cell information of the LTM candidate cell can be used by the third network device to optimize the configuration of the LTM candidate cell, thereby improving LTM robustness.

[0111] In some further embodiments, the connection failure information includes information indicating the latest layer 1 (L1) measurement result information of the terminal device or the latest layer 1 (L1) measurement result information before the above-mentioned connection failure occurs. This information may also be referred to as L1 measurement result information, and the L1 measurement result information may include at least one of cell information, beam information, cell measurement result information, and L1 beam measurement result information. As an example, the L1 measurement result information may be used by a third network device to determine the correspondence between the L1 measurement result information and the configuration information of the LTM candidate cell, thereby determining whether the configuration information of the LTM candidate cell needs to be optimized. Optionally, the connection failure information may include indication information indicating whether the cell corresponding to the L1 measurement result information is an LTM candidate cell. The indication information is used to indicate the relationship between the cell information corresponding to the L1 measurement result of the third network device and the LTM candidate cell, and is used by the third network device to determine whether the configuration information of the LTM candidate cell needs to be optimized.

[0112] As a possible example, the L1 measurement result information may include beam type information and / or corresponding beam measurement result information. The beam type information may be at least one of a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB). The beam measurement result information includes at least one of the following information: L1 reference signal received power (RSRP), L1 reference signal received quality (RSRQ), L1 reference signal strength indicator (RSSI), L1 signal to interference plus noise ratio (SINR), or other L1 signal quality information.

[0113] In some further embodiments, the connection failure information includes information indicating the number of LTM candidate cells configured by the first network device and / or the number of reportable beams configured by the first network device. This information may also be referred to as L1 measurement result reporting configuration information. As an example, the L1 measurement result reporting configuration information is used by the third network device to confirm whether the number of LTM candidate cells and / or the number of beams configured by the first network device is appropriate, thereby optimizing their configuration and improving LTM robustness.

[0114] In some further embodiments, the connection failure information includes information for indicating the random access configuration of the terminal device. This information may also be referred to as random access configuration information of the LTM candidate cell, and may include random access configuration information for performing uplink synchronization with the LTM candidate cell before receiving the LTM cell change message (e.g., LTM cell Switch command), and / or random access configuration information for performing a cell change with the LTM candidate cell after receiving the LTM cell change message. As an example, this information may be used by a third network device to optimize the random access configuration of the LTM candidate cell, thereby improving the performance of the random access process and thus improving the robustness of the LTM.

[0115] In some further embodiments, the connection failure information includes information indicating the latest layer 3 (L3) measurement result information of the terminal device or the latest layer 3 (L3) measurement result information before the connection failure occurs. This information may also be referred to as L3 measurement result information. As an example, the L3 measurement result information is used by the third network device to determine whether to optimize the LTM candidate cell based on the L3 measurement result.

[0116] In some other embodiments, the connection failure information includes information indicating whether the cell in the L3 measurement result information is an LTM candidate cell. This information may also be referred to as first indication information, which is used, for example, by the third network device to determine whether the LTM candidate cell needs to be optimized.

[0117] In some further embodiments, the connection failure information includes LTM target cell information. The LTM target cell information is used by the second network device to confirm the LTM target cell where the connection failure occurs, thereby determining the network device corresponding to the mobility report and forwarding the mobility report.

[0118] In some further embodiments, the connection failure information includes information indicating the length of time from when the terminal device receives an LTM cell change message (e.g., an LTM cell switch command) to when the terminal device receives the configuration information of the LTM target cell. This information may also be referred to as fourth time information. As an example, the fourth time information is used by the third network device to optimize the sending time of the LTM cell change message and / or the sending time of the configuration information of the above-mentioned LTM target cell, thereby improving LTM robustness.

[0119] In some further embodiments, the connection failure information includes information indicating the length of time from when the terminal device receives the configuration information of the LTM target cell to when the connection failure occurs. This information may also be referred to as fifth time information. As an example, the fifth time information is used by the third network device to optimize the transmission time of the configuration information of the LTM target cell and / or to optimize the transmission time of the LTM cell change message, thereby reducing the consumption of storage resources of the target network device's resource reservation and improving the robustness of LTM.

[0120] In some further embodiments, the connection failure information includes information indicating the length of time between receipt of an LTM cell change message (e.g., an LTM cell switch command) by the terminal device and occurrence of the connection failure. This information may also be referred to as sixth time information, which is used by the third network device to optimize the transmission time of the configuration information of the LTM candidate cell, thereby reducing resource reservation time on the network device to which the LTM candidate cell belongs and saving its network storage space.

[0121] In some further embodiments, the connection failure information includes information indicating a time advance (TA) of the LTM target cell received by the terminal device. This information may be referred to as TA information. As an example, the TA information is used by the third network device to confirm whether the determination of the TA is reasonable, thereby optimizing the TA determination mechanism, improving the reliability of the TA, and thereby improving the robustness of the LTM.

[0122] In some further embodiments, the connection failure information includes information indicating the length of time from when the terminal device completes uplink synchronization with the LTM target cell to when the timing advance is received. This information may also be referred to as seventh time information. As an example, the seventh time information is used by the third network device to optimize the TA determination mechanism, optimize the TA transmission time, improve the TA reliability, optimize the TA transmission time, and thereby improve the LTM robustness.

[0123] In some further embodiments, the connection failure information includes information indicating the length of time from when the terminal device receives the timing advance to when the terminal device initiates a random access procedure to the LTM target cell or sends the first uplink data. This information may also be referred to as eighth time information. As an example, the eighth time information is used by the third network device to determine the validity of the timing advance. As another example, if the connection failure is a HOF, the eighth time information may be used by the third network device to determine whether the HOF was caused by a TA expiration.

[0124] In some further embodiments, the connection failure information includes information indicating a random access configuration of the terminal device. This information may also be referred to as random access information of the terminal device and the LTM candidate cell. As an example, this information may include random access configuration information for performing uplink synchronization with the LTM candidate cell before receiving the LTM cell change message, and / or random access configuration information for performing a cell change with the LTM target cell after receiving the LTM cell change message.

[0125] In some further embodiments, the connection failure information includes information for indicating the CG (configured grant) configuration of the terminal device in the LTM target cell. This information may also be referred to as the CG configuration information of the terminal device in the LTM target cell. As an example, it is used to indicate the CG configuration configured for the terminal device in the LTM target cell for the first uplink data to occur during the LTM period. The information may include at least one of a CG period, an offset, a HARQ (Hybrid Automatic Repeat-reQuest) process ID, and an associated downlink reference signal.

[0126] The above embodiments are merely exemplary descriptions of connection failure information, but the present application is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, i.e., the connection failure information may include only one of the above information. Alternatively, one or more of the above embodiments may be combined, i.e., the connection failure information may include any combination of the above information.

[0127] For example, in the scenario shown in Figure 4, the connection failure may be a connection failure between the terminal device and the serving cell, such as the above scenario a. Correspondingly, the connection failure information may include any one or any combination of the aforementioned first time information, handover type information, second time information, third time information, first downlink synchronization information, first uplink synchronization information, cell information of the LTM candidate cell, L1 measurement result information, L1 measurement result reporting configuration information, random access configuration information of the LTM candidate cell, L3 measurement result information, and the first indication information.

[0128] For another example, in the scenario shown in Figure 5, the connection failure may be a connection failure between the terminal device and the LTM target cell, such as the above scenario b or the above scenario c. Correspondingly, the connection failure information may include the aforementioned first time information, switching type information, second time information, third time information, first downlink synchronization information, first uplink synchronization information, cell information of the LTM candidate cell, L1 measurement result information, reporting configuration information of the L1 measurement result, random access configuration information of the LTM candidate cell, L3 measurement result information, first indication information, LTM target cell information, fourth time information, fifth time information, sixth time information, timing advance information, seventh time information, eighth time information, random access information of the terminal device and the LTM target cell, and any one or any combination of the CG configuration information of the terminal device in the LTM target cell.

[0129] In an embodiment of the present application, when a terminal device detects a connection failure, the terminal device may attempt to reestablish the process. If the cell that the terminal device attempts to reestablish is an LTM candidate cell or a CHO candidate cell, the connection failure information may also include at least one of the following:

[0130] Cell information used to instruct the terminal device to attempt LTM recovery or CHO recovery;

[0131] Information indicating the type of recovery that takes precedence.

[0132] In the above embodiment, if the cell that the terminal device attempts to re-establish is an LTM candidate cell or a CHO candidate cell, the terminal device may successfully complete the LTM recovery or CHO recovery, or a connection failure may occur again (i.e., a second connection failure), that is, in the same LTM process, a continuous connection failure (or two connection failures) occurs. The terminal device may further record at least one of the following information in the mobility report:

[0133] Information used to indicate the length of time from the last time the terminal device received the above-mentioned LTM candidate cell configuration information to the occurrence of the second connection failure; it can be understood that the second connection failure is a connection failure between the terminal device and the cell attempting LTM recovery or CHO recovery.

[0134] Information indicating the length of time from the previous connection failure to the occurrence of the second connection failure.

[0135] In the above embodiment, the cell information for instructing the terminal device to attempt LTM recovery or CHO recovery may also be referred to as cell information for attempting LTM recovery or CHO recovery.

[0136] For example, if timer T311 is running, the cell selected by the terminal device is an LTM candidate cell or a CHO candidate cell, and the terminal device records the cell information of the attempted LTM recovery or CHO recovery; wherein, the start condition of timer T311 is that the terminal device initiates the re-establishment process.

[0137] In the above embodiment, the information indicating the length of time between the last (or most recent) receipt of the LTM candidate cell configuration information by the terminal device and the occurrence of a second connection failure may also be referred to as ninth time information. As an example, the ninth time information is used by the third network device to optimize the timing of sending the LTM candidate cell configuration information and / or to optimize the timing of sending the LTM cell change message, thereby determining the mobility parameters at the time of the LTM connection failure, and further optimizing the corresponding mobility parameters to improve LTM robustness.

[0138] In the above embodiment, the information indicating the time length from the connection failure to the second connection failure may also be referred to as tenth time information. As an example, the tenth time information is used by the third network device to determine the mobility parameters at the time of the LTM connection failure, thereby optimizing the corresponding mobility parameters and improving LTM robustness.

[0139] In the above embodiment, the information used to indicate the type of recovery to be performed preferentially may also be referred to as priority indication information. If the cell that the terminal device attempts to re-establish is both an LTM candidate cell and a CHO candidate cell, the priority indication information may be used to indicate the type of recovery to be performed preferentially configured for the terminal device by the third network device (e.g., the third network device and the first network device are the same network device). For example, the third network device may configure the terminal device to preferentially perform LTM recovery or preferentially perform CHO recovery.

[0140] In some embodiments, in the scenario shown in Figure 4, if the cell that the terminal device attempts to re-establish is an LTM candidate cell or a CHO candidate cell, the connection failure information may further include at least one of the above-mentioned cell information of attempting LTM recovery or CHO recovery, the ninth time information, the tenth time information and the priority indication information.

[0141] In other embodiments, in the scenario shown in Figure 5, if the cell that the terminal device attempts to re-establish is an LTM candidate cell or a CHO candidate cell, the connection failure information may further include at least one of the above-mentioned cell information of attempting LTM recovery or CHO recovery, the ninth time information, and the tenth time information.

[0142] The following describes the method of the embodiment of the present application by taking the scenarios shown in FIG4 and FIG5 as examples.

[0143] Figure 6 is a schematic diagram of the information interaction process between the terminal device and the network device in the scenario shown in Figure 4. In the example of Figure 6, the first network device is the source base station (SgNB) and the second network device is the receiving node. As shown in Figure 6, the process includes:

[0144] 610: The terminal device receives configuration information of the LTM candidate cell sent by the first network device (source base station);

[0145] 620: The terminal device determines that a connection failure occurs between the terminal device and the serving cell;

[0146] 630: The terminal device records the connection failure information in the mobility report;

[0147] 640: The terminal device sends a mobility report to the second network device (receiving node).

[0148] In operation 610, the LTM candidate cell configuration information may include cell information of the candidate cell. The description of the cell information can refer to the description of other embodiments of the present application and will not be repeated here.

[0149] In operation 620, the connection failure includes a radio link failure (RLF), a handover failure (HOF), a timer expiration, or a connection failure caused by other reasons. In addition, the connection failure is a connection failure between the terminal device and the serving cell, which occurs in the scenario shown in Figure 4, such as the aforementioned scenario a.

[0150] In operation 630, when the terminal device detects that the connection with the current serving cell fails, the terminal device needs to record the corresponding connection failure information. For example, the terminal device can record a mobility report related to the connection failure. The description of the mobility report can refer to the description of each embodiment of the present application and will not be repeated here.

[0151] In the above example, as mentioned above, the terminal device can record the following connection failure information in the above mobility report: first time information, switching type information, second time information, third time information, first downlink synchronization information, first uplink synchronization information, cell information of LTM candidate cells, L1 measurement result information, L1 measurement result reporting configuration information, random access configuration information of LTM candidate cells, L3 measurement result information and any one or any combination of the first indication information.

[0152] In the above example, as mentioned above, if the cell that the terminal device attempts to re-establish is an LTM candidate cell or a CHO candidate cell, the terminal device can record the following connection failure information in the above mobility report: cell information for attempting LTM recovery or CHO recovery, ninth time information, tenth time information, and at least one of priority indication information.

[0153] In operation 640, the terminal device may send the mobility report to the second network device. This application does not limit the specific sending method, adopted link, etc. The relevant content of the second network device has been explained above and will not be repeated here.

[0154] Figure 7 is a schematic diagram of the information interaction process between the terminal device and the network device in the scenario shown in Figure 5. In the example of Figure 7, the first network device is the source base station (SgNB) and the second network device is the receiving node. As shown in Figure 7, the process includes:

[0155] 710: The terminal device receives configuration information of the LTM candidate cell sent by the first network device (source base station);

[0156] 720: The terminal device receives a first change message, where the first change message is used to instruct the terminal device to perform an LTM cell change to an LTM target cell.

[0157] 730: The terminal device determines that a connection failure occurs between the terminal device and the LTM target cell;

[0158] 740: The terminal device records the connection failure information in the mobility report;

[0159] 750: The terminal device sends a mobility report to the second network device (receiving node).

[0160] In operation 710, the LTM candidate cell configuration information may include cell information of the candidate cell. The specific content of the cell information has been described above and will not be repeated here.

[0161] In operation 720 , the first change message is, for example, an LTM cell switch command, but the present application is not limited thereto, and the first change message may also be called by other names.

[0162] In operation 730, the connection failure includes a radio link failure (RLF), a handover failure (HOF), a timer expiration, or other connection failures. Furthermore, the connection failure is a connection failure between the terminal device and the LTM target cell, which occurs in the scenario shown in FIG5 , such as the aforementioned scenario b or scenario c. It is understood that the network device to which the LTM target cell belongs can be referred to as the LTM target network device.

[0163] In operation 740, when the terminal device detects that the connection with the LTM target cell fails, the terminal device needs to record the corresponding connection failure information in the mobility report. The relevant content of the mobility report has been explained above and will not be repeated here.

[0164] In the above example, the connection failure information may, for example, include the aforementioned first time information, switching type information, second time information, third time information, first downlink synchronization information, first uplink synchronization information, cell information of the LTM candidate cell, L1 measurement result information, L1 measurement result reporting configuration information, random access configuration information of the LTM candidate cell, L3 measurement result information, first indication information, LTM target cell information, fourth time information, fifth time information, sixth time information, time advance information, seventh time information, eighth time information, random access information of the terminal device and the LTM target cell, and CG configuration information of the terminal device in the LTM target cell, any one or any combination.

[0165] In the above example, as described above, if the cell that the terminal device attempts to reestablish is an LTM candidate cell or a CHO candidate cell, the terminal device may successfully complete LTM recovery or CHO recovery; or it may fail again, that is, continuous failures occur in the same LTM process. The terminal device may record the following connection failure information in the above mobility report: at least one of the cell information for attempting LTM recovery or CHO recovery, the ninth time information, and the tenth time information.

[0166] In operation 750, the terminal device may send the mobility report to the second network device. This application does not limit the specific sending method, adopted link, etc. The relevant content of the second network device has been explained above and will not be repeated here.

[0167] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0168] According to the method of the embodiment of the present application, a SON enhancement solution in the LTM scenario is introduced, so that the terminal device can report LTM-related connection failure information, so that the network device can make corresponding parameter adjustments based on the connection failure information, thereby improving the robustness of LTM.

[0169] Embodiments of the second aspect

[0170] The embodiment of the present application provides a method for mobility management, which is described from the perspective of the second network device. The same contents as those in the embodiment of the first aspect will not be repeated.

[0171] FIG8 is a schematic diagram of a method for mobility management according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0172] 810: The second network device receives a mobility report sent by the terminal device, where the mobility report includes connection failure information, and the connection failure information includes at least one of the following: information indicating the length of time from the last time the terminal device received the above-mentioned configuration information to the occurrence of the connection failure; information used to determine that the mobility type related to the connection failure is LTM.

[0173] The relevant content of the above-mentioned connection failure information has been explained in the embodiment of the first aspect, and its content is incorporated here and will not be repeated here.

[0174] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0175] According to the method of the embodiment of the present application, a SON enhancement solution in the LTM scenario is introduced, so that the terminal device can report LTM-related connection failure information, so that the network device can make corresponding parameter adjustments based on the connection failure information, thereby improving the robustness of LTM.

[0176] Embodiments of the third aspect

[0177] An embodiment of the present application provides a device for mobility management.

[0178] Figure 9 is a schematic diagram of a mobility management apparatus according to an embodiment of the present application. The apparatus may be, for example, a terminal device, or may be one or more components or assemblies configured on the terminal device. Because the principles for solving the problem of this apparatus are the same as those of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method of the embodiment of the first aspect, and the details of the common content will not be repeated here.

[0179] As shown in FIG9 , the apparatus 900 includes:

[0180] a receiving unit 910 configured to receive configuration information for configuring a layer 1 / layer 2 triggered mobility (LTM) candidate cell sent by a first network device;

[0181] a determining unit 920, which determines that an LTM connection failure occurs;

[0182] The processing unit 930 records connection failure information, where the connection failure information includes at least one of the following:

[0183] Information indicating the length of time between the last time the terminal device received the configuration information and the occurrence of the connection failure;

[0184] Information used to determine that the mobility type related to the connection failure is LTM.

[0185] In some embodiments, the connection failure information further includes at least one of the following:

[0186] Information used to indicate the length of time between the terminal device reporting the L1 measurement result information and the occurrence of the connection failure;

[0187] Information used to indicate the length of time from when the terminal device receives the configuration information or receives the configuration information for the last time to when the L1 measurement result information is reported;

[0188] Information used to indicate downlink synchronization information between the terminal device and the LTM candidate cell;

[0189] Information used to indicate uplink synchronization information between the terminal device and the LTM candidate cell;

[0190] Used to indicate the LTM candidate cell in the configuration information last received by the terminal device or used to indicate the latest LTM candidate cell information stored by the terminal device;

[0191] Information used to indicate the latest L1 measurement result information of the terminal device or the latest L1 measurement result information before the connection failure occurs;

[0192] Information used to indicate the number of LTM candidate cells and / or the number of configured reference signals configured by the first network device;

[0193] Information used to indicate the random access configuration of the terminal device;

[0194] Information used to indicate the latest L3 measurement result information of the terminal device or the latest L3 measurement result information before the connection failure occurs;

[0195] Information used to indicate whether the cell in the L3 measurement result information is the LTM candidate cell.

[0196] In some embodiments, the connection failure is a connection failure between the terminal device and the LTM target cell, and the connection failure information further includes at least one of the following:

[0197] LTM target cell information;

[0198] Information used to indicate the length of time from when the terminal device receives the LTM cell change message to when the terminal device receives the configuration information of the LTM target cell;

[0199] Information used to indicate the length of time between the terminal device receiving the configuration information of the LTM target cell and the occurrence of the connection failure;

[0200] Information used to indicate the length of time between the terminal device receiving the LTM cell change message and the occurrence of the connection failure;

[0201] Information used to indicate the timing advance of the LTM target cell received by the terminal device;

[0202] Information indicating the length of time from the completion of uplink synchronization between the terminal device and the LTM target cell to the receipt of the timing advance;

[0203] Information indicating the length of time from when the terminal device receives the timing advance to when the terminal device initiates a random access procedure to the LTM target cell or sends the first uplink data;

[0204] Information used to indicate the random access configuration of the terminal device;

[0205] Information used to indicate the CG configuration of the terminal device in the LTM target cell.

[0206] In the above embodiment, the information used to indicate the random access configuration of the terminal device may include at least one of the following:

[0207] Random access configuration information used for uplink synchronization with LTM candidate cells before receiving the LTM cell change message;

[0208] Random access configuration information used to perform a cell change with the LTM target cell after receiving the LTM cell change message.

[0209] In some embodiments, the cell that the terminal device attempts to re-establish is an LTM candidate cell or a conditional handover (CHO) candidate cell, and the connection failure information further includes at least one of the following:

[0210] Cell information used to instruct the terminal device to attempt LTM recovery or CHO recovery;

[0211] Information indicating the length of time between the last time the terminal device received the configuration information and the second connection failure;

[0212] Information indicating the length of time from the connection failure to the occurrence of a second connection failure;

[0213] Information indicating the type of recovery that takes precedence.

[0214] In some embodiments, as shown in FIG9 , the apparatus 900 further includes:

[0215] The sending unit 940 is configured to send a mobility report to the second network device, where the mobility report includes the connection failure information.

[0216] Figure 10 is another schematic diagram of a mobility management apparatus according to an embodiment of the present application. The apparatus may be a network device, or may be one or more components or assemblies configured on the network device. Since the principle of solving the problem of this apparatus is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the implementation of the method of the embodiment of the second aspect, and the details of the same content will not be repeated here.

[0217] As shown in FIG10 , the apparatus 1000 includes:

[0218] The receiving unit 1010 receives a mobility report sent by a terminal device, where the mobility report includes connection failure information, and the connection failure information includes at least one of the following:

[0219] Information indicating the length of time between the last time the terminal device received the configuration information and the occurrence of the connection failure;

[0220] Information used to determine that the mobility type related to the connection failure is LTM.

[0221] In some embodiments, the connection failure information further includes at least one of the following:

[0222] Information used to indicate the length of time between the terminal device reporting the L1 measurement result information and the occurrence of the connection failure;

[0223] Information used to indicate the length of time from when the terminal device receives the configuration information or receives the configuration information for the last time to when the L1 measurement result information is reported;

[0224] Information used to indicate downlink synchronization information between the terminal device and the LTM candidate cell;

[0225] Information used to indicate uplink synchronization information between the terminal device and the LTM candidate cell;

[0226] Used to indicate the LTM candidate cell in the configuration information last received by the terminal device or used to indicate the latest LTM candidate cell information stored by the terminal device;

[0227] Information used to indicate the latest L1 measurement result information of the terminal device or the latest L1 measurement result information before the connection failure occurs;

[0228] Information used to indicate the number of LTM candidate cells and / or the number of configured reference signals configured by the first network device;

[0229] Information used to indicate the random access configuration of the terminal device;

[0230] Information used to indicate the latest L3 measurement result information of the terminal device or the latest L3 measurement result information before the connection failure occurs;

[0231] Information used to indicate whether the cell in the L3 measurement result information is the LTM candidate cell.

[0232] In some embodiments, the connection failure is a connection failure between the terminal device and the LTM target cell, and the connection failure information further includes at least one of the following:

[0233] LTM target cell information;

[0234] Information used to indicate the length of time from when the terminal device receives the LTM cell change message to when the terminal device receives the configuration information of the LTM target cell;

[0235] Information used to indicate the length of time between the terminal device receiving the configuration information of the LTM target cell and the occurrence of the connection failure;

[0236] Information used to indicate the length of time between the terminal device receiving the LTM cell change message and the occurrence of the connection failure;

[0237] Information used to indicate the timing advance of the LTM target cell received by the terminal device;

[0238] Information indicating the length of time from the completion of uplink synchronization between the terminal device and the LTM target cell to the receipt of the timing advance;

[0239] Information indicating the length of time from when the terminal device receives the timing advance to when the terminal device initiates a random access procedure to the LTM target cell or sends the first uplink data;

[0240] Information used to indicate the random access configuration of the terminal device;

[0241] Information used to indicate the CG configuration of the terminal device in the LTM target cell.

[0242] In the above embodiment, the information used to indicate the random access configuration of the terminal device may include at least one of the following:

[0243] Random access configuration information used for uplink synchronization with LTM candidate cells before receiving the LTM cell change message;

[0244] Random access configuration information used to perform a cell change with the LTM target cell after receiving the LTM cell change message.

[0245] In some embodiments, the cell that the terminal device attempts to re-establish is an LTM candidate cell or a conditional handover (CHO) candidate cell, and the connection failure information further includes at least one of the following:

[0246] Cell information used to instruct the terminal device to attempt LTM recovery or CHO recovery;

[0247] Information indicating the length of time between the last time the terminal device received the configuration information and the second connection failure;

[0248] Information indicating the length of time from the connection failure to the occurrence of a second connection failure;

[0249] Information indicating the type of recovery that takes precedence.

[0250] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0251] It is worth noting that the above description only describes the components or modules related to this application, but this application is not limited thereto. The above-mentioned device may also include other components or modules. For the specific content of these components or modules, please refer to the relevant art. In addition, the above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0252] According to the apparatus of the embodiment of the present application, a SON enhancement solution in the LTM scenario is introduced, so that the terminal device can report LTM-related connection failure information, so that the network device can make corresponding parameter adjustments based on the connection failure information, thereby improving the robustness of LTM.

[0253] Embodiments of the fourth aspect

[0254] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0255] FIG11 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG11 , a communication system 1100 may include a network device 1110 and terminal devices 1120 and 1130. For simplicity, FIG11 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0256] In the embodiment of the present application, existing services or future services can be transmitted between the network device 1110 and the terminal devices 1120 and 1130. For example, these services may include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0257] It is worth noting that Figure 11 shows that both terminal devices 1120 and 1130 are within the coverage range of network device 1110, but the present application is not limited thereto. Both terminal devices 1120 and 1130 may not be within the coverage range of network device 1110, or one terminal device 1120 may be within the coverage range of network device 1110 while the other terminal device 1130 is outside the coverage range of network device 1110.

[0258] In some embodiments, the network device includes the apparatus 1000 described in the embodiment of the third aspect, configured to perform the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.

[0259] The above-mentioned network device can be an intra-DU mobility scenario, including a gNB-DU and a gNB-CU, or a gNB in ​​an inter-DU mobility scenario, including a source gNB-DU, a candidate or target gNB-DU, and a gNB-CU, and performs the method described in the embodiment of the second aspect.

[0260] In some embodiments, the terminal device includes the apparatus 900 described in the embodiment of the third aspect, and is configured to perform the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0261] The above-mentioned terminal device can be a UE in an intra-DU mobility scenario or an inter-DU mobility scenario, and executes the method described in the embodiment of the first aspect.

[0262] An embodiment of the present application also provides a network device, which may be, for example, a base station, such as a gNB in ​​an intra-DU mobility scenario or an inter-DU mobility scenario, but the present application is not limited thereto and may also be other network devices.

[0263] Figure 12 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 12 , network device 1200 may include a processor 1210 and a memory 1220 ; the memory 1220 is coupled to the processor 1210 . The memory 1220 may store various data and information processing programs, which are executed under the control of the processor 1210 .

[0264] In some embodiments, the functions of the device 1000 of the embodiment of the third aspect can be integrated into the processor 1210, wherein the processor 1210 can be configured to execute a program to implement the method described in the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0265] In other embodiments, the apparatus 1000 of the embodiment of the third aspect may be configured separately from the processor 1210. For example, the apparatus 1000 of the embodiment of the third aspect may be configured as a chip connected to the processor 1210, and the functions of the apparatus 1000 of the embodiment of the third aspect may be implemented through the control of the processor 1210.

[0266] Furthermore, as shown in FIG12 , network device 1200 may further include transceivers 1230 and 1240. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that network device 1200 does not necessarily include all of the components shown in FIG12 ; furthermore, network device 1200 may also include components not shown in FIG12 , for which reference may be made to the prior art.

[0267] An embodiment of the present application also provides a terminal device, which may be, for example, a UE, such as a UE in an intra-DU mobility scenario or an inter-DU mobility scenario, but the present application is not limited thereto and may also be other terminal devices.

[0268] Figure 13 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 13 , terminal device 1300 may include a processor 1310 and a memory 1320. Memory 1320 stores data and programs and is coupled to processor 1310. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0269] In some embodiments, the functions of the device 900 of the embodiment of the third aspect can be integrated into the processor 1310, wherein the processor 1310 can be configured to execute a program to implement the method described in the embodiment of the second aspect, the content of which is incorporated herein and will not be repeated here.

[0270] In other embodiments, the device 900 of the embodiment of the third aspect can be configured separately from the processor 1310. For example, the device 900 of the embodiment of the third aspect can be configured as a chip connected to the processor 1310, and the functions of the device 900 of the embodiment of the third aspect can be realized through the control of the processor 1310.

[0271] As shown in Figure 13 , the terminal device 1300 may further include: a communication module 1330, an input unit 1340, a display 1350, and a power supply 1360. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1300 does not necessarily include all of the components shown in Figure 13 , and the aforementioned components are not essential. Furthermore, the terminal device 1300 may also include components not shown in Figure 13 , for which reference may be made to the relevant art.

[0272] An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0273] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0274] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0275] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0276] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0277] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0278] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0279] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0280] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

Claims

1. An apparatus for mobility management, configured in a terminal device, wherein, The device includes: a receiving unit that receives configuration information for configuring a Layer 1 / Layer 2 Triggered Mobility (LTM) candidate cell sent by a first network device; a determining unit that determines that an LTM connection failure occurs; a processing unit that records connection failure information, where the connection failure information includes at least one of the following: information for indicating the time length between the last receipt of the configuration information from the terminal device and the occurrence of the connection failure; information for determining that the mobility type related to the connection failure is LTM.

2. The apparatus according to claim 1, wherein, The connection failure information further includes at least one of the following: information for indicating the time length between the reporting of Layer 1 (L1) measurement result information from the terminal device and the occurrence of the connection failure; information for indicating the time length between the receipt of the configuration information or the last receipt of the configuration information by the terminal device and the reporting of the L1 measurement result information; information for indicating the downlink synchronization information between the terminal device and the LTM candidate cell; information for indicating the uplink synchronization information between the terminal device and the LTM candidate cell; information for indicating the LTM candidate cell in the last configuration information received by the terminal device or for indicating the latest LTM candidate cell stored by the terminal device; information for indicating the latest or the latest L1 measurement result information before the occurrence of the connection failure of the terminal device; indication information for indicating whether the cell corresponding to the L1 measurement result information is an LTM candidate cell; information for indicating the number of LTM candidate cells configured by the first network device and / or the number of configured reference signals; information for indicating the random access configuration of the terminal device; information for indicating the latest or the latest L3 measurement result information before the occurrence of the connection failure of the terminal device; information for indicating whether the cell in the Layer 3 (L3) measurement result information is the LTM candidate cell.

3. The apparatus according to claim 2, wherein, The connection failure is the connection failure between the terminal device and the LTM target cell, and the connection failure information further includes at least one of the following: LTM target cell information; information for indicating the time length between the receipt of the LTM cell change message by the terminal device and the receipt of the configuration information of the LTM target cell by the terminal device; information for indicating the time length between the receipt of the configuration information of the LTM target cell by the terminal device and the occurrence of the connection failure; information for indicating the time length between the receipt of the LTM cell change message by the terminal device and the occurrence of the connection failure; information for indicating the time advance of the LTM target cell received by the terminal device; information for indicating the time length between the completion of the uplink synchronization between the terminal device and the LTM target cell and the receipt of the time advance; information for indicating the time length between the receipt of the time advance by the terminal device and the terminal device initiating a random access procedure to the LTM target cell or sending the first uplink data; information for indicating the random access configuration of the terminal device; Information for indicating the configured grant (CG) configuration of the terminal device in the LTM target cell.

4. The apparatus according to claim 2, wherein, Information for indicating the random access configuration of the terminal device, including at least one of the following: Random access configuration information for performing uplink synchronization with the LTM candidate cell before receiving the LTM cell change message; Random access configuration information for performing cell change with the LTM target cell after receiving the LTM cell change message.

5. The apparatus according to claim 1, wherein, The cell that the terminal device attempts to re-establish is an LTM candidate cell or a conditional handover (CHO) candidate cell, and the connection failure information further includes at least one of the following: Cell information for indicating that the terminal device attempts to perform LTM recovery or CHO recovery; Information for indicating the time length between the last time the terminal device received the configuration information and the occurrence of the second connection failure; Information for indicating the time length between the connection failure and the occurrence of the second connection failure; Information for indicating the type of recovery to be preferentially performed.

6. The device according to claim 1, wherein, The device further includes: The terminal device sends a mobility report to the second network device, and the mobility report includes the connection failure information.

7. A device for mobility management, configured in a network device, wherein, The device includes, A receiving unit that receives a mobility report sent by a terminal device, the mobility report includes connection failure information, and the connection failure information includes at least one of the following: Information for indicating the time length between the last time the terminal device received the configuration information and the occurrence of the connection failure; Information for determining that the mobility type related to the connection failure is LTM.

8. The device according to claim 7, wherein, The connection failure information further includes at least one of the following: Information for indicating the time length between the terminal device reporting the L1 measurement result information and the occurrence of the connection failure; Information for indicating the time length between the terminal device receiving the configuration information or the last time receiving the configuration information and reporting the L1 measurement result information; Information for indicating the downlink synchronization information between the terminal device and the LTM candidate cell; Information for indicating the uplink synchronization information between the terminal device and the LTM candidate cell; Information for indicating the LTM candidate cell in the last configuration information received by the terminal device or for indicating the latest LTM candidate cell stored by the terminal device; Information for indicating the latest L1 measurement result information of the terminal device or the latest L1 measurement result information before the occurrence of the connection failure; Indicator information for indicating whether the cell corresponding to the L1 measurement result information is an LTM candidate cell; Information for indicating the number of LTM candidate cells configured by the first network device and / or the number of configured reference signals; Information for indicating the random access configuration of the terminal device; Information for indicating the latest L3 measurement result information of the terminal device or the latest L3 measurement result information before the occurrence of the connection failure; Information for indicating whether the cell in the L3 measurement result information is the LTM candidate cell.

9. The device according to claim 8, wherein, The connection failure is the connection failure between the terminal device and the LTM target cell, and the connection failure information further includes at least one of the following: LTM target cell information; Information for indicating the time length between the terminal device receiving the LTM cell change message and the terminal device receiving the configuration information of the LTM target cell; For indicating the time between the terminal device receiving the configuration information of the LTM target cell and the occurrence of the connection failure Information on the time length; Information for indicating the time length between the terminal device receiving the LTM cell change message and the occurrence of the connection failure; Information for indicating the timing advance of the LTM target cell received by the terminal device; Information for indicating the time length between the terminal device completing uplink synchronization with the LTM target cell and receiving the timing advance; Information for indicating the time length between the terminal device receiving the timing advance and the terminal device initiating a random access procedure to the LTM target cell or sending the first uplink data; Information for indicating the random access configuration of the terminal device; Information for indicating the CG configuration of the terminal device in the LTM target cell.

10. The device according to claim 8, wherein, Information for indicating the random access configuration of the terminal device, including at least one of the following: Random access configuration information for performing uplink synchronization with the LTM candidate cell before receiving the LTM cell change message; Random access configuration information for performing cell change with the LTM target cell after receiving the LTM cell change message.

11. The device according to claim 7, wherein, The cell that the terminal device attempts to re - establish is an LTM candidate cell or a CHO candidate cell, and the connection failure information further includes at least one of the following: Information for indicating the cell information of the terminal device attempting LTM recovery or CHO recovery; Information for indicating the time length between the terminal device last receiving the configuration information and the occurrence of the second connection failure; Information for indicating the time length between the connection failure and the occurrence of the second connection failure; Information for indicating the type of recovery to be preferentially executed.

12. A terminal device, comprising a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method: Receive configuration information sent by a first network device for configuring an LTM candidate cell; Determine that an LTM connection failure occurs; Record connection failure information, where the connection failure information includes at least one of the following: Information for indicating the time length between the last time the terminal device received the configuration information and the occurrence of the connection failure; Information for determining that the mobility type related to the connection failure is LTM.

Images