Oil and gas business operator generation method, device, storage medium and program product

Abstract

This invention relates to the field of oil and gas business operators, and discloses a method, device, storage medium, and program product for generating oil and gas business operators. The method includes: constructing a tree-like classification system comprising multiple business nodes at different levels based on acquired oil and gas business process information, and determining the business attributes of each business node; matching the business attributes of each business node with multiple standard parameters using a general structural model to construct a mapping relationship between each business node and the standard parameters, wherein the general structural model includes multiple standard parameters; and generating a corresponding oil and gas business operator based on the mapping relationship between each business node and the standard parameters in response to an operator code generation instruction. The method provided by this invention enables the automatic generation of standardized parameter structure operator code, avoiding redundant development and improving the development efficiency and maintenance cost of operator code.

Description

Technical Field

[0001] This invention relates to the field of oil and gas business operators, and more particularly to a method, apparatus, storage medium, and program product for generating oil and gas business operators. Background Technology

[0002] Currently, in oil and gas business workflows, operator definition and parameter management mainly include two modes: "customized operator development" and "fixed parameter template reuse". The customized operator development model is designed for workflow requirements in different scenarios of oil and gas operations (such as drilling parameter calculation, oil production equipment status monitoring, and gathering and transportation process pressure analysis). Developers need to write operator code separately and manually define the input parameters (such as "drilling depth", "wellhead temperature", and "pump pressure") and output parameters (such as "drilling efficiency assessment results" and "equipment failure risk level") structure for each operator.

[0003] The fixed parameter template reuse mode involves pre-building a small number of general parameter templates (such as "numerical parameter templates" and "state parameter templates"), and then directly applying the templates to define the input and output parameters when developing new operators.

[0004] The above two models have the following problems: First, the development of customized operators is inefficient and costly: due to the complexity of the oil and gas business node system, each node's corresponding operator needs to define input and output parameters separately. The same type of parameters requires multiple writing of structural code, resulting in a large amount of repetitive work for developers, a long operator development cycle, and customized development will lead to operators being strongly bound to specific business scenarios and unable to be reused.

[0005] Second, poor scalability: Fixed parameter templates only cover basic parameter types and cannot meet the complex parameter requirements of oil and gas operations. Furthermore, the constraint rules of template parameters are fixed and cannot be dynamically adjusted according to specific business nodes (for example, the value range of "drilling depth" is 0-3000 meters in shallow well scenarios and 3000-10000 meters in deep well scenarios, which fixed templates cannot adapt to). This results in parameter definitions that do not meet actual business needs, requiring manual modification of the template code.

[0006] Third, workflow integration is difficult and maintenance costs are high: the input and output parameters of operators lack standard definitions, and the output parameters of one operator cannot be directly matched with the input parameters of another, increasing the complexity of workflow integration and making it prone to errors. Furthermore, when oil and gas business parameter standards are updated, the parameter definition code of the relevant operators needs to be modified one by one. After parameter modifications, historical versions cannot be traced, resulting in inconsistent parameter structures across different versions of operators, increasing the difficulty of later maintenance. Summary of the Invention

[0007] This invention provides a method, apparatus, storage medium, and program product for generating oil and gas business operators to solve at least one of the above-mentioned problems.

[0008] In a first aspect, embodiments of the present invention provide a method for generating oil and gas business operators, comprising: constructing a tree-shaped classification system including multiple business nodes at different levels based on acquired oil and gas business process information, and determining the business attributes of each business node; matching the business attributes of each business node with multiple standard parameters through a general structural model, and constructing a mapping relationship between each business node and the standard parameters, wherein the general structural model includes multiple standard parameters; and generating a corresponding oil and gas business operator based on the mapping relationship between each business node and the standard parameters in response to an operator code generation instruction.

[0009] Optionally, the general structural model is constructed based on the following steps: based on the business attributes of each business node, define the data type of the parameter structure and multiple core fields of the standard parameters, wherein the core fields include numeric fields, enumerated fields, composite fields and dynamic fields; construct the general structural model according to the data type of the parameter structure and multiple core fields of the standard parameters.

