CN113973316A

CN113973316A - Mobility parameter configuration method and related equipment

Info

Publication number: CN113973316A
Application number: CN202010716141.9A
Authority: CN
Inventors: 石小丽; 贾晓倩; 邹兰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-07-23
Filing date: 2020-07-23
Publication date: 2022-01-25
Also published as: WO2022017377A1

Abstract

The embodiment of the application discloses a mobility parameter configuration method and related equipment. Wherein the method may be implemented by an interaction between the first network management device and the second network management device. The first network management device may send a mobility optimization attribute to the second network management device, where the mobility optimization attribute is used to indicate an attribute configured in case of a secondary cell radio link failure and/or an imminent radio link failure. That is to say, the method realizes the mobility parameter optimization under the multi-link data transmission scene and the switching success scene, and ensures the mobility performance.

Description

Mobility parameter configuration method and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a mobility parameter configuration method and related devices.

Background

In a mobile communication system, a change in the location of a terminal device or a change in the load in the network may require the terminal device to be handed over from a first network device to a second network device. For example, a change in the location of the terminal device results in the terminal device needing to be handed over from base station 1 to base station 2. If the mobility optimization attribute is improperly set, the problems of too early and too late handover, ping-pong effect and the like may be caused, thereby causing handover failure and reducing system performance.

Disclosure of Invention

The embodiment of the application provides a mobility optimization attribute configured under the condition that a wireless link of a secondary cell fails and/or an imminent wireless link fails, which is beneficial to reducing the failure rate of switching in a system or between systems and ensuring the mobility performance.

In a first aspect, an embodiment of the present application provides a mobility parameter configuration method, which may be performed by a first network management device. The first network management device may be a network management entity defined by 3GPP, such as a management service consumer (management service provider). The first network management device may send a mobility optimization attribute to the second network management device, where the mobility optimization attribute is used to indicate an attribute configured in case of a secondary cell radio link failure and/or an imminent radio link failure.

The secondary cell radio link failure indicates that the secondary cell radio link failure is caused by the change of a secondary base station or a secondary cell in a multi-link data transmission scene. The impending radio link failure indicates that the quality of a radio link between the terminal device and the base station is poor in a scenario where the terminal device is successfully switched, that is, the radio link between the terminal device and the base station may be disconnected at any time.

As can be seen, the mobility optimization attribute provided in the embodiment of the present application may configure a corresponding mobility optimization attribute for the case where the two radio links fail. For example, the mobility optimization attribute aiming at the radio link failure of the secondary cell and the mobility optimization attribute aiming at the impending radio link failure are configured for the base station, the cell or the user, which is beneficial to reducing the failure rate of switching in the system or between the systems and ensuring the mobility performance.

In one possible design, the mobility optimization attribute includes a first policy parameter that includes one or more of: a handover trigger limit parameter, a handover adjustment policy parameter, an optimization period, or a handover optimization policy parameter.

And the switching trigger limiting parameter comprises a maximum switching trigger deviation value and/or a minimum switching trigger time interval when the secondary cell is switched. The switching adjustment strategy parameters comprise one or more of adjustment parameters of cell individual deviation, beam parameters, wireless link monitoring parameters and random access resource parameters. The handover optimization strategy parameters comprise an optimization triggering threshold corresponding to the radio link failure of the secondary cell and/or an optimization triggering threshold corresponding to the impending radio link failure.

Therefore, the first strategy parameter can limit the relevant parameters of the cell individual deviation during the secondary cell switching and the parameters of the minimum time interval and the like of the switching between the secondary cells, so that the failure of the wireless link of the secondary cell caused by the early switching, the late switching and the like of the secondary base station in the multi-link data transmission scene can be avoided, and the probability of the failure of the impending wireless link in the scene of successful switching can be reduced.

In one possible design, the mobility optimization attribute includes a first target parameter that includes one or more of: cell identity, maximum number of handover triggers or handover trigger optimization objective parameters. The handover trigger optimization target parameters comprise one or more of a radio link failure proportion of the secondary cell, an imminent radio link failure proportion, a ping-pong handover frequency proportion, a handover early failure rate or a handover late call drop rate.

Therefore, the first target parameter can limit the maximum times of cell switching triggering and the switching proportion of the secondary base station under the conditions of too early and too late switching, which is beneficial to reducing the probability of secondary cell radio link failure caused by too early and too late switching of the secondary base station under the scene of multilinked data transmission and reducing the probability of imminent radio link failure under the scene of successful switching.

In one possible design, the mobility optimization attribute includes a first control parameter that includes a mobility optimization function control parameter for a secondary cell radio link failure and/or a mobility optimization function control parameter for an impending radio link failure.

Therefore, the first control parameter can control the mobility optimization attribute to solve the problem of the link failure of the secondary cell in the multi-link data transmission scene, and can also control the mobility optimization attribute to solve the problem of the impending link failure in the scene of successful handover.

First objective parameters in one possible design, the mobility optimization attribute includes a second policy parameter that includes one or more of: a network device identification, an abnormal coverage policy parameter, or an abnormal radio link policy parameter.

Wherein the abnormal coverage strategy parameter comprises one or more of an abnormal coverage threshold, a reference signal received power threshold of a serving cell or a reference signal received power threshold of an adjacent cell. The abnormal radio link strategy parameters comprise one or more of abnormal radio link failure ratio threshold, network equipment group switching failure ratio threshold or impending radio link failure ratio threshold.

As can be seen, the second policy parameter may define the abnormal coverage policy of the base station, the ratio threshold of the handover failure of the secondary base station, the ratio threshold of the impending radio link failure, and other parameters, thereby determining the mobility optimization attribute at the base station level.

In one possible design, the mobility optimization attribute includes a second target parameter that includes one or more of: network device identification, abnormal coverage proportion, or handover trigger optimization objective parameters. The handover trigger optimization target parameters comprise one or more of a secondary cell radio link failure proportion, a secondary cell handover failure proportion or an impending radio link failure proportion.

In one possible design, 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.

In one possible design, the first network management device may further receive a response message sent by the second network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

It can be seen that, after receiving the mobility optimization attribute, the second network management device may perform configuration of the mobility optimization attribute. And the second network management device feeds back the configuration state to the first network management device, so that the first network management device knows whether the second network management device successfully configures the mobility optimization attribute.

In one possible design, the first network management device sends a request message to the second network management device, where the request message is 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 first network management device receives feedback information sent by the second network management device, wherein the feedback information comprises 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 under the condition that a radio link of a secondary cell fails and/or an imminent radio link fails.

It can be seen that the second network management device may also report the system performance data after the mobility optimization attribute configuration, and record the improvement of the system performance by the configuration of the mobility optimization attribute.

In one possible design, the mobility-optimized performance data includes one or more of: the total number of times of switching of the auxiliary node, the total number of times of switching failure of the auxiliary node, the number of times of generating ping-pong effect, the number of times of updating too early of the auxiliary node, the number of times of updating too late of the auxiliary node, the number of times of switching the auxiliary node to a wrong cell, or the number of times of failure of an impending wireless link.

In a second aspect, an embodiment of the present application provides a mobility parameter configuration method, which may be performed by a second network management device. Wherein the second network management device may be a network management entity defined by the standardization organization 3GPP, such as a management service consumer. The second network management device may receive a mobility optimization attribute sent by the first network management device, where the mobility optimization attribute is used to indicate an attribute configured in the case of a radio link failure and/or an imminent radio link failure of the secondary cell. The second network management device may further send the mobility optimization attribute to the second network device, so that the second network device adjusts a handover parameter in a process of handover of the terminal device from the first network device to the second network device according to the mobility optimization attribute when the secondary cell radio link fails and/or is imminent to fail.

It can be seen that the second network management device may receive the mobility optimization attribute, and may also send the mobility optimization attribute to a subordinate network device (such as an auxiliary base station, etc.), so that the network device configures a handover parameter according to the mobility optimization attribute, thereby facilitating reduction of probability of handover failure of the terminal device between the auxiliary cells or the auxiliary base stations.

The switching trigger limiting parameter comprises a maximum switching trigger deviation value and/or a minimum switching trigger time interval when the secondary cell is switched; the switching adjustment strategy parameters comprise one or more of adjustment parameters of cell individual deviation, beam parameters, wireless link monitoring parameters and random access resource parameters; the handover optimization strategy parameters comprise an optimization triggering threshold corresponding to the radio link failure of the secondary cell and/or an optimization triggering threshold corresponding to the impending radio link failure.

In one possible design, the second network management device may also 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 state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In one possible design, the second network management device receives a request message sent by the first network management device, where the request message is 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. And the second network management equipment sends feedback information to the first network management equipment, wherein the feedback information comprises 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 under the condition that the radio link of the secondary cell fails and/or the radio link is imminent.

In a third aspect, an embodiment of the present application provides a first network management device, where the first network management device includes a processing unit and a transceiver unit. The processing unit is used for determining a mobility optimization attribute, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a secondary cell radio link fails and/or an imminent radio link fails. The transceiver unit is configured to send the mobility optimization attribute to the second network management device.

In a possible design, the transceiver unit is further configured to receive a response message sent by the second network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In a possible design, the transceiver unit is further configured to send a request message to the second network management device, where 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 transceiver unit is further configured to receive feedback information sent by the second network management device, where the feedback information includes 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 in the case of a radio link failure and/or an imminent radio link failure of the secondary cell.

In a fourth aspect, an embodiment of the present application provides a second network management device, where the second network management device includes a transceiver unit. The receiving and sending unit is configured to receive a mobility optimization attribute sent by the first network management device, where the mobility optimization attribute is used to indicate an attribute configured in the case of a radio link failure and/or an imminent radio link failure of the secondary cell. The transceiver unit is further configured to send the mobility optimization attribute to the second network device, so that the second network device adjusts a handover parameter in a process of handover of the terminal device from the first network device to the second network device according to the mobility optimization attribute when the secondary cell radio link fails and/or is imminent to fail.

In one possible design, the transceiving unit 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 state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In a possible design, the transceiver unit is further configured to receive a request message sent by the first network management device, where the request message is 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 further configured to send feedback information to the first network management device, where 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 case of a radio link failure and/or an imminent radio link failure of the secondary cell.

In a fifth aspect, an embodiment of the present application provides a first network management device, where the first network management device has a function of implementing the mobility parameter configuration method provided in the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixth aspect, an embodiment of the present application provides a second network management device, where the second network management device has a function of implementing the mobility parameter configuration method provided in the second aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventh aspect, an embodiment of the present application provides a communication system, where the communication system includes the first network management device provided in the third aspect or the fifth aspect, and the second network management device provided in the fourth aspect or the sixth aspect.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium, which includes a program or instructions, which when executed on a computer, causes the computer to perform the method of the first aspect or any of the possible implementations of the first aspect.

In a ninth aspect, embodiments of the present application provide a computer-readable storage medium, which includes a program or instructions, which when executed on a computer, causes the computer to perform the method of the second aspect or any of the possible implementations of the second aspect.

