A method, apparatus and device for aggregating atomic capability interfaces based on a pipe model

Abstract

The application discloses a kind of based on pipeline model atomic ability interface aggregation method, device and equipment, method includes: receiving the atomic ability aggregation request of visual design interface, obtains the model parameter configured by design interface, and constructs pipeline data model according to model parameter;Wherein, pipeline data model includes multiple serial processing step units, each described step unit contains multiple parallel call request basic subunit, each described call request basic subunit and each atomic ability interface are one-to-one mapping relationship, and each step unit uses path parameter mapping mode to make the processing result of last step unit become the input parameter of each call request basic subunit in next step unit.The aggregation mode of atomic ability is simplified in the application, aggregated ability interface is quickly formed, software development efficiency is improved, code complexity is reduced, without customizing aggregation implementation code, and the number of servers is reduced.

Description

Technical Field

[0001] This invention belongs to the field of software system interface open technology, specifically relating to a method, apparatus and device for aggregating atomic capability interfaces based on a pipeline model. Background Technology

[0002] As microservice architecture becomes the mainstream for large-scale software systems, the breakdown of functions within microservice architecture is becoming increasingly granular, such as the increasingly detailed open interfaces for backend services. To achieve concise frontend logic and fewer calls to third-party services, quickly combining multiple atomic capability interfaces into a unified aggregate capability interface has become an effective solution.

[0003] In existing technologies, rapid aggregation of atomic capability interfaces is typically achieved by adding a middleware service or by using routing configuration functionality based on a microservice gateway. The middleware service approach involves re-encapsulating asynchronous services based on capability exposure requirements or using a process engine orchestration to uniformly call the actual atomic capability interfaces to achieve capability aggregation. The microservice gateway routing configuration approach uses routing forwarding to uniformly call business atomic capability interfaces to achieve aggregation. While both middleware services and gateway routing can aggregate various atomic capabilities and generate new open capabilities, middleware services require an additional service layer, and each aggregation interface needs customized development based on actual needs. This increases the workload of glue code connecting the front-end and back-end. Furthermore, process engine orchestration results in low performance and low processing efficiency for aggregation and combination calls, requiring additional scheduling time. Gateway routing requires modification of some business call logic, and due to the different implementation languages ​​and architectures of various gateways and their high implementation complexity, significant time and effort are required to learn the source code and then perform secondary development to implement the business call logic, increasing the complexity of building capability aggregation functionality. Summary of the Invention

[0004] The purpose of this invention is to provide an atomic capability interface aggregation method, apparatus, and device based on a pipeline model, in order to solve the technical problems of large workload and complex operation in existing atomic capability interface aggregation methods.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] The first aspect provides a pipeline-based method for aggregating atomic capability interfaces, including:

[0007] Receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface according to the atomic capability aggregation requests, and construct a pipeline data model according to the model parameters;

[0008] The pipeline data model is a mapping of the aggregation capability interface, including multiple serial processing step units. Each step unit contains multiple parallel call request basic sub-units. Each call request basic sub-unit has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameters of each call request basic sub-unit in the next step unit.

[0009] In one possible design, an atomic capability aggregation request is received from a visual design interface; model parameters configured through the design interface are obtained based on the atomic capability aggregation request; and a pipeline data model is constructed based on the model parameters, including:

[0010] Receive atomic capability aggregation requests from the visualization capability configuration interface, and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests;

[0011] Receive basic data configured by the visualization capability configuration interface, extract atomic capability interface data from the basic data, and instantiate a corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data.

[0012] Obtain the pre-processing conditions of the atomic capability interface, and instantiate the pre-processor corresponding to the basic sub-unit object of each call request based on the pre-processing conditions;

[0013] Obtain the configuration order of each atomic capability interface, and instantiate a step unit object for each sequential step according to the configuration order;

[0014] Obtain the post-processing conditions for each step unit, and instantiate and generate the post-processor for each step unit based on the post-processing conditions.

[0015] Obtain the response requirements of the aggregation capability interface, and instantiate and generate the response processor of the pipeline data model based on the response requirements.

[0016] In one possible design, path parameter mapping is used between the step units so that the processing result of the previous step unit becomes the input parameter of each basic sub-unit of the call request in the next step unit, including:

[0017] The parameter values ​​between each step unit use fixed values, reference values, and / or wildcard data types to define the data conversion mapping between the processing result of the previous step unit and the input parameters of each call request basic sub-unit in the next step unit;

