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 ENABLING CONNECTION BETWEEN AN IoT CLOUD AND A PLURALITY OF IoT
SENSOR DEVICES”
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 disclosure relates generally to communication network in IoT based systems and more particularly to enable connection between an IoT cloud and a plurality of IoT sensor devices.
BACKGROUND OF THE INVENTION DISCLOSURE:
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.
Currently, with the advancement in licensed networks (for e.g. GMS, EDGE, HSPA, LTE) and unlicensed networks (Wi-Fi, UMA, DECT, Bluetooth, Zigbee, RFID) of various wireless technologies, the wireless network operators provide communication services to multiple user devices by sharing network resources available in both the licensed network and in the unlicensed network. However, in order to provide such services to the multiple user devices, fiber to home (i.e. FTTx) service plays a critical role.
A Gateway is a device that connects multiple user devices to a broadband delivery network provided by service operators which may be installed at Home/Office and would be called as Home/Office Gateway. As a part of the wireless service operators’ network, the home gateway supports remote control, detection and configuration of the multiple user devices. Also, the FTTx service is connected to the home gateway and provides high-speed internet (HSI), media applications and home voice services. Further, the home gateway provides wireless and wired multimedia services to the user. Furthermore, with internet-protocol networks capturing the market by offering IoT services to the multiple user devices and sensors, the current technologies are targeted toward a home

or an office environment where multiple user devices are connected to the home gateway to offer an internet-protocol multimedia service (IMS) IoT service.
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 things to connect and exchange data, creating opportunities for more direct integration of the physical world into computer-based systems, resulting in efficiency improvements, economic benefits, and reduced human exertions. The “Internet of things” (IoT) concept getting more and more popular, devices, such as sensors, actuators and everyday objects including the coffee makers, washing machines, headphones, lamps and wearable devices, etc. are 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 receive control signals over an IP network using the

standard Internet protocols such as TCP/IP which is being exclusively used on the Internet.
A smart home/enterprise hub (Hub) acts as the heart of a smart home/enterprise network, tying together various IoT devices/NB-IoT devices and systems in a centralized platform. The Hub collects and translates various protocol communications from smart devices. For example, if a smartphone, which does not use Zigbee to communicate, wants to "talk" with a smart lock, which only uses Zigbee, the smart home hub acts as a translator between the two. The Smart home hubs can control many smart home, NB-IoT and IoT-enabled devices and systems, including smart sensors on thermostats, light bulbs, outlets and switches, doorbells, garage door openers, energy monitors, door locks and sensors, and window treatments/coverings and sensors. The Hub can also control motion sensors, flood and leak sensors, smart radios and speakers, security systems and cameras, smoke and carbon monoxide detectors, irrigation controllers and fans, water heaters and other household appliances
The smartphone is an example of a smart mobility wireless cellular connectivity device that allows end-users to use services on 2G, 3G or 4G mobile broadband Internet connections with an advanced mobile operating system which combines features of a personal computer operating system with other features useful for mobile or handheld use. These smartphones can access the Internet, have a touchscreen user interface, can run third-party apps, music players and are camera phones possessing high-speed mobile broadband 4G LTE internet, hotspot functionality, motion sensors, mobile payment mechanisms and enhanced security features with alarm and alert in emergency situations. Mobility devices may include smartphones, wearable devices, smart-watches, smart bands, wearable augmented devices, etc. For the sake of specificity, we will refer to the mobility device to smartphones/user device in this disclosure but will not limit the scope of the disclosure and may extend to any mobility device in implementing the technical solutions.

Brief background of the different radio system in IoT devices:
The above IoT devices and other smart devices are connected through either LTE network, Wi-Fi network, or short-range frequency such as Zigbee, Zwave, BLE or any other such network.
In the current system, we have solutions such as smart home hub that acts as the heart of a smart home network, tying together various devices and systems in a centralized platform. The Hub collects and translates various protocol communications from smart home devices. For example, if a smartphone/user device, which does not use Zigbee to communicate, wants to "talk" with a smart lock, which only uses Zigbee, the smart home hub acts as a translator between the two. The Smart home hubs can control many smart home and NB-IoT/IoT-enabled devices and systems, including smart sensors on thermostats, light bulbs, outlets and switches, doorbells, garage door openers, energy monitors, door locks and sensors, and window treatments/coverings sensors. They can also control motion sensors, flood and leak sensors, smart radios and speakers, security systems and cameras, smoke and carbon monoxide detectors, irrigation controllers and fans, water heaters and other household appliances.
Zigbee Devices
ZigBee bus is responsible for communication with ZigBee module, low-level network operations and network management. The Bus can be divided into three main sub-modules: module responsible for sending ZigBee messages, module for receiving messages and module for processing messages. The modules communicate using two message queues one for incoming messages and one for outgoing messages.
Once the gateway start, ZigBee bus performs initialization of ZigBee module and starts ZigBee network as coordinator with trust center. ZigBee bus is configured to initially select one of four channels 11, 15, 20 or 25 based on measured channel quality. In addition, the bus configures transmit power of ZigBee module

by default to a value that is set to 0 dBm. ZigBee supports three types of devices:
• Preferred – The devices that are known to the system. The Gateway knows endpoint and cluster structure, even custom clusters. The preferred devices are recognized based on manufacturer and model information provided in a basic cluster.
• Un-preferred – Such devices that are not directly supported, but gateway support their endpoint device types and clusters. These devices are recognized on inclusion by inspecting their endpoints and associated clusters. Supported un-preferred ZigBee types can be seen in Table 1 below.
• Unknown – Such devices that are unknown to the system. The device gateway inspects endpoints and clusters and adds services only for supported functionalities.
Required clusters to be supported

