WO2024078519A1 - 自治网络的自治方法和装置 - Google Patents

自治网络的自治方法和装置 Download PDF

Info

Publication number
WO2024078519A1
WO2024078519A1 PCT/CN2023/123905 CN2023123905W WO2024078519A1 WO 2024078519 A1 WO2024078519 A1 WO 2024078519A1 CN 2023123905 W CN2023123905 W CN 2023123905W WO 2024078519 A1 WO2024078519 A1 WO 2024078519A1
Authority
WO
WIPO (PCT)
Prior art keywords
autonomous
maintenance
capability information
workflow
network
Prior art date
Application number
PCT/CN2023/123905
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 WO2024078519A1 publication Critical patent/WO2024078519A1/zh

Links

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/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the technical field of communication networks, and in particular to an autonomous method and device for an autonomous network.
  • autonomous technology The application of automation or intelligent technology (hereinafter referred to as autonomous technology) in communication networks has gradually become the focus of industry attention and research hotspot, in order to solve the network operation and maintenance problems encountered by communication networks by introducing autonomous technology (such as artificial intelligence, machine learning, big data analysis, digital twins, etc.).
  • autonomous technology such as artificial intelligence, machine learning, big data analysis, digital twins, etc.
  • the operator management system may realize some autonomous service requirements, and the equipment vendor management system can realize the remaining autonomous service requirements. Therefore, operators will have different autonomous service requirements for equipment vendor management systems in different scenarios, and the equipment vendors need to provide adaptive autonomous capability information to meet them. The more autonomous capability information the equipment vendor system has, the better. Therefore, how to meet the differentiated autonomous service requirements of equipment vendor management systems has become an urgent problem to be solved.
  • the embodiments of the present application provide an autonomous method and device for an autonomous network.
  • an embodiment of the present application provides an autonomous method for an autonomous network, the method being applied to a first device, the method comprising:
  • the autonomous capability information represents information on autonomous capability for implementing an operation and maintenance workflow
  • An autonomous service requirement of the operation and maintenance workflow is sent to the second device, wherein the autonomous service requirement is associated with the autonomous capability information, and the autonomous service requirement is used to instruct the second device to provide an autonomous service of the operation and maintenance workflow.
  • the first device can accurately determine the autonomous service requirements that can be executed by the second device based on the autonomous capability information provided by the second device, thereby improving efficiency and avoiding the second device from opposing negotiation and challenging the autonomous service requirements; on the other hand, by sending the autonomous service requirements to the second device through the first device, the second device can provide autonomous services based on the differentiated requirements of the first device for the operation and maintenance workflow.
  • the method further comprises:
  • the first device can quickly obtain the result of whether the autonomous service demand can be provided, so as to make timely adjustments and improve the real-time performance of autonomy.
  • the method further includes: the operation and maintenance workflow is a target operation and maintenance workflow; before receiving the autonomous capability information sent by the second device, the method further includes:
  • An operation and maintenance step requirement is sent to the second device, wherein the operation and maintenance step requirement is used to request the autonomous capability information, and the autonomous capability information is information on the autonomous capability that satisfies the operation and maintenance step requirement and is used to implement the target operation and maintenance workflow.
  • the first device sends the operation and maintenance step requirements to the second device to obtain the autonomous capability information, which can accurately obtain the autonomous capability information corresponding to the operation and maintenance step requirements and avoid obtaining invalid autonomous capability information.
  • the autonomous management function deployed by the first device supports partial operation and maintenance step requirements for implementing the target operation and maintenance workflow
  • the operation and maintenance step requirements sent to the second device are operation and maintenance step requirements in addition to the partial operation and maintenance step requirements supported by the autonomous management function for implementing the target operation and maintenance workflow.
  • the operation and maintenance step requirements sent by the first device to the second device are as follows: Implementing some of the operation and maintenance step requirements beyond the requirements can ensure reasonable division of labor and coordination between the first device and the second device for the target operation and maintenance workflow, and avoid duplicate implementation.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and supported scenarios, and the autonomous state requirements are used to characterize the degree of participation of the second device in the operation and maintenance steps.
  • the autonomous capability information is multiple; after receiving the autonomous capability information sent by the second device, the method further includes:
  • the operation and maintenance step requirement of the first device determining the autonomous capability information corresponding to the operation and maintenance step requirement from the multiple autonomous capability information, wherein the operation and maintenance step requirement is the autonomous capability requirement for realizing the target operation and maintenance workflow in the operation and maintenance workflow;
  • the autonomous service requirement is determined based on the acquired autonomous capability information corresponding to the operation and maintenance step requirement.
  • the autonomous capability information includes: an autonomous capability identifier, the name of the operation and maintenance workflow, supported autonomous network levels, operation and maintenance task capability information corresponding to the supported autonomous network levels, and at least one of supported scenario information.
  • the autonomous service requirement includes: an autonomous service requirement identifier, the name of the operation and maintenance workflow, an associated autonomous capability identifier, an autonomous network level, scenario information, and at least one of a target autonomous performance indicator.
  • an embodiment of the present application further provides an autonomous method of an autonomous network, the method being applied to a second device, the method comprising:
  • autonomous capability information represents information on autonomous capabilities for implementing an operation and maintenance workflow
  • An autonomous service that executes the operation and maintenance workflow indicated by the autonomous service requirement.
  • the method further comprises:
  • a feasibility assessment result is sent to the first device, wherein the feasibility assessment result is used to indicate whether the second device supports the autonomous service requirement.
  • the operation and maintenance workflow is a target operation and maintenance workflow; before sending the autonomous capability information to the first device, the method further includes:
  • An operation and maintenance step requirement is received from the first device, wherein the operation and maintenance step requirement is used to request the autonomous capability information, and the autonomous capability information is information on the autonomous capability that satisfies the operation and maintenance step requirement and is used to implement the target operation and maintenance workflow.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and scenarios supported by the autonomous capabilities, and the autonomous state requirements are used to characterize the degree of participation of the second device in the operation and maintenance steps.
  • the autonomous capability information includes: an autonomous capability identifier, the name of the operation and maintenance workflow, supported autonomous network levels, operation and maintenance task capability information corresponding to the supported autonomous network levels, and at least one of supported scenario information.
  • the autonomous service requirement includes: an autonomous service requirement identifier, the name of the operation and maintenance workflow, an associated autonomous capability identifier, an autonomous network level, scenario information, and at least one of a target autonomous performance indicator.
  • an embodiment of the present application further provides an autonomous method for an autonomous network, the method comprising:
  • the second device sends autonomous capability information to the first device, wherein the autonomous capability information represents information of autonomous capability for implementing the operation and maintenance workflow;
  • the first device sends an autonomous service requirement to the second device, wherein the autonomous service requirement is associated with the autonomous capability information;
  • the second device executes the autonomous service of the operation and maintenance workflow indicated by the autonomous service requirement.
  • the method further comprises:
  • the second device sends a feasibility assessment result to the first device, wherein the feasibility assessment result is used to characterize the Whether the second device supports the autonomous service requirement.
  • the operation and maintenance workflow is a target operation and maintenance workflow; before the second device sends the autonomous capability information to the first device, the method further includes:
  • the first device sends an operation and maintenance step requirement to the second device, wherein the operation and maintenance step requirement is used to request the autonomous capability information, and the autonomous capability information is information on the autonomous capability that satisfies the operation and maintenance step requirement and is used to implement the target operation and maintenance workflow.
  • the autonomous management function deployed by the first device supports partial operation and maintenance step requirements for implementing the target operation and maintenance workflow
  • the operation and maintenance step requirements sent to the second device are operation and maintenance step requirements in addition to the partial operation and maintenance step requirements supported by the autonomous management function for implementing the target operation and maintenance workflow.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and scenarios supported by the autonomous capabilities, and the autonomous state requirements are used to characterize the degree of participation of the second device in the operation and maintenance steps.
  • the autonomous capability information is multiple; the method further includes:
  • the first device determines the autonomous capability information corresponding to the operation and maintenance step requirements from the multiple autonomous capability information according to the operation and maintenance step requirements of the first device, where the operation and maintenance step requirements are the autonomous capability requirements for implementing the target operation and maintenance workflow in the operation and maintenance workflow.
  • the autonomous capability information includes: an autonomous capability identifier, the name of the operation and maintenance workflow, supported autonomous network levels, operation and maintenance task capability information corresponding to the supported autonomous network levels, and at least one of supported scenario information.
  • the autonomous service requirement includes: an autonomous service requirement identifier, the name of the operation and maintenance workflow, an associated autonomous capability identifier, an autonomous network level, scenario information, and at least one of a target autonomous performance indicator.
  • an embodiment of the present application further provides an autonomous device of an autonomous network, the device comprising:
  • a first receiving unit configured to receive autonomous capability information sent by a second device, wherein the autonomous capability information represents information on autonomous capabilities for implementing an operation and maintenance workflow;
  • the first sending unit is used to send the autonomous service requirement of the operation and maintenance workflow to the second device, wherein the autonomous service requirement is associated with the autonomous capability information, and the autonomous service requirement is used to instruct the second device to provide autonomous services for the operation and maintenance workflow.
  • an embodiment of the present application further provides an autonomous device of an autonomous network, the device comprising:
  • a third sending unit configured to send autonomous capability information to the first device, wherein the autonomous capability information represents information on autonomous capability for implementing an operation and maintenance workflow;
  • a third receiving unit configured to receive an autonomous service requirement sent by the first device, wherein the autonomous service requirement is associated with the autonomous capability information
  • An execution unit is used to execute the autonomous service of the operation and maintenance workflow indicated by the autonomous service requirement.
  • an embodiment of the present application further provides an autonomous system of an autonomous network, the system comprising a first device and a second device in communication connection; wherein:
  • the first device is used to execute the method described in any embodiment of the first aspect above;
  • the second device is used to execute the method described in any embodiment of the second aspect above.
  • an embodiment of the present application further provides a computer-readable storage medium, on which computer instructions are stored.
  • the computer instructions are executed by a processor, the method described in any of the above embodiments is executed.
  • an embodiment of the present application further provides an electronic device, including:
  • the memory stores computer instructions that can be executed by the at least one processor.
  • the computer instructions are executed by the at least one processor so that the method described in any one of the above embodiments is executed.
  • an embodiment of the present application further provides a computer program product, which, when executed on a processor, enables the method described in any of the above embodiments to be executed.
  • an embodiment of the present application further provides a chip, the chip comprising a processor and a memory, the memory being used for The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method described in any of the above embodiments.
  • FIG1 is a schematic diagram of a grading standard for autonomous network levels according to an embodiment of the present application.
  • FIG2 is a schematic diagram of an application scenario of an autonomous method for an autonomous network according to an embodiment of the present application
  • FIG3 is a schematic diagram of an autonomous system of an autonomous network according to an embodiment of the present application.
  • FIG4 is a schematic diagram of a flow chart of an autonomous method for an autonomous network according to an embodiment of the present application.
  • FIG5 is a schematic diagram of a flow chart of an autonomous method for an autonomous network according to another embodiment of the present application.
  • FIG6 is a schematic diagram of a flow chart of an autonomous method for an autonomous network according to another embodiment of the present application.
  • FIG7 is a schematic diagram of the operation and maintenance step requirements of the quality optimization sub-operation and maintenance workflow according to an embodiment of the present application
  • FIG8 is a schematic flow chart of an autonomous method for an autonomous network according to another embodiment of the present application.
  • FIG9 is a schematic diagram of an autonomous device of an autonomous network according to an embodiment of the present application.
  • FIG10 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • FIG11 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • FIG12 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • FIG13 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • FIG. 14 is a schematic diagram of the structure of an electronic device according to an embodiment of the present application.
  • the communication network of the first device (such as the operator's communication management system, which can be called the operator management system) is becoming more and more complex, resulting in an increase in the difficulty of network operation and maintenance.
  • the operator management system which can be called the operator management system
  • autonomous technology The application of automation or intelligent technology (hereinafter referred to as autonomous technology) in communication networks has gradually become the focus of industry attention and research hotspot, in order to solve the network operation and maintenance problems encountered by communication networks by introducing autonomous technology (such as artificial intelligence, machine learning, big data analysis, digital twins, etc.).
  • autonomous technology such as artificial intelligence, machine learning, big data analysis, digital twins, etc.
  • autonomous Network the communication network that has introduced autonomous technology can be called an autonomous network (Autonomous Network), which means that the first device can achieve self-control through autonomous capabilities with as little human intervention as possible.
  • Autonomous technology can be applied to multiple operation and maintenance workflows in the life cycle of communication networks (such as telecommunication systems), including network planning, network deployment, network optimization, business operations, etc. It can reduce manual operations, reduce network operation and maintenance costs (Operating Expense, OPEX), and improve network operation and maintenance efficiency.
  • communication networks such as telecommunication systems
  • OPEX network operation and maintenance costs
  • the operation and maintenance workflow is an operation and maintenance step for achieving the network operation and maintenance purpose in the communication network, and the operation and maintenance step is implemented by one or more operation and maintenance tasks.
  • Different second devices such as the equipment vendor's communication management system, which can be called the equipment vendor management system
  • Operators need a unified set of grading standards to describe and evaluate the autonomous capabilities of the first device in different scenarios, and then guide the first device to introduce more autonomous capabilities or the most appropriate autonomous capabilities.
  • the autonomous network level is determined based on the grading standard, which refers to the autonomous capability level of the autonomous network.
  • the grading standard of the autonomous network level describes the autonomous capabilities of the operation and maintenance workflow (such as network planning, network deployment, network maintenance and network optimization workflows), and defines an autonomous network level evaluation method based on the grading standard of the autonomous network level.
  • the operator can evaluate and score the first device based on the evaluation method to obtain the corresponding autonomous network level score.
  • the autonomous network level of the first device is determined based on the degree of participation of the person and the first device in each operation and maintenance step in the operation and maintenance workflow.
  • the autonomous network level of the network optimization workflow can be determined as 6 levels, such as level 0 to level 5.
  • the autonomous network level includes the contents of the five operation and maintenance steps: intent management, perception, analysis, decision-making, and execution, and the intent management operation and maintenance step can be implemented by the monitoring rules and optimization strategy generation operation and maintenance tasks, and the network/business assurance intent evaluation operation and maintenance tasks; the perception operation and maintenance task type step can be implemented by the data collection operation and maintenance tasks; the analysis operation and maintenance step can be implemented by the performance anomaly identification operation and maintenance tasks, the performance degradation prediction operation and maintenance tasks, the performance problem root cause analysis operation and maintenance tasks, and the optimization solution generation operation and maintenance tasks; the decision operation and maintenance step can be implemented by the optimization solution evaluation and determination operation and maintenance tasks; the execution operation and maintenance step can be implemented by the optimization solution execution operation and maintenance tasks.
  • the participation degree of people and the first device in the same operation and maintenance step is different in different autonomous network levels.
  • the autonomous network level is level 0
  • the ten operation and maintenance steps are completed by people alone
  • the autonomous network level is level 5
  • the ten operation and maintenance steps are completed by the first device alone.
  • the autonomous network level is level 4
  • the intention management operation and maintenance steps in the operation and maintenance steps are completed by people and the first device together
  • the perception operation and maintenance steps, analysis operation and maintenance steps, decision-making operation and maintenance steps, and execution operation and maintenance steps in the operation and maintenance steps are completed by the first device respectively.
  • the participation degree of people and first devices at other levels please refer to Figure 1, and they will not be listed here one by one.
  • the first device may realize some autonomous service requirements, and the second device can realize the remaining autonomous service requirements. Therefore, the operator will have different autonomous service requirements for the second device in different scenarios, and the equipment manufacturer needs to provide adaptive autonomous capability information to meet them. It is not the case that the more autonomous capability information the equipment manufacturer's system has, the better. Therefore, how to meet the differentiated autonomous service requirements of the first device has become an urgent problem to be solved.
  • the second device sends autonomous capability information to the first device, where the autonomous capability information represents information used to implement the autonomous capability of the operation and maintenance workflow; the first device generates an autonomous service requirement based on the autonomous capability information, and sends the autonomous service requirement to the second device, where the autonomous service requirement is used to instruct the second device to provide autonomous services for the operation and maintenance workflow; the second device executes the autonomous service.
  • the present application provides an autonomous network autonomy method, which can be applied to the autonomous network shown in Figure 2.
  • the autonomous network includes a service operation unit, a cross-domain management function unit, a domain management function unit, and a network element.
  • the business operation unit also known as the communication service management function unit, can provide functions and management services such as billing, settlement, accounting, customer service, business, network monitoring, communication service life cycle management, business intent translation, etc.
  • functions and management services such as billing, settlement, accounting, customer service, business, network monitoring, communication service life cycle management, business intent translation, etc.
  • the cross-domain management function unit which may also be referred to as the network management function unit (network management function, NMF), provides one or more of the following functions or management services: network lifecycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, network optimization function, translation of the network intent of the communication service provider (intent from communication service provider, intent-CSP), translation of the network intent of the communication service user (intent from communication service consumer, intent-CSC), etc.
  • the network may include one or more network elements, subnetworks or network slices.
  • the cross-domain management function unit may be a network slice management function (network slice management function, NSMF), or a management data analytical function (management data analytical function, MDAF), or a cross-domain self-organization network function (SON-function), or a cross-domain intent management function unit.
  • network slice management function network slice management function
  • MDAF management data analytical function
  • SON-function cross-domain self-organization network function
  • the domain management function unit which may also be referred to as a subnetwork management function unit (subnetwork management function, subnetwork NMF) or a network element management function unit (network element/function management function), provides one or more of the following functions or management services: lifecycle management of subnetworks or network elements, deployment of subnetworks or network elements, fault management of subnetworks or network elements, performance management of subnetworks or network elements, assurance of subnetworks or network elements, optimization management of subnetworks or network elements, intent translation of subnetworks or network elements, etc.
  • the subnetwork here includes one or more network elements.
  • the subnetwork may also include one or more subnetworks, that is, one or more subnetworks form a subnetwork with a larger coverage area.
  • the subnetwork here may also include one or more network slice subnetworks.
  • the subnetwork may include one of the following descriptions:
  • a network in a certain technical domain such as wireless access network, core network, transmission network, etc.
  • a network of a certain standard such as the Global System for Mobile Communications (GSM) network, the Long Term Evolution (LTE) network, the fifth generation mobile communication technology (5G) network, etc.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • 5G fifth generation mobile communication technology
  • a network provided by a certain equipment manufacturer such as the network provided by equipment manufacturer X.
  • the network in a certain geographical area such as the network of factory A, the network of prefecture-level city B, etc.
  • Network elements are entities that provide network services, including core network elements, access network elements, etc.
  • core network elements may include but are not limited to access and mobility management function (AMF) entity, session management function (SMF) entity, policy control function (PCF) entity, network data analysis function (NWDAF) entity, network repository function (NRF), gateway, etc.
  • Access network elements may include but are not limited to: various base stations (such as next generation node B (gNB), evolved Node B (eNB), central unit control panel (CUCP), central unit (CU), distributed unit (DU), central unit user panel (CUUP), etc.
  • gNB next generation node B
  • eNB evolved Node B
  • CUCP central unit control panel
  • CU central unit
  • DU central unit user panel
  • CUUP central unit user panel
  • the scope of an autonomous network can include the following three situations:
  • a single-domain autonomous network includes network elements and domain management functional units.
  • a cross-domain autonomous network includes: network elements, domain management functional units, and cross-domain management functional units.
  • Business autonomous network the business autonomous network includes: network elements, domain management functional units, cross-domain management functional units, and business operation units.
  • the focus is on management service providers (Management Service Producer, MnS Producer) and management service consumers (Management Service Consumer, MnS Consumer).
  • the business operation unit is a management service provider
  • the business operator unit can be a management service consumer, that is, the business operation unit is the second device, and the business operator unit is the first device;
  • the management service is a management service provided by the above-mentioned cross-domain management function unit, the cross-domain management function unit is the management service provider, and the business operation unit is a management service consumer, that is, the cross-domain management function unit is the second device, and the business operator unit is the first device;
  • the management service is a management service provided by the above-mentioned domain management function unit, the domain management function unit is the management service provider, and the cross-domain management function unit or the business operation unit is the management service consumer, that is, the
  • the autonomous system of the autonomous network used to execute the autonomous method of the autonomous network of the present application mainly involves an autonomous network monitoring module, an autonomous network execution module, and a logical interface, as shown in Figure 3.
  • the autonomous network monitoring module is the first device, which is used to generate the operation and maintenance step requirements of the autonomous network and monitor the execution of the autonomous network;
  • the autonomous network execution module is the second device, which is used to provide and execute the autonomous capabilities of the autonomous network;
  • the logical interface is the logical interface between the autonomous network monitoring module and the autonomous network execution module, which is used for the interface for autonomous capability negotiation and monitoring.
  • the scope of the autonomous network can include three situations. Therefore, for different scopes of autonomous networks, the deployment scenarios of the autonomous network monitoring module and the autonomous network execution module may be different, for example:
  • the scope of the autonomous network includes a single-domain autonomous network.
  • the autonomous network execution module ie, the second device
  • the autonomous network monitoring module ie, the first device
  • the scope of the autonomous network includes cross-domain autonomous networks.
  • the autonomous network execution module ie, the second device
  • the autonomous network monitoring module ie, the first device
  • the scope of the autonomous network includes the business autonomous network.
  • the autonomous network execution module i.e., the second device
  • the autonomous network monitoring module i.e., the first device
  • a third-party system outside the autonomous network such as an enterprise system, etc.
  • the autonomous network monitoring module is the management service consumer, and the autonomous network execution module is Management service provider, the logical interface is the interface for autonomous capability negotiation and monitoring services.
  • the present application provides an autonomous method for an autonomous network, which can be applied to a first device.
  • FIG. 4 is a flow chart of an autonomous method for an autonomous network according to an embodiment of the present application. As shown in FIG. 4, the method includes:
  • S401 Receive autonomous capability information sent by a second device, wherein the autonomous capability information represents information on autonomous capabilities used to implement an operation and maintenance workflow.
  • the execution subject of this embodiment may be an autonomous device of an autonomous network, and the device may be applied to the first device, such as the device may be the first device, or at least part of the components of the first device (may be physical components or virtual components, which are not limited in this embodiment).
  • the first device may be a computer or a computer cluster, a server or a server cluster, or a terminal device, etc., which are not limited in this embodiment.
  • the information of the autonomous capability may be referred to as autonomous capability information.
  • the autonomous capability may be used to implement the operation and maintenance workflow. Accordingly, the autonomous capability information may be understood as the information of the autonomous capability used to implement the operation and maintenance workflow.
  • S402 Sending an autonomous service requirement of the operation and maintenance workflow to the second device, wherein the autonomous service requirement is associated with the autonomous capability information, and the autonomous service requirement is used to instruct the second device to provide an autonomous service of the operation and maintenance workflow.
  • the association between the autonomous service demand and the autonomous capability information can be understood as follows: the autonomous service demand is determined based on the autonomous capability information.
  • the first device can determine the autonomous service requirements for implementing the autonomous service based on the autonomous capability information, so as to send the autonomous service requirements to the second device, and the second device performs the autonomous service, thereby determining whether the second device can support the autonomous service requirements.
  • the first device can accurately determine the autonomous service requirements that can be executed by the second device based on the autonomous capability information provided by the second device, thereby improving efficiency and avoiding the second device from opposing negotiation and challenging the autonomous service requirements; on the other hand, by sending the autonomous service requirements to the second device through the first device, the second device can provide autonomous services based on the differentiated requirements of the first device for the operation and maintenance workflow.
  • the present application provides an autonomous method for an autonomous network, which can be applied to a second device.
  • FIG5 is a flow chart of an autonomous method for an autonomous network according to another embodiment of the present application. As shown in FIG5 , the method includes:
  • S501 Sending autonomous capability information to a first device, wherein the autonomous capability information represents information on autonomous capabilities for implementing an operation and maintenance workflow.
  • the execution subject of this embodiment may be an autonomous device of an autonomous network, and the device may be applied to a second device, such as the device may be at least a part of the components of the second device (may be a physical component or a virtual component, which is not limited in this embodiment).
  • the second device may be a computer or a computer cluster, a server or a server cluster, a terminal device, etc., which is not limited in this embodiment.
  • the information of the autonomous capability may be referred to as autonomous capability information.
  • the autonomous capability may be used to implement the operation and maintenance workflow. Accordingly, the autonomous capability information may be understood as the information of the autonomous capability used to implement the operation and maintenance workflow.
  • S502 Receive an autonomous service requirement sent by a first device, wherein the autonomous service requirement is associated with autonomous capability information.
  • the autonomous service requirement is determined by the first device according to the autonomous capability information.
  • S503 Execute the autonomous service of the operation and maintenance workflow indicated by the autonomous service requirement.
  • the first device can determine the autonomous service requirements for implementing the autonomous service based on the autonomous capability information, so as to send the autonomous service requirements to the second device, and the second device performs the autonomous service, thereby determining whether the second device can support the autonomous service requirements.
  • Figure 6 is a flow chart of an autonomous method of an autonomous network in another embodiment of the present application. As shown in Figure 6, the method includes:
  • the first device determines the operation and maintenance step requirements of the target operation and maintenance workflow, wherein the operation and maintenance step requirements are used to request autonomous capability information, and the autonomous capability information is information on the autonomous capability for realizing the target operation and maintenance workflow that satisfies the operation and maintenance step requirements.
  • the autonomous capability information is autonomous capability information that meets two conditions, one condition is to meet the operation and maintenance step requirements, and the other condition is to achieve the autonomy of the target operation and maintenance workflow.
  • the target operation and maintenance workflow is the operation and maintenance workflow that the first device needs to achieve.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and supported scenarios, and the autonomous state requirements are the requirements for the degree of participation of the second device in the operation and maintenance steps.
  • the operation and maintenance steps are implemented based on autonomous capabilities.
  • the operation and maintenance workflow can be one or more of a network planning workflow, a network deployment workflow, a network maintenance workflow, a network optimization workflow, etc.
  • the target operation and maintenance workflow can be at least part of the operation and maintenance workflow, that is, the target operation and maintenance workflow can be at least part of the workflows mentioned above.
  • the target operation and maintenance workflow can be a network planning workflow, a network deployment workflow, a network maintenance workflow, or a network optimization workflow. This embodiment does not limit the content of the target operation and maintenance workflow.
  • the target operation and maintenance workflow may be the overall workflow as described above, such as a network maintenance workflow.
  • the target operation and maintenance workflow may also be a partial sub-operation and maintenance workflow in which the overall workflow is split into multiple sub-operation and maintenance workflows.
  • the network maintenance workflow may include: monitoring troubleshooting sub-operation and maintenance workflow, network inspection sub-operation and maintenance workflow.
  • the target operation and maintenance workflow may be a network maintenance workflow, a monitoring troubleshooting sub-operation and maintenance workflow, or a network inspection sub-operation and maintenance workflow.
  • the network optimization workflow may include: a quality optimization sub-operation and maintenance workflow, an energy efficiency optimization sub-operation and maintenance workflow, etc.
  • the target operation and maintenance workflow may be a network optimization workflow, a quality optimization sub-operation and maintenance workflow, or an energy efficiency optimization sub-operation and maintenance workflow.
  • Each operation and maintenance workflow or sub-operation and maintenance workflow includes at least one operation and maintenance step (also called core capability).
  • the network planning workflow may include four operation and maintenance steps: intent translation, demand analysis and prediction, planning and simulation, and network design;
  • the monitoring and troubleshooting workflow may include three operation and maintenance steps: fault and hidden danger identification, fault demarcation and positioning, and fault handling;
  • the quality optimization workflow may include five operation and maintenance steps: intent translation, quality problem identification, quality problem positioning, solution generation and decision-making, and solution implementation effect verification.
  • This step can be understood as: the operation and maintenance workflow includes one or more operation and maintenance steps.
  • the first device can determine the operation and maintenance step requirements that the second device needs to support for the target operation and maintenance workflow.
  • the operation and maintenance step requirement describes the operation and maintenance steps that the first device wants the second device to support, the autonomous state requirements corresponding to the operation and maintenance steps, and the supported scenarios.
  • the autonomous state requirement describes the degree of participation of the second device in the operation and maintenance steps.
  • the autonomous state requirement may include:
  • Autonomous state requirement 1 The operation and maintenance steps are implemented manually; Autonomous state requirement 2: The second device implements the operation and maintenance steps based on manually formulated rules; Autonomous state requirement 3: The second device dynamically generates rules based on manually formulated strategies and implements the operation and maintenance steps; Autonomous state requirement 4: The second device dynamically generates rules based on artificial intelligence (AI)/machine learning (ML) models and implements the operation and maintenance steps; Autonomous state requirement 5: The second device can self-learn AI/ML models and implement the operation and maintenance steps.
  • AI artificial intelligence
  • ML machine learning
  • this embodiment does not limit the number of autonomous state requirements that the operation and maintenance steps can support, and the above examples are only used to exemplify the autonomous state requirements that the operation and maintenance steps may support.
  • the autonomous status requirements of the operation and maintenance steps supported by the second device describe the degree to which the second device participates in implementing the operation and maintenance steps.
  • the person in the above example can generally refer to implementers other than the second device, such as operation and maintenance personnel or the first device.
  • the operation and maintenance workflow may support one or more scenarios.
  • the scenarios supported by different operation and maintenance workflows may be partially the same, completely the same, or completely different, which is not limited in this embodiment.
  • the dimensions of the scenario division may include: one or more of the network standard, wireless performance, and wireless network.
  • the network standards may include: 2G, 3G, 4G, 5G, etc.
  • the wireless performance may include: coverage, capacity, rate, energy consumption, latency, etc.
  • the wireless network environment may include: indoor, outdoor-urban, outdoor-rural, etc.
  • Each scenario can be any combination of values taken from one or more of the above dimensions.
  • the scenarios of the quality optimization sub-operation and maintenance workflow can include: 4G urban coverage optimization scenario, 5G urban coverage optimization scenario, 4G rate optimization scenario, 5G capacity optimization scenario, etc.
  • the operation and maintenance steps of the operation and maintenance workflows in different scenarios may be the same, but the operation and maintenance step requirements may be different.
  • S601 may include the following steps:
  • Step 1 Determine the scenarios supported by the quality optimization sub-operation and maintenance workflow.
  • the scenarios supported by the quality optimization sub-operation and maintenance workflow may include: 4G urban coverage optimization scenario, 5G urban coverage optimization scenario, 4G rate optimization scenario, and 5G capacity optimization scenario.
  • Step 2 Determine the operation and maintenance steps included in the quality optimization sub-operation and maintenance workflow.
  • the quality optimization sub-operation and maintenance workflow includes the following operation and maintenance steps: intent translation, quality problem identification, quality problem One or more of positioning, plan generation and decision-making, and plan implementation effect verification.
  • Step 3 Determine the autonomous state requirements of each operation and maintenance step in the quality optimization sub-operation and maintenance workflow, and generate the overall operation and maintenance step requirements of the quality optimization sub-operation and maintenance workflow.
  • the overall operation and maintenance step requirements of the quality optimization sub-operation and maintenance workflow include the autonomous state requirements of each operation and maintenance step in the quality optimization sub-operation and maintenance workflow.
  • the autonomous state requirement determined for intent translation is autonomous state requirement 1: manual implementation; the autonomous state requirement determined for quality problem identification is autonomous state requirement 3: the second device implements based on manually given strategies; the autonomous state requirement determined for quality problem location is autonomous state requirement 2: the system implements based on manually given rules; the autonomous state requirement determined for solution generation and decision-making is autonomous state requirement 3: the system implements based on manually given strategies; the autonomous state requirement determined for solution implementation effect verification is autonomous state requirement 3: the system implements based on manually given strategies.
  • Step 4 Determine the operation and maintenance step requirements that the second device needs to support for the quality optimization sub-operation and maintenance workflow based on the overall operation and maintenance step requirements of the quality optimization sub-operation and maintenance workflow and the autonomy capabilities of the autonomous management function (Autonomy MnF) deployed by the first device itself.
  • Autonomy MnF autonomous management function
  • the autonomous management functions deployed by the first device include: autonomous management functions of intent translation (which can realize the autonomy of intent translation operation and maintenance steps), autonomous management functions of solution generation and decision-making (which can realize the autonomy of solution generation and decision-making operation and maintenance steps), then the operation and maintenance step requirements that the second device needs to support for the quality optimization sub-operation and maintenance workflow include: quality problem identification, autonomous state requirement 3: the second device implements the strategy based on manual settings; quality problem location, autonomous state requirement 2: the second device implements the strategy based on manual settings; verification of the implementation effect of the solution, autonomous state requirement 3: the second device implements the strategy based on manual settings.
  • the operation and maintenance step requirements of the quality optimization sub-operation and maintenance workflow may include two dimensions of content, one dimension of content is the content of the supported scenarios, and the other dimension of content is the content of the operation and maintenance steps.
  • the content of the supported scenarios includes: 4G urban coverage optimization scenario, 5G urban coverage optimization scenario, 4G rate optimization scenario, and 5G capacity optimization scenario.
  • the content of the operation and maintenance steps is the content in the dotted box, that is, the content of operation and maintenance step 2, operation and maintenance step 3, and operation and maintenance step 5.
  • the content of operation and maintenance step 1 and operation and maintenance step 4 is supported by the autonomous management function deployed by the first device itself.
  • the operation and maintenance step requirements sent by the first device to the second device are operation and maintenance step requirements in addition to some operation and maintenance step requirements that can be achieved by the autonomous management function of the first device. This can ensure the reasonable division of labor and collaboration between the first device and the second device for the target operation and maintenance workflow, and avoid duplication of implementation.
  • S602 The first device sends an operation and maintenance step request to the second device.
  • the operation and maintenance step requirement is used to request the second device to feedback the autonomous capability information corresponding to the operation and maintenance step requirement.
  • the second device receives the operation and maintenance step requirements sent by the telecommunications operator.
  • the second device determines the autonomous capability information corresponding to the operation and maintenance step requirements.
  • the first device sends the operation and maintenance step requirements to the second device to obtain the autonomous capability information, which can accurately obtain the autonomous capability information corresponding to the operation and maintenance step requirements and avoid obtaining invalid autonomous capability information.
  • the first device can provide one or more autonomous capability information, and different autonomous capability information may be for different operation and maintenance workflows or the same operation and maintenance workflow.
  • An autonomous capability information is implemented by a set of autonomous management functions and corresponding autonomous management function configuration parameters.
  • the autonomous capability information includes: autonomous capability identification (task Capability List), operation and maintenance workflow name (workflow Name), supported autonomous network levels (supported ANL List), operation and maintenance task (Task) capability information corresponding to the supported autonomous network levels (task Capability List), and supported scenario names (supported Scenario List).
  • the autonomous capability identifier is used to uniquely identify an autonomous capability.
  • the operation and maintenance workflow name is used to identify an operation and maintenance workflow.
  • the operation and maintenance workflow name can be a network planning workflow, a network deployment workflow, a network maintenance workflow, a network optimization workflow, a monitoring and troubleshooting sub-operation and maintenance workflow, a network inspection sub-operation and maintenance workflow, a quality optimization sub-operation and maintenance workflow, an energy efficiency optimization sub-operation and maintenance workflow, etc., which are not listed here one by one.
  • the supported autonomous network levels can be level 1, level 2, level 3, level 4 and level 5. Taking the quality optimization sub-operation and maintenance workflow as an example, levels 3, 4 and 5 can all meet the operation and maintenance step requirements of autonomous capabilities.
  • the operation and maintenance task capability information includes the name of the operation and maintenance task and the autonomous status of the operation and maintenance task.
  • the names of the operation and maintenance tasks include: monitoring rules and optimization strategy generation operation and maintenance tasks, network/business assurance intent assessment operation and maintenance tasks, Data collection operation and maintenance tasks, performance anomaly identification operation and maintenance tasks, performance degradation prediction operation and maintenance tasks, performance problem demarcation operation and maintenance tasks, performance problem root cause analysis operation and maintenance tasks, optimization plan generation operation and maintenance tasks, optimization plan evaluation and determination operation and maintenance tasks, optimization plan execution.
  • the autonomous status of the operation and maintenance tasks includes: the operation and maintenance tasks are completed by humans, the operation and maintenance tasks are completed by humans and the second device, and the second device completes.
  • the data collection operation and maintenance tasks, performance anomaly identification operation and maintenance tasks, and performance degradation prediction operation and maintenance tasks are operation and maintenance steps for identifying quality problems.
  • the performance problem demarcation operation and maintenance tasks and performance problem root cause analysis operation and maintenance tasks are operation and maintenance steps for locating quality problems.
  • the optimization plan execution operation and maintenance tasks are operation and maintenance steps for implementing and verifying the effectiveness of the plan.
  • the autonomous state of the data collection operation and maintenance task and the performance anomaly identification operation and maintenance task is that the operation and maintenance task is completed by the second device, and the autonomous state of the performance degradation prediction operation and maintenance task is that the operation and maintenance task is completed jointly by humans and the second device.
  • the operation and maintenance step requirements of the quality problem identification operation and maintenance step can be matched or supported as the second device is implemented based on manual strategies.
  • the autonomous state of the performance problem demarcation operation and maintenance task is that the operation and maintenance task is completed by the second device, and the autonomous state of the performance problem root cause analysis operation and maintenance task is that the operation and maintenance task is completed jointly by the second device and manual labor.
  • the operation and maintenance step requirements of the quality problem location operation and maintenance step can be matched or supported as the second device is implemented based on manual strategies.
  • the autonomous state of the optimization plan executing the operation and maintenance task is that the operation and maintenance task is completed by the second device, which can match or support the operation and maintenance step requirements of the plan effect implementation verification operation and maintenance steps for the second device to implement based on manual strategies.
  • the supported scenario names may include: 4G urban coverage optimization scenario, 5G urban coverage optimization scenario, 4G rate optimization scenario and 5G capacity optimization scenario, 5G rate optimization scenario, 4G capacity optimization scenario, etc.
  • S604 The second device sends autonomous capability information to the first device.
  • the first device receives the autonomous capability information sent by the second device.
  • the second device may send autonomous capability information to the first device based on interface model information (Information Model), wherein the interface model information may be used to describe interaction information between two systems (i.e., the second device and the first device).
  • Information Model Information Model
  • the interface model information of the autonomous capability information may be as shown in Table 1.
  • the interface model information of the scene may be shown in Table 2.
  • Table 2 The interface model information of the scene may be shown in Table 2.
  • the interface model information of the operation and maintenance task capability information may be shown in Table 3.
  • the first device determines an autonomous service requirement according to the acquired autonomous capability information, wherein the autonomous service requirement is used to instruct the second device to provide an autonomous service for the operation and maintenance workflow.
  • the autonomous service requirement may include: an autonomous service requirement identifier (Autonomy Service Req Id), an operation and maintenance workflow name, an associated autonomous capability identifier (Autonomy Capability Id), scenario information (selected Scenario List), and a target autonomous performance indicator (KEI Target List).
  • an autonomous service requirement identifier Autonomy Service Req Id
  • an operation and maintenance workflow name an associated autonomous capability identifier
  • Autonomy Capability Id Autonomy Capability Id
  • scenario information selected Scenario List
  • a target autonomous performance indicator Keylist
  • the autonomous service demand identifier is used to uniquely identify an autonomous service demand.
  • the operation and maintenance workflow name is used to identify an operation and maintenance workflow.
  • the associated autonomous capability identifier can be one or more associated autonomous capability identifiers.
  • the selected scenario is used to describe the scenario name supported by the autonomous service demand.
  • the target autonomous performance indicator is used to describe the performance requirements of the autonomous service. Taking the quality optimization sub-operation and maintenance workflow as an example, the target autonomous performance indicator may include: the coverage performance improvement ratio or the reduction ratio of grids/cells with poor coverage quality, the user rate performance improvement ratio or the reduction ratio of users with poor user rate experience, the fault recognition rate improvement ratio, the energy consumption reduction ratio, the optimization time, etc.
  • S605 may include: the first device obtains one or more autonomous capability information from the autonomous capability information, and generates a configuration value of the obtained autonomous capability information, thereby obtaining an autonomous service requirement.
  • the generated configuration value includes: an autonomous network level obtained from multiple supported autonomous network levels, and one or more scenarios obtained from multiple supported scenarios, etc.
  • the first device may also determine the autonomous service requirements based on the cost, security, and reliability of network operation and maintenance.
  • S606 The first device sends an autonomous service request to the second device.
  • the second device receives the autonomous service request sent by the first device.
  • the first device may send an autonomous service requirement to the second device based on the interface model information.
  • the interface model information of the autonomous service requirement may be as shown in Table 1. Table 1:
  • the second device determines an autonomous management function for realizing the target autonomous service requirement, and generates a control parameter of the determined autonomous management function.
  • the autonomous management function is a management function related to autonomy that has been deployed in the second device.
  • the autonomous management function may include: management data analysis function, model training function, data collection function (Data Collection Function), etc.
  • the management data analysis function may include: coverage analysis function (Coverage MDAF), self-managing network (Self Organizing Network) function (such as capacity and coverage optimization (CCO Function) function), etc.
  • the model training function may include: machine learning function (ML training Function), etc.
  • the control parameters of the autonomous management function include: switch parameters of the autonomous management function, connection parameters between autonomous management functions (such as IP addresses or URI information of autonomous management functions), and policy or rule control parameters of autonomous management functions.
  • connection parameters between the autonomous management functions may include: Internet Protocol Address (IP Address) or Uniform Resource Identifier (URI) information of the autonomous management function.
  • IP Address Internet Protocol Address
  • URI Uniform Resource Identifier
  • policy or rule control parameters of the autonomous management function may include: the execution time, cycle, and range of adjustable parameters of the autonomous management function.
  • S608 The second device configures the generated control parameters.
  • S609 The second device generates and sends autonomous service pre-evaluation result information to the first device.
  • the first device receives the autonomous service pre-evaluation result information sent by the second device.
  • the autonomous service pre-assessment result information includes a feasibility assessment result (feasibility Result), and the feasibility result is used to characterize whether the second device supports the autonomous service requirement, such as whether the autonomous management function in the second device can implement the autonomous service corresponding to the autonomous service requirement.
  • a feasibility assessment result (feasibility Result)
  • the feasibility result is used to characterize whether the second device supports the autonomous service requirement, such as whether the autonomous management function in the second device can implement the autonomous service corresponding to the autonomous service requirement.
  • the first device can quickly obtain the result of whether the autonomous service demand can be provided, so as to make timely adjustments and improve the real-time performance of autonomy.
  • the feasibility assessment result may indicate that the second device can support autonomous service requirements
  • the pre-assessment result information may also include a list of autonomous management functions determined in S607.
  • the feasibility result is used to describe whether the second device can support the autonomous service requirements, and the values are feasible and infeasible;
  • the autonomous management function list is the information of the autonomous management functions needed to support the autonomous service requirements, and the information of the autonomous management functions includes the identifier or name of the autonomous management function, and the type of the autonomous management function, etc.
  • the second device may send autonomous service pre-evaluation result information to the operator telecommunication system based on the interface model information.
  • the feasibility assessment result can indicate that the second device can support the autonomous service requirements
  • the first device can modify the autonomous service requirements, that is, return to S605 to re-execute S605-S609 so that the feasibility assessment result can indicate that the second device can support the autonomous service requirements.
  • the second device executes the autonomous service corresponding to the autonomous service requirement, generates and sends autonomous service execution result information to the first device.
  • the first device receives the autonomous service execution result information sent by the second device.
  • the autonomous service execution result information includes an autonomous performance index satisfaction value, wherein the autonomous performance satisfaction value is an actual measurement value of a target autonomous performance index obtained when the second device executes the autonomous service.
  • the second device may send the autonomous service execution result information to the first device in the form of an autonomous service monitoring report.
  • the second device generates an autonomous service monitoring report including the autonomous service execution result information, and sends the autonomous service monitoring report to the first device.
  • the second device may send an autonomous service monitoring report to the first device based on the interface model information.
  • the interface model information of the autonomous service monitoring report may be as shown in Table 4. Table 4:
  • the second device can provide corresponding autonomous capabilities based on the operation and maintenance step requirements of the first device for the autonomous capabilities of the target operation and maintenance workflow.
  • the first device specifies differentiated autonomous service requirements for different scenarios based on the autonomous capabilities of the second device.
  • the second device can then dynamically orchestrate autonomous management functions, provide differentiated autonomous services, and complete the division of labor and collaboration between the first device and the second device for the target operation and maintenance workflow, avoiding duplication.
  • FIG6 is only used to exemplify possible embodiments of the present application and cannot be understood as limiting the embodiments of the present application.
  • FIG6 in combination with the embodiment shown in FIG4 , the embodiment shown in FIG5 , and the embodiment shown in FIG6 , it can be seen that:
  • S604-S606 in the embodiment shown in FIG6 may be an embodiment; S604-S609 in the embodiment shown in FIG6 may be an embodiment; S604-S610 in the embodiment shown in FIG6 may be an embodiment; S605-S606 in the embodiment shown in FIG6 may be an embodiment; S605-S610 in the embodiment shown in FIG6 may be an embodiment; S606-S609 in the embodiment shown in FIG6 may be an embodiment Example; S606-S610 in the embodiment shown in Figure 6 may be an embodiment; S603-S606 in the embodiment shown in Figure 6 may be an embodiment; S603-S609 in the embodiment shown in Figure 6 may be an embodiment; S603-S610 in the embodiment shown in Figure 6 may be an embodiment; S603-S610 in the embodiment shown in Figure 6 may be an embodiment; S603-S610 in the embodiment shown in Figure 6 may be an embodiment; S602-S606 in the embodiment shown in Figure 6 may be an embodiment; S602-S609 in the embodiment shown in Figure 6
  • FIG. 8 is a flow chart of an autonomous method for an autonomous network according to another embodiment of the present application.
  • the method includes:
  • S801 The second device sends autonomous capability information to the first device.
  • the first device receives the autonomous capability information sent by the second device.
  • the autonomous capability information in the embodiment shown in FIG6 is the autonomous capability information corresponding to the operation and maintenance step requirements, and the operation and maintenance step requirements are the operation and maintenance step requirements for realizing the autonomous capability of the target operation and maintenance workflow. That is to say, in the embodiment shown in FIG6 , the autonomous capability information is the information of the autonomous capability corresponding to the target operation and maintenance workflow. In this embodiment, the autonomous capability information is the information of the autonomous capability corresponding to each operation and maintenance workflow.
  • the autonomous capability information in the embodiment shown in Figure 6 is the information of the autonomous capability corresponding to the one operation and maintenance workflow, that is, the information used to realize the autonomous capability of the one operation and maintenance workflow.
  • the autonomous capability information is the information for realizing the autonomous capability of each operation and maintenance workflow among the operation and maintenance workflows.
  • S802 The first device determines autonomous service requirements according to the autonomous capability information.
  • S802 may include the following steps:
  • the first device determines the operation and maintenance step requirements for achieving the autonomous capabilities of the target operation and maintenance workflow.
  • Step 2 The first device determines the autonomous capability information corresponding to the operation and maintenance step requirements.
  • the operator sends the operation and maintenance step requirements to the second device, so that the second device matches and obtains the autonomous capability information corresponding to the operation and maintenance step requirements.
  • the second device since the second device sends the autonomous capability information used to implement each operation and maintenance workflow to the first device, after the first device determines the operation and maintenance step requirements, it can select the autonomous capability information corresponding to the operation and maintenance step requirements from the autonomous capability information used to implement each operation and maintenance workflow.
  • Step 3 The first device determines the autonomous service requirements based on the autonomous capability information corresponding to the operation and maintenance step requirements.
  • S803 The first device sends an autonomous service request to the second device.
  • the second device receives the autonomous service request sent by the first device.
  • the second device determines an autonomous management function for realizing the autonomous service requirement, and generates a control parameter of the determined autonomous management function.
  • S806 The second device generates and sends autonomous service pre-evaluation result information to the first device.
  • the first device receives the autonomous service pre-evaluation result information sent by the second device.
  • the second device executes the autonomous service corresponding to the autonomous service requirement, generates and sends autonomous service execution result information to the first device.
  • the first device receives the autonomous service execution result information sent by the second device.
  • the first device specifies differentiated autonomous service requirements for different scenarios based on the autonomous capabilities of the second device
  • the second device can dynamically orchestrate autonomous management functions, provide differentiated autonomous services, and complete the division of labor and collaboration between the first device and the second device for specific operation and maintenance workflows to avoid duplication.
  • FIG8 is only used to illustrate a possible embodiment of the present application, and cannot be understood as a limitation on the embodiments of the present application.
  • the implementation principle that some technical features in the embodiment of FIG8 can constitute a new embodiment please refer to the description of the embodiment shown in FIG6, which will not be repeated here.
  • the present application also provides an autonomous device of an autonomous network.
  • FIG9 is a schematic diagram of an autonomous device of an autonomous network of an embodiment of the present application. As shown in FIG9 , the device 900 includes:
  • the first receiving unit 901 is configured to receive autonomous capability information sent by a second device, wherein the autonomous capability information represents information on autonomous capabilities for implementing an operation and maintenance workflow.
  • the first sending unit 902 is used to send the autonomous service requirement of the operation and maintenance workflow to the second device, wherein the autonomous service requirement is associated with the autonomous capability information, and the autonomous service requirement is used to instruct the second device to provide the autonomous service of the operation and maintenance workflow.
  • FIG10 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application, wherein the device 1000 includes:
  • the first receiving unit 1001 is used to receive the autonomous capability information sent by the second device, wherein the autonomous capability information represents the information of the autonomous capability for realizing the operation and maintenance workflow.
  • the first sending unit 1002 is used to send the autonomous service requirement of the operation and maintenance workflow to the second device, wherein the autonomous service requirement is associated with the autonomous capability information, and the autonomous service requirement is used to instruct the second device to provide the autonomous service of the operation and maintenance workflow.
  • the autonomous service requirement is associated with the autonomous capability information, which means that the autonomous service requirement is determined by the device 1000 according to the autonomous capability information.
  • the apparatus 1000 may further include:
  • the second receiving unit 1003 is configured to receive a feasibility evaluation result sent by the second device, wherein the feasibility evaluation result is used to indicate whether the second device supports the autonomous service requirement.
  • the operation and maintenance workflow is a target operation and maintenance workflow.
  • the apparatus 1000 may further include:
  • the second sending unit 1004 is used to send an operation and maintenance step requirement to the second device, wherein the operation and maintenance step requirement is used to request the autonomous capability information, and the autonomous capability information is information on the autonomous capability that meets the operation and maintenance step requirement and is used to implement the target operation and maintenance workflow.
  • the autonomous management function deployed by device 1000 supports partial operation and maintenance step requirements for implementing the target operation and maintenance workflow
  • the operation and maintenance step requirements sent to the second device are operation and maintenance step requirements in addition to the partial operation and maintenance step requirements supported by the autonomous management function for implementing the target operation and maintenance workflow.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and supported scenarios, and the autonomous state requirements are used to characterize the degree of participation of the second device in the operation and maintenance steps.
  • the autonomous capability information is multiple, as shown in FIG10 , the apparatus 1000 may further include:
  • the determining unit 1005 is configured to determine, according to the operation and maintenance step requirement of the device 1000, the autonomous capability information corresponding to the operation and maintenance step requirement from the plurality of autonomous capability information, wherein the operation and maintenance step requirement is a requirement for the autonomous capability of realizing a target operation and maintenance workflow in the operation and maintenance workflow;
  • the autonomous service requirement is determined based on the acquired autonomous capability information corresponding to the operation and maintenance step requirement.
  • the autonomous capability information includes: an autonomous capability identifier, the name of the operation and maintenance workflow, supported autonomous network levels, operation and maintenance task capability information corresponding to the supported autonomous network levels, and at least one of supported scenario information.
  • the autonomous service requirement includes: an autonomous service requirement identifier, the name of the operation and maintenance workflow, an associated autonomous capability identifier, an autonomous network level, scenario information, and at least one of a target autonomous performance indicator.
  • FIG. 11 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • the device 1100 includes:
  • the third sending unit 1101 is used to send autonomous capability information to the first device, wherein the autonomous capability information represents the autonomous capability information used for Information on the autonomy of operational workflows.
  • the third receiving unit 1102 is configured to receive an autonomous service requirement sent by the first device, wherein the autonomous service requirement is associated with the autonomous capability information.
  • the execution unit 1103 is used to execute the autonomous service of the operation and maintenance workflow indicated by the autonomous service requirement.
  • FIG. 12 is a schematic diagram of an autonomous device of an autonomous network according to another embodiment of the present application.
  • the device 1200 includes:
  • the third sending unit 1201 is used to send autonomous capability information to the first device, wherein the autonomous capability information represents information of autonomous capability for implementing an operation and maintenance workflow.
  • the third receiving unit 1202 is configured to receive an autonomous service requirement sent by the first device, wherein the autonomous service requirement is determined by the first device based on the autonomous capability information.
  • the execution unit 1203 is used to execute the autonomous service of the operation and maintenance workflow indicated by the autonomous service requirement.
  • the apparatus may further include:
  • the fourth sending unit 1204 is used to send a feasibility evaluation result to the first device, wherein the feasibility evaluation result is used to indicate whether the second device supports the autonomous service requirement.
  • the operation and maintenance workflow is a target operation and maintenance workflow.
  • the device 1200 may further include:
  • the fourth receiving unit 1205 is used to receive the operation and maintenance step requirements sent by the first device, wherein the operation and maintenance step requirements are used to request the autonomous capability information, and the autonomous capability information is information on the autonomous capability that meets the operation and maintenance step requirements and is used to implement the target operation and maintenance workflow.
  • the operation and maintenance step requirements include: operation and maintenance steps, autonomous state requirements corresponding to the operation and maintenance steps, and scenarios supported by the autonomous capabilities.
  • the autonomous state requirements are used to characterize the degree of participation of the device 1200 in the operation and maintenance steps.
  • the autonomous capability information includes: an autonomous capability identifier, the name of the operation and maintenance workflow, supported autonomous network levels, operation and maintenance task capability information corresponding to the supported autonomous network levels, and at least one of supported scenario information.
  • the autonomous service requirement includes: an autonomous service requirement identifier, the name of the operation and maintenance workflow, an associated autonomous capability identifier, an autonomous network level, scenario information, and at least one of a target autonomous performance indicator.
  • FIG13 is a schematic diagram of an autonomous system of an autonomous network according to another embodiment of the present application.
  • the system 1300 includes a first device 1301 and a second device 1302 in communication connection.
  • the first device 1301 may be a device as shown in FIG9 or FIG10
  • the second device 1302 may be a device as shown in FIG11 or FIG12 .
  • the embodiments of the present application also provide a chip, which includes a processor and a memory, the memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory to execute the method described in any of the above embodiments.
  • the present application further provides a computer-readable storage medium, on which computer instructions are stored.
  • the computer instructions are executed by a processor, the method described in any of the above embodiments is executed.
  • the present application further provides a computer program product, which, when executed on a processor, enables the method described in any one of the above embodiments to be executed.
  • the present application also provides an electronic device, including:
  • the memory stores computer instructions that can be executed by the at least one processor.
  • the computer instructions are executed by the at least one processor so that the method described in any one of the above embodiments is executed.
  • FIG. 14 is a schematic diagram of the structure of an electronic device according to an embodiment of the present application.
  • the electronic device includes a memory and a processor.
  • the electronic device may further include a communication interface and a bus, wherein the processor, the communication interface and the memory are connected via the bus; the processor is used to execute an executable module stored in the memory, such as a computer program.
  • the memory may include high-speed random access memory (RAM) and may also include A non-volatile memory, such as at least one disk storage.
  • RAM random access memory
  • a non-volatile memory such as at least one disk storage.
  • the communication connection between the system network element and at least one other network element is realized through at least one communication interface (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. can be used.
  • the bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Enhanced Industry Standard Architecture (EISA) bus, etc.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Enhanced Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, etc.
  • the memory is used to store the program, and the processor executes the program after receiving the execution instruction.
  • the method disclosed in any of the above-mentioned embodiments of the present application can be applied to the processor or implemented by the processor.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor, or a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored.
  • computer-executable instructions When the computer-executable instructions are executed by a processor, they are used to implement the method described in any of the above embodiments.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • 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 distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Databases & Information Systems (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Software Systems (AREA)
  • Control Of Position, Course, Altitude, Or Attitude Of Moving Bodies (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种自治网络的自治方法和装置，包括：第一装置接收第二装置发送的自治能力信息，其中，自治能力信息表征用于实现运维工作流的自治能力的信息，第一装置向第二装置发送运维工作流的自治服务需求，其中，自治服务需求与自治能力信息相关，自治服务需求用于指示第二装置提供运维工作流的自治服务，一方面，第一装置可以根据第二装置提供的自治能力信息准确确定第二装置可执行的自治服务需求，提高效率，避免第二装置反对协商和挑战自治服务需求；另一方面，通过第一装置向第二装置发送自治服务需求，使得第二装置可以根据第一装置针对运维工作流的差异化需求提供自治服务。

Description

自治网络的自治方法和装置
本申请要求于2022年10月14日提交中国国家知识产权局、申请号为202211260983.3、申请名称为“自治网络的自治方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信网络技术领域，尤其涉及一种自治网络的自治方法和装置。
背景技术
自动化或者智能化技术(以下简称自治技术)在通信网络中的应用日渐成为行业的关注重点和研究热点，以通过引入自治技术(如人工智能，机器学习，大数据分析，数字孪生等)，解决通信网络遇到的网络运维问题。
针对某个或某些运维工作流，运营商管理系统可能会实现部分自治服务需求，设备商管理系统可以实现其余的自治服务需求，所以运营商在不同的场景下对设备商管理系统会有不同的自治服务需求，需要设备商的提供适应的自治能力信息来满足，并不是设备商系统的自治能力信息越多越好，因此，如何满足设备商管理系统的差异化的自治服务需求成了亟待解决的问题。
发明内容
为解决上述技术问题，本申请实施例提供了一种自治网络的自治方法和装置。
第一方面，本申请实施例提供了自治网络的自治方法，所述方法应用于第一装置，所述方法包括：
接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
在本实施例中，一方面，第一装置可以根据第二装置提供的自治能力信息准确确定第二装置可执行的自治服务需求，提高效率，避免第二装置反对协商和挑战自治服务需求；另一方面，通过第一装置向第二装置发送自治服务需求，使得第二装置可以根据第一装置针对运维工作流的差异化需求提供自治服务。
在一些实施例中，所述方法还包括：
接收所述第二装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
在本实施例中，通过可行性评估结果，使得第一装置快速获取自治服务需求是否可以被提供的结果，以便及时作出调整，提高自治的实时性。
在一些实施例中，所述方法还包括：所述运维工作流为目标运维工作流；在所述接收第二装置发送的自治能力信息之前，所述方法还包括：
向所述第二装置发送运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
在本实施例中，第一装置向第二装置发送运维步骤需求来获取自治能力信息，能够精准获取与运维步骤需求对应的自治能力信息，避免获取无效的自治能力信息。
在一些实施例中，所述第一装置部署的自治管理功能支持实现所述目标运维工作流的部分运维步骤需求，向所述第二装置发送的运维步骤需求为除所述自治管理功能支持实现所述目标运维工作流的部分运维步骤需求之外的运维步骤需求。
在本实施例中，第一装置向第二装置发送的运维步骤需求为除第一装置的自治管理功能能够 实现的部分运维步骤需求之外的运维步骤需求，可以保障第一装置和第二装置针对目标运维工作流的合理分工和协同，避免重复实现。
在一些实施例中，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
在一些实施例中，所述自治能力信息为多个；在所述接收第二装置发送的自治能力信息之后，所述方法还包括：
根据所述第一装置的运维步骤需求，从所述多个自治能力信息中，确定与所述运维步骤需求对应的自治能力信息，其中，所述运维步骤需求为用于实现运维工作流中的目标运维工作流的自治能力的需求；
以及，所述自治服务需求是基于获取到的与所述运维步骤需求对应的自治能力信息确定的。
在本实施例中，通过从各自治能力信息中确定与运维步骤需求对应的自治能力信息，可以保障第一装置和第二装置针对目标运维工作流的合理分工和协同，避免重复实现。
在一些实施例中，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
在一些实施例中，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
第二方面，本申请实施例还提供了一种自治网络的自治方法，所述方法应用于第二装置，所述方法包括：
向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
接收所述第一装置发送的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
执行所述自治服务需求所指示的所述运维工作流的自治服务。
在一些实施例中，所述方法还包括：
向所述第一装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
在一些实施例中，所述运维工作流为目标运维工作流；在所述向第一装置发送自治能力信息之前，所述方法还包括：
接收所述第一装置发送的运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
在一些实施例中，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及所述自治能力对应支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
在一些实施例中，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
在一些实施例中，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
第三方面，本申请实施例还提供了一种自治网络的自治方法，所述方法包括：
第二装置向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
所述第一装置向所述第二装置发送自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
所述第二装置执行所述自治服务需求所指示的所述运维工作流的自治服务。
在一些实施例中，所述方法还包括：
所述第二装置向所述第一装置发送可行性评估结果，其中，所述可行性评估结果用于表征所 述第二装置是否支持所述自治服务需求。
在一些实施例中，所述运维工作流为目标运维工作流；在所述第二装置向第一装置发送自治能力信息之前，所述方法还包括：
所述第一装置向所述第二装置发送运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
在一些实施例中，所述第一装置部署的自治管理功能支持实现所述目标运维工作流的部分运维步骤需求，向所述第二装置发送的运维步骤需求为除所述自治管理功能支持实现所述目标运维工作流的部分运维步骤需求之外的运维步骤需求。
在一些实施例中，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及所述自治能力对应支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
在一些实施例中，所述自治能力信息为多个；所述方法还包括：
所述第一装置根据所述第一装置的运维步骤需求，从所述多个自治能力信息中，确定与所述运维步骤需求对应的自治能力信息，所述运维步骤需求为用于实现运维工作流中的目标运维工作流的自治能力的需求。
在一些实施例中，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
在一些实施例中，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
第四方面，本申请实施例还提供了一种自治网络的自治装置，所述装置包括：
第一接收单元，用于接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
第一发送单元，用于向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
第五方面，本申请实施例还提供了一种自治网络的自治装置，所述装置包括：
第三发送单元，用于向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
第三接收单元，用于接收所述第一装置发送的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
执行单元，用于执行所述自治服务需求所指示的所述运维工作流的自治服务。
第六方面，本申请实施例还提供了一种自治网络的自治系统，所述系统包括通信连接的第一装置和第二装置；其中，
所述第一装置，用于执行如上第一方面中任一实施例所述的方法；
所述第二装置，用于执行如上第二方面中任一实施例所述的方法。
第七方面，本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机指令，当所述计算机指令在被处理器运行时，使得上述任一实施例所述的方法被执行。
第八方面，本申请实施例还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的计算机指令，所述计算机指令被所述至少一个处理器执行，使得上述任一实施例所述的方法被执行。
第九方面，本申请实施例还提供了一种计算机程序产品，当所述计算机程序产品在处理器上运行时，使得上述任一实施例所述的方法被执行。
第十方面，本申请实施例还提供了一种芯片，所述芯片包括处理器和存储器，所述存储器用 于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如上任一实施例所述的方法。
附图说明
附图用于更好地理解本申请实施例，不构成对本申请的限定。其中，
图1为本申请实施例的自治网络等级的分级标准的示意图；
图2为本申请实施例的自治网络的自治方法的应用场景示意图；
图3为本申请实施例的自治网络的自治系统的示意图；
图4为本申请一个实施例的自治网络的自治方法的流程示意图；
图5为本申请另一个实施例的自治网络的自治方法的流程示意图；
图6为本申请另一实施例的自治网络的自治方法的流程示意图；
图7为本申请实施例的质量优化子运维工作流的运维步骤需求的示意图；
图8为本申请另一实施例的自治网络的自治方法的流程示意图；
图9为本申请一个实施例的自治网络的自治装置的示意图；
图10为本申请另一实施例的自治网络的自治装置的示意图；
图11为本申请另一实施例的自治网络的自治装置的示意图；
图12为本申请另一实施例的自治网络的自治装置的示意图；
图13为本申请另一实施例的自治网络的自治装置的示意图；
图14为本申请实施例的电子设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
随着垂直行业的引入，终端设备的增加和业务的多样性，第一装置(如运营商的通信管理系统，可以称为运营商管理系统)的通信网络越来越复杂，导致网络运维难度的增加。如何降低网络运维成本，简化网络运维流程，快速部署网络以满足多样性化的业务是网络运维迫切需要改善的点。
自动化或者智能化技术(以下简称自治技术)在通信网络中的应用日渐成为行业的关注重点和研究热点，以通过引入自治技术(如人工智能，机器学习，大数据分析，数字孪生等)，解决通信网络遇到的网络运维问题。
其中，被引入了自治技术的通信网络可以称为自治网络(Autonomous Network)，是指第一装置在尽可能少的人工干预的前提下，通过自治能力实现自我管控。
自治技术可以应用于通信网络(如电信系统(telecommunication systems))生命周期的多个运维工作流，包括网络规划，网络部署，网络优化，业务运营等，能够减少人工操作，降低网络运维成本(Operating Expense，OPEX)，提高网络运维效率。
其中，运维工作流为实现通信网络中的网络运维目的的运维步骤，运维步骤由一个或者多个运维任务实现。
不同的第二装置(如设备商的通信管理系统，可以称为设备商管理系统)引入不同的自治技术来解决不同或者相同的网络运维效率问题，从而达到降本增效，提质创收的目的。运营商需要一套统一的分级标准描述和评估第一装置在不同场景下的自治能力，进而牵引第一装置引入更多的自治能力或者最合适的自治能力。其中，自治网络等级为基于分级标准确定的，是指自治网络的自治能力等级。
在一些实施例中，自治网络等级的分级标准描述了运维工作流(如网络规划，网络部署，网络维护和网络优化等工作流)的自治能力，并基于自治网络等级的分级标准定义了自治网络等级评估方法，运营商可以基于评估方法对第一装置进行评估打分，从而得到对应的自治网络等级分 数。其中，第一装置的自治网络等级的确定是从运维工作流中每个运维步骤的人和第一装置的参与程度来确定。
示例性的，以运维工作流为网络优化工作流为例，如图1所示，基于自治网络等级的分级标准，可以将网络优化工作流的自治网络等级确定为6个等级，如为0级直至5级。如图1所示，自治网络等级包括：意图管理、感知、分析、决策、执行五个运维步骤的内容，且意图管理运维步骤可以由监控规则和优化策略生成运维任务实现、网络/业务保障意图评估运维任务实现；感知运维任务类型步骤可以由数据采集运维任务实现；分析运维步骤可以由性能异常识别运维任务、性能劣化预测运维任务、性能问题根因分析运维任务、优化方案生成运维任务实现；决策运维步骤可以由优化方案评估和确定运维任务实现；执行运维步骤可以由优化方案执行运维任务实现。
如图1所示，同一的运维步骤在不同的自治网络等级中，人和第一装置的参与程度不一样。例如，十个运维步骤在自治网络等级为0级时，分别由人单独完成，而在自治网络等级为5级时，十个运维步骤都为第一装置单独完成，在自治网络等级为4级时，运维步骤中的意图管理类运维步骤为由人和第一装置共同参与完成，而运维步骤中的感知类运维步骤、分析类运维步骤、决策类运维步骤、执行类运维步骤分别为第一装置完成，关于其他等级的人和第一装置的参与程度可以参阅图1，此处不再一一列举。
针对某个或某些运维工作流，第一装置可能会实现部分自治服务需求，第二装置可以实现其余的自治服务需求，所以运营商在不同的场景下对第二装置会有不同的自治服务需求，需要设备商的提供适应的自治能力信息来满足，并不是设备商系统的自治能力信息越多越好，因此，如何满足第一装置的差异化的自治服务需求成了亟待解决的问题。
为了解决上述技术问题，第二装置向第一装置发送自治能力信息，自治能力信息表征用于实现运维工作流的自治能力的信息；第一装置根据自治能力信息生成自治服务需求，并将自治服务需求发送给第二装置，自治服务需求用于指示第二装置提供运维工作流的自治服务；第二装置执行自治服务。
本申请提供了一种自治网络的自治方法，该自治网络的自治方法可以应用于如图2所示的自治网络。如图2所示，自治网络中包括业务营运单元、跨域管理功能单元、域管理功能单元、网元。
其中，业务运营单元，也可以称为通信业务管理功能单元(communication service management function)，可以提供计费、结算、账务、客服、营业、网络监控、通信业务生命周期管理，业务意图翻译等功能和管理服务。包括运营商的运营系统或者垂直行业的运营系统(vertical operational technology system)。
跨域管理功能单元，也可以称之为网络管理功能单元(network management function，NMF)，跨域管理功能单元提供以下一项或几项功能或者管理服务：网络的生命周期管理、网络的部署、网络的故障管理、网络的性能管理、网络的配置管理、网络的保障、网络的优化功能、通信服务提供商的网络意图(intent from communication service provider，intent-CSP)的翻译、通信服务使用者的网络意图(intent from communication service consumer，intent-CSC)的翻译等。这里的网络可以包括一个或者多个网元，子网络或者网络切片。例如，跨域管理功能单元可以是网络切片管理功能(network slice management function，NSMF)，或者管理数据分析功能(management data analytical function，MDAF)，或者跨域自组织网络功能(self-organization network function，SON-function)，或者跨域意图管理功能单元。
域管理功能单元，也可以称之为子网络管理功能单元(subnetwork management function，subnetwork NMF)或者网元管理功能单元(network element/function management function)，域管理功能单元提供以下一项或者多项功能或者管理服务：子网络或者网元的生命周期管理、子网络或者网元的部署、子网络或者网元的故障管理、子网络或者网元的性能管理、子网络或者网元的保障、子网络或者网元的优化管理、子网络或者网元的意图翻译等。这里的子网络包括一个或者多个网元。或者，这里的子网络也可以包括一个或多个子网络，即一个或多个子网络组成一个更大覆盖范围的子网络。又或者，这里的子网络也可以包括一个或多个网络切片子网络。子网络可以包括以下几种描述方式之一：
某个技术域的网络，比如无线接入网，核心网，传输网等。
某个制式的网络，比如全球移动通讯系统(Global System for Mobile Communications，GSM)网络，长期演进(Long Term Evolution，LTE)网络，第五代移动通信技术(5th Generation Mobile Communication Technology，5G)网络等。
某个设备商提供的网络，比如设备商X提供的网络等。
某个地理区域的网络，比如工厂A的网络，地级市B的网络等。
网元，为提供网络服务的实体，包括核心网网元、接入网网元等。例如，核心网网元可以包括但不限于接入与移动管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、策略控制功能(policy control function，PCF)实体、网络数据分析功能(network data analysis function，NWDAF)实体、网络存储功能(network repository function，NRF)、网关等。接入网网元可以包括但不限于：各类基站(例如下一代基站(generation node B，gNB)，演进型基站(evolved Node B，eNB)、集中控制单元(central unit control panel，CUCP)、集中单元(central unit，CU)、分布式单元(distributed unit，DU)、集中用户面单元(central unit user panel，CUUP)等。
如图2所示，自治网络的范围可以包括以下三种情况：
单域自治网络，单域自治网络中包括网元和域管理功能单元。
跨域自治网络，跨域自治网络中包括：网元、域管理功能单元、跨域管理功能单元。
业务自治网络，业务自治网络包括：网元、域管理功能单元、跨域管理功能单元、业务运营单元。
在服务化管理架构下，聚焦管理服务的提供者(Management Service Producer,MnS Producer)和管理服务的消费者(Management Service Consumer，MnS Consumer)。相应的，在如图2所示的应用场景中，若管理服务为上述业务运营单元提供的管理服务时，业务运营单元为管理服务提供者，业务运营商单元可以为管理服务消费者，即业务运营单元为第二装置，业务运营商单元为第一装置；若管理服务为上述跨域管理功能单元提供的管理服务时，跨域管理功能单元为管理服务提供者，业务运营单元为管理服务消费者，即跨域管理功能单元为第二装置，业务运营商单元为第一装置；若当管理服务为上述域管理功能单元提供的管理服务时，域管理功能单元为管理服务提供者，跨域管理功能单元或者业务运营单元为管理服务消费者，即域管理功能单元为第二装置，跨域管理功能单元或者业务运营单元为第一装置；若管理服务为上述网元提供的管理服务时，网元为管理服务提供者，域管理功能单元或者跨域管理功能单元或者业务运营单元为管理服务消费者，即网元为第二装置，域管理功能单元或者跨域管理功能单元或者业务运营单元为第一装置。
在一些实施例中，在如图2所示的应用场景的基础上，用于执行本申请的自治网络的自治方法的自治网络的自治系统主要涉及自治网络监控模块、自治网络执行模块、以及逻辑接口，如图3所示。
其中，自治网络监控模块为第一装置，自治网络监控模块用于生成自治网络的运维步骤需求，监控自治网络执行情况；自治网络执行模块为第二装置，自治网络执行模块用于提供并执行自治网络的自治能力；逻辑接口为自治网络监控模块和自治网络执行模块之间的逻辑接口，用于自治能力协商和监控的接口。
基于上述分析可知，自治网络的范围可以包括三种情况，因此，针对不同的自治网络的范围，自治网络监控模块和自治网络执行模块的部署场景可能不同，示例性的：
自治网络的范围包括单域自治网络，针对单域自治网络，自治网络执行模块(即第二装置)可以部署在域管理功能单元，自治网络监控模块(即第一装置)可以部署在跨域管理功能单元。
自治网络的范围包括跨域自治网络，针对跨域自治网络，自治网络执行模块(即第二装置)可以部署在跨域管理功能单元，自治网络监控模块(即第一装置)可以部署在业务运营单元。
自治网络的范围包括业务自治网络，针对业务自治网络，自治网络执行模块(即第二装置)可以部署在业务运营单元，自治网络监控模块(即第一装置)可以部署在自治网络之外的一个第三方系统(比如企业系统等)。
相应的，在服务化管理架构下，自治网络监控模块为管理服务消费者，自治网络执行模块为 管理服务提供者，逻辑接口为自治能力协商和监控服务的接口。
本申请提供了一种自治网络的自治方法，该方法可以应用于第一装置。请参阅图4，图4为本申请一个实施例的自治网络的自治方法的流程示意图。如图4所示，该方法包括：
S401：接收第二装置发送的自治能力信息。其中，自治能力信息表征用于实现运维工作流的自治能力的信息。
示例性的，本实施例的执行主体可以为自治网络的自治装置，该装置可以应用于第一装置，如该装置可以为第一装置，也可以为第一装置中的至少部分组件(可以为实体组件，也可以为虚拟组件，本实施例不做限定)。其中，第一装置可以为计算机或计算机集群，也可以为服务器或服务器集群，也可以终端设备，等等，本实施例不做限定。
自治能力的信息可以称为自治能力信息，自治能力可以用于实现运维工作流，相应的，自治能力信息可以理解为用于实现运维工作流的自治能力的信息。
S402：向第二装置发送运维工作流的自治服务需求。其中，自治服务需求与自治能力信息关联，自治服务需求用于指示第二装置提供运维工作流的自治服务。
其中，自治服务需求与自治能力信息关联可以理解为，自治服务需求是基于自治能力信息确定的。
示例性的，第一装置在接收到自治能力信息之后，可以基于该自治能力信息确定用于实现自治服务的自治服务需求，以便在将自治服务需求发送给第二装置，由第二装置执行自治服务，从而确定第二装置是否可以支持自治服务需求。
在本实施例中，一方面，第一装置可以根据第二装置提供的自治能力信息准确确定第二装置可执行的自治服务需求，提高效率，避免第二装置反对协商和挑战自治服务需求；另一方面，通过第一装置向第二装置发送自治服务需求，使得第二装置可以根据第一装置针对运维工作流的差异化需求提供自治服务。
本申请提供了一种自治网络的自治方法，该方法可以应用于第二装置。请参阅图5，图5为本申请另一个实施例的自治网络的自治方法的流程示意图。如图5所示，该方法包括：
S501：向第一装置发送自治能力信息。其中，自治能力信息表征用于实现运维工作流的自治能力的信息。
示例性的，本实施例的执行主体可以为自治网络的自治装置，该装置可以应用于第二装置，如该装置可以为第二装置中的至少部分组件(可以为实体组件，也可以为虚拟组件，本实施例不做限定)。其中，第二装置可以为计算机或计算机集群，也可以为服务器或服务器集群，也可以终端设备，等等，本实施例不做限定。
自治能力的信息可以称为自治能力信息，自治能力可以用于实现运维工作流，相应的，自治能力信息可以理解为用于实现运维工作流的自治能力的信息。
S502：接收第一装置发送的自治服务需求。其中，自治服务需求与自治能力信息关联。
例如，自治服务需求是第一装置根据自治能力信息确定的。
S503：执行自治服务需求所指示的运维工作流的自治服务。
示例性的，第一装置在接收到自治能力信息之后，可以基于该自治能力信息确定用于实现自治服务的自治服务需求，以便在将自治服务需求发送给第二装置，由第二装置执行自治服务，从而确定第二装置是否可以支持自治服务需求。
为使读者深刻理解本申请的实现原理，现结合图6至图8进行详细地阐述。其中，图6为本申请另一实施例的自治网络的自治方法的流程示意图。如图6所示，该方法包括：
S601：第一装置确定目标运维工作流的运维步骤需求。其中，运维步骤需求用于请求自治能力信息，自治能力信息为满足运维步骤需求的用于实现目标运维工作流的自治能力的信息。
也就是说，自治能力信息为达到两个条件的自治能力信息，一个条件是满足运维步骤需求，另一个条件是实现目标运维工作流的自治。其中，目标运维工作流为第一装置需要实现的运维工作流。
运维步骤需求包括：运维步骤、运维步骤对应的自治状态需求、以及支持的场景，自治状态需求为第二装置在运维步骤上的参与程度需求。其中，运维步骤基于自治能力实现。
基于上述分析可知，运维工作流可以为网络规划工作流、网络部署工作流、网络维护工作流、网络优化工作流等中的一种或多种。相应的，目标运维工作流可以为至少部分运维工作流，即目标运维工作流可以为上述工作流中的至少部分工作流。例如，目标运维工作流可以为网络规划工作流，也可以是网络部署工作流，也可以是网络维护工作流，也可以是网络优化工作流。本实施例对目标运维工作流的内容不做限定。
在一些实施例中，目标运维工作流可以为如上所述的整体工作流，如为网络维护工作流，在另一些实施例中，目标运维工作流也可以为将整体工作流拆分为多个子运维工作流中的部分子运维工作流。
例如，网络维护工作流可以包括：监控排障子运维工作流、网络巡检子运维工作流。相应的，目标运维工作流可以为网络维护工作流，也可以为监控排障子运维工作流，也可以为网络巡检子运维工作流。
又如，网络优化工作流可以包括：质量优化子运维工作流、能效优化子运维工作流等。相应的，目标运维工作流可以为网络优化工作流，也可以为质量优化子运维工作流，也可以为能效优化子运维工作流。
每个运维工作流或者子运维工作流包括至少一个运维步骤(也可以称为核心能力)。例如，网络规划工作流可以包括：意图翻译、需求分析预测、规划与仿真、网络设计四个运维步骤；监控排障工作流可以包括：故障与隐患识别、故障定界定位、故障处理三个运维步骤；质量优化工作流可以包括：意图翻译、质量问题识别、质量问题定位、方案生成和决策、方案实施效果验证五个运维步骤。
该步骤可以理解为：运维工作流包括一个或多个运维步骤，针对运维工作流中的目标运维工作流，第一装置可以确定第二装置针对目标运维工作流需支持的运维步骤需求。
示例性的，运维步骤需求描述了第一装置希望第二装置支持的运维步骤、运维步骤对应的自治状态需求、支持的场景，自治状态需求描述第二装置在运维步骤上的参与程度需求。例如，自治状态需求可以包括：
自治状态需求1：人工实施运维步骤；自治状态需求2：第二装置基于人工制定的规则实施运维步骤；自治状态需求3：第二装置基于人工制定的策略动态生成规则并实施所述运维步骤；自治状态需求4：第二装置基于人工智能(AI)/机器学习(ML)模型动态生成规则并实施运维步骤；自治状态需求5：第二装置能够自学习AI/ML模型并实施所述运维步骤。
应该理解的是，本实施例对运维步骤可以支持几种自治状态需求不做限定，上述示例只是用于示范性地说明，运维步骤可能支持的自治状态需求。
其中，第二装置支持的运维步骤的自治状态需求，描述的是第二装置参与实施运维步骤的程度，上面举例中人可以泛指第二装置以外的实施者，如可以是运维人员或者第一装置等。
运维工作流可以支持一个或者多个场景，不同的运维工作流可以支持的场景可能部分相同，也可以都相同，也可以完全不同，本实施例不做限定。场景的划分维度可以包括：网络制式、无线性能、无线网络中的一个或多个。
其中，网络制式可以包括：2G、3G、4G、5G等。无线性能可以包括：覆盖、容量、速率、能耗、时延等。无线网络环境可以包括：室内、室外-城区、室外-农村等。
每个场景可以由上述一个或多个维度上取值的任意组合，如质量优化子运维工作流的场景可以包括：4G城区覆盖优化场景，5G城区覆盖优化场景，4G速率优化场景，5G容量优化场景等。
不同场景的运维工作流的运维步骤可能相同，但运维步骤的运维步骤需求可能不同。
示例性的，以目标运维工作流为质量优化子运维工作流为例，S601可以包括如下步骤：
第一步骤：确定质量优化子运维工作流支持的场景。
其中，质量优化子运维工作流支持的场景可以包括：4G城区覆盖优化场景、5G城区覆盖优化场景、4G速率优化场景、5G容量优化场景。
第二步骤：确定质量优化子运维工作流包括的运维步骤。
其中，质量优化子运维工作流包括的运维步骤可以为：意图翻译、质量问题识别、质量问题 定位、方案生成和决策、方案实施效果验证中的一种或多种。
第三步骤：确定质量优化子运维工作流中每一运维步骤的自治状态需求，生成质量优化子运维工作流的整体运维步骤需求。质量优化子运维工作流的整体运维步骤需求包含了质量优化子运维工作流中每一运维步骤的自治状态需求。
示例性的，确定出的意图翻译的自治状态需求为自治状态需求1：人工实施；确定出的质量问题识别的自治状态需求为自治状态需求3：第二装置基于人工给的策略实施；确定出的质量问题定位的自治状态需求为自治状态需求2：系统基于人工给的规则实施；确定出的方案生成和决策的自治状态需求为自治状态需求3：系统基于人工给的策略实施；确定出的方案实施效果验证的自治状态需求为自治状态需求3：系统基于人工给的策略实施。
第四步骤：根据质量优化子运维工作流的整体运维步骤需求、以及第一装置自身部署的自治管理功能(Autonomy MnF)的自治能力情况，确定第二装置针对质量优化子运维工作流需支持的运维步骤需求。
例如，若第一装置自身部署的自治管理功能中包括：意图翻译的自治管理功能(可以实现意图翻译运维步骤的自治)、方案生成和决策的自治管理功能(可以实现方案生成和决策运维步骤的自治)，则确定出的第二装置针对质量优化子运维工作流需支持的运维步骤需求包括：质量问题识别，自治状态需求3：第二装置基于人工给的策略实施；质量问题定位，自治状态需求2：第二装置基于人工给的规则实施；方案实施效果验证，自治状态需求3：第二装置基于人工给的策略实施。
示例性的，如图7所示，质量优化子运维工作流的运维步骤需求可以包括两个维度的内容，一个维度的内容为支持场景的内容，一个维度的内容为运维步骤的内容。其中，支持场景的内容包括：4G城区覆盖优化场景、5G城区覆盖优化场景、4G速率优化场景、5G容量优化场景。运维步骤的内容为虚线框中的内容，即运维步骤2、运维步骤3、以及运维步骤5的内容，运维步骤1和运维步骤4的内容为第一装置自身部署的自治管理功能所支持的。
在本实施例中，第一装置向第二装置发送的运维步骤需求为除第一装置的自治管理功能能够实现的部分运维步骤需求之外的运维步骤需求，可以保障第一装置和第二装置针对目标运维工作流的合理分工和协同，避免重复实现。
S602：第一装置向第二装置发送运维步骤需求。
其中，运维步骤需求用于请求第二装置反馈与运维步骤需求对应的自治能力信息。
相应的，第二装置接收由运营商电信发送的运维步骤需求。
S603：第二装置确定与运维步骤需求对应的自治能力信息。
在本实施例中，第一装置向第二装置发送运维步骤需求来获取自治能力信息，能够精准获取与运维步骤需求对应的自治能力信息，避免获取无效的自治能力信息。
示例性的，第一装置能提供一个或者多个自治能力信息，不同的自治能力信息可能是针对不同的运维工作流或者相同的运维工作流。一个自治能力信息是由一组自治管理功能和对应的自治管理功能配置参数实现。
在一些实施例中，自治能力信息包括：自治能力标识(task Capability List)、运维工作流名称(workflow Name)、支持的自治网络等级(supported ANL List)、支持的自治网络等级对应的运维任务(Task)能力信息(task Capability List)、支持的场景名称(supported Scenario List)。
其中，自治能力标识，用于唯一识别一个自治能力。
运维工作流名称，用于识别一个运维工作流，如运维工作流名称可以为网络规划工作流，也可以为网络部署工作流，也可以为网络维护工作流，也可以为网络优化工作流，也可以为监控排障子运维工作流，也可以为网络巡检子运维工作流，也可以为质量优化子运维工作流、也可以为能效优化子运维工作流，等等，此处不再一一列举。支持的自治网络等级，可以是1级，2级，3级，4级和5级，以质量优化子运维工作流为例，3级，4级和5级都能满足自治能力的运维步骤需求。
运维任务能力信息包括运维任务的名称和运维任务的自治状态。以质量优化子运维工作流为例，运维任务的名称包括：监控规则和优化策略生成运维任务、网络/业务保障意图评估运维任务、 数据采集运维任务、性能异常识别运维任务、性能劣化预测运维任务、性能问题定界运维任务、性能问题根因分析运维任务、优化方案生成运维任务、优化方案评估和确定运维任务、优化方案执行。运维任务的自治状态包括：运维任务由人完成、运维任务由人和第二装置共同完成、第二装置完成。
在一些实施例中，结合图1可知，运维步骤和运维任务的对应关系可以理解如下：
数据采集运维任务、性能异常识别运维任务、性能劣化预测运维任务为用于实现质量问题识别的运维步骤。性能问题定界运维任务和性能问题根因分析运维任务为用于实现质量问题定位的运维步骤。优化方案执行运维任务为用于实现方案效果实施验证的运维步骤。
运维任务的自治状态如何匹配或者支撑要求的运维步骤需求描述如下：
数据采集运维任务和性能异常识别运维任务的自治状态为运维任务由第二装置完成，性能劣化预测运维任务的自治状态为运维任务由人和第二装置共同完成，可以匹配或者支撑质量问题识别运维步骤的运维步骤需求为第二装置基于人工策略实施。
性能问题定界运维任务的自治状态为运维任务由第二装置完成,性能问题根因分析运维任务的自治状态为运维任务由第二装置和人工共同完成，可以匹配或者支撑质量问题定位运维步骤的运维步骤需求为第二装置基于人工策略实施。
优化方案执行运维任务的自治状态为运维任务由第二装置完成，可以匹配或者支撑方案效果实施验证运维步骤的运维步骤需求为第二装置基于人工策略实施。
结合上述分析，支持的场景名称可以包括：4G城区覆盖优化场景、5G城区覆盖优化场景、4G速率优化场景和5G容量优化场景、5G速率优化场景、4G容量优化场景等。
S604：第二装置向第一装置发送自治能力信息。
相应的，第一装置接收由第二装置发送的自治能力信息。
在一些实施例中，第二装置可以基于接口模型信息(Information Model)向第一装置发送自治能力信息。其中，接口模型信息可以用于描述两个系统(即第二装置和第一装置)之间的交互信息。
示例性的，可读(is Readable)＝True用于描述接口调用者可以读取该参数，is Readable＝False用于描述接口调用者不能读取该参数；可配(is Writable)＝True用于描述接口调用者可以指定该参数取值，is Writable＝False用于描述接口调用者不能指定该参数取值。
相应的，自治能力信息的接口模型信息可以如表1所示，表1：
场景的接口模型信息可以如表2所示，表2：
运维任务能力信息的接口模型信息可以如表3所示，表3：
S605：第一装置根据获取的自治能力信息确定自治服务需求。其中，自治服务需求用于指示第二装置提供运维工作流的自治服务。
在一些实施例中，自治服务需求可以包括：自治服务需求标识(Autonomy Service Req Id)、运维工作流名称、关联的自治能力标识(Autonomy Capability Id)、场景信息(selected Scenario List)、目标自治性能指标(KEI Target List)。
其中，自治服务需求标识用于唯一识别一个自治服务需求。运维工作流名称用于识别一个运维工作流。关联的自治能力标识可以是一个或者多个关联的自治能力标识。选择的场景用于描述自治服务需求支持的场景名称。目标自治性能指标用于描述自治服务的性能需求，以质量优化子运维工作流为例，目标自治性能指标可以包括:覆盖性能提升比例或者覆盖质差栅格/小区减少比例、用户速率性能提升比例或者用户速率体验差用户减少比例、故障识别率提升比例、能耗减少比例、优化时长等。
在一些实施例中，S605可以包括：第一装置从自治能力信息中获取一个或者多个自治能力信息，并生成获取到的自治能力信息的配置值，从而得到自治服务需求。其中，生成的配置值包括：从多个支持的自治网络等级中获取的一个自治网络等级，以及从多个支持的场景中获取的一个或者多个场景等。
其中，第一装置根据还可以结合网络运维的成本、安全性、以及可靠性等，确定自治服务需求。
S606：第一装置向第二装置发送自治服务需求。
相应的，第二装置接收由第一装置发送的自治服务需求。
同理，第一装置可以基于接口模型信息向第二装置发送自治服务需求。示例性的，自治服务需求的接口模型信息可以如表1所示，表1：
S607：第二装置确定用于实现目标自治服务需求的自治管理功能，并生成确定出的自治管理功能的管控参数。
自治管理功能为第二装置中已部署的与自治相关的管理功能。示例性的，自治管理功能可以包括：管理数据分析功能、模型训练功能、数据采集功能(Data Collection Function)等。
其中，管理数据分析功能可以包括：覆盖分析功能(Coverage MDAF)、自管理网络(Self Organizing Network)功能(如容量和覆盖优化(CCO Function)功能)等。模型训练功能可以包括：机器学习功能(ML training Function)等。
自治管理功能的管控参数包括：自治管理功能的开关参数、自治管理功能之间的连接参数(如自治管理功能的IP地址或者URI信息)、自治管理功能的策略或者规则控制参数。
其中，自治管理功能之间的连接参数可以包括：自治管理功能的互联网协议地址(Internet Protocol Address)或者统一资源标识符(Uniform Resource Identifier，URI)信息。自治管理功能的策略或者规则控制参数可以包括：自治管理功能的执行时间、周期、以及可调参数的范围等。
S608：第二装置配置生成的管控参数。
S609：第二装置生成并向第一装置发送自治服务预评估结果信息。
相应的，第一装置接收由第二装置发送的自治服务预评估结果信息。
示例性的，自治服务预评估结果信息包括可行性评估结果(feasibility Result)，可行性结果用于表征第二装置是否支持自治服务需求，如第二装置中的自治管理功能是否可以实现与自治服务需求对应的自治服务。
在本实施例中，通过可行性评估结果，使得第一装置快速获取自治服务需求是否可以被提供的结果，以便及时作出调整，提高自治的实时性。
在一些实施例中，可行性评估结果可以表征第二装置可以支持自治服务需求，则预评估结果信息中还包括经S607确定出的自治管理功能的列表。
例如，可行性结果用于描述第二装置是否可以支持上自治服务需求，取值为可行和不可行；自治管理功能列表为支持自治服务需求需要使用的自治管理功能的信息，自治管理功能的信息包括自治管理功能的标识或者名称、以及自治管理功能的类型等。
同理，在一些实施例中，第二装置可以基于接口模型信息向营运商电信系统发送自治服务预评估结果信息。
在另一些实施例中，可行性评估结果可以表征第二装置可以支持自治服务需求，则第一装置可以修改自治服务需求，即返回至S605，以重新执行S605-S609，以使得可行性评估结果可以表征第二装置可以支持自治服务需求。
S610：第二装置执行自治服务需求对应的自治服务，生成并向第一装置发送自治服务执行结果信息。
相应的，第一装置接收由第二装置发送的自治服务执行结果信息。
示例性的，自治服务执行结果信息包括自治性能指标满足值。其中，自治性能满足值为第二装置执行自治服务时，得到的目标自治性能指标的实际测量值。
在一些实施例中，第二装置可以采用自治服务监控报告的方式向第一装置发送自治服务执行结果信息。如第二装置生成包括自治服务执行结果信息的自治服务监控报告，并向第一装置发送自治服务监控报告。
同理，第二装置可以基于接口模型信息向第一装置发送自治服务监控报告。示例性的，自治服务监控报告的接口模型信息可以如表4所示，表4：
在本实施例中，第二装置可以根据第一装置针对目标运维工作流的自治能力的运维步骤需求提供相应的自治能力，第一装置基于第二装置的自治能力指定针对不同场景的差异化自治服务需求，进而第二装置可以动态编排自治管理功能，提供差异化的自治服务，完成第一装置和第二装置针对目标运维工作流的分工和协同，避免重复实现。
需要说明的是，图6所示的实施例只是用于示范性地说明，本申请可能的实施例，而不能理解为对本申请实施例的限定。示例性的，结合图4所示的实施例、图5所示的实施例、以及图6所示的实施例可知：
图6所示的实施例中的S604-S606可以为一个实施例；图6所示的实施例中的S604-S609可以为一个实施例；图6所示的实施例中的S604-S610可以为一个实施例；图6所示的实施例中的S605-S606可以为一个实施例；图6所示的实施例中的S605-S609可以为一个实施例；图6所示的实施例中的S605-S610可以为一个实施例；图6所示的实施例中的S606-S609可以为一个实施 例；图6所示的实施例中的S606-S610可以为一个实施例；图6所示的实施例中的S603-S606可以为一个实施例；图6所示的实施例中的S603-S609可以为一个实施例；图6所示的实施例中的S603-S610可以为一个实施例；图6所示的实施例中的S602-S606可以为一个实施例；图6所示的实施例中的S602-S609可以为一个实施例；图6所示的实施例中的S602-S610可以为一个实施例。
请参阅图8，图8为本申请另一实施例的自治网络的自治方法的流程示意图。
如图8所示，该方法包括：
S801：第二装置向第一装置发送自治能力信息。
相应的，第一装置接收由第二装置发送的自治能力信息。
应该理解的是，为了避免繁琐地陈述，关于本实施例与上述实施例相同的技术特征，本实施例不再赘述。例如，关于自治能力信息地描述，可以参见上述实施例，此处不再赘述。
结合图6所示的实施例可知，图6所示的实施例中的自治能力信息是与运维步骤需求对应的自治能力信息，运维步骤需求为用于实现目标运维工作流的自治能力的运维步骤需求。也就是说，在图6所示的实施例中，自治能力信息为与目标运维工作流对应的自治能力的信息。而在本实施例中，自治能力信息为与各运维工作流各自对应的自治能力的信息。
例如，若目标运维工作流为各运维工作流中的某一运维工作流，则图6所示的实施例中的自治能力信息为该一个运维工作流对应的自治能力的信息，即用于实现该一个运维工作流的自治能力的信息，而在本实施例中，自治能力信息为实现各运维工作流中的每一运维工作流的自治能力的信息。
S802：第一装置根据自治能力信息确定自治服务需求。
在一些实施例中，S802可以包括如下步骤：
第一步骤：第一装置确定用于实现目标运维工作流的自治能力的运维步骤需求。
关于第一步骤的实现原理，可以参见S601，此处不再赘述。
第二步骤：第一装置确定与运维步骤需求对应的自治能力信息。
关于第二步骤的实现原理，可以参见S603，此处不再赘述。
在本实施例中，通过从各自治能力信息中确定与运维步骤需求对应的自治能力信息，可以保障第一装置和第二装置针对目标运维工作流的合理分工和协同，避免重复实现。
需要说明的是，在图6所示的实施例中，是由运营商将运维步骤需求发送给第二装置，以由第二装置匹配得到与运维步骤需求对应的自治能力信息，而在本实施例中，由于第二装置将用于实现各运维工作流的自治能力信息都发送给了第一装置，因此，当第一装置确定出运维步骤需求之后，可以从用于实现各运维工作流的自治能力信息中，选取与运维步骤需求对应的自治能力信息。
第三步骤：第一装置根据与运维步骤需求对应的自治能力信息，确定自治服务需求。
关于第三步骤的实现原理，可以参见S605，此处不再赘述。
S803：第一装置向第二装置发送自治服务需求。
相应的，第二装置接收由第一装置发送的自治服务需求。
关于S803的实现原理，可以参见S606，此处不再赘述。
S804：第二装置确定用于实现自治服务需求的自治管理功能，并生成确定出的自治管理功能的管控参数。
关于S804的实现原理，可以参见S607，此处不再赘述。
S805：第二装置配置生成的管控参数。
关于S805的实现原理，可以参见S608，此处不再赘述。
S806：第二装置生成并向第一装置发送自治服务预评估结果信息。
相应的，第一装置接收由第二装置发送的自治服务预评估结果信息。
关于S806的实现原理，可以参见S609，此处不再赘述。
S807：第二装置执行自治服务需求对应的自治服务，生成并向第一装置发送自治服务执行结果信息。
相应的，第一装置接收由第二装置发送的自治服务执行结果信息。
关于S807的实现原理，可以参见S610，此处不再赘述。
在本实施例中，第一装置基于第二装置的自治能力指定针对不同场景的差异化自治服务需求，进而第二装置可以动态编排自治管理功能，提供差异化的自治服务，完成第一装置和第二装置针对特定运维工作流的分工和协同，避免重复实现。
同理，图8所示的实施例只是用于示范性地说明，本申请可能的实施例，而不能理解为对本申请实施例的限定。关于图8实施例中的部分技术特征可以组成新的实施例的实现原理，可以参见对图6所示的实施例地描述，此处不再赘述。
根据本申请实施例的另一个方面，本申请还提供了一种自治网络的自治装置。图9为本申请一个实施例的自治网络的自治装置的示意图，如图9所示，该装置900包括：
第一接收单元901，用于接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息。
第一发送单元902，用于向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
图10为本申请另一实施例的自治网络的自治装置的示意图，该装置1000包括：
第一接收单元1001，用于接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息。
第一发送单元1002，用于向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
在一些实施例中，所述自治服务需求与所述自治能力信息关联是指，所述自治服务需求是所述装置1000根据所述自治能力信息确定的。
在一些实施例中，如图10所示，装置1000还可以包括：
第二接收单元1003，用于接收所述第二装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
在一些实施例中，运维工作流为目标运维工作流，如图10所示，装置1000还可以包括：
第二发送单元1004，用于向所述第二装置发送运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
在一些实施例中，装置1000部署的自治管理功能支持实现所述目标运维工作流的部分运维步骤需求，向所述第二装置发送的运维步骤需求为除所述自治管理功能支持实现所述目标运维工作流的部分运维步骤需求之外的运维步骤需求。
在一些实施例中，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
在一些实施例中，自治能力信息为多个，如图10所示，装置1000还可以包括：
确定单元1005，用于根据所述装置1000的运维步骤需求，从所述多个自治能力信息中，确定与所述运维步骤需求对应的自治能力信息，其中，所述运维步骤需求为用于实现运维工作流中的目标运维工作流的自治能力的需求；
以及，所述自治服务需求是基于获取到的与所述运维步骤需求对应的自治能力信息确定的。
在一些实施例中，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
在一些实施例中，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
图11为本申请另一实施例的自治网络的自治装置的示意图，该装置1100包括：
第三发送单元1101，用于向第一装置发送自治能力信息，其中，所述自治能力信息表征用于 实现运维工作流的自治能力的信息。
第三接收单元1102，用于接收所述第一装置发送的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联。
执行单元1103，用于执行所述自治服务需求所指示的所述运维工作流的自治服务。
图12为本申请另一实施例的自治网络的自治装置的示意图，该装置1200包括：
第三发送单元1201，用于向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息。
第三接收单元1202，用于接收所述第一装置发送的自治服务需求，其中，所述自治服务需求是所述第一装置基于所述自治能力信息确定的。
执行单元1203，用于执行所述自治服务需求所指示的所述运维工作流的自治服务。
在一些实施例中，如图12所示，该装置还可以包括：
第四发送单元1204，用于向所述第一装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
在一些实施例中，所述运维工作流为目标运维工作流，如图12所示，该装置1200还可以包括：
第四接收单元1205，用于接收所述第一装置发送的运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
在一些实施例中，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及所述自治能力对应支持的场景，所述自治状态需求用于表征所述装置1200在所述运维步骤上的参与程度需求。
在一些实施例中，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
在一些实施例中，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
图13为本申请另一实施例的自治网络的自治系统的示意图，如图13所示，该系统1300包括通信连接的第一装置1301和第二装置1302。第一装置1301可以为如图9或图10所示的装置，第二装置1302可以如图11或图12所示的装置。
根据本申请实施例的另一个方面，本申请实施例还提供了一种芯片，所述芯片包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如上任一实施例所述的方法。
根据本申请实施例的另一个方面，本申请还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机指令，当所述计算机指令在被处理器运行时，使得上述任一实施例所述的方法被执行。
根据本申请实施例的另一个方面，本申请还提供了一种计算机程序产品，当所述计算机程序产品在处理器上运行时，使得上述任一实施例所述的方法被执行。
根据本申请实施例的另一个方面，本申请还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的计算机指令，所述计算机指令被所述至少一个处理器执行，使得上述任一实施例所述的方法被执行。
请参阅图14，图14为本申请实施例的电子设备的结构示意图。
如图14所示，该电子设备包括存储器和处理器，该电子设备还可以包括通信接口和总线，其中，处理器、通信接口和存储器通过总线连接；处理器用于执行存储器中存储的可执行模块，例如计算机程序。
其中，存储器可能包含高速随机存取存储器(RAM，Random Access Memory)，也可能还包括 非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口可以是有线或者无线)实现该系统网元与至少一个其他网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等。
总线可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Enhanced Industry Standard Architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。
其中，存储器用于存储程序，处理器在接收到执行指令后，执行程序，前述本申请实施例任一实施例揭示的方法可以应用于处理器中，或者由处理器实现。
处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(Digital SignalProcessing，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现成可编程门阵列(Field-Programmable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
根据本申请实施例的另一个方面，本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质中存储有计算机执行指令，所述计算机执行指令被处理器执行时用于实现如上任一实施例所述的方法。
读者应理解，在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构或者特点包含于本申请的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必针对的是相同的实施例或示例。而且，描述的具体特征、结构或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
还应理解，在本申请各实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (29)

  1. 一种自治网络的自治方法，其特征在于，所述方法应用于第一装置，所述方法包括：
    接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
    向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收所述第二装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述运维工作流为目标运维工作流；在所述接收第二装置发送的自治能力信息之前，所述方法还包括：
    向所述第二装置发送运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一装置部署的自治管理功能支持实现所述目标运维工作流的部分运维步骤需求，向所述第二装置发送的运维步骤需求为除所述自治管理功能支持实现所述目标运维工作流的部分运维步骤需求之外的运维步骤需求。
  5. 根据权利要求3或4所述的方法，其特征在于，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
  6. 根据权利要求1-4中任一项所述的方法，其特征在于，所述自治能力信息为多个；在所述接收第二装置发送的自治能力信息之后，所述方法还包括：
    根据所述第一装置的运维步骤需求，从所述多个自治能力信息中，确定与所述运维步骤需求对应的自治能力信息，其中，所述运维步骤需求为用于实现运维工作流中的目标运维工作流的自治能力的需求；
    以及，所述自治服务需求是基于获取到的与所述运维步骤需求对应的自治能力信息确定的。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述自治服务需求与所述自治能力信息关联是指，所述自治服务需求是所述第一装置根据所述自治能力信息确定的。
  10. 一种自治网络的自治方法，其特征在于，所述方法应用于第二装置，所述方法包括：
    向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
    接收所述第一装置发送的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
    执行所述自治服务需求所指示的所述运维工作流的自治服务。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述第一装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
  12. 根据权利要求10或11所述的方法，其特征在于，所述运维工作流为目标运维工作流；在所述向第一装置发送自治能力信息之前，所述方法还包括：
    接收所述第一装置发送的运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
  13. 根据权利要求12所述的方法，其特征在于，所述运维步骤需求包括：运维步骤、所述运 维步骤对应的自治状态需求、以及所述自治能力对应支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
  14. 根据权利要求10-13中任一项所述的方法，其特征在于，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
  15. 根据权利要求10-14中任一项所述的方法，其特征在于，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
  16. 一种自治网络的自治方法，其特征在于，所述方法包括：
    第二装置向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
    所述第一装置向所述第二装置发送自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
    所述第二装置执行所述自治服务需求所指示的所述运维工作流的自治服务。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述第二装置向所述第一装置发送可行性评估结果，其中，所述可行性评估结果用于表征所述第二装置是否支持所述自治服务需求。
  18. 根据权利要求16或17所述的方法，其特征在于，所述运维工作流为目标运维工作流；在所述第二装置向第一装置发送自治能力信息之前，所述方法还包括：
    所述第一装置向所述第二装置发送运维步骤需求，其中，所述运维步骤需求用于请求所述自治能力信息，所述自治能力信息为满足所述运维步骤需求的用于实现所述目标运维工作流的自治能力的信息。
  19. 根据权利要求18所述的方法，其特征在于，所述第一装置部署的自治管理功能支持实现所述目标运维工作流的部分运维步骤需求，向所述第二装置发送的运维步骤需求为除所述自治管理功能支持实现所述目标运维工作流的部分运维步骤需求之外的运维步骤需求。
  20. 根据权利要求18或19所述的方法，其特征在于，所述运维步骤需求包括：运维步骤、所述运维步骤对应的自治状态需求、以及所述自治能力对应支持的场景，所述自治状态需求用于表征所述第二装置在所述运维步骤上的参与程度需求。
  21. 根据权利要求17-20中任一项所述的方法，其特征在于，所述自治能力信息为多个；所述方法还包括：
    所述第一装置根据所述第一装置的运维步骤需求，从所述多个自治能力信息中，确定与所述运维步骤需求对应的自治能力信息，所述运维步骤需求为用于实现运维工作流中的目标运维工作流的自治能力的需求。
  22. 根据权利要求17-21中任一项所述的方法，其特征在于，所述自治能力信息包括：自治能力标识、所述运维工作流的名称、支持的自治网络等级、支持的自治网络等级对应的运维任务能力信息、以及支持的场景信息中的至少一种。
  23. 根据权利要求17-22中任一项所述的方法，其特征在于，所述自治服务需求包括：自治服务需求标识、所述运维工作流的名称、关联的自治能力标识、自治网络等级、场景信息、目标自治性能指标中的至少一种。
  24. 一种自治网络的自治装置，其特征在于，所述装置包括：
    第一接收单元，用于接收第二装置发送的自治能力信息，其中，所述自治能力信息表征用于实现运维工作流的自治能力的信息；
    第一发送单元，用于向所述第二装置发送所述运维工作流的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联，所述自治服务需求用于指示第二装置提供所述运维工作流的自治服务。
  25. 一种自治网络的自治装置，其特征在于，所述装置包括：
    第三发送单元，用于向第一装置发送自治能力信息，其中，所述自治能力信息表征用于实现 运维工作流的自治能力的信息；
    第三接收单元，用于接收所述第一装置发送的自治服务需求，其中，所述自治服务需求与所述自治能力信息关联；
    执行单元，用于执行所述自治服务需求所指示的所述运维工作流的自治服务。
  26. 一种自治网络的自治系统，其特征在于，所述系统包括通信连接的第一装置和第二装置；其中，
    所述第一装置，用于执行如权利要求1-9中任一项所述的方法；
    所述第二装置，用于执行如权利要求10至15中任一项所述的方法。
  27. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机指令，当所述计算机指令在被处理器运行时，使得权利要求1至9中任一项所述的方法被执行；或者，使得权利要求10至15中任一项所述的方法被执行；或者，使得权利要求16至23中任一项所述的方法被执行。
  28. 一种电子设备，其特征在于，包括：
    至少一个处理器；以及
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的计算机指令，所述计算机指令被所述至少一个处理器执行，使得权利要求1至9中任一项所述的方法被执行；或者，使得权利要求10至15中任一项所述的方法被执行；或者，使得权利要求16至23中任一项所述的方法被执行。
  29. 一种计算机程序产品，其特征在于，当所述计算机程序产品在处理器上运行时，使得权利要求1至9中任一项所述的方法被执行；或者，使得权利要求1至8中任一项所述的方法被执行；或者，使得权利要求10至15中任一项所述的方法被执行；或者，使得权利要求16至23中任一项所述的方法被执行。
PCT/CN2023/123905 2022-10-14 2023-10-11 自治网络的自治方法和装置 WO2024078519A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211260983.3 2022-10-14
CN202211260983.3A CN117896759A (zh) 2022-10-14 2022-10-14 自治网络的自治方法和装置

Publications (1)

Publication Number Publication Date
WO2024078519A1 true WO2024078519A1 (zh) 2024-04-18

Family

ID=90638167

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/123905 WO2024078519A1 (zh) 2022-10-14 2023-10-11 自治网络的自治方法和装置

Country Status (2)

Country Link
CN (1) CN117896759A (zh)
WO (1) WO2024078519A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600760A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络管理方法、设备及系统
CN112202900A (zh) * 2020-09-30 2021-01-08 无锡雪浪数制科技有限公司 一种新型架构的边缘计算系统
WO2022061900A1 (zh) * 2020-09-28 2022-03-31 华为技术有限公司 故障自治能力的确定方法以及相关设备
WO2022170921A1 (zh) * 2021-02-09 2022-08-18 华为技术有限公司 网络问题信息获取方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600760A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 网络管理方法、设备及系统
WO2022061900A1 (zh) * 2020-09-28 2022-03-31 华为技术有限公司 故障自治能力的确定方法以及相关设备
CN112202900A (zh) * 2020-09-30 2021-01-08 无锡雪浪数制科技有限公司 一种新型架构的边缘计算系统
WO2022170921A1 (zh) * 2021-02-09 2022-08-18 华为技术有限公司 网络问题信息获取方法、装置及系统

Also Published As

Publication number Publication date
CN117896759A (zh) 2024-04-16

Similar Documents

Publication Publication Date Title
US10536866B2 (en) Orchestrating wireless network operations
EP4160995A1 (en) Data processing method and device
US10390276B2 (en) Method for traffic steering and network element
US11855873B2 (en) Virtualized cellular network multi-stage test and ticketing environment
WO2022061900A1 (zh) 故障自治能力的确定方法以及相关设备
US11218369B2 (en) Method, apparatus and system for changing a network based on received network information
CN113709777A (zh) 一种故障处理方法、装置及系统
US20230403223A1 (en) Data analysis apparatus management and control method and communication apparatus
WO2023045931A1 (zh) 一种网络性能异常分析方法、装置及可读存储介质
WO2024078519A1 (zh) 自治网络的自治方法和装置
CN111866977A (zh) 信息传递方法、装置、存储介质及电子装置
Zeydan Android vs. IOS: a comparative analysis over mobile operator infrastructures based on crowdsourced mobile dataset
Galani et al. Design and assessment of functional architecture for optimized spectrum and radio resource management in heterogeneous wireless networks
Algar et al. A quality of experience management framework for mobile users
CN105027497B (zh) 一种信息处理的方法及装置
Ferreira et al. Enhancing Network Performance based on 5G Network Function and Slice Load Analysis
WO2023185467A1 (zh) 一种网络自治能力评估方法、装置及存储介质
WO2024093876A1 (zh) 一种通信方法及装置
WO2024051805A1 (zh) 一种运维网络自治等级的评估方法、装置及系统
WO2021204075A1 (zh) 一种网络自动化管理方法及装置
WO2023241320A1 (zh) 自治系统的网络优化功能的指标确定方法和装置
EP4329359A1 (en) Telecommunications network optimisation based on cdr databases
WO2023185711A1 (zh) 一种用于机器学习模型训练的通信方法及装置
Gelonch et al. A real time emulator demonstrating advanced resource management solutions
Almomani et al. Architectural framework for wireless mobile ad hoc networks (AF WMANETs)

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: 23876720

Country of ref document: EP

Kind code of ref document: A1