[0018] When a parameter is configured with multiple data types, the parameter values ​​are overwritten according to the priority order of fixed value < reference value < wildcard.

[0019] In one possible design, after constructing the pipeline data model based on the model parameters, the method further includes:

[0020] The pipelined data model is serialized to generate JSON text, and the JSON text is stored in a text database.

[0021] In one possible design, after storing the JSON text in a text database, the method further includes:

[0022] The pipeline data model in JSON format is reviewed, and after approval, it is published to the message queue of the runtime service cache so that the aggregation capability interface can subscribe to the message queue at runtime.

[0023] In one possible design, after the pipelined data model is published to the message queue of the runtime service cache upon approval, the method further includes:

[0024] Receive the call request for the aggregation capability interface, and obtain the configuration data of the pipeline data model according to the call request;

[0025] The context environment for the call is constructed based on the configuration data, and the aggregated capability interface is processed using reactive streaming technology to return the response result according to the preset configuration rules.

[0026] In one possible design, the system receives calls to the aggregation capability interface and retrieves configuration data for the pipelined data model based on the calls, including:

[0027] Receive the call request of the aggregation capability interface, encapsulate the call request into a data stream, and distribute the data stream to the corresponding pipeline data model;

[0028] Retrieve configuration data for the pipelined data model from the message queue.

[0029] In one possible design, the context of the call is constructed based on the configuration data, and reactive streaming technology is used to process the aggregated capability interface to return a response result based on preset configuration rules, including:

[0030] Based on the data transformation mapping relationship in the configuration data, extract the actual parameter execution result of the previous step unit in the context environment, and set the actual parameter execution result in the input parameter of the basic sub-unit object of the call request of the next step unit;

[0031] The actual parameter data is processed and manipulated through the methods of the class object of the pipeline data model, and the response results are output and returned through the reactive listener method.

[0032] The second aspect provides an atomic capability interface aggregation device based on a pipeline model, comprising:

[0033] The model building module is used to receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface according to the atomic capability aggregation requests, and build a pipeline data model according to the model parameters.

[0034] The pipeline data model is a mapping of the aggregation capability interface, including multiple serial processing step units. Each step unit contains multiple parallel call request basic sub-units. Each call request basic sub-unit has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameters of each call request basic sub-unit in the next step unit.

[0035] In one possible design, the model building module includes:

[0036] The framework building unit is used to receive atomic capability aggregation requests from the visual capability configuration interface and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests.

[0037] The first object generation unit is used to receive the basic data configured by the visual capability configuration interface, extract atomic capability interface data from the basic data, and instantiate and generate a corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data.

[0038] The first processor generation unit is used to obtain the pre-processing conditions of the atomic capability interface and instantiate and generate the pre-processor corresponding to each basic sub-unit object of the call request based on the pre-processing conditions.

[0039] The second object generation unit is used to obtain the configuration order of each atomic capability interface and instantiate and generate step unit objects for each sequential step according to the configuration order.

[0040] The second processor generation unit is used to obtain the post-processing conditions of each step unit and instantiate and generate the post-processor of each step unit according to the post-processing conditions.

[0041] The third processor generation unit is used to obtain the response result requirements of the aggregation capability interface and instantiate and generate the response processor of the pipeline data model according to the response result requirements.

[0042] In one possible design, when a path parameter mapping method is used between each step unit so that the processing result of the previous step unit becomes the input parameter of each basic sub-unit of the call request in the next step unit, the model building module is specifically used for:

[0043] The parameter values ​​between each step unit use fixed values, reference values, and / or wildcard data types to define the data conversion mapping between the processing result of the previous step unit and the input parameters of each call request basic sub-unit in the next step unit;

[0044] When a parameter is configured with multiple data types, the parameter values ​​are overwritten according to the priority order of fixed value < reference value < wildcard.

[0045] In one possible design, the device further includes:

[0046] A storage module is used to serialize the pipelined data model to generate JSON text and store the JSON text in a text database.

[0047] In one possible design, the device further includes:

[0048] The publishing module is used to review pipelined data models in JSON format and publish them to the message queue of the runtime service cache after approval, so that the aggregation capability interface can subscribe to the message queue at runtime.

[0049] In one possible design, the device further includes:

[0050] The call response module is used to receive call requests from the aggregation capability interface and obtain the configuration data of the pipeline data model based on the call request.

[0051] The result return module is used to construct the context environment for the call based on the configuration data, and to process the aggregated capability interface using reactive streaming technology to return the response result of the preset configuration rules.

