WO2022057564A1 - 通信方法及装置、系统 - Google Patents

通信方法及装置、系统 Download PDF

Info

Publication number
WO2022057564A1
WO2022057564A1 PCT/CN2021/113637 CN2021113637W WO2022057564A1 WO 2022057564 A1 WO2022057564 A1 WO 2022057564A1 CN 2021113637 W CN2021113637 W CN 2021113637W WO 2022057564 A1 WO2022057564 A1 WO 2022057564A1
Authority
WO
WIPO (PCT)
Prior art keywords
intent
translation result
network element
target
intention
Prior art date
Application number
PCT/CN2021/113637
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 WO2022057564A1 publication Critical patent/WO2022057564A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the technical field of network intelligent management, and in particular, to a communication method, device, and system.
  • the intent implementation process includes intent translation, execution, and maintenance.
  • the intent translation functional block is responsible for intent translation, and the translation result is sent to the policy management functional block, which executes and maintains the intent.
  • intent translation occurs only once before execution, and the result of the translation is used for intent execution and maintenance (if needed). In the process of maintaining intent, there is no need for the participation of the intent translation function module.
  • Function modules such as policy management adjust the intent execution command according to the translation result of the intent translation function module, and send the execution command to the assisted system for execution.
  • intents include the following types: configuration intents, optimization intents, network maintenance intents, and business assurance intents.
  • configuration intents For the first three intents, the translation of the intent is only executed once, and the translation result can meet the needs of execution and maintenance.
  • the fourth kind of intent that is, business assurance intent
  • a single translation result is not enough for the intent execution and maintenance phases. Because for the fourth type of intent, the intent execution command in the intent execution phase is the configuration of a network, and the intent execution command in the intent maintenance phase is the adjustment of network performance, that is, the configuration plus optimization intent.
  • the intent commands required in the intent execution and maintenance phases are different (the intent execution command is part of the intent translation result), and the command group required in the intent maintenance phase is affected by the intent execution phase. It is difficult for the group to achieve the intention goal in the intention maintenance stage.
  • the present application provides a communication method, device, and system to solve the problem that the current intent single translation result cannot satisfy intent execution and maintenance at the same time.
  • a first aspect provides a communication method, the method includes: a first network element acquires performance data during an intent execution process, the intent includes a first intent target and a second intent target; the first network element according to The performance data during the execution of the intent determines that the second intent target has not been achieved; the first network element translates the intent according to the second intent objective to obtain a first translation result; and the The first network element sends the first execution command corresponding to the first translation result to the second network element.
  • the method before the first network element acquires the performance data during the execution of the intent, the method further includes: the first network element translates the intent to obtain a second translation result; The first network element performs a network state judgment and a judgment on whether the first intention target is achieved, and updates the second translation result according to the network status judgment and the judgment result of whether the first intention target is achieved; and the The first network element marks the second translation result and the updated second translation result by using the first stage identifier, and the first stage identifier is used to mark the second translation result and the updated second translation result.
  • the translation result is used in the intent execution process.
  • the method further includes: the first network element determines, according to the first stage identifier, whether the intent is to be Perform translation again to obtain the first translation result; and the first network element marks the first translation result with a second stage identifier, and the second stage identifier is used to mark the first translation result with in the intent maintenance process.
  • the first network element translates the intent according to the second intent target to obtain a first translation result, including: acquiring the second intent by the first network element the intent expression corresponding to the target; the first network element obtains the intent knowledge according to the intent expression corresponding to the second intent target; and the first network element arranges the intent knowledge to obtain a first translation result .
  • the first intent is network configuration
  • the second intent is adjustment of network performance
  • a communication apparatus in a second aspect, includes: a processing unit configured to acquire performance data during the execution of an intent, where the intent includes a first intent target and a second intent target; the processing unit, further for determining that the second intent target is not achieved according to the performance data during the execution of the intent; the processing unit is further configured to translate the intent according to the second intent target to obtain a first translation result; and a transceiver unit, configured to send a first execution command corresponding to the first translation result to the second network element.
  • the processing unit is further configured to translate the intent to obtain a second translation result; the processing unit is further configured to determine the network status and whether the first intent goal is achieved , and update the second translation result according to the network state judgment and the judgment result of whether the first intention goal is achieved; and the processing unit is also used to use the first stage identifier to interpret the second translation result. and the updated second translation result is marked, and the first stage identification is used to mark the second translation result and the updated second translation result for the intent execution process.
  • the processing unit is further configured to translate the intent again according to the first stage identifier when it is determined that the second intent target has not been achieved to obtain the first translation result; and the processing unit, further configured to mark the first translation result with a second stage identifier, where the second phase identifier is used to mark the first translation result for an intent maintenance process.
  • the processing unit is further configured to obtain an intent expression corresponding to the second intent target; the processing unit is further configured to obtain an intent expression corresponding to the second intent target according to the second intent target , to obtain intent knowledge; and the processing unit is further configured to arrange the intent knowledge to obtain a first translation result.
  • the first intent is network configuration
  • the second intent is adjustment of network performance
  • a communication device in a third aspect, may be a first network element in the first aspect or any possible implementation of the first aspect, or a module applied in the first network element, such as a chip or system-on-chip.
  • the communication apparatus includes at least one processor configured to execute the method in the first aspect or any possible implementation of the first aspect.
  • the communication device further includes a memory coupled to the at least one processor for performing the method in the first aspect or any possible implementation of the first aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled to the at least one processor, and the at least one processor can invoke and execute program instructions stored in the memory for performing the method in the first aspect or any possible implementation of the first aspect.
  • the communication apparatus further includes a communication interface for the communication apparatus to communicate with other devices.
  • the communication interface is a transceiver, an input/output interface, or a circuit or the like.
  • the communication device includes: at least one processor and a communication interface for executing the method in the first aspect or any possible implementation of the first aspect, specifically including: the at least one processor
  • the communication device communicates with the outside using the communication interface; the at least one processor is configured to run a computer program, so that the communication device executes the method in the first aspect or any possible implementation of the first aspect.
  • the external may be an object other than the processor, or an object other than the communication device.
  • the communication device is a chip or a system of chips.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip or the chip system.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • a communication system including the communication apparatus according to the second aspect or any one of the implementation of the second aspect, and a second network element.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer executes the first aspect or any one of the first aspects. method described.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to execute the above first aspect or any one of the first aspects to implement the method.
  • a chip is provided, the chip is coupled with a memory, and implements the communication method in the first aspect or any one of the first aspects of the embodiments of the present application.
  • Coupled in the embodiments of the present application means that two components are directly or indirectly combined with each other.
  • Fig. 1 is the schematic flow chart of existing intention implementation
  • FIG. 2 is a schematic diagram of an intent-based experiential networked intelligence (ENI) architecture
  • FIG. 3 is a schematic diagram of the architecture of a communication system to which the application is applicable;
  • FIG. 4 is a schematic diagram of the architecture of an example open network automation platform (ONAP);
  • ONAP open network automation platform
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of intent translation and execution in another communication method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of an intent maintenance in the communication method shown in FIG. 6;
  • FIG. 8 is a schematic flowchart of yet another intent maintenance in the communication method shown in FIG. 6;
  • FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a module of a communication device according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a hardware structure of a communication apparatus according to an embodiment of the present application.
  • ENI defines a cognitive network management architecture based on the observation direction to determine the behavior control model. It uses artificial intelligence (AI) technology and context-aware strategies to adjust the services provided according to changes in user needs, environmental conditions and business objectives.
  • AI artificial intelligence
  • the system is empirical in that it learns from the operator's instructions to improve its actions in the future. This can help operators automate their network configuration and monitoring process, thereby reducing operating expenses and improving the use and maintenance of their networks.
  • Intent driven management is started in order to shield the differentiation of device manufacturers. Only the intent model is retained in the network management system (NMS), and the intent expression is passed to the element management system (EMS). The intent expression only describes what to do, not how to do it. Only basic conceptual knowledge in the wireless field can be used to complete the intent design, thereby lowering the O&M threshold.
  • an intent-based ENI architecture is defined, as shown in Figure 2, which is capable of simultaneously supporting two types of policies.
  • the ENI system contains 11 functional blocks (FB), which can be divided into four categories: input function module, output function module, analysis function module and decision function module.
  • FB functional blocks
  • input function module output function module
  • analysis function module analysis function module
  • decision function module decision function module
  • Input function module It includes a data ingestion function module and a normalization function module.
  • the input function module is responsible for receiving data from external systems and normalizing the data.
  • Output functional module It includes an output generation functional module and a denormalisation functional module.
  • the output function module is responsible for converting the internal command of the system into a format that can be processed by the external system and sending it to the external system.
  • Analysis function module it includes knowledge management function module, context awareness function module and cognition management function module.
  • the analysis function module is responsible for perceptual analysis of the existing network context and prediction of the future network state.
  • Decision-making function module it includes policy management function module, situational awareness function module and model-driven engineering function module. Based on the perception of network state, the decision-making function module generates a new strategy according to the strategy target and arranges the strategy, and sends the operation command to the output module.
  • ENI further defines functional modules related to intent translation, intent execution and maintenance. Specifically, the ENI fusion architecture adds an intent knowledge repository to the knowledge management function module, adds an intent policy fulfillment sub-function module to the policy management function module, and also introduces an independent The intent translation function module.
  • the intent translation function module is used to perform intent translation on the received intent policy.
  • the intent knowledge base used to store expert experience and network element information, can be used as an independent functional module, or can be placed in the knowledge management functional module in the existing ENI architecture.
  • the intent policy execution function module is used to implement the intent execution and maintenance functions, and is responsible for arranging the intent policy and continuously meeting the intent requirements of the external system.
  • the intent enforcement process includes intent translation, execution, and maintenance.
  • intent translation function module is responsible for intent translation, and the translation result is sent to the policy management function module, which executes and maintains the intent.
  • policy management function module adjusts the intent executable command according to the achievement of the intent.
  • a complete intent policy consists of two parts: IntentDrivenAction and IntentDrivenObject, which represent the execution action and target of the intent policy respectively.
  • the intents include the following types: configuration intents, optimization intents, network maintenance intents, and business assurance intents. As shown in Table 1 below:
  • the translation of the intent is only executed once, and the translation result can meet the needs of execution and maintenance.
  • the fourth kind of intent that is, business assurance intent
  • a single translation result is not enough for the intent execution and maintenance phases. Because for the fourth type of intent, the intent execution command in the intent execution phase is the configuration of a network, and the intent execution command in the intent maintenance phase is the adjustment of network performance, that is, the configuration plus optimization intent.
  • the intent commands required in the intent execution and maintenance phases are different (the intent execution command is part of the intent translation result), and the command group required in the intent maintenance phase is affected by the intent execution phase. It is difficult for the group to achieve the intention goal in the intention maintenance stage.
  • the present application provides a communication solution.
  • the intent can be translated again, and the execution command can be adjusted according to the intent translation result, thereby increasing the probability of achieving the intent.
  • the communication system 100 includes a first network element 200 and a second network element 300 .
  • the first network element 200 may be an ENI system or an ONAP system, which includes multiple functional blocks (functional blocks, FBs).
  • the second network element 300 may be an assisted system.
  • the first network element 200 receives the intention creator, such as a user (user)/application (application, APP)/operation support system and other functional entities (operation support systems-like, OSS-like)/business support system and other functional entities (business support). systems-like, BSS-like) and other requests to create an intent, translate the intent, obtain an intent execution command, and send it to the second network element 300 for execution.
  • the intention creator such as a user (user)/application (application, APP)/operation support system and other functional entities (operation support systems-like, OSS-like)/business support system and other functional entities (business support).
  • systems-like, BSS-like and other requests to create an intent, translate the intent, obtain an intent execution command, and send it to the second network element
  • the communication system may be an intent-based ENI architecture as shown in FIG. 2 , or may be an ONAP as shown in FIG. 4 .
  • ONAP supports intents, which include:
  • ONAP UUI used to send intent creation instructions and receive intent execution results, is equivalent to the intent creator of the ENI system, such as user/APP/OSS-like/BSS-like, etc.
  • An intent framework for intent assurance, which includes several functional modules during intent execution. Specifically, including:
  • Intent management function module (intent management FB), intent translation function module, intent decision function module (intent decision FB) and intent verification function module (intent verification FB).
  • intent decision FB is equivalent to the intent processing FB in the ENI system.
  • A&AI Active & available inventory
  • resources refer to elements that constitute a service such as central processing unit (CPU), storage, network connection, virtualization network function (VNF), etc.
  • a service is a combination of multiple resources of.
  • A&AI can be regarded as a dynamic resource management library. It includes an intent knowledge base.
  • the intent translation function module can obtain intent knowledge from A&AI according to intent keywords.
  • DCAE ONAP data collection analytics and events
  • the DCAE platform mainly completes data collection. These structured or unstructured data can be persisted to what it calls a data lake.
  • the DCAE platform also provides a series of data analysis frameworks.
  • DCAE analytic applications are analytical applications developed based on the data analysis framework of the DCAE platform and collected data.
  • DCAE also provides closed-loop feedback capability. After analyzing the application results, it can call relevant actions to trigger ONAP service orchestration (SO) and ONAP controllers (controllers) to adjust the network services of the existing network.
  • SO ONAP service orchestration
  • controllers controllers
  • ONAP controller It is the core of network control in ONAP. It can interact with local controllers or network components in various virtual environments through network adapters.
  • ONAP SO A component executes a specified process by automatically and sequentially executing the activities, tasks, rules, and policies required to create, modify, or remove network, application, or infrastructure business and resources on demand.
  • SO is orchestrated at a very high level and provides an end-to-end view of infrastructure, network and applications.
  • Policy is a key link in the realization of closed-loop automation, responsible for the maintenance, distribution and processing of policy rule sets. Policies provide a centralized environment for creating and managing easily updated conditional rules.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application, the method may include the following steps:
  • a first network element acquires performance data during an intent execution process.
  • the intent includes a first intent target and a second intent target.
  • the first intent target is network configuration
  • the second intent target is network performance adjustment.
  • the intent may be the above-mentioned business assurance class intent, wherein the first intent objective of the intent is configuration, and the second intent objective of the intent is performance optimization.
  • the first intent object may be an intent object in an intent execution process
  • the second intent object may be an intent object in an intent maintenance process.
  • the first network element acquires the performance data during the execution of the intent, it further includes the following steps A1 to A3:
  • the first network element translates the intent to obtain a second translation result.
  • the first network element judges the network status and whether the first intention is achieved, and updates the second translation result according to the network status judgment and the judgment result of whether the first intention is achieved.
  • the first network element marks the second translation result and the updated second translation result by using a first stage identifier, and the first stage identifier is used to mark the second translation result and the updated second translation result.
  • the second translation result is used in the intent execution process.
  • the first network element receives an intent creation request sent by an intent creator, where the intent creation request includes an intent expression.
  • the intent expression includes the execution action of the intent policy and the goal.
  • the first network element translates the intent policy to obtain a second translation result, and the second translation result is used in the intent execution phase.
  • the first network element may mark the second translation result by using a first stage identifier, where the first phase identifier is used to mark the second translation result for the intent execution process.
  • the first network element judges the network state and whether the first intent goal is reached, and updates the second translation result according to the network state judgement and the judgment result of whether the first intent goal is met.
  • the first network element may mark the updated second translation result using a first stage identifier, where the first phase identifier is used to mark the updated second translation result for the intent execution process.
  • the first network element converts and makes decisions on the intent translation result, obtains executable commands or rules after the decision, and finally sends the execution commands or rules to the second network element (ie, the entity affected by the intent or the entity that acts on the intent) for execution.
  • the second network element ie, the entity affected by the intent or the entity that acts on the intent
  • the first network element acquires performance data during the execution of the intent. Specifically, the first network element obtains the performance data of the entity in the process of executing the intent from the second network element.
  • the performance data includes network status and the like.
  • the first network element determines, according to the performance data during the execution of the intent, that the second intent target has not been achieved.
  • the intent execution stage is mainly to execute the execution command corresponding to the translation result of the first intent target, and the execution process also judges whether the network state can satisfy the execution of the first intent target. After obtaining the performance data in the process, it is judged whether the second intention goal is achieved according to the performance data.
  • the first network element translates the intent according to the second intent target, and obtains a first translation result.
  • the first network element may translate the intent again according to the second intent target to obtain a first translation result.
  • step S103 includes: the first network element obtains the intent expression corresponding to the second intent target;
  • the first network element acquires the intent knowledge according to the intent expression corresponding to the second intent target;
  • the first network element arranges the intent knowledge to obtain a first translation result.
  • the first network element obtains the intent expression corresponding to the second intent target.
  • the intent expression may be the same as the intent expression obtained from the intent creator in the translation phase, or may be the intent expression sent by the intent creator. obtained by conversion.
  • the first network element may also acquire the service indicator corresponding to the second intent target without constructing an intent expression.
  • the first network element acquires the intent knowledge from the intent knowledge base according to the intent expression corresponding to the second intent target. After obtaining the intent knowledge, the first network element arranges the intent knowledge obtained according to the intent expression corresponding to the second intent target again to obtain the first translation result.
  • the first network element determines to translate the intent again according to the first stage identification, and after obtaining the first translation result, the first network element marks the first translation result with the second stage identification, and the second stage identification is used for The first translation result is marked for the intent maintenance process.
  • the first network element sends a first execution command corresponding to the first translation result to the second network element.
  • the second network element receives and executes the first execution command.
  • the first network element converts the first translation result into a form that can be understood by the intended entity according to the first translation result obtained by re-translation, that is, obtains the first execution command, and sends the first execution command to the second network element.
  • the second network element receives and executes the first execution command.
  • an intent translation request in the intent maintenance phase is added, so that the intent system can dynamically adjust the execution strategy corresponding to the intent according to the achievement of the intent goal during the intent maintenance phase.
  • the translation of the existing intent occurs only once before the intent execution phase.
  • intent translation is added in the intent maintenance phase, and multiple intent translations will occur throughout the life cycle of the intent. It enables the intent system to use more accurate translation results to adjust the commands, rules or sub-intents executable by the intent during the maintenance phase.
  • the intent can be translated again, and the execution command can be adjusted according to the intent translation result, thereby improving the probability of achieving the intent target.
  • FIG. 6 it is a schematic flowchart of intent translation and execution in another communication method provided by an embodiment of the present application, and the message between the intent execution module and the intent translation module uses the existing intent translation message.
  • the method may include the following steps:
  • the data ingestion&normalization FB sends a "new policy" message, which is used to instruct the creation of a new intent policy, which is an intent policy.
  • the message contains policyRefPoint, policyContent and policyMetadata.
  • the policyRefPoint parameter refers to the creator of the schematic strategy
  • policyContent refers to the schematic expression
  • policyMetadata refers to the relevant information of the schematic strategy, such as the validity period of the intent.
  • the data Ingestion&normalization FB normalizes the received intent policy and related data, and sends the normalized data to the knowledge management FB.
  • the knowledge management FB updates the local database according to the received normalized data.
  • the knowledge management FB sends a translation request to the intenttranslation FB.
  • the translation request carries information such as policyContent and policyMetadata.
  • the intenttranslation FB assigns an intent identifier to the intent policy.
  • the intent translation FB sends an identity update request to the knowledge management FB, where the identity update request is used to request to update the intent identity in the knowledge management FB.
  • the identity update request includes the above-mentioned intent identity.
  • the intenttranslation FB sends a response message to the user/app/OSS-like/BSS-like through the denormalisation&output generation FB, where the response message is used to inform that the intent has been processed.
  • intenttranslation FB performs intent syntax and lexical checking.
  • the intent translation FB feeds back intent error information to the knowledge management FB.
  • intenttranslation FB extracts intent keywords.
  • the intenttranslation FB sends an intent keyword update message to the knowledge management FB.
  • the intent keyword update message is used to request to update intent keywords in the knowledge management FB.
  • the intent keyword update message includes the intent keyword described above.
  • the intenttranslation FB sends an intent knowledge acquisition request to the knowledgemanagement FB.
  • the intent knowledge acquisition request includes the above intent keyword.
  • the intent knowledge includes an intent operation instruction ⁇ running condition, execution command> ⁇ (intentInstruction ⁇ executionCondition, Instruction> ⁇ ), an identifier (entityId) of an intent action device, and an execution target (fulfillmentCriterion).
  • intentInstruction represents the set of execution conditions and corresponding execution command pairs
  • entityId refers to the identifier of the device that acts on the schematic diagram
  • fulfillmentCriterion is used to judge whether the intent goal is achieved.
  • the intent translation FB arranges the received intent knowledge, and fills the entityId into the execution command in the intentInstruction.
  • the intent translation FB sends an intent knowledge update request to the knowledgemanagement FB, and updates the programmed intent policy, rule or self-intent to the intent context.
  • the intent translation FB sends a policy completion message to the context awareness FB.
  • the policy completion message carries the intent translation result and the first stage flag (flag).
  • the first stage identifier is used to indicate that the intent translation result is used in the intent execution phase.
  • the context awareness FB judges the network state, and updates the network state as the intent context information to the knowledgemanagement FB. And the context awareness FB sends the updated intent translation result to the situation awareness FB, carrying the first stage identifier, which is used to indicate that the intent translation result is used in the intent execution phase.
  • the situation awareness FB judges whether the intention goal is achieved, and updates the achievement status of the intention goal as the intention context information to the knowledgemanagement FB. And the situation awareness FB sends the updated intent translation result to the model-driven engineering FB, carrying the first stage identifier, which is used to indicate that the intent translation result is used in the intent execution phase.
  • model-driven engineering FB converts the translation result into a form that can be understood by the intended entity. And update the updated information to the knowledgemanagement FB. And send the updated intent translation result to the policy management FB, carrying the first stage identifier, the first phase identifier is used to indicate that the intent translation result is used in the intent execution phase.
  • the policy management FB converts and makes decisions on the intent translation result, and updates the executable commands or rules obtained after the decision to the knowledge management FB. And send the executable command or rule obtained after the decision to the denormalisation&output generation FB.
  • denormalisation & output generation FB will denormalize the execution command or rule and send it to the entity that is intended to be affected.
  • FIG. 7 it is a schematic flowchart of an intent maintenance in the communication method shown in FIG. 6 , and the method may include the following steps:
  • the context awareness FB after the context awareness FB receives the policy completion message, trigger the context awareness FB to send a performance data subscription request to the assisted system through the denormalisation&output generation FB.
  • the performance data subscription request is used to request the performance data of the assisted system.
  • the assisted system reports performance data to the data ingestion&normalization FB.
  • the data ingestion&normalization FB normalizes the performance data, and sends the processed data to the knowledge management FB.
  • the knowledge management FB stores the processed performance data, and sends the performance data and intent context information to the context awareness FB.
  • This intent context information is generated during the intent translation and execution phases described above.
  • the context awareness FB judges the network state according to the performance data, adds the network state information to the context information, and updates the intention context information to the knowledge management FB, and sends the updated context information to the situation awareness FB.
  • the situation awareness FB judges whether the intention is satisfied according to the performance data, and updates the intention satisfaction status as context information to the knowledge management FB, and sends the updated context information to the model-driven engineering FB.
  • the model-driven engineering FB adjusts or generates the intent policy according to the intent context information, updates the adjusted or generated intent policy to the knowledge management FB, and sends the updated intent policy and context information to the policy management FB.
  • the policymanagement FB firstly judges the achievement of the intent, and if not achieved, then determines that an intent translation request (translatePolicy) needs to be sent to the intent translation FB according to the flag information received during the intent execution phase.
  • This message carries an intent expression.
  • the intent expression can be the same as the intent expression obtained from the intent creator in the translation stage, or it can be transformed from the intent expression sent by the intent creator.
  • the intent translation FB sends an intent knowledge acquisition request to the knowledgemanagement FB, where the intent knowledge request carries an intent keyword.
  • the knowledgemanagement FB sends the intent knowledge to the intent translation FB, where the intent knowledge carries a second-stage identifier, and the second-phase identifier is used to identify the intent information for use in the intent maintenance phase.
  • the second stage identification information is optional.
  • the intent translation FB sends a policy completion message to the context awareness FB.
  • the strategy completion message carries the intent translation result and the second stage identifier.
  • the second stage flag is used to indicate this intent translation result for intent maintenance use.
  • the context awareness FB judges the network state, and updates the network state as the intention context information in the knowledgemanagement FB (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the situation awareness FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the situation awareness FB judges whether the intention target is achieved, and updates the achievement status of the intention target into the knowledgemanagement FB as the intention context information (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the model-driven engineering FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the model-driven engineering FB converts the translation result into a form that can be understood by the intent-acting entity. And update the updated information into the knowledge management FB (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the policy management FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the policy management FB converts and makes decisions on the intent translation result, and sends the executable commands or rules obtained after the decision to the knowledge management FB for storage, and sends the executable commands or rules obtained after the decision to denormalisation&output generation fb.
  • denormalisation & output generation FB sends execution commands or rules to entities intended to affect.
  • an intent translation request between the intent execution module and the intent translation module in the intent maintenance phase is added, so that the intent system can dynamically adjust the execution strategy corresponding to the intent according to the achievement of the intent goal during the intent maintenance phase.
  • the translation of the existing intent occurs only once before the intent execution phase.
  • intent translation is added in the intent maintenance phase, and multiple intent translations will occur throughout the life cycle of the intent. It enables the intent system to use more accurate translation results to adjust the commands, rules or sub-intents executable by the intent during the maintenance phase.
  • FIG. 8 it is a schematic flowchart of another intent maintenance in the communication method shown in FIG. 6 .
  • This method is applied to the ENI architecture shown in Figure 2.
  • the difference between the intent maintaining method and the intent maintaining method shown in FIG. 7 is that the message between the intent execution and intent translation modules in the intent maintaining method adopts a new message, and the message carries intent-related parameters, that is, the message in FIG. 8 .
  • S409 is different from the message S309 in the embodiment shown in FIG. 7 .
  • the method includes the following steps:
  • the context awareness FB after the context awareness FB receives the policy completion message, trigger the context awareness FB to send a performance data subscription request to the assisted system through the denormalisation&output generation FB.
  • the performance data subscription request is used to request the performance data of the assisted system.
  • the assisted system reports performance data to data ingestion&normalization.
  • the knowledge management FB stores the processed performance data, and sends the performance data and intent context information to the context awareness FB, and the intent context information is generated in the intent translation and execution stages.
  • the context awareness FB judges the network state according to the performance data, adds the network state information to the context information, and updates the intention context information to the knowledge management FB, and sends the updated context information to the situation awareness FB.
  • the situation awareness FB judges whether the intention is satisfied according to the performance data, and updates the intention satisfaction situation as context information to the knowledge management FB, and sends the updated context information to the model-driven engineering FB.
  • the model-driven engineering FB adjusts or generates the intent policy according to the intent context information, updates the adjusted or generated intent policy to the knowledge management FB, and sends the updated intent policy and context information to the policy management FB.
  • the policymanagement FB firstly judges the achievement of the intent, and if it is not achieved, then determines that an intent translation request (translatePolicyForAssurance) needs to be sent to the intent translation FB according to the flag information received during the intent execution phase.
  • intent translation request translatePolicyForAssurance
  • the parameters carried in this message are business indicators, that is, no intent expression needs to be constructed here.
  • the intent translation FB sends an intent knowledge acquisition request to the knowledgemanagement FB, where the intent knowledge request carries an intent keyword.
  • the knowledgemanagement FB sends the intent knowledge to the intent translation FB, where the intent knowledge carries a second-stage identifier, and the second-phase identifier is used to identify the intent information for use in the intent maintenance phase.
  • the second stage identification information is optional.
  • the intent translation FB sends a policy completion message to the context awareness FB.
  • the strategy completion message carries the intent translation result and the second stage identifier.
  • the second stage flag is used to indicate this intent translation result for intent maintenance use.
  • the context awareness FB judges the network state, and updates the network state as the intention context information in the knowledgemanagement FB (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the situation awareness FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the situation awareness FB judges whether the intention target is achieved, and updates the achievement status of the intention target into the knowledgemanagement FB as the intention context information (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the model-driven engineering FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the model-driven engineering FB converts the translation result into a form that can be understood by the intent-acting entity. And update the updated information into the knowledge management FB (refer to the corresponding description in the embodiment shown in FIG. 6 ). And send the updated intent translation result to the policy management FB, carrying the second stage identifier.
  • the second stage flag is used to indicate that this intent translation result is used in the intent maintenance phase.
  • the policy management FB converts and decides the intent translation result, and sends the executable command or rule obtained after the decision to the knowledge management FB for storage, and sends the executable command or rule obtained after the decision to denormalisation&output generation fb.
  • denormalisation & output generation FB sends execution commands or rules to entities intended to affect.
  • an intent translation request between the intent execution module and the intent translation module in the intent maintenance phase is added, so that the intent system can dynamically adjust the execution strategy corresponding to the intent according to the achievement of the intent goal during the intent maintenance phase.
  • the translation of the existing intent occurs only once before the intent execution phase.
  • intent translation is added in the intent maintenance phase, and multiple intent translations will occur throughout the life cycle of the intent. It enables the intent system to use more accurate translation results to adjust the commands, rules or sub-intents that the intent can execute during the maintenance phase.
  • FIG. 9 it is a schematic flowchart of another communication method provided by an embodiment of the present application, and the method is applied to the ONAP architecture shown in FIG. 4 .
  • the intent translation is entered, and the intent executable command, rule or sub-intent is adjusted according to the intent translation result.
  • the message sent by the intentdecision FB to the intent translation FB follows the message between the intent management FB and the intent translation, and the carried parameter is the intent expression.
  • the method may include the following steps:
  • the ONAP UUI sends a create intent/activate intent (create intent/activate intent) request to the intent management FB.
  • the request carries an intent expression.
  • the intent expression can be a natural language expression or a DSL expression.
  • the intent management FB sends an intent translation request to the intent translation FB.
  • the intent translation request carries an intent expression, which is a DSL expression.
  • the intent translation FB sends an intent knowledge query request to the intent knowledge repository, and the intent knowledge repository returns the intent knowledge to the intent translation FB.
  • the intent translation FB arranges the intent knowledge, and sends an intent decision request to the intent decision FB.
  • the intent decision request carries multiple sets of executable commands, rule sets or sub-intents, and requests it to make a decision on the intent translation result.
  • the intent decision request also carries a first stage identifier, an intent identifier, and an intent translation result, and the first phase identifier is also used to indicate that the translation result is used for intent execution.
  • the intent decision FB sends a query intent decision rule request to the ONAP policy FB, and the ONAP policy FB sends the decision rule to the intent decision FB.
  • the intent decision FB makes a decision on the intent translation result, and sends the decision result to other components in ONAP or other intent-acting entities, such as ONAP SO or ONAP controllers.
  • the intent decision FB sends a request for creating a network slice to ONAP SO, and the request for creating a network slice includes the CS profile.
  • Network slice instances are created interactively between ONAP SO and ONAP DCAE.
  • the ONAP SO sends a create network slice response to the intent decision FB, where the create network slice response includes a network slice identity (NSI).
  • NSI network slice identity
  • the intent decision FB sends a request for modifying the network slice to the ONAP SO, and the request for modifying the network slice includes the CS profile and the NS.
  • the network slice instance is modified interactively between ONAP SO and ONAP DCAE.
  • the ONAP SO sends a modified network slice response to the intent decision FB, where the modified network slice response includes a network slice identity (NSI).
  • NSI network slice identity
  • the intent decision FB sends an intent performance data acquisition message to the intent execution function module (intent handler FB), where the message carries a performance data indication indicating whether the schematic target is completed and the network state.
  • intent handler FB can be deployed separately or as part of ONAPDCAE.
  • the intent handler FB judges the intention achievement status and the network status according to the performance data indication received in step S506, and sends the intent achievement status and the network status to the intent decision FB.
  • the intent decision FB sends an intent translation request (Call intent translation) to the intent translation FB, and the request carries an intent expression, which may be the same as the expression in step S501, or may be the translation generated according to step S503 The resulting new intent expression.
  • the intent translation FB sends an intent knowledge query request to the intent knowledge repository, and the intent knowledge repository returns the intent knowledge to the intent translation FB.
  • the intent translation FB arranges the intent knowledge, and sends an intent decision request to the intent decision FB, where the intent decision request carries multiple sets of executable commands, rule groups or sub-intents, requesting it to make a decision on the intent translation result.
  • the intent decision request carries a second stage identifier, an intent identifier and an intent translation result, where the second phase identifier is used to indicate that the translation result is used in the intent maintenance phase.
  • the intent decision FB sends the translation result to other components in ONAP or other intent-acting entities, such as ONAP SO or ONAP Controller. For details, refer to step S505.
  • the intent decision FB feeds back the intent achievement status to the intent creator (ONAP UUI).
  • an intent translation request between the intent execution module and the intent translation module in the intent maintenance phase is added, so that the intent system can dynamically adjust the execution strategy corresponding to the intent according to the achievement of the intent goal during the intent maintenance phase.
  • the translation of the existing intent occurs only once before the intent execution phase.
  • intent translation is added in the intent maintenance phase, and multiple intent translations will occur throughout the life cycle of the intent. It enables the intent system to use more accurate translation results to adjust the commands, rules or sub-intents executable by the intent during the maintenance phase.
  • FIG. 10 it is a schematic flowchart of another communication method provided by an embodiment of the present application, and the method is applied to the ONAP architecture shown in FIG. 4 .
  • the difference between this communication method and the communication method shown in FIG. 9 is that the message between the intention execution and intention translation modules in this communication method adopts a new message, and the message carries the parameters related to the intention, that is, the message S608 in FIG. 10 is the same as that shown in FIG.
  • the message S508 in the embodiment shown in 9 is different.
  • the method may include the following steps:
  • the ONAP UUI sends a create intent/activate intent (create intent/activate intent) request to the intent management FB.
  • the request carries an intent expression.
  • the intent expression can be a natural language expression or a DSL expression.
  • the intent management FB sends an intent translation request to the intent translation FB.
  • the intent translation request carries an intent expression, which is a DSL expression.
  • the intent translation FB sends an intent knowledge query request to the intent knowledge repository, and the intent knowledge repository returns the intent knowledge to the intent translation FB.
  • the intent translation FB arranges the intent knowledge, and sends an intent decision request to the intent decision FB.
  • the intent decision request carries multiple sets of executable commands, rule sets or sub-intents, and requests it to make a decision on the intent translation result.
  • the intent decision request also carries a first stage identifier, an intent identifier, and an intent translation result, and the first phase identifier is also used to indicate that the translation result is used for intent execution.
  • the intent decision FB sends a query intent decision rule request to the ONAP policy FB, and the ONAP policy FB sends the decision rule to the intent decision FB.
  • the intent decision FB makes a decision on the intent translation result, and sends the decision result to other components in ONAP or other intent-acting entities, such as ONAP SO or ONAP controllers.
  • the intent decision FB sends a request for creating a network slice to ONAP SO, and the request for creating a network slice includes the CS profile.
  • Network slice instances are created interactively between ONAP SO and ONAP DCAE.
  • the ONAP SO sends a create network slice response to the intent decision FB, where the create network slice response includes a network slice identity (NSI).
  • NSI network slice identity
  • the intent decision FB sends a request for modifying the network slice to the ONAP SO, and the request for modifying the network slice includes the CS profile and the NS.
  • the network slice instance is modified interactively between ONAP SO and ONAP DCAE.
  • the ONAP SO sends a modified network slice response to the intent decision FB, where the modified network slice response includes a network slice identity (NSI).
  • NSI network slice identity
  • the intent decision FB sends an intent performance data acquisition message to the intent execution function module (intent handler FB), where the message carries a performance data indication indicating whether the schematic target is completed and the network state.
  • intent handler FB can be deployed separately or as part of ONAPDCAE.
  • the intent handler FB judges the intention achievement status and the network status according to the performance data indication received in step S606, and sends the intent achievement status and network status to the intent decision FB.
  • the intent decision FB sends an intent translation request (Call intent translation for assurance) to the intent translation FB.
  • the request carries a parameter that is a business indicator, that is, an intent expression does not need to be constructed here.
  • the intent translation FB sends an intent knowledge query request to the intent knowledge repository, and the intent knowledge repository returns the intent knowledge to the intent translation FB.
  • the intent translation FB arranges the intent knowledge, and sends an intent decision request to the intent decision FB, where the intent decision request carries multiple sets of executable commands, rule groups or sub-intents, and requests it to make a decision on the intent translation result.
  • the intent decision request carries a second stage identifier, an intent identifier and an intent translation result, where the second phase identifier is used to indicate that the translation result is used in the intent maintenance phase.
  • the intent decision FB sends the translation result to other components in ONAP or other intent-acting entities, such as ONAP SO or ONAP Controller. For details, refer to step S605.
  • the intent decision FB feeds back the intent achievement status to the intent creator (ONAP UUI).
  • an intent translation request between the intent execution module and the intent translation module in the intent maintenance phase is added, so that the intent system can dynamically adjust the execution strategy corresponding to the intent according to the achievement of the intent goal during the intent maintenance phase.
  • the translation of the existing intent occurs only once before the intent execution phase.
  • intent translation is added in the intent maintenance phase, and multiple intent translations will occur throughout the life cycle of the intent. It enables the intent system to use more accurate translation results to adjust the commands, rules or sub-intents executable by the intent during the maintenance phase.
  • an embodiment of the present application further provides a communication apparatus, where the communication apparatus 400 is the first network element in the above embodiment.
  • the communication device 400 includes: a processing unit 41 and a transceiver unit 42 . in:
  • a processing unit 41 configured to acquire performance data during the execution of an intent, where the intent includes a first intent target and a second intent target;
  • the processing unit 41 is further configured to determine, according to the performance data during the execution of the intention, that the second intention goal has not been achieved;
  • the processing unit 41 is further configured to translate the intent according to the second intent target to obtain a first translation result
  • the transceiver unit 42 is configured to send the first execution command corresponding to the first translation result to the second network element.
  • the processing unit 41 is further configured to translate the intent to obtain a second translation result
  • the processing unit 41 is further configured to perform network status judgment and judgment on whether the first intention target is achieved, and update the second translation result according to the network status judgment and the judgment result of whether the first intention target is achieved ;
  • the processing unit 41 is further configured to mark the second translation result and the updated second translation result with a first stage identifier, and the first phase identifier is used to mark the second translation result and the updated second translation result.
  • the second translation result of is used in the intent execution process.
  • processing unit 41 is further configured to translate the intent again according to the first stage identifier when it is determined that the second intent target has not been achieved, to obtain the first translation result;
  • the processing unit 41 is further configured to mark the first translation result with a second-stage identifier, where the second-phase identifier is used to mark the first translation result for an intent maintenance process.
  • processing unit 41 is further configured to obtain an intent expression corresponding to the second intent target
  • the processing unit 41 is further configured to acquire intent knowledge according to the intent expression corresponding to the second intent target;
  • the processing unit 41 is further configured to arrange the intent knowledge to obtain a first translation result.
  • the first intent is network configuration
  • the second intent is adjustment of network performance
  • the intent can be translated again, and the execution command can be adjusted according to the intent translation result, thereby improving the probability of achieving the intent target.
  • FIG. 12 a schematic diagram of the hardware structure of a communication device is also provided, and the communication device is used for executing the above communication method. Part or all of the above methods may be implemented by hardware, and may also be implemented by software or firmware.
  • the communication device may be a chip or an integrated circuit during specific implementation.
  • the communication device 500 may include:
  • the memory 53 and the processor 54 may be one or more, and one processor is taken as an example in FIG. 12 ), and may also include an input device 51 and an output device 52 .
  • the input device 51 , the output device 52 , the memory 53 and the processor 54 may be connected through a bus or other means, wherein the connection through a bus is taken as an example in FIG. 12 .
  • the processor 54 is configured to perform the method steps performed by the first network element in FIG. 5 to FIG. 10 .
  • the program of the above communication method may be stored in the memory 53 .
  • the memory 53 may be a physically independent unit, or may be integrated with the processor 54 .
  • the memory 53 can also be used to store data.
  • the communication apparatus may also only include a processor.
  • the memory for storing the program is located outside the communication device, and the processor is connected to the memory through a circuit or wire for reading and executing the program stored in the memory.
  • the processor may be a central processing unit (CPU), a network processor (NP), or a WLAN device.
  • CPU central processing unit
  • NP network processor
  • WLAN device a WLAN device
  • the processor may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL general array logic
  • the memory may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include non-volatile memory (non-volatile memory), such as flash memory (flash memory) , a hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above-mentioned types of memory.
  • volatile memory such as random-access memory (RAM)
  • non-volatile memory such as flash memory (flash memory) , a hard disk drive (HDD) or a solid-state drive (SSD)
  • flash memory flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory may also include a combination of the above-mentioned types of memory.
  • one or more embodiments of the present disclosure may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present disclosure may employ a computer program implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein form of the product.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • An embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to a memory through the interface, and when the at least one processor executes a computer program or instruction in the memory, the above-mentioned The method of any method embodiment is performed.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program may be stored thereon, and when the program is executed by a processor, the steps of the communication method described in any embodiment of the present disclosure are implemented.
  • the embodiments of the present application also provide a computer program product containing instructions, which, when run on a computer, cause the computer to execute the steps of the communication method described in any of the embodiments of the present disclosure.
  • An embodiment of the present application further provides a communication system, where the communication system includes the above-mentioned communication device.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one item (a) of a, b, or c may represent: a, b, c, ab, ac, bc, or abc, where a, b, and c may be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the division of the unit is only for one logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored, or not implement.
  • the shown or discussed mutual coupling, or direct coupling, or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted over a computer-readable storage medium.
  • the computer instructions can be sent from one website site, computer, server, or data center to another by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.)
  • wire e.g. coaxial cable, fiber optic, digital subscriber line (DSL)
  • wireless e.g., infrared, wireless, microwave, etc.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
  • the available media may be read-only memory (ROM), or random access memory (RAM), or magnetic media, such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as , digital versatile disc (digital versatile disc, DVD), or semiconductor media, for example, solid state disk (solid state disk, SSD) and the like.
  • ROM read-only memory
  • RAM random access memory
  • magnetic media such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as , digital versatile disc (digital versatile disc, DVD), or semiconductor media, for example, solid state disk (solid state disk, SSD) and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)
  • Machine Translation (AREA)

Abstract

本申请公开了一种通信方法及装置、系统。该方法包括：第一网元获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；所述第一网元根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；所述第一网元根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；以及所述第一网元向第二网元发送所述第一转译结果对应的第一执行命令。还公开了相应的装置和系统。采用本申请的方案，针对包括两种以上意图目标的意图，在意图维持阶段，可以再次对意图进行转译，根据意图转译结果调整执行命令，从而提高了意图目标达成的概率。

Description

通信方法及装置、系统
本申请要求于2020年09月19日提交中国国家知识产权局、申请号为202010990421.9、发明名称为“通信方法及装置、系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络智能管理技术领域，尤其涉及一种通信方法及装置、系统。
背景技术
基于意图的体验式网络智能(experiential networked intelligence，ENI)融合架构中，如图1所示的已有的意图实施流程示意图，意图实施过程包括意图转译、执行以及维持。意图实施过程中，由意图转译功能模块(intent translation functional block)负责意图转译，并且将转译的结果发送给策略管理功能模块(policy management functional block)，由策略管理功能模块进行意图执行以及维持。
如图1所示，意图转译仅仅在执行前发生一次，转译结果供意图执行以及维持(若需要)使用。意图在维持过程中，不需要意图转译功能模块的参与，策略管理等功能模块根据意图转译功能模块的转译结果调整意图执行命令，并将执行命令发送给辅助系统(assisted system)执行。
然而，意图包括以下几种类型：配置类意图、优化类意图、网络维护类意图和业务保障类意图。对于针对于前三种意图，意图的转译仅执行一次，转译结果可以满足执行以及维持的需求。而针对第四种意图，即业务保障类意图，单次的转译结果不足以供意图执行及维持阶段使用。因为对于第四类意图，意图执行阶段的意图执行命令是对于一个网络的配置，而意图维持阶段的意图执行命令是对于网络性能的调节，即是配置加优化类意图。
针对配置加优化类意图，意图执行以及维持阶段需要的意图命令不同(意图执行命令为意图转译结果的一部分)，且意图维持阶段需要的命令组受到意图执行阶段执行命令的影响，采用相同的命令组在意图维持阶段难以达成意图目标。
因此，需要解决目前意图单次转译结果无法同时满足意图执行以及维持的问题。
发明内容
本申请提供一种通信方法及装置、系统，以解决目前意图单次转译结果无法同时满足意图执行以及维持的问题。
第一方面，提供了一种通信方法，所述方法包括：第一网元获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；所述第一网元根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；所述第一网元根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；以及所述第一网元向第二网元发送所述第一转译结果对应的第一执行命令。
在一种可能的实现中，所述第一网元获取意图执行过程中的性能数据之前，所述方法还包括：所述第一网元对所述意图进行转译，得到第二转译结果；所述第一网元进行网络状态判断、所述第一意图目标是否达成的判断，并根据网络状态判断和所述第一意图目标是否达成的判断结果，更新所述第二转译结果；以及所述第一网元采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果 和更新的所述第二转译结果用于所述意图执行过程。
在又一种可能的实现中，所述第一网元确定所述第二意图目标未达成时，所述方法还包括：所述第一网元根据所述第一阶段标识确定对所述意图再次进行转译，得到所述第一转译结果；以及所述第一网元采用第二阶段标识对所述第一转译结果进行标记，所述第二阶段标识用于标记所述第一转译结果用于意图维持过程。
在又一种可能的实现中，所述第一网元根据所述第二意图目标，对所述意图进行转译，得到第一转译结果，包括：所述第一网元获取所述第二意图目标对应的意图表达式；所述第一网元根据所述第二意图目标对应的意图表达式，获取意图知识；以及所述第一网元对所述意图知识进行编排，得到第一转译结果。
在又一种可能的实现中，所述第一意图目标为网络配置，所述第二意图目标为网络性能的调节。
第二方面，提供了一种通信装置，所述装置包括：处理单元，用于获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；所述处理单元，还用于根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；所述处理单元，还用于根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；以及收发单元，用于向第二网元发送所述第一转译结果对应的第一执行命令。
在一种可能的实现中，所述处理单元，还用于对所述意图进行转译，得到第二转译结果；所述处理单元，还用于进行网络状态判断、所述第一意图目标是否达成的判断，并根据网络状态判断和所述第一意图目标是否达成的判断结果，更新所述第二转译结果；以及所述处理单元，还用于采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果和更新的所述第二转译结果用于所述意图执行过程。
在又一种可能的实现中，所述处理单元，还用于确定所述第二意图目标未达成时，根据所述第一阶段标识确定对所述意图再次进行转译，得到所述第一转译结果；以及所述处理单元，还用于采用第二阶段标识对所述第一转译结果进行标记，所述第二阶段标识用于标记所述第一转译结果用于意图维持过程。
在又一种可能的实现中，所述处理单元，还用于获取所述第二意图目标对应的意图表达式；所述处理单元，还用于根据所述第二意图目标对应的意图表达式，获取意图知识；以及所述处理单元，还用于对所述意图知识进行编排，得到第一转译结果。
在又一种可能的实现中，所述第一意图目标为网络配置，所述第二意图目标为网络性能的调节。
第三方面，提供了一种通信装置，该通信装置可以为上述第一方面或第一方面的任一可能的实现中的第一网元，或者应用于第一网元中的模块，例如芯片或芯片系统。其中，该通信装置包括至少一个处理器，用于执行上述第一方面或第一方面的任一可能的实现中的方法。
示例性地，该通信装置还包括存储器，该存储器与该至少一个处理器耦合，该至少一个处理器用于执行上述第一方面或第一方面的任一可能的实现中的方法。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该至少一个处理器耦合，该至少一个处理器可以调用并执行该存储器中存储的程序指令，用于执行上述第一方面或第一方面的任一可能的实现中的方法。
示例性地，该通信装置还包括通信接口，该通信接口用于该通信装置与其它设备进行通信。当该通信装置为第一网元时，该通信接口为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该通信装置包括：至少一个处理器和通信接口，用于执行上述第一方面或第一方面的任一可能的实现中的方法，具体地包括：该至少一个处理器利用该通信接口与外部通信；该至少一个处理器用于运行计算机程序，使得该通信装置执行上述第一方面或第一方面的任一可能的实现中的方法。可以理解，该外部可以是处理器以外的对象，或者是该通信装置以外的对象。
在另一种可能的设计中，该通信装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第四方面，提供了一种通信系统，包括如第二方面或第二方面的任一个实现所述的通信装置，以及第二网元。
第五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任一个实现所述的方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任一个实现所述的方法。
第七方面，提供了一种芯片，所述芯片与存储器耦合，执行本申请实施例第一方面或第一方面中任一实现所述的通信方法。
需要说明的是，本申请实施例中“耦合”是指两个部件彼此直接或间接地结合。
附图说明
图1为已有的意图实施流程示意图；
图2为基于意图的体验式网络智能(experiential networked intelligence，ENI)架构示意图；
图3为本申请适用的一种通信系统的架构示意图；
图4为示例的开放式网络自动化平台(open network automation platform，ONAP)的架构示意图；
图5为本申请实施例提供的一种通信方法的流程示意图；
图6为本申请实施例提供的另一种通信方法中意图转译及执行的流程示意图；
图7为图6所示的通信方法中一种意图维持的流程示意图；
图8为图6所示的通信方法中又一种意图维持的流程示意图；
图9为本申请实施例提供的又一种通信方法的流程示意图；
图10为本申请实施例提供的又一种通信方法的流程示意图；
图11为本申请实施例提供的一种通信装置的模块结构示意图；
图12为本申请实施例提供的一种通信装置的硬件结构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
ENI定义了一个基于观察方向决定行为控制模型的认知网络管理体系架构。它使用人工智能(artificial intelligence，AI)技术和情境感知策略，根据用户需求、环境条件和业务目标的变化调整提供的服务。该系统是经验性的，因为它从操作者的指令中学习相关知识，以改进其在将来采取的行动。这能够帮助运营商自动化其网络配置和监控过程，从而减少运营支出并改善其网络的使用和维护。
为了屏蔽设备厂商实现上的差异化，启动了意图驱动管理(intent driven management， IDM)。网络管理系统(network management system，NMS)中只保留意图(intent)模型，向网元管理系统(element management system，EMS)传递意图表达式。该意图表达式只描述做什么(what)，不涉及怎么(how)做，只需具备无线领域基本的概念知识即可完成意图设计，从而降低了运维门槛。
因此，定义了基于意图的ENI架构，如图2所示，其能够同时支持两种类型的策略(policy)。该ENI系统共包含11个功能模块(functional block，FB)，并可分为输入功能模块、输出功能模块、分析功能模块以及决策功能模块四大类。模块分类以及各类模块的功能如下所述：
输入功能模块：其包括数据获取(data ingestion)功能模块和标准化(normalization)功能模块。该输入功能模块负责接收外部系统的数据以及对数据进行归一化等操作。
输出功能模块：其包括输出产生(output generation)功能模块和反规范化(denormalisation)功能模块。该输出功能模块负责将系统内部命令转化为外部系统能够处理的格式并发送给外部系统。
分析功能模块：其包括知识管理(knowledge management)功能模块，上下文感知(context awareness)功能模块和认知管理(cognition management)功能模块。该分析功能模块负责对现有的网络上下文进行感知分析并且预测未来的网络状态。
决策功能模块：其包括策略管理(policy management)功能模块，状态感知(situational awareness)功能模块和模型驱动工程(model-driven engineering)功能模块。该决策功能模块在对网络状态感知的基础上，根据策略目标生成新的策略并对策略进行编排，并将操作命令发送给输出模块。
ENI进一步定义了与意图转译、意图执行和维持相关的功能模块。具体地，该ENI融合架构在知识管理功能模块中加入了意图知识库(intent knowledge repository)，在策略管理功能模块中加入了意图策略执行(intent policy fulfillment)子功能模块，以及还引入了一个独立的意图转译(intent translation)功能模块。
其中，意图转译功能模块，用于将收到的意图策略进行意图转译。
意图知识库，用于存放专家经验以及网元的信息，可以作为一个独立的功能模块，也可以放在ENI现有架构中的知识管理功能模块中。
意图策略执行功能模块，用于实现意图执行及维持功能，负责对意图策略进行编排并持续满足外部系统的意图需求。
意图实施过程包括意图转译、执行以及维持。意图实施过程中，由意图转译功能模块负责意图转译，并且将转译的结果发送给策略管理功能模块，由策略管理功能模块进行意图执行以及维持。意图执行及维持过程中，策略管理功能模块根据意图的达成情况调整意图可执行命令。
此外，为了更好地实现意图的调用，还定义了意图的表达方式，意图模型的形式化表达如下：
<intentExpression>:＝<IntentDrivenAction><IntentDrivenObject>
<IntentDrivenAction>:＝<IntentDrivenActionName><IntentDrivenActionProperties>
<IntentDrivenObject>:＝<IntentDrivenObjectName><IntentDrivenObjectProperties>
由如上表达式可以看出，一条完整的意图策略由两部分组成：IntentDrivenAction以及IntentDrivenObject，分别代表意图策略的执行动作以及目标。
意图包括以下几种类型：配置类意图、优化类意图、网络维护类意图和业务保障类意图。如下表1所示：
表1
Figure PCTCN2021113637-appb-000001
对于针对于前三种意图，意图的转译仅执行一次，转译结果可以满足执行以及维持的需求。而针对第四种意图，即业务保障类意图，单次的转译结果不足以供意图执行及维持阶段使用。因为对于第四类意图，意图执行阶段的意图执行命令是对于一个网络的配置，而意图维持阶段的意图执行命令是对于网络性能的调节，即是配置加优化类意图。
针对配置加优化类意图，意图执行以及维持阶段需要的意图命令不同(意图执行命令为意图转译结果的一部分)，且意图维持阶段需要的命令组受到意图执行阶段执行命令的影响，采用相同的命令组在意图维持阶段难以达成意图目标。
本申请提供一种通信方案，针对包括两种以上意图目标的意图，在意图维持阶段，可以再次对意图进行转译，根据意图转译结果调整执行命令，从而提高了意图目标达成的概率。
如图3所示，为本申请适用的一种通信系统的架构示意图，该通信系统100包括第一网元200和第二网元300。其中，第一网元200可以是ENI系统或者ONAP系统，其中包括多个功能模块(functional block，FB)。第二网元300可以是辅助系统(assisted system)。第一网元200接收意图创建者，如用户(user)/应用(application，APP)/运营支撑系统等功能实体(operation support systems-like，OSS-like)/业务支撑系统等功能实体(business support systems-like，BSS-like)等请求创建的意图，对意图进行转译，得到意图执行命令，发送给第二网元300执行。
示例性地，该通信系统可以是如图2所示的基于意图的ENI架构，还可以是如图4所示ONAP。ONAP支持意图，其包括：
ONAP UUI，用于发送意图创建指令及接收意图执行结果等，相当于ENI系统的意图创建者，如user/APP/OSS-like/BSS-like等。
用于意图执行(intent assurance)的意图框架(intent framework)，其包括若干个意图执行过程中的功能模块。具体地，包括：
意图管理功能模块(intent management FB)、意图转译功能模块、意图决定功能模块(intent decision FB)和意图验证功能模块(intent verification FB)。其中，intent decision FB相当于ENI系统中的intent processing FB。
激活的和可用的库(active&available inventory，A&AI)，其作用是维护资源(resource)和服务(service)的实时关系。其中，资源是指如中央处理单元(central processing unit，CPU)，存储，网络连接，虚拟化网络功能(virtualization network function，VNF)之类的构成服务的元素，而服务是由多个资源组合起来的。可以将A&AI看成一个动态的资源管理库。其包括意图知识库。其中，意图转译功能模块可以根据意图关键词从A&AI中获取意图知识。
ONAP数据收集分析和事件(data collection analytics and events，DCAE)：纵向分为两个部分，DCAE平台(platform)和DCAE分析应用(analytic applications)。DCAE platform主要完成数据采集，这些结构化或者非结构化的数据可以持久化存到其所称的数据湖(data lake)，同时DCAE platform还提供一系列数据的分析框架。DCAE analytic applications则是基于DCAE platform的数据分析框架和采集数据开发的分析应用。同时DCAE还提供闭环反馈能力，当分析应用得出结果后，可以调用相关action触发ONAP服务编制(serviceorchestration，SO)和ONAP控制器(controllers)对现网的网络服务进行调整。
ONAP控制器：是ONAP中网络控制的核心，它可以通过网络适配器(network adapters)与各类虚拟环境中本地的控制器或者网络组件交互。
ONAP SO：组件通过自动顺序执行按需创建、修改或移除网络、应用或基础架构业务和资源所需的活动、任务、规则和策略，从而执行指定的流程。SO在一个非常高的层次上进行编排，并提供基础设施、网络和应用的端到端视图。
ONAP策略(policy)：策略是实现闭环自动化的一个关键环节，负责策略规则集的维护、分发和处理。策略为创建和管理易于更新的条件规则提供了一个集中的环境。
管理网络(managed network)。
下面结合图1至图10，对本申请提供的通信方法进行详细描述：
如图5所示，为本申请实施例提供的一种通信方法的流程示意图，该方法可以包括以下步骤：
S101、第一网元获取意图执行过程中的性能数据。
本实施例中，该意图包括第一意图目标和第二意图目标。其中，第一意图目标为网络配置，第二意图目标为网络性能的调节。例如，该意图可以是上述业务保障类意图，其中，该意图的第一意图目标是配置，该意图的第二意图目标是性能优化。该第一意图目标可以是意图执行过程中的意图目标，该第二意图目标可以是意图维持过程中的意图目标。
第一网元获取意图执行过程中的性能数据之前，还包括如下步骤A1～A3：
A1、第一网元对所述意图进行转译，得到第二转译结果。
A2、第一网元进行网络状态判断、第一意图目标是否达成的判断，并根据网络状态判断和第一意图目标是否达成的判断结果，更新第二转译结果。
A3、第一网元采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果和更新的所述第二转译结果用于所述意图执行过程。
具体地，第一网元接收意图创建者发送的意图创建请求，该意图创建请求包括意图表达式。该意图表达式包括意图策略的执行动作以及目标。第一网元对该意图策略进行转译，得到第二转译结果，该第二转译结果用在意图执行阶段。可选地，第一网元可以采用第一阶段标识对第二转译结果进行标记，该第一阶段标识用于标记该第二转译结果用于意图执行过程。
并且在意图执行过程中，第一网元进行网络状态判断、第一意图目标是否达成的判断，并根据网络状态判断和第一意图目标是否达成的判断结果，更新第二转译结果。可选地，第一网元可以采用第一阶段标识对更新的第二转译结果进行标记，该第一阶段标识用于标记该更新的第二转译结果用于意图执行过程。
第一网元对意图转译结果进行转换以及决策，得到决策后的可执行命令或者规则，最后，将执行命令或者规则发送给第二网元(即意图影响的实体或者称意图作用实体)执行。
然后，第一网元获取意图执行过程中的性能数据。具体地，第一网元从第二网元获取该 实体在执行意图过程中的性能数据。该性能数据包括网络状态等。
S102、第一网元根据意图执行过程中的性能数据，确定第二意图目标未达成。
由于意图执行阶段，主要是执行针对第一意图目标的转译结果对应的执行命令，执行过程中也是判断网络状态是否能满足第一意图目标的执行，因此，第一网元可以在获取到意图执行过程中的性能数据后，根据性能数据判断第二意图目标是否达成。
S103、第一网元根据第二意图目标，对意图进行转译，得到第一转译结果。
若确定第二意图目标未达成，则第一网元可以根据第二意图目标，对意图再次进行转译，得到第一转译结果。
具体地，步骤S103包括：第一网元获取第二意图目标对应的意图表达式；
第一网元根据第二意图目标对应的意图表达式，获取意图知识；
第一网元对意图知识进行编排，得到第一转译结果。
具体实现过程中，第一网元获取第二意图目标对应的意图表达式，该意图表达式可以与转译阶段从意图创建者得到的意图表达式相同，也可以是根据意图创建者发送的意图表达式转变得到的。可替换地，第一网元也可以获取第二意图目标对应的业务指标，而不构造意图表达式。第一网元根据第二意图目标对应的意图表达式，从意图知识库获取意图知识。第一网元在获得该意图知识后，再次对根据第二意图目标对应的意图表达式获得的意图知识进行编排，得到第一转译结果。
进一步地，第一网元根据第一阶段标识确定对意图再次进行转译，得到第一转译结果之后，第一网元采用第二阶段标识对第一转译结果进行标记，该第二阶段标识用于标记第一转译结果用于意图维持过程。
S104、第一网元向第二网元发送第一转译结果对应的第一执行命令。相应地，第二网元接收该第一执行命令并执行。
第一网元根据再次转译获得的第一转译结果，将第一转译结果转化为可以被意图作用实体理解的形式，即得到第一执行命令，向第二网元发送该第一执行命令。第二网元接收该第一执行命令并执行。
在该实施例中增加在意图维持阶段的意图转译请求，使得意图系统在意图维持阶段能够根据意图目标的达成情况动态调整意图对应的执行策略。
已有的意图的转译只在意图执行阶段之前发生一次，本实施例中，在意图的维持阶段加入了意图转译，在整个意图的生命周期中会发生多次意图转译。使得意图系统在维持阶段能够运用更精确的转译结果调整意图可执行的命令、规则或者子意图。
根据本申请实施例提供的一种通信方法，针对包括两种以上意图目标的意图，在意图维持阶段，可以再次对意图进行转译，根据意图转译结果调整执行命令，从而提高了意图目标达成的概率。
还提供了另一种通信方法，该方法可应用于图2所示的ENI架构。该方法包括两部分：一部分是意图转译及执行流程，另一部分是意图维持流程。其中，意图维持流程主要是用来保证意图目标尽量能够达成。如图6所示，为本申请实施例提供的另一种通信方法中意图转译及执行的流程示意图，且意图执行模块以及意图转译模块之间的消息沿用已有的意图转译消息。该方法可包括以下步骤：
S201、用户(user)/应用(application，APP)/运营支撑系统等功能实体(operation support systems-like，OSS-like)/业务支撑系统等功能实体(business support systems-like，BSS-like)向data ingestion&normalization FB发送“新策略(new policy)”消息，该新策略消息用于指 示创建新意图策略(intent policy)，该策略为一种意图策略。该消息中包含policyRefPoint、policyContent和policyMetadata。其中，policyRefPoint参数指示意图策略的创造者，policyContent指示意图表达式，policyMetadata指示意图策略相关信息，比如意图的有效期等。
S202a～202b、data Ingestion&normalization FB对收到的意图策略以及相关数据进行归一化，并且将归一化后的数据发送给knowledge management FB。
S203、knowledge management FB根据收到的归一化后的数据更新本地数据库。
S204、knowledge management FB向intenttranslation FB发送转译请求。该转译请求携带policyContent和policyMetadata等信息。
S205a、intenttranslation FB给该意图策略分配意图标识。
S205b、intent translation FB向knowledge management FB发送标识更新请求，该标识更新请求用于请求更新knowledge management FB中的意图标识。该标识更新请求包括上述意图标识。
S206a～S206b、intenttranslation FB通过denormalisation&output generation FB向user/app/OSS-like/BSS-like发送响应消息，该响应消息用于告知意图已经开始被处理。
S207a、intenttranslation FB进行意图语法词法检查。
如果语法词法检查有误，执行S207b1～S207b2：
S207b1～S207b2、意图语法词法检查有误，通过denormalisation&output generation FB向意图创建者(例如，user/app/OSS-like/BSS-like)发送错误反馈信息。
S207b3、intent translation FB向knowledge management FB反馈意图错误信息。
如果词法语法检查无误，执行S207c-S207d：
S207c、intenttranslation FB提取意图关键词。
S207d、intenttranslation FB向knowledge management FB发送意图关键词更新消息。该意图关键词更新消息用于请求更新knowledge management FB中的意图关键词。该意图关键词更新消息包括上述意图关键词。
S208a、intenttranslation FB向knowledgemanagement FB发送意图知识获取请求。该意图知识获取请求包括上述意图关键词。
S208b、knowledgemanagement FB向intent translation FB发送意图知识。该意图知识中包括意图操作指令{<运行条件，执行命令>}(intentInstruction{<executionCondition,Instruction>})，意图作用设备的标识(entityId)，执行目标(fulfillmentCriterion)。其中intentInstruction表示执行条件及对应的执行命令对的集合，entityId指示意图作用设备的标识，fulfillmentCriterion用来判断意图目标是否达成。
S208c、intent translation FB将接收到的意图知识进行编排，将entityId填充到intentInstruction中的执行命令中。比如Instruction为MOD CELLULSCHALGO.UlEnhencedVoipSchSw:LocalCellId＝％obj；UlVoipSchOptSwitch＝ON，其中entityId取值为001，将entityId填入％obj，编排后的结果为MOD CELLULSCHALGO.UlEnhencedVoipSchSw:LocalCellId＝001；UlVoipSchOptSwitch＝ON。
S208d、intent translation FB向knowledgemanagement FB发送意图知识更新请求，将编排完的意图策略、规则或者自意图更新至意图上下文中。
S209、intent translation FB向context awareness FB发送策略完成消息。该策略完成消息携带意图转译结果，以及第一阶段标识(flag)。其中，第一阶段标识用于指示此意图转译结果用在意图执行阶段。
S210a～S210c、context awareness FB对网络状态进行判断，并且将网络状态作为意图上下文信息更新到knowledgemanagement FB中。并且context awareness FB将更新后的意图转译结果发送给situation awareness FB，携带第一阶段标识，该第一阶段标识用于指示此意图转译结果用在意图执行阶段。
S211a～S211c、situation awareness FB对意图目标是否达成进行判断，并且将意图目标的达成情况作为意图上下文信息更新到knowledgemanagement FB中。且situation awareness FB将更新后的意图转译结果发送给model-driven engineering FB，携带第一阶段标识，该第一阶段标识用于指示此意图转译结果用在意图执行阶段。
S212a～S212c、model-driven engineering FB将转译结果转化为可以被意图作用实体理解的形式。并且将更新的信息更新到knowledgemanagement FB中。并且将更新后的意图转译结果发送给policy management FB，携带第一阶段标识，该第一阶段标识用于指示此意图转译结果用在意图执行阶段。
S213a～S213c、policy management FB对意图转译结果进行转换以及决策，并将决策后得到的可执行命令或者规则更新到knowledgemanagement FB中。并且将决策后得到的可执行命令或者规则发送给denormalisation&output generation FB。
S214a～S214b、denormalisation&output generation FB将执行命令或者规则进行反规范化后发送给意图影响的实体。
如图7所示，为图6所示的通信方法中一种意图维持的流程示意图，该方法可以包括以下步骤：
S301～S302、在context awareness FB收到策略完成消息后，触发context awareness FB通过denormalisation&output generation FB向assisted system发送性能数据订阅请求。该性能数据订阅请求用于请求获取assisted system的性能数据。
S303、assistedsystem向data ingestion&normalization FB上报性能数据。
S304、data ingestion&normalization FB对性能数据进行归一化处理，并将处理后的数据发送给knowledge management FB。
S305a～S305b、knowledge management FB对处理后的性能数据进行存储，并且将性能数据以及意图上下文信息送给context awareness FB。此意图上下文信息是在上述意图转译以及执行阶段生成的。
S306a～S306c、context awareness FB根据性能数据判断网络状态，将网络状态信息增加至上下文信息中，并且将意图上下文信息更新到knowledge management FB中，且将更新后的上下文信息发送给situation awareness FB。
S307a～S307c、situation awareness FB根据性能数据判断意图是否满足，并且将意图满足情况作为上下文信息更新到knowledge management FB中，且将更新后的上下文信息发送给model-drivenengineering FB。
S308a～S308c、model-driven engineering FB根据意图上下文信息调整或者生成意图策略，并且将调整或者生成的意图策略更新到knowledge management FB中，并且将更新后的意图策略以及上下文信息发送给policy management FB。
S309、policymanagement FB首先判断意图达成情况，若没达成，则再根据意图执行阶段收到的flag信息确定需要向intent translation FB发送意图转译请求(translatePolicy)。此消息携带意图表达式。该意图表达式可以与转译阶段从意图创建者得到的意图表达式相同，也可以是根据意图创建者发送的意图表达式转变得到的。
S310、intent translation FB向knowledgemanagement FB发送获取意图知识请求，该意图知识请求携带意图关键词。
S311、knowledgemanagement FB向intent translation FB发送意图知识，该意图知识中携带第二阶段标识，该第二阶段标识用于标识此意图信息供意图维持阶段使用。该第二阶段标识信息为可选。
S312、intent translation FB向context awareness FB发送策略完成消息。该策略完成消息携带意图转译结果，以及第二阶段标识。该第二阶段标识用于指示此意图转译结果供意图维持使用。
S313、context awareness FB对网络状态进行判断，并且将网络状态作为意图上下文信息更新到knowledgemanagement FB中(可参考图6所示实施例中的相应描述)。并且将更新后的意图转译结果发送给situation awareness FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S314、situation awareness FB对意图目标是否达成进行判断，并且将意图目标的达成情况作为意图上下文信息更新到knowledgemanagement FB中(可参考图6所示实施例中的相应描述)。且将更新后的意图转译结果发送给model-driven engineering FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S315、model-driven engineering FB将转译结果转化为可以被意图作用实体理解的形式。并且将更新的信息更新到knowledge management FB中(可参考图6所示实施例中的相应描述)。并且将更新后的意图转译结果发送给policy management FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S316a～S316c、policy management FB对意图转译结果进行转换以及决策，并且将决策后得到的可执行命令或者规则发送给knowledge management FB进行存储，并且将决策后得到的可执行命令或者规则发送给denormalisation&output generation FB。
S317、denormalisation&output generation FB将执行命令或者规则发送给意图影响的实体。
在该实施例中增加在意图维持阶段意图执行模块与意图转译模块之间的意图转译请求，使得意图系统在意图维持阶段能够根据意图目标的达成情况动态调整意图对应的执行策略。
已有的意图的转译只在意图执行阶段之前发生一次，本实施例中，在意图的维持阶段加入了意图转译，在整个意图的生命周期中会发生多次意图转译。使得意图系统在维持阶段能够运用更精确的转译结果调整意图可执行的命令、规则或者子意图。
如图8所示，为图6所示的通信方法中又一种意图维持的流程示意图。该方法应用于图2所示的ENI架构。该意图维持方法与图7所示的意图维持方法的区别在于，该意图维持方法中意图执行以及意图转译模块之间的消息采用新的消息，消息中携带意图相关参数，即图8中的消息S409与图7所示实施例中的消息S309不同。该方法包括以下步骤：
S401～S402、在context awareness FB收到策略完成消息后，触发context awareness FB通过denormalisation&output generation FB向assisted system发送性能数据订阅请求。该性能数据订阅请求用于请求获取assisted system的性能数据。
S403、assistedsystem向data ingestion&normalization上报性能数据。
S404、data ingestion&normalization对性能数据进行归一化处理，并将处理后的数据发送给knowledge management FB。
S405a～S405b、knowledge management FB对处理后的性能数据进行存储，并且将性能数据以及意图上下文信息送给context awareness FB，此意图上下文信息是在意图转译以及执行 阶段生成的。
S406a～S406c、context awareness FB根据性能数据判断网络状态，将网络状态信息增加至上下文信息中，并且将意图上下文信息更新到knowledge management FB中，且将更新后的上下文信息发送给situation awareness FB。
S407a～S407c、situation awareness FB根据性能数据判断意图是否满足，并且将意图满足情况作为上下文信息更新到knowledge management FB中，且将更新后的上下文信息发送给model-drivenengineering FB。
S408a～S408c、model-driven engineering FB根据意图上下文信息调整或者生成意图策略，并且将调整或者生成的意图策略更新到knowledge management FB中，并且将更新后的意图策以及上下文信息发送给policy management FB。
S409、policymanagement FB首先判断意图达成情况，若没达成，则再根据意图执行阶段收到的flag信息确定需要向intent translation FB发送意图转译请求(translatePolicyForAssurance)。此消息携带参数为业务指标，即这里不用构造意图表达式。
S410、intent translation FB向knowledgemanagement FB发送获取意图知识请求，该意图知识请求携带意图关键词。
S411、knowledgemanagement FB向intent translation FB发送意图知识，该意图知识中携带第二阶段标识，该第二阶段标识用于标识此意图信息供意图维持阶段使用。该第二阶段标识信息为可选。
S412、intent translation FB向context awareness FB发送策略完成消息。该策略完成消息携带意图转译结果，以及第二阶段标识。该第二阶段标识用于指示此意图转译结果供意图维持使用。
S413、context awareness FB对网络状态进行判断，并且将网络状态作为意图上下文信息更新到knowledgemanagement FB中(可参考图6所示实施例中的相应描述)。并且将更新后的意图转译结果发送给situation awareness FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S414、situation awareness FB对意图目标是否达成进行判断，并且将意图目标的达成情况作为意图上下文信息更新到knowledgemanagement FB中(可参考图6所示实施例中的相应描述)。且将更新后的意图转译结果发送给model-driven engineering FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S415、model-driven engineering FB将转译结果转化为可以被意图作用实体理解的形式。并且将更新的信息更新到knowledge management FB中(可参考图6所示实施例中的相应描述)。并且将更新后的意图转译结果发送给policy management FB，携带第二阶段标识。该第二阶段标识用于指示此意图转译结果用在意图维持阶段。
S416a～S416c、policy management FB对意图转译结果进行转换以及决策，并且将决策后得到的可执行命令或者规则发送给knowledge management FB进行存储，并且将决策后得到的可执行命令或者规则发送给denormalisation&output generation FB。
S417、denormalisation&output generation FB将执行命令或者规则发送给意图影响的实体。
在该实施例中增加在意图维持阶段意图执行模块与意图转译模块之间的意图转译请求，使得意图系统在意图维持阶段能够根据意图目标的达成情况动态调整意图对应的执行策略。
已有的意图的转译只在意图执行阶段之前发生一次，本实施例中，在意图的维持阶段加入了意图转译，在整个意图的生命周期中会发生多次意图转译。使得意图系统在维持阶段能 够运用更精确的转译结果调整意图可执行的命令、规则或者子意图。
如图9所示，为本申请实施例提供的又一种通信方法的流程示意图，该方法应用于图4所示的ONAP架构。在意图实施维持阶段进入意图转译，并且根据意图转译结果调整意图可执行命令、规则或者子意图。本实施例中intentdecision FB向intent translation FB发送的消息沿用intent management FB与intent translation之间的消息，携带的参数为意图表达式。该方法可以包括以下步骤：
S500、ONAP UUI向intent management FB发送创建意图/激活意图(create intent/activate intent)请求。该请求携带意图表达式。该意图表达式可以为自然语言形式的表达式，也可以是DSL表达式。
S501、intent management FB向intent translation FB发送意图转译请求。该意图转译请求携带意图表达式，该意图表达式为DSL表达式。
S502、intent translation FB向intent knowledge repository发送意图知识查询请求，intent knowledge repository向intent translation FB返回意图知识。
S503、intent translation FB对意图知识进行编排，并且向intent decision FB发送意图决策请求。该意图决策请求中携带多组可执行命令、规则组或者子意图，请求其对意图转译结果进行决策。该意图决策请求中还携带第一阶段标识、意图标识以及意图转译结果，该第一阶段标识还用于指示转译结果供意图执行使用。
S504、intent decision FB向ONAP policy FB发送查询意图决策规则请求，ONAP policy FB将决策规则发送给intent decision FB。
S505、intent decision FB对意图转译结果进行决策，将决策结果发送给ONAP中其他组件或者其他意图作用实体，如ONAP SO或者ONAP controllers。
具体地，示例了两种选择方式：
选择方式a、intent decision FB向ONAP SO发送创建网络切片请求，该创建网络切片请求包括CS profile。ONAP SO与ONAP DCAE之间交互创建网络切片实例。然后，ONAP SO向intent decision FB发送创建网络切片响应，该创建网络切片响应包括网络切片标识(network slice identity，NSI)。
选择方式b、intent decision FB向ONAP SO发送修改网络切片请求，该修改网络切片请求包括CS profile和NS。ONAP SO与ONAP DCAE之间交互修改网络切片实例。然后，ONAP SO向intent decision FB发送修改网络切片响应，该修改网络切片响应包括网络切片标识(network slice identity，NSI)。
S506、intent decision FB向意图执行功能模块(intent handler FB)发送意图性能数据获取消息，消息中携带指示意图目标是否完成以及网络状态的性能数据指示。intent handler FB可以单独部署，也可以作为ONAPDCAE的一部分。
S507、intent handler FB根据步骤S506收到的性能数据指示，判断意图达成情况以及网络状态，并向intent decision FB发送意图达成情况以及网络状态。
S508、intent decision FB向intent translation FB发送意图转译请求(Call intent translation)，此请求中携带意图表达式，此意图表达式可以与步骤S501中的表达式相同，也可以是根据步骤S503生成的转译结果生成的新的意图表达式。
S509、intent translation FB向intent knowledge repository发送意图知识查询请求，intent knowledge repository向intent translation FB返回意图知识。
S510、intent translation FB对意图知识进行编排，并且向intent decision FB发送意图决策 请求，该意图决策请求中携带多组可执行命令、规则组或者子意图，请求其对意图转译结果进行决策。且该意图决策请求中携带第二阶段标识、意图标识以及意图转译结果，该第二阶段标识用于指示转译结果供意图维持阶段使用。
S511、intent decision FB将转译结果发送给ONAP中其他组件或者是其他意图作用实体，如ONAP SO或者ONAP Controller。具体可参考步骤S505。
S512～S513、intent decision FB将意图达成情况反馈给意图创建者(ONAP UUI)。
在该实施例中增加在意图维持阶段意图执行模块与意图转译模块之间的意图转译请求，使得意图系统在意图维持阶段能够根据意图目标的达成情况动态调整意图对应的执行策略。
已有的意图的转译只在意图执行阶段之前发生一次，本实施例中，在意图的维持阶段加入了意图转译，在整个意图的生命周期中会发生多次意图转译。使得意图系统在维持阶段能够运用更精确的转译结果调整意图可执行的命令、规则或者子意图。
如图10所示，为本申请实施例提供的又一种通信方法的流程示意图，该方法应用于图4所示的ONAP架构。该通信方法与图9所示的通信方法的区别在于，该通信方法中意图执行以及意图转译模块之间的消息采用新的消息，消息中携带意图相关参数，即图10中的消息S608与图9所示实施例中的消息S508不同。该方法可以包括以下步骤：
S600、ONAP UUI向intent management FB发送创建意图/激活意图(create intent/activate intent)请求。该请求携带意图表达式。该意图表达式可以为自然语言形式的表达式，也可以是DSL表达式。
S601、intent management FB向intent translation FB发送意图转译请求。该意图转译请求携带意图表达式，该意图表达式为DSL表达式。
S602、intent translation FB向intent knowledge repository发送意图知识查询请求，intent knowledge repository向intent translation FB返回意图知识。
S603、intent translation FB对意图知识进行编排，并且向intent decision FB发送意图决策请求。该意图决策请求中携带多组可执行命令、规则组或者子意图，请求其对意图转译结果进行决策。该意图决策请求中还携带第一阶段标识、意图标识以及意图转译结果，该第一阶段标识还用于指示转译结果供意图执行使用。
S604、intent decision FB向ONAP policy FB发送查询意图决策规则请求，ONAP policy FB将决策规则发送给intent decision FB。
S605、intent decision FB对意图转译结果进行决策，将决策结果发送给ONAP中其他组件或者其他意图作用实体，如ONAP SO或者ONAP controllers。
具体地，示例了两种选择方式：
选择方式a、intent decision FB向ONAP SO发送创建网络切片请求，该创建网络切片请求包括CS profile。ONAP SO与ONAP DCAE之间交互创建网络切片实例。然后，ONAP SO向intent decision FB发送创建网络切片响应，该创建网络切片响应包括网络切片标识(network slice identity，NSI)。
选择方式b、intent decision FB向ONAP SO发送修改网络切片请求，该修改网络切片请求包括CS profile和NS。ONAP SO与ONAP DCAE之间交互修改网络切片实例。然后，ONAP SO向intent decision FB发送修改网络切片响应，该修改网络切片响应包括网络切片标识(network slice identity，NSI)。
S606、intent decision FB向意图执行功能模块(intent handler FB)发送意图性能数据获取消息，消息中携带指示意图目标是否完成以及网络状态的性能数据指示。intent handler FB可 以单独部署，也可以作为ONAPDCAE的一部分。
S607、intent handler FB根据步骤S606收到的性能数据指示，判断意图达成情况以及网络状态，并向intent decision FB发送意图达成情况以及网络状态。
S608、intent decision FB向intent translation FB发送意图转译请求(Call intent translation for assurance)，此请求携带参数为业务指标，即这里不用构造意图表达式。
S609、intent translation FB向intent knowledge repository发送意图知识查询请求，intent knowledge repository向intent translation FB返回意图知识。
S610、intent translation FB对意图知识进行编排，并且向intent decision FB发送意图决策请求，该意图决策请求中携带多组可执行命令、规则组或者子意图，请求其对意图转译结果进行决策。且该意图决策请求中携带第二阶段标识、意图标识以及意图转译结果，该第二阶段标识用于指示转译结果供意图维持阶段使用。
S611、intent decision FB将转译结果发送给ONAP中其他组件或者是其他意图作用实体，如ONAP SO或者ONAP Controller。具体可参考步骤S605。
S612～S613、intent decision FB将意图达成情况反馈给意图创建者(ONAP UUI)。
在该实施例中增加在意图维持阶段意图执行模块与意图转译模块之间的意图转译请求，使得意图系统在意图维持阶段能够根据意图目标的达成情况动态调整意图对应的执行策略。
已有的意图的转译只在意图执行阶段之前发生一次，本实施例中，在意图的维持阶段加入了意图转译，在整个意图的生命周期中会发生多次意图转译。使得意图系统在维持阶段能够运用更精确的转译结果调整意图可执行的命令、规则或者子意图。
基于上述通信方法的同一构思，如图11所示，本申请实施例还提供了一种通信装置，该通信装置400是上述实施例中的第一网元。具体地，该通信装置400包括：处理单元41和收发单元42。其中：
处理单元41，用于获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；
所述处理单元41，还用于根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；
所述处理单元41，还用于根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；
收发单元42，用于向第二网元发送所述第一转译结果对应的第一执行命令。
在一种可能的实现中，所述处理单元41，还用于对所述意图进行转译，得到第二转译结果；
所述处理单元41，还用于进行网络状态判断、所述第一意图目标是否达成的判断，并根据网络状态判断和所述第一意图目标是否达成的判断结果，更新所述第二转译结果；
所述处理单元41，还用于采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果和更新的所述第二转译结果用于所述意图执行过程。
在又一种可能的实现中，所述处理单元41，还用于确定所述第二意图目标未达成时，根据所述第一阶段标识确定对所述意图再次进行转译，得到所述第一转译结果；
所述处理单元41，还用于采用第二阶段标识对所述第一转译结果进行标记，所述第二阶段标识用于标记所述第一转译结果用于意图维持过程。
在又一种可能的实现中，所述处理单元41，还用于获取所述第二意图目标对应的意图表 达式；
所述处理单元41，还用于根据所述第二意图目标对应的意图表达式，获取意图知识；
所述处理单元41，还用于对所述意图知识进行编排，得到第一转译结果。
在又一种可能的实现中，所述第一意图目标为网络配置，所述第二意图目标为网络性能的调节。
有关上述处理单元41和收发单元42的具体实现可参考图5～图10所示方法实施例中的第一网元的相关描述。
根据本申请实施例提供的一种通信装置，针对包括两种以上意图目标的意图，在意图维持阶段，可以再次对意图进行转译，根据意图转译结果调整执行命令，从而提高了意图目标达成的概率。
如图12所示，还提供了一种通信装置的硬件结构示意图，该通信装置用于执行上述通信方法。上述方法中的部分或全部可以通过硬件来实现，也可以通过软件或固件来实现。
可选的，该通信装置在具体实现时可以是芯片或者集成电路。
可选的，当上述实施例的通信方法中的部分或全部通过软件或固件来实现时，可以通过图12提供的一种通信装置500来实现。如图12所示，该通信装置500可包括：
存储器53和处理器54(装置中的处理器54可以是一个或多个，图12中以一个处理器为例)，还可以包括输入装置51、输出装置52。在本实施例中，输入装置51、输出装置52、存储器53和处理器54可通过总线或其它方式连接，其中，图12中以通过总线连接为例。
其中，在一个实施例中，处理器54用于执行图5～图10中第一网元所执行的方法步骤。
可选的，上述通信方法的程序可以存储在存储器53中。该存储器53可以是物理上独立的单元，也可以与处理器54集成在一起。该存储器53也可以用于存储数据。
可选的，当上述实施例的通信方法中的部分或全部通过软件实现时，该通信装置也可以只包括处理器。用于存储程序的存储器位于该通信装置之外，处理器通过电路或电线与存储器连接，用于读取并执行存储器中存储的程序。
处理器可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，或WLAN设备。
处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
存储器可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。
本领域技术人员应明白，本公开一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本公开一个或多个实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本公开一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理 器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
本申请实施例还提供一种计算机可读存储介质，该存储介质上可以存储有计算机程序，所述程序被处理器执行时实现本公开任一实施例描述的通信方法的步骤。
本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本公开任一实施例描述的通信方法的步骤。
本申请实施例还提供一种通信系统，该通信系统包括上述的通信装置。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
应理解，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。所显示或讨论的相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者通过该计算机可读存储介质进行传输。该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是只读存储器(read-only memory，ROM)，或随机存取存储器(random access memory，RAM)，或磁性介质，例如，软盘、硬盘、磁带、 磁碟、或光介质，例如，数字通用光盘(digital versatile disc，DVD)、或者半导体介质，例如，固态硬盘(solid state disk，SSD)等。

Claims (14)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一网元获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；
    所述第一网元根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；
    所述第一网元根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；
    所述第一网元向第二网元发送所述第一转译结果对应的第一执行命令。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网元获取意图执行过程中的性能数据之前，所述方法还包括：
    所述第一网元对所述意图进行转译，得到第二转译结果；
    所述第一网元进行网络状态判断、所述第一意图目标是否达成的判断，并根据网络状态判断和所述第一意图目标是否达成的判断结果，更新所述第二转译结果；
    所述第一网元采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果和更新的所述第二转译结果用于所述意图执行过程。
  3. 根据权利要求2所述的方法，其特征在于，所述第一网元确定所述第二意图目标未达成时，所述方法还包括：
    所述第一网元根据所述第一阶段标识确定对所述意图再次进行转译，得到所述第一转译结果；
    所述第一网元采用第二阶段标识对所述第一转译结果进行标记，所述第二阶段标识用于标记所述第一转译结果用于意图维持过程。
  4. 根据权利要求1～3任一项所述的方法，其特征在于，所述第一网元根据所述第二意图目标，对所述意图进行转译，得到第一转译结果，包括：
    所述第一网元获取所述第二意图目标对应的意图表达式；
    所述第一网元根据所述第二意图目标对应的意图表达式，获取意图知识；
    所述第一网元对所述意图知识进行编排，得到第一转译结果。
  5. 根据权利要求1～4任一项所述的方法，其特征在于，所述第一意图目标为网络配置，所述第二意图目标为网络性能的调节。
  6. 一种通信装置，其特征在于，所述装置包括：
    处理单元，用于获取意图执行过程中的性能数据，所述意图包括第一意图目标和第二意图目标；
    所述处理单元，还用于根据所述意图执行过程中的性能数据，确定所述第二意图目标未达成；
    所述处理单元，还用于根据所述第二意图目标，对所述意图进行转译，得到第一转译结果；
    收发单元，用于向第二网元发送所述第一转译结果对应的第一执行命令。
  7. 根据权利要求6所述的装置，其特征在于：
    所述处理单元，还用于对所述意图进行转译，得到第二转译结果；
    所述处理单元，还用于进行网络状态判断、所述第一意图目标是否达成的判断，并根据网络状态判断和所述第一意图目标是否达成的判断结果，更新所述第二转译结果；
    所述处理单元，还用于采用第一阶段标识对所述第二转译结果和更新的所述第二转译结果进行标记，所述第一阶段标识用于标记所述第二转译结果和更新的所述第二转译结果用于所述意图执行过程。
  8. 根据权利要求7所述的装置，其特征在于，所述处理单元，还用于确定所述第二意图目标未达成时，根据所述第一阶段标识确定对所述意图再次进行转译，得到所述第一转译结果；
    所述处理单元，还用于采用第二阶段标识对所述第一转译结果进行标记，所述第二阶段标识用于标记所述第一转译结果用于意图维持过程。
  9. 根据权利要求6～8任一项所述的装置，其特征在于：
    所述处理单元，还用于获取所述第二意图目标对应的意图表达式；
    所述处理单元，还用于根据所述第二意图目标对应的意图表达式，获取意图知识；
    所述处理单元，还用于对所述意图知识进行编排，得到第一转译结果。
  10. 根据权利要求6～9任一项所述的装置，其特征在于，所述第一意图目标为网络配置，所述第二意图目标为网络性能的调节。
  11. 一种通信系统，其特征在于，包括如权利要求6～10任一项所述的装置和第二网元。
  12. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，并读取存储器中的指令，并根据所述指令实现如权利要求1～5任一项所述的方法。
  13. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1～5任一项所述的方法。
  14. 一种计算机程序产品，其特征在于，所述计算机程序产品被计算机执行时，使得所述计算机实现权利要求1～5任一项所述的方法。
PCT/CN2021/113637 2020-09-19 2021-08-19 通信方法及装置、系统 WO2022057564A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010990421.9 2020-09-19
CN202010990421.9A CN114258035B (zh) 2020-09-19 2020-09-19 通信方法及装置、系统

Publications (1)

Publication Number Publication Date
WO2022057564A1 true WO2022057564A1 (zh) 2022-03-24

Family

ID=80776414

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/113637 WO2022057564A1 (zh) 2020-09-19 2021-08-19 通信方法及装置、系统

Country Status (2)

Country Link
CN (1) CN114258035B (zh)
WO (1) WO2022057564A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024099249A1 (zh) * 2022-11-11 2024-05-16 华为技术有限公司 一种信息处理方法及设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118118358A (zh) * 2022-11-30 2024-05-31 华为技术有限公司 一种意图管理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160241436A1 (en) * 2015-02-17 2016-08-18 Futurewei Technologies, Inc. Intent Based Network Configuration
CN110278111A (zh) * 2019-05-29 2019-09-24 西安电子科技大学 一种意图驱动网络通用架构及其意图驱动网络转译方法
US20200084120A1 (en) * 2018-09-07 2020-03-12 Juniper Networks, Inc. Dynamic intent assurance and programmability in computer networks
CN111277442A (zh) * 2020-01-21 2020-06-12 赣江新区智慧物联研究院有限公司 无线意图驱动网络的管理方法、装置及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190238410A1 (en) * 2018-01-31 2019-08-01 Hewlett Packard Enterprise Development Lp Verifying network intents
CN110198237B (zh) * 2019-05-27 2021-05-04 北京邮电大学 一种无线意图驱动网络的配置方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160241436A1 (en) * 2015-02-17 2016-08-18 Futurewei Technologies, Inc. Intent Based Network Configuration
US20200084120A1 (en) * 2018-09-07 2020-03-12 Juniper Networks, Inc. Dynamic intent assurance and programmability in computer networks
CN110278111A (zh) * 2019-05-29 2019-09-24 西安电子科技大学 一种意图驱动网络通用架构及其意图驱动网络转译方法
CN111277442A (zh) * 2020-01-21 2020-06-12 赣江新区智慧物联研究院有限公司 无线意图驱动网络的管理方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on scenarios for Intent driven management services for mobile networks (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.812, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V0.8.0, 6 November 2019 (2019-11-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 41, XP051840553 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024099249A1 (zh) * 2022-11-11 2024-05-16 华为技术有限公司 一种信息处理方法及设备

Also Published As

Publication number Publication date
CN114258035A (zh) 2022-03-29
CN114258035B (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
EP3098731B1 (en) System for linking diverse data systems
US10387011B2 (en) System and method to capture and document cross-product compatibility status information for industrial devices
US20170024290A1 (en) SYSTEM FOR DEVELOPMENT OF IoT SYSTEM ARCHITECTURE
WO2022057564A1 (zh) 通信方法及装置、系统
US9762454B2 (en) System and method to capture and document cross-product compatibility status information for industrial devices
Mavrogiorgou et al. Internet of medical things (IoMT): acquiring and transforming data into HL7 FHIR through 5G network slicing
US20150296022A1 (en) SYSTEM FOR MEDIATING HETEROGENEOUS DATA EXCHANGE SCHEMES BETWEEN IoT DEVICES
Guinea et al. A systematic review on the engineering of software for ubiquitous systems
GB2602230A (en) Configuration in process plant using i/o-abstracted field device configurations
US11381463B2 (en) System and method for a generic key performance indicator platform
CN108846020A (zh) 基于多源异构数据进行知识图谱自动化构建方法、系统
US20230289149A1 (en) System and method for using a graphical user interface to develop a virtual programmable logic controller
US11354152B2 (en) Self-evolving microservices
EP4156735A1 (en) Communication method and apparatus, and system
CN112653703A (zh) 一种基于边缘计算的多医疗协议转换解析方法和系统
CN107370808A (zh) 一种用于对大数据任务进行分布式处理的方法
Donahue et al. Veterans health information exchange: successes and challenges of nationwide interoperability
Carnero et al. Managing and deploying distributed and deep neural models through Kafka-ML in the cloud-to-things continuum
CN110717268B (zh) 一种基于face架构的可移植组件单元封装方法
JP2020149630A (ja) 制御システム、設定装置、および設定プログラム
Fu et al. Design and implementation of clinical LIS360 laboratory management system based on AI technology
Pico-Valencia et al. A systematic method for building internet of agents applications based on the linked open data approach
RU2742261C1 (ru) Цифровая компьютерно-реализуемая платформа для создания медицинских приложений с использованием искусственного интеллекта и способ её работы
US10324594B2 (en) Enterprise protocol management
CN114610648A (zh) 一种测试方法、装置及设备

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21868392

Country of ref document: EP

Kind code of ref document: A1