Supported clusters
Basic Identify Group Scene
Poll Control On Off Level Control Color Control
Temperature Measurement Pressure Measurement Humidity
Measurement Simple Metering
Electrical Measurement IAS Zone IAS WD
Table 1: List of supported un-preferred ZigBee types
BLE Devices
The latest version of the Bluetooth standard, Bluetooth 5, is set to offer a wide range of enhancements such as longer range, higher speed and extended support for connectionless services. This is a significant upgrade over today’s Bluetooth 4.2 technology and will open new IoT applications for the smart

environment.
Bluetooth 5 Enhancements
x 2 increase in speed
x 4 increase in range
x 8 increase in broadcast message capacity
The Bluetooth® mesh networking specifications define requirements to enable an interoperable many-to-many (m:m) mesh networking solution for Bluetooth Low Energy (LE) wireless technology-ideally suited for large-scale device networks to support building automation, sensor networks, asset tracking and other solutions where multiple devices need to communicate reliably and securely.
Mesh Profile: Defines fundamental requirements to enable an interoperable mesh networking solution for Bluetooth LE wireless technology.
Mesh Model: Introduces models, used to define basic functionality of nodes on a mesh network.
Mesh Device Properties: Defines device properties required for the Mesh Model specification.
A mesh network has a many-to-many topology, with each device able to communicate with every other device in the mesh. The communication is achieved using messages, and devices can relay messages to other devices so that the end-to-end communication range is extended far beyond the radio range of each individual numbers.
Z-Wave Devices
As the smart home's popularity explodes, more and more connected devices are being added to people's houses. A lot of these devices - sensors, lightbulbs,

heating controls, locks, plugs and the like - pack in Z-Wave to talk to each other. A much lower power alternative compared to Wi-Fi, but with a much bigger range than Bluetooth, Z-Wave operates using low-energy radio waves to communicate from device to device.
Unlike Wi-Fi, where devices must connect to a central hub (usually a router, or another access point), Z-Wave devices all link up together to form a mesh network. There's usually one central hub that does connect to the internet but the devices themselves - sensors, bulbs and so on - don't have Wi-Fi at all, they just use Z-Wave connectivity to talk to the hub, and that connectivity doesn't have to be direct; the mesh network means signals can hop from device to device.
The latest Z-Wave platform -700 series boasts a range of 100m for point-to-point contact and operates at such low power that some sensors will last 10 years on just a coin cell.
The Z-Wave system has three layers; radio, network and an application layer. These three layers work together to create a robust and reliable network that enables numerous nodes and devices to communicate with each other simultaneously. In Z-Wave terminology controlling devices are called controllers, reporting devices are called sensors and controlled devices are called actuators.
Controllers - devices that control other Z-Wave devices
• Remote Controls - universal remote control (with IR) or dedicated Z-Wave Remote Control with special keys for network functions, group and/or scene control
• USB sticks and IP gateways to allow PC software to access Z-Wave networks. Gateways also allow remote access via the internet
Sensors - devices that report information by sending a digital or analogue signal
• Analogue Sensors - measure parameters like temperature, humidity

and gas concentration
• Digital Sensors - door/glass breaking, motion detector and flood
warning
Actuators - Devices that switch digital (on/off for an electrical switch) or analogue signals (0 % ... 100 % for a dimmer or blind control)
• Electrical Switches - plug-in modules for wall outlets or direct replacements for traditional wall switches (digital)
• Electrical Dimmers - plug-in modules or replacements for traditional wall switches/dimmers (analogue)
However, the smart Hub in the current form translates various protocol communications from various smart devices, but it does not provide seamless user experience connecting all types of radio networks as above. The current IoT smart home Hub is independent and does not connect to all types of radio network. The current smart home deployments rely on dedicated IoT hub device which is expensive and is tied to the vendor with their own devices.
Further, the current system has the following limitations:
Current solution is proprietary Smart Hub with no solution that is convenient for seamless connectivity relating to various radios.
No solution that supports multiple radio connectivity modes-Zigbee/Z-Wave/ BLE/Thread X/etc.
Expensive smart Hubs which is difficult to connect with all devices on different radios.
Complex deployment for smart home/office with IoT devices with different radios.
Therefore in view of these limitations, there arises an imperative need in the art to overcome the limitations of prior existing solutions and to provide an

inexpensive solution to enable the connection between an IoT cloud and a plurality of IoT sensor 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 an inexpensive method and system that works along with the existing system and that can be connected to any device with the existing functionality and behaviour.
It is also an object of the invention to provide a way out to bypass the existing IoT hub and to provide a bridge to connect to various sensors connected over multiple radios. One more object of the present invention is to provide millions of customers a solution that will support various radio connectivity modes-Zigbee/Z-Wave/ BLE/Thread X/etc.
Also, an object of the present invention is to provide a versatile system that will provide an inexpensive solution to connect with all devices on different radios. The present invention provides setup and simple deployment for smart home/office with IoT devices with different radios. Also, the present invention eliminates the need for an additional hardware in the form of IoT hub. Furthermore, the present invention provides an easy alternative to the existing systems wherein a lot of extra wiring is required to provide the IoT connectivity.
Another object of the present invention is it provides mesh technology experience with cable facilitating mesh architecture. Yet another object of the present invention is to provide easy installation without the need for any

specialized trained technicians or experts for the installations wherein the solution is very easy to install.
In order to achieve the aforementioned objectives, the present disclosure provides a method and system of enabling a connection between an IoT cloud and a plurality of IoT sensor devices.
One aspect of the present invention relates to a method of enabling the connection between an IoT cloud and a plurality of IoT sensor devices. The method comprises establishing via a mesh adaptor, a connection with a plurality of IoT sensor devices, wherein the mesh adaptor comprising a plurality of connectivity modules associated with a unique connectivity mode and said connection is based on the unique connectivity mode of said connectivity module. Next, the method encompasses establishing via a processing unit a connection between said mesh adapter and a router. Thereafter the method comprises enabling via said processing unit, the router to establish a connection between said IoT cloud and said plurality of IoT sensor devices via said router.
Another aspect of the present invention relates to a system of enabling the connection between an IoT cloud and a plurality of IoT sensor devices. The system comprises at least one router configured to established connectivity between said IoT cloud and said plurality of IoT sensor devices. Further, the system comprises at least one system-on-a-chip connected to said at least one router and the system-on-a-chip further comprising a mesh adapter comprising a plurality of connectivity modules, wherein each of said connectivity modules being associated with a unique connectivity mode. Also, each of the connectivity modules are configured to establish a connection with the plurality of IoT sensor devices based on the unique connectivity mode of said connectivity modules. Thereafter the system-on-a-chip also comprises a processing unit connected to said mesh adapter, wherein the processing unit is configured to establish a connection between said mesh adapter and said at least one router, and to

enable, said at least one router, to establish a connection between said IoT cloud and said plurality of IoT sensor devices. Also, the system comprises at least one user device connected to said system-on-a-chip via said IoT cloud, wherein the user device is configured to control said plurality of IoT sensor devices via said established connectivity between said IoT cloud and said plurality of IoT sensor devices.
Yet another aspect of the present invention relates to a system-on-a-chip for enabling connection between an IoT cloud and a plurality of IoT sensor devices. The system-on-a-chip comprises at least one mesh adaptor comprising a plurality of connectivity modules, wherein each of said connectivity modules being associated with a unique connectivity mode and each of the connectivity modules are configured to establish a connection with the plurality of IoT sensor devices based on the unique connectivity mode of said connectivity modules. Also, the system-on-a-chip further comprises a processing unit connected to said mesh adapter, wherein the processing unit is configured to establish a connection between said mesh adapter and a router and to enable, said router, to establish a connection between said IoT cloud and said plurality of IoT sensor devices.
BRIEF DESCRIPTION OF DRAWINGS:
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 a system on a chip [100], in accordance with exemplary embodiments of the present disclosure.
FIG.2 illustrates a block diagram of a system [200], in accordance with exemplary embodiments of the present disclosure.
FIG. 3 illustrates an exemplary method flow diagram [300] depicting a method for enabling connection between an IoT cloud and a plurality of IoT sensor devices, in accordance with exemplary embodiments of the present disclosure.
FIG. 4 illustrates an exemplary flowchart illustrating the process of sending control commands via a user device, in accordance with exemplary embodiments of the present disclosure.
FIG. 5 illustrates an exemplary flowchart illustrating the process of sending call notifications via a system-on-a-chip, in accordance with exemplary embodiments of the present disclosure.
FIG. 6 illustrates an exemplary sequence diagram illustrating an IoT device discovery, in accordance with exemplary embodiments of the present disclosure.
FIG. 7 illustrates an exemplary sequence diagram illustrating an IoT device provisioning, in accordance with exemplary embodiments of the present disclosure.
FIG. 8 illustrates an exemplary sequence diagram illustrating a user device control and notification, 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 present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
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.
Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks.
Systems depicted in some of the figures may be provided in various configurations. In some embodiments, the systems may be configured as a distributed system where one or more components of the system are distributed across one or more networks in a cloud computing system.
As used herein, the “IoT sensor device” or “NB-IoT sensor device” or "NB LTE -IoT Device“, refers to any electrical, electronic, electromechanical and computing device. The IoT sensor device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other IoT sensor devices as well as non-IoT sensor devices and transmitting and/or receiving data from these devices. The IoT sensor device may have a processor, a display, a memory, a battery and an input means such as a hard keypad and/or a soft keypad. The at least one IoT sensor device may include, but is 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. The IoT sensor devices may be capable of operating on any radio access technology including but not limited to IP-enabled communication, ZigBee, Bluetooth,

Bluetooth Low Energy (BLE), Near Field Communication, Z-Wave, Thread-X 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, “memory unit”, “storage unit” and/or “memory” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
Referring to FIG. 1, that illustrates an exemplary block diagram of a system-on-a-chip [100], in accordance with exemplary embodiments of the present disclosure. As shown in Fig. 1, the system-on-a-chip [100] comprises at least one mesh adapter [104], at least one processing unit [108] and at least one storage unit [110], wherein all said components being connected to each other. The mesh adaptor [104] further comprises plurality of connectivity modules [106(A)], [106(B)], [106(C)]….. [106(N)] (Collectively referred to as connectivity module [106]), further each connectivity module connected to an antenna [112(A)], [112(B)], [112(C)]….. [112(N)] (Collectively referred to as antenna [112]).
The mesh adaptor [104] of said system-on-a-chip [100] is coupled to the

processing unit [108] and the storage unit [110]. The mesh adaptor [104] comprising connectivity module [106], wherein each of said connectivity modules [106] being associated with a unique connectivity mode. The connectivity module [106] includes but not limited to one of a Zigbee module, BLE module, Zwave module, Thread X module and such similar modules. Also, said connectivity module [106] is coupled to the antenna [112] to further support said unique connectivity mode. The unique connectivity mode is a unique radio connectivity mode and said unique connectivity mode includes but not limited to, one of a BLE mode, Zigbee mode, Zwave mode, Thread X mode and any such similar mode. Thereafter the each of the connectivity modules [106] are configured to establish a connection with a plurality of IoT sensor devices [202] based on the unique connectivity mode of said connectivity modules [106].
The processing unit [108] of said system-on-a-chip is coupled to the mesh adaptor [104]. The processing unit [108] is configured to establish a connection between said mesh adapter [104] and a router, and also to enable, said router, to establish a connection between said IoT cloud and said plurality of IoT sensor devices. The router is one of a wired and a wireless connectivity router.
Also, via said connections between said components of said system-on-a-chip, the system-on-a-chip is also configured to enable multiple unique connections between said IoT cloud and said plurality of IoT sensor devices via said router, based on said multiple unique connectivity modes.
In an instance, if said plurality of IoT sensor devices encompasses multiple IoT sensor devices operating on BLE, multiple IoT sensor devices operating on Zigbee and multiple IoT sensor devices operating on any such similar connectivity mode, in said instance, the system-on-a-chip, via said router, enables multiple unique connections between the IoT cloud and the IoT sensor devices operating on said BLE, Zigbee and any such similar connectivity mode. Also, the multiple unique