[0052] In one possible design, when receiving a call request to the aggregation capability interface and retrieving configuration data for the pipelined data model based on the call request, the call response module is specifically used for:

[0053] Receive the call request of the aggregation capability interface, encapsulate the call request into a data stream, and distribute the data stream to the corresponding pipeline data model;

[0054] Retrieve configuration data for the pipelined data model from the message queue.

[0055] In one possible design, when constructing the call context based on configuration data and using reactive streaming technology to process the aggregated capability interface to return a response result based on preset configuration rules, the result return module is specifically used for:

[0056] Based on the data transformation mapping relationship in the configuration data, extract the actual parameter execution result of the previous step unit in the context environment, and set the actual parameter execution result in the input parameter of the basic sub-unit object of the call request of the next step unit;

[0057] The actual parameter data is processed and manipulated through the methods of the class object of the pipeline data model, and the response results are output and returned through the reactive listener method.

[0058] A third aspect provides a computer device comprising a memory, a processor, and a transceiver connected in sequence, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the pipeline-based atomic capability interface aggregation method as described in any possible design of the first aspect.

[0059] The fourth aspect provides a computer-readable storage medium storing instructions that, when executed on a computer, perform the atomic capability interface aggregation method based on a pipeline model as described in any possible design of the first aspect.

[0060] The fifth aspect provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the atomic capability interface aggregation method based on a pipeline model as described in any possible design of the first aspect.

[0061] The advantages of this invention compared to the prior art are as follows:

[0062] This invention receives atomic capability aggregation requests from a visual design interface and constructs a pipeline-like data model based on the configuration parameters of the atomic capability interfaces. The pipeline-like data model maps the aggregated capability interfaces and includes multiple serially processed step units. Each step unit contains multiple parallel call request basic sub-units, and each call request basic sub-unit has a one-to-one mapping relationship with each atomic capability interface. Path parameter mapping is used between step units so that the processing result of the previous step unit becomes the input parameter for each call request basic sub-unit in the next step unit. By constructing the pipeline-like data model, multiple atomic capability interfaces are aggregated in parallel and serially into a new capability interface, i.e., the pipeline-like data model. The pipeline-like data model is a linear model, simplifying the aggregation of atomic capabilities, quickly forming aggregated capability interfaces, and improving software development efficiency. Therefore, it eliminates the need for additional intermediate service aggregation layers and service gateways, reducing code complexity, eliminating the need for customized aggregation implementation code, and reducing the number of servers. Attached Figure Description

[0063] Figure 1This is a flowchart of the atomic capability interface aggregation method based on the pipeline model in the embodiments of this application;

[0064] Figure 2 This is an interactive principle diagram of the atomic capability interface aggregation method based on the pipeline model in the embodiments of this application;

[0065] Figure 3 This is a schematic diagram of the pipeline data model in the embodiments of this application;

[0066] Figure 4 This is an execution flowchart of the preprocessor of the basic subunit of the call request in this application embodiment;

[0067] Figure 5 This is a publish-subscribe flowchart of the pipeline data model in this application embodiment;

[0068] Figure 6 A schematic diagram illustrating the method for processing the aggregation capability interface of the responsive streaming technology in this application embodiment. Detailed Implementation

[0069] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in conjunction with the accompanying drawings and descriptions of the embodiments or the prior art. Obviously, the following description of the structure of the accompanying drawings is only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. It should be noted that the description of these embodiments is for the purpose of helping to understand the present invention, but does not constitute a limitation of the present invention.

[0070] Example

[0071] To address the issues in existing technologies where intermediate services require an additional service layer, each aggregation interface needs customized development based on actual needs, leading to increased workload in glue code connecting the front-end and back-end, low performance of aggregation calls during process engine orchestration, and additional scheduling time, this application provides a pipeline-based atomic capability interface aggregation method. This method aggregates multiple atomic capability interfaces into a new capability interface in parallel and serially through the construction of a pipeline data model. The pipeline data model is a linear model, simplifying the aggregation of atomic capabilities, quickly forming aggregated capability interfaces, improving software development efficiency, eliminating the need for additional intermediate service aggregation layers and service gateways, reducing code complexity, eliminating the need for customized aggregation implementation code, and reducing the number of servers.

[0072] The atomic capability interface aggregation method based on the pipeline model provided in this application will be described in detail below.

