CN113703988B - Capability arrangement method, device, equipment and medium - Google Patents
Capability arrangement method, device, equipment and medium Download PDFInfo
- Publication number
- CN113703988B CN113703988B CN202010433517.5A CN202010433517A CN113703988B CN 113703988 B CN113703988 B CN 113703988B CN 202010433517 A CN202010433517 A CN 202010433517A CN 113703988 B CN113703988 B CN 113703988B
- Authority
- CN
- China
- Prior art keywords
- capability
- capacity
- target
- called
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000004590 computer program Methods 0.000 claims description 8
- 238000005516 engineering process Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 5
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 10
- 238000005538 encapsulation Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention provides a capability arrangement method, device, equipment and medium. The method comprises the following steps: acquiring a capability call request of the application equipment, wherein the capability call request comprises a target capability parameter and a target capability relation chain parameter; attributing the target capacity parameters to the corresponding capacities, and determining a target capacity relation chain matched with the target capacity relation chain parameters in at least one preset capacity relation chain; acquiring target capability information according to a target capability relation chain, and determining whether the capability to be called exists currently or not according to the target capability information; when the capability to be called exists currently, the capability to be called is called according to the capability parameter corresponding to the capability to be called, calling result information of the capability to be called is obtained, the capability to be called is updated to be called, and whether the capability to be called exists currently or not is determined according to the target capability information. Thus, the flexibility and the applicability of the capacity arrangement to complex business scenes with dependency relationships can be improved.
Description
Technical Field
The present invention relates to the field of capability arrangement technologies, and in particular, to a capability arrangement method, device, apparatus, and medium.
Background
At present, some internet enterprises continuously open various internet universal capabilities to the outside. For users using capabilities, each type of internet generic capability can implement its specific function, but it is sometimes desirable to implement multiple capabilities in one capability request, for example, if a sms capability call fails, then a voice notification capability is initiated for retransmission. However, for various general-purpose capability of the internet, the function types and the call flows are different, and unified management is difficult. In the face of the aforementioned demand scenario, new capability flows often need to be re-developed.
In order to solve the above-mentioned requirement scene, gradually produced the technical scheme of "ability arrangement". However, the current capability arrangement technical scheme only provides multi-node arrangement management of single capability for specific capability in the bottom network element, but cannot solve the function of multi-capability 'merge arrangement', and has too simple processing of capability relationship, and is difficult to realize for complex business scenes with dependency relationship among multiple capabilities.
Disclosure of Invention
The embodiment of the invention provides a capability arrangement method, device, equipment and medium, which can improve the flexibility and applicability of capability arrangement for complex service scenes with dependency relationships.
In a first aspect, an embodiment of the present invention provides a capability orchestration method, where the method includes: acquiring a capability call request of the application equipment, wherein the capability call request comprises a target capability parameter and a target capability relation chain parameter; attributing the target capacity parameters to the corresponding capacities, and determining a target capacity relation chain matched with the target capacity relation chain parameters in at least one preset capacity relation chain; acquiring target capability information according to a target capability relation chain, and determining whether the capability to be called exists currently or not according to the target capability information; when the capability to be called exists currently, the capability to be called is called according to the capability parameter corresponding to the capability to be called, calling result information of the capability to be called is obtained, the capability to be called is updated to be called, and whether the capability to be called exists currently or not is determined according to the target capability information.
In some implementations of the first aspect, determining a target capability relationship chain in at least one preset capability relationship chain that matches the target capability relationship chain parameters includes: determining a capability relation chain mark according to the target capability relation chain parameter; a target capability relationship chain matching the capability relationship chain label is determined in at least one preset capability relationship chain.
In some implementations of the first aspect, obtaining the target capability information according to the target capability relationship chain includes: and acquiring target capacity information according to the tangent plane technology and the target capacity relation chain.
In some implementations of the first aspect, the target capability information includes: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities.
In some implementations of the first aspect, before returning to determining whether there is currently a capability to be invoked according to the target capability information, the method further includes: and respectively determining the metering result, the charging result and the statistical result of the capability to be called according to the metering information, the charging information and the statistical information of the capability to be called in the calling result information and the target capability information, and displaying the metering result, the charging result and the statistical result.
In some implementations of the first aspect, when there is currently no capability to be invoked, the method further includes: and sending all the obtained call result information to the application equipment.
In some implementations of the first aspect, before obtaining the capability call request of the application device, the method further includes: acquiring at least two binary relations, wherein the binary relations are obtained by selecting a first capability, selecting a second capability after the first capability, and adding a called logic relation between the first capability and the second capability; according to at least two binary relations, adding a called logic relation between each binary relation to generate a capability relation chain; and carrying out de-duplication on the common capacity parameters of the capacities in the capacity relation chain, reserving the de-duplicated common capacity parameters and the proprietary capacity parameters of each capacity to obtain a parameter encapsulation body, determining a preset capacity relation chain according to the de-duplicated capacity relation chain, wherein the parameter encapsulation body corresponds to the preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request of the application equipment.
In a second aspect, an embodiment of the present invention provides a capability orchestration device, including: the acquisition module is used for acquiring a capability call request of the application equipment, wherein the capability call request comprises a target capability parameter and a target capability relation chain parameter; the attribution module is used for attributing the target capacity parameters to the corresponding capacities and determining a target capacity relation chain matched with the target capacity relation chain parameters in at least one preset capacity relation chain; the determining module is used for acquiring target capability information according to the target capability relation chain and determining whether the capability to be called exists currently or not according to the target capability information; and the calling module is used for calling the capacity to be called according to the capacity parameter corresponding to the capacity to be called when the capacity to be called exists currently, obtaining calling result information of the capacity to be called, updating the capacity to be called into the called capacity, and returning to determine whether the capacity to be called exists currently according to the target capacity information.
In some implementations of the second aspect, the attribution module is specifically configured to: determining a capability relation chain mark according to the target capability relation chain parameter; a target capability relationship chain matching the capability relationship chain label is determined in at least one preset capability relationship chain.
In some implementations of the second aspect, the determining module is specifically configured to: and acquiring target capacity information according to the tangent plane technology and the target capacity relation chain.
In some implementations of the second aspect, the target capability information includes: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities.
In some implementations of the second aspect, the apparatus further includes: and the display module is used for respectively determining the metering result, the charging result and the statistical result of the capability to be called according to the metering information, the charging information and the statistical information of the capability to be called in the calling result information and the target capability information before returning to determine whether the capability to be called exists currently according to the target capability information, and displaying the metering result, the charging result and the statistical result.
In some implementations of the second aspect, the apparatus further includes: and the sending module is used for sending all the obtained calling result information to the application equipment when the capability to be called does not exist currently.
In some implementations of the second aspect, the apparatus further includes: the generating module is used for acquiring at least two binary relations before acquiring a capacity calling request of the application equipment, wherein the binary relations are obtained by selecting a first capacity, selecting a second capacity after the first capacity and adding a called logic relation between the first capacity and the second capacity; according to at least two binary relations, adding a called logic relation between each binary relation to generate a capability relation chain; and carrying out de-duplication on the common capacity parameters of the capacities in the capacity relation chain, reserving the de-duplicated common capacity parameters and the proprietary capacity parameters of each capacity to obtain a parameter encapsulation body, determining a preset capacity relation chain according to the de-duplicated capacity relation chain, wherein the parameter encapsulation body corresponds to the preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request of the application equipment.
In a third aspect, an embodiment of the present invention provides a capability orchestration device, the device comprising: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the capability orchestration method described in the first aspect or any of the realizations of the first aspect.
In a fourth aspect, embodiments of the present invention provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the capability orchestration method according to the first aspect or any of the realizations of the first aspect.
According to the capacity scheduling method, device, equipment and medium provided by the embodiment of the invention, the target capacity parameter in the capacity calling request can be attributed to the corresponding capacity, namely the capacity parameter owned by each capacity is determined, the corresponding target capacity relation chain is determined according to the target capacity relation chain parameter in the capacity calling request, then the target capacity information is acquired according to the target capacity relation chain, whether the capacity to be called exists or not is determined according to the target capacity information, namely whether the capacity to be called can be called currently is judged, the influence of the logic relation of calling among the capacities is introduced, if the capacity to be called exists, the capacity to be called can be called according to the capacity parameter owned by the capacity to be called, the calling result information of the capacity to be called is obtained, and the calling step is repeated in order to call the capacity to be called in the preset capacity relation chain, so that the flexibility and the applicability of the capacity scheduling for complex service scene with the dependency relation can be improved, and the capacity scheduling for the complex service scene can be realized.
Drawings
In order to more clearly illustrate the technical solution of the embodiments of the present invention, the drawings that are needed to be used in the embodiments of the present invention will be briefly described, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a capacity orchestration method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a basic capability relationship chain provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram of a complex capability relationship chain according to an embodiment of the present invention;
FIG. 4 is a flow chart of another capacity orchestration method according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a capability orchestration device according to an embodiment of the present invention;
fig. 6 is a schematic hardware structure of a capability orchestration device according to an embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely configured to illustrate the invention and are not configured to limit the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the invention by showing examples of the invention.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
At present, in the current capability arrangement mode, capability arrangement is relatively simple, stays in a processing mode of multi-capability execution respectively, is difficult to realize for a general scene with a dependency relationship (such as short message-voice in the background technology) among the multi-capability, has no scene requirement related to the dependency relationship among the capabilities, has a smaller application range in reality, and has low application value.
Aiming at the problem, the embodiment of the invention provides a capacity scheduling method, a device, equipment and a medium, which can attribute the target capacity parameter in the capacity calling request to the corresponding capacity, namely, determine the capacity parameter owned by each capacity, determine the corresponding target capacity relation chain according to the target capacity relation chain parameter in the capacity calling request, acquire the target capacity information according to the target capacity relation chain, determine whether the capacity to be called exists according to the target capacity information, namely, judge whether the capacity to be called exists currently or not, introduce the influence of the calling logical relation between the capacities, call the capacity to be called according to the capacity parameter owned by the capacity to be called, obtain the calling result information of the capacity to be called, and repeat the calling step for calling the capacity to be called in the preset capacity relation chain, so that the flexibility and the applicability of the capacity scheduling for complex service scene with the dependency relation can be improved, and the capacity scheduling for the complex service scene can be realized.
Alternatively, in the embodiment of the present invention, the capability orchestration method may be applied to a capability orchestration system, and the capability orchestration method provided by the embodiment of the present invention is described below with reference to the accompanying drawings:
fig. 1 is a flow chart of a capability orchestration method according to an embodiment of the present invention, as shown in fig. 1, the capability orchestration method 100 may include S110 to S140.
S110, acquiring a capability call request of the application device.
Alternatively, in one embodiment, the capability invocation request from the application device may be obtained through a capability interface. The application device may be a device used by an application party that invokes the capability, such as an application server, an application terminal, or the like. The capability call request may include a target capability parameter and a target capability relationship chain parameter.
And S120, attributing the target capacity parameter to the corresponding capacity, and determining a target capacity relation chain matched with the target capacity relation chain parameter in at least one preset capacity relation chain.
Alternatively, in one embodiment, the target capability parameter may be differentiated and checked, and the target capability parameter is assigned to the corresponding capability, that is, the parameter assigned to the different capability is divided from the corresponding capability. In addition, a capability relationship chain label can be determined according to the target capability relationship chain parameter, and a target capability relationship chain matched with the capability relationship chain label can be determined in at least one preset capability relationship chain.
The preset capability relation chain may be a predetermined capability relation chain, the capability relation chain may be used to represent a logical relationship invoked between at least two capabilities, and the logical relationship may be generally regarded as a dependency relationship. It can be appreciated that in the conventional capability arrangement, there is only one relationship "combination relationship" between capabilities, that is, multiple capability executions are invoked at the same time. The capabilities in the combination relationship are not related to each other, and can be considered that no dependency relationship exists, and the execution results of the respective capabilities do not affect the calling of other capabilities. While the capability relationship chain herein may introduce the influence of a dependency.
As one example, a capability relationship chain has a basis and a complex score, and as shown in FIG. 2, a capability relationship chain of a basis may be "relational and" or "relational not". The "relationship and", "relationship or" relationship not "is a basic relationship obtained by diverging the dependency relationship between the capabilities, and represents a logical relationship called between the capabilities. In the relation AND, the solid line is used for representing the logic relation, and whether the capability A is successfully called or not is judged, and the capability B is called immediately afterwards; in the "relationship or", the logical relationship is represented by a dotted line, and only if the capability A is successfully called, the capability B is called; in the relation NOT, the logical relation is represented by a sigh and a dotted line, and the capability B is called only when the capability A fails to be called. For example, for the service scenario of "call voice notification notify again when short message notification fails", this may be implemented by "relationship not".
For more complex service scenes, the method can be realized by expanding basic relations to obtain complex capability relation chains. Taking the complex capability relationship chain shown in fig. 3 as an example, in the capability relationship chain 1, only the capability a is successfully invoked to invoke the capability B, and the relationship between C, D is executed no matter whether the relationship between A, B is successful or not, that is, only the capability C is successfully invoked to invoke the capability D; in the capability relationship chain 2, the capability B is invoked no matter whether the capability a is successfully invoked, and the relationship C, D is executed only if both of the relationships A, B are successfully invoked, i.e., the capability D is invoked no matter whether the capability C is successfully invoked or not after the capability C is invoked. Therefore, based on the basic relation, a more complex and flexible capability relation chain can be expanded to cope with complex and changeable application scenes in reality.
S130, acquiring target capability information according to the target capability relation chain, and determining whether the capability to be called exists currently or not according to the target capability information.
Optionally, in one embodiment, no additional development is generated during capacity orchestration in order to achieve matching between common functions such as metering, billing, and statistics and differentiated capabilities. Target capability information can be obtained according to a tangent plane technique and a target capability relation chain. The target capability information may include: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities. It can be appreciated that metering information, billing information, and statistics for each capability are preset.
As an example, the target capability relationship chain may be monitored, parameters may be injected or obtained, custom operations may be performed, and so on, by a tangent plane technique. Optionally, before determining the capability to be invoked, performing data monitoring and data transmission of the capability invocation through a tangent plane technology, thereby obtaining target capability information, and storing the target capability information into a dialogue data field (session) corresponding to the capability invocation request. The target capability information may be used to determine whether to meter, charge, etc. the service management functions according to the target capability information after the capability calling class performs calling. Meanwhile, whether the capability to be invoked exists currently or not can be judged according to the target capability information in the dialogue data domain.
And S140, when the capability to be called exists currently, calling the capability to be called according to the capability parameter corresponding to the capability to be called, obtaining calling result information of the capability to be called, updating the capability to be called, and returning to determine whether the capability to be called exists currently according to the target capability information.
Optionally, in an embodiment, the capability to be invoked may be invoked according to a capability parameter corresponding to the capability to be invoked, and the invoking process may include: parameter verification, parameter configuration, calling execution and the like, and calling data of the capacity to be called can be obtained after the calling. The call data can be analyzed, and the analysis processing can comprise two parts of capability self analysis mapping and unified analysis mapping. Specifically, the capability self-parsing mapping can process specific response parameters aiming at the capability, the unified parsing mapping is parsed into public response parameters, whether the call is successful or not is determined according to the common response parameters, and the parsing result and the call success or failure are regarded as call result information of the capability to be called. Optionally, for some to-be-invoked capabilities that respond to the business result immediately, the invocation result information may also include the amount of successful invocation. The call result information may then be stored into the dialog data field.
At the same time, the capability to be invoked may be updated to be invoked, i.e., the capability is not invoked any more, and then a determination is returned as to whether there is currently a capability to be invoked according to the target capability information, in other words, whether there is a next capability to be invoked may be determined by combining the target capability information and the invoked capability. Until all calls requiring calling capability in the relation chain are completed.
According to the capacity scheduling method, the target capacity parameters in the capacity calling request can be attributed to the corresponding capacities, namely the capacity parameters of each capacity can be determined, the corresponding target capacity relation chain is determined according to the target capacity relation chain parameters in the capacity calling request, then the target capacity information is acquired according to the target capacity relation chain, whether the capacity to be called exists or not is determined according to the target capacity information, namely whether the capacity to be called currently is judged, the influence of the logic relation of calling among the capacities is introduced, if the capacity to be called exists, the capacity to be called can be called according to the capacity parameters of the capacity to be called, calling result information of the capacity to be called is obtained, and in order to call the capacity to be called in the preset capacity relation chain, the calling step is repeated, so that the flexibility and the applicability of the capacity scheduling for complex service scenes with dependency relations can be improved, and the capacity scheduling for complex service scenes can be realized.
In one embodiment, in order to make capacity scheduling more flexible, capacity scheduling efficiency is improved. Before acquiring the capability call request of the application device, the method may further include the steps of:
first, at least two binary relations may be obtained, wherein the binary relations may be obtained by selecting a first capability, selecting a second capability after the first capability, and adding a called logical relation between the first capability and the second capability. The logical relationship is herein referred to as "relationship and" or "relationship not". A capability relationship chain may then be generated from the at least two binary relationships, with a calling logical relationship being added between each binary relationship.
And secondly, the common capacity parameters of the capacities in the capacity relation chain can be de-duplicated, and the common capacity parameters after de-duplication and the proprietary capacity parameters of each capacity are reserved to obtain the parameter package. In other words, the capability parameters of different capabilities are converged and managed, the capability parameters of a plurality of capabilities related to the capability relation chain are selected, the capability parameters of repeated fields are deduplicated, and when an application party invokes the relation chain, a unified parameter package which is unambiguous relative to code logic can be provided, namely, specific service parameters of different capabilities are ensured to have unique service fields, and common parameter fields are provided for the same service parameters.
And thirdly, a preset capability relation chain can be determined according to the capability relation chain after the duplication removal, specifically, public functions such as metering, charging, statistics and the like of each capability related in the capability relation chain after the duplication removal can be set, for example, "capability calling of each link in the relation chain is respectively metered, charged and counted", and "the capability calling of each link in the relation chain is metered once, charged once and counted once only when the relation chain completes a complete execution flow" can be set, so that metering information, charging information and statistical information of each capability are generated for subsequent use. Alternatively, the setting of the common function may be based on one capability in the relationship chain, or one binary relationship, or the entire chain of capability relationships. And then determining the set capacity relation chain as a preset capacity relation chain and storing the preset capacity relation chain.
The parameter encapsulation body corresponds to a preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request by the application equipment. Alternatively, the target capability parameters in the capability request may be adapted by the parameter encapsulation and grouped accordingly. And when different capabilities are called each time later, acquiring the capability parameters of the specific capability group in the parameter package to perform parameter configuration so as to realize capability calling.
When a new relation chain is obtained through capacity arrangement, an operator does not need to change an externally provided interface code or change parameter limitation, and the calling can be realized only by adding the capacity parameter corresponding to the capacity by an application side.
In order to notify the application of the capability call result and facilitate management of operators, another implementation of the capability orchestration method is provided in the embodiment of the present invention, and as shown in fig. 4, the capability orchestration method 200 may include S210 to S270.
S210, acquiring a capability call request of the application device.
S220, attributing the target capacity parameter to the corresponding capacity, and determining a target capacity relation chain matched with the target capacity relation chain parameter in at least one preset capacity relation chain.
S230, acquiring target capability information according to the target capability relation chain.
S240, determining whether the capability to be called exists currently according to the target capability information. If so, S250 is performed, and if not, S270 is performed.
S250, calling the capacity to be called according to the capacity parameter corresponding to the capacity to be called, obtaining calling result information of the capacity to be called, and updating the capacity to be called into the called capacity.
S260, determining the metering result, the charging result and the statistics result of the capability to be called according to the metering information, the charging information and the statistics information of the capability to be called in the calling result information and the target capability information respectively, and displaying the metering result, the charging result and the statistics result. Returning to S240, the corresponding operation is repeated.
Optionally, in an embodiment, according to success or failure of call in the call result information in the dialogue data domain and metering information, charging information and statistics information of the capability to be called in the target capability information in the dialogue data domain, whether to meter and how to meter, whether to count and how to count and other public functions can be respectively determined, so as to obtain a metering result, a charging result and a statistics result of the capability to be called, and store the metering result, the charging result and the statistics result in the dialogue data domain, further visualize the metering result, the charging result and the statistics result, display the metering result, the charging result and the to an operator, and facilitate management of the operator.
S270, all the obtained call result information is sent to the application equipment.
Optionally, in an embodiment, each piece of capability calling result information may be configured into a response parameter string in a unified format according to the capability calling result information in the dialogue data domain, and the application device is returned according to a return mode agreed by the application party at the operator, that is, a mode of selecting synchronous response or asynchronous receipt, so as to notify the application party.
It will be appreciated that S210 to S230 are identical to S110 to S130 in the above-described embodiments and will not be described in detail herein for the sake of brevity.
Based on the capability orchestration method according to the embodiment of the present invention, the embodiment of the present invention further provides a capability orchestration device, where the capability orchestration device may be applied to a capability orchestration system, as shown in fig. 5, and the capability orchestration device 300 may include: the device comprises an acquisition module 310, a attribution module 320, a determination module 330 and a calling module 340.
The acquiring module 310 is configured to acquire a capability call request of the application device, where the capability call request includes a target capability parameter and a target capability relationship chain parameter. The attribution module 320 is configured to attribute the target capability parameter to a corresponding capability, and determine a target capability relationship chain that matches the target capability relationship chain parameter in at least one preset capability relationship chain. The determining module 330 is configured to obtain the target capability information according to the target capability relation chain, and determine whether there is a capability to be invoked currently according to the target capability information. And the calling module 340 is configured to, when the capability to be called currently exists, call the capability to be called according to a capability parameter corresponding to the capability to be called, obtain calling result information of the capability to be called, update the capability to be called, and return to determining whether the capability to be called currently exists according to the target capability information.
In one embodiment, the attribution module 320 is specifically configured to: and determining a capability relation chain mark according to the target capability relation chain parameter, and determining a target capability relation chain matched with the capability relation chain mark in at least one preset capability relation chain.
In one embodiment, the determining module 330 is specifically configured to: and acquiring target capacity information according to the tangent plane technology and the target capacity relation chain.
In one embodiment, the target capability information includes: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities.
In one embodiment, the apparatus 300 further comprises: the display module 340 is configured to determine, before returning to determine whether the capability to be invoked currently exists according to the target capability information, a measurement result, a charging result, and a statistics result of the capability to be invoked according to the measurement information, the charging information, and the statistics information of the capability to be invoked in the invocation result information and the target capability information, and display the measurement result, the charging result, and the statistics result.
In one embodiment, the apparatus 300 further comprises: and the sending module 350 is configured to send all the obtained call result information to the application device when the capability to be invoked does not currently exist.
In one embodiment, the apparatus 300 further comprises: the generating module 360 is configured to obtain at least two binary relations before obtaining the capability call request of the application device, where the binary relations are obtained by selecting a first capability, selecting a second capability after the first capability, and adding a called logical relation between the first capability and the second capability. And adding a called logical relationship between each binary relationship according to at least two binary relationships to generate a capability relationship chain. And carrying out de-duplication on the common capacity parameters of the capacities in the capacity relation chain, reserving the de-duplicated common capacity parameters and the proprietary capacity parameters of each capacity to obtain a parameter package, and determining a preset capacity relation chain according to the de-duplicated capacity relation chain. The parameter encapsulation body corresponds to a preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request by the application equipment.
It is to be understood that the capability orchestration device 300 according to the embodiment of the present invention may correspond to the execution body of the capability orchestration method in fig. 1 according to the embodiment of the present invention, and specific details of operations and/or functions of each module/unit of the capability orchestration device 300 may be referred to the description of corresponding parts in the capability orchestration method in fig. 1 according to the embodiment of the present invention, which is not repeated herein for brevity.
Fig. 6 is a schematic hardware structure of a capability orchestration device according to an embodiment of the present invention.
As shown in fig. 6, the capacity orchestration device 400 in the present embodiment includes an input device 401, an input interface 402, a central processor 403, a memory 404, an output interface 405, and an output device 406. The input interface 402, the central processor 403, the memory 404, and the output interface 405 are connected to each other through the bus 410, and the input device 401 and the output device 406 are connected to the bus 410 through the input interface 402 and the output interface 405, respectively, and further connected to other components of the capability arrangement device 400.
Specifically, the input device 401 receives input information from the outside, and transmits the input information to the central processor 403 through the input interface 402; the central processor 403 processes the input information based on computer executable instructions stored in the memory 404 to generate output information, temporarily or permanently stores the output information in the memory 404, and then transmits the output information to the output device 406 through the output interface 405; the output device 406 outputs the output information to the outside of the capacity orchestration device 400 for use by the user.
In one embodiment, the capacity orchestration device 400 shown in fig. 6 comprises: a memory 404 for storing a program; processor 403 is configured to execute a program stored in the memory to perform the capability orchestration method provided by the embodiment shown in fig. 1.
Embodiments of the present invention also provide a computer readable storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement the capability orchestration method provided by the embodiment shown in fig. 1.
It should be clear that, all embodiments in this specification are described in a progressive manner, and the same or similar parts of all embodiments are referred to each other, so that for brevity, no further description is provided. The present invention is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after appreciating the spirit of the present invention.
The functional blocks shown in the above-described structural block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor Memory devices, read-Only Memory (ROM), flash Memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.
It should also be noted that the exemplary embodiments mentioned in this disclosure describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in a different order from the order in the embodiments, or several steps may be performed simultaneously.
In the foregoing, only the specific embodiments of the present invention are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present invention is not limited thereto, and any equivalent modifications or substitutions can be easily made by those skilled in the art within the technical scope of the present invention, and they should be included in the scope of the present invention.
Claims (14)
1. A method of capacity orchestration, the method comprising:
acquiring a capability call request of an application device, wherein the capability call request comprises a target capability parameter and a target capability relation chain parameter;
attributing the target capacity parameters to corresponding capacities, and determining a target capacity relation chain matched with the target capacity relation chain parameters in at least one preset capacity relation chain, wherein the preset capacity relation chain is a preset capacity relation chain and is used for representing a called logic relation between two capacities;
acquiring target capability information according to the target capability relation chain, and determining whether the capability to be called exists currently or not according to the target capability information;
when the capability to be called currently exists, calling the capability to be called according to a capability parameter corresponding to the capability to be called to obtain calling result information of the capability to be called, updating the capability to be called into the called capability, and returning to the step of determining whether the capability to be called currently exists according to the target capability information;
the obtaining the target capability information according to the target capability relation chain includes:
and acquiring the target capacity information according to a tangent plane technology and the target capacity relation chain.
2. The method of claim 1, wherein said determining a target capability relationship chain in at least one preset capability relationship chain that matches the target capability relationship chain parameter comprises:
determining a capability relationship chain mark according to the target capability relationship chain parameter;
determining the target capability relation chain matched with the capability relation chain mark in the at least one preset capability relation chain.
3. The method of claim 1, wherein the target capability information comprises: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities.
4. A method according to claim 3, wherein before returning the determination of whether there is currently a capability to be invoked based on the target capability information, the method further comprises:
and respectively determining a metering result, a charging result and a statistics result of the capability to be called according to metering information, charging information and statistics information of the capability to be called in the calling result information and the target capability information, and displaying the metering result, the charging result and the statistics result.
5. The method of claim 1, wherein when the capability to be invoked is not currently present, the method further comprises:
and sending all the obtained call result information to the application equipment.
6. The method of claim 1, wherein prior to obtaining the capability call request of the application device, the method further comprises:
acquiring at least two binary relations, wherein the binary relations are obtained by selecting a first capability, selecting a second capability after the first capability and adding a called logic relation between the first capability and the second capability;
according to the at least two binary relations, adding a called logic relation between each binary relation to generate a capacity relation chain;
and carrying out de-duplication on the common capacity parameters of the capacities in the capacity relation chain, reserving the de-duplicated common capacity parameters and the proprietary capacity parameters of each capacity to obtain a parameter package, determining a preset capacity relation chain according to the de-duplicated capacity relation chain, wherein the parameter package corresponds to the preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request by application equipment.
7. A capacity orchestration device, the device comprising:
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a capability calling request of the application equipment, and the capability calling request comprises a target capability parameter and a target capability relation chain parameter;
the attribution module is used for attributing the target capacity parameter to the corresponding capacity, determining a target capacity relation chain matched with the target capacity relation chain parameter in at least one preset capacity relation chain, wherein the preset capacity relation chain is a preset capacity relation chain, and the capacity relation chain is used for representing a logic relation called between two capacities;
the determining module is used for acquiring target capacity information according to the target capacity relation chain and determining whether the capacity to be called exists currently or not according to the target capacity information;
the calling module is used for calling the capability to be called according to the capability parameter corresponding to the capability to be called when the capability to be called exists currently, obtaining calling result information of the capability to be called, updating the capability to be called into the called capability, and returning the fact that whether the capability to be called exists currently or not is determined according to the target capability information;
the determining module is specifically configured to:
and acquiring the target capacity information according to a tangent plane technology and the target capacity relation chain.
8. The apparatus of claim 7, wherein the attribution module is specifically configured to:
determining a capability relationship chain mark according to the target capability relationship chain parameter;
determining the target capability relation chain matched with the capability relation chain mark in the at least one preset capability relation chain.
9. The apparatus of claim 7, wherein the target capability information comprises: the target capability relationship chain includes at least two capabilities, a logical relationship invoked between the at least two capabilities, metering information, billing information, and statistics for each of the at least two capabilities.
10. The apparatus of claim 7, wherein the apparatus further comprises:
and the display module is used for respectively determining the metering result, the charging result and the statistical result of the capability to be called according to the metering information, the charging information and the statistical information of the capability to be called in the calling result information and the target capability information before returning the capability to be called currently determined according to the target capability information, and displaying the metering result, the charging result and the statistical result.
11. The apparatus of claim 7, wherein the apparatus further comprises:
and the sending module is used for sending all the obtained calling result information to the application equipment when the capability to be called does not exist currently.
12. The apparatus of claim 7, wherein the apparatus further comprises:
the generating module is used for acquiring at least two binary relations before acquiring a capability calling request of the application device, wherein the binary relations are obtained by selecting a first capability, selecting a second capability after the first capability and adding a calling logic relation between the first capability and the second capability;
according to the at least two binary relations, adding a called logic relation between each binary relation to generate a capacity relation chain;
and carrying out de-duplication on the common capacity parameters of the capacities in the capacity relation chain, reserving the de-duplicated common capacity parameters and the proprietary capacity parameters of each capacity to obtain a parameter package, determining a preset capacity relation chain according to the de-duplicated capacity relation chain, wherein the parameter package corresponds to the preset capacity relation chain and is used for determining target capacity parameters in a capacity calling request by application equipment.
13. A capacity orchestration device, the device comprising: a processor and a memory storing computer program instructions;
the processor, when executing the computer program instructions, implements the capability orchestration method according to any one of claims 1-6.
14. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon computer program instructions, which when executed by a processor, implement the capability orchestration method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010433517.5A CN113703988B (en) | 2020-05-21 | 2020-05-21 | Capability arrangement method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010433517.5A CN113703988B (en) | 2020-05-21 | 2020-05-21 | Capability arrangement method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113703988A CN113703988A (en) | 2021-11-26 |
| CN113703988B true CN113703988B (en) | 2024-01-19 |
Family
ID=78645532
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010433517.5A Active CN113703988B (en) | 2020-05-21 | 2020-05-21 | Capability arrangement method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113703988B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483831A (en) * | 2008-12-30 | 2009-07-15 | ***通信集团北京有限公司 | Method, system and apparatus for value-added service capability of Internet service |
| WO2018059150A1 (en) * | 2016-09-28 | 2018-04-05 | 中兴通讯股份有限公司 | Open capability implementation method and apparatus |
| CN109885475A (en) * | 2018-12-14 | 2019-06-14 | 平安壹钱包电子商务有限公司 | Page conversion ratio calculation method, device, computer equipment and storage medium |
| WO2020010887A1 (en) * | 2018-07-09 | 2020-01-16 | 中兴通讯股份有限公司 | Network deployment method and apparatus |
| CN110730220A (en) * | 2019-09-26 | 2020-01-24 | 深圳市保臻社区服务科技有限公司 | Intelligent scheduling method and device based on system current business capability integration |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8019713B2 (en) * | 2005-07-08 | 2011-09-13 | Honda Motor Co., Ltd. | Commonsense reasoning about task instructions |
| CN101094223B (en) * | 2006-06-23 | 2010-12-08 | 国际商业机器公司 | Metod and device for distributing policy in service model facing to service system structural system |
| US8528043B2 (en) * | 2011-12-06 | 2013-09-03 | Sap Ag | Systems and methods for generating trust federation data from BPMN choreography |
| US20140006520A1 (en) * | 2012-06-28 | 2014-01-02 | Sap Ag | Consistent Interface for Customer - Message Set 1 |
| WO2020008301A1 (en) * | 2018-07-05 | 2020-01-09 | Open Text Sa Ulc | Systems and methods for communication flow modeling |
-
2020
- 2020-05-21 CN CN202010433517.5A patent/CN113703988B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483831A (en) * | 2008-12-30 | 2009-07-15 | ***通信集团北京有限公司 | Method, system and apparatus for value-added service capability of Internet service |
| WO2018059150A1 (en) * | 2016-09-28 | 2018-04-05 | 中兴通讯股份有限公司 | Open capability implementation method and apparatus |
| WO2020010887A1 (en) * | 2018-07-09 | 2020-01-16 | 中兴通讯股份有限公司 | Network deployment method and apparatus |
| CN110708178A (en) * | 2018-07-09 | 2020-01-17 | 中兴通讯股份有限公司 | Network deployment method and device |
| CN109885475A (en) * | 2018-12-14 | 2019-06-14 | 平安壹钱包电子商务有限公司 | Page conversion ratio calculation method, device, computer equipment and storage medium |
| CN110730220A (en) * | 2019-09-26 | 2020-01-24 | 深圳市保臻社区服务科技有限公司 | Intelligent scheduling method and device based on system current business capability integration |
Non-Patent Citations (2)
| Title |
|---|
| "基于微服务的精细化业务流程编排***";虞果;《中国优秀硕士学位论文全文数据库信息科技辑》;全文 * |
| Towards a framework for detecting containment violations in service choreography;Faiz UL Muram;《IEEE》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113703988A (en) | 2021-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111163129B (en) | Resource processing method and device based on cross-link network | |
| CN106375458B (en) | Service calling system, method and device | |
| CN111262726B (en) | Configuration information updating method and device and computer readable storage medium | |
| CN111274252A (en) | Block chain data chaining method, device, storage medium and server | |
| CN111782524B (en) | Application testing method and device, storage medium and electronic device | |
| CN103716356A (en) | Storage process operation method, device and system based on Web | |
| CN114785685A (en) | Software differential upgrading method and device, electronic equipment and readable storage medium | |
| US20170085673A1 (en) | Attribute Operating Method and Apparatus | |
| CN113691635A (en) | Method and device for calling micro service, electronic equipment and readable storage medium | |
| CN117176802B (en) | Full-link monitoring method and device for service request, electronic equipment and medium | |
| CN113703988B (en) | Capability arrangement method, device, equipment and medium | |
| CN115361295B (en) | TOPSIS-based resource backup method, device, equipment and medium | |
| CN109389271B (en) | Application performance management method and system | |
| CN114071448B (en) | Data transmission method, related network node and storage medium | |
| CN113342353B (en) | Mock data generation method and device | |
| CN111324645A (en) | Data processing method and device for block chain | |
| CN109412813A (en) | The endorsement method of elliptic curve, sign test method and apparatus | |
| CN112988339B (en) | Data management method and device | |
| CN114866970A (en) | Policy control method, system and related equipment | |
| CN114221883A (en) | Message testing method, device, server and storage medium | |
| CN109993406B (en) | Information processing method and device | |
| CN113822701A (en) | Cloud platform third-party resource computing method, device, equipment and readable medium | |
| CN117313856B (en) | Reliability test planning system and method | |
| CN110059125B (en) | Method for invoking proxy contract and related equipment | |
| CN112748931B (en) | Compiled file management method, calling method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |