State and Sequencing in Action Triggering Group Name

State and Sequencing in Action Triggering Group Name: Source: Convida Wireless; Mladin. Catalina@convidawireless. com; Meeting Date: 2019 -05 -20

Motivation • Existing functionality for action triggering – <action> defines the trigger event/condition and action to be performed – <dependency> defines a more complex trigger by combining multiple trigger events/conditions • What’s missing – An action can only be determined as triggered or not, there are no branching or options to apply (e. g. when an event happens, under condition A, take action 1; under condition B, take action 2 …) – A trigger is monitored during the entire process, may not be necessary (some action may be state-specific) – Management for a sequence of actions with inter-dependency • Motivation – Enable branching of actions – Improve efficiency of action triggering with state and process level management

Use Case: Process Control Same event (e. g. “p. H < 3”) may trigger different actions at different states. p. H value is monitored only in first 2 stages. T<60 START Heating: Heater on; If p. H<3, add cold water. T>70 Action branching at state transition. Reaction: Heater off; Blender on; (Re)start timer; If p. H<3, add hot water. Cooling: Blender off; 1 st Cooler on; 1 hour. 2 hours Quality test failed Process should be paused/ended if hazard detected, and resumed/restarted after hazard removed. T<60 T>60 Extra Cooling: 2 nd cooler on. T<60 Filtering: Passing through filter. Quality test passed Procedures may be updated online, e. g. insert a 2 nd filtering stage while the system is currently in cooling stage. END Whether 2 nd cooler will be turned on depends on result of 1 st cooler (intricate trigger)

Gaps • State-specific actions – Define actions for each state, both unconditional and conditional • Action branching and sequencing – Define action options at state transition – Action sequencing driven by state transitions • Process level management – – Pause, end or restart the process Dynamic update states/actions/triggers in the process Insert a new state or remove an existing state In an offline or online manner

Proposed Solution • <state> resource: – State status: active/inactive • Actions associated with inactive state will not be monitored – Links to actions • Check trigger event/condition, start monitoring – Transition(s) • list of transition conditions and the corresponding destination states • Action branching enabled by transitioning into different states • <process. Management> resource • Starting/ending state • Pre-condition and exit condition • Options to enable/disable, pause, end the process