[0073] It should be noted that the embodiments of this application are mainly applied to the field of open access to telecommunications cloud network resources, realizing a technical method that satisfies the need for open access to communication services while enabling the rapid, efficient, simple, and secure aggregation of atomic capabilities into new capabilities. The data model of a telecommunications cloud network resource system primarily abstracts physical and virtual resources in various communication and computing networks into object models such as points, lines, and surfaces. In the operation of communication services, a large amount of communication and computing resources need to be scheduled according to the characteristics of different voice, data, cloud, and networking services to complete service activation. This scheduling characteristic results in a large number of atomic capability interfaces. In actual production operation, tools or platforms are needed to quickly support the activation of new services, reduce the complexity of service activation in complex scenarios, and reduce the number of capability calls.

[0074] It should be noted that the atomic capability interface aggregation method based on the pipeline model provided in this application can be applied to any terminal device using an operating system. The operating system includes, but is not limited to, Windows, Mac, Linux, Chrome OS, UNIX, iOS, and Android systems, etc., and is not limited here. The terminal device includes, but is not limited to, iPads, personal mobile computers, industrial computers, and personal computers, etc., and is not limited here. For ease of description, unless otherwise specified, this application uses a personal computer as the execution subject in its embodiments. It is understood that the execution subject does not constitute a limitation on the embodiments of this application; other types of terminal devices may be used as the execution subject in some other embodiments.

[0075] like Figures 1-6 The diagram shown is a flowchart of an atomic capability interface aggregation method based on a pipeline model provided in this application. The atomic capability interface aggregation method based on a pipeline model includes, but is not limited to, the method implemented by step S1:

[0076] Step S1. Receive the atomic capability aggregation request from the visual design interface, obtain the model parameters configured through the design interface according to the atomic capability aggregation request, and construct a pipeline data model according to the model parameters.

[0077] The pipeline data model is a mapping of the aggregation capability interface, including multiple serial processing step units (process). Each step unit contains multiple parallel call request basic subunits (requestinput). Each call request basic subunit has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameters of each call request basic subunit in the next step unit.

[0078] like Figure 3 As shown, in one specific embodiment of step S1, an atomic capability aggregation request is received from the visual design interface; model parameters configured through the design interface are obtained according to the atomic capability aggregation request; and a pipeline data model is constructed according to the model parameters, including:

[0079] Step S11. Receive atomic capability aggregation requests from the visualization capability configuration interface, and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests;

[0080] It should be noted that the visual design interface in this embodiment includes a visual capability configuration interface. The visual capability configuration interface is used for designers to initiate atomic capability aggregation requests. After the backend responds to the atomic capability aggregation request and generates the basic framework of the model, the designer can configure the model parameters in the visual capability configuration interface. It should be noted that at this time, the basic framework only includes empty input filter and response filter configuration parameters. After obtaining the filter configuration parameters configured by the designer in the visual configuration interface, the pre-filter of the model is instantiated and generated according to the filter configuration parameters.

[0081] Step S12. Receive the basic data configured by the visualization capability configuration interface, extract the atomic capability interface data from the basic data, and instantiate and generate the corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data.

[0082] Preferably, the atomic capability interface data includes, but is not limited to, request addresses and input / output parameters, atomic capability interface data mapping configuration, pre- and post-filtering parameters, and added and trimmed data.

[0083] Step S13. Obtain the pre-processing conditions of the atomic capability interface, and instantiate the pre-processor corresponding to each basic sub-unit object of the call request based on the pre-processing conditions;

[0084] Step S14. Obtain the configuration order of each atomic capability interface, and instantiate and generate step unit objects for each sequential step according to the configuration order;

[0085] Step S15. Obtain the post-processing conditions of each step unit, and instantiate and generate the post-processor of each step unit according to the post-processing conditions.

[0086] Step S16. Obtain the response result requirements of the aggregation capability interface, and instantiate the response processor of the pipeline data model according to the response result requirements.

[0087] like Figure 4As shown, it should be noted that the pre-processor corresponding to each basic sub-unit of the call request in this embodiment, the post-processor of each step unit, and the pre-filter and response processor of the pipeline model all have the following functions: filtering, injecting, cleaning, shaping, and other operations on the input and output of the step unit process and the basic sub-unit requestinput; and can also be used to select whether to execute conditions. After processing by the pre-processor, the data can be converted into a preset data format, thereby carrying the request data that meets the conditions in the final atomic capability interface call. For some atomic capability interfaces that need to meet specific data conditions to be called, the conditional expression in the processor can be used to determine whether to call the interface. The processor can be preset through the configuration of the design-state visual interface. When aggregating different atomic capability interfaces, only different processor rules and conditions need to be configured to complete the preset parameter structure and preset conditions for calling different atomic capability interfaces; preferably, the processor is implemented using a filter method.

