A method for configuring mobility parameters and related equipment

Abstract

This application discloses a mobility parameter configuration method and related equipment. The method can be implemented through interaction between a first network management device and a second network management device. The first network management device can send mobility optimization attributes to the second network management device. These mobility optimization attributes are used to indicate attributes configured in cases of secondary cell radio link failure and / or impending radio link failure. In other words, this method achieves mobility parameter optimization in multi-link data transmission scenarios and successful handover scenarios, ensuring mobility performance.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a mobility parameter configuration method and related equipment. Background Technology

[0002] In mobile communication systems, changes in the location of a terminal device or changes in network load may necessitate a handover from one network device to another. For example, a change in the location of a terminal device might require a handover from base station 1 to base station 2. Improperly configured mobility optimization attributes can lead to problems such as premature or late handovers, ping-pong effects, etc., resulting in handover failures and reduced system performance. Summary of the Invention

[0003] This application provides a mobility parameter configuration method and related equipment. The method provides mobility optimization attributes configured in the event of secondary cell radio link failure and / or impending radio link failure, which helps to reduce the handover failure rate within or between systems and ensure mobility performance.

[0004] In a first aspect, embodiments of this application provide a mobility parameter configuration method, which can be executed by a first network management device. The first network management device can be a network management entity defined by the standardization organization 3GPP, such as a management service consumer. The first network management device can send mobility optimization attributes to a second network management device. These mobility optimization attributes are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure.

[0005] Among them, "secondary cell radio link failure" indicates that in a multi-link data transmission scenario, the failure of the secondary cell radio link is caused by changes in the secondary base station or secondary cell. "Imminent radio link failure" indicates that in a scenario where the terminal device has successfully handed over, the radio link quality between the terminal device and the base station is poor, meaning that the radio link between the terminal device and the base station may be disconnected at any time.

[0006] As can be seen, the mobility optimization attributes provided in this application embodiment can be configured to address the two types of radio link failures mentioned above. For example, configuring mobility optimization attributes for secondary cell radio link failures and for near-radio link failures for base stations, cells, or users helps reduce the handover failure rate within or between systems, thus ensuring mobility performance.

[0007] In one possible design, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger constraint parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0008] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0009] It is evident that the first strategy parameter can limit the relevant parameters of cell-specific offset during secondary cell handover and the minimum time interval between secondary cell handovers, thereby helping to avoid secondary cell radio link failures caused by secondary base station handovers being too early or too late in multi-link data transmission scenarios, and reducing the probability of near-radio link failure in successful handover scenarios.

[0010] In one possible design, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate, ping-pong handover rate, premature handover failure rate, or late handover call drop rate.

[0011] It is evident that the first target parameter can limit the maximum number of cell handover triggers and the handover ratio in cases of early or late secondary base station handovers. This helps to reduce the probability of secondary cell radio link failure caused by early or late secondary base station handovers in multi-link data transmission scenarios, as well as the probability of near-radio link failure in successful handover scenarios.

[0012] In one possible design, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0013] It is evident that the first control parameter can control the mobility optimization attribute to address the secondary cell link failure problem in multi-link data transmission scenarios, and can also control the mobility optimization attribute to address the near-radio link failure problem in successful handover scenarios.

[0014] In one possible design, the first objective parameter includes a mobility optimization attribute comprising a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter.

[0015] The abnormal coverage policy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameters include one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0016] As can be seen, the second strategy parameter can limit the abnormal coverage strategy of the base station, as well as the threshold for the proportion of secondary base station handover failure, the threshold for the proportion of radio link failure, and other parameters, thereby determining the mobility optimization attributes at the base station level.

[0017] In one possible design, the mobility optimization attribute includes a second objective parameter, which may include one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization objective parameter. The handover-triggered optimization objective parameter may include one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0018] In one possible design, mobility optimization attributes include one or more of a first policy parameter, a first objective parameter, a first control parameter, a second policy parameter, or a second objective parameter.

[0019] In one possible design, the first network management device can also receive a response message sent by the second network management device, which indicates the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0020] As can be seen, after receiving the mobility optimization attribute, the second network management device can configure the mobility optimization attribute. Furthermore, the second network management device sends feedback on the configuration status to the first network management device, allowing the first network management device to understand whether the second network management device has successfully configured the mobility optimization attribute.

[0021] In one possible design, the first network management device sends a request message to the second network management device, which requests mobility optimization performance data corresponding to a mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The first network management device receives feedback information from the second network management device, including the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute in the event of secondary cell radio link failure and / or impending radio link failure.

[0022] As can be seen, the second network management device can also report system performance data after configuring mobility optimization attributes, and record the improvement in system performance caused by the configuration of the mobility optimization attributes.

[0023] In one possible design, mobility optimization performance data includes one or more of the following: total number of secondary node handovers, total number of secondary node handover failures, number of times a ping-pong effect occurs, number of times a secondary node is updated too early, number of times a secondary node is updated too late, number of times a secondary node is switched to the wrong cell, or number of times a radio link is on the verge of failure.

[0024] Secondly, embodiments of this application provide a mobility parameter configuration method, which can be executed by a second network management device. The second network management device can be a network management entity defined by the standardization organization 3GPP, such as a management service consumer. The second network management device can receive mobility optimization attributes sent by a first network management device. These mobility optimization attributes are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure. The second network management device can also send the mobility optimization attributes to a second network device, so that the second network device can adjust the handover parameters during the handover process from the first network device to the second network device according to the mobility optimization attributes in the event of secondary cell radio link failure and / or impending radio link failure.

[0025] It is evident that the second network management device can receive the mobility optimization attribute and also send it to subordinate network devices (such as secondary base stations) so that the network devices can configure handover parameters according to the mobility optimization attribute, thereby helping to reduce the probability of handover failure of terminal devices between secondary cells or secondary base stations.

[0026] In one possible design, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger constraint parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0027] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover; the handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters; and the handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or the optimization triggering threshold corresponding to near radio link failure.

[0028] In one possible design, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate, ping-pong handover rate, premature handover failure rate, or late handover call drop rate.

[0029] In one possible design, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0030] In one possible design, the first objective parameter includes a mobility optimization attribute comprising a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter.

[0031] The abnormal coverage policy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameters include one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0032] In one possible design, the mobility optimization attribute includes a second objective parameter, which may include one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization objective parameter. The handover-triggered optimization objective parameter may include one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0033] In one possible design, the mobility optimization attributes include one or more of the following: a first policy parameter, a first objective parameter, a first control parameter, a second policy parameter, or a second objective parameter.

[0034] In one possible design, the second network management device can also send a response message to the first network management device, indicating the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0035] In one possible design, the second network management device receives a request message from the first network management device. This request message requests mobility optimization performance data corresponding to a mobility optimization attribute and / or an indication of such data. The second network management device sends feedback information to the first network management device, including the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of such data in the event of secondary cell radio link failure and / or impending radio link failure.

[0036] In one possible design, mobility optimization performance data includes one or more of the following: total number of secondary node handovers, total number of secondary node handover failures, number of times a ping-pong effect occurs, number of times a secondary node is updated too early, number of times a secondary node is updated too late, number of times a secondary node is switched to the wrong cell, or number of times a radio link is on the verge of failure.

[0037] Thirdly, embodiments of this application provide a first network management device, which includes a processing unit and a transceiver unit. The processing unit is used to determine mobility optimization attributes, which are attributes configured to indicate situations where a secondary cell radio link fails and / or is on the verge of failure. The transceiver unit is used to send the mobility optimization attributes to a second network management device.

[0038] In one possible design, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger constraint parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0039] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0040] In one possible design, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate, ping-pong handover rate, premature handover failure rate, or late handover call drop rate.

[0041] In one possible design, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0042] In one possible design, the first objective parameter includes a mobility optimization attribute comprising a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter.

[0043] The abnormal coverage policy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameters include one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0044] In one possible design, the mobility optimization attribute includes a second objective parameter, which may include one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization objective parameter. The handover-triggered optimization objective parameter may include one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0045] In one possible design, the mobility optimization attributes include one or more of the following: a first policy parameter, a first objective parameter, a first control parameter, a second policy parameter, or a second objective parameter.

[0046] In one possible design, the transceiver unit is also used to receive a response message sent by the second network management device, which indicates the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0047] In one possible design, the transceiver unit is further configured to send a request message to the second network management device, the request message being used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The transceiver unit is also configured to receive feedback information sent by the second network management device, the feedback information including, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0048] In one possible design, mobility optimization performance data includes one or more of the following: total number of secondary node handovers, total number of secondary node handover failures, number of times a ping-pong effect occurs, number of times a secondary node is updated too early, number of times a secondary node is updated too late, number of times a secondary node is switched to the wrong cell, or number of times a radio link is on the verge of failure.

[0049] Fourthly, embodiments of this application provide a second network management device, which includes a transceiver unit. The transceiver unit is configured to receive mobility optimization attributes sent by a first network management device. These mobility optimization attributes are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure. The transceiver unit is further configured to send the mobility optimization attributes to a second network device, so that the second network device adjusts handover parameters during the handover process from the first network device to the second network device based on the mobility optimization attributes in the event of secondary cell radio link failure and / or impending radio link failure.

[0050] In one possible design, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger constraint parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0051] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover; the handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters; and the handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or the optimization triggering threshold corresponding to near radio link failure.

[0052] In one possible design, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate, ping-pong handover rate, premature handover failure rate, or late handover call drop rate.

[0053] In one possible design, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0054] In one possible design, the first objective parameter includes a mobility optimization attribute comprising a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter.

[0055] The abnormal coverage policy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameters include one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0056] In one possible design, the mobility optimization attribute includes a second objective parameter, which may include one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization objective parameter. The handover-triggered optimization objective parameter may include one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0057] In one possible design, the mobility optimization attributes include one or more of the following: a first policy parameter, a first objective parameter, a first control parameter, a second policy parameter, or a second objective parameter.

[0058] In one possible design, the transceiver unit is also used to send a response message to the first network management device, which indicates the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0059] In one possible design, the transceiver unit is further configured to receive a request message sent by the first network management device, the request message being used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The transceiver unit is also configured to send feedback information to the first network management device, the feedback information including, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0060] In one possible design, mobility optimization performance data includes one or more of the following: total number of secondary node handovers, total number of secondary node handover failures, number of times a ping-pong effect occurs, number of times a secondary node is updated too early, number of times a secondary node is updated too late, number of times a secondary node is switched to the wrong cell, or number of times a radio link is on the verge of failure.

[0061] Fifthly, embodiments of this application provide a first network management device that has the function of implementing the mobility parameter configuration method provided in the first aspect. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0062] Sixthly, embodiments of this application provide a second network management device that has the function of implementing the mobility parameter configuration method provided in the second aspect. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0063] In a seventh aspect, embodiments of this application provide a communication system, which includes a first network management device provided in the third or fifth aspect above, and a second network management device provided in the fourth or sixth aspect.

[0064] Eighthly, embodiments of this application provide a computer-readable storage medium including a program or instructions that, when executed on a computer, cause the computer to perform the method of the first aspect or any possible implementation thereof.

[0065] In a ninth aspect, embodiments of this application provide a computer-readable storage medium including a program or instructions that, when executed on a computer, cause the computer to perform the method of the second aspect or any possible implementation thereof.

[0066] In a tenth aspect, embodiments of this application provide a chip or chip system including at least one processor and an interface, the interface and at least one processor being interconnected via a circuit, the at least one processor being configured to run a computer program or instructions to perform the methods described in the first aspect or any of the possible implementations of the first aspect.

[0067] Eleventhly, embodiments of this application provide a chip or chip system including at least one processor and an interface, the interface and at least one processor being interconnected via a circuit, the at least one processor being used to run computer programs or instructions to perform the methods described in the second aspect or any possible implementation of the second aspect.

[0068] The interfaces in the chip can be input / output interfaces, pins, or circuits, etc.

[0069] The chip system mentioned above can be a system on chip (SOC) or a baseband chip, etc. The baseband chip can include processors, channel encoders, digital signal processors, modems and interface modules, etc.

[0070] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage module of the chip, such as a register or cache, or it can be a storage module of the chip itself (e.g., read-only memory, random access memory, etc.).

[0071] In a twelfth aspect, embodiments of this application provide a computer program or computer program product, including code or instructions, which, when executed on a computer, cause the computer to perform the method in the first aspect or any possible implementation of the first aspect.

[0072] In a thirteenth aspect, embodiments of this application provide a computer program or computer program product, including code or instructions, which, when executed on a computer, cause the computer to perform the method in the second aspect or any possible implementation thereof. Attached Figure Description

[0073] Figure 1a A schematic diagram illustrating a scenario of premature switching, provided as an embodiment of this application;

[0074] Figure 1b A schematic diagram illustrating a mobility optimization scenario provided in an embodiment of this application;

[0075] Figure 2a This is a schematic diagram illustrating a multi-link data transmission scenario provided in an embodiment of this application.

[0076] Figure 2b This is a schematic diagram illustrating a terminal device failing to hand over between secondary base stations in a multi-link data transmission scenario, as provided in an embodiment of this application.

[0077] Figure 3 This is a schematic diagram illustrating a near-wireless link failure scenario in a successful handover scenario, provided as an embodiment of this application.

[0078] Figure 4 A schematic diagram of a communication system provided in an embodiment of this application;

[0079] Figure 5 A schematic diagram of a service-oriented management architecture provided in an embodiment of this application;

[0080] Figure 6 A flowchart illustrating a mobility parameter configuration method provided in an embodiment of this application;

[0081] Figure 7 This application provides a schematic diagram of a process for a first network management device and a second network management device to manage mobility optimization performance data.

[0082] Figure 8 A flowchart illustrating the management of MRO performance metrics by a first network management device and a second network management device, provided as an embodiment of this application;

[0083] Figure 9 A schematic diagram illustrating the process of managing MRO performance indicators using a first network management device and a second network management device, as provided in an embodiment of this application;

[0084] Figure 10 This application provides a schematic diagram of the structure of a first network management device according to an embodiment of the present application.

[0085] Figure 11 A schematic diagram of another first network management device provided in the embodiments of this application;

[0086] Figure 12 This is a schematic diagram of the structure of a second network management device provided in an embodiment of this application;

[0087] Figure 13 This is a schematic diagram of the structure of another second network management device provided in an embodiment of this application. Detailed Implementation

[0088] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0089] Before describing the embodiments of this application, the relevant concepts will be explained first.

[0090] In mobile communication systems, changes in the location of a terminal device or changes in network load may necessitate a handover from one network device to another. For example, a change in the location of a terminal device might require a handover from base station 1 to base station 2. Improper handover parameters on the network devices can lead to problems such as premature handover, late handover, or ping-pong effects, resulting in handover failure and reduced system performance.

[0091] For example, please see Figure 1a , Figure 1aThis diagram illustrates a premature handover scenario provided in an embodiment of this application. After the source cell issues a handover command to the terminal device, the handover to the target cell fails due to poor signal quality. In other words, radio link failure (RLF) between the terminal device and the target cell occurs before the handover is completed. The terminal device performs cell selection, selects the source cell, and attempts to re-establish radio resource control (RRC). The terminal device re-establishes itself with the source cell. After successful re-establishment, the source cell recognizes this as a premature handover scenario.

[0092] If handover parameters are improperly configured, they can be manually adjusted. However, manually configuring these parameters is time-consuming, and adjusting them after initial network deployment incurs significant costs. Therefore, the Mobility Robust Optimization (MRO) feature was proposed in Long Term Evolution (LTE) networks to optimize improperly configured handover parameters.

[0093] During the MRO optimization period, the base station can count the number of abnormal handovers. When the optimization period ends, the relevant handover parameters are optimized based on the count of abnormal handovers and a preset threshold.

[0094] Furthermore, after optimizing the handover-related parameters, the network management device can monitor whether various handover metrics have been optimized. If the handover metrics are optimized, the parameters will not be rolled back in the next optimization cycle; if the handover metrics deteriorate, the parameters will be rolled back in the next cycle. It is evident that MRO, by optimizing the handover-related parameters, can reduce the handover failure rate, user call drop rate, and the number of premature or late handovers in the network.

[0095] For example, MRO functionality can be applied to, for example... Figure 1a In the scenario shown, the switch occurred too early. Please refer to [link / reference]. Figure 1b , Figure 1b This application provides a mobility optimization scenario. Both base station 1 and base station 2 are configured with parameters for performing Mobility Optimization (MRO). Since premature handover might occur before the terminal device reaches the normal handover area, resulting in poor signal reception in the target cell, performing MRO can involve reducing the cell individual offset (CIO) to delay the handover.

[0096] With the evolution of networks, two new communication scenarios have been introduced under the New Radio (NR) system. One scenario is the transmission of data across multiple links, and the other is the successful handover of terminal devices between network devices.

[0097] Please see Figure 2a , Figure 2a This application provides a scenario for multi-link data transmission. The multi-link data transmission scenario may include a first network device, a second network device, and a terminal device. Figure 2a The example shown only depicts a scenario with a first network device, a second network device, and a terminal device. It is merely an example and is not intended to be limiting.

[0098] In this scenario, the terminal device can simultaneously maintain communication connections with both the first network device and the second network device, and can send and receive data. This scenario can be called a dual connectivity (DC) scenario. The first network device, referred to as the master node (MN), is responsible for exchanging radio resource control messages with the terminal device and for interacting with core network control plane entities. The network device other than the first network device, i.e., the second network device, can be called a secondary node (SN).

[0099] Similarly, if a terminal device can simultaneously maintain communication connections with a first network device and multiple second network devices and send and receive data, this scenario can be called a multi-connectivity (MC) scenario. Among the multiple network devices, the first network device can act as the MN, responsible for exchanging radio resource control messages with the terminal device and interacting with the core network control plane entities. The remaining multiple second network devices can all act as SNs.

[0100] The first network device can be an LTE-based master base station (e.g., MeNB) or an NR-based master base station (e.g., MgNB). The first network device can also be a master node (MN) in a dual-link architecture or an MN in a multi-link architecture; this embodiment does not impose any limitations.

[0101] The second network device can be an LTE-based secondary base station (e.g., SeNB) or an NR-based secondary base station (e.g., SgNB). The second network device can also be a secondary node (SN) under a DC architecture or an SN under an MC architecture; this embodiment does not limit the specific type of network device.

[0102] However, in scenarios involving multiple data transmission links, secondary cell radio link failures may occur due to changes in the serial number (SN). For example, failures can result from SN changes occurring too early, too late, or to the wrong cell.

[0103] Please see Figure 2b , Figure 2b This illustration shows a scenario where a terminal device fails to hand over between secondary base stations in a multi-link data transmission scenario provided by an embodiment of this application. The scenario involves a secondary base station being changed too early, potentially leading to premature handover of the secondary cell and consequently, failure of the secondary cell's radio link. Figure 2b As shown in the diagram. In this scenario, the terminal device experiences a radio link failure under the S-SN. Since the SN is the secondary base station, this is also referred to as a secondary cell group failure (SCG failure).

[0104] Please see Figure 3 , Figure 3 This application provides a scenario of near radio link failure in a successful handover situation. Near-RLF refers to a situation where, although the terminal device has successfully handed over between network devices, the radio link between the terminal device and the network device is unstable and may disconnect at any time, such as... Figure 3 As shown.

[0105] To address the wireless link issues in the aforementioned multi-link data transmission scenarios and successful handover scenarios, this application provides a mobility parameter configuration method. The mobility optimization attributes provided by this method indicate the attributes configured by the second network management device in the case of secondary cell wireless link failure and / or near wireless link failure, thereby achieving MRO optimization in the NR system under the above two scenarios.

[0106] The mobility parameter configuration method provided in this application embodiment can be applied to, for example, Figure 4 The communication system shown. Please refer to [link / reference]. Figure 4 , Figure 4 A communication system provided in this application includes a first network management device and a second network management device. Optionally, the communication system may further include a first network device, a second network device, and a terminal device. The first and second network devices are devices in an access network (such as base stations) used to communicate with the terminal device. The terminal device can switch between the first and second network devices to achieve seamless switching.

[0107] In this embodiment, both the first network management device and the second network management device are management entities defined by 3GPP. That is, the mobility parameter configuration method provided in this application can be applied to the NR network management architecture.

[0108] In the service-oriented management architecture defined by 3GPP, the externally visible behaviors and interfaces of management entities are defined as management services. In this service-oriented management architecture, management functions (MnFs) act as either management service producers (MnS producers) or management service consumers (MnS consumers). This service-oriented management architecture focuses on management service providers and consumers; the management service provider can also be referred to as a management service producer.

[0109] Please see Figure 5 , Figure 5 This is a schematic diagram of a service-oriented management architecture provided in an embodiment of this application. The service-oriented management architecture includes a business support system (BSS), a cross-domain management function (CD-MnF), a domain management function (Domain-MnF), and network elements.

[0110] If the management service is a management service provided by the cross-domain management functional unit, then the cross-domain management functional unit is the management service producer, and the business support system is the management service consumer.

[0111] If the management service is a management service provided by a domain management function unit, then the domain management function unit is the management service producer, and the cross-domain management function unit is the management service consumer.

[0112] When the management service is a management service provided by the network element, the network element is the management service producer, and the domain management functional unit is the management service consumer.

[0113] A business support system (BSS) is oriented towards communication services, providing functions and management services such as billing, settlement, accounting, customer service, sales, network monitoring, communication service lifecycle management, and service intent translation. The BSS can be an operator's operating system or a vertical OT system.

[0114] A cross-domain management function unit, also called a network management function (NMF), can be a network management system (NMS) or a network function management service consumer (NFMS_C), among other network management entities. The cross-domain management function unit provides one or more of the following management functions or services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization, and translation of network intents from communication service providers (Intent-CSPs).

[0115] The network referred to in the aforementioned management functions or services may include one or more network elements or sub-networks, or it may be a network slice. That is to say, the network management function unit may be a network slice management function (NSMF), a management data analytical function (MDAF), a self-organization network function (SON Function), or an intent-driven management service (Intent Driven MnS).

[0116] Optionally, in certain deployment scenarios, the cross-domain management function unit can also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, and translation of network intents (Intent-CSP) from service producers or network intents (intent from communication service consumer, Intent-CSC) from service consumers in the sub-network. Here, a sub-network consists of multiple smaller sub-networks, which can be network slice sub-networks.

[0117] The domain management function (MnF), also known as the network management function (NMF) or network element management function, can be various network element management entities, such as the wireless automation engine (MAE), the element management system (EMS), or the network function management service provider (NFMS_P).

[0118] The domain management function unit provides one or more of the following functions or management services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, optimization functions of subnetworks or network elements, and translation of intents from network operators (Intent-NOPs) of subnetworks or network elements. Here, a subnetwork includes one or more network elements. A subnetwork can also include other subnetworks, meaning one or more subnetworks can form a larger subnetwork.

