Network management method, apparatus and system

Abstract

A network management method is used to solve the problem that after a communication network is configured according to performance indicator requirements, the actual performance indicators of the communication network do not match the performance indicator requirements, thereby causing damage to services or waste of network resources. The method includes: a first-level network management device obtains an analysis report of a first-level managed object from a management data analysis device and / or obtains a status report of a second-level managed object from a second-level network management device, and instructs a second-level network management device to manage the second-level managed object according to the performance indicator requirements of the first-level managed object and the analysis report and / or status report.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a network management method, apparatus, and system. Background Art

[0002] In communication networks such as the 5th generation (5G) system, differentiated network services can be provided for users through the network slice (NS) method. Among them, a network slice refers to a logical network with specific network capabilities and network attributes. A network slice may include multiple subnets, such as a radio access network (RAN) subnet, a transport network (TN) subnet, and a core network (CN) subnet. Specifically, a network management device may configure the managed network according to the service requirements of users, thereby establishing a network slice instance (NSI) to provide differentiated network services for users.

[0003] However, due to the ever-changing usage of communication networks, after configuring the managed network according to performance metric requirements (such as the maximum number of user devices, the maximum number of connections, latency, latency tolerance, throughput, etc.), the actual performance metrics achieved by the managed network do not necessarily match the established performance metric requirements. Because as the service changes (such as changes in the number of concurrent users) and the network itself changes (such as changes in the working state of devices or network slices, etc.), the actual performance achieved by the managed network may exceed the requirements of the established performance requirements, thus wasting the operator's network resources, or may be lower than the requirements of the established performance requirements, thus damaging the service and reducing the user's service experience. Therefore, how to eliminate or reduce the difference between the actual performance metrics of the managed network and the established performance metric requirements, improve the matching degree between the two, and balance the satisfaction of the service level agreement (SLA) between the operator and the user and the utilization rate of the operator's network resources is a technical problem that needs to be solved urgently. Summary of the Invention

[0004] Embodiments of this application provide a network management method, apparatus, and system, which can eliminate or reduce the difference between the actual performance metrics of the managed network and the established performance metric requirements, improve the matching degree between the two, and balance the satisfaction of the SLA between the operator and the user and the utilization rate of the operator's network resources.

[0005] To achieve the above object, this application adopts the following technical solutions:

[0006] In a first aspect, a network management method is provided. This method is applied to a first-level network management device, which is connected to a second-level network management device. The first-level network management device and the second-level network management device respectively manage managed objects at different levels, and the managed objects are devices, networks, or services provided by the network. The method includes: obtaining an analysis report of the first-level managed objects from a management data analysis device and / or obtaining a status report of at least one second-level managed object from the second-level network management device, and instructing the second-level network management device to manage the second-level managed objects according to the performance index requirements of the first-level managed objects and the analysis report and / or the status report. Among them, the first-level managed objects include at least one second-level managed object or are associated with at least one second-level managed object; the analysis report includes information related to the performance indexes of the first-level managed objects and / or the resource information of the first-level managed objects; the status report includes any one or more of the following: analysis data, which is information related to the performance indexes of at least one second-level managed object and / or the resource information of at least one second-level managed object; decision data, which is a management operation that the second-level network management device decides to execute for the second-level managed objects; execution data, which is a management operation that the second-level network management device executes for the second-level managed objects based on the decision data and its execution result.

[0007] Based on the network management method described in the first aspect, the first-level network management device can determine the network configuration differences according to the performance index requirements of the first-level managed objects it manages, the analysis report of the first-level managed objects, and / or the status report of the second-level managed objects included or associated with the first-level managed objects, and then manage the second-level managed objects according to the network configuration differences to eliminate or reduce the network configuration differences, and further eliminate or reduce the differences between the actual performance indexes of the first-level managed objects and the established performance index requirements, improve the matching degree between the two, and take into account the satisfaction of the performance index requirements of the first-level managed objects and the utilization rate of the network resources allocated to the first-level managed objects.

[0008] In a possible design solution, the above-mentioned process of instructing the second-level network management device to manage the second-level managed objects according to the performance index requirements, analysis reports, and / or status reports of the first-level managed objects may include: generating management instruction information based on the performance index requirements, analysis reports, and / or status reports of the first-level managed objects, and sending the management instruction information to the second-level network management device. Among them, the management instruction information includes any one of the following: configuration operation information, including the configuration operations to be performed on the second-level managed objects, or configuration requirement information, including the configuration requirements for the second-level managed objects, or performance index requirement information, including the performance index requirements for the second-level managed objects. In this way, the network slice management service device can dynamically manage the network configuration of the network slice to meet the SLA requirements of the network slice, and can instruct the network slice subnet management service device to manage the network configuration of the network slice subnet accordingly to ensure that the network configuration of the managed network slice subnet matches the network configuration of the network slice, thereby improving the reliability and efficiency of the network service at the network slice level and the network slice subnet level.

[0009] Optionally, the management instruction information may include configuration operation information, and the configuration operation information includes any one or more of the following: adding a second-level managed object, deleting a second-level managed object, or modifying the configuration information of a second-level managed object.

[0010] Further, the above-mentioned process of generating management instruction information based on the performance index requirements, analysis reports, and / or status reports of the first-level managed objects may include: determining the network configuration differences based on the performance index requirements, analysis reports, and / or status reports of the first-level managed objects, and generating management instruction information based on the network configuration differences. Among them, the network configuration differences may be the differences between at least one second-level managed object and at least one second-level managed object that the first-level managed object needs to include or be associated with as determined according to the performance index requirements, analysis reports, and / or status reports.

[0011] Alternatively, the above-mentioned process of generating management instruction information based on the performance index requirements, analysis reports, and / or status reports of the first-level managed objects may include: determining the performance index differences based on the performance index requirements, analysis reports, and / or status reports of the first-level managed objects, and generating management instruction information based on the performance index differences. Among them, the performance index differences are the differences between the performance index measurement results of the first-level managed objects and the performance index requirements of the first-level managed objects.

[0012] Optionally, the above-mentioned process of sending the management instruction information to the second-level network management device may include: sending a closed-loop control management message to the second-level network management device, and the closed-loop control management message contains the management instruction information.

[0013] In a possible design solution, obtaining the analysis report of the first-level managed object from the management data analysis device may include: sending an analysis report subscription request message to the management data analysis device and receiving an analysis report notification message from the management data analysis device. Among them, the analysis report subscription request message may include the identifier of the first-level managed object, and the analysis report notification message may include the analysis report. Alternatively, sending an analysis report request message to the management data analysis device and receiving an analysis report response message from the management data analysis device. Among them, the analysis report request message may include the identifier of the first-level managed object, and the analysis report response message may include the analysis report.

[0014] Optionally, the performance metric-related information of the first-level managed object may be statistical information or prediction information of the measured values of the performance metrics of the first-level managed object, or the difference between the measurement results of the performance metrics of the first-level managed object and the performance metric requirements of the first-level managed object. Among them, the resource information of the first-level managed object may be statistical information or prediction information of the remaining amount of resources of the first-level managed object, or statistical information or prediction information of the resource utilization rate.

[0015] Furthermore, the information related to the performance metrics of the managed objects at the first level may include any one or more of the following: throughput statistical data of the managed objects at the first level, throughput prediction data of the managed objects at the first level, throughput distribution data of the managed objects at the first level, throughput requirement analysis data of the managed objects at the first level, average latency of the managed objects at the first level, maximum latency of the managed objects at the first level, minimum latency of the managed objects at the first level, latency jitter of the managed objects at the first level, latency tolerance of the services of the managed objects at the first level, packet delay budget of the services of the managed objects at the first level, supported moving speed of the managed objects at the first level, maximum packet loss rate of the managed objects at the first level, average packet loss rate of the managed objects at the first level, minimum packet loss rate of the managed objects at the first level, maximum packet length of the managed objects at the first level, supported positioning accuracy of the managed objects at the first level, supported synchronization accuracy level of the managed objects at the first level, supported energy consumption efficiency level of the managed objects at the first level, resource allocation priority of the managed objects at the first level, or resource allocation priority of each of at least one managed object at the second level. Among them, the resource information of the managed objects at the first level includes any one or more of the following: resource isolation level of the managed objects at the first level, analysis information on the resources of the managed objects at the first level, analysis information on the resources of at least one managed object at the second level, or analysis information on the configuration parameters of at least one managed object at the second level. That is to say, the network slice management service device can dynamically manage the network configuration related to throughput and / or latency according to the analysis report related to throughput and / or latency provided by the network analysis device to meet the SLA requirements related to throughput and / or latency.

[0016] Optionally, obtaining the status reports of at least one managed object at the second level from the second-level network management device may include: sending an operation and maintenance status request message to the second-level network management device and receiving an operation and maintenance status response message from the second-level network management device. Among them, the operation and maintenance status request message may contain the identifiers of at least one managed object at the second level; the operation and maintenance status response message may contain the status report. Or, sending an operation and maintenance status subscription request message to the second-level network management device and receiving an operation and maintenance status notification message from the second-level network management device. Among them, the operation and maintenance status subscription request message may include the identifiers of at least one managed object at the second level; the operation and maintenance status notification message may contain the status report.

[0017] Further, the status report may include analysis data. Among them, the analysis data may include one or more of the following: the mapping relationship between the throughput distribution of at least one second-level managed object and the service experience, the difference and reason between the actual throughput and the target throughput of at least one second-level managed object, or information about the services with unqualified throughput carried by at least one second-level managed object. Alternatively, the status report may include decision-making data. Among them, the decision-making data may include one or more of the following: the throughput control strategy of at least one second-level managed object, the management actions, resources or parameter configuration information for at least one second-level managed object. Alternatively, the status report may include execution data. Among them, the execution data may include one or more of the following: the management actions, resources or parameter configuration quantities executed by the second-level network management device, or the execution results.

[0018] In a possible design solution, the first-level network management device may be a network slice management service device, the first-level managed object may be a network slice, the second-level network management device may be a network slice subnet management service device, and the second-level managed object may be a network slice subnet.

[0019] In another possible design solution, the first-level network management device may be a network slice subnet management service device, the first-level managed object may be a network slice subnet, the second-level network management device may be a management device for network elements in the network slice subnet, and the second-level managed object may be a device in the network slice subnet.

[0020] In yet another possible design solution, the first-level network management device may be a communication service management service device, the first-level managed object may be a communication service or a communication service instance, the second-level network management device may be a network slice management service device, and the second-level managed object may be a network slice management service.

[0021] Second aspect, a network management device is provided. The device is applied to a first-level network management device, which is connected to a second-level network management device. The first-level network management device and the second-level network management device respectively manage managed objects at different levels, and the managed objects are devices, networks, or services provided by the network. The device includes: a processing module and a transceiver module. Among them, the transceiver module is used to obtain an analysis report of the first-level managed objects from a management data analysis device and / or obtain status reports of at least one second-level managed object from the second-level network management device. The processing module is used to instruct the second-level network management device to manage the second-level managed objects according to the performance index requirements of the first-level managed objects, as well as the analysis report and / or status report. Among them, the first-level managed objects include at least one second-level managed object or are associated with at least one second-level managed object; the analysis report includes information related to the performance indexes of the first-level managed objects and / or resource information of the first-level managed objects; the status report includes any one or more of the following: analysis data, which is information related to the performance indexes of at least one second-level managed object and / or resource information of at least one second-level managed object; decision data, which is a management operation that the second-level network management device decides to perform on the second-level managed objects; execution data, which is a management operation that the second-level network management device performs on the second-level managed objects based on the decision data and its execution result.

[0022] In a possible design solution, the processing module is further used to generate management instruction information according to the performance index requirements of the first-level managed objects, as well as the analysis report and / or status report. The transceiver module is further used to send the management instruction information to the second-level network management device. Among them, the management instruction information includes any one of the following: configuration operation information, which includes configuration operations to be performed on the second-level managed objects, or configuration requirement information, which includes configuration requirements for the second-level managed objects, or performance index requirement information, which includes performance index requirements for the second-level managed objects.

[0023] Optionally, the management instruction information may include configuration operation information, and the configuration operation information includes any one or more of the following: adding a second-level managed object, deleting a second-level managed object, or modifying the configuration information of a second-level managed object.

[0024] Optionally, the processing module is further configured to determine a network configuration difference according to the performance metric requirements of the first-level managed object, as well as the analysis report and / or the status report, and generate management indication information according to the network configuration difference. The network configuration difference may be the difference between at least one second-level managed object and at least one second-level managed object that the first-level managed object needs to include or be associated with according to the performance metric requirements, the analysis report, and / or the status report.

[0025] Alternatively, optionally, the processing module is further configured to determine a performance metric difference according to the performance metric requirements of the first-level managed object, as well as the analysis report and / or the status report, and generate management indication information according to the performance metric difference. The performance metric difference is the difference between the performance metric measurement result of the first-level managed object and the performance metric requirements of the first-level managed object.

[0026] Optionally, the transceiver module is further configured to send a closed-loop control management message to the second-level network management device, and the closed-loop control management message includes the management indication information.

[0027] In a possible design, the transceiver module is further configured to send an analysis report subscription request message to the management data analysis device and receive an analysis report notification message from the management data analysis device. The analysis report subscription request message may include the identifier of the first-level managed object, and the analysis report notification message may include the analysis report.

[0028] In another possible design, the transceiver module is further configured to send an analysis report request message to the management data analysis device and receive an analysis report response message from the management data analysis device. The analysis report request message may include the identifier of the first-level managed object, and the analysis report response message may include the analysis report.

[0029] Optionally, the performance metric related information of the first-level managed object may be the statistical information or prediction information of the measured value of the performance metric of the first-level managed object, or the difference between the performance metric measurement result of the first-level managed object and the performance metric requirements of the first-level managed object. The resource information of the first-level managed object may be the statistical information or prediction information of the remaining amount of resources of the first-level managed object, or the statistical information or prediction information of the resource utilization rate.

[0030] Further, the performance metric related information of the first - level managed object may include any one or more of the following: throughput statistical data of the first - level managed object, throughput prediction data of the first - level managed object, throughput distribution data of the first - level managed object, throughput requirement analysis data of the first - level managed object, average latency of the first - level managed object, maximum latency of the first - level managed object, minimum latency of the first - level managed object, latency jitter amount of the first - level managed object, latency tolerance of the services of the first - level managed object, packet delay budget of the services of the first - level managed object, moving speed of the users of the first - level managed object, maximum packet loss rate of the first - level managed object, average packet loss rate of the first - level managed object, minimum packet loss rate of the first - level managed object, maximum packet length of the first - level managed object, positioning accuracy supported by the first - level managed object, synchronization accuracy level supported by the first - level managed object, energy consumption efficiency level supported by the first - level managed object, resource allocation priority of the first - level managed object, or resource allocation priority of each of at least one second - level managed object. Among them, the resource information of the first - level managed object includes any one or more of the following: resource isolation level of the first - level managed object, analysis information of the resources of the first - level managed object, analysis information of the resources of at least one second - level managed object, or analysis information of the configuration parameters of at least one second - level managed object. That is to say, the network slice management service device can dynamically manage the network configuration related to throughput and / or latency according to the analysis report related to throughput and / or latency provided by the network analysis device to meet the SLA requirements related to throughput and / or latency.

[0031] In a possible design solution, the transceiver module is further configured to send an operation and maintenance status request message to the second - level network management device and receive an operation and maintenance status response message from the second - level network management device. Among them, the operation and maintenance status request message may include the identifiers of at least one second - level managed object; the operation and maintenance status response message may include a status report.

[0032] In another possible design solution, the transceiver module is further configured to send an operation and maintenance status subscription request message to the second - level network management device and receive an operation and maintenance status notification message from the second - level network management device. Among them, the operation and maintenance status subscription request message may include the identifiers of at least one second - level managed object; the operation and maintenance status notification message may include a status report.

[0033] Optionally, the status report may include analysis data. The analysis data may include one or more of the following: the mapping relationship between the throughput distribution of at least one second-level managed object and the service experience, the difference and reason between the actual throughput and the target throughput of at least one second-level managed object, or the information of the services with unqualified throughput carried by at least one second-level managed object. Alternatively, the status report may include decision-making data. The decision-making data may include one or more of the following: the throughput control strategy of at least one second-level managed object, the management actions, resources, or parameter configuration information for at least one second-level managed object. Alternatively, the status report may include execution data. The execution data may include one or more of the following: the management actions, resources, or parameter configuration amounts executed by the second-level network management device, or the execution results.

[0034] In a possible design solution, the first-level network management device may be a network slice management service device, the first-level managed object may be a network slice, the second-level network management device may be a network slice subnet management service device, and the second-level managed object may be a network slice subnet. In this way, closed-loop control at the network slice level can be achieved.

[0035] In another possible design solution, the first-level network management device may be a network slice subnet management service device, the first-level managed object may be a network slice subnet, the second-level network management device may be a management device for the network elements in the network slice subnet, and the second-level managed object may be the devices in the network slice subnet. In this way, closed-loop control at the network slice subnet level can be achieved.

[0036] In yet another possible design solution, the first-level network management device may be a communication service management service device, the first-level managed object may be a communication service or a communication service instance, the second-level network management device may be a network slice management service device, and the second-level managed object may be a network slice management service. In this way, closed-loop control at the communication service level can be achieved.

[0037] Optionally, the transceiver module may include a receiving module and a transmitting module. The receiving module is used to receive information sent by the managed object or other network management devices, and the transmitting module is used to send information to the managed object or other network management devices.

[0038] Optionally, the network management device described in the second aspect may further include a storage module that stores programs or instructions. When the processing module executes the programs or instructions, the network management device in the second aspect can execute the network management method in the first aspect.

[0039] It should be noted that the network management device described in the second aspect may be a network management equipment, such as an operation administration and maintenance (OAM) equipment, a business support system (BSS) equipment, an operations support system (OSS) equipment, or may also be a chip (system) or other components or assemblies that can be set in the network management equipment, or may also be a device including the network management equipment. This application does not make any limitations in this regard.

[0040] In addition, the technical effects of the network management device provided in the second aspect can refer to the technical effects of the network management method provided in the first aspect, which will not be elaborated here.

[0041] In a third aspect, a network management device is provided. The network management device is used to execute the network management method described in any possible implementation manner of the first aspect.

[0042] It should be noted that the network management device described in the third aspect may be a network management equipment, such as an OAM equipment, a BSS equipment, an OSS equipment, or may also be a chip (system) or other components or assemblies that can be set in the network management equipment, or may also be a device including the network management equipment. This application does not make any limitations in this regard.

[0043] In addition, the technical effects of the network management device provided in the third aspect can refer to the technical effects of the network management method provided in the first aspect, which will not be elaborated here.

[0044] In a fourth aspect, a network management device is provided. The network management device includes: a processor; wherein, the processor is used to execute the network management method described in any possible implementation manner of the first aspect.

[0045] It should be noted that the network management device described in the fourth aspect may be a network management equipment, such as an OAM equipment, a BSS equipment, an OSS equipment, or may also be a chip (system) or other components or assemblies that can be set in the network management equipment, or may also be a device including the network management equipment. This application does not make any limitations in this regard.

[0046] In addition, the technical effects of the network management device provided in the fourth aspect can refer to the technical effects of the network management method provided in the first aspect, which will not be elaborated here.

[0047] In a fifth aspect, a network management device is provided, including: a processor coupled to a memory. The processor is configured to execute a computer program stored in the memory, so that the network management device according to the fifth aspect executes the network management method in any possible implementation manner of the first aspect.

[0048] It should be noted that the network management device described in the fifth aspect may be a network management device, such as an OAM device, a BSS device, an OSS device, or may also be a chip (system) or other components or assemblies that can be set in the network management device, or may also be a device including the network management device. This application does not make any limitations in this regard.