connections are based on multiple unique connectivity modes associated with the connectivity module [106], such as in said instance the multiple unique connectivity modes based on said BLE, Zigbee and any such similar connectivity mode.
Furthermore, the system-on-a-chip on the basis of said connectivity between said IoT cloud and said plurality of IoT sensor devices further enables at least one user device connected to said system-on-a-chip via said IoT cloud, to control said plurality of IoT sensor devices. In an instance the user device may be connected to the router via said IoT cloud and thereafter the connectivity between the user device and the system-on-a-chip is provided via said router. Also, in an instance, the said plurality of IoT sensor devices may be controlled via a remote device connected via said IoT cloud or via a local user device connected via said router.
Also, the plurality of IoT sensor devices includes but not limited to a plurality of NB-IoT sensor devices and the connectivity between said IoT cloud and said plurality of NB-IoT sensor devices encompasses a connectivity over at least one NB-IoT channel. In an instance, the plurality of NB-IoT sensor devices may be the NB-LTE IoT sensor devices and the connectivity between said IoT cloud and said plurality of NB-LTE IoT sensor devices comprises a connectivity over at least one NB-LTE IoT channel.
Furthermore, in an instance, in order to enable a connection between an IoT cloud and one or more IoT sensor device, the system-on-a-chip firstly identifies the IoT sensor devices and the connectivity modes associated with said IoT sensor devices. Thereafter the system-on-a-chip connects to the IoT sensor devices using a pairing process by using an authentication code to ensure the chosen IoT sensor devices are the correct one. Thereafter the system-on-a-chip identifies a router configured to provide connectivity between said IoT sensor device and the IoT cloud. Further after said determination, the system-on-a-chip, via a processing unit [108], enables said router, to establish a connection

between said IoT cloud and said IoT sensor devices.
Next, a connectivity between a user device connected to said router via IoT cloud and the IoT sensor device is provided to enable an exchange of data thereby allowing the user to control the IoT sensor device through the system-on-a-chip as one-point solutions for hybrid type of IoT sensor devices. In an instance said connectivity between the user device and the IoT sensor device is followed by an authentication process and also in one more instance the user device may be locally connected to the router.
Referring to FIG. 2, the present invention illustrates an exemplary block diagram of a system [200], in accordance with exemplary embodiments of the present disclosure. As shown in the Fig. 2, the system comprises a plurality of IoT sensor devices [202(A)], [202(B)], [202(C)]….. [202(N)] (Collectively referred to as IoT sensor device/s [202]), at least one system-on-a-chip [102], at least one router [204], at least one IoT cloud [206] and at least one user device [208], wherein all the components of said system are interconnected with each other. Also, the system-on-a-chip [102] further comprises at least one mesh adaptor [104], at least one storage unit [110] and at least one processing unit [108]. The mesh adaptor [104] further comprising a plurality of connectivity modules [106], wherein each connectivity module [106] is coupled to an antenna [112]. The components of the system-on-a-chip are interconnected with each other and some of the interconnections and components are not shown in the Figures for the sake of clarity. Also, only a few components and/or units are shown in the figures for the sake of clarity, however, there may be multiple such components and/or units with multiple interconnections or in an instance for a particular implementation there may be as many components/units and interconnections in said system, as obvious to a person skilled in the art.
The router [204] is coupled to the user device [208] via the IoT cloud [206], wherein the said router is one of a wired and a wireless connectivity router. The

router [204] is configured to establish connectivity between said IoT cloud [206] and said plurality of IoT sensor devices [202].
The system-on-a-chip [100], is coupled to the router [204] and the IoT sensor device [202]. The system-on-a-chip [100] comprises at least one mesh adapter [104], at least one processing unit [108] and at least one storage unit [110]. The mesh adaptor [104] further comprises a plurality of connectivity modules [106] and further each connectivity module [106] is connected to an antenna [112]. All the components of the system-on-a-chip are interconnected with each other.
The mesh adaptor [104] of the system-on-a-chip [100], via the connectivity module [106], establishes a connection with the IoT sensor device [202], based on a unique connectivity mode associated with said each connectivity module [106]. The connectivity module [106] includes but not limited to one of a Zigbee module, BLE module, Zwave module, Thread X module and such similar modules. Also, said connectivity module [106] is coupled to the antenna [112] to further support said unique connectivity mode. The unique connectivity mode is a unique radio connectivity mode and said unique connectivity mode includes but not limited to, one of a BLE mode, Zigbee mode, Zwave mode, Thread X mode and any such similar radio connectivity mode.
Further, the processing unit [108] of said system-on-a-chip [100] establishes a connection between said mesh adapter [104] and the router [204]. Also, the processing unit [108], enables said router [204], to establish a connection between said IoT cloud [206] and said plurality of IoT sensor devices [202].
The system-on-a-chip [100] is also configured to enable multiple unique connections between said IoT cloud [206] and said plurality of IoT sensor devices [202] via said router [206], based on said multiple unique connectivity modes associated with the mesh adaptor [104].
In an instance, if said plurality of IoT sensor devices [202] encompasses multiple IoT sensor devices operating on thread X and multiple IoT sensor devices

operating on Z-Wave, the system-on-a-chip [100], via said router [204], enables multiple unique connections between the IoT cloud [206] and the IoT sensor devices [202] operating on said thread X and Z-wave. Also, the multiple unique connections are based on multiple unique connectivity modes associated with the mesh adapter [104], such as in said instance the multiple unique connectivity modes are based on said thread X and Z-wave connectivity modes associated with the mesh adapter [104].
The user device [208] is coupled to the router [204] via the IoT cloud [206]. Also, the user device [208], via the router [204], is further coupled to the system-on-a-chip [100]. The user device [208] is configured to control said plurality of IoT sensor devices [202] via said established connectivity between said IoT cloud [206] and said plurality of IoT sensor devices [202].
As used herein, the “user device” is a ‘smart computing device’ refers to any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices. Smart computing devices may include, but not limited to, a mobile phone, smartphone, pager, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device as may be obvious to a person skilled in the art. In general, a smart computing device is a digital, user-configured, computer networked device that can operate autonomously. A smart computing device is one of the appropriate systems for storing data and other information.
Furthermore, in an instance, the user device [208] may be locally coupled to the router [204] and the said plurality of IoT sensor devices [202] may be controlled via said local user device connected to router [204].
Also, the plurality of IoT sensor devices includes but not limited to plurality of NB-IoT sensor devices and the connectivity between said IoT cloud and said plurality of NB-IoT sensor devices encompasses a connectivity over at least one NB-IoT channel. In an instance, the plurality of NB-IoT sensor devices may be the

NB-LTE IoT sensor devices and the connectivity between said IoT cloud and said plurality of NB-LTE IoT sensor devices comprises a connectivity over at least one NB-LTE IoT channel.
Further, in an instance, in order to enable a connection between an IoT cloud [206] and two IoT motion sensor devices [202] each operating on different radio connectivity’s i.e. on a Zigbee and a BLE connectivity respectively, the system-on-a-chip [100] of the system [200], identifies the IoT motion sensor devices [202] and the radio connectivity i.e. the Zigbee and BLE connectivity, to which the IoT motion sensor devices [202] are associated with. Thereafter, the system-on-a-chip [100] connects to the IoT motion sensor devices [202] using a pairing process by using an authentication code. The said connections between the system-on-a-chip [100] and the IoT motion sensor devices [202] are based on two unique connectivity modes associated with two connectivity modules [106] of a mesh adapter [104] of the system-on-a-chip [100]. Also, in the said instance, the said unique connectivity modes are the Zigbee and BLE connectivity modes, corresponding to the Zigbee and BLE connectivity of said IoT motion sensor devices [202] respectively.
Also, the system-on-a-chip [100] further identifies a router [206] configured to provide connectivity between said IoT motion sensor device [202] and the IoT cloud [206]. Further after said determination, the system-on-a-chip [100], via a processing unit [108], enables said router [204], to establish a connection between said IoT cloud [206] and said IoT motion sensor devices [202].
Further, in the said instance, a connectivity between a user device [208] connected to said router [204] via IoT cloud [206] and the IoT motion sensor devices [202] is provided, to enable exchange of data thereby allowing the user to control the IoT motion sensor devices [202], through the system-on-a-chip [100] as one-point solutions for hybrid type of IoT motion sensor devices [202]. In an instance said connectivity between the user device IoT sensor device and

the IoT sensor device is followed by an authentication process.
Also, considering an exemplary use case, if an IoT motion sensor device [202] is implemented in a room along with an IoT switch [202], and as soon as the IoT motion sensor device [202] identifies a motion of a person in the room, a notification comprising the details of said movement is then passed to the system-on-a-chip [100], based on a connectivity established via the processing unit [108], between said IoT motion sensor device [202] and the system-on-a-chip [100]. Thereafter, the said information is then passed to a router [204], connected to the system-on-a-chip [100] and also, the system-on-a-chip [100], via a processing unit [108], enables said router [204], to establish a connection between said IoT cloud [206] and said IoT motion sensor device [202]. Further, the said information is then passed to a user device [208], via said IoT cloud [206], thereby allowing the user to control the IoT switch [202], based on the received information relating to the movement of the person in said room. Also, based on the users input the IoT switch [202] can be turned on/off, through the transmission of the user’s command to the IoT switch [202] via said IoT cloud [206], router [204] and system-on-a-chip [100].
Referring to Fig. 3, the present invention illustrates an exemplary method flow diagram [300] depicting a method for enabling connection between an IoT cloud and a plurality of IoT sensor devices, in accordance with exemplary embodiments of the present disclosure. The method begins at step [302].
The method at step [304] comprises, establishing via a mesh adaptor [104], a connection with plurality of IoT sensor devices [202], wherein the mesh adaptor comprising a plurality of connectivity modules [106], associated with a unique connectivity mode, and said connection is based on the unique connectivity mode of said connectivity module. The connectivity module [106] includes but not limited to one of a Zigbee module, BLE module, Zwave module, Thread X module and such similar modules. Also, said connectivity module [106] is

coupled to the antenna [112] to further support said unique connectivity mode. The unique connectivity mode is a unique radio connectivity mode and said unique connectivity mode includes but not limited to, one of a BLE mode, Zigbee mode, Zwave mode, Thread X mode and any such similar mode. Thereafter the each of the connectivity modules [106] are configured to establish a connection with a plurality of IoT sensor devices [202] based on the unique connectivity mode of said connectivity modules [106].
Next, the method at step [306] comprises, establishing via a processing unit [108], a connection between said mesh adapter [104] and a router [204]. The router [204] is one of a wired router and a wireless router.
Thereafter, the method at step [308] comprises, enabling via said processing unit [108], the router [204], to establish a connection between said IoT cloud [206] and said plurality of IoT sensor devices [202] via said router [204].
Furthermore, via the connections between said components of said system-on-a-chip [100], the system-on-a-chip [100] is also configured to enable multiple unique connections between said IoT cloud [206] and said plurality of IoT sensor devices [202] via said router [206], based on said multiple unique connectivity modes.
In an instance, if the plurality of IoT sensor devices [202] encompasses multiple IoT sensor devices operating different connectivity modes. In said instance, the system-on-a-chip [100], via said router [204], enables multiple unique connections between the IoT cloud [206] and the IoT sensor devices [202] operating on different radio connectivity. Also, the multiple unique connections are based on multiple unique connectivity modes associated with the connectivity modules [106] of the mesh adaptor [104] of the system-on-a-chip [100]. Also said multiple unique connectivity modes are corresponding to the radio connectivity on which the IoT sensor devices [202] are operating on.
Also, the system-on-a-chip [100], on the basis of said connectivity between said

