WO2022027659A1 - Procédé d'équilibrage de charge et dispositif et système associés - Google Patents

Procédé d'équilibrage de charge et dispositif et système associés 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)
Chinese (zh)
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/fr
Publication of WO2022027659A1 publication Critical patent/WO2022027659A1/fr

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

Sont divulgués un procédé d'équilibrage de charge, ainsi qu'un dispositif et un système associés, qui sont utilisés pour gérer un équilibrage de charge de tranche et un équilibrage de charge de faisceau. Un premier dispositif de gestion de réseau peut recevoir des informations de commande d'équilibrage de charge envoyées par un second dispositif de gestion de réseau, les informations de commande d'équilibrage de charge comprenant des informations d'équilibrage de charge de tranche et/ou des informations d'équilibrage de charge de faisceau. Le premier dispositif de gestion de réseau envoie les informations de commande d'équilibrage de charge à un nœud de réseau et le nœud de réseau exécute une fonction d'équilibrage de charge en fonction des informations de commande d'équilibrage de charge.
PCT/CN2020/107971 2020-08-07 2020-08-07 Procédé d'équilibrage de charge et dispositif et système associés WO2022027659A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107971 WO2022027659A1 (fr) 2020-08-07 2020-08-07 Procédé d'équilibrage de charge et dispositif et système associés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107971 WO2022027659A1 (fr) 2020-08-07 2020-08-07 Procédé d'équilibrage de charge et dispositif et système associés

Publications (1)

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

Family

ID=80116863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/107971 WO2022027659A1 (fr) 2020-08-07 2020-08-07 Procédé d'équilibrage de charge et dispositif et système associés

Country Status (1)

Country Link
WO (1) WO2022027659A1 (fr)

Cited By (5)

* 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 联想(北京)有限公司 处理方法和处理系统
CN116155365A (zh) * 2023-03-06 2023-05-23 亚太卫星宽带通信（深圳）有限公司 一种基于高通量点波束卫星的负载均衡方法及装置
WO2023231468A1 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé et appareil de communication
WO2023236774A1 (fr) * 2022-06-10 2023-12-14 华为技术有限公司 Procédé et appareil de gestion d'intention

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 (fr) * 2018-08-09 2020-02-13 Huawei Technologies Co., Ltd. Dispositif et procédé d'enregistrement d'ue assisté par analyse permettant la prise en charge d'un équilibrage de charge de tranche intra et inter-réseau
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 (fr) * 2018-08-09 2020-02-13 Huawei Technologies Co., Ltd. Dispositif et procédé d'enregistrement d'ue assisté par analyse permettant la prise en charge d'un équilibrage de charge de tranche intra et inter-réseau
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 (7)

* 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 (fr) * 2022-05-31 2023-12-07 华为技术有限公司 Procédé et appareil de communication
WO2023236774A1 (fr) * 2022-06-10 2023-12-14 华为技术有限公司 Procédé et appareil de gestion d'intention
CN115277571A (zh) * 2022-07-29 2022-11-01 联想(北京)有限公司 处理方法和处理系统
CN115277571B (zh) * 2022-07-29 2024-03-29 联想(北京)有限公司 处理方法和处理系统
CN116155365A (zh) * 2023-03-06 2023-05-23 亚太卫星宽带通信（深圳）有限公司 一种基于高通量点波束卫星的负载均衡方法及装置

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
WO2022027659A1 (fr) Procédé d'équilibrage de charge et dispositif et système associés
US11601819B2 (en) Orchestration and configuration of E2E network slices across 3GPP core network and ORAN
US11601367B2 (en) Systems and methods for dynamic network function resource allocation through the network repository function
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
WO2018161850A1 (fr) Système et procédé d'optimisation de politique de réseau
US12075332B2 (en) System and method for enabling subscriber-based policy decisions
US9462477B2 (en) Flexible network sharing
US11330489B2 (en) Apparatus, method and computer program
US20220338106A1 (en) Slice control method and apparatus
WO2021217672A1 (fr) Procédé de commande de charge pour tranche de réseau et produit associé
CN110730487B (zh) 一种选择会话管理功能网元的方法、装置及系统
US20210243592A1 (en) Pci configuration and mobility robustness optimization son functionality for 5g networks
WO2023035925A1 (fr) Procédé, appareil et système de traitement de service
US20230379764A1 (en) System and method for selecting network slices based on network slice congestion information
WO2022068371A1 (fr) Procédé et appareil de détermination de mode de communication, et support de stockage
US20230345347A1 (en) Method for determining mec access point and apparatus
CN113271629A (zh) 一种网络负载均衡方法、接入网设备及网络系统
US20210297941A1 (en) Mobile network operator selection
US20240298252A1 (en) Ran intelligent controller (ric) enabled dynamic access and mobility management function (amf) selection
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
WO2023217733A1 (fr) Appareils et procédés de préemption de tranche de réseau

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