An information processing method, apparatus, computer-readable storage medium, and device

Abstract

Embodiments of the present application disclose an information processing method, device, computer readable storage medium and equipment, the method comprises: based on the general information model and the field information model for policy management, the policy instance is parsed and / or the policy instance is executed, wherein the general information model is used for describing the common characteristics of different fields and / or different levels of policy, and the field information model is used for describing the information related to the policy running environment and / or interaction of each field.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to an information processing method and device, a computer readable storage medium and equipment. BACKGROUND

[0002] The self-intelligent network is born with the development of the digital and intelligent society, and through the network operation, the self-intelligent network realizes the digital and intelligent transformation and upgrading, meets the higher requirements of digital and intelligent products on network experience and agile support, and leads the information service to a new level. The self-intelligent network aims to build an automatic and intelligent operation and maintenance capability in the whole life cycle of the network, provide new network and ICT services with "zero waiting, zero failure and zero contact" for consumers and vertical industry customers, and create a self-configuration, self-repair and self-optimization digital and intelligent operation and maintenance capability for network intelligent operation and maintenance.

[0003] Rules / policies are important features of the self-intelligent network capability improvement. At present, the average level of the whole network is L2, and the typical feature of L2 is static injection rules, and the policy implementation includes automatic closed loop of state monitoring, condition analysis and action execution. Further, the self-intelligent network can be divided into L3, L4, L5 and other levels, wherein the typical feature of L3 is dynamic decoupling rules, the typical feature of L4 is AI assisted rule generation, and the typical feature of L5 is self-adaptive evolution. Therefore, the self-intelligent network policy management technology system needs to be expanded to realize the expression and systematic management of policy rules and the enhancement of evolution capability. SUMMARY

[0004] To solve the existing technical problems, the embodiments of the present application provide an information processing method, device, computer readable storage medium and equipment.

[0005] To achieve the above-mentioned purposes, the technical solutions of the embodiments of the present application are as follows:

[0006] In a first aspect, the embodiments of the present application provide an information processing method, comprising:

[0007] Analyzing a policy instance and / or executing a policy instance based on a general information model for policy management and a domain information model, wherein the general information model is used to describe the common features of policies in different domains and / or different levels, and the domain information model is used to describe the information related to the policy running environment and / or interaction of each domain.

[0008] In a second aspect, the embodiments of the present application further provide an information processing device, comprising an execution module for analyzing a policy instance and / or executing a policy instance based on a general information model for policy management and a domain information model, wherein the general information model is used to describe the common features of policies in different domains and / or different levels, and the domain information model is used to describe the information related to the policy running environment and / or interaction of each domain.

[0009] In a third aspect, an embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps of the foregoing information processing method.

[0010] In a fourth aspect, an embodiment of the present application further provides a computer device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the foregoing information processing method when executing the program.

[0011] The information processing method, device, computer readable storage medium and computer device provided by the embodiments of the present application are based on the general information model and the domain information model to analyze and / or execute the policy instance, adopt the policy modeling method based on model combination, can plan and manage the general information model and the domain information model related to the policy running context environment and / or interaction respectively for the operation and maintenance management policy of each domain of the self-intelligent network and hierarchical and cross-domain, can realize the unified modeling and flexible on-demand expansion of the policy, and enhance the systematic management and dynamic evolution capability. BRIEF DESCRIPTION OF DRAWINGS

[0012] Figure 1 FIG. 1 is a flowchart of an information processing method according to an embodiment of the present application;

[0013] Figure 2 FIG. 1 is a flowchart of an information processing method according to an embodiment of the present application;

[0014] Figure 3 FIG. 1 is a flowchart of an information processing method according to an embodiment of the present application;

[0015] Figure 4 FIG. 1 is a flowchart of an information processing method according to an embodiment of the present application;

[0016] Figure 5 FIG. 1 is a flowchart of an information processing method according to an embodiment of the present application; DETAILED DESCRIPTION

[0017] Before introducing the information processing scheme of the embodiments of the present application, first, briefly introduce the network management related concepts in the related art.

[0018] The concepts related to management include management, managed entity and management domain, which are introduced as follows.

[0019] Management: A set of processes responsible for describing, organizing, controlling, and managing access to the lifecycle needs of information and organizational entities.

[0020] Managed Entity: A manageable object associated with a product, service, and / or resource.

[0021] Management Domain: A domain that uses a common set of management mechanisms to manage its contents. A management domain is a type of managed entity with three key characteristics: 1) has a set of administrators defined to perform management operations on the managed entities it contains; 2) defines a set of applications responsible for different management operations (e.g., monitoring, configuration, etc.); 3) defines a common set of management mechanisms, such as policy rules, to govern the behavior of the managed entities it contains.

[0022] Policy-related concepts include policy and imperative policy, which are described as follows.

[0023] Policy: A set of rules used to govern and control the changes and / or maintenance of the state of one or more managed objects. Organizations are policy-driven entities, and policies are a natural way to express rules and restrictions on behavior and then automatically enforce those rules and restrictions, with the goal of ensuring consistent decisions are made to govern the behavior of a system.

[0024] Imperative Policy: A type of policy that uses statements to explicitly change the state of a set of target objects. Imperative policies explicitly define the order of statements that make up the policy.

[0025] Model-related concepts include information model and policy model, which are described as follows.

[0026] Information Model: A representation of concepts related to a specific environment in a form that is independent of data repositories, data definition languages, query languages, implementation languages, and protocols.

[0027] Policy Model: In the embodiments of the present invention, unless explicitly stated, policy will refer to a type of imperative policy, i.e., a policy composed of events, conditions, and actions. Events are any things that happen on a timeline that are important to the management system (e.g., changes to the managed system and / or its environment); conditions are a set of attributes, characteristics, and / or values that are compared to a set of known attributes, characteristics, and / or values to determine a decision to be made; actions are a set of operations that can be performed on a set of management entities, representing a transformation or process in the system being modeled.

[0028] In the related art, rules / policies are an important feature of self-intelligent network capability improvement. Currently, the average level of the whole network is L2, and the typical feature of L2 is static injection rules, and the policy implementation includes automatic closed loop of state monitoring, condition analysis and execution action. Further, the self-intelligent network can be divided into L3, L4, L5 and other levels, wherein the typical feature of L3 is dynamic decoupling rules, and the operation and maintenance personnel can dynamically edit and import policy rules according to the policy formal specification in the system execution stage, which means that the system needs to have systematic management capability for a larger number, more extensive sources and more complex relationship of policy rule system; the typical feature of L4 is AI assisted rule generation, which means that the policy rule itself needs to be iterated automatically through application monitoring and effectiveness evaluation; and the typical feature of L5 is self-adaptive evolution, which means that the policy rule needs to dynamically adapt to the changes of the system internal and external environment and actively evolve according to the dynamically evolved system target.

[0029] Therefore, it is necessary to expand the self-intelligent network policy management technology system to realize the standardization and formalization expression of policy rules, systematic management and enhancement of dynamic evolution capability.

[0030] The application will be described in further detail below with reference to the drawings and specific embodiments. Obviously, the described embodiments are part of the embodiments of the application, rather than all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the application.

[0031] In the description of the application, it should be noted that the terms "first", "second", "third" and the like are only used for description purposes and cannot be understood as indicating or implying relative importance. These terms are only used to distinguish one element (or threshold, application, instruction or operation) from another element (or threshold, application, instruction or operation). For example, the first operation can be referred to as the second operation, and the second operation can also be referred to as the first operation without departing from the scope of the application, and the first operation and the second operation are both operations, but they are not the same operation.

[0032] The term "and / or" in the embodiments of the application means any and all possible combinations of one or more of the associated listed items. It should be noted that when used in the specification, "comprising / including" specifies the presence of the stated features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements and / or components and / or groups thereof.