[0010] Optionally, the steps for determining the business attributes of each business node include: obtaining the business objectives, data types, and parameter constraints of each business node; constructing an oil and gas business node attribute table based on the business objectives, data types, and parameter constraints of each business node, and determining the business attributes of each business node.

[0011] Optionally, the steps of matching the business attributes of each business node with multiple standard parameters and constructing the mapping relationship between each business node and the standard parameters through a general structural model include: matching the corresponding standard parameters for the operator input parameters and operator output parameters of each business node based on the oil and gas business node attribute table and through the general structural model; generating an operator parameter mapping table according to the standard parameters mapped to the operator input parameters and operator output parameters of each business node, and determining the mapping relationship between each business node and the standard parameters.

[0012] Optionally, in response to the operator code generation instruction, the step of generating the corresponding oil and gas business operator based on the mapping relationship between each business node and standard parameters includes: in response to the operator code generation instruction, calling the code generation engine, and generating the input parameter parsing code and output parameter encapsulation code of the oil and gas business operator based on the operator parameter mapping table.

[0013] Optionally, the oil and gas business operator generation method further includes: adjusting the parameter constraint conditions in response to the parameter constraint adjustment command, so that the parameter range of the parameter constraint conditions is increased or decreased; and based on the adjusted parameter constraint conditions, retrieving all oil and gas business operators that reference the adjusted parameter constraint conditions, and synchronously updating the oil and gas business operators according to the change in the parameter range of the adjusted parameter constraint conditions.

[0014] Optionally, the oil and gas business operator generation method further includes: in a workflow formed by coupling multiple oil and gas business operators, comparing the output parameters of the previous oil and gas business operator and the input parameters of the next oil and gas business operator; if the parameter names are the same, then the parameter is directly transmitted in the workflow.

[0015] Optionally, the method for generating oil and gas business operators further includes: establishing a version log database of standard parameters and oil and gas business operators, wherein the version log database is used to store the update information of standard parameters and oil and gas business operators each time; when any oil and gas business operator is updated, based on the version log database, verifying whether the operator structure of the updated oil and gas business operator is compatible with that of the previous oil and gas business operator; if they are not compatible, comparing the differences in the standard parameters of the two and generating a difference prompt message.

[0016] Optionally, the oil and gas business operator generation method further includes: classifying and storing the generated oil and gas business operators according to different types of business nodes, and constructing an operator reuse library; based on the version log database, generating and displaying a standard parameter management interface and an operator reuse interface, wherein the standard parameter management interface is used to display and edit the standard parameter structure of the oil and gas business operators, and the operator reuse interface is used to display and call the oil and gas business operators in the operator reuse library, and generate and display the mapping relationship between each business node and the standard parameters.

[0017] In a second aspect, embodiments of the present invention provide an electronic device, including: a processor and a memory, wherein the memory stores instructions; the processor invokes the instructions in the memory to cause the processor to execute the oil and gas business operator generation method of any of the foregoing embodiments of the first aspect of the present invention.

[0018] Thirdly, embodiments of the present invention provide a computer-readable storage medium storing instructions that, when executed by a processor, implement the oil and gas business operator generation method of any of the foregoing embodiments of the first aspect of the present invention.

[0019] Fourthly, embodiments of the present invention provide a computer program product, which includes a computer program that, when executed by a processor, implements the oil and gas business operator generation method of any of the foregoing embodiments of the first aspect of the present invention.

[0020] The above-mentioned technical solution of the present invention establishes a mapping relationship between business nodes and standard parameters, thereby realizing the automatic generation of standardized parameter structure operator code, avoiding redundant development, and improving the development efficiency and maintenance cost of operator code. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0022] Figure 1 This is a flowchart of the first embodiment of the oil and gas business operator generation method of the present invention; Figure 2 This is a flowchart illustrating the steps of constructing a general structural model in one embodiment of the oil and gas business operator generation method of the present invention. Figure 3 This is a flowchart of step S110 in one embodiment of the oil and gas business operator generation method of the present invention; Figure 4 This is a flowchart of step S120 in one embodiment of the oil and gas business operator generation method of the present invention; Figure 5 This is a flowchart of a second embodiment of the oil and gas business operator generation method of the present invention; Figure 6 This is a flowchart of the third embodiment of the oil and gas business operator generation method of the present invention; Figure 7 This is a flowchart illustrating the mapping standard parameters in the first embodiment of the oil and gas business operator generation method of the present invention. Figure 8 This is a flowchart illustrating the reuse operator in the third embodiment of the oil and gas business operator generation method of the present invention. Figure 9 This is a flowchart illustrating the third embodiment of the oil and gas business operator generation method of the present invention; Figure 10 This is a structural block diagram of one embodiment of the electronic device of the present invention. Detailed Implementation

[0023] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0024] It should be noted that all directional indications in the embodiments of the present invention, such as up, down, left, right, front, back, etc., are only used to explain the relative positional relationship and movement of the components in a specific posture as shown in the attached figure. If the specific posture changes, the directional indication will also change accordingly.

[0025] Furthermore, the use of terms such as "first" and "second" in this invention is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0026] For ease of understanding, the method for generating oil and gas business operators according to embodiments of the present invention is described below, such as... Figure 1 As shown, the oil and gas business operator generation method in this embodiment of the invention includes steps S110 to S130.

[0027] In step S110, based on the acquired oil and gas business process information, a tree-shaped classification system including multiple business nodes at different levels is constructed to determine the business attributes of each business node.

[0028] In this embodiment, the business nodes of the oil and gas business are classified and hierarchically according to the entire process of oil and gas business, such as drilling, oil production, gathering and transportation, refining, equipment maintenance and safety supervision, to form a tree-shaped classification system of "first-level node - second-level node - third-level node" (e.g. "drilling → deep well drilling → deep well drilling parameter acquisition"), so as to cover every sub-node of the oil and gas business scenario.

[0029] like Figure 3 As shown, in some optional embodiments, the step of determining the service attributes of each service node in step S110 includes: Step S111: Obtain the business objectives, data types, and parameter constraints for each business node.

[0030] Step S112: Based on the business objectives, data types, and parameter constraints of each business node, construct an oil and gas business node attribute table and determine the business attributes of each business node.

[0031] In this embodiment, when determining the business attributes of each business node, the business attributes of each business node are first sorted out: business objectives, data types, and parameter constraint requirements.

[0032] The business objectives include parameter acquisition, anomaly detection, and result evaluation. Data types include numerical, enumerated, combined, and dynamic types. Parameter constraints include value range, unit validation, and required fields. After determining the business attributes of each business node, an oil and gas business node attribute table is established and output.

[0033] like Figure 2 As shown, in some optional embodiments, the general structural model is constructed through steps S101 to S102.

[0034] In step S101, based on the business attributes of each business node, the data type of the parameter structure and multiple core fields of the standard parameters are defined. These core fields include numeric fields, enumerated fields, composite fields, and dynamic fields.

[0035] In step S102, a general structural model is constructed according to the data type of the parameter structure and multiple core fields of the standard parameters.

[0036] like Figure 7 As shown in this embodiment, a general structural model with standard parameters is defined based on the business attributes of each business node. This general structural model is used to uniformly describe the operator elements, execution logic, and upstream and downstream dependencies of different business nodes.

[0037] In the process of model building, the oil and gas business process is first analyzed, and the business activities are broken down into standardized business nodes. Then, each business node is further abstracted into corresponding business operator elements, which include input conditions, execution actions and output results.

[0038] Based on this, a general structural model is constructed using a hierarchical structure, which provides a structured description of business nodes, operator definitions, parameter constraints, and dependencies between nodes.

[0039] Based on the aforementioned general structural model, standardized descriptions of business nodes and operator reuse can be achieved. Different oil and gas business scenarios only need to instantiate and map the model without redefining the operator logic. Furthermore, this general structural model supports the combination, replacement, and dynamic adjustment of business nodes, providing a unified structural foundation for subsequent business matching, scheduling, and optimization.

[0040] For example, the general structural model in this embodiment contains five core fields: param id, param name, param type, param constraint, and param version. The meaning and physical function of each field are shown in Table 1. Specifically, for different param types, a detailed structure is defined: Numeric type: The `decimal places` field represents the number of decimal places. For example, "2" means to retain two decimal places. Enumeration type: The enum values ​​field represents a list of enumerated values, such as "wear", "leakage", and "overload"; Combined type: The subparams field represents a list of subparameters, for example, "{param id:'wellheadpressure 001'},{param id:'wellhead temp 001'}"). Dynamic type: The dynamic rule field represents a dynamic rule expression, such as "if drilling depth > 3000 then mud density threshold = 1.2-1.5".

[0041] Table 1

[0042] In step S120, the business attributes of each business node are matched with multiple standard parameters using a general structural model to construct a mapping relationship between each business node and the standard parameters. The general structural model includes multiple standard parameters.

[0043] like Figure 4 As shown, in some optional embodiments, step S120 includes steps S121 to S122.

[0044] In step S121, based on the oil and gas business node attribute table, the standard parameters corresponding to the operator input parameters and operator output parameters of each business node are matched through the general structural model.

[0045] In step S122, an operator parameter mapping table is generated based on the standard parameters mapped to the operator input parameters and operator output parameters of each service node, and the mapping relationship between each service node and the standard parameters is determined.

[0046] In this embodiment, by establishing a mapping relationship between business nodes and standard parameters, and based on the oil and gas business node attribute table, the corresponding standard parameter structure is matched to the operator input and output parameters of each node to generate an operator parameter mapping table.

[0047] For example, the input parameters of the "Deep Well Drilling Parameter Acquisition" operator are mapped to the standard parameters of "Deep Well Drilling - Drilling Depth" and "Deep Well Drilling - Wellhead Temperature", and the output parameters are mapped to the combined standard parameters of "Deep Well Drilling - Real-time Drilling Parameter Set".

[0048] In step S130, in response to the operator code generation instruction, a corresponding oil and gas business operator is generated based on the mapping relationship between each business node and standard parameters.

[0049] In some optional embodiments, the step of generating oil and gas business operators includes: in response to an operator code generation instruction, invoking a code generation engine, and generating input parameter parsing code and output parameter encapsulation code for the oil and gas business operators based on an operator parameter mapping table.

[0050] like Figure 8 and Figure 9 As shown, in this embodiment, operator code is automatically generated: Based on the operator code generation instructions, and combined with the operator parameter mapping table, the code generation engine is called to automatically generate the operator's input parameter parsing and output parameter encapsulation code (such as Java or Python code), enabling rapid development of operator code.

[0051] Furthermore, after obtaining the input parameter parsing code and output parameter encapsulation code of the oil and gas business operator, the oil and gas business operator generation method also includes: in the workflow formed by coupling multiple oil and gas business operators, comparing the output parameter of the previous oil and gas business operator and the input parameter of the next oil and gas business operator, if the parameter names of the two are consistent, then the parameter is directly transmitted in the workflow.

[0052] In this embodiment, the standardized operators are stored according to business nodes, and the input parameters, output parameter standard parameter IDs, applicable scenarios, and version numbers of the operators are recorded to form a searchable and callable operator reuse library for automatic matching of workflow parameters.

[0053] When automatically matching workflow parameters, if multiple operators form a workflow, the output parameter paramid of the previous operator is compared with the input parameter paramid of the next operator. If they match, the parameter is passed directly.

[0054] For example, if the output parameter "Deep Well Drilling Parameter Acquisition" of the operator "Deep Well Drilling - Real-time Drilling Parameter Set" is the same as the input parameter param id of the operator "Deep Well Drilling Parameter Anomaly Detection", then the data can be directly transmitted without the need for an additional conversion interface to convert the data format.

[0055] Figure 5 This is a flowchart of a second embodiment of the oil and gas business operator generation method of the present invention. Some parts of the structure of the second embodiment are the same as those of the first embodiment; the differences between the two will be described below, while the similarities will not be detailed further.

[0056] like Figure 5As shown, in the second embodiment of the present invention, steps S210 to S230 are the same as steps S110 to S130 in the first embodiment of the present application, and will not be described in detail here.

[0057] After obtaining the oil and gas business operator, the oil and gas business operator generation method further includes steps S240 to S250.

[0058] In step S240, in response to the parameter constraint adjustment command, the parameter constraint conditions are adjusted so that the parameter range of the parameter constraint conditions is increased or decreased.

[0059] In step S250, based on the adjusted parameter constraints, all oil and gas business operators that reference the adjusted parameter constraints are retrieved, and the oil and gas business operators are updated synchronously according to the changes in the parameter range of the adjusted parameter constraints.

