WO2022027659A1 - 一种负载均衡方法、相关设备及*** - Google Patents

一种负载均衡方法、相关设备及*** Download PDF

Info

Publication number
WO2022027659A1
WO2022027659A1 PCT/CN2020/107971 CN2020107971W WO2022027659A1 WO 2022027659 A1 WO2022027659 A1 WO 2022027659A1 CN 2020107971 W CN2020107971 W CN 2020107971W WO 2022027659 A1 WO2022027659 A1 WO 2022027659A1
Authority
WO
WIPO (PCT)
Prior art keywords
load balancing
slice
management device
network
network node
Prior art date
Application number
PCT/CN2020/107971
Other languages
English (en)
French (fr)
Inventor
石小丽
许瑞岳
邹兰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/107971 priority Critical patent/WO2022027659A1/zh
Publication of WO2022027659A1 publication Critical patent/WO2022027659A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution

Definitions

  • the present application relates to wireless communication technologies, and in particular, to a load balancing method based on a load balancing MLB and related devices and systems.
  • Mobility load balance refers to the automatic adjustment of mobility-related parameters by exchanging load information between evolved base stations (evolved Node Bs, eNBs), so as to realize the uniformity of services or users among different eNBs. distributed.
  • eNBs evolved Node Bs
  • the purpose of MLB is to control uneven service distribution, achieve balanced distribution of service load among different cells, maintain a high radio resource utilization rate, and improve system capacity.
  • the management of MLB is performed by network nodes, such as a network management system (NMS), for the MLB function module to configure corresponding switches, targets and policies based on the cell MLB scenario.
  • NMS network management system
  • the eNB also supports MLB, and also supports sliced MLB and beam-based MLB, but the existing technology does not consider the management of slice-based MLB and beam-based MLB MLB management.
  • Embodiments of the present application provide a load balancing method, related devices, and systems, which are used to implement the management of slice load balancing and beam load balancing.
  • a first aspect of the embodiments of the present application provides a load balancing method, including:
  • the first network management device may receive load balancing control information from a network node of the second network management device, where the load balancing control information of the network node includes at least one of slice load balancing information and beam load balancing information, After receiving the load balancing control information, the first network management device may configure the load balancing control information.
  • the load balancing control information of the network node received by the first network management device includes at least one of the load balancing information of the slice and the load balancing information of the beam, so that the load balancing of the slice can be realized.
  • Management, or management of load balancing of beams, or management of load balancing of slices and load balancing of beams when both are enabled.
  • the load balancing control information of the network node configured by the first network management device may specifically be that the first network management device is in the management object of the network node.
  • the load balancing control information for configuring the network node also includes the load balancing control information for configuring the network node in the network node by the first network management device, wherein the management object of the network node may be the management object of the core network node, or the management object of the base station node. Manage objects.
  • the manner in which the first network management device configures the load balancing control information of the network node is limited, thus improving the feasibility of the solution.
  • the first network management device may also send load balancing control information of the network node to the network node, the The load balancing control information of the network node is used for the network node to perform the load balancing function.
  • the first network management device also sends load balancing control information of the network node to the network node, and the network node can perform the load balancing function according to the load balancing control information of the network node, thus improving the processing capability of load balancing.
  • the load balancing control of the network node includes load balancing switch information, load balancing target information, and load balancing policy information.
  • the load balancing switch information includes first indication information or second indication information, the first indication information is used to enable the load balancing function of at least one of slices and beams, and the second indication information is used to disable at least one of slices and beams load balancing function.
  • the load balancing target information includes at least one of a load target, a key performance indicator KPI target, and a key quality indicator KQI target , wherein the load targets include at least one of slices and beams, the KPI targets include at least one of slices and beams, and the KQI targets include at least one of slices and beams. KQI targets.
  • the load balancing policy information includes a load threshold, a load balancing optimization indication, a slice load balancing execution indication, a dedicated resource indication, At least one of available capacity resource statistics indication and slice group information, wherein the load threshold includes at least one load threshold of slices and beams, and the load balancing optimization indication includes at least one of slices and beams.
  • Load balancing optimization indication, dedicated The resource indication includes dedicated resource indication of at least one of slices and beams
  • the available capacity resource statistics indication includes available capacity resource statistics indication of at least one of slices and beams
  • the slice group information includes multiple slice identifiers. Multiple slices of the identity support the same service.
  • the load target includes the maximum range of the comprehensive available capacity CAC, the minimum range of the CAC, the maximum range of the radio resource utilization rate, At least one of the minimum range of radio resource utilization, the maximum range of radio resource control RRC connections, the minimum range of RRC connections, the maximum range of active users, and the minimum range of active users.
  • the KPI target includes at least one of protocol data unit PDU session abnormal release rate, PDU session establishment failure rate, abnormal RRC connection release rate, RRC connection establishment failure rate, and handover failure rate.
  • the KQI target includes at least one of response success rate, response delay, and display success rate, display delay, and download rate.
  • the abnormal release rate of the PDU session the ratio of the number of abnormal releases related to the load to the total number of abnormal releases.
  • PDU session establishment failure rate the ratio of load-related establishment failure times to total establishment attempts.
  • Abnormal RRC connection release rate The ratio of the load-related abnormal release times to the total RRC connection release times.
  • RRC connection establishment failure rate the ratio of load-related establishment failure times to total RRC establishment failure times.
  • Handover failure rate the ratio of load-related handover failures to total handover failures.
  • the download rate includes at least one of a page download rate, a video streaming media download rate, and a file download rate.
  • the response success rate includes at least one of page response success rate, video streaming media response success rate, and file download response success rate.
  • the display success rate includes at least one of page display success rate, video streaming media display success rate, and file download display success rate.
  • the response delay includes at least one of page response delay and average file delay.
  • the load threshold includes a CAC threshold, a capacity threshold for the number of available RRC connections, and a threshold for the number of active users. at least one.
  • the load balancing optimization instruction includes at least one of a first optimization instruction and a second optimization instruction, wherein the first optimization instruction is used to indicate in the neighbor relationship of the network node whether the neighbor cell allows slicing and the load of at least one of the beams Balance optimization, the second optimization indication is a cell list indicating in the network node whether to allow at least one of slicing and load balancing optimization of beams.
  • the load balancing execution instruction for slices includes the instruction to perform the load balancing function between the same slices, or the instruction to perform the load balancing function between different slices, or the instruction to perform the load balancing function between the same slices and the Instructions for performing load balancing functions between different slices.
  • the available capacity statistic indication includes at least one of an indication of only counting public available capacity, an indication of counting exclusive available capacity, an indication of counting priority available capacity, and an indication of counting shared available capacity.
  • the public available capacity includes at least one of exclusive available capacity, priority available capacity and shared available capacity.
  • the first network management device further The performance data of the network node can be sent to the second network management device, where the performance data of the network node includes the KPI and KQI of the slice, or the KPI and KQI of the beam, and the performance data can be used by the second network management device for load balancing control information is updated.
  • the first network management device may send the performance data of the network node to the second network management device, so as to evaluate the load balancing, and then update the load balancing control information.
  • the first network management device may Being a domain management entity, or a management service provider (MnS producer), or an EMS
  • the second network management device may be a cross-domain management entity, or a management service consumer (MnS consumer), or an NMS.
  • the first network management device may further receive a load balancing parameter sent by the network node.
  • the first network management device may also send a configuration response to the second network management device, where the configuration response carries the The indication of load balancing parameter update, or carrying the updated load balancing parameters, the configuration response also carries the identifier of the management object of the network node, or the identifier of the first network management device, or the configuration response carries the network node
  • the configuration response carries the identifier of the management object and the identifier of the first network management device, or the configuration response carries the identifier of the management object of the load balancing function
  • the configuration response may also carry the identifier of the management object of the load balancing function and the first network management The identification of the device.
  • the first network management device sends the updated load balancing parameters to the second network management device, so that the load balancing control information can be updated in a targeted manner.
  • a second aspect of the embodiments of the present application provides a communication apparatus, where the communication apparatus is configured to execute the first aspect and the method described in any one of the first aspect.
  • a third aspect of the embodiments of the present application provides a communication system, where the communication system includes: a first network management device and a second network management device, specifically: a second network management device, configured to send a network to the first network management device
  • the load balancing control information of the node, the load balancing control information includes at least one of the load balancing information of the slice and the load balancing information of the beam.
  • the first network management device is configured to receive the load balancing control information and configure the load balancing control information of the network node.
  • the first network management device is further configured to send load balancing control information of the network node to the network node, and the load balancing control information of the network node is used for Network nodes perform load balancing functions.
  • the load balancing control information of the network node configured by the first network management device includes:
  • the first network management device is specifically configured to configure load balancing control information of the network node in the management object of the network node.
  • any one of the first implementation manner of the third aspect to the second implementation manner of the third aspect, in the third implementation manner of the third aspect of the embodiments of the present application, the first network management device is also used to send performance data of the network node to the second network management device, where the performance data of the network node includes the KPI and KQI of the slice; or, the performance data includes the KPI and KQI of the beam;
  • the performance data is used by the second network management device to update the load balancing control information of the network node.
  • the communication system further includes a network node, where the network node is configured to perform load balancing across slices in multiple slices.
  • a fourth aspect of the embodiments of the present application provides a first network management device, including:
  • an interface configured to receive load balancing control information from a network node of the second network management device, where the load balancing control information of the network node includes at least one of slice load balancing information and beam load balancing information;
  • the processor is used to configure the load balancing control information of the network node.
  • the network management device is configured to perform the method of the aforementioned first aspect.
  • a fifth aspect of the embodiments of the present application provides a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and when the computer executes the above program, the method of the foregoing first aspect is performed.
  • a sixth aspect of the embodiments of the present application provides a computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer executes the method of the foregoing first aspect.
  • FIG. 1 is a schematic diagram of a communication system in an embodiment of the present application.
  • Fig. 2a is a schematic diagram of a management function in an embodiment of the present application.
  • FIG. 2b is a schematic diagram of a service-oriented architecture in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a 3GPP management system in an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a load balancing method in an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a scenario of load balancing in an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 13 is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 14a is a schematic diagram of another scenario of load balancing in an embodiment of the present application.
  • FIG. 14b is a schematic diagram of an association relationship between a load balancing optimization function and a management object of a network node in an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a communication device in an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a first network management device in an embodiment of the present application.
  • the embodiments of the present application can be applied to the NR system.
  • the NR system supports the load balancing of slices and the load balancing of beams.
  • the management of load balancing is performed by network nodes, such as the network management system as the load balancer.
  • Balancing function module configuration For the switch, target, and strategy of cell load balancing, an embodiment of the present application proposes a system that can manage at least one load balancing among cells, slices, and beams.
  • FIG. 1 This is a schematic diagram of a communication system in this embodiment of the application, the communication system includes a first network management device 101 and a second network management device 102.
  • the first network management device 101 can also communicate with the second network management device.
  • the network nodes 103 communicate.
  • the second network management device 102 is configured to send the load balancing control information of the network node 103 to the first network management device 101, where the load balancing control information includes at least one of the load balancing information of the slice and the load balancing information of the beam; the first The network management device 101 is configured to receive the load balancing control information of the network node 103 sent by the second network management device 102 , and configure the load balancing control information of the network node 103 .
  • the second network management device 102 may send the load balancing control information of the network node 103 to the first network management device 101, where the load balancing control information includes at least one load balancing among cells, slices and beams information, so that the load balancing of at least one of the cells, slices and beams can be managed.
  • the first network management device may be a distributed self-organizing network management function node, or may be a network management system (Network Management system, NMS), or a management service consumer (MnS consumer), or a cross-domain Manage nodes.
  • NMS Network Management system
  • MnS consumer management service consumer
  • the second network management device may be a wireless automation engine (MBB automation engine, MAE), or a network element management system (element management system, EMS), or a management service provider (MnS producer), or a domain management node.
  • MBB automation engine MAE
  • EMS network element management system
  • MnS producer management service provider
  • the network node may be a base station node or a core network node, and the base station node may specifically be an NR base station, or an LTE base station, or a cell, or a base station CU, or a base station CUCP, or a base station CUUP, or a base station CU cell, or a base station DU community.
  • the core network node may specifically be an LTE core network node, or an NR core network node.
  • the embodiments of the present application can be applied to the network management architecture of NR.
  • the management function (management function, MnF) is a management entity defined by 3GPP, and its externally visible behaviors and interfaces are defined as management services ( management services).
  • MnF management function
  • a management function (MnF) acts as a management service producer or a management service consumer.
  • the management service produced by the management service provider of the management function (MnF) may have multiple consumers.
  • a management function (MnF) may consume multiple management services from one or more management service producers.
  • the management function can act as both a management service provider and a management service consumer.
  • the service-oriented management architecture focuses on managing service providers and managing service consumers, please refer to a specific architecture of the service-oriented architecture in FIG. 2b.
  • the cross-domain management unit is the management service provider (management service producer, MnS producer), and the business support system (business support system, BSS) is the management service consumer. (management service consumer, MnS consumer).
  • the domain management unit is the management service provider (management service producer, MnS producer), and the cross-domain management unit is the management service consumer (management service consumer, MnS consumer).
  • the network element is the management service producer (management service producer, MnS producer), and the domain management unit is the management service consumer (management service consumer, MnS consumer).
  • the business support system is oriented to the communication service, and the business support system is used to provide billing, settlement, accounting, customer service, business, network monitoring, communication service life cycle management and Functional and management services such as business intent translation.
  • the business support system (BSS) can be an operator's operation system or a vertical industry's operation system (vertical OT system).
  • Cross-domain management function (CD-MnF), also called network management function (NMF).
  • the cross-domain management functional unit provides one or more of the following management functions or management services: network life cycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, and network optimization Function and network intent (Intent-CSP) translation, etc., the above-mentioned network includes one or more network elements or sub-networks, and also includes slices.
  • the network management functional unit may be a network slice management function (NSMF), a cross-domain management data analytical function (MDAF), or a cross-domain self-organizing network function (self-organization). network function, SON Function), or a cross-domain intent management functional unit (Intent Driven MnS).
  • the cross-domain management functional unit can also provide sub-network lifecycle management, sub-network deployment, sub-network fault management, sub-network performance management, sub-network configuration management, sub-network assurance, sub-network optimization functions, and sub-network Network intent, including the translation of sub-network service producer intent (intent from communication service provider, Intent-CSP), or the translation of sub-network service consumer intent (intent from communication service consumer, Intent-CSC), etc., the sub-network here It consists of multiple small sub-networks, which can be sliced sub-networks.
  • Domain management function also called network management function (NMF) or network element management function.
  • the domain management functional unit provides one or more of the following functions or management services: life cycle management of sub-networks or network elements, deployment of sub-networks or network elements, fault management of sub-networks or network elements, performance of sub-networks or network elements Management, assurance of sub-networks or network elements, optimization functions of sub-networks or network elements, and translation of intent from network operators (Intent-NOP) of sub-networks or network elements, etc.
  • the above-mentioned sub-networks include one or more network elements .
  • Sub-networks also include sub-networks, that is, one or more sub-networks form a larger sub-network.
  • the aforementioned subnetworks may also be slice subnetworks.
  • the domain management system can be a network slice subnet management function (NSSMF), a domain management data analytical function (Domain MDAF), or a domain self-organization network function (SON). Function) or domain intent management functional unit (Intent Driven MnS).
  • NSSMF network slice subnet management function
  • Domain MDAF domain management data analytical function
  • SON domain self-organization network function
  • Function domain intent management functional unit
  • the domain management functional unit can be deployed in the following ways, but is not limited to the following ways:
  • the first way classified by network type, it can be divided into access network domain management function unit (radio access network domain management function), core network domain management function unit (core domain management function) and transport network domain management function unit (transport network domain management function unit). domain management function), or a domain network management system, or at least two of the management access network, core network, and transmission network.
  • access network domain management function unit radio access network domain management function
  • core domain management function unit core domain management function
  • transport network domain management function unit transport network domain management function unit
  • domain management function or a domain network management system, or at least two of the management access network, core network, and transmission network.
  • the second way according to the administrative area, it can be divided into domain management functional units in a certain area, for example, the Shanghai sea area management functional unit, the Beijing domain management functional unit, and so on.
  • a network node is an entity that provides network services, including core network elements and access network elements, among which the core network elements include: access and mobility management functions (AMF), user plane functions ( user plane function, UPF), session management function (session management function, SMF), policy control function (policy control function, PCF), network data analysis unit (NWDAF), network warehouse unit (NRF) and gateways, etc., access network
  • the network elements include a base station (gNB, eNB), a centralized control unit (CUCP), a centralized unit (CU), a distributed unit (DU), a centralized user plane unit (CUUP), and the like.
  • a network node can also provide one or more of the following management functions or management services: NE life cycle management, NE deployment, NE fault management, NE performance management, NE guarantee, NE optimization function and the intent translation of network elements, etc.
  • the northbound interface in the LTE system is the interface between the cross-domain function management unit and the domain function management unit, that is, the domain management node management service function in the NR system
  • the southbound interface is the domain function management unit and the domain function management unit.
  • the interface between network nodes that is, the network element management service function.
  • the 3GPP management system includes a distributed self-organization network.
  • D-SON distributed self-organizing network management
  • D-SON evaluation distributed self-organizing network evaluation
  • the 3GPP management system interacts with the core network function (core network function, CNNF) and the wireless network function (radio access network function, RAN NF) for policy, target and switch interaction.
  • core network function CNNF
  • wireless network function radio access network function, RAN NF
  • the 3GPP management system includes a cross-domain function management unit and a domain function management unit, that is to say, the distributed self-organizing network management (D-SON management) function and the distributed self-organizing evaluation (D-SON evaluation) function can be located in The cross-domain function management unit or the domain function management unit.
  • D-SON management distributed self-organizing network management
  • D-SON evaluation distributed self-organizing evaluation
  • a process of the load balancing method in the embodiment of the present application includes:
  • the second network management device determines load balancing control information of the network node.
  • the second network management device may determine the load balancing control information of the network node, and the specific determination method is not limited here.
  • the second network management device may further determine the load balancing control information of the network node adjacent to the network node, or determine the load balancing control information of the adjacent cells of the network node.
  • the load balancing control information of the neighbor cells of the network node may also be information of the neighbor relationship of the network node.
  • the second network management device sends load balancing control information to the first network management device, and the first network management device receives the load balancing control information sent by the second network management device.
  • the second network management device may send the load balancing control information of the network node to the first network management device, and it can be understood that the load balancing control information is the demand information of the load balancing function of the network node.
  • the demand information of the load balancing function of the network node can be defined in a network resource model (network resource model, NRM), which will be described in the last part of the specific embodiment.
  • the load balancing control information may carry the identification information of the network node, or the identification information of the slice, or the identification information of the beam.
  • the second network management device sends an operation of creating a management object of a network node to the first network management device, so that the first network management device creates a management object of the network node, and the management object of the network node includes the load balancing of the network node control information
  • the management object of the network node may be the management object of the base station node or the management object of the core network node, wherein the management object of the base station node may be the management element (ManagedElement) information object class (information object class, IOC), Or base station DU function information object class (GNBDUFunction IOC), or base station CUCP function information object class (GNBCUCPFunction IOC), or base station CUUP function information object class (GNBCUUPFunction IOC), or CU cell information object class (NRCellCU IOC), or DU cell Information object class (NRcellDU IOC), which is not specifically limited here.
  • ManagedElement information object class
  • IOC information object class
  • the management object of the base station node is used to represent the configuration-related information of the base station node, for example, it also includes the identity of the base station node, the name of the base station node, the identity of the cell, and the configuration of the base station node. All relevant information is included here, and is not specifically limited.
  • the management object of the core network node can be the AMF function information object class (AMFFunction IOC), the UPF function information object class (UPFFunction IOC), or the SMF function information object class (SMFFunction IOC).
  • the management object is used to represent the configuration-related information of the core network node, for example, the name of the core network node and the identity of the core network node. Information related to the configuration of the core network node is included here, which is not specifically limited.
  • the load balancing control information can also exist as a management object.
  • the management object of the load balancing function can be defined as an MLB function information object class (MLBFunction IOC), or can be defined as other names, which are not limited here.
  • the second network management device may send to the first network management device an operation of creating a management object of the load balancing function, where the management object of the load balancing function includes the load balancing control information of the network node, the load balancing control information of the network node.
  • the information is used to indicate the control information provided by the load balancing function.
  • the management object of the load balancing function is associated with the management object of the network node, and is used to indicate control information that the network node has the load balancing function.
  • the second network management device may send load balancing control information to the first network management device through an object creation operation, or may send load balancing control information to the first network management device through an object update operation, a delete object operation, or an object modification operation.
  • Balance control information which is not specifically limited here. It should be understood that the first network management device receives an object creation operation, or an object update operation, or an object deletion operation, or an object modification operation that carries the load balancing function requirement of the network node.
  • the second network management device may send a network function management object creation request to the first network management device by creating a network function request (create NF request) message, for example, by creating a management object instance (Create management object instance, Create MOI ) operation sends the creation request of the network function management object to the first network management device, and in this Create MOI operation, the load balancing control information of the network node is carried, so that the first network management device establishes the management object, and configures the network node in the management object.
  • create NF request create NF request
  • Create MOI Create MOI
  • Load balancing control information or obtain the information of network function management objects through the operation of obtaining the management object instance attributes (getMOIAtrributes), modify the management object through the operation of modifying the management object instance attributes (modifyMOIAtrributes), and delete the management object through the operation of deleting the management object instance (delete MOI). object, or send load balancing control information to the first network management device through a newly defined operation, which is not specifically limited here.
  • the second network management device may receive a notification of the creation of a management object by the first network management device through a notification message for creating a management object instance (notifyMOICreation), or receive a notification message for deleting a management object instance (notifyMOIDeletion) from the first network management device.
  • the notification of the deletion of the management object of the management device, or the notification of the change of the management object of the first network management device is received through the notification change management object instance (notifyMOIchange) notification message, or the notification of the first network management device is received through a newly defined operation , which is not specifically limited here.
  • the second network management device may determine the identifier of the management object of the network node or the management object of the load balancing function, and send it to the first network management device. Further, the identifier of the management object of the network node or the management object of the load balancing function may be carried in the load balancing control information of the network node and sent to the first network management device.
  • the first network management device configures load balancing control information.
  • the first network management device After the first network management device receives the load balancing control information of the network node sent by the second network management device, it can configure the load balancing control information of the network node, that is, the first network management device configures the load balancing control information of the network node in the network node.
  • the balancing control information includes the load balancing control information of the network node configured by the first network management device in the management object of the network node, or the load balancing control information of the network node configured by the first network management device in the management object of the load balancing function.
  • the management object refers to the management object of the network node or the management object of the load balancing function, and is used to describe the load balancing control information of the network node.
  • the first network management device needs to first create a management object of the network node to be created, or create a management object of the load balancing function to be created.
  • this embodiment of the present application also provides an optional implementation manner:
  • the first network management device sends the load balancing control information to the network node, and the network node receives the load balancing control information sent by the first network management device.
  • the first network management device may send the load balancing control information of the network node to the network node.
  • this step can be implemented by a product, which is not specifically limited here.
  • the first network management device may directly configure the load balancing control information of the network node on the network node.
  • step 403 may be performed before step 404 or may be performed after step 404 .
  • the network node performs a load balancing function.
  • the network node After receiving the load balancing control information sent by the first network management device, the network node may perform a load balancing function according to the load balancing control information.
  • this step can be implemented by a product, which is not specifically limited here.
  • this embodiment of the present application also provides an optional implementation manner:
  • the network node sends the load balancing parameter to the first network management device, and the first network management device receives the load balancing parameter sent by the network node.
  • the network node After the network node performs the load balancing function, it will modify the load balancing parameters of the network node, such as the modification of the mobility parameter (cell individual offset, CIO), etc. This embodiment is not limited to this, but all parameters related to load balancing are can be included.
  • the network node may send the load balancing parameters after the load balancing function is performed to the first network management device, which may be understood as optimized or modified load balancing parameters.
  • this embodiment of the present application also provides an optional implementation manner:
  • the first network management device sends a configuration response to the second network management device, and the second network management device receives the configuration response sent by the first network management device.
  • the first network management device may send a configuration response to the second network management device, where the configuration response is used to instruct the first network management device to complete the configuration of the load balancing control information for the network node.
  • the first network management device may send a configuration response to the second network management device by creating an object response operation.
  • the response is used to indicate the management object of the first network management device to the network node or the management object of the load balancing function Configuration is complete.
  • a configuration response may also be sent to the first network management device through an update object response operation, a delete object response operation, or an object modification response operation. It should be understood that the response is used to indicate the management object of the network node by the first network management device.
  • the management object of the load balancing function is updated, deleted or modified, which is not limited here.
  • the first network management device may send a network function management object creation response to the second network management device through a create network function response (create NF response) message, for example, send a configuration response to the second network management device through the CreateMOI operation
  • the second network management device sends a configuration response, which is not specifically limited here.
  • the response operation includes an indication of updating the load balancing parameters, or may also include the updated parameter values of the load balancing parameters.
  • the response operation includes the identification of the first network management device, or the identification of the management object of the network node, or the identification of the management object of the load balancing function, or may also include the identification of the first network management device and the network
  • the identifier of the management object of the node or includes the identifier of the first network management device and the identifier of the management object of the load balancing function, which is not specifically limited here.
  • this embodiment of the present application also provides an optional implementation manner:
  • the second network management device requests the first network management device to obtain performance parameters, and the first network management device receives the request for obtaining performance parameters from the second network management device.
  • the second network management device may send a request for acquiring the performance parameter to the first network management device.
  • the performance parameters include the key performance indicator (key performance indicator, KPI) and key quality indicator (key quality indicator, KQI) of the slice, or also include the key performance indicator (key performance indicator, KPI) and key quality indicators ( key quality indicator, KQI), which is not limited here.
  • key performance indicator key performance indicator, KPI
  • key quality indicator key quality indicator, KQI
  • the performance data is used for the second network management device to evaluate the load balancing function, and further update the load balancing control information.
  • step 407 may be performed before step 408 or may be performed after step 408 .
  • this embodiment of the present application also provides an optional implementation manner:
  • the first network management device sends the performance parameter to the second network management device, and the second network management device receives the performance parameter sent by the first network management device.
  • the second network management device may send the performance parameter to the second network management device.
  • the load balancing control information includes the load balancing information of the slice, the load balancing information of the beam, and the load of the cell.
  • Equalization information which will be described separately below:
  • the load balancing information of the slice includes:
  • the load balancing switch of the slice is the first indication information or the second indication information, where the first indication information is "ON”, the second indication information is “OFF”, or the first indication information is " Ture”, the second indication information is "False”, or it can also be a value of other Boolean type or enumeration type, which is not limited here.
  • the load balancing switch of the slice may be SliceMLBControl, and the specific name is not limited in this application.
  • the load balancing target of the slice includes at least one of a load target of the slice, a key performance indicator (key performance indicator, KPI) target of the slice, and a key quality indicator (key quality indicator, KQI) target of the slice.
  • a key performance indicator key performance indicator, KPI
  • KQI key quality indicator
  • the load target of the slice includes the maximum range of the composite available capacity (CAC) of the slice, the minimum range of the composite available capacity (CAC) of the slice, the maximum range of the wireless resource utilization of the slice,
  • the minimum range of slice radio resource utilization, the maximum range of slice radio resource control (RRC) connections, the minimum range of slice radio resource control (RRC) connections, and the maximum number of slice active users At least one of the range and the minimum range of the number of active users in the slice, where the radio resource utilization rate is a parameter reflecting the resource occupancy of the network, and the number of active users is the users in the service state.
  • the composite available capacity (composite available capacity,CAC) range includes at least one of the uplink composite available capacity (composite available capacity,CAC) range and the downlink composite available capacity (composite available capacity,CAC) range, the sliced wireless
  • the range of the number of radio resource control (RRC) connections includes at least one of the range of the number of available radio resource control (RRC) connections of the slice and the range of the maximum number of radio resource control (RRC) connections of the slice.
  • the radio resource utilization range of a slice includes a physical resource block (PRB) utilization range, such as a non-guaranteed bit rate (non-GBR PRB) utilization range, a guaranteed bit rate (guaranteed bit rate) at least one of the bit rate, GBR (PRB) utilization range, and the total PRB utilization range.
  • PRB physical resource block
  • the key performance indicator (key performance indicator, KPI) target of the slice includes a protocol data unit (protocol data unit, PDU) session abnormal release rate of the slice, and a protocol data unit (protocol data unit, PDU) session establishment failure of the slice at least one of the abnormal radio resource control (RRC) connection release rate of the slice, the radio resource control (RRC) connection establishment failure rate of the slice, and the handover failure rate of the slice.
  • a protocol data unit protocol data unit, PDU
  • PDU protocol data unit
  • PDU protocol data unit
  • the abnormal release rate of the protocol data unit (protocol data unit, PDU) session is the ratio of the number of abnormal releases related to the load to the total number of abnormal releases.
  • the protocol data unit (PDU) session establishment failure rate is the ratio of the number of load-related establishment failures to the total number of establishment attempts.
  • the abnormal radio resource control (RRC) connection release rate is the ratio of the number of load-related abnormal releases to the total number of radio resource control (RRC) connection releases.
  • the radio resource control (RRC) connection establishment failure rate is the ratio of the number of load-related establishment failures to the total number of radio resource control (RRC) establishment attempts.
  • the handover failure rate is the ratio of the number of load-related handover failures to the total number of handover failures.
  • the key quality indicator (key quality indicator, KQI) target of the slice includes at least one of the response success rate of the slice, the response delay of the slice, the display success rate of the slice, the display delay of the slice, and the download rate of the slice.
  • the response success rate of the slice includes at least one of the page response success rate, the video streaming media response success rate, and the file download response success rate
  • the slice response delay includes page response delay, and file download.
  • the display success rate of the slice includes at least one of the page display success rate, the video streaming media display success rate and the file download display success rate
  • the download rate of the slice includes the page download rate, At least one of a video streaming media download rate and a file download rate.
  • the load balancing policy of the slice includes at least one of slice load threshold, slice load balancing optimization indication, slice load balancing execution indication, slice dedicated resource execution indication, slice available capacity statistics indication, and slice group information.
  • the load threshold of the slice includes a composite available capacity (composite available capacity, CAC) threshold, a slice available radio resource control (radio resource control, RRC) connection number threshold, a slice resource utilization threshold, and a slice
  • CAC composite available capacity
  • RRC radio resource control
  • the composite available capacity (composite available capacity,CAC) threshold includes at least one of an uplink composite available capacity (composite available capacity,CAC) threshold, a downlink composite available capacity (composite available capacity,CAC) threshold, and the sliced wireless
  • the resource control (radio resource control, RRC) connection threshold includes at least one of a slice's available radio resource control (RRC) connection threshold and a slice's maximum radio resource control (RRC) connection threshold
  • the resource utilization thresholds of slices include physical resource block (PRB) utilization thresholds, such as non-guaranteed bit rate (non-GBR PRB) utilization thresholds, guaranteed bit rate (guaranteed bit rate) , GBR (PRB) utilization threshold and at least one of the total PRB utilization threshold.
  • PRB physical resource block
  • the load balancing optimization instruction of the slice includes at least one of a first optimization instruction and a second optimization instruction, wherein the first optimization instruction is used to indicate in the neighbor relationship of the network node whether the neighbor of the network node allows
  • the load balancing optimization of the slice can also be understood as configuring the first optimization instruction in the management object of the neighbor relationship of the network node, or configuring the first optimization instruction in the management object of the load balancing function, and the first optimization instruction is used to instruct the management Whether the cell or neighboring cell in the object allows load balancing optimization of slices, for example, the first optimization indication may be isSliceMLBAllowed, and the specific name is not limited in this application.
  • the second optimization indication is the cell list indicating whether the load balancing optimization of the slice is allowed in the network node, or the slice list indicating whether the load balancing optimization of the slice is allowed, which can also be understood as being in the management object of the network node, or the load balancing The list of cells in the management object of the function indicating whether to allow the load balancing optimization of slices.
  • the second optimization instruction includes a first black and white table and a second black and white table, and the first black and white table includes a first black table and a first white table.
  • the first black table is used to indicate the list of cells that are not allowed to perform the slice load balancing function
  • the first white table is used to indicate the list of cells that are allowed to perform the slice load function.
  • the first black table may be SliceMLBCellblacklist
  • the first white table may be SliceMLBCellwhitelist, and the specific names are not limited in this application.
  • the second black and white table includes a second black table and a second white table.
  • the second black table is used to represent the slice list for which the slice load balancing function is not allowed to be performed
  • the second white table is used to represent the slice list that is allowed to perform the slice load function.
  • the second black list may be MLBSliceblacklist
  • the second white list may be MLBSlicewhitelist
  • the slice load balancing execution instruction includes at least one of an instruction to execute a load balancing function between the same slices and an instruction to execute a load balancing function between different slices, optionally, in different slices.
  • the instruction to perform a load balancing function between different slices includes at least one of an instruction to perform a load balancing function between the same cells in different slices and an instruction to perform a load balancing function between different cells in different slices.
  • the indication of performing the load balancing function between different slices may be isIntraSliceMLBAllowed, and the indication of performing the load balancing function between different slices may be isInterSliceMLBAllowed, and the specific name is not limited in this application.
  • the slice-dedicated resource indication is an indication of preferential access to slice-dedicated resources when performing load balancing.
  • the slice-dedicated resource indication may be expressed as MLBPriorityDedicatedresource, and the specific name is not limited in this application. It can be understood that the slice-specific resource indication is used to instruct the network node to preferentially allocate slice-specific resources to the terminal device when performing the load balancing function.
  • the statistic indication of available resource capacity of the slice includes a statistic indication that only counts the available capacity of the public resources on the slice, the statistic indication that counts the available capacity of the private resource on the slice, and the statistic indication that counts the available capacity of the priority resource on the slice. and at least one of the statistical indications of the available capacity of shared resources on the statistical slice, wherein the available capacity of public resources is the available capacity of resources that does not distinguish between exclusive resources, priority resources and shared resources.
  • the statistical indication that only counts the available capacity of the public resources on the slice may be CommonAvailableCapacity, and the specific name is not limited here. The name of this application is not limited here.
  • the statistical indication of the available capacity of the shared resources on the statistical slice may be SharedResourceAvailableCapacity, and the specific name is not limited in this application.
  • the statistics of the available capacity of the priority resources on the statistical slice The indication may be PreferredResourceAvailableCapacity, and the specific name is not limited in this application.
  • the slice group information includes multiple slice information.
  • the slice information may be slice identifiers, such as single network slice selection assistance information (S-NSSAI), and the slice identifiers identified by multiple slice identifiers. Multiple slices support the same business.
  • S-NSSAI single network slice selection assistance information
  • the slice group information is used to indicate that the network node load balancing function can be performed between slices within the slice group.
  • the slice group information may be slicegrouplist, and the specific name is not limited in this application.
  • the load balancing information of the beam includes:
  • the load balancing switch of the beam is the first indication information or the second indication information, wherein the first indication information is "ON”, the second indication information is “OFF”, or the first indication information is “Ture” ”, the second indication information is “False”, or it can also be a value of other Boolean or enumeration types, which is not limited here.
  • the load balancing switch of the beam may be BeamMLBControl, and the specific name is not limited in this application.
  • the load balancing target of the beam includes at least one of a load target of the beam, a key performance indicator (key performance indicator, KPI) target of the beam, and a key quality indicator (key quality indicator, KQI) target of the beam.
  • a key performance indicator key performance indicator, KPI
  • KQI key quality indicator
  • the load target of the beam includes the maximum range of the composite available capacity (CAC) of the beam, the minimum range of the composite available capacity (CAC) of the beam, the maximum range of the radio resource utilization of the beam, The minimum range of beam radio resource utilization, the maximum range of beam radio resource control (RRC) connections, the minimum range of beam radio resource control (RRC) connections, and the maximum number of beam active users At least one of the range and the minimum range of the number of beam active users, wherein the radio resource utilization is a parameter reflecting the resource occupancy of the network, and the number of active users is the users in the service state.
  • CAC composite available capacity
  • CAC composite available capacity
  • RRC maximum range of beam radio resource control
  • RRC minimum range of beam radio resource control
  • the composite available capacity (composite available capacity, CAC) range includes at least one of an uplink composite available capacity (composite available capacity, CAC) range and a downlink composite available capacity (composite available capacity, CAC) range.
  • the range of the number of resource control (radio resource control, RRC) connections includes at least one of the range of the number of available radio resource control (radio resource control, RRC) connections of the beam, and the range of the maximum number of radio resource control (radio resource control, RRC) connections of the cell.
  • the radio resource utilization range of the beam includes the physical resource block (PRB) utilization range, such as the non-guaranteed bit rate (non-GBR PRB) utilization range, the guaranteed bit rate (guaranteed bit rate). At least one of the range of bit rate, GBR PRB), and total PRB utilization. This application is not limited here.
  • the KPI targets of the beam include the abnormal release rate of the beam's protocol data unit (protocol data unit, PDU) session, the beam's protocol data unit (protocol data unit, PDU) session establishment failure rate, and the beam's abnormal radio resource control ( At least one of radio resource control (RRC) connection release rate, beam radio resource control (radio resource control, RRC) connection establishment failure rate and beam switching failure rate.
  • RRC radio resource control
  • the abnormal release rate of the protocol data unit (protocol data unit, PDU) session is the ratio of the number of abnormal releases related to the load to the total number of abnormal releases.
  • the protocol data unit (protocol data unit, PDU) session establishment failure rate is the ratio of the number of load-related establishment failures to the total number of establishment attempts.
  • the abnormal radio resource control (RRC) connection release rate is the ratio of the number of abnormal releases related to the load to the total number of RRC connection releases.
  • the radio resource control (radio resource control, RRC) connection establishment failure rate is the ratio of the number of load-related establishment failures to the total number of radio resource control (radio resource control, RRC) establishment attempts.
  • the handover failure rate is the ratio of the number of load-related handover failures to the total number of handover failures.
  • the KQI target of the beam includes at least one of the response success rate of the beam, the response delay of the beam, and the display success rate of the beam, the display delay of the beam, and the download rate of the beam.
  • the response of the beam includes at least one of the page response success rate, the video streaming media response success rate, and the file download response success rate
  • the beam response delay includes at least one of the page response delay and the average file download response delay.
  • the display success rate of the beam includes at least one of the page display success rate, the video streaming media display success rate and the file download display success rate
  • the beam download rate includes the page download rate, the video streaming media download rate and the file download rate. at least one of them.
  • the load balancing policy of the beam includes at least one of a beam load threshold, a beam load balancing optimization indication, a beam dedicated resource execution indication, and a beam available capacity statistics indication.
  • the load threshold of the beam includes a composite available capacity (composite available capacity, CAC) threshold, a beam available radio resource control (radio resource control, RRC) connection number threshold, a beam resource utilization threshold, and the beam The number of active users threshold.
  • the composite available capacity (composite available capacity,CAC) threshold includes at least one of an uplink composite available capacity (composite available capacity,CAC) threshold and a downlink composite available capacity (composite available capacity,CAC) threshold.
  • the resource control (radio resource control, RRC) connection threshold includes at least one of the available radio resource control (RRC) connection number threshold of the beam, and the maximum radio resource control (radio resource control, RRC) connection number threshold of the beam.
  • the resource utilization threshold of the beam includes the physical resource block (PRB) utilization threshold, for example, the non-guaranteed bit rate (non-GBR PRB) utilization threshold, the guaranteed bit rate (guaranteed bit rate) rate, at least one of GBR (PRB) utilization threshold and total PRB utilization threshold.
  • PRB physical resource block
  • the load balancing optimization instruction of the beam includes a first optimization instruction and a second optimization instruction, wherein the first optimization instruction is used to indicate whether the neighbor cell of the network node allows the load balancing optimization of the beam in the neighbor relationship of the network node.
  • the first optimization instruction is used to indicate whether the neighbor cell of the network node allows the load balancing optimization of the beam in the neighbor relationship of the network node.
  • it can also be understood as configuring the first optimization instruction in the management object of the neighbor relationship of the network node, or configuring the first optimization instruction in the management object of the load balancing function, and the first optimization instruction is used to indicate the cell in the management object or Whether the neighbor cell allows the load balancing optimization of the slice, for example, the first optimization indication may be isSSBMLBAllowed, and the specific name is not limited in this application.
  • the second optimization indication is the list of beams that indicates in the network node whether to allow the optimization of load balancing of beams, which can also be understood as a list of beams that indicates whether to allow the optimization of load balancing of beams in the management object of the network node or the management object of the load balancing function.
  • the beam list for example, the second optimization instruction includes a third black and white table, wherein the third black and white table includes a third black table and a third white table, and the third black table is used to indicate a beam list that is not allowed to perform the beam loading function,
  • the third white table is used to represent the list of beams that are allowed to perform the beam load balancing function.
  • the third black list may be MLBSSBblacklist
  • the third white list may be MLBSSBwhitelist, and the specific names are not limited in this application.
  • the beam-dedicated resource indication is an indication of preferentially accessing the beam's dedicated resources when load balancing is performed, for example, MLBPriorityDedicatedresource may be used to indicate, and the specific name is not limited in this application. It can be understood that the beam dedicated resource indication is used to instruct the network node to preferentially allocate beam dedicated resources to the terminal device when performing the load balancing function.
  • the statistical indication of the available resource capacity of the beam includes a statistical indication of only counting the available capacity of the public resources on each beam, a statistical indication of counting the available capacity of the dedicated resources on each beam, and counting the available capacity of the priority resources on each beam. and statistics of the available capacity of the shared resources on each beam.
  • the statistical indication of the available resource capacity of the beam includes a statistical indication of only the available capacity of the public resources on the beam, the statistical indication of the available capacity of the exclusive resource on the beam, and the statistical indication of the available capacity of the priority resource on the beam. and at least one of the statistical indications of the available capacity of the shared resources on the statistical beam, wherein the available capacity of the public resources is the available capacity of the resources without distinguishing between the exclusive resources, the priority resources and the shared resources.
  • the statistical indication that only counts the available capacity of the public resources on the beam may be CommonAvailableCapacity, and the specific name is not limited here. The name of this application is not limited here.
  • the statistical indication of the available capacity of the shared resources on the statistical beam can be SharedResourceAvailableCapacity, and the specific name is not limited in this application.
  • the statistics of the available capacity of the priority resources on the statistical beam The indication may be PreferredResourceAvailableCapacity, and the specific name is not limited in this application.
  • the load balancing information of the cell includes:
  • the load balancing switch of the cell is the first indication information or the second indication information, wherein the first indication information is "ON”, the second indication information is “OFF”, or the first indication information is “Ture” ”, the second indication information is “False”, or it can also be a value of other Boolean or enumeration types, which is not limited here.
  • the load balancing switch of the slice may be MLBControl, and the specific name is not limited in this application.
  • the load balancing target of the cell includes at least one of a load target of the cell, a key performance indicator (key performance indicator, KPI) target of the cell, and a key quality indicator (key quality indicator, KQI) target of the cell.
  • a key performance indicator key performance indicator, KPI
  • KQI key quality indicator
  • the load target of the cell includes the maximum range of composite available capacity (CAC) of the cell, the minimum range of the composite available capacity (CAC) of the cell, the maximum range of wireless resource utilization of the cell, Minimum range of cell radio resource utilization, maximum range of cell radio resource control (RRC) connections, minimum cell radio resource control (RRC) connections, cell active users At least one of the maximum range of the number of active users in the cell and the minimum range of the number of active users in the cell, wherein the radio resource utilization is a parameter reflecting the resource occupation of the network, and the active users are the users who maintain the service state.
  • CAC composite available capacity
  • CAC composite available capacity
  • CAC composite available capacity
  • CAC composite available capacity
  • RRC maximum range of cell radio resource control
  • RRC minimum cell radio resource control
  • the composite available capacity (composite available capacity, CAC) range includes at least one of an uplink composite available capacity (composite available capacity, CAC) range and a downlink composite available capacity (composite available capacity, CAC) range.
  • the range of the number of resource control (radio resource control, RRC) connections includes at least one of the range of the number of available radio resource control (radio resource control, RRC) connections of the cell, and the range of the maximum number of radio resource control (radio resource control, RRC) connections of the cell.
  • the radio resource utilization range of a cell includes the physical resource block (PRB) utilization range, such as the non-guaranteed bit rate (non-GBR PRB) utilization range, the guaranteed bit rate (guaranteed bit rate) At least one of bit rate, GBR (PRB) utilization range, and total PRB utilization range.
  • PRB physical resource block
  • the KPI targets of the cell include the abnormal release rate of the protocol data unit (protocol data unit, PDU) session of the cell, the failure rate of the establishment of the protocol data unit (protocol data unit, PDU) session of the cell, and the abnormal wireless communication rate of the cell.
  • the abnormal release rate of the protocol data unit (PDU) session is the ratio of the number of abnormal releases related to the load to the total number of abnormal releases
  • the failure rate of the session establishment of the protocol data unit (PDU) is the load related.
  • the ratio of the number of failures to the total number of establishment attempts is the ratio of the number of load-related abnormal releases to the total number of radio resource control (RRC) connection releases
  • wireless Resource control (radio resource control, RRC) connection establishment failure rate is the ratio of the number of load-related establishment failures to the total number of radio resource control (radio resource control, RRC) establishment attempts
  • handover failure rate is the load-related handover failure times and the total The ratio of the number of handover failures.
  • the KQI target of the cell includes at least one of the response success rate of the cell, the response delay of the cell, and the display success rate of the cell, the display delay of the cell, and the download rate of the cell.
  • the response of the cell includes at least one of the page response success rate, the video streaming media response success rate, and the file download response success rate
  • the cell response delay includes at least one of the page response delay and the average file download response delay.
  • the display success rate of the cell includes at least one of page display success rate, video streaming media display success rate and file download display success rate
  • the download rate of the cell includes page download rate, video streaming media download rate and file download rate. at least one of them.
  • the load balancing policy of the cell includes the load threshold of the cell and the load balancing optimization indication of the cell.
  • the load threshold of the cell includes at least one of the following composite available capacity (composite available capacity, CAC) threshold, cell available radio resource control (radio resource control, RRC) connection number threshold, cell resource utilization threshold and cell The threshold for the number of active users.
  • composite available capacity composite available capacity
  • CAC composite available capacity
  • RRC radio resource control
  • the composite available capacity (composite available capacity,CAC) threshold includes at least one of an uplink composite available capacity (composite available capacity,CAC) threshold and a downlink composite available capacity (composite available capacity,CAC) threshold;
  • the resource control (radio resource control, RRC) connection threshold includes at least one of the available radio resource control (RRC) connection threshold of the cell and the maximum radio resource control (RRC) connection threshold of the cell
  • the resource utilization of the cell includes the physical resource block (PRB) utilization threshold, for example, the non-guaranteed bit rate (non-GBR PRB) utilization threshold, the guaranteed bit rate (guaranteed bit rate) , GBR (PRB) utilization threshold, at least one of the total PRB utilization threshold.
  • PRB physical resource block
  • the load balancing optimization instruction of the cell includes a first optimization instruction and a second optimization instruction, wherein the first optimization instruction is used to indicate whether the neighbor cell of the network node allows the load balancing optimization of the cell in the neighbor relationship of the network node.
  • the first optimization instruction is used to indicate whether the neighbor cell of the network node allows the load balancing optimization of the cell in the neighbor relationship of the network node.
  • it can also be understood as configuring the first optimization instruction in the management object of the neighbor relationship of the network node, or configuring the first optimization instruction in the management object of the load balancing function, and the first optimization instruction is used to indicate the cell in the management object or Whether the neighbor cell allows the load balancing optimization of the cell.
  • the first optimization indication may be isLBAllowed, and the specific name is not limited in this application.
  • the second optimization indication is a list of cells in the network node indicating whether the load balancing optimization of the cells is allowed, and it can also be understood that the cells that indicate whether the load balancing optimization of the cells is allowed in the management object of the network node or the management object of the load balancing function
  • the list configures a black and white list for the network node, wherein the black list represents a list of cells that are not allowed to perform load balancing of cells, and the white list represents a list of cells that are allowed to perform load balancing of cells.
  • the network node is used as an example to describe the base station:
  • Scenario 1.1 Please refer to Figure 5.
  • cell 1 supports slice 1 and slice 2
  • slice 1 and slice 2 share resources, which can be physical resource blocks.
  • PRB physical resource block, PRB
  • radio resource control radio resource control, RRC
  • RRC terminal equipment terminal equipment radio resource control
  • slice 1 of cell 1 When slice 1 of cell 1 is under high load, slice 2 of cell 1 is under low load, slice 2 of cell 2 is under high load, and slice 3 of cell 3 is under low load, for users in cell 1, due to the load of slice 1 If the load is heavy, the load of slice 2 is lighter, and the terminal device can switch to slice 2 in cell 1, thereby ensuring the quality of the service.
  • slice 2 of cell 1 can accommodate terminal equipment under slice 2 of cell 2 to achieve slice load balancing.
  • Scenario 1.2 Please refer to Figure 6, when slice 1 of cell 1 is under high load, slice 2 of cell 1 is under low load, cell 1 is under normal load, slice 2 of cell 2 is under high load, and slice 1 of cell 3 is under high load Time. Since the load of slice 1 of cell 1 is high and the load of slice 2 is low, the load of slice 1 of cell 3 can be balanced to the slice 2 of cell 1, that is, the terminal equipment switches from cell 3 to cell 1, and the slice to make changes.
  • the following describes the scenario in which slice 1 and slice 2 are configured with dedicated resources, shared resources, and priority resources.
  • the above resources may be physical resource blocks (PRBs) and radio resource controls (RRCs) of terminal equipment. ) number of connections.
  • PRBs physical resource blocks
  • RRCs radio resource controls
  • Scenario 1.3 Please refer to Figure 7.
  • slice 1 of cell 1 is under low load
  • slice 2 of cell 1 is under high load
  • slice 2 of cell 2 is under high load
  • the dedicated resources of slice 1 of cell 1 have remaining , then the load of slice 2 of cell 2 cannot be transferred to slice 1 of cell 1 at this time.
  • the base station needs to count the availability of dedicated resources, shared resources and priority resources of each cell and each slice. If the base station does not count the load of dedicated resources, shared resources and priority resources, cell 1 may continue to accept cell 2. of users have no resources available, or are overloaded.
  • Scenario 1.4 Referring to Figure 8, when slice 1 of cell 1 is under low load, slice 2 of cell 1 is under high load, and slice 2 of cell 2 is under high load, the shared and priority resources of slice 1 of cell 1 are: If the rest is left, then the load of slice 2 of cell 2 can be transferred to slice 1 of cell 1 at this time. At this time, the base station needs to count the availability of dedicated resources, shared resources and priority resources of each cell and each slice.
  • Scenario 1.5 Referring to Figure 9, when slice 1 of cell 1 is under low load and slice 2 of cell 1 is under high load, the dedicated resources, shared resources and priority resources of slice 1 of cell 1 are left over.
  • the base station should preferentially select dedicated resources for the terminal equipment, so as to improve the utilization rate of the user's resources. At this time, the base station needs to count the availability of dedicated resources, shared resources and priority resources of each cell and each slice.
  • Scenario 2.1 Please refer to Figure 10.
  • cell 1 supports beam 1 and beam 2
  • beam 1 and beam 2 share resources, which can be physical resource blocks (physical resource block, PRB) radio resource control (radio resource control, RRC) connections and terminal equipment radio resource control (radio resource control, RRC) connections
  • cell 2 supports beam 2
  • cell 3 supports beam 1.
  • beam 1 of cell 1 When beam 1 of cell 1 is under high load, beam 2 of cell 1 is under low load, beam 2 of cell 2 is under high load, and beam 3 of cell 3 is under low load, for users in cell 1, due to the load of beam 1 If the load is heavy, the load of beam 2 is lighter, and the terminal equipment can switch to beam 2 in cell 1, thereby ensuring the quality of the service.
  • beam 2 of cell 1 can accommodate terminal equipment under beam 2 of cell 2 to achieve beam load balancing.
  • Scenario 2.2 Refer to Figure 11, when beam 1 of cell 1 is under high load, beam 2 of cell 1 is under low load, cell 1 is under normal load, beam 2 of cell 2 is under high load, and beam 1 of cell 3 is under high load Time. Since the load of beam 1 of cell 1 is high and the load of beam 2 is low, the load of beam 1 of cell 3 can be balanced to the beam 2 of cell 1, that is, the terminal equipment is switched from cell 3 to cell 1, and the beam changes.
  • the following describes the scenario in which beam 1 and beam 2 are configured with dedicated resources, shared resources, and priority resources.
  • the above resources may be physical resource blocks (PRBs) and radio resource controls (RRCs) of terminal equipment. ) number of connections.
  • PRBs physical resource blocks
  • RRCs radio resource controls
  • Scenario 2.3 Please refer to Figure 12.
  • the base station needs to count the availability of dedicated resources, shared resources and priority resources of each cell and each beam. If the base station does not count the load of dedicated resources, shared resources and priority resources, cell 1 may continue to accept cell 2. of users have no resources available, or are overloaded.
  • Scenario 2.4 Referring to Figure 13, when beam 1 of cell 1 is under low load, beam 2 of cell 1 is under high load, and beam 2 of cell 2 is under high load, the shared and priority resources of beam 1 of cell 1 are If the rest is left, then the load of beam 2 of cell 2 can be transferred to beam 1 of cell 1 at this time. Then, at this time, the base station needs to count the availability of exclusive resources, shared resources and priority resources of each cell and each beam.
  • Scenario 2.5 Please refer to Figure 14a.
  • the base station should preferentially select dedicated resources for the terminal equipment, so as to improve the utilization rate of the user's resources. Then, at this time, the base station needs to count the availability of exclusive resources, shared resources and priority resources of each cell and each beam.
  • the optimization function of load balancing can be defined as MLBFunction or DMLBFunction, or other names, which are not limited here.
  • the optimization function of load balancing may exist as a management object IOC, such as MLBFunction IOC, or DMLBFunction IOC, which is not limited in this application.
  • Fig. 14b is a schematic diagram of the association relationship between the load balancing optimization function and the management object of the network node.
  • the load balancing optimization function can be associated with the network node, for example, associated with the management object of the network node, or , the load balancing optimization function can also be associated with a sub-network entity, for example, associated with a sub-network management object (subnetwork), which is not limited in this application.
  • subnetwork sub-network management object
  • the load balancing control information of the load balancing optimization function includes at least one of a load balancing switch, a load balancing target, and a load balancing strategy, which is not specifically limited here.
  • Table 1 Exemplarily, as described in Table 1, the load balancing control information added in the DMLBFunction information object class (information object class, IOC) defined in the network resource model (network resource management, NRM) is described.
  • Table 1 is an example of adding load balancing control information in DMLBFunction IOC.
  • Table 2 Exemplarily, as shown in Table 2, the load balancing control information added in the NRCellRelation information object class IOC defined in the network resource model NRM is described.
  • Table 2 is an example of adding load balancing control information in the NRCellRelation IOC.
  • M is a mandatory option
  • CM is a conditional mandatory option
  • O is an optional option.
  • This application does not limit whether the attribute in practical application is a mandatory option or an optional option.
  • isMLBAllowed, isSliceMLBAllowed, and isSSBMLBAllowed indications the other attributes are parameters already supported in the prior art, which will not be repeated here. For details, refer to 3GPP TS 28.541.
  • the communication device in this application is described below:
  • FIG. 15 is a schematic diagram of a communication device in an embodiment of the present application.
  • An embodiment of the communication device in the present application includes:
  • the receiving unit 1503 is configured to receive load balancing control information from a network node of the second network management device, where the load balancing control information of the network node includes at least one of slice load balancing information and beam load balancing information.
  • the configuration unit 1502 is configured to configure the load balancing control information of the network node.
  • the configuration unit 1502 is specifically configured to configure the load balancing control information of the network node in the management object of the network node.
  • the communication apparatus 1500 further includes a sending unit 1501 .
  • the sending unit 1501 is configured to send load balancing control information of the network node to the network node, where the load balancing control information of the network node is used for the network node to perform a load balancing function.
  • the sending unit 1501 is further configured to send performance data of the network node to the second network management device, where the performance data of the network node includes the KQI and KPI of the slice; or, the performance data includes the KQIs and KPIs.
  • the performance data is used by the second network management device to update the load balancing control information.
  • FIG. 16 is a schematic structural diagram of a first network management device in an embodiment of the present application, which is used to implement the operations of the first network management device in the above-mentioned embodiment.
  • the first network management device includes a processor 1601 and an interface 1603, which are optional Yes, the first network management device further includes a memory 1602, and an interface 1603 is used to implement communication with other devices.
  • the interface in this embodiment of the present application may also be a transceiver.
  • the method performed by the first network management device in the above embodiment may be implemented by the processor 1601 calling a program stored in the memory 1602 .
  • the apparatus for the first network management device may include a processor 1601, and the processor 1601 executes the method performed by the first network management device in the above method embodiments by invoking a program in the memory.
  • the processor here may be an integrated circuit with signal processing capability, such as a central processing unit.
  • the means for the first network management device may be implemented by one or more integrated circuits configured to implement the above method. For example: one or more application specific integrated circuits, or, one or more microprocessors, or, one or more field programmable logic gate arrays, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
  • the functions and implementation process of the receiving unit 1503 , the configuring unit 1502 and the sending unit 1501 in FIG. 15 can call the computer-executable instructions stored in the memory 1602 through the processor 1601 in the first network management device shown in FIG. 16 . to realise.
  • the functions and implementation process of the configuration unit 1502 and the receiving unit 1503 in FIG. 15 can be implemented by the processor 1601 in the first network management device shown in FIG. 16 calling the computer execution instructions stored in the memory 1602.
  • the functions and implementation process of the receiving unit 1503 and the transmitting unit 1501 can be implemented through the interface 1603 in the first network management device shown in FIG. 16 .
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center by wire (eg coaxial cable, optical fiber, Digital Subscriber Line, DSL) or wireless (eg infrared, wireless, microwave, etc.).
  • wire eg coaxial cable, optical fiber, Digital Subscriber Line, DSL
  • wireless eg infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, a data center, etc. that includes one or more available media integrated.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network management device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种负载均衡方法、相关设备及***，用于对切片负载均衡以及波束负载均衡进行管理。第一网络管理设备可以接收第二网络管理设备发送的负载均衡控制信息，该负载均衡控制信息中包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种，第一网络管理设备向网络节点发送该负载均衡控制信息，网络节点根据该负载均衡控制信息执行负载均衡功能。