[0088] In one specific implementation of step S1, a path parameter mapping method is used between each step unit so that the processing result of the previous step unit becomes the input parameter of each basic sub-unit of the call request in the next step unit, including:

[0089] The parameter values ​​between each step unit use fixed values, reference values, and / or wildcard data types to define the data conversion mapping between the processing result of the previous step unit and the input parameters of each call request basic sub-unit in the next step unit;

[0090] When a parameter is configured with multiple data types, the parameter values ​​are overwritten according to the priority order of fixed value < reference value < wildcard.

[0091] It's important to note that data transfer between processing units is the fundamental operation mode of a pipelined data model. During pipeline model construction, parameter values ​​between process objects are defined using fixed values, reference values, and / or wildcards to define the data transformation mapping between the processing result of the previous process and the input of the next process. This allows, during runtime, the corresponding actual parameters are extracted from the runtime context based on the data transformation mapping relationship and set in the input request data parameters of the next process's requestInput, thereby realizing the processing and flow of data within the pipeline model.

[0092] Fixed-type data is configured with parameter names and fixed values ​​beforehand during the pipeline model design and construction process. Parameter values ​​support character, integer, numeric, and / or date types. Fixed values ​​can be injected into parameters at the input or output of any process. Reference-type data is configured with parameter names and reference values ​​during the pipeline model design and construction process. Reference values ​​are constructed according to the format: <pipeline model object instance name> + separator (.) + <pipeline model sub-object instance name> + separator (.) + <processed result jsonpath expression>. When a parameter is configured with multiple types of values, the order is fixed value < reference value < wildcard. The data transfer format conventions are shown in the table below:

[0093]

[0094] In one specific implementation, after constructing the pipeline data model based on the model parameters, the method further includes:

[0095] Step S2. Serialize the pipelined data model to generate JSON text, and store the JSON text in a text database.

[0096] like Figure 5 As shown, in one specific implementation, after storing the JSON text in a text database, the method further includes:

[0097] The pipeline data model in JSON format is reviewed, and after approval, it is published to the message queue of the runtime service cache so that the aggregation capability interface can subscribe to the message queue at runtime.

[0098] It should be noted that the design-mode functionality also includes an approval process for aggregation capabilities. The approval method can be automatic system approval or manual approval. After approval, it is automatically published to a message queue. The runtime service of the aggregation capability interface will subscribe to this message queue. When a new version of a certain aggregation capability interface is released, the corresponding configuration data is pulled from the message queue and finally put into the local service cache for generating the context environment when actually called.

[0099] In one specific implementation, after the pipelined data model is published to the message queue of the runtime service cache upon approval, the method further includes:

[0100] Step S4. Receive the call request of the aggregation capability interface, and obtain the configuration data of the pipeline data model according to the call request;

[0101] In one possible design, the system receives calls to the aggregation capability interface and retrieves configuration data for the pipelined data model based on the calls, including:

[0102] Step S41. Receive the call request of the aggregation capability interface, encapsulate the call request into a data stream, and distribute the data stream to the corresponding pipeline data model;

[0103] Step S42. Retrieve the configuration data for the pipelined data model from the message queue.

[0104] Step S5. Construct the context environment for the call based on the configuration data, and use reactive streaming technology to process the aggregation capability interface to return the response result of the preset configuration rules.

[0105] In one possible design, the context of the call is constructed based on the configuration data, and reactive streaming technology is used to process the aggregated capability interface to return a response result based on preset configuration rules, including:

[0106] Step S51. Based on the data transformation mapping relationship in the configuration data, extract the actual parameter execution result of the previous step unit in the context environment, and set the actual parameter execution result in the input parameter of the basic sub-unit object of the call request of the next step unit;

[0107] Step S52. Process and manipulate the actual parameter data through the methods of the class object of the pipeline data model, and output the response result and return it through the reactive listener method.

[0108] like Figure 6 As shown, based on the publicly available information, when a request arrives from the aggregation capability interface, the request is encapsulated into a data stream. Through a publish-subscribe-like streaming process, instantiated class objects serve as elements in the stream. Methods within these class objects are used to process and manipulate the actual parameter data. For example, the `run()` method in the `RequestInput` instance calls the actual atomic capability, while the `beforeRun()` and `afterRun()` methods process the actual data. Within these two methods, different filter classes, such as `etlFilter()`, `injectFilter()`, and `decideFilter()`, are called to process the actual parameter data, depending on the configuration. Finally, the streaming process handles the final data result in a reactive listener method and returns it to the actual caller.