[0119] Optionally, the subnet here can also be a network slice subnet. The domain management system can be a network slice subnet management function (NSSMF), a management data analytical function (Domain MDAF), a self-organizing network function (SON Function), an IntentDriven MnS, etc.

[0120] The domain management functional units can be classified as follows:

[0121] Based on network type, domain management functions can be categorized into: Radio Access Network Domain Management Function (RAN-Domain-MnF), Core Network Domain Management Function (CN-Domain-MnF), and Transport Network Domain Management Function (TN-Domain-MnF). It's important to note that a domain management function unit can also be a domain network management system, capable of managing one or more of the access network, core network, or transport network.

[0122] According to administrative regions, they can be classified as: regional management functional units of a certain area, such as Shanghai regional management functional unit, Beijing regional management functional unit, etc.

[0123] Network elements are entities that provide network services, including core network elements and access network elements. Core network elements include: access and mobility management function (AMF), session management function (SMF), policy control function (PCF), network data analytical function (NWDAF), network repository function (NRF), and gateways. Access network elements include: base stations (such as gNB, eNB), central unit control plane (CUCP), central unit (CU), distribution unit (DU), and central unit user plane (CUUP).

[0124] Among them, network elements can provide one or more of the following management functions or services: network element lifecycle management, network element deployment, network element fault management, network element performance management, network element assurance, network element optimization functions, and network element intent translation, etc.

[0125] The following description will be based on specific embodiments.

[0126] Please see Figure 6 , Figure 6This is a flowchart illustrating a mobility parameter configuration method provided in an embodiment of this application. Figure 6 The mobility parameter configuration method is implemented through interaction between a first network management device and a second network management device. For ease of understanding, the first network management device described in this embodiment can be... Figure 5 In the cross-domain management functional unit (such as NMS), the second network management device can be Figure 5 Domain management functional units (such as EMS) within a system. This method may include the following steps:

[0127] S601, the first network management device determines mobility optimization attributes, which are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure. The first network management device, as a management service consumer, determines mobility optimization attributes (MRO attributes). In this embodiment, in addition to determining conventional mobility optimization attributes, the first network management device can also determine corresponding mobility optimization attributes for secondary cell radio link failure in multi-link data transmission scenarios and for impending radio link failure in successful handover scenarios, thereby achieving MRO optimization in these two scenarios.

[0128] It should be noted that the mobility optimization attribute is a parameter for the Mobility Robustness Optimization (MRO) function. The MRO function can be implemented on one or more nodes such as base stations, cells, base station CU, base station DU, cells on base station CU, cells on base station DU, or sub-network management nodes. This embodiment does not limit this, and its main purpose is to optimize the mobility of the terminal.

[0129] The mobility optimization attribute determined by the first network management device is the mobility optimization attribute of the network node. The network node can be one or more of the following: cell, base station, base station CU, base station DU, cell on base station CU, and cell on base station DU. This embodiment does not limit the type of network node.

[0130] It should be noted that the MRO optimization described in this application includes the optimization of mobility parameters (e.g., cell-specific paranoid CIO) in scenarios where the secondary cell radio link fails due to early or late SN replacement or ping-pong scenarios, as well as the optimization of mobility parameters, beam parameters (e.g., Qin and Qout of beam detection), radio link monitoring parameters (e.g., radio link timestamps T310 and T312, number of radio link control RLC retransmissions, etc.), and random access resources (e.g., random access resources of the beam, downlink signal strength threshold of the beam, downlink signal strength threshold of the supplementary carrier, etc.) in scenarios where the handover is successful but the radio link is on the verge of failure.

[0131] The following is a detailed description of the cell-level mobility optimization attributes corresponding to cell-level optimization.

[0132] Cell-level mobility optimization attributes may include one or more of a first policy parameter, a first target parameter, and a first control parameter. The first policy parameter includes policies corresponding to secondary cell radio link failures in multi-link data transmission scenarios and near-failure radio link failures in successful handover scenarios. The secondary cell radio link failure scenario in multi-link data transmission scenarios can be referenced... Figure 2b The corresponding descriptions and scenarios where the wireless link is on the verge of failure after a successful handover can be found in the following references. Figure 3 And the corresponding descriptions, which will not be repeated here.

[0133] The first strategy parameter may include one or more of the following: cell local ID, handover triggering limit parameters, handover adjustment strategy parameters, optimization period, or handover optimization strategy parameters.

[0134] The cell identifier is used to indicate the cell for which mobility optimization attributes are to be configured. The cell identifier can be one or more of the following: physical cell identity (PCI), cell global identity (CGI), cell name, or cell ID; this embodiment does not limit this. For example, if the cell identifier in the first policy parameter is cell 1 (PCI 1), it means that the first network management device has determined the mobility optimization attributes of cell 1.

[0135] The handover trigger limiting parameters include one or more of the following: maximum handover trigger deviation, minimum handover trigger change time, maximum SN change trigger deviation, and minimum SN change trigger change time. This embodiment does not limit these parameters.

[0136] The maximum handover trigger deviation represents the maximum deviation of the handover trigger parameters, which is the maximum adjustment value of the cell-specific offset (CIO), for example, a maximum adjustment value of 10dB. The higher the CIO value of this cell, the less likely the user is to hand over to a neighboring cell. For example, if it is necessary to reduce late handovers, the CIO value of this cell can be reduced, and the degree of reduction can be referred to the maximum handover trigger deviation described in this embodiment.

[0137] The minimum handover trigger change time represents the minimum time required to update the handover trigger parameters, which is also the minimum adjustment time for the CIO. In other words, the minimum handover trigger change time represents the minimum time interval between two handover trigger parameter updates, and is used to control the stability and convergence of the MRO algorithm.

[0138] The maximum SN change trigger deviation represents the maximum deviation of the trigger parameters for SN change, which is the maximum adjustment value of the CIO for SN change, for example, the maximum adjustment value is 10dB. For example, if it is necessary to reduce the delay in SN change, the CIO of the SN or the cells under the SN can be adjusted to reduce the CIO value of the SN or the cells under the SN. The degree of reduction is referred to the maximum SN change trigger deviation described in this embodiment. By determining the maximum SN change trigger deviation, the first network management device can help avoid situations such as SN change too early, SN change too late, and SN change to the wrong cell, thereby avoiding radio link problems in the secondary cell caused by the SN change.

[0139] It should be noted that SN replacement here is SN handover, or secondary cell handover between SNs, or secondary cell handover, that is, the UE handover between secondary cells.

[0140] The minimum SN replacement trigger change time represents the minimum time for updating the SN replacement trigger parameters, which is also the minimum CIO adjustment time for SN replacement. In other words, the minimum SN replacement trigger change time represents the minimum time interval between two SN replacement trigger parameter updates. The minimum SN replacement trigger change time is used to control the stability and convergence of the SN replacement MRO algorithm.

[0141] The handover adjustment strategy parameters include one or more of the following: cell-specific offset (CIO) adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. Cell-specific offset (CIO) adjustment parameters include, for example, maximum CIO adjustment range for same-frequency MRO, minimum CIO adjustment range for same-frequency MRO, maximum CIO adjustment range for different-frequency MRO, and minimum CIO adjustment range for different-frequency MRO. Beam parameters include, for example, maximum / minimum values ​​of beam detection Qin and Qout. Radio link monitoring parameters include, for example, maximum / minimum values ​​of radio link monitoring timestamps T310 and T312, and maximum / minimum values ​​of radio link control (RLC) retransmission counts. Random access resource parameters include, for example, maximum / minimum values ​​of beam downlink signal strength thresholds (such as RSRP Threshold SSB and RSRP Threshold CSIRS) and downlink signal strength thresholds for supplementary carriers (such as RSRP Threshold SSB-SUL).

[0142] Among them, the maximum value of the CIO adjustment range for same-frequency MRO represents the maximum value of CIO adjustment optimized by same-frequency MRO, and the minimum value of the CIO adjustment range for same-frequency MRO represents the minimum value of CIO adjustment optimized by same-frequency MRO. In other words, the maximum value of the CIO adjustment range for same-frequency MRO and the minimum value of the CIO adjustment range for same-frequency MRO define the adjustment range of CIO during same-frequency handover.

[0143] For example, the first network management device can determine that the maximum value for CIO adjustment in the same-frequency MRO optimization is 5dB, and the minimum value is -5dB. Correspondingly, when adjusting the CIO, the first or second network device can adjust the CIO within the range of -5dB to 5dB.

[0144] Wherein, the maximum value of the CIO adjustment range (inter-frequency MRO) represents the maximum value of the CIO adjustment optimized by the inter-frequency MRO, and the minimum value of the CIO adjustment range (inter-frequency MRO) represents the minimum value of the CIO adjustment optimized by the inter-frequency MRO. In other words, the maximum value and minimum value of the CIO adjustment range (inter-frequency MRO) define the adjustment range of CIO during inter-frequency handover.

[0145] For example, the first network management device can determine that the maximum value for the CIO adjustment in inter-frequency MRO optimization is 10dB, and the minimum value is -10dB. Correspondingly, when adjusting the CIO, the first or second network device can adjust the CIO within the range of -10dB to 10dB.

[0146] The MRO optimization cycle indicates the frequency of MRO statistics and optimization. In other words, the MRO optimization cycle indicates how often the first or second network device performs MRO statistics and optimization.

[0147] The handover optimization strategy parameters include one or more parameters such as the optimization trigger threshold corresponding to secondary cell radio link failure and the optimization trigger threshold corresponding to near radio link failure. Specifically, the handover optimization strategy parameters include one or more parameters such as the abnormal handover ratio threshold, the early handover optimization ratio threshold, the late handover optimization ratio threshold, the abnormal SN replacement ratio threshold, the early SN replacement optimization ratio threshold, the late SN replacement optimization ratio threshold, the ping-pong ratio threshold, the SN replacement ping-pong ratio threshold, the near-RLF ratio threshold, and the beam failure ratio threshold.

[0148] Abnormal handover includes handovers that are too early and handovers that are too late. The abnormal handover ratio can be expressed as the ratio of the sum of the number of early handovers and the number of late handovers to the total number of handovers, i.e., Abnormal handover ratio = (Number of early handovers + Number of late handovers) / Total number of handovers. The abnormal handover ratio threshold limits the maximum value of the abnormal handover ratio. In other words, if the abnormal handover ratio of the system exceeds the abnormal handover ratio threshold, MRO optimization is triggered.

[0149] The premature switch optimization ratio threshold limits the maximum value of the premature switch ratio. In other words, if the system's premature switch ratio exceeds this premature switch optimization ratio threshold, MRO optimization is triggered.

[0150] The late-switching optimization ratio threshold limits the maximum value of the late-switching ratio. In other words, if the late-switching ratio of the system exceeds this late-switching optimization ratio threshold, MRO optimization is triggered.

[0151] Abnormal SN switching includes both premature and delayed SN switching. The abnormal SN switching ratio can be expressed as the ratio of the sum of premature and delayed SN switching counts to the total number of SN switching counts, i.e., Abnormal SN Switching Ratio = (Premature SN Switching Count + Delayed SN Switching Count) / Total SN Switching Count. An abnormal SN switching ratio threshold limits the maximum value of this ratio. In other words, if the system's abnormal SN switching ratio exceeds this threshold, MRO optimization is triggered.

[0152] The premature SN replacement optimization ratio threshold limits the maximum value of the premature SN replacement ratio. In other words, if the premature SN replacement ratio of the system exceeds this premature SN replacement optimization ratio threshold, MRO optimization is triggered.

[0153] The late SN replacement optimization ratio threshold limits the maximum value of the late SN replacement ratio. In other words, if the late SN replacement ratio of the system exceeds this late SN replacement optimization ratio threshold, MRO optimization is triggered.

[0154] Understandably, the aforementioned abnormal SN replacement ratio threshold, SN replacement too early optimization ratio threshold, and SN replacement too late optimization ratio threshold are mainly aimed at the problem of secondary cell radio link failure caused by SN changes in multi-link data transmission scenarios. By determining the above three types of MRO attributes, it is beneficial to reduce the probability of secondary cell radio link failure caused by SN replacement too early or too late.

[0155] The ping-pong ratio threshold limits the maximum value of the ping-pong switching ratio. The ping-pong switching ratio is the ratio of the number of ping-pong switching to the total number of switching, i.e., ping-pong switching ratio = number of ping-pong switching / total number of switching. In other words, if the system's ping-pong switching ratio exceeds this threshold, MRO optimization is triggered.

[0156] The SN switching ratio threshold limits the maximum value of the SN switching ratio. The SN switching ratio is the ratio of the number of SN switching operations to the total number of SN switching operations, i.e., SN switching ratio = number of SN switching operations / total number of SN switching operations. In other words, if the system's SN switching ratio exceeds this threshold, MRO optimization is triggered.

[0157] The near-RLF ratio threshold limits the maximum value of the near-RLF ratio. The near-RLF ratio is the ratio of the number of near-link failures to the number of successful handovers, i.e., near-RLF ratio = number of near-link failures / number of successful handovers. In other words, in a successful handover scenario, if the near-RLF ratio reaches this near-RLF ratio threshold, MRO optimization is triggered.

[0158] The beam failure ratio threshold limits the maximum value of the beam failure ratio. The beam failure ratio is the ratio of the number of beam failures to the number of successful handovers, i.e., beam failure ratio = number of beam failures / number of successful handovers. In other words, in a successful handover scenario, if the beam failure ratio reaches this threshold, MRO optimization is triggered. The first target parameter may include one or more parameters such as cell identifier, maximum number of handover triggers, and handover trigger optimization target parameters. This first target parameter can be understood as the expected or required goal of MRO.

[0159] The cell identifier is used to indicate the cell for which mobility optimization attributes are to be configured. In other words, the cell identifier indicates the cell for which the desired or required goal is to be achieved. For a detailed description of the cell identifier, please refer to the description in the preceding embodiments; it will not be repeated here.

[0160] The maximum number of handover triggers is used to limit the number of times the handover trigger parameters can be changed. In order to improve the convergence of the algorithm, the number of handover trigger changes for a cell cannot be too many, that is, it cannot exceed the maximum number of handover triggers.

[0161] For example, if the ping-pong handover ratio in cell 1 exceeds the ping-pong ratio threshold frequently, MRO optimization will be triggered each time it exceeds the threshold. However, if the number of handovers triggering MRO optimization is too high, it may lead to a significant increase in system management overhead. Therefore, the number of times MRO optimization is triggered needs to be limited to not exceeding the maximum number of handover triggers.

[0162] The target parameters for handover trigger optimization include the proportion of abnormal RLFs, the proportion of ping-pong handovers, the failure rate of handovers that are too early, the call drop rate of handovers that are too late, the failure rate of abnormal SCGs, and the failure rate of SNs that are too early or too late.

[0163] Abnormal RLF includes RLF caused by premature handover and RLF caused by premature handover. The abnormal RLF ratio can be expressed as the ratio of the sum of RLF caused by premature handover and RLF caused by premature handover to the total number of handovers, i.e., Abnormal RLF ratio = (RLF caused by premature handover + RLF caused by premature handover) / Total number of handovers. This abnormal RLF ratio is the optimization target of MRO; that is, MRO optimization helps to reduce the abnormal RLF ratio.

[0164] The ping-pong handover ratio is the ratio of the number of ping-pong handovers to the total number of handovers, i.e., ping-pong handover ratio = number of ping-pong handovers / total number of handovers. This ping-pong handover ratio is the optimization target of MRO (Maintenance, Repair, and Overhaul). In other words, MRO optimization helps to reduce the ping-pong handover ratio.

[0165] The premature handover failure rate is the ratio of the number of premature handovers to the total number of handovers, i.e., premature handover failure rate = number of premature handovers / total number of handovers. In other words, the premature handover failure rate is the optimization target of MRO (Maintenance, Repair, and Overhaul). Therefore, MRO optimization helps to reduce the premature handover failure rate.

[0166] The late handover drop rate is the ratio of the number of late handovers to the total number of handovers, i.e., Late handover drop rate = Number of late handovers / Total number of handovers. This late handover drop rate is the optimization target of MRO (Maintenance, Repair, and Operations). In other words, MRO optimization helps to reduce the late handover drop rate.

[0167] Abnormal SCG failures include SCG failures caused by premature SN replacement and SCG failures caused by premature SN replacement. The abnormal SCG failure ratio can be expressed as the ratio of the sum of SCG failures caused by premature SN replacement and SCG failures caused by premature SN replacement to the total number of handovers, i.e., Abnormal SCG failure ratio = (SCG failures caused by premature SN replacement + SCG failures caused by premature SN replacement) / Total number of handovers. This abnormal SCG failure ratio is the optimization target for MRO (Maintenance, Repair, and Overhaul). In other words, optimizing MRO through SN replacement helps reduce the abnormal SCG failure ratio.

[0168] The premature failure rate of SN replacement is the ratio of the number of premature SN replacements to the total number of SN replacements, i.e., premature SN replacement failure rate = number of premature SN replacements / total number of SN replacements. In other words, the premature failure rate of SN replacement is the optimization target of MRO for SN replacement. That is to say, through MRO optimization, it is beneficial to reduce the premature failure rate of SN replacement.

[0169] The late SN change call drop rate is the ratio of the number of late SN changes to the total number of SN changes, i.e., Late SN Change Call Drop Rate = Number of Late SN Changes / Total Number of SN Changes. This Late SN Change Call Drop Rate is the optimization target of MRO for SN changes. In other words, MRO optimization helps to reduce the Late SN Change Call Drop Rate.

[0170] The first control parameter is also called the control switch for the MRO function. In this application embodiment, two types of control switches are added to the existing MRO function control switches, including the mobility optimization function control switch for secondary cell radio link failure and the mobility optimization function control switch for near radio link failure.

[0171] In this embodiment, both the mobility optimization function control switch for secondary cell radio link failure and the mobility optimization function control switch for near radio link failure can be of Boolean data type. For example, "on" indicates that the mobility optimization function for secondary cell radio link failure is enabled, and "off" indicates that the mobility optimization function for secondary cell radio link failure is disabled. Alternatively, "on" indicates that the mobility optimization function for near radio link failure is enabled, and "off" indicates that the mobility optimization function for near radio link failure is disabled. Optionally, the control switch for this MRO function can also be of enumeration data type, such as "yes" or "no," or other data types that can represent switches; this embodiment does not limit this.

[0172] The mobility optimization function control switch for secondary cell radio link failure, also known as the MR-DC MRO function switch or SN Change MRO function switch, is used to control the base station to perform MRO optimization when SN change failure occurs. For example, in an MR-DC scenario, the base station can detect the number of premature SN changes, the number of late SN changes, and the total number of handovers. If SN change failure occurs, such as a large number of premature SN changes, the MR-DC MRO function switch activates the MRO function. When the MR-DC MRO function switch controls the MRO function to be active and the system meets the MRO triggering conditions, MRO optimization is triggered, such as modifying handover parameters.

[0173] The mobility optimization function control switch for near-radio link failure, also known as the successful handover optimization function switch, is used to control the base station to perform MRO optimization when mobility issues arise in a successful handover scenario involving near-radio link failure. For example, in a successful handover scenario, the base station can detect the number of near-RLF links. If the number of near-RLF links is large, the successful handover optimization function switch will activate the MRO function, triggering MRO optimization.

[0174] The following section provides a detailed description of the base station-level mobility optimization attributes corresponding to base station-level optimizations.

[0175] For base station-level mobility optimization attributes, these may include second policy parameters, second target parameters, and second control parameters, etc.

[0176] The second policy parameters include policies for secondary cell radio link failures in multi-link data transmission scenarios, and for near-failure radio link failures in successful handover scenarios. Specifically, the second policy parameters may include: network device identifier, abnormal coverage policy parameters, and abnormal radio link policy parameters.

[0177] The network device identifier can be a base station identifier (base station ID) or a base station name, used to indicate different network devices (such as base stations, etc.), and this embodiment does not limit it. For example, if the base station identifier in the second policy parameter is base station 1 (base station ID 1), then it means that the first network management device has determined the mobility optimization attributes of base station 1.

[0178] The abnormal coverage strategy parameters include one or more parameters such as the abnormal coverage threshold, the reference signal receiving power (RSRP) threshold of the serving cell, and the reference signal receiving power threshold of neighboring cells. This embodiment does not limit these parameters.

[0179] The abnormal coverage threshold represents the maximum percentage of abnormal coverage between the serving cell and neighboring cells within a MRO optimization cycle. If the percentage of abnormal coverage between the serving cell and neighboring cells exceeds this threshold within an MRO optimization cycle, MRO is not triggered. In other words, since the abnormal coverage threshold indicates coverage performance rather than mobility performance, even if the percentage of abnormal coverage exceeds this threshold, mobility performance optimization will not be triggered, i.e., MRO optimization will not be triggered.

[0180] The reference signal received power threshold for the serving cell indicates that when a terminal device experiences an RLF (Recurrent Link Failure) or handover failure, if the RSRP (Receiving Power Count) value of the serving cell in the successfully rebuilt RLF report is less than this threshold, and the RSRP values ​​of neighboring cells are also less than this threshold, then abnormal coverage is considered to exist. In other words, the reference signal received power threshold of the serving cell can indicate whether abnormal coverage exists. Optionally, if the reference signal received power threshold of the serving cell indicates abnormal coverage, and the abnormal coverage ratio exceeds the abnormal coverage threshold, then MRO (Maintenance, Repair, and Overhaul) optimization is not triggered.

[0181] The reference signal received power threshold for neighboring cells indicates that when a terminal device experiences an RLF (Recurrent Link Request) or handover failure, if the RSRP (Receiving Signal Received Power) value of the serving cell in the successfully rebuilt RLF report is less than this threshold, and the RSRP of neighboring cells is also less than this threshold, then abnormal coverage is considered to exist. In other words, the reference signal received power threshold for neighboring cells can indicate whether abnormal coverage exists. Optionally, if the reference signal received power threshold for neighboring cells indicates abnormal coverage, and the abnormal coverage ratio exceeds the abnormal coverage threshold, then MRO (Maintenance, Repair, and Operations) optimization is not triggered.

[0182] Abnormal wireless link policy parameters include one or more parameters such as abnormal wireless link failure ratio threshold, network device group handover failure ratio threshold, and near-wireless link failure ratio threshold.

[0183] Abnormal radio link failures, also known as abnormal RLFs, include abnormal RLFs caused by premature handovers and abnormal RLFs caused by late handovers. The abnormal RLF ratio can be expressed as the ratio of the sum of abnormal RLFs caused by premature handovers and abnormal RLFs caused by late handovers to the total number of handovers, i.e., Abnormal RLF ratio = (Number of abnormal RLFs caused by premature handovers + Number of abnormal RLFs caused by late handovers) / Total number of handovers. If the system's abnormal RLF ratio exceeds this threshold, MRO optimization is triggered.

[0184] Network device group handover failures, also known as abnormal SCG failures, include SCG failures caused by premature SN replacement and SCG failures caused by premature SN replacement. The abnormal SCG failure ratio can be expressed as the ratio of the sum of SCG failures caused by premature SN replacement and SCG failures caused by premature SN replacement to the total number of handovers, i.e., Abnormal SCG failure ratio = (Number of SCG failures caused by premature SN replacement + Number of SCG failures caused by premature SN replacement) / Total number of handovers. If the system's abnormal SCG failure ratio exceeds this threshold, MRO optimization is triggered.

