FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM OF AUTOMATIC RULE CREATION FOR IOT DEVICE”
We, Reliance Jio Infocomm Limited, an Indian National of, 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad-380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF INVENTION
The present invention relates to wireless network and user equipment, and more particularly to embedded IoT devices interconnected with cognitive technology, referred to as cognitive Internet of Things (CIoT).
BACKGROUND OF THE INVENTION
The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
The Internet of Things (IoT) is a network of devices, vehicles, home appliances, and other items embedded with electronics, software, sensors, actuators, and connectivity which can be readable, recognizable, locatable, addressable, and controllable via an IoT communications network that enables these devices to connect and exchange data, creating opportunities for more direct integration of the physical world into computer-based systems, resulting in efficiency improvement, economic benefits, and reduced human exertions. With the “Internet of things” (IoT) concept getting more and more popular, devices, such as sensors, actuators and everyday objects including coffee makers, washing machines, headphones, lamps and wearable devices, etc. are also being increasingly looked upon as potential IoT devices. IoT involves extending internet connectivity beyond standard devices, such as desktops, laptops, smartphones and tablets, to any range of traditionally dumb or non-internet-enabled physical devices and everyday objects. Embedded with technology, these devices can communicate and interact over the Internet, and they can be remotely monitored and controlled.
The term "Enterprise IoT" refers to devices used in business and corporate settings in a network of physical objects that contain embedded technology to

communicate and sense or interact with their internal states or the external environment. Here, IoT refers to Internet-connected physical devices, in many cases everyday objects (things) that can communicate their status, respond to events, or even act autonomously. This enables communication among those things, closing the gap between the real and the virtual world and creating smarter processes and structures that can support us without needing our attention. IoT has evolved from the convergence of wireless technologies, micro-electromechanical systems (MEMS), and the Internet. An IoT device is generally provisioned with an IP address to provide it with the capability of transferring data and receiving control signals over an IP network using the standard Internet protocols such as TCP/IP which is being exclusively used on the Internet. Recently, 3GPP has introduced a new technology NB-IoT i.e., Narrowband IoT in release 13. The low-end IoT applications can be met with this technology. This technology has better performance than the Low Power Wide Area (LPWA). It has taken efforts to address IoT markets with completion of standardization on NB-IoT. Narrowband IoT is a low power wide area network (LPWAN) technology. NB-IoT has been developed to enable efficient communication, long battery life for mass IoT devices. The NB-IoT technology has been implemented in licensed bands. The licensed bands of LTE are used for exploiting this technology. This technology makes use of a minimum system bandwidth of 180 kHz i.e. one PRB (Physical Resource Block) is allocated for this technology. The NB-IoT can be seen as a separate RAT (Radio Access Technology). The NB-IoT can be deployed in 3 modes: “in-band”, “guard band” and “standalone”. In the “in-band” operation, resource blocks present within LTE carrier is used. The inner resource blocks are not used as they are allotted for synchronization of LTE signals. In “guard band” operation, resource blocks between LTE carriers that are not utilized by any operator are used. In “standalone” operation, GSM frequencies are used or possibly unused LTE bands are used. Release 13 contains important refinements like discontinuous reception (eDRX) and power save mode. The PSM (Power Save

Mode) ensures battery longevity in release 12 and is completed by eDRX for the devices that need to receive data more frequently.
The NB-IoT technology focuses on devices like meter reading of water and electricity consumption that are stationery. Some of the use cases are: facility management services, fire alarms for home and commercial properties, tracking of persons and objects. The industries where NB-IoT services can add value are: Smart city, smart home, safety and security, agriculture, health care and Energy. Another example for IoT industry includes logistic tracking. The tracking devices on shipping containers send huge volumes of sensor data that are collected and taken for analysis in order to make sure that real-time tracing of shipment locations can be made possible. The output display units are used for receiving alerts and optimized with service recommendations. The NB-IoT technology addresses some of the key IoT requirements:
• Battery lifetime of the devices increases.
• Improved network coverage.
• Cost of the devices is reduced.
• Multiplexing of devices met for capacity requirements.
• Support a massive number of devices.
The NB-IoT technology support low power consumption, use of low-cost devices and provides excellent coverage.
In the existing art, for instance, one solution provides a method for collecting and utilizing user behaviour data within an IoT system. The prior art solution utilizes data associated with the user behaviour to monitor and record each user from each of the IoT devices and the IoT devices controlled by each user but does not provide any solution in which the IoT devices are interconnected with cognitive technology and wherein the IoT output are based on the inference of rules based on user pattern trigger actions which are based on the occurrence of events as well as capability data of the respective IoT devices.

Moreover, another prior art solution provides a method for analyzing individual and group healthcare data in order to provide real-time healthcare recommendations. The prior art solution numerically solves certain types of computationally explosive operations in healthcare where computationally explosive comparison can increase exponentially if the genetic sequences of a million humans are compared to the genetic sequences of a second, different million humans. Thus, the above-mentioned solution solves certain types of computationally explosive operations but does not provide any solution in which the IoT devices are interconnected with cognitive technology and wherein the IoT output is based on the inference of rules based on user pattern trigger actions based on the occurrence of events as well as capability data of the respective IoT devices.
The existing arts do not describe automatically creating rules and actions based on devices owned by a user, and also do not describe triggering actions based on events received from the devices. As users continue to buy more IoT devices, defining explicit rules across devices, understanding each device capabilities are a tedious process and have a steep learning curve for end-user. As a huge number of IoT devices are connected and as businesses use applications to parse IoT data, defining and understanding explicit rules across devices becomes a real concern. Also, as the numbers grow for the IoT devices in the future there needs to be an efficient architecture to optimally create rules and actions based on devices owned by user and triggers actions based on events from device to save the power of the battery and provide improved coverage. Therefore, there is a need in the art, for a system and a method to automatically create rules and actions for IoT devices owned by a user and provide an efficient way of communication between a massive number of IoT devices.
SUMMARY
This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed

description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present disclosure is to provide a method and system for automatically creating rules and actions using cognitive IoT technology. It is also an object of the present invention is to provide a system and method that can support cognitive solution for IoT wherein the IoT output are based on the inference of rules based on user pattern triggered actions based on the occurrence of events as well as capability data of the respective IoT devices. Another object of the present invention is to provide a method that tries to auto-create rules and actions based on devices owned by user and triggers actions based on events from device. Another object of the present invention is to address the issue of complexity that will help common people who are not tech-savvy and be able to use IoT devices in most efficient manner with a very simple interface.
Yet another object of the present invention is to recommend IoT rules inferred based on user pattern of triggering an action based on events decision to automate a rule with proven pattern (Higher frequency follow up action) identified by cloud and accuracy verified by taking selective user consent. Yet another object of the present invention is to leverage data from existing user interactions with IoT devices and uses the information to generate rules for new device owners. Yet another object of the present invention is to identify appropriate actions on users IoT devices based on the capabilities of devices owned. Yet another object of the present invention is to recommend inferred rules on account the social relationships of a user and associated emotional context to an event. Yet another object of the present invention is to enable connectivity across multiple non-compatible devices for interactions that will help users appreciate the value of IoT devices and will incentivize users to buy even non-compatible devices.

Yet another object of the present invention is to make users aware that IoT devices are not just control appliances with on/off operations but with cognitive solution for IoT wherein the IoT output are based on the inference of rules based on user pattern triggered actions based on the occurrence of events. Yet another object of the present invention is to recommend IoT rules to users as part of device provisioning workflow for any new purchased IoT device like camera, thermostat, AC, etc. Yet another object of the present invention is to provide artificial intelligence system utilizing explicitly and/or implicitly trained classifiers that can be used, via device context and rule engine component, to automatically learn and create actions itself, based on the events associated with IoT device.
In order to achieve the aforementioned objectives, the present disclosure provides a method and a system for automatically creating rules and actions for IoT devices using cognitive Internet of Things.
One aspect of the present invention relates to a method of automatically creating rules and actions for IoT devices. The method comprises receiving, at a device capability management unit, one or more capabilities of a plurality of IoT devices. Next, the method comprises correlating, by the device capability management unit, the one or more capabilities of the plurality of IoT devices. Next, the method comprises creating automatically, at a rule engine unit, at least one rule and at least one action for each of the plurality of IoT devices based on the correlation of the one or more capabilities of the plurality of IoT devices, wherein the at least one action relates to the at least one rule. Thereafter, the method comprises receiving, at an event processor unit, at least one event data from at least one of the plurality of IoT devices. Next, the method comprises processing, at the rule engine unit, the at least one event data to identify the at least one rule and the at least one appropriate action for the at least one of the plurality of IoT devices. Thereafter, the method comprises executing, by a rule execution unit, the identified at least one rule and the at least one action on the

at least one of the plurality of IoT devices.
Another aspect of the present invention relates to a system for automatically creating rules and actions for IoT devices. The system comprises a device capability management unit, configured to receive, one or more capabilities of a plurality of IoT devices. and to correlate the one or more capabilities of the plurality of IoT devices. The system comprises a rule engine unit connected to the device capability management unit. The rule engine unit is configured to create automatically at least one rule and at least one action of the plurality of IoT devices based on the correlation of the one or more capabilities of the plurality of IoT devices, wherein the at least one action relates to the at least one rule. The system comprises an event processor unit connected to the rule engine unit and the device capability management unit. The event processor unit is configured to receive at least one event data from at least one of the plurality of IoT devices. Thereafter, the rule engine unit is configured to process the at least one event data to identify at least one rule and at least one appropriate action for the at least one of the plurality of IoT devices.
The system also comprises a rule execution unit connected to the event processor unit, the rule engine unit and the device capability management unit. The rule execution unit is configured to execute the identified at least one rule and the at least one action on at least one of the plurality of IoT devices.
BRIEF DESCRIPTION OF INVENTION
The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure

of such drawings includes disclosure of electrical components, electronic
components or circuitry commonly used to implement such components.
FIG.1 illustrates a block diagram of an NB-IoT Device [100], in accordance with
exemplary embodiments of the present disclosure.
FIG. 2 illustrates a block diagram of a system [200] for automatically creating
rules and actions for IoT devices, in accordance with exemplary embodiments of
the present disclosure.
FIG.3 illustrates an exemplary method flow diagram [300] for automatically
creating rules and actions for the IoT devices, in accordance with exemplary
embodiments of the present disclosure.
FIG. 4 illustrates an exemplary signal flow diagram illustrating creation of at least
one rule, in accordance with exemplary embodiments of the present disclosure.
FIG. 5 illustrates an exemplary signal flow diagram illustrating execution of at
least one rule, in accordance with exemplary embodiments of the present
disclosure.
FIG. 6 illustrates an exemplary diagram representing the execution of the at least
one rule and the at least one action, in accordance with exemplary embodiments
of the present disclosure.
The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DESCRIPTION OF THE INVENTION
In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the invention. However, it will be apparent that various embodiments of the present disclosure may be practiced without these specific details. The figures and description are not intended to be restrictive. The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide

those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be