[0033] The steps in the embodiments of the present application do not necessarily have to be processed in the order as described, and the steps can be selectively rearranged, deleted or added according to requirements. The step description in the embodiments of the present application is only an optional sequence combination, and does not represent all sequence combinations of the embodiments of the present application. The sequence of steps in the embodiments cannot be considered as a limitation of the present application.

[0034] The embodiments of the present application provide an information processing method. Figure 1 As shown in the flowchart of the information processing method of the embodiments of the present application, Figure 1 The method comprises the following steps.

[0035] In step 101, a policy instance is parsed and / or executed based on a common information model for policy management and a domain information model. The common information model is used to describe common features of policies in different domains and / or different levels, and the domain information model is used to describe information related to policy running environment and / or interaction of each domain.

[0036] In the embodiments, the common information model and the domain information model are both forms irrelevant to data storage, data definition language, query language, implementation language and protocol, and represent concepts related to specific environment. The common information model represents common features of policies in different domains and / or different levels, such as the same features of policies in different management domains, different levels or cross-domain and cross-level. The domain information model represents information related to policy running environment and / or interaction of each domain, such as information related to policy running context environment and policy running context interaction in each management domain.

[0037] In step 101, a policy instance is parsed and / or executed based on the common information model and the domain information model. In the embodiments, the policy instance is, for example, an instance for policy operation and maintenance management. The parsed policy instance means that elements / parameters of the policy instance corresponding to the common information model and the domain information model are determined, and the executed policy instance means that the policy instance is executed by the execution engine corresponding to each domain according to the elements / parameters of the policy instance corresponding to the common information model and the domain information model.

[0038] The information processing method of the embodiment of the present application analyzes the policy instance and / or the execution policy instance based on the general information model and the domain information model, adopts the policy modeling method based on model combination, can plan and manage the general information model and the domain information model related to the policy running context environment and / or interaction respectively for the operation and maintenance management policy of each domain of the self-intelligent network, hierarchical and cross-domain, can realize the unified modeling and flexible on-demand expansion of the policy, and enhances the systematic management and dynamic evolution capability.

[0039] In an optional embodiment of the present application, the general information model can include at least one of intention information, basic information, instruction element information, target range information and expected effectiveness information.

[0040] In the embodiment, the general information model can include but is not limited to the intention information, the basic information, the instruction element information, the target range information and the expected effectiveness information. For example, the intention information can be used to describe the intention of the policy. The intention is a service description method, which can abstractly define the network demand and give a set of expectations about the network or service without specifying technical details. The basic information can be used to describe the name, type, source, version and other information of the policy. The instruction element information can be used to describe the information related to the policy execution. The target range information can be used to describe the information related to the applicable scope of the policy. The expected effectiveness information can be used to describe the related information for evaluating the execution effect of the policy.

[0041] In some embodiments, the intention information can include at least one of the following: target domain information representing the domain to which the policy is applied; object range information representing the managed object to which the policy is applied; and expected effectiveness information representing the expected effectiveness of the policy execution. In the embodiment, the general information model can include but is not limited to the intention information such as the target domain information, the object range information and the expected effectiveness information. The target domain information can be used to describe the domain to which the policy is applied, such as the management domain type and the management domain name to which the policy is applied. The object range information can be used to describe the managed object to which the policy is applied, such as the instance identifier of the policy application object. The expected effectiveness information can be used to describe the expected effectiveness of the policy execution, such as the expected effectiveness index.

[0042] As an example, the intention information can be added in the description part of the general information model.

[0043] In some embodiments, the basic information can include at least one of the following information related to the lifecycle management of the policy: policy name, policy type, policy source, version information. For example, the policy name can be a string or identifier used to uniquely identify and accurately reference the corresponding policy model in a specific context; the policy type can be an enumerated value or string used to distinguish different types of imperative policies, for example, "ECA" can represent a "Event-Condition-Action" type of policy, "MEDA" can represent a "Match-Estimate-Decide-Act" type of policy, and the like; the policy source can be an enumerated value or string used to distinguish different sources of imperative policies, for example, "Cloud" represents a telecommunications cloud professional operator, "RAN" represents a wireless professional operator, and the like; and the version information can be a string used to specify the update relationship of different versions of the policy. It should be noted that the basic information can not include the policy type or the field corresponding to the policy type is empty, and the default value is the default type, for example, "ECA" type; the basic information can not include the policy source or the field corresponding to the policy source is empty, and the default value is the default value, for example, "NULL".

[0044] Taking the common information element Policy as an example, Table 1 is an exemplary description information of parameters in the information element Policy related to the basic information contained in the general information model. In Table 1, the "Parameter" column represents the parameters contained in the information element; the "Qualifier" column represents the attributes of whether the corresponding parameter can be supported by the system, wherein "M" represents mandatory support, and "O" represents optional support; the "Cardinality" column represents the multiplicity of the corresponding parameter (i.e. the number of "how many" and the selectivity "possible or necessary"), wherein "1" represents only one (the corresponding parameter is mandatory), "0..1" represents zero or one (the corresponding parameter is optional), "1..N" (N>1) represents 1 to N (N>1) (the corresponding parameter can be repeatedly defined), and "0..N" (N>1) represents zero to N (N>1) (the corresponding parameter can be repeatedly defined); the "Content" column represents the data type of the corresponding parameter, wherein "String" represents a string, and "Enum" represents an enumerated type; and the "Description" column represents the description information of the corresponding parameter.

[0045] As shown in Table 1, the value of the parameter policyFunctionName can describe the function or name of the policy, such as scaling, self-healing, virtual resource optimization, etc., and the value type is a string; the value of the parameter policyFlavour can describe the type of the policy, and the value range can include {ECA, OODA, MEDA, Other}, wherein ECA represents the policy type of event-condition-action, OODA represents the policy type of Observe-Orient-Decide-Act, MEDA represents the policy type of Match-Evaluate-Decide-Act, and Other represents other policy types; the value of the parameter policySource can describe the source of the policy, and the value type is a string; and the value of the parameter policyVersion can describe the version information of the policy, and the value type is a string.

[0046] Table 1

[0047]

[0048]

[0049] In some embodiments, the instruction element information can include one or more logical units related to policy execution. For example, the logical units are used to describe the trigger event, evaluation condition, action decision, etc. of policy execution, wherein the trigger event can be specified by referring to the corresponding model in the domain information model of a specific domain, to specify the set of instruction policy trigger events and their combination mode; the evaluation condition can be specified by referring to the corresponding model in the domain information model of a specific domain, to specify the set of conditions required for evaluation of instruction policy action decision and their combination mode; and the action decision can be determined by referring to the corresponding model in the domain information model of a specific domain, to determine the specific operation action to be executed according to the trigger event and the evaluation condition, which can be used to change or maintain the specific state of the managed object.

[0050] Taking a meta-policy in the form of an event-condition-action (ECA) imperative policy as an example, the meta-policy is used to monitor, evaluate and dynamically update the policy, and the corresponding meta-policy application domain is composed of three sub-modules of event triggering, condition evaluation and action execution. The meta-policy is applied to the automatic closed loop of policy knowledge management. Taking the construction of the meta-policy in the information element as an example, the parameters related to the instruction element information contained in the general information model in the information element include but are not limited to the policy element (Policy), the state element (State), the task element (Task), the context set element (ContextMap) and the context element (Context), which are introduced below based on Table 2.1 to Table 2.5.

[0051] Table 2.1 is an exemplary description information of parameters related to instruction element information in policy element, in which the column "Content" of Table 2.1 indicates that the value of the corresponding parameter is context set element, and "State" indicates that the value of the corresponding parameter is state element. As shown in Table 2.1, the value of the parameter globalContext can describe the execution element embodied by the system context during the execution of the policy, for example, the related system variables of event / condition / action used during the execution of the ECA policy, the access interface of the service interface, the access parameter, the access right, etc., and the value type is context set element. The value of the parameter firstState can describe the first state of the policy execution, for example, the event (Event) state of the ECA policy, and the value type is state element.

