WO2023051536A1 - 网络管理方法及装置 - Google Patents

网络管理方法及装置 Download PDF

Info

Publication number
WO2023051536A1
WO2023051536A1 PCT/CN2022/121771 CN2022121771W WO2023051536A1 WO 2023051536 A1 WO2023051536 A1 WO 2023051536A1 CN 2022121771 W CN2022121771 W CN 2022121771W WO 2023051536 A1 WO2023051536 A1 WO 2023051536A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
network management
closed
information
network
Prior art date
Application number
PCT/CN2022/121771
Other languages
English (en)
French (fr)
Inventor
张健
行骁程
王曼
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023051536A1 publication Critical patent/WO2023051536A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the communication field, and in particular to a network management method and device.
  • Service level specification (service level specification, SLS) assurance closed loop (closed loop SLS assurance, COSLA) (also known as closed loop management process) can be used to monitor the completion status of closed loop assurance goals (assurance goals) and resource utilization, and can adjust and A resource associated with a network slice or network slice subnet to satisfy one or more closed-loop assurance objectives.
  • SLS service level specification
  • COSLA closed loop management process
  • Network slicing is a cross-domain network, and its SLS guarantee goal needs to be completed through multiple closed-loop management processes.
  • 3GPP 3rd generation partnership project
  • cross domain cross domain
  • COSLA deployed at the 3rd generation partnership project (3GPP) cross domain (cross domain) level provides end-to-end SLS guarantees for network slicing to ensure the service experience of network slicing
  • COSLA in the radio access network (radio access network, RAN) domain provides SLS assurance for network slice subnets in the RAN domain
  • COSLA deployed in the core network (core network, CN) domain provides SLS for network slice subnets in the CN domain Assurance
  • COSLA can include monitoring, analysis, decision-making, execution and other management services (management service(s), MnS(s)).
  • the present application provides a network management method and device capable of realizing the SLS target of network slicing and/or network slicing subnets.
  • a network management method is provided.
  • the network management method can be applied to the first network management production entity, the first network management production entity is used to manage the first closed-loop management process, the first closed-loop management process is a management process for realizing the SLS target of the first managed object, the first The managed object is the resource or business managed by the first closed-loop management process.
  • the second closed-loop management process is a management process to realize the service level specification SLS target of the second managed object.
  • the second closed-loop management process is managed by the second network production entity Management, the second managed object is the resource or service managed by the second closed-loop management process.
  • the network management method includes: receiving a first message from a network management consumption entity, and executing one or more first management policies in the first management policy information.
  • the first message includes first management policy information
  • the first management policy information is the management policy information corresponding to the first closed-loop management process, there is an association relationship between the first closed-loop management process and at least one second closed-loop management process
  • the second The management policy information corresponding to the closed-loop management process is the second management policy information
  • the first management policy information and at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process
  • the first management policy information includes one or more first management policies.
  • the first network management production entity receives first management policy information, and executes one or more first management policies in the first management policy information.
  • the first management policy information is the management policy information corresponding to the first closed-loop management process, there is an association relationship between the first closed-loop management process and at least one second closed-loop management process, and the management policy information corresponding to the second closed-loop management process is the second
  • the management strategy information, the first management strategy information and at least one second management strategy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process, and the first managed object is the first closed-loop management
  • the resources or services managed by the process, the first closed-loop management process is a management process for realizing the SLS target of the first managed object. In this way, the first network management production entity can realize the SLS target of the first managed object (eg, network slice and/or network slice subnet).
  • the first management policy information may include one or more first action indication information, and the first action indication information may be used to instruct the first network management production entity to set the first closed-loop management process corresponding to the first Configuration information of managed objects.
  • the network management producer can execute one or more operations indicated by the first action instruction information, so that the performance of the closed-loop management process can meet the guarantee target.
  • the first management policy information may further include: one or more condition information, and/or one or more event information.
  • one piece of condition information corresponds to at least one first action indication information
  • one piece of event information corresponds to at least one first action indication information. That is to say, when one piece of condition information and/or event information is satisfied, the network management producer can execute one or more operations indicated by the first action indication information, so that the first closed-loop management process can meet the guarantee target.
  • condition information in the first management policy information may include: the relationship between the performance of the first managed object corresponding to the first closed-loop management process and the performance threshold.
  • the event information may include one or more of the following: a notification event corresponding to the first managed object corresponding to the first closed-loop management process, and/or a notification event corresponding to a managed object other than the first managed object corresponding to the first closed-loop management process Notification events, notification events generated by network management production entities, and notification events generated by network management production entities other than the network management production entity.
  • the execution of one or more first management policies in the first management policy information may include: setting the first managed object corresponding to the first closed-loop management process according to the first action instruction information configuration information. In this way, the guarantee target corresponding to the first closed-loop management process can be guaranteed.
  • the execution of one or more first management policies in the first management policy information may include: in the case of satisfying condition information and/or event information, instructing information according to the first action , setting the configuration information of the first managed object corresponding to the first closed-loop management process.
  • the entity receiving the first message is the first network management production entity
  • the management object corresponding to the first closed-loop management process is the first managed object
  • the first message may further include one or more of the following: an identifier of the second network management production entity, an identifier of the second closed-loop management process, and a guarantee target of the first closed-loop management process.
  • multiple network management and production entities can not only be based on their respective management policy information (for example, the first network management and production entity corresponds to the first management policy information,
  • the second network management and production entity realizes the assurance objectives of the respective closed-loop management processes, and may further negotiate the assurance objectives of the respective closed-loop management processes according to the received first message.
  • the second network management production entity may perform functions similar to those of the first network management production entity, for example, the second network management production entity receives the second management policy information from the network management consumption entity, and executes the second management policy information One or more secondary management policies in .
  • the implementation of the second management policy information is similar to the specific implementation of the first management policy information, the main difference is that the first closed-loop management process is replaced by the second closed-loop management process.
  • the second management policy information may include one or more first action indication information, and the first action indication information may be used to instruct the network management production entity to set the configuration information of the second managed object corresponding to the second closed-loop management process. Refer to the implementation manner of the above-mentioned first management policy information, and details will not be repeated one by one.
  • the first management policy information may also include one or more first sub-action indication information, and the first sub-action indication information may be used to instruct the first network management production entity to send the second network management production entity Sending the first notification information and/or the first operation result, the execution of one or more first management policies in the first management policy information may include: according to the identification of the second network management production entity and the first sub-action indication information , sending the first collaboration message to the second network management and production entity.
  • the first cooperation message may include the first notification information and/or the first operation result
  • the first notification information may include the guarantee target of the second closed-loop management process that the network management consumption entity expects the second network management production entity to adopt
  • the first The operation result may be obtained by the first network management production entity according to the first action instruction information
  • the first operation result may be obtained by the first network management production entity according to one or more of condition information and event information
  • the first The action indicates that the information is obtained.
  • the first network management and production entity can cooperate with the second network management and production entity, so as to meet the guarantee target corresponding to the closed-loop management process.
  • the second management policy information may also include one or more first sub-action indication information, and the first sub-action indication information may be used to instruct the second network management production entity to send the first network
  • the management production entity sends the second notification information and/or the second running result.
  • the second network management production entity may send the second cooperation message to the first network management production entity according to the identifier of the first network management production entity and the first subaction indication information.
  • the network management method provided in the first aspect may further include: sending the second message to the network management consumption entity.
  • the second message may include the first operation result and/or the first modification request information
  • the first operation result may be obtained by the first network management and production entity according to the first action instruction information
  • the first operation result may be the first Obtained by a network management production entity according to one or more of the condition information and event information
  • the first action instruction information the first modification request information can be used to request modification of the first management policy information, and/or the first closed-loop management process assurance goals.
  • the network management consuming entity can adjust the management policy information and/or guarantee target of the first closed-loop management process according to the first running result and/or modification request.
  • the first modification request information may be determined by the first network management and production entity according to the second notification information, the second operation result, and/or its own first operation result.
  • the second notification information may include the guarantee target of the first closed-loop management process that the network management consumption entity expects the first network management production entity to adopt, and the second operation result may be obtained by the second network management production entity according to the first action instruction information
  • the second running result may be obtained by the second network management and production entity according to one or more items of condition information and event information, and the first action instruction information.
  • the first network management production entity may determine whether to request to modify the first Assurance objectives and/or management strategy information of the closed-loop management process can also determine expected assurance objectives and/or management strategy information.
  • the network management method provided in the first aspect may further include: receiving a second cooperation message from the second network management and production entity.
  • the second cooperation message may include the second notification information and/or the second operation result.
  • the second network management production entity can cooperate with the first network management production entity, so that the performance corresponding to the closed-loop management process meets the guarantee target.
  • the network management method provided in the first aspect may further include: receiving new first management policy information and/or new assurance targets of the first closed-loop management process from the network management consuming entity.
  • the first network management production entity can further realize the SLS target of the first managed object according to the new management policy information and/or the new guarantee target.
  • the first running result may include one or more of the following: the first performance result, the identification of the first management policy information corresponding to the first performance result, the condition information corresponding to the first performance result, The event information corresponding to the first performance result, and the first action indication information corresponding to the first performance result.
  • the first performance result may include a performance result of the first managed object.
  • first closed-loop management processes there may be one or more first closed-loop management processes.
  • second closed-loop management processes there may be one or more first closed-loop management processes.
  • the association relationship may include a connection relationship, or a containment relationship, or a sharing relationship.
  • the second network management production entity can perform functions similar to those of the first network management production entity in the method shown in the first aspect, the main difference is that the first closed-loop management process is replaced by the second closed-loop management process, The first network management production entity is replaced by the second network management production entity, which will not be repeated here.
  • a network management method is provided.
  • the network management method is applied to network management consuming entities, and includes: determining N pieces of management strategy information according to association relationship information and guarantee objectives of N closed-loop management processes, and sending a first message to at least two network management production entities.
  • the relationship information includes the relationship between N closed-loop management processes, N is an integer greater than 1, the closed-loop management process is a management process to achieve the SLS target of the managed object, and the managed object is defined by the closed-loop management process.
  • N pieces of management strategy information are used to realize the guarantee objectives of N closed-loop management processes, and N closed-loop management processes correspond to N managed objects one-to-one.
  • the first message includes management strategy information
  • the network management production entity is used to manage the closed-loop management process
  • the management strategy information includes one or more management strategies.
  • the main difference between the N pieces of management policy information is that the N pieces of management policy information correspond to different closed-loop management processes, for example, management policy information 1 corresponds to closed-loop management process 1, and management policy information 2 corresponds to closed-loop management process 2.
  • the management policy information may include one or more first action indication information, and the first action indication information may be used to instruct the network management production entity to set the configuration information of the managed object corresponding to the closed-loop management process.
  • the management policy information may further include: one or more condition information, and/or one or more event information.
  • one piece of condition information corresponds to at least one first action indication information
  • one piece of event information corresponds to at least one first action indication information.
  • condition information may include: a delay threshold corresponding to the managed object corresponding to the closed-loop management process, and/or a throughput threshold corresponding to the managed object corresponding to the closed-loop management process.
  • the event information may include one or more of the following: notification events corresponding to the managed objects corresponding to the closed-loop management process, and/or notification events corresponding to managed objects other than the managed objects corresponding to the closed-loop management process, and events generated by the network management production entity. notification events, and notification events generated by network management production entities other than network management production entities.
  • the entity receiving the first message is the first network management production entity
  • the closed-loop management process corresponding to the first network management production entity is the first closed-loop management process
  • the management process corresponding to the first closed-loop management process The object is the first managed object
  • the closed-loop management process associated with the first closed-loop management process is the second closed-loop management process
  • the entity used to manage the second closed-loop management process is the second network management production entity
  • the first message also It may include one or more of the following: the identification of the second network management production entity, the identification of the second closed-loop management process, and the guarantee target of the first closed-loop management process.
  • the management policy information may further include one or more first sub-action indication information, and the first sub-action indication information may be used to instruct the first network management production entity to send the second network management production entity to the second network management production entity.
  • a notification information and/or a first operation result the first notification information may include the guarantee target of the second closed-loop management process that the network management consumption entity expects the second network management production entity to adopt, and the first operation result may be the first network management production entity
  • the entity obtains according to the first action indication information, or, the first operation result may be obtained by the first network management and production entity according to one or more items of condition information and event information, and the first action indication information.
  • the network management method provided by the second aspect may further include: receiving a second message from the network management production entity.
  • the second message may include the first operation result and/or the first modification request information
  • the first operation result may be obtained by the network management production entity according to the first action instruction information
  • the first operation result may be the network management production Obtained by the entity according to one or more items of condition information and event information
  • the first action instruction information, the first modification request information may be used to request modification of management policy information and/or guarantee objectives of the closed-loop management process.
  • the network management method provided in the second aspect may further include: according to the first operation result of at least one network management production entity and/or the first modification request information of at least one network management production entity, Identify new management policy information and/or new assurance objectives for closed-loop management processes.
  • the network management method provided by the second aspect may further include: sending new management policy information and/or new guarantee targets of the closed-loop management process to the network management production entity.
  • the guarantee objectives of the N closed-loop management processes may be determined by the network management consuming entity according to the demand information of the N managed objects.
  • the association relationship information may be determined by the network management consuming entity according to the association relationship between the managed objects respectively corresponding to the N closed-loop management processes.
  • the number of closed-loop management processes managed by the network management production entity may be one or more.
  • the association relationship may include a connection relationship, or a containment relationship, or a sharing relationship.
  • a network management device is provided.
  • the network management device is used to manage the first closed-loop management process.
  • the first closed-loop management process is a management process for realizing the SLS target of the first managed object.
  • the first managed object is the resource or business managed by the first closed-loop management process.
  • the second closed-loop management process is a management process for realizing the SLS target of the second managed object.
  • the second closed-loop management process is managed by the second network management and production entity, and the second managed object is the resource or service managed by the second closed-loop management process.
  • the network management device includes: a transceiver module and a processing module.
  • the transceiver module is configured to receive the first message from the network management consumption entity.
  • a processing module configured to execute one or more first management policies in the first management policy information.
  • the first message includes first management policy information
  • the first management policy information is the management policy information corresponding to the first closed-loop management process, there is an association relationship between the first closed-loop management process and at least one second closed-loop management process
  • the second The management policy information corresponding to the closed-loop management process is the second management policy information
  • the first management policy information and at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process
  • the first management policy information includes one or more first management policies.
  • the first management policy information may include one or more first action indication information, and the first action indication information may be used to instruct the network management device to set the first managed object corresponding to the first closed-loop management process configuration information.
  • the first management policy information may further include: one or more condition information, and/or one or more event information.
  • one piece of condition information corresponds to at least one first action indication information
  • one piece of event information corresponds to at least one first action indication information.
  • condition information may include: a relationship between performance of the first managed object corresponding to the first closed-loop management process and a performance threshold.
  • the event information may include one or more of the following: a notification event corresponding to the first managed object corresponding to the first closed-loop management process, and/or a notification event corresponding to a managed object other than the first managed object corresponding to the first closed-loop management process A notification event, a notification event generated by a network management device, and a notification event generated by a first network management device other than the network management device.
  • the processing module is further configured to set configuration information of the first managed object corresponding to the first closed-loop management process according to the first action indication information.
  • the processing module is further configured to set the first managed object corresponding to the first closed-loop management process according to the first action indication information. configuration information.
  • the entity receiving the first message is the first network management device
  • the management object corresponding to the first closed-loop management process is the first managed object
  • the entity used to manage the second closed-loop management process is
  • the first message may also include one or more of the following: the identifier of the second network management production entity, the identifier of the second closed-loop management process, and the guarantee target of the first closed-loop management process.
  • the first management policy information may further include one or more first sub-action indication information, and the first sub-action indication information may be used to instruct the first network management device to send to the second network management production entity
  • the first notification information and/or the first operation result, the transceiver module is further configured to send the first cooperation message to the second network management and production entity according to the identification of the second network management and production entity and the first sub-action indication information.
  • the first cooperation message may include the first notification information and/or the first operation result
  • the first notification information may include the guarantee target of the second closed-loop management process that the network management consumption entity expects the second network management production entity to adopt
  • the first The operation result may be obtained by the first network management device according to the first action instruction information
  • the first operation result may be obtained by the first network management device according to one or more of condition information and event information, and the first action instruction information obtained.
  • the transceiver module is further configured to send the second message to the network management consumption entity.
  • the second message may include the first operation result and/or the first modification request information
  • the first operation result may be obtained by the first network management device according to the first action instruction information
  • the first operation result may be the first Obtained by the network management device according to one or more of the condition information and event information
  • the first action instruction information the first modification request information may be used to request modification of the first management policy information and/or the first closed-loop management process Safeguard goals.
  • the first modification request information may be determined by the first network management device according to the second notification information and/or the second operation result.
  • the second notification information may include the guarantee target of the first closed-loop management process that the network management consumer entity expects the first network management device to adopt, and the second operation result may be obtained by the second network management production entity according to the first action instruction information,
  • the second running result may be obtained by the second network management and production entity according to one or more items of condition information and event information, and the first action indication information.
  • the transceiver module is further configured to receive a second cooperation message from the second network management and production entity.
  • the second cooperation message may include the second notification information and/or the second operation result.
  • the transceiving module is further configured to receive new first management policy information and/or new guarantee targets of the first closed-loop management process from the network management consuming entity.
  • the first running result may include one or more of the following: the first performance result, the identification of the first management policy information corresponding to the first performance result, the condition information corresponding to the first performance result, The event information corresponding to the first performance result, and the first action instruction information corresponding to the first performance result.
  • the first performance result may include a performance result of the first managed object.
  • the number of closed-loop management processes managed by the network management device may be one or more.
  • the association relationship may include a connection relationship, or a containment relationship, or a sharing relationship.
  • the transceiver module described in the third aspect may include a receiving module and a sending module.
  • the receiving module is used to receive data and/or signaling from the network management consumption entity and/or other network management production entities;
  • the sending module is used to send data and/or signaling to the network management consumption entity and/or other network management production entities / or signaling.
  • This application does not specifically limit the specific implementation manner of the transceiver module.
  • the network management device described in the third aspect may further include a storage module, where programs or instructions are stored in the storage module.
  • the processing module executes the program or instruction
  • the network management device described in the third aspect can execute the method described in the first aspect.
  • the network management device described in the third aspect may be a network management production entity, or may be a chip (system) or other components or components that may be installed in the network management production entity, which is not limited in this application.
  • a network management device in a fourth aspect, includes: a transceiver module and a processing module.
  • the processing module is configured to determine N pieces of management strategy information according to the association relationship information and the guarantee objectives of the N closed-loop management processes.
  • a transceiver module configured to send the first message to at least two network management and production entities.
  • the relationship information includes the relationship between N closed-loop management processes, N is an integer greater than 1, the closed-loop management process is a management process to achieve the SLS target of the managed object, and the managed object is the resource managed by the closed-loop management process Or business, N management policy information is used to realize the guarantee goal of N closed-loop management processes, and N closed-loop management processes are in one-to-one correspondence with N managed objects.
  • the first message includes management strategy information
  • the network management production entity is used to manage the closed-loop management process
  • the management strategy information includes one or more management strategies.
  • the management policy information may include one or more first action indication information, and the first action indication information may be used to instruct the network management production entity to set the configuration information of the managed object corresponding to the closed-loop management process.
  • the management policy information may further include: one or more condition information, and/or one or more event information.
  • one piece of condition information corresponds to at least one first action indication information
  • one piece of event information corresponds to at least one first action indication information.
  • condition information may include: a delay threshold corresponding to the managed object corresponding to the closed-loop management process, and/or a throughput threshold corresponding to the managed object corresponding to the closed-loop management process.
  • the event information may include one or more of the following: notification events corresponding to the managed objects corresponding to the closed-loop management process, and/or notification events corresponding to managed objects other than the managed objects corresponding to the closed-loop management process, and events generated by the network management production entity. notification events, and notification events generated by network management production entities other than network management production entities.
  • the entity receiving the first message is the first network management production entity
  • the closed-loop management process corresponding to the first network management production entity is the first closed-loop management process
  • the management process corresponding to the first closed-loop management process The object is the first managed object
  • the closed-loop management process associated with the first closed-loop management process is the second closed-loop management process
  • the entity used to manage the second closed-loop management process is the second network management production entity
  • the first message also It may include one or more of the following: the identification of the second network management production entity, the identification of the second closed-loop management process, and the guarantee target of the first closed-loop management process.
  • the management policy information may further include one or more first sub-action indication information, and the first sub-action indication information may be used to instruct the first network management production entity to send the second network management production entity to the second network management production entity.
  • a notification information and/or a first operation result the first notification information may include the guarantee target of the second closed-loop management process that the network management device expects the second network management production entity to adopt, and the first operation result may be the first network management production entity
  • the first operation result may be obtained according to the first action indication information, or the first operation result may be obtained by the first network management and production entity according to one or more items of condition information and event information, and the first action indication information.
  • the transceiver module is further configured to receive the second message from the network management and production entity.
  • the second message may include the first operation result and/or the first modification request information
  • the first operation result may be obtained by the network management production entity according to the first action instruction information
  • the first operation result may be the network management production Obtained by the entity according to one or more items of condition information and event information
  • the first action instruction information, the first modification request information may be used to request modification of management policy information and/or guarantee objectives of the closed-loop management process.
  • the processing module is further configured to determine new management policy information and and/or new assurance objectives for the closed-loop management process.
  • the transceiver module is further configured to send new management policy information and/or new guarantee targets of the closed-loop management process to the network management and production entity.
  • the guarantee objectives of the N closed-loop management processes may be determined by the network management device according to the demand information of the N managed objects.
  • the association relationship information may be determined by the network management device according to the association relationship between the managed objects respectively corresponding to the N closed-loop management processes.
  • the number of closed-loop management processes managed by the network management production entity may be one or more.
  • the association relationship may include a connection relationship, or a containment relationship, or a sharing relationship.
  • the transceiver module described in the fourth aspect may include a receiving module and a sending module.
  • the receiving module is used to receive data and/or signaling from the network management production entity;
  • the sending module is used to send data and/or signaling to the network management production entity.
  • This application does not specifically limit the specific implementation manner of the transceiver module.
  • the network management device described in the fourth aspect may further include a storage module, where programs or instructions are stored in the storage module.
  • the processing module executes the program or instruction
  • the network management device described in the fourth aspect can execute the method described in the second aspect.
  • the network management device described in the fourth aspect may be a network management consuming entity, or a chip (system) or other components or components that may be configured in the network management consuming entity, which is not limited in this application.
  • a network management device in a fifth aspect, includes: a processor, the processor is coupled with a memory, and the memory is used for storing computer programs.
  • the processor is configured to execute the computer program stored in the memory, so that the network management method described in any possible implementation manner of the first aspect to the second aspect is executed.
  • the network management device described in the fifth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an input/output port.
  • the transceiver can be used for the network management device to communicate with other devices.
  • the input port can be used to realize the receiving function involved in the first aspect to the second aspect
  • the output port can be used to realize the sending function involved in the first aspect to the second aspect
  • the network management device described in the fifth aspect may be a network management consuming entity or a network management producing entity, or a chip or a chip system disposed inside the network management consuming entity or the network management producing entity.
  • a network management system in a sixth aspect, includes a network management consumption entity, a first network management production entity, and at least one second network management production entity, the first network management production entity is used for managing the first closed-loop management process, and the second network management production entity is used for Manage the second closed-loop management process.
  • the first closed-loop management process is a management process for realizing the SLS target of the first managed object.
  • the second closed-loop management process is a management process for realizing the SLS target of the second managed object.
  • the first The managed object is the resource or business managed by the first closed-loop management process
  • the second managed object is the resource or business managed by the second closed-loop management process; wherein,
  • the network management consumption entity is used to determine N pieces of management strategy information according to the association relationship information and the guarantee objectives of the N closed-loop management processes; wherein, the association relationship information includes the association relationship between the N closed-loop management processes, and N is greater than 1 Integer, N pieces of management policy information are used to achieve the guarantee goal of N closed-loop management processes, N closed-loop management processes include a first closed-loop management process and at least one second closed-loop management process, N management policy information includes first management policy information and at least one second management strategy information, the first management strategy information includes one or more first management strategies, and the second management strategy information includes one or more second management strategies;
  • the network management consumption entity is further configured to send the first management policy information to the first network management production entity, and send at least one second management policy information to at least one second network management production entity;
  • the first network management production entity is configured to receive the first management policy information from the network management consumption entity;
  • the first network management production entity is further configured to implement one or more first management policies in the first management policy information
  • the second network management production entity is configured to receive the second management policy information from the network management consumption entity;
  • the second network management production entity is further configured to implement one or more second management policies in the second management policy information.
  • the network management consumption entity may be used to implement the method described in the second aspect above
  • the first network management production entity may be used to implement the method described in the first aspect above
  • the second network management production entity may be used to implement the above method described in the second aspect.
  • the network management system includes at least two network management devices according to the third aspect and the network management device according to the fourth aspect.
  • the number of network management consumption entities may be one or more.
  • a chip system in a seventh aspect, includes a logic circuit and an input/output port.
  • the logic circuit is used to realize the processing function involved in the first aspect to the second aspect
  • the input/output port is used to realize the sending and receiving function involved in the first aspect to the second aspect.
  • the input port can be used to realize the receiving function involved in the first aspect to the second aspect
  • the output port can be used to realize the sending function involved in the first aspect to the second aspect.
  • the chip system further includes a memory, which is used for storing program instructions and data for realizing the functions involved in the first aspect to the second aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a computer-readable storage medium stores a computer program or an instruction; when the computer program or instruction is run on a computer, any one of the first aspect to the second aspect The network management method described in a possible implementation manner is executed.
  • a ninth aspect provides a computer program product, including a computer program or instruction, when the computer program or instruction is run on a computer, the network management described in any one of the possible implementations of the first aspect to the second aspect method is executed.
  • FIG. 1 is a schematic diagram of the architecture of a network management system provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of another network management system provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a network management method provided in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a managed object provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another managed object provided by the embodiment of the present application.
  • FIG. 6 is a schematic diagram of a network slice management architecture provided by an embodiment of the present application.
  • FIG. 7 is a schematic flow chart of another network management method provided in the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another network management method provided in the embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network management device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another network management device provided by an embodiment of the present application.
  • the technical solution of the embodiment of the present application can be applied to various network management systems, such as wireless fidelity (wireless fidelity, WiFi) system, vehicle to any object (vehicle to everything, V2X) communication system, device-to-device (device-to-device) , D2D) communication system, vehicle networking communication system, 4th generation (4G) mobile communication system, such as long term evolution (long term evolution, LTE) system, worldwide interconnection microwave access (worldwide interoperability for microwave access, WiMAX) Communication systems, fifth generation (5th generation, 5G) mobile communication systems, such as new air interface (new radio, NR) systems, and future communication systems, such as sixth generation (6th generation, 6G) mobile communication systems, etc.
  • 4G 4th generation
  • LTE long term evolution
  • WiMAX worldwide interconnection microwave access
  • 5th generation, 5G mobile communication systems
  • new air interface new radio, NR
  • future communication systems such as sixth generation (6th generation, 6G) mobile communication systems, etc.
  • the present application presents various aspects, embodiments or features in terms of a system that can include a number of devices, components, modules and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. In addition, combinations of these schemes can also be used.
  • the network architecture and business 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 limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
  • FIG. 2 is a schematic structural diagram of a network management system to which the closed-loop management method provided in the embodiment of the present application is applicable.
  • the network management system includes a network management consumption entity and at least two network management production entities, for example, a network management production entity 1 and a network management production entity 2 .
  • the number of network management consumption entities may be one or more.
  • the above-mentioned network management consumption entity is used to interact with the network management production entity, and may instruct the network management production entity to manage the closed-loop management process.
  • the network management consumption entity can be used to determine the management policy information corresponding to the closed-loop management process, and send it to the network management production entity corresponding to the closed-loop management process, so that the network management production entity can manage the closed-loop management process according to the management policy information. Refer to the method shown in Figure 3 below.
  • the network management consumption entity may also be called a closed-loop (close loop, CL) management consumption entity, a closed-loop management consumer, a closed-loop management service consumer, a network management consumer, or a 3GPP management framework consumer (as shown in FIG. 1 shown), this application takes the network management consumer entity as an example for illustration.
  • 3GPP management framework consumers may include business support system (business support system, BSS), vertical industry operation and maintenance technology (operational technology, OT) system (vertical OT system), etc.
  • the network management consumption entity may be a physical device, and the functions of the network management consumption entity may be deployed on the physical device.
  • the network management consumption entity may be a functional module deployed in the physical device.
  • the above network management production entity is used to interact with the network management consumption entity and/or other network management production entities, can receive management policy information from the network management consumption entity, and coordinate and manage the closed-loop management process according to the management policy information, and can communicate with Other network management and production entities cooperate to manage the closed-loop management process.
  • a network management production entity can manage one or more closed-loop management processes, and different network management producers can manage different closed-loop management processes.
  • network management production entity 1 is used to manage closed-loop management process 1
  • network management production entity 2 is used to manage closed-loop management processes. Management closed-loop management process2.
  • the network management production entity may be called a closed-loop management production entity, a closed-loop management producer, a network management producer, or a closed-loop management service producer, etc.
  • This application uses the network management production entity as an example for illustration.
  • the network management production entity may be a physical device, and the functions of the network management production entity may be deployed on the physical device.
  • the network management production entity may be a functional module deployed in the physical device.
  • the network management consumption entity and the network management production entity, or different network management production entities can be deployed in a centralized or distributed manner.
  • the network management consumption entity and the network management production entity may be different hardware modules deployed in the same physical device, or may be different physical devices.
  • the functions of the network management consumption entity and the network The function of managing the production entity may be deployed in different hardware modules in the same physical device, and may also be deployed in different physical devices, which is not limited in this application.
  • the centralized deployment or distributed deployment of different network management and production entities is similar, and will not be repeated in this application.
  • the network management production entity may include but not limited to: monitor (monitor, M) management production entity, analysis (analysis, A) management production entity, decision (decision, D) management production entity, And execution (execution, E) manages production entities.
  • monitor monitoring management production entity
  • analysis analysis
  • decision decision
  • execution execution
  • E execution
  • the monitoring management production entity is used to perform monitoring functions to provide monitoring services
  • the analysis management production entity is used to perform analysis functions to provide analysis services
  • the decision-making management production entity is used to provide decision-making services for decision-making functions
  • the execution management production entity is used to implement execution functions to provide Execute the service.
  • the network management production entity can schedule the decision-making management production entity, execution management production entity, monitoring management production entity, and analysis management production entity, thereby supporting the closed-loop management process.
  • decision management production entity can be called decision management producer
  • execution management production entity can be called execution management producer
  • monitoring management production entity can be called monitoring management producer
  • analysis management production entity can be called analysis management Producers
  • the decision management production entity, the execution management production entity, the monitoring management production entity, and the analysis management production entity can be deployed in a centralized manner (such as deployed in the network management production entity) or distributed deployment, This application does not limit this.
  • monitoring and management production entity can be deployed in the network management production entity, or can be deployed in a physical device together with the network management production entity, or can be integrated with the network management production entity.
  • the network management and production entities are deployed independently, and communicate through the management service database entity (also called an integration bus).
  • the functional entity that provides the service can be called the producer or provider of the corresponding service, and the functional entity that consumes the service can be called the consumer of the corresponding service.
  • Various "producers” in this application can also be “consumers”. Use Services provided by other "Producers”.
  • network management method provided in the embodiment of the present application can be applied between any two nodes shown in Figure 2, such as between a closed-loop management consumption entity and a closed-loop management production entity, or between at least two closed-loop management production entities
  • any two nodes shown in Figure 2 such as between a closed-loop management consumption entity and a closed-loop management production entity, or between at least two closed-loop management production entities
  • FIG. 2 is only a simplified schematic diagram for ease of understanding, and the network management system may also include other entities, which are not shown in FIG. 2 .
  • the first item, network slices and network slice subnets are The first item, network slices and network slice subnets:
  • Network slicing refers to a logical network that provides specific network capabilities and network attributes.
  • Network slicing supports a variety of differentiated service types, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (massive machine type communications). type communication, mMTC), etc.
  • a network slice may include multiple subnets, such as a radio access network subnet (subnet), a transport network (transport network, TN) subnet, and a core network subnet.
  • a network slice instance may include a network slice subnet instance (network slice subnet instance, NSSI) of a wireless network, an NSSI of a transmission network, and an NSSI of a core network.
  • NSSI is a collection of network functions (network function, NF) and required physical/virtual resources.
  • the NSI may include a group of network function instances and required resources (such as computing, storage and network resources), which are used to form a deployed network slice.
  • An NSI can be an end-to-end logical network instance that provides specific network capabilities and attributes.
  • An NSI can consist of one or more NSSIs.
  • the network function may be a processing function in the network, and may be used to define functional behaviors and interfaces.
  • the NF may include a physical network function (physical network function, PNF) and a virtual network function, the physical network function may be understood as a traditional network element, and the virtual network function may be a virtualized network function.
  • the end-to-end logical network may be a network between a terminal device and an application server, and may include, for example, a radio access network, a core network, and/or a transmission network.
  • a network slice subnet can represent a set of managed functions and management aspects of required resources (such as computing, storage, and network resources), and is a network subnet formed by one or more NFs and their networking , which can be part of an end-to-end logical network, such as a radio access network subnet, a core network subnet, or a transport subnet.
  • a network slice subnet instance can represent a group of managed function instances and the management aspects of resources used (such as computing, storage, and network resources).
  • NSSI is formed by one or more NFs and their networking. NSSI can be composed of parts or complete The NSI of the NSI, the NSSI may be the NSSI of the wireless network, the NSSI of the transmission network, or the NSSI of the core network.
  • the second item, the managed object is a
  • Managed objects can be resources or services.
  • resources may include but not limited to one or more of the following: network elements (for example, equipment, resources related to network elements, such as wireless spectrum, computing resources, storage resources, bandwidth resources, etc.), subnets, and networks.
  • a network can be a physical network or a logical network, such as a network slice or a network slice subnet.
  • Services may refer to various services carried by the network, such as vertical industry services (such as programmable logic controller (programmable logic controller, PLC) control, video monitoring, remote monitoring, etc.), voice, video and other services.
  • vertical industry services such as programmable logic controller (programmable logic controller, PLC) control, video monitoring, remote monitoring, etc.
  • voice video and other services.
  • the managed object may be one of the following items: a physical network, a service provided by a physical network, a logical network, a service provided by a logical network, a component of a physical network and a logical network (such as a device, a network element), or the services it provides.
  • the managed object may be one of the following items: communication service instance, subnetwork (subnetwork), network slice, network slice subnetwork, NSI, NSSI, communication service, device, and network element.
  • the managed object may also be called a managed network, a managed network entity (managed entity), a managed logical network (managed logical network), a managed network device, and the like.
  • the network management production entity may also be called a management subject or a management node (management node), which is not specifically limited in this application.
  • Table 1 below lists network management production entities and corresponding managed objects, corresponding to different managed objects, network management production entities may have different names.
  • Network Management Production Entity managed object Communication Services
  • Network Management Production Entity communication service or communication service instance
  • Network Slicing Network Management Production Entity Network slicing, NSI Network slicing subnet network management production entity Network slice subnet, NSSI
  • the communication service or communication service instance is the managed object of the communication service network management production entity; the network slice or network slice instance is the managed object of the network slice network management production entity; the network slice subnet or network slice subnet The network instance is the managed object of the network management production entity of the network slice subnet.
  • the network slicing subnet includes the network slicing subnet of the wireless access network domain, the network slicing subnet of the core network domain, and the network slicing subnet of the transport domain.
  • the closed-loop management process may be a management process to achieve the SLS goal of the managed object.
  • the closed-loop management process may include functions (such as monitoring functions, analysis functions, decision-making functions, execution functions), management services (such as monitoring, analysis, decision-making, execution), methods and process etc.
  • the closed-loop management process may be called SLS guarantee closed-loop, or closed-loop management service, etc., or the closed-loop management process may be simply called closed-loop.
  • the closed-loop management process deployed at the cross-domain level and provides end-to-end network slicing SLS guarantee services can be called a closed-loop management process at the network slice level.
  • the closed-loop management process deployed in the RAN domain and provides The closed-loop management process of the SLS guarantee service of the network slice subnet in the RAN domain can be called the closed-loop management process of the network slice subnet level, which is deployed in the closed-loop management process of the CN domain and provides the SLS guarantee service of the network slice subnet of the CN domain
  • the closed-loop management process may be referred to as a network slice subnet-level closed-loop management process.
  • FIG. 3 is a schematic flow chart of a network management method provided in an embodiment of the present application.
  • the network management method can be applied to the communication between any two nodes shown in FIG. 2 .
  • the network management method includes the following steps:
  • the network management consumption entity determines N pieces of management policy information according to the association relationship information and the guarantee objectives of the N closed-loop management processes.
  • the association relationship information may include the association relationship between N closed-loop management processes, where N is an integer greater than 1, and the N closed-loop management processes correspond to the N managed objects one-to-one.
  • association relationship among the N closed-loop management processes may include a connection relationship, or a containment relationship, or a sharing relationship, and the like.
  • the N closed-loop management processes may be managed by N different network management and production entities.
  • the N closed-loop management processes may include a first closed-loop management process and at least one second closed-loop management process, there is an association between the first closed-loop management process and at least one second closed-loop management process, and the first closed-loop management process is controlled by the first The network management production entity manages, and the second closed-loop management process is managed by the second network management production entity.
  • the N managed objects may include a first managed object and at least one second managed object, the first closed-loop management process corresponds to the first closed-loop management process, and the second closed-loop management process corresponds to the second closed-loop management process.
  • the closed-loop management process may be a management process for realizing the SLS target of the managed object.
  • the closed-loop management process may be a management process for realizing the SLS target of the managed object.
  • the first closed-loop management process may be a management process for realizing the SLS goal of the first managed object.
  • the second closed-loop management process may be a management process for realizing the SLS goal of the second managed object.
  • the managed object may be a resource or service managed by a closed-loop management process.
  • the managed object may be a resource or service managed by a closed-loop management process.
  • the first managed object may be a resource or service managed by the first closed-loop management process.
  • the second managed object may be a resource or service managed by the second closed-loop management process.
  • the association relationship information may be determined by the network management consuming entity according to the association relationship between the managed objects respectively corresponding to the N closed-loop management processes.
  • FIG. 4 is a schematic diagram of a managed object provided by an embodiment of the present application.
  • managed objects include NSI, NSSI-1, and NSSI-2.
  • NSI is a cross-domain network slice
  • NSSI-1 is a slice subnet of RAN domain 1
  • NSSI-2 is a slice subnet of RAN domain 2
  • NSSI-1 is a slice subnet of RAN domain
  • NSSI-2 is CN Sliced subnets for the domain.
  • NSI corresponds to closed-loop management process 1
  • NSSI-1 corresponds to closed-loop management process 2
  • NSSI-2 corresponds to closed-loop management process 3.
  • NSI includes NSSI-1 and NSSI-2, NSSI-1 and NSSI-2 are connected, then the association relationship between NSI and NSSI-1 is an inclusion relationship, the association relationship between NSI and NSSI-2 is an inclusion relationship, and NSSI- The association relationship between 1 and NSSI-2 is a connection relationship.
  • the closed-loop management process 1 to closed-loop management process 3 is: the relationship between closed-loop management process 1 and closed-loop management process 2 is an inclusion relationship, the relationship between closed-loop management process 1 and closed-loop management process 3 is an inclusion relationship, and the relationship between closed-loop management process 2 and closed-loop management process
  • the association relationship of 3 is a connection relationship.
  • FIG. 4 is illustrated by taking managed objects including NSI, NSSI-1, and NSSI-2 as an example, and this application does not limit the number of NSSI and NSI.
  • FIG. 5 is a schematic diagram of another managed object provided by the embodiment of the present application.
  • managed objects include NSI-1, NSI-2, and NSSI.
  • NSI-1 and NSI-2 are resource sharing relationships. For example, NSI-1 and NSI-2 share the slice subnet of the same RAN domain.
  • NSI-1 and NSI-2 are two different cross-domain network slices.
  • NSSI is Slice subnets of the RAN domain.
  • NSI-1 corresponds to closed-loop management process 4
  • NSI-2 corresponds to closed-loop management process 5
  • NSSI corresponds to closed-loop management process 6.
  • NSI-1 and NSI-2 are connected, NSI-1 contains NSSI, NSI-2 contains NSSI, then the association relationship between NSI-1 and NSI-2 is a sharing relationship, and the association relationship between NSI-1 and NSSI is inclusion Relationship, the association relationship between NSI-2 and NSSI is an inclusion relationship.
  • the closed-loop management process 4 to closed-loop can be obtained
  • the relationship between management processes 6 is: the relationship between closed-loop management process 4 and closed-loop management process 5 is a sharing relationship, the relationship between closed-loop management process 4 and closed-loop management process 6 is an inclusion relationship, and the relationship between closed-loop management process 5 and closed-loop management process
  • the association relationship of 6 is an inclusion relationship.
  • the association relationship of the multiple closed-loop management processes is a sharing relationship.
  • the situation that the managed objects corresponding to multiple closed-loop management processes share all resources is as follows, the closed-loop management process a is used to realize the throughput index requirement of the managed object a, and the closed-loop management process b is used to realize the delay index of the managed object a It is required that closed-loop management process a and closed-loop management process b correspond to different guarantee objectives of the same managed object (such as managed object a), then closed-loop management process a and closed-loop management process b correspond to the same managed object, and the same managed object resources are all the same, so the relationship between closed-loop management process a and closed-loop management process b is a sharing relationship.
  • the N pieces of management policy information can be used to achieve the assurance objectives of the N closed-loop management processes.
  • one piece of management policy information may include one or more management policies.
  • the N pieces of management policy information may include first management policy information and at least one piece of second management policy information.
  • the first management policy information may include one or more first management policies
  • the second management policy information may include one or more second management policies.
  • the guarantee objectives of the N closed-loop management processes may be determined by the network management consuming entity according to the demand information of the N managed objects.
  • the protection target may include business or network requirements
  • the network management consumer entity may determine N pieces of management policy information based on the association relationship information and the business or network requirements of the N closed-loop management processes. This application does not limit the name of the protection target .
  • the requirement information of the managed object may be a subset of attributes of a service level agreement (service level agreement, SLA) or SLS, for example, network slicing service requirements (service profile) and/or network slicing subnet performance requirements (slice profile) for all or part of the attributes in the index requirements.
  • SLA service level agreement
  • SLS network slicing service requirements
  • slice profile network slicing subnet performance requirements
  • the network slicing service requirements may include information such as latency, downlink throughput of the network slice (dLThptPerSlice), and uplink throughput of the network slice (uLThptPerSlice).
  • the network slicing subnet performance requirements may include information such as delay of the network slicing subnet, downlink throughput of the network slicing subnet (dLThptPerSliceSubnet), and uplink throughput of the network slicing subnet (uLThptPerSliceSubnet).
  • the network management consumption entity can determine the end-to-end delay of the closed-loop management process at the network slice level according to the end-to-end delay requirement in the network slice service requirements, and determine the RAN domain delay in the network slice subnet performance requirement Requirements, determine the delay of the closed-loop management process of the RAN domain network slice subnet level, and determine the delay of the closed-loop management process of the CN domain network slice subnet level according to the CN domain delay requirement in the network slice subnet performance requirements.
  • the guarantee target of the closed-loop management process 1 may include: the end-to-end delay is less than the first threshold; the guarantee target of the closed-loop management process 2 may include: the delay of the RAN domain 1 is less than the second threshold;
  • the guaranteed goal of the closed-loop management process 3 may include: the latency of the RAN domain 2 is less than a third threshold.
  • the first threshold, the second threshold and the third threshold may be the same or different.
  • the management policy information may include one or more first action indication information.
  • the first action instruction information may be used to instruct the network management production entity to set the configuration information of the managed object corresponding to the closed-loop management process.
  • the configuration information may include but not limited to one or more of the following: radio resource configuration information, core network resource configuration information, and parameter configuration (such as handover parameter) information.
  • the first action instruction information can be used to: instruct the network management production entity to allocate resources for the managed object corresponding to the closed-loop management process, instruct the network management production entity to adjust (or modify) the managed object corresponding to the closed-loop management process
  • the resource configuration information of the management object instructing the network management production entity to delete the resource configuration information of the managed object corresponding to the closed-loop management process, instructing the network management production entity to add the resource configuration information of the managed object corresponding to the closed-loop management process, and/or instruct the network Manage production entities modify configuration parameters.
  • a first action indication information may be called a management policy.
  • a piece of first action indication information in the first management policy information may be called a first management policy.
  • a piece of first action indication information in the second management policy information may be called a second management policy.
  • the specific implementation manners of the N pieces of management strategy information can refer to the implementation manners of the management strategy information described above and below, and the main difference between the N pieces of management strategy information is that the N pieces of management strategy information Management policy information corresponds to different closed-loop management processes and managed objects.
  • management policy information 1 corresponds to closed-loop management process 1 and managed object 1
  • management policy information 2 corresponds to closed-loop management process 2 and managed object 2.
  • the management policy information may include an identification of the management policy information.
  • the management policy information may further include: one or more condition information, and/or one or more event information.
  • condition information may include: the relationship between the network or service of the managed object corresponding to the closed-loop management process and the network threshold or service threshold.
  • the network or service of the managed object may include but not limited to one or more of the following: delay and throughput.
  • the network or service threshold may include but not limited to one or more of the following: delay threshold, and throughput threshold.
  • condition information may include: the latency of the managed object is greater than the latency threshold, and/or the throughput of the managed object is smaller than the throughput threshold.
  • one piece of condition information may correspond to at least one piece of first action indication information.
  • a piece of condition information and a corresponding piece of first action indication information may be referred to as a management policy.
  • a piece of condition information in the first management policy information and a corresponding piece of first action indication information may be referred to as a first management policy.
  • a piece of condition information in the second management policy information and a corresponding piece of first action indication information may be referred to as a second management policy.
  • the network management producer may execute one or more operations indicated by the first action indication information when one piece of condition information is satisfied.
  • the event information may include one or more of the following: notification events corresponding to managed objects corresponding to the closed-loop management process, and/or notification events corresponding to managed objects other than the managed objects corresponding to the closed-loop management process, network The notification event generated by the management production entity and the notification event generated by the network management production entity other than the network management production entity.
  • the notification events corresponding to the managed objects corresponding to the closed-loop management process may include: preconfigured periodic events and condition-triggered events; the notification events corresponding to the managed objects other than the managed objects corresponding to the closed-loop management process may include: Pre-configured periodic events and condition-triggered events; notification events generated by network management production entities may include: pre-configured periodic events and condition-triggered events; notification events generated by network management production entities other than the network management production entity may include : Preconfigured periodic events and conditional trigger events.
  • a condition-triggered event may include an event triggered by a condition (such as a watchdog, or a condition corresponding to other mechanisms, etc.).
  • a condition such as a watchdog, or a condition corresponding to other mechanisms, etc.
  • one piece of event information may correspond to at least one piece of first action indication information.
  • a piece of event information and a corresponding piece of first action indication information may be referred to as a management policy.
  • a piece of event information and a corresponding piece of first action indication information in the first management policy information may be referred to as a first management policy.
  • a piece of event information in the second management policy information and a corresponding piece of first action indication information may be referred to as a second management policy.
  • the network management producer may execute one or more operations indicated by the first action indication information when one event information is satisfied.
  • one piece of event information and one piece of condition information may correspond to at least one piece of first action instruction information.
  • a piece of event information, a piece of condition information, and a corresponding piece of first action indication information may be referred to as a management policy.
  • a piece of event information, a piece of condition information, and a corresponding piece of first action indication information in the first management policy information may be referred to as a first management policy.
  • An event information, a condition information, and a corresponding first action indication information in the second management policy information may be referred to as a second management policy.
  • the network management producer may execute one or more operations indicated by the first action indication information.
  • the management policy information may further include one or more first subaction indication information.
  • the management policy information may include: one or more first action indication information, and one or more first sub-action indication information.
  • the management policy information may include: one or more first action indication information, one or more condition information, and one or more first sub-action indication information.
  • the management policy information may include: one or more first action indication information, one or more event information, and one or more first sub-action indication information.
  • the management policy information may include: one or more first action indication information, one or more condition information, one or more event information, and one or more first sub-action indication information.
  • event information and/or condition information may correspond to the first sub-action indication information.
  • the network management producer may perform one or more operations indicated by the first subaction indication information.
  • a piece of event information, a piece of condition information, and a corresponding piece of first subaction indication information may be referred to as a management policy.
  • This application does not enumerate the management strategies one by one.
  • a piece of event information, a piece of condition information, and a corresponding piece of first subaction indication information in the first management policy information may be referred to as a first management policy.
  • An event information, a condition information, and a corresponding first subaction indication information in the second management policy information may be referred to as a second management policy.
  • the first subaction instruction information may be used to instruct the first network management production entity to send the first notification information and/or the first operation result to the second network management production entity.
  • the entity receiving the first message is the first network management production entity
  • the closed-loop management process managed by the first network management production entity is the first closed-loop management process, which exists with the first closed-loop management process
  • the closed-loop management process of the association relationship is the second closed-loop management process
  • the entity used to manage the second closed-loop management process is the second network management production entity.
  • the number of the second closed-loop management process may be one or more
  • the number of the second network management production entity may be one or more.
  • the network management production entity 1 receives the first message
  • the network management production entity 1 is the first network management production entity
  • the closed-loop management process 1 is the first closed-loop management process.
  • the network management production entity 2 is the second network management production entity
  • the closed-loop management process 2 is the second closed-loop management process.
  • the network management production entity 2 receives the first message
  • the network management production entity 2 is the first network management production entity
  • the closed-loop management process 2 is the first closed-loop management process.
  • the network management production entity 1 is the first network management production entity.
  • the second network manages the production entity
  • the closed-loop management process 1 is the second closed-loop management process.
  • both the network management production entity 1 and the network management production entity 2 can receive the first message, and the network management production entity 2 receives the management policy information 1 corresponding to the closed-loop management process 1 included in the first message received by the network management production entity 1.
  • the first notification information may include the guarantee target of the second closed-loop management process that the network management consuming entity expects the second network management producing entity to adopt.
  • the first operation result may be obtained by the first network management and production entity according to the first action instruction information, or the first operation result may be obtained by the first network management and production entity according to one of condition information and event information or Multiple items, and the first action indicates that the information is obtained.
  • the management policy information may include a strategy for instructing the first network management production entity to cooperate with the second network management production entity, and the network management production entities may cooperate according to the first sub-action instruction information, so as to control the closed-loop management process Coordinate management.
  • the first running result may include one or more of the following: the first performance result, the identification of the management policy information corresponding to the first performance result, the condition information corresponding to the first performance result, the corresponding The event information of the event information and the first action indication information corresponding to the first performance result.
  • the management object corresponding to the first closed-loop management process is the first managed object, and the first performance result may include a performance result of the first managed object.
  • the first performance result includes: the throughput of the first managed object is >100 megabits per second (million bits per second, Mbps), or the performance result of the first managed object satisfies or fails the first closed-loop management process protection goals.
  • the first running result may include one or more of the following: the first performance result, the identification of the management policy information used to obtain the first performance result, condition information, event information, and first action instruction information.
  • the second network management and production entity can determine whether to adjust its own strategy according to the first operation result, so as to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process.
  • the management policy information corresponding to the closed-loop management process will be described below with reference to FIG. 4 and Tables 2 to 4.
  • Table 2 takes the closed-loop management process in Figure 4 including closed-loop management process 1 and closed-loop management process 2, NSI is cross-domain network slicing, NSSI-1 is RAN domain slice subnet, and delay as an example.
  • the first action instruction information corresponding to the closed-loop management process 1 instructs the network management producer 1 to increase the network slice resource configuration so that the end-to-end delay is ⁇ 10ms.
  • the first action indication information corresponding to the closed-loop management process 2 instructs the network management producer 2 to increase the network slice resource configuration, so as to reduce the RAN domain delay to ⁇ 5ms.
  • the condition information corresponds to the first action instruction information, and when the condition information is satisfied, the network management producer executes the operation in the first action instruction information.
  • the first sub-action indication information corresponding to the closed-loop management process 1 may instruct the network management producer 1 to send the first notification information to the network management producer 2, and may also indicate to send the first operation result (not shown in Table 2).
  • the first sub-action indication information corresponding to the closed-loop management process 2 may instruct the network management producer 2 to apply the guarantee target in the first notification information when the event information is satisfied, and may also instruct the network management producer 2 to apply the first notification Events of assurance targets in the information are reported to the network management consuming entity, and/or the network management producer 1 (not shown in Table 2).
  • the network management producer 2 executes the operation indicated by the first sub-action indication information.
  • the first sub-action indication information corresponding to the closed-loop management process 1 may correspond to or not correspond to the condition information corresponding to the closed-loop management process 1 .
  • Table 2 is only an example.
  • the management policy information may include more or less content than that in Table 2, and this application does not list them all.
  • Table 3 takes the closed-loop management process in Figure 4 including closed-loop management process 2 and closed-loop management process 3
  • NSSI-1 is the slice subnet of the RAN domain
  • NSSI-2 is the slice subnet of the CN domain
  • the throughput as an example.
  • the first action instruction information corresponding to the closed-loop management process 2 instructs the network management producer 2 to increase the network slice resource configuration, so that the throughput of the RAN domain network slice subnet is >100 Mbps.
  • the first action indication information corresponding to the closed-loop management process 3 instructs the network management producer 3 to increase the resource configuration of the network slice, so that the throughput of the network slice in the CN domain is >100 Mbps.
  • the condition information corresponds to the first action instruction information, and when the condition information is satisfied, the network management producer executes the operation in the first action instruction information.
  • the first sub-action indication information corresponding to the closed-loop management process 2 can instruct the network management producer 2 to send the first notification information to the network management producer 3, and can also indicate to send the first operation result (not shown in Table 3), because the closed-loop Management process 2 and closed-loop management process 3 are connected (connected in series), and the throughput bottleneck of any segment will affect the cross-domain throughput performance.
  • the management producer 2 and the network management producer 2 are cooperation messages of each other).
  • the first sub-action indication information corresponding to the closed-loop management process 3 may instruct the network management producer 3 to apply the guarantee target in the first notification information when the event information is satisfied, and may also instruct the network management producer 3 to apply the first notification Events of assurance targets in the information are reported to the network management consuming entity, and/or the network management producer 2 (not shown in Table 3).
  • the network management producer 3 executes the operation indicated by the first sub-action indication information, and the first sub-action indication information corresponding to the closed-loop management process 2 may be the same as that corresponding to the closed-loop management process 2. Correspondence to condition information.
  • Table 3 is only an example.
  • the management policy information may include more or less content than that in Table 3, and this application does not list them all.
  • the closed-loop management process in Figure 4 includes closed-loop management process 1 to closed-loop management process 3.
  • NSI is a cross-domain network slice
  • NSSI-1 is a slice subnet in the RAN domain
  • NSSI-2 is a slice subnet in the CN domain. Latency or throughput as an example.
  • the first action instruction information respectively corresponding to the closed-loop management process 1 to the closed-loop management process 3 respectively indicates to increase the configuration of network slice resources, so as to achieve the respectively corresponding guarantee goals.
  • the condition information may correspond to the first action instruction information, and if the condition information is satisfied, the network management producer executes the operation in the corresponding first action instruction information.
  • the first sub-action indication information 1 corresponding to the closed-loop management process 1 can instruct the network management producer 1 to send the first notification information 1 to the network management producer 2 or the network management producer 3, and can also indicate to send the first operation result (Table 4 not shown).
  • the first sub-action indication information 1 corresponding to the network management producer 2 or the network management producer 3 indicates that the network management producer 2 or the network management producer 3 receives the first notification information 1 (satisfies the event information 1), then Applying the guarantee target in the first notification information 1 according to the first sub-action instruction information can increase the subnet resource configuration of the corresponding domain slice, so as to achieve the guarantee target of delay ⁇ 5 ms.
  • the closed-loop management process 2 or the first sub-action indication information 2 corresponding to the network management producer 3 may instruct the network management producer 2 or 3 to send the first operation result and/or the first modification request information to the network management producer 1, optional Specifically, the first modification request information may be used to request modification of management policy information and/or assurance objectives of the closed-loop management process.
  • the first sub-action indication information 3 corresponding to the network management producer 1 may indicate that the network management producer 1 receives the first operation result and/or the first modification request information (satisfied event information), and then sends the network management producer entity 2 or 3 to send the first notification information 3, for example, the first notification information 3 may include a throughput > 90 Mbps.
  • the closed-loop management process 2 or the first sub-action indication information 3 corresponding to the network management producer 3 may indicate that the first notification information 3 (satisfying the event information 2) is received from the network management production entity 1, then the first notification is applied For the guarantee goal in Information 3, the resource configuration of the corresponding domain slice subnet can be added to achieve the guarantee goal of throughput >90Mbps.
  • the first sub-action indication information 5 of the closed-loop management process 2 may instruct the network management producer 2 to send the first notification information 5 to the network management producer 3, for example, when the first notification information 5 may include the CN domain corresponding to the closed-loop management process 3 If the delay is ⁇ 5ms, it may also indicate to send the first running result (not shown in Table 4).
  • the first sub-action indication information 4 corresponding to the network management producer 3 may indicate that the network management producer 3 receives the first notification information 5 (satisfies the event information 3), and then applies the guarantee target in the first notification information 5, You can increase the corresponding domain slice subnet resource configuration to achieve the guarantee goal of delay ⁇ 5ms.
  • the first sub-action indication information 5 of the closed-loop management process 3 may instruct the network management producer 3 to send the first notification information 4 to the network management producer 2, for example, when the first notification information 4 may include the RAN domain corresponding to the closed-loop management process 2 If the delay is ⁇ 5ms, it may also indicate to send the first running result (not shown in Table 4).
  • the first sub-action instruction information 4 corresponding to the network management producer 2 may indicate that the network management producer 2 receives the first notification information 4 (satisfies the event information 3), and then applies the guarantee target in the first notification information 4, You can increase the corresponding domain slice subnet resource configuration to achieve the guarantee goal of delay ⁇ 5ms.
  • a network management producer such as network management producer 1, network management producer 2, network management producer 3, etc.
  • receives multiple first notification messages within a preset time window and multiple first If the content of the notification information is the same, the operation in the first sub-action instruction information may be performed only once.
  • the first sub-action instruction information or the first action corresponding to the multiple first notification information can be executed according to the priorities of multiple closed-loop management processes Instructions.
  • the priority of the closed-loop management process 1 is higher than that of the closed-loop management process 2
  • the priority of the closed-loop management process 2 is higher than that of the closed-loop management process 3
  • the network management producer 1 receives the first notification information from the network management producer 2, and The first notification information of network management producer 3, if there is a conflict between the two first notification information, first execute the action triggered by the first notification information of network management producer 2, and then execute the first notification information of network management producer 3 Actions triggered by information.
  • Table 4 is only an example.
  • the management policy information may include more or less content than that in Table 3, and this application does not list them all.
  • the management policy information corresponding to the closed-loop management process will be described in detail below in conjunction with FIG. 5 and Table 5.
  • Table 5 takes the closed-loop management process in FIG. 5 including closed-loop management process 4 and closed-loop management process 5, NSI-1 and NSI-2 as two different cross-domain network slices, and throughput as an example.
  • the first action indication information corresponding to the closed-loop management process 4 instructs the network management producer 4 to increase the configuration of network slice resources, so that the cross-domain 1 network slice throughput is less than 100 Mbps.
  • the first action indication information corresponding to the closed-loop management process 5 instructs the network management producer 5 to increase the network slice resource configuration so that the cross-domain 2 network slice throughput is ⁇ 120 Mbps.
  • the condition information corresponds to the first action instruction information, and when the condition information is satisfied, the network management producer executes the operation in the first action instruction information.
  • the first sub-action indication information corresponding to the closed-loop management process 4 may instruct the network management producer 4 to send the first notification information to the network management producer 5, and may also indicate to send the first operation result (not shown in Table 5).
  • the first sub-action indication information corresponding to the closed-loop management process 5 may instruct the network management producer 5 to apply the guarantee target in the first notification information when the event information is satisfied, and may also instruct the network management producer 5 to apply the first notification Events of assurance targets in the information are reported to the network management consuming entity, and/or the network management producer 4 (not shown in Table 5).
  • the network management producer 5 executes the operation indicated by the first sub-action indication information, and the first sub-action indication information corresponding to the closed-loop management process 4 may be the same as that corresponding to the closed-loop management process 4. Correspondence to condition information.
  • Table 5 is only an example.
  • the management policy information may include more or less content than that in Table 5, and this application does not list them all.
  • the network management consuming entity sends a first message to at least two network management producing entities.
  • the network management producing entity receives the first message from the network management consuming entity.
  • the sending may be divided into multiple steps.
  • the above S302 may include: S302-1, the network management consumption entity sends a first message to the first network management production entity , S302-2.
  • the network management consuming entity sends the first message to the second network management producing entity.
  • the first network management producing entity receives the first message from the network management consuming entity
  • the second network management producing entity receives the first message from the network management consuming entity.
  • the first message may include management policy information.
  • the first message received by the first network management and production entity includes first management policy information
  • the first message received by the second network management and production entity includes second management policy information
  • the combination of the first management policy information and the second management policy information The main difference is that: the first management policy information corresponds to the first closed-loop management process
  • the second management policy information corresponds to the second closed-loop management process.
  • At least two network management production entities include a network management production entity 1 and a network management production entity 2, the network management production entity 1 is used to manage the closed-loop management process 1, and the network management production entity 2 is used to manage the closed-loop management process 2, then the network
  • the first message 1 sent by the management consumption entity to the network management production entity 1 may include management policy information 1 ;
  • the first message 2 sent by the network management consumption entity to the network management production entity 2 may include management policy information 2 .
  • the network management production entity 1 can realize the guaranteed goal of the closed-loop management process 1 according to the management policy information 1
  • the network management and production entity 2 can realize the guaranteed goal of the closed-loop management process 2 according to the management policy information 2 .
  • a network management production entity may be used to manage the closed-loop management process.
  • the number of closed-loop management processes managed by a network management production entity is one or more.
  • the embodiment of the present application is described by taking the management of a closed-loop management process by a network management production entity as an example.
  • the entity receiving the first message is the first network management and production entity
  • the first message may include first management policy information
  • the first management policy information is the management policy information corresponding to the first closed-loop management process
  • the first closed-loop management There is an association relationship between the process and at least one second closed-loop management process
  • the management policy information corresponding to the second closed-loop management process is the second management policy information.
  • the first management policy information and the at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of the at least one second closed-loop management process.
  • N pieces of management policy information can be used to realize the guarantee goal of N closed-loop management processes, and the sum of the number of first management policy information and at least one second management policy information can be N.
  • the entity receiving the first message is the first network management production entity
  • the closed-loop management process managed by the first network management production entity is the first closed-loop management process
  • the object is the first managed object
  • the closed-loop management process associated with the first closed-loop management process is the second closed-loop management process
  • the entity used to manage the second closed-loop management process is the second network management production entity.
  • the first message may further include one or more of the following items: an identifier of the second network management production entity, an identifier of the second closed-loop management process, and a guarantee target of the first closed-loop management process.
  • the first message received by the second network management production entity may also include one or more of the following: the identifier of the first network management production entity, the identifier of the first closed-loop management process, and the guarantee of the second closed-loop management process Target.
  • the first message 1 sent by the network management consumption entity to the network management production entity 1 may include management policy information 1, the identification of the network management production entity 2, the identification of the closed-loop management process 2, and the guarantee target of the closed-loop management process 1;
  • the first message 2 sent by the consumer entity to the network management production entity 2 may include management policy information 2 , the identifier of the network management production entity 1 , the identifier of the closed-loop management process 1 , and the guarantee target of the closed-loop management process 2 .
  • the network management production entity 1 and the network management production entity 2 can not only realize the assurance goals of their respective closed-loop management processes according to their respective management policy information, but also obtain the network management production entity associated with themselves, their own The closed-loop management process associated with the closed-loop management process of management, so as to negotiate the guarantee objectives of the closed-loop management process with the relationship.
  • the first network management production entity executes one or more first management policies in the first management policy information.
  • the first network management production entity executes one or more first management policies in the first management policy information, where the first management policy information is determined according to the association relationship information and the guarantee objectives of the N closed-loop management processes, Considering the assurance objectives of this closed-loop management process and the assurance objectives of the closed-loop management process associated with this closed-loop management process, in this way, the SLS objectives of managed objects (such as network slices and/or network slice subnets) can be achieved.
  • managed objects such as network slices and/or network slice subnets
  • the above S303 may include: the first network management production entity sets configuration information of the first managed object corresponding to the first closed-loop management process according to the first action indication information.
  • the network management production entity 1 is the first network management production entity, and the network management production entity 1 adds network slice resource configuration according to the first action indication information corresponding to the first closed-loop management process 1, so that the RAN The domain delay is less than 10ms, so that the guarantee target corresponding to the closed-loop management process 1 can be guaranteed.
  • the above S303 may include: when the condition information and/or event information are satisfied, the first network management production entity sets the first closed-loop management process corresponding to the first action instruction information according to the first action instruction information. Configuration information of a managed object.
  • the network management production entity 1 is the first network management production entity, and if the end-to-end delay>10ms, the first network management production entity increases the network slice resource configuration according to the first action instruction information , so that the end-to-end delay is less than 10ms, so that the guarantee target corresponding to the closed-loop management process 1 can be guaranteed.
  • the network management production entity 1 is the first network management production entity
  • the conditional trigger event instructs the network management production entity 1 to network management
  • the production entity 2 sends the first notification information.
  • the above S303 may include: the first network management production entity sends the first cooperation message to the second network management production entity according to the identifier of the second network management production entity and the first subaction indication information.
  • the second network management production entity receives the first collaboration message from the first network management production entity.
  • the first cooperation message may include the first notification information and/or the first operation result
  • the first notification information may include the guarantee target of the second closed-loop management process that the network management consumption entity expects the second network management production entity to adopt
  • the first operation result may be obtained by the first network management production entity according to the first action instruction information
  • the first operation result may be obtained by the first network management production entity according to one or more of condition information and event information
  • the first action indicates that information is obtained.
  • the first network management production entity is network management production entity 1
  • the first network management production entity reports to network management production entity 2 according to the identification of network management production entity 2 and the first sub-action instruction information
  • a first cooperation message is sent, where the first cooperation message includes first notification information, and the first notification information may include the RAN domain delay corresponding to the closed-loop management process 2 ⁇ 3 ms.
  • the first network management and production entity can cooperate with the second network management and production entity, so as to meet the guarantee target corresponding to the closed-loop management process.
  • the above S303 may include: when the condition information and/or event information are satisfied, the first network management production entity indicates information according to the identifier of the second network management production entity and the first sub-action , sending the first collaboration message to the second network management and production entity.
  • the first network management production entity is network management production entity 1
  • the first network management production entity sends a network management production entity according to the first sub-action instruction information.
  • the entity 2 sends a first cooperation message, where the first cooperation message includes first notification information, and the first notification information may include the RAN domain delay corresponding to the closed-loop management process 2 ⁇ 3 ms.
  • the first network management production entity is network management production entity 1
  • the first network management production entity 2 and the first sub-action indication information 3 send the first cooperation message to the network management production entity 2
  • the first cooperation message includes the first notification information 3
  • the first notification information 3 may include the throughput corresponding to the closed-loop management process 2 Volume>90Mbps.
  • the first network management production entity is the network management production entity 1
  • the first network management production entity sends the first cooperation message to the network management production entity 2
  • the first cooperation message includes the first notification information
  • the first notification information may include the RAN domain delay corresponding to the closed-loop management process 2 ⁇ 3ms.
  • the attribute corresponding to the first closed-loop management process does not meet the guarantee target, and/or when the first modification request information is received from the second network management production entity, it can cooperate with the second network management production entity, so that Make the attributes corresponding to the closed-loop management process meet the assurance objectives.
  • the network management method provided in the embodiment of the present application may further include: S305, the first network management production entity sends the first cooperation message to the second network management production entity.
  • the second network management production entity receives the first collaboration message from the first network management production entity.
  • the first cooperation message includes the first notification information and/or the first running result.
  • the first network management production entity may directly send the second cooperation message to the second network management production entity, regardless of whether the management policy information includes the first subaction indication information.
  • the network management method provided in the embodiment of the present application may further include: S306, the second network management production entity sets the first closed-loop management process corresponding to the second closed-loop management process according to the guarantee target in the first notification information. 2. The configuration information of the managed object.
  • the first notification information is received from the first network management and production entity.
  • the guarantee target corresponding to the closed-loop management process 2 is RAN domain delay ⁇ 5ms
  • the network management production entity 2 receives the first notification information
  • the first notification information includes the RAN domain corresponding to the closed-loop management process 2
  • the network management and production entity 2 applies the guarantee target of RAN domain delay ⁇ 3ms, and increases RAN domain slice subnet resources to make the RAN domain delay less than 3ms.
  • the second network management production entity and the first network management production entity can cooperate to realize the guarantee target of the first managed object and/or the second managed object.
  • the embodiment of the present application does not limit the order of the above S306 and the following S304, for example, the above S306 may be performed after the following S304.
  • the second network management production entity executes one or more second management policies in the second management policy information.
  • the first network management production entity and the second network management production entity may first negotiate, for example, negotiate one or more second management policies in the management policy information to be executed (for example, the management policy information includes multiple management policies), and for example, the condition information in the management policy information to be executed can be negotiated (for example, the management policy information includes multiple condition information).
  • the second network management production entity executes one or more second management policies in the second management policy information, where the second management policy information is determined according to the association relationship information and the assurance objectives of the N closed-loop management processes, Taking into account the guarantee objectives of this closed-loop management process (such as the second closed-loop management process) and the closed-loop management processes (such as one or more first closed-loop management processes) that are associated with this closed-loop management process.
  • SLS targets for managed objects such as network slices and/or network slice subnets.
  • the above S304 may include: the second network management production entity sets the configuration information of the second managed object corresponding to the second closed-loop management process according to the first action indication information.
  • the network management production entity 2 adds network slice resource configuration according to the first action instruction information corresponding to the first closed-loop management process 2, so that the RAN The domain delay is less than 5ms, so that the guarantee target corresponding to the closed-loop management process 2 can be guaranteed.
  • the above S304 may include: when the condition information and/or event information are satisfied, the second network management production entity sets the first action instruction information corresponding to the second closed-loop management process. 2. The configuration information of the managed object.
  • the network management production entity 2 is the second network management production entity, and if the RAN domain delay>5ms, the network management production entity 2 increases the network slice resource configuration according to the first action instruction information, so as to Make the end-to-end delay ⁇ 5ms, so as to guarantee the guarantee target corresponding to the closed-loop management process 2.
  • the network management production entity 2 is the second network management production entity, and if the first notification information from the network management production entity 1 is received, the network management production entity 2 applies the guarantee in the first notification information
  • the goal is to increase the configuration of network slicing resources so that the end-to-end delay is less than 5ms, so that the guarantee goal corresponding to the closed-loop management process 2 can be guaranteed.
  • the network management production entity 2 may also report the event of applying the assurance target in the first notification information to the network management consumption entity.
  • the network management production entity 2 is the second network management production entity, if the RAN domain delay>5ms, a conditional trigger event is triggered, and the conditional trigger event instructs the network management production entity 2 to increase network slice resources configuration.
  • the above S304 may include: the second network management production entity sends the second cooperation message to the second network management production entity according to the identifier of the first network management production entity and the first subaction indication information.
  • the specific implementation is similar to that in S303 where the first network management production entity sends the first cooperation message to the second network management production entity according to the identifier of the second network management production entity and the first sub-action indication information, and will not be repeated here.
  • the second cooperation message may include the second notification information and/or the second running result.
  • the second notification information may include the guarantee target of the first closed-loop management process that the network management consuming entity expects to be adopted by the first network management producing entity.
  • the second operation result may be obtained by the second network management production entity according to the first action instruction information, or the second operation result may be obtained by the second network management production entity according to one or more of condition information and event information. Multiple items, and the first action indicates that the information is obtained.
  • the second network management production entity can cooperate with the first network management production entity to meet the guarantee target corresponding to the closed-loop management process (eg, the first closed-loop management process and/or the second closed-loop management process).
  • the closed-loop management process eg, the first closed-loop management process and/or the second closed-loop management process.
  • the above S304 may include: when the condition information and/or event information are satisfied, the second network management production entity indicates information according to the identifier of the first network management production entity and the first sub-action , sending the second collaboration message to the first network management and production entity.
  • the specific implementation is the same as that in S303, when the condition information and/or event information are satisfied, the first network management production entity sends The first cooperation message is similar and will not be repeated here.
  • the attribute corresponding to the second closed-loop management process does not meet the guarantee target, and/or when the first modification request information is received from the first network management and production entity, it can cooperate with the first network management and production entity , so that the attributes corresponding to the closed-loop management process (for example, the first closed-loop management process and/or the second closed-loop management process) meet the guarantee target.
  • the closed-loop management process for example, the first closed-loop management process and/or the second closed-loop management process
  • the network management production entity (such as the first network management production entity, or the second network management production entity, etc.) can call other management service functions during the process of executing the management policy, for example, call the performance management (performance management, PM ) function, or fault management (fault management, FM) function to monitor performance or faults to determine whether the conditions in the associated policy are met, and call the function of orchestration management service (orchestration MnS) to reconfigure resources or parameters, etc.
  • performance management performance management
  • FM fault management
  • orchestration management service orchestration MnS
  • the network management method provided in the embodiment of the present application may further include: S307, the second network management production entity sends a second cooperation message to the first network management production entity.
  • the first network management production entity receives the second collaboration message from the second network management production entity.
  • the second cooperation message includes the second notification information and/or the second running result.
  • the second network management production entity may directly send the second cooperation message to the first network management production entity, regardless of whether the second management policy information includes the first subaction indication information.
  • network management and production entities can automatically cooperate in operation and maintenance, accelerate the convergence of the closed-loop management process, reduce message interaction between network management and production entities, and can coordinate in real time without relying on centrally deployed collaborators (such as network management consumer entities). Improves the efficiency of achieving SLS goals for managed objects.
  • the network management method provided in the embodiment of the present application may further include: S308.
  • the first network management production entity sets the first closed-loop management process corresponding to the first closed-loop management process according to the guarantee target in the second notification information. Configuration information of a managed object.
  • the second notification information is received from the second network management and production entity.
  • the closed-loop management process 3 is the first closed-loop management process
  • the network management producer 3 is the first network management production entity
  • the guarantee target corresponding to the closed-loop management process 3 is CN domain throughput > 100 Mbps
  • the network management production entity 3 receives the first notification information 3, and the first notification information 3 includes the CN domain throughput corresponding to the closed-loop management process 3 corresponding to the closed-loop management process 3>90Mbps
  • the network management production entity 3 applies the CN domain throughput>
  • the guaranteed goal of 90Mbps increases the CN domain slice subnet resources to make the CN domain throughput >90Mbps.
  • the first network management production entity and the second network management production entity can cooperate to realize the guarantee target of the first managed object and/or the second managed object.
  • the network management method provided in the embodiment of the present application may further include: S309, the first network management production entity sends a second message to the network management consumption entity.
  • the network management consuming entity receives the second message from the first network management producing entity.
  • the second message may include the first running result and/or the first modification request information of the first network management and production entity.
  • the first modification request information of the first network management production entity may be used to request modification of the first management policy information and/or the guarantee target of the first closed-loop management process.
  • the network management consuming entity can adjust the management policy information and/or guarantee target of the first closed-loop management process according to the first operation result and/or modification request.
  • the first modification request information of the first network management production entity may include management policy information expected to be used by the first network management production entity, and/or a guarantee target of the first closed-loop management process.
  • the first modification request information may include a delay ⁇ 3ms.
  • the network management consuming entity can directly adopt the management policy information and/or guarantee target included in the first modification request information as the management policy information and/or guarantee target of the first closed-loop management process; or refer to the first modification request information Adjust the management strategy information and/or guarantee objectives of the first closed-loop management process.
  • the first network management production entity implements one or more first management policies in the first management policy information (above S303) and has achieved the SLS target of the first managed object, then S309 may not be executed; Or perform S309, wherein the second message includes the first operation result, but does not include the first modification request information of the first network management and production entity.
  • the first modification request information of the first network management production entity may be determined by the first network management production entity according to the second notification information and/or the second operation result, and/or the first operation result.
  • the first network management production entity may determine whether to request modification according to the assurance target that the network management consumption entity expects it to adopt, the second operation result of the second network management production entity, and/or its own first operation result.
  • the assurance objective and/or management strategy information of the first closed-loop management process can also determine the desired assurance objective and/or management strategy information.
  • the second notification information and/or the second operation result may be received by the first network management production entity from the second network management production entity.
  • the first network management production entity may directly apply the guarantee target in the first notification information; and may also send an event of applying the guarantee target in the first notification information to the network management consumption entity.
  • the network management method provided in the embodiment of the present application may further include: S310, the second network management production entity sends a second message to the network management consumption entity.
  • the network management consuming entity receives the second message from the second network management producing entity.
  • the second message may include the second running result and/or the first modification request information of the second network management and production entity.
  • the first modification request information of the second network management production entity may be used to request modification of the second management policy information and/or the guarantee target of the second closed-loop management process.
  • the network management consuming entity can adjust the management policy information and/or guarantee target of the second closed-loop management process according to the second running result and/or modification request of the second network management producing entity.
  • the second modification request information of the second network management production entity may include management policy information expected to be used by the second network management production entity, and/or a guarantee target of the second closed-loop management process.
  • the network management consuming entity can directly adopt the management policy information and/or guarantee target included in the first modification request information as the management policy information and/or guarantee target of the second closed-loop management process; or refer to the first modification request information Adjust the management strategy information and/or guarantee objectives of the second closed-loop management process.
  • the second network management producing entity may periodically send the second message to the network management consuming entity.
  • the second network management production entity implements one or more second management policies in the second management policy information (above S304) and has achieved the SLS target of the second managed object, S310 may not be executed; Or perform S310, wherein the second message includes the second running result, but does not include the first modification request information of the second network management and production entity.
  • the first modification request information of the second network management and production entity is determined by the second network management and production entity according to the first notification information and/or the first operation result, and/or the second operation result .
  • the second network management production entity may determine whether to request modification according to the assurance target that the network management consumption entity expects it to adopt, the first operation result of the first network management production entity, and/or its own second operation result.
  • the assurance objective and/or management strategy information of the second closed-loop management process can also determine the desired assurance objective and/or management strategy information.
  • the network management method provided by the embodiment of the present application may further include: S311, the network management consumption entity according to the first operation result of at least one network management production entity and/or at least one network management production entity The first modification request information to determine the new management policy information and/or the new guarantee target of the closed-loop management process.
  • the new management policy information may include one or more new management policy information, such as new first management policy information, and/or new second management policy information.
  • the new guarantee target of the closed-loop management process may include the new guarantee target of the first closed-loop management process, and/or the new guarantee target of the second closed-loop management process.
  • the first operation result of at least one network management production entity may include: the first operation result of network management production entity 1 and/or the first operation result of network management production entity 2 .
  • the first modification request information of at least one network management production entity may include: the first modification request information of the network management production entity 1, and/or the first modification request information of the network management production entity 2.
  • the first notification information of the first sub-action indication information corresponding to the closed-loop management process 1 can be modified to: the RAN domain delay corresponding to the closed-loop management process 2 is ⁇ 6ms.
  • the network management consumption entity can adjust the management of one or more closed-loop management processes according to the first operation results of one or more network management production entities and/or the first modification request information of one or more network management production entities
  • the policy information and/or guarantee target so that the corresponding network management production entity further realizes the SLS target of the corresponding managed object according to the new management policy information and/or the new guarantee target.
  • the network management method provided in this application may support manual or external entities to optimize management policy information and/or guarantee objectives, for example, manually according to the first operation result of at least one network management production entity and/or at least one network management production entity
  • the entity's first modification request information determines new management policy information and/or a new guarantee target of the closed-loop management process.
  • the network management method provided by the embodiment of the present application may further include: S312, the network management consumption entity sends new first management policy information and/or the first closed-loop to the first network management production entity New assurance objectives for the management process.
  • the first network management production entity receives the new first management policy information and/or the new assurance target of the first closed-loop management process from the network management consumption entity.
  • the first network management production entity can further realize the SLS target of the first managed object according to the new management policy information and/or the new guarantee target.
  • the network management method provided by the embodiment of the present application may further include: S313, the network management consumption entity sends new second management policy information and/or the second closed-loop to the second network management production entity New assurance objectives for the management process.
  • the second network management production entity receives the new second management policy information and/or the new assurance target of the second closed-loop management process from the network management consumption entity.
  • the second network management production entity can further realize the SLS target of the second managed object according to the new second management policy information and/or the new guarantee target.
  • first network management production entity implements one or more first management policies in the first management policy information (above S303) and has achieved the SLS target of the first managed object, then S309 may not be executed; If the second network management production entity implements one or more second management policies (above S304) in the second management policy information and has achieved the SLS target of the second managed object, then S310 may not be performed.
  • the first network management production entity receives first management policy information, and executes one or more first management policies in the first management policy information.
  • the first management policy information is management policy information corresponding to the first closed-loop management process, there is an association relationship between the first closed-loop management process and at least one second closed-loop management process, the second closed-loop management process corresponds to the second management policy information, and the first closed-loop management process corresponds to the second management policy information.
  • One piece of management policy information and at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process
  • the first managed object is the resource managed by the first closed-loop management process or business
  • the first closed-loop management process is a management process for realizing the SLS target of the first managed object
  • the second closed-loop management process is a management process for realizing the SLS target of the second managed object
  • the second closed-loop management process is controlled by the second network Manage production entity management.
  • the first network management and production entity can realize the SLS target of the first managed object (such as network slices and/or network slice subnets, etc.), which can improve user service experience and ensure normal operation of services.
  • a network management consumption entity determines N pieces of management policy information according to the association relationship information and the guarantee objectives of N closed-loop management processes as an example.
  • the N pieces of management policy information can be Determined by two or more network management consuming entities, for example, the first network management consuming entity and the second network management consuming entity can negotiate and determine N pieces of management strategy information according to the association relationship information and the guarantee objectives of N closed-loop management processes.
  • one network management consuming entity may send N pieces of management policy information to N network management producing entities, for details, refer to the foregoing S302-1 and S302-2.
  • multiple network management consumption entities may send N management policy information to N network management production entities, for example, the first network management consumption entity sends the first management policy to the first network management production entity information, the second network management consuming entity sends the second management policy information to the second network management producing entity.
  • the process of generating management policy information will be described below with reference to FIG. 6 and FIG. 7 .
  • the network management method shown in FIG. 7 can be used in combination with the network management method shown in FIG. 3 above.
  • Management functions related to network slicing include communication service management function (communication service management function, CSMF), network slice management function (network slice management function, NSMF), and network slice subnet management function (network slice subnet management function, NSSMF).
  • communication service management function communication service management function
  • CSMF communication service management function
  • NSMF network slice management function
  • NSSMF network slice subnet management function
  • the management architecture of network slicing is shown in Figure 6.
  • the management architecture of network slicing may include: communication service management service (communication service management service, CSMS) production entity, network slice management service (network slice management service, NSMS) production entity, network Slice subnet management service (network slice subnet management service, NSSMS) production entity.
  • the NSSMS production entity may include: RAN NSSMS production entity, CN NSSMS production entity and TN NSSMS production entity.
  • the management architecture of the network slice may also include: a CSMS consumption entity, an NSMS consumption entity, and an NSSMS consumption entity (not shown in FIG. 6 ).
  • the NSMS production entity manages the life cycle (such as creation, deletion, modification) and performance, alarm, etc. of the network slice instance NSI.
  • the NSSMS production entity manages the life cycle, performance, and alarms of the network slice subnet instance NSSI.
  • the CSMF and the CSMS production entity can be equivalently replaced, the NSMF and the NSMS production entity can be equivalently replaced, and the NSSMF and the NSSMS production entity can be equivalently replaced.
  • a “production entity” may be referred to as a "producer”, and a “consumption entity” may be referred to as a “consumer”.
  • the network management production entity may be a physical device, and the functions of the network management production entity may be deployed on the physical device.
  • the network management production entity may be a functional module deployed in the physical device.
  • FIG. 7 is a schematic flowchart of another network management method provided in the embodiment of the present application.
  • the network management method shown in FIG. 7 is mainly described in conjunction with FIG. 4 to generate management policy information, and the generated management policy information can be used in the network management method shown in FIG. 3 above.
  • the network management production entity may include: a network slice network management production entity, a RAN network slice subnet network management production entity, a CN network slice subnet network management production entity, and a TN network slice subnet network management production entity (Fig. When the method shown in 7 is used in combination with FIG. 4, the TN network slicing subnet network management production entity may not be included).
  • the NSMS production entity can manage the consumer of the production entity for the network slice network
  • the NSSMS production entity can manage the consumer of the production entity for the network slice subnet network.
  • the RAN NSSMS production entity can manage the consumption of the production entity for the RAN network slice subnet network
  • the CN NSSMS production entity can manage the consumers of the production entity for the CN network slice subnet network
  • the TN NSSMS production entity can manage the consumers of the production entity for the TN network slice subnet network.
  • the network management production entity may be a closed-loop management production entity (which may be called a closed-loop management producer, or a closed-loop management service producer, etc.), NSMS production entity, and NSSMS production entity.
  • the closed-loop management production entity , the NSMS production entity, and the NSSMS production entity may be different network management production entities.
  • the network management production entity in the method shown in FIG. 7 may be a closed-loop management production entity.
  • the network slice network management production entity may be a network slice closed-loop management production entity
  • the RAN network slice subnet network management production entity may be RAN network slicing subnet closed-loop management production entity
  • CN network slicing subnet closed-loop management production entity can be CN network slicing subnet closed-loop management production entity
  • TN network slicing subnet network management production entity can be TN network slicing subnet closed-loop management production entity entity.
  • the network management production entity in the method shown in FIG. 3 may be a closed-loop management production entity.
  • the network management production entity in the method shown in FIG. 8 may be a closed-loop management production entity.
  • the network management method includes the following steps:
  • the NSMS consumption entity sends a service requirement (service profile) to the NSMS production entity, requesting to create an NSI.
  • the NSMS producing entity receives service requirements from the NSMS consuming entity.
  • service requirements may include delay, bandwidth, security and reliability, and so on.
  • the NSMS production entity creates an NSI according to the service requirement.
  • the created NSI may be the NSI in FIG. 4 .
  • the NSMS production entity sends the service requirement or a subset of the service requirement to the closed-loop management production entity.
  • the closed-loop management production entity receives service requirements or a subset of service requirements from the NSMS production entity.
  • service requirements or subsets of service requirements can be targeted for assurance.
  • the network management production entity creates a first closed-loop management process.
  • the first closed-loop management process (which may be referred to as CL1) may support or realize a corresponding closed-loop goal.
  • the first closed-loop management process may include steps (monitoring, analysis, decision-making, execution), management services, methods and procedures involved in the closed-loop management control.
  • steps monitoring, analysis, decision-making, execution
  • management services methods and procedures involved in the closed-loop management control.
  • details please refer to the above description of the closed-loop management process.
  • the network management production entity associates the first closed-loop management process with the NSI as the network slice-level closed-loop management process CL1.
  • the network management production entity sends the first slice profile (slice profile) and the second slice profile to the NSSMS production entity.
  • the NSSMS production entity receives the first slice requirement and the second slice requirement from the network management production entity.
  • the first slice requirement may be used to request the creation of NSSI-1
  • the second slice requirement may be used to request the creation of NSSI-2.
  • the NSSMS production entity may include a RAN NSSMS production entity and a CN NSSMS production entity.
  • the above S705 may include: the network management production entity sends the first slice profile (slice profile) to the RAN NSSMS production entity, and sends the second slice profile to the CN NSSMS production entity.
  • the RAN NSSMS production entity receives the first slice requirement from the network management production entity
  • the CN NSSMS production entity receives the second slice requirement from the network management production entity.
  • the network management production entity may send service requirements or a subset of service requirements to the NSSMS production entity. Accordingly, the NSSMS production entity receives service requirements or a subset of service requirements from the network management production entity.
  • the NSSMS production entity creates NSSI-1 and NSSI-2.
  • the RAN NSSMS production entity may create NSSI-1 according to the first slice requirement, and the CN NSSMS production entity may create NSSI-2 according to the second slice requirement.
  • the NSSMS production entity sends the first slice requirement, the second slice requirement, and subnetwork-level management policy information to the network management production entity.
  • the network management production entity receives the first slice requirement, the second slice requirement, and subnetwork-level management policy information from the NSSMS production entity.
  • the network management production entity may include a RAN network slice subnet network management production entity and a CN network slice subnet network management production entity.
  • NSSI-1 there may be one network management production entity, or three different network management production entities respectively corresponding to NSI, NSSI-1, and NSSI-2.
  • the above S707 may include: the RAN NSSMS production entity sends the first slicing requirement and subnet-level management policy information to the RAN network slice subnet network management production entity; the CN NSSMS production entity sends the CN network slice subnet network The management production entity sends the second slice requirement and subnet level management policy information.
  • the RAN network slice subnet network management production entity receives the first slicing requirement and subnet level management policy information from the RAN NSSMS production entity; the CN network slice subnet network management production entity receives the first slice request from the CN NSSMS production entity 2. Slicing requirements, and subnet-level management policy information.
  • the RAN NSSMS production entity and the CN NSSMS production entity can determine the association relationship according to the service requirements, the association relationship between the first slice requirement and the second slice requirement, and the network composition information, and determine the subnet level management according to the association relationship policy information.
  • the management policy information at the subnet level may include management policy information corresponding to NSSI-1 and management policy information corresponding to NSSI-2.
  • the network composition information may include: NSI, NSSI-1 and NSSI-2.
  • the association relationship may include: NSI includes NSSI-1 and NSSI-2, and NSSI-1 and NSSI-2 are a connection relationship.
  • the RAN NSSMS production entity and the CN NSSMS production entity can serve as consumption entities of the network management production entity.
  • the network management production entity creates a second closed-loop management process and a third closed-loop management process.
  • the second closed-loop management process and the third closed-loop management process may respectively support or achieve corresponding assurance objectives.
  • the second closed-loop management process CL2 is associated with NSSI-1
  • the third closed-loop management process CL3 is associated with NSSI-2.
  • the second closed-loop management process and the third closed-loop management process may be network slicing subnet level closed-loop management processes.
  • both the second closed-loop management process and the third closed-loop management process may include steps (monitoring, analysis, decision-making, execution), management services, methods and processes involved in the closed-loop management control.
  • the above S708 may include: the RAN network management production entity creates a second closed-loop management process, and the CN network management production entity creates a third closed-loop management process.
  • the network management production entity sends subnetwork-level management policy information to the NSMS production entity.
  • the NSMS production entity sends the management policy information of the first closed-loop management process, the management policy information of the second closed-loop management process, and the management policy information of the third closed-loop management process to the network management production entity.
  • the network management production entity receives the management policy information of the first closed-loop management process, the management policy information of the second closed-loop management process, and the management policy information of the third closed-loop management process from the NSMS production entity.
  • the above S710 may include: the NSMS production entity sends the first closed-loop management process management to the network slice network management production entity, the RAN network slice subnet network management production entity, and the CN network slice subnet network management production entity respectively Policy information, management policy information of the second closed-loop management process, and management policy information of the third closed-loop management process.
  • the network slice network management production entity, the RAN network slice subnet network management production entity, and the CN network slice subnet network management production entity respectively receive the management policy information and the second closed-loop management process from the NSMS production entity. Management policy information of the management process, and management policy information of the third closed-loop management process.
  • the method shown in FIG. 7 may further include: the NSMS production entity determines the first closed-loop management process, the second closed-loop management process and the third closed-loop management process according to the association relationship of NSI, NSSI-1 and NSSI-2 According to the association relationship of the first closed-loop management process, the second closed-loop management process, the third closed-loop management process and the subnet level management policy information, the management policy information of the first closed-loop management process, the second closed-loop management process The management policy information of , and the management policy information of the third closed-loop management process.
  • FIG. 8 is a schematic flowchart of another network management method provided by the embodiment of the present application.
  • the network management method shown in FIG. 8 mainly describes the application of management policy information.
  • the network management method shown in FIG. 8 can be used in combination with the network management method shown in FIG. 3 and/or FIG. 7 .
  • the network management production entity can communicate with the M/A/D/E management production entity through the management service database entity, and the M/A/D/E management production entity can represent the monitoring management production entity, analysis management production entity, decision-making management production entity, Or executive management production entity abbreviation.
  • monitoring and management production entity the analysis management production entity, the decision-making management production entity, the execution management production entity, and the management service database entity can be deployed together with the network management production entity on one physical device, or can be integrated with the network management production entity Deploy independently or partially centrally.
  • the network management method shown in Figure 8 further opens the corresponding services for internal monitoring, analysis, decision-making, and execution of the closed-loop management process, and the corresponding functions are composed of monitoring and management of production entities, analysis and management
  • the production entity, the decision-making management production entity, and the execution management production entity are respectively executed, and how to register and discover the above-mentioned services through the management service database (MnS repository) entity is explained.
  • the content included in the management policy information can refer to the above-mentioned Figure 3
  • the method for generating management policy information may refer to the method shown in FIG. 7 .
  • the M/A/D/E management production entity sends a registration management service request to the management service database entity respectively.
  • the management service database entity receives the registration management service request from the M/A/D/E management production entity.
  • a registration management service request may be used to request management service registration.
  • the management service is a management service included in the closed loop, for example, monitoring, analysis, decision-making, execution, and the like.
  • the registration management service request may include registration information.
  • the registration information may include the identifier of the management service, the unique name of the service, the service port, the service address, and the like. In this way, management services can be discovered and invoked.
  • an identification of a management service may include an identification of a monitoring management service, an identification of an analysis management service, an identification of a decision management service, and an identification of an execution management service.
  • management service database (MnS repository) entity may also be called an integration bus (integration fabric).
  • the management service database entity sends registration success information to the M/A/D/E management production entities respectively.
  • management services such as M/A/D/E MnSes receive registration success information from the management service database entity.
  • the network management consuming entity sends the service requirement or a subset of the service requirement to one or more network management producing entities. Accordingly, the network management producing entity receives service requirements or a subset of service requirements from the network management consuming entities.
  • the network management consumption entity may include: a network slice management consumption entity, a RAN network slice subnet network management consumption entity, a CN network slice subnet network management consumption entity, and a TN network slice subnet network management consumption entity.
  • the network management production entity may include: a network slice network management production entity, a RAN network slice subnet network management production entity, a CN network slice subnet network management production entity, and a TN network slice subnet network management production entity.
  • the aforementioned network management production entity may be a network management consumption entity, for example, the network slice network management production entity may be a network management consumption entity of a network slice closed-loop management producer, and the like.
  • all or part of attributes of a service requirement or a subset of a service requirement can be used as an assurance target in the closed-loop management process.
  • One or more network management production entities send a request message to the management service database entity.
  • the management service database entity receives request messages from one or more network management production entities.
  • the request message may be used to request management service information, and the management service information may be used to generate a closed-loop management process.
  • the management service information may include a management service identifier, a service unique name, a service port, a service address, and the like.
  • the management service information may include the identifier of the M/A/D/E management production entity, the name, port or address of the M/A/D/E management production entity.
  • the management service database entity sends management service information to one or more network management production entities respectively.
  • the network management production entity receives management service information from the management service database entity.
  • the network management production entity generates a first closed-loop management process according to the management service information.
  • the first closed-loop management process may support or realize the SLS target of the corresponding managed object.
  • the network management production entity can call the M/A/D through information such as the identity of the M/A/D/E management production entity, the name, port or address of the M/A/D/E management production entity, etc. /E manages production entities.
  • the network management consuming entity sends the management policy information to the network management producing entity.
  • the network management producing entity receives management policy information from the network management consuming entity.
  • the network management production entity saves the management policy information.
  • the network management production entity sends corresponding management policy information to the M/A/D/E management production entity respectively.
  • the M/A/D/E management production entity respectively receives the management policy information from the network management production entity.
  • the network management and production entity may send management policy information related to monitoring to the M management and production entity, the network management and production entity may send management policy information related to analysis to the A management and production entity, and the network management and production entity may send the D management and production entity
  • the production entity sends management policy information related to decision-making, and the network management production entity can send management policy information related to execution to the E management production entity.
  • the network management production entity does not need to send corresponding management policy information to the M/A/D/E management production entity, and the network management production entity uniformly schedules management policy information related to monitoring and management related to analysis. Policy information, decision-related management policy information, and execution-related management policy information.
  • the network management production entity sends subscription messages to the M/A/D/E management production entities respectively.
  • the M/A/D/E management and production entities respectively receive subscription messages from the network management and production entities.
  • the subscription message may include but not limited to one or more of the following: performance, alarm measurement information, analysis information, decision information, and execution results.
  • the M/A/D/E management and production entities may respectively send the information that the network management and production entities request to subscribe to the network management and production entities.
  • the M/A/D/E management and production entity respectively sends a third message to the network management and production entity.
  • the network management production entity receives the third message from the M/A/D/E management production entity.
  • the third message may include but not limited to one or more of the following: performance, alarm measurement information, analysis information, decision information, and execution result.
  • the third message may be determined after the M/A/D/E management production entity obtains the management data according to the subscription message.
  • the management data may include attribute related data, alarm data, and the like.
  • attribute related data For example, data related to throughput, data related to delay, etc.
  • the M/A/D/E management and production entities may respectively send the third message periodically.
  • the management data may be collected by the monitoring and management production entity from the management system of the network element.
  • the data related to the throughput/delay of the RAN domain is obtained from the management system of the RAN
  • the data related to the throughput/delay of the CN domain is obtained from the management system of the CN.
  • the network management production entity executes the management policy in the management policy information.
  • the network management production entity performs management actions according to the management policy information, for example, calling the M/A/D/E management production entity to implement corresponding management policies.
  • the M/A/D/E management production entity executes the management strategy in the management strategy information.
  • the M/A/D/E management production entity may execute corresponding management policies according to the schedule of the network management production entity, or, the M/A/D/E management production entity may execute the corresponding management policy according to the management policy information received in S809 above Implement appropriate management strategies.
  • the M/A/D/E management production entity can obtain monitoring data, obtain management data analysis information, make management decisions, perform management actions, etc., and can also send the operation results to the network management production entity.
  • the network management method provided by the embodiment of the present application has been described in detail above with reference to FIGS. 3-8 .
  • the network management device provided by the embodiment of the present application will be described in detail below with reference to FIGS. 9-10 .
  • FIG. 9 is a schematic structural diagram of a network management device that can be used to implement the embodiment of the present application.
  • the network management device 900 may be a network management production entity (such as a first network management production entity or a second network management production entity, etc.), a network management consumption entity, an NSMS consumption entity, an NSMS production entity, an NSSMS production entity, or a management service database entity , or M/A/D/E management and production entities, and can also be applied to network management production entities, network management consumption entities, NSMS consumption entities, NSMS production entities, NSSMS production entities, management service database entities, or M/A/ D/E manages chips or other components with corresponding functions in the production entity. As shown in FIG.
  • the network management device 900 may include a processor 901 .
  • the network management apparatus 900 may further include one or more of a memory 902 and a transceiver 903 .
  • the processor 901 may be coupled with one or more of the memory 902 and the transceiver 903, such as through a communication bus, or the processor 901 may be used alone.
  • the components of the network management device 900 will be specifically introduced below in conjunction with FIG. 9 :
  • the processor 901 is the control center of the network management device 900, and may be one processor, or a general term for multiple processing elements.
  • the processor 901 is one or more central processing units (central processing unit, CPU), may also be a specific integrated circuit (application specific integrated circuit, ASIC), or is configured to implement one or more An integrated circuit, for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA).
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • An integrated circuit for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 901 can execute various functions of the network management device 900 by running or executing software programs stored in the memory 902 and calling data stored in the memory 902 .
  • the processor 901 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 9 .
  • the network management apparatus 900 may also include multiple processors, for example, the processor 901 and the processor 904 shown in FIG. 9 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more communication devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 902 may be a read-only memory (read-only memory, ROM) or other types of static storage communication devices that can store static information and instructions, or a random access memory (random access memory, RAM) that can store information and other types of dynamic storage communication devices for instructions, and can also be electrically erasable programmable read-only memory (EEPROM), 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 disc storage media or other magnetic storage communication devices, or can be used to carry or store desired information in the form of instructions or data structures program code and any other medium that can be accessed by a computer, but not limited to.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • Other optical disc storage optical disc storage (including compact discs, laser discs, optical discs, digital versatile disc
  • the memory 902 can be integrated with the processor 901, or can exist independently, and is coupled with the processor 901 through the input/output port (not shown in FIG. 9 ) of the network management device 900, which is not specifically limited in this embodiment of the present application. .
  • the input port can be used to implement the network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D in any of the above method embodiments.
  • /E manages the production entity, and can also be applied to the network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D/E management production entity execution
  • the receiving function, the output port can be used to implement any of the above method embodiments by the network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D /E manages the production entity, and can also be applied to the network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D/E management production entity execution send function.
  • the memory 902 may be used to store a software program for executing the solution of the present application, and the execution is controlled by the processor 901 .
  • the processor 901 may be used to control the execution of the solution of the present application.
  • the transceiver 903 is used for communication with other network management devices.
  • the transceiver 903 may be used to communicate with the network management consumption entity and/or other network management production entities.
  • the transceiver 903 may be used to communicate with at least two network management production entities.
  • the transceiver 903 may include a receiver and a transmitter (not separately shown in FIG. 9 ). Wherein, the receiver is used to realize the receiving function, and the transmitter is used to realize the sending function.
  • the transceiver 903 can be integrated with the processor 901, or can exist independently, and is coupled with the processor 901 through an input/output port (not shown in FIG. 9 ) of the network management device 900, which is not specifically described in this embodiment of the present application. limited.
  • network management device 900 does not constitute a limitation to the network management device.
  • An actual network management device may include more or less components, or different component arrangements.
  • the actions of the network management production entity (such as the first network management production entity, or the second network management production entity, etc.) in the above-mentioned Figures 3-8 can be called by the processor 901 in the network management device 900 shown in Figure 9
  • the application program code stored in the memory 902 is executed by instructing the network management production entity.
  • the above-mentioned actions of the network management consuming entity in FIGS. 3-8 can be executed by the processor 901 in the network management device 900 shown in FIG. 9 calling the application code stored in the memory 902 to instruct the network management consuming entity to execute This is without any limitation.
  • the actions of the NSMS consuming entities in FIGS. 3-8 above can be executed by the processor 901 in the network management device 900 shown in FIG. any restrictions.
  • the above-mentioned actions of the NSMS production entity in FIGS. 3-8 can be executed by the processor 901 in the network management device 900 shown in FIG. 9 calling the application program code stored in the memory 902 to instruct the NSMS production entity to execute. any restrictions.
  • the above-mentioned actions of the management service database entity in FIGS. 3-8 can be executed by the processor 901 in the network management device 900 shown in FIG. 9 calling the application program code stored in the memory 902 to instruct the management service database entity. This is without any limitation.
  • the above-mentioned actions of the M/A/D/E management production entity in FIGS. 3-8 can be invoked by the processor 901 in the network management device 900 shown in FIG.
  • the D/E manages the execution of the production entity, which is not limited in this embodiment.
  • the network management device 900 can execute the network management production entity (the first network management production entity) in the above method embodiment , or the second network management production entity) any one or more possible design methods involved; when the network management device is a network management consumption entity, the network management device 900 can execute the network management consumption entity in the above method embodiment Any one or more of the possible designs involved.
  • the network management device 900 can execute any one or more possible design methods involved in the NSMS consumer entity in the above method embodiments; when the network management device is an NSMS production entity, the network The management device 900 can implement any one or more possible design methods involved in the NSMS production entity in the above method embodiment; when the network management device is an NSSMS production entity, the network management device 900 can perform the above method embodiment.
  • any one or more possible design methods involved in the NSSMS production entity when the network management device is a management service database entity, the network management device 900 can execute any one of the management service database entities in the above method embodiments or multiple possible design modes; when the network management device is an M/A/D/E management production entity, the network management device 900 can execute the M/A/D/E management production entity involved in the above method embodiment Any one or more possible designs.
  • FIG. 10 is a schematic structural diagram of another network management device provided by an embodiment of the present application. For ease of description, FIG. 10 only shows the main components of the network management device.
  • the network management device 1000 includes a transceiver module 1001 and a processing module 1002 .
  • the network management device 1000 may be the network management production entity (such as the first network management production entity, or the second network management production entity, etc.), network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS Production entities, management service database entities, or M/A/D/E management production entities, can also be applied to network management production entities, network management consumption entities, NSMS consumption entities, NSMS production entities, NSSMS production entities, management service databases entity, or M/A/D/E manages the production entity.
  • the network management production entity such as the first network management production entity, or the second network management production entity, etc.
  • network management consumption entity such as the first network management production entity, or the second network management production entity, etc.
  • NSMS consumption entity such as the first network management production entity, or the second network management production entity, etc.
  • NSSMS Production entities such as the first network management production entity, or the second network management production entity, etc.
  • the transceiver module 1001 which may also be referred to as a transceiver unit, is used to implement the network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D/E management production entity can also be applied to network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D/ E manages the sending and receiving functions performed by the production entity.
  • the transceiver module 1001 may include a receiving module and a sending module (not shown in FIG. 10 ). Wherein, the receiving module is used for receiving data and/or signaling from other devices; the sending module is used for sending data and/or signaling to other devices. This application does not specifically limit the specific implementation manner of the transceiver module.
  • the transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the processing module 1002 can be used to implement the network management production entity (such as the first network management production entity, or the second network management production entity, etc.), the network management consumption entity, the NSMS consumption entity, and the NSMS production entity in any of the above method embodiments. Entities, NSSMS production entities, management service database entities, or M/A/D/E management production entities, can also be applied to network management production entities, network management consumption entities, NSMS consumption entities, NSMS production entities, NSSMS production entities, The processing function performed by the management service database entity, or the M/A/D/E management production entity.
  • the processing module 1002 may be a processor.
  • the network management apparatus 1000 is presented in the form of dividing various functional modules in an integrated manner.
  • a “module” here may refer to a specific ASIC, a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the functions described above.
  • the network management device 1000 can take the form of the network management device 900 shown in FIG. 9 .
  • the processor 901 in the network management apparatus 900 shown in FIG. 9 may invoke the computer-executed instructions stored in the memory 902, so that the network management method in the foregoing method embodiments is executed.
  • the functions/implementation process of the transceiver module 1001 and the processing module 1002 in FIG. 10 can be implemented by the processor 901 in the network management device 900 shown in FIG. 9 invoking computer-executed instructions stored in the memory 902 .
  • the function/implementation process of the processing module 1002 in FIG. 10 can be realized by the processor 901 in the network management device 900 shown in FIG.
  • the function/implementation process can be realized by the transceiver 903 in the network management device 900 shown in FIG. 9 .
  • the network management device 1000 provided in this embodiment can execute the above-mentioned network management method, the technical effect it can obtain can refer to the above-mentioned method embodiment, and details are not repeated here.
  • the network management device 1000 shown in FIG. 10 can be applied to the network management system shown in FIG. 1 and FIG.
  • the first network manages the functions of the production entities.
  • the network management device 1000 is used to manage the first closed-loop management process
  • the first closed-loop management process is a management process for realizing the SLS target of the first managed object
  • the first managed object is the resource or service managed by the first closed-loop management process
  • the second closed-loop management process is a management process for realizing the SLS target of the second managed object
  • the second closed-loop management process is managed by the second network management production entity
  • the second managed object is the resource or service managed by the second closed-loop management process .
  • the transceiver module 1001 is configured to receive the first message from the network management consumption entity.
  • the first message includes first management policy information
  • the first management policy information is the management policy information corresponding to the first closed-loop management process, there is an association relationship between the first closed-loop management process and at least one second closed-loop management process
  • the second The management policy information corresponding to the closed-loop management process is the second management policy information
  • the first management policy information and at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process
  • the first management policy information includes one or more first management policies.
  • the processing module 1002 is configured to execute one or more first management policies in the first management policy information.
  • the network management apparatus 1000 may further include a storage module (not shown in FIG. 10 ), where programs or instructions are stored in the storage module.
  • the processing module 1002 executes the program or instruction
  • the network management apparatus 1000 can execute the function of the first network management production entity in the network management method shown in FIGS. 3-5 .
  • the network management device 1000 may be the first network management production entity, or a chip (system) or other components or components that may be configured in the first network management production entity, which is not limited in this application.
  • the network management device 1000 shown in FIG. 10 can be applied to the network management system shown in FIG. 1 and FIG.
  • the second network manages the functions of the production entities.
  • the network management device 1000 is used to manage the second closed-loop management process
  • the second closed-loop management process is a management process for realizing the SLS target of the second managed object
  • the second managed object is the resource or service managed by the second closed-loop management process
  • the first closed-loop management process is managed by the first network management and production entity.
  • the first closed-loop management process is a management process for realizing the SLS target of the first managed object.
  • the first managed object is the resource or service managed by the first closed-loop management process. .
  • the transceiver module 1001 is configured to receive the first message from the network management consumption entity.
  • the first message includes the second management policy information
  • the second management policy information is the management policy information corresponding to the second closed-loop management process, there is an association relationship between the second closed-loop management process and at least one first closed-loop management process, and the first
  • the management policy information corresponding to the closed-loop management process is the first management policy information
  • the first management policy information and at least one second management policy information are used to achieve the guarantee goal of the first closed-loop management process and the guarantee goal of at least one second closed-loop management process
  • the second management policy information includes one or more second management policies.
  • the processing module 1002 is configured to execute one or more second management policies in the second management policy information.
  • the network management apparatus 1000 may further include a storage module (not shown in FIG. 10 ), where programs or instructions are stored in the storage module.
  • the processing module 1002 executes the program or instruction
  • the network management device 1000 can execute the function of the second network management production entity in the network management method shown in FIGS. 3-5 .
  • the network management device 1000 may be the second network management production entity, or may be a chip (system) or other components or components that may be configured in the second network management production entity, which is not limited in this application.
  • the network management device 1000 shown in FIG. 10 can be applied to the network management system shown in FIG. 1 and FIG. 2 to execute the network management methods shown in FIGS. 3-5
  • the network manages the functions of the consuming entities.
  • the processing module 1002 is configured to determine N pieces of management strategy information according to the association relationship information and the guarantee objectives of the N closed-loop management processes.
  • the relationship information includes the relationship between N closed-loop management processes, N is an integer greater than 1, the closed-loop management process is a management process to achieve the SLS target of the managed object, and the managed object is the resource managed by the closed-loop management process Or business, N pieces of management strategy information are used to realize the guarantee goal of N closed-loop management processes, N closed-loop management processes correspond to N managed objects one by one, and one piece of management strategy information includes one or more management strategies.
  • a transceiver module 1001 configured to send a first message to at least two network management and production entities.
  • the first message includes management policy information
  • the network management production entity is used to manage the closed-loop management process.
  • the network management apparatus 1000 may further include a storage module (not shown in FIG. 10 ), where programs or instructions are stored in the storage module.
  • the processing module 1002 executes the program or instruction
  • the network management device 1000 can execute the function of the network management consumption entity in the network management methods shown in FIGS. 2-5 .
  • the network management device 1000 may be a network management consuming entity, or a chip (system) or other components or components that may be configured in the network management consuming entity, which is not limited in this application.
  • the network management device 1000 shown in FIG. 10 can be applied to the network management system shown in FIG. 1 and FIG. NSMS consumption entity, NSMS production entity, NSSMS production entity, management service database entity, or M/A/D/E management production entity, can also be applied to network management production entity, network management consumption entity, NSMS consumption entity, NSMS production entity Entity, NSSMS production entity, management service database entity, or M/A/D/E management production entity function. All relevant content of the steps involved in the above method embodiments can be referred to the function descriptions of the corresponding functional modules, and will not be repeated here.
  • An embodiment of the present application provides a network management system.
  • the network management system includes: at least two network management production entities and network management consumption entities.
  • the at least two network management production entities may include a first network management production entity and at least one second network management production entity, where the first network management production entity is configured to perform the actions of the first network management production entity in the foregoing method embodiments,
  • the second network management production entity is used to execute the actions of the second network management production entity in the foregoing method embodiments.
  • the network management consuming entity is used to execute the actions of the network management consuming entity in the above method embodiments, and the specific execution method and process may refer to the above method embodiments, which will not be repeated here.
  • An embodiment of the present application provides a chip system, and the chip system includes a logic circuit and an input/output port.
  • the logic circuit can be used to implement the processing function involved in the network management method provided by the embodiment of the present application
  • the input/output port can be used for the sending and receiving function involved in the network management method provided in the embodiment of the present application.
  • the input port can be used to realize the receiving function involved in the network management method provided by the embodiment of the present application
  • the output port can be used to realize the sending function involved in the network management method provided in the embodiment of the present application.
  • the processor in the network management device 900 may be used to perform, for example but not limited to, baseband related processing, and the transceiver in the network management device 900 may be used to perform, for example but not limited to, radio frequency transceiving.
  • the above-mentioned devices may be respectively arranged on independent chips, or at least partly or all of them may be arranged on the same chip.
  • processors can be further divided into analog baseband processors and digital baseband processors.
  • the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be set on an independent chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip.
  • a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) integrated on the same chip.
  • application processors such as but not limited to graphics processors, multimedia processors, etc.
  • Such a chip can be called a system chip (system on chip). Whether each device is independently arranged on different chips or integrated and arranged on one or more chips often depends on the specific needs of product design.
  • the embodiment of the present invention does not limit the specific implementation forms of the foregoing devices.
  • the chip system further includes a memory, where the memory is used to store program instructions and data for implementing functions involved in the network management method provided by the embodiments of the present application.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • An embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium includes a computer program or an instruction, and when the computer program or instruction is run on a computer, the network management method provided by the embodiment of the present application is executed.
  • An embodiment of the present application provides a computer program product, and the computer program product includes: a computer program or an instruction.
  • the computer program or instruction When the computer program or instruction is run on a computer, the network management method provided in the embodiment of the present application is executed.
  • the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory Access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the above-mentioned embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or other arbitrary combinations.
  • the above-described embodiments may be implemented in whole or in part in the form of computer program products.
  • the computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center by wired (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may 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 includes one or more sets of available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • At least one means one or more, and “multiple” means two or more.
  • At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Abstract

本申请提供一种网络管理方法及装置，能够实现网络切片和/或网络切片子网的服务等级规范SLS目标。该方法包括：第一网络管理生产实体接收第一管理策略信息，并执行第一管理策略信息中的第一管理策略。第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程存在关联关系，第二闭环管理过程对应第二管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第一被管理对象为第一闭环管理过程所管理的资源或业务，第一闭环管理过程和第二闭环管理过程分别是实现第一被管理对象和第二被管理对象的SLS目标的管理过程。

Description

网络管理方法及装置
本申请要求于2021年09月30日提交国家知识产权局、申请号为202111163413.8、申请名称为“网络管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种网络管理方法及装置。
背景技术
服务等级规范(service level specification，SLS)保障闭环(closed loop SLS assurance，COSLA)(也可称为闭环管理过程)可用于监控闭环保障目标(assurance goals)完成状况、和资源利用情况，可以调整与网络切片(network slice)或网络切片子网(network slice subnet)关联的资源，以满足一个或多个闭环保障目标。
网络切片是一种跨域网络，其SLS保障目标需要通过多个闭环管理过程完成。结合图1，通过部署在第三代合作伙伴计划(3rd generation partnership project，3GPP)跨域(cross domain)级的COSLA提供端到端的网络切片的SLS保障，保证网络切片的业务体验；通过部署在无线接入网(radio access networ，RAN)域的COSLA提供RAN域的网络切片子网的SLS保障；通过部署在核心网(core network，CN)域的COSLA提供CN域的网络切片子网的SLS保障,COSLA可以包括监控、分析、决策、执行等管理服务(management service(s)，MnS(s))。
但是，对于具体如何实现网络切片和/或网络切片子网的SLS目标，业界尚未给出相应的技术方案。
发明内容
本申请提供一种网络管理方法及装置，能够实现网络切片和/或网络切片子网的SLS目标。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种网络管理方法。该网络管理方法可应用于第一网络管理生产实体，第一网络管理生产实体用于管理第一闭环管理过程，第一闭环管理过程是实现第一被管理对象的SLS目标的管理过程，第一被管理对象为第一闭环管理过程所管理的资源或业务，第二闭环管理过程是实现第二被管理对象的服务等级规范SLS目标的管理过程，第二闭环管理过程由第二网络管理生产实体管理，第二被管理对象为第二闭环管理过程所管理的资源或业务。
该网络管理方法包括：接收来自网络管理消费实体的第一消息,执行第一管理策略信息中的一个或多个第一管理策略。其中，第一消息包括第一管理策略信息，第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应的管理策略信息为第二管理策略信息， 第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第一管理策略信息包括一个或多个第一管理策略。
基于第一方面提供的网络管理方法，第一网络管理生产实体接收第一管理策略信息，并执行第一管理策略信息中的一个或多个第一管理策略。该第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应的管理策略信息为第二管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第一被管理对象为第一闭环管理过程所管理的资源或业务，第一闭环管理过程是实现第一被管理对象的SLS目标的管理过程。如此，第一网络管理生产实体能够实现第一被管理对象(例如网络切片和/或网络切片子网)的SLS目标。
在一种可能的设计方式中，第一管理策略信息可以包括一个或多个第一动作指示信息，第一动作指示信息可用于指示第一网络管理生产实体设置第一闭环管理过程对应的第一被管理对象的配置信息。如此，网络管理生产者可以执行一个或多个第一动作指示信息所指示的操作，从而可以使闭环管理过程的性能满足保障目标。
在一种可能的设计方式中，第一管理策略信息还可以包括：一个或多个条件信息、和/或一个或多个事件信息。其中，一个条件信息对应至少一个第一动作指示信息，一个事件信息对应至少一个第一动作指示信息。也就是说，在满足一个条件信息和/或事件信息的情况下，网络管理生产者可以执行一个或多个第一动作指示信息所指示的操作，从而可以使第一闭环管理过程满足保障目标。
可选地，第一管理策略信息中的条件信息可以包括：第一闭环管理过程对应的第一被管理对象的性能与性能阈值的关系。事件信息可以包括如下一项或多项：第一闭环管理过程对应的第一被管理对象对应的通知事件、和/或第一闭环管理过程对应的第一被管理对象以外的被管理对象对应的通知事件、网络管理生产实体生成的通知事件、本网络管理生产实体以外的网络管理生产实体生成的通知事件。
在一种可能的设计方式中，上述执行第一管理策略信息中的一个或多个第一管理策略，可以包括：根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。如此，从而可以保障第一闭环管理过程对应的保障目标。
在一种可能的设计方式中，上述执行第一管理策略信息中的一个或多个第一管理策略，可以包括：在满足条件信息、和/或事件信息的情况下，根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。
在一种可能的设计方式中，接收第一消息的实体为第一网络管理生产实体，与第一闭环管理过程对应的管理对象为第一被管理对象，用于管理第二闭环管理过程的实体为第二网络管理生产实体，第一消息还可以包括如下一项或多项：第二网络管理生产实体的标识、第二闭环管理过程的标识、和第一闭环管理过程的保障目标。
如此，多个网络管理生产实体(例如第一网络管理生产实体、第二网络管理生产实体等)之间不仅可以根据各自的管理策略信息(例如第一网络管理生产实体对应第一管理策略信息、第二网络管理生产实体对应第二管理策略信息等)实现各自的闭环管理过程的保障目标，还可以进一步根据接收的第一消息协商各自的闭环管理过程的保障目标。
可选地，第二网络管理生产实体可执行与第一网络管理生产实体类似的功能，例如，第二网络管理生产实体接收来自网络管理消费实体的第二管理策略信息,执行第二管理策略信息中的一个或多个第二管理策略。第二管理策略信息的实现方式与第一管理策略信息的具体实现方式类似，主要区别在于将第一闭环管理过程替换为第二闭环管理过程。例如，第二管理策略信息可以包括一个或多个第一动作指示信息，第一动作指示信息可用于指示网络管理生产实体设置第二闭环管理过程对应的第二被管理对象的配置信息，具体可参照上述第一管理策略信息的实现方式，不一一赘述。
在一种可能的设计方式中，第一管理策略信息还可以包括一个或多个第一子动作指示信息，第一子动作指示信息可用于指示第一网络管理生产实体向第二网络管理生产实体发送第一通知信息和/或第一运行结果，上述执行第一管理策略信息中的一个或多个第一管理策略，可以包括：根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息。其中，第一协作消息可以包括第一通知信息和/或第一运行结果，第一通知信息可以包括网络管理消费实体期望第二网络管理生产实体采用的第二闭环管理过程的保障目标，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。如此，第一网络管理生产实体可实现与第二网络管理生产实体进行协作操作，从而满足闭环管理过程对应的保障目标。
可选地，与第一管理策略信息类似，第二管理策略信息还可以包括一个或多个第一子动作指示信息，第一子动作指示信息可用于指示第二网络管理生产实体向第一网络管理生产实体发送第二通知信息和/或第二运行结果。第二网络管理生产实体可以根据第一网络管理生产实体的标识和第一子动作指示信息，向第一网络管理生产实体发送第二协作消息。
在一种可能的设计方式中，第一方面提供的网络管理方法，还可以包括：向网络管理消费实体发送第二消息。其中，第二消息可以包括第一运行结果和/或第一修改请求信息，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的，第一修改请求信息可用于请求修改第一管理策略信息、和/或第一闭环管理过程的保障目标。如此，可以使网络管理消费实体根据第一运行结果和/或修改请求，调整第一闭环管理过程的管理策略信息和/或保障目标。
在一种可能的设计方式中，第一修改请求信息可以是第一网络管理生产实体根据第二通知信息、第二运行结果、和/或自身的第一运行结果确定的。其中，第二通知信息可以包括网络管理消费实体期望第一网络管理生产实体采用的第一闭环管理过程的保障目标，第二运行结果可以是第二网络管理生产实体根据第一动作指示信息获得的，或者，第二运行结果可以是第二网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
如此，第一网络管理生产实体可以根据网络管理消费实体向期望其采用的保障目标、第二网络管理生产实体的第二运行结果、和/或自身的第一运行结果，确定是否请求修改第一闭环管理过程的保障目标和/或管理策略信息，还可以确定期望的保障目标和/或管理策略信息。
在一种可能的设计方式中，第一方面提供的网络管理方法，还可以包括：接收来 自第二网络管理生产实体的第二协作消息。其中，第二协作消息可以包括第二通知信息和/或第二运行结果。如此，第二网络管理生产实体可与第一网络管理生产实体进行协作操作，从而使闭环管理过程对应的性能满足保障目标。
在一种可能的设计方式中，第一方面提供的网络管理方法，还可以包括：接收来自网络管理消费实体的新的第一管理策略信息和/或第一闭环管理过程的新的保障目标。如此，第一网络管理生产实体可以进一步根据新的管理策略信息和/或新的保障目标实现第一被管理对象的SLS目标。
在一种可能的设计方式中，第一运行结果可以包括如下一项或多项：第一性能结果、第一性能结果对应的第一管理策略信息的标识、第一性能结果对应的条件信息、第一性能结果对应的事件信息、第一性能结果对应的第一动作指示信息。其中，第一性能结果可以包括第一被管理对象的性能的结果。
在一种可能的设计方式中，第一闭环管理过程的数量可以为一个或多个。可选地，第二闭环管理过程的数量可以为一个或多个。
在一种可能的设计方式中，关联关系可以包括连接关系、或包含关系、或共享关系。
需要说明的是，第二网络管理生产实体可执行与第一方面中所示的方法中第一网络管理生产实体类似的功能，主要区别在于将第一闭环管理过程替换为第二闭环管理过程、将第一网络管理生产实体替换为第二网络管理生产实体，此处不再赘述。
第二方面，提供一种网络管理方法。该网络管理方法应用于网络管理消费实体，包括：根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息,向至少两个网络管理生产实体发送第一消息。其中，关联关系信息包括N个闭环管理过程之间的关联关系，N为大于1的整数，闭环管理过程是实现被管理对象的服务等级规范SLS目标的管理过程，被管理对象为闭环管理过程所管理的资源或业务，N个管理策略信息用于实现N个闭环管理过程的保障目标，N个闭环管理过程与N个被管理对象一一对应。第一消息包括管理策略信息，网络管理生产实体用于管理闭环管理过程，管理策略信息包括一个或多个管理策略。
可选地，N个管理策略信息之间的主要区别在于N个管理策略信息分别对应的闭环管理过程不同，例如管理策略信息1对应闭环管理过程1，管理策略信息2对应闭环管理过程2。
在一种可能的设计方式中，管理策略信息可以包括一个或多个第一动作指示信息，第一动作指示信息可用于指示网络管理生产实体设置闭环管理过程对应的被管理对象的配置信息。
在一种可能的设计方式中，管理策略信息还可以包括：一个或多个条件信息、和/或一个或多个事件信息。其中，一个条件信息对应至少一个第一动作指示信息，一个事件信息对应至少一个第一动作指示信息。
可选地，条件信息可以包括：闭环管理过程对应的被管理对象对应的时延阈值、和/或闭环管理过程对应的被管理对象对应的吞吐量阈值。事件信息可以包括如下一项或多项：闭环管理过程对应的被管理对象对应的通知事件、和/或闭环管理过程对应的被管理对象以外的被管理对象对应的通知事件、网络管理生产实体生成的通知事件、网络管理生产实体以外的网络管理生产实体生成的通知事件。
在一种可能的设计方式中，接收第一消息的实体为第一网络管理生产实体，第一网络管理生产实体对应的闭环管理过程为第一闭环管理过程，与第一闭环管理过程对应的管理对象为第一被管理对象，与第一闭环管理过程存在关联关系的闭环管理过程为第二闭环管理过程，用于管理第二闭环管理过程的实体为第二网络管理生产实体，第一消息还可以包括如下一项或多项：第二网络管理生产实体的标识、第二闭环管理过程的标识、和第一闭环管理过程的保障目标。
在一种可能的设计方式中，管理策略信息还可以包括一个或多个第一子动作指示信息，第一子动作指示信息可用于指示第一网络管理生产实体向第二网络管理生产实体发送第一通知信息和/或第一运行结果，第一通知信息可以包括网络管理消费实体期望第二网络管理生产实体采用的第二闭环管理过程的保障目标，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
在一种可能的设计方式中，第二方面提供的网络管理方法，还可以包括：接收来自网络管理生产实体的第二消息。其中，第二消息可以包括第一运行结果和/或第一修改请求信息，第一运行结果可以是网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的，第一修改请求信息可用于请求修改管理策略信息、和/或闭环管理过程的保障目标。
在一种可能的设计方式中，第二方面提供的网络管理方法，还可以包括：根据至少一个网络管理生产实体的第一运行结果和/或至少一个网络管理生产实体的第一修改请求信息，确定新的管理策略信息和/或闭环管理过程的新的保障目标。
在一种可能的设计方式中，第二方面提供的网络管理方法，还可以包括：向网络管理生产实体发送新的管理策略信息和/或闭环管理过程的新的保障目标。
在一种可能的设计方式中，N个闭环管理过程的保障目标可以是网络管理消费实体根据N个被管理对象的需求信息确定的。
在一种可能的设计方式中，关联关系信息可以是网络管理消费实体根据N个闭环管理过程分别对应的被管理对象之间的关联关系确定的。
在一种可能的设计方式中，网络管理生产实体管理的闭环管理过程的数量可以为一个或多个。
在一种可能的设计方式中，关联关系可以包括连接关系、或包含关系、或共享关系。
此外，第二方面所述的网络管理方法的技术效果可以参考第一方面所述的网络管理方法的技术效果，此处不再赘述。
第三方面，提供一种网络管理装置。网络管理装置用于管理第一闭环管理过程，第一闭环管理过程是实现第一被管理对象的SLS目标的管理过程，第一被管理对象为第一闭环管理过程所管理的资源或业务，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，第二闭环管理过程由第二网络管理生产实体管理，第二被管理对象为第二闭环管理过程所管理的资源或业务。
该网络管理装置包括：收发模块和处理模块。其中，收发模块，用于接收来自网络管理消费实体的第一消息。处理模块，用于执行第一管理策略信息中的一个或多个第一管理 策略。其中，第一消息包括第一管理策略信息，第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应的管理策略信息为第二管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标,第一管理策略信息包括一个或多个第一管理策略。
在一种可能的设计方式中，第一管理策略信息可以包括一个或多个第一动作指示信息，第一动作指示信息可用于指示网络管理装置设置第一闭环管理过程对应的第一被管理对象的配置信息。
在一种可能的设计方式中，第一管理策略信息还可以包括：一个或多个条件信息、和/或一个或多个事件信息。其中，一个条件信息对应至少一个第一动作指示信息，一个事件信息对应至少一个第一动作指示信息。
可选地，条件信息可以包括：第一闭环管理过程对应的第一被管理对象的性能与性能阈值的关系。事件信息可以包括如下一项或多项：第一闭环管理过程对应的第一被管理对象对应的通知事件、和/或第一闭环管理过程对应的第一被管理对象以外的被管理对象对应的通知事件、网络管理装置生成的通知事件、网络管理装置以外的第一网络管理装置生成的通知事件。
在一种可能的设计方式中，处理模块，还用于根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。
在一种可能的设计方式中，在满足条件信息、和/或事件信息的情况下，处理模块，还用于根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。
在一种可能的设计方式中，接收第一消息的实体为第一网络管理装置，与第一闭环管理过程对应的管理对象为第一被管理对象，用于管理第二闭环管理过程的实体为第二网络管理生产实体，第一消息还可以包括如下一项或多项：第二网络管理生产实体的标识、第二闭环管理过程的标识、和第一闭环管理过程的保障目标。
在一种可能的设计方式中，第一管理策略信息还可以包括一个或多个第一子动作指示信息，第一子动作指示信息可用于指示第一网络管理装置向第二网络管理生产实体发送第一通知信息和/或第一运行结果，收发模块，还用于根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息。其中，第一协作消息可以包括第一通知信息和/或第一运行结果，第一通知信息可以包括网络管理消费实体期望第二网络管理生产实体采用的第二闭环管理过程的保障目标，第一运行结果可以是第一网络管理装置根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理装置根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
在一种可能的设计方式中，收发模块，还用于向网络管理消费实体发送第二消息。其中，第二消息可以包括第一运行结果和/或第一修改请求信息，第一运行结果可以是第一网络管理装置根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理装置根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的，第一修改请求信息可用于请求修改第一管理策略信息、和/或第一闭环管理过程的保障目标。
在一种可能的设计方式中，第一修改请求信息可以是第一网络管理装置根据第二通知信息和/或第二运行结果确定的。其中，第二通知信息可以包括网络管理消费实体期望第 一网络管理装置采用的第一闭环管理过程的保障目标，第二运行结果可以是第二网络管理生产实体根据第一动作指示信息获得的，或者，第二运行结果可以是第二网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
在一种可能的设计方式中，收发模块，还用于接收来自第二网络管理生产实体的第二协作消息。其中，第二协作消息可以包括第二通知信息和/或第二运行结果。
在一种可能的设计方式中，收发模块，还用于接收来自网络管理消费实体的新的第一管理策略信息和/或第一闭环管理过程的新的保障目标。
在一种可能的设计方式中，第一运行结果可以包括如下一项或多项：第一性能结果、第一性能结果对应的第一管理策略信息的标识、第一性能结果对应的条件信息、第一性能结果对应的事件信息、第一性能结果对应的第一动作指示信息。其中，第一性能结果可以包括第一被管理对象的性能的结果。
在一种可能的设计方式中，网络管理装置管理的闭环管理过程的数量可以为一个或多个。
在一种可能的设计方式中，关联关系可以包括连接关系、或包含关系、或共享关系。
需要说明的是，第三方面所述的收发模块可以包括接收模块和发送模块。其中，接收模块用于接收来自网络管理消费实体、和/或其他网络管理生产实体的数据和/或信令；发送模块用于向网络管理消费实体、和/或其他网络管理生产实体发送数据和/或信令。本申请对于收发模块的具体实现方式，不做具体限定。
可选地，第三方面所述的网络管理装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得第三方面所述的网络管理装置可以执行第一方面所述的方法。
需要说明的是，第三方面所述的网络管理装置可以是网络管理生产实体，也可以是可设置于网络管理生产实体的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，第三方面所述的网络管理装置的技术效果可以参考第一方面所述的网络管理方法的技术效果，此处不再赘述。
第四方面，提供一种网络管理装置。该网络管理装置包括：收发模块和处理模块。其中，处理模块，用于根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息。收发模块，用于向至少两个网络管理生产实体发送第一消息。其中，关联关系信息包括N个闭环管理过程之间的关联关系，N为大于1的整数，闭环管理过程是实现被管理对象的SLS目标的管理过程，被管理对象为闭环管理过程所管理的资源或业务，N个管理策略信息用于实现N个闭环管理过程的保障目标，N个闭环管理过程与N个被管理对象一一对应。第一消息包括管理策略信息，网络管理生产实体用于管理闭环管理过程，管理策略信息包括一个或多个管理策略。
在一种可能的设计方式中，管理策略信息可以包括一个或多个第一动作指示信息，第一动作指示信息可用于指示网络管理生产实体设置闭环管理过程对应的被管理对象的配置信息。
在一种可能的设计方式中，管理策略信息还可以包括：一个或多个条件信息、和/或一个或多个事件信息。其中，一个条件信息对应至少一个第一动作指示信息，一个事件信 息对应至少一个第一动作指示信息。
可选地，条件信息可以包括：闭环管理过程对应的被管理对象对应的时延阈值、和/或闭环管理过程对应的被管理对象对应的吞吐量阈值。事件信息可以包括如下一项或多项：闭环管理过程对应的被管理对象对应的通知事件、和/或闭环管理过程对应的被管理对象以外的被管理对象对应的通知事件、网络管理生产实体生成的通知事件、网络管理生产实体以外的网络管理生产实体生成的通知事件。
在一种可能的设计方式中，接收第一消息的实体为第一网络管理生产实体，第一网络管理生产实体对应的闭环管理过程为第一闭环管理过程，与第一闭环管理过程对应的管理对象为第一被管理对象，与第一闭环管理过程存在关联关系的闭环管理过程为第二闭环管理过程，用于管理第二闭环管理过程的实体为第二网络管理生产实体，第一消息还可以包括如下一项或多项：第二网络管理生产实体的标识、第二闭环管理过程的标识、和第一闭环管理过程的保障目标。
在一种可能的设计方式中，管理策略信息还可以包括一个或多个第一子动作指示信息，第一子动作指示信息可用于指示第一网络管理生产实体向第二网络管理生产实体发送第一通知信息和/或第一运行结果，第一通知信息可以包括网络管理装置期望第二网络管理生产实体采用的第二闭环管理过程的保障目标，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
在一种可能的设计方式中，收发模块，还用于接收来自网络管理生产实体的第二消息。其中，第二消息可以包括第一运行结果和/或第一修改请求信息，第一运行结果可以是网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的，第一修改请求信息可用于请求修改管理策略信息、和/或闭环管理过程的保障目标。
在一种可能的设计方式中，处理模块，还用于根据至少一个网络管理生产实体的第一运行结果和/或至少一个网络管理生产实体的第一修改请求信息，确定新的管理策略信息和/或闭环管理过程的新的保障目标。
在一种可能的设计方式中，收发模块，还用于向网络管理生产实体发送新的管理策略信息和/或闭环管理过程的新的保障目标。
在一种可能的设计方式中，N个闭环管理过程的保障目标可以是网络管理装置根据N个被管理对象的需求信息确定的。
在一种可能的设计方式中，关联关系信息可以是网络管理装置根据N个闭环管理过程分别对应的被管理对象之间的关联关系确定的。
在一种可能的设计方式中，网络管理生产实体管理的闭环管理过程的数量可以为一个或多个。
在一种可能的设计方式中，关联关系可以包括连接关系、或包含关系、或共享关系。
需要说明的是，第四方面所述的收发模块可以包括接收模块和发送模块。其中，接收模块用于接收来自网络管理生产实体的数据和/或信令；发送模块用于向网络管理生产实体发送数据和/或信令。本申请对于收发模块的具体实现方式，不做具体限定。
可选地，第四方面所述的网络管理装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得第四方面所述的网络管理装置可以执行第二方面所述的方法。
需要说明的是，第四方面所述的网络管理装置可以是网络管理消费实体，也可以是可设置于网络管理消费实体的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，第四方面所述的网络管理装置的技术效果可以参考第二方面所述的网络管理方法的技术效果，此处不再赘述。
第五方面，提供一种网络管理装置。该网络管理装置包括：处理器，该处理器与存储器耦合，存储器用于存储计算机程序。
处理器用于执行存储器中存储的计算机程序，以使得如第一方面至第二方面中任一种可能的实现方式所述的网络管理方法被执行。
在一种可能的设计中，第五方面所述的网络管理装置还可以包括收发器。该收发器可以为收发电路或输入/输出端口。所述收发器可以用于该网络管理装置与其他设备通信。
需要说明的是，输入端口可用于实现第一方面至第二方面所涉及的接收功能，输出端口可用于实现第一方面至第二方面所涉及的发送功能。
在本申请中，第五方面所述的网络管理装置可以为网络管理消费实体、或网络管理生产实体，或者设置于网络管理消费实体、或网络管理生产实体内部的芯片或芯片系统。
此外，第五方面所述的网络管理装置的技术效果可以参考第一方面至第二方面中任一种实现方式所述的网络管理方法的技术效果，此处不再赘述。
第六方面，提供一种网络管理系统。该网络管理系统包括网络管理消费实体、第一网络管理生产实体、和至少一个第二网络管理生产实体，第一网络管理生产实体用于管理第一闭环管理过程，第二网络管理生产实体用于管理第二闭环管理过程，第一闭环管理过程是实现第一被管理对象的服务等级规范SLS目标的管理过程，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，第一被管理对象为第一闭环管理过程所管理的资源或业务，第二被管理对象为第二闭环管理过程所管理的资源或业务；其中，
网络管理消费实体，用于根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息；其中，关联关系信息包括N个闭环管理过程之间的关联关系，N为大于1的整数，N个管理策略信息用于实现N个闭环管理过程的保障目标，N个闭环管理过程包括第一闭环管理过程和至少一个第二闭环管理过程，N个管理策略信息包括第一管理策略信息和至少一个第二管理策略信息，第一管理策略信息包括一个或多个第一管理策略，第二管理策略信息包括一个或多个第二管理策略；
网络管理消费实体，还用于向第一网络管理生产实体发送第一管理策略信息，向至少一个第二网络管理生产实体发送至少一个第二管理策略信息；
第一网络管理生产实体，用于接收来自网络管理消费实体的第一管理策略信息；
第一网络管理生产实体，还用于执行第一管理策略信息中的一个或多个第一管理策略；
第二网络管理生产实体，用于接收来自网络管理消费实体的第二管理策略信息；
第二网络管理生产实体，还用于执行第二管理策略信息中的一个或多个第二管理策略。
可选地，网络管理消费实体可用于实现上述如第二方面所述方法，第一网络管理生 产实体可用于实现上述如第一方面所述方法，第二网络管理生产实体可用于实现上述与第一方面所述方法类似的方法，
或者，该网络管理系统包括至少两个如第三方面所述的网络管理装置和如第四方面所述的网络管理装置。
可选地，网络管理消费实体的数量可以为一个或多个。
第七方面，提供了一种芯片系统，该芯片系统包括逻辑电路和输入/输出端口。其中，逻辑电路用于实现第一方面至第二方面所涉及的处理功能，输入/输出端口用于实现第一方面至第二方面所涉及的收发功能。具体地，输入端口可用于实现第一方面至第二方面所涉及的接收功能，输出端口可用于实现第一方面至第二方面所涉及的发送功能。
在一种可能的设计中，该芯片系统还包括存储器，该存储器用于存储实现第一方面至第二方面所涉及功能的程序指令和数据。
该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第八方面，提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序或指令；当该计算机程序或指令在计算机上运行时，使得第一方面至第二方面中任意一种可能的实现方式所述的网络管理方法被执行。
第九方面，提供一种计算机程序产品，包括计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得第一方面至第二方面中任意一种可能的实现方式所述的网络管理方法被执行。
附图说明
图1为本申请实施例提供的一种网络管理系统的架构示意图；
图2为本申请实施例提供的另一种网络管理系统的架构示意图；
图3为本申请实施例提供的一种网络管理方法的流程示意图；
图4为本申请实施例提供的一种被管理对象的示意图；
图5为本申请实施例提供的另一种被管理对象的示意图；
图6为本申请实施例提供的一种网络切片的管理架构的示意图；
图7为本申请实施例提供的另一种网络管理方法的流程示意图；
图8为本申请实施例提供的又一种网络管理方法的流程示意图；
图9为本申请实施例提供的一种网络管理装置的结构示意图；
图10为本申请实施例提供的另一种网络管理装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种网络管理系统，例如无线保真(wireless fidelity，WiFi)系统，车到任意物体(vehicle to everything，V2X)通信系统、设备间(device-to-device，D2D)通信系统、车联网通信系统、第4代(4th generation，4G)移动通信系统，如长期演进(long term evolution，LTE)系统、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)移动通信系统，如新空口(new radio，NR)系统，以及未来的通信系统，如第六代(6th generation，6G)移动通信系统等。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。 应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例地”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为便于理解本申请实施例，首先以图2中示出的网络管理系统为例详细说明适用于本申请实施例的网络管理系统。示例性地，图2为本申请实施例提供的闭环管理方法所适用的一种网络管理系统的架构示意图。
如图2所示，该网络管理系统包括网络管理消费实体和至少两个网络管理生产实体，例如，网络管理生产实体1和网络管理生产实体2。可选地，网络管理消费实体的数量可以为一个或多个。
其中，上述网络管理消费实体用于与网络管理生产实体进行交互，可指示网络管理生产实体对闭环管理过程进行管理。示例性地，网络管理消费实体可用于确定闭环管理过程对应的管理策略信息，并发送给闭环管理过程对应的网络管理生产实体，以使网络管理生产实体根据管理策略信息管理闭环管理过程，具体可参照下述图3所示的方法。
需要说明的是，网络管理消费实体也可称为闭环(close loop，CL)管理消费实体、闭环管理消费者、闭环管理服务消费者、网络管理消费者、或3GPP管理框架消费者(如图1所示)，本申请以网络管理消费实体为例进行阐述。其中，3GPP管理框架消费者可以包括业务支撑系统(business support system，BSS)、垂直行业运维技术(operational technology，OT)系统(vertical OT system)等。网络管理消费实体可以是物理设备，网络管理消费实体的功能可以部署在物理设备上，例如，网络管理消费实体可以是部署在物理设备内的功能模块。
上述网络管理生产实体用于与网络管理消费实体和/或其他网络管理生产实体进行交互，可以接收来自网络管理消费实体的管理策略信息，并根据管理策略信息对闭环管理过程进行协调管理，可以与其他网络管理生产实体协作管理闭环管理过程，具体可参照下述图3所示的方法。一个网络管理生产实体可以管理一个或多个闭环管理过程，不同网络管理生产者可以管理不同的闭环管理过程，例如，网络管理生产实体1用于管理闭环管理过程1，网络管理生产实体2用于管理闭环管理过程2。
需要说明的是，网络管理生产实体可以称为闭环管理生产实体、闭环管理生产者、网络管理生产者、或闭环管理服务生产者等,本申请以网络管理生产实体为例进行阐述。网络管理生产实体可以是物理设备，网络管理生产实体的功能可以部署在物理设备上，例如，网络管理生产实体可以是部署在物理设备内的功能模块。
网络管理消费实体与网络管理生产实体、或不同的网络管理生产实体可以集中式部署或分布式部署。以网络管理消费实体和网络管理生产实体为例，网络管理消费实体和网络管理生产实体可以是部署于同一物理设备中的不同硬件模块，还可以是不同物理设备，网 络管理消费实体的功能和网络管理生产实体的功能可以部署在同一物理设备中的不同硬件模块中，还可以部署在不同物理设备中，本申请对此不进行限定。不同的网络管理生产实体的集中式部署或分布式部署与之类似，本申请不再赘述。
可选地，如图2所示，网络管理生产实体可以包括但不限于：监控(monitor，M)管理生产实体、分析(analysis，A)管理生产实体、决策(decision，D)管理生产实体、和执行(execution，E)管理生产实体。其中，监控管理生产实体用于执行监控功能提供监控服务，分析管理生产实体用于执行分析功能提供分析服务，决策管理生产实体用于决策功能提供决策服务，执行管理生产实体用于实现执行功能提供执行服务。网络管理生产实体可以对决策管理生产实体、执行管理生产实体、监控管理生产实体、和分析管理生产实体进行调度，从而支持闭环管理过程。
需要说明的是，决策管理生产实体可以称为决策管理生产者,执行管理生产实体可以称为执行管理生产者，监控管理生产实体可以称为监控管理生产者，分析管理生产实体可以称为分析管理生产者，本申请以决策管理生产实体、执行管理生产实体、监控管理生产实体、和分析管理生产实体为例进行阐述。
与网络管理消费实体和网络管理生产实体类似，决策管理生产实体、执行管理生产实体、监控管理生产实体、和分析管理生产实体可以集中式部署(例如部署于网络管理生产实体)或分布式部署，本申请对此不进行限定。
需要说明的是，监控管理生产实体、分析管理生产实体、决策管理生产实体、和执行管理生产实体可以部署于网络管理生产实体内，或者与网络管理生产实体集中部署于一个物理设备，也可以与网络管理生产实体分别独立部署，并通过管理服务数据库实体(也可称为集成总线)进行通信。
提供服务的功能实体可以称为对应服务的生产者或提供者，消费服务的功能实体可以称为对应服务的消费者，本申请中各种“生产者”同时也可以是“消费者”，使用其他“生产者”提供的服务。
需要说明的是，本申请实施例提供的网络管理方法，可以适用于图2所示的任意两个节点之间，如闭环管理消费实体与闭环管理生产实体之间、至少两个闭环管理生产实体之间，具体实现可以参考下述方法实施例，此处不再赘述。
应理解，图2仅为便于理解而示例的简化示意图，该网络管理系统中还可以包括其他实体，图2中未予以画出。
为了使得本申请实施例更加清楚，以下对与本申请实施例相关的部分内容以及概念作统一介绍。
第一项，网络切片和网络切片子网：
网络切片是指提供特定网络能力和网络属性的逻辑网络。网络切片支持多种差异化的业务类型，例如增强移动宽带(enhanced mobile broadband，eMBB)、超高可靠性低时延通信(ultra-reliable and low latency communications，URLLC)、海量机器类型通信(massive machine type communication，mMTC)等。一个网络切片可以包括多个子网，如无线接入网子网(subnet)、传输网(transport network，TN)子网、核心网子网。
一个网络切片实例(network slice instance，NSI)可以包括无线网的网络切片子网实例(network slice subnet instance，NSSI)、传输网的NSSI和核心网的NSSI。NSSI是由网络 功能(network function，NF)和所需的物理/虚拟资源组成的集合。
其中，NSI可以包括一组网络功能实例和所需资源(如计算、存储和网络资源)，用于组成一个所部署的网络切片。NSI可以是端到端逻辑网络实例，提供特定网络能力和属性，NSI可以由一个或多个NSSI组成。其中，网络功能，可以是网络中的处理功能，可用于定义功能行为和接口。NF可以包括物理网络功能(physical network function，PNF)和虚拟网络功能，物理网络功能可以理解为传统的网元，虚拟网络功能可以为虚拟化网络功能。
在本申请中，端到端逻辑网络可以是终端设备到应用服务器之间的网络，例如可以包括无线接入网、核心网、和/或传输网。
网络切片子网(network slice subnet)可表示一组被管理的功能和所需资源(如计算、存储和网络资源)的管理方面，是由一个或多个NF及其组网形成的网络子网，可以是端到端逻辑网络的一部分，例如无线接入网子网、核心网子网、传输子网。
网络切片子网实例可表示一组被管理功能实例和所使用的资源(如计算、存储和网络资源)的管理方面，NSSI由一个或多个NF及其组网形成，NSSI可组成部分或完整的NSI，NSSI可以为无线网的NSSI、传输网的NSSI、或核心网的NSSI。
第二项，被管理对象：
被管理对象可以为资源或业务。其中，资源可以包括但不限于如下一项或多项：网元(例如，设备、网元相关的资源，如无线频谱、计算资源、存储资源、带宽资源等)、子网、和网络。网络可以为物理网络，也可以是逻辑网络，如网络切片、或网络切片子网。业务可指网络所承载的各种业务，如垂直行业业务(如可编程逻辑控制器(programmable logic controller，PLC)控制、视频监控、远程监控等)、语音、视频等业务。
示例性地，被管理对象可以是以下项目之一：物理网络、物理网络所提供的服务、逻辑网络、逻辑网络所提供的服务、物理网络与逻辑网络的组成部分(如设备、网元)或其提供的服务。具体地，被管理对象可以是以下项目之一：通信服务实例、子网(subnetwork)、网络切片、网络切片子网、NSI、NSSI、通信服务、设备、网元。可选地，相对于网络管理生产实体，被管理对象也可以称为被管理网络、被管理网络实体(managed entity)、被管理逻辑网络(managed logical network)、被管理网络设备等。同理，相对于被管理对象，网络管理生产实体也可以称为管理主体或管理节点(management node)，本申请对此不作具体限定。以下表1列举了网络管理生产实体和相应的被管理对象，对应不同的被管理对象，网络管理生产实体可以有不同的名称。
表1
网络管理生产实体 被管理对象
通信服务网络管理生产实体 通信服务或通信服务实例
网络切片网络管理生产实体 网络切片、NSI
网络切片子网网络管理生产实体 网络切片子网、NSSI
如表1所示，通信服务或者通信服务实例为通信服务网络管理生产实体的被管理对象；网络切片或网络切片实例为网络切片网络管理生产实体的被管理对象；网络切片子网或网络切片子网实例为网络切片子网网络管理生产实体的被管理对象。其中，网络切片子网包 括无线接入网域的网络切片子网、核心网域的网络切片子网、传输域的网络切片子网。
第三项，闭环管理过程：
闭环管理过程可以是实现被管理对象的SLS目标的管理过程。示例性地，闭环管理过程可以包括实现被管理对象的SLS目标所涉及的功能(例如监控功能、分析功能、决策功能、执行功能)、管理服务(例如监控、分析、决策、执行)、方法和过程等。
示例性地，闭环管理过程可以称为SLS保障闭环、或闭环管理服务等，或者闭环管理过程可以简称为闭环。
结合图1，部署在跨域级的闭环管理过程、且提供端到端的网络切片的SLS保障服务的闭环管理过程可以称为网络切片级闭环管理过程，部署在RAN域的闭环管理过程、且提供RAN域的网络切片子网的SLS保障服务的闭环管理过程可以称为网络切片子网级闭环管理过程，部署在CN域的闭环管理过程、且提供CN域的网络切片子网的SLS保障服务的闭环管理过程可以称为网络切片子网级闭环管理过程。
需要说明的是，本申请图3所示的网络管理方法以闭环管理过程进行阐述。
示例性地，图3为本申请实施例提供的一种网络管理方法的流程示意图。该网络管理方法可以适用于图2所示的任意两个节点之间的通信。以一个网络管理生产实体管理一个闭环管理过程为例。
如图3所示，该网络管理方法包括如下步骤：
S301，网络管理消费实体根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息。
示例性地，关联关系信息可以包括N个闭环管理过程之间的关联关系，N为大于1的整数，N个闭环管理过程与N个被管理对象一一对应。
可选地，N个闭环管理过程之间的关联关系可以包括连接关系、或包含关系、或共享关系等。
可选地，N个闭环管理过程可以是由N个不同的网络管理生产实体管理的。
例如，N个闭环管理过程可以包括第一闭环管理过程和至少一个第二闭环管理过程，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第一闭环管理过程由第一网络管理生产实体管理，第二闭环管理过程由第二网络管理生产实体管理。
例如，N个被管理对象可以包括第一被管理对象和至少一个第二被管理对象，第一闭环管理过程对应第一闭环管理过程，第二闭环管理过程对应第二闭环管理过程。
示例性地，闭环管理过程可以是实现被管理对象的SLS目标的管理过程，具体可参照上述第三项中的阐述，此处不再赘述。
例如，第一闭环管理过程可以是实现第一被管理对象的SLS目标的管理过程。
又例如，第二闭环管理过程可以是实现第二被管理对象的SLS目标的管理过程。
示例性地，被管理对象可以为闭环管理过程所管理的资源或业务，具体可参照上述第二项中的阐述，此处不再赘述。
例如，第一被管理对象可以为第一闭环管理过程所管理的资源或业务。
又例如，第二被管理对象可以为第二闭环管理过程所管理的资源或业务。
在一些实施例中，关联关系信息可以是网络管理消费实体根据N个闭环管理过程分别对应的被管理对象之间的关联关系确定的。
图4为本申请实施例提供的一种被管理对象的示意图。
如图4所示，被管理对象包括NSI、NSSI-1、和NSSI-2。NSI为跨域的网络切片，NSSI-1为RAN域1的切片子网，NSSI-2为RAN域2的切片子网，或者，NSSI-1为RAN域的切片子网，NSSI-2为CN域的切片子网。NSI对应闭环管理过程1，NSSI-1对应闭环管理过程2，NSSI-2对应闭环管理过程3。
结合图4，NSI包含NSSI-1和NSSI-2，NSSI-1和NSSI-2连接，则NSI与NSSI-1的关联关系为包含关系，NSI与NSSI-2的关联关系为包含关系，NSSI-1与NSSI-2的关联关系为连接关系。根据NSI、NSSI-1、和NSSI-2之间的关联关系、以及闭环管理过程1至闭环管理过程3与NSI、NSSI-1、和NSSI-2的对应关系，可获得闭环管理过程1至闭环管理过程3之间的关联关系为：闭环管理过程1与闭环管理过程2的关联关系为包含关系，闭环管理过程1与闭环管理过程3的关联关系为包含关系，闭环管理过程2与闭环管理过程3的关联关系为连接关系。
需要说明的是，图4以被管理对象包括NSI、NSSI-1、和NSSI-2为例进行阐述，本申请不对NSSI、和NSI的数量进行限定。
图5为本申请实施例提供的另一种被管理对象的示意图。
如图5所示，被管理对象包括NSI-1、NSI-2、和NSSI。NSI-1和NSI-2为资源共享关系，例如NSI-1和NSI-2共享同一个RAN域的切片子网，NSI-1和NSI-2为两个不同的跨域的网络切片，NSSI为RAN域的切片子网。NSI-1对应闭环管理过程4，NSI-2对应闭环管理过程5，NSSI对应闭环管理过程6。
结合图5，NSI-1和NSI-2连接，NSI-1包含NSSI，NSI-2包含NSSI，则NSI-1与NSI-2的关联关系为共享关系，NSI-1与NSSI的关联关系为包含关系，NSI-2与NSSI的关联关系为包含关系。根据NSI-1、NSI-2、和NSSI之间的关联关系、以及闭环管理过程4至闭环管理过程6与NSI-1、NSI-2、和NSSI的对应关系，可获得闭环管理过程4至闭环管理过程6之间的关联关系为：闭环管理过程4与闭环管理过程5的关联关系为共享关系，闭环管理过程4与闭环管理过程6的关联关系为包含关系，闭环管理过程5与闭环管理过程6的关联关系为包含关系。
可选地，若多个闭环管理过程对应的被管理对象共享部分或全部资源，则多个闭环管理过程的关联关系为共享关系。
对于多个闭环管理过程对应的被管理对象共享部分资源的情况可参照上述对图5的阐述。
对于多个闭环管理过程对应的被管理对象共享全部资源的情况如下，闭环管理过程a用于实现被管理对象a的吞吐量指标要求，闭环管理过程b用于实现被管理对象a的时延指标要求，闭环管理过程a与闭环管理过程b对应同一被管理对象(例如被管理对象a)的不同保障目标，则闭环管理过程a与闭环管理过程b对应同一个被管理对象，同一个被管理对象的资源全部相同，从而闭环管理过程a与闭环管理过程b的关联关系为共享关系。
示例性地，N个管理策略信息可用于实现N个闭环管理过程的保障目标。
结合图4，假设闭环管理过程1对应管理策略信息1，闭环管理过程2对应管理策略信息2，闭环管理过程3对应管理策略信息3，则管理策略信息1至管理策略信息3的结合使用可以实现闭环管理过程1的保障目标至闭环管理过程3的保障目标，或者，管理策 略信息1至管理策略信息3可以分别实现闭环管理过程1的保障目标至闭环管理过程3的保障目标，例如，管理策略信息1可实现闭环管理过程1的保障目标，管理策略信息2可实现闭环管理过程2的保障目标，管理策略信息3可实现闭环管理过程3的保障目标。
可选地，一个管理策略信息可以包括一个或多个管理策略。
例如，N个管理策略信息可以包括第一管理策略信息和至少一个第二管理策略信息。第一管理策略信息可以包括一个或多个第一管理策略，第二管理策略信息可以包括一个或多个第二管理策略。
在一些实施例中，N个闭环管理过程的保障目标可以是网络管理消费实体根据N个被管理对象的需求信息确定的。
可选地，保障目标可以包括业务或网络需求，网络管理消费实体可以根据关联关系信息和N个闭环管理过程的业务或网络需求，确定N个管理策略信息，本申请不对保障目标的名称进行限定。
示例性地，被管理对象的需求信息可以是服务等级协议(service level agreement，SLA)或SLS的属性的子集，例如网络切片业务需求(service profile)和/或网络切片子网性能需求(slice profile)中的全部或部分属性的指标要求。
例如，网络切片业务需求可以包括时延(latency)、网络切片下行吞吐量(dLThptPerSlice)、和网络切片上行吞吐量(uLThptPerSlice)等信息。网络切片子网性能需求可以包括网络切片子网的时延、网络切片子网下行吞吐量(dLThptPerSliceSubnet)、和网络切片子网上行吞吐量(uLThptPerSliceSubnet)等信息。
示例性地，网络管理消费实体可以根据网络切片业务需求中的端到端时延需求，确定网络切片级闭环管理过程的端到端时延，根据网络切片子网性能需求中的RAN域时延需求，确定RAN域网络切片子网级的闭环管理过程的时延，根据网络切片子网性能需求中的CN域时延需求，确定CN域网络切片子网级的闭环管理过程的时延。
结合图4，以时延为例，闭环管理过程1的保障目标可以包括：端到端时延小于第一阈值；闭环管理过程2的保障目标可以包括：RAN域1时延小于第二阈值；闭环管理过程3的保障目标可以包括：RAN域2时延小于第三阈值。其中，第一阈值、第二阈值和第三阈值之间可以相同或不同。
在一种可能的设计方式中，管理策略信息可以包括一个或多个第一动作指示信息。
可选地，第一动作指示信息可用于指示网络管理生产实体设置闭环管理过程对应的被管理对象的配置信息。
例如，配置信息可以包括但不限于如下一项或多项：无线资源配置信息、核心网资源配置信息、参数配置(如切换参数)信息。
示例性地，以资源为例，第一动作指示信息可用于：指示网络管理生产实体为闭环管理过程对应的被管理对象分配资源、指示网络管理生产实体调整(或修改)闭环管理过程对应的被管理对象的资源配置信息、指示网络管理生产实体删除闭环管理过程对应的被管理对象的资源配置信息、指示网络管理生产实体增加闭环管理过程对应的被管理对象的资源配置信息、和/或指示网络管理生产实体修改配置参数。
可选地，一个第一动作指示信息可以称为一个管理策略。
例如，第一管理策略信息中的一个第一动作指示信息可以称为一个第一管理策略。第 二管理策略信息中的一个第一动作指示信息可以称为一个第二管理策略。
需要说明的是，在本申请实施例中，N个管理策略信息的具体实现方式均可参照上述和下述记载的管理策略信息的实现方式，N个管理策略信息之间的主要区别在于N个管理策略信息分别对应的闭环管理过程、被管理对象不同，例如管理策略信息1对应闭环管理过程1和被管理对象1，管理策略信息2对应闭环管理过程2和被管理对象2。
在一些实施例中，管理策略信息可以包括管理策略信息的标识。
在一种可能的设计方式中，管理策略信息还可以包括：一个或多个条件信息、和/或一个或多个事件信息。
可选地，条件信息可以包括：闭环管理过程对应的被管理对象的网络或业务与网络阈值或业务阈值的关系。
例如，被管理对象的网络或业务可以包括但不限于如下一项或多项：时延、和吞吐量。
例如，网络或业务阈值可以包括但不限于如下一项或多项：时延阈值、和吞吐量阈值。
示例性地，条件信息可以包括：被管理对象的时延大于时延阈值、和/或被管理对象的吞吐量小于吞吐量阈值。
可选地，一个条件信息可对应至少一个第一动作指示信息。
可选地，一个条件信息和对应的一个第一动作指示信息可以称为一个管理策略。
例如，第一管理策略信息中的一个条件信息和对应的一个第一动作指示信息可以称为一个第一管理策略。第二管理策略信息中的一个条件信息和对应的一个第一动作指示信息可以称为一个第二管理策略。
也就是说，在满足一个条件信息的情况下，网络管理生产者可以执行一个或多个第一动作指示信息所指示的操作。
可选地，事件信息可以包括如下一项或多项：闭环管理过程对应的被管理对象对应的通知事件、和/或闭环管理过程对应的被管理对象以外的被管理对象对应的通知事件、网络管理生产实体生成的通知事件、本网络管理生产实体以外的网络管理生产实体生成的通知事件。
示例性地，闭环管理过程对应的被管理对象对应的通知事件可以包括：预配置的周期性事件、条件触发事件；闭环管理过程对应的被管理对象以外的被管理对象对应的通知事件可以包括：预配置的周期性事件、条件触发事件；网络管理生产实体生成的通知事件可以包括：预配置的周期性事件、条件触发事件；本网络管理生产实体以外的网络管理生产实体生成的通知事件可以包括：预配置的周期性事件、条件触发事件。
例如，条件触发事件可以包括由条件(如看门狗、或其他机制对应的条件等)触发的事件。
可选地，一个事件信息可对应至少一个第一动作指示信息。
可选地，一个事件信息和对应的一个第一动作指示信息可以称为一个管理策略。
例如，第一管理策略信息中的一个事件信息和对应的一个第一动作指示信息可以称为一个第一管理策略。第二管理策略信息中的一个事件信息和对应的一个第一动作指示信息可以称为一个第二管理策略。
也就是说，在满足一个事件信息的情况下，网络管理生产者可以执行一个或多个第一动作指示信息所指示的操作。
或者，可选地，一个事件信息和一个条件信息可对应至少一个第一动作指示信息。
可选地，一个事件信息、一个条件信息、和对应的一个第一动作指示信息可以称为一个管理策略。
例如，第一管理策略信息中的一个事件信息、一个条件信息、和对应的一个第一动作指示信息可以称为一个第一管理策略。第二管理策略信息中的一个事件信息、一个条件信息、和对应的一个第一动作指示信息可以称为一个第二管理策略。
也就是说，在满足事件信息和条件信息的情况下，网络管理生产者可以执行一个或多个第一动作指示信息所指示的操作。
在一种可能的设计方式中，管理策略信息还可以包括一个或多个第一子动作指示信息。
例如，管理策略信息可以包括；一个或多个第一动作指示信息、和一个或多个第一子动作指示信息。再例如，管理策略信息可以包括；一个或多个第一动作指示信息、一个或多个条件信息、和一个或多个第一子动作指示信息。又例如，管理策略信息可以包括；一个或多个第一动作指示信息、一个或多个事件信息、和一个或多个第一子动作指示信息。又例如，管理策略信息可以包括；一个或多个第一动作指示信息、一个或多个条件信息、一个或多个事件信息、和一个或多个第一子动作指示信息。
可选地，事件信息和/或条件信息可与第一子动作指示信息对应。
也就是说，在满足事件信息和/或条件信息的情况下，网络管理生产者可以执行一个或多个第一子动作指示信息所指示的操作。
可选地，一个事件信息、一个条件信息、和对应的一个第一子动作指示信息可以称为一个管理策略。本申请不对管理策略一一列举。
例如，第一管理策略信息中的一个事件信息、一个条件信息、和对应的一个第一子动作指示信息可以称为一个第一管理策略。第二管理策略信息中的一个事件信息、一个条件信息、和对应的一个第一子动作指示信息可以称为一个第二管理策略。
一些实施例中，第一子动作指示信息可用于指示第一网络管理生产实体向第二网络管理生产实体发送第一通知信息和/或第一运行结果。
可选地，接收第一消息(详见下述S302)的实体为第一网络管理生产实体，第一网络管理生产实体管理的闭环管理过程为第一闭环管理过程，与第一闭环管理过程存在关联关系的闭环管理过程为第二闭环管理过程，用于管理第二闭环管理过程的实体为第二网络管理生产实体。其中，第二闭环管理过程的数量可以为一个或多个，第二网络管理生产实体的数量可以为一个或多个。
例如，结合图2，若网络管理生产实体1接收第一消息，则网络管理生产实体1为第一网络管理生产实体，闭环管理过程1为第一闭环管理过程，对于网络管理生产实体1，网络管理生产实体2为第二网络管理生产实体，闭环管理过程2为第二闭环管理过程。若网络管理生产实体2接收第一消息，则网络管理生产实体2为第一网络管理生产实体，闭环管理过程2为第一闭环管理过程，对于网络管理生产实体2，网络管理生产实体1为第二网络管理生产实体，闭环管理过程1为第二闭环管理过程。当然，网络管理生产实体1和网络管理生产实体2均可以接收第一消息，网络管理生产实体1接收的第一消息中包括的闭环管理过程1对应的管理策略信息1，网络管理生产实体2接收的第一消息中包括的闭环管理过程2对应的管理策略信息1。
示例性地，第一通知信息可以包括网络管理消费实体期望第二网络管理生产实体采用的第二闭环管理过程的保障目标。
示例性地，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
也就是说，管理策略信息可以包括指示第一网络管理生产实体与第二网络管理生产实体进行协作的策略，网络管理生产实体之间可以根据第一子动作指示信息进行协作，从而对闭环管理过程进行协调管理。
在一些实施例中，第一运行结果可以包括如下一项或多项：第一性能结果、第一性能结果对应的管理策略信息的标识、第一性能结果对应的条件信息、第一性能结果对应的事件信息、第一性能结果对应的第一动作指示信息。
可选地，与第一闭环管理过程对应的管理对象为第一被管理对象，第一性能结果可以包括第一被管理对象的性能的结果。
例如，第一性能结果包括：第一被管理对象的吞吐量>100兆位每秒(million bits per second，Mbps)，或者第一被管理对象的性能的结果满足或不满足第一闭环管理过程的保障目标。
也就是说，第一运行结果可以包括如下一项或多项：第一性能结果、获得第一性能结果采用的管理策略信息的标识、条件信息、事件信息、和第一动作指示信息。如此，可以使第二网络管理生产实体根据该第一运行结果确定是否调整自身的策略，以实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标。
下面结合图4以及表2至表4对闭环管理过程对应的管理策略信息进行阐述。
表2以图4中闭环管理过程包括闭环管理过程1和闭环管理过程2、NSI为跨域的网络切片、NSSI-1为RAN域的切片子网、以及时延为例。闭环管理过程1对应的第一动作指示信息指示网络管理生产者1增加网络切片资源配置，以使端到端时延<10ms。闭环管理过程2对应的第一动作指示信息指示网络管理生产者2增加网络切片资源配置，以使RAN域时延降低到<5ms。条件信息与第一动作指示信息对应，在满足条件信息的情况下，网络管理生产者执行第一动作指示信息中的操作。
闭环管理过程1对应的第一子动作指示信息可以指示网络管理生产者1向网络管理生产者2发送第一通知信息，还可以指示发送第一运行结果(表2中未示出)。闭环管理过程2对应的第一子动作指示信息可以指示网络管理生产者2在满足事件信息的情况下，应用第一通知信息中的保障目标，还可以指示网络管理生产者2把应用第一通知信息中的保障目标的事件报告给网络管理消费实体、和/或网络管理生产者1(表2中未示出)。在满足闭环管理过程2对应的事件信息的情况下，网络管理生产者2执行第一子动作指示信息指示的操作。可选地，闭环管理过程1对应的第一子动作指示信息可以与闭环管理过程1对应的条件信息对应、或不对应。
需要说明的是，表2仅为一种示例，例如管理策略信息可以包括比表2中更多或更少的内容，本申请不一一列举。
表2
Figure PCTCN2022121771-appb-000001
表3以图4中闭环管理过程包括闭环管理过程2和闭环管理过程3、NSSI-1为RAN域的切片子网、NSSI-2为CN域的切片子网、以及吞吐量为例。闭环管理过程2对应的第一动作指示信息指示网络管理生产者2增加网络切片资源配置，以使RAN域网络切片子网吞吐量>100Mbps。闭环管理过程3对应的第一动作指示信息指示网络管理生产者3增加网络切片资源配置，以使CN域网络切片吞吐量>100Mbps。条件信息与第一动作指示信息对应，在满足条件信息的情况下，网络管理生产者执行第一动作指示信息中的操作。
闭环管理过程2对应的第一子动作指示信息可以指示网络管理生产者2向网络管理生产者3发送第一通知信息，还可以指示发送第一运行结果(表3中未示出)，由于闭环管理过程2与闭环管理过程3为连接关系(串联)，其中任一段吞吐量瓶颈会影响到跨域的吞吐量性能，闭环管理过程2与闭环管理过程3需同步调整或者等待协作方(例如网络管理生产者2与网络管理生产者2互为协作方)的协作消息。闭环管理过程3对应的第一子动作指示信息可以指示网络管理生产者3在满足事件信息的情况下，应用第一通知信息中的保障目标，还可以指示网络管理生产者3把应用第一通知信息中的保障目标的事件报告给网络管理消费实体、和/或网络管理生产者2(表3中未示出)。在满足闭环管理过程3对应的事件信息的情况下，网络管理生产者3执行第一子动作指示信息指示的操作，闭环管理过程2对应的第一子动作指示信息可以与闭环管理过程2对应的条件信息对应。
需要说明的是，表3仅为一种示例，例如管理策略信息可以包括比表3中更多或更少的内容，本申请不一一列举。
表3
Figure PCTCN2022121771-appb-000002
表4以图4中闭环管理过程包括闭环管理过程1至闭环管理过程3，NSI为跨域的网络切片，NSSI-1为RAN域的切片子网，NSSI-2为CN域的切片子网，时延或吞吐量为例。闭环管理过程1至闭环管理过程3分别对应的第一动作指示信息分别指示增加网络切片资源配置，以使达到分别对应的保障目标。条件信息可以与第一动作指示信息对应，在满足条件信息的情况下，网络管理生产者执行对应的第一动作指示信息中的操作。
闭环管理过程1对应的第一子动作指示信息1可以指示网络管理生产者1向网络管理生产者2或网络管理生产者3发送第一通知信息1，还可以指示发送第一运行结果(表4中未示出)。相应地，网络管理生产者2或网络管理生产者3对应的第一子动作指示信息1指示网络管理生产者2或网络管理生产者3接收到第一通知信息1(满足事件信息1)，则根据第一子动作指示信息应用第一通知信息1中的保障目标，可以增加对应域切片子网资源配置，以达到时延<5ms的保障目标。
表4
Figure PCTCN2022121771-appb-000003
Figure PCTCN2022121771-appb-000004
Figure PCTCN2022121771-appb-000005
闭环管理过程2或网络管理生产者3对应的第一子动作指示信息2可以指示网络管理生产者2或3向网络管理生产者1发送第一运行结果和/或第一修改请求信息，可选地，第一修改请求信息可用于请求修改管理策略信息、和/或闭环管理过程的保障目标。相应地，网络管理生产者1对应的第一子动作指示信息3可以指示网络管理生产者1接收到第一运行结果和/或第一修改请求信息(满足事件信息)，则向网络管理生产实体2或3发送第一通知信息3，例如该第一通知信息3可以包括吞吐量>90Mbps。相应地，闭环管理过程2或网络管理生产者3对应的第一子动作指示信息3可以指示接收到来自网络管理生产实体1的第一通知信息3(满足事件信息2)，则应用第一通知信息3中的保障目标，可以增加对应域切片子网资源配置，以达到吞吐量>90Mbps的保障目标。
闭环管理过程2的第一子动作指示信息5可以指示网络管理生产者2向网络管理生产者3发送第一通知信息5，例如该第一通知信息5可以包括闭环管理过程3对应的CN域时延<5ms，还可以指示发送第一运行结果(表4中未示出)。相应地，网络管理生产者3对应的第一子动作指示信息4可以指示网络管理生产者3接收到第一通知信息5(满足事件信息3)，则应用第一通知信息5中的保障目标，可以增加对应域切片子网资源配置，以达到时延<5ms的保障目标。
闭环管理过程3的第一子动作指示信息5可以指示网络管理生产者3向网络管理生产者2发送第一通知信息4，例如该第一通知信息4可以包括闭环管理过程2对应的RAN域 时延<5ms，还可以指示发送第一运行结果(表4中未示出)。相应地，网络管理生产者2对应的第一子动作指示信息4可以指示网络管理生产者2接收到第一通知信息4(满足事件信息3)，则应用第一通知信息4中的保障目标，可以增加对应域切片子网资源配置，以达到时延<5ms的保障目标。
可选地，若网络管理生产者(例如网络管理生产者1、网络管理生产者2、网络管理生产者3等)在预设时间窗口内接收到多个第一通知信息、且多个第一通知信息内容相同，则可以仅执行一次第一子动作指示信息中的操作。
可选地，若网络管理生产者的多个第一通知信息有冲突，则可以根据多个闭环管理过程的优先级来执行多个第一通知信息对应的第一子动作指示信息或第一动作指示信息。
例如，闭环管理过程1的优先级高于闭环管理过程2，闭环管理过程2的优先级高于闭环管理过程3，网络管理生产者1接收到来自网络管理生产者2的第一通知信息、和网络管理生产者3的第一通知信息，若这两个第一通知信息存在冲突，则先执行网络管理生产者2的第一通知信息触发的动作，再执行网络管理生产者3的第一通知信息触发的动作。
需要说明的是，表4仅为一种示例，例如管理策略信息可以包括比表3中更多或更少的内容，本申请不一一列举。
下面结合图5以及表5对闭环管理过程对应的管理策略信息进行具体阐述。
表5
Figure PCTCN2022121771-appb-000006
表5以图5中闭环管理过程包括闭环管理过程4和闭环管理过程5、NSI-1和NSI-2为两个不同的跨域的网络切片、以及吞吐量为例。闭环管理过程4对应的第一动作指示信 息指示网络管理生产者4增加网络切片资源配置，以使跨域1网络切片吞吐量<100Mbps。闭环管理过程5对应的第一动作指示信息指示网络管理生产者5增加网络切片资源配置，以使跨域2网络切片吞吐量<120Mbps。条件信息与第一动作指示信息对应，在满足条件信息的情况下，网络管理生产者执行第一动作指示信息中的操作。
闭环管理过程4对应的第一子动作指示信息可以指示网络管理生产者4向网络管理生产者5发送第一通知信息，还可以指示发送第一运行结果(表5中未示出)。闭环管理过程5对应的第一子动作指示信息可以指示网络管理生产者5在满足事件信息的情况下，应用第一通知信息中的保障目标，还可以指示网络管理生产者5把应用第一通知信息中的保障目标的事件报告给网络管理消费实体、和/或网络管理生产者4(表5中未示出)。在满足闭环管理过程5对应的事件信息的情况下，网络管理生产者5执行第一子动作指示信息指示的操作，闭环管理过程4对应的第一子动作指示信息可以与闭环管理过程4对应的条件信息对应。
需要说明的是，表5仅为一种示例，例如管理策略信息可以包括比表5中更多或更少的内容，本申请不一一列举。
S302(图3中未示出)，网络管理消费实体向至少两个网络管理生产实体发送第一消息。相应地，网络管理生产实体接收来自网络管理消费实体的第一消息。
需要说明的是，网络管理消费实体向至少两个网络管理生产实体发送第一消息时，可以是分为多个步骤发送的。
以至少两个网络管理生产实体包括第一网络管理生产实体和第二网络管理生产实体为例，上述S302，可以包括：S302-1，网络管理消费实体向第一网络管理生产实体发送第一消息，S302-2，网络管理消费实体向第二网络管理生产实体发送第一消息。相应地，第一网络管理生产实体接收来自网络管理消费实体的第一消息，第二网络管理生产实体接收来自网络管理消费实体的第一消息。
示例性地，第一消息可以包括管理策略信息。例如，第一网络管理生产实体接收的第一消息包括第一管理策略信息，第二网络管理生产实体接收的第一消息包括第二管理策略信息，第一管理策略信息与第二管理策略信息的主要区别在于：第一管理策略信息对应第一闭环管理过程，第二管理策略信息对应第二闭环管理过程。具体实现方式均可参照上述S301中管理策略信息的实现方式，此处不再赘述。
例如，至少两个网络管理生产实体包括网络管理生产实体1和网络管理生产实体2,网络管理生产实体1用于管理闭环管理过程1，网络管理生产实体2用于管理闭环管理过程2，则网络管理消费实体向网络管理生产实体1发送的第一消息1可以包括管理策略信息1；网络管理消费实体向网络管理生产实体2发送的第一消息2可以包括管理策略信息2。如此，网络管理生产实体1可以根据管理策略信息1实现闭环管理过程1的保障目标，网络管理生产实体2可以根据管理策略信息2实现闭环管理过程2的保障目标。
如此，多个网络管理生产实体可以根据各自的管理策略信息对各自的闭环管理过程对应的保障目标。
可选地，网络管理生产实体可用于管理闭环管理过程。一个网络管理生产实体管理的闭环管理过程的数量为一个或多个。本申请实施例以一个网络管理生产实体管理一个闭环管理过程为例进行说明。
示例性地，接收第一消息的实体为第一网络管理生产实体，第一消息可以包括第一管理策略信息，第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应的管理策略信息为第二管理策略信息。
示例性地，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标。具体实现可参照上述S301中N个管理策略信息可用于实现N个闭环管理过程的保障目标的具体示例，第一管理策略信息与至少一个第二管理策略信息的数量的和可以为N。
在一种可能的设计方式中，接收第一消息的实体为第一网络管理生产实体，第一网络管理生产实体管理的闭环管理过程为第一闭环管理过程，与第一闭环管理过程对应的管理对象为第一被管理对象，与第一闭环管理过程存在关联关系的闭环管理过程为第二闭环管理过程，用于管理第二闭环管理过程的实体为第二网络管理生产实体。第一消息还可以包括如下一项或多项：第二网络管理生产实体的标识、第二闭环管理过程的标识、和第一闭环管理过程的保障目标。
可选地，第二网络管理生产实体接收的第一消息还可以包括如下一项或多项：第一网络管理生产实体的标识、第一闭环管理过程的标识、和第二闭环管理过程的保障目标。
示例性地，假设至少两个网络管理生产实体包括网络管理生产实体1和网络管理生产实体2,网络管理生产实体1用于管理闭环管理过程1，网络管理生产实体2用于管理闭环管理过程2，则网络管理消费实体向网络管理生产实体1发送的第一消息1可以包括管理策略信息1、网络管理生产实体2的标识、闭环管理过程2的标识、闭环管理过程1的保障目标；网络管理消费实体向网络管理生产实体2发送的第一消息2可以包括管理策略信息2、网络管理生产实体1的标识、闭环管理过程1的标识、闭环管理过程2的保障目标。
如此，网络管理生产实体1和网络管理生产实体2不仅可以根据各自的管理策略信息实现各自的闭环管理过程的保障目标，还可以根据接收的第一消息获得与自身关联的网络管理生产实体、自身管理的闭环管理过程关联的闭环管理过程，从而协商存在关联关系的闭环管理过程的保障目标。
S303，第一网络管理生产实体执行第一管理策略信息中的一个或多个第一管理策略。
关于第一管理策略信息的具体实现方式，可参照上述S301中管理策略信息的实现方式，此处不再赘述。
示例性地，第一网络管理生产实体执行第一管理策略信息中的一个或多个第一管理策略，该第一管理策略信息是根据关联关系信息和N个闭环管理过程的保障目标确定的，考虑了本闭环管理过程的保障目标和与本闭环管理过程存在关联关系的闭环管理过程的保障目标，如此，可以实现被管理对象(例如网络切片和/或网络切片子网)的SLS目标。
在一种可能的设计方式中，上述S303可以包括：第一网络管理生产实体根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。
示例性地，结合表2，假设网络管理生产实体1为第一网络管理生产实体，网络管理生产实体1根据第闭环管理过程1对应的第一动作指示信息，增加网络切片资源配置，以使RAN域时延<10ms，从而可以保障闭环管理过程1对应的保障目标。
在一种可能的设计方式中，上述S303可以包括：在满足条件信息、和/或事件信息的 情况下，第一网络管理生产实体根据第一动作指示信息，设置第一闭环管理过程对应的第一被管理对象的配置信息。
示例性地，结合表2，假设网络管理生产实体1为第一网络管理生产实体，若端到端时延>10ms，则第一网络管理生产实体根据第一动作指示信息，增加网络切片资源配置，以使端到端时延<10ms，从而可以保障闭环管理过程1对应的保障目标。
示例性地，结合表2，假设网络管理生产实体1为第一网络管理生产实体，若端到端时延>10ms，则触发条件触发事件，该条件触发事件指示网络管理生产实体1向网络管理生产实体2发送第一通知信息。
在一种可能的设计方式中，上述S303可以包括：第一网络管理生产实体根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息。
相应地，第二网络管理生产实体接收来自第一网络管理生产实体的第一协作消息。
可选地，第一协作消息可以包括第一通知信息和/或第一运行结果，第一通知信息可以包括网络管理消费实体期望第二网络管理生产实体采用的第二闭环管理过程的保障目标，第一运行结果可以是第一网络管理生产实体根据第一动作指示信息获得的，或者，第一运行结果可以是第一网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。关于第一通知信息和第一运行结果的具体实现方式可参照上述S301，此处不再赘述。
示例性地，结合表2，假设第一网络管理生产实体为网络管理生产实体1，第一网络管理生产实体根据网络管理生产实体2的标识和第一子动作指示信息，向网络管理生产实体2发送第一协作消息，该第一协作消息包括第一通知信息，第一通知信息可以包括闭环管理过程2对应的RAN域时延<3ms。
如此，第一网络管理生产实体可实现与第二网络管理生产实体进行协作操作，从而满足闭环管理过程对应的保障目标。
在一种可能的设计方式中，上述S303可以包括：在满足条件信息、和/或事件信息的情况下，第一网络管理生产实体根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息。
示例性地，结合表2，假设第一网络管理生产实体为网络管理生产实体1，若端到端时延>10ms，则第一网络管理生产实体根据第一子动作指示信息，向网络管理生产实体2发送第一协作消息，该第一协作消息包括第一通知信息，第一通知信息可以包括闭环管理过程2对应的RAN域时延<3ms。
示例性地，结合表4，假设第一网络管理生产实体为网络管理生产实体1，若接收到来自网络管理生产实体2的第一修改请求信息，则第一网络管理生产实体根据网络管理生产实体2的标识和第一子动作指示信息3，向网络管理生产实体2发送第一协作消息，该第一协作消息包括第一通知信息3，第一通知信息3可以包括闭环管理过程2对应的吞吐量>90Mbps。
示例性地，结合表2，假设第一网络管理生产实体为网络管理生产实体1，若端到端时延>10ms且接收到来自网络管理生产实体2的第一修改请求信息(表2中未示出)，则第一网络管理生产实体向网络管理生产实体2发送第一协作消息，该第一协作消息包括第 一通知信息，第一通知信息可以包括闭环管理过程2对应的RAN域时延<3ms。
如此，在第一闭环管理过程对应的属性不满足保障目标时、和/或接收到来自第二网络管理生产实体的第一修改请求信息时，可与第二网络管理生产实体进行协作操作，从而使闭环管理过程对应的属性满足保障目标。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S305，第一网络管理生产实体向第二网络管理生产实体发送第一协作消息。相应地，第二网络管理生产实体接收来自第一网络管理生产实体的第一协作消息。
可选地，第一协作消息包括第一通知信息和/或第一运行结果。
也就是说，第一网络管理生产实体可以直接向第二网络管理生产实体发送第二协作消息，不受管理策略信息是否包括第一子动作指示信息影响。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S306，第二网络管理生产实体根据第一通知信息中的保障目标，设置第二闭环管理过程对应的第二被管理对象的配置信息。
可选地，该第一通知信息是从第一网络管理生产实体接收的。
示例性地，结合表2，闭环管理过程2对应的保障目标为RAN域时延<5ms，若网络管理生产实体2收到第一通知信息，第一通知信息包括闭环管理过程2对应的RAN域时延<3ms，则网络管理生产实体2应用RAN域时延<3ms这个保障目标，增加RAN域切片子网资源，使RAN域时延<3ms。
也就是说，第二网络管理生产实体与第一网络管理生产实体可以通过协作来实现第一被管理对象和/或第二被管理对象的保障目标。
需要说明的是，本申请实施例不限定上述S306与下述S304的先后顺序，例如上述S306可以在下述S304之后执行。
S304，第二网络管理生产实体执行第二管理策略信息中的一个或多个第二管理策略。
关于第二管理策略信息的具体实现方式，可参照上述S301中管理策略信息的实现方式，此处不再赘述。
需要说明的是，在S303和S304之前，第一网络管理生产实体与第二网络管理生产实体之间可以先进行协商，例如协商将要执行的管理策略信息中的一个或多个第二管理策略(例如管理策略信息中包括多个管理策略)，又例如可以协商将要执行的管理策略信息中的条件信息(例如管理策略信息中包括多个条件信息)。
示例性地，第二网络管理生产实体执行第二管理策略信息中的一个或多个第二管理策略，该第二管理策略信息是根据关联关系信息和N个闭环管理过程的保障目标确定的，考虑了本闭环管理过程(例如第二闭环管理过程)的保障目标和与本闭环管理过程存在关联关系的闭环管理过程(例如一个或多个第一闭环管理过程)的保障目标，如此，可以实现被管理对象(例如网络切片和/或网络切片子网)的SLS目标。
在一种可能的设计方式中，上述S304可以包括：第二网络管理生产实体根据第一动作指示信息，设置第二闭环管理过程对应的第二被管理对象的配置信息。
示例性地，结合表2，假设网络管理生产实体2为第二网络管理生产实体，网络管理生产实体2根据第闭环管理过程2对应的第一动作指示信息，增加网络切片资源配置，以使RAN域时延<5ms，从而可以保障闭环管理过程2对应的保障目标。
在一种可能的设计方式中，上述S304可以包括：在满足条件信息、和/或事件信息的情况下，第二网络管理生产实体根据第一动作指示信息，设置第二闭环管理过程对应的第二被管理对象的配置信息。
示例性地，结合表2，假设网络管理生产实体2为第二网络管理生产实体，若RAN域时延>5ms，则网络管理生产实体2根据第一动作指示信息，增加网络切片资源配置，以使端到端时延<5ms，从而可以保障闭环管理过程2对应的保障目标。
示例性地，结合表2，假设网络管理生产实体2为第二网络管理生产实体，若接收到网络管理生产实体1的第一通知信息，则网络管理生产实体2应用第一通知信息中的保障目标，增加网络切片资源配置，以使端到端时延<5ms，从而可以保障闭环管理过程2对应的保障目标。可选地，网络管理生产实体2还可以把应用第一通知信息中的保障目标的事件报告给网络管理消费实体。
示例性地，结合表2，假设网络管理生产实体2为第二网络管理生产实体，若RAN域时延>5ms，则触发条件触发事件，该条件触发事件指示网络管理生产实体2增加网络切片资源配置。
在一种可能的设计方式中，上述S304可以包括：第二网络管理生产实体根据第一网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第二协作消息。具体实现与S303中第一网络管理生产实体根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息类似，此处不再赘述。
可选地，第二协作消息可以包括第二通知信息和/或第二运行结果。
可选地，第二通知信息可以包括网络管理消费实体期望第一网络管理生产实体采用的第一闭环管理过程的保障目标。
可选地，第二运行结果可以是第二网络管理生产实体根据第一动作指示信息获得的，或者，第二运行结果可以是第二网络管理生产实体根据条件信息和事件信息中的一项或多项、以及第一动作指示信息获得的。
如此，第二网络管理生产实体可实现与第一网络管理生产实体进行协作操作，从而满足闭环管理过程(例如第一闭环管理过程和/或第二闭环管理过程)对应的保障目标。
在一种可能的设计方式中，上述S304可以包括：在满足条件信息、和/或事件信息的情况下，第二网络管理生产实体根据第一网络管理生产实体的标识和第一子动作指示信息，向第一网络管理生产实体发送第二协作消息。具体实现与S303中在满足条件信息、和/或事件信息的情况下，第一网络管理生产实体根据第二网络管理生产实体的标识和第一子动作指示信息，向第二网络管理生产实体发送第一协作消息类似，此处不再赘述。
如此，在第二闭环管理过程对应的属性不满足保障目标时、和/或接收到来自第一网络管理生产实体的第一修改请求信息的情况下，可与第一网络管理生产实体进行协作操作，从而使闭环管理过程(例如第一闭环管理过程和/或第二闭环管理过程)对应的属性满足保障目标。
一些实施例中，网络管理生产实体(例如第一网络管理生产实体、或第二网络管理生产实体等)执行管理策略的过程中可以调用其他管理服务的功能，例如调用绩效管理(performance management，PM)的功能、或故障管理(fault management，FM)的功能进行性能或故障监控以判断关联策略中的条件是否满足，调用编排管理服务(orchestration  MnS)的功能对资源或参数进行重配置等。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S307，第二网络管理生产实体向第一网络管理生产实体发送第二协作消息。相应地，第一网络管理生产实体接收来自第二网络管理生产实体的第二协作消息。
可选地，第二协作消息包括第二通知信息和/或第二运行结果。
也就是说，第二网络管理生产实体可以直接向第一网络管理生产实体发送第二协作消息，不受第二管理策略信息是否包括第一子动作指示信息影响。
如此，网络管理生产实体可以自动协作运维，加速闭环管理过程的收敛，减少网络管理生产实体间的消息交互，可以不依赖于集中部署的协作者(如网络管理消费实体)进行实时协调，可以提高实现被管理对象的SLS目标的效率。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S308，第一网络管理生产实体根据第二通知信息中的保障目标，设置第一闭环管理过程对应的第一被管理对象的配置信息。
可选地，该第二通知信息是从第二网络管理生产实体接收的。
示例性地，结合表4，假设闭环管理过程3为第一闭环管理过程，网络管理生产者3为第一网络管理生产实体，闭环管理过程3对应的保障目标为CN域吞吐量>100Mbps，若网络管理生产实体3收到第一通知信息3，第一通知信息3包括闭环管理过程3对应的闭环管理过程3对应的CN域吞吐量>90Mbps，则网络管理生产实体3应用CN域吞吐量>90Mbps这个保障目标，增加CN域切片子网资源，使CN域吞吐量>90Mbps。
也就是说，第一网络管理生产实体与第二网络管理生产实体可以通过协作来实现第一被管理对象和/或第二被管理对象的保障目标。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S309,第一网络管理生产实体向网络管理消费实体发送第二消息。相应地，网络管理消费实体接收来自第一网络管理生产实体的第二消息。
可选地，第二消息可以包括第一运行结果和/或第一网络管理生产实体的第一修改请求信息。
关于第一运行结果的具体实现方式可参照上述S301，此处不再赘述。
可选地，第一网络管理生产实体的第一修改请求信息可用于请求修改第一管理策略信息、和/或第一闭环管理过程的保障目标。
如此，网络管理消费实体可以根据第一运行结果和/或修改请求，调整第一闭环管理过程的管理策略信息和/或保障目标。
示例性地，第一网络管理生产实体的第一修改请求信息可以包括第一网络管理生产实体期望使用的管理策略信息、和/或第一闭环管理过程的保障目标。例如，第一修改请求信息可以包括时延<3ms。
如此，网络管理消费实体可以直接采用第一修改请求信息中包括的管理策略信息、和/或保障目标，作为第一闭环管理过程的管理策略信息和/或保障目标；或者参考第一修改请求信息中包括的管理策略信息、和/或保障目标，调整第一闭环管理过程的管理策略信息和/或保障目标。
需要说明的是，若第一网络管理生产实体执行第一管理策略信息中的一个或多个第一 管理策略(上述S303)后已实现第一被管理对象的SLS目标，则可以不执行S309；或者执行S309，其中第二消息包括第一运行结果，不包括第一网络管理生产实体的第一修改请求信息。
在一些实施例中，第一网络管理生产实体的第一修改请求信息可以是第一网络管理生产实体根据第二通知信息和/或第二运行结果、和/或第一运行结果确定的。
关于第二通知信息、第二运行结果的具体实现方式可参照上述S304，此处不再赘述。
也就是说，第一网络管理生产实体可以根据网络管理消费实体向期望其采用的保障目标、第二网络管理生产实体的第二运行结果、和/或自身的第一运行结果，确定是否请求修改第一闭环管理过程的保障目标和/或管理策略信息，还可以确定期望的保障目标和/或管理策略信息。
在一些实施例中，第二通知信息和/或第二运行结果可以是第一网络管理生产实体从第二网络管理生产实体接收的。
示例性地，第一网络管理生产实体接收第二通知信息后，可以直接应用第一通知信息中的保障目标；还可以把应用第一通知信息中的保障目标的事件发送给网络管理消费实体。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S310，第二网络管理生产实体向网络管理消费实体发送第二消息。相应地，网络管理消费实体接收来自第二网络管理生产实体的第二消息。
可选地，第二消息可以包括第二运行结果和/或第二网络管理生产实体的第一修改请求信息。
可选地，第二网络管理生产实体的第一修改请求信息可用于请求修改第二管理策略信息、和/或第二闭环管理过程的保障目标。
如此，网络管理消费实体可以根据第二网络管理生产实体的第二运行结果和/或修改请求，调整第二闭环管理过程的管理策略信息和/或保障目标。
示例性地，第二网络管理生产实体的第二修改请求信息可以包括第二网络管理生产实体期望使用的管理策略信息、和/或第二闭环管理过程的保障目标。
如此，网络管理消费实体可以直接采用第一修改请求信息中包括的管理策略信息、和/或保障目标，作为第二闭环管理过程的管理策略信息和/或保障目标；或者参考第一修改请求信息中包括的管理策略信息、和/或保障目标，调整第二闭环管理过程的管理策略信息和/或保障目标。
一些实施例中，第二网络管理生产实体可以向网络管理消费实体周期性发送第二消息。
需要说明的是，若第二网络管理生产实体执行第二管理策略信息中的一个或多个第二管理策略(上述S304)后已实现第二被管理对象的SLS目标，则可以不执行S310；或者执行S310，其中第二消息包括第二运行结果，不包括第二网络管理生产实体的第一修改请求信息。
在一种可能的设计方式中，第二网络管理生产实体的第一修改请求信息是第二网络管理生产实体根据第一通知信息和/或第一运行结果、和/或第二运行结果确定的。
关于第一通知信息、第一运行结果的具体实现方式，可参照上述S303中的实现方式，此处不再赘述。关于第二运行结果的具体实现方式，可参照上述S304中的实现方式，此 处不再赘述。
也就是说，第二网络管理生产实体可以根据网络管理消费实体向期望其采用的保障目标、第一网络管理生产实体的第一运行结果、和/或自身的第二运行结果，确定是否请求修改第二闭环管理过程的保障目标和/或管理策略信息，还可以确定期望的保障目标和/或管理策略信息。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S311，网络管理消费实体根据至少一个网络管理生产实体的第一运行结果和/或至少一个网络管理生产实体的第一修改请求信息，确定新的管理策略信息和/或闭环管理过程的新的保障目标。
可选地，新的管理策略信息可以包括一个或多个新的管理策略信息，例如新的第一管理策略信息、和/或新的第二管理策略信息。
可选地，闭环管理过程的新的保障目标可以包括第一闭环管理过程的新的保障目标、和/或第二闭环管理过程的新的保障目标。
示例性地，结合图2，至少一个网络管理生产实体的第一运行结果可以包括：网络管理生产实体1的第一运行结果、和/或网络管理生产实体2的第一运行结果。至少一个网络管理生产实体的第一修改请求信息可以包括：网络管理生产实体1的第一修改请求信息、和/或网络管理生产实体2的第一修改请求信息。
例如，结合表2，可以将闭环管理过程1对应的第一子动作指示信息的第一通知信息修改为：闭环管理过程2对应的RAN域时延<6ms。
如此，网络管理消费实体可以根据一个或多个网络管理生产实体的第一运行结果、和/或一个或多个网络管理生产实体的第一修改请求信息，调整一个或多个闭环管理过程的管理策略信息和/或保障目标，以使相应的网络管理生产实体进一步根据新的管理策略信息和/或新的保障目标实现相应的被管理对象的SLS目标。
可选地，本申请提供的网络管理方法可以支持人工或外部实体优化管理策略信息和/或保障目标，例如，人工根据至少一个网络管理生产实体的第一运行结果和/或至少一个网络管理生产实体的第一修改请求信息，确定新的管理策略信息和/或闭环管理过程的新的保障目标。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S312，网络管理消费实体向第一网络管理生产实体发送新的第一管理策略信息和/或第一闭环管理过程的新的保障目标。相应地，第一网络管理生产实体接收来自网络管理消费实体的新的第一管理策略信息和/或第一闭环管理过程的新的保障目标。
如此，第一网络管理生产实体可以进一步根据新的管理策略信息和/或新的保障目标实现第一被管理对象的SLS目标。
在一种可能的设计方式中，本申请实施例提供的网络管理方法，还可以包括：S313，网络管理消费实体向第二网络管理生产实体发送新的第二管理策略信息和/或第二闭环管理过程的新的保障目标。相应地，第二网络管理生产实体接收来自网络管理消费实体的新的第二管理策略信息和/或第二闭环管理过程的新的保障目标。
如此，第二网络管理生产实体可以进一步根据新的第二管理策略信息和/或新的保障目标实现第二被管理对象的SLS目标。
需要说明的是，若第一网络管理生产实体执行第一管理策略信息中的一个或多个第一管理策略(上述S303)后已实现第一被管理对象的SLS目标，则可以不执行S309；若第二网络管理生产实体执行第二管理策略信息中的一个或多个第二管理策略(上述S304)后已实现第二被管理对象的SLS目标，则可以不执行S310。
基于图3所示的网络管理方法，第一网络管理生产实体接收第一管理策略信息，并执行第一管理策略信息中的一个或多个第一管理策略。该第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应第二管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第一被管理对象为第一闭环管理过程所管理的资源或业务，第一闭环管理过程是实现第一被管理对象的SLS目标的管理过程，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，第二闭环管理过程由第二网络管理生产实体管理。如此，第一网络管理生产实体能够实现第一被管理对象(例如网络切片和/或网络切片子网等)的SLS目标，可以提高用户的业务体验，保障业务的正常运行。
需要说明的是，图3以一个网络管理消费实体根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息为例，在另一些实施例中，N个管理策略信息可以是两个或两个以上网络管理消费实体确定的，例如第一网络管理消费实体和第二网络管理消费实体可以根据关联关系信息和N个闭环管理过程的保障目标协商确定N个管理策略信息。
可选地，可以由一个网络管理消费实体将N个管理策略信息发送给N个网络管理生产实体的，具体可参照上述S302-1和S302-2。或者，可选地，可以由多个网络管理消费实体将N个管理策略信息发送给N个网络管理生产实体的，例如，第一网络管理消费实体向第一网络管理生产实体发送第一管理策略信息，第二网络管理消费实体向第二网络管理生产实体发送第二管理策略信息。
下面结合图6和图7对生成管理策略信息的过程进行阐述。图7所示的网络管理方法可与上述图3所示的网络管理方法结合使用。
网络切片相关的管理功能包括通信服务管理功能(communication service management function，CSMF)、网络切片管理功能(network slice management function，NSMF)、和网络切片子网管理功能(network slice subnet management function，NSSMF)。
网络切片的管理架构如图6所示，网络切片的管理架构可以包括：通信服务管理服务(communication service management service，CSMS)生产实体、网络切片管理服务(network slice management service，NSMS)生产实体、网络切片子网管理服务(network slice subnet management service，NSSMS)生产实体。其中，NSSMS生产实体可以包括：RAN NSSMS生产实体、CN NSSMS生产实体和TN NSSMS生产实体。网络切片的管理架构还可以包括：CSMS消费实体、NSMS消费实体、和NSSMS消费实体(图6中未示出)。其中，NSMS生产实体管理网络切片实例NSI的生命周期(如创建、删除、修改)和性能、告警等。NSSMS生产实体管理网络切片子网实例NSSI的生命周期和性能、告警等。
在本申请实施例中，CSMF与CSMS生产实体可以等同替换、NSMF与NSMS生产实体可以等同替换、NSSMF与NSSMS生产实体可以等同替换。
需要说明的是，本申请中“生产实体”可以称为“生产者”，“消费实体”可以称为“消费者”。 网络管理生产实体可以是物理设备，网络管理生产实体的功能可以部署在物理设备上，例如，网络管理生产实体可以是部署在物理设备内的功能模块。
示例性地，图7为本申请实施例提供的另一种网络管理方法的流程示意图。图7所示的网络管理方法主要结合图4对生成管理策略信息进行阐述，生成的管理策略信息可用于上述图3所示的网络管理方法。
可选地，网络管理生产实体可以包括：网络切片网络管理生产实体、RAN网络切片子网网络管理生产实体、CN网络切片子网网络管理生产实体、和TN网络切片子网网络管理生产实体(图7所示的方法与图4结合使用时，可以不包括TN网络切片子网网络管理生产实体)。NSMS生产实体可以为网络切片网络管理生产实体的消费者，NSSMS生产实体可以为网络切片子网网络管理生产实体的消费者，例如RAN NSSMS生产实体可以为RAN网络切片子网网络管理生产实体的消费者，CN NSSMS生产实体可以为CN网络切片子网网络管理生产实体的消费者，TN NSSMS生产实体可以为TN网络切片子网网络管理生产实体的消费者。
可选地，网络管理生产实体可以是闭环管理生产实体(可以称为闭环管理生产者、或闭环管理服务生产者等)、NSMS生产实体、和NSSMS生产实体等实体的上位概念，闭环管理生产实体、NSMS生产实体、和NSSMS生产实体可以是不同的网络管理生产实体。
例如，图7所示的方法中的网络管理生产实体可以为闭环管理生产实体，相应地，网络切片网络管理生产实体可以为网络切片闭环管理生产实体，RAN网络切片子网网络管理生产实体可以为RAN网络切片子网闭环管理生产实体，CN网络切片子网网络管理生产实体可以为CN网络切片子网闭环管理生产实体，TN网络切片子网网络管理生产实体可以为TN网络切片子网闭环管理生产实体。再例如，图3所示的方法中的网络管理生产实体可以为闭环管理生产实体，又例如，图8所示的方法中的网络管理生产实体可以为闭环管理生产实体。
如图7所示，该网络管理方法包括如下步骤：
S701，NSMS消费实体向NSMS生产实体发送服务需求(service profile)，请求创建NSI。相应地，NSMS生产实体接收来自于NSMS消费实体的服务需求。
示例性地，服务需求可以包括时延、带宽、安全性和可靠性等。
S702，NSMS生产实体根据服务需求创建NSI。
示例性地，创建的NSI可以为图4中的NSI。
S703，NSMS生产实体向闭环管理生产实体发送服务需求或服务需求的子集。相应地，闭环管理生产实体接收来自NSMS生产实体的服务需求或服务需求的子集。
可选地，服务需求或服务需求的子集可以作为保障目标。
S704，网络管理生产实体创建第一闭环管理过程。
可选地，第一闭环管理过程(可简称CL1)可以支持或实现对应的闭环目标。
示例性地，第一闭环管理过程可以包括管理控制闭环所涉及的步骤(监控、分析、决策、执行)、管理服务、方法和过程等。具体可参照上述对闭环管理过程的阐述。
可选地，网络管理生产实体将第一闭环管理过程与NSI关联，作为网络切片级闭环管理过程CL1。
S705，网络管理生产实体向NSSMS生产实体发送第一切片需求(slice profile)和第 二切片需求。相应地，NSSMS生产实体接收来自网络管理生产实体的第一切片需求和第二切片需求。
可选地，第一切片需求可用于请求创建NSSI-1，第二切片需求可用于请求创建NSSI-2。
一些实施例中，NSSMS生产实体可以包括RAN NSSMS生产实体和CN NSSMS生产实体。
可选地，上述S705，可以包括：网络管理生产实体向RAN NSSMS生产实体发送第一切片需求(slice profile)，向CN NSSMS生产实体发送第二切片需求。相应地，RAN NSSMS生产实体接收来自网络管理生产实体的第一切片需求，CN NSSMS生产实体接收来自网络管理生产实体的第二切片需求。
可选地，网络管理生产实体可以向NSSMS生产实体发送服务需求或服务需求的子集。相应地，NSSMS生产实体接收来自网络管理生产实体的服务需求或服务需求的子集。
S706，NSSMS生产实体创建NSSI-1和NSSI-2。
示例性地，结合图4，RAN NSSMS生产实体可以根据第一切片需求创建NSSI-1，CN NSSMS生产实体根据第二切片需求创建NSSI-2。
S707，NSSMS生产实体向网络管理生产实体发送第一切片需求、第二切片需求、和子网级的管理策略信息。相应地，网络管理生产实体接收来自NSSMS生产实体的第一切片需求、第二切片需求、和子网级的管理策略信息。
一些实施例中，网络管理生产实体可以包括RAN网络切片子网网络管理生产实体和CN网络切片子网网络管理生产实体。
需要说明的是，网络管理生产实体可以是一个，也可以是分别对应于NSI、NSSI-1、NSSI-2的三个不同的网络管理生产实体。
可选地，上述S707，可以包括：RAN NSSMS生产实体向RAN网络切片子网网络管理生产实体发送第一切片需求、和子网级的管理策略信息；CN NSSMS生产实体向CN网络切片子网网络管理生产实体发送第二切片需求、和子网级的管理策略信息。相应地，RAN网络切片子网网络管理生产实体接收来自RAN NSSMS生产实体的第一切片需求、和子网级的管理策略信息；CN网络切片子网网络管理生产实体接收来自CN NSSMS生产实体的第二切片需求、和子网级的管理策略信息。
可选地，RAN NSSMS生产实体和CN NSSMS生产实体可以根据服务需求、第一切片需求和第二切片需求的关联关系和网络组成信息，确定关联关系，并根据关联关系确定子网级的管理策略信息。
示例性地，子网级的管理策略信息可以包括NSSI-1对应的管理策略信息、和NSSI-2对应的管理策略信息。
示例性地，结合图4，网络组成信息可以包括：NSI、NSSI-1和NSSI-2。
示例性地，结合图4，关联关系可以包括：NSI包含NSSI-1和NSSI-2，NSSI-1和NSSI-2为连接关系。
可选地，RAN NSSMS生产实体和CN NSSMS生产实体可作为网络管理生产实体的消费实体。
S708，网络管理生产实体创建第二闭环管理过程和第三闭环管理过程。
可选地，第二闭环管理过程和第三闭环管理过程可以分别支持或实现对应的保障目标。
示例性地，第二闭环管理过程CL2关联NSSI-1，第三闭环管理过程CL3关联NSSI-2。第二闭环管理过程和第三闭环管理过程可以为网络切片子网级闭环管理过程。
示例性地，第二闭环管理过程和第三闭环管理过程均可以包括管理控制闭环所涉及的步骤(监控、分析、决策、执行)、管理服务、方法和过程等。
一些实施例中，上述S708，可以包括：RAN网络管理生产实体创建第二闭环管理过程，和CN网络管理生产实体创建第三闭环管理过程。
S709，网络管理生产实体向NSMS生产实体发送子网级的管理策略信息。
S710，NSMS生产实体向网络管理生产实体发送第一闭环管理过程的管理策略信息、第二闭环管理过程的管理策略信息、和第三闭环管理过程的管理策略信息。相应地，网络管理生产实体接收来自NSMS生产实体的第一闭环管理过程的管理策略信息、第二闭环管理过程的管理策略信息、和第三闭环管理过程的管理策略信息。
可选地，上述S710，可以包括：NSMS生产实体向网络切片网络管理生产实体、RAN网络切片子网网络管理生产实体、和CN网络切片子网网络管理生产实体分别发送第一闭环管理过程的管理策略信息、第二闭环管理过程的管理策略信息、和第三闭环管理过程的管理策略信息。相应地，网络切片网络管理生产实体、RAN网络切片子网网络管理生产实体、和CN网络切片子网网络管理生产实体分别接收来自NSMS生产实体的第一闭环管理过程的管理策略信息、第二闭环管理过程的管理策略信息、和第三闭环管理过程的管理策略信息。
一些实施例中，图7所示的方法还可以包括：NSMS生产实体根据NSI、NSSI-1和NSSI-2的关联关系，确定第一闭环管理过程、第二闭环管理过程和第三闭环管理过程的关联关系，并根据第一闭环管理过程、第二闭环管理过程、第三闭环管理过程的关联关系和子网级的管理策略信息，生成第一闭环管理过程的管理策略信息、第二闭环管理过程的管理策略信息、和第三闭环管理过程的管理策略信息。
图8为本申请实施例提供的又一种网络管理方法的流程示意图。图8所示的网络管理方法主要对管理策略信息的应用进行阐述。图8所示的网络管理方法可以与图3和/或图7所示的网络管理方法结合使用。网络管理生产实体可以通过管理服务数据库实体与M/A/D/E管理生产实体通信，M/A/D/E管理生产实体可以表示监控管理生产实体、分析管理生产实体、决策管理生产实体、或执行管理生产实体简称。
需要说明的是，监控管理生产实体、分析管理生产实体、决策管理生产实体、执行管理生产实体、和管理服务数据库实体可以与网络管理生产实体集中部署于一个物理设备，也可以与网络管理生产实体分别独立部署，或者部分集中部署。
与图7所示的网络管理方法相比，图8所示的网络管理方法中将闭环管理过程内部监控、分析、决策、执行对应的服务进一步打开，对应的功能由监控管理生产实体、分析管理生产实体、决策管理生产实体、执行管理生产实体分别执行，并阐述如何通过管理服务数据库(MnS repository)实体对上述各服务进行注册与发现，管理策略信息包括的内容可参照上述图3所示的方法，管理策略信息的生成方式可参照图7所示的方法。
S801，M/A/D/E管理生产实体分别向管理服务数据库实体发送注册管理服务请求。相应地，管理服务数据库实体接收来自M/A/D/E管理生产实体的注册管理服务请求。
可选地，注册管理服务请求可用于请求进行管理服务注册。
示例性地，管理服务为闭环所包含的管理服务，例如，监控、分析、决策、执行等。
示例性地，注册管理服务请求可以包括注册信息。注册信息可以包括管理服务的标识、服务唯一名称、服务端口、服务地址等。如此，可以使管理服务被发现和调用。
例如，管理服务的标识可以包括监控管理服务的标识、分析管理服务的标识、决策管理服务的标识、和执行管理服务的标识。
可选地，管理服务数据库(MnS repository)实体也可称为集成总线(integration fabric)。
S802，管理服务数据库实体向M/A/D/E管理生产实体分别发送注册成功信息。相应地，M/A/D/E MnSes等管理服务接收来自管理服务数据库实体的注册成功信息。
S803，网络管理消费实体向一个或多个网络管理生产实体发送服务需求或服务需求的子集。相应地，网络管理生产实体接收来自网络管理消费实体的服务需求或服务需求的子集。
可选地，网络管理消费实体可以包括：网络切片管理消费实体、RAN网络切片子网网络管理消费实体、CN网络切片子网网络管理消费实体和TN网络切片子网网络管理消费实体。
可选地，网络管理生产实体可以包括：网络切片网络管理生产实体、RAN网络切片子网网络管理生产实体、CN网络切片子网网络管理生产实体和TN网络切片子网网络管理生产实体。上述网络管理生产实体可以是网络管理消费实体，例如网络切片网络管理生产实体可以是网络切片闭环管理生产者的网络管理消费实体等。
可选地，服务需求或服务需求的子集的全部或部分属性可以作为闭环管理过程的保障目标。
S804，一个或多个网络管理生产实体向管理服务数据库实体发送请求消息。相应地，管理服务数据库实体接收来自一个或多个网络管理生产实体的请求消息。
可选地，请求消息可用于请求管理服务信息，管理服务信息可用于生成闭环管理过程。
示例性地，管理服务信息可以包括管理服务的标识、服务唯一名称、服务端口、服务地址等。例如，管理服务信息可以包括M/A/D/E管理生产实体的标识、M/A/D/E管理生产实体的名称、端口或地址。
S805，管理服务数据库实体向一个或多个网络管理生产实体分别发送管理服务信息。相应地，网络管理生产实体接收来自管理服务数据库实体的管理服务信息。
S806，网络管理生产实体根据管理服务信息生成第一闭环管理过程。
可选地，第一闭环管理过程(可简称CL1)可以支持或实现对应的被管理对象的SLS目标。
在一些实施例中，网络管理生产实体可以通过M/A/D/E管理生产实体的标识、M/A/D/E管理生产实体的名称、端口或地址等信息来调用M/A/D/E管理生产实体。
S807，网络管理消费实体向网络管理生产实体发送管理策略信息。相应地，网络管理生产实体接收来自网络管理消费实体的管理策略信息。
需要说明的是，管理策略信息包括的内容可参照上述S301，管理策略信息的生成过程可以参照实施例3，此处不再赘述。
S808，网络管理生产实体保存管理策略信息。
S809，网络管理生产实体向M/A/D/E管理生产实体分别发送对应的管理策略信息。相 应地，M/A/D/E管理生产实体分别接收来自网络管理生产实体的管理策略信息。
示例性地，网络管理生产实体可以向M管理生产实体发送与监控相关的管理策略信息，网络管理生产实体可以向A管理生产实体发送与分析相关的管理策略信息，网络管理生产实体可以向D管理生产实体发送与决策相关的管理策略信息，网络管理生产实体可以向E管理生产实体发送与执行相关的管理策略信息。
需要说明的是，网络管理生产实体可以不向M/A/D/E管理生产实体分别发送对应的管理策略信息，由网络管理生产实体统一调度与监控相关的管理策略信息、与分析相关的管理策略信息、与决策相关的管理策略信息和与执行相关的管理策略信息。
S810，网络管理生产实体向M/A/D/E管理生产实体分别发送订阅消息。相应地，M/A/D/E管理生产实体分别接收来自网络管理生产实体的订阅消息。
示例性地，订阅消息可以包括但不限于如下一项或多项：性能、告警测量信息、分析信息、决策信息、和执行结果。如此，M/A/D/E管理生产实体可分别向网络管理生产实体发送网络管理生产实体请求订阅的信息。
S811，M/A/D/E管理生产实体分别向网络管理生产实体发送第三消息。相应地，网络管理生产实体接收来自M/A/D/E管理生产实体的第三消息。
示例性地，第三消息可以包括但不限于如下一项或多项：性能、告警测量信息、分析信息、决策信息、和执行结果。
可选地，第三消息可以是M/A/D/E管理生产实体根据订阅消息获取管理数据后确定的。
示例性地，管理数据可以包括属性的相关数据、告警数据等。例如与吞吐量相关的数据、与时延相关的数据等。
一些实施例中，M/A/D/E管理生产实体可以分别周期性发送第三消息。
一些实施例中，管理数据可以是监控管理生产实体从网元的管理系统收集上来的。例如从RAN的管理系统获取RAN域的与吞吐量/时延相关的数据，从CN的管理系统获取CN域的与吞吐量/时延相关的数据。
S812，网络管理生产实体执行管理策略信息中的管理策略。
示例性地，网络管理生产实体根据管理策略信息进行管理行为，例如调用M/A/D/E管理生产实体执行相应的管理策略。
关于S812的具体实现方式可参照上述S303，此处不再赘述。
S813，M/A/D/E管理生产实体执行管理策略信息中的管理策略。
可选地，M/A/D/E管理生产实体可以根据网络管理生产实体的调度执行相应的管理策略，或者，M/A/D/E管理生产实体根据在上述S809中接收的管理策略信息执行相应的管理策略。
示例性地，M/A/D/E管理生产实体可以获取监控数据、获取管理数据分析信息、进行管理决策、执行管理行为等，还可以将运行结果发送给网络管理生产实体。
本申请中，除特殊说明外，各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中，如果没有特殊说明以及逻辑冲突，不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新 的实施例、实施方式、实施方法、或实现方法。以下所述的本申请实施方式并不构成对本申请保护范围的限定。
以上结合图3-图8详细说明了本申请实施例提供的网络管理方法。以下结合图9-图10详细说明本申请实施例提供的网络管理装置。
图9为可用于执行本申请实施例提供的一种网络管理装置的结构示意图。网络管理装置900可以是网络管理生产实体(例如第一网络管理生产实体、或第二网络管理生产实体等)、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体中的芯片或者其他具有相应功能的部件。如图9所示，网络管理装置900可以包括处理器901。可选地，网络管理装置900还可以包括存储器902和收发器903中的一个或多个。其中，处理器901可以与存储器902和收发器903中的一个或多个耦合，如可以通过通信总线连接，处理器901也可以单独使用。
下面结合图9对网络管理装置900的各个构成部件进行具体的介绍：
处理器901是网络管理装置900的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器901是一个或多个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
其中，处理器901可以通过运行或执行存储在存储器902内的软件程序，以及调用存储在存储器902内的数据，执行网络管理装置900的各种功能。
在具体的实现中，作为一种实施例，处理器901可以包括一个或多个CPU，例如图9中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，网络管理装置900也可以包括多个处理器，例如图9中所示的处理器901和处理器904。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个通信设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
可选地，存储器902可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储通信设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储通信设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储通信设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器902可以和处理器901集成在一起，也可以独立存在，并通过网络管理装置900的输入/输出端口(图9中未示出)与处理器901耦合，本申请实施例对此不作具体限定。
示例性地，输入端口可用于实现上述任一方法实施例中由网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、 或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体执行的接收功能，输出端口可用于实现上述任一方法实施例中由网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体执行的发送功能。
其中，所述存储器902可用于存储执行本申请方案的软件程序，并由处理器901来控制执行。上述具体实现方式可以参考下述方法实施例，此处不再赘述。
可选地，收发器903，用于与其他网络管理装置之间的通信。例如，网络管理装置900为网络管理生产实体时，收发器903可以用于与网络管理消费实体和/或其他网络管理生产实体通信。又例如，网络管理装置900为网络管理消费实体时，收发器903可以用于与至少两个网络管理生产实体通信。此外，收发器903可以包括接收器和发送器(图9中未单独示出)。其中，接收器用于实现接收功能，发送器用于实现发送功能。收发器903可以和处理器901集成在一起，也可以独立存在，并通过网络管理装置900的输入/输出端口(图9中未示出)与处理器901耦合，本申请实施例对此不作具体限定。
需要说明的是，图9中示出的网络管理装置900的结构并不构成对该网络管理装置的限定，实际的网络管理装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
其中，上述图3-图8中网络管理生产实体(例如第一网络管理生产实体、或第二网络管理生产实体等)的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令网络管理生产实体执行。
上述图3-图8中网络管理消费实体的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令网络管理消费实体执行，本实施例对此不作任何限制。
上述图3-图8中NSMS消费实体的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令NSMS消费实体执行，本实施例对此不作任何限制。
上述图3-图8中NSMS生产实体的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令NSMS生产实体执行，本实施例对此不作任何限制。
上述图3-图8中管理服务数据库实体的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令管理服务数据库实体执行，本实施例对此不作任何限制。
上述图3-图8中M/A/D/E管理生产实体的动作可以由图9所示的网络管理装置900中的处理器901调用存储器902中存储的应用程序代码以指令M/A/D/E管理生产实体执行，本实施例对此不作任何限制。
当网络管理装置为网络管理生产实体(第一网络管理生产实体、或第二网络管理生产实体)时，网络管理装置900可执行上述方法实施例中的网络管理生产实体(第一网络管 理生产实体、或第二网络管理生产实体)所涉及的任一种或多种可能的设计方式；当网络管理装置为网络管理消费实体时，网络管理装置900可执行上述方法实施例中的网络管理消费实体所涉及的任一种或多种可能的设计方式。
当网络管理装置为NSMS消费实体时，网络管理装置900可执行上述方法实施例中的NSMS消费实体所涉及的任一种或多种可能的设计方式；当网络管理装置为NSMS生产实体时，网络管理装置900可执行上述方法实施例中的NSMS生产实体所涉及的任一种或多种可能的设计方式；当网络管理装置为NSSMS生产实体时，网络管理装置900可执行上述方法实施例中的NSSMS生产实体所涉及的任一种或多种可能的设计方式；当网络管理装置为管理服务数据库实体时，网络管理装置900可执行上述方法实施例中的管理服务数据库实体所涉及的任一种或多种可能的设计方式；当网络管理装置为M/A/D/E管理生产实体时，网络管理装置900可执行上述方法实施例中的M/A/D/E管理生产实体所涉及的任一种或多种可能的设计方式。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图10为本申请实施例提供的另一种网络管理装置的结构示意图。为了便于说明，图10仅示出了该网络管理装置的主要部件。
该网络管理装置1000包括收发模块1001、和处理模块1002。该网络管理装置1000可以是前述方法实施例中的网络管理生产实体(例如第一网络管理生产实体、或第二网络管理生产实体等)、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体。收发模块1001，也可以称为收发单元，用以实现上述任一方法实施例中由网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体执行的收发功能。
需要说明的是，收发模块1001可以包括接收模块和发送模块(图10中未示出)。其中，接收模块用于接收来自其他设备的数据和/或信令；发送模块用于向其他设备发送数据和/或信令。本申请对于收发模块的具体实现方式，不做具体限定。该收发模块可以由收发电路、收发机、收发器或者通信接口构成。
处理模块1002，可以用于实现上述任一方法实施例中由网络管理生产实体(例如第一网络管理生产实体、或第二网络管理生产实体等)、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体执行的处理功能。该处理模块1002可以为处理器。
在本实施例中，该网络管理装置1000以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本 领域的技术人员可以想到该网络管理装置1000可以采用图9所示的网络管理装置900的形式。
比如，图9所示的网络管理装置900中的处理器901可以通过调用存储器902中存储的计算机执行指令，使得上述方法实施例中的网络管理方法被执行。
具体的，图10中的收发模块1001和处理模块1002的功能/实现过程可以通过图9所示的网络管理装置900中的处理器901调用存储器902中存储的计算机执行指令来实现。或者，图10中的处理模块1002的功能/实现过程可以通过图9所示的网络管理装置900中的处理器901调用存储器902中存储的计算机执行指令来实现，图10中的收发模块1001的功能/实现过程可以通过图9中所示的网络管理装置900中的收发器903来实现。
由于本实施例提供的网络管理装置1000可执行上述网络管理方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
在一种可能的设计方案中，图10所示出的网络管理装置1000可适用于图1、图2所示出的网络管理系统中，执行图2-图5所示的网络管理方法中的第一网络管理生产实体的功能。网络管理装置1000用于管理第一闭环管理过程，第一闭环管理过程是实现第一被管理对象的SLS目标的管理过程，第一被管理对象为第一闭环管理过程所管理的资源或业务，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，第二闭环管理过程由第二网络管理生产实体管理，第二被管理对象为第二闭环管理过程所管理的资源或业务。
其中，收发模块1001，用于接收来自网络管理消费实体的第一消息。其中，第一消息包括第一管理策略信息，第一管理策略信息为第一闭环管理过程对应的管理策略信息，第一闭环管理过程与至少一个第二闭环管理过程之间存在关联关系，第二闭环管理过程对应的管理策略信息为第二管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第一管理策略信息包括一个或多个第一管理策略。
处理模块1002，用于执行第一管理策略信息中的一个或多个第一管理策略。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可选的，网络管理装置1000还可以包括存储模块(图10中未示出)，该存储模块存储有程序或指令。当处理模块1002执行该程序或指令时，使得网络管理装置1000可以执行图3-图5所示的网络管理方法中的第一网络管理生产实体的功能。
需要说明的是，网络管理装置1000可以是第一网络管理生产实体，也可以是可设置于第一网络管理生产实体的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，网络管理装置1000的技术效果可以参考图3-图5所示的网络管理方法的技术效果，此处不再赘述。
在一种可能的设计方案中，图10所示出的网络管理装置1000可适用于图1、图2所示出的网络管理系统中，执行图2-图5所示的网络管理方法中的第二网络管理生产实体的功能。网络管理装置1000用于管理第二闭环管理过程，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，第二被管理对象为第二闭环管理过程所管理的资源或业务，第一闭环管理过程由第一网络管理生产实体管理，第一闭环管理过程是实现第一被 管理对象的SLS目标的管理过程，第一被管理对象为第一闭环管理过程所管理的资源或业务。
其中，收发模块1001，用于接收来自网络管理消费实体的第一消息。其中，第一消息包括第二管理策略信息，第二管理策略信息为第二闭环管理过程对应的管理策略信息，第二闭环管理过程与至少一个第一闭环管理过程之间存在关联关系，第一闭环管理过程对应的管理策略信息为第一管理策略信息，第一管理策略信息与至少一个第二管理策略信息用于实现第一闭环管理过程的保障目标和至少一个第二闭环管理过程的保障目标，第二管理策略信息包括一个或多个第二管理策略。
处理模块1002，用于执行第二管理策略信息中的一个或多个第二管理策略。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可选的，网络管理装置1000还可以包括存储模块(图10中未示出)，该存储模块存储有程序或指令。当处理模块1002执行该程序或指令时，使得网络管理装置1000可以执行图3-图5所示的网络管理方法中的第二网络管理生产实体的功能。
需要说明的是，网络管理装置1000可以是第二网络管理生产实体，也可以是可设置于第二网络管理生产实体的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，网络管理装置1000的技术效果可以参考图3-图5所示的网络管理方法的技术效果，此处不再赘述。
在又一种可能的设计方案中，图10所示出的网络管理装置1000可适用于图1、图2所示出的网络管理系统中，执行图3-图5所示的网络管理方法中网络管理消费实体的功能。
其中，处理模块1002，用于根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息。其中，关联关系信息包括N个闭环管理过程之间的关联关系，N为大于1的整数，闭环管理过程是实现被管理对象的SLS目标的管理过程，被管理对象为闭环管理过程所管理的资源或业务，N个管理策略信息用于实现N个闭环管理过程的保障目标，N个闭环管理过程与N个被管理对象一一对应，一个管理策略信息包括一个或多个管理策略。
收发模块1001，用于向至少两个网络管理生产实体发送第一消息。其中，第一消息包括管理策略信息，网络管理生产实体用于管理闭环管理过程。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可选的，网络管理装置1000还可以包括存储模块(图10中未示出)，该存储模块存储有程序或指令。当处理模块1002执行该程序或指令时，使得网络管理装置1000可以执行图2-图5所示的网络管理方法中网络管理消费实体的功能。
需要说明的是，网络管理装置1000可以是网络管理消费实体，也可以是可设置于网络管理消费实体的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，网络管理装置1000的技术效果可以参考图2-图5所示的网络管理方法的技术效果，此处不再赘述。
在一种可能的设计方案中，图10所示出的网络管理装置1000可适用于图1、图2所 示出的网络管理系统中，执行图6-图7所示的网络管理方法中的NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体，也可以是应用于网络管理生产实体、网络管理消费实体、NSMS消费实体、NSMS生产实体、NSSMS生产实体、管理服务数据库实体、或M/A/D/E管理生产实体的功能。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本申请实施例提供一种网络管理系统。该网络管理系统包括：至少两个网络管理生产实体和网络管理消费实体。至少两个网络管理生产实体可以包括第一网络管理生产实体和至少一个第二网络管理生产实体，其中，第一网络管理生产实体用于执行上述方法实施例中第一网络管理生产实体的动作，第二网络管理生产实体用于执行上述方法实施例中第二网络管理生产实体的动作，具体执行方法和过程可参照上述方法实施例，此处不再赘述。
网络管理消费实体用于执行上述方法实施例中网络管理消费实体的动作，具体执行方法和过程可参照上述方法实施例，此处不再赘述。
本申请实施例提供一种芯片系统，该芯片系统包括逻辑电路和输入/输出端口。其中，逻辑电路可用于实现本申请实施例提供的网络管理方法所涉及的处理功能，输入/输出端口可用于本申请实施例提供的网络管理方法所涉及的收发功能。
示例性地，输入端口可用于实现本申请实施例提供的网络管理方法所涉及的接收功能，输出端口可用于实现本申请实施例提供的网络管理方法所涉及的发送功能。
示例性的，网络管理装置900中的处理器可用于进行，例如但不限于，基带相关处理，网络管理装置900中的收发器可用于进行，例如但不限于，射频收发。上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。例如，处理器可以进一步划分为模拟基带处理器和数字基带处理器。其中，模拟基带处理器可以与收发器集成在同一块芯片上，数字基带处理器可以设置在独立的芯片上。随着集成电路技术的不断发展，可以在同一块芯片上集成的器件越来越多，例如，数字基带处理器可以与多种应用处理器(例如但不限于图形处理器，多媒体处理器等)集成在同一块芯片之上。这样的芯片可以称为系统芯片(system on chip)。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的具体需要。本发明实施例对上述器件的具体实现形式不做限定。
在一种可能的设计中，该芯片系统还包括存储器，该存储器用于存储实现本申请实施例提供的网络管理方法所涉及功能的程序指令和数据。
该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质包括计算机程序或指令，当计算机程序或指令在计算机上运行时，使得本申请实施例提供的网络管理方法被执行。
本申请实施例提供一种计算机程序产品，该计算机程序产品包括：计算机程序或指令，当计算机程序或指令在计算机上运行时，使得本申请实施例提供的网络管理方法被执行。
应理解，在本申请实施例中的处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field  programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件(如电路)、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以 硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种网络管理方法，其特征在于，应用于第一网络管理生产实体，所述第一网络管理生产实体用于管理第一闭环管理过程，所述第一闭环管理过程是实现第一被管理对象的服务等级规范SLS目标的管理过程，所述第一被管理对象为所述第一闭环管理过程所管理的资源或业务，第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，所述第二闭环管理过程由第二网络管理生产实体管理，所述第二被管理对象为所述第二闭环管理过程所管理的资源或业务，包括：
    接收来自网络管理消费实体的第一消息；其中，所述第一消息包括第一管理策略信息，所述第一管理策略信息为所述第一闭环管理过程对应的管理策略信息，所述第一闭环管理过程与至少一个所述第二闭环管理过程之间存在关联关系，所述第二闭环管理过程对应的管理策略信息为第二管理策略信息，所述第一管理策略信息与至少一个所述第二管理策略信息用于实现所述第一闭环管理过程的保障目标和至少一个所述第二闭环管理过程的保障目标，所述第一管理策略信息包括一个或多个第一管理策略；
    执行所述第一管理策略信息中的一个或多个第一管理策略。
  2. 根据权利要求1所述的网络管理方法，其特征在于，所述第一管理策略信息包括一个或多个第一动作指示信息，所述第一动作指示信息用于指示所述第一网络管理生产实体设置所述第一闭环管理过程对应的第一被管理对象的配置信息。
  3. 根据权利要求2所述的网络管理方法，其特征在于，所述第一管理策略信息还包括：一个或多个条件信息、和/或一个或多个事件信息；其中，一个所述条件信息对应至少一个所述第一动作指示信息，一个所述事件信息对应至少一个所述第一动作指示信息。
  4. 根据权利要求2所述的网络管理方法，其特征在于，所述执行所述第一管理策略信息中的一个或多个第一管理策略，包括：
    根据所述第一动作指示信息，设置所述第一闭环管理过程对应的第一被管理对象的配置信息。
  5. 根据权利要求3所述的网络管理方法，其特征在于，所述执行所述第一管理策略信息中的一个或多个第一管理策略，包括：
    在满足所述条件信息、和/或所述事件信息的情况下，根据所述第一动作指示信息，设置所述第一闭环管理过程对应的第一被管理对象的配置信息。
  6. 根据权利要求1-5中任一项所述的网络管理方法，其特征在于，所述第一消息还包括如下一项或多项：所述第二网络管理生产实体的标识、所述第二闭环管理过程的标识、和所述第一闭环管理过程的保障目标。
  7. 根据权利要求6所述的网络管理方法，其特征在于，所述第一管理策略信息还包括一个或多个第一子动作指示信息，所述第一子动作指示信息用于指示所述第一网络管理生产实体向所述第二网络管理生产实体发送第一通知信息和/或第一运行结果，所述执行所述第一管理策略信息中的一个或多个第一管理策略，包括：
    根据所述第二网络管理生产实体的标识和所述第一子动作指示信息，向所述第二网络管理生产实体发送第一协作消息；其中，所述第一协作消息包括所述第一通知信息和/或所述第一运行结果，所述第一通知信息包括所述网络管理消费实体期望所述第二网络管理生产实体采用的所述第二闭环管理过程的保障目标，所述第一运行结果是所述第一网络管理 生产实体根据所述第一动作指示信息获得的，或者，所述第一运行结果是所述第一网络管理生产实体根据所述条件信息和所述事件信息中的一项或多项、以及所述第一动作指示信息获得的。
  8. 根据权利要求2-7中任一项所述的网络管理方法，其特征在于，所述方法还包括：
    向所述网络管理消费实体发送第二消息；其中，所述第二消息包括第一运行结果和/或第一修改请求信息，所述第一运行结果是所述第一网络管理生产实体根据所述第一动作指示信息获得的，或者，所述第一运行结果是所述第一网络管理生产实体根据所述条件信息和所述事件信息中的一项或多项、以及所述第一动作指示信息获得的，所述第一修改请求信息用于请求修改所述第一管理策略信息、和/或所述第一闭环管理过程的保障目标。
  9. 根据权利要求8所述的网络管理方法，其特征在于，所述第一修改请求信息是所述第一网络管理生产实体根据第二通知信息和/或第二运行结果确定的；其中，所述第二通知信息包括所述网络管理消费实体期望所述第一网络管理生产实体采用的所述第一闭环管理过程的保障目标，所述第二运行结果是所述第二网络管理生产实体根据所述第一动作指示信息获得的，或者，所述第二运行结果是所述第二网络管理生产实体根据所述条件信息和所述事件信息中的一项或多项、以及所述第一动作指示信息获得的。
  10. 根据权利要求9所述的网络管理方法，其特征在于，所述方法还包括：
    接收来自所述第二网络管理生产实体的第二协作消息；其中，所述第二协作消息包括所述第二通知信息和/或所述第二运行结果。
  11. 根据权利要求7-10中任一项所述的网络管理方法，其特征在于，所述第一运行结果包括如下一项或多项：第一性能结果、所述第一性能结果对应的第一管理策略信息的标识、所述第一性能结果对应的条件信息、所述第一性能结果对应的事件信息、所述第一性能结果对应的第一动作指示信息；其中，所述第一性能结果包括所述第一被管理对象的性能的结果。
  12. 根据权利要求1-11中任一项所述的网络管理方法，其特征在于，所述第一闭环管理过程的数量为一个或多个。
  13. 根据权利要求1-12中任一项所述的网络管理方法，其特征在于，所述关联关系包括连接关系、或包含关系、或共享关系。
  14. 一种网络管理方法，其特征在于，应用于网络管理消费实体，包括：
    根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息；其中，所述关联关系信息包括所述N个闭环管理过程之间的关联关系，N为大于1的整数，所述闭环管理过程是实现被管理对象的服务等级规范SLS目标的管理过程，所述被管理对象为所述闭环管理过程所管理的资源或业务，所述N个管理策略信息用于实现所述N个闭环管理过程的保障目标，所述N个闭环管理过程与N个所述被管理对象一一对应，一个所述管理策略信息包括一个或多个管理策略；
    向至少两个网络管理生产实体发送第一消息；其中，所述第一消息包括所述管理策略信息，所述网络管理生产实体用于管理所述闭环管理过程。
  15. 根据权利要求14所述的网络管理方法，其特征在于，所述管理策略信息包括一个或多个第一动作指示信息，所述第一动作指示信息用于指示所述网络管理生产实体设置所述闭环管理过程对应的被管理对象的配置信息。
  16. 根据权利要求15所述的网络管理方法，其特征在于，所述管理策略信息还包括：一个或多个条件信息、和/或一个或多个事件信息；其中，一个所述条件信息对应至少一个所述第一动作指示信息，一个所述事件信息对应至少一个所述第一动作指示信息。
  17. 根据权利要求14-16中任一项所述的网络管理方法，其特征在于，接收所述第一消息的实体为第一网络管理生产实体，所述第一网络管理生产实体对应的闭环管理过程为第一闭环管理过程，与所述第一闭环管理过程对应的管理对象为第一被管理对象，与所述第一闭环管理过程存在关联关系的闭环管理过程为第二闭环管理过程，用于管理所述第二闭环管理过程的实体为第二网络管理生产实体，所述第一消息还包括如下一项或多项：所述第二网络管理生产实体的标识、所述第二闭环管理过程的标识、和所述第一闭环管理过程的保障目标。
  18. 根据权利要求17所述的网络管理方法，其特征在于，所述管理策略信息还包括一个或多个第一子动作指示信息，所述第一子动作指示信息用于指示所述第一网络管理生产实体向所述第二网络管理生产实体发送第一通知信息和/或第一运行结果，所述第一通知信息包括所述网络管理消费实体期望所述第二网络管理生产实体采用的所述第二闭环管理过程的保障目标，所述第一运行结果是所述第一网络管理生产实体根据所述第一动作指示信息获得的，或者，所述第一运行结果是所述第一网络管理生产实体根据所述条件信息和所述事件信息中的一项或多项、以及所述第一动作指示信息获得的。
  19. 根据权利要求14-18中任一项所述的网络管理方法，其特征在于，所述方法还包括：
    接收来自所述网络管理生产实体的第二消息；其中，所述第二消息包括第一运行结果和/或第一修改请求信息，所述第一运行结果是所述网络管理生产实体根据所述第一动作指示信息获得的，或者，所述第一运行结果是所述网络管理生产实体根据所述条件信息和所述事件信息中的一项或多项、以及所述第一动作指示信息获得的，所述第一修改请求信息用于请求修改所述管理策略信息、和/或所述闭环管理过程的保障目标。
  20. 根据权利要求19所述的网络管理方法，其特征在于，所述方法还包括：
    根据至少一个所述网络管理生产实体的所述第一运行结果和/或至少一个所述网络管理生产实体的所述第一修改请求信息，确定新的管理策略信息和/或所述闭环管理过程的新的保障目标。
  21. 根据权利要求14-20中任一项所述的网络管理方法，其特征在于，所述N个闭环管理过程的保障目标是所述网络管理消费实体根据所述N个被管理对象的需求信息确定的。
  22. 根据权利要求14-21中任一项所述的网络管理方法，其特征在于，所述关联关系信息是所述网络管理消费实体根据所述N个闭环管理过程分别对应的被管理对象之间的关联关系确定的。
  23. 根据权利要求14-22中任一项所述的网络管理方法，其特征在于，所述网络管理生产实体管理的闭环管理过程的数量为一个或多个。
  24. 根据权利要求14-23中任一项所述的网络管理方法，其特征在于，所述关联关系包括连接关系、或包含关系、或共享关系。
  25. 一种网络管理装置，其特征在于，所述网络管理装置包括用于执行如权利要求1至13中任一项所述方法的单元或模块。
  26. 一种网络管理装置，其特征在于，所述网络管理装置包括用于执行如权利要求14至24中任一项所述方法的单元或模块。
  27. 一种网络管理装置，其特征在于，所述网络管理装置包括：处理器；所述处理器，用于执行如权利要求1-24中任一项所述的网络管理方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-24中任一项所述的网络管理方法被执行。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-24中任一项所述的网络管理方法被执行。
  30. 一种网络管理系统，其特征在于，所述网络管理系统包括网络管理消费实体、第一网络管理生产实体、和至少一个第二网络管理生产实体，所述第一网络管理生产实体用于管理第一闭环管理过程，所述第二网络管理生产实体用于管理第二闭环管理过程，所述第一闭环管理过程是实现第一被管理对象的服务等级规范SLS目标的管理过程，所述第二闭环管理过程是实现第二被管理对象的SLS目标的管理过程，所述第一被管理对象为所述第一闭环管理过程所管理的资源或业务，所述第二被管理对象为所述第二闭环管理过程所管理的资源或业务；其中，
    所述网络管理消费实体，用于根据关联关系信息和N个闭环管理过程的保障目标，确定N个管理策略信息；其中，所述关联关系信息包括所述N个闭环管理过程之间的关联关系，N为大于1的整数，所述N个管理策略信息用于实现所述N个闭环管理过程的保障目标，所述N个闭环管理过程包括所述第一闭环管理过程和至少一个所述第二闭环管理过程，所述N个管理策略信息包括第一管理策略信息和至少一个第二管理策略信息，所述第一管理策略信息包括一个或多个第一管理策略，所述第二管理策略信息包括一个或多个第二管理策略；
    所述网络管理消费实体，还用于向所述第一网络管理生产实体发送所述第一管理策略信息，向所述至少一个第二网络管理生产实体发送所述至少一个第二管理策略信息；
    所述第一网络管理生产实体，用于接收来自所述网络管理消费实体的所述第一管理策略信息；
    所述第一网络管理生产实体，还用于执行所述第一管理策略信息中的一个或多个第一管理策略；
    所述第二网络管理生产实体，用于接收来自所述网络管理消费实体的所述第二管理策略信息；
    所述第二网络管理生产实体，还用于执行所述第二管理策略信息中的一个或多个第二管理策略。