[0185] The near-RLF ratio, also known as the near-RLF ratio, can be expressed as the ratio of near-RLF failures to successful handovers, i.e., near-RLF ratio = near-RLF failures / successful handovers. The near-RLF ratio threshold limits the maximum value of the near-RLF ratio. In other words, in a successful handover scenario, if the near-RLF ratio reaches this threshold, MRO optimization is triggered.

[0186] It should be noted that the second strategy parameter may also include the first strategy parameter in the cell-level mobility optimization attributes described in the previous embodiments. That is, the second strategy parameter may also include one or more parameters such as cell identifier, handover trigger limitation parameter, handover adjustment strategy parameter, optimization period, or handover optimization strategy parameter. For a description of each parameter, please refer to the description in the previous embodiments, which will not be repeated here.

[0187] The second target parameter may include one or more parameters such as network device identifier, abnormal coverage ratio, and handover trigger optimization target parameter. The description and function of the network device identifier are the same as those in the second policy parameter, and will not be repeated here.

[0188] The abnormal coverage ratio represents the proportion of abnormal coverage between the serving cell and neighboring cells within a MRO optimization cycle. For example, the ratio of the overlapping coverage area between the serving cell and neighboring cells to the sum of the coverage areas formed by the serving cell and neighboring cells can reflect the abnormal coverage ratio between the serving cell and neighboring cells. The overlapping coverage area between the serving cell and neighboring cells can be considered as the abnormal coverage area.

[0189] The target parameters for switching trigger optimization include one or more parameters such as the abnormal RLF ratio, the abnormal SCG failure ratio, and the near-RLF ratio. The descriptions of the abnormal RLF ratio and the abnormal SCG failure ratio can be found in the detailed description of the first target parameter in the previous embodiment, and will not be repeated here.

[0190] The near-RLF ratio can be expressed as the ratio of near-RLF occurrences to successful handovers, i.e., near-RLF ratio = near-RLF occurrences / successful handovers. This near-RLF ratio is the optimization target for MRO (Maintenance, Repair, and Operations). In other words, MRO optimization helps to reduce the near-RLF ratio.

[0191] The second control parameter, also known as the control switch for the MRO function, adds two types of control switches to the existing MRO function control switches in this application embodiment: a mobility optimization function control switch for secondary cell radio link failure and a mobility optimization function control switch for near radio link failure. Detailed descriptions of these two types of switches can be found in the detailed description of the first control parameter, and will not be repeated here.

[0192] Optionally, the MRO optimization described in this embodiment can also be a subnet-level optimization. The subnet-level mobility optimization attributes corresponding to the subnet-level optimization are the same as the base station-level mobility optimization attributes. For a detailed description, please refer to the description of the base station-level mobility optimization attributes, which will not be repeated here.

[0193] S602, the first network management device sends mobility optimization attributes to the second network management device; correspondingly, the second network management device receives the mobility optimization attributes sent by the first network management device.

[0194] After determining the mobility optimization attribute, the first network management device can send the mobility optimization attribute to the second network management device. For example, the first network management device sends network node information, including the mobility optimization attribute, to the second network management device via the northbound interface. The network node can be a network function node, such as a base station, cell, base station CU, base station DU, base station CU cell, or base station DU cell, etc.

[0195] Optionally, the first network management device sends one or more of the cell identifier information, base station identifier information, and slice identifier information to the second network management device.

[0196] Optionally, the second network management device receives an object creation notification from the first network management device, which carries mobility optimization attributes of the network node. The second network management device then creates a management object for the network node instance based on the received object creation notification. The network node can be a network function node, such as a base station, cell, base station CU, base station DU, base station CU cell, or base station DU cell, etc. The second network management device configures the mobility optimization attributes in the management object of the network node.

[0197] The object creation notification is used to enable the first network management device to create corresponding management objects and configure them accordingly. Optionally, the object creation notification may also include one or more of a base station identifier, a cell identifier, or a slice identifier, which are used to indicate whether the mobility optimization attribute is at the base station, cell, or slice level, respectively.

[0198] For example, a management service consumer sends a `create MOI` operation to a management service producer, carrying attributes related to mobility optimization functionality. After the operation is created, the management service consumer can send a `get MOI Attributes` operation to the management service producer to actively retrieve the configuration parameters of a specific object. Alternatively, the management service consumer can send a `modify MOI Attributes` operation to the management service producer to modify the parameters of a specific object. Or, the management service consumer can send a `delete MOI Attributes` operation to the management service producer to delete a specific object. These operations can utilize existing operation messages or newly defined operation messages; this embodiment does not impose limitations.

[0199] Optionally, after receiving the mobility optimization attribute from the object creation notification sent by the first network management device, the second network management device may also send the mobility optimization attribute to the second network device, so that the second network device can adjust the handover parameters of the terminal device during the handover process from the first network device to the second network device according to the mobility optimization attribute in the event of secondary cell radio link failure and / or impending radio link failure.

[0200] Specifically, the second network management device can send the mobility optimization attribute to the second network device through a private interface between the second network management device and the second network device.

[0201] For example, a managed service consumer determines mobility optimization attributes and sends these attributes to managed base stations 1 and 2 through a managed service producer. Base stations 1 and 2 then configure corresponding parameters based on the received mobility optimization attributes. If a terminal device successfully hands over from base station 1 to base station 2, but the near-RLF ratio exceeds the near-RLF ratio threshold in the mobility optimization attribute, then base station 2 triggers MRO optimization, adjusting mobility parameters, beam parameters, etc.

[0202] Optionally, the interaction between the first network management device and the second network management device in this embodiment may further include the following steps:

[0203] S603, the first network management device receives a response message sent by the second network management device; correspondingly, the second network management device sends a response message to the first network management device.

[0204] Specifically, the second network management device can perform corresponding configurations based on mobility optimization attributes. After configuration, the second network management device sends a response message to the first network management device.

[0205] Optionally, the response message can be an existing Create MOI response operation message or a newly defined operation message; this embodiment does not impose any limitations.

[0206] Optionally, the response message may carry the identifier of the managed object and / or the identifier of the second network management device. For example, it may carry a distinctive name (DN). The identifier of the managed object may be created by the first network management device and sent to the second network management device in the Create MOI request.

[0207] Optionally, the response message may also include one or more of the following: a configuration success message, a configuration failure message, or an information indicating that configuration is not possible. This embodiment does not impose any limitations on this. Correspondingly, the configuration status of the second network management device includes configuration success, configuration failure, or inability to configure. For example, if the mobility optimization attribute of the second network management device is configured successfully, then the response message sent by the second network management device to the first network management device will be a configuration success message.

[0208] Optionally, the response message may also include the reason for the configuration failure or inability to configure. For example, the response message sent by the second network management device to the first network management device may be a configuration failure message, and the response message may also include the reason for the configuration failure.

[0209] This application provides a mobility parameter configuration method, which can be interactively executed between a first network management device and a second network management device. The first network management device can send mobility optimization attributes to the second network management device. These mobility optimization attributes are used to indicate attributes configured in cases of secondary cell radio link failure and / or impending radio link failure. In other words, this method achieves mobility parameter optimization management in both multi-link data transmission scenarios and successful handover scenarios, ensuring mobility performance in these two scenarios.

[0210] The following section provides a detailed description of the management process for performance metrics between network management devices and network devices in multi-link data transmission scenarios and successful handover scenarios.

[0211] Please see Figure 7 , Figure 7 This application provides a schematic diagram illustrating a process for a first network management device and a second network management device to manage mobility optimization performance data. The process is implemented through interaction between the first network management device and the second network management device, and includes the following steps:

[0212] S701, the first network management device sends a request message to the second network management device. The request message is used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or to request an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0213] The request message sent by the first network management device to the second network management device may be a data subscription operation message, which is used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or to notify the mobility optimization performance data corresponding to the mobility optimization attribute.

[0214] The data subscription operation message may carry information about network nodes. This information can be from various network nodes such as base stations, cells, base stations (CUs), base stations (DUs), base station CU cells, or base station DU cells. This data subscription operation message is used to request mobility optimization performance data from network nodes and / or instructions regarding such data.

[0215] Optionally, the data subscription operation message may also carry slice identification information, such as NSSAI, S-NSSAI, NSSI, etc. This subscription operation is used to request mobility optimization performance data for a specified slice and / or an indication of the mobility optimization performance data for a specified slice.

[0216] For example, the first network management device sends a data subscription operation message for a network node to the second network management device. This data subscription operation carries a request for mobility optimization performance data from the network node. The network node can be a network function node, such as one or more of the following: a base station, a cell, a base station CU, a base station DU, a base station CU cell, or a base station DU cell.

[0217] Optionally, the data subscription operation message may also include the period for sending performance data, trigger thresholds, etc.

[0218] Optionally, the data subscription operation message may indicate specific mobility optimization performance data, such as one or more of the following: performance data related to multi-link data transmission and performance data related to successful handover. This embodiment does not limit this.

[0219] It should be noted that the data subscription operation message can be an existing subscribe operation message, or a new message can be defined; this embodiment does not impose any limitations.

[0220] S702, the first network management device receives feedback information sent by the second network management device.

[0221] The feedback information received by the first network device may include mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute in the event of secondary cell radio link failure and / or impending radio link failure. That is, the feedback information may include only specific performance data, only an indication of performance data, or both specific performance data and an indication of performance data.

[0222] In one implementation, the feedback information may include mobility optimization performance data corresponding to mobility optimization attributes in the event of secondary cell radio link failure and / or impending radio link failure.

[0223] The mobility optimization performance data corresponding to the mobility optimization attributes refers to the performance indicators of handover for network elements managed by the second network management device. This mobility optimization data may include, but is not limited to: the total number of handovers, the total number of handover failures, the total number of secondary node handovers, the total number of secondary node handover failures, the number of ping-pong effects, the number of secondary node updates that occurred too early, the number of secondary node updates that occurred too late, the number of secondary nodes handovers to the wrong cell, the number of secondary node ping-pong handovers, the number of near-radio link failures, or the number of beam failures, etc.

[0224] The total number of handover events refers to the number of handover events counted within one MRO optimization cycle, regardless of RAT. In other words, the total number of handover events can be the number of handover events occurring within the same system (intra-RAT handover events) or the number of handover events occurring between different systems (inter-RAT handover events).

[0225] It should be noted that intra-RAT refers to handover within the same standard, such as handover between LTE and LTE, or between NR and NR. inter-RAT refers to handover between different standards, such as handover between LTE and NR, or between eLTE and NR under the NG-RAN architecture. This embodiment does not limit the scope of inter-RAT.

[0226] The total number of handover failures refers to the number of handover failures counted within one MRO optimization cycle, regardless of RAT. In other words, the total number of handover failures can be the number of handover failures under intra-RAT or the number of handover failures under inter-RAT.

[0227] Optionally, the total number of handover failures can also be the number of inter-RAT too early handover failures, the number of intra-RAT too late handover failures, the number of intra-RAT handover failures to the wrong cell, the number of inter-RAT too early handover failures, the number of inter-RAT too late handover failures, or the number of unnecessary handovers to another RAT, etc.

