WO2023050408A1 - Ot域低代码开发方法、平台和计算机可读介质 - Google Patents

Ot域低代码开发方法、平台和计算机可读介质 Download PDF

Info

Publication number
WO2023050408A1
WO2023050408A1 PCT/CN2021/122421 CN2021122421W WO2023050408A1 WO 2023050408 A1 WO2023050408 A1 WO 2023050408A1 CN 2021122421 W CN2021122421 W CN 2021122421W WO 2023050408 A1 WO2023050408 A1 WO 2023050408A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
workflow
microservice
code development
work unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/122421
Other languages
English (en)
French (fr)
Inventor
廖亮
周振华
朱骁洵
翁畅维
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens Ltd China
Siemens AG
Siemens Corp
Original Assignee
Siemens Ltd China
Siemens AG
Siemens Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens Ltd China, Siemens AG, Siemens Corp filed Critical Siemens Ltd China
Priority to PCT/CN2021/122421 priority Critical patent/WO2023050408A1/zh
Priority to EP21958977.7A priority patent/EP4398092A4/en
Priority to US18/697,511 priority patent/US20240419408A1/en
Priority to CN202180102255.7A priority patent/CN117940889A/zh
Publication of WO2023050408A1 publication Critical patent/WO2023050408A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/35—Creation or generation of source code model driven
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse

Definitions

  • Embodiments of the present invention relate to OT domain low-code development technology, and in particular to an OT domain low-code development method, platform, and computer-readable medium.
  • Embodiments of the present invention provide an OT domain low-code development method, platform, and computer-readable medium. Predefine the operation templates that various OT devices can perform. By instantiating the templates into function blocks and then combining them into OT domain workflows, it is more suitable for code development in the OT domain, and provides a graphical user interface for users to input instructions to Generate each function block and finally form the OT domain workflow based on the relationship between the function blocks, realizing low-code development.
  • an OT domain low-code development method is provided, and the method can be executed by an OT domain low-code development platform.
  • the OT domain low-code development tool in the platform receives instructions input by the user on the graphical user interface, and the instructions are used to generate an OT domain workflow, and determine the functions included in the OT domain workflow according to the instructions Interrelationships between blocks and function blocks, and generate the OT domain workflow according to the determined interrelationships between each function block and function blocks.
  • the operation to be performed by the OT device is defined by a function block, and the function block is an example of an operation template of the category to which the OT device belongs, and the operation template predefines the OT device of this type Operations that can be performed;
  • the OT domain workflow is used to define the operations to be performed by a work unit in the OT domain, wherein the main controller of the work unit is connected to each OT device in the work unit to control each OT device The operations to be performed by the work unit are completed according to the definition of the OT domain workflow.
  • an OT domain low-code development platform including components for executing each step in the method provided in the first aspect.
  • an OT domain low-code development platform including: at least one memory configured to store computer-readable codes; at least one processor configured to invoke the computer-readable codes to execute the computer-readable codes provided in the first aspect steps in the method.
  • a computer-readable medium where computer-readable instructions are stored on the computer-readable medium, and when the computer-readable instructions are executed by a processor, the processor executes the method provided in the first aspect. steps in the method.
  • a computer program product tangibly stored on a computer-readable medium and comprising computer-readable instructions that, when executed, cause at least one processor to perform a first
  • various steps in the method are provided.
  • the OT domain low-code development tool also deploys the OT domain workflow to the runtime of the main controller of the work unit, so that it is connected to the main controller
  • Each OT device in the working unit performs operations according to the OT domain workflow. In this way, the purpose of OT domain workflow control work unit operation is realized.
  • the OT domain low-code development platform further includes an OT domain microservice generator, which generates a microservice based on the OT domain workflow, so that the IT domain code development tool realizes that IT equipment passes
  • a data platform invokes the microservice to trigger the runtime of the main controller of the work unit to execute the OT domain workflow.
  • IT equipment can call microservices generated based on OT domain workflow, thereby triggering the execution of OT workflow and realizing the integration of IT domain and OT domain.
  • the OT domain microservice generator or a third-party device registers the microservice on the data platform, so that the IT domain code development tool realizes that IT equipment passes the The data platform discovers the connected microservices.
  • IT equipment can discover the connected microservices, which can more effectively realize the invocation of microservices by IT equipment, and strengthen the relationship between the OT domain and the IT domain. fusion.
  • the OT domain microservice generator generates the API of the microservice based on the OT domain workflow, wherein the processing in the API includes the OT domain workflow
  • the input parameter of the API is the parameter obtained by the input port of the OT domain workflow
  • the output parameter of the API is the parameter output by the output port of the OT domain workflow.
  • the operation template follows an information model for runtime interaction with the main controller.
  • the compatibility between the OT domain workflow and various main controllers is realized, so that the runtime of the main controller can correctly analyze the operation that the OT domain workflow wants to achieve, thereby realizing the completion of the operation of the work unit.
  • FIGS. 1 to 4 are schematic diagrams of OT domain low-code development platforms provided by various embodiments of the present invention.
  • Fig. 5 is a flow chart of the OT domain low-code development method provided by the embodiment of the present invention.
  • FIG. 6 is a schematic diagram of the hardware implementation of the OT domain low-code development platform provided by the embodiment of the present invention.
  • the term “comprising” and its variants represent open terms meaning “including but not limited to”.
  • the term “based on” means “based at least in part on”.
  • the terms “one embodiment” and “an embodiment” mean “at least one embodiment.”
  • the term “another embodiment” means “at least one other embodiment.”
  • the terms “first”, “second”, etc. may refer to different or the same object. The following may include other definitions, either express or implied. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.
  • FIG. 1 shows an OT domain low-code development platform 100 provided by an embodiment of the present invention, and the platform 100 is used to implement low-code development in the OT domain.
  • Operational Technology is a collection of hardware and software that detects or triggers changes in processes or events in an enterprise by directly monitoring and/or controlling physical devices (referred to as OT devices).
  • OT utilizes computers to monitor or change physical conditions such as industrial control systems (Industrial Control System, ICS).
  • Industrial Control System ICS
  • the industrial control system is based on computer-implemented facilities, systems, and equipment for remote monitoring and/or control of key industrial processes to achieve physical functions.
  • the word "OT” is used to distinguish industrial control systems from traditional information technology (Information Technology, IT) systems in terms of technical implementation and functions.
  • OT devices may include, but are not limited to: Internet of Things (IoT) devices, Programmable Logic Controllers (PLC), Robotics, Manual Process, Industrial Computers (Industrial Personal Computer, IPC) and so on.
  • IoT Internet of Things
  • PLC Programmable Logic Controllers
  • IPC Intelligent Personal Computer
  • the concept of "work unit” is proposed, which makes the development closer to a relatively complete and independent control process and operation, which is more in line with the characteristics of industrial control, improves the integration of development, and reduces the complexity of development.
  • the work unit can be defined according to the actual industrial scene, for example: one station on the production line corresponds to one work unit, etc. Different work units have different technological processes.
  • the OT domain low-code development platform 100 may include:
  • An OT domain low-code development tool 10 the OT domain low-code development tool 10 can be configured as:
  • the instructions are used to generate an OT domain workflow, and the OT domain workflow is used to define the operations to be performed by a work unit in the OT domain, wherein the main controller of the work unit is connected to the work unit
  • Each OT device in the OT domain controls each OT device to complete the operations to be performed by the work unit according to the definition of the OT domain workflow;
  • the operation templates 50 of the operations that can be performed by various OT devices can be listed on the graphical user interface in the form of icons, and the user can determine the operations that the OT device needs to perform by selecting and dragging the icons onto the canvas, and through Set the specific parameters of the operation to further set the precise operation.
  • the user's selection of the operation template 50 , dragging and dropping of the operation template 50 , and setting of operation parameters can all be regarded as instructions input by the user on the graphical user interface.
  • the OT domain low-code development tool 10 obtains the information of the operation template 50 according to the instruction, and generates an instance of the operation template 50 (in the process of instantiating the operation template 50, the purpose of accurately setting the operation of the OT device is achieved) .
  • the operation to be performed by a work unit that is, more than one operation is defined in the OT domain workflow, so it usually includes multiple function blocks. According to the sequence and interrelationship of the operations, determine each function block included in the OT domain workflow and the interrelationships between functional blocks, and generate OT domain workflow accordingly.
  • the OT domain low-code development platform 100 may also include the runtime 30 of the main controller of the above-mentioned working unit.
  • the OT domain low-code development tool 10 can deploy the generated OT domain workflow to the runtime 30 of the main controller of the work unit, so that each OT device in the work unit connected to the main controller follows the OT domain Workflows perform actions.
  • the composition of the OT domain low-code development platform 100 shown in FIG. 1 and FIG. 2 only involves the OT domain.
  • the integration of the IT domain and the OT domain has become increasingly important for the digital transformation of enterprises. What needs to be realized is how the enterprise can control the process of the OT domain in an understandable and non-IT programming way.
  • the OT domain low-code development platform 100 shown in FIG. 3 solves how to control the flow of the OT domain through the code development platform 300 of the IT domain.
  • the OT domain low-code development platform 100 may further include an OT domain microservice generator 20 , which can generate microservices 40 based on OT domain workflow.
  • the IT domain code development tool 301 can be programmed to enable the IT device to call the microservice 40 through a data platform 200 to trigger the runtime 30 of the main controller of the work unit to execute the OT domain workflow.
  • the code development platform 300 of the IT domain can control the process of the OT domain, that is, the integration of the IT domain and the OT domain is realized.
  • the microservice 40 is automatically generated by the OT domain microservice generator 20 based on the OT domain workflow. It is not necessary for the code development tool 301 in the IT domain to understand the details of the OT domain workflow.
  • IT equipment may include but not limited to: manufacturing operation management (Manufacturing Operation Management, MOM) system, manufacturing execution system (manufacturing execution system, MES), enterprise resource planning (Enterprise Resource Planning, ERP) system, enterprise service bus (Enterprise Service Bus) Service Bus, ERP), Product Lifecycle Management (Product Lifecycle Management, PLM) system, etc.
  • MOM Manufacturing Operation Management
  • MES Manufacturing execution system
  • ERP enterprise resource planning
  • ERP enterprise service bus
  • PLM Product Lifecycle Management
  • the IT domain can call the microservice 40 , it is required that the IT domain can obtain the information of the microservice 40 .
  • Possible ways include but are not limited to the following two:
  • the code developers in the OT domain can notify the code developers in the IT domain of the names and IP addresses of the generated microservices 40, so that the code developers in the IT domain can directly assign the microservices 40 to The information of 40 is written into the code, so as to implement the call of the IT equipment to the microservice 40.
  • Method 1 is more suitable for scenarios with a small number of microservices.
  • each microservice 40 can be registered on the data platform 200 , so that the IT domain code development tool 301 can realize the IT domain equipment to discover the connected microservice 40 through the data platform 200 through code development.
  • the device for completing the registration of the microservice 40 may be the OT domain microservice generator 20 or a third-party device 60 (as shown in FIG. 4 ).
  • the third-party device 60 can be regarded as a part of the OT domain low-code development platform 100 , or implemented in the data platform 200 .
  • Method 2 is more suitable for scenarios with a large number of microservices.
  • the OT domain microservice generator 20 can generate the API of the microservice 40 based on the OT domain workflow, wherein, the processing procedure in the API can include the operation of each functional block in the OT domain workflow, and the input parameter of the API is OT
  • the parameters obtained by the input port of the domain workflow, and the output parameters of the API are the parameters output by the output port of the OT domain workflow.
  • the operational template 50 described above follows an information model for interacting with the runtime 30 of the master controller. In this way, the standardization of communication between the OT domain workflow and the main controllers of various OT devices is realized.
  • FIG. 5 is a flowchart of an OT domain low-code development method 500 provided by an embodiment of the present invention.
  • the method 500 can be implemented by the OT domain low-code development platform 100, and can include the following steps:
  • the OT domain low-code development tool 10 receives instructions input by the user on the graphical user interface, the instructions are used to generate an OT domain workflow, and the OT domain workflow is used to define the operations to be performed by a work unit in the OT domain, where the work The main controller of the unit connects each OT device in the working unit to control each OT device to complete the operation to be performed by the working unit according to the definition of the OT domain workflow;
  • the OT domain low-code development tool 10 determines each function block included in the OT domain workflow and the relationship between the function blocks according to the instruction, wherein, for each OT device in the work unit, the OT device to execute The operation is defined by a function block, and the function block is an instance of the operation template 50 of the category to which the OT device belongs, and the operation template 50 predefines the operations that the OT device of this type can perform;
  • S503 The OT domain low-code development tool 20 generates an OT domain workflow according to the determined functional blocks and the relationship between the functional blocks.
  • the OT domain low-code development tool 10 deploys the OT domain workflow to the runtime 30 of the main controller of the work unit, so that each OT device in the work unit connected to the main controller follows the OT domain workflow perform an action.
  • the OT domain microservice generator 20 generates a microservice 40 based on the OT domain workflow, so that the IT domain code development tool 301 realizes that the equipment in the IT domain invokes the microservice 40 through a data platform 200 to trigger the main controller of the work unit
  • the runtime 30 executes OT domain workflows.
  • the OT domain microservice generator 20 can generate the API of the microservice 40 based on the OT domain workflow, wherein, the processing procedure in the API includes the operation of each functional block in the OT domain workflow, and the input parameters of the API are OT domain work flow The parameters obtained by the input port of the flow, and the output parameters of the API are the parameters output by the output port of the OT domain workflow.
  • S506 The OT domain microservice generator 20 or a third-party device 60 registers the microservice 40 on the data platform 200, so that the IT domain code development tool 301 realizes that the equipment in the IT domain discovers the connected microservice 40 through the data platform 200.
  • FIG. 6 shows a way of hardware implementation of the OT domain low-code development platform 100 provided by the embodiment of the present invention.
  • the aforementioned OT domain low-code development tool 10, OT domain microservice generator 20, runtime 30, and third-party device 60 can all be implemented as individual hardware devices, such as servers, workstations, single-chip microcomputers or processing chips. Alternatively, these devices are implemented on the same hardware device, which is stored in at least one memory as a software program, and is called by at least one processor to implement the aforementioned OT domain low-code development method 500 .
  • the operation template 50 and the generated microservices 40 can be stored in at least one memory.
  • the OT domain low-code development platform 100 may include: at least one memory 101 including a computer-readable medium, such as random access memory (RAM). At least one processor 102 coupled with at least one memory 101 may also be included. Computer-executable instructions are stored in at least one memory 101 and, when executed by at least one processor 102, cause at least one processor 102 to perform the steps described herein.
  • at least one processor 102 may include a microprocessor, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a state machine, and the like.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • state machine and the like.
  • Examples of computer readable media include, but are not limited to, floppy disks, CD-ROMs, magnetic disks, memory chips, ROM, RAM, ASICs, configured processors, all-optical media, magnetic tape or other magnetic media, or from which a computer processor can Any other medium that reads instructions.
  • various other forms of computer-readable media can transmit or carry instructions to the computer, including routers, private or public networks, or other wired and wireless transmission devices or channels. Instructions may include code in any computer programming language, including C, C++, C++, Visual Basic, java, and JavaScript.
  • At least one memory 101 shown in FIG. 3 may contain a program 11 for generating OT domain workflow, so that at least one processor 102 executes the OT domain low-code development method 500 described in the embodiment of the present invention.
  • the OT domain low-code development program 11 may include the following program modules: an OT domain low-code development tool 10 , and optionally, an OT domain microservice generator 20 , a runtime 30 , and a third-party device 60 .
  • the OT domain low-code development tool 10 can be a lightweight web-based application program, which can be implemented on an industrial site (such as an edge device or a local server), or on a cloud (such as a public cloud such as AWS or such as OpenStack) private cloud).
  • Its visual engineering paradigm is derived from Function Block Typed Diagram (FBTD).
  • FBTD Function Block Typed Diagram
  • the OT domain microservice generator 20 can use modern translation programming languages to generate standard APIs such as RESTful or RPC.
  • Runtime 30 can easily implement OT domain workflow and provide openness based on the ecosystem of open source communities (such as Python).
  • the runtime 30 can be deployed on an embedded IoT device such as a single board computer (Single Board Computer, SBC).
  • the OT domain low-code development platform 100 may also include a communication interface 103 to realize communication with other devices, such as communication with the data platform 200 .
  • the embodiments of the present invention may include devices having architectures different from those shown in FIG. 6 .
  • the above architecture is only exemplary, and is used to explain the OT domain low-code development method 500 provided by the embodiment of the present invention.
  • the embodiments of the present invention also provide a computer-readable medium, where computer-readable instructions are stored on the computer-readable medium.
  • the processor executes the aforementioned OT domain low code development method.
  • Examples of computer readable media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tape, non- Volatile memory card and ROM.
  • the computer readable instructions may be downloaded from a server computer or cloud by a communication network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本发明实施例涉及OT域低代码开发技术，尤其涉及一种OT域低代码开发平台、方法和计算机可读介质。其中，OT域低代码开发工具10接收用户在图形用户界面上输入的指令以生成一个OT域工作流，所述OT域工作流用于定义OT域中一个工作单元要执行的操作，根据所述指令确定所述OT域工作流中所包括的各个功能块和功能块之间的相互关系，其中，对于所述工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板（50）的实例，所述操作模板（50）预先定义该类OT设备能够执行的操作，以及按照确定的各个功能块和功能块之间的相互关系，生成所述OT域工作流。