[0060] In this embodiment, the process of dynamically adjusting the parameter constraints is as follows: When business scenarios change, such as adjusting the drilling depth range from 0-8000 meters to 0-10000 meters, the `param constraint` field of the corresponding standard parameter can be modified. For example, the value of the `range` parameter can be updated to 0-10000. The operators that reference this parameter can be retrieved and all operators that reference this parameter can be updated synchronously. This achieves automatic synchronous updates of all operators without having to modify the operator code one by one.

[0061] When the parameter types required for operator reuse scenarios differ, for example, if the original operator input parameter is "numeric-integer" and the reuse scenario is "numeric-decimal", the built-in conversion function is called to convert the integer to a decimal and perform unit conversion, thereby achieving parameter type adaptation and conversion without having to redevelop the operator.

[0062] During the operation of oil and gas business, changes in business scenarios include both proactive manual adjustments and non-manual adjustments triggered by changes in equipment status or abnormal events.

[0063] For changes in business scenarios not triggered by human intervention, abnormal features that may affect the execution status of business nodes are detected by collecting and analyzing equipment operation data, sensor monitoring data, and business operation logs.

[0064] When abnormal characteristics of changes in the above-mentioned non-human business scenarios are detected, the status information of the corresponding business nodes is updated, and based on the updated business node status, the corresponding business operators are re-matched, the execution logic is adjusted, or the parameter values ​​of the corresponding business operators are modified.

[0065] Meanwhile, the detected abnormal business scenarios and their updated operators are saved as new sample data to the version log database and operator reuse library to achieve continuous updating and optimization of the general structural model and business operators.

[0066] Figure 6 This is a flowchart of the third embodiment of the oil and gas business operator generation method of the present invention. Some structures of the third embodiment are the same as those of the first embodiment. The differences between the two will be described below, while the similarities will not be described in detail.

[0067] like Figure 6 As shown, in the third embodiment of the present invention, steps S310 to S330 are the same as steps S110 to S130 in the first embodiment of the present application, and will not be described in detail here. The oil and gas business operator generation method in the third embodiment of the present application also includes steps S340 to S350.

[0068] In step S340, a version log database for standard parameters and oil and gas business operators is established. The version log database is used to store the update information of standard parameters and oil and gas business operators each time.

[0069] In step S350, when any oil and gas business operator is updated, the operator structure of the updated oil and gas business operator is checked against the version log database to see if they are compatible. If they are not compatible, the differences in their standard parameters are compared and a difference prompt message is generated.

[0070] In this embodiment, version logs are established for standard parameters and oil and gas business operators respectively to record the content of each update, such as parameter constraint modification records, operator function optimization records, update time, updater, and version number.

[0071] When the operator version in the workflow is updated, the compatibility of the new operator's input and output parameter versions with other operators is checked. For example, if the output parameter of the old operator is V1.0 and the input parameter of the new operator is V2.0, the parameter structure of the two operators is checked for compatibility. If they are not compatible, the differences between the two operators are detected and displayed. For example, if the new operator adds the field "decimal places", the corresponding updates or adaptations are performed to achieve version compatibility verification.

[0072] When querying version update records, you can trace back to historical versions by version number to achieve version history tracking.

[0073] Furthermore, the oil and gas business operator generation method of the third embodiment of this application also includes steps S360 to S370.

[0074] In step S360, the generated oil and gas business operators are classified and stored according to different types of business nodes to build an operator reuse library.

[0075] In step S370, based on the version log database, a standard parameter management interface and an operator reuse interface are generated and displayed. The standard parameter management interface is used to display and edit the standard parameter structure of oil and gas business operators, and the operator reuse interface is used to display and call oil and gas business operators in the operator reuse library, as well as generate and display the mapping relationship between each business node and the standard parameters.

[0076] In this embodiment, users can visually create, edit, and delete standard parameters through the standard parameter management interface. The standard parameter management interface provides parameter retrieval functions by real-time preview of the parameter structure (e.g., displaying the param constraint in JSON format) and by business node, parameter type, and version number.