[0052] Table 2.1

[0053]

[0054] Table 2.2 is an exemplary description information of parameters related to instruction element information in state element, in which the column "Content" of Table 2.2 indicates that the value of the corresponding parameter is identifier, "Enum" indicates that the value of the corresponding parameter is enumeration type, "Task" indicates that the value of the corresponding parameter is task element, and "Logic" indicates that the value of the corresponding parameter is logic element. As shown in Table 2.2, the value of the parameter stateType can indicate the type of the policy state, which should be selected based on the parameter policyFlavour contained in the information element Policy shown in Table 1, the value type of the parameter stateType is enumeration type, and the value range can include {Event, Condition, Action, Other}, in which Event indicates event, Condition indicates condition, Action indicates action, and Other indicates other state type; the value of the parameter taskItem can describe the information of each task contained in the current state, in which each state (state) contains at least one task (task), and the value type is task element (Task); the value of the parameter taskSelectionLogic is used to describe the selection logic based on the current context for selecting one task from the state to complete the state transition when the state contains more than one task, and the value type is logic element (Logic); and the value of the parameter nextState can describe the identifier of the next state.

[0055] Table 2.2

[0056]

[0057] Table 2.3 is an exemplary description information of parameters related to instruction element information in task element. As shown in Table 2.3, the value of parameter taskType can describe the type of task, and when the type of policy is ECA type, the value range is {EventTask, ConditionTask, ActionTask, Other}, wherein EventTask represents event task, ConditionTask represents condition task, ActionTask represents action task, and Other represents other task type. The value of parameter taskInput can represent the input parameter of task, and the value type is context set. When taskType is EventTask, the value of parameter taskInput can describe the triggering event of policy, for example, various events such as alarms, prompts, reports and the like that can be collected / feedback / received by NFV-MANO components. The value of parameter taskLogic is used to describe the calculation logic based on context how to obtain the output taskOutput from the input taskInpu of task. The value of parameter taskOutput can be used to describe the output result of task, and when taskType is ActionTask, taskOutput is used to describe the execution action of policy.

[0058] Table 2.3

[0059]

[0060] Table 2.4 is an exemplary description information of parameters related to instruction element information in context set element. In Table 2.4, “Context” in the column of “Content” means that the value of corresponding parameter is context element. As shown in Table 2.4, the value of parameter mapName can describe the function of the context set element. The value of parameter contextItem can describe the specific context variable contained, and the value type is context element.

[0061] Table 2.4

[0062]

[0063] Table 2.5 is an exemplary description information of parameters related to instruction element information in context element. As shown in Table 2.5, the value of parameter contextName can describe the function of context element. The value of parameter contextAccess can describe the access address of context element. The value of parameter contextParameter can describe the access parameter of context element, for example, it can be a sequence of key-value pair (KVP, KeyValuePair) pairs, wherein the key is parameter name, and the value is the access input parameter of context.

[0064] Table 2.5

[0065]

[0066] In some embodiments, the target scope information can include one or more of a domain and / or managed object that describes the scope of the policy application. For example, the domain of the scope of the policy application can be uniquely identified and accurately referenced in a particular context by referencing the corresponding model in the domain information model of the particular domain used by the policy model. The managed object of the scope of the policy application can be uniquely identified and accurately referenced in a particular context by referencing the corresponding model in the domain information model of the particular domain used by the policy model.

[0067] For example, the parameters in the information element Policy that are related to the target scope information include, but are not limited to, domain ID, domain type, object ID, object type, etc. When the relevant attributes are not present, the target scope of the policy can be defaulted to the current system full scope (all domains / managed objects).

[0068] Table 3 is an exemplary description information of parameters related to target range information in the information element Policy. As shown in Table 3, the value of the parameter targetDomainType can describe the type of the management domain to which the policy applies. In the embodiment, the name and meaning of all management domains should be uniformly planned by the network operator according to the actual production network. For example, the combination of geographical area, professional field, machine room identifier, device type, and the like can be combined. The default value can be the current management domain. The value range of the parameter targetDomainType can include {RAN, TN, CN, NFV-MANO, Other}, wherein RAN represents an access network, TN represents a transmission network, CN represents a core network, NFV-MANO represents a network function virtualization management and orchestrator, and Other represents other management domains. The value of the parameter targetDomainID can describe the identifier of the management domain to which the policy applies. The value of the parameter targetObjectType can describe the type of the managed object to which the policy applies, which can depend on the type of the management domain. Different management domain types correspond to different types of managed objects. For example, when the value of the management domain is "RAN", the value of the type of the managed object can include "base station", "cell", "link", or other. The value of the parameter targetObjectID can describe the instance identifier of the managed object to which the policy applies. In the embodiment, the name and meaning of all managed objects should be uniformly planned by the network operator according to the actual production network. For example, the device number in the uniform resource management system can be obtained by combining geographical area, professional field, machine room identifier, device type, and device identifier. The default value can be all managed objects of the current management domain.

[0069] Table 3

[0070]

[0071]

[0072] In some embodiments, the expected effectiveness information can include one or more metrics describing the effectiveness of the policy application. For example, the metrics can include functional metrics, performance metrics, and availability metrics, each of which can be described by referencing a corresponding model in a specific management domain extension model, and reusing the modeling of the evaluation conditions in the instruction element information.

[0073] For example, the information element Policy, Table 4.1 shows exemplary description information of parameters related to the expected effectiveness information in the information element Policy. As shown in Table 4.1, the parameters related to the expected effectiveness information in the information element Policy can include, but are not limited to, funcExpectation, perfExpectation, stabExpectation, and the like. The value of the parameter funcExpectation can describe the expected functional metrics of the policy application, the value of the parameter perfExpectation can describe the expected performance metrics of the policy application, and the value of the parameter stabExpectation can describe the expected availability metrics of the policy application.

[0074] Table 4.1

[0075]

[0076]

[0077] The parameters funcExpectation, perfExpectation, and stabExpectation described above can describe the expected metrics evaluation conditions of the policy application by using the logic element in the domain information model. Table 4.2 shows exemplary description information of parameters related to the expected effectiveness information in the logic element. As shown in Table 4.2, the value of the parameter logicName can describe the function of the logic element, the value of the parameter logicDsl can describe the domain-specific language used to implement the logic element, such as Shell, Python, Java, and the like, and the value of the parameter logicCode can describe the logic code implemented using the programming language of the type specified by the parameter logicDsl.

[0078] Table 4.2

[0079]

[0080] In an alternative embodiment of the present application, the domain information model can include at least one of: a domain information model corresponding to each domain and related to instruction element information; a domain information model corresponding to each domain and related to expected effectiveness information; a domain information model corresponding to each domain and related to target scope information. In this embodiment, the domain information model can include, but is not limited to, three types of domain information model, i.e., a domain information model corresponding to each domain and related to instruction element information, a domain information model corresponding to each domain and related to expected effectiveness information, and a domain information model corresponding to each domain and related to target scope information.

[0081] In some embodiments, the domain information model related to instruction element information can be used to provide information element definitions related to policy execution. For example, the domain information model related to instruction element information can be used to provide all specific information element definitions related to instruction element information that have been well defined and are believed to be executable in each domain, such as specific information element definitions related to trigger events, evaluation conditions, and action decisions.

[0082] In some embodiments, the domain information model related to expected effectiveness information can be used to provide information element definitions related to policy application effect evaluation. For example, the domain information model related to expected effectiveness information can be used to provide all specific information element definitions related to expected effectiveness information that have been well defined and are believed to be executable in each domain, such as specific information element definitions related to a set of function indicators, performance indicators, availability indicators, and combinations thereof of policy application.