combined in any suitable manner in one or more embodiments.
The term “machine-readable storage medium” or “computer-readable storage medium” or “memory unit” or “storage unit” includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing, or carrying instruction(s) and/or data. A machine-readable medium may include a non-transitory medium in which data can be stored and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-program product may include code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
As used herein, a “processor” or “processing unit” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according

to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
As used herein, a “rule” may refer to a set of instructions defined for the IoT devices to perform the one or more tasks in a desired and an efficient manner. For example, the instruction may be created for a water level sensor (e.g., an IoT device) to send an alert to a user device in case the water level reaches to a threshold level.
As used herein, a “user equipment”, “user device”, “smart-user device”, “electronic device”, “mobile station,” “mobile subscriber station,” “access terminal,” “terminal,” “handset,” “appliance,” “machine”, and similar terminology refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive and/or convey data associated with voice, video, sound, and/or substantially any data-stream or signaling-stream. Furthermore, the user equipment may be any electrical, electronic, and/or computing device or equipment, which is capable of implementing the features of the present disclosure and is obvious to a person skilled in the art. Also, the foregoing terms are utilized interchangeably in the subject specification and related drawings.
The present invention provides a solution relating to an efficient way of communicating between a plurality of IoT devices with less power consumption to ease the life of the user. More specifically, the present invention provides a method and a system for automatically creating rules and actions to be performed by at least one of the plurality of IoT devices based on the event data received from the at least one of the plurality of IoT devices. Further, the present invention provides a method and a system for automatically creating rules and the associated actions to the IoT devices using cognitive IoT technology. In general, the cognitive IoT refers to the use of cognitive computing technologies in combination with data generated by connected IoT devices and the actions those IoT devices can perform. The present invention receives the capabilities of

the IoT devices and identifies the correlation between the IoT devices owned by the user. Based on the correlation between the IoT devices, user pattern of interacting with the IoT devices, and one or more parameters, the present invention automatically creates rules to be executed by at least one of the IoT devices based on the event data received from the at least one of the plurality of IoT devices. The present invention is further explained in detail below with reference now to the diagrams.
Referring to FIG. 1, that illustrates an exemplary block diagram of NB-IOT device [100], in accordance with exemplary embodiments of the present disclosure. As shown in FIG. 1, the NB-IoT device 100 comprises at least one NB-IoT Radio Interface [110], at least one antenna [112], at least one IoT application module [102], at least one memory [106], at least one on-boarding client module [108] and at least one processing unit [104], said components being connected to each other.
The NB-IoT Radio Interface [110] of the said NB-IoT device [100] is coupled to said antenna [112], IoT application module [102], on-boarding client module [108] and processing unit [104]. The NB-IoT Radio Interface [110] along with the said antenna [112] is configured to enable wireless communication over an NB-IoT network. The NB-IoT Radio Interface [110] further along with said antenna [112] provides wireless access to the NB-IoT device by implementing known NB-IoT LTE protocols.
The memory [106] is coupled to said IoT application module [102], on-boarding client module [108] and processing unit [104]. The memory [106] is configured to store data from the different modules of NB-IoT Device [100], in order to assist the said modules to carry out different functions.
The IoT application module [102] is coupled to said NB-IoT LTE Radio Interface [110], memory [106], on-boarding client module [108] and processing unit [104]. The IoT application module [102] may be configured to implement IoT functionality in combination with multiple hardware and software components.

The said IoT application module [102] is further configured to communicate over the desired IP path via said NB- LTE IoT Radio Interface [110].
The on-boarding client module [108] is coupled to said NB-IoT LTE Radio Interface [110], memory [106], IoT application module [102] and processing unit [104]. The on-boarding client module [108] may be configured to communicate to an on-boarding server via the NB LTE-IoT Radio Interface [110] while being in charge of device-specific on-boarding function.
Further, the processing unit [104] of NB-IoT Device is coupled to said, IoT Application module [102], NB-IoT LTE Radio Interface [110], the memory [106], and the on-boarding client module [108]. The processing unit [104] is configured to execute the functions of all modules present in the NB-LTE-IoT device. The processing unit [104] is also configured to process and send the data associated with the capabilities of the IoT Device, data associated with the type of IoT device, data associated with the maintenance of the IoT device, data associated with the working of the IoT device, data associated with any defect in the IoT device and the like. Further, the processing unit [104] is also configured to process all the data which is required to enable the functions of the present invention.
In one of the preferred embodiments, the NB-IoT ecosystem may include various modules according to various aspects of the invention described to provide wireless access to the NB-IoT client devices according to the 3GPP NB-IoT protocols. For instance, the NB-IoT ecosystem may include Access Point application responsible for managing and provisioning the NB-IOT wireless Access Point. Further, the NB-IoT ecosystem may include communication interface for backhaul and to reach out to onboarding server for information exchange. The processor and memory which are being used by various modules of Access Point may be used to carry out their respective functions.
Referring to FIG. 2, that illustrates a block diagram of a system [200] for automatically creating rule and action for IoT devices, in accordance with

exemplary embodiments of the present disclosure. The system [200] comprises a plurality of IoT devices [202A, 202B, … 202N, hereinafter collectively referred to as ‘202’], an IoT Gateway [204], and a cloud server [212], said components being connected to each other. The IoT Gateway [204] further includes a rule execution unit [206], a sensor profile management unit [208], and a firmware upgrade controller unit [210]. The cloud server [212] further includes a Cloud Application Programming Interface (Cloud API) [214], a device provisioning unit [216], a firmware upgrade unit [218], an access control unit [220], a rule engine unit [222], a device context unit [224], a notification service unit [226], a device capability management unit [228], an event processor unit [230], and a storage unit [232], an application on a user device [234], wherein all the components are connected to each other.
As used herein, the “cloud API” refers to a cloud-based application programming interface that enables the development of applications and services used for the provisioning of cloud hardware, software, and platforms. Cloud APIs allows an administrator to integrate applications and other workloads into the cloud. Further, the cloud API [214] facilitates in providing an interface for the exchange of information between the units present at the IoT Gateway [204] and the cloud server [212]. Furthermore, each of the unit present at the cloud server [212] is connected with other units of the cloud server [212] through the Cloud API as the cloud API specifies the way of interaction between the software/hardware components. In a non-limiting example, the cloud API facilitates in providing a way of interaction in between the event processor unit [230] and the rule engine unit [222].
As used herein, “IoT device” is a piece of hardware with a sensor that transmits data from one place to another over the Internet. The IoT devices include but is not limited to wireless sensors, software, actuators, and computer devices. These devices are attached to a particular object that operates through the internet, enabling the transfer of data among objects or people automatically

without human intervention. Further, the IoT device refers to any electrical, electronic, electromechanical and computing device. The NB-IoT device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other NB-IoT devices as well as non NB-IoT devices and transmitting data to these devices. In an example, the IoT device includes but are not limited to, a thermostat, an electric switch, a washing machine, a computing device, a coffee maker, a refrigerator, a headphone, a lamp, a room sensor, a microwave, a fan, a light and any such device that is obvious to a person skilled in the art. NB-IoT devices may be capable of operating on any radio access technology and facilitate interoperability, including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy (BLE), Near Field Communication (NFC), Z-Wave, and the like. In an example, IoT device [202A] is capable of operating on Zig Bee radio access technology, the IoT device [202B] is capable of operating on Bluetooth Low Energy radio access technology. Thus, the plurality of IoT devices [202] are capable of operating on at least one of IP-enabled communication, Zig Bee technology, Bluetooth technology, Bluetooth Low Energy (BLE) technology, Near Field Communication technology, Z-Wave technology, and the like.
As used herein, “Zigbee” is an IEEE 802.15.4 based, low power, low data rate supporting wireless networking standard, which is basically used for two-way communication between sensors and control system. It is a short-range communication standard which covers a range of 10 to 100 meters. As used herein, “Bluetooth Low Energy (BLE)” or “Bluetooth Smart”, is the low power-version of Bluetooth that was developed for the Internet of Things (IoT) and was introduced as part of the Bluetooth 4.0 core specification. Bluetooth LE uses a 2.4 GHz unlicensed radio band to interconnect nearby devices. It provides a data rate of up to 1 Mbps while consuming just 0.01 to 0.5 watts. An IoT device is generally provisioned with an IP address to provide it with the capability of transferring data and receive control signals over an IP network using the

standard Internet protocols such as TCP/IP which is being exclusively used on the Internet. In an example, the use of the IoT devices may include but are not limited to home automation, wearable devices, security devices, child monitoring, fitness and health devices.
The system [200] comprises the device capability management unit [228]. The device capability management unit is configured to receive one or more capabilities of the plurality of IoT devices [202]. Further, the data associated with the one or more capabilities of the plurality of IoT devices [202] is received through the IoT Gateway [204].
As used herein, the “device capability” of an IoT device refers to the actions supported by the IoT device. In an example, the IoT device is a smart Air Conditioner (AC) and the one or more capabilities of the smart AC may refer to the action of smartly monitoring and controlling the temperature of the environment or automatically gets turn on based on the temperature of the environment. In another example, the IoT device is a wearable fitness tracker and the one or more capabilities of the fitness tracker are to track the health parameters of a user and to automatically notify the user or a doctor in case the blood pressure of the user reaches too low or reaches too high.
As used herein, the “IoT Gateway” refers to a medium to transfer the data from the plurality of IoT devices [202] to the cloud server [212] and vice-versa. In general, the Internet of Things (IoT) gateway is a physical device or software program that serves as the connection point between the cloud and controllers, sensors and intelligent devices. Further, the IoT Gateway [204] can provide additional security for the IoT network and the data it transports. Moreover, as a part of the wireless service operators’ network, the IoT Gateway [204] supports remote control, detection and configuration of the multiple IoT devices. The device capability management unit [228] is configured to manage the one or more capabilities of the plurality of IoT devices [202]. More particularly, the device capability management unit [228] is configured to correlate the one or

more capabilities of the plurality of IoT devices [202]. The device capability management unit [228] perform analysis of the one or more capabilities of the plurality of IoT devices [202] to find the correlation between the plurality of IoT devices [202]. In one embodiment, the device capability management unit [228] find the correlation between the plurality of IoT devices [202] based on the past interaction of the user with the IoT devices or based on the data associated with the interaction of the similar plurality of users with their owned IoT devices. In another embodiment of the present invention, the device capability management unit [228] find the correlation between the IoT devices using data associated with the pre-existing rules defined for the IoT devices. In yet another embodiment of the present invention, the device capability management unit [228] find the correlation between the plurality of IoT devices based on the score provided by the users using the IoT devices. For example, the working of the IoT device X with the IoT device Y is preferred and liked by a majority of users and thus the score of the correlation of IoT device X with IoT device Y is high. In another example, the first IoT device i.e., smoke detector can work well with a second IoT device i.e., sprinkler for the spray of water and a third IoT device i.e., smartphone to remotely monitor the situation. Thus, the device capability management unit [228] correlates the capabilities of the smoke detection sensor and the sprinkler sensor to perform a task of spraying the water at the time of smoke detection or at the time of the fire and also providing the live streaming command to the camera to remotely monitor the situation.
The device capability management unit [228] is connected with the rule engine unit [222] via the cloud API [214] to transmit the one or more capabilities and the correlation data of the plurality of IoT devices [202]. The rule engine unit [222] is connected to the device capability management unit [228]. The rule engine unit is configured to create automatically at least one rule and at least one action for each of the plurality IoT devices based on the correlation of the one or more capabilities of the plurality of IoT devices. Further, the at least one

action relates to the at least one rule. The rule engine unit [222] maintains the at least one rule and the at least one action in a Rule Database and interfaces with the device capability management unit [228] during rule creation process. Each of the at least one rule created by the rule engine unit [222] is first validated by the user and then execution of the at least one rule occurs. In case the at least one rule created by the rule engine unit [222] is not validated or accepted by the user, the at least one rule gets deleted.
The rule engine unit [222] is configured to create the at least one rule and the at least one action using an artificial intelligence-based systems. In example, the rule engine unit [222] utilize explicitly and/or implicitly trained classifiers which can be employed in connection with performing inference and/or probabilistic determinations and/or statistical-based determinations to create automatically the at least one rule. The rule engine unit [222] with artificial intelligence-based systems facilitates in identifying the pattern used for the plurality of IoT devices [202] to create automatically the at least one rule and in determining the trend of actions associated with various events to create the at least one action. In an example, the past interaction of similar users with their owned IoT devices and the efficiency of the at least one action performed by the IoT devices facilitates in determining the at least one appropriate action to be performed by at least one of the plurality of IoT devices [202] owned by the user which further ease the task of creating the at least one rule for the plurality of IoT devices [202]. In an embodiment, the rule engine unit [222] may further create the at least one rule and at least one action to be triggered in response to at least one event by identifying the best appropriate and efficient combination of the IoT devices used in performing the task with high accuracy. The rule engine unit [222] is further configured to provide a score to the at least one rule created for the plurality of IoT devices and also update the score dynamically based on a number of times the at least one rule is executed at the plurality of IoT devices. The rule engine unit [222] is further configured to update the score of the at least one

rule based on the interaction of similar users and the efficiency of the at least
one rule created automatically by the rule engine unit [222]. The rule engine unit
[222] may analyze the rule patterns based on actions triggered by users in
response to time-critical events for automatically creating the at least one rule
and the at least one action for each of the plurality of IoT devices [202]
In an example, the below is a sample rule that is created by the platform for a
user owning Gas Leak sensor and Camera Product. This example is only an
illustration and many such sample rules can be created by person skilled in the
art.
Rule


The system [200] includes the event processor unit [230] connected with the rule engine unit [222] and the device capability management unit [228] through the cloud API [214]. The event processor unit [230] is configured to receive the at least one event data from at least one of the plurality of IoT devices [202]. As used herein, “event” is defined as the occurrence of change in the normal situations or an event may also be defined as the occurrence of unusual or important things.
The event processor unit [230] is configured to refine the event data to filter out the normalized events which require an immediate response or an immediate action to be performed. In an example, the events related to the security, home monitoring, health and fitness may be considered as the relevant or normalized events. For instance, the detection of baby cry in absence of parents, detection of motion at the door, sudden increase or decrease in health parameters of the user and the like can be considered as the relevant or normalized events. Below is another example of the relevant event in which the motion is detected by the Motion sensor and the leakage of the gas is detected by the gas sensor. "Event": ["Motion detected"," Gas Leak detected"]
The event processor unit [230] is configured to receive device context data from the device context unit [224]. The event processor unit [230] sends the request to the device context unit [224] for the addition of the at least one device context data. After receiving the at least one device context data, the event processor unit [230] sends the at least one event data along with the at least one device context data to the rule engine unit [222] for the identification of the at least one rule and the at least one appropriate action. Thus, the rule engine unit [222] identify the at least one rule and the at least one appropriate action for the at least one of the plurality of IoT devices [202] based on the at least one device context data.
The device context unit [224] is connected with the rule engine unit [222], the event processor unit [230], the device capability management unit [228] and the

rule execution unit [206], The device context unit [224] is configured to provide the at least one device context data and its associated social context. Any input event received from the event processor unit [230] is classified based on the context and the corresponding context information is added by the device context unit. In one embodiment, the event processor unit [230] may transmit the at least one normalized event data to the device context unit [224] to add the context of the device for the events. In another embodiment, the rule engine unit [222] may directly coordinate with the device context unit [224] to add the context of the device for the at least one event data received from the event processor unit [230]. The context of the device may be received from one or more sensors like camera sensor, GPS sensors, and the like. In an example, the coordinates of the communication device of the user identifies the location of the user.
The rule engine unit [222] further checks the context of the device by interacting with the device context unit [224]. Based on the context of the device and the normalized event data, the rule engine unit [222] identifies the at least one rule and the at least one appropriate action. Further, the rule engine unit [222] may identify the at least one appropriate action for the at least one of the plurality of IoT devices [202] based on the at least one rule created for the at least one of the plurality of IoT devices associated with the at least one event. Further, the rule engine unit [222] starts inferring at least one rule applicable across the at least one of the plurality of IoT devices [202].
The rule engine unit [222] further sends the identified at least one rule and the identified at least one action to the event processor unit [230]. The event processor unit [230] is further configured to notify the identified at least one rule and identified at least one action to the at least one of the plurality of IoT devices [202]. Further, the at least one rule and the at least one action are executed after an acceptance of the identified at least one rule at the user device. In an example, the at least one rule is notified on the application on a user device of