[0077] The operator reuse interface displays all operators in the operator reuse library, annotating the applicable scenarios, input and output parameter lists, and reuse counts of the operators. This allows users to call the appropriate operators to the target workflow and automatically generate parameter mapping relationships, which are then displayed on the interface.

[0078] In addition to the embodiments described above, operator reuse and database construction can also be achieved in other ways, for example: 1. XML-based fixed parameter template solution: Parameter templates are defined using XML format (e.g., ... <param id="drilling_depth" type="NUMBER" range="0-10000"> This approach uses XML templates to parse parameter structures during operator development. While this method enables the reuse of basic parameters, it does not support dynamic constraints and composite parameters (e.g., the range cannot be adjusted according to the scenario), and the XML format parsing efficiency is low, failing to meet the requirements in terms of adaptability and efficiency.

[0079] 2. Database-based parameter configuration scheme: The parameter structure is stored in a relational database, and parameter definitions are obtained through SQL queries. The operator code reads the parameter structure from the database. This approach lacks a version management mechanism, cannot trace historical versions, and has slow database query speed. The parameter parsing efficiency during operator runtime is low, making it only suitable for scenarios with low parameter update frequency and low efficiency requirements.

[0080] 3. Parameter Conversion Scheme Based on General API: This scheme retains the traditional model of custom operator development, using a general parameter conversion API to solve parameter incompatibility issues during workflow integration. However, this scheme cannot solve the problems of operator reuse and parameter standardization, resulting in very low operator development efficiency.

[0081] Parameter templates can be defined in XML format (e.g.) <param id="drilling_depth" type="NUMBER" range="0-10000"> When developing operators, XML templates are used to parse parameter structures.

[0082] The aforementioned solutions all have their own limitations and cannot adapt to the complex scenarios of oil and gas business. The method in this application addresses the complex parameter requirements of oil and gas business by subdividing each business node through core fields and a general structural model, in order to solve the standardization problem of combined parameters with multiple sub-parameters and dynamic parameters with constraint rules that change with the scenario.

[0083] For example, such as Figure 8 As shown, using the method of the above embodiments of this application, the structure of the dynamic parameter of "deep well drilling-mud density threshold" can be defined as follows: { "param_id":"drilling_mud_density_001", "param_name":"Deep Well Drilling - Mud Density Threshold", "param_type":"DYNAMIC", "param_constraint":{ "range":"1.2-1.5", "unit":"g / cm³", "required":true }, "dynamic_rule":"if drilling depth > 3000 then range = '1.3-1.6';if drilling depth > 5000 then range = '1.4-1.7'", "param_version":"V2.0" } By establishing a unique mapping based on param id, a standard parameter can be reused in multiple operators. For example, the "wellhead temperature" parameter can be reused in multiple operators such as "oil wellhead monitoring" and "refining distillation tower monitoring". As well as an operator can be reused in multiple scenarios, for example, the "temperature anomaly detection" operator can be dynamically adjusted through parameter constraints and reused in shallow wells, deep wells, refining and other scenarios.

[0084] During workflow integration, appropriate parameters are automatically matched using `param id` to resolve integration difficulties caused by incompatibility of traditional parameters. For example: The output parameter param id of drilling parameter acquisition operator A is "drilling_real_time_data_001", a combined type; The input parameter param id of the drilling parameter anomaly detection operator B is: "drilling_real_time_data_001"; When the param id matches, the data is directly transmitted for reuse without the need for format conversion.

[0085] The above-described technical solution of this application achieves the following beneficial effects: 1. Standardized parameter structure and automatic code generation have been implemented to avoid redundant development. The dynamic parameter adaptation mechanism supports the reuse of operators across scenarios, eliminating the need to redevelop operators for new scenarios, thereby improving the development efficiency of operators and reducing labor and time costs.

[0086] 2. By automatically matching parameters using param id, parameter incompatibility issues are eliminated, workflow processing speed is accelerated, and integration error rate is reduced.

[0087] 3. Parameter and operator versions support batch updates and historical traceability management. When parameter standards are updated, they can be updated and modified in a timely manner, improving maintenance efficiency.

[0088] 4. Parameter constraints can be dynamically adjusted according to the scenario, improving the flexibility and adaptability of reusing parameters of all types in oil and gas business.

[0089] 5. A unified business node-parameter-operator standard system has been established to solve the problems of traditional parameter confusion and operator silos, which facilitates the digitalization of the entire oil and gas business process, lowers the threshold for operator development, and is applicable to workflow operator development in different fields.

[0090] The oil and gas business operator generation method provided in this embodiment of the invention includes: constructing a tree-shaped classification system including multiple business nodes at different levels based on the acquired oil and gas business process information, and determining the business attributes of each business node; matching the business attributes of each business node with multiple standard parameters through a general structural model, and constructing a mapping relationship between each business node and the standard parameters, wherein the general structural model includes multiple standard parameters; and generating a corresponding oil and gas business operator based on the mapping relationship between each business node and the standard parameters in response to the operator code generation instruction.

[0091] The oil and gas business operator generation method provided in this embodiment of the invention establishes a mapping relationship between business nodes and standard parameters, thereby realizing the automatic generation of standardized parameter structure operator code, avoiding redundant development, and improving the development efficiency and maintenance cost of operator code.

[0092] In addition to the above method embodiments, the present invention also provides, as follows: Figure 10 An electronic device is shown, including a processor 401 and a memory 402, wherein the memory 402 stores instructions.

[0093] The processor 401 can call instructions in the memory 402 to execute the oil and gas business operator generation method of any of the above embodiments of the present invention.

[0094] The oil and gas business operator generation method provided in the above embodiments of this application includes: constructing a tree-shaped classification system including multiple business nodes at different levels based on the acquired oil and gas business process information, and determining the business attributes of each business node; matching the business attributes of each business node with multiple standard parameters through a general structural model, and constructing a mapping relationship between each business node and the standard parameters, wherein the general structural model includes multiple standard parameters; and generating a corresponding oil and gas business operator based on the mapping relationship between each business node and the standard parameters in response to the operator code generation instruction.

[0095] The electronic device provided in this embodiment of the invention establishes a mapping relationship between business nodes and standard parameters by implementing the above method, which enables the automatic generation of standardized parameter structure operator code, avoids redundant development, and improves the development efficiency and maintenance cost of operator code.

[0096] Furthermore, the electronic device provided in the embodiments of the present invention may also include a communication interface 403 and a bus 404, wherein the processor 401, the memory 402 and the communication interface 403 are electrically connected through the bus 404.

[0097] The memory 402 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 403 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 404 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 10 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0098] Processor 401 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 401 or by instructions in software form. Processor 401 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a readily available storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 402. The processor 401 reads the information from memory 402 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0099] This invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of the above-described oil and gas business operator generation method.