[0228] To demonstrate the performance metrics of network elements configured with the MRO optimization attributes described in this application embodiment during handover, the following will introduce mobility optimization performance data for multi-link data transmission scenarios and mobility optimization performance data for successful handover scenarios. Specifically, this may include: the total number of secondary node handovers, the total number of secondary node handover failures, the number of times the ping-pong effect occurs, the number of times the secondary node updates too early, the number of times the secondary node updates too late, the number of times the secondary node switches to the wrong cell, or the number of times it is on the verge of radio link failure, etc.

[0229] The total number of secondary node switching events is the number of SN switching events counted within one MRO optimization cycle. Optionally, the total number of secondary node switching events can be either the total number of inter-RAT SN change events or the total number of intra-RAT SN change events.

[0230] The total number of secondary node switchover failures is the number of SN switchover failures counted within one MRO optimization cycle. Optionally, the total number of secondary node switchover failures can be either the total number of secondary node switches under inter-RAT or the total number of secondary node switches under intra-RAT.

[0231] The number of handover ping pongs is the number of handovers that occur within one MRO optimization cycle. Optionally, the number of handover ping pongs can be the number of handovers under inter-RAT or the number of handovers under intra-RAT.

[0232] The number of SN too early HO failures refers to the number of handover failures caused by premature SN updates within a single MRO optimization cycle. Optionally, the number of premature SN updates can be either the number of inter-RAT SN too early HO failures or the number of intra-RAT SN too early HO failures.

[0233] The number of late SN (Side Node) HO failures refers to the number of handover failures caused by late SN updates within a single MRO optimization cycle. Optionally, the number of late SN updates can be either the number of inter-RAT (Side Node) toolate HO failures or the number of intra-RAT (Side Node) too late HO failures.

[0234] The number of times the secondary node switches to the wrong cell is the number of times the SN switches to the wrong cell within one MRO optimization cycle. Optionally, the number of times the secondary node switches to the wrong cell can be the number of times the secondary node switches to the wrong cell under inter-RAT (number of inter-RAT SN to wrong cell) or the number of times the secondary node switches to the wrong cell under intra-RAT (number of intra-RAT SN to wrong cell).

[0235] The number of SN change ping pong handovers refers to the number of SN change ping pongs counted within one MRO optimization cycle. Optionally, the number of SN change ping pong handovers can be the number of inter-RAT SN change ping pongs or the number of intra-RAT SN change ping pongs.

[0236] The number of near-RLFs refers to the number of near-RLFs counted within one MRO optimization cycle. Optionally, the number of near-RLFs can be the number of near-RLFs under inter-RAT or the number of near-RLFs under intra-RAT.

[0237] The number of beam failures is the number of beam failures counted within one MRO optimization cycle.

[0238] In one implementation, the feedback information may not include the aforementioned performance data, but only include an indication of the mobility optimization performance data corresponding to the mobility optimization attribute (such as notify ready). For example, the feedback information may include notify ready, which could indicate the performance data requested by the request message.

[0239] The following two examples illustrate two processes for managing MRO performance metrics. One process involves a first network management device triggering a subscription to obtain mobility optimization performance data, with a second network management device reporting the data in file-based format. The other process involves a second network management device triggering a measurement task and reporting mobility optimization performance data, with the second device reporting the data in stream-based format.

[0240] In one example, see Figure 8 , Figure 8 This application provides a schematic diagram illustrating the process of managing MRO performance metrics using a first network management device and a second network management device. The process is implemented through interaction between the first and second network management devices and includes the following steps:

[0241] S801, the first network management device sends a subscription operation to the second network management device;

[0242] S802, the second network management device sends an indication message to the first network management device, the indication message being used to indicate that the file data is ready;

[0243] S803, the first network management device sends a request message to the second network management device, which is used to request the acquisition of available file data.

[0244] In this process, the subscription operation sent by the first network management device to the second network management device is used to subscribe to the MRO performance metrics of the second network management device. For example, the first network management device can obtain specific MRO performance metrics through this subscription operation.

[0245] The subscription operation may include information about network nodes. This information can be information about base stations, cells, base stations (CU), base stations (DU), CU cells, or DU cells. The subscription operation is used to request the transmission of mobility optimization performance data from network nodes and / or instructions regarding such data.

[0246] Optionally, the subscription operation may also carry slice identification information, such as NSSAI, S-NSSAI, NSSI, etc. This subscription operation is used to indicate a request for mobility optimization performance data for a specified slice and / or an indication of requesting mobility optimization performance data for a specified slice.

[0247] For example, the first network management device sends a subscription operation for a network node to the second network management device, the subscription operation carrying mobility optimization performance data of the network node. The network node can be a network function node, such as one or more of the following: base station, cell, base station CU, base station DU, base station CU cell, or base station DU cell.

[0248] Optionally, the subscription operation may also include the period for sending performance data, trigger thresholds, etc.

[0249] Optionally, the subscription operation may carry indications of specific MRO performance metrics. For example, a subscription operation sent by the first network management device to the second network management device may carry a first indication and / or a second indication. The first indication is used to indicate performance metrics related to multi-link data transmission (such as performance metrics related to SN change), and the second indication is used to indicate performance metrics related to successful handover (such as performance metrics related to near-RLF).

[0250] Optionally, the subscription operation can use existing subscribe operation messages or define new messages; this embodiment does not impose any limitations.

[0251] After receiving the subscription operation from the first network management device, the second network management device can collect relevant mobility optimization performance data and record it in files. The second network management device can send an indication message to the first network management device, indicating that the file data is ready. For example, the indication message sent by the second network management device can use an existing Notify Ready operation message, or a new message can be defined; this embodiment does not impose any limitations.

[0252] Optionally, the indication message (file ready operation) may carry an indication of a specific MRO performance metric being ready. For example, the indication message sent by the second network management device to the first network management device carries a first ready indication and / or a second ready indication. The first ready indication indicates that performance metrics related to multi-link data transmission (such as SN change-related performance metrics) are included in the file, and the second ready indication indicates that performance metrics related to successful handover (such as near-RLF-related performance metrics) are included in the file.

[0253] After receiving the instruction information, the first network management device can send a request message to the second network management device. This request message is used to request the acquisition of available file data. This request message can use the existing "list Available Files" operation message, or a new message can be defined; this embodiment does not impose any limitations.

[0254] In one example, see Figure 9 , Figure 9This application provides a schematic diagram illustrating another process for managing MRO performance metrics using a first network management device and a second network management device, as part of an embodiment of the present application. This process is implemented through interaction between the first network management device and the second network management device, and includes the following steps:

[0255] S901, the first network management device sends a measurement task creation operation to the second network management device;

[0256] S902, the second network management device sends a data stream connection establishment operation to the first network management device;

[0257] S903, the second network management device sends a data stream to the first network management device.

[0258] The measurement task is used to collect the same type of measurement for the same instance with different granularity periods. Subsequently, the first network management device can send a list of measurement tasks to the second network management device, so that the second network management device can establish the corresponding measurement task data stream.

[0259] Optionally, the measurement task creation operation can include network node information. This network node information can be information about a base station, cell, base station CU, base station DU, base station CU cell, or base station DU cell. This measurement task creation operation is used to request the creation of a measurement connection for mobility optimization performance data of the network node.

[0260] Optionally, the Create Measurement Task operation can also include slice identification information, such as NSSAI, S-NSSAI, NSSI, etc. The Create Measurement Task operation is used to request the creation of a measurement connection for mobility optimization performance data of a specified slice.

[0261] For example, the first network management device sends a network node creation measurement task operation to the second network management device, which carries mobility optimization performance data of the network node. The network node can be a network function node, such as one or more of the following: base station, cell, base station CU, base station DU, base station CU cell, or base station DU cell.

[0262] Optionally, the creation of a measurement task operation may also include the period for sending performance data, trigger thresholds, etc.

[0263] The measurement task operation can use the existing create measurement job operation message. The measurement task list can use the existing list measurement jobs operation message, the existing create MOI operation message, or other newly defined messages; this embodiment does not impose any limitations.

[0264] The data flow connection establishment operation is used to establish a data flow between the first network management device and the second network management device.

[0265] Optionally, the data stream connection establishment operation can carry a stream information list, which includes stream identifier, measurement management object DN information, etc.

[0266] Optionally, the data stream connection establishment operation can use the existing establish streaming connection operation message or define a new operation message; this embodiment does not impose any limitations.

[0267] Optionally, the data stream connection establishment operation may carry indications of specific MRO performance metrics. For example, the data stream connection establishment operation sent by the first network management device to the second network management device carries a first indication and a second indication. The first indication is used to indicate performance metrics related to multi-link data transmission (such as performance metrics related to SN change), and the second indication is used to indicate performance metrics related to successful handover (such as performance metrics related to near-RLF).

[0268] This application provides a management process for performance metrics between network management devices and network devices in multi-link data transmission scenarios and successful handover scenarios, solving the management of mobility optimization performance data in these scenarios. This management process allows the first network management device to adjust mobility optimization attributes based on mobility optimization performance data, thereby helping to reduce the handover failure rate for users.

[0269] The following combination Figures 10 to 13 The relevant devices in the embodiments of this application are described in detail.

[0270] This application provides a first network management device, such as... Figure 10 As shown, the first network management device 1000 can be used to implement the mobility parameter configuration method in the embodiments of this application. The first network management device 1000 may include:

[0271] Processing unit 1001 is used to determine mobility optimization attributes, which are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure.

[0272] The transceiver unit 1002 is used to send the mobility optimization attribute to the second network management device.

[0273] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of S601 and S602 in the embodiments will not be repeated here.

[0274] In one implementation, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger limit parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0275] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0276] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first strategy parameters in the embodiments will not be repeated here.

[0277] In one implementation, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio links, ping-pong handover count rate, premature handover failure rate, or late handover call drop rate.

[0278] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first target parameter in the embodiments will not be repeated here.

[0279] In one implementation, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0280] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first control parameter in the embodiments will not be repeated here.

[0281] In one implementation, the mobility optimization attribute includes a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter. The abnormal coverage policy parameter includes one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameter includes one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0282] For specific implementation details, please refer to [link / reference]. Figure 6The detailed description of the second strategy parameters in the embodiments will not be repeated here.

[0283] In one implementation, the mobility optimization attribute includes a second target parameter, which includes one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization target parameter. The handover-triggered optimization target parameter includes one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0284] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second target parameter in the embodiments will not be repeated here.

[0285] In one implementation, the mobility optimization attribute includes one or more of a first policy parameter, a first target parameter, a first control parameter, a second policy parameter, or a second target parameter.

[0286] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of the first strategy parameter, first target parameter, first control parameter, second strategy parameter, and second target parameter in the embodiments will not be repeated here.

[0287] In one implementation, the transceiver unit 1002 is further configured to receive a response message sent by the second network management device, the response message indicating the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0288] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of S603 in the embodiment will not be repeated here.

[0289] In one implementation, the transceiver unit 1002 is further configured to send a request message to the second network management device, the request message being used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The transceiver unit 1002 is also configured to receive feedback information sent by the second network management device, the feedback information including, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0290] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of S701 and S702 in the embodiments will not be repeated here.

[0291] In one implementation, mobility optimization performance data includes one or more of the following: the total number of secondary node handovers, the total number of secondary node handover failures, the number of times a ping-pong effect occurs, the number of times a secondary node is updated too early, the number of times a secondary node is updated too late, the number of times a secondary node is switched to the wrong cell, or the number of times a radio link is on the verge of failure.

[0292] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of the total number of secondary node handovers, the total number of secondary node handover failures, the number of times the ping-pong effect occurred, the number of times the secondary node was updated too early, the number of times the secondary node was updated too late, the number of times the secondary node was switched to the wrong cell, or the number of times the radio link was on the verge of failure, as described in the embodiments, will not be repeated here.

[0293] In one implementation, the transceiver unit 1002 is further configured to:

[0294] Send a subscription operation to the second network management device;

[0295] Receive an indication message sent by the second network management device, which indicates that the file data is ready;

[0296] A request message is sent to the second network management device to request available file data.

[0297] For specific implementation details, please refer to [link / reference]. Figure 8 The detailed descriptions of S801 to S803 in the embodiments will not be repeated here.

[0298] In one implementation, the transceiver unit 1002 is further configured to:

[0299] Send a command to create a measurement task to the second network management device;

[0300] Receive data stream connection establishment operation sent by the second network management device;

[0301] Receives data streams sent by the second network management device.

[0302] For specific implementation details, please refer to [link / reference]. Figure 9 The detailed descriptions of S901 to S903 in the embodiments will not be repeated here.

[0303] In one implementation, Figure 10 The functions implemented by each unit can be achieved through a transceiver and a processor. Please refer to [link / reference]. Figure 11 , Figure 11This is a schematic diagram of the structure of a first network management device provided in an embodiment of this application. The first network management device can be a device (e.g., a chip) that performs the mobility parameter configuration function described in the embodiments of this application. The first network management device 1100 may include a transceiver 1101, at least one processor 1102, and a memory 1103. The transceiver 1101, processor 1102, and memory 1103 can be interconnected via one or more communication buses, or via other methods. This embodiment uses a bus connection as an example, such as... Figure 11 As shown.

[0304] Transceiver 1101 can be used to send or receive data. It is understood that transceiver 1101 is a general term and may include both receivers and transmitters. For example, a transmitter is used to send the mobility optimization attributes to a second network management device.

[0305] The processor 1102 can be used to process data. For example, the processor 1102 can call program code stored in the memory 1103 to determine mobility optimization attributes. The processor 1102 may include one or more processors, such as one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof. If the processor 1102 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0306] The memory 1103 is used to store program code, etc. The memory 1103 may include volatile memory, such as random access memory (RAM). The memory 1103 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD). The memory 1103 may also include combinations of the above types of memory.

[0307] The transceiver 1101 and processor 1102 described above can be used to implement the mobility parameter configuration method in the embodiments of this application, wherein the specific implementation is as follows:

[0308] Determine mobility optimization attributes, which are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure;

[0309] Send the mobility optimization attribute to the second network management device.

[0310] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of S601 and S602 in the embodiments will not be repeated here.

[0311] In one implementation, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger limit parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0312] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0313] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first strategy parameters in the embodiments will not be repeated here.

[0314] In one implementation, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio links, ping-pong handover count rate, premature handover failure rate, or late handover call drop rate.

[0315] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first target parameter in the embodiments will not be repeated here.

[0316] In one implementation, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0317] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first control parameter in the embodiments will not be repeated here.

[0318] In one implementation, the mobility optimization attribute includes a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter. The abnormal coverage policy parameter includes one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameter includes one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0319] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second strategy parameters in the embodiments will not be repeated here.

[0320] In one implementation, the mobility optimization attribute includes a second target parameter, which includes one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization target parameter. The handover-triggered optimization target parameter includes one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0321] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second target parameter in the embodiments will not be repeated here.

[0322] In one implementation, the mobility optimization attribute includes one or more of a first policy parameter, a first target parameter, a first control parameter, a second policy parameter, or a second target parameter.

[0323] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of the first strategy parameter, first target parameter, first control parameter, second strategy parameter, and second target parameter in the embodiments will not be repeated here.

[0324] In one implementation, transceiver 1101 is further configured to receive a response message sent by the second network management device, the response message indicating the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0325] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of S603 in the embodiment will not be repeated here.

[0326] In one implementation, transceiver 1101 is further configured to send a request message to a second network management device, the request message being used to request mobility optimization performance data corresponding to a mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. Transceiver 1101 is also configured to receive feedback information sent by the second network management device, the feedback information including, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0327] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of S701 and S702 in the embodiments will not be repeated here.

[0328] In one implementation, mobility optimization performance data includes one or more of the following: the total number of secondary node handovers, the total number of secondary node handover failures, the number of times a ping-pong effect occurs, the number of times a secondary node is updated too early, the number of times a secondary node is updated too late, the number of times a secondary node is switched to the wrong cell, or the number of times a radio link is on the verge of failure.

[0329] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of the total number of secondary node handovers, the total number of secondary node handover failures, the number of times the ping-pong effect occurred, the number of times the secondary node was updated too early, the number of times the secondary node was updated too late, the number of times the secondary node was switched to the wrong cell, or the number of times the radio link was on the verge of failure, as described in the embodiments, will not be repeated here.

[0330] In one implementation, transceiver 1101 is also used for:

[0331] Send a subscription operation to the second network management device;

[0332] Receive an indication message sent by the second network management device, which indicates that the file data is ready;

[0333] A request message is sent to the second network management device to request available file data.

[0334] For specific implementation details, please refer to [link / reference]. Figure 8 The detailed descriptions of S801 to S803 in the embodiments will not be repeated here.

[0335] In one implementation, transceiver 1101 is also used for:

[0336] Send a command to create a measurement task to the second network management device;

[0337] Receive data stream connection establishment operation sent by the second network management device;

[0338] Receives data streams sent by the second network management device.

[0339] For specific implementation details, please refer to [link / reference]. Figure 9 The detailed descriptions of S901 to S903 in the embodiments will not be repeated here.

[0340] This application provides a second network management device, such as... Figure 12 As shown, the second network management device 1200 can be used to implement the mobility parameter configuration method in the embodiments of this application. The second network management device 1200 may include:

[0341] The transceiver unit 1201 is configured to receive mobility optimization attributes sent by the first network management device, the mobility optimization attributes being used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure; the transceiver unit 1201 is also configured to send the mobility optimization attributes to the second network device, so that the second network device adjusts the handover parameters of the terminal device during the handover process from the first network device to the second network device according to the mobility optimization attributes in the event of secondary cell radio link failure and / or impending radio link failure.

[0342] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of S601 and S602 in the embodiments will not be repeated here.

[0343] In one implementation, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger limit parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0344] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0345] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first strategy parameters in the embodiments will not be repeated here.

[0346] In one implementation, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio links, ping-pong handover count rate, premature handover failure rate, or late handover call drop rate.

[0347] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first target parameter in the embodiments will not be repeated here.

[0348] In one implementation, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0349] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first control parameter in the embodiments will not be repeated here.

[0350] In one implementation, the mobility optimization attribute includes a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter. The abnormal coverage policy parameter includes one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameter includes one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0351] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second strategy parameters in the embodiments will not be repeated here.

[0352] In one implementation, the mobility optimization attribute includes a second target parameter, which includes one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization target parameter. The handover-triggered optimization target parameter includes one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0353] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second target parameter in the embodiments will not be repeated here.

[0354] In one implementation, the mobility optimization attribute includes one or more of a first policy parameter, a first target parameter, a first control parameter, a second policy parameter, or a second target parameter.

[0355] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of the first strategy parameter, first target parameter, first control parameter, second strategy parameter, and second target parameter in the embodiments will not be repeated here.

[0356] In one implementation, the transceiver unit 1201 is further configured to send a response message to the first network management device, the response message indicating the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0357] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of S603 in the embodiment will not be repeated here.

[0358] In one implementation, the transceiver unit 1201 is further configured to receive a request message sent by the first network management device. The request message requests mobility optimization performance data corresponding to a mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The transceiver unit 1201 is also configured to send feedback information to the first network management device. This feedback information includes, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0359] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of S701 and S702 in the embodiments will not be repeated here.

[0360] In one implementation, mobility optimization performance data includes one or more of the following: the total number of secondary node handovers, the total number of secondary node handover failures, the number of times a ping-pong effect occurs, the number of times a secondary node is updated too early, the number of times a secondary node is updated too late, the number of times a secondary node is switched to the wrong cell, or the number of times a radio link is on the verge of failure.

[0361] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of the total number of secondary node handovers, the total number of secondary node handover failures, the number of times the ping-pong effect occurred, the number of times the secondary node was updated too early, the number of times the secondary node was updated too late, the number of times the secondary node was switched to the wrong cell, or the number of times the radio link was on the verge of failure, as described in the embodiments, will not be repeated here.

[0362] In one implementation, the transceiver unit 1201 is further configured to receive a subscription operation sent by the first network management device. The processing unit 1202 determines that the file data is ready. The transceiver unit 1201 is further configured to send an indication message to the first network management device, the indication message indicating that the file data is ready; the transceiver unit 1201 is further configured to receive a request message sent by the first network management device, the request message requesting to obtain available file data.

[0363] For specific implementation details, please refer to [link / reference]. Figure 8 The detailed descriptions of S801 to S803 in the embodiments will not be repeated here.

[0364] In one implementation, the transceiver unit 1201 is further configured to:

[0365] Receive the "Create Measurement Task" operation sent by the first network management device;

[0366] Send a data stream connection establishment operation to the first network management device;

[0367] Send a data stream to the first network management device.

[0368] For specific implementation details, please refer to [link / reference]. Figure 9 The detailed descriptions of S901 to S903 in the embodiments will not be repeated here.

[0369] In one implementation, Figure 12 The functions implemented by each unit can be achieved through a transceiver and a processor. Please refer to [link / reference]. Figure 13 , Figure 13 This is a schematic diagram of the structure of a second network management device provided in an embodiment of this application. The second network management device can be a device (e.g., a chip) that performs the mobility parameter configuration function described in the embodiments of this application. The second network management device 1300 may include a transceiver 1301, at least one processor 1302, and a memory 1303. The transceiver 1301, processor 1302, and memory 1303 can be interconnected via one or more communication buses, or via other methods. This embodiment uses a bus connection as an example, such as... Figure 13 As shown.

[0370] Transceiver 1301 can be used to send or receive data. It is understood that transceiver 1301 is a general term and may include receivers and transmitters. For example, a receiver is used to receive mobility optimization attributes sent by a first network management device.

[0371] The processor 1302 can be used to process data. The processor 1302 may include one or more processors, such as one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof. If the processor 1302 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0372] The memory 1303 is used to store program code, etc. The memory 1303 may include volatile memory, such as random access memory (RAM). The memory 1303 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD). The memory 1303 may also include combinations of the above types of memory.

[0373] The transceiver 1301 described above can be used to implement the mobility parameter configuration method in the embodiments of this application, wherein the specific implementation is as follows:

[0374] Receive mobility optimization attributes sent by the first network management device, which are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure;

[0375] The mobility optimization attribute is sent to the second network device so that the second network device can adjust the handover parameters of the terminal device during the handover process from the first network device to the second network device in the event of failure of the secondary cell radio link and / or impending failure of the radio link.

[0376] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of S601 and S602 in the embodiments will not be repeated here.

[0377] In one implementation, the mobility optimization attribute includes a first strategy parameter, which includes one or more of the following: a switch trigger limit parameter, a switch adjustment strategy parameter, an optimization period, or a switch optimization strategy parameter.

[0378] The handover triggering parameters include the maximum handover triggering deviation and / or the minimum handover triggering time interval during secondary cell handover. The handover adjustment strategy parameters include one or more of the following: cell-specific offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization strategy parameters include the optimization triggering threshold corresponding to secondary cell radio link failure, and / or, the optimization triggering threshold corresponding to near radio link failure.

[0379] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first strategy parameters in the embodiments will not be repeated here.

[0380] In one implementation, the mobility optimization attribute includes a first target parameter, which includes one or more of the following: cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters. The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio links, ping-pong handover count rate, premature handover failure rate, or late handover call drop rate.

[0381] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first target parameter in the embodiments will not be repeated here.