the user device. Further, the identified at least one rule is activated only after acceptance of the at least one rule created by the rule engine unit [222]. After acceptance or validation of the at least one rule, the rule engine unit [222] communicate with the rule execution unit [206].
The rule execution unit [206] is present at the IoT Gateway [204] for the execution of the at least one rule and the at least one appropriate action associated with the at least one event. The rule execution unit [206] is connected to the event processor unit [230], the rule engine unit [222] and the device capability management unit [228]. The rule execution unit [206] is configured to execute the at least one rule identified by the rule engine unit [222]. The rule execution unit [206] interact with at least one of the plurality of IoT devices for executing the at least one rule and the at least one action.
The IoT gateway [204] further comprises the sensor profile management unit [208] which is configured to manage the sensors installed in the plurality of IoT devices [202]. The sensor profile management unit [208] is further configured to create profile of each of the sensors installed in the IoT devices based on the one or more parameters, wherein the one or more parameters includes but are not limited to battery life, power supply, manufacturing data, expiry data, working status, connectivity data, maintenance data and the like. The profile of each sensor created by the sensor profile management unit also facilitates in managing the sensors. The IoT gateway [204] further comprises the firmware upgrade controller unit [210]. The firmware upgrade controller unit [210] is configured to enable the execution of the updates at each of the plurality of IoT device [202].
The system [200] further comprises a device provisioning unit [216] present at the cloud server [212]. The device provisioning unit [216] manages device registration of the plurality of IoT devices [202] and association to end user. The system [200] further comprises a firmware upgrade unit [218] present at the cloud server [212] which is configured to upgrade the firmware associated with

each of the plurality of IoT devices [202] to enhance the capabilities of the system [200] and to also fix any undesired issue which may affect the efficiency of the system [200]. The system [200] further comprises an access control unit [220] present at the cloud server [212] to manage permissions for gateway and its associated sensors [200]. The system [200] further comprises a notification service unit [226] present at the cloud server [212] which is configured to enable the notification services. In an example, the notification service unit [226] facilitates in providing notification to at least one of the plurality of IoT devices [202] based on incoming device event data.
The system [200] further comprises the storage unit [232] at the cloud server [212]. As used herein, “storage unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machines. The storage unit [232] is configured to maintain a rule database and a context database. The rule database comprises the at least one rule created for the plurality of IoT devices [202] and the context database comprises the at least one device context data received by the device context unit [224]. Further, the storage unit is configured to stores all the data which is required to enable the functionality of the present invention.
FIG.3 illustrates an exemplary method flow diagram [300], depicting method for automatically creating rule and action for IoT devices, in accordance with exemplary embodiments of the present disclosure. The method begins at step [302].
At step [304], the method comprises receiving, at a device capability management unit [228], one or more capabilities of a plurality of IoT devices [202]. Next, at step [306], the method comprises correlating, by the device capability management unit [228], the one or more capabilities of the plurality of IoT devices [202]. Thereafter, at step [308], the method comprises creating automatically, at a rule engine unit [222], at least one rule and at least one action for each of the plurality of IoT devices [202] based on the correlation of the one

or more capabilities of the plurality of IoT devices [202]. The at least one action relates to the at least one rule.
Next, at step [310], the method comprises receiving, at an event processor unit [230], at least one event data from at least one of the plurality of IoT devices [202]. Further, at step [312], the method comprises processing, at the rule engine unit [222], the at least one event data to identify at least one rule and at least one appropriate action for the at least one of the plurality of IoT devices [202]. The method further comprises receiving at least one device context data from a device context unit [224] and then identifying, at the rule engine unit [222], the at least one rule and the at least one appropriate action for the at least one of the plurality of IoT devices [202] based on the at least one device context data. The method further comprises notifying, by the event processor unit [230], the identified at least one rule and the identified at least one action to the at least one of the plurality of IoT devices [202], wherein the at least one rule and the at least one action are executed after an acceptance of the identified at least one rule at the user device.
Thereafter, at step [314], the method comprises executing, by a rule execution unit [206], the identified at least one rule and the at least one action on the at least one of the plurality of IoT devices [202]. The method comprises providing, by the rule engine unit [222], a score to the at least one rule created for the plurality of IoT devices. The score of the rule is dynamically updated based on a number of times the at least one rule is executed at the plurality of IoT devices. The method further comprises maintaining, at a storage unit [232], a rule database and a context database. The rule database comprises the at least one rule created for the plurality of IoT devices [202] and the context database comprises the at least one device context data. After successfully executing the at least one rule and the at least one action, the method terminates at step [314]. FIG. 4 illustrates an exemplary sequence diagram illustrating creation of at least

one rule, in accordance with exemplary embodiments of the present disclosure. At step [402], the IoT device [202A], transmit the one or more capabilities to the device capability management unit [228]. The device capability of the IoT device [202A] refers to the action supported by the IoT device [202A]. In an example, the IoT device [202A] is a motion detection sensor and the action supported by the IoT device [202A] is to sense the motion.
At step [404], the IoT device [202B], transmit the one or more capabilities to the device capability management unit [228]. The device capability of the IoT device [202B] refers to the action supported by the IoT device [202B]. In an example, the IoT device [202B] is a streaming device and the action supported by the IoT device [202B] is to provide streaming of the content.
Next, at step [406], the rule engine unit [222] create automatically at least one rule for the IoT device [202A] and the IoT device [202B] based on the correlation of the one or more capabilities of the IoT device [202A] and the IoT device [202B]. The correlation of the one or more capabilities of the IoT device [202A] and the IoT device [202B] is identified by the device capability management unit [228]. In an example, the detection of motion at the main door by the motion detection sensor (for e.g., IoT Device [202A]) and the streaming of the activity on the display screen by the streaming device (for e.g., IoT Device [202B]) can be correlated by the DCMU for the home security reasons. Thus, the rule engine unit [222] may create an at least one rule of triggering the action of streaming in case the motion is detected at the main door at a certain time or in absence of the user.
Thereafter, at step [408], the IoT device [202A] sends event data to the event processor unit [230]. In an example, the motion detection sensor (for e.g., IoT device [202A]) sends the event of detecting motion at the main door of the house at 1:00 A.M to the event processor unit [230].
Next, at step [410], the event processor unit [230] sends notification of the at least one rule applicable to the event on the application on a user device [234] of