[0083] In some embodiments, the domain information model related to target scope information can be used to provide information element definitions related to policy application scope. For example, the domain information model related to target scope can be used to provide all specific information element definitions related to object scope information that have been well defined and are believed to be interfaced by the current policy management application domain in each domain, such as specific information element definitions related to a set of management domains and / or managed objects of policy application.

[0084] The information processing method of the embodiment of the present application adopts a strategy modeling method based on model combination, can separately plan and manage the general information model and the domain information model for the operation and maintenance management strategies of each field of the self-intelligent network, hierarchical and cross-domain, can realize unified modeling and flexible on-demand expansion of the strategies, and can expand the intention information in the general information model, increase the strategy modeling expansion information of the target domain information (for example, the management domain), the object range information (for example, the managed object), and the expected effect information (for example, the effectiveness index), can provide formal description and registration and interaction mechanism for the distributed strategy modeling elements (for example, the trigger event, the action execution, and the condition evaluation), so as to provide reference indexes for the suitability and feasibility evaluation of the strategy application required by the dynamic automatic iteration and adaptive evolution of the strategy management.

[0085] As an optional implementation, the method can further include: acquiring the respective corresponding capability information of all fields, the capability information being used to determine the domain information model; the capability information including at least one of the following: information element definition, code implementation, and service interface corresponding to the instruction element information of each field; information element definition, code implementation, and service interface corresponding to the expected effectiveness information of each field; information element definition, code implementation, and service interface corresponding to the target range information of each field.

[0086] In the embodiment, the respective fields can also register the capabilities corresponding to the instruction element information, the expected effectiveness information, and the target range information, for example, the sub-management domain can register the capabilities to the upper management domain in a step-by-step manner, or the global centralized registration of the capabilities can be adopted.

[0087] For example, the capability information corresponding to the instruction element information can be used to provide all specific information element definitions, code implementations, and service interfaces related to the instruction element information that have been well defined and are believed to be executable in the corresponding management domain, for example, information element definitions, code implementations, and service interfaces describing the trigger event, the evaluation condition, and the action decision; the capability information corresponding to the expected effectiveness information can be used to provide all specific information element definitions, code implementations, and service interfaces related to the expected effectiveness information that have been well defined and are believed to be executable in the corresponding management domain, for example, information element definitions, code implementations, and service interfaces describing the function, the performance, the available index set, and the combination thereof; and the capability information corresponding to the target range information can be used to provide all specific information element definitions, code implementations, and service interfaces of the management domain / managed object set that have been well defined and are believed to be connected to the management domain by the management domain of the strategy application in the corresponding management domain.

[0088] Based on the foregoing embodiments, the embodiments of the present application further provide an information processing method. In the embodiments, the parsing and / or executing of the policy instance based on the general information model and the domain information model for policy management can include: determining a domain model instance according to the domain information model, and updating a description part of the general information model contained in the policy instance; the domain model instance is used to provide a context environment and / or context interaction information for running of the policy instance; and the parsing and / or executing of the policy instance based on the updated general information model and the domain model instance.

[0089] In the embodiments, the domain model instance corresponding to the policy instance can be determined according to the information element definition (i.e., the domain information model related to the instruction element information) provided by the domain information model related to the policy execution, the information element definition (i.e., the domain information model related to the expected effect information) related to the policy application effect evaluation, and the information element definition (i.e., the domain information model related to the target range information) related to the policy application range; meanwhile, the description part of the model constructed by the general information model in the policy instance can be updated; and the parsing and / or executing of the policy instance based on the updated general information model and the domain model instance.

[0090] For example, the description part can be added with information related to the policy source, the policy version, the policy application management domain, the policy application managed object, and the policy expected effect.

[0091] In some embodiments, the updating of the description part of the general information model contained in the policy instance can include: obtaining an intention of the policy; and adding corresponding intention information in the description part of the general information model based on the intention, the intention information including at least one of the following: target domain information representing a domain to which the policy is applied, object range information representing a managed object to which the policy is applied, and expected effect information representing an expected effect of the policy execution.

[0092] In some embodiments, the parameters related to the target domain information, the object range information, and the expected effect information can be added in the information element Policy shown in Table 1, such as a parameter describing a management domain type, a parameter describing a management domain identifier, a parameter describing a managed object type, a parameter describing a managed object identifier, a parameter describing an expected function index, a parameter describing an expected performance index, and a parameter describing an expected availability index.

[0093] In the embodiment, the existing description model of the instructive policy can be extended in the general information model based on the intention, and the extension information for the target (management domain), the policy application range (managed object), and the expected effect (effectiveness index) is added. On the one hand, the background knowledge required for the identification and resolution of potential policy conflicts in the policy management system is provided, and on the other hand, the reference index required for the monitoring and evaluation of the applicability, feasibility and effectiveness of the policy application in the dynamic automatic iteration and self-adaptive evolution of the policy management is provided.

[0094] In an optional embodiment of the present application, the parsing of the policy instance and / or the execution policy instance based on the updated general information model and the domain information model can include: parsing the information elements related to at least one of the instruction element information, the target range information and the expected effectiveness information contained in the corresponding policy instance based on the general information model; and parsing the parameter values of the information elements contained in the corresponding policy instance based on the domain information model.

[0095] For example, referring to the foregoing Tables 2.1 to 2.5, the information elements related to the instruction element information can include the policy element, the state element, the task element, the context set element and the context element, referring to Table 3, the elements related to the target range information can include the parameters targetDomainType, targetDomainID, targetObjectType, targetObjectID in the information element Policy, and referring to Tables 4.1 to 4.2, the information elements related to the expected effectiveness information can include the parameters funcExpectation, perfExpectation, stabExpectation in the information element Policy.

[0096] In some embodiments, the domain model instance includes a first model instance corresponding to the context element and / or a second model instance corresponding to the logic element; and the parsing of the policy instance and / or the execution policy instance based on the updated general information model and the domain model instance can include: determining the parameters of the context element by referring to the first model instance, and / or determining the parameters of the logic element by referring to the second model instance; and parsing the policy instance and / or the execution policy instance based on the parameters of the context element and / or the parameters of the logic element.

[0097] For example, the parameters funcExpectation, perfExpectation, stabExpectation, and the parameter taskLogic in the task element can be determined by using the corresponding logic elements in the domain information model, and the parameter contextItem in the context set element can be determined by using the corresponding context element in the domain information model. Thus, the context element and the logic element can be used to combine the general information model and the domain information model.

[0098] In an optional embodiment of the present application, the information elements related to the instruction element information include at least one of the following: a state element for describing state information of a policy from triggering to execution; a task element for describing information of tasks to be executed by a policy execution engine in each state; and a logic element for describing processing logic of the policy execution engine for executing the tasks. In this embodiment, the Logic element can be used by the policy execution engine to analyze and execute the policy tasks, the Context element can be used by each management domain to define specific instances of the domain interaction context, and the Logic element can be used by each management domain to define specific logic instances of the domain policy tasks using the domain-specific language. The state element and the task element can be referred to Table 2.2 and Table 2.3, which are not described herein again for the sake of brevity.

[0099] In an optional embodiment of the present application, the information elements related to the instruction element information in the domain information model further include at least one of the following: a context element for describing input and output contexts of each policy element, state element or task element; and a context set element for describing each context element. In this embodiment, the Context element can be used by the policy modeling to model the execution context of the corresponding general information model, which can be referred to Table 2.5 for the sake of brevity, and is not described herein again.

[0100] In an optional embodiment of the present application, the adding of the corresponding intention information in the description part of the general information model based on the intention includes: updating the description part based on the intention, and the updated description part includes at least one of the following: a parameter for describing a domain type of a policy application; a parameter for describing a domain identifier of the policy application; a parameter for describing a managed object type of the policy application; a parameter for describing a managed object identifier of the policy application; and a parameter for describing an expected result of the policy execution.

[0101] Exemplarily, the parameters targetDomainType, targetDomainID, targetObjectType, targetObjectID, Expectations and the like can be added in the information element Policy shown in Table 1, wherein the value of the parameter targetDomainType can describe the type of the domain to which the policy is applied, the value of the parameter targetDomainID can describe the identification of the domain to which the policy is applied, the value of the parameter targetObjectType can describe the type of the managed object to which the policy is applied, the value of the parameter targetObjectID can describe the identification of the managed object to which the policy is applied, and the value of the parameter Expectations can describe the expected effect of the policy execution.

[0102] The information processing scheme of the embodiment of the application will be described below in combination with a specific application scenario.

[0103] Figure 2 A schematic diagram of the relationship between the information elements in the NFV-MANO policy information model of the embodiment of the application is shown in Table 1. Figure 2 As shown in Table 1, the general information model in the NFV-MANO policy information model includes the information element Policy, the information element State and the information element Task, and the domain information model includes the information element Context, the information element ContextMap and the information element Logic. Among them, the information element Policy can refer to the information element ContextMap through the parameter localContext, the information element ContextMap can be associated with the information element Context, the information element State can refer to the information element Logic through the parameters taskSelectionLogic and stateFinalizerLogic, the information element Task can refer to the information element ContextMap through the parameters taskInput / taskOutput, and refer to the information element ContextMap through the parameter taskLogic.

[0104] The information elements Policy, State, Task, Logic, ContextMap and Context will be introduced respectively through Tables 5.1 to 5.6.

[0105] Table 5.1 is an exemplary description of parameters included in the information element Policy in this example. As shown in Table 5.1, the information element Policy is a deployment template describing the deployment of a policy, and contains basic information required by a policy and information for constructing constituent items of the policy. The value of the parameter policyFunctionDescription can describe the function of the corresponding policy, such as scaling, self-healing, virtual resource optimization, etc. The value of the parameter policyFlavour can describe the expression form of the policy, such as ECA, OODA, MEDA, etc. The value type is an enumeration type, and the value range can be {ECA, OODA, MEDA, Other}, where Other represents other expression forms of the policy in addition to ECA, OODA, and MEDA. The value of the parameter targetType can describe the scope of the policy. If the policy is universal and can be applied to all managed objects, the value can be Common. If the policy is only applied to specific managed objects, the value can be Specific. The value of the parameter firstState can specify the first state of the policy execution, such as the Event state of the ECA policy. The value of the parameter globalContext can describe the system global context of the policy execution, such as the access interface / parameter / permission of the related system variables / service interface of event / condition / action required by the ECA policy execution. The value of the parameter localContext can describe the internal context of the policy execution, which is used for variable transmission / parameter sharing between different states / tasks, such as the specific results of the condition evaluation in the ECA policy execution as branch conditions for selecting specific actions to execute.

[0106] Referring to Table 5.1, the information element Policy can be extended in this embodiment to include the parameters policySource, policyVersion, targetDomainType, targetDomainID, targetObjectType, targetObjectID, and expectations. The value of the parameter policySource can describe the source of the policy, and the value of the parameter policyVersion can describe the version information of the policy.

[0107] The value of the parameter targetDomainType can describe the policy application management domain type. In this example, the name of all management domains and their meanings should be uniformly planned by the network operator according to the actual production network. For example, the name can be allocated according to a geographical area, a professional field, a machine room identifier, a device type, and the like, or a combination thereof. The default value can be the current management domain. For example, the value range can be {RAN, TN, CN, NFV-MANO, Other}, where RAN represents an access network, TN represents a transmission network, CN represents a core network, NFV-MANO represents a network function virtualization management and orchestrator, and Other represents another management domain type. The value of the parameter targetDomainID can describe the policy application management domain identifier.

[0108] The value of the parameter targetObjectType can describe the policy application managed object type, which depends on the management domain type, that is, the corresponding managed object is different when the management domain type is different. For example, when the value of the management domain type is "RAN", the value range of the managed object type can be {base station, cell, link, other}, or when the value of the management domain type is "NFV-MANO", the value range of the managed object type can be {NS, VNF, VNFC, VR, Other}, where NS represents a network service, VNF represents a virtual network function, VNFC represents a virtual network function component, VR represents a virtual resource, and Other represents another managed object type. The value of the parameter targetObjectID can describe the policy application object instance identifier. When the targetType is Specific, the parameter targetObjectID is a required parameter. The default value can be all managed objects of the current management domain. In this example, the name of all managed objects and their meanings should be uniformly planned by the network operator according to the actual production network. For example, the device number in the uniform resource management system (which can be obtained according to a geographical area, a professional area, a machine room identifier, a device type, a device identifier, and the like, or a combination thereof) can be used.

[0109] The value of the parameter expectations can describe the policy application expected index, which can include, but is not limited to, a function, a performance, an availability, and the like.

[0110] Table 5.1

[0111]

[0112]

[0113] The information element State describes the specific state of the policy from triggering to execution. In the context of ECA policy expression, event, condition and action, as three examples of state, can be respectively expressed by the common parameters of this information element. Table 5.2 shows the exemplary description information of the parameters included in the information element State in this example. The value of the parameter stateType can describe the type of the policy state; the value of the parameter taskItem can describe the information of each task contained in the current state; the value of the parameter taskSelectionLogic can describe the selection logic based on the current context for selecting one task from the state to complete the state transition when the state contains more than one task; and the value of the parameter nextState can describe the identifier of the next state.

[0114] Table 5.2

[0115]

[0116] The information element Task expresses the specific information of each task that needs to be executed by the policy engine in the policy state. In the context of ECA policy expression, multiple event sub-items under event, multiple condition sub-items under condition and multiple action sub-items under action can be respectively expressed by the parameters of this information element. Table 5.3 shows the exemplary description information of the parameters included in the information element Task in this example. The value of the parameter taskType can describe the type of the task; the value of the parameter taskInput can describe the input parameter of the task. When taskType = EventTask, taskInput is used to describe the policy triggering event, i.e., various types of alarms, hints, reports and other events that can be collected / feedback / received by the NFV-MANO component; the value of the parameter taskLogic can describe the calculation logic based on the context for obtaining the output taskOutput from the input taskInput of the task; and the value of the parameter taskOutput can describe the output result of the task. When taskType = ActionTask, taskOutput is used to describe the policy execution action.

[0117] Table 5.3

[0118]

[0119] The information element Logic is used to support the description of various types of processing logic. Table 5.4 shows exemplary description information of parameters included in the information element Logic in this example. As shown in Table 5.4, the value of the parameter logicName can describe the logic function; the value of the parameter logicDsl can describe the domain-specific language of the logic, for example, Shell, Python, Java, etc.; and the value of the parameter logicCode can describe the logic code implemented using the programming language of the specified type of logicDsl.

[0120] Table 5.4

[0121]

[0122] The information element ContextMap is used to support the input and output context description of various types of policy / state / task. Table 5.5 shows exemplary description information of parameters included in the information element ContextMap in this example. As shown in Table 5.5, the value of the parameter mapName can describe the function of the context set (map); and the value of the parameter contextItem can describe the specific context variable (information element Context) contained.

[0123] Table 5.5

[0124]

[0125] Table 5.6 shows exemplary description information of parameters included in the information element Context in this example. As shown in Table 5.6, the value of the parameter contextName can describe the function of the context element (context); the value of the parameter contextAccess can describe the access address of the context; and the value of the parameter contextPara can describe the access parameters of the context, for example, a sequence of KVP key-value pairs required, where the key is the parameter name and the value is the access input parameter of the context.

[0126] Table 5.6

[0127]

[0128]

[0129] As shown in Table 5.6, the value of the parameter contextName can describe the function of the context element (context); the value of the parameter contextAccess can describe the access address of the context; and the value of the parameter contextPara can describe the access parameters of the context, for example, a sequence of KVP key-value pairs required, where the key is the parameter name and the value is the access input parameter of the context. Figure 2 As shown in Table 5.6, the value of the parameter contextName can describe the function of the context element (context); the value of the parameter contextAccess can describe the access address of the context; and the value of the parameter contextPara can describe the access parameters of the context, for example, a sequence of KVP key-value pairs required, where the key is the parameter name and the value is the access input parameter of the context.

[0130] Figure 3 The relationship of each information element in the NFV-MANO automatic scaling strategy of the embodiment of the present application is shown in the following figure: Figure 3 As shown in the figure, the Context and Logic information elements in the common model are used to realize the combination of the general information model and the domain information model in this example. Specifically, the Context is used for modeling the execution context of the policy modeling common model, and the Logic is used for the policy execution engine to parse the execution policy task. Each management domain can directly use the Context information element to define the specific instance of the domain interaction context and use the Logic information element to define the specific logic instance of the domain policy task using the domain-specific language.

[0131] The values of the parameters of each information element are described below in Tables 6.1 to 6.11.

[0132] Please refer to Figure 3 Table 6.1 shows the specific values of the parameters in the information element Policy of this example. As shown in Table 6.1, the value of the parameter firstState is EventState, which can specifically use the information element State shown in Table 5.2. The specific values of the information element EventState can be referred to Table 6.2. The value of the parameter nextState in the information element EventState is ConditionState, which can also use the information element State shown in Table 5.2. The specific values of the information element ConditionState can be referred to Table 6.3. The value of the parameter nextState in the information element ConditionState is ActionState, which can also use the information element State shown in Table 5.2. The specific values of the information element ActionState can be referred to Table 6.4. The value of the parameter nextState in the information element ActionState is NULL (empty).

[0133] Table 6.1

[0134] Attributes (parameters / attributes) Value (value) policyFunctionDescription auto_scale policyFlavour ECA targetObjectType VNF targetObjectID NULL targetDomainType NFV-MANO firstState EventState globalContext vnfindicator.utilization localContext NULL policySource Zhangsan policyVersion 1.0.0 targetDomainType NFV-MANO targetDomainID CMCC-Beijing-Fengtai-DC1 Expectations {UtilityExpectationLogic}

[0135] Table 6.2 shows the specific values of the parameters in the information element EventState of this example. Please refer to Figure 3 and Table 6.2, the information element EventState can refer to the information element EventTask through the parameter taskItem, and the information element EventTask can specifically use the information element Task shown in Table 5.3. The specific values can be referred to Table 6.5.

[0136] Table 6.2

[0137]

[0138]

[0139] Table 6.3 shows the specific values ​​of each parameter in the ConditionState information element of this example. (Refer to...) Figure 3 As shown in Table 6.3, the information element ConditionState can reference the information element ConditionTask through the parameter taskItem. The specific information element ConditionTask can be the information element Task shown in Table 5.3, and the specific values ​​can be found in Table 6.6.

[0140] Table 6.3

[0141] Attributes Value stateType Condition taskItem ConditionTask taskSelectionLogic NULL stateFinalizerLogic NULL nextState ActionState

[0142] Table 6.4 shows the specific values ​​of each parameter in the ActionState information element of this example. (Refer to...) Figure 3 As shown in Table 6.4, the information element ActionState can reference the information element ActionTask through the parameter taskItem. The information element ActionTask can specifically use the information element Task shown in Table 5.3, and the specific values ​​can be found in Table 6.7.

[0143] Table 6.4

[0144] Attributes Value stateType Action taskItem ActionTask taskSelectionLogic NULL stateFinalizerLogic NULL nextState NULL

[0145] Table 6.5 shows the specific values ​​of each parameter in the EventTask information element of this example. (Refer to...) Figure 3 As shown in Table 6.5, the information element EventTask can reference a specific domain instance model vnfIndicator.utilization provided in the domain information model through the parameter taskInput. This domain instance model vnfIndicator.utilization can specifically use the information element ContextMap shown in Table 5.5.

[0146] Table 6.5

[0147] Attributes Value taskType EventTask taskInput vnfIndicator.utilization taskLogic NULL taskOutput NextState

[0148] Table 6.6 shows the specific values ​​of each parameter in the ConditionTask information element of this example. (Refer to...) Figure 3And Table 6.6, the information element ConditionTask can refer to the specific domain instance model ConditionLogic provided in the domain information model by the parameter taskLogic, which can specifically adopt the information element Logic shown in Table 5.4, and the specific value can refer to Table 6.8.

[0149] Table 6.6

[0150] Attributes Value taskType ConditionTask taskInput NULL taskLogic ConditionLogic taskOutput NextState

[0151] Table 6.7 is the specific value of each parameter in the information element ActionTask of the present example, which can refer to Figure 3 And Table 6.7, the information element ActionTask can refer to the specific domain instance model ScaleContextMap provided in the domain information model by the parameter taskOutput, which can specifically adopt the information element ContextMap shown in Table 5.5, and the specific value can refer to Table 6.9.

[0152] Table 6.7

[0153] Attributes Value taskType ActionTask taskInput NULL taskLogic NULL taskOutput ScaleContextMap

[0154] Table 6.8 is the specific value of each parameter in the information element ConditionLogic of the present example, which can refer to Figure 3 And Table 6.8, the parameter logicCode in the information element ConditionLogic takes the value "(utilization_vnf_indicator>=60)and call_proc_scale_level<3)", that is, the scaling condition in the present example.

[0155] Table 6.8

[0156]

[0157] Table 6.9 is the specific value of each parameter in the information element ScaleContextMap of the present example, which can refer to Figure 3 And Table 6.9, the information element ScaleContextMap refers to the domain instance model ScaleContext in the domain information model by the parameter contextItem, which can specifically adopt the information element Context shown in Table 5.6, and the specific value can refer to Table 6.10.

[0158] Table 6.9

[0159] Attributes Value ​ ​ ​ ​

[0160] Table 6.10 shows the specific values of the parameters in the information element ScaleContext of the present example, refer to Table 6.10, the value of the parameter contextAccess in the information element ScaleContext is “Vnflcm.scale”, and the value of the parameter contextPara is “type: scale_out; aspect: call_proc; number_of_steps: 1”. ​

[0161] Table 6.10

[0162]

[0163] Refer to Table 6.1, the information element Policy can refer to the field instance model UtilityExpectationLogic in the field information model by the parameter Expectations, and the field instance model UtilityExpectationLogic can adopt the information element Logic shown in Table 5.4. Table 6.11 shows the specific values of the parameters in the information element UtilityExpectationLogic, as shown in Table 6.11, the value of the parameter logicCode is “vnfindicator.utilization<=60%”, that is, the expected goal of guaranteeing that the VNF utilization efficiency in the machine room is less than 60%.

[0164] Table 6.11

[0165] ​ ​ ​ ​ ​ "vnfindicator.utilization <= 60%"

[0166] In the present example, the intent about the policy can be delivered into the corresponding policy through the expected effect field model (as shown in Table 6.11), to provide reference indexes for subsequent monitoring and evaluating the applicability, feasibility and effectiveness of the policy application.

[0167] ​It is noted that intent management provides a simplified way for the operation support system / business support system (OSS / BSS) to use the NFV-MANO service, only specifying the NFV-related requirements and constraints without understanding how the NFV-MANO performs the operations converted from the NFV intent. For example, an intent owner (e.g., OSS / BSS) requests to update an existing intent, which contains the expectation to update the performance of a network service (NS) instance, e.g., increase / decrease the incoming data rate of a specific service access point (SAP). Based on the intent expectation, the intent handler converts the updated intent into corresponding policies, and finally performs the corresponding NS operations (e.g., scaling up the existing NS) through the policies to meet the intent requirements.

[0168] According to the modeling way of intent, the specific expression about (function, performance, available indicator set and its combination, etc.) can be constructed through the expectation of the general intent model. In the intent management system, the above-mentioned expectations about function, performance, available indicator set and its combination, etc. will finally be converted into specific information element definitions, code implementations, service interfaces of all expected performance evaluations (function, performance, available indicator set and its combination, etc.) that can be executed with certainty. Taking the expectation to update the performance of the NS instance as an example, the expected performance in this example is to keep the usage efficiency of the VNF within a fixed threshold, which will finally be converted into specific information element definitions and code implementations, such as UtilityExpectationLogic shown in Table 6.11.

[0169] Based on the NFV-MANO policy information model shown in Tables 5.1 to 5.6, by defining the above-mentioned intent expectation, the corresponding imperative policy description model can be extended (i.e., updating the description part in the general information model included in the policy instance), as shown in Table 6.1, adding the indicator Expectations about expected performance, which can refer to the defined domain information model UtilityExpectation corresponding to the intent expectation.

[0170] In this example, after the execution of the intent-based policy, the execution effect needs to be continuously guaranteed and optimized. At this time, the reference index for evaluating the feasibility of the policy application can be provided according to the extended performance index (Utility Expectation) about the expected effect. For example, the domain information model of the Utility Expectation referring to the Utility Expectation defined in the intent can be based on the model, the code implementation of the Utility Expectation Logic corresponding to the model is used as the reference index of the related performance index, and the difference between the actual effect after the execution of the policy and the reference index is analyzed to further guarantee and optimize the execution effect of the policy.

[0171] In this example, the policy modeling method based on model combination is used to plan and manage the respective planning and management of the common model (i.e., the general information model) of the public elements of the policy modeling and the domain-specific modeling field model (i.e., the domain information model) related to the interaction with the context environment of the policy operation, so as to realize the unified modeling and flexible on-demand extension of the policy. In the common model, the existing imperative policy description model is extended based on the intent, and the policy modeling extension for the target (management domain), the policy application range (managed object), and the expected effect (effect index) is added. On the one hand, the background knowledge required for the policy management systematization and the identification and elimination of potential policy conflicts can be provided, and on the other hand, the reference index required for the monitoring and evaluation of the applicability, feasibility, and effectiveness of the policy application for the dynamic automatic iteration and self-adaptive evolution of the policy management can be provided. In this example, the formal description, registration, and interaction mechanism of the distributed policy modeling elements (for example, trigger event, action execution, and condition evaluation) can be provided to provide the reference index required for the applicability and feasibility evaluation of the policy application for the dynamic automatic iteration and self-adaptive evolution of the policy management.

[0172] The embodiment of the present application also provides an information processing device. ​ The schematic diagram of the composition structure of the information processing device of the embodiment of the present application is shown in ​ As shown in the figure, the information processing device 20 includes an execution module 21, which is configured to parse a policy instance and / or execute the policy instance based on a general information model and a domain information model for policy management. The general information model is used to describe the common features of the policies in different domains and / or different levels, and the domain information model is used to describe the information related to the running environment and / or interaction of the policies in each domain.

[0173] In an optional embodiment of the present application, the general information model includes at least one of intent information, basic information, instruction element information, target range information, and expected effect information.

[0174] In an optional embodiment of the present application, the intent information comprises at least one of the following: target domain information representing a domain of policy application; object scope information representing a managed object of policy application; expected effect information representing an expected result of policy execution.

[0175] In an optional embodiment of the present application, the base information comprises at least one of the following information related to policy lifecycle management: policy name, policy type, policy source, version information.

[0176] In an optional embodiment of the present application, the instruction element information comprises one or more logical units describing policy execution related.

[0177] In an optional embodiment of the present application, the target scope information comprises one or more domains and / or managed objects describing policy application scope.

[0178] In an optional embodiment of the present application, the expected effect information comprises one or more metrics describing policy application result.

[0179] In an optional embodiment of the present application, the domain information model comprises at least one of the following: a domain information model corresponding to each domain and related to instruction element information; a domain information model corresponding to each domain and related to expected effect information; a domain information model corresponding to each domain and related to target scope information.

[0180] In an optional embodiment of the present application, the domain information model related to instruction element information is used to provide information element definition related to policy execution.

[0181] In an optional embodiment of the present application, the domain information model related to expected effect information is used to provide information element definition related to policy application result evaluation.

[0182] In an optional embodiment of the present application, the domain information model related to target scope information is used to provide information element definition related to policy application scope.

[0183] In an optional embodiment of the present application, the execution module 21 is configured to determine a domain model instance according to the domain information model, and update a description part of a general information model contained in the policy instance; the domain model instance is used to provide context environment and / or context interaction information of the policy instance running; the policy instance is parsed and / or executed based on the updated general information model and the domain model instance.

[0184] In an optional embodiment of the present application, the execution module 21 is configured to acquire an intention of the policy; and add corresponding intention information in the description part of the general information model based on the intention, the intention information including at least one of target domain information representing a domain to which the policy is applied, object range information representing an object to which the policy is applied, and expected effect information representing an expected effect of the policy execution.

[0185] In an optional embodiment of the present application, the execution module 21 is configured to parse an information element related to at least one of instruction element information, target range information and expected effect information included in a corresponding policy instance based on the general information model; and parse a parameter value of the information element included in the corresponding policy instance based on the domain information model.

[0186] In an optional embodiment of the present application, the information element related to the instruction element information includes at least one of state information for describing a state of the policy from triggering to execution, task information for describing a task to be executed by the policy engine in each state, and logic information for describing processing logic of the policy execution engine in executing the task.

[0187] In an optional embodiment of the present application, the information element related to the instruction element information included in the domain information model further includes at least one of context information for describing input and output context of each policy element, state element or task element, and context set information for describing each context element.

[0188] In an optional embodiment of the present application, the execution module 21 is configured to update the description part based on the intention, the updated description part including at least one of a parameter for describing a type of the domain to which the policy is applied, a parameter for describing an identity of the domain to which the policy is applied, a parameter for describing a type of the object to which the policy is applied, a parameter for describing an identity of the object to which the policy is applied, and a parameter for describing the expected effect of the policy execution.

[0189] In an optional embodiment of the present application, the domain model instance includes a first model instance corresponding to the context element and / or a second model instance corresponding to the logic element; the execution module 21 is configured to determine a parameter of the context element by referencing the first model instance and / or determine a parameter of the logic element by referencing the second model instance; and parse the policy instance and / or execute the policy instance based on the parameter of the context element and / or the parameter of the logic element.

[0190] In an alternative embodiment of the present application, the device further comprises an acquisition module for acquiring respective capability information of all domains, the capability information being used to determine the domain information model; the capability information comprises at least one of the following: information element definition, code implementation and service interface corresponding to instruction element information of each domain; information element definition, code implementation and service interface corresponding to expected effectiveness information of each domain; information element definition, code implementation and service interface corresponding to target range information of each domain.

[0191] In the embodiments of the present application, the execution module 21 in the information processing device 20 can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a field-programmable gate array (FPGA) in actual application.

[0192] It should be noted that the information processing device provided in the above embodiments is only taken as an example for the division of the above program modules when performing information processing, and in actual application, the above processing can be completed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-described processing. In addition, the information processing device and the information processing method provided in the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be described here.

[0193] The embodiments of the present application further provide a computer device. ​ A structural schematic diagram of the computer device of the embodiments of the present application is shown in FIG. 3. ​ As shown in FIG. 3, the computer device 30 comprises at least one processor 31, a memory 32 and at least one network interface 33. Each component in the computer device 30 is coupled together through a bus system 34. It can be understood that the bus system 34 is used to realize the connection and communication between the components. The bus system 34 comprises a data bus, a power supply bus, a control bus and a state signal bus. However, for the purpose of clear illustration, all kinds of buses are marked as the bus system 34 in FIG. 3. ​