IoT cloud [206] and said plurality of IoT sensor devices [202] further enables at least one user device [208] connected to said system-on-a-chip [100] via said IoT cloud [206], to control said plurality of IoT sensor devices [202]. In an instance the user device [208] may be connected to the router [204] via said IoT cloud [206] and thereafter the connectivity between the user device [208] and the system-on-a-chip [100] is provided via said router [204]. Also, in an instance the said plurality of IoT sensor devices [202] may be controlled via a remote device connected via said IoT cloud [206].
Furthermore, the plurality of IoT sensor devices [202] includes but not limited to plurality of NB-IoT sensor devices and the connectivity between said IoT cloud [206] and said plurality of NB-IoT sensor devices [202] encompasses a connectivity over at least one NB-IoT channel. In an instance, the plurality of NB-IoT sensor devices may be the NB-LTE IoT sensor devices and the connectivity between said IoT cloud and said plurality of NB-LTE IoT sensor devices comprises a connectivity over at least one NB-LTE IoT channel.
Furthermore, in an instance, in order to enable a connection between an IoT cloud [206] and a IoT temperature sensor device [202] operating on Z-wave connectivity, the system-on-a-chip [100] of the system [200], identifies the IoT light sensor device [202] and the radio connectivity i.e. the Z-Wave connectivity, the IoT light sensor device [202], associated with. Thereafter, the system-on-a-chip [100] connects to the IoT light sensor device [202] using a pairing process by using an authentication code. The said connection between the system-on-a-chip [100] and the IoT light devices [202] is based on a unique connectivity mode associated with a connectivity module [106] of a mesh adapter [104] of the system-on-a-chip [100]. Also, in the said instance, the said unique connectivity mode is the Z-Wave connectivity mode, corresponding to the Z-Wave connectivity of said IoT light sensor device [202].
Also, the system-on-a-chip [100] further identifies a router [206] configured to

provide connectivity between said IoT light sensor device [202] and the IoT cloud [206]. Further after said determination, the system-on-a-chip [100], via a processing unit [108], enables said router [204], to establish a connection between said IoT cloud [206] and said IoT light sensor device [202].
Further, in the said instance, a connectivity between a user device [208] connected to said router [204] via IoT cloud [206] and the IoT light sensor devices [202] is provided, to enable exchange of data thereby allowing the user to control the IoT light sensor device [202], through the system-on-a-chip [100]. In an instance said connectivity between the user device [208] and the IoT sensor device [202] is followed by an authentication process.
Furthermore, in an instance, one or more IoT motion sensors [202] may be implemented in a virtual reality (VR) environment. Also, in said instance, the VR environment may comprise a cricket bat, a virtual cricket ball and a user device [208]. Next, if the IoT motion sensor device [202] is implemented in the cricket bat, the said IoT motion sensor device [202] will capture the movement related to the cricket bat. Also, as soon as the IoT motion sensor device [202] identifies a motion of the bat, a notification comprising the details of said movement of the bat is then passed to the system-on-a-chip [100], via a connectivity link based on the connectivity mode associated with the system-on-a-chip [100] and the IoT motion sensor device [202]. The connectivity link between said IoT motion sensor device [202] and the system-on-a-chip [100] is established via the processing unit [108]. Thereafter, the said information is then passed to a router [204], connected to the system-on-a-chip [100] and also, further, the system-on-a-chip [100], via a processing unit [108], enables said router [204], to establish a connection between said IoT cloud [206] and said IoT motion sensor device [202].
Further, the said information is then passed to the user device [208], via said IoT cloud [206], thereby allowing the user to control the movement of the cricket

bat and/or the cricket ball, based on the received information relating to the movement of the bat.
Referring to Fig. 4 of the present invention, the FIG. 4 illustrates an exemplary flowchart illustrating the process of sending control commands via a user device, in accordance with exemplary embodiments of the present disclosure.
At step [402], the process encompasses initiating an IoT subscription via a router [204], wherein the IoT subscription enables the router [204] to establish a connection between an IoT cloud [206] and one or more IoT sensor devices [202].
Next, at step [404], the process leads to sending at least one control command from the said user device [208], to control said one or more IoT sensor devices [202]. Further in an instance, when a user device [208] transmits control commands to one or more IoT sensor devices [202], the said commands are transmitted via a system-on-a-chip [100]. The system-on-a-chip [100] further translates said commands to the IoT sensor device [202].
Thereafter, at step [406], the process comprises verification of the IoT sensor device, via the router [204].
Further, after successful verification, the process leads to step [408], and at step [408] the router [204] determines whether the IoT sensor device is online or not. Next, at step [410], the online status of the IoT sensor device [202] is confirmed and the process further leads to step [412].
At step [412] the router [204] sends a command to a system-on-a-chip [100], wherein the command comprising the at least one control command received from the said user device [208].
Lastly, the IoT sensor device [202], based on said at least one control command received from the said user device [208], triggers an attribute change. For instance, if the IoT sensor device [202] is an IoT switch, then triggers an attribute