[0049] In addition, the technical effects of the network management device provided in the fifth aspect can refer to the technical effects of the network management method provided in the first aspect, and will not be elaborated here.

[0050] In a sixth aspect, a network management device is provided, including: a processor and an interface circuit. Among them, the interface circuit is configured to receive code instructions and transmit them to the processor; the processor is configured to run the code instructions to execute the network management method described in any possible implementation manner of the first aspect.

[0051] It should be noted that the network management device described in the sixth aspect may be a network management device, such as an OAM device, a BSS device, an OSS device, or may also be a chip (system) or other components or assemblies that can be set in the network management device, or may also be a device including the network management device. This application does not make any limitations in this regard.

[0052] In addition, the technical effects of the network management device provided in the sixth aspect can refer to the technical effects of the network management method provided in the first aspect, and will not be elaborated here.

[0053] In a seventh aspect, a network management device is provided. The network management device includes a processor and a transceiver. The transceiver is used for information interaction between the network management device and other network management devices. The processor executes program instructions to execute the network management method described in any possible implementation manner of the first aspect.

[0054] It should be noted that the network management device described in the seventh aspect may be a network management device, such as an OAM device, a BSS device, an OSS device, or may also be a chip (system) or other components or assemblies that can be set in the network management device, or may also be a device including the network management device. This application does not make any limitations in this regard.

[0055] In addition, the technical effects of the network management device provided in the seventh aspect can refer to the technical effects of the network management method provided in the first aspect, and will not be elaborated here.

[0056] In an eighth aspect, there is provided a processor configured to execute the network management method according to any possible implementation manner in the first aspect.

[0057] In a ninth aspect, there is provided a network management system. The network management system includes a first-level network management device and a second-level network management device. Among them, the first-level network management device is configured to: obtain an analysis report and / or a status report associated with a management object, and according to the analysis report and / or the status report, instruct the second-level network management device to manage configuration information associated with the management object. Wherein, the management object is a physical network and / or a logical network managed by the first-level network management device, the analysis report includes characteristic information of the operation and maintenance status of the management object, and the status report includes information on the operation and maintenance status and / or operation and maintenance operations associated with the management object. The second-level network management device is configured to: manage the configuration information associated with the management object according to the instruction of the first network management.

[0058] In a tenth aspect, there is provided a computer-readable storage medium including a computer program or instruction, which, when running on a computer, causes the computer to execute the network management method according to any possible implementation manner in the first aspect.

[0059] In an eleventh aspect, there is provided a computer program product, characterized in that the computer program product includes: a computer program or instruction, which, when running on a computer, causes the computer to execute the network management method according to any possible implementation manner in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 Schematic diagram of the architecture of a network management system provided by an embodiment of the present application Figure 1 ;

[0061] Figure 2 Schematic diagram of the architecture of a network management system provided by an embodiment of the present application Figure 2 ;

[0062] Figure 3 Schematic diagram of the relationship between management objects at different levels provided by an embodiment of the present application;

[0063] Figure 4 Schematic diagram of the process of the network management method provided by an embodiment of the present application Figure 1 ;

[0064] Figure 5 Schematic diagram of the process of the network management method provided by an embodiment of the present application Figure 2 ;

[0065] Figure 6Flow diagram of the network management method provided by the embodiments of the present application Figure 3 ;

[0066] Figure 7 Flow diagram of the network management method provided by the embodiments of the present application Figure 4 ;

[0067] Figure 8 Flow diagram of the network management method provided by the embodiments of the present application Figure 5 ;

[0068] Figure 9 Structural diagram of the network management device provided by the embodiments of the present application Figure 1 ;

[0069] Figure 10 Structural diagram of the network management device provided by the embodiments of the present application Figure 2 。 Detailed implementation manners

[0070] Next, the technical solutions in the present application will be described in conjunction with the accompanying drawings. Among them, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. do not necessarily limit to be different.

[0071] The technical solutions of the embodiments of the present application can be applied to various network management systems, such as wireless fidelity (WiFi) systems, vehicle to everything (V2X) network management systems, device-to-device (D2D) network management systems, vehicle networking network management systems, 5th generation (5G) mobile network management systems, such as new radio (NR) systems, and future network management systems, such as 6th generation (6G) mobile network management systems, etc.

[0072] The present application will present various aspects, embodiments or features around a system that may include multiple devices, components, modules, etc. It should be understood and clear that each system may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions can also be used.

[0073] In addition, in the embodiments of the present application, words such as "exemplarily" and "for example" are used to give examples, illustrations or explanations. Any embodiment or design solution described as an "example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the word "example" is intended to present concepts in a specific manner.

[0074] In the embodiments of the present application, the words "of", "corresponding", "associated" and "corresponding" can sometimes be used interchangeably. It should be noted that when their differences are not emphasized, their intended meanings are the same.

[0075] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art can know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0076] To facilitate the understanding of the embodiments of the present application, first, Figure 1 and Figure 2 the network management system shown in is taken as an example to detail the network management system applicable to the embodiments of the present application.

[0077] Figure 1 It is a schematic diagram of the architecture of a network management system applicable to the network management method provided by the embodiments of the present application. As Figure 1 shown, the network management system 100 includes a first-level network management device 110 and a second-level network management device 120. The first-level network management device 110 is connected to the second-level network management device 120, and the first-level network management device 110 and the second-level network management device 120 respectively manage managed objects at different levels. Among them, the managed objects can be devices (or network elements), networks or services provided by the network. Among them, the network can be a physical network or a logical network, such as a network slice.

[0078] The first-level network management device 110 and the second-level network management device 120 are connected and manage network configurations through information interaction with each other to improve the matching degree between the actual performance indicators of the managed network and the performance indicator requirements. The functions of the first-level network management device 110 and the functions of the second-level network management device 120 can be deployed on the same physical device (in this case, the first-level network management device 110 and the second-level network management device 120 become functional modules within the physical device), or can be deployed on different physical devices. The embodiments of the present application do not make specific limitations on this.

[0079] When the first - level network management device 110 is a communication service management service (CSMS) device, the second - level network management device 120 can be a network slice management service (NSMS) device.

[0080] When the first - level network management device 110 is a network slice management service device, the second - level network management device 120 can be a network slice subnet management service (NSSMS) device.

[0081] When the first - level network management device 110 is a network slice subnet management service device, the second - level network management device 120 can be a management device of network elements in the network slice subnet. Among them, the management device of network elements can be a network function management function (NFMF) device / network functions virtualization orchestration (NFVO) device 290.

[0082] Figure 2 Schematic architecture of the network management system applicable to the network management method provided in the embodiments of this application Figure 2 As Figure 2 shown, the network management system 200 may include one or more of the following: communication service management service device 210, network slice management service device 220, network slice subnet management service device 230, management data analysis device 240, preformance management (PM) device / fault management (FM) device 250, radio access network (RAN) device 260, core network (CN) device 270, or transport network (TN) device 280.

[0083] The above communication service management service device 210 can also be referred to as a communication service management service producer (CSMS producer), a communication service management service provider (CSMS provider), a communication service management function (CSMF) device, or a communication service management device, and is used to execute a communication service closed-loop control (communication service control loop) or a communication service instance closed-loop control (communication service instance control loop).

[0084] The above network slice management service device 220 can also be referred to as a network slice management service producer (NSMS producer), a network slice management service provider (NSMS provider), a network slice service management function (NSMF) device, or a network slice management device, and is used to execute a network slice closed-loop control (network slice control loop) or a network slice instance closed-loop control (network slice instance control loop).

[0085] The above network slice subnet management service device 230 can also be referred to as a network slice subnet management service producer (NSSMS producer), a network slice subnet management service provider (NSSMS provider), a network slice subnet management function (NSSMF) device, or a network slice subnet management device, and is used to execute a network slice subnet closed-loop control (network slice subnet close loop) or a network slice subnet instance closed-loop control (network slice subnet instance close loop).

[0086] The above communication service closed-loop control and network slice closed-loop control are end-to-end (E2E) closed-loop controls, and the network slice subnet closed-loop control is a domain-level closed-loop control (domain control loop), that is, a subnet-level closed-loop control (subnet-level control loop).

[0087] It should be noted that a communication service can also be referred to as a communication service instance, a network slice can also be referred to as a network slice instance, and a network slice subnet can also be referred to as a network slice subnet instance.

[0088] The above-mentioned management data analysis device 240 can also be called a management data analytics service (MDAS) device, a management data analytics service producer, a management data analytics service provider, or a management data analytics function (MDAF) device. It is used to collect performance / alarm data of network slice subnets in each domain from the network domain through means such as a performance management device / fault management device, aggregate and process these performance / alarm data at different levels such as communication service, network slice, and network slice subnet, so as to obtain aggregated performance information and alarm information, and provide it to the network management device at the corresponding level. It should be understood that the function of the management data analysis device can be independently deployed in a certain physical device, or can be deployed in combination with other functional devices. For example, it can be deployed in combination with the network management device at any level in the embodiments of the present application (in this case, the management data analysis device becomes an internal functional module of the network management device at this level).

[0089] Among them, a network slice can include one or more network slice subnets, such as a radio access network slice subnet (RANNSSI), a core network slice subnet (CN NSSI), and a transport network slice subnet (TN NSSI). That is, a network slice is an end-to-end logical network slice composed of network slice subnets in multiple domains, and the resource part of the communication service is mapped to the network slice. It is a communication service / communication service instance provided by the network slice instance for one or more tenants, and they can all be used as management objects.

[0090] It should be noted that the above-mentioned various "producers" can also be "consumers" at the same time, using the services provided by other "producers".

[0091] A managed object refers to one of the following items managed by a network management device: a physical network, services provided by a physical network, a logical network, services provided by a logical network, components of a physical network and a logical network (such as devices, network elements), or services provided thereby. For the convenience of description, the managed objects managed by the first-level network management device 110 are referred to as first-level managed objects, and the managed objects managed by the second-level network management device 120 are referred to as second-level managed objects. Specifically, a managed object may be one of the following items: a communication service instance, a subnetwork, a network slice, a network slice subnetwork, a communication service, a device, or a network element. Optionally, relative to a network management device, a managed object may also be referred to as a managed network, managed entities, a managed logical network, a managed network device, etc. Similarly, relative to a managed object, a network management device may also be referred to as a management entity or a management node, which is not specifically limited in the embodiments of the present application. Table 1 below lists network management devices and corresponding managed objects.

[0092] Table 1

[0093]

[0094] Table 2

[0095]

[0096] As shown in Table 1, a communication service or a communication service instance is a managed object of a communication service management service device; a network slice or a network slice instance is a managed object of a network slice management service device; a network slice subnetwork or a network slice subnetwork instance is a managed object of a network slice subnetwork management service device. Among them, a network slice subnetwork includes a network slice subnetwork in a radio access network domain, a network slice subnetwork in a core network domain, and a network slice subnetwork in a transmission domain.

[0097] Exemplarily, the specific referential contents of the first-level network management device, the first-level managed object, the second-level network management device, and the second-level managed object in the embodiments of the present application under closed-loop control at different levels may be as shown in Table 2.

[0098] For ease of description, in the embodiments of this application, the communication service management service device, CSMS device, CSMF device, communication service management service producer, communication service management service provider, and communication service management device are collectively referred to as the communication service management service device; the network slice management service device, NSMS device, NSMF device, network slice management service producer, and network slice management service provider are collectively referred to as the network slice management service device; the network slice subnet management service device, NSSMS device, NSSMF device, network slice subnet management service producer, and network slice subnet management service provider are collectively referred to as the network slice subnet management service device; and the management data analysis service device, MDAS device, management data analysis function device, MDAF device, management data analysis service producer, and management data analysis service provider are collectively referred to as the management data analysis device.

[0099] The devices in the above access network slice subnet are referred to as access network devices, which can be devices with wireless transceiver functions or chips or chip systems that can be set in such devices, including: access points (APs) in a wireless fidelity (WiFi) system, such as home gateways, routers, servers, switches, bridges, etc., evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless relay nodes, wireless backhaul nodes, transmission and reception point (TRP or transmission point, TP), etc. It can also include 5G, such as gNB in a new radio (NR) system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), a road side unit (RSU) with base station functions, etc.

[0100] The devices in the above core network slice subnets are called core network devices, such as access and mobility management function (AMF) devices, session management function (SMF) devices, user plane function (UPF) devices, policy control function (PCF) devices, unified data management (UDM) devices, and application function (AF) devices. Among them, AMF devices are mainly responsible for mobility management in the wireless network, such as user location updates, user network registration, cell handovers, etc. SMF devices are mainly responsible for session management in the wireless network, such as session establishment, modification, release, etc. Specific functions may include allocating Internet protocol (IP) addresses for users, selecting UPF devices that provide packet forwarding functions, etc. PCF devices are mainly responsible for providing various policies to AMF devices and SMF devices, such as network slice selection policies, quality of service (QoS) policies, etc. UPF devices are mainly responsible for processing user packets, such as forwarding, charging, etc. UDM devices are mainly used to store user data, such as subscription information, authentication / authorization information. AF is mainly responsible for providing services for the 3rd generation partnership project (3GPP) network, such as influencing service routing, interacting with PCF devices for policy control, etc.

[0101] The devices in the above transport network slice subnets are called transport network devices, including network devices on the transport network side of the above network management system, which provide long-distance data transmission services and can be classified by type into: optical fiber transport network devices, satellite transport network devices, or other types of transport network devices.

[0102] Specifically, communication can be interacted between a communication service management service device and a network slice management service device, between the network slice management service device and a network slice subnet management service device, between the network slice subnet management service device and a management device of a network element in the network slice subnet, between the communication service management service device and a management data analysis device, between the network slice management service device and the management data analysis device, and between the network slice subnet management service device and the management data analysis device. A communication service management service device can interact with one or more network slice management service devices, a network slice management service device can interact with one or more network slice subnet management service devices, and a network slice subnet management service device can interact with one or more management devices of network elements in a network slice subnet (such as an NFMF device).

[0103] Figure 3 This is a schematic diagram of the relationship between managed objects at different levels provided by the embodiments of the present application. In this figure, a communication service 310 (or a communication service instance) can be associated with or use one or more network slices 320, and multiple communication services 310 can be associated with or use the same network slice 320. Similarly, a network slice 320 can include multiple network slice subnets 330, and multiple network slices 320 can include the same network slice subnet 330. The network slice subnet 330 can include: a network slice subnet 340 of the access network, a network slice subnet of the transport network ( Figure 3 not shown in the figure) and a network slice subnet 350 of the core network. Optionally, the network slice subnet 330 can also nestedly include another network slice subnet 330. For example, communication service 1 and communication service 2 can jointly be associated with or use network slice 1, communication service 2 is also associated with or uses network slice 2, and communication service 3 is associated with or uses network slice 3; network slice 1 includes network slice subnets 1, 2, and 3, network slice 2 includes network slice subnet 2, and network slice 3 includes network slice subnet 3; network slice subnet 1 nestedly includes an access network slice subnet -1 and a core network slice subnet -1; network slice 2 includes network slice subnet 2; network slice subnet 2 nestedly includes an access network slice subnet -2 and a core network slice subnet -2; network slice 3 includes network slice subnet 3; network slice subnet 3 nestedly includes an access network slice subnet -2 and a core network slice subnet -3. It can be seen that the access network slice subnet -2 is shared by network slice subnet 2 and network slice subnet 3.

[0104] It should be noted that the network management method provided by the embodiments of the present application is applicable to Figure 1 or Figure 2 the network management system shown in the figure, and the specific implementation can refer to the following method embodiments.

[0105] It should be noted that the solution in the embodiments of this application can also be applied to other network management systems, and the corresponding device or apparatus names can also be replaced with the device or apparatus names corresponding to the functions in other network management systems. In addition, the various devices described in the embodiments of this application can also be referred to as network elements, such as access network elements, core network elements, etc., and the embodiments of this application do not make specific limitations on this.

[0106] It should be understood that Figure 1 and Figure 2 are only simplified schematic diagrams shown for ease of understanding. The network management system provided by the embodiments of this application may further include other network devices, and / or, other terminal devices, Figure 1 and Figure 2 which are not drawn in the figure.

[0107] Next, the network management method provided by the embodiments of this application will be specifically described in conjunction with Figures 4 - 8 The network management method provided by the embodiments of this application will be specifically elaborated.

[0108] Figure 4 is a schematic flow chart of the network management method provided by the embodiments of this application Figure 1 . This network management method is applicable to Figure 1 or Figure 2 The network management system shown in the figure, and includes the following steps:

[0109] S401, the first-level network management device obtains the analysis report of the first-level managed object from the management data analysis device and / or obtains the status reports of at least one second-level managed object from the second-level network management device.

[0110] Specifically, the first-level managed object includes at least one second-level managed object, or is associated with at least one second-level managed object. For example, in order to provide a communication service instance (or communication service) to a customer, at least one network slice instance is required to support the communication service. Then, the communication service instance is the first-level managed object, and each network slice instance in the at least one network slice instance is a second-level managed object.

[0111] Specifically, the analysis report may include information related to the performance metrics of the first-level managed object and / or the resource information of the first-level managed object.

[0112] Among them, the information related to the performance metrics of the first-level managed object is the statistical information or prediction information of the measurement results of the performance metrics of the first-level managed object, or the difference between the measurement results of the performance metrics of the first-level managed object and the performance metric requirements of the first-level managed object; the information related to the performance metrics of the first-level managed object may include any one or more of the following:

[0113] - Throughput statistical data of the first-level managed object; the throughput statistical data of the managed object refers to the average throughput of all users of the managed object (such as a network slice) within a certain time range; or,

[0114] - Throughput prediction data of the first-level managed object; the throughput prediction data of the managed object refers to the predicted average throughput of all users of the managed object (such as a network slice) within a certain future time range; or,

[0115] - Throughput distribution data of the first-level managed object; the throughput distribution data of the managed object refers to the distribution of the statistical information or prediction information of the throughput statistical data of the managed object (such as a network slice) in different time ranges and / or different coverage areas; or,

[0116] - Throughput requirement analysis data of the first-level managed object; the throughput requirement analysis data of the managed object refers to the throughput capacity requirement that the managed object (such as a network slice) needs to support, calculated or analyzed based on information such as the number of online users, service types, and traffic volume; or,

[0117] - Average latency of the first-level managed object; the average latency of the managed object refers to the average end-to-end latency of the services supported by the managed object (such as a network slice), for example, the average latency between the terminal device and the anchor UPF device; or,

[0118] - Maximum latency of the first-level managed object statistically by service or user; the maximum latency of the managed object statistically by service or user refers to the maximum end-to-end latency of a certain type of service or a certain user supported by the managed object (such as a network slice), for example, the maximum latency between the terminal device and the anchor UPF device; or,

[0119] - Minimum latency of the first-level managed object statistically by service or user; the minimum latency of the managed object statistically by service or user refers to the minimum end-to-end latency of a certain type of service or a certain user supported by the managed object (such as a network slice), for example, the minimum latency between the terminal device and the UPF device; or,

[0120] - Latency jitter of the first-level managed object; the latency jitter of the managed object refers to the change in the end-to-end latency of the service or the end-to-end latency of the network or the latency of a certain communication path in the network, which causes the change in the rate of data packets arriving at the target node in the managed object (such as a network slice); or,

[0121] - Delay tolerance of the first - level managed object; the delay tolerance of a managed object refers to the difference between the delay requirement of the service supported by the managed object (such as a network slice) and the maximum acceptable delay; or

[0122] - Packet delay budget (PDB) of the first - level managed object; the packet delay budget of a managed object refers to the upper limit of the packet transmission delay between two transmission nodes on the data transmission path in the managed object (such as a network slice) or the upper limit of the packet processing delay within a certain network node. For example, in a 5G network, the upper limit of the packet transmission delay between a terminal device and a UPF device; or,

[0123] - Mobile speed supported by the first - level managed object; the mobile speed supported by a managed object refers to the maximum mobile speed of the user equipment supported by the managed object (such as a network slice), or the average mobile speed of all online users within a certain time range, or the average mobile speed expected to be supported within a certain future time range; or,

[0124] - Maximum packet loss rate of the first - level managed object; the maximum packet loss rate of a managed object refers to the maximum value of the packet loss rate of a certain service supported by the managed object (such as a network slice) or all services of a certain online user; or,

[0125] - Average packet loss rate of the first - level managed object; the average packet loss rate of a managed object refers to the average value of the packet loss rate of a certain service supported by the managed object (such as a network slice) or all services of a certain online user; or,

[0126] - Minimum packet loss rate of the first - level managed object; the minimum packet loss rate of a managed object refers to the minimum value of the packet loss rate of a certain service supported by the managed object (such as a network slice) or all services of a certain online user; or,

[0127] - Maximum packet length of the first - level managed object; the maximum packet length of a managed object refers to the maximum data packet length of a certain service supported by the managed object (such as a network slice) or all services of a certain online user; or,

[0128] - Positioning accuracy supported by the first - level managed object; the positioning accuracy supported by a managed object refers to the accuracy that the positioning technology supported by the managed object (such as a network slice) can achieve for positioning the user terminal. For example, the horizontal error of the positioning result < 5 meters and the vertical error < 3 meters.

[0129] - The clock synchronization accuracy supported by the first-level managed object; the clock synchronization accuracy supported by the managed object refers to the degree of synchronization between the devices or network elements in the managed object (such as a network slice) and the standard clock. For example, the device or network element can use the IEEE 1588 Precision Time Protocol to synchronize its internal clock to a difference of only 1 microsecond (μs) to 10 nanoseconds (ns) from the standard clock; or,

[0130] - The energy consumption efficiency supported by the first-level managed object, where the energy consumption efficiency supported by the managed object refers to the ratio of the performance of the managed object (such as a network element) to the energy consumption, for example, the ratio of the throughput per unit time to the power consumption; or,

[0131] - The resource allocation priority of the first-level managed object; the resource allocation priority of the managed object refers to the priority order in which the managed object (such as a network slice) is allocated network resources, and the managed object with a higher priority is allocated network resources first; or,

[0132] Or the resource allocation priority of each second-level managed object in at least one second-level managed object.

[0133] Specifically, the resource information of the first-level managed object is statistical information or prediction information on the remaining amount of resources of the first-level managed object, or statistical information or prediction information on the resource utilization rate; the resource information of the first-level managed object may include any one or more of the following:

[0134] - The resource isolation level of the first-level managed object; the resource isolation level of the managed object refers to the sharing level of the network resources of the managed object (such as a network slice), for example, complete resource independence, partial resource sharing, all resource sharing, etc., also known as the resource sharing level.

[0135] Analysis information on the resources of the first-level managed object,

[0136] Analysis information on the resources of at least one second-level managed object (including recommended resource configurations), or analysis information on the configuration parameters of at least one second-level managed object (including recommended configuration parameters).

[0137] Specifically, the first-level network management device can receive the analysis report of the first-level managed object from the MDAS device through a subscription-notification mechanism. For details, see other embodiments in this application, such as Figure 5 The corresponding embodiments; the first-level network management device can also receive the analysis report of the first-level managed object from the MDAS device through a request-response mechanism. For details, see other embodiments in this application, such as Figure 5 The corresponding embodiments.

[0138] Specifically, the status report of the second-level managed object includes any one or more of the following:

[0139] (1) Analysis data, which is information related to the performance metrics of at least one second-level managed object and / or the resource information of at least one second-level managed object; among them, the items included in the information related to the performance metrics of the second-level managed object are similar to those included in the information related to the performance metrics of the first-level managed object above. For example, it includes the throughput statistical data of the second-level managed object, the resource allocation priority of the second-level managed object, etc.; the items included in the resource information of the second-level managed object are similar to those included in the resource information of the first-level managed object above. For example, it includes the resource isolation level of the second-level managed object, the configuration parameters of the second-level managed object.

[0140] (2) Decision data, which is the management operation to be performed on the second-level managed object by the second-level network management device based on the analysis data;

[0141] (3) Execution data, which is the management operation performed by the second-level network management device on the second-level managed object based on the decision data and its execution result.

[0142] Among them, the attributes of the analysis data may include identification (ID), type, and content. Among them, the identification represents the identification corresponding to a certain analysis data. For example, the ID of the latency analysis data may be 1, and the ID of the throughput analysis data may be 2. The type represents the classification of the analysis data, and the classification may include but is not limited to: latency analysis, throughput analysis. The content refers to the specific content of the analysis data. For example, the content may include average latency, maximum latency, minimum latency, etc. The content can be implemented using data structures such as arrays, structures, classes, etc., and can contain one or more <key, value> pairs. Among them, the keys may include but are not limited to: key performance indicator (KPI) statistics information, performance measurement indicator statistics information, root cause, and gap analysis with closed-loop control objectives. The values may include one or more of the following: the mapping relationship between the service parameter distribution and the service experience QoE, the difference and root cause between the actual service parameters and the target service parameters, or the service information where the service parameters do not meet the standards. Among them, the service parameters may include but are not limited to: throughput parameters, mobility management parameters, or QoE. The service information where the service parameters do not meet the standards may include one or more of the following: the list of cells / gNBs with average throughput not meeting the standards, the statistical information of the number of terminal devices / connections / signal strength distribution / service type distribution within the coverage area with average throughput not meeting the standards, and the analysis information of the quality of service (QoS) measurement values of the services with average throughput not meeting the standards.

[0143] The following performance indicators take the downlink (DL) and / or uplink (UL) throughput as an example to describe the analysis data of the managed objects at each level.

[0144] (1) The mapping relationship between the DL and / or UL average throughput level statistics and the network slice QoE

[0145] Exemplarily, divided by coverage area and service type, the mapping relationship may include one or more of the following: the downlink throughput distribution of the managed objects at each level, the uplink throughput distribution of the managed objects at each level, the downlink throughput QoE mapping of the managed objects at each level, and the uplink throughput QoE mapping of the managed objects at each level.

[0146] (2) The difference and root cause between the DL and / or UL average throughput level and the throughput target of the managed objects at each level

[0147] Exemplarily, the throughput target difference and root cause may include one or more of the following: the downlink throughput difference of managed objects at each level, the uplink throughput distribution of managed objects at each level.

[0148] (3) DL (or UL) average throughput poor-quality cell / gNB list (poor quality means that the relevant indicators are lower than the preset threshold)

[0149] Exemplarily, it may include one or more of the following: the downlink throughput difference of managed objects at each level, the uplink throughput distribution of managed objects at each level.

[0150] (4) Statistical information on the number of terminal devices / connections / signal strength distribution / service type distribution in the DL (or UL) average throughput poor-quality coverage area

[0151] Exemplarily, it may include one or more of the following: the number of terminal devices with poor downlink throughput of managed objects at each level, the number of terminal devices with poor downlink throughput of managed objects at each level, the proportion of the coverage area with poor downlink throughput of managed objects at each level, the proportion of the coverage area with poor uplink throughput of managed objects at each level.

[0152] (5) QoS measurement analysis of DL (or UL) average throughput poor-quality services (statistics of QCI and QoS flow measurement information)

[0153] Exemplarily, it may include one or more of the following: QoS measurement analysis information of DL average throughput poor-quality services of managed objects at each level, QoS measurement analysis information of UL average throughput poor-quality services of managed objects at each level.

[0154] The following performance indicators describe the status report of managed objects at each level by taking DL and / or UL throughput as an example.

[0155] Among them, the analysis data of managed objects at each level may include the following types:

[0156] (1) The mapping relationship between the average throughput level statistics and QoE according to the throughput coverage area and service type may include but is not limited to: the DL throughput distribution of managed objects at each level, the UL throughput distribution network of managed objects at each level, DL throughput QoE mapping, UL throughput QoE mapping.

[0157] (2) The difference and root cause between the actual service parameters and the target service parameters may include: the DL throughput difference of managed objects at each level, the UL throughput distribution of managed objects at each level.

[0158] (3) Average throughput poor-quality cell / gNB list, which may include: DL throughput differences of managed objects at each level, UL throughput distributions of managed objects at each level.

[0159] (4) Statistical information on the number of terminal devices / connections / signal strength distribution / service type distribution within the average throughput poor-quality coverage area, which may include: the number of DL throughput poor-quality terminal devices of managed objects at each level, the number of UL throughput poor-quality terminal devices of managed objects at each level, the proportion of the DL throughput poor-quality coverage area of managed objects at each level, and the proportion of the UL throughput poor-quality coverage area of managed objects at each level.

[0160] (5) QoS measurement and analysis of average throughput poor-quality services, which may include: QoS measurement and analysis of DL throughput poor-quality services and QoS measurement and analysis of UL throughput poor-quality services of managed objects at each level.

[0161] The attributes of the above decision data include metrics, categories, and content. Among them, the metric is used to represent the corresponding service parameter. The content is of array type and can contain one or more key-value pairs. The key-value pairs may include, but are not limited to: increasing resources, decreasing resources, increasing parameter configuration, decreasing parameter configuration, etc. Among them, the decision data may include the following types:

[0162] (1) Adopt a control strategy based on average throughput. For example, the control strategy can be based on a mapping table of throughput levels and radio resource configurations.

[0163] (2) Increase or decrease network slice resources. Network slice resources include, but are not limited to, RAN resources and CN resources.

[0164] (3) Increase or decrease communication service resources. Communication service resources include, but are not limited to, RAN resources and CN resources.

[0165] (4) The maximum value and / or guaranteed value of network slice resource configuration. The maximum value refers to the upper limit of resource configuration, and the guaranteed value refers to the lower limit of resource configuration.

[0166] (5) The maximum value / guaranteed value configuration management quantity of communication service resource configuration.

[0167] Table 3

[0168]

[0169] The attributes of the above-mentioned execution data include metrics, actions, management quantities, and execution results. Among them, metrics are used to represent corresponding business parameters; actions refer to operations performed on specific managed objects. For example, actions can include operations such as increasing or decreasing resources, increasing or decreasing parameter configurations, etc. Management quantities contain management values corresponding to one or more managed objects. Among them, management values can include resource management quantities, resource management step sizes, and resource management frequencies.

[0170] It should be noted that the operation and maintenance status and / or operation and maintenance operations related to the managed object include, but are not limited to, all or part of the analysis reports related to the operation and maintenance status, such as analysis data, or information obtained by further processing the analysis data or management information based on the analysis data, such as network configuration management decision information, execution action information, execution result information, etc.

[0171] Taking throughput as an example of performance metrics, the exemplary content included in the status reports of managed objects at each level is shown in Table 3. It should be understood that the performance metrics in the status report content in Table 3 can also be other performance metrics. Other performance metrics can include latency, load, reliability, etc.

[0172] Table 4

[0173]

[0174] The exemplary content included in the status reports of other performance metrics is shown in Table 4. Among them, the SLA metric quality difference statistics can include, but are not limited to: SLA metric values, grades, target completion degrees or gap analyses, time / position distributions. KPI statistics / forecast analyses can include, but are not limited to: grades, distributions, mapping relationships with QoE, impact analyses. KPI quality difference / alarm statistics can include, but are not limited to: KPI metric values, grades, target completion degrees or gap analyses, time / position distributions, degrees of impact. KPI statistics / forecast analyses can include, but are not limited to: grades, distributions, mapping relationships with QoE, impact analyses. KPI quality difference / alarm statistics can include, but are not limited to: KPI metric values, grades, target completion degrees or gap analyses, time / position distributions, degrees of impact. In Table 4, the communication service steady-state time limit indicates that the measurement results of the SLS metrics of the communication service remain within a preset value range within a certain time range.

[0175] In addition to throughput, the business parameters mentioned in the above analysis information and analysis data can also include network slice quality of experience (QoE) and mobility management. The exemplary content included in the status report formed with network slice quality of experience as a metric is shown in Table 5 below.

[0176] Table 5

[0177]

[0178] In the analysis data column of Table 5, the service QoE quality difference statistics may include but are not limited to: serviceProfile satisfaction report for the network slice service description model, the proportion of the number of users / volume of services / coverage area / time period with service QoE level lower than the target value and the size of the gap). The root causes of service QoE quality difference may include but are not limited to: wireless coverage problems / congestion problems. The target improvement suggestions for service QoE may include but are not limited to: such as targets / distributions / relevant KPI target suggestions for network slices. KPI prediction information may include but is not limited to: latency, uplink throughput, downlink throughput, trend prediction of latency / cross-domain service description model, network slice load analysis / prediction. KPI quality difference / alarm statistics may include but are not limited to: cross-domain service description model satisfaction report, E2E latency, difference analysis of uplink / downlink throughput lower than the target value. The root causes of KPI quality difference may include but are not limited to: KPI thresholds / alarm thresholds such as congestion, high load, weak coverage, etc. The KPI improvement target suggestions may include but are not limited to: E2E latency, E2E uplink / downlink throughput target suggestions, analysis information of the network slice subnets affected. For example, RAN NSSI-ID = 1 indicates that the access network slice subnet identified as 1 is affected, and the service experience can be improved by managing the resources of the access network slice subnet identified as 1.

[0179] In the decision data column of Table 5, the serviceProfile update request may include but is not limited to: for example, if the latency cannot be guaranteed, it is decided to request the upper-layer closed-loop to modify the latency / rate guarantee thresholds for the network slice in the serviceProfile. The network slice closed-loop control strategies adopted may include but are not limited to: network slice resource management strategies based on latency and load thresholds. The network configuration update request may include but is not limited to: if the single-domain latency cannot be guaranteed, it is decided to request the upper layer to modify the latency guarantee threshold for the single-domain network slice subnet in the network slice description model (sliceProfile). The network slice subnet closed-loop control strategies adopted may include but are not limited to: radio resource management strategies based on latency / coverage conditions and load thresholds. For a request to the cross-domain management function to reduce the relevant resources of a certain other network slice, for example, the network slice management service device of network slice -1 requests to manage the network resources of network slice -2 in order to obtain some of the resources occupied by network slice -2. Among them, network slice -1 represents the network slice identified as 1, and network slice -2 represents the network slice identified as 2.

[0180] In the data execution column of Table 5, the communication service resource increase / decrease actions may include, but are not limited to, the management amount determined according to the decision. The network slice resource increase / decrease actions may include, but are not limited to, the management amount determined according to the decision.

[0181] The exemplary content included in the status report formed with mobility management requirements as indicators is shown in Table 6 below:

[0182] Table 6

[0183]

[0184] In the data analysis column of Table 6, the service experience mobility-related statistics / forecasts may include, but are not limited to, the service QoE statistics corresponding to different mobile speed level services / terminal devices. The service experience mobile performance quality difference statistics may include, but are not limited to, the proportion and gap size of the number of users / traffic volume / coverage area / time period where the service QoE mobility-related statistics are lower than the target value / threshold. The root cause of the service experience mobile performance quality difference may include, but are not limited to, such as wireless coverage problems / congestion problems. The analysis scenario ID may include, but are not limited to, the handover between the dual connectivity (EN-DC) scenario and the stand-alone networking (SA) scenario. The mobility-related KPI statistics / forecast information may include, but are not limited to, the handover success rate distribution, the handover service interruption time, the uplink / downlink service throughput during handover, and the analysis / forecast of the service type / traffic volume / load related to handover. The mobility-related KPI quality difference / alarm statistics may include, but are not limited to, the analysis of the difference where the handover success rate is lower than the target value and the uplink / downlink service delay / throughput during handover is lower than the target value. The root cause of the mobility-related KPI quality difference may include, but are not limited to, such as congestion, high load, weak coverage and other KPI thresholds / alarm thresholds. The handover parameter analysis may include, but are not limited to, the terminal device measurement report period, the trigger threshold, and the handover condition parameters.

[0185] In the decision data column of Table 6, for the status report of the network slice, the handover performance target update request may include, but is not limited to, that the handover interruption delay / throughput cannot be guaranteed, and it is decided to request the upper layer closed-loop to modify the delay / rate guarantee threshold during handover and the mobile rate support level is reduced. For the status report of the network slice subnet, the handover performance target update request may include, but is not limited to, for example, the access network single-domain network slice subnet delay / throughput during the air interface handover cannot be guaranteed, and it is decided to request the upper layer network slice closed-loop to modify the air interface delay / throughput guarantee threshold of the access network slice subnet in the sliceProfile. The handover parameter modification may include, but is not limited to, modifying the air interface handover parameters such as handover wireless conditions.

[0186] In the data execution column of Table 6, for the status report of network slices, the handover performance target update request may include, but is not limited to: the handover interruption delay / throughput cannot be guaranteed, and it is decided to request the upper-layer closed-loop to modify the delay / rate guarantee threshold during handover, and the mobile rate support level is reduced. For the status report of network slice subnets, the handover performance target update request may include, but is not limited to: the handover interruption delay / throughput cannot be guaranteed, and it is decided to request the upper-layer closed-loop to modify the delay / rate guarantee threshold during handover, and the mobile rate support level is reduced.

[0187] It should be noted that the above Tables 3 to 6 are only several examples of the above status reports. In actual applications, other parameters may also be used, which are not listed here one by one.

[0188] Specifically, the first-level network management device can receive the status reports of at least one second-level managed object from the second-level network management device through a subscription-notification mechanism. For details, see other embodiments in this application, such as Figure 5 the corresponding embodiments; the first-level network management device can also receive the status reports of at least one second-level managed object from the second-level network management device through a request-response mechanism. For details, see other embodiments in this application, such as Figure 5 the corresponding embodiments.

[0189] S402, the first-level network management device instructs the second-level network management device to manage the second-level managed object according to the performance index requirements, analysis report, and / or status report of the first-level managed object.

[0190] Specifically, the first-level network management device generates management instruction information according to the performance index requirements, analysis report, and / or status report of the first-level managed object, and then sends the management instruction information to the second-level network management device; among them, the management instruction information includes any one of the following:

[0191] Configuration operation information, including the configuration operations to be performed on the second-level managed object; or,

[0192] Configuration requirement information, including the configuration requirements for the second-level managed object; or,

[0193] Performance index requirement information, including the performance index requirements for the second-level managed object.

[0194] Specifically, the configuration operation information includes any one or more of the following:

[0195] Adding one or more second-level managed objects, or,

[0196] Deleting one or more second-level managed objects, or,

[0197] Modify the configuration information of one or more second-level managed objects.

[0198] Specifically, the configuration requirement information can be the requirements for the quantity and configuration of the second-level managed objects. For example, a total of 3 second-level managed objects are required, and each second-level managed object supports a bandwidth of 10 million bits per second (Mbps). The second-level network management device can perform management operations based on the situation of the second-level managed objects already included or associated with the first-level managed object. For example, assuming that 2 second-level managed objects are already included or associated, then add 1 second-level managed object that supports a 10 Mbps bandwidth. Another example, assuming that 3 second-level managed objects are already included, but each second-level managed object supports an 8 Mbps bandwidth, then add resources that can support a 2 Mbps bandwidth to each of these 3 second-level managed objects.

[0199] Exemplarily, the performance metric requirements of the second-level managed objects can be the requirements for latency. For example: it is required that 2 second-level managed objects both support a maximum latency of 10 milliseconds (ms). The second-level network management device can perform management operations based on the situation of the second-level managed objects already included or associated with the first-level managed object. For example, assuming that the maximum latency supported by 2 second-level managed objects already included or associated is 15 ms, the second-level network management device modifies the positions of the 2 second-level managed objects or adds resources to improve scheduling, so that the maximum latency supported by these 2 second-level managed objects is reduced to 10 ms.