the user. The event processor unit [230] interact with the rule engine unit [222]
for identifying the applicable at least one rule and then notifying the user on an
application on a user device [234] of the user device about the identified at least
one rule.
Next, at step [412], the user accepts the at least one rule for successfully
activation of the at least one rule. Further, the accepted at least one rule is saved
in the rule database and updated in the rule database. The user is not further
notified for rule creation events in future if the user accepts the notified rule. In
case, the user does not accept the at least one rule, the created at least one rule
is deleted by the rule engine unit [222].
Referring to Fig. 5 of the present invention, the Fig. 5 illustrates an exemplary
sequence diagram illustrating execution of at least one rule, in accordance with
exemplary embodiments of the present disclosure.
At step [502], the IoT device [202A] sends event data to the event processor Unit
[230]. In an example, the motion detection sensor (for e.g., IoT device [102A])
sends the event of detecting motion at the main door of the house at 1:00 A.M
to the event processor unit [230].
At step [504], the event processor unit [230] sends a request to a device context
unit [224] to add the context of the event. In an example, the device context unit
[224] checks the presence of the user at home when the motion at the door is
detected by the motion detection sensor and then take the appropriate at least
one action based on the context. Further, the presence of the user at the home
can be detected through multiple sources such as but not limited to GPS sensors
of the user device, camera units, user activity data and the like.
At step [506], the event processor unit [230] sends request to the rule engine
unit [222] to match the events for rule trigger. In an example, the event
processor unit [230] sends request to the rule engine unit [222] to match the
event of detecting motion at the door for triggering the appropriate rule.
At step [508], the rule engine unit [222] check the current device and event

context with the device context unit [224]. In an example, the rule engine unit [222] check the event context with the device context unit [224] and determine that the user is not present at home when the motion is detected at the main door. The rule engine unit [222] checks the device context to identify the appropriate at least one action required to be performed by one of the plurality of IoT devices [202].
At step [510], the rule engine unit [222] identifies the at least one action that needs to be performed by IoT device [102B] based on the at least one rule defined earlier for such type of events and the associated context. In an example, the rule engine unit [222] identifies the at least one action to provide streaming on the streaming device associated with the user for remotely monitoring of the situation. In another example, the rule engine unit [222] may identify the action of notifying the near-by security guards along with providing real-time streaming to the user. The rule engine unit [222] triggers the at least one action to at least one of the IoT device [202B] to perform the required actions.
Referring to Fig. 6 of the present invention, the Fig. 6 illustrates an exemplary use case of the execution of at least one rule, in accordance with exemplary embodiments of the present disclosure.
At step [602], the cry of a baby is detected as a first IoT event. In an example, the baby cry may be detected through at least one of a sound sensor, and a camera sensor. Further, at step [604], the time of the event is identified as 3:00 P.M and the context of the event is identified as the availability of parents in other room. The context of the event may be identified based on the GPS coordinates of the device of the parents or may be based on the historical data of the parents. At step [606], the at least one action is identified as per the defined at least one rule to play lullaby/videos on the display screen of the device in the room of the baby.
At step [608], the motion at the main door is detected as a second IoT event. In an example, the motion at the door may be detected with the help of a motion

sensor. At step [610], the time of the event is identified as 1:00 A.M and the context of the event is identified as “home mode away” which means that the family members are not present at the home. At step [612], the at least one action is identified as per the defined at least one rule to provide live streaming of the security cameras on the user device for remote monitoring of the activity. At step [614], the temperature of 31 degrees is detected in the room as a third IoT event. In an example, the temperature of 31 degrees may be detected by a temperature sensor. At step [616], the time of the event is determined as 2:00 P.M and the context of the event is identified as “user in-home, preferred temp-25” which means that the preferred temperature of the user is 25 degree Celsius. At step [618], the at least one action is identified as per the defined at least one rule to keep the temperature of the AC at 25 degree Celsius automatically when the user is present at home.
In a non-limiting embodiment, below mentioned table includes the IoT device, their attributes, capabilities, category and Social Context to better understand the invention.

Device Attributes Capabilities Category Social Context
Light status: live commands: Home Group device
attributes:
name: Light State
type: ENUM
values:
- 'off‘, 'on' 'off': arguments: [] 'on': arguments: [] Automation
Baby status: commands: Baby Group device
Monitoring online/offline “start Monitoring Events are of
Camera attributes: streaming': interest to baby
name: Crydetected type: ENUM values:
- 'off'
- 'on' arguments: [] 'on':
arguments: [] parents

Wearable attributes: commands: Fitness and Personal device
name: StepCount type: INT name: BP Value
type: INT name: Heart rate
type: INT “Alert users': arguments: []
“Notify doctor”':
arguments: [] Health