[0194] ​It can be appreciated that the memory 32 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a ferromagnetic random access memory (FRAM), a Flash Memory, a magnetic surface memory, an optical disc, or a Compact Disc Read-Only Memory (CD-ROM). The magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a Random Access Memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM can be used, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 32 described in the embodiments of the present application is intended to include, but not limited to, these and any other suitable type of memory.

[0195] The memory 32 in the embodiments of the present application is used to store various types of data to support the operation of the computer device 30. Examples of these data include any computer program for operating on the computer device 30, such as the program of the information processing method of the embodiments of the present application, etc.

[0196] The method disclosed in the embodiments of the present application can be applied in or implemented by the processor 31. The processor 31 can be an integrated circuit chip having the processing capability of signals. In the implementation process, each step of the above method can be completed by the integrated logic circuit of hardware in the processor 31 or the instruction in the form of software. The above processor 31 can be a general-purpose processor, DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The processor 31 can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the above can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium, which is located in the memory 32. The processor 31 reads the information in the memory 32 and combines the hardware to complete the steps of the above method.

[0197] In the exemplary embodiments, the computer device 30 can be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors (Microprocessors), or other electronic elements, for executing the above method.

[0198] In the example embodiment, the embodiment of the present application also provides a computer readable storage medium, such as the memory 32 including a computer program executable by the processor 31 of the computer device 30 to complete the steps of the foregoing method. The computer readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; or various devices including one or any combination of the above memories, such as mobile phones, computers, tablet devices, personal digital assistants, and the like.

[0199] The methods disclosed in the several method embodiments provided by the present application can be combined arbitrarily without conflict to obtain new method embodiments.

[0200] The features disclosed in the several product embodiments provided by the present application can be combined arbitrarily without conflict to obtain new product embodiments.

[0201] The features disclosed in the several method or device embodiments provided by the present application can be combined arbitrarily without conflict to obtain new method embodiments or device embodiments.

[0202] In the several embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the various components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0203] The units described above as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0204] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0205] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware, and the foregoing program can be stored in a computer readable storage medium, and the program performs the steps of the above-mentioned method embodiments when executed; and the foregoing storage medium includes a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disc or an optical disc, and various media capable of storing program codes.

[0206] Alternatively, the integrated unit of the present application can be stored in a computer readable storage medium if it is realized in the form of a software function module and sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes a mobile storage device, a ROM, a RAM, a magnetic disc or an optical disc, and various media capable of storing program codes.

[0207] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An information processing method characterized by comprising: The method comprises: resolving and / or executing a policy instance based on a common information model and a domain information model for policy management, wherein the common information model is used to describe common features of policies in different domains and / or different levels, and the domain information model is used to describe information related to policy running environment and / or interaction of each domain; wherein the resolving and / or executing the policy instance based on the common information model and the domain information model comprises: determining a domain model instance according to the domain information model, and updating a description part of the common information model contained in the policy instance; the domain model instance is used to provide context environment and / or context interaction information for running of the policy instance; resolving and / or executing the policy instance based on the updated common information model and the domain model instance; wherein the resolving and / or executing the policy instance based on the updated common information model and the domain model instance comprises: resolving information elements related to at least one of instruction element information, target range information and expected effectiveness information contained in the corresponding policy instance based on the common information model; resolving parameter values of the information elements contained in the corresponding policy instance based on the domain model instance.

2. The method of claim 1, wherein, The common information model comprises at least one of intention information, basic information, instruction element information, target range information and expected effectiveness information.

3. The method of claim 2, wherein, The intention information comprises at least one of: target domain information representing a domain to which the policy is applied; object range information representing a managed object to which the policy is applied; expected effectiveness information representing an expected effectiveness of policy execution.

4. The method of claim 2, wherein, The basic information comprises at least one of the following information related to policy lifecycle management: policy name, policy type, policy source, version information.

5. The method of claim 2, wherein, The instruction element information comprises one or more logical units describing policy execution.

6. The method of claim 2, wherein, The target range information comprises one or more domains and / or managed objects describing policy application range.

7. The method of claim 2, wherein, The expected effectiveness information comprises one or more metric indicators describing policy application effectiveness.

8. The method of claim 1, wherein, The domain information model comprises at least one of: a domain information model corresponding to each domain and related to instruction element information; a domain information model corresponding to each domain and related to expected effectiveness information; a domain information model corresponding to each domain and related to target range information.

9. The method of claim 8, wherein, The domain information model related to instruction element information is used to provide definition of information elements related to policy execution.

10. The method of claim 8, wherein, The domain information model related to expected effectiveness information is used to provide definition of information elements related to policy application effectiveness evaluation.

11. The method of claim 8, wherein, The domain information model related to target range information is used to provide definition of information elements related to policy application range.

12. The method of claim 11, wherein, The updating the description part of the common information model contained in the policy instance comprises: obtaining intention of the policy; adding corresponding intent information in a description part of the common information model based on the intent, the intent information including at least one of the following: target domain information representing a domain to which a policy is applied, object scope information representing a managed object to which the policy is applied, and expected effect information representing an expected result of policy execution.

13. The method of claim 1, wherein, The information elements related to the instruction element information include at least one of the following: a state element for describing state information of a policy from triggering to execution; a task element for describing information of each task to be executed by a policy engine in each state of the policy; a logic element for describing processing logic of the policy execution engine for executing each task.

14. The method of claim 13, wherein, The information elements related to the instruction element information included in the domain information model further include at least one of the following: a context element for describing input and output contexts of each policy element, state element or task element; a context set element for describing each context element.

15. The method of claim 12, wherein, The adding of the corresponding intent information in the description part of the common information model based on the intent includes: updating the description part based on the intent, the updated description part including at least one of the following: a parameter for describing a type of a domain to which a policy is applied; a parameter for describing an identity of the domain to which the policy is applied; a parameter for describing a type of a managed object to which the policy is applied; a parameter for describing an identity of the managed object to which the policy is applied; a parameter for describing an expected result of policy execution.

16. The method of claim 14, wherein, The domain model instance includes a first model instance corresponding to the context element and / or a second model instance corresponding to the logic element; and the parsing of the policy instance and / or the execution policy instance based on the updated common information model and the domain model instance includes: determining parameters of the context element by referencing the first model instance, and / or determining parameters of the logic element by referencing the second model instance; parsing the policy instance and / or the execution policy instance based on the parameters of the context element and / or the parameters of the logic element.

17. The method of claim 8, wherein, The method further includes: obtaining respective capability information of all domains, the capability information being used to determine the domain information model, the capability information including at least one of the following: information element definitions, code implementations and service interfaces corresponding to the instruction element information of each domain; information element definitions, code implementations and service interfaces corresponding to the expected effect information of each domain; information element definitions, code implementations and service interfaces corresponding to the target scope information of each domain.

18. An information processing apparatus comprising: The apparatus includes an execution module for parsing a policy instance and / or an execution policy instance based on a common information model for policy management and a domain information model, wherein the common information model is used to describe common features of policies in different domains and / or at different levels, and the domain information model is used to describe information related to a policy running environment and / or interaction of each domain; wherein the parsing of the policy instance and / or the execution policy instance based on the common information model for policy management and the domain information model includes: determining a domain model instance according to the domain information model, and updating a description part of a common information model contained in the policy instance; the domain model instance is used to provide a context environment and / or context interaction information for running of the policy instance; analyzing and / or executing the policy instance based on the updated common information model and the domain model instance; wherein the analyzing and / or executing the policy instance based on the updated common information model and the domain model instance comprises: analyzing information elements related to at least one of instruction element information, target range information and expected effectiveness information contained in the corresponding policy instance based on the common information model; analyzing parameter values of the information elements contained in the corresponding policy instance based on the domain model instance.

19. A computer readable storage medium having stored thereon a computer program, characterized in that, The program, when executed by a processor, implements the steps of the method of any one of claims 1 to 17.

20. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, The processor, when executing the program, implements the steps of the method of any one of claims 1 to 17.

Images