[0200] Specifically, the first-level network management device can generate management indication information through at least the following two methods.

[0201] Generation method 1: The first-level network management device determines the network configuration difference based on the performance metric requirements of the first-level managed object and the analysis report and / or status report, and then generates management indication information based on the network configuration difference. This management indication information is used to enable the second-level network management device to reduce or eliminate the network configuration difference.

[0202] Specifically, the network configuration difference refers to the difference between at least one second-level managed object MOList1 currently included or associated with the first-level managed object and at least one second-level managed object MOList2 that the first-level managed object needs to include or needs to be associated with according to the performance metric requirements and the analysis report and / or status report, including the difference in the quantity of the second-level managed objects and / or the difference in the network configuration of the second-level managed objects.

[0203] Specifically, the method for generating management indication information based on network configuration differences is illustrated as follows.

[0204] Example 1: The network configuration difference is the difference in the number of managed objects at the second level. Assume that the current first-level managed object contains or is associated with M second-level managed objects (where M can be determined, for example, according to the performance index requirements of the first-level managed object and the initially estimated performance index achievement efficiency; the initially estimated performance index achievement efficiency is, for example, 100 Mbps throughput per second-level managed object). Then, using 2 second-level managed objects in "parallel" to form a first-level managed object can achieve a throughput of 200 Mbps, and using 2 second-level managed objects in "series" to form a first-level managed object can achieve a throughput of 100 Mbps. According to the performance index requirements of the first-level managed object, as well as the analysis report and / or status report, it is determined that the first-level managed object needs to contain or be associated with N second-level managed objects (for example, first determine the latest performance index achievement efficiency according to the analysis report or status report, and then determine N according to the performance index requirements and the new performance index achievement efficiency; taking the case where the second-level managed objects are in parallel to form the first-level managed object as an example, the new performance index achievement efficiency is 50 Mbps throughput per second-level managed object, then to achieve the same 200 Mbps throughput, it is determined that 4 second-level managed objects are needed). Then the network configuration difference D is N - M second-level managed objects. Assume that the network resource configurations within these N + M second-level managed objects are all the same. If D is greater than zero, it means that the network resource configuration used to implement the first-level managed object, that is, the number of second-level managed objects, does not meet the performance index requirements for the first-level managed object, which will damage the user services running based on the first-level managed object, thus affecting the user experience. Therefore, the generated management indication information instructs the second-level network management device to add N - M second-level managed objects (of course, it will also instruct the specific configuration parameters of each second-level managed object). If D is less than zero, it means that the network resource configuration exceeds the performance index requirements, which will waste the operator's network resources, thus reducing the operator's input-output ratio. Therefore, the generated management indication information instructs the second-level network management device to delete M - N second-level managed objects. If D is equal to zero, that is, N = M, it means that the network resource configuration exactly meets the performance index requirements, which is exactly the result expected by the operator. Therefore, the first-level network management device can either not generate management indication information or generate management indication information in the form of "maintain configuration".

[0205] Example 2: The network configuration difference is the difference in the network configuration of the managed object at the second level. Assume that the current managed object at the first level contains or is associated with 1 managed object at the second level, and the resource configuration of this managed object at the second level is A (for example, a network resources that can support a 2 Mbps bandwidth) (for example, initially determined according to the performance index requirements of the managed object at the first level and the initial estimated performance index achievement efficiency; for example, the initial estimated performance index achievement efficiency is 100%, that is, the network resources that support a 100 Mbps bandwidth can reach a throughput of 100 Mbps, then to achieve a throughput of 200 Mbps, it is determined that 100 network resources that support a 2 Mbps bandwidth are required), and according to the performance index requirements of the managed object at the first level by the user or operator, as well as the analysis report and / or status report, it is determined that the managed object at the first level also needs to contain or be associated with 1 managed object at the second level, and the resource configuration of this managed object at the second level is B (for example, b resources that can support a 2 Mbps bandwidth) (for example, the latest performance index achievement efficiency is determined according to the analysis report or status report, and then B is determined according to the performance index requirements and the new performance index achievement efficiency; for example, the new performance index achievement efficiency is 50%, that is, the network resources that support a 100 Mbps bandwidth can only reach a throughput of 50 Mbps, then to achieve the same throughput of 200 Mbps, it is determined that 200 resources that support a 2 Mbps bandwidth are required), then the network configuration difference D is B - A (for example, b - a resources that support a 2 Mbps bandwidth); if D is greater than zero, it means that the network resource configuration used to implement the managed object at the first level, that is, the number of links with a 2 Mbps bandwidth, does not meet the performance index requirements for the managed object at the first level, which will damage the user services running based on the managed object at the first level, thereby affecting the user experience. Therefore, the generated management indication information instructs the network management device at the second level to add configuration to the existing managed object at the second level (for example, add b - a resources that support a 2 Mbps bandwidth); if D is less than zero, it means that the network resource configuration exceeds the performance index requirements, which will waste the operator's network resources, thereby reducing the operator's input-output ratio. Then, the generated management indication information instructs the managed object at the second level to delete configuration from the existing managed object at the second level (for example, delete a - b resources that support a 2 Mbps bandwidth); if D is equal to zero, that is, B = A (for example, b = a), it means that the network resource configuration exactly meets the performance index requirements. Therefore, the network management device at the first level may not generate management indication information, or may generate management indication information in the form of "maintain configuration". It should be understood that the network configuration difference may include both quantity differences and configuration differences.

[0206] Generation method 2: The first-level network management device determines the performance index difference based on the performance index requirements of the first-level managed object, as well as the analysis report and / or status report, and then generates management instruction information according to the performance index difference. The performance index difference refers to the difference between the actual measurement result of the performance index of the first-level managed object and the performance index requirements of the first-level managed object. The configuration management information is used to enable the second-level network management device to reduce or eliminate the performance index difference.

[0207] Specifically, the method of generating management instruction information according to the performance index difference is illustrated as follows:

[0208] Suppose the throughput requirement of the performance index of the first-level managed object is 100 Mbps, and it can be known from the above analysis report and / or status report that the actual throughput of the first-level managed object is 80 Mbps. Then, to make up for the throughput of 20 Mbps, the management instruction information generated by the first-level network management device instructs the second-level network management device to add 10 resources supporting a 2 Mbps bandwidth for the first-level managed object. The second-level network management device can add 10 resources supporting a 2 Mbps bandwidth for the existing second-level managed object according to the management instruction information, or add a second-level managed object, which contains 10 resources supporting a 2 Mbps bandwidth.

[0209] Specifically, the above performance index achievement efficiency is a data measuring the input-output ratio, which can be the ratio of the quantified value of the actually achieved performance index to the quantified value of the invested network resources (the number and configuration of the second-level managed objects). For example: Suppose the actually achieved performance index of the first-level managed object (such as a certain network slice) is a throughput of 80 Mbps, and its quantified value is 80. The first-level managed object is in parallel with 4 second-level managed objects, then the quantified value of these 4 second-level managed objects is 4. Then the performance index achievement efficiency is 80 / 4 = 20. To achieve the performance index requirement of 100 Mbps, only 1 second-level managed object (whose delay meets the requirements within 100% of the time range) needs to be added.

[0210] Specifically, the first-level network management device sending management instruction information to the second-level network management device can be: sending a closed-loop control management message to the second-level network management device, which contains the management instruction information. Specifically, reference can be further made to other embodiments of this application, such as Figure 5 The corresponding embodiment. The second-level network management device receives the closed-loop control management message and manages the second-level managed object according to the management instruction information therein. Optionally, the second-level network management device sends the result of management according to the management instruction information to the first-level network management device.

[0211] The aboveFigure 4 The corresponding method flow enables the first - level network management device to determine network configuration differences based on the performance index requirements of the first - level managed objects it manages, as well as the analysis reports of the first - level managed objects and / or the status reports of the second - level managed objects included in or associated with the first - level managed objects. Furthermore, it manages the second - level managed objects according to the network configuration differences to eliminate or reduce the network configuration differences, thereby eliminating or reducing the differences between the actual performance indexes of the first - level managed objects and the established performance index requirements, improving the matching degree between the two, and taking into account both the satisfaction of the performance index requirements of the first - level managed objects and the utilization rate of the network resources allocated to the first - level managed objects.

[0212] It should be understood that in order to continuously maintain the matching degree between the actual performance indexes of the first - level managed objects and the established performance index requirements, the processes of S401 and S402 can be executed cyclically. From this perspective, the analysis data, decision - making data, and execution data in the status report of the second - level managed objects obtained by the first - level network management device in the current cycle S401 are respectively the content in the analysis report of the second - level managed objects obtained by the second - level network management device in the previous cycle S401, the decisions (such as management instruction information) made based on the analysis report, and the execution results of the management instruction information.

[0213] Figure 5 Flow schematic of the network management method provided by the embodiments of the present application Figure 2 This network management method can be applicable to Figure 1 or Figure 2 the network management system shown in, and includes the following steps:

[0214] S501, the first - level network management device generates first management instruction information according to the performance index requirements of the first - level managed objects.

[0215] Specifically, the first - level network management device obtains the performance index requirements of the first - level managed objects from local or other network management devices, and then generates first management instruction information based on the performance index requirements. The first management instruction information is used to instruct the second - level network management device to manage the second - level managed objects to meet the performance index requirements of the first - level managed objects.

[0216] S502, the first - level network management device sends the first management instruction information to the second - level network management device.

[0217] Specifically, the first - level network management device constructs a request message and sends it to the second - level network management device. The request message contains the first management instruction information. It should be understood that the embodiments of the present application do not limit the name and format of the request message.

[0218] S503. The second-level network management device manages the second-level managed objects according to the first management instruction information.

[0219] Specifically, the second-level network management device receives and parses the request message, obtains the first management instruction information therefrom, then manages the second-level managed objects based on the first management instruction information, and records the identifiers of the managed second-level managed objects. For example, if the first management instruction information indicates to add a second-level managed object, the second-level network management device adds a second-level managed object according to the indication and records the identifier of the newly added second-level managed object. Similarly, if there is a deletion of a second-level managed object, the identifier of the deleted second-level managed object can also be recorded.

[0220] S504. The second-level network management device returns the identifiers (or list of identifiers) of the managed second-level managed objects to the first-level network management device.

[0221] Specifically, the second-level network management device returns a response message to the first-level network management device. The response message contains the identifiers of the second-level managed objects managed in S503. If there are multiple second-level managed objects, the response message contains the identifiers of multiple second-level managed objects, that is, a list of identifiers.

[0222] S505. The first-level network management device sends an analysis report request message or an analysis report subscription request message to the management data analysis device. The analysis report request message or the analysis report subscription request message contains the identifier of the first-level managed object.

[0223] Specifically, the first-level network management device can obtain the analysis report of the first-level managed object from the management data analysis device through a request-response mechanism. For example, the first-level network management device sends an analysis report request message to the management data analysis device, and the message contains the identifier of the first-level managed object, so that the subsequent management data analysis device can return the analysis report of the first-level managed object to the first-level network management device.

[0224] Specifically, the first-level network management device can obtain the analysis report of the first-level managed object from the management data analysis device through the subscription-notification mechanism. For example, the first-level network management device sends an analysis report subscription request message to the management data analysis device. This message contains the identifier of the first-level managed object and can be sent only once. Whenever an analysis report is generated, the management data analysis device can actively notify or push the generated analysis report to the first-level network management device. It should be understood that the "analysis report request message" is exemplary and not restrictive. The first-level network management device can request the analysis report from the management data analysis device through other messages. The "analysis report subscription request message" is also exemplary and not restrictive. The first-level network management device can subscribe to the analysis report of the first-level managed object from the management data analysis device through other messages.

[0225] S506. The management data analysis device analyzes the performance metrics of the first-level managed object to generate an analysis report of the first-level managed object.

[0226] S507. The management data analysis device sends an analysis report response message or an analysis report notification message (the analysis report of the first-level managed object) to the first-level network management device. The analysis report response message or the analysis report notification message contains the generated analysis report of the first-level managed object (the analysis report of the first-level managed object).

[0227] It should be understood that the "analysis report response message" is exemplary and not restrictive. The management data analysis device can return the analysis report to the first-level network management device through other messages. The "analysis report notification message" is also exemplary and not restrictive. The management data analysis device can notify or push the analysis report to the first-level network management device through other messages.

[0228] S508. The first-level network management device sends a status report request message or a status report subscription request message to the second-level network management device. The status report request message or the status report subscription request message contains the identifier or list of identifiers of the second-level managed object received in S504.

[0229] S509. The second-level network management device performs an operation and maintenance operation.

[0230] Specifically, the second - level network management device obtains the analysis data of the second - level managed objects included in or associated with the first - level managed objects from the management data analysis device, generates decision data based on this, and further forms execution data. Among them, the decision data is the management operation to be executed for the second - level managed objects based on the analysis data, and the execution data is the result of the management operation executed on the second - level managed objects according to the decision data. For the specific process, reference can also be made to other embodiments in this application, such as S401, Figure 6 , Figure 7 and other descriptions in the embodiments.

[0231] S510. The second - level network management device sends an operation and maintenance status response message or an operation and maintenance status notification message to the first - level network management device. The operation and maintenance status response message or the operation and maintenance status notification message includes the status report of the second - level managed objects.

[0232] Specifically, the status report includes any one or more of the following: the analysis data in S509, the decision data in S509, and the execution data in S509.

[0233] It should be understood that the order between the processes of S506 - S507 and the processes of S508 - S510 is not fixed. For example, in a possible solution, the processes of S508 - S510 can be completed between S506 and S507, or can be completed before S505.

[0234] It should be understood that the status report of the second - level managed objects can be generated at different steps such as when the second - level network management device monitors, analyzes, makes management decisions, and executes management decisions on the second - level managed objects.

[0235] S511. The first - level network management device generates second management indication information based on the performance index requirements of the first - level managed objects and the analysis report and / or the status report.

[0236] This process can refer to other embodiments in this application, such as S402, Figure 6 , Figure 7 or Figure 8 the descriptions in the corresponding embodiments.

[0237] It should be understood that the analysis report and the status report are not all necessary for the first - level network management device to generate the second management indication information. That is, the first - level network management device can generate the second management indication information based on any one of the following:

[0238] The performance index requirements of the first - level managed objects and the analysis report;

[0239] Performance index requirements of the first - level managed objects and status reports of the second - level managed objects;

[0240] Performance index requirements, analysis reports of the first - level managed objects, and status reports of the second - level managed objects.

[0241] Thus, when the analysis report is not needed, the processes of S505 - S507 can be omitted; when the status report is not needed, the processes of S508 - S510 can be omitted.

[0242] S512. The first - level network management device sends a closed - loop control message to the second - level network management device, and the closed - loop control message includes second management indication information.

[0243] Specifically, the first - level network management device sends a closed - loop control message to the second - level network management device, and the closed - loop control message includes second management indication information; the second - level network management device receives the closed - loop control message, obtains the second management indication information therein, and manages the second - level managed objects according to the second management indication information. Optionally, the second - level network management device sends the result of managing the second - level managed objects to the first - level network management device.

[0244] It should be understood that the "closed - loop control message" is exemplary and not restrictive. The first - level network management device can send the second management indication information to the second - level network management device through other messages.

[0245] It should be understood that the processes of S505 - S512 can be cyclically executed periodically to continuously maintain the consistency between the actual performance index of the first - level managed objects and the performance index requirements.

[0246] The above - mentioned Figure 5 Corresponding method flow enables the first - level network management device to obtain network configuration differences based on the feedback results of the management data analysis device and the second - level network management device, and manage the second - level managed objects accordingly. The data analysis ability is concentrated in the management data analysis device, which can reduce the complexity and performance burden of the first - level network management device.

[0247] Figure 6 Schematic diagram of the process of the network management method provided by the embodiment of the present application Figure 3 , and this network management method can be applicable to Figure 1 or Figure 2The network management system shown is used to implement closed-loop control of network slices / closed-loop control of network slice instances in Table 2. Among them, the network slice management service device corresponds to the first-level network management device above, the network slice corresponds to the first-level managed object above, the network slice subnet management service device corresponds to the second-level network management device above, and one of one or more network slice subnets used to implement the network slice corresponds to the second-level managed object above. The network management method includes the following steps:

[0248] S601. The network slice management service device obtains the throughput requirement of the network slice.

[0249] For example, the throughput requirement of the network slice can be the DL and / or UL average throughput of 80% of the network slice users, such as 100 Mbps.

[0250] Exemplarily, the network slice management service device can obtain the identifier of the network slice and the throughput requirement of the network slice from the communication service management service device. The specific implementation can refer to the prior art, and the embodiments of the present application will not elaborate on this.

[0251] S602. The network slice management service device obtains the throughput requirement of the network slice subnet according to the throughput requirement of the network slice.

[0252] Specifically, the network slice management service device can obtain the DL and / or UL throughput requirements of one or more network slice subnets according to the throughput requirement of the network slice. For example, the DL and / or UL average throughput of the access network subnet and the core network subnet can be 200 Mbps and 100 Mbps respectively.

[0253] S603. The network slice management service device sends the throughput requirement of the network slice subnet to the network slice subnet management service device, and the network slice subnet management service device receives the throughput requirement of the network slice subnet.

[0254] Specifically, the network slice management service device sends the throughput requirements of one or more network slice subnets to the network slice subnet management service device; the network slice subnet management service device receives the throughput requirements of one or more network slice subnets and creates or updates one or more network slice subnets accordingly, that is, if one or more network slice subnets have not been created, one or more network slice subnets are created based on the received throughput requirements, and if one or more network slice subnets have been created, one or more network slice subnets are updated based on the received throughput requirements.

[0255] S604. The network slice management service device sends a throughput analysis request of the network slice to the management data analysis device, and the management data analysis device receives the throughput analysis request of the network slice.

[0256] Specifically, the network slice management service device may send a request message for requesting an analysis report of a network slice to the management data analysis device through a standardized interface. The request message may include one or more of the following: a network slice identifier or a single network slice selection assistance information (S-NSSAI), or an analysis item identifier. Among them, the network slice identifier is used to identify a network slice or a network slice instance to request analysis data of the network slice or network slice instance corresponding to the network slice identifier. The analysis item identifier is used to identify the data item to be analyzed to request the analysis data corresponding to the data item identifier. The analysis item identifier may include a data type (such as performance type, alarm type, configuration type) and a data name / key. For example, "performance / delay" indicates a request for analysis data of the delay in performance data. Specifically, reference may also be made to S505, which will not be elaborated here.

[0257] S605. The management data analysis device analyzes the throughput of the network slice to generate an analysis report on the throughput of the network slice.

[0258] Specifically, after receiving the throughput analysis request of the network slice, the management data analysis device requests the performance management device / fault management device to report the throughput performance measurement / alarm report of the network slice. The performance management device / fault management device sends the throughput performance measurement / alarm report of the network slice to the management data analysis device. The management data analysis device receives the throughput performance measurement / alarm report of the network slice and analyzes the throughput of the network slice to generate an analysis report on the throughput of the network slice.

[0259] S606. The management data analysis device sends the analysis report on the throughput of the network slice to the network slice management service device, and the network slice management service device receives the analysis report on the throughput of the network slice.

[0260] Among them, the items included in the analysis report of the network slice may refer to the description of the analysis report of the first-level managed object in S401. For example, it may include throughput statistical data, throughput prediction data, throughput distribution data, throughput requirement analysis data, etc. of the network slice.

[0261] S607. The network slice subnet management service device sends a status report of the network slice subnet associated with the network slice to the network slice management service device, and the network slice management service device receives the status report of the network slice subnet associated with the network slice.

[0262] Specifically, for the process in which the network slice management service device obtains the status report of the network slice subnet associated with the network slice, reference can be made to the process of S508 - S510, which will not be elaborated here.

[0263] The items included in the status report of the network slice subnet associated with the network slice can refer to the description of the status report of the second - level managed object in S401. For the sake of distinction, the analysis data, decision data, and execution data that may be included in the status report of the network slice subnet associated with the network slice are respectively referred to as first - level analysis data, first - level decision data, and first - level execution data.

[0264] It is assumed that the first - level analysis data includes one or more of the following: the mapping relationship between the throughput distribution and QoE of the corresponding network slice subnet (i.e., the network slice subnet associated with the network slice, the same below), the difference between the actual throughput and the target throughput of the corresponding network slice subnet and its root cause, or the service information where the throughput of the corresponding network slice subnet fails to meet the standard.

[0265] It is assumed that the first - level decision data includes one or more of the following: the throughput control policy of the corresponding network slice subnet, the network configuration quantity of the corresponding network slice subnet, or the network configuration maximum value or guaranteed value configuration management quantity. Among them, the network configuration quantity, network configuration maximum value, or guaranteed value configuration management quantity are decisions made for the analysis information or suggestions related to operation and maintenance in the first - level analysis data. For example, management decision information such as the increase, modification, deletion of resources of the relevant network slice subnet and their corresponding quantities, management decision information such as the increase, modification, deletion of resources of the relevant network slice subnet, addition of a new network slice subnet, deletion of the relevant network slice subnet, or increase, modification, deletion of configuration parameters of the relevant network slice subnet.

[0266] It is assumed that the first - level execution data includes one or more of the following: the network configuration actions, configuration quantities, or execution results executed for the corresponding network slice subnet, which are the management behaviors and management results of the network slice subnet management service device regarding the above - mentioned first - level decision data.

[0267] It should be noted that S606 and S607 can be fully executed or partially executed. When fully executed, S607 can be executed before S606 or after S606. The embodiments of this application do not make specific limitations on this. When partially executed, only one of S606 and S607 can be executed, and in this case, the other step can be regarded as an optional step.

[0268] S608, the network slice management service device generates the third management indication information.

[0269] Specifically, the network slice management service device generates third management indication information based on the performance metrics of the network slice, as well as the analysis report in S606 and / or the status report in S607.

[0270] The third management indication information is used to instruct the network slice subnet management service device to manage the network slice subnet associated with the network slice, and may specifically include one or more of the following: management operations performed on the network slice subnet associated with the network slice, configuration requirements for the network slice subnet associated with the network slice, or performance requirements for the network slice subnet associated with the network slice.

[0271] The management operations performed on the network slice subnet associated with the network slice may include one or more of the following: increasing the network resources of one or more network slice subnets associated with the network slice, deleting the network resources of one or more network slice subnets associated with the network slice, activating or deactivating the network slice subnet associated with the network slice, or modifying the parameters of one or more network slice subnets associated with the network slice.

[0272] The following items (1), (2), and (3) exemplarily illustrate how the network slice management service device generates the third management indication information.

[0273] (1) Optionally, the network slice management service device may generate the third management indication information according to the performance metric requirements of the network slice and the analysis report of the network slice. Examples are as follows:

[0274] The hypothesis analysis report contains measurement analysis information related to the performance metrics of the network slice. When the network slice management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice is lower than the performance metric requirements of the network slice (i.e., a performance metric difference is determined), the generated third management instruction information instructs (the network slice subnet management service device) to increase the resources of one or more network slice subnets associated with the network slice, or add a new network slice subnet, or activate a network slice subnet in the deactivated state, so as to improve the measurement result of the performance metrics and increase the satisfaction of the SLA by increasing network resources. In this case (the measured value is lower than the requirement), optionally, the analysis report of the network slice can also include suggestions on the resources of the newly added network slice subnet or the newly added network slice subnet, so that the third management instruction information can also be generated based on this suggestion. When the network slice management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice is greater than the performance metric requirements of the network slice (i.e., a performance metric difference is determined), the generated third management instruction information instructs (the network slice subnet management service device) to reduce the resources of one or more network slice subnets associated with the network slice, or delete the network slice subnet related to the network slice, or deactivate the network slice subnet associated with the network slice, so as to reduce the resource vacancy rate and improve the utilization efficiency of network resources by reducing network resources. Similarly, in this case (the measured value is greater than the requirement), optionally, the analysis report of the network slice can also include suggestions on reducing the resources of the network slice subnet or deleting or deactivating the network slice subnet, so that the third management instruction information can also be generated based on this suggestion.

[0275] Optionally, the network slice management service device can also generate the third management instruction information according to the performance analysis information of the network slice subnets associated with the network slice (such as radio access network slice subnets, core network slice subnets, transport network slice subnets) contained in the analysis report of the network slice.

[0276] (2) Optionally, the network slice management service device can also generate the third management instruction information according to the performance metric requirements of the network slice and the status report of the network slice subnets associated with the network slice.

[0277] (2.1) Optionally, the network slice management service device can generate the third management instruction information according to the analysis data (i.e., the first analysis data of S607) contained in the status report of the network slice subnets associated with the network slice. For example, the performance metric measurement analysis information of the network slice subnets (such as radio access network slice subnets, core network slice subnets, transport network slice subnets). The following are examples.

[0278] Suppose the status report contains measurement analysis information on the performance metrics of a network slice subnet associated with a network slice. When the network slice management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice for the associated network slice subnet is lower than the performance metric requirements of this network slice subnet (the performance metric requirements are obtained based on the performance metric requirements of the network slice), the generated third management indication information instructs (the network slice subnet management service device) to increase the resources of the network slice subnet associated with the network slice, or add a new network slice subnet, or activate a network slice subnet in the deactivated state, that is, to improve the measurement results of the performance metrics by increasing network resources. When the network slice management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice for the associated network slice subnet is greater than the performance metric requirements of this network slice subnet, the generated third management indication information instructs to reduce the resources of the network slice subnet associated with the network slice, or delete the network slice subnet, or deactivate the network slice subnet, in order to improve the utilization efficiency of the resources.

[0279] In addition to the above measurement analysis information on the performance metrics, the first analysis data may also contain other information and can also be used to determine the third management indication information. This is further illustrated by examples below.

[0280] For example, the first analysis data includes the mapping relationship between the average throughput (UL or DL throughput, the same below) level of a network slice subnet and the QoE of the network slice. Then, based on this mapping relationship, the network slice management service device can determine the area where the throughput does not meet the standard and count the proportion of the non-compliant areas within the coverage area of the network slice. For example, when counting the throughput information, the coverage area information corresponding to the location of the terminal device is recorded. The coverage area information may include information such as the geographical grid ID, longitude and latitude information, cell information, beam ID, etc. Based on the coverage area information corresponding to the location of the terminal device, the area where the throughput does not meet the standard or the area where the throughput meets the standard can be determined, and then the QoE satisfaction degree of the coverage area can be calculated. The network slice management service device can obtain the throughput information of the network slice subnet associated with the network slice. Among them, the throughput information of the network slice subnet associated with the network slice may include one or more of the following: throughput distribution location information, time information, the correspondence between throughput and service experience QoE, service experience or QoS coverage information, and radio signal quality information at the coverage location. For example, the QoE value of geographical grid 1 is 4 points, the throughput level is 4, and the signal strength level is 4; the QoE value of geographical grid 2 is 3 points, the throughput level is 4, and the signal strength level is 3. Among them, the levels are taken as 1, 2, 3, 4, 5 for example; the geographical grid can be a regular hexagon or square area with a side length of 5 meters.

[0281] When it is determined that the proportion of the throughput non-compliance area is greater than the preset threshold, the network slice management service device determines that the throughput of the network slice subnets associated with the network slice does not meet the standard. Moreover, according to the specific proportion of the non-compliance area, the network slice management service device can formulate management strategies for network configuration. For example, increase the corresponding resource configuration or reduce the DL and / or UL throughput requirements to improve the satisfaction degree of throughput requirements. The network slice management service device can obtain the status reports of multiple network slice subnets associated with the network slice, and based on the proportion information of the throughput non-compliance areas in the multiple status reports, combined with the network slice analysis report, the priority information of the network slice subnets, the resource availability information, etc., formulate management strategies for network configuration of multiple network slice subnets, such as requesting to configure more network resources for a certain network slice subnet. Since the network slice management service device can obtain end-to-end network information, it can improve the performance of multiple network slice subnets associated with the network slice through new third management indication information, and then improve the performance of the network slice. For example, when the proportion of the geographical grids with a throughput level of 3 or below in the coverage area of a network slice subnet associated with the network slice exceeds 30%, it is determined that the throughput of the coverage area of the network slice subnet does not meet the standard. In this way, the network slice management service device needs to request the network slice subnet management device to configure corresponding wireless resources for the traffic scheduling of the terminal devices in the coverage area of the non-compliant network slice subnet to improve the throughput. For example, N more radio resource blocks can be allocated to each poor-quality terminal device (i.e., the terminal device with poor quality of service); where N is a positive integer, and the specific value of N is related to the radio resource management algorithm. When the throughputs of multiple network slice subnets associated with the network slice do not meet the standard, the network slice management service device requests the network slice subnet management service device to configure different radio resource blocks for the corresponding network slice subnets according to the priority and resource availability of the network slice subnets. For example, it requests the network slice subnet management service device 1 to allocate N - 10 more radio resource blocks to each poor-quality terminal device, and requests the network slice subnet management service device 2 to allocate N + 10 more radio resource blocks to each poor-quality terminal device.

[0282] For another example, the first analysis data may include the difference and root cause between the average throughput level of the network slice subnet and the throughput target of the network slice subnet. Then, the network slice management service device can determine, based on this information, that the low throughput is caused by high network slice load, and then can increase the resource configuration method to improve the satisfaction degree of throughput requirements.

[0283] For example, the network slice management service device determines the load of the coverage area based on one or more of the following: the number of users within the network slice coverage area, the user traffic volume, or the proportion of radio resources. For instance, when there are more than two users in each geographical grid, the user traffic volume exceeds 10 mega bits per second (Mbps), and the proportion of radio resources exceeds 70%, it can be determined that the load of the coverage area is high. Thus, the network slice management service device can increase the throughput of online users through one or more of the following: reducing the service rate of the terminal device, restricting the access of new terminal devices, restricting the creation of new services, and increasing the radio resource configuration.

[0284] For another example, the first analysis data may include a list of cells / base stations with poor average throughput quality in the network slice subnet. Then, the network slice management service device can obtain a list of cells or base stations with substandard throughput from this data, so as to request the network slice subnet management service device to perform corresponding management actions for the cells or base stations. The network slice subnet management service device can further request the network element management service device to perform corresponding management actions. For example, when the proportion of geographical grids with a throughput level of 3 or below within the cell range exceeds 30%, it can be considered that the throughput of this cell is substandard. Furthermore, the identifiers of the non-compliant cells and the identifiers of the base stations corresponding to the non-compliant cells can be added to the list of base stations or cells with substandard throughput. Thus, the network slice management service device can increase the uplink throughput of this cell by increasing the radio access network resources in the non-compliant cell.

[0285] For another example, the first analysis data may include statistical data on the number of terminal devices / connections / signal strength distribution / service type distribution within the coverage area with poor average throughput in the network slice subnet. The network slice management service device can obtain the number of users, the number of links, the radio signal quality information, and the service type information in the areas with substandard throughput from this statistical data, so as to perform corresponding management actions for the base stations or cells. For example, the network slice management service device increases the radio access network resources or manages the load balancing strategy in this cell, thereby increasing the uplink throughput of this cell.

[0286] For example, the network slice management service device switches some services or terminal devices to other cells or other frequency bands, so that the services or terminal devices are evenly distributed within the coverage overlapping area of adjacent cells or different frequencies. For instance, the number of users in each cell or each frequency band is maintained within the range of 30 - 50, and the average traffic volume of each geographical grid is maintained at about 10 Mbps.

[0287] For another example, the first analysis data may include the QoS measurement analysis of the average throughput of the network slice subnet for poor-quality services. The network slice management service device can analyze the measurement information of the QoS flow corresponding to the service with unqualified throughput from this data. Among them, the measurement information of the QoS flow may include, but is not limited to: delay, rate, packet loss rate. Furthermore, the network slice management service device can obtain the corresponding relationship between the throughput, the configuration in the QoS flow, and the QoS metric measurement. In this way, the network slice management service device can change the DL and / or UL throughput by managing the QoS priority configuration.

[0288] For example, the network slice management service device compares the priority configuration information of the QoS flow with the actual measurement information of the QoS flow. Among them, the priority configuration information of the QoS flow may include the QoS flow category. The QoS flow category may include values such as 3, 5, 7, 9, etc. Each value represents the priority, delay, rate, packet loss rate and other index information of the QoS flow. If the index in the actual measurement information is lower than the preset ratio of the corresponding index in the priority configuration information, the network slice management service device can increase the priority of the QoS flow by n levels; where n is a positive integer. For example, if the rate in the actual measurement information is lower than 80% of the rate in the priority configuration information, the network slice management service device can increase the priority of the QoS flow by 1 level. By increasing the priority of the QoS flow, the network slice management service device can enable the corresponding terminal device or service to obtain more resources during scheduling, thereby increasing the DL and / or UL throughput.

[0289] (2.2) Optionally, the network slice management service device may also generate third management indication information according to the decision data (i.e., the first decision data in S607) and / or execution data (i.e., the first execution data in S607) in the status report of the network slice subnet associated with the network slice.

[0290] When the decision information includes information such as adding network slice subnet resources, adding a new network slice subnet, reducing resources, or deleting a network slice subnet, the network slice management service device combines the current available network resources, network slice subnet analysis information, execution result information, and status reports of other network slice subnets to determine whether the decision of the network slice subnet management service device is valid, and to determine whether to maintain or modify the decision of the network slice subnet management service device. The status report of the network slice subnet associated with the network slice may also include decision information of the network slice subnet without including execution result information, and indicate whether the decision information has been executed. For unexecuted decision information, it is stated that the network slice subnet management service device requests the network slice management service device to judge the feasibility of the decision information. In this case, the network slice management service device may adjust or improve the decision information based on the network resources it manages to generate third management indication information. For example, it judges whether the resource quantity in the decision information can be allocated, and makes adjustments according to the judgment result to form the third management indication information.

[0291] (3) Optionally, the network slice management service device may also generate third management indication information according to the performance index requirements of the network slice, the analysis report of the network slice, and the status report of the network slice subnet associated with the network slice. Examples are as follows:

[0292] When the network slice management service device determines that the information indicated by the analysis report of the network slice and the status report of the network slice subnet associated with the network slice is consistent, for example, based on the analysis report of the network slice, it is determined that the measured value of the network slice performance index is lower (or higher) than the network slice performance index requirement, and based on the status report of the network slice subnet associated with the network slice, it is determined that the measured value of the performance index corresponding to this network slice subnet is lower (or higher) than the performance index requirement of this network slice subnet (obtained based on the network slice performance index requirement), and the resource utilization rate of the network slice subnet is lower (or higher) than the preset threshold, the network slice management service device judges that it is necessary to increase (or decrease) the resource configuration of one or more network slice subnets, and the generated third management indication information instructs (the network slice subnet management service device) to increase (or decrease) the resource configuration of a certain network slice subnet. When the network slice management service device determines that the information indicated by the analysis report of the network slice and the status report of the network slice subnet associated with the network slice is inconsistent, the network slice management service device synthesizes the status reports and historical statuses of multiple network slice subnets to determine to increase, maintain, or decrease the resource configuration of a certain network slice subnet, and the generated third management indication information instructs to increase, maintain, or decrease the resource configuration of a certain network slice subnet.

[0293] It should be noted that the specific content of the analysis report of the network slice and the status report of the network slice subnet associated with the network slice can be referred to the description in S401 above, and will not be elaborated here.

[0294] Optionally, the network slice management service device may first determine a first set of management operations according to the performance index requirements of the network slice, the analysis report of the network slice, and / or the status report of the network slice subnet associated with the network slice, and then generate third management indication information based on the first set of management operations; where the first set of management operations is a set of management operations to be performed on the network slice subnet associated with the network slice, including any one or more of the following: adding a network slice subnet, deleting a network slice subnet, modifying the network configuration of the network slice subnet, and modifying the operating parameters of the network slice subnet.

[0295] It should be understood that the third management indication information is also referred to as configuration requirement information.

[0296] S609. The network slice management service device sends the third management indication information to the network slice subnet management service device, and the network slice subnet management service device receives the third management indication information.

[0297] Specifically, the manner in which the network slice management service device sends the third management indication information to the network slice subnet management service device can refer to the description in S512 and will not be elaborated here. The network slice subnet management service device receives the third management indication information and manages the network slice subnet according to the third management indication information, such as adding a network slice subnet, deleting a network slice subnet, modifying the network configuration of the network slice subnet, etc. Optionally, the network slice subnet management service device sends the result of managing the network slice subnet to the network slice management service device, such as the identifier of the added network slice subnet, the indication information of successful deletion of the network slice subnet, etc.

[0298] The above Figure 6 The corresponding method flow enables the network slice management service device to determine the network configuration difference according to the performance index requirements of the network slice it manages, the analysis report of the network slice, and / or the status report of the network slice subnet included in or associated with the network slice, and then manage the network slice subnet according to the network configuration difference to eliminate or reduce the network configuration difference, and further eliminate or reduce the difference between the actual performance index of the network slice and the established performance index requirements, improve the matching degree between the two, and take into account the satisfaction of the performance index requirements of the network slice and the utilization rate of the network resources allocated to the network slice.

[0299] Figure 7 is the process schematic of the network management method provided by the embodiment of the present application Figure 4 , and this network management method is applicable to Figure 1 orFigure 2 The network management system shown is used to implement the closed-loop control of the network slice subnet / closed-loop control of the network slice subnet instance in Table 2. Among them, the network slice subnet management service device corresponds to the first-level network management device above, the network slice subnet corresponds to the first-level managed object above, and the management device of the network element corresponds to the second-level network management device above, such as a network function management function device or a network function virtualization orchestrator device, which is used to implement one or more network devices or network elements of the network slice subnet corresponding to the second-level managed object above. The network management method includes the following steps:

[0300] S701, the network slice subnet management service device obtains the throughput requirement of the network slice subnet.

[0301] For example, the throughput requirement of the network slice subnet can be the DL and / or UL average throughput of 80% of the network slice users, such as 100 Mbps.

[0302] Exemplarily, the network slice subnet management service device can obtain the identifier of the network slice subnet and the throughput requirement of the network slice subnet from the network slice management service device. The specific implementation can refer to the prior art, and this application embodiment will not elaborate on it.

[0303] S702, the network slice subnet management service device obtains the throughput requirement of the network element associated with the network slice subnet according to the throughput requirement of the network slice subnet.

[0304] Specifically, the network slice subnet management service device can obtain the DL and / or UL throughput requirements of one or more network elements according to the throughput requirement of the network slice subnet. For example, the DL and / or UL average throughput of access network element 1 and core network element 1 can be 20 Mbps and 10 Mbps respectively.

[0305] S703, the network slice subnet management service device sends the throughput requirement of the network element associated with the network slice subnet to the management device of the network element, and the management device of the network element receives the throughput requirement of the network element.

[0306] Specifically, the network slice subnet management service device sends the throughput requirements of one or more network elements to the management device of the network element; the management device of the network element receives the throughput requirements of one or more network elements and accordingly adds or creates or updates one or more network elements, that is, if one or more network elements have not been added or created, one or more network elements are added or created based on the received throughput requirements, and if one or more network elements have been added or created, one or more network elements are updated based on the received throughput requirements.

[0307] S704. The network slice subnet management service device sends a throughput analysis request for the network slice subnet to the management data analysis device, and the management data analysis device receives the throughput analysis request for the network slice subnet.

[0308] Specifically, the network slice subnet management service device may send a request message for requesting an analysis report of the network slice subnet to the management data analysis device through a standardized interface. The request message may include one or more of the following: a network slice subnet identifier or a network element identifier, or an analysis item identifier. Among them, the network slice subnet identifier is used to request an analysis of a specific network slice subnet or a network slice subnet instance, and the analysis item identifier may refer to the relevant description in S604. Specifically, reference may also be made to S505, which will not be elaborated here.

[0309] S705. The management data analysis device analyzes the throughput of the network slice subnet to generate a throughput analysis report of the network slice subnet.

[0310] Specifically, after receiving the throughput analysis request for the network slice subnet, the management data analysis device requests the performance management device / fault management device to report the throughput performance measurement / alert report of the network slice subnet. The performance management device / fault management device sends the throughput performance measurement / alert report of the network slice subnet to the management data analysis device. The management data analysis device receives the throughput performance measurement / alert report of the network slice subnet and analyzes the throughput of the network slice subnet to generate a throughput analysis report of the network slice subnet.

[0311] S706. The management data analysis device sends the throughput analysis report of the network slice subnet to the network slice subnet management service device, and the network slice subnet management service device receives the throughput analysis report of the network slice subnet.

[0312] Among them, the items included in the analysis report of the network slice subnet may refer to the description of the analysis report of the first-level managed object in S401. For example, it may include the throughput statistical data of the network slice subnet, the average packet loss rate of the network slice subnet statistically by service or user, the minimum packet loss rate of the network slice subnet statistically by service or user, the maximum packet length of the network slice subnet statistically by service or user, etc.

[0313] Among them, the management of the resources of the network slice subnet includes operations such as adding, modifying, and deleting the resources of the network slice subnet. The management of the resources of the devices associated with the network slice subnet includes one or more of the following: adding, modifying, deleting the resources of the devices associated with the network slice subnet, or adding associated devices to the network slice subnet, or deleting associated devices from the network slice subnet. The management of the configuration parameters of the network slice subnet or the devices associated with the network slice subnet includes one or more of the following: adding, modifying, deleting the configuration parameters of the network slice subnet or the devices associated with the network slice subnet. The content of the analysis report can specifically refer to the analysis data in Tables 3-6 above, which will not be elaborated here.

[0314] It should be noted that the network slice subnet management service device can send a request message to the management data analysis device through a standardized interface. The request message is used to request the management data analysis device to feedback the analysis report of the network slice subnet. Among them, the request message can include one or more of the following: network slice subnet identifier or S-NSSAI, or analysis item identifier.

[0315] It should be understood that the network slice subnet management service device can also manage the network configuration of the network slice subnet according to the content of the above analysis report of the network slice subnet, so as to further improve the accuracy of the relevant configuration of performance indicators such as management throughput and / or latency. The specific implementation can refer to S402 above, which will not be elaborated here.

[0316] S707, the management device of the network element sends a status report of the device associated with the network slice subnet to the network slice subnet management service device, and the network slice subnet management service device receives the status report of the device associated with the network slice subnet.

[0317] Specifically, the process for the network slice subnet management service device to obtain the status report of the device associated with the network slice subnet from the management device of the network element can refer to the process of S508-S510, which will not be elaborated here.

[0318] The items included in the status report of the device associated with the network slice subnet can refer to the description of the status report of the second-level managed object in S401. For the convenience of distinction, the analysis data, decision data, and execution data that the status report of the device associated with the network slice subnet may include are respectively called second analysis data, second decision data, and second execution data.

[0319] Suppose the second analysis data includes one or more of the following: the mapping relationship between the throughput distribution and QoE of the corresponding device (i.e., the device associated with the network slice subnet or the network element, the same below), the difference between the actual throughput and the target throughput of the corresponding device and the root cause, or the service information of the corresponding device with insufficient throughput.

[0320] It is assumed that the second decision data includes one or more of the following: the throughput control policy of the corresponding device, the network configuration quantity of the corresponding device, or the network configuration maximum value or guaranteed value configuration management quantity of the corresponding device. Among them, the network configuration quantity, the network configuration maximum value or the guaranteed value configuration management quantity are decisions made for the analysis information or suggestions related to operation and maintenance in the second analysis data. For example, management decision information such as the increase, modification, deletion of resources of related devices and their corresponding quantities, and management decision information such as the increase, modification, deletion of resources of related devices, the addition of new devices, the deletion of related devices, or the increase, modification, deletion of configuration parameters of related devices.

[0321] It is assumed that the second execution data includes one or more of the following: the network configuration actions, configuration quantities, or execution results executed for the corresponding device, which are the management behaviors and management results of the management device of the network element regarding the above-mentioned second decision data.

[0322] It should be noted that S706 and S707 can be all executed or partially executed. When all are executed, S707 can be executed before S706 or after S706. The embodiments of the present application do not make specific limitations on this. When partially executed, only one of S706 and S707 can be executed, and in this case, the other step can be regarded as an optional step.

[0323] S708, the network slice subnet management service device generates the fourth management indication information.

[0324] Specifically, the network slice subnet management service device generates the fourth management indication information based on the performance indicators of the network slice subnet and the analysis report in S706 and / or the status report in S707.

[0325] Among them, the fourth management indication information is used to instruct the management device of the network element in the network slice subnet to manage the configuration information of the device associated with the network slice subnet, including one or more of the following: the management operations to be performed on the device associated with the network slice subnet, the configuration requirements of the device associated with the network slice subnet, or the performance requirements of the device associated with the network slice subnet.

[0326] Among them, the management operations to be performed on the device associated with the network slice subnet may include one or more of the following: adding one or more devices associated with the network slice subnet, deleting one or more devices associated with the network slice subnet, activating the device associated with the network slice subnet in the deactivated state, deactivating the device associated with the network slice subnet, or modifying the parameters of one or more devices associated with the network slice subnet.

[0327] The following items (1), (2), and (3) exemplarily illustrate how the network slice subnet management service device generates the fourth management indication information.

[0328] (1) Optionally, the network slice subnet management service device may generate the fourth management indication information according to the performance metric requirements of the network slice subnet and the analysis report of the network slice subnet. The following is an example:

[0329] Suppose the analysis report contains measurement and analysis information related to the performance requirement metrics corresponding to the network slice subnet. When the measurement and analysis information indicates that the measured value is lower than the performance requirement of the metric, the network slice subnet management service device determines to increase the resources of one or more devices associated with the network slice subnet, or add devices associated with the network slice subnet, or activate devices associated with the network slice subnet that are in the deactivated state, that is, to improve the measurement results by configuring more resources. In this case (the measured value is lower than the requirement), optionally, the analysis report may also contain suggestions for adding device resources or adding devices. When the measurement and analysis information indicates that the measured value is greater than the performance requirement of the metric, the network slice subnet management service device reduces the resources of one or more devices associated with the network slice subnet, or deletes the devices associated with the network slice subnet, or deactivates the devices associated with the network slice subnet to improve the resource utilization efficiency. In this case (the measured value is greater than the requirement), optionally, the analysis report may also contain suggestions for reducing device resources, or deleting, or deactivating the devices associated with the network slice subnet. The network slice subnet management service device determines the need to increase, or reduce, or maintain the resource configuration of one or more of the radio access network devices, core network devices, and transport network devices included in the analysis report of the network slice subnet, or increase, or reduce, or maintain the number of devices and the required configuration information.

[0330] Optionally, the network slice subnet management service device also generates the fourth management indication information according to the performance analysis information of the devices associated with the network slice subnet (such as radio access network devices, core network devices, and transport network devices) included in the analysis report of the network slice subnet.

[0331] (2) Optionally, the network slice subnet management service device may also generate the fourth management indication information according to the performance metric requirements of the network slice subnet and the status report of the devices associated with the network slice subnet.

[0332] (2.1) Optionally, the network slice subnet management service device may generate the fourth management indication information according to the analysis data (i.e., the second analysis data of S607) included in the status report of the devices associated with the network slice subnet. For example, the performance metric measurement and analysis information of the corresponding devices (such as radio access network devices, core network devices, and transport network devices). The following is an example.

[0333] Suppose the status report contains measurement analysis information on the performance metrics of devices associated with a network slice subnet. When the network slice subnet management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice subnet for the associated devices is lower than the performance metric requirements of these devices (the performance metric requirements are obtained based on the performance metric requirements of the network slice subnet), the generated fourth management indication information instructs (the management device of the network element) to increase the resources of the devices associated with the network slice subnet or activate the devices in the deactivated state, that is, to improve the measurement results of the performance metrics by increasing network resources. When the network slice subnet management service device determines, based on this measurement analysis information, that the measured value of the performance metrics of the network slice subnet for the associated devices is greater than the performance metric requirements of these devices, the generated fourth management indication information instructs to reduce the resources of the devices associated with the network slice subnet, or delete the devices associated with the network slice subnet, or deactivate the devices associated with the network slice subnet, in order to improve the resource utilization efficiency.

[0334] In addition to the above measurement analysis information on the performance metrics, the second analysis data may also contain other information, which can also be used to determine the fourth management indication information. This is further illustrated by examples below.

[0335] For example, the second analysis data includes the mapping relationship between the average throughput (uplink or downlink throughput, the same below) level statistics of the network elements associated with the network slice subnet and the QoE of the network slice subnet. Then, based on this mapping relationship, the network slice subnet management service device can determine the area where the throughput does not meet the standard and count the proportion of the non-compliant areas within the coverage area of the network slice subnet. For example, when counting the throughput information, the coverage area information corresponding to the location of the terminal device is recorded. The coverage area information may include information such as geographical grid ID, longitude and latitude information, cell information, beam ID, etc. Based on the coverage area information corresponding to the location of the terminal device, the area where the throughput does not meet the standard or the area where the throughput meets the standard can be determined, and then the QoE satisfaction degree of the coverage area can be calculated. The network slice subnet management service device can obtain the throughput information of the devices associated with the network slice subnet. Among them, the throughput information of the devices associated with the network slice subnet may include one or more of the following: throughput distribution location information, time information, the correspondence between throughput and service experience QoE, service experience or QoS coverage information, and wireless signal quality information at the coverage location. For example, the QoE value of geographical grid 1 is 4 points, the throughput level is 4, and the signal strength level is 4; the QoE value of geographical grid 2 is 3 points, the throughput level is 4, and the signal strength level is 3. Among them, the levels are taken as 1, 2, 3, 4, 5 for example; the geographical grid can be a hexagonal or square area with a side length of 5 meters.

[0336] When it is determined that the proportion of the throughput non-compliance area is greater than the preset threshold, the network slice subnet management service device determines that the throughput of the devices associated with the network slice subnet is non-compliant. And, according to the specific proportion of the non-compliance area, the network slice subnet management service device can make a management strategy for network configuration. For example, increase the corresponding resource configuration or reduce the DL and / or UL throughput requirements to improve the satisfaction of throughput requirements. The network slice subnet management service device can obtain the status reports of multiple devices associated with the network slice subnet, and based on the proportion information of the throughput non-compliance area in the multiple status reports, combined with the analysis report of the devices related to the network slice subnet, the priority information of the devices related to the network slice subnet, the available resource information, etc., make a management strategy for network configuration for multiple devices, such as requesting to configure more network resources for a certain device. Since the network slice subnet management service device can obtain end-to-end network information, it can improve the performance of multiple devices associated with the network slice subnet through the new fourth management indication information, and then improve the performance of the network slice subnet. For example, when the proportion of the geographical grids with a throughput level of 3 or below in the coverage area of a device associated with the network slice subnet exceeds 30%, it is determined that the throughput of the device coverage area is non-compliant. Thus, the network slice subnet management service device needs to request the management device of the network element to configure more corresponding wireless resources for the service scheduling of the terminal devices in the coverage area of the non-compliant device to improve the throughput. For example, N wireless resource blocks can be allocated more for each poor-quality terminal device (i.e., the terminal device with poor quality of service); where N is a positive integer, and the specific value of N is related to the wireless resource management algorithm. When the throughputs of multiple devices associated with the network slice subnet are all non-compliant, the network slice subnet management service device requests the management device of the network element to configure different wireless resource blocks for the corresponding devices according to the device priority and resource availability. For example, it requests the management device 1 of the network element to allocate N - 10 wireless resource blocks more for each poor-quality terminal device, and requests the management device 2 of the network element to allocate N + 10 wireless resource blocks more for each poor-quality terminal device.

[0337] For another example, the second analysis data may include the difference and root cause between the average throughput level of the network elements of the network slice subnet and the throughput target of the network elements of the network slice subnet. Then, the network slice subnet management service device can determine, based on this information, that the low throughput is caused by the high load of the network elements of the network slice subnet, and then can improve the satisfaction of throughput requirements by increasing the resource configuration method.

[0338] For example, the network slice subnet management service device determines the load of the coverage area based on one or more of the following: the number of users within the network slice subnet coverage area, user traffic volume, or the proportion of radio resources. For instance, when there are more than 2 users in each geographical grid, the user traffic volume exceeds 10 megabits per second (Mbps), and the proportion of radio resources exceeds 70%, it can be determined that the load of the coverage area is high. Thus, the network slice subnet management service device can increase the throughput of online users through one or more of the following: reducing the service rate of the terminal device, restricting the access of new terminal devices, restricting the creation of new services, and increasing the radio resource configuration.

[0339] For another example, the second analysis data may include a list of cells / base stations with poor average throughput quality of the network slice subnet. Then, the network slice subnet management service device can obtain a list of cells or base stations with substandard throughput from this data, so as to request the management device of the network element to perform corresponding management actions for the cells or base stations. For example, when the proportion of geographical grids with a throughput level of 3 or below within the cell range exceeds 30%, it can be considered that the throughput of this cell is substandard. Furthermore, the identifiers of the substandard cells and the identifiers of the base stations corresponding to the substandard cells can be added to the list of base stations or cells with substandard throughput. Thus, the network slice subnet management service device can increase the uplink throughput of this cell by increasing radio access network resources in the substandard cell.

[0340] For another example, the second analysis data may include statistical data on the number of terminal devices / connections / signal strength distribution / service type distribution within the average throughput quality difference coverage area of the network slice subnet. The network slice subnet management service device can obtain the number of users, the number of links, radio signal quality information, and service type information in the area with substandard throughput from this statistical data, so as to perform corresponding management actions for the base station or cell. For example, the network slice subnet management service device increases radio access network resources or manages the load balancing strategy in this cell, thereby increasing the uplink throughput of this cell.

[0341] For example, the network slice subnet management service device switches some services or terminal devices to other cells or other frequency bands, so that the services or terminal devices are evenly distributed within the coverage overlapping area of adjacent cells or different frequencies. For instance, the number of users in each cell or each frequency band is maintained within the range of 30 - 50, and the average traffic volume in each geographical grid is maintained at about 10 Mbps.

[0342] For another example, the second analysis data may include the QoS measurement analysis of the average throughput of the network element in the network slice subnet, which refers to the measurement information of the QoS indicators in this network element, such as the processing delay of this network element, the throughput of the network element, etc. The network slice subnet management service device can analyze the measurement information of the QoS flow corresponding to the service with unqualified throughput in this network element from this data. Among them, the measurement information of this QoS flow may include but is not limited to: delay, rate, packet loss rate. Furthermore, the network slice subnet management service device can obtain the corresponding relationship between the throughput, the attribute configuration in the QoS flow, and the QoS indicator measurement. In this way, the network slice subnet management service device can change the DL and / or UL throughput by managing the QoS priority configuration.

[0343] For example, the network slice subnet management service device compares the priority configuration information of the QoS flow with the actual measurement information of the QoS flow. Among them, the priority configuration information of the QoS flow may include the QoS flow category. The QoS flow category may include values such as 3, 5, 7, 9, etc. Each value represents the priority of the QoS flow, and indicator information such as delay, rate, packet loss rate. If the indicator in the actual measurement information is lower than the preset ratio of the corresponding indicator in the priority configuration information, the network slice subnet management service device can increase the priority of the QoS flow by n levels; where n is a positive integer. For example, if the rate in the actual measurement information is lower than 80% of the rate in the priority configuration information, the network slice subnet management service device can increase the priority of the QoS flow by 1 level. By increasing the priority of the QoS flow, the network slice subnet management service device can enable the corresponding terminal device or service to obtain more resources during scheduling, thereby increasing the DL and / or UL throughput.

[0344] (2.2) Optionally, the network slice subnet management service device may also generate fourth management indication information according to the decision data (i.e., the second decision data of S707) and / or the execution data (i.e., the second execution data of S607) in the status report of the device associated with the network slice subnet.

[0345] When the decision information includes information such as adding device resources, adding new devices, reducing resources, or deleting devices, the network slice subnet management service device combines the resource availability of the network slice subnet, analysis information, execution result information, and status reports of other network slice subnets to determine whether the decision of the network slice subnet management service device is valid, and determines whether to maintain or modify the decision of the network slice subnet management service device. The status report of the device associated with the network slice subnet may also include decision information of the network slice subnet without including execution result information, and indicates whether the decision information has been executed. For unexecuted decision information, it is stated that the management device of the network element requests the network slice subnet management service device to judge the feasibility of the decision information. In this case, the network slice subnet management service device may adjust or improve the decision information based on the network resources it manages to generate fourth management indication information. For example, it judges whether the resource quantity in the decision information can be allocated and adjusts according to the judgment result to form fourth management indication information.

[0346] (3) Optionally, the network slice subnet management service device may also generate fourth management indication information according to the performance index requirements of the network slice subnet, the analysis report of the network slice subnet, and the status report of the device associated with the network slice subnet. The following are examples:

[0347] When the network slice subnet management service device determines that the information indicated by the analysis report of the network slice subnet and the status report of the device associated with the network slice subnet is consistent. For example, based on the analysis report of the network slice subnet, it is determined that the measured value of the performance index of the network slice subnet is lower (or higher) than the performance index requirements of the network slice subnet. Based on the status report of the device associated with the network slice subnet, it is determined that the measured value of the performance index corresponding to the device is lower (or higher) than the performance index requirements of the device (obtained based on the performance index requirements of the network slice subnet), and the resource utilization rate of the device is lower (or higher) than the preset threshold. The network slice subnet management service device judges that it is necessary to increase (or decrease) the resource configuration of one or more devices, and the generated fourth management indication information instructs (the management device of the network element) to increase (or decrease) the resource configuration of a certain device. When the network slice subnet management service device determines that the information indicated by the analysis report of the network slice subnet and the status report of the device associated with the network slice subnet is inconsistent, the network slice subnet management service device synthesizes the status reports and historical statuses of multiple devices to determine to increase, maintain, or decrease the resource configuration of a certain device, and the generated fourth management indication information instructs to increase, maintain, or decrease the resource configuration of a certain device.

[0348] It should be noted that the specific content of the analysis report of the network slice subnet and the status report of the devices associated with the network slice subnet can be referred to the description in S401 above, and will not be elaborated here.

[0349] Optionally, the network slice subnet management service device may first determine a second set of management operations according to the performance index requirements of the network slice subnet, the analysis report of the network slice subnet, and / or the status report of the devices associated with the network slice subnet, and then generate fourth management indication information based on the second set of management operations; where the second set of management operations is a set of management operations to be performed on the devices associated with the network slice subnet, including any one or more of the following: adding devices, deleting devices, modifying the network configuration of devices, and modifying the operating parameters of devices.

[0350] It should be understood that the fourth management indication information is also referred to as configuration requirement information.