[0382] In one implementation, the mobility optimization attribute includes a first control parameter, which includes mobility optimization function control parameters for secondary cell radio link failure and / or mobility optimization function control parameters for near radio link failure.

[0383] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the first control parameter in the embodiments will not be repeated here.

[0384] In one implementation, the mobility optimization attribute includes a second policy parameter, which includes one or more of the following: network device identifier, abnormal coverage policy parameter, or abnormal radio link policy parameter. The abnormal coverage policy parameter includes one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameter includes one or more of the following: abnormal radio link failure ratio threshold, network device group handover failure ratio threshold, or near-failure radio link ratio threshold.

[0385] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second strategy parameters in the embodiments will not be repeated here.

[0386] In one implementation, the mobility optimization attribute includes a second target parameter, which includes one or more of the following: network device identifier, abnormal coverage ratio, or handover-triggered optimization target parameter. The handover-triggered optimization target parameter includes one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

[0387] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of the second target parameter in the embodiments will not be repeated here.

[0388] In one implementation, the mobility optimization attribute includes one or more of a first policy parameter, a first target parameter, a first control parameter, a second policy parameter, or a second target parameter.

[0389] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed descriptions of the first strategy parameter, first target parameter, first control parameter, second strategy parameter, and second target parameter in the embodiments will not be repeated here.

[0390] In one implementation, transceiver 1301 is further configured to send a response message to the first network management device, the response message indicating the configuration status of the second network management device. The configuration status of the second network management device includes configuration success, configuration failure, or inability to configure.

[0391] For specific implementation details, please refer to [link / reference]. Figure 6 The detailed description of S603 in the embodiment will not be repeated here.

[0392] In one implementation, transceiver 1301 is further configured to receive a request message sent by a first network management device, the request message being used to request mobility optimization performance data corresponding to a mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. Transceiver 1301 is also configured to send feedback information to the first network management device, the feedback information including, in the event of secondary cell radio link failure and / or impending radio link failure, the mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute.

[0393] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of S701 and S702 in the embodiments will not be repeated here.

[0394] In one implementation, mobility optimization performance data includes one or more of the following: the total number of secondary node handovers, the total number of secondary node handover failures, the number of times a ping-pong effect occurs, the number of times a secondary node is updated too early, the number of times a secondary node is updated too late, the number of times a secondary node is switched to the wrong cell, or the number of times a radio link is on the verge of failure.

[0395] For specific implementation details, please refer to [link / reference]. Figure 7 The detailed descriptions of the total number of secondary node handovers, the total number of secondary node handover failures, the number of times the ping-pong effect occurred, the number of times the secondary node was updated too early, the number of times the secondary node was updated too late, the number of times the secondary node was switched to the wrong cell, or the number of times the radio link was on the verge of failure, as described in the embodiments, will not be repeated here.

[0396] In one implementation, transceiver 1301 is further configured to receive a subscription operation sent by a first network management device. Processor 1302 determines that file data is ready. Transceiver 1301 is further configured to send an indication message to the first network management device, the indication message indicating that file data is ready; transceiver 1301 is further configured to receive a request message sent by the first network management device, the request message requesting to obtain available file data.

[0397] For specific implementation details, please refer to [link / reference]. Figure 8 The detailed descriptions of S801 to S803 in the embodiments will not be repeated here.

[0398] In one implementation, transceiver 1301 is also used for:

[0399] Receive the "Create Measurement Task" operation sent by the first network management device;

[0400] Send a data stream connection establishment operation to the first network management device;

[0401] Send a data stream to the first network management device.

[0402] For specific implementation details, please refer to [link / reference]. Figure 9 The detailed descriptions of S901 to S903 in the embodiments will not be repeated here.

[0403] This application provides a computer-readable storage medium storing a program or instructions that, when executed on a computer, cause the computer to perform the mobility parameter setting method described in this application.

[0404] This application provides a chip or chip system, which includes at least one processor and an interface. The interface and the at least one processor are interconnected via a circuit. The at least one processor is used to run computer programs or instructions to perform the mobility parameter setting method in this application embodiment.

[0405] The interfaces in the chip can be input / output interfaces, pins, or circuits, etc.

[0406] The chip system mentioned above can be a system on chip (SOC) or a baseband chip, etc. The baseband chip can include processors, channel encoders, digital signal processors, modems and interface modules, etc.

[0407] In one implementation, the chip or chip system described above in this application further includes at least one memory, which stores instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0408] This application provides a communication system, including a first network management device and a second network management device according to embodiments of this application.

[0409] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0410] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0411] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A mobility parameter configuration method, characterized in that, include: The first network management device determines mobility optimization attributes, which are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure. The first network management device sends the mobility optimization attribute to the second network device through the second network management device. The mobility optimization attribute is used to adjust the handover parameters of the terminal device during the handover process from the first network device to the second network device in the event of secondary cell radio link failure and / or impending radio link failure. The mobility optimization attribute includes a first policy parameter and / or a first control parameter. The first policy parameter includes one or more of the following: handover trigger limiting parameter, handover adjustment policy parameter, optimization period, or handover optimization policy parameter. The handover trigger limiting parameter includes the maximum handover trigger deviation value and / or the minimum handover trigger time interval during secondary cell handover. The handover adjustment policy parameter includes one or more of the following: cell individual offset adjustment parameter, beam parameter, radio link monitoring parameter, and random access resource parameter. The handover optimization policy parameter includes an optimization trigger threshold corresponding to secondary cell radio link failure and / or an optimization trigger threshold corresponding to impending radio link failure. The first control parameter includes a mobility optimization function control switch for secondary cell radio link failure and / or a mobility optimization function control switch for impending radio link failure.

2. The method according to claim 1, characterized in that, The mobility optimization attribute further includes a first objective parameter; the first objective parameter includes one or more of the following: Cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters; among which... The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio link, ping-pong handover frequency, early handover failure rate, or late handover call drop rate.

3. The method according to claim 1, characterized in that, The mobility optimization attribute further includes a second policy parameter; the second policy parameter includes one or more of the following: Network device identifier, abnormal coverage policy parameters, or abnormal wireless link policy parameters; among which, The abnormal coverage strategy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal wireless link policy parameters include one or more of the following: abnormal wireless link failure ratio threshold, network device group handover failure ratio threshold, or near-wireless link failure ratio threshold.

4. The method according to claim 1, characterized in that, The mobility optimization attribute further includes a second objective parameter; the second objective parameter includes one or more of the following: Network device identifier, abnormal coverage ratio, or handover trigger optimization target parameter; wherein, the handover trigger optimization target parameter includes one or more of the following: secondary cell radio link failure ratio, secondary cell handover failure ratio, or near-failure radio link ratio.

5. The method according to claim 1, characterized in that, The method further includes: The first network management device receives a response message sent by the second network management device, the response message indicating the configuration status of the second network management device.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The first network management device sends a request message to the second network management device. The request message is used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or request an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The first network management device receives feedback information sent by the second network management device. The feedback information includes mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute in the event of secondary cell radio link failure and / or impending radio link failure.

7. The method according to claim 6, characterized in that, The mobility optimization performance data includes one or more of the following: Total number of secondary node handovers, total number of secondary node handover failures, number of times the ping-pong effect occurred, number of times the secondary node was updated too early, number of times the secondary node was updated too late, number of times the secondary node was switched to the wrong cell, or number of times the radio link was on the verge of failure.

8. A mobility parameter configuration method, characterized in that, include: The second network management device receives mobility optimization attributes sent by the first network management device. The mobility optimization attributes are used to indicate attributes configured in the event of secondary cell radio link failure and / or impending radio link failure. The second network management device sends the mobility optimization attribute to the second network device. The mobility optimization attribute is used to adjust handover parameters during the handover process from the first network device to the second network device in the event of secondary cell radio link failure and / or impending radio link failure. The mobility optimization attribute includes a first policy parameter and / or a first control parameter. The first policy parameter includes one or more of the following: handover trigger limiting parameters, handover adjustment policy parameters, optimization period, or handover optimization policy parameters. The handover trigger limiting parameter includes the maximum handover trigger deviation value and / or the minimum handover trigger time interval during secondary cell handover. The handover adjustment policy parameter includes one or more of the following: cell individual offset adjustment parameters, beam parameters, radio link monitoring parameters, and random access resource parameters. The handover optimization policy parameter includes an optimization trigger threshold corresponding to secondary cell radio link failure and / or an optimization trigger threshold corresponding to impending radio link failure. The first control parameter includes a mobility optimization function control switch for secondary cell radio link failure and / or a mobility optimization function control switch for impending radio link failure.

9. The method according to claim 8, characterized in that, The mobility optimization attribute further includes a first objective parameter; the first objective parameter includes one or more of the following: Cell identifier, maximum number of handover triggers, or handover trigger optimization target parameters; among which... The handover trigger optimization target parameters include one or more of the following: secondary cell radio link failure rate, near-failure rate of radio link, ping-pong handover frequency, early handover failure rate, or late handover call drop rate.

10. The method according to claim 8, characterized in that, The mobility optimization attribute further includes a second policy parameter; the second policy parameter includes one or more of the following: Network device identifier, abnormal coverage policy parameters, or abnormal wireless link policy parameters; among which, The abnormal coverage strategy parameters include one or more of the following: abnormal coverage threshold, reference signal received power threshold of the serving cell, or reference signal received power threshold of neighboring cells. The abnormal radio link policy parameters include one or more of the following: abnormal radio link failure ratio threshold, secondary cell handover failure ratio threshold, or near-radio link failure ratio threshold.

11. The method according to claim 8, characterized in that, The mobility optimization attribute further includes a second objective parameter, which includes one or more of the following: Network device identifier, abnormal coverage ratio, or handover trigger optimization target parameter; wherein, the handover trigger optimization target parameter includes one or more of the following: abnormal radio link failure ratio, secondary cell handover failure ratio, or near-radio link failure ratio.

12. The method according to claim 8, characterized in that, The method further includes: The second network management device sends a response message to the first network management device, the response message indicating the configuration status of the second network management device.

13. The method according to any one of claims 8 to 12, characterized in that, The method further includes: The second network management device receives a request message sent by the first network management device. The request message is used to request mobility optimization performance data corresponding to the mobility optimization attribute and / or to request an indication of the mobility optimization performance data corresponding to the mobility optimization attribute. The second network management device sends feedback information to the first network management device. The feedback information includes mobility optimization performance data corresponding to the mobility optimization attribute and / or an indication of the mobility optimization performance data corresponding to the mobility optimization attribute in the event of secondary cell radio link failure and / or impending radio link failure.

14. The method according to claim 13, characterized in that, The mobility optimization performance data includes one or more of the following: Total number of secondary node handovers, total number of secondary node handover failures, number of times the ping-pong effect occurred, number of times the secondary node was updated too early, number of times the secondary node was updated too late, number of times the secondary node was switched to the wrong cell, or number of times the radio link was on the verge of failure.

15. A first network management device, characterized in that, Including memory and processor; The memory is used to store instructions; The processor is configured to execute the instructions such that the method as described in any one of claims 1 to 7 is performed.

16. A second network management device, characterized in that, Including memory and processor; The memory is used to store instructions; The processor is configured to execute the instructions such that the method as described in any one of claims 8 to 14 is performed.

17. A communication system, characterized in that, include: A first network management device is configured to perform the method as described in any one of claims 1 to 7; A second network management device is used to perform the method as described in any one of claims 8 to 14.

18. A computer-readable storage medium, characterized in that, Includes a program or instructions that, when run on a computer, execute the method as described in any one of claims 1 to 7 or 8 to 14.

Images