PCT/CN2022/121771 2021-09-30 2022-09-27 网络管理方法及装置 WO2023051536A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111163413.8 2021-09-30
CN202111163413.8A CN115915173A (zh) 2021-09-30 2021-09-30 网络管理方法及装置

Publications (1)

Publication Number Publication Date
WO2023051536A1 true WO2023051536A1 (zh) 2023-04-06

Family

ID=85729555

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/121771 WO2023051536A1 (zh) 2021-09-30 2022-09-27 网络管理方法及装置

Country Status (2)

Country Link
CN (1) CN115915173A (zh)
WO (1) WO2023051536A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021064254A1 (en) * 2019-10-04 2021-04-08 NEC Laboratories Europe GmbH Data analytics-based sls assurance solution utilising ue qoe measurement
CN113132132A (zh) * 2019-12-30 2021-07-16 华为技术有限公司 一种切片控制方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021064254A1 (en) * 2019-10-04 2021-04-08 NEC Laboratories Europe GmbH Data analytics-based sls assurance solution utilising ue qoe measurement
CN113132132A (zh) * 2019-12-30 2021-07-16 华为技术有限公司 一种切片控制方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Architecture framework (Release 16)", 3GPP TS 28.533, no. V16.5.1, 30 September 2020 (2020-09-30), pages 1 - 30, XP051961192 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Management services for communication service assurance; Stage 2 and stage 3 (Release 17)", 3GPP TS 28.536, no. V17.0.0, 24 June 2021 (2021-06-24), pages 1 - 24, XP052029620 *
ERICSSON: "Discussion paper around aspects on Closed Loop SLS Assurance architecture", 3GPP TSG-SA5 MEETING 129E, S5-201354, 14 February 2020 (2020-02-14), XP051855916 *

Also Published As

Publication number Publication date
CN115915173A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
US20220014963A1 (en) Reinforcement learning for multi-access traffic management
US11146462B2 (en) Network slice management method, device, and system
US10856183B2 (en) Systems and methods for network slice service provisioning
US10742522B2 (en) Creation and modification of shareable slice instances
US20220124560A1 (en) Resilient radio resource provisioning for network slicing
US20220086218A1 (en) Interoperable framework for secure dual mode edge application programming interface consumption in hybrid edge computing platforms
DE102022202872A1 (de) Neuronales graphennetzwerk und bestärkendes-lernen-techniken zur verbindungsverwaltung
US20220248226A1 (en) Dynamic access policy provisioning in a device fog
WO2018205931A1 (en) Service provision steps using slices and associated definitions
US20210274418A1 (en) Information Transmission Method and Apparatus
US10848366B2 (en) Network function management method, management unit, and system
WO2019137516A1 (zh) 网络切片部署方法及其装置
DE102023200988A1 (de) Dynamische latenz-responsive cache-verwaltung
KR102500594B1 (ko) 통신 네트워크에서의 서비스 계층 메시지 템플릿들
Li et al. Federated orchestration for network slicing of bandwidth and computational resource
CN112930663B (zh) 用于处理5g网络中的管理对象优先级的装置和方法
WO2023051536A1 (zh) 网络管理方法及装置
US11134365B2 (en) Resource link management at service layer
CN110875945B (zh) 用于在通用服务实体上进行任务处理的方法、装置和介质
WO2019100924A1 (zh) 一种网络性能保障方法及装置
Khalil et al. Iot service qos guarantee using qbaiot wireless access method
WO2023003686A1 (en) Multi- access edge computing (mec) application registry in mec federation
WO2020063521A1 (zh) 能力上报方法及装置
US20220376995A1 (en) Method and apparatus for abstracting network resources in a mobile communications network
García‐Rois et al. Evaluating management and orchestration impact on closed‐loop orchestration delay

Legal Events

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

Ref document number: 22874921

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022874921

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022874921

Country of ref document: EP

Effective date: 20240402