[0351] S709, the network slice subnet management service device sends the fourth management indication information to the management function device of the network element, and the management device of the network element receives the fourth management indication information.

[0352] Specifically, the manner in which the network slice subnet management service device sends the fourth management indication information to the management device of the network element can be referred to the description in S512 and will not be elaborated here. The management device of the network element receives the fourth management indication information and manages the network elements in the network slice subnet according to the fourth management indication information, such as adding network elements, deleting network elements, modifying the configuration of network elements, etc.

[0353] Optionally, the management function device of the network element sends the results of managing the network elements in the network slice subnet to the network slice subnet management service device, such as the identifier of the added network element, the indication information indicating the successful modification of the configuration of the network element, etc.

[0354] The above Figure 7 The corresponding method flow enables the network slice subnet management service device to determine the network configuration difference according to the performance index requirements of the network slice subnet it manages, the analysis report of the network slice subnet, and / or the status report of the network elements included in or associated with the network slice subnet, and then manage the network elements according to the network configuration difference to eliminate or reduce the network configuration difference, and further eliminate or reduce the difference between the actual performance index of the network slice subnet and the established performance index requirements, improve the coincidence degree between the two, and take into account the satisfaction degree of the performance index requirements of the network slice subnet and the utilization rate of the network resources allocated to the network slice subnet.

[0355] Figure 8 Schematic diagram of the process of the network management method provided by the embodiment of the present application Figure 5 This network management method can be applied to Figure 1 Or Figure 2The network management system shown is used to implement closed-loop control of communication services / closed-loop control of communication service instances. Among them, the communication service management service device corresponds to the first-level network management device above, the communication service corresponds to the first-level managed object above, the network slice management service device corresponds to the second-level network management device above, and one of the one or more network slices used to implement the communication service corresponds to the second-level managed object above. The network management method includes the following steps:

[0356] S801. The communication service management service device obtains the throughput requirement of the communication service.

[0357] For example, the throughput requirement of the communication service can be the DL and / or UL average throughput of 80% of the communication service users, such as 100 Mbps.

[0358] Exemplarily, the communication service management service device can obtain the throughput requirement of the communication service from the user's SLA. The specific implementation can refer to the prior art, and this application embodiment will not elaborate on it.

[0359] S802. The communication service management service device obtains the throughput requirement of the network slice associated with the communication service according to the throughput requirement of the communication service.

[0360] Specifically, the communication service management service device can obtain the DL and / or UL throughput requirements of one or more network slices according to the throughput requirement of the communication service. For example, the DL and / or UL average throughput of the network slice can be 200 Mbps and 100 Mbps respectively.

[0361] S803. The communication service management service device sends the throughput requirement of the network slice associated with the communication service to the network slice management service device, and the network slice management service device receives the throughput requirement of the network slice.

[0362] Specifically, the communication service management service device sends the throughput requirements of one or more network slices to the network slice management service device; the network slice management service device receives the throughput requirements of one or more network slices and creates or updates one or more network slices accordingly, that is, if one or more network slices have not been created, one or more network slices are created based on the received throughput requirements, and if one or more network slices have been created, one or more network slices are updated based on the received throughput requirements.

[0363] S804. The communication service management service device sends a throughput analysis request of the communication service to the management data analysis device, and the management data analysis device receives the throughput analysis request of the communication service.

[0364] Specifically, the communication service management service device may send a request message for requesting an analysis report of a communication service to the management data analysis device through a standardized interface. The request message may include one or more of the following: a communication service identifier, a performance metric identifier, or an analysis item identifier. Among them, the communication service identifier is used to identify a communication service or a communication service instance to request analysis data of the communication service or communication service instance corresponding to the communication service identifier. The analysis item identifier may refer to S604. Specifically, reference may also be made to S505, which will not be elaborated here.

[0365] In S805, the management data analysis device analyzes the throughput of the communication service to generate an analysis report on the throughput of the communication service.

[0366] Specifically, after receiving the throughput analysis request for the communication service, the management data analysis device requests the performance management device / fault management device to report the throughput performance measurement / alert report of the communication service. The performance management device / fault management device sends the throughput performance measurement / alert report of the communication service to the management data analysis device. The management data analysis device receives the throughput performance measurement / alert report of the communication service and analyzes the throughput of the communication service to generate an analysis report on the throughput of the communication service.

[0367] In S806, the management data analysis device sends the analysis report on the throughput of the communication service to the communication service management service device, and the communication service management service device receives the analysis report on the throughput of the communication service.

[0368] Among them, the items included in the analysis report of the communication service may refer to the description of the analysis report of the first-level managed object in S401. For example, it may include throughput statistical data, throughput prediction data, throughput distribution data, throughput requirement analysis data, etc. of the communication service.

[0369] Among them, the management of the resources of the communication service includes operations such as adding, modifying, and deleting the resources of the communication service. The management of the resources of the network slice associated with the communication service includes one or more of the following: adding, modifying, deleting the resources of the network slice associated with the communication service, or adding a new associated network slice for the communication service, deleting an unnecessary network slice from the network slice associated with the communication service. The management of the configuration parameters of the communication service or the network slice associated with the communication service includes one or more of the following: adding, modifying, deleting the configuration parameters of the communication service or the network slice associated with the communication service. The content of the analysis report may specifically refer to the analysis data in Tables 3-6 above, which will not be elaborated here.

[0370] It should be noted that the communication service management service device can send a request message to the management data analysis device through a standardized interface. The request message is used to request the management data analysis device to feedback an analysis report of the communication service. Among them, the request message may include one or more of the following: a communication service identifier, or an analysis item identifier.

[0371] It should be understood that the communication service management service device can also manage the network configuration of the network slice according to the content of the above analysis report of the network slice, so as to further improve the accuracy of the relevant configuration of performance indicators such as management throughput and / or latency. The specific implementation can refer to S402 above and will not be elaborated here.

[0372] S807, the network slice management service device sends a status report of the network slice associated with the communication service to the communication service management service device, and the communication service management service device receives the status report of the network slice associated with the communication service.

[0373] Specifically, the process for the communication service management service device to obtain the status report of the network slice associated with the communication service from the network slice management service device can refer to the process of S508 - S510 and will not be elaborated here.

[0374] The items included in the status report of the network slice associated with the communication service can refer to the description of the status report of the second - level managed object in S401. For the convenience of distinction, the analysis data, decision data, and execution data that may be included in the status report of the network slice associated with the communication service are respectively referred to as the third - analysis data, the third - decision data, and the third - execution data.

[0375] Suppose the third - analysis data includes one or more of the following: the mapping relationship between the throughput distribution and QoE of the corresponding network slice (i.e., the network slice associated with the communication service, the same below), the difference between the actual throughput and the target throughput of the corresponding network slice and its root cause, or the service information where the throughput of the corresponding network slice fails to meet the standard.

[0376] Suppose the third - decision data includes one or more of the following: the throughput control strategy of the corresponding network slice, the network configuration quantity of the corresponding network slice, or the network configuration maximum value or guaranteed value configuration management quantity. Among them, the network configuration quantity, the network configuration maximum value or the guaranteed value configuration management quantity are decisions made for the analysis information or suggestions related to operation and maintenance in the third - analysis data. For example, management decision information such as the increase, modification, deletion of resources of the relevant network slice and their corresponding quantities, management decision information such as the increase, modification, deletion of resources of the relevant network slice, the addition or deletion of network slices, or the increase, modification, deletion of configuration parameters of the relevant network slice.

[0377] Suppose the third execution data includes one or more of the following: network configuration actions, configuration quantities, or execution results performed for the corresponding network slice, which are the management behaviors and management results of the network slice management service device regarding the above-mentioned third decision data.

[0378] It should be noted that S806 and S807 can be fully executed or partially executed. When fully executed, S807 can be executed before S806 or after S806. The embodiments of this application do not make specific limitations in this regard. When partially executed, only one of S806 and S807 can be executed, and in this case, the other step can be regarded as an optional step.

[0379] S808, the communication service management service device generates the fifth management indication information.

[0380] Specifically, the communication service management service device generates the fifth management indication information based on the performance metrics of the communication service and the analysis report in S806 and / or the status report in S807.

[0381] Among them, the fifth management indication information is used to instruct the network slice management service device to manage the network slice associated with the communication service, and specifically may include one or more of the following: management operations performed on the network slice associated with the communication service, configuration requirements for the network slice associated with the communication service, or performance requirements for the network slice associated with the communication service.

[0382] Among them, the management operations performed on the network slice associated with the communication service may include one or more of the following: increasing the network resources of one or more network slices associated with the communication service, deleting the network resources of one or more network slices associated with the communication service, activating the network slice associated with the communication service, deactivating the network slice associated with the communication service, or modifying the parameters of one or more network slices associated with the communication service.

[0383] The following items (1), (2), and (3) exemplarily illustrate how the communication service management service device generates the fifth management indication information.

[0384] (1) Optionally, the communication service management service device can generate the fifth management indication information according to the performance metric requirements of the communication service and the analysis report of the communication service. Examples are as follows:

[0385] The hypothesis analysis report contains measurement analysis information related to the performance metrics of a communication service. When the communication service management service device determines, based on this measurement analysis information, that the measured value of the performance metric of the communication service is lower than the performance metric requirement of the communication service (i.e., a performance metric difference is determined), the generated fifth management instruction information instructs (the network slice management service device) to increase the resources of one or more network slices associated with the communication service, or add a network slice associated with the communication service, or activate a network slice associated with the communication service that is in a deactivated state, so as to improve the measurement result of the performance metric and increase the satisfaction of the SLA by increasing network resources. In this case (the measured value is lower than the requirement), optionally, the analysis report of the communication service may also contain suggestions on adding resources to the network slice associated with the communication service or adding a network slice associated with the communication service, so that the fifth management instruction information may also be generated based on this suggestion. When the communication service management service device determines, based on this measurement analysis information, that the measured value of the performance metric of the communication service is greater than the performance metric requirement of the communication service (i.e., a performance metric difference is determined), the generated fifth management instruction information instructs (the network slice management service device) to reduce the resources of one or more network slices associated with the communication service, or delete the network slice related to the communication service, or deactivate the network slice associated with the communication service, so as to reduce the resource vacancy rate and improve the utilization efficiency of network resources by reducing network resources. Similarly, the analysis report of the communication service may also contain suggestions on reducing the resources of the network slice associated with the communication service or deleting or deactivating the network slice associated with the communication service, so that the fifth management instruction information may also be generated based on this suggestion.

[0386] Optionally, the communication service management service device also generates the fifth management instruction information according to the performance analysis information of the network slice associated with the communication service included in the analysis report of the communication service.

[0387] (2) Optionally, the communication service management service device may also generate the fifth management instruction information according to the performance metric requirement of the communication service and the status report of the network slice associated with the communication service.

[0388] (2.1) Optionally, the communication service management service device may generate the fifth management instruction information according to the analysis data (i.e., the third analysis data of S807) included in the status report of the network slice associated with the communication service, such as the measurement analysis information of the performance metric of the network slice. The following are examples.

[0389] Suppose the status report contains measurement analysis information of performance metrics of a network slice associated with a communication service. When the communication service management service device determines, based on the measurement analysis information, that the measured value of the performance metrics of the network slice associated with the communication service is lower than the performance metric requirements of the communication service (the performance metric requirements are obtained based on the performance metric requirements of the communication service), the generated fifth management indication information instructs (the network slice management service device) to increase the resources of the network slice associated with the communication service, or add a new network slice, or activate a network slice in a deactivated state, that is, to improve the measurement result of the performance metrics by increasing network resources. When the communication service management service device determines, based on the measurement analysis information, that the measured value of the performance metrics of the network slice associated with the communication service is greater than the performance metric requirements of the network slice, the generated fifth management indication information instructs to reduce the resources of the network slice associated with the communication service, or delete the network slice associated with the communication service, or deactivate the network slice associated with the communication service, so as to improve the utilization efficiency of resources.

[0390] In addition to the above measurement analysis information of performance metrics, the third analysis data may also include other information and can also be used to determine the fifth management indication information, which is further illustrated by examples below.

[0391] For example, the third analysis data includes the mapping relationship between the average throughput (uplink or downlink throughput, the same below) level statistics of the network slice associated with the communication service and the QoE of the communication service; then, based on this mapping relationship, the communication service management service device can determine the area where the throughput does not meet the standard and count the proportion of the non-compliant areas within the coverage area of the communication service. For example, when counting the throughput information, the coverage area information corresponding to the location of the terminal device is recorded, and the coverage area information may include information such as geographical grid ID, longitude and latitude information, cell information, beam ID, etc. According to the coverage area information corresponding to the location of the terminal device, the area where the throughput does not meet the standard or the area where the throughput meets the standard can be determined, and then the QoE satisfaction degree of the coverage area can be calculated. The communication service management service device can obtain the throughput information of the network slice associated with the communication service, where the throughput information of the network slice associated with the communication service may include one or more of the following: throughput distribution location information, time information, the correspondence between throughput and service experience QoE, service experience or QoS coverage information, and wireless signal quality information at the coverage location. For example, the QoE value of geographical grid 1 is 4 points, the throughput level is 4, and the signal strength level is 4; the QoE value of geographical grid 2 is 3 points, the throughput level is 4, and the signal strength level is 3. Among them, the levels are taken as 1, 2, 3, 4, 5 for example; the geographical grid can be a regular hexagon or square area with a side length of 5 meters.

[0392] When it is determined that the proportion of the throughput non-compliance area is greater than the preset threshold, the communication service management service device determines that the throughput of the network slice associated with the communication service does not meet the standard. Moreover, according to the specific proportion of the non-compliance area, the communication service management service device can make a management strategy for network configuration. For example, increasing the corresponding resource configuration or reducing the DL and / or UL throughput requirements to improve the satisfaction of throughput requirements. The communication service management service device can obtain the status reports of multiple network slices associated with the communication service, and based on the proportion information of the throughput non-compliance area in the multiple status reports, combined with the communication service analysis report, the priority information of the network slice, the resource availability information, etc., make a management strategy for the network configuration of multiple network slices, such as requesting to configure more network resources for a certain network slice. Since the communication service management service device can obtain end-to-end network information, it can improve the performance of multiple network slices associated with the communication service through the new fifth management indication information, and then improve the performance of the communication service. For example, when the proportion of the number of geographical grids with a throughput level of 3 or below in a network slice associated with the communication service exceeds 30% within the coverage area of the network slice, it is determined that the throughput of the network slice coverage area does not meet the standard. In this way, the communication service management service device needs to request the network slice management device to configure corresponding wireless resources for the service scheduling of the terminal devices in the coverage area of the non-compliant network slice to improve the throughput. For example, N wireless resource blocks can be allocated more for each poor-quality terminal device (i.e., the terminal device with poor service quality); where N is a positive integer, and the specific value of N is related to the wireless resource management algorithm. When the throughputs of multiple network slices associated with the communication service do not meet the standard, the communication service management service device requests the network slice management service device to configure different wireless resource blocks for the corresponding network slices according to the priority and resource availability of the network slices. For example, it requests the network slice management service device 1 to allocate N - 10 wireless resource blocks more for each poor-quality terminal device, and requests the network slice management service device 2 to allocate N + 10 wireless resource blocks more for each poor-quality terminal device.

[0393] For another example, the third analysis data may include the difference and root cause between the average throughput level of the network slice associated with the communication service and the communication service throughput target. Then, the communication service management service device can determine, based on this information, that the low throughput is caused by high communication service load, and then can improve the satisfaction of throughput requirements by increasing the resource configuration method.

[0394] For example, the communication service management service device determines the load of the coverage area based on one or more of the following: the number of users within the communication service coverage area, the user traffic volume, or the radio resource occupancy ratio. For instance, when there are more than 2 users in each geographical grid, the user traffic volume exceeds 10 megabits per second (Mbps), and the radio resource occupancy ratio exceeds 70%, it can be determined that the load of the coverage area is high. Thus, the communication service management service device can increase the throughput of online users through one or more of the following: reducing the service rate of the terminal device, restricting the access of new terminal devices, restricting the creation of new services, and increasing the radio resource configuration.

[0395] For another example, the third analysis data may include a list of cells / base stations with poor average throughput quality of the network slice associated with the communication service. Then, the communication service management service device can obtain a list of cells or base stations with substandard throughput from this data, so as to request the network slice management service device to perform corresponding management actions for the cells or base stations. The communication service management service device can further request the network slice management service device to execute corresponding management actions. For example, when the proportion of geographical grids with a throughput level of 3 or below within the cell range exceeds 30%, it can be considered that the throughput of this cell is substandard. Furthermore, the identifiers of the substandard cells and the identifiers of the base stations corresponding to the substandard cells can be added to the list of base stations or cells with substandard throughput. Thus, the network slice management service device can increase the uplink throughput of this cell by increasing the radio access network resources in the substandard cell.

[0396] For another example, the third analysis data may include statistical data on the number of terminal devices / connection numbers / signal strength distribution / service type distribution within the coverage area with poor average throughput quality of the network slice associated with the communication service. The communication service management service device can obtain the number of users, connection numbers, radio signal quality information, and service type information in the area with substandard throughput from this statistical data, so as to perform corresponding management actions for the base stations or cells. For example, the communication service management service device increases the radio access network resources or manages the load balancing strategy in this cell, thereby increasing the uplink throughput of this cell.

[0397] For example, the communication service management service device switches some services or terminal devices to other cells or other frequency bands, so that the services or terminal devices are evenly distributed within the coverage overlapping area of adjacent cells or different frequencies. For instance, the number of users in each cell or each frequency band is maintained within the range of 30 - 50, and the average traffic volume of each geographical grid is maintained at about 10 Mbps.

[0398] For another example, the third analysis data may include the QoS measurement analysis of the average throughput of the network slice associated with the communication service and the poor-quality service. The communication service management service device may analyze the measurement information of the QoS flow corresponding to the service with insufficient throughput from this data. Among them, the measurement information of the QoS flow may include, but is not limited to: delay, rate, and packet loss rate. Furthermore, the communication service management service device may obtain the correspondence between the throughput, the configuration in the QoS flow, and the QoS metric measurement. In this way, the communication service management service device may change the DL and / or UL throughput by managing the QoS priority configuration.

[0399] For example, the communication service management service device compares the priority configuration information of the QoS flow with the actual measurement information of the QoS flow. Among them, the priority configuration information of the QoS flow may include the QoS flow category. The QoS flow category may include values such as 3, 5, 7, 9, etc. Each value represents the priority, delay, rate, packet loss rate, and other metric information of the QoS flow. If the metric in the actual measurement information is lower than the preset ratio of the corresponding metric in the priority configuration information, the communication service management service device may increase the priority of the QoS flow by n levels; where n is a positive integer. For example, if the rate in the actual measurement information is lower than 80% of the rate in the priority configuration information, the communication service management service device may increase the priority of the QoS flow by 1 level. By increasing the priority of the QoS flow, the communication service management service device may enable the corresponding terminal device or service to obtain more resources during scheduling, thereby increasing the DL and / or UL throughput.

[0400] (2.2) Optionally, the communication service management service device may also generate fifth management indication information according to the decision data (i.e., the third decision data of S807) and / or the execution data (i.e., the third execution data of S807) in the status report of the network slice associated with the communication service.

[0401] When the decision information includes information such as increasing network slice resources, adding a new network slice, reducing resources, or deleting a network slice, the communication service management service device combines the current available network resources, communication service analysis information, execution result information, and status reports of other network slices to determine whether the decision of the network slice management service device is effective, and determines whether to maintain or modify the decision of the network slice management service device. The status report of the network slice associated with the communication service may also include decision information of the network slice without including execution result information, and indicates whether the decision information has been executed. For unexecuted decision information, it is stated that the network slice management service device requests the communication service management service device to judge the feasibility of the decision information. In this case, the communication service management service device may adjust or improve the decision information based on the network resources it manages to generate fifth management indication information. For example, it judges whether the resource quantity in the decision information can be allocated, and adjusts according to the judgment result to form fifth management indication information.

[0402] (3) Optionally, the communication service management service device may also generate fifth management indication information according to the performance index requirements of the communication service, the analysis report of the communication service, and the status report of the network slice associated with the communication service. Examples are as follows:

[0403] When the communication service management service device determines that the information indicated by the analysis report of the communication service and the status report of the network slice associated with the communication service is consistent, for example, based on the analysis report of the communication service, it is determined that the measured value of the communication service performance index is lower (or higher) than the communication service performance index requirement, and based on the status report of the network slice associated with the communication service, it is determined that the measured value of the performance index corresponding to this network slice is lower (or higher) than the performance index requirement of this network slice (obtained based on the communication service performance index requirement), and the network slice resource utilization rate is lower (or higher) than the preset threshold, the communication service management service device judges that it is necessary to increase (or decrease) the resource configuration of one or more network slices, and the generated fifth management indication information indicates (the network slice management service device) to increase (or decrease) the resource configuration of a certain network slice. When the communication service management service device determines that the information indicated by the analysis report of the communication service and the status report of the network slice associated with the communication service is inconsistent, the communication service management service device synthesizes the status reports and historical statuses of multiple network slices to determine to increase, maintain, or decrease the resource configuration of a certain network slice, and the generated fifth management indication information indicates to increase, maintain, or decrease the resource configuration of a certain network slice.

[0404] It should be noted that the specific content of the analysis report of the communication service and the status report of the network slice associated with the communication service may be referred to the description in S401 above, and will not be elaborated here.

[0405] Optionally, the communication service management service device may first determine a third set of management operations based on the performance index requirements of the communication service, the analysis report of the communication service, and / or the status report of the network slice subnet associated with the communication service, and then generate fifth management indication information based on the third set of management operations; wherein the third set of management operations is a set of management operations to be performed on the network slice associated with the communication service, including any one or more of the following: adding a network slice, deleting a network slice, modifying the network configuration of the network slice, and modifying the operating parameters of the network slice.

[0406] It should be understood that the fifth management indication information is also referred to as configuration requirement information.

[0407] S809. The communication service management service device sends the fifth management indication information to the network slice management service device, and the network slice management service device receives the fifth management indication information.

[0408] Specifically, the manner in which the communication service management service device sends the fifth management indication information to the network slice management service device may refer to the description in S512 and will not be elaborated here. The network slice management service device receives the fifth management indication information and manages the network slice according to the fifth management indication information, such as adding a network slice, deleting a network slice, modifying the network configuration of the network slice, etc.

[0409] Optionally, the network slice management service device sends the result of managing the network slice to the communication service management service device, such as the identifier of the added network slice, the indication information indicating the successful modification of the network slice configuration, the indication information indicating the successful deletion of the network slice, etc.

[0410] The above Figure 8 The corresponding method flow enables the communication service management service device to determine the network configuration difference based on the performance index requirements of the communication service instances it manages, the analysis report of the communication service instances, and / or the status report of the network slices included in or associated with the communication service instances, and then manage the network slices according to the network configuration difference to eliminate or reduce the network configuration difference, thereby eliminating or reducing the difference between the actual performance index of the communication service instance and the established performance index requirements, improving the coincidence degree between the two, and taking into account the satisfaction degree of the performance index requirements of the communication service instance and the utilization rate of the network resources allocated to the communication service instance.

[0411] Based on Figures 4 - 8For the network management method shown in any of the above, network management devices at each level can determine network configuration differences based on the performance index requirements of the managed objects at their management levels, as well as the analysis reports of the managed objects at this level and / or the status reports of the managed objects at the next level included in or associated with the managed objects at this level. Furthermore, the network management devices can manage the managed objects at the next level according to the network configuration differences to eliminate or reduce the network configuration differences, and further eliminate or reduce the differences between the actual performance indexes of the managed objects at this level and the established performance index requirements, improve the matching degree between the two, and balance the satisfaction degree of the performance index requirements of the managed objects at this level and the utilization rate of the network resources allocated to the managed objects at this level.

[0412] The above combines Figures 4 - 8 has described in detail the network management method provided by the embodiments of the present application. The following combines Figures 9 - 10 to describe in detail the network management device for executing the network management method provided by the embodiments of the present application.

[0413] Figure 9 is a schematic structural diagram of the network management device 900 provided by the embodiments of the present application Figure 1 . This device is applied to the first-level network management device, which is connected to the second-level network management device. The first-level network management device and the second-level network management device respectively manage managed objects at different levels, and the managed objects are devices, networks, or services provided by the network. As Figure 9 shown, the network management device 900 includes: a transceiver module 901 and a processing module 902. For the sake of convenience of description, Figure 9 only the main components of the network management device 900 are shown.

[0414] In some embodiments, the network management device 900 can be applicable to Figure 1 or Figure 2 shown in the network management system, and execute the functions of the first-level network management device in Figures 4 - 8 any one of the network management methods shown.

[0415] Specifically, the transceiver module 901 is used to support the communication between the first-level network management device and other network entities, such as performing the indication operations in S402, S507, S510, S603, S706, or S809, etc.

[0416] The processing module 902 is used for the control function of the first-level network management device, such as controlling the transceiver module 901 to perform the indication operations in S401, S402, S511, S608, or S808, etc. For the specific implementation manners of the transceiver module 901 and the processing module 902, reference can be made to the above Figures 4 - 8The relevant content in the method embodiments shown in any of the above is not elaborated here.

[0417] Optionally, the transceiver module 901 may include a receiving module and a sending module ( Figure 9 not shown in the figure). Among them, the receiving module is used to receive information sent by other devices, such as a second-level network management device or a management data analysis service, and the sending module is used to send information to other devices, such as a second-level network management device or a management data analysis service.

[0418] Optionally, the network management device 900 may further include a storage module ( Figure 9 not shown in the figure), and the storage module stores programs or instructions. When the processing module 902 executes the programs or instructions, the network management device 900 can execute Figures 4 - 8 any of the network management methods shown above.

[0419] It should be noted that the network management device 900 may be a network management device, such as an operation administration and maintenance (OAM) device, a business support system (BSS) device, an operations support system (OSS) device, or may also be a chip (system) or other components or assemblies that can be set in the network management device, or may also be a device including the network management device. The present application does not make any limitations in this regard.

[0420] In addition, the technical effects of the network management device 900 can refer to Figures 4 - 8 the technical effects of any of the network management methods shown above, which are not elaborated here.

[0421] Exemplarily, Figure 10 is a schematic structural diagram of the network management device provided by the embodiments of the present application. Figure 2 This network management device may be a network management device, such as an OAM device, a BSS device, an OSS device, or may also be a chip (system) or other components or assemblies that can be set in the network management device, or may also be a device including the network management device. As Figure 10 shown, the network management device 1000 may include a processor 1001. Optionally, the network management device 1000 may further include a memory 1002 and / or a transceiver 1003. Among them, the processor 1001 is coupled to the memory 1002 and the transceiver 1003, such as being connected through a communication bus.

[0422] Next, in combination with Figure 10Specific introductions are made to each component of the network management device 1000:

[0423] Among them, the processor 1001 is the control center of the network management device 1000, which can be a single processor or a collective term for multiple processing elements. For example, the processor 1001 is one or more central processing units (CPUs), or can be an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0424] Optionally, the processor 1001 can execute various functions of the network management device 1000 by running or executing software programs stored in the memory 1002 and calling data stored in the memory 1002.

[0425] In a specific implementation, as an embodiment, the processor 1001 can include one or more CPUs, such as Figure 10 CPU0 and CPU1 shown in

[0426] In a specific implementation, as an embodiment, the network management device 1000 can also include multiple processors, such as Figure 2 the processor 1001 and the processor 1004 shown in. Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, the processor can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0427] Among them, the memory 1002 is used to store software programs for implementing the solutions of the present application and is controlled by the processor 1001 for execution. The specific implementation method can refer to the above method embodiments and will not be elaborated here.

[0428] Optionally, the memory 1002 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1002 may be integrated with the processor 1001 or may exist independently and be coupled to the processor 1001 through the interface circuit of the network management device 1000 ( Figure 10 not shown in the figure), and the embodiments of the present application do not make specific limitations on this.

[0429] The transceiver 1003 is used for communication with other network management devices. For example, if the network management device 1000 is a network management device, the transceiver 1003 may be used for communication with the managed network or with another network management device, and thus may obtain an analysis report and / or a status report of the managed network.

[0430] Optionally, the transceiver 1003 may include a receiving module and a transmitting module ( Figure 10 not shown separately in the figure). Among them, the receiving module may be used to receive information from the managed network or other network management devices. The transmitting module may be used to send information to the managed network or other network management devices. The transceiver 1003 may implement Figure 9 the functions that the transceiver module 901 in the figure can implement.

[0431] Optionally, the transceiver 1003 may be integrated with the processor 1001 or may exist independently and be coupled to the processor 1001 through the interface circuit of the network management device 1000 ( Figure 10 not shown in the figure), and the embodiments of the present application do not make specific limitations on this.

[0432] It should be noted that Figure 10 the structure of the network management device 1000 shown in the figure does not constitute a limitation on the network management device. The actual network management device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0433] In addition, for the technical effects of the network management device 1000, reference may be made to the technical effects of the network management method in the foregoing method embodiments, which will not be elaborated herein.

[0434] The embodiments of the present application further provide a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip system implements the method in any of the foregoing method embodiments.

[0435] Optionally, the processor in the chip system may be one or more. The processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented by software, the processor may be a general-purpose processor that implements by reading software code stored in the memory.

[0436] Optionally, the memory in the chip system may also be one or more. The memory may be integrated with the processor or may be separately provided from the processor, which is not limited in the present application. Exemplarily, the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be separately provided on different chips. The present application does not specifically limit the type of the memory and the setting manner of the memory and the processor.

[0437] Exemplarily, the chip system may be a field programmable gate array (FPGA), may be an application specific integrated circuit (ASIC), may also be a system on chip (SoC), may also be a central processing unit (CPU), may also be a network processor (NP), may also be a digital signal processing circuit (DSP), may also be a microcontroller unit (MCU), may also be a programmable logic device (PLD) or other integrated chips.

[0438] The embodiments of the present application further provide a network management system. The network management system includes a first-level network management device and a second-level network management device. Among them, the first-level network management device is applicable to Figure 1 or Figure 2 in the network management system shown, and executesFigures 4 - 8 the functions of the first-level network management device in the network management method shown in any one of Figure 1 or Figure 2 in the network management system shown in Figures 4 - 8 the functions of the second-level network management device in the network management method shown in any one of

[0439] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0440] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0441] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware, or any combination thereof. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that contains one or more collections of available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media. The semiconductor media can be a solid-state drive.

[0442] It should be understood that the term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects before and after, but it may also represent an "and / or" relationship, which can be specifically understood with reference to the context.

[0443] In the present application, "at least one" means one or more, and "a plurality" means two or more. "At least one of the following" or its similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0444] It should be understood that in various embodiments of the present application, the magnitude of the sequence numbers of the above processes does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0445] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0446] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0447] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

[0448] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0449] In addition, the functional units in each embodiment of this application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0450] When the above-mentioned function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.

[0451] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A network management method is applied to a first - level network management device. The first - level network management device is connected to a second - level network management device. The first - level network management device and the second - level network management device respectively manage managed objects at different levels. The managed objects are devices, networks, or services provided by the network. Characterized in that, The network management method includes: Obtaining a status report of at least one second - level managed object from the second - level network management device; According to the performance index requirements of the first - level managed object and the status report, instructing the second - level network management device to manage the second - level managed object; Wherein, the first - level managed object is associated with the at least one second - level managed object.

2. The network management method according to claim 1, Characterized in that, The step of, according to the performance index requirements of the first - level managed object and the status report, instructing the second - level network management device to manage the second - level managed object includes: Generating management instruction information according to the performance index requirements of the first - level managed object and the status report; Sending the management instruction information to the second - level network management device; Wherein, the management instruction information includes any one of the following: Configuration operation information, including configuration operations to be performed on the second - level managed object, or, Configuration requirement information, including configuration requirements for the second - level managed object, or, Performance index requirement information, including performance index requirements for the second - level managed object.

3. The network management method according to claim 2, Characterized in that, The management instruction information includes configuration operation information, and the configuration operation information includes any one or more of the following: Adding a second - level managed object, Deleting a second - level managed object, Or modifying the configuration information of the second - level managed object.

4. The network management method according to claim 2 or 3, Characterized in that, The step of generating management instruction information according to the performance index requirements of the first - level managed object and the status report includes: Determining a network configuration difference according to the performance index requirements of the first - level managed object and the status report. The network configuration difference is the difference between the at least one second - level managed object and the at least one second - level managed object that the first - level managed object needs to include or be associated with according to the performance index requirements and the status report; Generating the management instruction information according to the network configuration difference.

5. The network management method according to claim 2 or 3, Characterized in that, The step of generating management instruction information according to the performance index requirements of the first - level managed object and the status report includes: Determining a performance index difference according to the performance index requirements of the first - level managed object and the status report. The performance index difference is the difference between the performance index measurement result of the first - level managed object and the performance index requirements of the first - level managed object; Generate the management indication information according to the difference in the performance metrics.

6. The network management method according to claim 2 or 3, wherein, the sending the management indication information to the second-level network management device includes: sending a closed-loop control management message to the second-level network management device, where the closed-loop control management message includes the management indication information.

7. The network management method according to any one of claims 1-3, wherein, the obtaining the status report of at least one second-level managed object from the second-level network management device includes: sending an operation and maintenance status request message to the second-level network management device, where the operation and maintenance status request message includes the identifier of the at least one second-level managed object; receiving an operation and maintenance status response message from the second-level network management device, where the operation and maintenance status response message includes the status report; or, sending an operation and maintenance status subscription request message to the second-level network management device, where the operation and maintenance status subscription request message includes the identifier of the at least one second-level managed object; receiving an operation and maintenance status notification message from the second-level network management device, where the operation and maintenance status notification message includes the status report.

8. The network management method according to any one of claims 1-3, wherein, the status report includes execution data, and the execution data includes one or more of the following: management actions performed by the second-level network management device, resource or parameter configuration amounts, or execution results.

9. The network management method according to any one of claims 1-3, wherein, the first-level network management device is a network slice management service device, the first-level managed object is a network slice, the second-level network management device is a network slice subnet management service device, and the second-level managed object is a network slice subnet.

10. The network management method according to any one of claims 1-3, wherein, the first-level network management device is a network slice subnet management service device, the first-level managed object is a network slice subnet, the second-level network management device is a management device of a network element in the network slice subnet, and the second-level managed object is a device in the network slice subnet.

11. The network management method according to any one of claims 1-3, wherein, the first-level network management device is a communication service management service device, the first-level managed object is a communication service or a communication service instance, the second-level network management device is a network slice management service device, and the second-level managed object is a network slice management service.

12. A network management apparatus, which is applied to a first-level network management device, the first-level network management device is connected to a second-level network management device, the first-level network management device and the second-level network management device respectively manage managed objects at different levels, and the managed objects are devices, networks, or services provided by the networks, wherein, the network management apparatus includes: a transceiver module and a processing module; wherein, The processing module is configured to control the transceiver module to obtain a status report of at least one second - level managed object from the second - level network management device; The processing module is configured to, according to the performance index requirements of the first - level managed object and the status report, instruct the second - level network management device to manage the second - level managed objects; Wherein, the first - level managed object is associated with the at least one second - level managed object.

13. The network management device according to claim 12, wherein, The processing module is further configured to generate management instruction information according to the performance index requirements of the first - level managed object and the status report; The transceiver module is further configured to send the management instruction information to the second - level network management device; Wherein, the management instruction information includes any one of the following: Configuration operation information, including configuration operations to be performed on the second - level managed objects, or, Configuration requirement information, including configuration requirements for the second - level managed objects, or, Performance index requirement information, including performance index requirements for the second - level managed objects.

14. The network management device according to claim 13, wherein, The management instruction information includes configuration operation information, and the configuration operation information includes any one or more of the following: Adding a second - level managed object, Deleting a second - level managed object, Or modifying the configuration information of the second - level managed object.

15. The network management device according to any one of claims 12 - 13, wherein, The transceiver module is further configured to send an operation and maintenance status request message to the second - level network management device, the operation and maintenance status request message containing the identifiers of the at least one second - level managed object; and receive an operation and maintenance status response message from the second - level network management device, the operation and maintenance status response message containing the status report; Or, The transceiver module is further configured to send an operation and maintenance status subscription request message to the second - level network management device, the operation and maintenance status subscription request message including the identifiers of the at least one second - level managed object; and receive an operation and maintenance status notification message from the second - level network management device, the operation and maintenance status notification message containing the status report.

16. The network management device according to any one of claims 12 - 13, wherein, The status report contains execution data, and the execution data includes one or more of the following: management actions performed by the second - level network management device, resource or parameter configuration amounts, or execution results.

17. The network management device according to any one of claims 12 - 13, wherein, The first - level network management device is a network slice management service device, the first - level managed object is a network slice, the second - level network management device is a network slice subnet management service device, and the second - level managed object is a network slice subnet.

18. The network management device according to any one of claims 12 - 13, wherein, The first - level network management device is a network slice subnet management service device, the first - level managed object is a network slice subnet, the second - level network management device is a management device for network elements in the network slice subnet, and the second - level managed object is a device in the network slice subnet.

19. The network management device according to any one of claims 12 - 13, characterized in that, the first - level network management device is a communication service management service device, the first - level managed object is a communication service or a communication service instance, the second - level network management device is a network slice management service device, and the second - level managed object is a network slice management service.

20. A network management device, characterized in that, comprises: a processor, the processor being coupled to a memory; the processor is configured to execute a computer program stored in the memory, so that the network management device executes the network management method according to any one of claims 1 - 11.

21. A network management device, characterized in that, comprises: a processor and an interface circuit; wherein, the interface circuit is configured to receive code instructions and transmit them to the processor; the processor is configured to run the code instructions to execute the network management method according to any one of claims 1 - 11.

22. A processor, characterized in that, the processor is configured to execute the network management method according to any one of claims 1 - 11.

23. A network management system, characterized in that, the network management method comprises: a first - level network management device and a second - level network management device, the first - level network management device is connected to the second - level network management device, the first - level network management device and the second - level network management device respectively manage managed objects at different levels, and the managed objects are devices, networks or services provided by the networks; wherein, the first - level network management device is configured to obtain a status report of at least one second - level managed object from the second - level network management device; the first - level network management device is further configured to, according to the performance index requirements of the first - level managed object and the status report, instruct the second - level network management device to manage the second - level managed object; the second - level network management device is configured to provide a status report of at least one second - level managed object to the first - level network management device; the second - level network management device is further configured to manage the second - level managed object according to the instruction of the first - level network management device; wherein, the first - level managed object is associated with the at least one second - level managed object.

24. The network management system according to claim 23, characterized in that, the first - level network management device is specifically configured to: generate management instruction information according to the performance index requirements of the first - level managed object and the status report; send the management instruction information to the second - level network management device; wherein, the management instruction information includes any one of the following: Configuration operation information, including configuration operations to be performed on the second-level managed object, or, Configuration requirement information, including configuration requirements for the second-level managed object, or, Performance metric requirement information, including performance metric requirements for the second-level managed object.

25. The network management system according to claim 23 or 24, wherein, the status report contains execution data, and the execution data includes one or more of the following: management actions performed by the second-level network management device, amounts of resource or parameter configuration, or execution results.

Images