WO2022228156A1 - 一种策略编排处理方法、装置、设备、系统及存储介质 - Google Patents

一种策略编排处理方法、装置、设备、系统及存储介质 Download PDF

Info

Publication number
WO2022228156A1
WO2022228156A1 PCT/CN2022/087153 CN2022087153W WO2022228156A1 WO 2022228156 A1 WO2022228156 A1 WO 2022228156A1 CN 2022087153 W CN2022087153 W CN 2022087153W WO 2022228156 A1 WO2022228156 A1 WO 2022228156A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
target
identifier
instruction
iot
Prior art date
Application number
PCT/CN2022/087153
Other languages
English (en)
French (fr)
Inventor
蔡昌俊
俞军燕
厉智
祝唯
陆桥
艾义
谢良
黄朝晖
马安进
陈倩慈
林德辉
彭伟泽
卢红亮
杨禹洲
黎卓虹
殷杰
Original Assignee
广州地铁集团有限公司
腾讯科技（深圳）有限公司
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 广州地铁集团有限公司, 腾讯科技（深圳）有限公司 filed Critical 广州地铁集团有限公司
Publication of WO2022228156A1 publication Critical patent/WO2022228156A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces

Definitions

  • the present application relates to the Internet of Things technology, and in particular, to a business processing method, apparatus, device, and computer-readable storage medium.
  • the output variables of the nodes are defined in the action in advance, which is not suitable for IoT devices with uncertain output variables.
  • IoT devices for example, in the urban rail industry
  • the scenario-based requirements and iterations of industrial control on the business side are complex and changeable, and the device control linkage between different manufacturers and systems is very important. difficulty.
  • Embodiments of the present application provide a service processing method, apparatus, device, and computer-readable storage medium, which can perform codeless configuration of IoT nodes on a policy orchestration interface, and construct linkage control between IoT devices in a codeless manner.
  • the embodiment of the present application provides a service processing method, including:
  • the at least one target node includes an IoT node
  • the configuration information of the target node is obtained, wherein, when the target node is an IoT node, the configuration information includes at least device configuration information and instruction configuration information determined based on the IoT platform , the IoT platform establishes a communication connection with the terminal that performs policy arrangement;
  • the target business process is determined based on the configuration information of each target node.
  • An embodiment of the present application provides a service processing apparatus, including: .
  • a first determination module configured to receive a first selection operation for the node identifier in the policy arrangement interface, and determine at least one selected target node
  • a first presentation module configured to present the at least one target node in the policy orchestration interface, where the at least one target node includes an IoT node;
  • a second presentation module configured to present a configuration interface in response to a configuration operation for the target node
  • the first obtaining module is configured to obtain the configuration information of the target node in response to the input operation received through the configuration interface, wherein, when the target node is an IoT node, the configuration information at least includes the information determined based on the IoT platform.
  • Device configuration information and instruction configuration information the IoT platform establishes a communication connection with the terminal that performs policy programming;
  • the second determination module is configured to determine the target business process based on the configuration information of each target node when receiving the strategy arrangement completion operation.
  • the configuration interface includes a device configuration interface and an instruction configuration interface
  • the first acquisition module is further configured to:
  • the device configuration interface In response to the device setting operation received through the device configuration interface, obtain device configuration information corresponding to the IoT node, where the device configuration information includes a device identifier;
  • an instruction configuration interface is presented, the instruction configuration interface is dynamically generated based on the object model information of the IoT device;
  • a configured device instruction is obtained.
  • the apparatus further includes:
  • a first sending module configured to send an acquisition request for object model information to the IoT platform, where the acquisition request carries each device identifier;
  • a first receiving module configured to receive an acquisition response sent by the IoT platform, and acquire information of each object model corresponding to each device identifier carried in the acquisition response;
  • the second acquisition module is used to parse the object model information and acquire the output parameter definition of the configured device instruction
  • an information generation module configured to dynamically generate the output description information of the IoT node based on each device identifier, device instruction and output parameter definition;
  • the mounting module is configured to mount the output description information on the device class output parameter of the IoT node.
  • the information generation module is also used to:
  • the hierarchical structure from device to instruction to output parameter establish a one-to-one correspondence between the device identifier, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction;
  • the output description information of the IoT node is dynamically generated according to the device identifier in each corresponding relationship, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction according to a preset description format.
  • the first obtaining module is further used for:
  • the selected at least one device identification is acquired.
  • the apparatus further includes:
  • the third acquisition module is used to acquire the information of each object model corresponding to each device identifier
  • a grouping module configured to configure and group each device identifier based on the information of each object model, and obtain a grouping result, wherein the grouping result includes at least one grouping identifier and a device identifier corresponding to each grouping identifier;
  • the third presentation module is configured to present the respective grouping identifiers and the device identifiers corresponding to the respective grouping identifiers on the grouping interface.
  • the grouping interface presents an entry for batch configuration of instructions
  • the apparatus further includes:
  • a selection module configured to select all device identifiers corresponding to the group identifier in response to the fourth selection operation for the group identifier; or,
  • a fourth obtaining module configured to obtain a plurality of selected device identities in response to the fifth selection operation for the plurality of device identities
  • the third determining module is configured to determine that a trigger operation for the instruction configuration entry is received when a trigger operation for the instruction batch configuration entry is received.
  • the grouping interface presents a separate configuration entry for instructions
  • the apparatus further includes:
  • a fifth acquisition module configured to acquire the selected device identification in response to the sixth selection operation for a device identification
  • the fourth determination module is configured to determine that a trigger operation for the instruction configuration entry is received when a trigger operation for the instruction separate configuration entry is received.
  • the first obtaining module is further used for:
  • each optional instruction identifier In the instruction configuration interface, each optional instruction identifier, the parameter identifier corresponding to each optional instruction identifier, and the data source setting entry of each parameter identifier are presented.
  • the first obtaining module is further used for:
  • the configured device instruction is determined based on the target instruction identification, the target parameter identification and the assignment information.
  • the data source setting interface displays at least the following data sources: manual input, constants, input from the policy user, selection from other nodes of the policy, and the first acquisition module is also used for:
  • the target source node When the target source node is an action node, present at least one output parameter identifier of the target source node in response to a triggering operation for the output parameter selection entry, and determine the target output based on the tenth selection operation for the at least one output parameter identifier parameter identifier;
  • the output value of the target output parameter identifier is determined as the assignment information of the target parameter identifier.
  • the first obtaining module is further used for:
  • an output parameter selection interface is presented in response to a trigger operation for the output parameter selection entry, and the output parameter selection interface displays at least one optional output parameter of the target source node, so
  • the optional output parameters described above include device-type output parameters and non-device-type output parameters
  • the assignment information of the target parameter identifier is determined.
  • the output parameter setting interface includes a device identification selection entry, a device instruction selection entry, and an output parameter selection entry of the IoT node, and the first acquisition module is further configured to:
  • the target device identifier determines the target device identifier, target device instruction and target output parameter identifier through triggering operations for the device identifier selection entry, the device instruction selection entry and the output parameter selection entry respectively;
  • the assignment information of the target parameter identifier is determined based on the target device identifier, the target device instruction and the target output parameter identifier, wherein the target assignment information is after the IoT device corresponding to the target device identifier executes the target device instruction
  • the target output parameter identifies corresponding output information.
  • the first obtaining module is further configured to:
  • the target action and the output parameter information are determined as configuration information of the target node.
  • the second determining module is further configured to:
  • the device also includes:
  • the sixth determining module is configured to determine connection information between different target nodes based on the binding relationship, and connect the corresponding target nodes based on the connection information.
  • An embodiment of the present application provides a service processing device, including:
  • the processor is configured to implement the methods provided by the embodiments of the present application when executing the executable instructions stored in the memory.
  • An embodiment of the present application provides a business processing system, including: a business processing device, an IoT platform, and an IoT device, wherein a communication connection is established between the business processing device and the IoT platform, and the IoT platform is connected to the IoT platform. A communication connection is established between the IoT devices;
  • the IoT platform is used for device grouping of the IoT devices, determining device labels, and managing object models;
  • the service processing device uses the device grouping information, device label information and object model provided by the IoT platform to perform policy arrangement according to the method described above.
  • Embodiments of the present application provide a computer-readable storage medium storing executable instructions for causing a processor to execute the methods provided by the embodiments of the present application.
  • Embodiments of the present application provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the foregoing method provided by the embodiments of the present application.
  • the strategy arrangement after receiving the first selection operation for the node identifier in the strategy arrangement interface, at least one selected target node is determined, and the at least one target node is presented in the strategy arrangement interface, and the at least one target node is at least one target node.
  • Including IoT nodes then configure each target node, and present a configuration interface in response to a configuration operation for the target node; in response to an input operation received through the configuration interface, obtain the configuration information of the target node, wherein when the target node is configured
  • the configuration information includes at least the device configuration information and instruction configuration information determined based on the IoT platform.
  • the target business process is determined based on the configuration information of each target node.
  • the IoT node when the IoT node needs to be orchestrated in the policy, the IoT node can be configured with codeless device instructions through the policy orchestration interface, so as to realize the construction of the IoT device in a codeless manner.
  • the linkage control improve the efficiency of industrial control.
  • FIG. 1 is a schematic diagram of a network architecture of a service processing system provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an implementation flow of the service processing method provided by the embodiment of the present application.
  • FIG. 4 is a schematic flow chart of the implementation of determining the assignment information of the target parameter identifier provided by the embodiment of the present application;
  • FIG. 5 is a schematic flowchart of yet another implementation of the service processing method provided by the embodiment of the present application.
  • FIG. 6 is a schematic diagram of a system architecture of a service processing method provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of still another system architecture of a business processing method applied in an urban rail scenario provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the generation process of the output variable of the IoT node provided by the embodiment of the present application.
  • FIG. 9 is a schematic diagram of a strategy provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a device configuration interface provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of an interface after grouping based on an object model provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of an instruction configuration interface provided by an embodiment of the present application.
  • 13 is a schematic diagram of an interface in which the data source provided by this embodiment of the present application is selected from other nodes of this policy;
  • FIG. 14 is a schematic diagram of an interface for setting a data source of an action node according to an embodiment of the present application
  • FIG. 15 is a schematic diagram of an interface for binding an output variable of an IoT node to an input variable of another node according to an embodiment of the present application.
  • first ⁇ second ⁇ third is only used to distinguish similar objects, and does not represent a specific ordering of objects. It is understood that “first ⁇ second ⁇ third” Where permitted, the specific order or sequence may be interchanged to enable the embodiments of the application described herein to be practiced in sequences other than those illustrated or described herein.
  • Object model It is a digital representation of a device in the physical space in the cloud. It describes what the device is, what it can do, and what information it can provide externally from three dimensions: attributes, services, and events.
  • IoT platform Provides device connectivity and communication capabilities, supports device management, object model definition and other functions.
  • Process orchestration A complete business process can be realized by combining atomic services on the interactive interface.
  • Strategy platform Provides non-coding business process orchestration capabilities, execution capabilities and monitoring capabilities.
  • Action node a node in the process orchestration of the policy platform, which realizes the function of the node by referring to the actual action (service).
  • IoT node a special action node that combines IoT technology and has the ability to control equipment.
  • Action The atomic service composed of the business application programming interface (API, Application Programming Interface) is encapsulated by a certain standard, and the input parameters and output parameters are defined for the use of process orchestration.
  • API Application Programming Interface
  • the embodiments of the present application provide a business processing method, apparatus, device, and computer-readable storage medium, which can perform code-free configuration of IoT nodes on a policy orchestration interface, and construct linkage control between IoT devices in a code-free manner.
  • the following Exemplary applications of the service processing devices provided by the embodiments of the present application are described.
  • the service processing devices provided by the embodiments of the present application may be implemented as notebook computers, tablet computers, desktop computers, set-top boxes, mobile devices (for example, mobile phones, portable music players) , personal digital assistants, dedicated messaging devices, portable game devices), vehicle-mounted devices and other types of user terminals can also be implemented as servers.
  • exemplary applications when the device is implemented as a terminal will be described.
  • FIG. 1 is a schematic diagram of a network architecture of a service processing system 100 provided by an embodiment of the present application.
  • the IoT platform 300 and the terminal 400, the IoT device 200 and the IoT platform 300, and the IoT platform 300 and the terminal 400 are connected through a network (not shown in FIG. 1), the network may be a wide area network or a local area network, Or a combination of the two.
  • the IoT platform 300 acquires the device information of each IoT device 200, groups the IoT devices, and determines the object model of each IoT device.
  • a policy orchestration client may be installed in the terminal 400, or the terminal 400 may open a policy orchestration engine through a browser to perform policy orchestration.
  • various nodes are displayed in the strategy arrangement interface, such as start node, end node, action node, IoT node, rule node, etc.
  • the display icons or display colors of different types of nodes are different . Users can determine each target node involved in policy execution according to their own business requirements, and move the target node to the editing area of the policy orchestration interface by dragging and dropping.
  • the dragged target node can be the start node, end node, action Any one or more of nodes, IoT nodes, and rule nodes, and then configure the target node.
  • the terminal will set the IoT device information associated with the IoT node through the IoT platform and Through the object model information provided by the IoT platform, the command configuration of the IoT device is performed through the visual interface, so as to realize the code-free configuration of the IoT device.
  • the IoT platform may be an IoT server, and the IoT server may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud service, cloud Cloud servers for basic cloud computing services such as databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.
  • the terminal 400 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a vehicle terminal, etc., but is not limited thereto.
  • FIG. 2 is a schematic structural diagram of a terminal 400 provided by an embodiment of the present application.
  • the terminal 400 shown in FIG. 2 includes: at least one processor 410 , a memory 450 , at least one network interface 420 and a user interface 430 .
  • the various components in terminal 400 are coupled together by bus system 440 . It is understood that the bus system 440 is used to implement the connection communication between these components.
  • the bus system 440 also includes a power bus, a control bus, and a status signal bus. For clarity, however, the various buses are labeled as bus system 440 in FIG. 2 .
  • the processor 410 may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where a general-purpose processor may be a microprocessor or any conventional processor or the like.
  • DSP Digital Signal Processor
  • User interface 430 includes one or more output devices 431 that enable presentation of media content, including one or more speakers and/or one or more visual display screens.
  • User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, and other input buttons and controls.
  • Memory 450 may be removable, non-removable, or a combination thereof.
  • Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like.
  • Memory 450 optionally includes one or more storage devices that are physically remote from processor 410 .
  • Memory 450 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM, Read Only Memory), and the volatile memory may be a random access memory (RAM, Random Access Memory).
  • ROM read-only memory
  • RAM random access memory
  • the memory 450 described in the embodiments of the present application is intended to include any suitable type of memory.
  • memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.
  • the operating system 451 includes system programs for processing various basic system services and performing hardware-related tasks, such as framework layer, core library layer, driver layer, etc., for implementing various basic services and processing hardware-based tasks;
  • An input processing module 453 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.
  • FIG. 2 shows the service processing apparatus 454 stored in the memory 450, which may be software in the form of programs and plug-ins, including the following software modules : the first determination module 4541, the first presentation module 4542, the second presentation module 4543, the first acquisition module 4544 and the second determination module 4545, these modules are logical, so any combination or Split further.
  • a first presentation module 4542 and a second presentation module 4543, and other presentation modules, for enabling presentation of information eg, user interfaces for operating peripherals and displaying content and information
  • information eg, user interfaces for operating peripherals and displaying content and information
  • the apparatus provided by the embodiments of the present application may be implemented in hardware.
  • the apparatus provided by the embodiments of the present application may be a processor in the form of a hardware decoding processor, which is programmed to execute the present application
  • the service processing method provided by the embodiment for example, a processor in the form of a hardware decoding processor may adopt one or more Application Specific Integrated Circuits (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device) ), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array) or other electronic components.
  • ASIC Application Specific Integrated Circuit
  • DSP Programmable Logic Device
  • PLD Programmable Logic Device
  • CPLD Complex Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • the service processing method provided by the embodiment of the present application will be described with reference to the exemplary application and implementation of the terminal provided by the embodiment of the present application, and the service processing method is applied to the terminal shown in FIG. 1 .
  • FIG. 3 is a schematic diagram of an implementation flow of the service processing method provided by the embodiment of the present application.
  • the service processing method provided by the embodiment of the present application will be described with reference to the steps shown in FIG. 3 .
  • Step S101 Receive a first selection operation for the node identifier in the policy arrangement interface, and determine at least one selected target node.
  • a policy orchestration process needs to be started, which can be implemented by starting a client terminal dedicated to policy orchestration (corresponding to a policy orchestration platform or a policy platform in other embodiments), or Is to launch the policy orchestration page through the browser.
  • the policy orchestration interface can be presented on the display screen of the terminal, and various types of node identifiers can be displayed in the node identifier display area of the policy orchestration interface, for example, it can include: start node, end node, action Nodes, IoT Nodes, Rule Nodes, etc.
  • the node identification may be a node icon, and the colors and/or shapes of different types of node icons may be different.
  • the first selection operation may be an operation of dragging a certain node identifier (node icon), and in this embodiment of the present application, the first selection operation may be an action or a series of actions.
  • the target node selected at this time is also an action node or an IoT node, for example.
  • the first selection operation is a series of actions, then multiple target nodes are selected at this time, for example, an action node, an IoT node, a rule node, an end node, and the like may be selected.
  • Step S102 presenting the at least one target node in the policy arrangement interface.
  • At least one target node includes an IoT node, which is a special action node that combines IoT technology and can control IoT devices connected to the IoT.
  • the strategy arrangement interface can display node identification display area, node editing area, etc.
  • the first selection operation can be dragging a certain target node from the node identification display area to the node editing area, or dragging certain target nodes from the node identification display area to the node editing area in sequence. Drag and drop the node ID display area to the node editing area. At this point, the node ID of the target node is displayed in the node editing area.
  • Step S103 in response to the configuration operation for the target node, presenting a configuration interface.
  • the configuration operation for the target node can be right-clicking the target node and selecting the node configuration selection control, or it can be an operation of double-clicking a target node.
  • a configuration item area may also be displayed in the policy orchestration interface, and an interactive control with configuration information required by the target node may be displayed in the configuration item area.
  • the configuration item area For example, when configuring an action node is selected, the configuration item area
  • the interactive controls for the required configuration information displayed in can include entry controls for configuring actions, entry controls for configuring input parameters, and entry controls for configuring output parameters. When different entry controls are clicked, the same or different configuration interfaces can be presented.
  • the interactive controls for the required configuration information displayed in the configuration item area may include the entry controls for configuring the device.
  • a configuration instruction may be presented on the device configuration interface. When you click on different entry controls, different configuration interfaces can be presented.
  • Step S104 in response to the input operation received through the configuration interface, obtain the configuration information of the target node.
  • the terminal that performs policy orchestration, or the policy orchestration platform establishes a communication connection with the IoT platform, and when the target node is the IoT node, the configuration information at least includes the device configuration determined based on the IoT platform. information and directive configuration information.
  • the device configuration information may include an IoT device identifier corresponding to the IoT node, a device group identifier of the IoT device, and the like, and the instruction configuration information may include instructions that the IoT device needs to execute.
  • the configuration information at least includes action information, input parameter information, and output parameter information.
  • the IoT device may be a device in an urban rail transit system, such as a display screen, elevator, lighting device, gate, security inspection device, etc. in a subway station.
  • IoT devices can also be devices in other scenarios, such as monitoring devices, alarm devices, etc. in a security system.
  • the input operation received through the configuration interface may be a series of operation sets, thereby realizing the configuration of device information and instruction information, or the configuration of action information, input parameter information, and output parameter information.
  • the IoT platform is connected to the terminal that performs policy orchestration.
  • users can configure IoT nodes and other nodes in a code-free manner, and complex linkage between devices can be constructed. , and do not need to care about the different sources and models of the equipment, so that it can coordinate and communicate with various equipment of different manufacturers without modifying the product code.
  • Step S105 when receiving the operation of completing the strategy arrangement, determine the target business process based on the configuration information of each target node.
  • the target business process is determined based on the configuration information of each target node.
  • the target business process is determined based on the configuration information of each target node.
  • the target business process generated at this time is node A ⁇ node B ⁇ node C.
  • connection information between different target nodes may also be determined based on the binding relationship; and based on the connection The information is connected to the corresponding target node.
  • the implementation of connecting the corresponding target nodes based on the connection information may be that a line segment with a direction is presented between each target node presented on the policy orchestration interface, thereby directly presenting the connection relationship between the target nodes.
  • the service processing method when performing policy orchestration, after receiving the first selection operation for the node identifier in the policy orchestration interface, at least one selected target node is determined and presented in the policy orchestration interface the at least one target node, the at least one target node includes at least an IoT node, and then each target node is configured, and a configuration interface is presented in response to a configuration operation for the target node; in response to an input operation received through the configuration interface, Obtain the configuration information of the target node, wherein, when the target node is an IoT node, the configuration information includes at least device configuration information and instruction configuration information determined based on the IoT platform. The configuration information of the target node determines the target business process.
  • the IoT node when the IoT node needs to be orchestrated in the policy, the IoT node can be configured with codeless device instructions through the policy orchestration interface. In this way, the linkage control between IoT devices is constructed in a code-free manner, and the efficiency of industrial control is improved.
  • the configuration interface when the target node is an IoT node, the configuration interface includes a device configuration interface and an instruction configuration interface, and the device configuration interface is presented when a trigger operation for an entry control for configuring the device is received.
  • Fig. Step S104 shown in 3 "Acquiring the configuration information of the target node in response to the input operation received through the configuration interface" can be implemented by the following steps:
  • Step S1041 in response to the device setting operation received through the device configuration interface, obtain device configuration information corresponding to the IoT node.
  • the device configuration information includes a device identifier, and in some embodiments, the device configuration information may further include a device group identifier.
  • the device setting operation may be a collection of a series of operations, for example, may include a selection operation of a device group, a selection operation of a device identification, and the like.
  • the device configuration interface also displays an entry control for a configuration command (ie, the command configuration entry described below). After completing the configuration of the device information, the command configuration interface can be presented by triggering the command configuration entry.
  • a configuration command ie, the command configuration entry described below.
  • Step S1042 in response to a triggering operation for the instruction configuration entry, presenting an instruction configuration interface.
  • an instruction configuration entry may include a batch configuration entry and a single configuration entry.
  • a trigger operation for a batch configuration entry or a single configuration entry is received, it is considered that an instruction setting operation is received, thereby presenting an instruction configuration interface.
  • the command configuration interface presented may be the same through batch configuration entries or through triggering operations of a single configuration entry.
  • the instruction configuration interface is dynamically generated by parsing the object model information of the IoT device, and the instruction configuration interface of the IoT device with different object model information may be different.
  • Step S1043 in response to the command setting operation received through the command configuration interface, obtain the configured device command.
  • the instruction setting operation is also a series of operations, which may include, for example, an operation of selecting an instruction identifier, an operation of selecting an instruction parameter, an operation of selecting a parameter source, and the like.
  • step S1041 may be implemented by the following steps:
  • Step S10411 Receive a trigger operation for the device group entry in the device configuration interface, and present each device group on the device configuration interface.
  • the device configuration interface presents a display area with a device group entry and a device identifier.
  • each device group can be displayed as shown in FIG. 10 .
  • a device group may also have a hierarchy. For example, as shown in FIG. 10 , a first-level device group is displayed in the leftmost column. The column displays the second-level equipment group under the first-level equipment group, and then select the second-level equipment group, and display each device identification under the second-level equipment group in the equipment identification display area.
  • Step S10412 in response to the second selection operation for the device group, obtain the selected target device group.
  • the second selection operation can be one operation or multiple operations. For example, in some implementation scenarios, there is only one level of device group, then only one device group selection can be performed at this time, and when there are multiple levels of device groups When the device group is selected, multiple device group selections can be made.
  • Line 18, Line 22, cloud development environment 1, station model equipment, etc. are the first-level equipment groups.
  • the middle column displays "station A station model equipment, B station model equipment, passenger flow equipment, TEST, station model-track equipment and other secondary equipment groups under the "Model Equipment”.
  • TEST is the selected secondary device group, that is, "TEST” is the target device group.
  • Step S10413 Present each device identifier included in the target device group.
  • each device identifier of the target device group may be displayed in the device identifier display area of the device configuration interface.
  • the device identification display area may be the area 1002 in FIG. 10 .
  • the device ID under the "TEST" device group is displayed in this area, that is, PM01101.
  • Step S10414 in response to the third selection operation for the device identification, obtain at least one selected device identification.
  • the third selection operation may be an operation of selecting one device identifier, or an operation of selecting multiple device identifiers, for example, an operation of selecting all device identifiers in the target device group.
  • the device configuration interface also presents device control modes, including parallel control and serial control. After acquiring at least one selected device identifier, a suitable control mode can be selected. When serial control is selected, It is necessary to issue device commands one time in the order of the selected device IDs, and it is necessary to wait until the execution result of the command issued this time is received before sending the command to the next device. When parallel control is selected, device instructions are sent to the IoT device corresponding to at least one device identifier at the same time without waiting for the execution result, which is macroscopically parallel.
  • the device information configuration of the IoT node is completed, and the final selected device identifier is the device associated with the IoT node, or the device added to the business process.
  • Step S201 obtain each object model information corresponding to each device identifier.
  • the terminal may acquire the object model information corresponding to each device identifier from the IoT platform. For example, it may be that the terminal sends an acquisition request for the object model information to the IoT platform, and the acquisition request carries each device identifier.
  • the IoT platform acquires each device identifier when receiving the acquisition request, and acquires the object corresponding to each device identifier.
  • Model information carry the object model information in the acquisition response and send it to the terminal.
  • the terminal parses and obtains the response, and obtains each object model information corresponding to each device identifier.
  • Step S202 based on the information of each object model, configure and group each device identifier to obtain a grouping result.
  • the device identifiers of the same object model are grouped into a group.
  • the grouping result includes at least one grouping identifier and a device identifier corresponding to each grouping identifier. Since the devices of the same object model are grouped into a group, and the command configuration interface is implemented according to the object model of the device, the devices in the same group can be configured in batches.
  • Step S203 present the respective grouping identifiers and the device identifiers corresponding to the respective grouping identifiers on the grouping interface.
  • the grouping interface may be an interface as shown in FIG. 11 , and the grouping interface displays a grouping identifier, that is, “device group-1” and a device identifier under the grouping, that is, PM01101.
  • the grouping interface presents an entry for batch configuration of instructions, such as the “batch configuration” control 1102 shown in FIG. 11 , so that batch settings can be performed on devices of the same object model through the following steps:
  • Step S204A in response to the fourth selection operation for the group identification, select all device identifications corresponding to the group identification.
  • the fourth selection operation may be an operation of clicking the "select all” control shown in Fig. 11, at this time, all the device identifiers of "device group-1" will be selected, that is, all device identifiers under "device group-1" correspond to The selection control is selected.
  • step S204A may be performed, but some devices are selected through step S204A': step S204A', in response to the fifth selection operation for the plurality of device identities, obtain the selected plurality of device identities.
  • the fifth selection operation may be a selection operation for selection controls corresponding to multiple device identifiers, which is a series of operations.
  • Step S205A when a trigger operation for the batch configuration entry of the instruction is received, it is determined that a trigger operation for the instruction configuration entry is received.
  • the command batch configuration entry can be the "Batch Configuration" control shown in Figure 11, and the "Batch Configuration” control shown in Figure 11 can be enabled only when at least two device identifiers are selected through step S204A or through step S204A' , that is, the "Batch Configuration" control can respond to the corresponding trigger operation.
  • the grouping interface presents a separate command configuration entry, for example, the “edit” control 1103 in the configuration item shown in FIG. 11 , at this time, the device can be set individually by command through the following steps:
  • Step S204B in response to the sixth selection operation for one device identification, obtain the selected device identification.
  • the sixth selection operation is a selection operation for a selection control corresponding to a certain device identifier, and the device identifier is acquired at this time.
  • Step S205B when a triggering operation for the command-independent configuration entry is received, it is determined that a triggering operation for the command-configuration entry is received.
  • the command individual configuration entry can be the "edit" control in the configuration item in Figure 11.
  • click or touch the "edit” control at this time and it is considered that a trigger operation for the command individual configuration entry is received.
  • step S1042 “In response to the triggering operation for the command configuration entry, present the command configuration interface", which can be achieved by the following steps:
  • Step S10421 in response to the triggering operation for the command configuration entry, obtain the object model information corresponding to the device to be configured.
  • the device to be configured may be one device or multiple devices.
  • the multiple devices belong to the same group, that is, the object models of the multiple devices are the same.
  • Step S10422 acquiring the service information in the object model information.
  • the service information includes instructions that can be operated by the device, and there may be one service or multiple services in one object model information.
  • Step S10423 generating an instruction configuration interface based on the service information, and presenting the instruction configuration interface.
  • the service information may be first parsed to determine at least one optional instruction identifier of the device to be configured and the parameter identifier corresponding to each optional instruction identifier; then the instruction configuration interface presents each optional instruction identifier, the Each optional command identifier corresponds to the parameter identifier and the data source setting entry for each parameter identifier.
  • the service information is parsed to determine at least one optional instruction identifier of the device to be configured and the parameter identifier corresponding to each optional instruction identifier.
  • the field corresponding to the "instruction name" in the service information may be determined as available. Select the instruction identifier, which may be to determine the field corresponding to the parameter name in "inputData" as the parameter identifier.
  • the optional command ID, parameter ID and data source setting entry are presented in the command configuration interface.
  • FIG. 12 is a schematic diagram of an instruction configuration interface provided by an embodiment of the present application. As shown in FIG. 12 , an optional instruction identifier "play message”, a parameter identifier "message” corresponding to the optional instruction, and data are displayed on the instruction configuration interface. Source entry 1203.
  • the command configuration interface of the device to be configured is dynamically generated according to the object model information of the device to be configured, which can ensure the adaptability between the command configuration interface and the device to be configured, thereby ensuring the correctness of the command configuration.
  • step S1043 in response to the command setting operation received through the command configuration interface, obtain the configured device command, can be implemented by the following steps:
  • Step S10431 in response to the seventh selection operation for the optional instruction identifier, determine the selected target instruction identifier.
  • the seventh selection operation is a selection operation for a certain optional instruction, that is to say, when an instruction is configured, one instruction and one instruction are sequentially configured.
  • the seventh selection operation may be a selection operation for the optional instruction identifier of play message, and the play message is determined as the target instruction identifier.
  • Step S10432 in response to the eighth selection operation for the parameter identifier corresponding to the target instruction identifier, determine the selected target parameter identifier.
  • the eighth selection operation may be a selection operation for a certain optional instruction. Taking FIG. 12 as an example, since there is only one parameter identifier, the eighth selection operation at this time is an operation of selecting the parameter identifier of the message.
  • Step S10433 in response to a triggering operation for the data source setting entry identified by the target parameter, a data source setting interface is presented.
  • the data source setting interface displays at least the following data sources: manual input, constant, incoming from the policy user, and selection from other nodes in this policy.
  • Step S10434 in response to the input operation through the data source setting interface, determine the assignment information of the target parameter identifier.
  • the input operation through the data source setting interface may include the operation of selecting the data source and the setting operation of setting the data source.
  • step S10434 it can firstly select a data source from manual input, constants, input from the policy user, select a data source from other node selections in this policy, and present the assignment interface corresponding to the selected data source, wherein, when selecting When the data source is manual input, an input box will be presented to manually input the parameter values of the data source through the input box; when the data source is selected as a constant, an input box can also be presented to input a parameter value through the input box.
  • Constant value which is determined as the assignment of the target parameter identifier; when the selection data source is selected from other nodes of this strategy, the node selection box and the node's output parameter selection box will be displayed, and through the selection of the node selection box The selection operation of the operation and the output parameter selection box of the node determines the assignment information of the target parameter identifier.
  • the assignment information of the target parameter identifier is determined, that is, the input information corresponding to the target parameter identifier is determined.
  • Step S10435 Determine the configured device instruction based on the target instruction identifier, the target parameter identifier and the assignment information.
  • the instruction of the device to be configured is configured in a visual way, so as to realize the codeless configuration of the device instruction, which can reduce the difficulty of configuration and improve the configuration. efficiency.
  • step S10434 in response to the input operation through the data source setting interface, determine the The assignment information of the target parameter identifier" can be realized through the following steps from step S4341 to step S4347 shown in Figure 4:
  • Step S4341 presenting a node selection entry and an output parameter selection entry.
  • Fig. 13 is a schematic diagram of the interface provided by this embodiment of the present application that the data source is selected from other nodes in this strategy. As shown in Fig. 13, when the selected data source is selected from other nodes in this strategy, node selection entries 1301 and 1301 are displayed. Output parameter selection entry 1302.
  • Step S4342 present at least one optional node in response to the triggering operation for the node selection entry, receive a ninth selection operation for the optional node, and determine the target source node.
  • the trigger operation may be an operation of clicking or touching the node selection entry, and when the trigger operation is received, at least one selectable node is presented.
  • the ninth selection operation may be a selection operation for a certain optional node, that is, a target source node is selected through the ninth selection operation.
  • Step S4343 determine whether the target source node is an action node or an IoT node.
  • step S4344 when the target source node is an action node, go to step S4344; when the target source node is an IoT node, go to step S4347.
  • Step S4344 when the target source node is an action node, in response to a trigger operation for the output parameter selection entry, present at least one output parameter identifier of the target source node.
  • the trigger operation for the output parameter selection entry may be clicking or touching the output parameter selection entry.
  • the data source selects another node, it means that the output of the other node is used as the input of this node, so after receiving the trigger operation, at least one output parameter identifier of the target source node is presented.
  • the output parameter identifier is predefined, so after receiving the trigger operation for the output parameter selection entry, it is sufficient to directly acquire and display at least one output parameter identifier of the target source node.
  • the node as the data source is the action node "Get dynamic message".
  • the output parameters of the action node can be directly displayed, that is, for "broadcast messages”.
  • Step S4345 Determine the target output parameter identifier based on the tenth selection operation for the at least one output parameter identifier.
  • the tenth selection operation is an operation of selecting one of the at least one output parameter identifiers as the target output parameter identifier.
  • Step S4346 Determine the output value of the target output parameter identifier as the assignment information of the target parameter identifier.
  • step S4346 the output value of the target output parameter identifier is determined as the input value corresponding to the target parameter identifier in the IoT node.
  • Step S4347 when the target source node is an IoT node, in response to the triggering operation for the output parameter selection entry, an output parameter selection interface is presented.
  • the target source node of the action node "Confirm Broadcast Result” is the IoT node "Display Screen Broadcast Message", and the data of the action node "Confirm Broadcast Result" is selected through the interface described in Figure 14
  • the source is "select from other nodes in this strategy", and after selecting the IoT node "display broadcast message", click the trigger operation for the output parameter selection entry 1401 in Figure 14, the output parameter selection interface 1402 is displayed, and the output The parameter selection interface displays at least one optional output parameter of the target source node, and the optional output parameter includes a device-type output parameter and a non-device-type output parameter.
  • the optional output parameter includes a device-type output parameter and a non-device-type output parameter.
  • the device execution result is a device-type output parameter, that is, the output parameter is the output parameter through the object.
  • the command execution result after the connected device executes the relevant command can be considered as a device-level output parameter, while whether the code is successfully executed and whether all the devices are successfully executed are non-device-class output parameters, reflecting the overall execution status of the command.
  • the assignment information of the target parameter identifier is determined based on the selected non-device output parameter, and further, when the policy is executed , the dynamic output value of the non-device output parameter of the IoT node is determined as the input value identified by the target parameter.
  • Step S4348 when the twelfth selection operation for the device class output parameter is received, the output parameter setting interface is presented.
  • the output parameter setting interface is shown in FIG. 15 .
  • the output parameter device interface includes a device identification selection entry 1501 , a device instruction selection entry 1502 and an output parameter selection entry 1503 of the IoT node.
  • Step S4349 in response to an input operation through the output parameter setting interface, determine the assignment information of the target parameter identifier.
  • Step S4349 can be implemented by the following two steps:
  • the target device ID, target device command and target output parameter ID are determined respectively through triggering operations for the device ID selection entry, the device command selection entry and the output parameter selection entry.
  • the optional device identifiers can be presented first through the triggering operation for the device identifier selection entry, and then one of the optional device identifiers is selected as the target device identifier. After the target device identifier is selected, when receiving When the trigger operation for the device command selection entry is reached, the optional device command corresponding to the target device identifier is presented, and one of the optional device commands is selected as the target device command. When the trigger operation for the output parameter selection entry is received , present the optional output parameter identifier corresponding to the target device instruction, and then select one of the optional output parameter identifiers as the target output parameter identifier.
  • the assignment information of the target parameter identifier is determined based on the target device identifier, the target device instruction and the target output parameter identifier.
  • the assignment information of the target parameter identifier that is, the input information of the target parameter identifier, through this step, the output information of the target output parameter identifier in the target device instruction identifier corresponding to the target device identifier in the IoT node as the data source can be used as the target parameter. Identified input information.
  • the input operation through the data source setting interface can be completed, the assignment information of the target parameter identifier can be determined, and the target parameter identifier in the target node can be completed in a visual way only by clicking operations. Binding of input variables to improve configuration efficiency.
  • the output variable of the IoT node is the result of device control, it is related to the selected device and cannot be defined in advance. Therefore, after configuring the device command, you can dynamically generate the output variable of the node in combination with the object model of the IoT device through the following steps:
  • Step S301 sending an acquisition request of the object model information to the IoT platform.
  • the acquisition request carries each device identifier; upon receiving the acquisition request, the IoT platform acquires each device identifier, acquires the object model information corresponding to each device identifier, and carries the object model information in the acquisition response and sends it to the terminal.
  • Step S302 Receive an acquisition response sent by the IoT platform, and acquire each object model information corresponding to each device identifier carried in the acquisition response.
  • the terminal After receiving the acquisition response, the terminal parses the acquisition response, and acquires each object model information corresponding to each device identifier.
  • Step S303 parse the object model information, and obtain the output parameter definition of the configured device instruction.
  • the definition of the output parameter in the configured device instruction may be obtained by obtaining the "outputData" part of the object model information.
  • Step S304 Determine the output description information of the IoT node based on the device configuration information, the device instruction and the output parameter definition.
  • a one-to-one correspondence between the device identifier, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction can be established according to the hierarchical structure from the device to the instruction to the output parameter;
  • the device identifier in the corresponding relationship, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction dynamically generate the output description information of the IoT node according to a preset description format.
  • the commands configured by device 1 are command 1 and command 2
  • the command configured by device 2 is command 1
  • the output parameters under command 1 are defined as parameter A
  • command The output parameters under 2 are defined with parameter B
  • the following correspondence will be constructed: device 1-command 1-parameter A, device 1-command 2-parameter B, device 2-command 1-parameter A.
  • the output description information of the IoT node is generated according to the content in the above corresponding relationship according to the preset description format.
  • the output description information may be generated according to the JSON format and stored.
  • Step S305 mount the output description information to the output variable of the IoT node.
  • the output variable of the IoT node is not a specific variable, but a piece of description information.
  • the description information can indicate the device information controlled by the IoT node, the instructions controlled by each device, and the output parameters included in each command, so that the output variables of the IoT node can be dynamically generated in combination with the object model, thereby ensuring the output variables. Adaptive.
  • the step S104 "in response to an input operation received through the configuration interface, obtain the configuration information of the target node" shown in FIG. 3 can be implemented by the following steps:
  • Step S1041' in response to the triggering operation for the action selection entry in the configuration interface, present at least one optional action.
  • the triggering operation of the action selection entry can be the operation of right-clicking the target node, or the operation of double-clicking the target node.
  • at least one optional action may be presented.
  • Step S1042' in response to the eleventh selection operation for the at least one optional action, determine a target action.
  • one of at least one optional action may be selected as the target action.
  • the user may also be supported to input a keyword, thereby filtering out actions matching the keyword, and then determining the target action from the actions matching the keyword.
  • Step S1043' obtain the preset output parameter information of the target action.
  • the output parameter information of each action such as output parameter identification, output parameter type, etc.
  • the output parameter information of the action can also be directly obtained. arrive.
  • Step S1044' determine the target action and the output parameter information as the configuration information of the target node.
  • FIG. 5 is a schematic diagram of another implementation flow of the service processing method provided by the embodiment of the present application. As shown in FIG. 5 , the flow includes:
  • Step S501 the terminal starts a policy arrangement process, and presents a policy arrangement interface.
  • the terminal may start the installed policy orchestration application client, or start the policy orchestration engine, so as to start the policy orchestration process and present the policy orchestration interface.
  • a strategy arrangement for business processes applied to the urban rail transit system is performed.
  • the business process is, after obtaining the abnormal alarm information in the subway, use the display screen to play the alarm information, and determine whether the broadcast is broadcast.
  • the alarm information can be triggered by a train failure, a fire, or other reasons.
  • Step S502 the terminal receives the first selection operation for the node identifier in the policy arrangement interface, and determines at least one selected target node.
  • the selected target nodes can be two action nodes and one IoT node.
  • the first action node is node A
  • the first IoT node is node B
  • the second action node is node C.
  • Step S503 the terminal presents the at least one target node in the policy arrangement interface.
  • At least one target node includes an IoT node.
  • the target node may also be an action node, a rule node, and the like.
  • nodes A, B, and C are displayed on the policy orchestration interface.
  • Step S504 when the target node is an IoT node, the terminal acquires the device configuration information corresponding to the IoT node in response to the device setting operation received through the device configuration interface.
  • the device configuration information includes a device identifier.
  • the device configuration information may further include device group identifications, device labels, and the like.
  • the terminal may obtain the device grouping information, device identification information, etc. of the IoT devices connected to the IoT platform through the IoT platform, so as to perform IoT based on the received device grouping information, device identification information, etc. Node corresponds to the configuration of device information.
  • the configuration process of the node A can be completed through the configuration interface of the action node.
  • the configuration of the device information can be done through the interfaces shown in FIG. 10 and FIG. 11 during implementation.
  • Step S505 the terminal sends an acquisition request for the object model information to the IoT platform in response to the triggering operation for the command configuration entry.
  • the acquisition request carries the device identifier included in the device configuration information acquired in step S504.
  • Step S506 the IoT platform receives the acquisition request, and acquires the device identifier carried in the acquisition request.
  • Step S507 the IoT platform obtains the object model information corresponding to the device identifier.
  • the object model information includes device basic information, device attribute information, device events, and device operable instructions (ie, device services).
  • Step S508 the IoT platform sends an acquisition response carrying the object model information to the terminal.
  • Step S509 the terminal receives the acquisition response, and acquires the object model information carried in the acquisition response.
  • Step S510 the terminal acquires the service information in the object model information.
  • the service information in the object model information can represent the operable instructions of the device, and the instructions that can be operated by the IoT devices of different object models may be different, the service information is obtained in this step to pass the service in the subsequent steps.
  • the information generates an instruction configuration interface corresponding to the object model.
  • Step S511 the terminal generates an instruction configuration interface based on the service information, and presents the instruction configuration interface.
  • an instruction configuration interface is generated based on the service information, which can be obtained by parsing the service information to obtain an instruction identifier and an input parameter identifier in the service information, so as to present the instruction configuration interface as shown in FIG. 12 , the instruction identifier— Parameter identification—the third-level configuration entry of the data source, so as to perform instruction configuration through the three-level configuration entry.
  • Step S512 the terminal acquires the configured device instruction in response to the instruction setting operation received through the instruction configuration interface.
  • Step S513 the terminal parses the object model information corresponding to the IoT node, and obtains the output parameter definition of the configured device instruction.
  • the output parameter definition is the description of the result returned after the IoT device sends the command, and each command will have its own return result. Then, the output description of the IoT node can be generated through the output parameters of the device instruction in the composition model.
  • Step S514 the terminal determines the output description information of the IoT node based on the device configuration information, the device instruction and the output parameter definition.
  • the output description information of the IoT node may be generated according to the hierarchical structure of device-instruction-output parameter, and stored according to a preset format.
  • Step S515 the terminal mounts the output description information on the device class output parameter of the IoT node.
  • the interface shown in FIG. 14 and FIG. 15 can be used to complete the comparison between the device output parameter of node B and the input parameter of node C. Visual binding.
  • Step S5166 when the terminal receives the operation of completing the arrangement of policies, it determines the target business process based on the configuration information of each target node.
  • the target business process is: node A (acquiring alarm information) ⁇ node B (playing alarm information on the display screen) ⁇ node C (determining the playback result), that is to say, when alarm information appears in the subway system, the The information will be used as the input of node B.
  • the display screen controlled by node B will play the alarm information through voice and video, and then further determine whether the playback is successful to confirm whether the alarm information is sent.
  • the configuration information of each target node may be used to determine the binding relationship between output variables and input variables between different target nodes, and determine the target business process based on the binding relationship.
  • the terminal after starting the policy orchestration process, the terminal presents the policy orchestration interface, and determines at least one selected target node through the first selection operation for the node identifier in the policy orchestration interface, and then selects at least one target node.
  • the at least one target node is presented in the policy orchestration interface, and the at least one target node includes an IoT node; when the target node is an IoT node, the terminal responds to the device setting operation received through the device configuration interface, based on the IoT
  • the IoT platform obtains the device configuration information corresponding to the IoT node, wherein the device configuration information includes the device identifier; then the terminal responds to the triggering operation for the command configuration entry, and sends the IoT platform an acquisition request for the object model information. After obtaining the corresponding object model information based on the device identifier carried in the acquisition request, the object model information is returned to the terminal.
  • the terminal When configuring the command, the terminal dynamically generates the command configuration interface based on the service information in the object model, and presents the command configuration interface.
  • the command configuration interface, and the command setting operation received through the command configuration interface is used to configure the device command, and the output variables of the IoT node are also dynamically generated according to the definition of the output parameters in the object model, so as to ensure the IoT node.
  • the output variable is the control result of the IoT device to ensure the output accuracy; when the terminal receives the completion of the operation of the strategy orchestration, the target business process is determined based on the configuration information of each target node; in this way, the IoT and the process orchestration technology are integrated to provide the city Rail industry, security control and other scenarios provide a way of code-free business and equipment arrangement, and the solution of dynamically generating IoT node output variables and visual binding proposed in the embodiment of this application is a good solution to process arrangement and objects.
  • the integration of networking technologies ensures the accuracy and effectiveness of the target business process.
  • FIG. 6 is a schematic diagram of the system architecture of the service processing method provided by the embodiment of the present application.
  • the system architecture includes: an IoT device 601, an IoT platform 602, and a business processing device (strategy platform) 603, wherein:
  • the IoT device 601 includes a plurality of physical devices connected to the Internet of Things, such as urban rail physical devices;
  • the IoT platform 602 is used for device grouping of physical devices, determining device labels, and managing object models;
  • the business processing device (policy platform) 603 is connected to the IoT platform 602, and uses the device grouping information, device label information and object model provided by the IoT platform to perform strategy arrangement, strategy management and template management.
  • the policy executor executes the policy and controls the corresponding physical device through the control device in the IoT platform 602 .
  • the policy platform in this embodiment of the present application corresponds to the policy orchestration platform in other embodiments.
  • FIG. 7 is a schematic diagram of still another system architecture of a business processing method applied in an urban rail transit scenario provided by an embodiment of the present application. Similar to FIG. 6 , the system architecture includes urban rail equipment 701 , an IoT platform 702 and a strategy platform 703. In the strategy platform, the strategy of action node 7031 ⁇ IoT node 7032 ⁇ action node 7033 needs to be arranged.
  • Fig. 7 shows the configuration process of IoT node. As shown in Fig. 7, the configuration process includes: selecting Device 711 , device preview 712 , model grouping 713 , batch configuration 714 , model analysis 715 , interface generation 716 , and configuration instruction 717 .
  • the selection device 711 it is necessary to select the device based on the device grouping information and device label information obtained from the IoT platform.
  • model grouping it is necessary to obtain the object model from the IoT platform, and from the same object model.
  • the process from model parsing to interface generation it is also necessary to parse the object model based on the object model obtained from the IoT platform, so as to dynamically generate the command control interface (that is, the command configuration interface in other embodiments). ).
  • the command and control interface is dynamically generated according to the service in the object model.
  • a device can have multiple services, and a service can have multiple input parameters.
  • the display object model is used as an example for description.
  • the following is the definition of the display object model.
  • Profile equipment basic information
  • Properties equipment properties
  • Events equipment events
  • Service equipment services, that is, the instructions that the device can operate, and a device can have multiple services.
  • the object model of this display screen has only one service—playing messages, and there is only one input parameter under this service, that is, the message, which is of string type.
  • the output variable of the action node is defined in the action in advance, and you only need to mount the output parameter of the action to the output variable of the node.
  • the output variable of the IoT node is the result of device control, which is related to the selected device and cannot be defined in advance. Therefore, in the embodiment of the present application, the output variable of the node is dynamically generated from the combination model. After the user configures the device command, the generation process of the node output variable includes the steps shown in Figure 8:
  • Step S801 acquiring the object model of the selected device.
  • Step S802 analysing the object model.
  • Step S803 extracting the parameter definition of the selected instruction.
  • Step S804 combine the command output parameter with the structure of device-command-output parameter.
  • Step S805 generating a node outgoing parameter description.
  • Step S806 mount to the output variable of the IoT node.
  • the output parameter definition (outputData) in the display screen command is the description of the result returned after the device sends the command, and each command will have its own return result. Then, the output description of the IoT node can be generated through the output parameters of the device instructions in the composition model, stored in a certain format (JSON), and finally mounted on the output parameters of the IoT node (devices).
  • the output parameter is an output parameter of a special type (Device).
  • the IoT node may also include dynamically generated non-device-level output parameters, which may be expanded according to actual needs.
  • IoT node output parameters The following are examples of IoT node output parameters:
  • activity0oqhb04 represents the id of the current IoT node, which is unique in each policy.
  • filedKey is the node's outgoing parameter identifier, which is unique within a node.
  • outputKey is the external identifier of the node's outgoing parameter, which is unique within a policy, and is expressed in the form of "node id + node outgoing parameter".
  • the output variable of the IoT node is not a specific variable, but a description. This description indicates which devices this node controls, which commands each device controls, and what parameters each command has.
  • the output variables of the IoT node will be referenced (bound) in other nodes as the input of other nodes.
  • its output variable is a description, not a specific variable, it cannot be directly bound to the input parameters of subsequent nodes. Therefore, when binding, by parsing the output variable devices of the IoT node, a visual interface is generated with the hierarchical structure of "device-command-output parameter". The user only needs to click to bind the selected output parameter to other nodes. on the input variable.
  • the value here is an alternative, indicating that the current input parameter is bound to the success output parameter of the sendMessage service of the specified device [768100001-5a9d2b4579074afeb073c63a0125bc17] in the IoT node whose id is Activity0oqhb04.
  • filedKey is the input parameter identifier of the current node, which is unique within the same node.
  • “souce” is the data source of the input.
  • value is a substitute value, indicating that the current input parameter binding is the output parameter (devices) of another node (Activity0oqhb04). Since it is an IoT node, it further specifies the id as "768100001-5a9d2b4579074afeb073c63a0125bc17 "The "success” parameter of the "sendMessage” service of the device.
  • the present invention implements the access and unified management of the material model of the urban rail equipment through the Internet of Things technology, breaks the linkage barriers between the equipment, and deeply integrates the material model through the strategy arranging capability of the strategy engine, so that the user does not need a code base, and is extremely
  • the construction and execution of inter-device linkage strategies can be realized with a low threshold.
  • IoT nodes Users can configure device control instructions without code by dragging and dropping IoT nodes on the policy orchestration interface.
  • the devices that need to be controlled can be quickly screened by device grouping or labeling, and one or more devices can be selected here.
  • Devices under the same object model will be assigned to a configuration group for batch configuration.
  • the command configuration interface of the device and the output variables of this node are dynamically generated to realize code-free configuration.
  • Other nodes bind the dynamic output variables of the IoT node by visual selection.
  • Obtain dynamic message 901 an action node, used to obtain a message, and output the message in the form of a variable for use by subsequent nodes.
  • Display screen broadcast message 902 IoT node, perform instruction configuration on the display screen device, here will receive the message variable of the previous node, and output the device control result in the form of a variable.
  • Confirm the broadcast result 903 the action node, used to confirm the broadcast result, needs to receive the output variable of the IoT node as the input of this node.
  • the first step is to drag an action node on the orchestration interface, and select the action in the platform - "Get Dynamic Message", the action node has an output parameter - message.
  • the second step is to drag and drop the IoT node on the orchestration interface.
  • This node integrates the capabilities provided by the IoT platform.
  • the user can filter the devices to be controlled according to the device grouping/label, and can select multiple, and can set serial or parallel. control.
  • FIG. 10 is a schematic diagram of an interface for selecting a device to be controlled provided by an embodiment of the application.
  • the device group 1001 in FIG. 10 can be used to select the group where the device to be controlled is located. Select a device under the device group, and in the selection box 1002 shown in FIG. 10 , the device PM01101 is selected.
  • the IoT node will group the selected devices according to the object model, and present the interface shown in FIG. 11 .
  • Devices of the same object model can be configured in batches.
  • multiple devices can be selected through Figure 11.
  • the "Select All” control 1101 shown in Figure 11 can be checked, and then click "Batch Configuration" 1102, The command configuration interface shown in FIG. 12 is entered.
  • the check boxes corresponding to multiple devices may also be selected to select multiple devices.
  • the fourth step is to configure the device command.
  • the command configuration interface shown in FIG. 12 is dynamically generated by the policy platform obtaining the object model of the device to be set, and then analyzing the service information of the object model.
  • - Input parameters of the service The hierarchy of the data source is displayed. Take the object model of the display screen as an example to illustrate, in the object model of the display screen, there is only one service (playing message), and the service has only one input parameter (message). Therefore, a play message is displayed in the instruction setting interface.
  • - message - data source If the device to be configured has multiple services, or a service has multiple input parameters, then when you click the operation control 1201 on the far left of Figure 12, all optional commands can be displayed. After selecting the command, click the middle
  • the operation control 1202 can display all the input parameters of the command, select one of them, and then select the data source based on the operation control 1203 on the far right.
  • the assignment of the command input parameter (that is, the data source) has four ways as shown in FIG. 12 :
  • Constants select the constants defined in the strategy platform
  • Policy user input the input parameter of the policy, which is passed in when the policy is started;
  • the data source of the IoT node is the action node of “obtaining dynamic messages”, as shown in FIG. 13 .
  • the data source selects “select from other nodes in this policy”.
  • two selection controls for selecting nodes and output parameters will be displayed, 1301 and 1302 respectively.
  • the selected node is "Get Dynamic Message”
  • the output parameter is "Message”.
  • the output variable of the previous node is bound to the input variable of the current instruction, so that the message obtained by the previous node will be transmitted to this instruction.
  • the fifth step drag the action node on the orchestration interface, and select the action in the platform - "Confirm Broadcast Result", the action node has an input parameter - broadcast result, that is, the device control result of the previous IoT node.
  • the data source selected for this action node is "Select from other nodes in this strategy", and the selected node is "Display screen broadcast message", since the node of "Display screen broadcast message" is the IoT node , that is to say, the output variable of the IoT node "display broadcast message” needs to be bound with the input parameter of the action node "confirm broadcast result”.
  • the device PM01101 controlled by the IoT node is selected through the device selection control 1501
  • the command "play message” controlled by the device is selected through the command selection control 1502
  • the control is selected through the output parameter 1503 Select the parameter "execution is successful" of the instruction. In this way, the binding of the output variable of the IoT node to this input parameter is completed through the visual method shown in Figure 15.
  • device control instructions can be configured in a codeless form by dragging and dropping IoT nodes on the strategy orchestration interface.
  • the devices that need to be controlled can be quickly screened by device grouping or labels, and one or more devices can be selected.
  • Devices under the same object model will be assigned to a configuration group for batch configuration.
  • the command configuration interface of the device and the output variables of this node are dynamically generated to realize code-free configuration.
  • Other nodes bind the dynamic output variables of the IoT node by visual selection.
  • the device in the urban rail scenario is abstracted and managed in a unified manner, and the physical model of the IoT platform is introduced into the process orchestration, so that users can
  • the complex linkage between devices is constructed by means of codes, and there is no need to care about the different sources and models of the devices, so as to achieve coordination and communication with various devices of different manufacturers without modifying the product code.
  • the software modules stored in the service processing apparatus 454 of the memory 450 may include :
  • the first determination module 4541 is configured to receive the first selection operation for the node identifier in the policy orchestration interface, and determine at least one selected target node;
  • a first presentation module 4542 configured to present the at least one target node in the policy orchestration interface, where the at least one target node includes an IoT node;
  • the second presentation module 4543 is configured to present a configuration interface in response to the configuration operation for the target node
  • the first obtaining module 4544 is used to obtain the configuration information of the target node in response to the input operation received through the configuration interface, wherein, when the target node is an IoT node, the configuration information at least includes device configuration information and instructions configuration information;
  • the second determining module 4545 is configured to determine the target business process based on the configuration information of each target node when receiving the policy orchestration completion operation.
  • the configuration interface includes a device configuration interface and an instruction configuration interface
  • the first acquisition module is further configured to:
  • the device configuration interface In response to the device setting operation received through the device configuration interface, obtain device configuration information corresponding to the IoT node, where the device configuration information includes a device identifier;
  • an command configuration interface is presented, and the command configuration interface is dynamically generated based on the object model information of the IoT device;
  • a configured device instruction is obtained.
  • the apparatus further includes:
  • a first sending module configured to send an acquisition request for object model information to the IoT platform, where the acquisition request carries each device identifier;
  • a first receiving module configured to receive an acquisition response sent by the IoT platform, and acquire information of each object model corresponding to each device identifier carried in the acquisition response;
  • the second acquisition module is used to parse the object model information and acquire the output parameter definition of the configured device instruction
  • an information generation module configured to dynamically generate the output description information of the IoT node based on each device identifier, device instruction and output parameter definition;
  • the mounting module is configured to mount the output description information on the device class output parameter of the IoT node.
  • the information generation module is also used to:
  • the hierarchical structure from device to instruction to output parameter establish a one-to-one correspondence between the device identifier, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction;
  • the output description information of the IoT node is dynamically generated according to the device identifier in each corresponding relationship, the device instruction configured by the device identifier, and the output parameter definition of the configured device instruction according to a preset description format.
  • the first obtaining module is further used for:
  • the selected at least one device identification is acquired.
  • the apparatus further includes:
  • the third acquisition module is used to acquire the information of each object model corresponding to each device identifier
  • a grouping module configured to configure and group each device identifier based on the information of each object model, and obtain a grouping result, wherein the grouping result includes at least one grouping identifier and a device identifier corresponding to each grouping identifier;
  • the third presentation module is configured to present the respective grouping identifiers and the device identifiers corresponding to the respective grouping identifiers on the grouping interface.
  • the grouping interface presents an entry for batch configuration of instructions
  • the apparatus further includes:
  • a selection module configured to select all device identifiers corresponding to the group identifier in response to the fourth selection operation for the group identifier; or,
  • a fourth obtaining module configured to obtain a plurality of selected device identities in response to the fifth selection operation for the plurality of device identities
  • the third determining module is configured to determine that a trigger operation for the instruction configuration entry is received when a trigger operation for the instruction batch configuration entry is received.
  • the grouping interface presents a separate configuration entry for instructions
  • the apparatus further includes:
  • a fifth acquisition module configured to acquire the selected device identification in response to the sixth selection operation for a device identification
  • the fourth determination module is configured to determine that a trigger operation for the instruction configuration entry is received when a trigger operation for the instruction separate configuration entry is received.
  • the first obtaining module is further used for:
  • each optional instruction identifier In the instruction configuration interface, each optional instruction identifier, the parameter identifier corresponding to each optional instruction identifier, and the data source setting entry of each parameter identifier are presented.
  • the first obtaining module is further used for:
  • the configured device instruction is determined based on the target instruction identification, the target parameter identification and the assignment information.
  • the data source setting interface displays at least the following data sources: manual input, constants, input from the policy user, selection from other nodes of the policy, and the first acquisition module is also used for:
  • the target source node When the target source node is an action node, present at least one output parameter identifier of the target source node in response to a triggering operation for the output parameter selection entry, and determine the target output based on the tenth selection operation for the at least one output parameter identifier parameter identifier;
  • the output value of the target output parameter identifier is determined as the assignment information of the target parameter identifier.
  • the first obtaining module is further used for:
  • an output parameter selection interface is presented in response to a trigger operation for the output parameter selection entry, and the output parameter selection interface displays at least one optional output parameter of the target source node, so
  • the optional output parameters described above include device-type output parameters and non-device-type output parameters
  • the assignment information of the target parameter identifier is determined.
  • the output parameter setting interface includes a device identification selection entry, a device instruction selection entry, and an output parameter selection entry of the IoT node, and the first acquisition module is further configured to:
  • the target device identifier determines the target device identifier, target device instruction and target output parameter identifier through triggering operations for the device identifier selection entry, the device instruction selection entry and the output parameter selection entry respectively;
  • the assignment information of the target parameter identifier is determined based on the target device identifier, the target device instruction and the target output parameter identifier, wherein the target assignment information is after the IoT device corresponding to the target device identifier executes the target device instruction
  • the target output parameter identifies corresponding output information.
  • the first obtaining module is further configured to:
  • the target action and the output parameter information are determined as configuration information of the target node.
  • the second determining module is further configured to:
  • the device also includes:
  • the sixth determining module is configured to determine connection information between different target nodes based on the binding relationship, and connect the corresponding target nodes based on the connection information.
  • Embodiments of the present application provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the foregoing method provided by the embodiments of the present application.
  • the embodiments of the present application provide a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored, and when the executable instructions are executed by a processor, the processor will cause the processor to execute the method provided by the embodiments of the present application, for example , as shown in Figure 3, Figure 4 and Figure 5.
  • the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories Various equipment.
  • executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and which Deployment may be in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • executable instructions may, but do not necessarily correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, a Hyper Text Markup Language (HTML, Hyper Text Markup Language) document
  • HTML Hyper Text Markup Language
  • One or more scripts in stored in a single file dedicated to the program in question, or in multiple cooperating files (eg, files that store one or more modules, subroutines, or code sections).
  • executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or alternatively, distributed across multiple sites and interconnected by a communication network execute on.