Description

OT域低代码开发方法、平台和计算机可读介质 技术领域
本发明实施例涉及OT域低代码开发技术，尤其涉及一种OT域低代码开发方法、平台和计算机可读介质。
背景技术
[根据细则91更正 07.12.2021]　
目前，市场上存在诸多IT低代码开发工具或平台。其中，部分工具或平台对物联网的使用场景，面向有经验的IT工程师，而OT工程师和初级IT工程师则难以理解其范式。而另一些工具或平台更适用于IT域低代码开发的使用场景，不能很好地适用于OT域。
因此，急需适用于OT域的低代码开发方案。
发明内容
本发明实施例提供一种OT域低代码开发方法、平台和计算机可读介质。预先定义各类OT设备能够执行的操作模板，通过将模板实例化为功能块并进而组合成OT域工作流，从而更加适用于OT域的代码开发，并且提供图形用户界面供用户输入指令，以生成各个功能块并基于功能块之间的关系最终形成OT域工作流，实现了低代码开发。
第一方面，提供一种OT域低代码开发方法，该方法可由OT域低代码开发平台执行。该平台中的OT域低代码开发工具接收用户在图形用户界面上输入的指令，所述指令用于生成一个OT域工作流，根据所述指令确定所述OT域工作流中所包括的各个功能块和功能块之间的相互关系，并按照确定的各个功能块和功能块之间的相互关系，生成所述OT域工作流。其中，对于所述工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板的实例，所述操作模板预先定义该类OT设备能够执行的操作；所述OT域工作流用于定义OT域中一个工作单元要执行的操作，其中，所述工作单元的主控制器连接所述工作单元中的各OT设备，以控制各OT设备按照所述OT域工作流的定义完成所述工作单元要执行的操作。
第二方面，提供一种OT域低代码开发平台，包括用于执行第一方面提供的方法中各步骤的组成部分。
第三方面，提供一种OT域低代码开发平台，包括：至少一个存储器，被配置为存储计 算机可读代码；至少一个处理器，被配置为调用所述计算机可读代码，执行第一方面提供的方法中各步骤。
第四方面，提供一种计算机可读介质，所述计算机可读介质上存储有计算机可读指令，所述计算机可读指令在被处理器执行时，使所述处理器执行第一方面提供的方法中各步骤。
第五方面，提供一种计算机程序产品，所述计算机程序产品被有形地存储在计算机可读介质上并且包括计算机可读指令，所述计算机可读指令在被执行时使至少一个处理器执行第一方面提供的方法中各步骤。
对于上述任一方面，可选地，所述OT域低代码开发工具还将所述OT域工作流部署到所述工作单元的主控制器的运行时上，以使得连接到该主控制器上的所述工作单元中的各个OT设备按照所述OT域工作流执行操作。这样，实现了OT域工作流控制工作单元操作的目的。
对于上述任一方面，可选地，OT域低代码开发平还包括一个OT域微服务生成器，其基于所述OT域工作流生成一个微服务，以使得IT域代码开发工具实现IT设备通过一个数据平台调用所述微服务而触发所述工作单元的主控制器的运行时执行所述OT域工作流。这样，通过数据平台，IT设备可以调用基于OT域工作流生成的微服务，从而触发OT工作流的执行，实现了IT域和OT域的融合。
对于上述任一方面，可选地，所述OT域微服务生成器或一个第三方装置在所述数据平台上注册所述微服务，以使得所述IT域代码开发工具实现IT设备通过所述数据平台发现已连接的所述微服务。当微服务的数量较多时，通过在数据平台上注册微服务，从而实现IT设备可以发现已连接的微服务，更加有效地实现了IT设备对微服务的调用，加强了OT域和IT域的融合。
对于上述任一方面，可选地，所述OT域微服务生成器基于所述OT域工作流生成所述微服务的API，其中，所述API中的处理过程包括所述OT域工作流中各个功能块的操作，所述API的输入参数为所述OT域工作流的的输入端口获取的参数，所述API的输出参数为所述OT域工作流的输出端口输出的参数。这里，提供了基于OT域工作流生成微服务的具体方案，实现了基于功能块的OT域工作流向微服务的自动转换。
对于上述任一方面，可选地，所述操作模板遵循与所述主控制器的运行时交互的信息模型。这样，实现了OT域工作流与各种主控制器的兼容，使得主控制器的运行时能够正确解析OT域工作流想要实现的操作，从而实现了工作单元操作的完成。
附图说明
图1～图4为本发明各实施例提供的OT域低代码开发平台的示意图。
图5为本发明实施例提供的OT域低代码开发方法的流程图。
图6为本发明实施例提供的OT域低代码开发平台硬件实现的示意图。
附图标记列表：
100：OT域低代码开发平台
10：OT域低代码开发工具              20：OT域微服务生成器
30：工作单元的主控制器上的运行时    40：微服务    50：操作模板
60：第三方装置
200：数据平台
300：IT域的代码开发平台
301：IT域的代码开发工具
101：至少一个存储器    102：至少一个处理器    103：通信接口
11：OT域低代码开发程序
500：本发明实施例提供的OT域低代码开发方法
S501～S506：方法500的步骤
具体实施方式
现在将参考示例实施方式讨论本文描述的主题。应该理解，讨论这些实施方式只是为了使得本领域技术人员能够更好地理解从而实现本文描述的主题，并非是对权利要求书中所阐述的保护范围、适用性或者示例的限制。可以在不脱离本发明实施例内容的保护范围的情况下，对所讨论的元素的功能和排列进行改变。各个示例可以根据需要，省略、替代或者添加各种过程或组件。例如，所描述的方法可以按照与所描述的顺序不同的顺序来执行，以及各个步骤可以被添加、省略或者组合。另外，相对一些示例所描述的特征在其它例子中也可以进行组合。
如本文中使用的，术语“包括”及其变型表示开放的术语，含义是“包括但不限于”。术语“基于”表示“至少部分地基于”。术语“一个实施例”和“一实施例”表示“至少一个实施例”。术语“另一个实施例”表示“至少一个其他实施例”。术语“第一”、“第二”等可以指代不同的或相同的对象。下面可以包括其他的定义，无论是明确的还是隐含的。除非上下文中明确地指明，否则一个术语的定义在整个说明书中是一致的。
下面结合附图对本发明实施例进行详细说明。
图1示出了本发明实施例提供的一种OT域低代码开发平台100，该平台100用于实现OT域的低代码开发。
根据Gartner的定义，运营技术(Operational Technology，OT)集合了硬件和软件，通过直接地监视和/或控制物理设备(称为OT设备)，检测或触发企业中过程的变化或发生的事件。OT利用计算机监视或改变诸如工业控制系统(Industrial Control System，ICS)的物理状态。其中，工业控制系统是基于计算机实现的设施、系统和设备，用于远程监视和/或控制关键的工业过程，实现物理功能。“OT”这个词的叫法用于将工业控制系统和传统的信息技术(Information Technology，IT)系统在技术实现和功能上加以区分。
如前所述，目前还没有一种适用于OT域的低代码开发工具和平台。图1所示的平台100中，由于预先定义了各类OT设备能够执行操作的操作模板50(可视为提供了OT域的能力)，可以方便且快捷地基于操作模板50生成各个功能块，进而组装成OT域工作流，从而实现了适用于OT域的低代码开发。开发工程师无需对各类OT设备有深入的理解，即能实现OT域开发。这里，OT设备可包括但不限于：物联网(Internet of Things，IoT)设备、可编程逻辑控制器(Programmable Logic Controller，PLC)、机器人(Robotics)、人工过程(Manual Process)、工控机(Industrial Personal Computer，IPC)等。
并且，提出了“工作单元”的概念，使得开发更贴近于一个相对完整和独立的控制流程和操作，更符合工业控制的特点，提高了开发的集成度，降低了开发的复杂度。这里，可以根据实际的工业场景定义工作单元，比如：生产线上的一个工位对应一个工作单元等，不同的工作单元的工艺流程不同。
具体地，如图1所示，OT域低代码开发平台100可包括：
一个OT域低代码开发工具10，该OT域低代码开发工具10可被配置为：
-接收用户在图形用户界面上输入的指令，指令用于生成一个OT域工作流，OT域工作流用于定义OT域中一个工作单元要执行的操作，其中，工作单元的主控制器连接工作单元中的各OT设备，以控制各OT设备按照OT域工作流的定义完成工作单元要执行的操作；
-根据指令确定OT域工作流中所包括的各个功能块和功能块之间的相互关系，其中，对于工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板50的实例，操作模板50预先定义该类OT设备能够执行的操作，以及
-按照确定的各个功能块和功能块之间的相互关系，生成OT域工作流。
其中，各类OT设备能执行的操作的操作模板50可以图标的形式列举在图形用户界面上，用户可通过选择、拖拽图标到画布上的方式来确定OT设备需要执行的操作，并且可通过设置操作的具体参数来进一步设置精确的操作。用户选择操作模板50、拖拽操作模板50、设置操作的参数等均可视为用户在图形用户界面上输入的指令。OT域低代码开发工具10在接收到该指令后，按照指令获取操作模板50的信息，并生成操作模板50的实例(在操作模板50实例化的过程中，达到精确设置OT设备操作的目的)。通常一个工作单元要执行的操作，即OT域工作流中定义的操作不止一项，因此通常要包括多个功能块，按照操作的顺序和相互关系，确定OT域工作流中包括的各个功能块和功能块之间的相互关系，并据此生成OT域工作流。
进一步地，如图2所示，OT域低代码开发平台100还可包括上述工作单元的主控制器的运行时30。OT域低代码开发工具10可将生成的OT域工作流部署到工作单元的主控制器的运行时30上，以使得连接到该主控制器上的该工作单元中的各个OT设备按照OT域工作流执行操作。
图1和图2所示的OT域低代码开发平台100的组成仅涉及OT域。但IT域与OT域融合对于企业数字化转型已经变得越来越重要。需要实现的是企业如何采用一种易懂且非IT编程的方式来控制OT域的流程。图3所示的OT域低代码开发平台100解决了如何通过IT域的代码开发平台300来控制OT域的流程。如图3所示，OT域低代码开发平台100在图2所示的结构基础上，还可进一步包括一个OT域微服务生成器20，其可基于OT域工作流生成微服务40。这样，IT域代码开发工具301即可通过编程实现IT设备通过一个数据平台200调用微服务40而触发工作单元的主控制器的运行时30执行OT域工作流。从而实现了IT域的代码开发平台300对OT域流程的控制，即实现了IT域和OT域的融合。这里，微服务40是OT域微服务生成器20基于OT域工作流自动生成的，无需IT域的代码开发工具301理解OT域工作流的细节，仅需获取微服务40的标识(比如：名称)和IP地址即可，无需IT域的开发人员了解OT域设备和控制流程，容易实现和理解。这里，IT设备可包括但不限于：制造运营管理(Manufacturing Operation Management，MOM)系统、制造执行系统(manufacturing execution system，MES)、企业资源计划(Enterprise Resource Planning，ERP)系统、企业服务总线(Enterprise Service Bus，ERP)、产品生命周期管理(Product Lifecycle Management，PLM)系统等。
若要实现IT域能够调用微服务40，则需要IT域能够获取微服务40的信息。可实现的方式包括但不限于以下两种：
方式一、
在方式一中，OT域的代码开发人员可将生成的各微服务40的名称和IP地址通知IT域的代码开发人员，这样，IT域的代码开发人员在开发过程中可直接将各微服务40的信息写入代码中，从而实现IT设备对微服务40的调用。方式一比较适合微服务数量较少的场景。
方式二、
在方式二中，可采用注册、发现机制。其中，可在数据平台200上注册各微服务40，这样IT域代码开发工具301则可通过代码开发实现IT域设备通过数据平台200发现已连接的微服务40。而完成微服务40注册的装置可以使OT域微服务生成器20或一个第三方装置60(如图4所示)。该第三方装置60可以视为OT域低代码开发平台100的一部分，或者在数据平台200中实现。方式二比较适合微服务数量较多的场景。
可选地，OT域微服务生成器20可基于OT域工作流生成微服务40的API，其中，API中的处理过程可包括OT域工作流中各个功能块的操作，API的输入参数为OT域工作流的的输入端口获取的参数，API的输出参数为OT域工作流的输出端口输出的参数。
可选地，上述操作模板50遵循与主控制器的运行时30交互的信息模型。这样，实现了OT域工作流与各种OT设备的主控制器之间的通信的标准化。
图5为本发明实施例提供的OT域低代码开发方法500的流程图，方法500可由OT域低代码开发平台100实现，可包括如下步骤：
S501：OT域低代码开发工具10接收用户在图形用户界面上输入的指令，指令用于生成一个OT域工作流，OT域工作流用于定义OT域中一个工作单元要执行的操作，其中，工作单元的主控制器连接工作单元中的各OT设备，以控制各OT设备按照OT域工作流的定义完成工作单元要执行的操作；
S502：OT域低代码开发工具10根据指令确定OT域工作流中所包括的各个功能块和功能块之间的相互关系，其中，对于工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板50的实例，操作模板50预先定义该类OT设备能够执行的操作；
S503：OT域低代码开发工具20按照确定的各个功能块和功能块之间的相互关系，生成OT域工作流。
S504：OT域低代码开发工具10将OT域工作流部署到工作单元的主控制器的运行时30上，以使得连接到该主控制器上的工作单元中的各个OT设备按照OT域工作流执行操作。
S505：OT域微服务生成器20基于OT域工作流生成一个微服务40，以使得IT域代码开发工具301实现IT域的设备通过一个数据平台200调用微服务40而触发工作单元的主控 制器的运行时30执行OT域工作流。具体地，OT域微服务生成器20可基于OT域工作流生成微服务40的API，其中，API中的处理过程包括OT域工作流中各个功能块的操作，API的输入参数为OT域工作流的的输入端口获取的参数，API的输出参数为OT域工作流的输出端口输出的参数。
S506：OT域微服务生成器20或一个第三方装置60在数据平台200上注册微服务40，以使得IT域代码开发工具301实现IT域的设备通过数据平台200发现已连接的微服务40。
图6示出了本发明实施例提供的OT域低代码开发平台100的硬件实现的一种方式。其中，前述的OT域低代码开发工具10、OT域微服务生成器20、运行时30、第三方装置60均可实现为单独的各个硬件设备，比如：服务器、工作站、单片机或处理芯片。或者，这些装置在同一台硬件设备上实现，其作为软件程序存储在至少一个存储器中，通过至少一个处理器的调用来实现前述的OT域低代码开发方法500。其中，操作模板50和生成的各个微服务40可存储在至少一个存储器中。
具体地，如图6所示，OT域低代码开发平台100可包括：至少一个存储器101，其包括计算机可读介质，例如随机存取存储器(RAM)。还可包括与至少一个存储器101耦合的至少一个处理器102。计算机可执行指令存储在至少一个存储器101中，并且当由至少一个处理器102执行时，可以使至少一个处理器102执行本文所述的步骤。其中，至少一个处理器102可以包括微处理器、专用集成电路(ASIC)、数字信号处理器(DSP)、中央处理单元(CPU)、图形处理单元(GPU)、状态机等。计算机可读介质的实施例包括但不限于软盘、CD-ROM、磁盘，存储器芯片、ROM、RAM、ASIC、配置的处理器、全光介质、所有磁带或其他磁性介质，或计算机处理器可以从中读取指令的任何其他介质。此外，各种其它形式的计算机可读介质可以向计算机发送或携带指令，包括路由器、专用或公用网络、或其它有线和无线传输设备或信道。指令可以包括任何计算机编程语言的代码，包括C、C++、C语言、Visual Basic、java和JavaScript。
图3中所示的至少一个存储器101可以包含生成OT域工作流的程序11，使得至少一个处理器102执行本发明实施例中所述的OT域低代码开发方法500。OT域低代码开发程序11可以包括如下程序模块：OT域低代码开发工具10，可选地，还可包括OT域微服务生成器20、运行时30、第三方装置60。
其中，OT域低代码开发工具10可以为轻量级的基于web的应用程序，可在工业现场(比如边缘设备或本地服务器)上实现，也可在云端(诸如AWS的公共云或诸如OpenStack的私有云)上实现。其可视化的工程范式源于功能块类型图表(Funtion Block Typed Diagram， FBTD)。OT域微服务生成器20可使用现代的翻译编程语言来生成诸如RESTful或RPC的标准API。运行时30可简单地实现OT域工作流，并基于开源社区(比如Python)的生态系统提供开放性。运行时30可部署在诸如单板计算机(Single Board Computer，SBC)的嵌入式IoT设备上。
此外，OT域低代码开发平台100还可包括一个通信接口103，实现与其他设备之间的通信，比如与数据平台200之间通信。
应当提及的是，本发明实施例可以包括具有不同于图6所示架构的装置。上述架构仅仅是示例性的，用于解释本发明实施例提供的OT域低代码开发方法500。
此外，本发明实施例实施例还提供一种计算机可读介质，该计算机可读介质上存储有计算机可读指令，计算机可读指令在被处理器执行时，使处理器执行前述的OT域低代码开发方法。计算机可读介质的实施例包括软盘、硬盘、磁光盘、光盘(如CD-ROM、CD-R、CD-RW、DVD-ROM、DVD-RAM、DVD-RW、DVD+RW)、磁带、非易失性存储卡和ROM。可选地，可以由通信网络从服务器计算机上或云上下载计算机可读指令。
需要说明的是，上述各流程和各系统结构图中不是所有的步骤和模块都是必须的，可以根据实际的需要忽略某些步骤或模块。各步骤的执行顺序不是固定的，可以根据需要进行调整。上述各实施例中描述的系统结构可以是物理结构，也可以是逻辑结构，即，有些模块可能由同一物理实体实现，或者，有些模块可能分由多个物理实体实现，或者，可以由多个独立设备中的某些部件共同实现。