change to switch on or switch off.
Referring to Fig. 5 of the present invention, the FIG. 5 illustrates an exemplary flowchart illustrating the process of sending call notifications via a system-on-a-chip, in accordance with exemplary embodiments of the present disclosure.
At step [502], the process comprises triggering an event notification to a system-on-a-chip [100] via an IoT Sensor Device [202]. For instance, the notification triggered via an IoT temperature sensor device [202], with respect to a change in the weather, to turn on/off an air conditioner.
Next, at step [504], the system-on-a-chip [100], transmits said received event notification to a router [204]. Also, at step [506], the system-on-a-chip [100], transmits said received event notification to an IoT Cloud [206], via said router [204].
Thereafter, at step [508] the IoT cloud [206] notifies the user device [208], the said information received via the event notification. For instance, an increase in the environment temperature.
Next, at step [510], the process further checks for a pre-defined rule relating to the information received via said event notification. For instance, if there is an increase in the environment temperature then turn on the air conditioner and if there is a decrease in the environment temperature then turn off the air conditioner.
Next, at step [512], said rule is identified. As per the given instance, the rule to turn on the air conditioner is identified as the information received via the event notification comprises an indication of an increase in the environment temperature.
Lastly, at step [514], the IoT sensor device [202], triggers an action corresponding to the rule, i.e. with respect to the above instance, the IoT sensor device [202] turns on the air conditioner.

Referring to Fig. 6 of the present invention, the FIG. 6 illustrates an exemplary sequence diagram illustrating an IoT device discovery, in accordance with exemplary embodiments of the present disclosure.
At step [602], the user device [208], transmits a device discovery command to the router [204]. The said device discovery command is transmitted to identify at least one IoT sensor device [202] in order to establish a connection between an IoT cloud [206] and one or more IoT sensor devices [202] via said router [204].
Next, at step [604], the router [204] further transmits said device discovery command to the system-on-a-chip [100] and thereafter at step [606] the system-on-a-chip [100] identifies the IoT sensor devices [202].
Thereafter, at step [608] a list of IoT sensor devices [202] is received at the system-on-a-chip [100]. Further, the said list is stored at the storage unit [110] and the list further comprises the details relating to the identified IoT sensor devices [202], including but not limited to the radio-connectivity/connectivity mode associated with the identified IoT sensor devices [202].
Next, at step [610], the said list is then passed to the router [204] via said system-on-a-chip [100]. The router lastly at step [612], provides said list of identified IoT sensor devices [202] to the user device [208].
Furthermore, in an instance the IoT device discovery of BLE associated - IoT sensor devices [202] is achieved via BLE GATT discovery procedures. In the said instance, a beacon device sends out a BLE advertisement consisting of a unique ID for that beacon with pre-configured service characteristics and if the user device [208] has Bluetooth turned on, it will receive nearby BLE advertisement. The system-on-a-chip [100] recognizes the ID of a beacon and can trigger a notification to user device [208] via router [204].
Also, in one other instance, the IoT device discovery of Zigbee - associated IoT sensor devices [202] follows the standard commissioning methods. The user taps

a button on the IoT sensor device [202] to activate a pairing mode. A command is then issued to the system-on-a-chip [100], via the router [204] to open up Zigbee connectivity mode to accept incoming pairing requests. The router [204] accepts incoming joining request from the IoT sensor device [202] after successful handshake. The system-on-a-chip [100] follows the touch commissioning procedures as defined in Zigbee specification for pairing with the Zigbee IoT sensor devices [202]. The system-on-a-chip [100] further issues commands to perform various operations from the Zigbee end nodes.
Similarly, in other instances, the IoT sensor device discovery for IoT sensor devices associated with other connectivity modes including but not limited to Z-wave/IEEE 802.15.4 may be achieved using standards discovery procedures.
Referring to Fig. 7 of the present invention, the FIG. 7 illustrates an exemplary sequence diagram illustrating an IoT device provisioning, in accordance with exemplary embodiments of the present disclosure.
At step [702], the user device [208], receives from the router [204], a list comprising the details of the identified IoT sensor devices [202].
Next, at step [704], the user device [208] selects the IoT sensor device to provision, wherein the said selection is made from the received list of identified IoT sensor devices [202].
Thereafter, at step [706] the router [204] further transmits a provision sensor indication to the system-on-a-chip [100].
Next, at step [708], the system-on-a-chip [100] transmits an IoT Sensor Device Pair command to the IoT sensor device [202]. After receiving said IoT Sensor Device Pair command, the IoT sensor device [202] at step [710] transmits a pairing successful indication to the system-on-a-chip [100].
Further upon receipt of said pairing successful indication the system-on-a-chip [100] at step [712] transmits a provisioning response to the router [204].

Lastly, the router [204], at step [714] transmits to the user device [208], a success/failure response corresponding to the received provisioning response.
Furthermore, in an instance, the provisioning of the IoT sensor device [202] is achieved via an authentication process. The system-on-a-chip [100] receives at least one IoT sensor device [202] authentication details and transmits the IoT sensor device [202] registration request to the IoT cloud [206]. The IoT cloud [206] validates the user device [208] and the IoT sensor device details and creates user to the IoT sensor device association on the IoT cloud [206]. The IoT sensor device [202] is then registered against a user account, therefore authorizing the user device [208] to control the IoT sensor device [202] and to receive notifications from the IoT sensor device [202] in both local and remote modes.
Referring to Fig. 8 of the present invention, the FIG. 8 illustrates an exemplary sequence diagram illustrating a user device control and notification, in accordance with exemplary embodiments of the present disclosure.
At step [802], the user device [208] sends a control command to the router [204], to control said one or more IoT sensor devices [202].
The router [204], at step [804], further transmits said control command to the system-on-a-chip [100].
Next, at step [806], the system-on-a-chip [100] transmits a switch on sensor command to the IoT sensor device [202], wherein the switch on sensor command is corresponding to the received control command from the user device [208].
Next, at step [808], the IoT sensor device [202] notifies the sensor change to the system-on-a-chip [100]. The said change is based on the received switch on sensor command.
Also, at step [808] an example of motion detected event is indicated, wherein

the said motion detection further leads to the change in the sensor. For instance, a change in the motion may lead to the change in the state of an IoT sensor device [202], for example changing to a switch-on state from a switch-off state.
Next, at step [810] a notification of said sensor change is then transmitted from said system-on-a-chip [100] to the router [204].
Lastly, the router [204], at step [812] further transmits said notification of said sensor change to the user device [208].
Furthermore, in an instance, the IoT sensor devices [202] associated with different connectivity modes can be controlled over the local transports. For instance, the Zigbee/BLE IoT sensor devices can be controlled over the local Zigbee/BLE transport. The Zigbee IoT sensor device control follows the Zigbee cluster definition and the BLE IoT sensor device control follows GATT control flow.
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 a limitation.

We Claim:
1. A system-on-a-chip for enabling a connection between an IoT cloud and a
plurality of IoT sensor devices comprising:
- at least one mesh adaptor comprising a plurality of connectivity modules, wherein,
each of said connectivity modules being associated with a unique connectivity mode, and
each of the connectivity modules are configured to establish a connection with the plurality of IoT sensor devices based on the unique connectivity mode of said connectivity modules; - a processing unit connected to said mesh adapter, wherein the processing unit is configured to:
establish a connection between said mesh adapter and a router;
and
enable, said router, to establish a connection between said IoT
cloud and said plurality of IoT sensor devices.
2. The system-on-a-chip as claimed in claim 1, wherein the connectivity between said IoT cloud and said plurality of IoT sensor devices further enables at least one user device connected to said system-on-a-chip via said IoT cloud, to control said plurality of IoT sensor devices.
3. The system-on-a-chip as claimed in claim 1, wherein the connectivity modules comprises one of a Zigbee module, BLE module, Zwave module and Thread X module.
4. The system-on-a-chip as claimed in claim 1, wherein the unique connectivity mode is one of a BLE mode, Zigbee mode, Zwave mode and Thread X mode.
5. The system-on-a-chip as claimed in claim 1, wherein the router is one of a wired and a wireless router.
6. The system-on-a-chip as claimed in claim 1, wherein the system on chip is

further configured to enable multiple unique connections between said IoT cloud and said plurality of IoT sensor devices via said router, wherein the multiple unique connections are based on said multiple unique connectivity modes.
7. The system-on-a-chip as claimed in claim 1, wherein the plurality of IoT sensor devices comprises plurality of NB-IoT sensor devices.
8. The system-on-a-chip as claimed in claim 1, wherein the connectivity between said IoT cloud and said plurality of NB-IoT sensor devices comprises a connectivity over at least one NB-IoT channel.
9. A method for enabling a connection between an IoT cloud and a plurality of IoT sensor devices, the method comprises:

- establishing via a mesh adaptor, a connection with a plurality of IoT sensor devices, wherein the mesh adaptor comprising a plurality of connectivity modules associated with a unique connectivity mode, and said connection is based on the unique connectivity mode of said connectivity module;
- establishing via a processing unit a connection between said mesh adapter and a router, and
- enabling via said processing unit, the router to establish a connection between said IoT cloud and said plurality of IoT sensor devices via said router.

10. The method as claimed in claim 9, wherein the connectivity between said IoT cloud and said plurality of IoT sensor devices further enables at least one user device connected via said IoT cloud, to control said plurality of IoT sensor devices.
11. The method as claimed in claim 9, wherein the connectivity modules comprises one of a Zigbee module, BLE module, Zwave module and Thread X module.
12. The method as claimed in claim 9, wherein the unique connectivity mode

is one of a BLE mode, Zigbee mode, Zwave mode and Thread X mode.
13. The method as claimed in claim 9, wherein the router is one of a wired and a wireless router.
14. The method as claimed in claim 9, the method comprises enabling multiple unique connections between said IoT cloud and said plurality of IoT sensor devices via said router, wherein the multiple unique connections are based on said multiple unique connectivity modes.
15. The method as claimed in claim 9, wherein the plurality of IoT sensor devices comprises plurality of NB-IoT sensor devices.
16. The method as claimed in claim 9, wherein the connectivity between said IoT cloud and said plurality of NB-IoT sensor devices comprises a connectivity over at least one NB-IoT channel.
17. A system for enabling a connection between an IoT cloud and a plurality of IoT sensor devices, the system comprising:

- at least one router configured to established connectivity between said IoT cloud and said plurality of IoT sensor devices.
- at least one SYSTEM-ON-A-CHIP connected to said at least one router, the system-on-a-chip comprising:
a mesh adapter comprising, a plurality of connectivity modules,
wherein each of said connectivity modules being associated with a
unique connectivity mode, and
each of the connectivity modules are configured to establish a
connection with the plurality of IoT sensor devices based on the
unique connectivity mode of said connectivity modules;
a processing unit connected to said mesh adapter, wherein the
processing unit is configured to establish a connection between
said mesh adapter and said at least one router, and to
enable, said at least one router, to establish a connection
between said IoT cloud and said plurality of IoT sensor devices.

- at least one user device connected to said system-on-a-chip via said IoT cloud, wherein the user device is configured to control said plurality of IoT sensor devices via said established connectivity between said IoT cloud and said plurality of IoT sensor devices.
18. The system as claimed in claim 17, wherein the connectivity modules comprises one of a Zigbee module, BLE module, Zwave module and Thread X module.
19. The system as claimed in claim 17, wherein the unique connectivity mode is one of a BLE mode, Zigbee mode, Zwave mode and Thread X mode.
20. The system as claimed in claim 17, wherein the router is one of a wired and a wireless router.
21. The system as claimed in claim 17, the system is configured to enable multiple unique connections between said IoT cloud and said plurality of IoT sensor devices via said router, wherein the multiple unique connections are based on said multiple unique connectivity modes.
22. The system as claimed in claim 17, wherein the plurality of IoT sensor devices comprises plurality of NB-IoT sensor devices.
23. The system as claimed in claim 17, wherein the connectivity between said IoT cloud and said plurality of NB-IoT sensor devices comprises a connectivity over at least one NB-IoT channel.