Device Attributes Capabilities Social Context
Speaker name: AudioPlat commands: Group device
status: live playTrack(uri,level):
attributes: { arguments:
type:STRING - name: uri
Name : Music file } type: STRING
Air name: Air Conditioner commands:
Conditioner Mode status: proposed setAirConditionerMode:
attributes: arguments:
airConditionerMode: - schema: HvacMode
schema: HvacMode type: ENUM
type: ENUM name: mode values: -
values: --auto -cool -dry auto , cool, dry
TV Control name: TVControl commands: setTvChannel:
proposed attributes: arguments: -
status: live type: STRING
attributes: { name: channel
type: STRING channelUp:
Name : Music file arguments: [ ]
} channelDown: arguments: [ ]
While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and

that many changes can be made in the preferred embodiments without departing from the principles of the invention. These and other changes in the preferred embodiments of the invention will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the invention and not as limitation.

We Claim:
1. A method [300] of automatically creating rules and actions for IoT
devices, the method comprising:
- receiving, at a device capability management unit [228], one or more capabilities of a plurality of IoT devices [202];
- correlating, by the device capability management unit [228], the one or more capabilities of the plurality of IoT devices [202];
- creating automatically, at a rule engine unit [222], at least one rule and at least one action for each of the plurality of IoT devices [202] based on the correlation of the one or more capabilities of the plurality of IoT devices [202], wherein the at least one action relates to the at least one rule;
- receiving, at an event processor unit [230], at least one event data from at least one of the plurality of IoT devices [202];
- processing, at the rule engine unit [222], the at least one event data to identify at least one rule and at least one appropriate action for the at least one of the plurality of IoT devices [202]; and
- executing, by a rule execution unit [206], the identified at least one rule and the at least one action on the at least one of the plurality of IoT devices [202].

2. The method as claimed in claim 1, further comprising: notifying, by the event processor unit [230], the identified at least one rule and the identified at least one action to the at least one of the plurality of IoT devices [202], wherein the at least one rule and the at least one action are executed after an acceptance of the identified at least one rule at the user device.
3. The method as claimed in claim 1, further comprising:

- receiving, at the rule engine unit [222], at least one device context data received from a device context unit [224]; and
- identifying, at the rule engine unit [222], the at least one rule and

the at least one appropriate action for the at least one of the plurality of IoT devices [202] based on the at least one device context data.
4. The method as claimed in claim 1, further comprising maintaining, at a
storage unit [232], a rule database and a context database, wherein
- the rule database comprises the at least one rule created for each of the plurality of IoT devices [202],
- the context database comprises the at least one device context data.

5. The method as claimed in claim 1, further comprising providing, by the rule engine unit [222], a score to the at least one rule created for each of the plurality of IoT devices [202], wherein the score of the rule is dynamically updated based on a number of times the at least one rule is executed at the plurality of IoT devices [202].
6. The method as claimed in claim 1, further comprising refining, at the event processor unit [230], the at least one event data to filter out the normalized events.
7. The method as claimed in claim 1, wherein the at least one rule is created by using an artificial intelligence based system, wherein the artificial intelligence based system facilitates in identifying the pattern used for the plurality of IoT devices [202] to create automatically the at least one rule and the at least one action.
8. A system [200] for automatically creating rules and actions for IoT devices, the system comprising:

- a device capability management unit [228] configured to receive one or more capabilities of a plurality of IoT devices [202]and to correlate the one or more capabilities of the plurality of IoT devices [202];
- a rule engine unit [222] connected to the device capability management unit [228], wherein the rule engine unit [222] is configured to create

automatically at least one rule and at least one action for each of the plurality of IoT devices [202] based on the correlation of the one or more capabilities of the plurality of IoT devices [202], wherein the at least one action relates to the at least one rule;
- an event processor unit [230] connected to the rule engine unit [222] and the device capability management unit [228], wherein the event processor unit [230] is configured to receive at least one event data from at least one of the plurality of IoT devices [202];
- wherein the rule engine unit [222] is configured to process the at least one event data to identify at least one rule and at least one appropriate action for the at least one of the plurality of IoT devices [202];
- a rule execution unit [206] connected to the event processor unit [230], the rule engine unit [222] and the device capability management unit [228], wherein the rule execution unit [206] is configured to execute the identified at least one rule and the at least one action on the at least one of the plurality of IoT devices [202].

9. The system [200] as claimed in claim 8, wherein the event processor unit [230] is further configured to notify the identified at least one rule and the identified at least one action to the at least one of the plurality of IoT devices [202], wherein the at least one rule and the at least one action are executed after an acceptance of the identified at least one rule at the user device.
10. The system [200] as claimed in claim 8, further comprises a device context unit [224] connected to the rule execution unit [206], the event processor unit [230], the rule engine unit [222] and the device capability management unit [228], wherein the device context unit [224] is configured to provide device context data, wherein the device context data is further involved in the identification of the at least one rule and the at least one appropriate action for the at least one of the plurality of

IoT devices [202].
11. The system [200] as claimed in claim 8, further comprises a storage unit [232] connected to the rule execution unit [206], the event processor unit [230], the rule engine unit [222] and the device capability management unit [228], wherein the storage unit [232] is configured to maintain a rule database and a context database, wherein the rule database comprises at least one rule created for each of the plurality of IoT devices [202] and the context database comprises the at least one device context data.
12. The system [200] as claimed in claim 8, wherein the rule engine unit [222] is further configured to provide a score to the at least one rule created for each of the plurality of IoT devices [202] and wherein the score of the at least one rule is dynamically updated based on a number of times the at least one rule is executed at the plurality of IoT devices [202].
13. The system [200] as claimed in claim 8, wherein the event processor unit [230] is further configured to refine the at least one event data to filter out the normalized events.
14. The system [200] as claimed in claim 8, wherein the rule engine unit [222] with an artificial intelligence based system facilitates in identifying the pattern used for the plurality of IoT devices [202] to create automatically the at least one rule and the at least one action.