In a tenth aspect, an embodiment of the present application provides a chip or a chip system, where the chip or the chip system includes at least one processor and an interface, the interface and the at least one processor are interconnected by a line, and the at least one processor is configured to execute a computer program or instructions to perform the method described in any one of the first aspect or any one of the possible implementation manners of the first aspect.

In an eleventh aspect, embodiments of the present application provide a chip or a chip system, where the chip or the chip system includes at least one processor and an interface, the interface and the at least one processor are interconnected by a line, and the at least one processor is configured to execute a computer program or instructions to perform the method described in any one of the second aspect or any one of the possible implementation manners of the second aspect.

The interface in the chip may be an input/output interface, a pin, a circuit, or the like.

The system-on-chip in the above aspect may be a system-on-chip (SOC), a baseband chip, and the like, where the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem, an interface module, and the like.

In one possible implementation, the chip or chip system described above in this application further comprises at least one memory having instructions stored therein. The memory may be a memory module inside the chip, such as a register, a cache, etc., or may be a memory module of the chip (e.g., a read-only memory, a random access memory, etc.).

In a twelfth aspect, embodiments of the present application provide a computer program or a computer program product, which includes code or instructions, when the code or instructions are executed on a computer, cause the computer to execute the method of the first aspect or any possible implementation manner of the first aspect.

In a thirteenth aspect, embodiments of the present application provide a computer program or a computer program product, which includes code or instructions, when the code or instructions are run on a computer, cause the computer to execute the method of the second aspect or any one of the possible implementations of the second aspect.

Drawings

Fig. 1a is a schematic diagram of a premature handover scenario provided in an embodiment of the present application;

fig. 1b is a schematic diagram of a mobility optimization scenario provided in an embodiment of the present application;

fig. 2a is a schematic diagram of a multilink data transmission scenario provided in an embodiment of the present application;

fig. 2b is a schematic diagram illustrating a handover failure of a terminal device between secondary base stations in a scenario of multilink data transmission according to an embodiment of the present application;

fig. 3 is a schematic diagram illustrating an imminent radio link failure in a handover success scenario according to an embodiment of the present application;

fig. 4 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 5 is a schematic diagram of a service management architecture according to an embodiment of the present application;

fig. 6 is a flowchart illustrating a mobility parameter configuration method according to an embodiment of the present application;

fig. 7 is a schematic flowchart illustrating a first network management device and a second network management device managing mobility optimization performance data according to an embodiment of the present application;

fig. 8 is a schematic flowchart of a first network management device and a second network management device managing MRO performance indicators according to an embodiment of the present application;

fig. 9 is a schematic flowchart of another example of a first network management device and a second network management device managing an MRO performance indicator according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a first network management device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of another first network management device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a second network management device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another second network management device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

Before the description of the embodiments of the present application, the related concepts are first explained.

In a mobile communication system, a change in the location of a terminal device or a change in the load in the network may require the terminal device to be handed over from a first network device to a second network device. For example, a change in the location of the terminal device results in the terminal device needing to be handed over from base station 1 to base station 2. If the switching parameters of the network device are not properly set, problems such as too early switching, too late switching, ping-pong effect, etc. may be caused, thereby causing a switching failure and reducing the system performance.

For example, please refer to fig. 1a, wherein fig. 1a is a schematic diagram of a premature handover scenario according to an embodiment of the present disclosure. After the source cell issues the handover command to the terminal device, the terminal device fails to handover to the target cell due to poor signal quality of the target cell. That is, Radio Link Failure (RLF) between the terminal device and the target cell occurs before handover is completed. The terminal device performs cell selection, selects a source cell and attempts Radio Resource Control (RRC) reestablishment. The terminal equipment reestablishes the source cell, and after the reestablishment is successful, the source cell recognizes that the scene is a scene with early switching.

If the switching parameters are not properly set, the switching parameters of the system can be adjusted in a manual setting mode. However, it is time consuming to manually set the switching parameters of the system, and it is costly to adjust the switching parameters of the system after the initial deployment of the network is completed. Based on this, a Mobility Robustness Optimization (MRO) function is proposed in a Long Term Evolution (LTE) network, which can optimize setting of inappropriate handover parameters.

In the MRO optimization period, the base station may count the number of times of abnormal handover. And when the optimization period is reached, optimizing the relevant parameters of the switching according to the counted abnormal switching times and a preset threshold value.

Further, after optimizing the relevant parameters of the switching, the network management device can monitor whether each index of the switching is optimized. If the switching index is optimized, the parameter is not returned in the next optimization period; and if the switching index is deteriorated, performing parameter rollback in the next period. Therefore, the MRO can reduce the handover failure rate and the user call drop rate in the network and reduce the number of times of too early and too late handover by optimizing the relevant parameters of the handover.

For example, the MRO function may be applied in a premature handover scenario as shown in fig. 1 a. Referring to fig. 1b, fig. 1b is a mobility optimization scenario provided in the embodiment of the present application. Wherein, the base station 1 and the base station 2 are both configured with relevant parameters for performing MRO. The terminal equipment may switch in the normal switching area too early, so that the terminal equipment receives poor signals in the target cell. Then performing MRO may be to turn down a Cell Index Offset (CIO) to make the handover arrive a little later.

With the evolution of networks, under a new radio access (NR) system, two new communication scenarios are introduced. One scenario is a scenario of multi-link data transmission, and the other scenario is a scenario in which the terminal device is successfully switched between network devices.

Referring to fig. 2a, fig. 2a is a scenario of multilink data transmission according to an embodiment of the present disclosure. The multi-link data transmission scenario may include a first network device, a second network device, and a terminal device. Fig. 2a shows only one scenario of a first network device, a second network device, and a terminal device, which is merely an example and is not limited in this embodiment.

The terminal device may simultaneously have a communication connection with the first network device and a communication connection with the second network device and may send and receive data, and this scenario may be referred to as a Dual Connectivity (DC) scenario. The first network device may be referred to as a Master Node (MN), and is responsible for interacting with a terminal device and interacting with a core network control plane entity. The network device other than the first network device, i.e., the second network device, may be referred to as a Secondary Node (SN).

Similarly, if the terminal device can simultaneously have communication connection with the first network device and a plurality of second network devices and can transmit and receive data, the scenario may be referred to as a multi-connectivity (MC) scenario. Among the plurality of network devices, there may be a first network device serving as the MN, and responsible for interacting with the terminal device for radio resource control messages and interacting with the core network control plane entity. The remaining plurality of second network devices may each act as SNs.

The first network device may be a main base station of an LTE scheme (e.g., MeNB), or may be a main base station of an NR scheme (e.g., MgNB). The first network device may also be a Master Node (MN) in a dual-link architecture, or an MN in a multi-link architecture, which is not limited in this embodiment.

The second network device may be an LTE secondary base station (e.g., SeNB) or an NR secondary base station (e.g., SgNB). The second network device may also be a Secondary Node (SN) in a DC architecture or an SN in an MC architecture, which is not limited in this embodiment.

However, in a scenario of multi-link data transmission, a secondary cell radio link failure may be caused by SN change. For example, a secondary cell radio link failure may result from a SN change that is too early, a SN change that is too late, a SN change to the wrong cell, etc.

Referring to fig. 2b, fig. 2b is a schematic view of a scenario in which a terminal device fails to switch between secondary base stations in a multi-link data transmission scenario provided in an embodiment of the present application. Wherein the secondary cell radio link failure may be caused by the premature secondary base station change, which may result in the premature secondary cell handover, as shown in fig. 2 b. In the scenario, the terminal device fails a radio link under the S-SN, because the SN is a secondary base station, which is also called secondary cell group failure (SCG failure).

Referring to fig. 3, fig. 3 is a diagram illustrating an imminent radio link failure in a handover success scenario according to an embodiment of the present application. The imminent radio link failure (near-RLF) means that although the terminal device is successfully switched between the network devices, the state of the radio link between the terminal device and the network device is unstable, and the radio link may be disconnected at any time, as shown in fig. 3.

In order to solve the problem of the radio link in the scenario of multi-link data transmission and the scenario of successful handover, embodiments of the present application provide a mobility parameter configuration method, where a mobility optimization attribute provided by the method indicates an attribute configured by a second network management device in the case of a radio link failure and/or an imminent radio link failure of a secondary cell, so as to implement MRO optimization in an NR system in the above two cases.

The mobility parameter configuration method provided in the embodiment of the present application may be applied to the communication system shown in fig. 4. Referring to fig. 4, fig. 4 is a communication system provided in an embodiment of the present application, where the communication system 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 network device and the second network device are devices (such as base stations and the like) in an access network, and are used for communicating with the terminal device. The terminal device can be switched between the first network device and the second network device, and seamless switching is achieved.

The first network management device and the second network management device are both management entities defined by 3 GPP. That is to say, the mobility parameter configuration method provided in the embodiment of the present application may be applied to a network management architecture of NR.

The externally visible behavior and interface of a management entity in the 3GPP defined services management architecture is defined as a management service. In a management architecture for a given service, a management function (MnF) plays a role of a management service provider (MnS provider) or a management service consumer (MnS provider). The servitization management architecture focuses on managing service providers, which may also be referred to as managing service producers, and managing service consumers.

Referring to fig. 5, fig. 5 is a schematic view of a service management architecture according to an embodiment of the present disclosure. The service management architecture includes a Business Support System (BSS), a cross-Domain management function (CD-MnF), a Domain management function (Domain-MnF), and a network element (element).

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

If the management service is the management service provided by the domain management functional unit, the domain management functional unit is a management service producer, and the cross-domain management functional unit is a management service consumer.

And when the management service is the management service provided by the network element, the network element is a management service producer, and the domain management functional unit is a management service consumer.

The service support system is oriented to communication service (communication service), and is used for providing functions and management services such as charging, settlement, accounting, customer service, business, network monitoring, communication service life cycle management, service intention translation and the like. The service support system may be an operation system of an operator or an operation system of a vertical industry (vertical OT system).

The cross-domain management function unit, also called a Network Management Function (NMF), may be a network management entity such as a Network Management System (NMS), a network function management service consumer (NFMS _ C), and the like. Wherein, the cross-domain management function unit provides one or more of the following management functions or management services: the network management system comprises the following components of network life cycle management, network deployment, network fault management, network performance management, network configuration management, network guarantee, network optimization function, service producer network intention (Intent-CSP) translation and the like.

The network referred to in the management function or the management service may include one or more network elements or sub-networks, and may also be a network slice. That is, the network management Function unit may be a Network Slice Management Function (NSMF), or a cross-domain Management Data Analysis Function (MDAF), or a self-organization network Function (SON Function) or a cross-domain intention management Function (Intent drive MnS).