Description

一种负载均衡方法、相关设备及*** 技术领域
本申请涉及无线通信技术，尤其涉及一种基于负载均衡MLB的负载均衡方法以及相关设备及***。
背景技术
移动性负载均衡(mobility load balance，MLB)是指演进型基站(evolved Node B，eNB)之间通过交换负荷信息，自动调节与移动性相关的参数，实现业务或者用户在不同eNB之间的均匀分布。MLB的目的在于控制不均匀的业务分布，达到业务负荷在不同的小区之间的均衡分布，以及保持较高的无线资源利用率，提高***容量。
在长期演进(long term evolution,LTE)***中，MLB的管理是由网络节点，例如网络管理***(network management system，NMS)为MLB功能模块配置基于小区MLB场景的相应的开关、目标以及策略。
然而，在新无线接入技术***(new radio，NR)中，eNB也支持MLB，并且还支持了切片的MLB以及波束的MLB，但是现有技术没有考虑到基于切片的MLB的管理以及基于波束的MLB管理。
发明内容
本申请实施例提供了一种负载均衡方法、相关设备以及***，用于实现对切片负载均衡以及波束负载均衡的管理。
本申请实施例的第一方面提供一种负载均衡方法，包括：
第一网络管理设备可以接收来自第二网络管理设备的网络节点的负载均衡控制信息，该网络节点的负载均衡控制信息中包括了切片的负载均衡信息以及波束的负载均衡信息中的至少一种，第一网络管理设备在接收到该负载均衡控制信息之后，可以配置该负载均衡控制信息。
本申请实施例中，第一网络管理设备接收的网络节点的负载均衡控制信息中，包括了切片的负载均衡信息以及波束的负载均衡信息中的至少一种，从而能够实现对切片的负载均衡的管理，或对波束的负载均衡的管理，或对切片的负载均衡以及波束的负载均衡同时开启时的管理。
结合第一方面，本申请实施例的第一方面的第一种实现方式中，第一网络管理设备配置网络节点的负载均衡控制信息具体可以是，第一网络管理设备在网络节点的管理对象中配置网络节点的负载均衡控制信息，也包括第一网络管理设备在网络节点中配置网络节点的负载均衡控制信息，其中，网络节点的管理对象可以为核心网节点的管理对象，或者为基站节点的管理对象。
本申请实施例中，限定了第一网络管理设备配置网络节点的负载均衡控制信息的方式，因此提高了方案的可行性。
结合第一方面或第一方面的第一种实现方式，本申请实施例第一方面的第二种实现方 式中，第一网络管理设备还可以向网络节点发送网络节点的负载均衡控制信息，该网络节点的负载均衡控制信息用于网络节点执行负载均衡功能。
本申请实施例中，第一网络管理设备还会向网络节点发送网络节点的负载均衡控制信息，网络节点可以根据网络节点的负载均衡控制信息执行负载均衡功能，因此提高了负载均衡的处理能力。
结合第一方面、第一方面的第一种实现方式至第一方面的第二种实现方式中任一种，本申请实施例第一方面的第三种实现方式中，网络节点的负载均衡控制信息包括负载均衡开关信息、负载均衡目标信息以及负载均衡策略信息。其中，负载均衡开关信息包括第一指示信息或者第二指示信息，第一指示信息用于开启切片以及波束中至少一种的负载均衡功能，第二指示信息用于关闭切片以及波束中至少一种的负载均衡功能。
结合第一方面的第三种实现方式，本申请实施例第一方面的第四种实现方式中，负载均衡目标信息包括负载目标、关键性能指标KPI目标以及关键质量指标KQI目标中的至少一种，其中，负载目标包括切片以及波束中至少一种的负载目标，KPI目标包括切片以及波束中至少一种的KPI目标，KQI目标包括切片以及波束中至少一种的KQI目标。
结合第一方面的第三种实现方式，本申请实施例第一方面的第五种实现方式中，负载均衡策略信息包括负载阈值、负载均衡优化指示、切片的负载均衡执行指示、专用资源指示、可用容量资源统计指示以及切片组信息中的至少一种，其中，负载阈值包括切片以及波束中至少一种的负载阈值，负载均衡优化指示包括切片以及波束中至少一种的负载均衡优化指示，专用资源指示包括切片以及波束中至少一种的专用资源指示，可用容量资源统计指示包括切片以及波束中至少一种的可用容量资源统计指示，切片组信息包括多个切片标识，上述多个切片标识所标识的多个切片支持相同的业务。
结合第一方面的第四种实现方式，本申请实施例第一方面的第六种实现方式中，负载目标包括综合可用容量CAC的最大范围、CAC的最小范围、无线资源利用率的最大范围、无线资源利用率的最小范围、无线资源控制RRC连接数的最大范围、RRC连接数的最小范围、激活态用户数的最大范围以及激活态用户数的最小范围中的至少一种。KPI目标包括协议数据单元PDU会话异常释放率、PDU会话建立失败率、异常RRC连接释放率、RRC连接建立失败率以及切换失败率中的至少一种。KQI目标包括响应成功率、响应时延以及显示成功率、显示时延以及下载速率中的至少一种。其中，PDU会话异常释放率为：负载相关的异常释放次数与总异常释放次数的比值。PDU会话建立失败率为：负载相关的建立失败次数与总建立尝试次数的比值。异常RRC连接释放率为：负载相关的异常释放次数与总RRC连接释放次数的比值。RRC连接建立失败率为：负载相关的建立失败次数与总RRC建立失败次数的比值。切换失败率为：负载相关的切换失败次数与总的切换失败次数的比值。其中，下载速率包括页面下载速率、视频流媒体下载速率以及文件下载速率中的至少一种。响应成功率包括页面响应成功率、视频流媒体响应成功率以及文件下载响应成功率中的至少一种。显示成功率包括页面显示成功率、视频流媒体显示成功率以及文件下载显示成功率中的至少一种。响应时延包括页面响应时延以及文件平均时延中的至少一种。
结合第一方面的第一方面的第五种实现方式，本申请实施例第一方面的第七种实现方 式中，负载阈值包括CAC阈值、可用RRC连接数容量阈值以及激活态用户数阈值中的至少一种。负载均衡优化指示包括第一优化指示以及第二优化指示中的至少一种，其中，第一优化指示用于在网络节点的邻区关系中指示邻区是否允许切片以及波束中至少一种的负载均衡优化，第二优化指示为在网络节点中指示是否允许切片以及波束中至少一种的负载均衡优化的小区列表。切片的负载均衡执行指示包括，在相同的切片之间执行负载均衡功能的指示，或者在不同的切片之间执行负载均衡功能的指示，或者包括相同的切片之间执行负载均衡功能的指示和在不同的切片之间执行负载均衡功能的指示。可用容量统计指示包括只统计公共的可用容量的指示、统计专有的可用容量的指示、统计优先的可用容量的指示以及统计共享的可用容量的指示中的至少一种。其中，公共的可用容量包括专有的可用容量、优先的可用容量以及共享的可用容量中的至少一种。
结合第一方面、第一方面的第一种实现方式至第一方面的第七种实现方式中任一种，本申请实施例第一方面的第八种实现方式中，第一网络管理设备还可以向第二网络管理设备发送网络节点的性能数据，该网络节点的性能数据包括切片的KPI以及KQI，或者包括波束的KPI以及KQI，该性能数据可以用于第二网络管理设备对负载均衡控制信息进行更新。
本申请实施例中，第一网络管理设备可以向第二网络管理设备发送网络节点的性能数据，从而对负载均衡进行评估，进而对负载均衡控制信息进行更新。
结合第一方面、第一方面的第一种实现方式至第一方面的第八种实现方式中任一种，本申请实施例第一方面的第九种实现方式中，第一网络管理设备可以为域管理实体，或管理服务提供者(MnS producer)，或EMS，第二网络管理设备可以为跨域管理实体，或管理服务消费者(MnS consumer)，或NMS。
结合第一方面的第九种实现方式，本申请实施例第一方面的第十种实现方式中，第一网络管理设备还可以接收到网络节点发送的负载均衡参数。
结合第一方面的第十种实现方式，本申请实施例第一方面的第十一种实现方式中，第一网络管理设备还可以向第二网络管理设备发送配置响应，该配置响应中携带了负载均衡参数更新的指示，或者携带了更新后的负载均衡参数，该配置响应中还会携带网络节点的管理对象的标识，或者携带第一网络管理设备的标识，或者该配置响应中携带网络节点的管理对象的标识以及第一网络管理设备的标识，或者该配置响应中携带负载均衡功能的管理对象的标识，或者该配置响应中也可以携带负载均衡功能的管理对象的标识以及第一网络管理设备的标识。
本申请实施例中，第一网络管理设备向第二网络管理设备发送更新后的负载均衡参数，从而能针对性地对负载均衡控制信息进行更新。
本申请实施例第二方面提供了一种通信装置，该通信装置用于执行上述第一方面以及第一方面中任意一项所描述的方法。
本申请实施例第三方面提供了一种通信***，该通信***包括：第一网络管理设备以及第二网络管理设备，具体地：第二网络管理设备，用于向第一网络管理设备发送网络节点的负载均衡控制信息，负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡 信息中的至少一种。第一网络管理设备，用于接收负载均衡控制信息，配置网络节点的负载均衡控制信息。
结合第三方面，本申请实施例第三方面的第一种实现方式中，第一网络管理设备还用于向网络节点发送网络节点的负载均衡控制信息，该网络节点的负载均衡控制信息用于网络节点执行负载均衡功能。
结合第三方面或第三方面的第一种实现方式，本申请实施例第三方面的第二种实现方式中，第一网络管理设备配置网络节点的负载均衡控制信息包括：
第一网络管理设备，具体用于在网络节点的管理对象中配置网络节点的负载均衡控制信息。
结合第三方面、第三方面的第一种实现方式至第三方面的第二种实现方式中任一种，本申请实施例第三方面的第三种实现方式中，第一网络管理设备，还用于向第二网络管理设备发送网络节点的性能数据，网络节点的性能数据包括切片的KPI以及KQI；或，性能数据包括波束的KPI以及KQI；
性能数据用于第二网络管理设备对网络节点的负载均衡控制信息进行更新。
结合第三方面的第一种实现方式，本申请实施例第三方面的第四种实现方式中，通信***还包括网络节点，该网络节点用于在多个切片内执行跨切片的负载均衡。
本申请实施例第四方面提供了一种第一网络管理设备，包括：
接口，用于接收来自第二网络管理设备的网络节点的负载均衡控制信息，网络节点的负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种；
处理器，用于配置网络节点的负载均衡控制信息。
该网络管理设备用于执行前述第一方面的方法。
本申请实施例第五方面提供了一种计算机可读存储介质，该计算机可读存储介质中保存有程序，当该计算机执行上述程序时，执行前述第一方面的方法。
本申请实施例第六方面提供了一种计算机程序产品，当该计算机程序产品在计算机上执行时，计算机执行前述第一方面的方法。
附图说明
图1为本申请实施例中通信***的一个示意图。
图2a本申请实施例中管理功能的一个示意图。
图2b为本申请实施例中服务化架构的一个示意图。
图3为本申请实施例中3GPP管理***的一个示意图。
图4为本申请实施例中负载均衡方法的一个流程示意图。
图5为本申请实施例中负载均衡的一个场景示意图。
图6为本申请实施例中负载均衡的另一场景示意图。
图7为本申请实施例中负载均衡的另一场景示意图。
图8为本申请实施例中负载均衡的另一场景示意图。
图9为本申请实施例中负载均衡的另一场景示意图。
图10为本申请实施例中负载均衡的另一场景示意图。
图11为本申请实施例中负载均衡的另一场景示意图。
图12为本申请实施例中负载均衡的另一场景示意图。
图13为本申请实施例中负载均衡的另一场景示意图。
图14a为本申请实施例中负载均衡的另一场景示意图。
图14b为本申请实施例中负载均衡优化功能与网络节点的管理对象的关联关系示意图。
图15为本申请实施例中通信装置的一个结构示意图。
图16为本申请实施例中第一网络管理设备的一个结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例可应用于NR***，相对于LTE***，NR***支持了切片的负载均衡以及波束的负载均衡，在LTE***中，对负载均衡的管理是由网络节点，例如网络管理***为负载均衡功能模块配置针对小区负载均衡的开关、目标以及策略，本申请实施例提出了一种能对小区、切片、以及波束中至少一种的负载均衡进行管理的***，请参阅图1，图1为本申请实施例中通信***的一个示意图，该通信***包括第一网络管理设备101，第二网络管理设备102，第一网络管理设备101除了能与第二网络管理设备进行通信，还能与网络节点103通信。
第二网络管理设备102，用于向第一网络管理设备101发送网络节点103的负载均衡控制信息，负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种；第一网络管理设备101，用于接收第二网络管理设备102发送的网络节点103的负载均衡控制信息，并配置网络节点103的负载均衡控制信息。
本申请实施例中，第二网络管理设备102可以向第一网络管理设备101发送网络节点103的负载均衡控制信息，该负载均衡控制信息中包括了小区、切片以及波束中至少一种的负载均衡信息，从而能够实现对小区、切片以及波束中至少一种的负载均衡进行管理。
在本申请实施例中，第一网络管理设备可以是分布式自组织网络管理功能节点，也可以是网络管理***(Network Management system，NMS)，或管理服务消费者(MnS consumer)，或跨域管理节点。
第二网络管理设备可以是无线自动化引擎(MBB automation engine，MAE)，也可以是网元管理***(element management system，EMS)，或管理服务提供者(MnS producer)， 或域管理节点。
网络节点可以为基站节点，或者也可以为核心网节点，基站节点具体可以为NR基站，或者LTE基站，或小区，或基站CU，或基站CUCP，或基站CUUP，或基站CU小区，或基站DU小区。核心网节点具体可以为LTE核心网节点，或者为NR核心网节点。
本申请实施例可应用于NR的网络管理架构，具体的，请参阅图2a，管理功能(management function，MnF)，是3GPP定义的管理实体，其外部可见的行为和接口被定义为管理服务(management services)。在给予服务的管理体系结构中，管理功能(MnF)扮演着管理服务提供者(management service producer)或者管理服务消费者(management service consumer)。管理功能(MnF)的管理服务提供者生产的管理服务可能有多个消费者。管理功能(MnF)可从一个或者多个管理业务生产者中消费多个管理业务。
请参阅图2a，管理功能(MnF)可以同时扮演管理服务提供者与管理服务消费者。
可以理解的是，服务化管理架构聚焦于管理服务提供者和管理服务消费者，请参阅图2b中服务化架构的一种具体架构。
当管理服务为图2b中跨域管理单元提供的管理服务，则跨域管理单元为管理服务提供者(management service producer,MnS producer)，业务支撑***(business support system,BSS)为管理服务消费者(management service consumer,MnS consumer)。
当管理服务为以上域管理单元提供的管理服务，则域管理单元为管理服务提供者(management service producer,MnS producer)，跨域管理单元为管理服务消费者(management service consumer,MnS consumer)。
当管理服务为以上网元提供的管理服务，则网元为管理服务提供者(management service producer,MnS producer)，域管理单元为管理服务消费者(management service consumer,MnS consumer)。
其中，业务支撑***(business support system，BSS)是面向通信业务(communication service)的，该业务支撑***用于提供计费、结算、帐务、客服、营业、网络监控、通信业务生命周期管理以及业务意图翻译等功能和管理服务。业务支撑***(business support system，BSS)可以为运营商的运营***，也可以为垂直行业的运营***(vertical OT system)。
跨域管理功能单元(cross domain management function，CD-MnF)，也叫网络管理功能单元(network management function，NMF)。跨域管理功能单元提供以下一项或者多项管理功能或者管理服务：网络的生命周期管理、网络的部署、网络的故障管理、网络的性能管理、网络的配置管理、网络的保障、网络的优化功能以及网络意图(Intent-CSP)的翻译等，上述的网络包括一个或者多个网元或者子网络，也包括切片。网络管理功能单元可以是切片管理功能单元(network slice management function，NSMF)，也可以是跨域管理数据分析功能单元(management data analytical function，MDAF)，或者是跨域自组织网络功能(self-organization network function，SON Function)，或者是跨域意图管理功能单元(Intent Driven MnS)。
跨域管理功能单元也可以提供子网络的生命周期管理、子网络的部署、子网络的故障 管理、子网络的性能管理、子网络的配置管理、子网络的保障、子网络的优化功能以及子网络意图，包括子网络服务生产者意图(intent from communication service provider，Intent-CSP)的翻译，或者子网络服务消费者意图(intent from communication service consumer，Intent-CSC)的翻译等，这里的子网络由多个小的子网络组成，可以是切片子网络。
域管理功能单元(domain management function,Domain-MnF)，也叫子网络管理功能单元(network management function,NMF)或者网元管理功能单元。域管理功能单元提供以下一项或者多项功能或者管理服务：子网络或者网元的生命周期管理、子网络或者网元的部署、子网络或者网元的故障管理、子网络或者网元的性能管理、子网络或者网元的保障、子网络或者网元的优化功能以及子网络或者网元的意图(intent from network operator，Intent-NOP)的翻译等，上述子网络包括一个或者多个网元。子网络也包括子网络，即一个或者多个子网络组成一个更大的子网络。上述子网络也可以是切片子网络。
域管理***可以是切片子网络管理功能单元(network slice subnet management function，NSSMF),域管理数据分析功能单元(management data analytical function，Domain MDAF)或者域自组织网络功能(self-organization network function，SON Function)或者域意图管理功能单元(Intent Driven MnS)。
其中，域管理功能单元可以以下方式部署，但不限于以下方式：
第一种方式：按网络类型分类，可分为接入网域管理功能单元(radio access network domain management function)、核心网域管理功能单元(core domain management function)以及传输网域管理功能单元(transport domain management function)，也可以是某个域网络管理***，也可以是管理接入网、核心网以及传输网中的至少两种。
第二种方式：按行政区域划分，可分为某个地区的域管理功能单元，例如，上海域管理功能单元，北京域管理功能单元等。
网络节点为提供网络服务的实体，包括核心网网元以及接入网网元等，其中核心网网元包括：接入和移动性管理功能(access and mobility management function，AMF)、用户面功能(user plane function，UPF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)、网络数据分析单元(NWDAF)、网络仓库单元(NRF)以及网关等，接入网网元包括基站(gNB，eNB)、集中控制单元(CUCP)、集中单元(CU)、分布式单元(DU)以及集中用户面单元(CUUP)等。
网络节点也可以提供以下一项或者多项管理功能或者管理服务：网元的生命周期管理、网元的部署、网元的故障管理、网元的性能管理、网元的保障、网元的优化功能以及网元的意图翻译等。
需要说明的是，在LTE***下的北向接口就是跨域功能管理单元和域功能管理单元之间的接口，也就是NR***中的域管理节点管理服务功能，南向接口就是域功能管理单元和网络节点之间的接口，也就是网元管理服务功能。
具体的，在自优化网络(self-organizing network，SON)的分布式优化架构中，请参阅图3，3GPP管理***(3GPP management system)里包括了分布式自组织网络 (distributed self-organization network，D-SON)的分布式自组织网络管理(D-SON management)功能和分布式自组织网络评价(D-SON evaluation)功能。3GPP管理***与核心网网络功能(core network function，CN NF)以及无线的网络功能(radio access network function，RAN NF)之间进行策略、目标以及开关的交互。其中，3GPP管理***中包括跨域功能管理单元和域功能管理单元，也即是说分布式自组织网络管理(D-SON management)功能和分布式自组织评价(D-SON evaluation)功能可以位于跨域功能管理单元或者域功能管理单元。
请参阅图4，本申请实施例中负载均衡方法的一个流程包括：
401、第二网络管理设备确定网络节点的负载均衡控制信息。
第二网络管理设备可以确定网络节点的负载均衡控制信息，具体确定方式此处不做限定。
可选的，第二网络管理设备还可以确定与该网络节点相邻的网络节点的负载均衡控制信息，或者确定该网络节点的邻区的负载均衡控制信息。其中，网络节点的邻区的负载均衡控制信息也可以为网络节点的邻区关系的信息。
402、第二网络管理设备向第一网络管理设备发送负载均衡控制信息，第一网络管理设备接收到第二网络管理设备发送的该负载均衡控制信息。
第二网络管理设备可以向第一网络管理设备发送网络节点的负载均衡控制信息，可以理解的是，该负载均衡控制信息即为网络节点的负载均衡功能的需求信息。可选的，网络节点的负载均衡功能的需求信息可以定义在网络资源模型(network resource model,NRM)中，该网络资源模型(network resource model,NRM)将在具体实施例的最后部分进行描述。
可选的，负载均衡控制信息中可以携带网络节点的标识信息，或者携带切片的标识信息，或者携带波束的标识信息。
具体的，第二网络管理设备向第一网络管理设备发送创建网络节点的管理对象操作，使得第一网络管理设备建立网络节点的管理对象，该网络节点的管理对象中包括了网络节点的负载均衡控制信息，其中，网络节点的管理对象可以为基站节点的管理对象或核心网节点的管理对象，其中，基站节点的管理对象可以是管理元素(ManagedElement)信息对象类(information object class，IOC)，或基站DU功能信息对象类(GNBDUFunction IOC)，或基站CUCP功能信息对象类(GNBCUCPFunction IOC)，或基站CUUP功能信息对象类(GNBCUUPFunction IOC)，或CU小区信息对象类(NRCellCU IOC)，或DU小区信息对象类(NRcellDU IOC)，具体此处不做限定，基站节点的管理对象用于表示基站节点的配置相关信息，例如还包括基站节点的标识、基站节点的名称小区的标识，与基站节点配置相关的信息都包括在此，具体不做限定。核心网节点的管理对象可以是AMF功能信息对象类(AMFFunction IOC)，或UPF功能信息对象类(UPFFunction IOC)，或SMF功能信息对象类(SMFFunction IOC)，具体此处不做限定，核心网节点的管理对象用于表示核心网节点的配置相关信息，例如还包括核心网节点的名称、核心网节点的标识，与核心网节点配置相关的信息都包括在此，具体不做限定。
可选的，负载均衡控制信息也可以作为管理对象存在，例如，负载均衡功能的管理对象可以定义为MLB功能信息对象类(MLBFunction IOC)，或者可以定义为其它名称，具体此处不做限定。相应的，第二网络管理设备可以向第一网络管理设备发送创建负载均衡功能的管理对象操作，该负载均衡功能的管理对象中包括了网络节点的负载均衡控制信息，该网络节点的负载均衡控制信息用于表示负载均衡功能具备的控制信息。可选的，负载均衡功能的管理对象关联在网络节点的管理对象下，用于表示网络节点具备负载均衡功能的控制信息。
可选的，第二网络管理设备可以通过创建对象操作向第一网络管理设备发送负载均衡控制信息，也可以通过更新对象操作，或删除对象操作，或修改对象操作向第一网络管理设备发送负载均衡控制信息，具体此处不做限定。应理解，第一网络管理设备接收携带网络节点的负载均衡功能需求的创建对象操作，或更新对象操作，或删除对象操作，或修改对象操作。
示例性的，第二网络管理设备可以通过创建网络功能请求(create NF request)消息向第一网络管理设备发送网络功能管理对象创建请求，例如，通过创建管理对象实例(Create management object instance，Create MOI)操作向第一网络管理设备发送网络功能管理对象的创建请求，该Create MOI操作中携带网络节点的负载均衡控制信息，使得第一网络管理设备建立管理对象，并在管理对象中配置网络节点的负载均衡控制信息，或者通过获取管理对象实例属性(getMOIAtrributes)操作得到网络功能管理对象的信息，通过修改管理对象实例属性(modifyMOIAtrributes)操作修改管理对象，通过删除管理对象实例操作(delete MOI)删除管理对象，或通过新定义的操作向第一网络管理设备发送负载均衡控制信息，具体此处不做限定。
示例性的，第二网络管理设备可以通过通知创建管理对象实例(notifyMOICreation)通知消息接收第一网络管理设备的创建管理对象的通知，或通过通知删除管理对象实例(notifyMOIDeletion)通知消息接收第一网络管理设备的删除管理对象的通知，或通过通知改变管理对象实例(notifyMOIchange)通知消息接收第一网络管理设备的更改管理对象的通知，或者，通过新定义的操作来接收第一网络管理设备的通知，具体此处不做限定。
可选的，第二网络管理设备可以确定网络节点的管理对象或者负载均衡功能的管理对象的标识，并发送给第一网络管理设备。进一步的，网络节点的管理对象或者负载均衡功能的管理对象的标识，可以携带在网络节点的负载均衡控制信息中发送给第一网络管理设备。
403、第一网络管理设备配置负载均衡控制信息。
第一网络管理设备接收到第二网络管理设备发送的网络节点的负载均衡控制信息之后，可以配置网络节点的负载均衡控制信息，也即是第一网络管理设备在网络节点中配置网络节点的负载均衡控制信息，包括第一网络管理设备在网络节点的管理对象中配置网络节点的负载均衡控制信息，或者第一网络管理设备在负载均衡功能的管理对象中，配置网络节点的负载均衡控制信息。其中，管理对象指的是网络节点的管理对象或负载均衡功能的管理对象，用于描述网络节点的负载均衡控制信息。
可选的，当步骤402中执行的是CreateMOI操作时，第一网络管理设备需要先创建待创建的网络节点的管理对象，或者创建待创建的负载均衡功能的管理对象。
可选的，本申请实施例还提供了一个可选的实施方式：
404、第一网络管理设备向网络节点发送负载均衡控制信息，网络节点接收到第一网络管理设备发送的该负载均衡控制信息。
可选的，第一网络管理设备可以向网络节点发送网络节点的负载均衡控制信息。
需要说明的是，该步骤可以通过产品实现，具体在此不做限定。对于第一网络管理设备位于网络节点的情况下，第一网络管理设备可以直接在网络节点上配置网络节点的负载均衡控制信息。
需要说明的是，本申请实施例不限定步骤403与步骤404之间的先后关系，步骤403可以在步骤404之前执行，也可以在步骤404之后执行。
405、网络节点执行负载均衡功能。
网络节点在接收到第一网络管理设备发送的负载均衡控制信息之后，可以根据该负载均衡控制信息执行负载均衡功能。
需要说明的是，该步骤可以通过产品实现，具体此处不做限定。
可选的，本申请实施例还提供了一个可选的实施方式：
406、网络节点向第一网络管理设备发送负载均衡参数，第一网络管理设备接收到网络节点发送的该负载均衡参数。
网络节点执行负载均衡功能后，会对网络节点的负载均衡参数进行修改，例如对移动性参数(cell individual offset，CIO)的修改等，本实施例不限与此，但凡是负载均衡相关的参数都可包括在内。网络节点可以向第一网络管理设备发送执行了负载均衡功能之后的负载均衡参数，可以理解为优化后或者修改后的负载均衡参数。
可选的，本申请实施例还提供了一个可选的实施方式：
407、第一网络管理设备向第二网络管理设备发送配置响应，第二网络管理设备接收到第一网络管理设备发送的该配置响应。
第一网络管理设备可以向第二网络管理设备发送配置响应，该配置响应用于指示第一网络管理设备对网络节点的负载均衡控制信息配置完成。具体的，第一网络管理设备可以通过创建对象响应操作向第二网络管理设备发送配置响应，应理解，该响应用于指示第一网络管理设备对网络节点的管理对象或者负载均衡功能的管理对象配置完成。或者，也可以通过更新对象响应操作，或删除对象响应操作，或修改对象响应操作向第一网络管理设备发送配置响应，应理解，该响应用于指示第一网络管理设备对网络节点的管理对象或者负载均衡功能的管理对象更新、删除或者修改完成，具体此处不做限定。
示例性的，第一网络管理设备可以通过创建网络功能响应(create NF response)消息向第二网络管理设备发送网络功能管理对象创建响应，例如，通过CreateMOI操作向第二网络管理设备发送配置响应，也可以通过获取管理对象实例属性操作(getMOIAtrributes)操作，或修改管理对象实例(modifyMOIAtrribute)，或删除管理对象实例(deleteMOI)操作，或通知管理对象实例(notifyMOI)操作，或使用新定义的 操作向第二网络管理设备发送配置响应，具体此处不做限定。
可选的，响应操作中包括负载均衡参数更新的指示，或者也可以包括负载均衡参数更新后的参数值。
可选的，响应操作中包括第一网络管理设备的标识，或者包括网络节点的管理对象的标识，或者包括负载均衡功能的管理对象的标识，或者也可以包括第一网络管理设备的标识以及网络节点的管理对象的标识，或者包括第一网络管理设备的标识以及负载均衡功能的管理对象的标识，具体此处不做限定。
可选的，本申请实施例还提供了一个可选的实施方式：
408、第二网络管理设备向第一网络管理设备请求获取性能参数，第一网络管理设备接收第二网络管理设备的该获取性能参数请求。
第二网络管理设备可以向第一网络管理设备发送获取性能参数的请求。
具体的，性能参数包括切片的关键性能指标(key performance indicator，KPI)和关键质量指标(key quality indicator，KQI)，或者也包括波束的关键性能指标(key performance indicator，KPI)和关键质量指标(key quality indicator，KQI)，具体此处不做限定。
需要说明的是，上述关键性能指标(key performance indicator，KPI)和关键质量指标(key quality indicator，KQI)为网络节点所统计，具体统计方法本申请不限定。
还需要说明的是，性能数据用于第二网络管理设备对负载均衡功能进行评估，进一步的对负载均衡控制信息进行更新。
本申请实施例中不限定步骤407与步骤408之间的先后关系，步骤407可以在步骤408之前执行，也可以在步骤408之后执行。
可选的，本申请实施例还提供了一个可选的实施方式：
409、第一网络管理设备向第二网络管理设备发送性能参数，第二网络管理设备接收到第一网络管理设备发送的该性能参数。
第二网络管理设备接收到第一网络管理设备发送的获取性能参数的请求后，可以向第二网络管理设备发送性能参数。
下面开始对负载均衡控制信息进行说明：
可选的，在上述图4对应的实施例的基础上，下面将对负载均衡控制信息的内容进行描述，其中，负载均衡控制信息包括切片的负载均衡信息、波束的负载均衡信息以及小区的负载均衡信息，下面将分别进行描述：
一、切片的负载均衡信息包括：
1、切片的负载均衡开关：
本申请实施例中，切片的负载均衡开关为第一指示信息或第二指示信息，其中，第一指示信息为“ON”，第二指示信息为“OFF”，或者，第一指示信息为“Ture”，第二指示信息为“False”，或者还可以为其他布尔型或枚举型的取值，在此不做限定。例如，切片的负载均衡开关可以是SliceMLBControl，具体命名本申请在此不做限定。
2、切片的负载均衡目标：
可选的，切片的负载均衡目标包括切片的负载目标、切片的关键性能指标(key performance indicator，KPI)目标以及切片的关键质量指标(key quality indicator，KQI)目标中的至少一种。
可选的，切片的负载目标包括切片的综合可用容量(composite available capacity，CAC)的最大范围、切片的综合可用容量(composite available capacity，CAC)的最小范围、切片无线资源利用率的最大范围、切片无线资源利用率的最小范围、切片无线资源控制(radio resource control，RRC)连接数的最大范围、切片无线资源控制(radio resource control，RRC)连接数的最小范围、切片激活态用户数的最大范围以及切片激活态用户数的最小范围中的至少一种，其中，无线资源利用率为反应网络的资源占用情况的参数，激活态用户数为保持业务状态的用户。可选的，综合可用容量(composite available capacity，CAC)范围包括上行综合可用容量(composite available capacity，CAC)范围、下行综合可用容量(composite available capacity，CAC)范围中的至少一种，切片的无线资源控制(radio resource control，RRC)连接数范围包括切片的可用无线资源控制(radio resource control，RRC)连接数范围、切片的最大无线资源控制(radio resource control，RRC)连接数范围中的至少一种，切片的无线资源利用率范围包括物理资源块(physical resource block，PRB)利用率范围，例如非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率范围、保证比特速率(guaranteed bit rate，GBR PRB)利用率范围以及总的PRB利用率范围中的至少一种。
可选的，切片的关键性能指标(key performance indicator，KPI)目标包括切片的协议数据单元(protocol data unit，PDU)会话异常释放率、切片的协议数据单元(protocol data unit，PDU)会话建立失败率、切片的异常无线资源控制(radio resource control，RRC)连接释放率、切片的无线资源控制(radio resource control，RRC)连接建立失败率以及切片的切换失败率中的至少一种。
其中，协议数据单元(protocol data unit，PDU)会话异常释放率为，负载相关的异常释放次数与总异常释放次数的比值。
协议数据单元(protocol data unit，PDU)会话建立失败率为，负载相关的建立失败次数与总建立尝试次数的比值。
异常无线资源控制(radio resource control，RRC)连接释放率为，负载相关的异常释放次数与总无线资源控制(radio resource control，RRC)连接释放次数的比值。
无线资源控制(radio resource control，RRC)连接建立失败率为，负载相关的建立失败次数与总无线资源控制(radio resource control，RRC)建立尝试次数的比值。
切换失败率为，负载相关的切换失败次数与总的切换失败次数的比值。
可选的，切片的关键质量指标(key quality indicator，KQI)目标包括切片的响应成功率、切片的响应时延以及切片的显示成功率、切片的显示时延以及切片的下载速率中的至少一种，可选的，切片的响应成功率包括页面响应成功率、视频流媒体响应成功率以及文件下载的响应成功率中的至少一种，切片的响应时延包括页面响应时延、以及文件下载的平均响应时延中的至少一种，切片的显示成功率包括页面显示成功率、视频流媒体显示 成功率以及文件下载的显示成功率中的至少一种，切片的下载速率包括页面下载速率、视频流媒体下载速率以及文件下载速率中的至少一种。
3、切片的负载均衡策略：
可选的，切片的负载均衡策略包括切片负载阈值、切片负载均衡优化指示、切片负载均衡执行指示、切片专用资源执行指示以及切片可用容量统计指示以及切片组信息中的至少一种。
可选的，切片的负载阈值包括综合可用容量(composite available capacity，CAC)阈值、切片可用无线资源控制(radio resource control，RRC)连接数阈值、切片的资源利用率阈值以及切片的激活态用户数阈值中的至少一种。可选的，综合可用容量(composite available capacity，CAC)阈值包括上行综合可用容量(composite available capacity，CAC)阈值、下行综合可用容量(composite available capacity，CAC)阈值中的至少一种，切片的无线资源控制(radio resource control，RRC)连接阈值包括切片的可用无线资源控制(radio resource control，RRC)连接数阈值、切片的最大无线资源控制(radio resource control，RRC)连接数阈值中的至少一种，切片的资源利用率阈值包括物理资源块(physical resource block，PRB)利用率阈值，例如非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率阈值、保证比特速率(guaranteed bit rate，GBR PRB)利用率阈值以及总的PRB利用率阈值中的至少一种。
可选的，切片的负载均衡优化指示包括第一优化指示以及第二优化指示中的至少一种，其中，第一优化指示用于在网络节点的邻区关系中指示网络节点的邻区是否允许切片的负载均衡优化，也可以理解为在网络节点的邻区关系的管理对象中配置第一优化指示，或者在负载均衡功能的管理对象中配置第一优化指示，第一优化指示用于指示管理对象中的小区或邻区是否允许切片的负载均衡优化，例如，第一优化指示可以为isSliceMLBAllowed，具体命名本申请在此不做限定。
第二优化指示为，在网络节点中指示是否允许切片的负载均衡优化的小区列表，或者指示是否允许切片的负载均衡优化的切片列表，也可以理解为在网络节点的管理对象中，或者负载均衡功能的管理对象中指示是否允许切片的负载均衡优化的小区列表，示例性的，第二优化指示包括第一黑白表以及第二黑白表，第一黑白表包括第一黑表以及第一白表，第一黑表用于表示不允许进行切片负载均衡功能的小区列表，第一白表用于表示允许执行切片负载功能的小区列表。例如，第一黑表可以为SliceMLBCellblacklist，第一白表可以为SliceMLBCellwhitelist，具体命名本申请在此不做限定。
第二黑白表包括第二黑表以及第二白表，第二黑表用于表示用于不允许执行切片负载均衡功能的切片列表，第二白表用于表示允许执行切片负载功能的切片列表，示例性的，第二黑表可以为MLBSliceblacklist，第二白表可以为MLBSlicewhitelist，具体命名本申请在此不做限定。
可选的，切片负载均衡执行指示包括，在相同的切片之间执行负载均衡功能的指示以及在不同的切片之间执行负载均衡功能的指示中的至少一种，可选的，在不同的切片之间执行负载均衡功能的指示包括在不同切片相同小区之间执行负载均衡功能的指示以及在不 同切片不同小区之间执行负载均衡功能的指示中的至少一种，示例性的，在相同的切片之间执行负载均衡功能的指示可以为isIntraSliceMLBAllowed，在不同的切片之间执行负载均衡功能的指示可以为isInterSliceMLBAllowed，具体命名本申请在此不限定。
可选的，切片专用资源指示为在执行负载均衡时优先接入切片的专用资源的指示，例如，切片专用资源指示可以表示为MLBPriorityDedicatedresource，具体命名本申请在此不限定。可以理解，切片专用资源指示用于指示网络节点在执行负载均衡功能时优先为终端设备分配切片的专用资源的指示。
可选的，切片的可用资源容量统计指示包括，只统计切片上公共资源的可用容量的统计指示、统计切片上专有资源的可用容量的统计指示、统计切片上优先资源的可用容量的统计指示以及统计切片上共享资源的可用容量的统计指示中的至少一种，其中，公共资源的可用容量为不区分专有资源、优先资源以及共享资源的资源可用容量。示例性的，只统计切片上公共资源的可用容量的统计指示可以为CommonAvailableCapacity，具体命名本申请在此不限定，示例性的，统计切片上专有资源的可用容量的统计指示可以为DedicatedResourceAvailableCapacity，具体命名本申请在此不限定，示例性的，统计切片上共享资源的可用容量的统计指示可以为SharedResourceAvailableCapacity，具体命名本申请在此不限定，示例性的，统计切片上优先资源的可用容量的统计指示可以为PreferedResourceAvailableCapacity，具体的命名本申请在此不限定。
可选的，切片组信息包括多个切片信息，具体的，切片信息可以是切片标识，例如单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)，多个切片标识所标识的多个切片支持相同的业务。切片组信息用于指示网络节点负载均衡功能可以在切片组内的切片之间执行。示例性的，切片组信息可以为slicegrouplist，具体的命名本申请在此不限定。
二、波束的负载均衡信息包括：
1、波束的负载均衡开关：
本实施例中，波束的负载均衡开关为第一指示信息或第二指示信息，其中，第一指示信息为“ON”，第二指示信息为“OFF”，或者，第一指示信息为“Ture”，第二指示信息为“False”，或者还可以为其他布尔型或枚举型的取值，在此不做限定。例如，波束的负载均衡开关可以是BeamMLBControl，具体命名本申请在此不做限定。
2、波束的负载均衡目标：
可选的，波束的负载均衡目标包括波束的负载目标、波束的关键性能指标(key performance indicator，KPI)目标以及波束的关键质量指标(key quality indicator，KQI)目标中的至少一种。
可选的，波束的负载目标包括波束的综合可用容量(composite available capacity，CAC)的最大范围、波束的综合可用容量(composite available capacity，CAC)的最小范围、波束无线资源利用率的最大范围、波束无线资源利用率的最小范围、波束无线资源控制(radio resource control，RRC)连接数的最大范围、波束无线资源控制(radio resource control，RRC)连接数的最小范围、波束激活态用户数的最大范围以及波束激活 态用户数的最小范围中的至少一种，其中，无线资源利用率为反应网络的资源占用情况的参数，激活态用户数为保持业务状态的用户。可选的，综合可用容量(composite available capacity，CAC)范围包括上行综合可用容量(composite available capacity，CAC)范围、下行综合可用容量(composite available capacity，CAC)范围中的至少一种，波束的无线资源控制(radio resource control，RRC)连接数范围包括波束的可用无线资源控制(radio resource control，RRC)连接数范围、小区的最大无线资源控制(radio resource control，RRC)连接数范围中的至少一种，波束的无线资源利用率范围包括物理资源块(physical resource block，PRB)利用率范围，例如非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率范围、保证比特速率(guaranteed bit rate，GBR PRB)、总的PRB利用率范围中的至少一种。本申请在此不做限定。
可选的，波束的KPI目标包括波束的协议数据单元(protocol data unit，PDU)会话异常释放率、波束的协议数据单元(protocol data unit，PDU)会话建立失败率以及波束的异常无线资源控制(radio resource control，RRC)连接释放率、波束的无线资源控制(radio resource control，RRC)连接建立失败率以及波束的切换失败率中的至少一种。
其中，协议数据单元(protocol data unit，PDU)会话异常释放率为负载相关的异常释放次数与总异常释放次数的比值。
协议数据单元(protocol data unit，PDU)会话建立失败率为负载相关的建立失败次数与总建立尝试次数的比值。
异常无线资源控制(radio resource control，RRC)连接释放率为负载相关的异常释放次数与总RRC连接释放次数的比值。
无线资源控制(radio resource control，RRC)连接建立失败率为负载相关的建立失败次数与总无线资源控制(radio resource control，RRC)建立尝试次数的比值。
切换失败率为负载相关的切换失败次数与总的切换失败次数的比值。
可选的，波束的KQI目标包括波束的响应成功率、波束的响应时延以及波束的显示成功率、波束的显示时延以及波束的下载速率中的至少一种，可选的，波束的响应成功率包括页面响应成功率、视频流媒体响应成功率以及文件下载的响应成功率中的至少一种，波束的响应时延包括页面响应时延、以及文件下载的平均响应时延中的至少一种，波束的显示成功率包括页面显示成功率、视频流媒体显示成功率以及文件下载的显示成功率中的至少一种，波束的下载速率包括页面下载速率、视频流媒体下载速率以及文件下载速率中的至少一种。
3、波束的负载均衡策略：
可选的，波束的负载均衡策略包括波束负载阈值、波束负载均衡优化指示、波束专用资源执行指示以及波束可用容量统计指示中的至少一种。
可选的，波束的负载阈值包括综合可用容量(composite available capacity，CAC)阈值、波束可用无线资源控制(radio resource control，RRC)连接数阈值、波束的资源利用率阈值以及波束的激活态用户数阈值。可选的，综合可用容量(composite available capacity，CAC)阈值包括上行综合可用容量(composite available capacity，CAC)阈 值、下行综合可用容量(composite available capacity，CAC)阈值中的至少一种，波速的无线资源控制(radio resource control，RRC)连接阈值包括波束的可用无线资源控制(radio resource control，RRC)连接数阈值、波束的最大无线资源控制(radio resource control，RRC)连接数阈值中的至少一种，波束的资源利用率阈值包括物理资源块(physical resource block，PRB)利用率阈值，例如，非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率阈值、保证比特速率(guaranteed bit rate，GBR PRB)利用率阈值、总的PRB利用率阈值中的至少一种。本申请在此不做限定。
可选的，波束的负载均衡优化指示包括第一优化指示以及第二优化指示，其中，第一优化指示用于在网络节点的邻区关系中指示网络节点的邻区是否允许波束的负载均衡优化，也可以理解为在网络节点的邻区关系的管理对象中配置第一优化指示，或者在负载均衡功能的管理对象中配置第一优化指示，第一优化指示用于指示管理对象中的小区或邻区是否允许切片的负载均衡优化，示例性的，第一优化指示可以为isSSBMLBAllowed，具体命名本申请在此不做限定。
第二优化指示为，在网络节点中指示是否允许波束的负载均衡优化的波束列表，也可以理解为在网络节点的管理对象中或者负载均衡功能的管理对象中指示是否允许波束的负载均衡优化的波束列表，示例地，第二优化指示包括第三黑白表，其中，第三黑白表包括第三黑表以及第三白表，第三黑表用于表示不允许执行波束负载功能的波束列表，第三白表用于表示允许执行波束负载均衡功能的波束列表。示例性的，第三黑表可以为MLBSSBblacklist，第三白表可以为MLBSSBwhitelist，具体命名本申请在此不做限定。
可选的，波束专用资源指示为，在执行负载均衡时优先接入波束的专用资源的指示，例如，可以使用MLBPriorityDedicatedresource来指示，具体命名本申请在此不限定。可以理解，波束专用资源指示用于指示网络节点在执行负载均衡功能时优先为终端设备分配波束的专用资源。
可选的，波束的可用资源容量统计指示包括，只统计各个波束上公共资源的可用容量的统计指示、统计各个波束上专有资源的可用容量的统计指示、统计各个波束上优先资源的可用容量的统计指示以及统计各个波束上共享资源的可用容量的统计指示。
可选的，波束的可用资源容量统计指示包括，只统计波束上公共资源的可用容量的统计指示、统计波束上专有资源的可用容量的统计指示、统计波束上优先资源的可用容量的统计指示以及统计波束上共享资源的可用容量的统计指示中的至少一种，其中，公共资源的可用容量为不区分专有资源、优先资源以及共享资源的资源可用容量。示例性的，只统计波束上公共资源的可用容量的统计指示可以为CommonAvailableCapacity，具体命名本申请在此不限定，示例性的，统计波束上专有资源的可用容量的统计指示可以为DedicatedResourceAvailableCapacity，具体命名本申请在此不限定，示例性的，统计波束上共享资源的可用容量的统计指示可以为SharedResourceAvailableCapacity，具体命名本申请在此不限定，示例性的，统计波束上优先资源的可用容量的统计指示可以为PreferedResourceAvailableCapacity，具体的命名本申请在此不限定。
三、小区的负载均衡信息包括：
1、小区的负载均衡开关：
本实施例中，小区的负载均衡开关为第一指示信息或第二指示信息，其中，第一指示信息为“ON”，第二指示信息为“OFF”，或者，第一指示信息为“Ture”，第二指示信息为“False”，或者还可以为其他布尔型或枚举型的取值，在此不做限定。例如，切片的负载均衡开关可以是MLBControl，具体命名本申请在此不做限定。
2、小区的负载均衡目标：
可选的，小区的负载均衡目标包括小区的负载目标、小区的关键性能指标(key performance indicator，KPI)目标以及小区的关键质量指标(key quality indicator，KQI)目标中的至少一种。
可选的，小区的负载目标包括小区的综合可用容量(composite available capacity，CAC)的最大范围、小区的综合可用容量(composite available capacity，CAC)的最小范围、小区无线资源利用率的最大范围、小区无线资源利用率的最小范围、小区无线资源控制无线资源控制(radio resource control，RRC)连接数的最大范围、小区无线资源控制(radio resource control，RRC)连接数的最小范围、小区激活态用户数的最大范围以及小区激活态用户数的最小范围中的至少一种，其中，无线资源利用率为反应网络的资源占用情况的参数，激活态用户数为保持业务状态的用户。可选的，综合可用容量(composite available capacity，CAC)范围包括上行综合可用容量(composite available capacity，CAC)范围、下行综合可用容量(composite available capacity，CAC)范围中的至少一种，小区的无线资源控制(radio resource control，RRC)连接数范围包括小区的可用无线资源控制(radio resource control，RRC)连接数范围、小区的最大无线资源控制(radio resource control，RRC)连接数范围中的至少一种，小区的无线资源利用率范围包括物理资源块(physical resource block，PRB)利用率范围，例如非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率范围、保证比特速率(guaranteed bit rate，GBR PRB)利用率范围、总的PRB利用率范围中的至少一种。
可选的，小区的KPI目标包括小区的协议数据单元协议数据单元(protocol data unit，PDU)会话异常释放率、小区的协议数据单元(protocol data unit，PDU)会话建立失败率以及小区的异常无线资源控制(radio resource control，RRC)连接释放率、小区的无线资源控制(radio resource control，RRC)连接建立失败率以及小区的切换失败率中的至少一种。
其中，协议数据单元(protocol data unit，PDU)会话异常释放率为负载相关的异常释放次数与总异常释放次数的比值，协议数据单元(protocol data unit，PDU)会话建立失败率为负载相关的建立失败次数与总建立尝试次数的比值，异常无线资源控制(radio resource control，RRC)连接释放率为负载相关的异常释放次数与总无线资源控制(radio resource control，RRC)连接释放次数的比值，无线资源控制(radio resource control，RRC)连接建立失败率为负载相关的建立失败次数与总无线资源控制(radio resource control，RRC)建立尝试次数的比值，切换失败率为负载相关的切换失败次数与总的切换失败次数的比值。
可选的，小区的KQI目标包括小区的响应成功率、小区的响应时延以及小区的显示成功率、小区的显示时延以及小区的下载速率中的至少一种，可选的，小区的响应成功率包括页面响应成功率、视频流媒体响应成功率以及文件下载的响应成功率中的至少一种，小区的响应时延包括页面响应时延、以及文件下载的平均响应时延中的至少一种，小区的显示成功率包括页面显示成功率、视频流媒体显示成功率以及文件下载的显示成功率中的至少一种，小区的下载速率包括页面下载速率、视频流媒体下载速率以及文件下载速率中的至少一种。
3、小区的负载均衡策略：
可选的，小区的负载均衡策略包括小区的负载阈值以及小区的负载均衡优化指示。
可选的，小区的负载阈值包括如下至少一种的综合可用容量(composite available capacity，CAC)阈值、小区可用无线资源控制(radio resource control，RRC)连接数阈值、小区的资源利用率阈值以及小区的激活态用户数阈值。
可选的，综合可用容量(composite available capacity，CAC)阈值包括上行综合可用容量(composite available capacity，CAC)阈值、下行综合可用容量(composite available capacity，CAC)阈值中的至少一种；小区的无线资源控制(radio resource control，RRC)连接阈值包括小区的可用无线资源控制(radio resource control，RRC)连接数阈值、小区的最大无线资源控制(radio resource control，RRC)连接数阈值中的至少一种，小区的资源利用率包括物理资源块(physical resource block，PRB)利用率阈值，例如，非保证比特速率(non-guaranteed bit rate，non-GBR PRB)利用率阈值、保证比特速率(guaranteed bit rate，GBR PRB)利用率阈值、总的PRB利用率阈值中的至少一种。本申请在此不做限定。
可选的，小区的负载均衡优化指示包括第一优化指示以及第二优化指示，其中，第一优化指示用于在网络节点的邻区关系中指示网络节点的邻区是否允许小区的负载均衡优化，也可以理解为在网络节点的邻区关系的管理对象中配置第一优化指示，或者在负载均衡功能的管理对象中配置第一优化指示，第一优化指示用于指示管理对象中的小区或邻区是否允许小区的负载均衡优化。例如，第一优化指示可以为isLBAllowed，具体命名本申请在此不做限定。
第二优化指示为，在网络节点中指示是否允许小区的负载均衡优化的小区列表，也可以理解在网络节点的管理对象中或者负载均衡功能的管理对象中指示是否允许小区的负载均衡优化的小区列表，例如，为网络节点配置黑白列表，其中黑表表示不允许进行小区的负载均衡的小区列表，白表表示允许进行小区的负载均衡的小区列表。
下面针对不同的实际应用场景进行说明，具体的，以网络节点为基站来示例描述：
一、小区的负载均衡和切片的负载均衡同时开启时的场景。
场景1.1：请参阅图5，当基于小区的MLB功能与基于切片的MLB功能同时开启时，小区1支持切片1和切片2，切片1和切片2是共享资源的，该资源可以为物理资源块(physical resource block，PRB)的无线资源控制(radio resource control，RRC)连接数以及终端设备终端设备的无线资源控制(radio resource control，RRC)连接数，小区2支持切 片2，小区3支持切片1。
当小区1的切片1处于高负载，小区1的切片2处于低负载，小区2的切片2处于高负载，小区3的切片3处于低负载时，对于小区1下的用户，由于切片1的负载较重，切片2的负载较轻，终端设备在小区1下可以切换至切片2，从而保证业务的质量。
对于在小区之间移动的终端设备，小区1的切片2可以接纳小区2的切片2下的终端设备达到切片负载均衡。
场景1.2：请参阅图6，当小区1的切片1处于高负载，小区1的切片2处于低负载，小区1处于正常负载，小区2的切片2处于高负载，小区3的切片1处于高负载时。由于小区1的切片1的负载较高，切片2负载较低，小区3的切片1的负载可以均衡到小区1的切片2下，也即终端设备从小区3切换至小区1，同时终端设备的切片进行改变。
下面针对切片1和切片2配置了专有资源、共享资源以及优先资源的场景进行说明，上述资源可以为物理资源块(physical resource block，PRB)以及终端设备的无线资源控制(radio resource control，RRC)连接数。
场景1.3：请参阅图7，当小区1的切片1处于低负载，小区1的切片2处于高负载，小区2的切片2处于高负载时，其中，小区1的切片1的专有资源有剩余，那么此时小区2的切片2的负载无法转移至小区1的切片1中。那么此时就需要基站统计各个小区以及各切片的专有资源、共享资源以及优先资源的可用情况，如果基站没有统计专用资源、共享资源以及优先资源的负载情况，小区1可能会继续接纳小区2的用户导致没有资源可用，或者超负荷。
场景1.4：请参阅图8，当小区1的切片1处于低负载，小区1的切片2处于高负载，小区2的切片2处于高负载时，其中，小区1的切片1的共享和优先资源有剩余，那么此时小区2的切片2的负载可以转移至小区1的切片1中。那么此时就需要基站统计各个小区以及各切片的专有资源、共享资源以及优先资源的可用情况。
场景1.5：请参阅图9，小区1的切片1处于低负载，小区1的切片2处于高负载时，其中，小区1的切片1的专用资源、共享资源和优先资源有剩余，当终端设备入网时，基站应优先为该终端设备选择专用资源，以提升用户的资源的利用率。那么此时就需要基站统计各个小区以及各切片的专有资源、共享资源以及优先资源的可用情况。
二、小区的负载均衡和波束的负载均衡同时开启时的场景。
场景2.1：请参阅图10，当基于小区的MLB功能与基于波束的MLB功能同时开启时，小区1支持波束1和波束2，波束1和波束2是共享资源的，该资源可以为物理资源块(physical resource block，PRB)的无线资源控制(radio resource control，RRC)连接数以及终端设备的无线资源控制(radio resource control，RRC)连接数，小区2支持波束2，小区3支持波束1。
当小区1的波束1处于高负载，小区1的波束2处于低负载，小区2的波束2处于高负载，小区3的波束3处于低负载时，对于小区1下的用户，由于波束1的负载较重，波束2的负载较轻，终端设备在小区1下可以切换至波束2，从而保证业务的质量。
对于在小区之间移动的终端设备，小区1的波束2可以接纳小区2的波束2下的终端 设备达到波束负载均衡。
场景2.2：请参阅图11，当小区1的波束1处于高负载，小区1的波束2处于低负载，小区1处于正常负载，小区2的波束2处于高负载，小区3的波束1处于高负载时。由于小区1的波束1的负载较高，波束2负载较低，小区3的波束1的负载可以均衡到小区1的波束2下，也即终端设备从小区3切换至小区1，同时终端设备的波束进行改变。
下面针对波束1和波束2配置了专有资源、共享资源以及优先资源的场景进行说明，上述资源可以为物理资源块(physical resource block，PRB)以及终端设备的无线资源控制(radio resource control，RRC)连接数。
场景2.3：请参阅图12，当小区1的波束1处于低负载，小区1的波束2处于高负载，小区2的波束2处于高负载时，其中，小区1的波束1的专有资源有剩余，那么此时小区2的波束2的负载无法转移至小区1的波束1中。那么此时就需要基站统计各个小区以及各波束的专有资源、共享资源以及优先资源的可用情况，如果基站没有统计专用资源、共享资源以及优先资源的负载情况，小区1可能会继续接纳小区2的用户导致没有资源可用，或者超负荷。
场景2.4：请参阅图13，当小区1的波束1处于低负载，小区1的波束2处于高负载，小区2的波束2处于高负载时，其中，小区1的波束1的共享和优先资源有剩余，那么此时小区2的波束2的负载可以转移至小区1的波束1中。那么此时就需要基站统计各个小区以及各波束的专有资源、共享资源以及优先资源的可用情况。
场景2.5：请参阅图14a，小区1的波束1处于低负载，小区1的波束2处于高负载时，其中，小区1的波束1的专用资源、共享资源和优先资源有剩余，当终端设备入网时，基站应优先为该终端设备选择专用资源，以提升用户的资源的利用率。那么此时就需要基站统计各个小区以及各波束的专有资源、共享资源以及优先资源的可用情况。
除此之外，本申请实施例对负载均衡的NRM模型进行了定义：
负载均衡的优化功能可以定义为MLBFunction或者DMLBFunction，或者其他名称，具体在此不做限定。
可选的，负载均衡的优化功能可以作为管理对象IOC存在，例如MLBFunction IOC，或者DMLBFunction IOC，本申请在此不做限定。
可选的，请参阅图14b，图14b为负载均衡优化功能与网络节点的管理对象的关联关系示意图，负载均衡优化功能可以关联在网络节点上，例如，关联在网络节点的管理对象上，或者，负载均衡优化功能也可以关联在子网实体上，例如，关联在子网管理对象(subnetwork)上，本申请在此不做限定，需要说明的是，图14b中，“1”表示负载均衡优化功能和网络节点的管理对象之间具有关联，“0”表示负载均衡优化功能与网络节点的管理对象之间不具有关联。
需要说明的是，负载均衡优化功能所具有的负载均衡的控制信息包括负载均衡开关、负载均衡目标以及负载均衡策略中的至少一种，具体此处不做限定。
示例性的，如表1所述，描述了在网络资源模型(network resource management，NRM)中定义的DMLBFunction信息对象类(information object class，IOC)中增加的负载均 衡控制信息。表1为在DMLBFunction IOC中增加负载均衡控制信息的示例。
表1
Figure PCTCN2020107971-appb-000001
其中，“M”为必选项，“O”为可选项，本申请对实际应用中的属性为可选项还是必选项不做限定。
其中，MLBControl为现有技术已经支持的参数。
示例性的，如表2所示，描述了在网络资源模型NRM中定义的NRCellRelation信息对象类IOC中增加的负载均衡控制信息。表2为在NRCellRelation IOC中增加负载均衡的控制信息的示例。
表2
Figure PCTCN2020107971-appb-000002
Figure PCTCN2020107971-appb-000003
其中“M”为必选，“CM”为条件必选项，“O”为可选项，本申请对实际应用中的属性是必选项还是可选项不做限定。除了isMLBAllowed、isSliceMLBAllowed以及isSSBMLBAllowed指示之外的其余属性为现有技术中已经支持的参数，这里不再赘述，具体可参考3GPP TS 28.541。
下面对本申请中的通信装置进行描述：
本申请提供一种通信装置，该装置可以应用在第一网络管理设备中，请参阅图15，图15为本申请实施例中通信装置的一个示意图，本申请中通信装置的一个实施例包括：
接收单元1503，用于接收来自第二网络管理设备的网络节点的负载均衡控制信息，网络节点的负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种。配置单元1502，用于配置网络节点的负载均衡控制信息。
在本申请的一些可选实施例中，配置单元1502具体用于在网络节点的管理对象中配置网络节点的负载均衡控制信息。
在本申请的一些可选实施例中，通信装置1500还包括发送单元1501。发送单元1501用于向网络节点发送网络节点的负载均衡控制信息，网络节点的负载均衡控制信息用于网络节点执行负载均衡功能。
在本申请的一些可选实施例中，发送单元1501，还用于向第二网络管理设备发送网络节点的性能数据，网络节点的性能数据包括切片的KQI以及KPI；或，性能数据包括波束的KQI以及KPI。该性能数据用于第二网络管理设备对负载均衡控制信息进行更新。
下面对本申请中的第一网络管理设备进行描述。图16为本申请实施例中的第一网络管理设备的一个结构示意图，用于实现上述实施例中第一网络管理设备的操作，该第一网络管理设备包括处理器1601和接口1603，可选的，该第一网络管理设备还包括存储器1602，接口1603用于实现与其他设备进行通信，需要说明的是，本申请实施例中的接口也可以为收发器。
以上实施例中第一网络管理设备执行的方法可以通过处理器1601调用存储器1602中存储的程序来实现。即，用于第一网络管理设备的装置可以包括处理器1601，该处理器1601通过调用存储器中的程序，以执行以上方法实施例中的第一网络管理设备执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如中央处理器。用于第一网络管理设备的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个特殊应用集成电路，或，一个或多个微处理器，或，一个或者多个现场可编辑逻辑门阵列等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
具体的，图15中的接收单元1503、配置单元1502和发送单元1501的功能以及实现过程可以通过图16所示的第一网络管理设备中的处理器1601调用存储器1602中存储的计算机可执行指令来实现。或者，图15中的配置单元1502和接收单元1503的功能以及实现过程可以通过图16所示的第一网络管理设备中的处理器1601调用存储器1602中存储的计算机执行指令来实现，图15中的接收单元1503和发送单元1501的功能以及实现过程可以通过图16中所示的第一网络管理设备中的接口1603来实现。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备 (可以是个人计算机，服务器，或者网络管理设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (23)

  1. 一种负载均衡方法，其特征在于，包括：
    第一网络管理设备接收来自第二网络管理设备的网络节点的负载均衡控制信息，所述负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种；
    所述第一网络管理设备配置所述网络节点的负载均衡控制信息。
  2. 根据权利要求1所述的负载均衡方法，其特征在于，所述第一网络管理设备配置所述网络节点的负载均衡控制信息包括：
    所述第一网络管理设备在所述网络节点的管理对象中配置所述负载均衡控制信息。
  3. 根据权利要求1或2所述的负载均衡方法，其特征在于，所述方法还包括：
    所述第一网络管理设备向所述网络节点发送所述负载均衡控制信息，所述负载均衡控制信息用于所述网络节点执行负载均衡功能。
  4. 根据权利要求1至3中任一项所述的负载均衡方法，其特征在于，所述负载均衡信息包括负载均衡开关信息、负载均衡目标信息以及负载均衡策略信息中的至少一种；
    所述负载均衡开关信息包括第一指示信息或第二指示信息，所述第一指示信息用于指示开启切片以及波束中至少一种的负载均衡功能，所述第二指示信息用于指示关闭切片以及波束中至少一种的负载均衡功能。
  5. 根据权利要求4所述的负载均衡方法，其特征在于，所述负载均衡目标信息包括负载目标、关键性能指标KPI目标以及关键质量指标KQI目标中的至少一种，其中，所述负载目标包括所述切片以及所述波束中至少一种的负载目标，所述KPI目标包括所述切片以及所述波束中至少一种的KPI目标，所述KQI目标包括所述切片以及所述波束中至少一种的KQI目标。
  6. 根据权利要求4所述的负载均衡方法，其特征在于，所述负载均衡策略信息包括负载阈值、负载均衡优化指示、切片的负载均衡执行指示、专用资源指示、可用容量资源统计指示以及切片组信息中的至少一种，其中，所述负载阈值包括所述切片以及所述波束中至少一种的负载阈值，所述负载均衡优化指示包括所述切片以及所述波束中至少一种的负载均衡优化指示，所述专用资源指示包括所述切片以及所述波束中至少一种的专用资源指示，所述可用容量资源统计指示包括所述切片以及所述波束中至少一种的可用容量资源统计指示，所述切片组信息包括多个切片标识，所述多个切片标识所标识的多个切片支持相同的业务。
  7. 根据权利要求5所述的负载均衡方法，其特征在于，所述负载目标包括综合可用容量CAC的最大范围、CAC的最小范围、无线资源利用率的最大范围、无线资源利用率的最小范围、无线资源控制RRC连接数的最大范围、RRC连接数的最小范围、激活态用户数的最大范围以及激活态用户数的最小范围中的至少一种；
    所述KPI目标包括协议数据单元PDU会话异常释放率、PDU会话建立失败率、异常RRC连接释放率、RRC连接建立失败率以及切换失败率至少中的一种；
    所述KQI目标包括响应成功率、响应时延以及显示成功率、显示时延以及下载速率中的至少一种。
  8. 根据权利要求6所述的负载均衡方法，其特征在于，所述负载阈值包括CAC阈值、可用RRC连接数容量阈值以及激活态用户数阈值中的至少一种；
    所述负载均衡优化指示包括第一优化指示以及第二优化指示中的至少一种，其中，所述第一优化指示用于在所述网络节点的邻区关系中指示所述网络节点的邻区是否允许所述切片以及所述波束中至少一种的负载均衡优化，所述第二优化指示为，在所述网络节点中指示是否允许所述切片以及所述波束中至少一种的负载均衡优化的小区列表；
    所述切片的负载均衡执行指示包括，在相同的切片之间执行负载均衡功能的指示，和/或，在不同的切片之间执行负载均衡功能的指示；
    所述可用容量统计指示包括只统计公共的可用容量的指示、统计专有的可用容量的指示、统计优先的可用容量的指示以及统计共享的可用容量的指示至少一种。
  9. 根据权利要求1至8中任一项所述的负载均衡方法，其特征在于，所述方法还包括：
    所述第一网络管理设备向所述第二网络管理设备发送所述网络节点的性能数据，所述网络节点的性能数据包括所述切片的KPI以及KQI；或，所述性能数据包括所述波束的KPI以及KQI；
    所述性能数据用于所述第二网络管理设备对所述负载均衡控制信息进行更新。
  10. 根据权利要求1至9中任一项所述的负载均衡方法，其特征在于，所述第一网络管理设备为域管理实体，或管理服务提供者MnS producer，或网元管理***EMS；
    所述第二网络管理设备为跨域管理实体，或管理服务消费者MnS consumer，或网络管理***NMS。
  11. 一种通信***，其特征在于，所述通信***包括第一网络管理设备、第二网络管理设备；
    所述第二网络管理设备，用于向所述第一网络管理设备发送网络节点的负载均衡控制信息，所述负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种；
    所述第一网络管理设备，用于接收所述负载均衡控制信息，配置所述网络节点的所述负载均衡控制信息。
  12. 根据权利要求11所述的通信***，其特征在于，所述第一网络管理设备，还用于向所述网络节点发送所述负载均衡控制信息，所述负载均衡控制信息用于所述网络节点执行负载均衡功能。
  13. 根据权利要求11或12所述的通信***，其特征在于，所述第一网络管理设备配置所述网络节点的所述负载均衡控制信息包括：
    所述第一网络管理设备，具体用于在所述网络节点的管理对象中配置所述负载均衡控制信息。
  14. 根据权利要求11至13中任一项所述的通信***，其特征在于，所述第一网络管理设备，还用于向所述第二网络管理设备发送所述网络节点的性能数据，所述网络节点的性能数据包括所述切片的KPI以及KQI；或，所述性能数据包括所述波束的KPI以及KQI；
    所述性能数据用于所述第二网络管理设备对所述负载均衡控制信息进行更新。
  15. 根据权利要求12所述的通信***，其特征在于，所述通信***还包括：
    网络节点，用于在所述多个切片内执行跨切片的负载均衡。
  16. 一种通信装置，其特征在于，包括用于执行权利要求1至10中任一项所述的方法。
  17. 一种第一网络管理设备，其特征在于，包括：
    接口，用于接收来自第二网络管理设备的网络节点的负载均衡控制信息，所述负载均衡控制信息包括切片的负载均衡信息以及波束的负载均衡信息中的至少一种；
    处理器，用于配置所述网络节点的负载均衡控制信息。
  18. 根据权利要求17所述的第一网络管理设备，其特征在于，
    所述处理器，具体用于在所述网络节点的管理对象中配置所述负载均衡控制信息。
  19. 根据权利要求17或18所述的第一网络管理设备，其特征在于，
    所述接口，还用于向所述网络节点发送所述负载均衡控制信息，所述负载均衡控制信息用于所述网络节点执行负载均衡功能。
  20. 根据权利要求17至19中任一项所述的第一网络管理设备，其特征在于，所述负载均衡信息包括负载均衡开关信息、负载均衡目标信息以及负载均衡策略信息中的至少一种；
    所述负载均衡开关信息包括第一指示信息或第二指示信息，所述第一指示信息用于指示开启切片以及波束中至少一种的负载均衡功能，所述第二指示信息用于指示关闭切片以及波束中至少一种的负载均衡功能。
  21. 根据权利要求17至20中任一项所述的第一网络管理设备，其特征在于，
    所述接口，还用于向所述第二网络管理设备发送所述网络节点的性能数据，所述网络节点的性能数据包括所述切片的KPI以及KQI；或，所述性能数据包括所述波束的KPI以及KQI；
    所述性能数据用于所述第二网络管理设备对所述负载均衡控制信息进行更新。
  22. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中保存有程序，当所述计算机执行所述程序时，执行如权利要求1-10中任一项所述的方法。
  23. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上执行时，所述计算机执行如权利要求1-10中任一项所述的方法。
PCT/CN2020/107971 2020-08-07 2020-08-07 一种负载均衡方法、相关设备及*** WO2022027659A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107971 WO2022027659A1 (zh) 2020-08-07 2020-08-07 一种负载均衡方法、相关设备及***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107971 WO2022027659A1 (zh) 2020-08-07 2020-08-07 一种负载均衡方法、相关设备及***

Publications (1)

Publication Number Publication Date
WO2022027659A1 true WO2022027659A1 (zh) 2022-02-10

Family

ID=80116863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/107971 WO2022027659A1 (zh) 2020-08-07 2020-08-07 一种负载均衡方法、相关设备及***

Country Status (1)

Country Link
WO (1) WO2022027659A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114554551A (zh) * 2022-04-25 2022-05-27 广州世炬网络科技有限公司 基于prb利用率的基站负载均衡方法、装置及设备
CN115277571A (zh) * 2022-07-29 2022-11-01 联想(北京)有限公司 处理方法和处理***
WO2023231468A1 (zh) * 2022-05-31 2023-12-07 华为技术有限公司 一种通信方法及装置
WO2023236774A1 (zh) * 2022-06-10 2023-12-14 华为技术有限公司 意图管理的方法与装置

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105681258A (zh) * 2014-11-19 2016-06-15 腾讯科技（武汉）有限公司 基于第三方服务器的会话方法和会话装置
CN108029062A (zh) * 2015-09-18 2018-05-11 华为技术有限公司 用于网络切片重选的***和方法
US20180331935A1 (en) * 2017-05-10 2018-11-15 Vivint, Inc. Load balancing in multiple-input multiple-output systems using a mesh network
CN110049514A (zh) * 2019-03-29 2019-07-23 中国科学院计算技术研究所 一种适用于多波束卫星网络的负载均衡控制方法
CN110115055A (zh) * 2016-12-23 2019-08-09 华为技术有限公司 用于编程和/或管理核心网络切片的***及方法
WO2020030277A1 (en) * 2018-08-09 2020-02-13 Huawei Technologies Co., Ltd. Device and method for ue registration assisted by analytics to support intra and inter network slice load balancing
CN110831068A (zh) * 2018-08-08 2020-02-21 中兴通讯股份有限公司 负荷均衡方法、装置、存储介质及电子装置
CN110972107A (zh) * 2018-09-29 2020-04-07 华为技术有限公司 一种负载均衡方法及装置
CN111083738A (zh) * 2018-10-22 2020-04-28 ***通信有限公司研究院 一种负载均衡方法及设备
CN111201831A (zh) * 2019-11-11 2020-05-26 北京小米移动软件有限公司 随机接入方法及装置、终端及存储介质

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105681258A (zh) * 2014-11-19 2016-06-15 腾讯科技（武汉）有限公司 基于第三方服务器的会话方法和会话装置
CN108029062A (zh) * 2015-09-18 2018-05-11 华为技术有限公司 用于网络切片重选的***和方法
CN110115055A (zh) * 2016-12-23 2019-08-09 华为技术有限公司 用于编程和/或管理核心网络切片的***及方法
US20180331935A1 (en) * 2017-05-10 2018-11-15 Vivint, Inc. Load balancing in multiple-input multiple-output systems using a mesh network
CN110831068A (zh) * 2018-08-08 2020-02-21 中兴通讯股份有限公司 负荷均衡方法、装置、存储介质及电子装置
WO2020030277A1 (en) * 2018-08-09 2020-02-13 Huawei Technologies Co., Ltd. Device and method for ue registration assisted by analytics to support intra and inter network slice load balancing
CN110972107A (zh) * 2018-09-29 2020-04-07 华为技术有限公司 一种负载均衡方法及装置
CN111083738A (zh) * 2018-10-22 2020-04-28 ***通信有限公司研究院 一种负载均衡方法及设备
CN110049514A (zh) * 2019-03-29 2019-07-23 中国科学院计算技术研究所 一种适用于多波束卫星网络的负载均衡控制方法
CN111201831A (zh) * 2019-11-11 2020-05-26 北京小米移动软件有限公司 随机接入方法及装置、终端及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Load balancing considering NR feature", 3GPP TSG-RAN WG3 #103, R3-190419, 16 February 2019 (2019-02-16), XP051604360 *
ZTE: "Further Discussion on Load Information Reporting for MLB", 3GPP TSG-RAN WG3 #105BIS, R3-195644, 4 October 2019 (2019-10-04), XP051792674 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114554551A (zh) * 2022-04-25 2022-05-27 广州世炬网络科技有限公司 基于prb利用率的基站负载均衡方法、装置及设备
CN114554551B (zh) * 2022-04-25 2022-09-02 广州世炬网络科技有限公司 基于prb利用率的基站负载均衡方法、装置及设备
WO2023231468A1 (zh) * 2022-05-31 2023-12-07 华为技术有限公司 一种通信方法及装置
WO2023236774A1 (zh) * 2022-06-10 2023-12-14 华为技术有限公司 意图管理的方法与装置
CN115277571A (zh) * 2022-07-29 2022-11-01 联想(北京)有限公司 处理方法和处理***
CN115277571B (zh) * 2022-07-29 2024-03-29 联想(北京)有限公司 处理方法和处理***

Similar Documents

Publication Publication Date Title
US10952105B2 (en) Communication method, source base station, target base station, core network device, and terminal device
US11877197B2 (en) Communication method and system by RRC carrying NSSAI, and corresponding core network device
US11601819B2 (en) Orchestration and configuration of E2E network slices across 3GPP core network and ORAN
EP3576457B1 (en) Communication method, access network device and core network device
WO2022027659A1 (zh) 一种负载均衡方法、相关设备及***
US20200120580A1 (en) Communication method, network device, terminal device, and system
WO2018161850A1 (en) System and method of network policy optimization
US11696184B2 (en) Quality of service manager for network slices of a network
US20220369204A1 (en) Method and device for providing service to user device by using network slice in communication system
US9462477B2 (en) Flexible network sharing
US11601367B2 (en) Systems and methods for dynamic network function resource allocation through the network repository function
US20220338106A1 (en) Slice control method and apparatus
US11064422B2 (en) System and method for enabling subscriber-based policy decisions
US11330489B2 (en) Apparatus, method and computer program
WO2021217672A1 (zh) 网络切片的负载控制方法及相关产品
US20210243592A1 (en) Pci configuration and mobility robustness optimization son functionality for 5g networks
WO2022068371A1 (zh) 通信方式的确定方法、装置及存储介质
CN110730487B (zh) 一种选择会话管理功能网元的方法、装置及***
CN113271629A (zh) 一种网络负载均衡方法、接入网设备及网络***
WO2023035925A1 (zh) 一种业务处理方法、装置和***
US20230379764A1 (en) System and method for selecting network slices based on network slice congestion information
US20230362658A1 (en) Radio access network intelligent controller (ric) based radio resource allocation for non-standalone and standalone users
US20240007931A1 (en) Systems and methods for performing access control
US20230345347A1 (en) Method for determining mec access point and apparatus
US20210297941A1 (en) Mobile network operator selection

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20948166

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20948166

Country of ref document: EP

Kind code of ref document: A1