Abstract

提供了一种业务处理方法、装置、设备及计算机可读存储介质；方法至少可以应用于交通领域，包括：接收针对策略编排界面中节点标识的第一选择操作，确定并呈现选中的至少一个目标节点，至少一个目标节点至少包括物联节点；响应于针对目标节点的配置操作，呈现配置界面（S103）；响应于通过配置界面接收到的输入操作，获取目标节点的配置信息（S104），其中，当目标节点为物联节点时，配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息；当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程（S105）。通过本申请，能够在策略编排界面对物联节点进行无代码配置，以无代码的方式构造物联设备间的联动控制。

Description

一种策略编排处理方法、装置、设备、系统及存储介质 技术领域
本申请涉及物联网技术，尤其涉及一种业务处理方法、装置、设备及计算机可读存储介质。
背景技术
随着计算机技术和工业控制技术的发展，工业控制的复杂程度越来越高，运营成本也随之提高。为此，人们采用流程编排的方式，将流程与任务相结合，以将某些服务能力固化，从而达到快速、自动化完成指定任务的目的。
目前进行流程编排时，节点的输出变量是事先在动作中定义好的，不适用于输出变量不定的物联设备。而在一些结合有物联设备的工业控制场景中(例如在城轨行业中)，业务侧的关于工业控制的场景化需求与迭代复杂且多变，且对于不同厂商及系统的设备控制联动十分困难。
发明内容
本申请实施例提供一种业务处理方法、装置、设备及计算机可读存储介质，能够在策略编排界面对物联节点进行无代码配置，以无代码的方式构造物联设备间的联动控制。
本申请实施例的技术方案是这样实现的：
本申请实施例提供一种业务处理方法，包括：
接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点；
在该策略编排界面中呈现该至少一个目标节点，该至少一个目标节点包括物联节点；
响应于针对目标节点的配置操作，呈现配置界面；
响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息，其中，当该目标节点为物联节点时，该配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，所述物联平台与进行策略编排的终端建立有通信连接；
当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
本申请实施例提供一种业务处理装置，包括：。
第一确定模块，用于接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点；
第一呈现模块，用于在该策略编排界面中呈现该至少一个目标节点，该至少一个目标节点包括物联节点；
第二呈现模块，用于响应于针对目标节点的配置操作，呈现配置界面；
第一获取模块，用于响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息，其中，当该目标节点为物联节点时，该配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，所述物联平台与进行策略编排的终端建立有通信连接；
第二确定模块，用于当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
在一些实施例中，当该目标节点为物联节点时，该配置界面包括设备配置界面和指令配置界面，该第一获取模块，还用于：
响应于通过该设备配置界面接收到的设备设置操作，获取该物联节点对应的设备配置信息，该设备配置信息包括设备标识；
响应于针对指令配置入口的触发操作，呈现指令配置界面，所述指令配置界面是基于物联设备的物模型信息动态生成的；
响应于通过该指令配置界面接收到的指令设置操作，获取配置的设备指令。
在一些实施例中，该装置还包括：
第一发送模块，用于向物联平台发送物模型信息的获取请求，所述获取请求中携带有各个设备标识；
第一接收模块，用于接收物联平台发送的获取响应，获得所述获取响应中携带的各个设备标识对应的各个物模型信息；
第二获取模块，用于解析所述物模型信息，获取配置的设备指令的输出参数定义；
信息生成模块，用于基于各个设备标识、设备指令和输出参数定义动态生成所述物联节点的输出描述信息；
挂载模块，用于将所述输出描述信息挂载到所述物联节点的设备类输出参数上。
在一些实施例中，该信息生成模块，还用于：
按照设备至指令至输出参数的层级结构，建立设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义的一一对应关系；
将各个对应关系中的设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义按照预设描述格式动态生成所述物联节点的输出描述信息。
在一些实施例中，该第一获取模块，还用于：
接收针对该设备配置界面中设备组入口的触发操作，在该设备配置界面呈现各个设备组；
响应于针对该设备组的第二选择操作，获取选中的目标设备组；
呈现目标设备组中包括的各个设备标识；
响应于针对设备标识的第三选择操作，获取选中的至少一个设备标识。
在一些实施例中，该装置还包括：
第三获取模块，用于获取各个设备标识对应的各个物模型信息；
分组模块，用于基于该各个物模型信息，对各个设备标识进行配置分组，得到分组结果，其中，该分组结果包括至少一个分组标识和各个分组标识对应的设备标识；
第三呈现模块，用于在分组界面呈现该各个分组标识和该各个分组标识对应的设备标识。
在一些实施例中，该分组界面呈现有指令批量配置入口，该装置还包括：
选择模块，用于响应于针对分组标识的第四选择操作，选中该分组标识对应的所有设备标识；或者，
第四获取模块，用于响应于针对多个设备标识的第五选择操作，获取选择的多个设备标识；
第三确定模块，用于当接收到针对指令批量配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
在一些实施例中，该分组界面呈现有指令单独配置入口，该装置还包括：
第五获取模块，用于响应于针对一个设备标识的第六选择操作，获取选择的设备标识；
第四确定模块，用于当接收到针对指令单独配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
在一些实施例中，该第一获取模块，还用于：
响应于针对指令配置入口的触发操作，获取待配置设备对应的物模型信息；
获取该物模型信息中的服务信息；
解析该服务信息，确定该待配置设备的至少一个可选指令标识和各个可选指令标识对应的参数标识；
在该指令配置界面呈现各个可选指令标识、该各个可选指令标识对应的参数标识和各个参数标识的数据来源设置入口。
在一些实施例中，该第一获取模块，还用于：
响应于针对可选指令标识的第七选择操作，确定选中的目标指令标识；
响应于针对目标指令标识对应的参数标识的第八选择操作，确定选中的目标参数标识；
响应于针对目标参数标识的数据来源设置入口的触发操作，呈现数据来源设置界面；
响应于通过数据来源设置界面的输入操作，确定该目标参数标识的赋值信息；
基于该目标指令标识、该目标参数标识和该赋值信息确定配置的设备指令。
在一些实施例中，该数据来源设置界面至少显示有以下数据来源：手动输入、常量、策略使用方传入、从本策略的其他节点选择，该第一获取模块，还用于：
当通过该数据来源设置界面接收到选择数据来源为从本策略的其他节点选择的第八选择操作时，呈现节点选择入口和输出参数选择入口；
响应于针对该节点选择入口的触发操作，呈现至少一个可选节点，接收针对可选节点的第九选择操作，确定目标来源节点；
当该目标来源节点为动作节点时，响应于针对输出参数选择入口的触发操作，呈现该目标来源节点的至少一个输出参数标识，基于针对该至少一个输出参数标识的第十选择操作，确定目标输出参数标识；
将该目标输出参数标识的输出值确定为该目标参数标识的赋值信息。
在一些实施例中，该第一获取模块，还用于：
当该目标来源节点为物联节点时，响应于针对输出参数选择入口的触发操作，呈现输出参数选择界面，所述输出参数选择界面显示有所述目标来源节点的至少一个可选输出参数，所述可选输出参数包括设备类输出参数和非设备类输出参数；
当接收到针对设备类输出参数的第十二选择操作时，呈现所述输出参数设置界面；
响应于通过所述输出参数设置界面的输入操作，确定所述目标参数标识的赋值信息。
在一些实施例中，所述输出参数设置界面包括所述物联节点的设备标识选择入口、设备指令选择入口和输出参数选择入口，该第一获取模块，还用于：
按照设备至指令至输出参数的层级结构，分别通过针对设备标识选择入口、设备指令选择入口和输出参数选择入口的触发操作，确定目标设备标识、目标设备指令和目标输出参数标识；
基于所述目标设备标识、目标设备指令和目标输出参数标识确定所述目标参数标识的赋值信息，其中，所述目标赋值信息为所述目标设备标识对应的物联设备执行所述目标设备指令后所述目标输出参数标识对应的输出信息。
在一些实施例中，当该目标节点为动作节点时，该第一获取模块，还用于：
响应于针对该配置界面中动作选择入口的触发操作，呈现至少一个可选动作；
响应于针对该至少一个可选动作的第十一选择操作，确定目标动作；
获取该目标动作预设的输出参数信息；
将该目标动作和该输出参数信息确定为该目标节点的配置信息。
在一些实施例中，该第二确定模块，还用于：
基于各个目标节点的配置信息，确定不同目标节点之间的输入变量与输出变量之间的绑定关系；
基于该绑定关系，确定目标业务流程；
该装置还包括：
第六确定模块，用于基于该绑定关系，确定不同目标节点之间的连接信息，基于该连接信息连接对应的目标节点。
本申请实施例提供一种业务处理设备，包括：
存储器，用于存储可执行指令；
处理器，用于执行该存储器中存储的可执行指令时，实现本申请实施例提供的方法。
本申请实施例提供一种业务处理系统，包括：业务处理设备、物联平台和物联设备，其中，所述业务处理设备与物联平台之间建立有通信连接，所述物联平台与所述物联设备之间建立有通信连接；
所述物联平台，用于进行所述物联设备的设备分组、确定设备标签，并进行物模型管理；
所述业务处理设备，利用所述物联平台提供的设备分组信息、设备标签信息和物模型按照上述所述的方法进行策略编排。
本申请实施例提供一种计算机可读存储介质，存储有可执行指令，用于引起处理器执行时，实现本申请实施例提供的方法。
本申请实施例提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行本申请实施例提供的上述方法。
本申请实施例具有以下有益效果：
在进行策略编排时，接收到针对策略编排界面中节点标识的第一选择操作后，确定选中的至少一个目标节点，并在该策略编排界面中呈现该至少一个目标节点，该至少一个目标节点至少包括物联节点，之后对各个目标节点进行配置，响应于针对目标节点的配置操作，呈现配置界面；响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息，其中，当该目标节点为物联节点时，该配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程，在本申请实施例提供的业务处理方法中，当策略中需要对编排物联节点时，可以通过策略编排界面对物联节点进行无代码的设备指令配置，从而实现以无代码的方式构造物联设备间的联动控制，提高工业控制效率。
附图说明
图1是本申请实施例提供的业务处理系统的网络架构示意图；
图2是本申请实施例提供的终端的结构示意图；
图3是本申请实施例提供的业务处理方法的一种实现流程示意图；
图4为本申请实施例提供的确定该目标参数标识的赋值信息的实现流程示意图；
图5为本申请实施例提供的业务处理方法的再一种实现流程示意图；
图6为本申请实施例提供的业务处理方法的系统架构示意图；
图7为本申请实施例提供的应用于城轨场景下业务处理方法的再一种系统架构示意图；
图8为本申请实施例提供的物联节点输出变量的生成流程示意图；
图9为本申请实施例提供的策略示意图；
图10为本申请实施例提供的设备配置界面示意图；
图11为本申请实施例提供的基于物模型进行分组后的界面示意图；
图12为本申请实施例提供的指令配置界面示意图；
图13为本申请实施例提供的数据来源为从本策略的其他节点选择的界面示意图；
图14为本申请实施例提供的设置动作节点的数据来源的界面示意图；
图15为本申请实施例提供的将物联节点的输出变量绑定至其他节点的输入变量的界面示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，所描述的实施例不应视为对本申请的限制，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
在以下的描述中，涉及到“一些实施例”，其描述了所有可能实施例的子集，但是可以理解，“一些实施例”可以是所有可能实施例的相同子集或不同子集，并且可以在不冲突的情况下相互结合。
在以下的描述中，所涉及的术语“第一\第二\第三”仅仅是是区别类似的对象，不代表针对对象的特定排序，可以理解地，“第一\第二\第三”在允许的情况下可以互换特定的顺序或先后次序，以使这里描述的本申请实施例能够以除了在这里图示或描述的以外的顺序实施。
除非另有定义，本文所使用的所有的技术和科学术语与属于本申请的技术领域的技术人员通常理解的含义相同。本文中所使用的术语只是为了描述本申请实施例的目的，不是旨在限制本申请。
对本申请实施例进行进一步详细说明之前，对本申请实施例中涉及的名词和术语进行说明，本申请实施例中涉及的名词和术语适用于如下的解释。
1)物模型：是对物理空间中的设备在云端的数字化表示，从属性，服务和事件三个维度分别描述该设备是什么，能做什么，可以对外提供哪些信息。
2)物联平台：提供设备的连接通信能力，支持设备管理，物模型定义等功能。
3)流程编排(策略编排)：通过在交互界面上组合原子业务可以实现一个完整的业务流程。
4)策略平台：提供无代码化的业务流程编排能力，执行能力和监控能力。
5)动作节点：策略平台流程编排中的节点，通过引用实际的动作(服务)来实现节点的功能。
6)物联节点：一种特殊的动作节点，结合了物联技术，具有控制设备的能力。
7)动作：通过一定标准封装业务应用程序接口(API，Application Programming Interface)组成的原子服务，定义了输入参数与输出参数，供流程编排使用。
本申请实施例提供一种业务处理方法、装置、设备和计算机可读存储介质，能够在策略编排界面对物联节点进行无代码配置，以无代码的方式构造物联设备间的联动控制，下面说明本申请实施例提供的业务处理设备的示例性应用，本申请实施例提供的业务处理设备可以实施为笔记本电脑，平板电脑，台式计算机，机顶盒，移动设备(例如，移动电话，便携式音乐播放器，个人数字助理，专用消息设备，便携式游戏设备)、车载设备等各种类型的用户终端，也可以实施为服务器。下面，将说明设备实施为终端时示例性应用。
参见图1，图1是本申请实施例提供的业务处理系统100网络架构示意图，如图1所示，该网络架构包括物联设备200(示例性示出了物联设备200-1、200-2和200-3)、物联平台300和终端400，物联设备200和物联平台300以及物联平台300与终端400通过网络(图1未示出)连接，网络可以是广域网或者局域网，又或者是二者的组合。
物联平台300获取各个物联设备200的设备信息，并对物联设备进行设备分组、确定各个物联设备的物模型。在本申请实施例中，终端400中可以安装有策略编排客户端，或者终端400可以通过浏览器打开策略编排引擎从而进行策略编排。在开始进行策略编排时，在策略编排界面中显示有各种节点，例如包括开始节点、结束节点、动作节点、物联节点、规则节点等，不同类型的节点的显示图标或显示颜色是不同的。用户可以根据自身的业务需求，确定出策略执行涉及的各个目标节点，并将目标节点通过拖拽操作移动至策略编排界面的编辑区域，拖拽进入的目标节点可以是开始节点、结束节点、动作节点、物联节点、规则节点的任意一个或多个，然后对目标节点进行配置，当目标节点包括物联节点时，终端会通过物联平台设置该物联节点所关联的物联设备信息并且通过物联平台提供的物模型信息通过可视化界面进行物联设备的指令配置，从而实现物联设备的无代码配置。
在一些实施例中，物联平台可以为物联网服务器，该物联网服务器可以是独立的物理服务器，也可以是多个物理服务器构成的服务器集群或者分布式系统，还可以是提供云服务、云数据库、云计算、云函数、云存储、网络服务、云通信、中间件服务、域名服务、安全服务、CDN、以及大数据和人工智能平台等基础云计算服务的云服务器。终端400可以是智能手机、平板电脑、笔记本电脑、台式计算机、智能音箱、智能手表、车载终端等，但并不局限于此。
参见图2，图2是本申请实施例提供的终端400的结构示意图，图2所示的终端400包括：至少一个处理器410、存储器450、至少一个网络接口420和用户接口430。终端400中的各个组件通过总线系统440耦合在一起。可理解，总线系统440用于实现这些组件之间的连接通信。总线系统440除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图2中将各种总线都标为总线系统440。
处理器410可以是一种集成电路芯片，具有信号的处理能力，例如通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等，其中，通用处理器可以是微处理器或者任何常规的处理器等。
用户接口430包括使得能够呈现媒体内容的一个或多个输出装置431，包括一个或多个扬声器和/或一个或多个视觉显示屏。用户接口430还包括一个或多个输入装置432，包括有助于用户输入的用户接口部件，比如键盘、鼠标、麦克风、触屏显示屏、摄像头、其他输入按钮和控件。
存储器450可以是可移除的，不可移除的或其组合。示例性的硬件设备包括固态存储器， 硬盘驱动器，光盘驱动器等。存储器450可选地包括在物理位置上远离处理器410的一个或多个存储设备。
存储器450包括易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。非易失性存储器可以是只读存储器(ROM，Read Only Memory)，易失性存储器可以是随机存取存储器(RAM，Random Access Memory)。本申请实施例描述的存储器450旨在包括任意适合类型的存储器。
在一些实施例中，存储器450能够存储数据以支持各种操作，这些数据的示例包括程序、模块和数据结构或者其子集或超集，下面示例性说明。
操作系统451，包括用于处理各种基本系统服务和执行硬件相关任务的系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务；
网络通信模块452，用于经由一个或多个(有线或无线)网络接口420到达其他计算设备，示例性的网络接口420包括：蓝牙、无线相容性认证(WiFi)、和通用串行总线(USB，Universal Serial Bus)等；
输入处理模块453，用于对一个或多个来自一个或多个输入装置432之一的一个或多个用户输入或互动进行检测以及翻译所检测的输入或互动。
在一些实施例中，本申请实施例提供的装置可以采用软件方式实现，图2示出了存储在存储器450中的业务处理装置454，其可以是程序和插件等形式的软件，包括以下软件模块：第一确定模块4541、第一呈现模块4542、第二呈现模块4543、第一获取模块4544和第二确定模块4545，这些模块是逻辑上的，因此根据所实现的功能可以进行任意的组合或进一步拆分。
第一呈现模块4542和第二呈现模块4543，以及其他呈现模块，用于经由一个或多个与用户接口430相关联的输出装置431(例如，显示屏、扬声器等)使得能够呈现信息(例如，用于操作外围设备和显示内容和信息的用户接口)；
将在下文中说明各个模块的功能。
在另一些实施例中，本申请实施例提供的装置可以采用硬件方式实现，作为示例，本申请实施例提供的装置可以是采用硬件译码处理器形式的处理器，其被编程以执行本申请实施例提供的业务处理方法，例如，硬件译码处理器形式的处理器可以采用一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)或其他电子元件。
将结合本申请实施例提供的终端的示例性应用和实施，说明本申请实施例提供的业务处理方法，该业务处理方法应用于图1所示的终端。
参见图3，图3是本申请实施例提供的业务处理方法的一种实现流程示意图，将结合图3示出的步骤对本申请实施例提供的业务处理方法进行说明。
步骤S101，接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点。
在一些实施例中，在步骤S101之前，需要启动策略编排进程，在实现时可以是启动终端中专门用于策略编排的客户端(对应其他实施例中的策略编排平台或策略平台)，还可以是通过浏览器启动策略编排页面。
在启动策略编排进程之后，可以在终端的显示屏上呈现策略编排界面，在策略编排界面的节点标识显示区域可以显示有各种类型的节点标识，例如，可以包括：开始节点、结束节点、动作节点、物联节点、规则节点等。节点标识可以是节点图标，不同类型的节点图标的颜色和/或形状可以是不同的。
第一选择操作可以是拖拽某一节点标识(节点图标)的操作，在本申请实施例中，该第一选择操作可以是一个动作，也可以是一系列动作。当第一选择操作为一个动作时，那么此时选择出的也即为一个目标节点，例如可以是动作节点或者物联节点。当第一选择操作为一系列动作时，那么此时选择出的是多个目标节点，例如可以包括动作节点、物联节点、规则节点、结束节点等等。
步骤S102，在该策略编排界面中呈现该至少一个目标节点。
在本申请实施例中，至少一个目标节点包括物联节点，物联节点是一种特殊的动作节点，结合了物联技术，能够控制连接入物联网的物联设备。
策略编排界面中可以显示有节点标识显示区域、节点编辑区域等，第一选择操作可以是将某一个目标节点从节点标识显示区域拖拽至节点编辑区域，或者是将某几个目标节点依次从节点标识显示区域拖拽至节点编辑区域。此时在节点编辑区域显示目标节点的节点标识。
步骤S103，响应于针对目标节点的配置操作，呈现配置界面。
针对目标节点的配置操作可以是右击目标节点并选择节点配置的选择控件，还可以是双击某个目标节点的操作。在一些实施例中，在策略编排界面中还可以显示有配置项区域，在该配置项区域可以显示有目标节点所需配置信息的互动控件，例如当选中对动作节点进行配置时，配置项区域中显示的所需配置信息的互动控件可以包括配置动作的入口控件、配置输入参数的入口控件、配置输出参数的入口控件，当点击不同的入口控件时，可以呈现相同或不同的配置界面。
再比如，当选中对物联节点进行配置时，配置项区域中显示的所需配置信息的互动控件可以包括配置设备的入口控件，在配置完设备信息后，可以在设备配置界面呈现有配置指令的入口控件，当点击不同的入口控件时，可以呈现不同的配置界面。
步骤S104，响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息。
在本申请实施例中，进行策略编排的终端，或者说策略编排平台与物联平台建立有通信连接，当该目标节点为物联节点时，该配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息。设备配置信息可以包括物联节点对应的物联设备标识、物联设备的设备组标识等，指令配置信息可以包括物联设备需要执行的指令。当目标节点为动作节点时，该配置信息至少包括动作信息、输入参数信息、输出参数信息。
在本申请实施例中，物联设备可以是城轨交通系统中的设备，例如可以是地铁站内的显示屏、电梯、照明设备、闸机、安检设备等等。物联设备还可以是其他场景中的设备，例如可以是安防系统中的监控设备、报警设备等等。
在本申请实施例中，通过配置界面接收到的输入操作可以是一系列操作集合，从而实现对设备信息、指令信息的配置，或者实现对动作信息、输入参数信息、输出参数信息的配置。
在本申请实施例中，将物联平台与进行策略编排的终端建立连接，在策略编排过程中，能够使得用户以无代码的方式来配置物联节点及其他节点，能够构造设备间的复杂联动，且无需关心设备的不同来源与型号，达到在不修改产品代码的情况下，与不同厂商的各种设备进行协调与通信。
步骤S105，当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
在接收到策略编排完成操作时后，基于各个目标节点的配置信息确定目标业务流程，在实现时可以是，首先基于各个目标节点的配置信息，确定不同目标节点之间的输入变量与输出变量之间的绑定关系，然后再基于该绑定关系，确定目标业务流程。
例如有三个目标节点，分别为节点A、节点B和节点C，其中，节点A的输出变量与节点B的输入变量之间具有绑定关系，节点B的输出变量与节点C之间具有绑定关系，那么此时生成的目标业务流程为节点A→节点B→节点C。
在一些实施例中，在确定出不同目标节点之间的输入变量与输出变量之间的绑定关系后，还可以基于该绑定关系，确定不同目标节点之间的连接信息；并基于该连接信息连接对应的目标节点。
基于连接信息连接对应的目标节点在实现可以是，在呈现于策略编排界面的各个目标节点之间呈现带有方向的线段，从而直接呈现目标节点之间的连接关系。
在本申请实施例提供的业务处理方法中，在进行策略编排时，接收到针对策略编排界面中节点标识的第一选择操作后，确定选中的至少一个目标节点，并在该策略编排界面中呈现该至少一个目标节点，该至少一个目标节点至少包括物联节点，之后对各个目标节点进行配置，响应于针对目标节点的配置操作，呈现配置界面；响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息，其中，当该目标节点为物联节点时，该配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程，在本申请实施例提供的业务处理方法中，当策略中需要对编排物联节点时，可以通过策略编排界面对物联节点进行无代码的设备指令配置，从而实现以无代码的方式构造物联设备间的联动控制，提高工业控制效率。
在一些实施例中，当该目标节点为物联节点时，该配置界面包括设备配置界面和指令配置界面，当接收到针对配置设备的入口控件的触发操作时呈现设备配置界面，此时，图3所示的步骤S104“响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息”，可以通过以下步骤实现：
步骤S1041，响应于通过该设备配置界面接收到的设备设置操作，获取该物联节点对应的设备配置信息。
其中，设备配置信息包括设备标识，在一些实施例中，该设备配置信息还可以包括设备组标识。该设备设置操作可以是一系列操作的集合，例如可以包括设备组的选择操作、设备标识的选择操作等。
在设备配置界面还显示有配置指令的入口控件(也即下述的指令配置入口)，在完成对设备信息的配置后，可以通过触发该指令配置入口，呈现指令配置界面。
步骤S1042，响应于针对指令配置入口的触发操作，呈现指令配置界面。
在本申请实施例中，指令配置入口可以包括批量配置入口和单个配置入口，当接收到针对批量配置入口或者接收到单个配置入口的触发操作时，均认为是接收到指令设置操作，从而呈现指令配置界面。通过批量配置入口或者通过单个配置入口的触发操作，所呈现的指令配置界面可以是相同的。
在一些实施例中，指令配置界面是通过解析物联设备的物模型信息而动态生成的，具有 不同物模型信息的物联设备的指令配置界面可以是不同的。
步骤S1043，响应于通过该指令配置界面接收到的指令设置操作，获取配置的设备指令。
指令设置操作同样为一系列的操作，例如可以包括选择指令标识的操作、选择指令参数的操作，以及选择参数来源的操作等。在进行指令设置时，需要按照指令—输入参数—数据来源的层级依次进行配置，从而获取配置的设备指令。
通过上述的步骤S1041至步骤S1043即完成了通过配置界面对物联节点的无代码配置，降低了物联节点的配置复杂度，能够以极低门槛即可实现设备间联动策略的构造与执行。
在一些实施例，上述步骤S1041可以通过以下步骤实现：
步骤S10411，接收针对该设备配置界面中设备组入口的触发操作，在该设备配置界面呈现各个设备组。
在设备配置界面呈现有设备组入口和设备标识的显示区域，当接收到针对设备组入口的触发操作时，可以如图10所示显示各个设备组。在本申请实施例中，设备组也可以具有层级，例如，如图10所示，在最左侧一栏显示的是一级设备组，在选择某一一级设备组后，会在中间一栏显示该一级设备组下属的二级设备组，进而再选择二级设备组，并在设备标识显示区域显示该二级设备组下属的各个设备标识。
步骤S10412，响应于针对该设备组的第二选择操作，获取选中的目标设备组。
该第二选择操作可以是一个操作也可以是多个操作，例如在一些实现场景中，只有一个层级的设备组，那么此时只进行一次设备组的选择即可，而当有多个层级的设备组时，可以进行多次设备组的选择。
继续以图10为例进行说明，18号线、22号线、云上开发环境1、车站模型设备等为一级设备组，在选择“车站模型设备”之后，在中间一栏显示有“车站模型设备”下属的A站模型设备、B站模型设备、客流设备、TEST、车站模型-轨道设备等二级设备组。假设“TEST”为选中的二级设备组，也即“TEST”为目标设备组。
步骤S10413，呈现目标设备组中包括的各个设备标识。
此时可以是在设备配置界面的设备标识显示区域显示目标设备组组的各个设备标识。以图10为例，设备标识显示区域可以是图10中的1002区域。在该区域显示有“TEST”设备组下的设备标识，也即PM01101。
步骤S10414，响应于针对设备标识的第三选择操作，获取选中的至少一个设备标识。
该第三选择操作可以是选择一个设备标识的操作，也可以是选择多个设备标识的操作，例如可以是选择目标设备组中所有设备标识的操作。
在一些实施例中，设备配置界面还呈现有设备控制方式，其中包括并行控制和串行控制，在获取到选中的至少一个设备标识后，可以选择适合的控制方式，当选择串行控制时，需要按照选中的设备标识的顺序一次发出设备指令，并且需要等到本次发出指令的执行结果收到后再向下一个设备发送指令。当选择并行控制时，是同时向至少一个设备标识对应的物联设备发送设备指令，而无需等待执行结果，宏观上是并行的。
通过上述的步骤S10411至步骤S10414，即完成了对物联节点的设备信息配置，最终选择的设备标识，也即与物联节点关联的设备，或者说增加至业务流程的设备。
在一些实施例中，当通过上述步骤S10411至步骤S10414，完成对设备配置信息的设置后，点击图10中的“下一步”按钮控件，会执行以下步骤，以基于物模型对设备进行配置分组：
步骤S201，获取各个设备标识对应的各个物模型信息。
步骤S201在实现时，可以是终端从物联平台获取各个设备标识对应的物模型信息。例如可以是终端向物联平台发送物模型信息的获取请求，该获取请求中携带有各个设备标识，物联平台在接收到该获取请求中，获取各个设备标识，并获取各个设备标识对应的物模型信息，将物模型信息携带于获取响应中发送至终端。终端解析获取响应，获取到各个设备标识对应的各个物模型信息。
步骤S202，基于该各个物模型信息，对各个设备标识进行配置分组，得到分组结果。
该步骤在实现时，是将同一物模型的设备标识分为一组。其中，该分组结果包括至少一个分组标识和各个分组标识对应的设备标识。由于同一物模型的设备是分为一组的，而指令配置界面是根据设备的物模型实现的，因此可以对同一分组下的设备进行批量配置。
步骤S203，在分组界面呈现该各个分组标识和该各个分组标识对应的设备标识。
该分组界面可以是如图11所示的界面，在该分组界面中显示有分组标识，也即“设备组-1”以及该分组下的设备标识，也即PM01101。
在一些实施例中，该分组界面中呈现有指令批量配置入口，如图11所示的“批量配置”控件1102，从而可以通过以下步骤对同一物模型的设备进行批量设置：
步骤S204A，响应于针对分组标识的第四选择操作，选中该分组标识对应的所有设备标识。
该第四选择操作可以是点击图11所示的“全选”控件的操作，此时会选中“设备组-1”的全部设备标识，也即“设备组-1”下的所有设备标识对应的选择控件为选中状态。
在一些实施例中，可以执行步骤S204A，而是通过步骤S204A’选择部分设备：步骤S204A’，响应于针对多个设备标识的第五选择操作，获取选择的多个设备标识。
第五选择操作可以是针对多个设备标识对应的选择控件的选中操作，为一系列操作。
步骤S205A，当接收到针对指令批量配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
指令批量配置入口可以是如图11所示的“批量配置”控件，只有通过步骤S204A或者通过步骤S204A’选择出至少两个设备标识时，图11所示的“批量配置”控件才能被使能，也即该“批量配置”控件才能响应对应的触发操作。
在一些实施例中，该分组界面呈现有指令单独配置入口，例如可以是图11所示的配置项中的“编辑”控件1103，此时可以通过以下步骤对设备进行指令单独设置：
步骤S204B，响应于针对一个设备标识的第六选择操作，获取选择的设备标识。
第六选择操作为针对某一个设备标识对应的选择控件的选中操作，此时获取该设备标识。
步骤S205B，当接收到针对指令单独配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
指令单独配置入口可以是图11中配置项中的“编辑”控件，当仅选择出一个设备标识时，此时点击或者触控“编辑”控件，认为接收到针对指令单独配置入口的触发操作。
在本申请实施例中，不论是接收到指令批量配置入口的触控操作还是接收到指令单独配置入口的触控操作，都认为是接收到针对指令配置入口的触发操作，对应地，上述步骤S1042“响应于针对指令配置入口的触发操作，呈现指令配置界面”，可以通过以下步骤实现：
步骤S10421，响应于针对指令配置入口的触发操作，获取待配置设备对应的物模型信息。
待配置设备可以是一个设备，还可以是多个设备，当待配置设备是多个设备时，该多个设备为属于同一分组的设备，也即该多个设备的物模型是相同的。
步骤S10422，获取该物模型信息中的服务信息。
该服务信息中包括设备可操作的指令，在一个物模型信息中可以有一个服务，也可以有多个服务。
步骤S10423，基于该服务信息生成指令配置界面，并呈现该指令配置界面。
步骤S10423在实现时，可以首先解析该服务信息，确定该待配置设备的至少一个可选指令标识和各个可选指令标识对应的参数标识；之后在该指令配置界面呈现各个可选指令标识、该各个可选指令标识对应的参数标识和各个参数标识的数据来源设置入口。
在实现时，解析服务信息，确定待配置设备的至少一个可选指令标识和各个可选指令标识对应的参数标识，在实现时，可以是将服务信息中“指令名称”对应的字段确定为可选指令标识，可以是将“inputData”中参数名称对应的字段确定为参数标识。之后在指令配置界面呈现可选指令标识、参数标识和数据来源设置入口。
图12为本申请实施例提供的指令配置界面示意图，如图12所示，在该指令配置界面显示有可选指令标识“播放消息”、该可选指令对应的参数标识“消息”，以及数据来源入口1203。
由于物联设备的类别、型号的多样性，不同种类的物联设备，或者说同一种类不同型号的物联设备能够选择的指令都是不尽相同的，因此在上述步骤S10421至步骤S10423中，是根据待配置设备的物模型信息动态生成待配置设备的指令配置界面，能够保证指令配置界面与待配置设备之间的自适应性，进而保证指令配置的正确性。
基于上述呈现出的指令配置界面，上述步骤S1043“响应于通过该指令配置界面接收到的指令设置操作，获取配置的设备指令”，可以通过以下步骤实现：
步骤S10431，响应于针对可选指令标识的第七选择操作，确定选中的目标指令标识。
第七选择操作为针对某一个可选指令的选择操作，也就是说在进行指令配置时，是一条指令、一条指令依次进行配置的。在图12中，由于仅有一个可选指令标识，因此第七选择操作可以是针对播放消息这一可选指令标识的选择操作，并将播放消息确定为目标指令标识。
步骤S10432，响应于针对目标指令标识对应的参数标识的第八选择操作，确定选中的目标参数标识。
在选择出目标指令标识后，会在图12的中间区域显示给目标指令标识对应的参数标识，以供选择，在图12中显示有消息这一个参数标识。第八选择操作可以为针对某一个可选指令的选择操作，继续以图12为例，由于仅有一个参数标识，因此，此时第八选择操作为选中消息这一参数标识的操作。
步骤S10433，响应于针对目标参数标识的数据来源设置入口的触发操作，呈现数据来源设置界面。
该数据来源设置界面至少显示有以下数据来源：手动输入、常量、策略使用方传入、从本策略的其他节点选择。
步骤S10434，响应于通过数据来源设置界面的输入操作，确定该目标参数标识的赋值信息。
通过数据来源设置界面的输入操作可以包括选择数据来源的操作和设置数据来源的设置操作。
步骤S10434在实现时，可以是首先从手动输入、常量、策略使用方传入、从本策略的其他节点选择中选中一种数据来源，并呈现所选数据来源对应的赋值界面，其中，当选择数据来源为手动输入时，那么会呈现一个输入框，以通过该输入框手动输入数据来源的参数值；当选择数据来源为常量时，也同样可以呈现一个输入框，以通过该输入框输入一个常量值，将该常量值确定为目标参数标识的赋值；当选择数据来源为从本策略的其他节点选择时，会呈现节点选择框和节点的输出参数选择框，并通过针对节点选择框的选择操作和节点的输出参数选择框的选择操作，确定目标参数标识的赋值信息。
在本申请实施例中，确定该目标参数标识的赋值信息，也即确定目标参数标识对应的输入信息。
步骤S10435，基于该目标指令标识、该目标参数标识和该赋值信息确定配置的设备指令。
在上述步骤S10431至步骤S10435中，按照可选指令—参数标识—数据来源的层级，通过可视化的方式对待配置设备的指令进行配置，从而实现设备指令的无代码配置，能够降低配置难度，提高配置效率。
在一些实施例中，当通过该数据来源设置界面接收到选择数据来源为从本策略的其他节点选择的第八选择操作时，上述步骤S10434“响应于通过数据来源设置界面的输入操作，确定该目标参数标识的赋值信息”，可以通过图4所示的步骤S4341至步骤S4347以下步骤实现：
步骤S4341，呈现节点选择入口和输出参数选择入口。
图13为本申请实施例提供的数据来源为从本策略的其他节点选择的界面示意图，如图13所示，当选择数据来源为从本策略的其他节点选择时，会呈现节点选择入口1301和输出参数选择入口1302。
步骤S4342，响应于针对该节点选择入口的触发操作，呈现至少一个可选节点，接收针对可选节点的第九选择操作，确定目标来源节点。
该触发操作可以是点击或者触控该节点选择入口的操作，当接收到该触发操作后，呈现至少一个可选节点。第九选择操作可以是针对某一个可选节点的选择操作，也即通过第九选择操作选择出的是一个目标来源节点。
步骤S4343，判断目标来源节点为动作节点还是物联节点。
其中，当目标来源节点为动作节点时，进入步骤S4344；当目标来源节点为物联节点时，进入步骤S4347。
步骤S4344，当该目标来源节点为动作节点时，响应于针对输出参数选择入口的触发操作，呈现该目标来源节点的至少一个输出参数标识。
针对输出参数选择入口的触发操作可以是点击或者触控输出参数选择入口。
当数据来源选择其他节点时，说明是将其他节点的输出作为本节点的输入，因此在接收到该触发操作后，呈现目标来源节点的至少一个输出参数标识。对于动作节点来说，输出参数标识是预先定义好的，因此可以在接收到针对输出参数选择入口的触发操作后，直接获取并显示该目标来源节点的至少一个输出参数标识即可。
如图13所示，作为数据来源的节点为“获取动态消息”这一动作节点，此时，可以在接收到针对参数选择入口的触控操作后，直接显示该动作节点的输出参数，也即为“广播消息”。
步骤S4345，基于针对该至少一个输出参数标识的第十选择操作，确定目标输出参数标识。
第十选择操作为从至少一个输出参数标识中选择其中一个作为目标输出参数标识的操作。
步骤S4346，将该目标输出参数标识的输出值确定为该目标参数标识的赋值信息。
通过步骤S4346，也即将目标输出参数标识的输出值确定为本物联节点中目标参数标识对应的输入值。
步骤S4347，当该目标来源节点为物联节点时，响应于针对输出参数选择入口的触发操作，呈现输出参数选择界面。
在本申请实施例中，“确认广播结果”这一动作节点的目标来源节点为物联节点“显示屏广播消息”，在通过图14所述的界面选择出动作节点“确认广播结果”的数据来源为“从本策略的其他节点选择”，并且选择物联节点“显示屏广播消息”之后，点击图14中的针对输出参数选择入口1401的触发操作后，显示输出参数选择界面1402，该输出参数选择界面显示有所述目标来源节点的至少一个可选输出参数，所述可选输出参数包括设备类输出参数和非设备类输出参数。在图14中输出参数选择界面1402中显示有代码是否执行成功、设备是否全部执行成功、设备执行结果三个输出参数，其中，设备执行结果为设备类输出参数，也即该输出参数是通过物联设备执行相关指令后的指令执行结果，可以认为是设备级输出参数，而代码是否执行成功、设备是否全部执行成功为非设备类输出参数，反映指令的整体执行状况。
在一些实施例中，当接收到针对非设备类输出参数的第十三选择操作时，那么基于选择出的非设备类输出参数确定该目标参数标识的赋值信息，进一步地，是将策略执行时，物联节点的该非设备类输出参数的动态输出值确定为目标参数标识的输入值。
步骤S4348，当接收到针对设备类输出参数的第十二选择操作时，呈现该输出参数设置界面。
输出参数设置界面如图15所示，该输出参数设备界面包括该物联节点的设备标识选择入口1501、设备指令选择入口1502和输出参数选择入口1503。
步骤S4349，响应于通过该输出参数设置界面的输入操作，确定所述目标参数标识的赋值信息。
步骤S4349可以通过以下两个步骤实现：
第一步，按照设备至指令至输出参数的层级结构，分别通过针对设备标识选择入口、设备指令选择入口和输出参数选择入口的触发操作，确定目标设备标识、目标设备指令和目标输出参数标识。
在实现时，可以是先通过针对设备标识选择入口的触发操作，呈现可选的设备标识，然后从可选的设备标识中选择出一个作为目标设备标识，在选择出目标设备标识后，当接收到针对设备指令选择入口的触发操作时，呈现该目标设备标识对应的可选设备指令，并从可选设备指令中选择出一个作为目标设备指令，当接收到针对输出参数选择入口的触发操作时，呈现该目标设备指令对应的可选输出参数标识，进而从可选输出参数标识中选择出一个作为目标输出参数标识。
第二步，基于该目标设备标识、目标设备指令和目标输出参数标识确定该目标参数标识的赋值信息。
目标参数标识的赋值信息，也即目标参数标识的输入信息，通过该步骤即可将作为数据来源的物联节点中目标设备标识对应的目标设备指令标识中目标输出参数标识的输出信息作为目标参数标识的输入信息。
通过上述步骤S4341至步骤S4349即可完成通过数据来源设置界面的输入操作，确定该目标参数标识的赋值信息，通过可视化的方式，只需要通过点选操作，就能够完成目标节点中目标参数标识的输入变量的绑定，从而提高配置效率。
由于物联节点的输出变量为设备控制的结果，与选择的设备有关，无法事先定义，因此在配置完设备指令后，可以通过以下步骤结合物联设备的物模型动态生成节点的输出变量：
步骤S301，向物联平台发送物模型信息的获取请求。
该获取请求中携带有各个设备标识；物联平台在接收到该获取请求中，获取各个设备标识，并获取各个设备标识对应的物模型信息，将物模型信息携带于获取响应中发送至终端。
步骤S302，接收物联平台发送的获取响应，获得所述获取响应中携带的各个设备标识对应的各个物模型信息。
终端接收到该获取响应后，解析该获取响应，获取到各个设备标识对应的各个物模型信息。
步骤S303，解析该物模型信息，获取配置的设备指令的输出参数定义。
在实现时，可以是通过获取物模型信息中的“outputData”部分，从而获取出所配置的设备指令中对输出参数的定义。
步骤S304，基于该设备配置信息、设备指令和输出参数定义确定该物联节点的输出描述信息。
在实现时，可以是按照设备至指令至输出参数的层级结构，建立设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义的一一对应关系；然后将各个对应关系中的设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义按照预设描述格式动态生成所述物联节点的输出描述信息。
假设配置的有两个设备标识，分别为设备1和设备2，设备1配置的指令有指令1和指令2，设备2配置的指令为指令1，指令1下的输出参数定义有参数A，指令2下的输出参数定义有参数B，那么会构建以下对应关系：设备1-指令1-参数A、设备1-指令2-参数B、设备2-指令1-参数A。进而根据以上对应关系中的内容按照预设描述格式生成该物联节点的输出描述信息，在实现时可以是按照JSON的格式生成输出描述信息并存储下来。
步骤S305，将该输出描述信息挂载到该物联节点的输出变量上。
在上述步骤S301至步骤S305所在的实施例中，物联节点的输出变量并不是一个具体的变量，而是一段描述信息。该描述信息能够指示该物联节点控制了的设备信息，每个设备控制的指令，以及各个指令中包括的输出参数，如此能够结合物模型动态生成物联节点的输出变量，从而保证输出变量的自适应性。
在一些实施例中，当该目标节点为动作节点时，图3所示的步骤S104“响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息”可以通过以下步骤实现：
步骤S1041’，响应于针对该配置界面中动作选择入口的触发操作，呈现至少一个可选动作。
动作选择入口的触发操作可以是右击目标节点的操作，还可以是双击目标节点的操作。当接收到该触发操作后，可以呈现至少一个可选动作。
步骤S1042’，响应于针对该至少一个可选动作的第十一选择操作，确定目标动作。
在该步骤中，可以从至少一个可选动作中选择出一个作为目标动作。在一些实施例中，当可选动作比较多时，还可以支持用户输入关键字，进而筛选出与关键字匹配的动作，然后再从与关键字匹配的动作中确定目标动作。
步骤S1043’，获取该目标动作预设的输出参数信息。
对于动作节点来说，各个动作的输出参数信息，例如可以包括输出参数标识、输出参数类型等，都是预先设置好的，当选择出一个动作后，该动作的输出参数信息也就可以直接获取到。
步骤S1044’，将该目标动作和该输出参数信息确定为该目标节点的配置信息。
通过上述步骤S1041’至步骤S1044’，即可完成对动作节点的配置。
基于前述的实施例，本申请实施例再提供一种业务处理方法，图5为本申请实施例提供的业务处理方法的再一种实现流程示意图，如图5所示，该流程包括：
步骤S501，终端启动策略编排进程，并呈现策略编排界面。
这里，终端可以是通过启动已安装好的策略编排应用程序客户端，还可以是启动策略编排引擎，以启动策略编排进程，并呈现策略编排界面。在本申请实施例中进行一个应用于城轨交通系统中的业务流程的策略编排。假设该业务流程为，在获取到地铁内异常报警信息后，使用显示屏播放报警信息，并确定广播是否播放。该报警信息可以是列车故障触发的，还可以是出现火情触发的，还可以是其他原因触发的。
步骤S502，终端接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点。
在上述需要编排的业务流程中，除了开始节点和结束节点之外，还需要三个节点，其中第一个为动作节点，用于获取报警信息，第二个为物联节点，用于播放报警信息，第三个为动作节点，用于确认是否播放成功，因此在该步骤中，选择的目标节点可以为两个动作节点和一个物联节点。为了便于说明，第一个动作节点为节点A，第一个物联节点为节点B，第二个动作节点为节点C。
步骤S503，终端在该策略编排界面中呈现该至少一个目标节点。
在至少一个目标节点中包括物联节点，当然，目标节点还可以是动作节点、规则节点等。此时在策略编排界面呈现节点A、B、C。
步骤S504，当目标节点为物联节点时，终端响应于通过该设备配置界面接收到的设备设置操作，获取该物联节点对应的设备配置信息。
其中，设备配置信息包括设备标识。在一些实施例中，设备配置信息还可以包括设备组标识、设备标签等。步骤S504在实现时，可以是终端通过物联平台获取连入该物联平台的物联设备的设备分组信息、设备标识信息等，从而基于接收到的设备分组信息、设备标识信息等进行物联节点对应设备信息的配置。
并且由于节点B是在节点A获取到报警信息之后执行的，因此在对节点B配置之前，已经可以通过动作节点的配置界面完成了对节点A的配置过程，在步骤S504中，是对节点B的设备信息进行配置，在实现时，可以是通过图10、图11所示的界面完成设备信息的配置。
步骤S505，终端响应于针对指令配置入口的触发操作，向物联平台发送物模型信息的获取请求。
该获取请求中携带有在步骤S504中所获取到的设备配置信息包括的设备标识。
步骤S506，物联平台接收该获取请求，并获取该获取请求中携带的设备标识。
步骤S507，物联平台获取该设备标识对应的物模型信息。
物模型信息包括设备基本信息、设备属性信息、设备事件、设备可操作的指令(也即设备服务)。
步骤S508，物联平台将携带有物模型信息的获取响应发送至终端。
步骤S509，终端接收获取响应，并获取该获取响应携带的物模型信息。
步骤S510，终端获取该物模型信息中的服务信息。
由于物模型信息中的服务信息能够表征设备可操作的指令，而不同物模型的物联设备所能操作的指令可能是不同的，因此在该步骤中获取服务信息，以在后续步骤中通过服务信息生成该物模型对应的指令配置界面。
步骤S511，终端基于该服务信息生成指令配置界面，并呈现该指令配置界面。
在该步骤中，基于服务信息生成指令配置界面，可以是通过解析服务信息，获取服务信息中的指令标识、输入参数标识，从而在该指令配置界面中呈现如图12所示的，指令标识—参数标识—数据来源这三级配置入口，以通过这三级配置入口进行指令配置。
步骤S512，终端响应于通过该指令配置界面接收到的指令设置操作，获取配置的设备指令。
通过该步骤即完成了对节点B的指令配置。
步骤S513，终端解析该物联节点对应的物模型信息，获取配置的设备指令的输出参数定义。
输出参数定义是对物联设备发送指令后返回结果的描述，每个指令都会有自己的返回结果。那么通过组合物模型中设备指令的输出参数就可以生成物联节点的输出描述。
步骤S514，终端基于该设备配置信息、设备指令和输出参数定义确定该物联节点的输出描述信息。
在本申请实施例中，可以是按照设备—指令—输出参数的层级结构生成物联节点的输出描述信息，并按照预设格式存储。
步骤S515，终端将该输出描述信息挂载到该物联节点的设备类输出参数上。
在本申请实施例中，由于节点C的输入参数为节点B的设备类输出参数，因此，可以通过图14和图15所示的界面，完成节点B的设备类输出参数与节点C输入参数的可视化绑定。
步骤S516，当终端接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
在本申请实施例中目标业务流程为：节点A(获取报警信息)→节点B(显示屏播放报警信息)→节点C(确定播放结果)，也就是说，在地铁系统出现报警信息时，报警信息会作为节点B的输入，此时节点B控制的显示屏就会通过语音、视频的方式播放报警信息，然后再进一步确定是否播放成功，以确认报警信息是否发送出去。
步骤S516在实现时，可以是通过各个目标节点的配置信息，确定不同目标节点之间输出变量和输入变量的绑定关系，并进行基于绑定关系确定目标业务流程。
需要说明的是，本申请实施例中与其他实施例相同的步骤或术语请参照其他实施例中的说明。
在本申请实施例提供的业务处理方法中，终端在启动策略编排进程后，呈现策略编排界面，并且通过策略编排界面中针对节点标识的第一选择操作，确定选中的至少一个目标节点， 进而在该策略编排界面中呈现该至少一个目标节点，在该至少一个目标节点中包括物联节点；当目标节点为物联节点时，终端响应于通过该设备配置界面接收到的设备设置操作，基于物联平台获取该物联节点对应的设备配置信息，其中，设备配置信息包括设备标识；之后终端响应于针对指令配置入口的触发操作，向物联平台发送物模型信息的获取请求，物联平台在基于获取请求中携带的设备标识获取到对应的物模型信息之后，向终端返回物模型信息，在对指令进行配置时，终端是基于物模型中的服务信息，动态生成指令配置界面，并呈现该指令配置界面，并通过该指令配置界面接收到的指令设置操作，进行设备指令的配置，并且物联节点的输出变量也是根据物模型中输出参数的定义而动态生成的，从而保证物联节点的输出变量为物联设备的控制结果，保证输出准确性；当终端接收到策略编排完成操作时时，基于各个目标节点的配置信息确定目标业务流程；如此将物联网与流程编排技术进行集成，为城轨行业、安防控制等场景提供一种无代码业务及设备编排的方式，同时本申请实施例中提出的动态生成物联节点输出变量及可视化绑定的方案，很好的解决了流程编排与物联网技术融合的问题，保证目标业务流程的准确性和有效性。
下面，将说明本申请实施例在一个实际的应用场景中的示例性应用。
图6为本申请实施例提供的业务处理方法的系统架构示意图，如图6所示，该系统架构包括：物联设备601、物联平台602和业务处理设备(策略平台)603，其中：
物联设备601中包括多个连接入物联网的物理设备，例如可以是城轨物理设备；
物联平台602，用于进行物理设备的设备分组、确定设备标签，并进行物模型管理；
业务处理设备(策略平台)603，和物联平台602相连，并利用物联平台提供的设备分组信息、设备标签信息和物模型进行策略编排、策略管理和模板管理，在指定出策略后，利用策略执行器执行策略，并通过物联平台602中的控制设备控制对应的物理设备。
本申请实施例中的策略平台，对应其他实施例中的策略编排平台。
图7为本申请实施例提供的应用于城轨场景下业务处理方法的再一种系统架构示意图，与图6类似，在该系统架构中，包括城轨设备701、物联平台702和策略平台703，在该策略平台中，需要编排动作节点7031→物联节点7032→动作节点7033的策略，图7中示出了物联节点的配置过程，如图7所示，该配置过程包括：选择设备711、设备预览712、模型分组713、批量配置714、模型解析715、界面生成716、配置指令717。其中，在选择设备711中，需要基于从物联平台获取设备分组信息和设备标签信息进行设备选择，在进行模型分组时，需要从物联平台获取物模型，并从将相同物模型的设备分为一组；在从模型解析到界面生成的过程在实现时，同样需要基于从物联平台获取的物模型，解析物模型，从而动态生成命令控制界面(也即其他实施例中的指令配置界面)。命令控制界面是根据物模型中的服务(Service)动态生成的，一个设备可以有多个服务，一个服务可以有多个入参。
并且通过图7可以看出，通过动作节点输出的是预设的普通变量、通过物联节点输出的是动态变量。
在本申请实施例中，以显示屏物模型为例进行说明。以下为显示屏物模型的定义。
Figure PCTCN2022087153-appb-000001
Figure PCTCN2022087153-appb-000002
Figure PCTCN2022087153-appb-000003
物模型定义中共有4种内容：Profile(设备基本信息)、Properties(设备的属性)、Events(设备事件)、Service(设备服务，即设备可操作的指令，一个设备可有多个服务)。
通过上述显示屏的物模型定义可以看出，这个显示屏的物模型只有一个服务—播放消息，同时这个服务下只有一个入参，也即消息，是字符串类型的。
动作节点的输出变量是事先在动作中定义的，只需要将动作的出参挂载到节点的输出变量上即可。而物联节点的输出变量为设备控制的结果，与选择的设备有关，无法事先定义，因此，在本申请实施例中，将结合物模型动态生成节点的输出变量。当用户配置完设备指令后，节点输出变量的生成流程包括如图8所示的各个步骤：
步骤S801，获取所选设备的物模型。
步骤S802，解析物模型。
步骤S803，提取所选指令的出参定义。
步骤S804，以设备-指令-出参的结构组合指令出参。
步骤S805，生成节点出参描述。
步骤S806，挂载到物联节点的输出变量上。
在上述显示屏的物模型定义中，显示屏指令中的出参定义(outputData)即是对设备发送指令后返回结果的描述，每个指令都会有自己的返回结果。那么通过组合物模型中设备指令的出参就可以生成物联节点的输出描述，以一定格式(JSON)存储下来，最后挂载到物联节点的输出参数上(devices)。该输出参数是一个特殊类型(Device)的出参。在本申请实施例中，该物联节点还可以包含动态生成的非设备级的输出参数，可根据实际需求进行扩展。
以下为物联节点输出参数的例子：
Figure PCTCN2022087153-appb-000004
Figure PCTCN2022087153-appb-000005
其中，“Activity0oqhb04”代表当前物联节点的id，它在每个策略中是唯一的。“filedKey”为节点出参标识，在一个节点内是唯一的，“outKey”为节点出参的对外标识，在一个策略内是唯一的，以“节点id+节点出参”的形式表示。
物联节点的输出变量并不是一个具体的变量，而是一段描述。这段描述指示了这个节点控制了哪些设备，每个设备控制了哪些指令，每个指令有哪些出参。
物联节点的输出变量会在其他节点中被引用(绑定)，作为其他节点的输入。但由于它的输出变量是一段描述，不是具体的变量，不可直接绑定到后面节点的入参中。因此在绑定时，通过解析物联节点的输出变量devices，以“设备–指令–出参”的层级结构生成可视化界面，用户只需要点选，即可将选择的出参绑定到其他节点的输入变量上。
下面是当前节点入参绑定物联节点出参的例子：
Figure PCTCN2022087153-appb-000006
这里的value是一个替代量，指示了当前入参绑定的是id为Activity0oqhb04的物联节点中指定设备[768100001-5a9d2b4579074afeb073c63a0125bc17]的sendMessage服务的success出参。
其中，“filedKey”为当前节点的入参标识，在同一节点内是唯一的。“souce”为入参的数据来源。“value”在当前情况下是一个替代量，指示了当前入参绑定是的另外一个节点(Activity0oqhb04)的出参(devices)，由于它是物联节点，进一步指定了id为“768100001-5a9d2b4579074afeb073c63a0125bc17”的设备的“sendMessage”服务的“success”出参。
以下以业务处理方法在城轨行业中的应用为例进行说明。
城轨行业中，业务侧的关于工业控制的场景化需求与迭代复杂且多变，且对于不同厂商及系统的设备控制联动十分困难。所以本发明将城轨设备通过物联网技术进行物模型接入与统一管理，打破设备间的联动壁垒，并通过策略引擎的策略编排能力与物模型进行深度集成，实现用户无需代码基础，以极低门槛即可实现设备间联动策略的构造与执行。
用户可以在策略编排界面上通过拖入物联节点无代码的配置设备控制指令。在物联节点中通过设备分组或标签可快速筛选需要控制的设备，这里可以选择1个或多个设备。同一物模型下的设备会被分配到一个配置组里，实现批量配置。并根据物模型动态生成设备的指令配置界面及此节点的输出变量，实现无代码配置。其他节点通过可视化选择的方式来绑定物联节点的动态输出变量。
下面以一个实际场景来描述物联与编排技术融合的产品表现—显示屏设备广播消息，策略如图9所示，包括：开始—获取动态消息—显示屏广播消息—确认广播结果—结束。
在该策略中共有3个节点：
获取动态消息901：动作节点，用来获取消息，并将消息以变量形式输出供后面节点使用。
显示屏广播消息902：物联节点，对显示屏设备进行指令配置，这里会接收上一个节点的消息变量，并将设备控制结果以变量形式输出。
确认广播结果903：动作节点，用来确认广播结果，需要接收物联节点的输出变量作为本节点的输入。
该策略的编排步骤如下：
第一步，在编排界面上拖入动作节点，并选择平台中的动作-“获取动态消息”，该动作节点有一个出参—消息。
第二步，在编排界面上拖入物联节点，这个节点集成物联平台提供的能力，用户可以根据设备分组/标签来筛选需要控制的设备，可以选择多个，并可以设置串行或并行控制。
图10为本申请实施例提供的选择需要控制的设备的界面示意图，如图10所示，可以通过图10中设备分组1001，选择需要控制的设备所在分组，例如可以选择车站模型设备，然后再选择该设备分组下的设备，在如图10所示的选择框1002中，选中了设备PM01101。
第三步，点击图10中的“下一步”按钮控件1003，物联节点会根据物模型对所选的设备进行分组，并呈现图11所示的界面。同一物模型的设备可以进行批量配置，在实现时，可以通过图11可以选择多个设备，例如，可以是勾选图11所示的“全选”控件1101，之后点击“批量配置”1102，就进入了如图12所示的指令配置界面，在一些实施例中，还可以是选中多个设备对应的选中框，以选择多个设备。
当需要对单个设备进行指令配置时，在选中单个设备后，可以点击图11的配置项中的“编辑”控件1103，同样可以进入如图12所示的指令配置界面。
第四步，配置设备指令。
在本申请实施例中，图12所示的指令配置界面是策略平台获取到待设置设备的物模型，然后对物模型的服务信息进行解析而动态生成的，在该指令设置界面中，以服务-服务的输入参数-数据来源的层级进行显示。以上述显示屏的物模型为例进行说明，该显示屏的物模型中，只有一个服务(播放消息)，该服务只有一个输入参数(消息)，因此，在该指令设置界面中显示有播放消息-消息-数据来源。如果待配置设备具有多个服务，或者某个服务有多个输入参数时，那么在点击图12最左侧的操作控件1201时，可以呈现所有可选指令，当选择好指令后，点击中间的操作控件1202，可以显示该指令的所有输入参数，选择其中一个，然后再基于最右侧的操作控件1203选择数据来源。
在本申请实施例中，指令入参的赋值(也即数据来源)有图12所示的4种方式：
手动输入：用户自己输入；
常量：选择策略平台中定义的常量；
策略使用方传入：策略的入参，启动策略时传入；
从本策略的其他节点选择：可以从前面节点的输出变量中选择。
在本申请实施例中，由于物联节点的数据来源为“获取动态消息”这一动作节点，因此，如图13所示，此时数据来源选择“从本策略的其他节点选择”，此时，会显示选择节点和出参的两个选择控件，分别为1301和1302，此时选择节点为“获取动态消息”，出参为“消息”。这样就将上一节点的输出变量与当前指令的输入变量进行绑定，如此，上一个节点获得消息就 会传送到这个指令中。
第五步，在编排界面上拖入动作节点，并选择平台中的动作—“确认广播结果”，该动作节点有一个入参—广播结果，即上一物联节点的设备控制结果。
如图14所示，为该动作节点选择的数据来源为“从本策略的其他节点选择”，并且选择的节点为“显示屏广播消息”，由于“显示屏广播消息”的节点为物联节点，那么也就是说，需要将物联节点“显示屏广播消息”的输出变量与该动作节点“确认广播结果”的输入参数进行绑定，此时可以点击图14所示的“出参”选择控件1401，从而呈现图15所示的界面。如图15所示，按照设备-指令-出参的层级，通过设备选择控件1501选择物联节点控制的设备PM01101，通过指令选择控件1502选择设备控制的指令“播放消息”，通过出参选择控件1503选择该指令的出参“执行是否成功”。如此，即通过图15所示的可视化方式完成物联节点输出变量与此入参的绑定。
在上述策略编排的实现过程中，可以在策略编排界面上通过拖入物联节点以无代码形式进行设备控制指令的配置。在物联节点中通过设备分组或标签可快速筛选需要控制的设备，并且可以选择1个或多个设备。同一物模型下的设备会被分配到一个配置组里，实现批量配置。并根据物模型动态生成设备的指令配置界面及此节点的输出变量，实现无代码配置。其他节点通过可视化选择的方式来绑定物联节点的动态输出变量。在本申请实施例中，通过集成物联网和流程编排技术，对城轨场景下的设备进行物模型抽象及统一管理，并将物联平台的物模型引入到流程编排中，从而使用户以无代码的方式来构造设备间的复杂联动，且无需关心设备的不同来源与型号，达到在不修改产品代码的情况下，与不同厂商的各种设备进行协调与通信。
下面继续说明本申请实施例提供的业务处理装置454的实施为软件模块的示例性结构，在一些实施例中，如图2所示，存储在存储器450的业务处理装置454中的软件模块可以包括：
第一确定模块4541，用于接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点；
第一呈现模块4542，用于在该策略编排界面中呈现该至少一个目标节点，该至少一个目标节点包括物联节点；
第二呈现模块4543，用于响应于针对目标节点的配置操作，呈现配置界面；
第一获取模块4544，用于响应于通过该配置界面接收到的输入操作，获取该目标节点的配置信息，其中，当该目标节点为物联节点时，该配置信息至少包括设备配置信息和指令配置信息；
第二确定模块4545，用于当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
在一些实施例中，当该目标节点为物联节点时，该配置界面包括设备配置界面和指令配置界面，该第一获取模块，还用于：
响应于通过该设备配置界面接收到的设备设置操作，获取该物联节点对应的设备配置信息，该设备配置信息包括设备标识；
响应于针对指令配置入口的触发操作，呈现指令配置界面，所述指令配置界面是基于物 联设备的物模型信息动态生成的；
响应于通过该指令配置界面接收到的指令设置操作，获取配置的设备指令。
在一些实施例中，该装置还包括：
第一发送模块，用于向物联平台发送物模型信息的获取请求，所述获取请求中携带有各个设备标识；
第一接收模块，用于接收物联平台发送的获取响应，获得所述获取响应中携带的各个设备标识对应的各个物模型信息；
第二获取模块，用于解析所述物模型信息，获取配置的设备指令的输出参数定义；
信息生成模块，用于基于各个设备标识、设备指令和输出参数定义动态生成所述物联节点的输出描述信息；
挂载模块，用于将所述输出描述信息挂载到所述物联节点的设备类输出参数上。
在一些实施例中，该信息生成模块，还用于：
按照设备至指令至输出参数的层级结构，建立设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义的一一对应关系；
将各个对应关系中的设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义按照预设描述格式动态生成所述物联节点的输出描述信息。
在一些实施例中，该第一获取模块，还用于：
接收针对该设备配置界面中设备组入口的触发操作，在该设备配置界面呈现各个设备组；
响应于针对该设备组的第二选择操作，获取选中的目标设备组；
呈现目标设备组中包括的各个设备标识；
响应于针对设备标识的第三选择操作，获取选中的至少一个设备标识。
在一些实施例中，该装置还包括：
第三获取模块，用于获取各个设备标识对应的各个物模型信息；
分组模块，用于基于该各个物模型信息，对各个设备标识进行配置分组，得到分组结果，其中，该分组结果包括至少一个分组标识和各个分组标识对应的设备标识；
第三呈现模块，用于在分组界面呈现该各个分组标识和该各个分组标识对应的设备标识。
在一些实施例中，该分组界面呈现有指令批量配置入口，该装置还包括：
选择模块，用于响应于针对分组标识的第四选择操作，选中该分组标识对应的所有设备标识；或者，
第四获取模块，用于响应于针对多个设备标识的第五选择操作，获取选择的多个设备标识；
第三确定模块，用于当接收到针对指令批量配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
在一些实施例中，该分组界面呈现有指令单独配置入口，该装置还包括：
第五获取模块，用于响应于针对一个设备标识的第六选择操作，获取选择的设备标识；
第四确定模块，用于当接收到针对指令单独配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
在一些实施例中，该第一获取模块，还用于：
响应于针对指令配置入口的触发操作，获取待配置设备对应的物模型信息；
获取该物模型信息中的服务信息；
解析该服务信息，确定该待配置设备的至少一个可选指令标识和各个可选指令标识对应的参数标识；
在该指令配置界面呈现各个可选指令标识、该各个可选指令标识对应的参数标识和各个参数标识的数据来源设置入口。
在一些实施例中，该第一获取模块，还用于：
响应于针对可选指令标识的第七选择操作，确定选中的目标指令标识；
响应于针对目标指令标识对应的参数标识的第八选择操作，确定选中的目标参数标识；
响应于针对目标参数标识的数据来源设置入口的触发操作，呈现数据来源设置界面；
响应于通过数据来源设置界面的输入操作，确定该目标参数标识的赋值信息；
基于该目标指令标识、该目标参数标识和该赋值信息确定配置的设备指令。
在一些实施例中，该数据来源设置界面至少显示有以下数据来源：手动输入、常量、策略使用方传入、从本策略的其他节点选择，该第一获取模块，还用于：
当通过该数据来源设置界面接收到选择数据来源为从本策略的其他节点选择的第八选择操作时，呈现节点选择入口和输出参数选择入口；
响应于针对该节点选择入口的触发操作，呈现至少一个可选节点，接收针对可选节点的第九选择操作，确定目标来源节点；
当该目标来源节点为动作节点时，响应于针对输出参数选择入口的触发操作，呈现该目标来源节点的至少一个输出参数标识，基于针对该至少一个输出参数标识的第十选择操作，确定目标输出参数标识；
将该目标输出参数标识的输出值确定为该目标参数标识的赋值信息。
在一些实施例中，该第一获取模块，还用于：
当该目标来源节点为物联节点时，响应于针对输出参数选择入口的触发操作，呈现输出参数选择界面，所述输出参数选择界面显示有所述目标来源节点的至少一个可选输出参数，所述可选输出参数包括设备类输出参数和非设备类输出参数；
当接收到针对设备类输出参数的第十二选择操作时，呈现所述输出参数设置界面；
响应于通过所述输出参数设置界面的输入操作，确定所述目标参数标识的赋值信息。
在一些实施例中，所述输出参数设置界面包括所述物联节点的设备标识选择入口、设备指令选择入口和输出参数选择入口，该第一获取模块，还用于：
按照设备至指令至输出参数的层级结构，分别通过针对设备标识选择入口、设备指令选择入口和输出参数选择入口的触发操作，确定目标设备标识、目标设备指令和目标输出参数标识；
基于所述目标设备标识、目标设备指令和目标输出参数标识确定所述目标参数标识的赋值信息，其中，所述目标赋值信息为所述目标设备标识对应的物联设备执行所述目标设备指令后所述目标输出参数标识对应的输出信息。
在一些实施例中，当该目标节点为动作节点时，该第一获取模块，还用于：
响应于针对该配置界面中动作选择入口的触发操作，呈现至少一个可选动作；
响应于针对该至少一个可选动作的第十一选择操作，确定目标动作；
获取该目标动作预设的输出参数信息；
将该目标动作和该输出参数信息确定为该目标节点的配置信息。
在一些实施例中，该第二确定模块，还用于：
基于各个目标节点的配置信息，确定不同目标节点之间的输入变量与输出变量之间的绑定关系；
基于该绑定关系，确定目标业务流程；
该装置还包括：
第六确定模块，用于基于该绑定关系，确定不同目标节点之间的连接信息，基于该连接信息连接对应的目标节点。
本申请实施例提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行本申请实施例提供的上述方法。
本申请实施例提供一种存储有可执行指令的计算机可读存储介质，其中存储有可执行指令，当可执行指令被处理器执行时，将引起处理器执行本申请实施例提供的方法，例如，如图3、图4和图5示出的方法。
在一些实施例中，计算机可读存储介质可以是FRAM、ROM、PROM、EPROM、EEPROM、闪存、磁表面存储器、光盘、或CD-ROM等存储器；也可以是包括上述存储器之一或任意组合的各种设备。
在一些实施例中，可执行指令可以采用程序、软件、软件模块、脚本或代码的形式，按任意形式的编程语言(包括编译或解释语言，或者声明性或过程性语言)来编写，并且其可按任意形式部署，包括被部署为独立的程序或者被部署为模块、组件、子例程或者适合在计算环境中使用的其它单元。
作为示例，可执行指令可以但不一定对应于文件系统中的文件，可以可被存储在保存其它程序或数据的文件的一部分，例如，存储在超文本标记语言(HTML，Hyper Text Markup Language)文档中的一个或多个脚本中，存储在专用于所讨论的程序的单个文件中，或者，存储在多个协同文件(例如，存储一个或多个模块、子程序或代码部分的文件)中。
作为示例，可执行指令可被部署为在一个计算设备上执行，或者在位于一个地点的多个计算设备上执行，又或者，在分布在多个地点且通过通信网络互连的多个计算设备上执行。
以上所述，仅为本申请的实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和范围之内所作的任何修改、等同替换和改进等，均包含在本申请的保护范围之内。

Claims (15)

  1. 一种业务处理方法，其特征在于，包括：
    接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点；
    在所述策略编排界面中呈现所述至少一个目标节点，所述至少一个目标节点包括物联节点；
    响应于针对目标节点的配置操作，呈现配置界面；
    响应于通过所述配置界面接收到的输入操作，获取所述目标节点的配置信息，其中，当所述目标节点为物联节点时，所述配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，所述物联平台与进行策略编排的终端建立有通信连接；
    当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
  2. 根据权利要求1中所述的方法，其特征在于，当所述目标节点为物联节点时，所述配置界面包括设备配置界面和指令配置界面，响应于通过所述配置界面接收到的输入操作，获取所述目标节点的配置信息，包括：
    响应于通过所述设备配置界面接收到的设备设置操作，获取所述物联节点对应的设备配置信息，所述设备配置信息包括设备标识；
    响应于针对指令配置入口的触发操作，呈现指令配置界面，所述指令配置界面是基于物联设备的物模型信息动态生成的；
    响应于通过所述指令配置界面接收到的指令设置操作，获取配置的设备指令。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    向物联平台发送物模型信息的获取请求，所述获取请求中携带有各个设备标识；
    接收物联平台发送的获取响应，获得所述获取响应中携带的各个设备标识对应的各个物模型信息；
    解析所述物模型信息，获取配置的设备指令的输出参数定义；
    基于各个设备标识、设备指令和输出参数定义动态生成所述物联节点的输出描述信息；
    将所述输出描述信息挂载到所述物联节点的设备类输出参数上。
  4. 根据权利要求3中所述的方法，其特征在于，所述基于所述设备标识、设备指令和输出参数定义动态生成所述物联节点的输出描述信息，包括：
    按照设备至指令至输出参数的层级结构，建立设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义的一一对应关系；
    将各个对应关系中的设备标识、所述设备标识配置的设备指令，和所述配置的设备指令的输出参数定义按照预设描述格式动态生成所述物联节点的输出描述信息。
  5. 根据权利要求2中所述的方法，其特征在于，所述响应于通过所述设备配置界面接收到的设备设置操作，获取所述物联节点对应的设备配置信息，包括：
    接收针对所述设备配置界面中设备组入口的触发操作，在所述设备配置界面呈现各个设备组；
    响应于针对所述设备组的第二选择操作，获取选中的目标设备组；
    呈现目标设备组中包括的各个设备标识；
    响应于针对设备标识的第三选择操作，获取选中的至少一个设备标识。
  6. 根据权利要求5中所述的方法，其特征在于，所述方法还包括：
    获取各个设备标识对应的各个物模型信息；
    基于所述各个物模型信息，对各个设备标识进行配置分组，得到分组结果，其中，所述分组结果包括至少一个分组标识和各个分组标识对应的设备标识；
    在分组界面呈现所述各个分组标识和所述各个分组标识对应的设备标识。
  7. 根据权利要求6中所述的方法，其特征在于，所述分组界面呈现有指令批量配置入口，所述方法还包括：
    响应于针对分组标识的第四选择操作，选中所述分组标识对应的所有设备标识；或者，
    响应于针对多个设备标识的第五选择操作，获取选择的多个设备标识；
    当接收到针对指令批量配置入口的触发操作时，确定接收到针对指令配置入口的触发操作。
  8. 根据权利要求7中所述的方法，其特征在于，所述响应于针对指令配置入口的触发操作，呈现指令配置界面，包括：
    响应于针对指令配置入口的触发操作，获取待配置设备对应的物模型信息；
    获取所述物模型信息中的服务信息；
    解析所述服务信息，确定所述待配置设备的至少一个可选指令标识和各个可选指令标识对应的参数标识；
    在所述指令配置界面呈现各个可选指令标识、所述各个可选指令标识对应的参数标识和各个参数标识的数据来源设置入口。
  9. 根据权利要求8中所述的方法，其特征在于，所述响应于通过所述指令配置界面接收到的指令设置操作，获取配置的设备指令，包括：
    响应于针对可选指令标识的第七选择操作，确定选中的目标指令标识；
    响应于针对目标指令标识对应的参数标识的第八选择操作，确定选中的目标参数标识；
    响应于针对目标参数标识的数据来源设置入口的触发操作，呈现数据来源设置界面；
    响应于通过数据来源设置界面的输入操作，确定所述目标参数标识的赋值信息；
    基于所述目标指令标识、所述目标参数标识和所述赋值信息确定配置的设备指令。
  10. 根据权利要求9所述的方法，其特征在于，所述数据来源设置界面至少显示有以下数据来源：手动输入、常量、策略使用方传入、从本策略的其他节点选择，所述响应于通过数据来源设置界面的输入操作，确定所述目标参数标识的赋值信息，包括：
    当通过所述数据来源设置界面接收到选择数据来源为从本策略的其他节点选择的第八选择操作时，呈现节点选择入口和输出参数选择入口；
    响应于针对所述节点选择入口的触发操作，呈现至少一个可选节点，接收针对可选节点的第九选择操作，确定目标来源节点；
    当所述目标来源节点为物联节点时，响应于针对输出参数选择入口的触发操作，呈现输 出参数选择界面，所述输出参数选择界面显示有所述目标来源节点的至少一个可选输出参数，所述可选输出参数包括设备类输出参数和非设备类输出参数；
    当接收到针对设备类输出参数的第十二选择操作时，呈现所述输出参数设置界面；
    响应于通过所述输出参数设置界面的输入操作，确定所述目标参数标识的赋值信息。
  11. 根据权利要求10中所述的方法，其特征在于，所述输出参数设置界面包括所述物联节点的设备标识选择入口、设备指令选择入口和输出参数选择入口，所述响应于通过所述输出参数设置界面的输入操作，确定所述目标参数标识的赋值信息，包括：
    按照设备至指令至输出参数的层级结构，分别通过针对设备标识选择入口、设备指令选择入口和输出参数选择入口的触发操作，确定目标设备标识、目标设备指令和目标输出参数标识；
    基于所述目标设备标识、目标设备指令和目标输出参数标识确定所述目标参数标识的赋值信息，其中，所述目标赋值信息为所述目标设备标识对应的物联设备执行所述目标设备指令后所述目标输出参数标识对应的输出信息。
  12. 一种业务处理装置，其特征在于，包括：
    第一确定模块，用于接收针对策略编排界面中节点标识的第一选择操作，确定选中的至少一个目标节点；
    第一呈现模块，用于在所述策略编排界面中呈现所述至少一个目标节点，所述至少一个目标节点包括物联节点；
    第二呈现模块，用于响应于针对目标节点的配置操作，呈现配置界面；
    第一获取模块，用于响应于通过所述配置界面接收到的输入操作，获取所述目标节点的配置信息，其中，当所述目标节点为物联节点时，所述配置信息至少包括基于物联平台确定的设备配置信息和指令配置信息，所述物联平台与进行策略编排的终端建立有通信连接；
    第二确定模块，用于当接收到策略编排完成操作时，基于各个目标节点的配置信息确定目标业务流程。
  13. 一种业务处理设备，其特征在于，包括：
    存储器，用于存储可执行指令；
    处理器，用于执行所述存储器中存储的可执行指令时，实现权利要求1至10任一项所述的方法。
  14. 一种业务处理系统，其特征在于，包括：业务处理设备、物联平台和物联设备，其中，所述业务处理设备与物联平台之间建立有通信连接，所述物联平台与所述物联设备之间建立有通信连接；
    所述物联平台，用于进行所述物联设备的设备分组、确定设备标签，并进行物模型管理；
    所述业务处理设备，利用所述物联平台提供的设备分组信息、设备标签信息和物模型按照权利要求1至10任一项所述的方法进行策略编排。
  15. 一种计算机可读存储介质，其特征在于，存储有可执行指令，用于被处理器执行时，实现权利要求1至10任一项所述的方法。
PCT/CN2022/087153 2021-04-27 2022-04-15 一种策略编排处理方法、装置、设备、系统及存储介质 WO2022228156A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110460057.XA CN114968032B (zh) 2021-04-27 2021-04-27 一种策略编排处理方法、装置、设备、系统及存储介质
CN202110460057.X 2021-04-27

Publications (1)

Publication Number Publication Date
WO2022228156A1 true WO2022228156A1 (zh) 2022-11-03

Family

ID=82973917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/087153 WO2022228156A1 (zh) 2021-04-27 2022-04-15 一种策略编排处理方法、装置、设备、系统及存储介质

Country Status (2)

Country Link
CN (1) CN114968032B (zh)
WO (1) WO2022228156A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115801856B (zh) * 2023-02-07 2023-05-16 深圳开鸿数字产业发展有限公司 基于原子化服务的业务处理方法及相关设备
CN116107561B (zh) * 2023-04-14 2023-06-23 湖南云畅网络科技有限公司 一种基于低代码的动作节点快速构建方法、系统和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262443A1 (en) * 2009-04-08 2010-10-14 D Albis John N Systems and methods associated with a collaborative strategy editor
WO2017190401A1 (zh) * 2016-05-05 2017-11-09 深圳前海大数点科技有限公司 一种物联网服务系统
CN109981692A (zh) * 2017-12-27 2019-07-05 中国科学院沈阳自动化研究所 一种新型工业物联网架构及其实现方法
CN112130993A (zh) * 2020-09-07 2020-12-25 国网江苏省电力有限公司信息通信分公司 基于图形化建模的电力边缘物联代理边缘计算方法及系统
CN112215430A (zh) * 2020-10-21 2021-01-12 中铁第四勘察设计院集团有限公司 一种图形化的轨道交通结构化应急预案编制系统及方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9791485B2 (en) * 2014-03-10 2017-10-17 Silver Spring Networks, Inc. Determining electric grid topology via a zero crossing technique
CN109784708A (zh) * 2019-01-07 2019-05-21 江河瑞通（北京）技术有限公司 水行业多模型耦合计算的云服务系统
US20200279136A1 (en) * 2019-03-01 2020-09-03 Royal Bank Of Canada System and method for multi-type mean field reinforcement machine learning
CN112083922A (zh) * 2020-09-21 2020-12-15 深圳市金玺智控技术有限公司 可视化编程方法、装置、设备及存储介质
CN112667334A (zh) * 2020-12-25 2021-04-16 瀚云科技有限公司 设备控制信息的配置方法、装置、电子设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262443A1 (en) * 2009-04-08 2010-10-14 D Albis John N Systems and methods associated with a collaborative strategy editor
WO2017190401A1 (zh) * 2016-05-05 2017-11-09 深圳前海大数点科技有限公司 一种物联网服务系统
CN109981692A (zh) * 2017-12-27 2019-07-05 中国科学院沈阳自动化研究所 一种新型工业物联网架构及其实现方法
CN112130993A (zh) * 2020-09-07 2020-12-25 国网江苏省电力有限公司信息通信分公司 基于图形化建模的电力边缘物联代理边缘计算方法及系统
CN112215430A (zh) * 2020-10-21 2021-01-12 中铁第四勘察设计院集团有限公司 一种图形化的轨道交通结构化应急预案编制系统及方法

Also Published As

Publication number Publication date
CN114968032B (zh) 2024-02-02
CN114968032A (zh) 2022-08-30

Similar Documents

Publication Publication Date Title
WO2022228156A1 (zh) 一种策略编排处理方法、装置、设备、系统及存储介质
KR102622652B1 (ko) 컨트롤러 기반 디바이스들의 그룹에 대한 자동 소프트웨어 개발을 위한 방법 및 장치
CN111814089B (zh) 一种页面渲染的方法、装置、渲染服务器和存储介质
US8478800B1 (en) Log streaming facilities for computing applications
US10135940B2 (en) Subscribing to event notifications using object instances
WO2023093414A1 (zh) 微应用的开发方法、装置、设备、存储介质及程序产品
CN109558202A (zh) 基于小程序的列表页面开发方法、装置、设备及存储介质
CN111026982A (zh) 智能合约处理方法、计算机设备及存储介质
CN111556158B (zh) 物联网平台的接入方法、接入装置、接入设备及存储介质
CN112015654A (zh) 用于测试的方法和装置
WO2024088207A1 (zh) 视图生成方法、装置、电子设备及存储介质
CN113934913A (zh) 数据抓取方法、装置、存储介质及电子设备
CN112988752A (zh) 资源管理方法、装置、存储介质及电子设备
CN110781180A (zh) 一种数据筛选方法和数据筛选装置
CN112332997A (zh) 终端设备的配网方法、终端设备及计算机可读存储介质
US9208058B2 (en) Providing directional debugging breakpoints
CN112558968B (zh) 一种资源树视图的生成方法、装置、设备及存储介质
CN111666100A (zh) 软件框架生成方法、装置、电子设备及存储介质
CN110730236A (zh) 基于人工智能的业务推送方法、装置及电子设备
CN113934832A (zh) 基于会话的交互处理方法、装置、设备、介质及程序产品
WO2021129812A1 (zh) 运行人工智能应用的方法、系统及设备
CN102804177B (zh) 提供自适应上下文模型框架的方法、装置
CN114327709A (zh) 一种控制页面生成方法、装置、智能设备及存储介质
CN114356387A (zh) 一种流程自动化方法、用于实现流程自动化的设备和系统
WO2020168570A1 (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: 22794627

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22794627

Country of ref document: EP

Kind code of ref document: A1