Optionally, in some deployment scenarios, the cross-domain management function unit may further provide lifecycle management of the sub-network, deployment of the sub-network, fault management of the sub-network, performance management of the sub-network, configuration management of the sub-network, provisioning of the sub-network, optimization function of the sub-network, translation of network intentions (Intent-CSPs) of service producers of the sub-network or network intentions (Intent-CSCs) of service consumers of the sub-network, and the like. The sub-network here consists of a plurality of small sub-networks, which may be network slicing sub-networks.

A Domain management function (Domain-MnF), also called a Network Management Function (NMF) or a network element management function. For example, the domain management function unit may be an element management entity such as a wireless automation engine (mbe), an Element Management System (EMS), a network function management service provider (NFMS _ P), and the like.

Wherein the domain management function unit provides one or more of the following functions or management services: lifecycle management of a sub-network or network element, deployment of a sub-network or network element, fault management of a sub-network or network element, performance management of a sub-network or network element, provisioning of a sub-network or network element, optimization function of a sub-network or network element, and translation of an Intent-to-NOP (Intent-to-NOP) of a sub-network or network element, and the like. A sub-network here comprises one or more network elements. The sub-networks may also comprise sub-networks, i.e. one or more sub-networks constitute one larger sub-network.

Optionally, the sub-network may also be a network slicing sub-network. The Domain management system may be a network slice sub-network management Function (NSSMF), a Domain management data analysis Function (Domain MDAF), a Domain-organization network Function (SON Function), a Domain intention management Function (Intent driver MnS), and the like.

Wherein, the domain management functional unit can be classified according to the following modes, including:

the classification by network type can be divided into: an access network Domain management function unit (RAN-Domain-MnF), a core network Domain management function unit (CN-Domain-MnF), a transport network Domain management function unit (TN-Domain-MnF), and the like. It should be noted that the domain management function unit may also be a domain network management system, which may manage one or more of an access network, a core network, or a transport network;

the classification by administrative regions can be divided into: and a domain management function unit in a certain region, such as a shanghai domain management function unit, a beijing domain management function unit, and the like.

The network element is an entity providing network services, and includes a core network element, an access network element, and the like. Wherein, the core network element includes: an access and mobility management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), a network data analysis unit (NWDAF), a network Repository unit (NF) and a gateway, etc. The access network element comprises: a base station (e.g., a gbb, eNB), a Central Unit Control Plane (CUCP), a Central Unit (CU), a Distributed Unit (DU), a Central Unit User Plane (CUUP), and so on.

Wherein, the network element may provide one or more of the following management functions or management services: the method comprises the following steps of network element life cycle management, network element deployment, network element fault management, network element performance management, network element guarantee, network element optimization function, network element intention translation and the like.

The following description will be made in conjunction with specific embodiments.

Referring to fig. 6, fig. 6 is a flowchart illustrating a mobility parameter configuration method according to an embodiment of the present disclosure. The mobility parameter configuration method in fig. 6 is implemented by interaction between a first network management device and a second network management device. For convenience of understanding, the first network management device described in this embodiment may be a cross-domain management function (e.g., NMS) in fig. 5, and the second network management device may be a domain management function (e.g., EMS) in fig. 5. The method may comprise the steps of:

s601, the first network management device determines a mobility optimization attribute, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a radio link of a secondary cell fails and/or an imminent radio link fails. The first network management device, as a management service consumer, determines mobility optimization attributes (MRO attributes). In this embodiment, the first network management device may determine, in addition to the conventional mobility optimization attribute, the corresponding mobility optimization attribute for the case where the radio link of the secondary cell fails in the scenario of multilink data transmission and the case where the radio link is imminent in the scenario of successful handover, so as to implement MRO optimization in the two scenarios.

It should be noted that the mobility optimization attribute is a parameter for a Mobility Robustness Optimization (MRO) function, and the MRO function may be implemented on one or more nodes of a base station, a cell, a base station CU, a base station DU, a cell on the base station CU, a cell on the base station DU, or a sub-network management node.

The mobility optimization attribute determined by the first network management device is a mobility optimization attribute of a network node, and the network node may be one or more of a cell, a base station CU, a base station DU, a cell on the base station CU, and a cell on the base station DU, which is not limited in this embodiment.

It should be noted that the MRO optimization described in this embodiment of the present application includes optimization of mobility parameters (for example, cell-specific paradox CIO) in a secondary cell radio link failure scenario caused by a too early, too late, or ping-pong scenario, and optimization of mobility parameters, beam parameters (for example, Qin and Qout of beam detection), radio link monitoring parameters (for example, radio link timestamps T310 and T312, radio link control RLC retransmission times, and the like), random access resources (for example, random access resources of beams, downlink signal strength thresholds of supplementary carriers, and the like) in an imminent radio link failure scenario in a handover success scenario.

The cell-level mobility optimization attributes corresponding to the cell-level optimization are described in detail below.

The mobility optimization attribute for the cell level may include one or more of a first policy parameter, a first target parameter, and a first control parameter. The first strategy parameters comprise strategies corresponding to the condition of radio link failure of the secondary cell in a multi-link data transmission scene and the condition of impending radio link failure in a scene of successful switching. Fig. 2b and the corresponding description may be referred to for the case of the radio link failure of the secondary cell in the scenario of multilink data transmission, and fig. 3 and the corresponding description may be referred to for the case of the impending radio link failure in the scenario of successful handover, which is not described herein again.

The first policy parameters may include: one or more of a cell identity (cell local ID), a handover trigger defining parameter, a handover adjustment policy parameter, an optimization period, or a handover optimization policy parameter.

The cell identifier is used for indicating a cell to be configured with the mobility optimization attribute. The cell identifier may be one or more of a Physical Cell Identifier (PCI), a global cell identifier (CGI), a name of a cell (cell name), or an identifier of a cell (cell ID), which is not limited in this embodiment. For example, if the cell identifier in the first policy parameter is cell 1(PCI 1), this means that the first network management device determines the mobility optimization attribute of cell 1.

The handover trigger limiting parameter includes one or more of a maximum handover trigger deviation (maximum handover trigger), a minimum handover trigger change time (minimum time between trigger change), a maximum SN change trigger deviation (maximum SN change trigger), and a minimum SN change trigger change time (minimum time between SN change trigger change), which is not limited in this embodiment.

The maximum handover trigger offset represents a maximum offset of the handover trigger parameter, that is, a maximum adjustment value of a Cell Index Offset (CIO), for example, the maximum adjustment value is 10 dB. The larger the CIO value of the cell is, the more difficult the user is to switch to the adjacent cell. For example, if it is necessary to reduce the too late handover, the CIO value of the cell may be reduced, and the reduced degree refers to the maximum handover trigger offset described in this embodiment.

Wherein, the minimum handover trigger modification time represents the minimum time for updating the handover trigger parameter, i.e. represents the minimum time for adjusting the CIO. That is, the minimum handover trigger change time represents the minimum time interval between two handover trigger parameter updates for controlling the stability and convergence of the MRO algorithm.

The maximum SN replacement trigger deviation represents a maximum deviation of a trigger parameter for SN replacement, that is, a maximum adjustment value of the CIO for SN replacement, and the maximum adjustment value is, for example, 10 dB. For example, if it is necessary to reduce the too late SN replacement, the SN or the CIO of the cell under the SN may be adjusted to reduce the SN or the CIO value of the cell under the SN, and the reduced degree refers to the maximum SN replacement trigger offset described in this embodiment. The first network management device is beneficial to avoiding the conditions of early (SN change topo early) auxiliary node replacement, late (SN change topo late) auxiliary node replacement, error (SN change topo wreng cell) auxiliary node replacement and the like by determining the maximum SN replacement triggering deviation, thereby avoiding the problem of auxiliary cell wireless link caused by auxiliary node replacement.

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

The minimum SN replacement trigger change time represents a minimum time for updating the SN replacement trigger parameter, that is, represents a minimum time for adjusting the CIO of the SN replacement, that is, the minimum SN replacement trigger change time represents a minimum time interval between two SN replacement trigger parameter updates. Wherein the minimum SN change trigger change time is used to control the stability and convergence of the MRO algorithm for SN change.

The switching adjustment strategy parameters comprise one or more of adjustment parameters of cell individual offset CIO, beam parameters, wireless link monitoring parameters and random access resource parameters. The adjustment parameters of the individual cell offset CIO include parameters such as CIO adjustment range maximum value co-frequency MRO, CIO adjustment range minimum value co-frequency MRO, CIO adjustment range maximum value inter-frequency MRO, and CIO adjustment range minimum value inter-frequency MRO. The beam parameters include parameters such as the maximum/minimum of Qin, the maximum/minimum of Qout, etc. for beam detection. The radio link monitoring parameters include parameters such as maximum/minimum value of radio link monitoring timestamp T310, maximum/minimum value of T312, maximum/minimum value of number of radio link control RLC retransmissions, and the like. The random access resource parameters include parameters such as a maximum value/a minimum value of a beam downlink signal strength Threshold (e.g., RSRP Threshold SSB, RSRP Threshold CSIRS), a downlink signal strength Threshold of a supplementary carrier (e.g., RSRP Threshold SSB-SUL), and the like.

And the same-frequency MRO of the CIO adjustment range maximum value represents the maximum value of the same-frequency MRO optimized CIO adjustment, and the same-frequency MRO of the CIO adjustment range minimum value represents the minimum value of the same-frequency MRO optimized CIO adjustment. That is, the co-frequency MRO of the maximum value of the CIO adjustment range and the co-frequency MRO of the minimum value of the CIO adjustment range define the adjustment range of the CIO during the co-frequency handover.

For example, the first network management device may determine that the maximum value of intra-frequency MRO optimization CIO adjustment is 5dB, and the minimum value of intra-frequency MRO optimization CIO adjustment is-5 dB. Correspondingly, when the first network device or the second network device adjusts the CIO, the adjustment range of the CIO is between-5 dB and 5 dB.

The maximum value of the CIO adjustment range, the pilot frequency MRO, the minimum value of the CIO adjustment range, the pilot frequency MRO and the minimum value of the CIO adjustment range are respectively equal to or greater than the maximum value of the CIO adjustment range, and the pilot frequency MRO, the minimum value of the CIO adjustment range, the minimum value of the pilot frequency MRO and the minimum value of the CIO adjustment range are respectively equal to or greater than the maximum value of the CIO adjustment range. That is, the maximum value pilot frequency MRO of the CIO adjustment range and the minimum value pilot frequency MRO of the CIO adjustment range define the adjustment range of the CIO at pilot frequency handover.

For example, the first network management device may determine that the maximum value of the inter-frequency MRO optimization CIO adjustment is 10dB and the minimum value of the inter-frequency MRO optimization CIO adjustment is-10 dB. Correspondingly, when the first network device or the second network device adjusts the CIO, the adjustment range of the CIO is between-10 dB and 10 dB.

The MRO optimization period indicates a period for performing MRO statistics and optimization. That is, the MRO optimization period indicates how often the first network device or the second network device performs MRO statistics and optimization.

The handover optimization strategy parameters include one or more parameters such as an optimization triggering threshold corresponding to the radio link failure of the secondary cell, an optimization triggering threshold corresponding to the impending radio link failure, and the like. Specifically, the handover optimization strategy parameters include one or more parameters such as an abnormal handover ratio threshold, a handover early optimization ratio threshold, a handover late optimization ratio threshold, an abnormal SN replacement ratio threshold, an SN replacement early optimization ratio threshold, an SN replacement late optimization ratio threshold, a ping-pong ratio threshold, an SN replacement ping-pong ratio threshold, a near-RLF ratio threshold, and a beam failure (beam failure) ratio threshold.

Wherein the abnormal switching comprises switching too early and switching too late. The abnormal switching ratio can be expressed as: the ratio of the sum of the number of switching earliest times and the number of switching latest times to the total number of switching times, that is, the abnormal switching ratio is (number of switching earliest times + number of switching latest times)/total number of switching times. The abnormal switching ratio threshold defines the maximum value of the abnormal switching ratio. That is, if the abnormal switching ratio of the system is greater than the abnormal switching ratio threshold, MRO optimization is triggered.

Wherein the handoff early optimization scaling threshold defines a maximum value of the handoff early scaling. That is, if the system's handoff early proportion is greater than the handoff early optimization proportion threshold, then MRO optimization is triggered.

Wherein the handover too late optimization scaling threshold defines a maximum value of the handover too late scaling. That is, if the too-late handover ratio of the system is greater than the too-late handover optimization ratio threshold, MRO optimization is triggered.

Wherein the abnormal SN replacement comprises SN switching too early and SN switching too late. Then the abnormal SN replacement ratio can be expressed as: the ratio of the sum of the SN early switching times and the SN late switching times to the total SN switching times, i.e., the abnormal SN replacement ratio (SN early switching times + SN late switching times)/total SN switching times. The abnormal SN replacement ratio threshold defines the maximum value of the abnormal SN replacement ratio. That is, if the abnormal SN replacement ratio of the system is greater than the abnormal SN replacement ratio threshold, MRO optimization is triggered.

Wherein the SN replacement premature optimization scaling threshold defines a maximum value of the SN replacement premature scaling. That is, if the system's SN replacement premature ratio is greater than the SN replacement premature optimization ratio threshold, then MRO optimization is triggered.

Wherein, the SN replacement too-late optimization proportion threshold limits the maximum value of the SN replacement too-late proportion. That is, if the SN change too late proportion of the system is greater than the SN change too late optimization proportion threshold, MRO optimization is triggered.

It can be understood that, the above abnormal SN change ratio threshold, SN change premature optimization ratio threshold, and SN change late optimization ratio threshold are mainly for the problem that the secondary cell radio link fails due to SN change in the scenario of multilink data transmission, and by determining the above three types of MRO attributes, it is beneficial to reduce the probability that the secondary cell radio link fails due to SN change too early, SN change too late, and the like.

Wherein, the ping-pong ratio threshold limits the maximum value of the ping-pong handover ratio. The ping-pong handover ratio is a ratio of the ping-pong handover times to the total handover times, i.e., the ping-pong handover ratio is the ping-pong handover times/the total handover times. That is, if the ping-pong handover ratio of the system is greater than the ping-pong ratio threshold, the MRO optimization is triggered.

Wherein, the SN replacing ping-pong ratio threshold limits the maximum value of the SN replacing ping-pong ratio. The SN replacement ping-pong ratio is a ratio of the SN replacement ping-pong frequency to the total SN replacement frequency, i.e., the SN replacement ping-pong switching ratio is the SN replacement ping-pong frequency/the total SN replacement frequency. That is, if the SN change ping-pong ratio of the system is greater than the SN change ping-pong ratio threshold, the MRO optimization is triggered.

Wherein the near-RLF ratio threshold defines a maximum value of the near-RLF ratio. The near-RLF ratio is a ratio of the number of times of radio link failure is imminent to the number of times of successful handover, i.e., the near-RLF ratio is the number of times of radio link failure is imminent/the number of times of successful handover. That is, in a successful handover scenario, if the near-RLF ratio reaches the near-RLF ratio threshold, MRO optimization is triggered.

Wherein the beam failure (beam failure) ratio threshold defines the maximum value of the beam failure ratio. The beam failure ratio is a ratio of the number of beam failures to the number of successful handovers, i.e., the beam failure ratio is the number of beam failures/the number of successful handovers. That is, in the handover success scenario, if the beam failure ratio reaches the beam failure ratio threshold, MRO optimization is triggered. The first target parameter may include one or more of a cell identifier, a maximum number of handover triggers, a handover trigger optimization target parameter, and the like. The first target parameter may be understood as a target that is desired or required by the MRO.

The cell identifier is used for indicating a cell to be configured with the mobility optimization attribute. That is, the cell identification indicates the cell that is expected or needed to achieve the target. For a detailed description of the cell identifier, please refer to the description of the foregoing embodiments, which is not described herein again.

The maximum number of handover triggers is used to limit the number of changes of handover trigger parameters, and for better algorithm convergence, the number of changes of handover trigger of a cell cannot be too large, i.e. cannot exceed the maximum number of handover triggers.

For example, the ping-pong handover ratio of cell 1 exceeds the ping-pong ratio threshold more times, and MRO optimization is triggered each time the ping-pong handover ratio exceeds the ping-pong ratio threshold. However, if the number of times of triggering MRO optimization by handover is too large, a large amount of management overhead may be added to the system, so the number of times of triggering MRO optimization needs to be limited to not exceed the maximum number of times of triggering by handover.

The handover trigger optimization target parameters comprise parameters such as an abnormal RLF ratio, a ping-pong handover frequency ratio, a handover early failure rate, a handover late call drop rate, an abnormal SCG failure ratio, an SN replacement early failure rate or an SN replacement late call drop rate.

The abnormal RLF comprises RLF caused by switching too early and RLF caused by switching too late. Then the abnormal RLF ratio can be expressed as: the ratio of the sum of the RLF caused by premature handover and the RLF caused by late handover to the total number of handovers, i.e. the abnormal RLF ratio (RLF caused by premature handover + RLF caused by late handover)/total number of handovers. The abnormal RLF proportion is an optimization target of MRO, namely, the abnormal RLF proportion is favorably reduced through MRO optimization.

The ping-pong switching frequency ratio is a ratio of the ping-pong switching frequency to the total switching frequency, that is, the ping-pong switching frequency ratio is the ping-pong switching frequency/the total switching frequency. The ping-pong switching frequency proportion is an optimization target of MRO, that is, the ping-pong switching frequency proportion is favorably reduced through MRO optimization.

The premature handover failure rate is a ratio of the number of premature handover times to the total number of handover times, that is, the premature handover failure rate is the number of premature handover times/the total number of handover times. That is, the handover early failure rate is an optimization target of MRO, that is, the handover early failure rate is favorably reduced by MRO optimization.

The too-late handover drop rate is a ratio of the too-late handover times to the total handover times, that is, the too-late handover drop rate is the too-late handover times/the total handover times. The too-late handover call drop rate is an optimization target of MRO, that is, the too-late handover call drop rate is favorably reduced through MRO optimization.

The abnormal SCG failure comprises SCG failure caused by SN replacement early and SCG failure caused by SN replacement late. Then the abnormal SCG failure rate can be expressed as: the sum of SCG failure caused by too early SN replacement and SCG failure caused by too late SN replacement is a ratio of the abnormal SCG failure rate (SCG failure caused by too early SN replacement + SCG failure caused by too late SN replacement)/the total number of times of switching. The abnormal SCG failure rate is the optimization target of MRO, that is, the abnormal SCG failure rate is reduced by the MRO optimization of SN replacement.

The SN replacement premature failure rate is a ratio of the SN replacement premature times to the total SN replacement times, that is, the SN replacement premature failure rate is SN replacement premature times/total SN replacement times. That is, the early failure rate of SN replacement is an optimization target of MRO of SN replacement, that is, the early failure rate of SN replacement is favorably reduced by MRO optimization.

The SN replacement too-late call drop rate is proportional to the number of times of the too-late SN replacement and the total number of times of the SN replacement, that is, the SN replacement too-late call drop rate is equal to the number of times of the too-late SN replacement/the total number of times of the SN replacement. The SN replacement too-late call drop rate is an optimization target of the MRO of the SN replacement, namely, the SN replacement too-late call drop rate is favorably reduced through the MRO optimization.

The first control parameter is also called a control switch of an MRO function, and two types of control switches are additionally arranged in the existing control switch of the MRO function in the embodiment of the application, including a mobility optimization function control switch for assisting the radio link failure of a cell and a mobility optimization function control switch for approaching the radio link failure.

The mobility optimization function control switch for the radio link failure of the secondary cell and the mobility optimization function control switch for the impending radio link failure can be both of Boolean (Boolean) data types. For example, the mobility optimization function that indicates the radio link failure of the secondary cell is turned on by on, and the mobility optimization function that indicates the radio link failure of the secondary cell is turned off by off. For another example, the mobility optimization function that is imminent radio link failure is turned on by on, and the mobility optimization function that is imminent radio link failure is turned off by off. Optionally, the control switch of the MRO function may also be an Enumeration (Enumeration) data type, for example, yes or no, or may also be another data type that may indicate a switch, which is not limited in this embodiment.

The mobility optimization function control switch for the radio link failure of the secondary cell may also be referred to as an MR-DC MRO function switch or an SN Change MRO function switch, and is used to control the base station to perform MRO optimization when an SN Change failure occurs. For example, in an MR-DC scenario, the base station may detect the number of SN changes too early, the number of SN changes too late, and the total number of handovers. If the SN replacement fails, for example, the SN replacement is too early, the MR-DC MRO function switch controls the MRO function to be started. When the MR-DC MRO function switch controls the MRO function to be in an on state and the system reaches an MRO triggering condition, MRO optimization is triggered, for example, switching parameters are modified.

The mobility optimization function control switch for impending radio link failure may also be referred to as a success handover optimization function switch, and the success handover optimization function switch is used for controlling the base station to execute MRO optimization when a mobility problem of impending radio link failure occurs in a handover success scene. For example, in a handover success scenario, the base station may detect the number of links of near-RLF. And if the link quantity of the near-RLF is larger, the success handover optimization function switch controls the opening of the MRO function to trigger the MRO optimization.

The base station level mobility optimization attributes corresponding to the base station level optimization are described in detail below.

The mobility optimization attribute at the base station level may include a second policy parameter, a second target parameter, a second control parameter, and the like.

The second strategy parameters comprise strategies corresponding to the condition of radio link failure of the secondary cell in a multilink data transmission scene and the condition of impending radio link failure in a scene of successful switching. Specifically, the second policy parameter may include: network device identification, abnormal coverage policy parameters, abnormal radio link policy parameters, etc.