[0100] The computer-readable storage medium provided in this embodiment of the invention stores data and computer-executable instructions for the above-described oil and gas business operator generation method. The oil and gas business operator generation method includes: constructing a tree-shaped classification system including multiple business nodes at different levels based on acquired oil and gas business process information, and determining the business attributes of each business node; matching the business attributes of each business node with multiple standard parameters through a general structural model, and constructing a mapping relationship between each business node and the standard parameters, wherein the general structural model includes multiple standard parameters; and generating a corresponding oil and gas business operator based on the mapping relationship between each business node and the standard parameters in response to the operator code generation instruction.

[0101] The computer-readable storage medium provided in this embodiment of the invention establishes a mapping relationship between business nodes and standard parameters by implementing the above method, which enables the automatic generation of standardized parameter structure operator code, avoids redundant development, and improves the development efficiency and maintenance cost of operator code.

[0102] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps: In step S110, based on the acquired oil and gas business process information, a tree-shaped classification system including multiple business nodes at different levels is constructed to determine the business attributes of each business node.

[0103] In step S120, the business attributes of each business node are matched with multiple standard parameters using a general structural model to construct a mapping relationship between each business node and the standard parameters. The general structural model includes multiple standard parameters.

[0104] In step S130, in response to the operator code generation instruction, a corresponding oil and gas business operator is generated based on the mapping relationship between each business node and standard parameters.

[0105] The computer program product provided in this embodiment of the invention establishes a mapping relationship between business nodes and standard parameters by implementing the above method, which enables the automatic generation of standardized parameter structure operator code, avoids redundant development, and improves the development efficiency and maintenance cost of operator code.

[0106] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0107] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0108] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for generating oil and gas business operators, characterized in that, The method includes: Based on the acquired oil and gas business process information, a tree-shaped classification system including multiple business nodes at different levels is constructed to determine the business attributes of each business node. Through the general structural model, the business attributes of each business node are matched with multiple standard parameters to construct a mapping relationship between each business node and the standard parameters. The general structural model includes multiple standard parameters. In response to the operator code generation instruction, a corresponding oil and gas business operator is generated based on the mapping relationship between each business node and the standard parameters.

2. The oil and gas business operator generation method of claim 1, wherein, The general structural model is constructed based on the following steps: Based on the business attributes of each business node, the data type of the parameter structure and multiple core fields of the standard parameters are defined, wherein the core fields include numeric fields, enumerated fields, combined fields and dynamic fields; The general structure model is constructed according to the data type of the parameter structure and the multiple core fields of the standard parameters.

3. The oil and gas business operator generation method of claim 1, wherein, The steps for determining the business attributes of each of the aforementioned business nodes include: Obtain the business objectives, data types, and parameter constraints for each of the business nodes; Based on the business objectives, data types, and parameter constraints of each business node, an oil and gas business node attribute table is constructed to determine the business attributes of each business node.

4. The method for generating oil and gas business operators according to claim 3, characterized in that, The steps of matching the business attributes of each business node with multiple standard parameters and constructing the mapping relationship between each business node and the standard parameters using the general structural model include: Based on the oil and gas business node attribute table, the standard parameters are matched to the operator input parameters and operator output parameters of each business node through the general structural model. Based on the standard parameters mapped to the operator input and output parameters of each business node, an operator parameter mapping table is generated to determine the mapping relationship between each business node and the standard parameters.

5. The method for generating oil and gas business operators according to claim 4, characterized in that, The steps for generating corresponding oil and gas business operators in response to operator code generation instructions, based on the mapping relationship between each business node and the standard parameters, include: In response to the operator code generation instruction, the code generation engine is invoked to generate the input parameter parsing code and output parameter encapsulation code for the oil and gas business operator based on the operator parameter mapping table.

6. The method of claim 3, wherein, The method further includes: In response to a parameter constraint adjustment command, the parameter constraint condition is adjusted such that the parameter range of the parameter constraint condition is increased or decreased; and Based on the adjusted parameter constraints, all oil and gas business operators that reference the adjusted parameter constraints are retrieved, and the oil and gas business operators are updated synchronously according to the changes in the parameter range of the adjusted parameter constraints.

7. The method of claim 1, wherein, The method further includes: In a workflow formed by coupling multiple oil and gas business operators, the output parameters of the previous oil and gas business operator and the input parameters of the next oil and gas business operator are compared. If the parameter names are the same, the parameter is directly transmitted in the workflow.

8. The oil and gas business operator generation method of claim 1, wherein, The method further includes: Establish a version log database for the standard parameters and the oil and gas business operators. The version log database is used to store the update information of the standard parameters and the oil and gas business operators for each time. When any of the oil and gas business operators is updated, the operator structure of the updated oil and gas business operator is checked against the version log database to see if they are compatible. If they are not compatible, the differences in the standard parameters of the two are compared and a difference prompt message is generated.

9. The method of claim 8, wherein, The method further includes: The generated oil and gas business operators are classified and stored according to the different types of business nodes, and an operator reuse library is constructed. Based on the version log database, a standard parameter management interface and an operator reuse interface are generated and displayed. The standard parameter management interface is used to display and edit the standard parameter structure of the oil and gas business operator. The operator reuse interface is used to display and call the oil and gas business operators in the operator reuse library, and to generate and display the mapping relationship between each business node and the standard parameters.

10. An electronic device, comprising: The electronic device includes: a processor and a memory, wherein the memory stores instructions; The processor invokes the instructions in the memory to cause the electronic device to implement the oil and gas business operator generation method as described in any one of claims 1 to 9.

11. A computer-readable storage medium storing instructions thereon, characterized in that, When the instruction is executed by the processor, it implements the oil and gas business operator generation method as described in any one of claims 1 to 9.

12. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the oil and gas business operator generation method as described in any one of claims 1 to 9.

Images