2018 IEEE International Conference on Web Services (ICWS) 2018
DOI: 10.1109/icws.2018.00052
|View full text |Cite
|
Sign up to set email alerts
|

A Service-Based Fog Execution Environment for the IoT-Aware Business Process Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 3 publications
0
3
0
Order By: Relevance
“…Also, the work of Muhić et al [29] presents the technical physical solution of the architectural model to support the business model for the Centre for digital communications with customers by considering web and mobile application for customer's interaction. On the other hand, the work of Cheng et al [30] states an execution environment based on the highly distribution that fog nodes provide and the easy integration that Application Programming Interfaces (API) facilitate. Finally, it is important to emphasize the work of Serhani et.al [31], since it proposes an ECG monitoring architecture, as the case study of the present work.…”
Section: Related Workmentioning
confidence: 99%
“…Also, the work of Muhić et al [29] presents the technical physical solution of the architectural model to support the business model for the Centre for digital communications with customers by considering web and mobile application for customer's interaction. On the other hand, the work of Cheng et al [30] states an execution environment based on the highly distribution that fog nodes provide and the easy integration that Application Programming Interfaces (API) facilitate. Finally, it is important to emphasize the work of Serhani et.al [31], since it proposes an ECG monitoring architecture, as the case study of the present work.…”
Section: Related Workmentioning
confidence: 99%
“…A centralised orchestration [72,136,137,138] has full control over all the services composed, whereas a distributed approach (also known as "decentralised orchestration" [139,140,141,142,143,144,145,146,147,148]) defines sub-workflows for a collaborative exchange of workflow control flow over the network. Although orchestration is not as popular as dataflows, there are some implementations available for this mechanism to support the definition of control-driven IoT workflows [149,150,151].…”
Section: Related Workmentioning
confidence: 99%
“…An orchestration engine is responsible for executing a workflow process by invoking service operations in a given order. Although traditional engines can be used (e.g., Camunda BPM workflow engine [86,237], Activiti [238,239] and AWS Step Functions [151]), recently we have seen the emergence of orchestration engines particularly designed for IoT systems (e.g., PROtEUS [149] and [150]). 6 Figure 15(a) illustrates a centralised orchestration for the services A, B, C and D, where the coordinator Orch1 defines a "composite service" for the sequential invocation of .…”
Section: Orchestrationmentioning
confidence: 99%