The network device identifier may be a base station identifier (base station ID) or a base station name, and is used to indicate different network devices (such as a base station, etc.), which is not limited in this embodiment. For example, the base station in the second policy parameter is identified as base station 1 (base station ID1), which means that the first network management device determines the mobility optimization attribute of base station 1.

The abnormal coverage policy parameter includes one or more parameters such as an abnormal coverage threshold, a Reference Signal Receiving Power (RSRP) threshold of the serving cell, and a Reference Signal Receiving Power threshold of the neighboring cell, which is not limited in this embodiment.

The abnormal coverage threshold represents the maximum value of the abnormal coverage ratio between the serving cell and the neighboring cell in an MRO optimization period. If the abnormal coverage ratio between the service cell and the adjacent cell exceeds the abnormal coverage threshold in an MRO optimization period, the MRO is not triggered. That is, since the abnormal coverage threshold indicates coverage performance rather than mobility performance, even if the abnormal coverage ratio of the system exceeds the abnormal coverage threshold, the mobility performance optimization, i.e., MRO optimization, is not triggered.

The reference signal received power threshold of the serving cell indicates that when the terminal device has RLF or fails to switch, the RLF report after successful reconstruction includes an RSRP value of the serving cell that is smaller than the threshold, and an RSRP value of the neighboring cell that is also smaller than the threshold, it is considered that abnormal coverage exists. That is, the reference signal received power threshold of the serving cell may indicate whether there is abnormal coverage. Optionally, if the reference signal received power threshold of the serving cell indicates that there is abnormal coverage and the abnormal coverage ratio exceeds the abnormal coverage threshold, the MRO optimization is not triggered.

The reference signal received power threshold of the neighboring cell indicates that, when the terminal device has RLF or fails to switch, the RLF report after successful re-establishment contains an RSRP value of the serving cell that is less than the threshold, and the RSRP of the neighboring cell is also less than the threshold, then it is considered that abnormal coverage exists. That is, the reference signal received power threshold of the neighboring cell may indicate whether there is abnormal coverage. Optionally, if the reference signal received power threshold of the neighboring cell indicates that there is abnormal coverage, and the abnormal coverage ratio exceeds the abnormal coverage threshold, the MRO optimization is not triggered.

The abnormal radio link strategy parameters comprise one or more parameters such as abnormal radio link failure ratio threshold, network equipment group switching failure ratio threshold, impending radio link failure ratio threshold and the like.

The abnormal radio link failure is also referred to as abnormal RLF, and includes abnormal RLF caused by early handover and abnormal RLF caused by late handover. The abnormal RLF ratio can be expressed as: the ratio of the sum of the abnormal RLF caused by early handover and the abnormal RLF caused by late handover to the total number of handovers, i.e. the ratio of the abnormal RLF to the total number of handovers is (number of abnormal RLFs caused by early handover + number of abnormal RLFs caused by late handover)/total number of handovers. And if the abnormal RLF ratio of the system is larger than the abnormal RLF ratio threshold, triggering MRO optimization.

The network device group switching failure is also called as an abnormal SCG failure, and includes SCG failure caused by too early SN replacement and SCG failure caused by too late SN replacement. The abnormal SCG failure rate can be expressed as: the sum of SCG failure caused by too early SN replacement and SCG failure caused by too late SN replacement is a ratio of the abnormal SCG failure rate (SCG failure rate caused by too early SN replacement + SCG failure rate caused by too late SN replacement)/total switching rate. And if the abnormal SCG failure ratio of the system is greater than the abnormal SCG failure ratio threshold, triggering MRO optimization.

The ratio of the number of times of near-RLF to the number of times of successful handover, that is, the ratio of the number of times of near-RLF to the number of times of successful handover. The near-RLF ratio threshold defines a maximum value of the near-RLF ratio, that is, in a handover success scenario, if the near-RLF ratio reaches the near-RLF ratio threshold, MRO optimization is triggered.

It is to be noted that the second policy parameter may also comprise the first policy parameter in the cell-level mobility optimization attribute as described in the previous embodiment. That is to say, the second policy parameter may further include one or more parameters such as a cell identifier, a handover trigger limiting parameter, a handover adjustment policy parameter, an optimization period, or a handover optimization policy parameter, and the description of each parameter refers to the description in the foregoing embodiments, which is not described herein again.

The second objective parameter may include one or more of network device identification, abnormal coverage ratio, handover trigger optimization objective parameter, etc. The description of the network device identifier is the same as the description and the function of the network device identifier in the second policy parameter, and is not repeated here.

The abnormal coverage ratio represents the abnormal coverage ratio between the serving cell and the neighboring cell in one MRO optimization period. For example, the ratio of the overlapping coverage area between the serving cell and the neighboring cell to the sum of the coverage areas formed by the serving cell and the neighboring cell may reflect the abnormal coverage ratio between the serving cell and the neighboring cell. The overlapping coverage area between the serving cell and the neighboring cell may be regarded as an abnormal coverage area.

The handover trigger optimization target parameters comprise one or more parameters such as abnormal RLF proportion, abnormal SCG failure proportion, near-RLF proportion and the like. The description of the abnormal RLF ratio and the abnormal SCG failure ratio may refer to the detailed description of the first target parameter in the foregoing embodiments, and is not repeated herein.

The near-RLF ratio may be expressed as a ratio of the near-RLF times to the successful switching times, that is, the near-RLF ratio is near-RLF times/successful switching times. The near-RLF ratio is the optimization target of MRO, namely, the near-RLF ratio is favorably reduced through MRO optimization.

The second control parameter is also called a control switch of the MRO function, and in the embodiment of the present application, two types of control switches are added in the existing MRO function control switch, including a mobility optimization function control switch for assisting a cell radio link failure and a mobility optimization function control switch for an imminent radio link failure. For the detailed description of the two types of switches, reference may be made to the detailed description of the first control parameter, which is not repeated herein.

Optionally, the MRO optimization described in this embodiment may also be subnet-level optimization. The mobility optimization attribute of the subnet level corresponding to the optimization of the subnet level is the same as the mobility optimization attribute of the base station level, and the specific description may refer to the description of the mobility optimization attribute of the base station level, which is not described herein again.

S602, the first network management device sends a mobility optimization attribute to the second network management device; correspondingly, the second network management device receives the mobility optimization attribute sent by the first network management device.

After determining the mobility optimization attribute, the first network management device may send the mobility optimization attribute to the second network management device. For example, the first network management device sends network node information to the second network management device through a northbound interface, where the network node information includes the mobility optimization attribute. The network node may be a network function node such as a base station, a cell, a base station CU or, a base station DU, a base station CU cell or a base station DU cell, etc.

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

Optionally, the second network management device receives an object creation notification sent by the first network management device, where the object creation notification carries the mobility optimization attribute of the network node, and the second network management device creates a management object of the network node instance according to the received object creation notification. The network node may be a network function node, such as a base station, a cell, a base station CU, a base station DU, a base station CU cell, or a base station DU cell, and the second network management device configures a mobility optimization attribute in a management object of the network node.

The object creation notification is used for enabling the first network management device to create corresponding management objects and perform corresponding configuration on the management objects. Optionally, the object creation notification further includes 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.

For example, the management service consumer sends a create MOI operation to the management service producer, which carries the relevant attributes of the mobility optimization function. After the operation is created, the management service consumer may send get MOI Attributes operation to the management service producer to actively obtain the configuration parameters of a certain object. Alternatively, the management service consumer may also send a modify MOI Attributes operation to the management service producer to modify the parameters of an object. Alternatively, the management service consumer may also send delete MOI Attributes to the management service producer to delete an object. The operation may be to continue using an existing operation message, or may also use a newly defined operation message, which is not limited in this embodiment.

Optionally, after the second network management device receives the mobility optimization attribute in 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 adjusts the handover parameter in the process of switching the terminal device from the first network device to the second network device according to the mobility optimization attribute under the condition that the radio link of the secondary cell fails and/or is imminent to fail.

The sending, by the second network management device, the mobility optimization attribute to the second network device may be implemented through a private interface between the second network management device and the second network device, or the like.

For example, the management service consumer determines the mobility optimization attributes, which are issued by the management service producer to the managed base stations 1 and 2. And the base station 1 and the base station 2 carry out corresponding parameter configuration according to the received mobility optimization attribute. If the handover is successful in the process of handover of the terminal device from the base station 1 to the base station 2, but the near-RLF ratio exceeds the near-RLF ratio threshold in the mobility optimization attribute, the base station 2 triggers MRO optimization to optimize mobility parameters, beam parameters, and the like.

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

s603, the first network management equipment receives a response message sent by the second network management equipment; correspondingly, the second network management device sends a response message to the first network management device.

Specifically, the second network management device may perform corresponding configuration according to the mobility optimization attribute, and after the configuration, the second network management device sends a response message to the first network management device.

Optionally, the response message may be an existing Create MOI response operation message or a newly defined operation message, which is not limited in this embodiment.

Optionally, the response message may carry an identifier of the management object and/or an identifier of the second network management device. For example, carrying a Distinguished Name (DN). The identifier of the management object may be created by the first network management device in a Create MOI request and sent to the second network management device.

Optionally, the response message may further include one or more of a message that the configuration is successful, a message that the configuration is failed, or information that the configuration is not possible, which is not limited in this embodiment. Correspondingly, the configuration state of the second network management device includes successful configuration, failed configuration or incapability of configuration. For example, if the mobility optimization attribute of the second network management device is successfully configured, the response message sent by the second network management device to the first network management device is a message that the configuration is successful.

Optionally, the response message may also carry a reason of configuration failure or incapability of configuration. For example, the response message sent by the second network management device to the first network management device is a configuration failure message, and the response message further includes a reason for the configuration failure.

The embodiment of the 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 may send a mobility optimization attribute to the second network management device, where the mobility optimization attribute is used to indicate an attribute configured in the case of a radio link failure and/or an imminent radio link failure of the secondary cell. That is to say, the method realizes the management of mobility parameter optimization under the multi-link data transmission scene and the switching success scene, and ensures the mobility performance under the two scenes.

The following describes in detail the management flow of performance indexes between the network management device and the network devices in the scenario of multilink data transmission and in the scenario of successful handover.

Referring to fig. 7, fig. 7 is a schematic flowchart illustrating a process of managing mobility optimization performance data by a first network management device and a second network management device according to an embodiment of the present application. The process is realized by interaction between a first network management device and a second network management device, and comprises the following steps:

s701, the first network management equipment sends a request message to the second network management equipment, wherein the request message is used for requesting mobility optimization performance data corresponding to the mobility optimization attribute and/or requesting an indication of the mobility optimization performance data corresponding to the mobility optimization attribute;

the request message sent by the first network management device to the second network management device may be a data subscription operation message, where the data subscription operation message is used to request mobility optimization performance data corresponding to the mobility optimization attribute and/or request an indication (notify) of the mobility optimization performance data corresponding to the mobility optimization attribute.

The data subscription operation message may carry information of the network node. The information of the network node may be information of various network nodes such as a base station, a cell, a base station CU or, a base station DU, a base station CU cell, or a base station DU cell. The data subscription operation message is for requesting mobility optimized performance data of the network node and/or an indication of mobility optimized performance data of the network node.

Optionally, the data subscription operation message may also carry identification information of the slice, for example, identification information of NSSAI, S-NSSAI, NSSI, and the like. The subscription operation is for requesting the slice-specific mobility optimization performance data and/or an indication of the slice-specific mobility optimization performance data.

For example, a first network management device sends a data subscription operation message of a network node to a second network management device, where the data subscription operation carries mobility optimization performance data of a request network node. The network node may be a network function node, such as one or more of a base station, a cell, a base station CU or, a base station DU, a base station CU cell or a base station DU cell, among others.

Optionally, the data subscription operation message further includes a period for sending the performance data, a trigger threshold, and the like.

Optionally, the data subscription operation message indicates specific mobility optimization performance data, for example, may indicate one or more of performance data related to multilink data transmission and performance data related to handover success, which is not limited in this embodiment.

It should be noted that the data subscription operation message may be an existing subscribe operation message, or may also define a new message, which is not limited in this embodiment.

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

The feedback information received by the first network device may include 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 in the case of a radio link failure and/or an imminent radio link failure of the secondary cell. That is, the feedback information may include only the specific performance data, may include only the indication of the performance data, and may include the specific performance data and the indication of the performance data.

In one implementation, the feedback information may include mobility optimization performance data corresponding to the mobility optimization attribute in case of a radio link failure and/or an imminent radio link failure of the secondary cell.

And the mobility optimization performance data corresponding to the mobility optimization attribute is a performance index for switching the network element managed by the second network management device. The mobility optimization data may include, but is not limited to: the total number of times of switching, the total number of times of switching failure, the total number of times of switching of the auxiliary node, the total number of times of switching failure of the auxiliary node, the number of times of generating ping-pong effect, the number of times of updating too early of the auxiliary node, the number of times of updating too late of the auxiliary node, the number of times of switching to a wrong cell by the auxiliary node, the number of times of ping-pong switching of the auxiliary node, the number of times of failure of an impending wireless link or the number of times of failure of a beam, etc.

The total number of times of handover events (number of handover events) is the number of times of handover events counted in an MRO optimization period, and RATs are not distinguished. That is, the total number of times of occurrence of handover may be the number of handover events of handover in the same system (number of inter-RAT handover events), or the number of handover events of handover in different systems (number of inter-RAT handover events).

It should be noted that intra-RAT refers to handover in the same system, such as handover between LTE and LTE, and handover between NR and NR. The inter-RAT refers to handover between different systems, such as handover between LTE and NR, and handover between LTE and NR in NG-RAN architecture, which is not limited in this embodiment.

Wherein, the total number of handover failures (number of handover failures) is the number of handover failures counted in an MRO optimization period, and RATs are not distinguished. That is, the total number of handover failures may be the number of handover failures under the intra-RAT (number of intra-RAT handover failures) or the number of handover failures under the inter-RAT (number of inter-RAT handover failures).

Optionally, the total number of handover failures may be the number of handover early failures under inter-RAT (number of inter-RAT handover failures), the number of handover late failures under intra-RAT (number of inter-RAT handover failures), the number of handover to error cells under intra-RAT (number of inter-RAT handover failures to while cells), the number of handover early failures under inter-RAT (number of inter-RAT handover failures), the number of handover late failures under inter-RAT (number of inter-RAT handover failures), or the number of unnecessary handover failures (number of unnecessary handover RATs).

In order to embody the performance index of the network element performing the handover after configuring the MRO optimization attribute according to the embodiment of the present application, the following will introduce mobility optimization performance data of a multi-link data transmission scenario and mobility optimization performance data of a handover success scenario, which may specifically include: the total number of times of switching of the auxiliary node, the total number of times of switching failure of the auxiliary node, the number of times of generating ping-pong effect, the number of times of updating too early of the auxiliary node, the number of times of updating too late of the auxiliary node, the number of times of switching the auxiliary node to a wrong cell, the number of times of failure of an impending wireless link, and the like.

The total number of SN change events (number of SN change events) switched by the auxiliary node is the number of SN change events counted in one MRO optimization period. Optionally, the total number of times of the secondary node handover may be the total number of times of the secondary node handover under the inter-RAT (number of inter-RAT SN change events), or the total number of times of the secondary node handover under the intra-RAT (number of intra-RAT SN change events).

Wherein, the total number of switching failures of the auxiliary node (number of SN change failures) is the number of SN switching failures counted in one MRO optimization period. Optionally, the total number of times of the failure of the secondary node handover may be the total number of times of the secondary node handover under the inter-RAT (number of inter-RAT SN change failures), or the total number of times of the secondary node handover under the intra-RAT (number of intra-RAT SN change failures).

Wherein, the number of ping-pong effect generation (number of ping-pong ping pong) is the number of ping-pong handover generation counted in an MRO optimization period. Alternatively, the number of ping-pong effect may be the number of ping-pong handovers under the inter-RAT (number of inter-RAT handover ping pong), or the number of ping-pong handovers under the intra-RAT (number of intra-RAT handover ping pong).

The number of times of early update of the secondary node (number of SN to early HO failures) is the number of times of handover failures caused by early update of SNs counted in one MRO optimization period. Optionally, the number of times of the secondary node updating too early may be the number of times of handover failure caused by the secondary node updating too early under the inter-RAT (number of inter-RAT SN to early HO failures), or the number of times of handover failure caused by the secondary node updating too early under the intra-RAT (number of intra-RAT SN to early HO failures).

The number of times (number of SN top HO failures) of the secondary node that is updated too late is the number of times of handover failure caused by the SN updated too late counted in one MRO optimization period. Optionally, the number of too late secondary node updates may be the number of handover failures caused by too late secondary node updates under the inter-RAT (number of inter-RAT SN top HO failures), or the number of handover failures caused by too late secondary node updates under the intra-RAT (number of intra-RAT SN top HO failures).

The number of times (number of SN to wrong cells) that the secondary node switches to the wrong cell is the number of times that the SN is switched to the wrong cell counted in one MRO optimization period. Optionally, the number of times the secondary node switches to the wrong cell may be the number of times the secondary node switches to the wrong cell under the inter-RAT (number of inter-RAT SN to wlan cell), or the number of times the secondary node switches to the wrong cell under the intra-RAT (number of intra-RAT SN to wlan cell).

The number of ping-pong switching of the auxiliary node (number of SN change ping pong) is the number of SN change ping-pong counted in an MRO optimization period. Optionally, the ping-pong handover times of the secondary node may be the ping-pong change times of the secondary base station under the inter-RAT (number of inter-RAT SN change ping pong), or the ping-pong change times of the secondary node under the intra-RAT (number of intra-RAT SN change ping pong).

Wherein, the number of times of radio link failure (near-RLF) is the number of times of near-RLF counted in an MRO optimization period. Optionally, the number of times of imminent radio link failure may be the number of times of imminent radio link failure under the inter-RAT (number of inter-RAT near-RLF), or the number of times of imminent radio link failure under the intra-RAT (number of intra-RAT near-RLF).

Wherein, the number of Beam failures (number of Beam failures) is the number of Beam failures counted in an MRO optimization period.

In one implementation, the feedback information may not include the performance data, but only include an indication (e.g., notify ready) of mobility optimization performance data corresponding to the mobility optimization attribute. For example, a notify ready may be included in the feedback information, which may indicate the performance data requested by the request message.

Two procedures for managing MRO performance indicators are described below by way of two examples. One of the methods is to acquire mobility optimization performance data by triggering subscription through a first network management device, and the second network management device reports the mobility optimization performance data in a file-based manner. And the other is to trigger the measurement task and report mobility optimization performance data through second network management equipment, and the second network management equipment adopts a stream-based report.

In an example, please refer to fig. 8, and fig. 8 is a flowchart illustrating a procedure of managing MRO performance indicators by a first network management device and a second network management device according to an embodiment of the present application. The process is realized by interaction between a first network management device and a second network management device, and comprises the following steps:

s801, a first network management device sends subscription operation to a second network management device;

s802, the second network management device sends an indication message to the first network management device, wherein the indication message is used for indicating the readiness of file data;

s803, the first network management device sends a request message to the second network management device, where the request message is used to request to obtain available file data.

The subscription operation sent by the first network management device to the second network management device is used for subscribing the MRO performance index of the second network management device. For example, the first network management device may obtain a specific MRO performance index through the subscription operation.

Wherein, the subscription operation can carry the information of the network node. The information of the network node may be information of a base station, a cell, a base station CU, a base station DU, a base station CU cell or a base station DU cell. The subscription operation is for requesting transmission of mobility optimized performance data of the network node and/or an indication of mobility optimized performance data of the network node.

Optionally, the subscription operation may also carry identification information of the slice, for example, identification information such as NSSAI, S-NSSAI, NSSI, and the like. The subscription operation is to indicate a request for mobility optimized performance data for a specified slice and/or an indication of mobility optimized performance data for a specified slice.

For example, a first network management device sends a subscription operation of a network node to a second network management device, where the subscription operation carries mobility optimization performance data of the network node. The network node may be a network function node such as one or more of a base station, a cell, a base station CU, a base station DU, a base station CU cell or a base station DU cell.

Optionally, the subscription operation further includes a period for sending performance data, a trigger threshold, and the like.

Optionally, the subscription operation may carry an indication of a specific MRO performance index. For example, the subscription operation sent by the first network management device to the second network management device carries the first indication and/or the second indication. Wherein the first indication is used for indicating a performance index related to multi-link data transmission (such as a performance index related to SN change), and the second indication is used for indicating a performance index related to handover success (such as a performance index related to near-RLF).

Optionally, the subscription operation may use an existing subscribe operation message, or may define a new message, which is not limited in this embodiment.

After receiving the subscription operation sent by the first network management device, the second network management device may collect the relevant mobility optimization performance data, and record the relevant mobility optimization performance data in files (files). The second network management device may transmit an indication message indicating file data ready (file ready) to the first network management device. For example, the indication message sent by the second network management device may use an existing Notify Ready operation message, or may define a new message, which is not limited in this embodiment.

Optionally, the indication message (file ready operation) may carry an indication of a specific MRO performance indicator ready. For example, the indication message sent by the second network management device to the first network management device carries the first ready indication and/or the second ready indication. Wherein a first ready indication indicates that a performance indicator related to multilink data transmission (e.g., a SN change related performance indicator) is included in the file, and a second ready indication indicates that a performance indicator related to handover success (e.g., a near-RLF related performance indicator) is included in the file.

After receiving the indication information, the first network management device may send a request message to the second network management device, where the request message is used to request to acquire available file data (available files). The request message may use an existing list Available Files operation message, or may define a new message, which is not limited in this embodiment.