[0109] Based on the above disclosure, this application embodiment receives atomic capability aggregation requests from a visual design interface and constructs a pipeline data model according to the configuration parameters of the atomic capability interfaces. The pipeline data model is a mapping of the aggregation capability interfaces and includes multiple serial processing steps. Each step unit contains multiple parallel call request sub-units. Each call request sub-unit has a one-to-one mapping relationship with each atomic capability interface. Path parameter mapping is used between each step unit so that the processing result of the previous step unit becomes the input parameter for each call request sub-unit in the next step unit. After the pipeline data model is reviewed and published to the runtime service cache, the runtime service receives the actual aggregation capability interface call request, reads the corresponding pipeline model configuration data from the cache, constructs the call context, and uses reactive streaming technology to process the atomic capability interface call and return the result to the caller. In essence, this application's embodiments utilize a pipeline data model to aggregate multiple atomic capability interfaces in parallel and serially into a new capability interface—the pipeline data model. This linear model simplifies the aggregation of atomic capabilities, rapidly forming aggregated capability interfaces and improving software development efficiency. It eliminates the need for additional intermediate service aggregation layers and service gateways, reducing code complexity and the need for customized aggregation implementation code, thus reducing the number of servers. Furthermore, the pipeline model's operation in the cache is easily controlled, requiring no additional components such as a scheduling engine. It exhibits very high scheduling efficiency for atomic capability interfaces, fully meeting the high-concurrency, low-latency interface call requirements of telecommunications cloud network resource systems. The operation of communication services in the telecommunications field involves the scheduling and correlation of numerous resources. The pipeline model, by forming aggregated capabilities and scheduling calls to underlying atomic capability interfaces, can partially simplify the complexity of service scheduling and efficiently achieve service operation.

[0110] The second aspect provides an atomic capability interface aggregation device based on a pipeline model, comprising:

[0111] The model building module is used to receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface according to the atomic capability aggregation requests, and build a pipeline data model according to the model parameters.

[0112] The pipeline data model is a mapping of the aggregation capability interface, including multiple serial processing step units. Each step unit contains multiple parallel call request basic sub-units. Each call request basic sub-unit has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameters of each call request basic sub-unit in the next step unit.

[0113] In one possible design, the model building module includes:

[0114] The framework building unit is used to receive atomic capability aggregation requests from the visual capability configuration interface and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests.

[0115] The first object generation unit is used to receive the basic data configured by the visual capability configuration interface, extract atomic capability interface data from the basic data, and instantiate and generate a corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data.

[0116] The first processor generation unit is used to obtain the pre-processing conditions of the atomic capability interface and instantiate and generate the pre-processor corresponding to each basic sub-unit object of the call request based on the pre-processing conditions.

[0117] The second object generation unit is used to obtain the configuration order of each atomic capability interface and instantiate and generate step unit objects for each sequential step according to the configuration order.

[0118] The second processor generation unit is used to obtain the post-processing conditions of each step unit and instantiate and generate the post-processor of each step unit according to the post-processing conditions.

[0119] The third processor generation unit is used to obtain the response result requirements of the aggregation capability interface and instantiate and generate the response processor of the pipeline data model according to the response result requirements.

[0120] In one possible design, when a path parameter mapping method is used between each step unit so that the processing result of the previous step unit becomes the input parameter of each basic sub-unit of the call request in the next step unit, the model building module is specifically used for:

[0121] The parameter values ​​between each step unit use fixed values, reference values, and / or wildcard data types to define the data conversion mapping between the processing result of the previous step unit and the input parameters of each call request basic sub-unit in the next step unit;

[0122] When a parameter is configured with multiple data types, the parameter values ​​are overwritten according to the priority order of fixed value < reference value < wildcard.

[0123] In one possible design, the device further includes:

[0124] A storage module is used to serialize the pipelined data model to generate JSON text and store the JSON text in a text database.

[0125] In one possible design, the device further includes:

[0126] The publishing module is used to review pipelined data models in JSON format and publish them to the message queue of the runtime service cache after approval, so that the aggregation capability interface can subscribe to the message queue at runtime.

[0127] In one possible design, the device further includes:

[0128] The call response module is used to receive call requests from the aggregation capability interface and obtain the configuration data of the pipeline data model based on the call request.

[0129] The result return module is used to construct the context environment for the call based on the configuration data, and to process the aggregated capability interface using reactive streaming technology to return the response result of the preset configuration rules.

[0130] In one possible design, when receiving a call request to the aggregation capability interface and retrieving configuration data for the pipelined data model based on the call request, the call response module is specifically used for:

[0131] Receive the call request of the aggregation capability interface, encapsulate the call request into a data stream, and distribute the data stream to the corresponding pipeline data model;

[0132] Retrieve configuration data for the pipelined data model from the message queue.

[0133] In one possible design, when constructing the call context based on configuration data and using reactive streaming technology to process the aggregated capability interface to return a response result based on preset configuration rules, the result return module is specifically used for:

[0134] Based on the data transformation mapping relationship in the configuration data, extract the actual parameter execution result of the previous step unit in the context environment, and set the actual parameter execution result in the input parameter of the basic sub-unit object of the call request of the next step unit;

[0135] The actual parameter data is processed and manipulated through the methods of the class object of the pipeline data model, and the response results are output and returned through the reactive listener method.

[0136] The working process, working details and technical effects of the aforementioned device provided in the second aspect of this embodiment can be found in the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

[0137] A third aspect provides a computer device comprising a memory, a processor, and a transceiver connected in sequence, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the pipeline-based atomic capability interface aggregation method as described in any possible design of the first aspect.

[0138] Specifically, the memory may include, but is not limited to, Random-Access Memory (RAM), Read-Only Memory (ROM), Flash Memory, First-In-First-Out (FIFO) Memory, and / or First-In-Last-Out (FILO) Memory, etc.; the processor may not be limited to the STM32F105 series microprocessor; the transceiver may be, but is not limited to, a WiFi (Wireless Fidelity) wireless transceiver, a Bluetooth wireless transceiver, a GPRS (General Packet Radio Service) wireless transceiver, and / or a ZigBee (a low-power LAN protocol based on the IEEE 802.15.4 standard) wireless transceiver, etc. Furthermore, the computer device may also include, but is not limited to, a power module, a display screen, and other necessary components.

[0139] The working process, working details and technical effects of the aforementioned computer device provided in the third aspect of this embodiment can be found in the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

[0140] The fourth aspect provides a computer-readable storage medium storing instructions that, when executed on a computer, perform the atomic capability interface aggregation method based on a pipeline model as described in any possible design of the first aspect.

[0141] The computer-readable storage medium refers to a carrier for storing data, which may include, but is not limited to, floppy disks, optical disks, hard disks, flash memory, USB flash drives and / or memory sticks, etc. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

[0142] The working process, working details and technical effects of the aforementioned computer-readable storage medium provided in the fourth aspect of this embodiment can be found in the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

[0143] The fifth aspect provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the atomic capability interface aggregation method based on a pipeline model as described in any possible design of the first aspect.

[0144] The working process, working details and technical effects of the computer program product containing instructions provided in the fifth aspect of the embodiments of this application can be found in the method described in the first aspect or any possible design of the first aspect, and will not be repeated here.

[0145] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for aggregating atomic capability interfaces based on a pipeline model, characterized in that, include: Receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface according to the atomic capability aggregation requests, and construct a pipeline data model according to the model parameters; The pipeline data model is a mapping of aggregation capability interfaces, including multiple serial processing step units. Each step unit contains multiple parallel basic call request sub-units. Each basic call request sub-unit has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameters of each basic call request sub-unit in the next step unit. After the pipeline data model is reviewed and published to the runtime service cache, the runtime service receives the actual aggregation capability interface call request, reads the corresponding pipeline model configuration data in the cache, constructs the call context environment, and uses reactive streaming technology to process the atomic capability interface call and return the result to the caller, so that no additional scheduling engine component is needed for control. Receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface based on the atomic capability aggregation requests, and construct a pipeline data model based on the model parameters, including: Receive atomic capability aggregation requests from the visualization capability configuration interface, and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests; Receive basic data configured by the visualization capability configuration interface, extract atomic capability interface data from the basic data, and instantiate a corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data. Obtain the pre-processing conditions of the atomic capability interface, and instantiate the pre-processor corresponding to the basic sub-unit object of each call request based on the pre-processing conditions; Obtain the configuration order of each atomic capability interface, and instantiate a step unit object for each sequential step according to the configuration order; Obtain the post-processing conditions for each step unit, and instantiate and generate the post-processor for each step unit based on the post-processing conditions. Obtain the response requirements of the aggregation capability interface, and instantiate and generate the response processor of the pipeline data model based on the response requirements.

2. The atomic capability interface aggregation method based on the pipeline model according to claim 1, characterized in that, The steps are mapped using path parameters so that the processing result of the previous step becomes the input parameter for each basic sub-unit of the call request in the next step, including: The parameter values ​​between each step unit use fixed values, reference values, and / or wildcard data types to define the data conversion mapping between the processing result of the previous step unit and the input parameters of each call request basic sub-unit in the next step unit; When a parameter is configured with multiple data types, the parameter values ​​are overwritten according to the priority order of fixed value < reference value < wildcard.

3. The atomic capability interface aggregation method based on the pipeline model according to any one of claims 1-2, characterized in that, After constructing the pipeline data model based on the model parameters, the method further includes: The pipelined data model is serialized to generate JSON text, and the JSON text is stored in a text database.

4. The atomic capability interface aggregation method based on the pipeline model according to claim 3, characterized in that, After storing the JSON text in a text database, the method further includes: The pipeline data model in JSON format is reviewed, and after approval, it is published to the message queue of the runtime service cache so that the aggregation capability interface can subscribe to the message queue at runtime.

5. The atomic capability interface aggregation method based on the pipeline model according to claim 4, characterized in that, After the pipelined data model is published to the message queue of the runtime service cache following approval, the method further includes: Receive the call request for the aggregation capability interface, and obtain the configuration data of the pipeline data model according to the call request; The context environment for the call is constructed based on the configuration data, and the aggregated capability interface is processed using reactive streaming technology to return the response result according to the preset configuration rules.

6. The atomic capability interface aggregation method based on the pipeline model according to claim 5, characterized in that, Receive calls to the aggregation capability interface and obtain the configuration data for the pipeline data model based on the calls, including: Receive the call request of the aggregation capability interface, encapsulate the call request into a data stream, and distribute the data stream to the corresponding pipeline data model; Retrieve configuration data for the pipelined data model from the message queue.

7. The atomic capability interface aggregation method based on the pipeline model according to claim 5, characterized in that, The context environment for the call is constructed based on the configuration data, and the aggregated capability interface is processed using reactive streaming technology to return the response result according to the preset configuration rules, including: Based on the data transformation mapping relationship in the configuration data, extract the actual parameter execution result of the previous step unit in the context environment, and set the actual parameter execution result in the input parameter of the basic sub-unit object of the call request of the next step unit; The actual parameter data is processed and manipulated through the methods of the class object of the pipeline data model, and the response results are output and returned through the reactive listener method.

8. An atomic capability interface aggregation device based on a pipeline model, characterized in that, include: The model building module is used to receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface according to the atomic capability aggregation requests, and build a pipeline data model according to the model parameters. The pipeline data model is a mapping of the aggregation capability interface, including multiple serial processing step units. Each step unit contains multiple parallel basic sub-units of call requests. Each basic sub-unit of call request has a one-to-one mapping relationship with each atomic capability interface. The step units are mapped using path parameters so that the processing result of the previous step unit becomes the input parameter of each basic sub-unit of call request in the next step unit. After the pipeline data model is reviewed, it is published to the runtime service cache. After the runtime service receives the actual call request of the aggregation capability interface, it reads the corresponding pipeline model configuration data in the cache, constructs the call context environment, and uses reactive streaming technology to process the call of the atomic capability interface and return the result to the caller, so that no additional scheduling engine component is needed for control. Receive atomic capability aggregation requests from the visual design interface, obtain model parameters configured through the design interface based on the atomic capability aggregation requests, and construct a pipeline data model based on the model parameters, including: Receive atomic capability aggregation requests from the visualization capability configuration interface, and generate the basic framework of the pipeline data model based on the atomic capability aggregation requests; Receive basic data configured by the visualization capability configuration interface, extract atomic capability interface data from the basic data, and instantiate a corresponding call request basic sub-unit object for each atomic capability interface based on the atomic capability interface data. Obtain the pre-processing conditions of the atomic capability interface, and instantiate the pre-processor corresponding to the basic sub-unit object of each call request based on the pre-processing conditions; Obtain the configuration order of each atomic capability interface, and instantiate a step unit object for each sequential step according to the configuration order; Obtain the post-processing conditions for each step unit, and instantiate and generate the post-processor for each step unit based on the post-processing conditions. Obtain the response requirements of the aggregation capability interface, and instantiate and generate the response processor of the pipeline data model based on the response requirements.

9. A computer device, characterized in that, The device includes a memory, a processor, and a transceiver connected in sequence. The memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program and execute the atomic capability interface aggregation method based on the pipeline model as described in any one of claims 1 to 7.

Images