WO2021165900A1 - An automated system to perform desired orchestration activity - Google Patents

An automated system to perform desired orchestration activity Download PDF

Info

Publication number
WO2021165900A1
WO2021165900A1 PCT/IB2021/051419 IB2021051419W WO2021165900A1 WO 2021165900 A1 WO2021165900 A1 WO 2021165900A1 IB 2021051419 W IB2021051419 W IB 2021051419W WO 2021165900 A1 WO2021165900 A1 WO 2021165900A1
Authority
WO
WIPO (PCT)
Prior art keywords
orchestration
user
devices
specific
definition
Prior art date
Application number
PCT/IB2021/051419
Other languages
French (fr)
Inventor
Mrinmoy Jyoti DAS
Shipra DAS
Original Assignee
Das Mrinmoy Jyoti
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 Das Mrinmoy Jyoti filed Critical Das Mrinmoy Jyoti
Publication of WO2021165900A1 publication Critical patent/WO2021165900A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803Home automation networks
    • H04L12/2816Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/2821Avoiding conflicts related to the use of home appliances
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B15/00Systems controlled by a computer
    • G05B15/02Systems controlled by a computer electric

Definitions

  • TECHNICAL FIELD The present disclosure relates generally to automation solutions; and more specifically, to systems and methods for automation of the daily needs of industries, agriculture, as well as other consumers, for example.
  • automation solutions have become a reality.
  • automation provides customised solutions to current practices, such as industrial, social, domestic project, for example, daily monitoring of a microenvironment like a greenhouse.
  • edge orchestration devices comprising sensors and actuators.
  • a water pump automation system for a definitive combination of overhead tank, reservoir, input supply, motor, and so on.
  • the water pump automation system is specific to a predefined combination of aforesaid resources and may not be reusable to an extended scenario like flood control although the same sensors which senses the water level of tank can measure the water level of crick, drain river or low land, and the actuators can initiate action based on a water flow sensor. Therefore, due to inflexibility in solutions, the extended utilisation of the automation solution is limited, hence, the cost reduction in future implementations are minimal.
  • IOT platforms along with conventional orchestrating devices employ any of a flow chart, visual programming-based orchestration facility or microprocessor level programming to solve specific problems.
  • microprocessor-level programming in a project circumvents the extensive manual interventions in such projects.
  • a majority section of the normal users for example a person having good understanding of his day-to-day problems but having minimal or no computational development knowledge, are unable to bring benefits of such automation solutions to solve their known issues and help to bring more efficiency in their day-to-day life.
  • the microprocessor-level programming is complex and shifts the focus from solving the actual problem to the code development issues.
  • the microprocessor-level programming is cost-intensive due to the need of costly and limited number of microprogramming developers. Such limited number of microprogramming developers further limits the expansion of automation solution to support the global need.
  • the present disclosure seeks to provide a system for automation.
  • the present disclosure also seeks to provide a method of automation.
  • the present disclosure seeks to provide a solution to the existing problem of microprocessor level programming for conventional sensor and actuator-based edge orchestration devices, that are both complex and costly.
  • An aim of the present disclosure is to provide a solution that overcomes at least partially the problems encountered in prior art, and provide an independent, efficient, flexible and cost-effective automation solution that is a software and intelligent hardware-based solution.
  • an embodiment of the present disclosure provides a system for automation, the system comprising:
  • a device controller configured to operate one or more devices to perform a desired orchestration activity, wherein the one or more devices are physically connected to the device controller;
  • a server arrangement having an application module comprising:
  • an orchestration application configured to:
  • a distributer application configured to:
  • an embodiment of the present disclosure provides a method of automation, the method comprising: receiving a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; sharing the execution information and status of the performed orchestration activity with a third-party.
  • Embodiments of the present disclosure substantially eliminate or at least partially address the aforementioned problems in the prior art, and enable users having low computation development and knowledge to define their automation need for their day-to-day activities for more efficiency and ease, at affordable cost. Additional aspects, advantages, features and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative embodiments construed in conjunction with the appended claims that follow.
  • FIG. 1 is a schematic illustration of a system for automation, in accordance with an embodiment of the present disclosure
  • FIG. 2 is a flow chart of steps of a method of automation, in accordance with an embodiment of the present disclosure.
  • an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent.
  • a non-underlined number relates to an item identified by a line linking the non-underlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing.
  • an embodiment of the present disclosure provides a system for automation, system comprising:
  • a device controller configured to operate one or more devices, physically connected to the device controller, to perform a desired orchestration activity
  • server arrangement communicably coupled to the device controller and a user device associated with a user, the server arrangement comprising:
  • an orchestration application configured to:
  • an embodiment of the present disclosure provides a method of automation, the method comprising: receiving, from a user device, a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; sharing the execution information and status of the performed orchestration activity with a third-party.
  • the present disclosure provides the aforesaid system for automation.
  • the system is a cloud- and intelligent device-based automation solution for defining automation need.
  • the system replaces the microprocessor-level programming with user input form based programming solution imparted by an orchestration application.
  • the user input form based programming is an alternate solution to the complexity and cost associated with the microprocessor-level programming.
  • the orchestration application converts formatted natural language user input (user-specific logic) into a server-specific format and to a particular device- specific format (referred to as "orchestration definition” hereafter), separately.
  • the orchestration definition is stored at various levels (namely, state definitions), i.e. at the server arrangement initially and loaded on to a specific electronic device for performing a desired orchestration activity.
  • state definitions i.e. at the server arrangement initially and loaded on to a specific electronic device for performing a desired orchestration activity.
  • the system enables saving onto the microprocessors of the devices only a required part of the orchestration definition needed to perform the desired orchestration activity at real time.
  • such distributed state definition model prevents the microprocessor size limitation to become an overall system limitation.
  • only authorized users can select a particular electronic device from a list of virtual devices registered on the system and load the orchestration definition in the selected electronic device.
  • the authorized access of the devices enables protecting the electronic device from hacking.
  • system refers to an independent automation platform comprising a server arrangement and multiple devices configured to perform the desired orchestration activity.
  • the system employs microprocessors, firmware, applications, tools, servers and formatted data structures to enable users to customize and implement the desired orchestration activity according to their needs.
  • the system is an ecosystem comprising one or more such systems and a group of users managing one or more systems.
  • the term "user” as used herein refers to any entity (such as a person i.e. a human being or a third-party system) that is associated with or operates the system or provides user-specific logic to the system. Typically, the user has a good understanding of his day-to-day problems but has minimal or no computational development knowledge to automate their day-to-day life.
  • the user is any of: an end user (human or system), a local entrepreneur, an device implementer or a technical user.
  • the user is an end user such as any home or office owner, a farmer, a manufacturer, and the like, requiring automating his day-to-day activity, involving automated operation of appliances or processes and remaining informed regarding the state of the day-to-day activity or any system of their use.
  • the user is a local entrepreneur working locally to identify local needs, accordingly find and promote the fitment of the existing solutions of the entire ecosystem for solving local issues and/or to initiate new projects to solve the local issues as well as remote issues.
  • the user is a technical user managing the entire system.
  • the user is a device implementer or a technical user of the system.
  • the device implementer may provide the orchestration definition, configure and implement the same on the corresponding hardware.
  • the device implementer may be associated with the local entrepreneurs and trained by technical users to solve a local or remote issue.
  • the user is a third-party system or a virtual program, such as, an autonomous program or a hot.
  • the term "device controller” as used herein refers to a unique and independent electronic device implemented as a self-operating sensing and switching machine.
  • the device controller employs a microprocessor driven by an operating application.
  • the device controller is configured to communicate with one or more devices for receiving commands as well as sending commands for an action thereof.
  • the device controller comprises multiple plug-in ports for receiving one or more devices.
  • the plug-in ports are complementary to the connecting parts of the one or more devices to enable proper fitting thereof.
  • the plug-in ports are all of the same shape and size or different.
  • the device controller typically serves as a common interface to which one or more devices are connected.
  • the one or more devices are selected from a group of: a central management system, a subsystem, an edge orchestration device.
  • the central management system, the subsystem and the edge orchestration device form different nodes or elements of a distributed network and a hierarchy network.
  • the central management system, the subsystem and the edge orchestration device communicate with each other and transmit complex information to accomplish a single or similar activity, referred here as the desired orchestration activity in the hierarchy network.
  • the central management system manages the distributed network, optionally comprising one or more remote servers.
  • the subsystem is one or more intermediary systems in the distributed network.
  • the edge orchestration devices are the end-points of the distributed network.
  • the desired orchestration activity is implemented in the one or more devises as per the hierarchy network.
  • the edge orchestration devices provide a real-time control and monitoring, of various industrial applications for example, based on an access to information flowing from higher or neighboring nodes or elements of the distributed network, to perform the desired orchestration activity.
  • the one or more devices are any of internet of things devices, physical equipment, machines.
  • the one or more devices are communicably coupled with each other via, for example, Wi-Fi or GSM connection, to enable coordinated effort by the one or more devices.
  • the edge orchestration device is at least one of: a sensor, an appliance, and a communication device. It will be appreciated that the plurality of edge orchestration device may be operated to perform a desired orchestration activity.
  • the sensors are operable to sense and record local parameters in real time and generate corresponding sensor signals.
  • the different types of sensors for example thermal sensors, motion sensors, gas sensors, proximity sensors, humidity sensors and level sensors, simultaneously sense and record different parameters, for example heat or cold, movement, gas and chemicals, objects, humidity and level or height of liquid or gases, respectively.
  • the sensor data is provided as commends or signals, corresponding to the measured entity, to at least one of: actuators, switches and regulators associated with the plug-in ports of one or more appliances for operating the said appliance.
  • the sensor data may be used to operate other remote or neighboring devices that are a part of the distributed network but may not be physically connected to the device controller.
  • the device controller employs microprocessors driven by a unique application to interpret the sensor data. Thereby, eliminating the need for additional microprocessors between the device controller and the sensors.
  • the communication device communicates using at least one of: a Bluetooth®, a Wi-Fi or a near field communication (NFC) device.
  • the device controller comprises communication ports configured to receive communication devices to connect the device controller and/or the one or more devices with other neighboring devices enabled with a corresponding communication means.
  • the connected devices communicate with each other and perform actions commanded by one another.
  • server arrangement refers to an arrangement of physical or virtual computational entities such as a processor, and a memory unit or a database structure that includes programmable and/or non-programmable components configured to store, process and/or share information.
  • the server may be a single hardware server or a plurality of hardware servers operating in a parallel or distributed architecture.
  • the server arrangement comprises a database operable to store information related to the user-specific logic, server-specific orchestration definition, orchestration definition, execution logic, local parameters sensed and recorded by the sensors, and commands from one or more devices generated in the process of performing the desired orchestration activity.
  • the server arrangement is communicatively coupled to the device controller and the user device associated with the user via a communication network.
  • the communication network includes but not limited to, a cellular network, short range radio (for example, such as Bluetooth®), Internet, a wireless local area network, and an Infrared Local Area Network, or any combination thereof.
  • the user device provides a user interface.
  • the user-specific logic is received via the user interface.
  • the user-specific logic is received as at least one of: a textual format, an audio format, or any combination thereof.
  • the user interface enables connecting the user with the one or more devices via a virtual platform.
  • the user interface displays a virtual platform, and wherein the virtual platform is configured to register thereon at least one of: the device controller, the one or more devices and an authorized user.
  • the virtual platform allows access to the system environment and the status of the one or more devices plug-in to the device controller.
  • the user interface is driven by a mobile or web application.
  • the mobile or web application logs in to display of the user device to access the user interface and display the virtual platform.
  • the mobile or web application enables sending commands to the device controller to control, configure or orchestrate one or more devices.
  • the registered device controller and the one or more devices have corresponding virtual devices therefor.
  • the authorized user may be authorized to access the components of the system at multiple levels in the distributed network.
  • the device controller is associated with a communication identity. Specifically, the communication identity enables access to the device controller by the local users or technical users to ensure proper working of the device controller locally as well as in neighboring and remote systems.
  • the registered users are authorized to access the registered devices.
  • the device controller and the one or more devices are accessed via the user device associated with the authorized user of the system.
  • the users are required to register themselves by providing information indicative of identity of the user.
  • the preliminary authorization of the user may require the user to enter an authorization code.
  • the authorization code may be a personal identification number (PIN), a fingerprint for biometric verification, or a verification using facial recognition of the user.
  • the authorized users may claim the registered device using a unique device identity in the virtual platform.
  • the registered device controller and the one or more devices are assigned a unique device identity and said device identity is shared with an authorized user.
  • the authorized users claim a given registered electronic device using the unique device identity associated therewith via the virtual platform. It will be appreciated that only the authorized users can claim a registered electronic device by entering the unique device identity upon confirming their authorization code.
  • the authorized user can operate, take actions on or share data from the devices claimed successfully thereby.
  • the device controller is fully compatible with the system and therefore the devices require no custom coding to follow the registration and authentication process.
  • a unique device identity corresponding to each registered device prevents unauthorized access, such as for example hacking, thereof.
  • the registered device may be accessed by one or more users at different levels of operation.
  • a local communication identity is shared with a local user for having access to the system environment for configuring the device controller or one or more devices according to the local user's owned network.
  • the level of operation and actions thereon is limited in view of the security of the entire system.
  • the local user may select, based on the automation need, the one or more devices from a list of devices supported by the system, and specific one or more devices to be allocated to one or more plug-in ports of the device controller.
  • the system subsequently enables implementing the orchestration activity of the selected sensors and one or more devices, such as actuators, based on the orchestration definition corresponding thereto.
  • the server arrangement hosts a multitude of server applications and tools.
  • the server arrangement is configured to orchestrate the device controller and associated one or more devices via the multitude of server applications.
  • the said server applications are operable to process the user-specific logic into a machine-specific format, i.e. the server-specific orchestration definition and the device-specified definition or the orchestration definition.
  • the server applications are operable to convert the user-specific logic into the orchestration definition in a two-step compilation process.
  • the orchestration application is configured to receive, from the user device, the user specific logic.
  • the user-specific logic is in a structured natural language or as input to dynamic web form.
  • the user defines an automation need in natural language, for example English sentences, on a standard template or form.
  • the template or form provides information associated with different automation options associated with the one or more devices in a guided query manner.
  • the guided query manner allows a user to select from options against a guided query and/or entering some guided values, for example.
  • the user-specific logic in structured natural language or as input to dynamic web form eliminates the need for complex programming, block diagrams, flow charts, and the like to create specific orchestration definition.
  • the user-specific logic is saved in the database to log a specific user response for a specific situation and reads the saved data back next time such situation occurs. It will be appreciated that such logs may be used to train a system for future automation.
  • the orchestration module compiles the received (and saved) user-specific logic into the server-specific orchestration definition.
  • the server-specific orchestration definition is a machine -readable structured format of the user-specific logic that can be read and processed by the server arrangement for operating the device controller and the associated one or more devices to perform the desired orchestration activity.
  • the English sentences of the user-specific logic are transformed into a format selected from any one of: microformat, RDF, HTML, CSV, XML, JSON, and so on, to provide the necessary context required to support the application for which they are created.
  • the compiled server-specific orchestration definition is also persisted in the database for further processing thereof or training the system for example.
  • the server arrangement communicates with various one or more devices associated with the device controller and based on the received communication use a corresponding server-specific orchestration definition to prepare the one or more devices to perform the desired orchestration activity.
  • the orchestration application is configured to persist the server-specific orchestration definition in the database with a unique identification and a corresponding correlation ID is shared with an authorized user.
  • the unique identification associated with the server-specific orchestration definition enables securely storing thereof with the server arrangement until it is required by the device controller and the one or more devices for orchestrating the desired orchestration activity.
  • the distributer application is configured to compile the server- specific orchestration definition into the orchestration definition for operating the one or more devices.
  • the orchestration definition is a unique device specific format readable and understandable by a specific device, such as the device controller and/or the corresponding one or more devices.
  • the orchestration definition is different from the server-specific definition in that the specific devices are associated with different operating systems and require a specific format for performing the desired orchestration activity.
  • an orchestration definition for an infrared sensor is different from an orchestration definition for a hot.
  • an orchestration definition for an iOS-based device is different from an Android-based device.
  • the distributer application is configured to distribute the orchestration definition along with the execution logic to the one or more devices for performing the desired orchestration activity.
  • the orchestration definition and the execution logic is specific for a particular device, selected from the registered one or more devices, that is required to perform the desired orchestration activity.
  • the orchestration definition and the execution logic is implemented in the particular device(s) of the hierarchical network. Therefore, the orchestration definition along with the execution logic specific for a device is loaded thereon for performing the desired orchestration activity.
  • execution logic refers to a set of instructions for carrying out a process, by an executing machine such as one or more devices, based on a command from the user.
  • the execution logic is descriptive of a particular action carried out by the one or more devices in order to perform the desired orchestration activity.
  • the orchestration definition and the execution logic corresponding to a given device for performing the desired orchestration activity is distributed to or loaded on to the given device as and when required to avoid using up the microprocessor memory of the given device.
  • the aforementioned two-step compilation process enables a format that is small enough as the memory provision in the microprocessors, but represent all the orchestration definitions required to perform the desired orchestration activity. Therefore, the limitation of the microprocessor memory does not turn into a limitation of the system.
  • the device controller is configured to operate the one or more devices to perform the desired orchestration activity based on communication received from at least one of: the sensors, the server-specific orchestration definition, the orchestration definition, and other connected devices.
  • the orchestration activity of the corresponding one or more devices such as an appliance, is pre- defined by the orchestration definition. Therefore, the device controller is configured to operate the actuators and corresponding appliances to perform the orchestration activity based on the received sensor data and/or composite situations (i.e. from local or remote neighboring devices).
  • the orchestration definition is loaded on to the one or more devices and/or device controller in real time based on the received sensor data and/or composite situations.
  • the orchestration definition may be determined from a previous orchestration activity, such as for example, a frequently implemented orchestration definition, such as for example from the previous day, week or month.
  • the communicating devices i.e. the one or more devices, the server arrangement and the neighboring devices, are all communicably coupled.
  • the device controller is configured to command the remote appliances to perform a corresponding activity to enable performing the desired orchestration activity.
  • the orchestration definition is loaded to the one or more device by an authorized user. More specifically, the authorized user connects to the virtual platform and selects a particular device in the virtual platform. Subsequently, a request for loading the orchestration definition to the selected device is generated by using the correlation identity associated with the unique identity assigned to the server-specific orchestration definition and the user's authorization code. Consequently, the distributer application compiles the server-specific orchestration definition into the orchestration definition and loads the compiled orchestration definition to the selected device.
  • storing the server-specific orchestration definition in the database for a major part of time enables saving only a part of the orchestration definition in the microprocessor memory of the particular one or more devices that is required for orchestrating the desired orchestration activity in real-time.
  • the authorized users operate, take actions and share data from the claimed one or more devices.
  • the system is a stand-alone system and can operate independently.
  • the orchestration definition is not required to be installed in an external device, such as a mobile or laptop device.
  • the orchestration definition can be run on the system itself, such as on the device controller and/or one or more devices.
  • the system may be accessed at various levels, such as end-user, local user, technical user and device implementer, to ensure proper working thereof.
  • the system components are secured for authorized use only.
  • the system comprises creating an automation project on a virtual platform by a user, registered with the system.
  • the user is required to fill out an inception document to define an automation need in detail.
  • the user is required to select one or more devices from the virtual platform and map the sensors as well as actuators thereof.
  • a mapping of the sensors with the corresponding actuators is also performed to ensure proper coordination therebetween.
  • the system is configured to identify and reset events based on any dependent event.
  • the events may be local parameters such as sensor data, commands from connected devices, state data of the devices, and so on.
  • the system employs the said events to create an orchestration definition.
  • the orchestration definition is stored in a part of the system, specifically the server, until the orchestration definition is required to be loaded to a particular electronic device for operation thereof. Subsequently, the orchestration activity is performed by the particular one or more devices based on the orchestration definition.
  • the present disclosure also relates to the method as described above.
  • Various embodiments and variants disclosed above apply mutatis mutandis to the method.
  • the method of automation comprising: receiving, from a user device, a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; - sharing the execution information and status of the performed orchestration activity with a third-party.
  • the execution information and status of the performed orchestration activity is shared with a third-party to enable identification of dependent events and assessing change in the overall execution if one or more of the dependent events is changed.
  • the user-specific logic is in a structured natural language or as input to dynamic web form.
  • the authorized users operate, take actions and share data from the claimed one or more devices.
  • the system 100 for automation comprises a device controller 102 and a server arrangement 104.
  • the device controller 102 is configured to operate one or more devices, such as devices 106, 108 and 110, to perform a desired orchestration activity.
  • the one or more devices, such as the devices 106, 108 and 110, are physically connected to the device controller 102.
  • the server arrangement 104 is communicably coupled to the device controller 102 and a user device 112 associated with a user (not shown).
  • the server arrangement 104 comprises an orchestration application and a distributer application.
  • the orchestration application is configured to receive, from the user device 112, a user-specific logic, persist the user-specific logic in a database 114, compile the user-specific logic into a server- specific orchestration definition, and persist the server-specific orchestration definition in the database 114.
  • the distributer application is configured to compile the server-specific orchestration definition into an orchestration definition for operating the one or more devices, such as the devices 106, 108 and 110, and distribute the orchestration definition along with an execution logic to the one or more devices, such as the devices 106, 108 and 110, for performing the desired orchestration activity.
  • a user-specific logic is received from a user device.
  • the user-specific logic is persisted in a database.
  • the user-specific logic is compiled into a server-specific orchestration definition.
  • the server- specific orchestration definition is persisted in the database.
  • the server- specific orchestration definition is compiled into an orchestration definition for operating the one or more devices.
  • the orchestration definition along with an execution logic is distributed to the one or more devices for performing a desired orchestration activity.
  • the execution information and status of the performed orchestration activity is shared with a third-party.
  • steps 202, 204, 206, 208, 210, 212 and 214 are only illustrative and other alternatives can also be provided where one or more steps are added, one or more steps are removed, or one or more steps are provided in a different sequence without departing from the scope of the claims herein.

Abstract

Disclosed is a system for automation. The system comprises a device controller and a server arrangement communicably coupled to the device controller and a user device associated with a user. The device controller is configured to operate one or more devices, physically connected to the device controller, to perform desired orchestration activity. The server arrangement has an application module comprising an orchestration application configured to receive, from user device, a user-specific logic, persist user-specific logic in a database, compile user-specific logic into a server-specific orchestration definition, and persist server-specific orchestration definition in database. The application module also comprises a distributer application configured to: compile server-specific orchestration definition into an orchestration definition for operating one or more devices, and distribute orchestration definition along with an execution logic to one or more devices for performing desired orchestration activity. Disclosed also is a method of automation using the aforementioned system.

Description

AN AUTOMATED SYSTEM TO PERFORM DESIRED ORCHESTRATION ACTIVITY
TECHNICAL FIELD The present disclosure relates generally to automation solutions; and more specifically, to systems and methods for automation of the daily needs of industries, agriculture, as well as other consumers, for example.
BACKGROUND
With the progress of internet of things, automation solutions have become a reality. Typically, automation provides customised solutions to current practices, such as industrial, social, domestic project, for example, daily monitoring of a microenvironment like a greenhouse.
Advances in the field of automation has provided several specific edge orchestration devices comprising sensors and actuators. For example, a water pump automation system for a definitive combination of overhead tank, reservoir, input supply, motor, and so on. However, such devices provide solutions to specific problems only, and very rigidly. In the above example, for instance, the water pump automation system is specific to a predefined combination of aforesaid resources and may not be reusable to an extended scenario like flood control although the same sensors which senses the water level of tank can measure the water level of crick, drain river or low land, and the actuators can initiate action based on a water flow sensor. Therefore, due to inflexibility in solutions, the extended utilisation of the automation solution is limited, hence, the cost reduction in future implementations are minimal. Additionally, IOT platforms along with conventional orchestrating devices employ any of a flow chart, visual programming-based orchestration facility or microprocessor level programming to solve specific problems. Conventionally, such microprocessor-level programming in a project circumvents the extensive manual interventions in such projects. However, a majority section of the normal users, for example a person having good understanding of his day-to-day problems but having minimal or no computational development knowledge, are unable to bring benefits of such automation solutions to solve their known issues and help to bring more efficiency in their day-to-day life. Moreover, the microprocessor-level programming is complex and shifts the focus from solving the actual problem to the code development issues. Furthermore, the microprocessor-level programming is cost-intensive due to the need of costly and limited number of microprogramming developers. Such limited number of microprogramming developers further limits the expansion of automation solution to support the global need.
Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks associated with conventional automation solutions at affordable costs.
SUMMARY
The present disclosure seeks to provide a system for automation. The present disclosure also seeks to provide a method of automation. The present disclosure seeks to provide a solution to the existing problem of microprocessor level programming for conventional sensor and actuator-based edge orchestration devices, that are both complex and costly. An aim of the present disclosure is to provide a solution that overcomes at least partially the problems encountered in prior art, and provide an independent, efficient, flexible and cost-effective automation solution that is a software and intelligent hardware-based solution.
In one aspect, an embodiment of the present disclosure provides a system for automation, the system comprising:
- a device controller configured to operate one or more devices to perform a desired orchestration activity, wherein the one or more devices are physically connected to the device controller; and
- a server arrangement having an application module comprising:
- an orchestration application configured to:
- receive a user-specific logic, - persist the user-specific logic in a database,
- compile the user-specific logic into a server-specific orchestration definition, and
- persist the server-specific orchestration definition in the database; and a distributer application configured to:
- compile the server-specific orchestration definition into an orchestration definition for operating the one or more devices, and
- distribute the orchestration definition along with an execution logic to the one or more devices for performing the desired orchestration activity.
In another aspect, an embodiment of the present disclosure provides a method of automation, the method comprising: receiving a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; sharing the execution information and status of the performed orchestration activity with a third-party.
Embodiments of the present disclosure substantially eliminate or at least partially address the aforementioned problems in the prior art, and enable users having low computation development and knowledge to define their automation need for their day-to-day activities for more efficiency and ease, at affordable cost. Additional aspects, advantages, features and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative embodiments construed in conjunction with the appended claims that follow.
It will be appreciated that features of the present disclosure are susceptible to being combined in various combinations without departing from the scope of the present disclosure as defined by the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the present disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those skilled in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.
Embodiments of the present disclosure will now be described, by way of example only, with reference to the following diagrams wherein:
FIG. 1 is a schematic illustration of a system for automation, in accordance with an embodiment of the present disclosure;
FIG. 2 is a flow chart of steps of a method of automation, in accordance with an embodiment of the present disclosure.
In the accompanying drawings, an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent. A non-underlined number relates to an item identified by a line linking the non-underlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing. DETAILED DESCRIPTION OF EMBODIMENTS
The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognize that other embodiments for carrying out or practising the present disclosure are also possible.
In one aspect, an embodiment of the present disclosure provides a system for automation, system comprising:
- a device controller configured to operate one or more devices, physically connected to the device controller, to perform a desired orchestration activity; and
- a server arrangement communicably coupled to the device controller and a user device associated with a user, the server arrangement comprising:
- an orchestration application configured to:
- receive, from the user device, a user-specific logic,
- persist the user-specific logic in a database,
- compile the user-specific logic into a server-specific orchestration definition, and
- persist the server-specific orchestration definition in the database; and
- a distributer application configured to:
- compile the server-specific orchestration definition into an orchestration definition for operating the one or more devices, and
- distribute the orchestration definition along with an execution logic to the one or more devices for performing the desired orchestration activity.
In another aspect, an embodiment of the present disclosure provides a method of automation, the method comprising: receiving, from a user device, a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; sharing the execution information and status of the performed orchestration activity with a third-party.
The present disclosure provides the aforesaid system for automation. The system is a cloud- and intelligent device-based automation solution for defining automation need. The system replaces the microprocessor-level programming with user input form based programming solution imparted by an orchestration application. Beneficially, the user input form based programming is an alternate solution to the complexity and cost associated with the microprocessor-level programming. Moreover, the orchestration application converts formatted natural language user input (user-specific logic) into a server-specific format and to a particular device- specific format (referred to as "orchestration definition” hereafter), separately. Beneficially, receiving user input in structured natural language or as input to dynamic web form enables users having low computational development knowledge to define their automation needs using sensors, regulators, and various appliances to implement their day-to-day activity more efficiently and easily at affordable costs without requiring a microprocessor programmer whose services are very costly. Moreover, the orchestration definition is stored at various levels (namely, state definitions), i.e. at the server arrangement initially and loaded on to a specific electronic device for performing a desired orchestration activity. In this way, the system enables saving onto the microprocessors of the devices only a required part of the orchestration definition needed to perform the desired orchestration activity at real time. Additionally, beneficially, such distributed state definition model prevents the microprocessor size limitation to become an overall system limitation. Moreover, only authorized users can select a particular electronic device from a list of virtual devices registered on the system and load the orchestration definition in the selected electronic device. Beneficially, the authorized access of the devices enables protecting the electronic device from hacking.
Throughout the present disclosure, the term "system " as used herein refers to an independent automation platform comprising a server arrangement and multiple devices configured to perform the desired orchestration activity. The system employs microprocessors, firmware, applications, tools, servers and formatted data structures to enable users to customize and implement the desired orchestration activity according to their needs. Optionally, at an implementation level, the system is an ecosystem comprising one or more such systems and a group of users managing one or more systems.
The term "user” as used herein refers to any entity (such as a person i.e. a human being or a third-party system) that is associated with or operates the system or provides user-specific logic to the system. Typically, the user has a good understanding of his day-to-day problems but has minimal or no computational development knowledge to automate their day-to-day life. Optionally, the user is any of: an end user (human or system), a local entrepreneur, an device implementer or a technical user. In an example, the user is an end user such as any home or office owner, a farmer, a manufacturer, and the like, requiring automating his day-to-day activity, involving automated operation of appliances or processes and remaining informed regarding the state of the day-to-day activity or any system of their use. In another example, the user is a local entrepreneur working locally to identify local needs, accordingly find and promote the fitment of the existing solutions of the entire ecosystem for solving local issues and/or to initiate new projects to solve the local issues as well as remote issues. In yet another example, the user is a technical user managing the entire system. In still another example, the user is a device implementer or a technical user of the system. The device implementer may provide the orchestration definition, configure and implement the same on the corresponding hardware. Optionally, the device implementer may be associated with the local entrepreneurs and trained by technical users to solve a local or remote issue. Optionally, the user is a third-party system or a virtual program, such as, an autonomous program or a hot.
The term "device controller” as used herein refers to a unique and independent electronic device implemented as a self-operating sensing and switching machine. The device controller employs a microprocessor driven by an operating application. Optionally, the device controller is configured to communicate with one or more devices for receiving commands as well as sending commands for an action thereof. Optionally, the device controller comprises multiple plug-in ports for receiving one or more devices. The plug-in ports are complementary to the connecting parts of the one or more devices to enable proper fitting thereof. Optionally, the plug-in ports are all of the same shape and size or different. The device controller typically serves as a common interface to which one or more devices are connected.
Optionally, the one or more devices are selected from a group of: a central management system, a subsystem, an edge orchestration device. It will be appreciated that the central management system, the subsystem and the edge orchestration device form different nodes or elements of a distributed network and a hierarchy network. The central management system, the subsystem and the edge orchestration device communicate with each other and transmit complex information to accomplish a single or similar activity, referred here as the desired orchestration activity in the hierarchy network. Optionally, the central management system manages the distributed network, optionally comprising one or more remote servers. Optionally, the subsystem is one or more intermediary systems in the distributed network. Optionally, the edge orchestration devices are the end-points of the distributed network. Beneficially, the desired orchestration activity is implemented in the one or more devises as per the hierarchy network. Typically, the edge orchestration devices provide a real-time control and monitoring, of various industrial applications for example, based on an access to information flowing from higher or neighboring nodes or elements of the distributed network, to perform the desired orchestration activity. Optionally, the one or more devices are any of internet of things devices, physical equipment, machines. Optionally, the one or more devices are communicably coupled with each other via, for example, Wi-Fi or GSM connection, to enable coordinated effort by the one or more devices. Optionally, the edge orchestration device is at least one of: a sensor, an appliance, and a communication device. It will be appreciated that the plurality of edge orchestration device may be operated to perform a desired orchestration activity. Optionally, the sensors are operable to sense and record local parameters in real time and generate corresponding sensor signals. More optionally, the different types of sensors, for example thermal sensors, motion sensors, gas sensors, proximity sensors, humidity sensors and level sensors, simultaneously sense and record different parameters, for example heat or cold, movement, gas and chemicals, objects, humidity and level or height of liquid or gases, respectively. The sensor data is provided as commends or signals, corresponding to the measured entity, to at least one of: actuators, switches and regulators associated with the plug-in ports of one or more appliances for operating the said appliance. Optionally, the sensor data may be used to operate other remote or neighboring devices that are a part of the distributed network but may not be physically connected to the device controller. Moreover, the device controller employs microprocessors driven by a unique application to interpret the sensor data. Thereby, eliminating the need for additional microprocessors between the device controller and the sensors.
Optionally, the communication device communicates using at least one of: a Bluetooth®, a Wi-Fi or a near field communication (NFC) device. Optionally, the device controller comprises communication ports configured to receive communication devices to connect the device controller and/or the one or more devices with other neighboring devices enabled with a corresponding communication means. Optionally, the connected devices communicate with each other and perform actions commanded by one another. Throughout the present disclosure, the term "server arrangement” as used herein refers to an arrangement of physical or virtual computational entities such as a processor, and a memory unit or a database structure that includes programmable and/or non-programmable components configured to store, process and/or share information. It will be appreciated that the server may be a single hardware server or a plurality of hardware servers operating in a parallel or distributed architecture. Moreover, the server arrangement comprises a database operable to store information related to the user-specific logic, server-specific orchestration definition, orchestration definition, execution logic, local parameters sensed and recorded by the sensors, and commands from one or more devices generated in the process of performing the desired orchestration activity.
Furthermore, the server arrangement is communicatively coupled to the device controller and the user device associated with the user via a communication network. In an example, the communication network includes but not limited to, a cellular network, short range radio (for example, such as Bluetooth®), Internet, a wireless local area network, and an Infrared Local Area Network, or any combination thereof. Optionally, the user device provides a user interface. The user- specific logic is received via the user interface. The user-specific logic is received as at least one of: a textual format, an audio format, or any combination thereof. Moreover, the user interface enables connecting the user with the one or more devices via a virtual platform.
Optionally, the user interface displays a virtual platform, and wherein the virtual platform is configured to register thereon at least one of: the device controller, the one or more devices and an authorized user. Specifically, the virtual platform allows access to the system environment and the status of the one or more devices plug-in to the device controller. Optionally, the user interface is driven by a mobile or web application. Specifically, the mobile or web application logs in to display of the user device to access the user interface and display the virtual platform. The mobile or web application enables sending commands to the device controller to control, configure or orchestrate one or more devices. Moreover, the registered device controller and the one or more devices have corresponding virtual devices therefor. It will be appreciated that the authorized user may be authorized to access the components of the system at multiple levels in the distributed network. Optionally, the device controller is associated with a communication identity. Specifically, the communication identity enables access to the device controller by the local users or technical users to ensure proper working of the device controller locally as well as in neighboring and remote systems.
Furthermore, the registered users are authorized to access the registered devices. In this regard, the device controller and the one or more devices are accessed via the user device associated with the authorized user of the system. Optionally, the users are required to register themselves by providing information indicative of identity of the user. In particular, the preliminary authorization of the user may require the user to enter an authorization code. Optionally, the authorization code may be a personal identification number (PIN), a fingerprint for biometric verification, or a verification using facial recognition of the user.
Optionally, the authorized users may claim the registered device using a unique device identity in the virtual platform. Specifically, the registered device controller and the one or more devices are assigned a unique device identity and said device identity is shared with an authorized user. Notably, the authorized users claim a given registered electronic device using the unique device identity associated therewith via the virtual platform. It will be appreciated that only the authorized users can claim a registered electronic device by entering the unique device identity upon confirming their authorization code. Moreover, the authorized user can operate, take actions on or share data from the devices claimed successfully thereby. It will be appreciated that the device controller is fully compatible with the system and therefore the devices require no custom coding to follow the registration and authentication process. Moreover, a unique device identity corresponding to each registered device prevents unauthorized access, such as for example hacking, thereof. Furthermore, the registered device may be accessed by one or more users at different levels of operation. In this regard, a local communication identity is shared with a local user for having access to the system environment for configuring the device controller or one or more devices according to the local user's owned network. Moreover, the level of operation and actions thereon is limited in view of the security of the entire system. In this regard, the local user may select, based on the automation need, the one or more devices from a list of devices supported by the system, and specific one or more devices to be allocated to one or more plug-in ports of the device controller. The system subsequently enables implementing the orchestration activity of the selected sensors and one or more devices, such as actuators, based on the orchestration definition corresponding thereto.
More specifically, the server arrangement hosts a multitude of server applications and tools. Specifically, the server arrangement is configured to orchestrate the device controller and associated one or more devices via the multitude of server applications. The said server applications are operable to process the user-specific logic into a machine-specific format, i.e. the server-specific orchestration definition and the device-specified definition or the orchestration definition. In this regard, the server applications are operable to convert the user-specific logic into the orchestration definition in a two-step compilation process.
In a first step, the orchestration application is configured to receive, from the user device, the user specific logic. Optionally, the user-specific logic is in a structured natural language or as input to dynamic web form. In this regard, the user defines an automation need in natural language, for example English sentences, on a standard template or form. The template or form provides information associated with different automation options associated with the one or more devices in a guided query manner. The guided query manner allows a user to select from options against a guided query and/or entering some guided values, for example. Beneficially, the user-specific logic in structured natural language or as input to dynamic web form eliminates the need for complex programming, block diagrams, flow charts, and the like to create specific orchestration definition. Moreover, the user-specific logic is saved in the database to log a specific user response for a specific situation and reads the saved data back next time such situation occurs. It will be appreciated that such logs may be used to train a system for future automation. Furthermore, the orchestration module compiles the received (and saved) user-specific logic into the server-specific orchestration definition. The server-specific orchestration definition is a machine -readable structured format of the user-specific logic that can be read and processed by the server arrangement for operating the device controller and the associated one or more devices to perform the desired orchestration activity. In this regard, for example, the English sentences of the user-specific logic are transformed into a format selected from any one of: microformat, RDF, HTML, CSV, XML, JSON, and so on, to provide the necessary context required to support the application for which they are created. Moreover, the compiled server-specific orchestration definition is also persisted in the database for further processing thereof or training the system for example. Notably, the server arrangement communicates with various one or more devices associated with the device controller and based on the received communication use a corresponding server-specific orchestration definition to prepare the one or more devices to perform the desired orchestration activity.
Optionally, the orchestration application is configured to persist the server-specific orchestration definition in the database with a unique identification and a corresponding correlation ID is shared with an authorized user. Specifically, the unique identification associated with the server-specific orchestration definition enables securely storing thereof with the server arrangement until it is required by the device controller and the one or more devices for orchestrating the desired orchestration activity.
In a second step, the distributer application is configured to compile the server- specific orchestration definition into the orchestration definition for operating the one or more devices. The orchestration definition, as mentioned above, is a unique device specific format readable and understandable by a specific device, such as the device controller and/or the corresponding one or more devices. The orchestration definition is different from the server-specific definition in that the specific devices are associated with different operating systems and require a specific format for performing the desired orchestration activity. In an example, an orchestration definition for an infrared sensor is different from an orchestration definition for a hot. In yet another example, an orchestration definition for an iOS-based device is different from an Android-based device.
Moreover, the distributer application is configured to distribute the orchestration definition along with the execution logic to the one or more devices for performing the desired orchestration activity. It will be appreciated that the orchestration definition and the execution logic is specific for a particular device, selected from the registered one or more devices, that is required to perform the desired orchestration activity. Further, the orchestration definition and the execution logic is implemented in the particular device(s) of the hierarchical network. Therefore, the orchestration definition along with the execution logic specific for a device is loaded thereon for performing the desired orchestration activity. The term "execution logic " refers to a set of instructions for carrying out a process, by an executing machine such as one or more devices, based on a command from the user. Notably, the execution logic is descriptive of a particular action carried out by the one or more devices in order to perform the desired orchestration activity. The orchestration definition and the execution logic corresponding to a given device for performing the desired orchestration activity is distributed to or loaded on to the given device as and when required to avoid using up the microprocessor memory of the given device. Beneficially, the aforementioned two-step compilation process enables a format that is small enough as the memory provision in the microprocessors, but represent all the orchestration definitions required to perform the desired orchestration activity. Therefore, the limitation of the microprocessor memory does not turn into a limitation of the system.
Optionally, the device controller is configured to operate the one or more devices to perform the desired orchestration activity based on communication received from at least one of: the sensors, the server-specific orchestration definition, the orchestration definition, and other connected devices. Moreover, the orchestration activity of the corresponding one or more devices, such as an appliance, is pre- defined by the orchestration definition. Therefore, the device controller is configured to operate the actuators and corresponding appliances to perform the orchestration activity based on the received sensor data and/or composite situations (i.e. from local or remote neighboring devices). Optionally, the orchestration definition is loaded on to the one or more devices and/or device controller in real time based on the received sensor data and/or composite situations. Optionally, the orchestration definition may be determined from a previous orchestration activity, such as for example, a frequently implemented orchestration definition, such as for example from the previous day, week or month. It will be appreciated that the communicating devices, i.e. the one or more devices, the server arrangement and the neighboring devices, are all communicably coupled. Optionally, the device controller is configured to command the remote appliances to perform a corresponding activity to enable performing the desired orchestration activity.
Moreover, the orchestration definition is loaded to the one or more device by an authorized user. More specifically, the authorized user connects to the virtual platform and selects a particular device in the virtual platform. Subsequently, a request for loading the orchestration definition to the selected device is generated by using the correlation identity associated with the unique identity assigned to the server-specific orchestration definition and the user's authorization code. Consequently, the distributer application compiles the server-specific orchestration definition into the orchestration definition and loads the compiled orchestration definition to the selected device. Beneficially, storing the server-specific orchestration definition in the database for a major part of time enables saving only a part of the orchestration definition in the microprocessor memory of the particular one or more devices that is required for orchestrating the desired orchestration activity in real-time. Optionally, the authorized users operate, take actions and share data from the claimed one or more devices.
In an embodiment, the system is a stand-alone system and can operate independently. For example, the orchestration definition is not required to be installed in an external device, such as a mobile or laptop device. The orchestration definition can be run on the system itself, such as on the device controller and/or one or more devices. Additionally, the system may be accessed at various levels, such as end-user, local user, technical user and device implementer, to ensure proper working thereof. Moreover, the system components are secured for authorized use only.
In an exemplary implementation, the system comprises creating an automation project on a virtual platform by a user, registered with the system. The user is required to fill out an inception document to define an automation need in detail. Subsequently, the user is required to select one or more devices from the virtual platform and map the sensors as well as actuators thereof. Optionally, a mapping of the sensors with the corresponding actuators is also performed to ensure proper coordination therebetween. The system is configured to identify and reset events based on any dependent event. Optionally, the events may be local parameters such as sensor data, commands from connected devices, state data of the devices, and so on. Optionally, the system employs the said events to create an orchestration definition. The orchestration definition is stored in a part of the system, specifically the server, until the orchestration definition is required to be loaded to a particular electronic device for operation thereof. Subsequently, the orchestration activity is performed by the particular one or more devices based on the orchestration definition.
The present disclosure also relates to the method as described above. Various embodiments and variants disclosed above apply mutatis mutandis to the method.
The method of automation comprising: receiving, from a user device, a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; - sharing the execution information and status of the performed orchestration activity with a third-party.
The execution information and status of the performed orchestration activity is shared with a third-party to enable identification of dependent events and assessing change in the overall execution if one or more of the dependent events is changed. Optionally, the user-specific logic is in a structured natural language or as input to dynamic web form.
Optionally, the authorized users operate, take actions and share data from the claimed one or more devices.
DETAILED DESCRIPTION OF THE DRAWINGS Referring to FIG. 1, illustrated is a schematic illustration of a system 100 for automation, in accordance with an embodiment of the present disclosure. The system 100 for automation comprises a device controller 102 and a server arrangement 104. The device controller 102 is configured to operate one or more devices, such as devices 106, 108 and 110, to perform a desired orchestration activity. The one or more devices, such as the devices 106, 108 and 110, are physically connected to the device controller 102. The server arrangement 104 is communicably coupled to the device controller 102 and a user device 112 associated with a user (not shown). The server arrangement 104 comprises an orchestration application and a distributer application. The orchestration application is configured to receive, from the user device 112, a user-specific logic, persist the user-specific logic in a database 114, compile the user-specific logic into a server- specific orchestration definition, and persist the server-specific orchestration definition in the database 114. The distributer application is configured to compile the server-specific orchestration definition into an orchestration definition for operating the one or more devices, such as the devices 106, 108 and 110, and distribute the orchestration definition along with an execution logic to the one or more devices, such as the devices 106, 108 and 110, for performing the desired orchestration activity.
Referring to FIG. 2, illustrated is a flow chart 200 of steps of a method of automation, in accordance with an embodiment of the present disclosure. At step 202, a user-specific logic is received from a user device. At step 204, the user- specific logic is persisted in a database. At step 206, the user-specific logic is compiled into a server-specific orchestration definition. At step 208, the server- specific orchestration definition is persisted in the database. At step 210, the server- specific orchestration definition is compiled into an orchestration definition for operating the one or more devices. At step 212, the orchestration definition along with an execution logic is distributed to the one or more devices for performing a desired orchestration activity. At step 214, the execution information and status of the performed orchestration activity is shared with a third-party.
The steps 202, 204, 206, 208, 210, 212 and 214 are only illustrative and other alternatives can also be provided where one or more steps are added, one or more steps are removed, or one or more steps are provided in a different sequence without departing from the scope of the claims herein.
Modifications to embodiments of the present disclosure described in the foregoing are possible without departing from the scope of the present disclosure as defined by the accompanying claims. Expressions such as “including”, “comprising”, “incorporating”, “have”, “is” used to describe and claim the present disclosure are intended to be construed in a non-exclusive manner, namely allowing for items, components or elements not explicitly described also to be present. Reference to the singular is also to be construed to relate to the plural.

Claims

CLAIMS What is claimed is:
1. A system for automation, the system comprising:
- a device controller configured to operate one or more devices to perform a desired orchestration activity, wherein the one or more devices are physically connected to the device controller; and
- a server arrangement having an application module comprising:
- an orchestration application configured to:
- receive a user-specific logic,
- persist the user-specific logic in a database,
- compile the user-specific logic into a server-specific orchestration definition, and
- persist the server-specific orchestration definition in the database; and
- a distributer application configured to:
- compile the server-specific orchestration definition into an orchestration definition for operating the one or more devices, and
- distribute the orchestration definition along with an execution logic to the one or more devices for performing the desired orchestration activity.
2. A system of claim 1, wherein the device controller comprises multiple plug in ports for receiving one or more devices.
3. The system of claim 1 or 2, wherein the one or more devices are selected from a group of: a central management system, a subsystem, an edge orchestration device, wherein the edge orchestration device is at least one of: a sensor, an actuator, a switch, a regulator, an appliance, and a communication device.
4. The system of claim 2, wherein the sensors are operable to sense and record local parameters in real time and generate corresponding sensor signals.
5. The system of any of the preceding claims, wherein the device controller is configured to operate the one or more devices to perform the desired orchestration activity based on communication received from at least one of: the sensors, the server-specific orchestration definition, the orchestration definition and other connected devices.
6. The system of claim 1, wherein the orchestration application is configured to persist the server-specific orchestration definition in the database with a unique identification and a corresponding correlation ID is shared with an authorized user.
7. The system of any of the preceding claims, wherein the user-specific logic is in a structured natural language or as input to dynamic web form.
8. The system of any of the preceding claims, wherein the system further comprises a user interface to receive a user-specific logic.
9. A system of claim 8, wherein the user interface displays a virtual platform, and wherein the virtual platform is configured to register thereon at least one of: the device controller, the one or more devices and an authorized user.
10. A system of any of the preceding claims, wherein the authorized users claim the registered device using a unique device identity in the virtual platform.
11. A system of any of the preceding claims, wherein the authorized users operate, take actions and share data from the claimed one or more devices.
12. A method of automation, the method comprising: receiving a user-specific logic; persisting the user-specific logic in a database; compiling the user-specific logic into a server-specific orchestration definition; - persisting the server-specific orchestration definition in the database; compiling the server-specific orchestration definition into an orchestration definition for operating the one or more devices; distributing the orchestration definition along with an execution logic to the one or more devices for performing a desired orchestration activity; sharing the execution information and status of the performed orchestration activity with a third-party.
13. The method of claim 12, wherein the user-specific logic is in a structured natural language or as input to dynamic web form.
14. A method of claim 12 or 13, wherein the authorized users operate, take actions and share data from the claimed one or more devices.
PCT/IB2021/051419 2020-02-21 2021-02-19 An automated system to perform desired orchestration activity WO2021165900A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202011007499 2020-02-21
IN202011007499 2020-02-21

Publications (1)

Publication Number Publication Date
WO2021165900A1 true WO2021165900A1 (en) 2021-08-26

Family

ID=77391477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/051419 WO2021165900A1 (en) 2020-02-21 2021-02-19 An automated system to perform desired orchestration activity

Country Status (1)

Country Link
WO (1) WO2021165900A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170093593A1 (en) * 2015-09-24 2017-03-30 Intel Corporation FACILITATING PORTABLE, REUSABLE, AND SHARABLE INTERNET OF THINGS (IoT)-BASED SERVICES AND RESOURCES
US10276170B2 (en) * 2010-01-18 2019-04-30 Apple Inc. Intelligent automated assistant
US20190238358A1 (en) * 2018-02-01 2019-08-01 Bby Solutions, Inc. Automatic device orchestration and configuration
US20190287525A1 (en) * 2018-03-19 2019-09-19 Samsung Electronics Co., Ltd. System for processing sound data and method of controlling system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10276170B2 (en) * 2010-01-18 2019-04-30 Apple Inc. Intelligent automated assistant
US20170093593A1 (en) * 2015-09-24 2017-03-30 Intel Corporation FACILITATING PORTABLE, REUSABLE, AND SHARABLE INTERNET OF THINGS (IoT)-BASED SERVICES AND RESOURCES
US20190238358A1 (en) * 2018-02-01 2019-08-01 Bby Solutions, Inc. Automatic device orchestration and configuration
US20190287525A1 (en) * 2018-03-19 2019-09-19 Samsung Electronics Co., Ltd. System for processing sound data and method of controlling system

Similar Documents

Publication Publication Date Title
JP7392245B2 (en) Orchestration system, computer program, non-transitory machine-readable storage medium, and method
US10663956B2 (en) Configuration in process plant using I/O-abstracted field device configurations
US11435728B2 (en) I/O virtualization for commissioning
US7640291B2 (en) Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming
US7146232B2 (en) Agent program environment
US20180173205A1 (en) Industrial internet connected control system
EP1580630B1 (en) Controller with agent functionality
US11163536B2 (en) Maintenance and commissioning
Leitão et al. Multiagent system integrating process and quality control in a factory producing laundry washing machines
CN101305350A (en) Software architecture system and method for communication with, and management of, at least one component within a household appliance
EP3243110B1 (en) Provisioning of control layer applications for use in industrial control environments
US9208267B2 (en) Cloud based simulation and analysis for control appliances
Katipamula et al. An open-source automated continuous condition-based maintenance platform for commercial buildings
Katsigarakis et al. Sense‐Think‐Act Framework for Intelligent Building Energy Management
Vrba Review of industrial applications of multi-agent technologies
CN113641150A (en) Remote deployment and commissioning of workstations within a distributed control system
WO2021165900A1 (en) An automated system to perform desired orchestration activity
CN105264447A (en) Process automation system with a central computing unit
EP1577724B1 (en) Agent program environment
US10476869B2 (en) Apparatus and method for obtaining up-to-date security credentials
Katipamula et al. Transactional network: Improving efficiency and enabling grid services for buildings
CN104641305A (en) System for account setup and/or device installation
KR102613336B1 (en) Smart Housing Platform, and Smart Home Service Method
US20230306099A1 (en) Multi-factor authentication of industrial assets
Krejcar Complete low cost SCADA system of the intelligent house

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: 21757126

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21757126

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21757126

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20/03/2023)