In an example, please refer to fig. 9, and fig. 9 is a schematic flowchart illustrating a procedure for managing an MRO performance indicator by a first network management device and a second network management device according to an embodiment of the present application. The process is realized by interaction between a first network management device and a second network management device, and comprises the following steps:

s901, a first network management device sends a measurement task creating operation to a second network management device;

s902, the second network management device sends a data stream connection establishment operation to the first network management device;

and S903, the second network management device sends the data stream to the first network management device.

Wherein the measurement tasks are used to collect the same measurement type for the same instance with different granularity periods. Subsequently, the first network management device may send the measurement work list to the second network management device, so that the second network management device establishes a corresponding measurement task data flow.

Optionally, the information of the network node may be carried in the measurement task creating operation. The information of the network node may be information of a base station, a cell, a base station CU or, a base station DU, a base station CU cell or a base station DU cell. The create measurement task operates to request the creation of a measurement connection of mobility optimized performance data of the network node.

Optionally, the measurement task creating operation may also carry identification information of the slice, for example, identification information such as NSSAI, S-NSSAI, NSSI, and the like. The create measurement task operates to request the creation of a measurement connection specifying mobility optimized performance data for a slice.

For example, a first network management device sends a measurement task creating operation of a network node to a second network management device, where the measurement task creating operation carries mobility optimization performance data of the network node. The network node may be a network function node such as one or more of a base station, a cell, a base station CU or, a base station DU, a base station CU cell or a base station DU cell, etc.

Optionally, the measurement task creating operation further includes a period for sending performance data, a trigger threshold, and the like.

Wherein, the measurement task operation can use the existing create measurement task job operation message. The measurement task list may use an existing list measurement task job message, or an existing create MOI operation message, or other newly defined messages, which is not limited in this embodiment.

Wherein the data flow connection establishment operation is to establish a data flow between the first network management device and the second network management device.

Optionally, the data stream connection establishment operation may carry a stream information list, where the stream information list includes a stream identifier, measurement management object DN information, and the like.

Optionally, the data stream connection establishment operation may use an existing examination streaming connection operation message, or define a new operation message, which is not limited in this embodiment.

Optionally, the data flow connection establishment operation may carry an indication of a specific MRO performance indicator. For example, the first indication and the second indication are carried in the data stream connection establishment operation sent by the first network management device to the second network management device. Wherein the first indication is used for indicating a performance index related to multi-link data transmission (such as a performance index related to SN change), and the second indication is used for indicating a performance index related to handover success (such as a performance index related to near-RLF).

The embodiment of the application provides a management process of performance indexes between network management equipment and network equipment in a multi-link data transmission scene and a switching success scene, and solves the management of mobility optimization performance data in the multi-link data transmission scene and the switching success scene. The management process is beneficial to enabling the first network management device to adjust the mobility optimization attribute according to the mobility optimization performance data, and therefore the switching failure rate of the user in the switching process is reduced.

The following describes related devices of the embodiments of the present application in detail with reference to fig. 10 to 13.

An embodiment of the present application provides a first network management device, and as shown in fig. 10, the first network management device 1000 may be used to implement a mobility parameter configuration method in the embodiment of the present application. The first network management device 1000 may include:

a processing unit 1001, configured to determine a mobility optimization attribute, where the mobility optimization attribute is used to indicate an attribute configured in a case where a secondary cell radio link fails and/or an imminent radio link fails;

a transceiving unit 1002, configured to send the mobility optimization attribute to the second network management device.

For a specific implementation manner, please refer to detailed descriptions in S601 and S602 in the embodiment of fig. 6, which are not described herein again.

In one implementation, the mobility optimization attribute includes a first policy parameter including one or more of: a handover trigger limit parameter, a handover adjustment policy parameter, an optimization period, or a handover optimization policy parameter.

For a specific implementation manner, please refer to the detailed description of the first policy parameter in the embodiment of fig. 6, which is not described herein again.

In one implementation, the mobility optimization attribute includes a first target parameter including one or more of: cell identity, maximum number of handover triggers or handover trigger optimization objective parameters. The handover trigger optimization target parameters comprise one or more of a radio link failure proportion of the secondary cell, an imminent radio link failure proportion, a ping-pong handover frequency proportion, a handover early failure rate or a handover late call drop rate.

For a specific implementation manner, please refer to the detailed description of the first target parameter in the embodiment of fig. 6, which is not repeated herein.

In one implementation, the mobility optimization attribute includes a first control parameter, and the first control parameter includes a mobility optimization function control parameter of a secondary cell radio link failure and/or a mobility optimization function control parameter of an imminent radio link failure.

For a specific implementation manner, please refer to the detailed description of the first control parameter in the embodiment of fig. 6, which is not repeated herein.

In one implementation, the mobility optimization attribute includes a second policy parameter that includes one or more of: a network device identification, an abnormal coverage policy parameter, or an abnormal radio link policy parameter. Wherein the abnormal coverage strategy parameter comprises one or more of an abnormal coverage threshold, a reference signal received power threshold of a serving cell or a reference signal received power threshold of an adjacent cell. The abnormal radio link strategy parameters comprise one or more of abnormal radio link failure ratio threshold, network equipment group switching failure ratio threshold or impending radio link failure ratio threshold.

For a specific implementation manner, please refer to the detailed description of the second policy parameter in the embodiment of fig. 6, which is not described herein again.

In one implementation, the mobility optimization attribute includes a second objective parameter including one or more of: network device identification, abnormal coverage proportion, or handover trigger optimization objective parameters. The handover trigger optimization target parameters comprise one or more of a secondary cell radio link failure proportion, a secondary cell handover failure proportion or an impending radio link failure proportion.

For a specific implementation, please refer to the detailed description of the second target parameter in the embodiment of fig. 6, which is not repeated herein.

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.

For a specific implementation manner, please refer to detailed descriptions of the first policy parameter, the first target parameter, the first control parameter, the second policy parameter, and the second target parameter in the embodiment of fig. 6, which are not described herein again.

In one implementation, the transceiving unit 1002 is further configured to receive a response message sent by the second network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

For a specific implementation manner, please refer to the detailed description in S603 in the embodiment of fig. 6, which is not repeated herein.

In one implementation, the transceiving unit 1002 is further configured to send a request message to the second network management device, where the request message is 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 transceiving unit 1002 is further configured to receive feedback information sent by the second network management device, where the feedback information includes 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 under the condition that a radio link of the secondary cell fails and/or an imminent radio link fails.

For a specific implementation manner, please refer to detailed descriptions in S701 and S702 in the embodiment of fig. 7, which are not repeated herein.

In one implementation, the mobility optimization performance data includes one or more of: the total times of switching the auxiliary nodes, the total times of switching failure of the auxiliary nodes, the times of generating ping-pong effect, the times of updating too early of the auxiliary nodes, the times of updating too late of the auxiliary nodes, the times of switching the auxiliary nodes to wrong cells or the times of failure of an impending wireless link.

For a specific implementation manner, please refer to detailed descriptions of the total number of times of switching of the secondary node, the total number of times of failure of switching of the secondary node, the number of times of generating a ping-pong effect, the number of times of updating too early of the secondary node, the number of times of updating too late of the secondary node, the number of times of switching of the secondary node to a wrong cell, or the number of times of failure of an imminent radio link in the embodiment of fig. 7, which is not described herein again.

In one implementation, the transceiving unit 1002 is further configured to:

sending a subscription operation to the second network management device;

receiving an indication message sent by the second network management device, wherein the indication message is used for indicating that the file data is ready;

and sending a request message to the second network management equipment, wherein the request message is used for requesting to acquire the available file data.

For a specific implementation manner, please refer to detailed descriptions in S801 to S803 in the embodiment of fig. 8, which are not repeated herein.

In one implementation, the transceiving unit 1002 is further configured to:

sending a measurement task creating operation to the second network management equipment;

receiving a data stream connection establishment operation sent by second network management equipment;

and receiving the data stream sent by the second network management equipment.

For a specific implementation manner, please refer to detailed descriptions in S901 to S903 in the embodiment of fig. 9, which are not described herein again.

In one implementation, the relevant functions implemented by the various elements in fig. 10 may be implemented by a transceiver and a processor. Referring to fig. 11, fig. 11 is a schematic structural diagram of a first network management device according to an embodiment of the present disclosure, where the first network management device may be a device (e.g., a chip) having a mobility parameter configuration function according to the embodiment of the present disclosure. The first network management device 1100 may include a transceiver 1101, at least one processor 1102, and a memory 1103. The transceiver 1101, the processor 1102 and the memory 1103 may be connected to each other via one or more communication buses, or may be connected in other manners. The bus connection mode is taken as an example in the present embodiment, as shown in fig. 11.

Among other things, the transceiver 1101 may be used to transmit or receive data. It is to be understood that the transceiver 1101 is a generic term and may include both a receiver and a transmitter. For example, the transmitter is configured to transmit the mobility optimization attribute to the second network management device.

Wherein the processor 1102 may be configured to process data. For example, the processor 1102 may invoke program code stored in the memory 1103 to determine the mobility optimization attributes. The processor 1102 may include one or more processors, for example, the processor 1102 may be one or more Central Processing Units (CPUs), Network Processors (NPs), hardware chips, or any combination thereof. In the case where the processor 1102 is one CPU, the CPU may be a single core CPU or a multi-core CPU.

The memory 1103 is used for storing program codes and the like. The memory 1103 may include a volatile memory (volatile memory), such as a Random Access Memory (RAM). The memory 1103 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD), or a solid-state drive (SSD). The memory 1103 may also comprise a combination of memories of the kind described above.

The transceiver 1101 and the processor 1102 may be configured to implement a mobility parameter configuration method in this embodiment, where a specific implementation manner is as follows:

determining a mobility optimization attribute, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a radio link of a secondary cell fails and/or an imminent radio link fails;

the mobility optimization attribute is sent to the second network management device.

In one implementation, the transceiver 1101 is further configured to receive a response message sent by the second network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In one implementation, the transceiver 1101 is further configured to send a request message to the second network management device, where the request message is 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 1101 is further configured to receive feedback information sent by the second network management device, where the feedback information includes 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 under the condition that a radio link of the secondary cell fails and/or an imminent radio link fails.

In one implementation, the transceiver 1101 is further configured to:

sending a subscription operation to the second network management device;

In one implementation, the transceiver 1101 is further configured to:

and receiving the data stream sent by the second network management equipment.

An embodiment of the present application provides a second network management device, and as shown in fig. 12, the second network management device 1200 may be used to implement a mobility parameter configuration method in the embodiment of the present application. The second network management apparatus 1200 may include:

a transceiving unit 1201, configured to receive a mobility optimization attribute sent by a first network management device, where the mobility optimization attribute is used to indicate an attribute configured in a case where a secondary cell radio link fails and/or an imminent radio link fails; the transceiving unit 1201 is further configured to send the mobility optimization attribute to the second network device, so that the second network device adjusts a handover parameter in a process of handover of the terminal device from the first network device to the second network device according to the mobility optimization attribute when the secondary cell radio link fails and/or is imminent to fail.

In one implementation, the transceiving unit 1201 is further configured to send a response message to the first network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In an implementation manner, the transceiving unit 1201 is further configured to receive a request message sent by the first network management device, where the request message is 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 transceiving unit 1201 is further configured to send feedback information to the first network management device, where the feedback information includes 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 in the case that a radio link of the secondary cell fails and/or an imminent radio link fails.

In one implementation, the mobility optimization performance data includes one or more of: the total number of times of switching of the auxiliary node, the total number of times of switching failure of the auxiliary node, the number of times of generating ping-pong effect, the number of times of updating too early of the auxiliary node, the number of times of updating too late of the auxiliary node, the number of times of switching the auxiliary node to a wrong cell, or the number of times of failure of an impending wireless link.

In one implementation manner, the transceiving 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 transceiving unit 1201 is further configured to send an indication message to the first network management device, where the indication message is used to indicate that the file data is ready; the transceiving unit 1201 is further configured to receive a request message sent by the first network management device, where the request message is used to request to acquire available file data.

In one implementation, the transceiving unit 1201 is further configured to:

receiving measurement task creating operation sent by first network management equipment;

sending a data stream connection establishment operation to a first network management device;

and transmitting the data stream to the first network management equipment.

In one implementation, the relevant functions implemented by the various elements in fig. 12 may be implemented by a transceiver and a processor. Referring to fig. 13, fig. 13 is a schematic structural diagram of a second network management device according to an embodiment of the present disclosure, where the second network management device may be a device (e.g., a chip) having a mobility parameter configuration function according to the embodiment of the present disclosure. The second network management device 1300 may include a transceiver 1301, at least one processor 1302, and a memory 1303. The transceiver 1301, the processor 1302, and the memory 1303 may be connected to each other through one or more communication buses, or may be connected in other manners. The bus connection mode is taken as an example in the present embodiment, as shown in fig. 13.

The transceiver 1301 may be used to transmit or receive data, among other things. It is to be understood that the transceiver 1301 is generic and may include a receiver and a transmitter. For example, the receiver is configured to receive the mobility optimization attribute sent by the first network management device.

Processor 1302 may be used, among other things, to process data. The processor 1302 may include one or more processors, for example, the processor 1302 may be one or more Central Processing Units (CPUs), Network Processors (NPs), hardware chips, or any combination thereof. In the case where the processor 1302 is a single CPU, the CPU may be a single-core CPU or a multi-core CPU.

The memory 1303 stores program codes and the like. The memory 1303 may include a volatile memory (RAM), such as a Random Access Memory (RAM). The memory 1303 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD), or a solid-state drive (SSD). The memory 1303 may also comprise a combination of the above-mentioned kinds of memories.

The transceiver 1301 may be used to implement the mobility parameter configuration method in the embodiment of the present application, where the specific implementation manner is as follows:

receiving a mobility optimization attribute sent by first network management equipment, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a radio link of a secondary cell fails and/or an imminent radio link fails;

and sending the mobility optimization attribute to second network equipment, so that the second network equipment adjusts the switching parameters of the terminal equipment in the process of switching from the first network equipment to the second network equipment according to the mobility optimization attribute under the condition that the radio link of the secondary cell fails and/or the radio link is imminent to fail.

In one implementation, the transceiver 1301 is further configured to send a response message to the first network management device, where the response message indicates a configuration status of the second network management device. The configuration state of the second network management device includes successful configuration, failed configuration, or incapability of configuration.

In an implementation manner, the transceiver 1301 is further configured to receive a request message sent by the first network management device, where the request message is 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 1301 is further configured to send feedback information to the first network management apparatus, where 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 case of a radio link failure and/or an imminent radio link failure of the secondary cell.

In one implementation, the transceiver 1301 is further configured to receive a subscription operation sent by the first network management device. Processor 1302 determines that the file data is ready. The transceiver 1301 is further configured to send an indication message to the first network management apparatus, where the indication message is used to indicate that the file data is ready; the transceiver 1301 is further configured to receive a request message sent by the first network management apparatus, where the request message is used to request to obtain available file data.

In one implementation, the transceiver 1301 is further configured to:

and transmitting the data stream to the first network management equipment.

An embodiment of the present application provides a computer-readable storage medium, which stores a program or instructions, and when the program or instructions are run on a computer, the program or instructions cause the computer to execute a mobility parameter setting method in an embodiment of the present application.

The embodiment of the present application provides a chip or a chip system, where the chip or the chip system includes at least one processor and an interface, the interface and the at least one processor are interconnected through a line, and the at least one processor is configured to run a computer program or an instruction to perform the mobility parameter setting method in the embodiment of the present application.

In one implementation, the chip or chip system described above in this application further includes at least one memory having instructions stored therein. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or may be a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).

The embodiment of the application provides a communication system, which comprises a first network management device and a second network management device.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A mobility parameter configuration method is characterized by comprising the following steps:

the first network management equipment determines a mobility optimization attribute, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a secondary cell radio link fails and/or an imminent radio link fails;

and the first network management equipment sends the mobility optimization attribute to the second network management equipment.

2. The method of claim 1, wherein the mobility optimization attribute comprises a first policy parameter; the first policy parameters include one or more of:

a handover trigger defining parameter, a handover adjustment strategy parameter, an optimization cycle or a handover optimization strategy parameter; wherein,

the switching trigger limiting parameter comprises a maximum switching trigger deviation value and/or a minimum switching trigger time interval when the secondary cell is switched;

the switching adjustment strategy parameters comprise one or more of adjustment parameters of cell individual deviation, beam parameters, wireless link monitoring parameters and random access resource parameters;

the switching optimization strategy parameters comprise an optimization triggering threshold corresponding to the radio link failure of the secondary cell and/or an optimization triggering threshold corresponding to the impending radio link failure.

3. The method of claim 1, wherein the mobility optimization attribute comprises a first target parameter; the first target parameter comprises one or more of:

cell identification, maximum number of handover triggers or handover trigger optimization target parameter; wherein,

the handover trigger optimization target parameters comprise one or more of a radio link failure proportion of the secondary cell, an imminent radio link failure proportion, a ping-pong handover frequency proportion, a handover early failure rate or a handover late call drop rate.

4. The method of claim 1, wherein the mobility optimization attribute comprises a first control parameter; the first control parameter includes: and the mobility optimization function control parameter of the radio link failure of the secondary cell and/or the mobility optimization function control parameter of the impending radio link failure.

5. The method of claim 1, wherein the mobility optimization attribute comprises a second policy parameter; the second policy parameters include one or more of:

network equipment identification, abnormal coverage strategy parameters or abnormal wireless link strategy parameters; wherein,

the abnormal coverage strategy parameter comprises one or more of an abnormal coverage threshold, a reference signal received power threshold of a serving cell or a reference signal received power threshold of an adjacent cell;

the abnormal wireless link strategy parameters comprise one or more of abnormal wireless link failure ratio threshold, network equipment group switching failure ratio threshold or impending wireless link failure ratio threshold.

6. The method of claim 1, wherein the mobility optimization attribute comprises a second objective parameter; the second target parameter comprises one or more of:

network equipment identification, abnormal coverage proportion or switching trigger optimization target parameters; the handover trigger optimization target parameters comprise one or more of a secondary cell radio link failure proportion, a secondary cell handover failure proportion or an impending radio link failure proportion.

7. The method of claim 1, further comprising:

the first network management device receives a response message sent by the second network management device, wherein the response message indicates the configuration state of the second network management device.

8. The method according to any one of claims 1 to 7, further comprising:

the first network management device sends a request message to a second network management device, wherein the request message is used for requesting mobility optimization performance data corresponding to the mobility optimization attribute and/or requesting 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, where 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 case of a secondary cell radio link failure and/or an imminent radio link failure.

9. The method of claim 8, wherein the mobility optimization performance data comprises one or more of:

the total number of times of switching of the auxiliary node, the total number of times of switching failure of the auxiliary node, the number of times of generating ping-pong effect, the number of times of updating too early of the auxiliary node, the number of times of updating too late of the auxiliary node, the number of times of switching the auxiliary node to a wrong cell, or the number of times of failure of an impending wireless link.

10. A mobility parameter configuration method is characterized by comprising the following steps:

the second network management equipment receives a mobility optimization attribute sent by the first network management equipment, wherein the mobility optimization attribute is used for indicating an attribute configured under the condition that a radio link of a secondary cell fails and/or an imminent radio link fails;

and the second network management equipment sends the mobility optimization attribute to second network equipment so that the second network equipment adjusts the switching parameters of the terminal equipment in the process of switching from the first network equipment to the second network equipment according to the mobility optimization attribute under the condition that the radio link of the secondary cell fails and/or the radio link is imminent to fail.

11. The method of claim 10, wherein the mobility optimization attribute comprises a first policy parameter; the first policy parameters include one or more of:

12. The method of claim 10, wherein the mobility optimization attribute comprises a first target parameter; the first target parameter comprises one or more of:

13. The method of claim 10, wherein the mobility optimization attribute comprises a first control parameter; the first control parameter includes: and the mobility optimization function control parameter of the radio link failure of the secondary cell and/or the mobility optimization function control parameter of the impending radio link failure.

14. The method of claim 10, wherein the mobility optimization attribute comprises a second policy parameter; the second policy parameters include one or more of:

the abnormal radio link strategy parameters comprise one or more of abnormal radio link failure ratio threshold, auxiliary cell switching failure ratio threshold or impending radio link failure ratio threshold.

15. The method of claim 10, wherein the second target parameter comprises one or more of:

network equipment identification, abnormal coverage proportion or switching trigger optimization target parameters; the handover trigger optimization target parameters comprise one or more of abnormal radio link failure proportion, secondary cell handover failure proportion or impending radio link failure proportion.

16. The method of claim 10, further comprising:

the second network management device sends a response message to the first network management device, wherein the response message indicates the configuration state of the second network management device.

17. The method according to any one of claims 10 to 16, further comprising:

the second network management device receives a request message sent by the first network management device, where the request message is 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 second network management device sends feedback information to the first network management device, where 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 case of a secondary cell radio link failure and/or an imminent radio link failure.

18. The method of claim 17, wherein the mobility optimization performance data comprises one or more of:

19. A first network management device comprising a memory and a processor;

the memory to store instructions;

the processor to execute the instructions such that the method of any one of claims 1 to 9 is performed.

20. A second network management device comprising a memory and a processor;

the memory to store instructions;

the processor configured to execute the instructions such that the method of any of claims 10 to 18 is performed.

21. A communication system, comprising:

a first network management device for performing the method of any one of claims 1 to 9;

a second network management device for performing the method of any one of claims 10 to 18.

22. A computer-readable storage medium comprising a program or instructions for performing the method of any one of claims 1 to 9 or 10 to 18 when the program or instructions are run on a computer.