Claims (15)

  1. 一种OT域低代码开发平台(100)，包括：一个OT域低代码开发工具(10)，其特征在于，所述OT域低代码开发工具(10)被配置为：
    -接收用户在图形用户界面上输入的指令，所述指令用于生成一个OT域工作流，所述OT域工作流用于定义OT域中一个工作单元要执行的操作，其中，所述工作单元的主控制器连接所述工作单元中的各OT设备，以控制各OT设备按照所述OT域工作流的定义完成所述工作单元要执行的操作；
    -根据所述指令确定所述OT域工作流中所包括的各个功能块和功能块之间的相互关系，其中，对于所述工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板(50)的实例，所述操作模板(50)预先定义该类OT设备能够执行的操作，以及
    -按照确定的各个功能块和功能块之间的相互关系，生成所述OT域工作流。
  2. 如权利要求1所述的平台，其特征在于，所述OT域低代码开发工具(10)还被配置为：
    -将所述OT域工作流部署到所述工作单元的主控制器的运行时(30)上，以使得连接到该主控制器上的所述工作单元中的各个OT设备按照所述OT域工作流执行操作。
  3. 如权利要求2所述的平台，其特征在于，还包括一个OT域微服务生成器(20)，被配置为：
    -基于所述OT域工作流生成一个微服务(40)，以使得IT域代码开发工具(301)实现IT设备通过一个数据平台(200)调用所述微服务(40)而触发所述工作单元的主控制器的运行时(30)执行所述OT域工作流。
  4. 如权利要求3所述的平台，其特征在于，
    -所述OT域微服务生成器(20)还被配置为在所述数据平台(200)上注册所述微服务(40)，以使得所述IT域代码开发工具(301)实现IT设备通过所述数据平台(200)发现已连接的所述微服务(40)；或者
    -所述平台还包括一个第三方装置(60)，被配置为在所述数据平台(200)上注册所述微服务(40)，以使得所述IT域代码开发工具(301)实现IT设备通过所述数据平台(200)发现已连接的所述微服务(40)。
  5. 如权利要求3所述的平台，其特征在于，所述OT域微服务生成器(20)在基于所述OT域工作流生成一个微服务(40)时，被具体配置为：
    -基于所述OT域工作流生成所述微服务(40)的API，其中，所述API中的处理过程包括所述OT域工作流中各个功能块的操作，所述API的输入参数为所述OT域工作流的的输入端口获取的参数，所述API的输出参数为所述OT域工作流的输出端口输出的参数。
  6. 如权利要求2所述的平台，其特征在于，所述操作模板(50)遵循与所述主控制器的运行时(30)交互的信息模型。
  7. 一种OT域低代码开发方法(400)，其特征在于，包括：
    -OT域低代码开发工具(10)接收(S501)用户在图形用户界面上输入的指令，所述指令用于生成一个OT域工作流，所述OT域工作流用于定义OT域中一个工作单元要执行的操作，其中，所述工作单元的主控制器连接所述工作单元中的各OT设备，以控制各OT设备按照所述OT域工作流的定义完成所述工作单元要执行的操作；
    -所述OT域低代码开发工具(10)根据所述指令确定(S502)所述OT域工作流中所包括的各个功能块和功能块之间的相互关系，其中，对于所述工作单元中的每一个OT设备，该OT设备要执行的操作由功能块定义，功能块是该OT设备所属类别的操作模板(50)的实例，所述操作模板(50)预先定义该类OT设备能够执行的操作；
    -所述OT域低代码开发工具(20)按照确定的各个功能块和功能块之间的相互关系，生成(S503)所述OT域工作流。
  8. 如权利要求7所述的方法，其特征在于，在所述OT域低代码开发工具(10)生成(S503)所述OT域工作流之后，还包括：
    -所述OT域低代码开发工具(10)将所述OT域工作流部署(S504)到所述工作单元的主控制器的运行时(30)上，以使得连接到该主控制器上的所述工作单元中的各个OT设备按照所述OT域工作流执行操作。
  9. 如权利要求8所述的方法，其特征在于，在所述OT域低代码开发工具(10)生成(S503)所述OT域工作流之后，还包括：
    -OT域微服务生成器(20)基于所述OT域工作流生成(S505)一个微服务(40)，以使得IT域代码开发工具(301)实现IT设备通过一个数据平台(200)调用所述微服务(40) 而触发所述工作单元的主控制器的运行时(30)执行所述OT域工作流。
  10. 如权利要求9所述的方法，其特征在于，在所述OT域微服务生成器(20)基于所述OT域工作流生成(S505)一个微服务(40)之后，还包括：
    -所述OT域微服务生成器(20)或一个第三方装置(60)在所述数据平台(200)上注册(S506)所述微服务(40)，以使得所述IT域代码开发工具(301)实现IT设备通过所述数据平台(200)发现已连接的所述微服务(40)。
  11. 如权利要求9所述的方法，其特征在于，所述OT域微服务生成器(20)基于所述OT域工作流生成(S505)一个微服务(40)，包括：
    -所述OT域微服务生成器(20)基于所述OT域工作流生成所述微服务(40)的API，其中，所述API中的处理过程包括所述OT域工作流中各个功能块的操作，所述API的输入参数为所述OT域工作流的的输入端口获取的参数，所述API的输出参数为所述OT域工作流的输出端口输出的参数。
  12. 如权利要求8所述的方法，其特征在于，所述操作模板(50)遵循与所述主控制器的运行时(30)交互的信息模型。
  13. 一种OT域低代码开发平台(100)，其特征在于，包括：
    至少一个存储器(101)，被配置为存储计算机可读代码；
    至少一个处理器(102)，被配置为调用所述计算机可读代码，执行如权利要求7～12任一项所述的方法中的步骤。
  14. 一种计算机可读介质，其特征在于，所述计算机可读介质上存储有计算机可读指令，所述计算机可读指令在被处理器执行时，使所述处理器执行如权利要求7～12任一项所述的方法中的步骤。
  15. 一种计算机程序产品，其特征在于，所述计算机程序产品被有形地存储在计算机可读介质上并且包括计算机可读指令，所述计算机可读指令在被执行时使至少一个处理器执行根据权利要求7～12中任一项所述的方法。
PCT/CN2021/122421 2021-09-30 2021-09-30 Ot域低代码开发方法、平台和计算机可读介质 Ceased WO2023050408A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2021/122421 WO2023050408A1 (zh) 2021-09-30 2021-09-30 Ot域低代码开发方法、平台和计算机可读介质
EP21958977.7A EP4398092A4 (en) 2021-09-30 2021-09-30 Ot domain low-code development method and platform, and computer-readable medium
US18/697,511 US20240419408A1 (en) 2021-09-30 2021-09-30 OT Domain Low-Code Development Method and Platform, and Computer-Readable Medium
CN202180102255.7A CN117940889A (zh) 2021-09-30 2021-09-30 Ot域低代码开发方法、平台和计算机可读介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/122421 WO2023050408A1 (zh) 2021-09-30 2021-09-30 Ot域低代码开发方法、平台和计算机可读介质

Publications (1)

Publication Number Publication Date
WO2023050408A1 true WO2023050408A1 (zh) 2023-04-06

Family

ID=85781186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/122421 Ceased WO2023050408A1 (zh) 2021-09-30 2021-09-30 Ot域低代码开发方法、平台和计算机可读介质

Country Status (4)

Country Link
US (1) US20240419408A1 (zh)
EP (1) EP4398092A4 (zh)
CN (1) CN117940889A (zh)
WO (1) WO2023050408A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118012403A (zh) * 2024-04-08 2024-05-10 西南林业大学 基于自然语言处理的低代码开发方法、系统及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12306914B2 (en) * 2022-03-16 2025-05-20 Ping Identity International, Inc. Console-based no-code/low-code theme management for authentication journeys

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170083386A1 (en) * 2015-09-17 2017-03-23 Salesforce.Com, Inc. PROCESSING EVENTS GENERATED BY INTERNET OF THINGS (IoT)
CN106933212A (zh) * 2017-04-21 2017-07-07 华南理工大学 一种分布式制造环境下的可重构工业机器人编程控制方法
CN108681444A (zh) * 2018-04-12 2018-10-19 华中科技大学 一种基于xml技术的软plc组态开发方法
US20210096827A1 (en) * 2019-09-26 2021-04-01 Rockwell Automation Technologies, Inc. Industrial programming development with a trained analytic model

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11057282B2 (en) * 2019-06-17 2021-07-06 Sap Se Microservice generation system
US11567737B1 (en) * 2021-09-21 2023-01-31 Rockwell Automation Technologies, Inc. Graphical and text based co-design editor for industrial automation projects

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170083386A1 (en) * 2015-09-17 2017-03-23 Salesforce.Com, Inc. PROCESSING EVENTS GENERATED BY INTERNET OF THINGS (IoT)
CN106933212A (zh) * 2017-04-21 2017-07-07 华南理工大学 一种分布式制造环境下的可重构工业机器人编程控制方法
CN108681444A (zh) * 2018-04-12 2018-10-19 华中科技大学 一种基于xml技术的软plc组态开发方法
US20210096827A1 (en) * 2019-09-26 2021-04-01 Rockwell Automation Technologies, Inc. Industrial programming development with a trained analytic model

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4398092A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118012403A (zh) * 2024-04-08 2024-05-10 西南林业大学 基于自然语言处理的低代码开发方法、系统及存储介质
CN118012403B (zh) * 2024-04-08 2024-06-11 西南林业大学 基于自然语言处理的低代码开发方法、系统及存储介质

Also Published As

Publication number Publication date
CN117940889A (zh) 2024-04-26
EP4398092A4 (en) 2025-05-21
EP4398092A1 (en) 2024-07-10
US20240419408A1 (en) 2024-12-19

Similar Documents

Publication Publication Date Title
EP3501141B1 (en) A network service design and deployment process for nfv systems
CN102542382B (zh) 业务规则的操作方法和装置
US20220075610A1 (en) Node selection method and apparatus
CN102567092B (zh) 组件作用域的创建和终止
US20200057995A1 (en) Extensibility of business logic shared across a business process orchestration engine, a rule engine, and a user interface
WO2019216082A1 (ja) システム構成導出装置およびシステム構成導出方法
CN113067900A (zh) 智能合约的部署方法及装置
WO2023050408A1 (zh) Ot域低代码开发方法、平台和计算机可读介质
CN108134698B (zh) 一种工业多协议物联网关的图形化配置平台
FI3610369T3 (fi) Teknologiat integraatioliittymien luomiseksi ja jakamiseksi pilvipalvelun välitysjärjestelmässä
CN113347060A (zh) 基于流程自动化的电力网络故障检测方法、装置和系统
CN108604996B (zh) 一种nfv系统中的策略传输方法和装置
CN114219325B (zh) 用于动态配置人员的方法、装置、设备及介质
CA3234576A1 (en) Assignment and dynamic application of a permission rule to a group of entities
US20050267795A1 (en) Dynamically assembling business process models
CN103593416B (zh) 一种分布式试验运行中间件异构网关的自动生成方法
WO2019072033A1 (zh) 一种网络方法和系统、及终端
CN102799530A (zh) 一种基于uml架构的软件系统的性能预测方法
CN112433821B (zh) 业务模型的搭建方法、装置、电子设备及介质
WO2023142082A1 (zh) 设备控制方法、装置、平台和计算机可读介质
Liu et al. Completing virtual network embedding all in one mathematical programming
JP5505690B2 (ja) システム設計支援装置、システムの設計支援方法およびシステム設計支援プログラム
CN118661184A (zh) 工作流创建方法、系统、介质及程序产品
US20250094035A1 (en) Information Processing Methods and Apparatus
CN112636968A (zh) 网络方案的构建方法、装置、可读介质以及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21958977

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180102255.7

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2021958977

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021958977

Country of ref document: EP

Effective date: 20240327

WWE Wipo information: entry into national phase

Ref document number: 18697511

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE