FIELD OF THE INVENTION

[0001] The present invention generally relates to an internet of things (IoT) and more particularly relates to a system and a method for controlling the functioning of IoT devices.
BACKGROUND

[0002] In our homes or even in commercial spaces, there are multiple electronic devices which are operated through remote controllers or a stationary regulator/switch by manual operation.
[0003] With the advent of the Internet of Things (IoT), considering the ease of operations for a user, electronic devices provide functionality with a dual source for controlling operations of the electronic devices. The existing technology provides options to control IoT electronic devices either using applications installed in the user device or through the conventional switches usually mounted on switchboards.
[0004] Now, as users’ demand for smart living spaces has been gradually increasing, every major electronics industry corporation has started manufacturing the IoT electronic devices. Thus, the user has a wide range of products and brands to choose from multiple manufacturers. It may be possible that the user may purchase and install the IoT electronic devices of different manufacturers within a vicinity or same living space. For example, the user may choose to install two smart bulbs from two different manufacturers in the living room. Now, as a user installs the IoT electronic devices, such as smart bulbs, the user may also be required to download an application in the user’s smartphone for operating the downloaded IoT electronic devices. As each manufacturer may be providing a different application for operating the IoT electronic devices. Thus, the user may be required to download a separate application for each manufacturer even if the IoT devices installed are of the same type, such as smart bulbs. This leads to inconvenience to the user, as the user must ensure that the application for each of the IoT electronic devices is downloaded and connected to the respective IoT devices. Also, the smartphone’s memory space may be clogged with multiple applications.
[0005] Therefore, there exists a need to find a solution for the above-mentioned technical problems.
SUMMARY

[0006] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention and nor is it intended for determining the scope of the invention.
[0007] According to one embodiment of the present disclosure, a method for enabling an integrated application in a user device to control the functioning of a plurality of Internet of Things (IoT) devices. The method includes receiving, by a unified server, a request from the integrated application via a first server associated with a first IoT device, of the plurality of IoT devices, for configuration settings associated with a second IoT device, of the plurality of IoT devices. The method includes determining, by the unified server, whether a second server associated with the second IoT device is registered with the unified server; and transmitting, by the unified server, the configuration settings to the integrated application via the first server upon determining that the second server associated with the second IoT device is registered with the unified server, wherein the configuration settings enable the integrated application to control the functioning of the second IoT device.
[0008] According to one embodiment of the present disclosure, a system for enabling an integrated application in a user device to control the functioning of a plurality of Internet of Things (IoT) devices. The system includes a processor in connection with a unified server configured to receive, by the unified server, a request from the integrated application via a first server associated with a first IoT device, of the plurality of IoT devices, for configuration settings associated with a second IoT device, of the plurality of IoT devices. The processor is configured to determine, by the unified server, whether a second server associated with the second IoT device is registered with the unified server; and transmit, by the unified server, the configuration settings to the integrated application via the first server upon determining that the second server associated with the second IoT device is registered with the unified server, wherein the configuration settings enable the integrated application to control the functioning of the second IoT device.
[0009] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0011] Figure 1 illustrates a schematic block diagram depicting an environment for the implementation of a system for enabling an application in a user device to control the functioning of a plurality of Internet of Things (IoT) devices, according to an embodiment of the present invention;
[0012] Figure 2 illustrates another schematic detailed block diagram of modules/software components of the system, according to an embodiment of the present invention;
[0013] Figure 3 illustrates a process flow of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices via a first server, according to an embodiment of the present invention;
[0014] Figure 4 illustrates a process flow of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices via a unified server, according to an embodiment of the present invention;
[0015] Figure 5 illustrates a process flow of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices via the unified server, according to an embodiment of the present invention;
[0016] Figure 6 illustrates another process flow of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices via the first server, according to an embodiment of the present invention;
[0017] Figure 7 illustrates a flow chart of a method for enabling the application in the user device to control the functioning of a plurality of IoT devices, according to an embodiment of the present invention;
[0018] Figure 8 illustrates another flow chart of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices, according to an embodiment of the present invention; and
[0019] Figure 9 illustrates another flow chart of a method for enabling the application in the user device to control the functioning of the plurality of IoT devices, according to an embodiment of the present invention.
[0020] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

DETAILED DESCRIPTION

[0021] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.
[0022] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
[0023] Reference throughout this specification to “an aspect,” “another aspect” or similar language 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, appearances of the phrase “in an embodiment”, “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0024] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0025] The present disclosure aims to provide an integrated platform or an application which may be in communication with multiple manufacturers and is adapted to allow users to operate IoT electronic devices of different manufacturers using the said platform/application.
[0026] Figure 1 illustrates a schematic block diagram depicting an environment for the implementation of a system 100 for enabling an integrated application 102a in a user device 102b to control the functioning of a plurality of Internet of Things (IoT) devices 104a and 104b, according to an embodiment of the present invention. For the sake of brevity, the system 100 to control the functioning of the plurality of Internet of Things (IoT) devices 104 is hereinafter interchangeably referred to as the system 100.
[0027] In an embodiment, referring to Figure 1, the system 100 may be implemented for the plurality of IoT devices 104a and 104b, the application 102a installed in the user device 102b, a unified server 108, a first server 110, and a second server 112. Although only two IoT devices 104a and 104b are depicted in Fig. 1, a person skilled in the art may appreciate that more than two such devices may be present in the system 100.
[0028] In an embodiment, referring to Figure 1, the system 100 may include the user device 102b, the application 102a installed in the user device 102b and running on an operating system (OS) of the user device 102b that generally defines a first active user environment. The application 102a may be indicative of a software package that performs a specific function for an end user. The OS typically presents or displays the application through a graphical user interface (“GUI”) of the OS. Other applications may be running on the operating system of the user device 102b but may not be actively displayed. In an example, the user device 102b may be but is not limited to, a tablet PC, a Personal Digital Assistant (PDA), a smartphone, a palmtop computer, a laptop computer, a desktop computer, a server, a cloud server, a remote server, a communications device, a wireless telephone, or any other machine controllable through the wireless-network and capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. The application 102a may be adapted to receive input(s) from a user for controlling the functioning of the plurality of IoT devices 104a and 104b. Further, the application 102a installed in the user device 102b may be adapted to control the functioning of the plurality of IoT devices 104a and 104b. The user device 102b may also be in communication with the unified server 108 and the first server 110.
[0029] In some embodiments, the plurality of IoT devices 104a and 104b, the user device 102b, the unified server 108, and the first server 110 may be in communication with each other via a wireless communication network. In an example, the wireless communication network may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network as appeared throughout the present disclosure may be a zig-bee network, a cellular telephone network such as 4G, 5G, an 802.11, 802.16, 802.20, 802.1Q, Wi-Fi, or a WiMax network. Further, the network may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. In the example, a gateway device 106 is placed in the vicinity of the plurality of IoT devices 104a and 104b and is adapted to provide the wireless communication network to the plurality of IoT devices 104a, 104b, and the user device 102b.
[0030] In some embodiments, the plurality of IoT devices may include a first IoT device 104a and a second IoT device 104b. In one example, the first IoT device 104a and the second IoT device 104b may be but are not limited to, a smart bulb, a smart fan, or a smart human voice assistant. Although only two IoT devices 104a and 104b as smart bulbs are depicted in Figure 1, a person skilled in the art may appreciate any other type of IoT devices that may also be present in the system 100. The user device 102b is adapted to control the functioning of the first IoT device 104a and the second IoT device 104b via the application 102a. In one example, the application 102a, the first IoT device 104a and the second IoT device 104b may be present in a same network and may be communicating with each other via the gateway device 106. In the example, the application 102a may send connection request to the first IoT device 104a and the second IoT device 104b. In an alternate example the application 102a may alternatively receive connection request from the first IoT device 104a and the second IoT device 104b. The connection request is akin to pairing of the user device 102b with the first IoT device 104a and/or the second IoT device 104b respectively.
[0031] In some embodiments, the unified server 108 may be a cloud IoT Core server which may be in communication with the first server 110 and the second server 112 respectively. In an example, the first server 110 and the second server 112 may be cloud IoT core servers belonging to different electronic device manufacturers. The unified server 108 may be adapted to store configuration settings for the plurality of IoT devices 104a and 104b as the first server 110 and the second server 112 may be registered with the unified server 108. The configuration settings may be indicative of functional capabilities to connect, configure, troubleshoot, and operate the plurality of IoT devices 104a and 104b. In one example, the unified server 108 may be in communication with the user device 102b and adapted to transmit the configuration settings corresponding to the plurality of IoT devices 104 to the user device 102b such that the configuration settings enable the application 102a installed in the user device 102b to control the functioning of the corresponding plurality of IoT devices 104a and 104b.
[0032] Further, the unified server 108 may be adapted to create a respective profile for each of the first server 110 and the second server 112 wherein each of the first server 110 and the second server 112 may store information about the plurality of IoT devices 104a, 104b such as but not limited to, type of IoT devices, functional architecture of the IoT devices, and the associated configuration settings respectively in the profile. Thus, in one example, the first server 110 and the second server 112 are registered with the unified server 108. Further, the first server 110 and the second server 112 may act as a client while communicating with the unified server 108, thereby creating a client-server communication model. In an example, the first server 110 and the second server 112 may create a profile by adding various information such as but not limited to, server profile, the associated plurality of IoT devices, IoT devices profile, and the configuration settings associated with each of the plurality of IoT devices. In the example, the unified server 108 may be adapted to generate reports, and data with respect to operations of the plurality of IoT devices 104a, 104b among other data. In the example, the client may connect with the unified server 108 by accessing the profile using credentials. The credentials may indicate a dedicated username and password provided by the unified server 108 to each of the first server 110 and the second server 112. The dedicated username and password may enable the first server 110 and the second server 112 to access respective profiles created at the unified server 108.
[0033] In some embodiments, the first server 110 may be associated with a first manufacturer and the second server 112 may be associated with a second manufacturer different from the first manufacturer. In one example, the first server 110 is associated with the first IoT device 104a. Thus, the first server 110 is adapted to transmit the configuration settings for the first IoT device 104a to the application 102a such that the configuration settings enable the application 102a to control functions such as switch ON/OFF, change the state of operation, etc. of the first IoT device 104a. In the example, the application 102a is also associated with the first manufacturer and thus maintains active communication with the first server 110.
[0034] In one example, the second server 112 is associated with the second IoT device 104b. Now, as the user may attempt to control the functioning of the second IoT device 104b using the application 102a, which is associated with the first manufacturer and maintains communication with the first server 110, the application 102a may fail to recognize the second IoT device 104b at first instance. The application 102a may thus send a request indicative of non-identification of the second IoT device 104b to the first server 110. In the example, the application 102a may display a notification to the user indicating that the second IoT device 104b may not be associated with the first server 110.
[0035] Further, in response to the first server 110 receiving the non-identification request from the application 102a, the first server may transmit a request for configuration settings associated with the second IoT device 104b. The unified server 108 may receive such a request for configuration settings from the first server 110. In an example, as part of the request, the first server 110 requests the unified server 108 to share the configuration settings associated with the second IoT device 104b. In the example, the unified server 108 may determine if the configuration settings associated with the second IoT device 104b is stored in a local database at the unified server 108. The unified server 108 may transmit the configuration settings to the first server 110 upon determining that the second server 112 has created the profile for the second IoT device 104b and its associated configuration settings are stored with the unified server 108.
[0036] Thus, the first server 110 receives the configuration settings associated with the second IoT device 104b from the unified server 108 and further transmits the configuration settings to the application 102a. Then, the application 102a may be able to control the functioning of the second IoT device 104b. In an example, the application 102a is associated with the first server 110 and the first manufacturer may be able to control the functioning of the second IoT device 104b say, the smart bulb associated with the second manufacturer.
[0037] In an example, along with the configuration settings, the unified server 108 may also transmit any interface such as, but not limited to, an HTML page which may be displayed on the user device 102b. The HTML page may be adaptive to display a list of controlling functions associated with the second IoT device 104b such that the user may refer to the list to easily operate the configuration settings in the application 102a.
[0038] In an embodiment, the unified server 108 may include the modules/engines/units implemented with an AI module that may include a plurality of neural network layers. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), and Restricted Boltzmann Machine (RBM). The learning technique is a method for training a predetermined target device (for example, a robot, or the unified server) using a plurality of learning data to cause, allow, or control the target device to make a determination or prediction. Examples of learning techniques include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. At least one of a plurality of CNN, DNN, RNN, RMB models and the like may be implemented to thereby achieve execution of the present subject matter’s mechanism through an AI model. A function associated with AI may be performed through the non-volatile memory, the volatile memory, and the processor. The processor may include one or a plurality of processors. At this time, one or a plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). One or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning. In one example, the unified server 108 with the AI module may be adapted to provide a recommendation to the first server 110 and/or the second server 112. In the example, the recommendation may be indicative of proposing the configuration settings related to a type of IOT device registered by respective server. In the example the unified server 108 may be adapted to provide a sandbox for the IoT device registered by respective server. The sandbox may include the recommended configuration settings based on learning obtained by the AI module from the previously store configuration settings of other IoT devices.
[0039] Figure 2 illustrates another schematic detailed block diagram of modules/software components of the system 100, according to an embodiment of the present invention.
[0040] In an embodiment, referring to Figures 1 and 2, the unified server 108 may include, but is not limited to, a processor 202, memory 204, modules 206, and data 208. The modules 206 and the memory 204 may be coupled to the processor 202.
[0041] The processor 202 can be a single processing unit or several units, all of which could include multiple computing units. The processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 202 is adapted to fetch and execute computer-readable instructions and data stored in the memory 204. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). One or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning. A detailed explanation of each of the unified server 108 as shown in figures 1 and 2 will be explained in detail in the forthcoming paragraphs. Further, the working of the system 100 will be explained with respect to figures 1 and 2. The reference numerals are kept the same in the disclosure wherever applicable for ease of explanation.
[0042] The memory 204 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0043] The modules 206, amongst other things, include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types. The modules 206 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulates signals based on operational instructions.
[0044] Further, the modules 206 can be implemented in hardware, instructions executed by a processing unit, or by a combination thereof. The processing unit can comprise a computer, a processor, a state machine, a logic array, or any other suitable devices capable of processing instructions. The processing unit can be a general-purpose processor which executes instructions to cause the general-purpose processor to perform the required tasks or, the processing unit can be dedicated to performing the required functions. In another embodiment of the present disclosure, the processor 202 via the modules 206 is configured to execute machine-readable instructions (software) which perform the working of the system 100 within the scope of the present invention as described in forthcoming paragraphs.
[0045] In an embodiment, the modules 206 may include a receiving module 210, a determining module 212, and a transmitting module 214. The receiving module 210, the determining module 212, and the transmitting module 214 may be in communication with each other. The data 208 serves, amongst other things, as a repository for storing data processed, received, and generated by one or more of the modules 206.
[0046] Referring to Figure 1 and Figure 2, the receiving module 210 may be adapted to receive the request from the application 102a via the first server 110. In an example, the first server 110 is associated with the first IoT device 104a. The request may be indicative of requesting the configuration settings associated with the second IoT device 104b. In another example, the receiving module 210 may receive the request directly from the application 102a without the involvement of the first server 110. The receiving module 210 is in communication with the determining module 212.
[0047] In an embodiment, the determining module 212 may be adapted to determine whether the second server 112 associated with the second IoT device 104b is registered with the unified server 108 or not. In an example, the registration of the second server 112 with the unified server 108 may imply that the second server 112 has created the profile and stores the configuration settings associated with the second IoT device 104b with the local database at the unified server 108. Similarly, in another example, the registration of the first server 110 with the unified server 108 may imply that the first server 110 has created the profile and stores the configuration settings associated with the first IoT device 104a with the local database at the unified server 108.
[0048] In an example, the determining module 212 may be adapted to transmit a request to the second server 112 to receive the configuration settings associated with the second IoT device 104b upon determining that the configuration settings associated with the second IoT device 104b are not stored in the unified server 108. The receiving module 210 and the determining module 212 are in communication with the transmitting module 214.
[0049] In an embodiment, the transmitting module 214 may be adapted to transmit the configuration settings to the application 102a via the first server 110. In an example, the transmitting module 214 may be adapted to transmit the configuration settings to the application 102a directly without the involvement of the first server 110. Thus, the configuration settings enable the application 102a to control the functioning of the second IoT device 104b.
[0050] Figure 3 illustrates a process flow of a method 300 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104 via the first server 110, according to an embodiment of the present invention.
[0051] In an embodiment, at step 302, the method 300 may include the first IoT device 104a establishing a connection with the application 102a on the user device 102b. In an example, the connection is indicative of pairing between the first IoT device 104a and the application 102a such that the application 102a may be able to communicate with respective IoT Device. The connection may be established through but not limited to, Bluetooth, Wi-Fi, RFID, NFC, and other networks. In one example, the application 102a may be adapted to scan and find respective IoT device in its proximity or within the same network. Thus, in the example, the application 102a may attempt to establish the connection with the first IoT device 104a. In an another example, the first IoT device 104a may be adapted to scan and find the application 102a on the user device 102b in its proximity or within the same network. Thus, in the example, the first IoT device 104a may attempt to establish the connection with the application 102a. In an another example, the first IoT device 104a may possess a unique key such as alphanumeric code, a QR code which the application 102a may utilize to establish the connection or achieve the pairing.
[0052] At step 304, the application 102a being associated with the first server 110, transmits the connection request of the first IoT device 104a to the first server 110. Upon receiving the connection request, the first server 110 is adapted to validate the first IoT device 104a. The validation may be indicative of cryptographically verifying the identity of the first IoT device 104a for the purpose of authenticating the first IoT device 104a. In an example, the authentication of the plurality of IoT devices 104a, 104b may indicate the establishment of a model for controlling access to plurality of IoT devices 104a, 104b through the internet and other secured or unsecured network platforms. Further, upon successful validation, an encrypted channel is established so the first IoT device 104a and the first server 110 may communicate privately.
[0053] Thus, at step 306, the first server 110 may transmit the configuration settings associated with the first IoT device 104a to the application 102a such that the application 102a may control the functioning of the first IoT device 104a. At step 308, the application 102a may send instructions based on the configuration settings to the first IoT device 104a for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the first IoT device 104a.
[0054] Further, at step 310, the second IoT device 104b may be attempting to establish a connection with the application 102a on the user device 102b. In an example, the connection is indicative of pairing between the second IoT device 104b and the application 102a such that the application 102a may be able to communicate with respective IoT Device. The connection may be established through but not limited to, Bluetooth, Wi-Fi, RFID, NFC, and other networks. In one example, the application 102a may be adapted to scan and find respective IoT device in its proximity or within the same network. Thus, in the example, the application 102a may attempt to establish the connection with the second IoT device 104b. In an another example, the second IoT device 104b may be adapted to scan and find the application 102a on the user device 102b in its proximity or within the same network. Thus, in the example, the second IoT device 104b may attempt to establish the connection with the application 102a. In an another example, the second IoT device 104b may possess a unique key such as alphanumeric code, a QR code which the application 102a may utilize to establish the connection or achieve the pairing.
[0055] At step 312, the application 102a being associated with the first server 110 transmits the connection request of the second IoT device 104b to the first server 110. Upon receiving the connection request, the first server 110 is adapted to validate the second IoT device 104b.
[0056] At step 314, the first server 110 fails to validate the second IoT device 104b as the second IoT device 104b is associated with the second server 112 of the second manufacturer. Thus, the first server 110 sends the request to the unified server 108 for receiving the configuration settings associated with the second IoT device 104b.
[0057] In some embodiments, the unified server 108 may be adapted to validate the second IoT device 104b. In an example, in validation, the unified server 108 may determine if the second server 112 associated with the second IoT device 104b is registered with the unified server 108. Further, the unified server 108 determines whether the second server 112 has stored the configuration settings associated with the second IoT device 104b as part of registration on the unified server 108.
[0058] Thus, at step 316, the unified server 108 transmits the configuration settings associated with the second IoT device 104b to the first server 110 upon determining that the second server 112 is registered.
[0059] At step 318, the first server 110 transmits the configuration settings associated with the second IoT device 104b to the application 102a associated with the first server 110.
[0060] At step 320, the application 102a may send instructions based on the configuration settings to the second IoT device 104b for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the second IoT device 104b.
[0061] At step 322 is in continuation with the previous step 316. The unifier server 108 may transmit a request to the second server 112 to receive the configuration settings associated with the second IoT device 104b upon determining that the configuration settings associated with the second IoT device 104b are not stored in the unified server 108.
[0062] At step 324, the second server 112 may store the configuration settings associated with the second IoT device 104b on the unified server 108. In an example, in continuation with the step 322, the second server 112 may send the configuration settings associated with the second IoT device 104b to the unified server 108 upon receiving the request.
[0063] Figure 4 illustrates a process flow of a method 400 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104 via the unified server 108, according to an embodiment of the present invention.
[0064] In an embodiment, at step 402, the method 400 may include the first IoT device 104a establishing a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the first IoT device 104a and the application 102a that are already explained in Figure 3, at step 302 are not explained in detail here. At step 404, the application 102a being associated with the unified server 108, transmits the connection request of the first IoT device 104a to the unified server 108. Upon receiving the connection request, the unified server 108 is adapted to validate the first IoT device 104a. The validation may be indicative of cryptographically verifying the identity of the first IoT device 104a. Upon successful validation, an encrypted channel is established so the first IoT device 104a and the unified server 108 may communicate privately.
[0065] Thus, at step 406, the unified server 108 may transmit the configuration settings associated with the first IoT device 104a to the application 102a such that the application 102a may control the functioning of the first IoT device 104a. At step 408, the application 102a may send instructions based on the configuration settings to the first IoT device 104a for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the first IoT device 104a.
[0066] Similarly, at step 410, the second IoT device 104b may be attempting to establish a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the second IoT device 104b and the application 102a that are already explained in Figure 3, at step 310 are not explained in detail here.
[0067] At step 412, the application 102a being associated with the unified server 108 transmits the connection request of the second IoT device 104b to the unified server 108.
[0068] In some embodiments, upon receiving the connection request, the unified server 108 may be adapted to validate the second IoT device 104b. In an example, in validation, the unified server 108 may determine if the second server 112 associated with the second IoT device 104b is registered with the unified server 108. Further, the unified server 108 determines whether the second server 112 has stored the configuration settings associated with the second IoT device 104b as part of registration on the unified server 108.
[0069] Thus, at step 414, the unified server 108 transmits the configuration settings associated with the second IoT device 104b to the application 102a upon determining that the second server 112 is registered.
[0070] At step 416, the application 102a may send instructions based on the configuration settings to the second IoT device 104b for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the second IoT device 104b.
[0071] At step 418, in continuation with step 414, the unified server 108 may transmit a request to the second server 112 to receive the configuration settings associated with the second IoT device 104b upon determining that the configuration settings associated with the second IoT device 104b are not stored in the unified server 108.
[0072] At step 422, the second server 112 may store the configuration settings associated with the second IoT device 104b on the unified server 108. In an example, in continuation with the step 418, the second server 112 may send the configuration settings associated with the second IoT device 104b to the unified server 108 upon receiving the request.
[0073] Figure 5 illustrates a process flow of a method 500 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104 via the unified server 108, according to an embodiment of the present invention.
[0074] In an embodiment, at step 502, the method 500 may include the first IoT device 104a establishing a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the first IoT device 104a and the application 102a that are already explained in Figure 3, at step 302 are not explained in detail here. At step 504, the application 102a being associated with the unified server 108, transmits the connection request of the first IoT device 104a to the unified server 108. Upon receiving the connection request, the unified server 108 is adapted to validate the first IoT device 104a. The validation may be indicative of cryptographically verifying the identity of the first IoT device 104a. Upon successful validation, an encrypted channel is established so the first IoT device 104a and the unified server 108 may communicate privately.
[0075] Thus, at step 506, the unified server 108 may transmit the configuration settings associated with the first IoT device 104a to the application 102a such that the application 102a may control the functioning of the first IoT device 104a. At step 508, the application 102a may send instructions based on the configuration settings to the first IoT device 104a for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the first IoT device 104a.
[0076] Similarly, at step 510, the second IoT device 104b may be attempting to establish a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the second IoT device 104b and the application 102a that are already explained in Figure 3, at step 310 are not explained in detail here.
[0077] At step 512, the application 102a being associated with the unified server 108 transmits the connection request of the second IoT device 104b to the unified server 108. Upon receiving the connection request, the unified server 108 may be adapted to validate the second IoT device 104b. In an example, in validation, the unified server 108 may be adapted to determine whether the configuration settings associated with the second IoT device 104b is stored in the local database with the unified server 108. The configuration settings associated with the second IoT device 104b may be stored in the unified server 108 by the client creating the profile with the unified server 108. The client may store the plurality of IoT devices 104 and the associated configuration settings.
[0078] At step 514, the unified server 108 transmits the configuration settings associated with the second IoT device 104b to the application 102a.
[0079] At step 516, the application 102a may send instructions based on the configuration settings to the second IoT device 104b for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the second IoT device 104b. In an example, if the configuration settings associated with the second IoT device 104b are not stored in the unified server 108, then the unified server 108 may transmit a message notification to be displayed on the application 102a indicating that the second IoT device 104b is not registered with the unified server 108.
[0080] Figure 6 illustrates another process flow of a method 600 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104a 104b, according to an embodiment of the present invention.
[0081] In an embodiment, at step 602, the method 600 may include the first IoT device 104a establishing a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the first IoT device 104a and the application 102a that are already explained in Figure 3, at step 302 are not explained in details here. At step 604, the application 102a being associated with the first server 110, transmits the connection request of the first IoT device 104a to the first server 110. Upon receiving the connection request, the first server 110 is adapted to validate the first IoT device 104a. The validation may be indicative of cryptographically verifying the identity of the first IoT device 104a. Upon successful validation, an encrypted channel is established so the first IoT device 104a and the first server 110 may communicate privately.
[0082] Thus, at step 606, the first server 110 may transmit the configuration settings associated with the first IoT device 104a to the application 102a such that the application 102a may control the functioning of the first IoT device 104a. At step 608, the application 102a may send instructions based on the configuration settings to the first IoT device 104a for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the first IoT device 104a.
[0083] Further, at step 610, the second IoT device 104b may be attempting to establish a connection with the application 102a on the user device 102b. For the sake of brevity, constructional and operational features of the connection between the second IoT device 104b and the application 102a that are already explained in Figure 3, at step 310 are not explained in detail here.
[0084] At step 612, the application 102a being associated with the first server 110 transmits the connection request of the second IoT device 104b to the first server 110. Upon receiving the connection request, the first server 110 is adapted to validate the second IoT device 104b.
[0085] At step 614, the first server 110 fails to validate the second IoT device 104b as the second IoT device 104b is not associated with the first server 110. Thus, first server 110 sends the request to the unified server 108 for validation and receives the configuration settings associated with the second IoT device 104b.
[0086] In some embodiments, the unified server 108 may be adapted to validate the second IoT device 104b. In an example, in validation, the unified server 108 may determine if the configuration settings associated with the second IoT device 104b is stored in the unified server 108. The configuration settings associated with the second IoT device 104b may be stored in the unified server 108 by the client creating the profile with the unified server 108. The client may store the plurality of IoT devices 104 and the associated configuration settings. In an example, if the configuration settings associated with the second IoT device 104b are not stored in the unified server 108, then the unified server 108 may transmit a message notification to be displayed on the application 102a indicating that the second IoT device 104b is not registered with the unified server 108.
[0087] Thus, at step 616, the unified server 108 transmits the configuration settings associated with the second IoT device 104b to the first server 110 upon determining that the configuration settings associated with the second IoT device 104b are stored in the unified server 108.
[0088] At step 618, the first server 110 transmits the configuration settings associated with the second IoT device 104b to the application 102a associated with the first server 110.
[0089] At step 620, the application 102a may send instructions based on the configuration settings to the second IoT device 104b for performing one of, but not limited to, connecting, configuring, troubleshooting, and operating the second IoT device 104b.
[0090] Figure 7 illustrates an exemplary flow chart comprising a method 700 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104, according to an embodiment of the present invention. The method 700 may be a computer-implemented method executed, for example, by the unified server 108 and the modules 206. For the sake of brevity, constructional and operational features of the system 100 that are already explained in the description of Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, and Figure 6 are not explained in detail in the description of Figure 7.
[0091] At step 702, the method 700 may include receiving, by the unified server 108 the request from the application 102a via the first server 110 associated with the first IoT device 104a for the configuration settings associated with the second IoT device 104b.
[0092] At step 704, the method 700 may include determining, by the unified server 108 whether the second server 112 associated with the second IoT device 104b is registered with the unified server 108.
[0093] At step 706, the method 700 may include transmitting, by the unified server 108 the configuration settings to the application 102a via the first server 110 upon determining that the second server 112 associated with the second IoT device 104b is registered with the unified server 108. In an example, the configuration settings enable the application 102a to control the functioning of the second IoT device 104b.
[0094] Figure 8 illustrates another flow chart of a method 800 for enabling the application 102a in the user device 102b to control the functioning of the plurality of IoT devices 104, according to an embodiment of the present invention.
[0095] At step 802, the method 800 may include receiving, by the unified server 108 the request from the application 102a associated with the first IoT device 104a for the configuration settings associated with the second IoT device 104b.
[0096] At step 804, the method 800 may include determining, by the unified server 108 whether the second server 112 associated with the second IoT device 104b is registered with the unified server 108.
[0097] At step 806, the method 800 may include transmitting, by the unified server 108 the configuration settings to the application 102a upon determining that the second server 112 associated with the second IoT device 104b is registered with the unified server 108.
[0098] Figure 9 illustrates another flow chart of a method 900 for enabling the application 102a in a user device 102b to control the functioning of the plurality of IoT devices 104, according to an embodiment of the present invention.
[0099] At step 902, the method 900 may include receiving, by the unified server 108, the request from the application 102a associated with the first IoT device 104a for configuration settings associated with the second IoT device 104b. In an example, the unified server 108 may receive the request from the application 102a via the first server 110 associated with the first IoT device 110 and the first manufacturer.
[0100] At step 904, the method 900 may include determining, by the unified server 108 whether the second IoT device 104b is registered with the unified server 108.
[0101] At step 906, the method 900 may include transmitting, by the unified server 108, the configuration settings to integrated application 102a upon determining that second IoT device 104b is registered with the unified server 108.
[0102] The present invention provides various advantages:
• The present invention enables a user to operate multiple IoT devices with a single application.
• The present invention eases operational usage of the IoT devices as the user may refer to only one application for controlling functions of multiple IoT devices.
• The present invention helps in saving memory space in smartphones as the user does not have to save multiple applications for multiple IoT devices.
• The present invention is advantageous for manufacturers as they may avoid configuring, and maintaining, a server and an application. Instead, the manufacturers may create a profile with the unified server and store the IoT devices and associated configuration settings. The user will access the unified server for operating the IoT device associated with the said manufacturer.

[0103] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0104] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

We Claims:

1. A method (700) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices (104a, 104b), the method (700) comprising:
receiving (702), by a unified server (108), a request from the integrated application (102a) via a first server (110) associated with a first IoT device (104a), of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determining (704), by the unified server (108), whether a second server (112) associated with the second IoT device (104b) is registered with the unified server (108); and
transmitting (706), by the unified server (108), the configuration settings to the integrated application (102a) via the first server (110) upon determining that the second server (112) associated with the second IoT device (104b) is registered with the unified server (108), wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

2. The method (700) as claimed in claim 1, wherein each of the first IoT device (104a) and the first server (110) is associated with a first manufacturer, and wherein each of the second IoT device (104b) and the second server (112) is associated with a second manufacturer different from the first manufacturer.

3. The method (700) as claimed in claim 1, wherein the receiving comprises receiving the request from the integrated application (102a) associated with the first manufacturer.

4. The method (700) as claimed in claim 1 comprising:
determining, by the unified server (108), whether the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108).

5. The method (700) as claimed in claim 4 comprising:
identifying, by the unified server (108), the second server (112) associated with the second IoT device (104b), upon determining that configuration settings associated with the second IoT device (104b) are not stored in the unified server (108); and
transmitting, by the unified server (108), a request to the second server (112) to receive the configuration settings associated with the second IoT device (104b).

6. A method (800) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices (104a, 104b), the method (800) comprising:
receiving (802), by a unified server (108), a request from the integrated application (102a) associated with a first IoT device (104a) of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determining (804), by the unified server (108), whether a second server (112) associated with the second IoT device (104b) is registered with the unified server (108); and
transmitting (806), by the unified server (108), the configuration settings to the integrated application (102a) upon determining that the second server (112) associated with the second IoT device (104b) is registered with the unified server (108) wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

7. The method (800) as claimed in claim 6, wherein the first IoT device (104a) is associated with a first manufacturer, and wherein each of the second IoT device (104b) and the second server (112) is associated with a second manufacturer different from the first manufacturer.

8. The method (800) as claimed in claim 6, wherein the receiving comprises receiving the request from the integrated application (102a) associated with the first manufacturer.

9. The method (800) as claimed in claim 6, comprising:
determining, by the unified server (108), whether the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108).

10. The method (800) as claimed in claim 9, the method comprising:
identifying, by the unified server (108), the second server (112) associated with the second IoT device (104b), upon determining that the configuration settings associated with the second IoT device (104b) are not stored in the unified server (108); and
transmitting, by the unified server (108), a request to the second server (112) to receive the configuration settings associated with the second IoT device (104b).

11. A method (900) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices, the method (900) comprising:
receiving (902), by a unified server (108), a request from the integrated application (102a) associated with a first IoT device (104a) of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determining (904), by the unified server (108), whether the second IoT device (104b) is registered with the unified server (108); and
transmitting (906), by the unified server (108), the configuration settings to the integrated application (102a) upon determining that second IoT device (104b) is registered with the unified server (108) wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

12. The method (900) as claimed in claim 11, wherein the receiving comprises receiving the request from the integrated application (102a) via a first server (110) associated with the first IoT device (104a) and a first manufacturer.

13. The method (900) as claimed in claim 11, wherein the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108) and the second IoT device (104b) is associated with a second manufacturer.

14. A system (100) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices (104a, 104b), the system (100) comprises:
a processor (202) in connection with a unified server (108) configured to:
receive, by the unified server (108), a request from the integrated application (102a) via a first server (110) associated with a first IoT device (104a), of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determine, by the unified server (108), whether a second server (112) associated with the second IoT device (104b) is registered with the unified server (108); and
transmit, by the unified server (108), the configuration settings to the integrated application (102a) via the first server (110) upon determining that the second server (112) associated with the second IoT device (104b) is registered with the unified server (108), wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

15. The system (100) as claimed in claim 14, wherein each of the first IoT device (104a) and the first server (110) is associated with a first manufacturer, and wherein each of the second IoT device (104b) and the second server (112) is associated with a second manufacturer different from the first manufacturer.

16. The system (100) as claimed in claim 14, wherein the processor (202) is configured to: receive the request from the integrated application (102a) associated with the first manufacturer.

17. The system (100) as claimed in claim 14, the processor (202) is configured to:
determine, by the unified server (108), whether the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108).

18. The system (100) as claimed in claim 17, the processor (202) is configured to:
identify, by the unified server (108), the second server (112) associated with the second IoT device (104b), upon determining that configuration settings associated with the second IoT device (104b) are not stored in the unified server (108); and
transmit, by the unified server (108), a request to the second server (112) to receive the configuration settings associated with the second IoT device (104b).

19. A system (100) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices (104a, 104b), the system (100) comprises:
a processor (202) in connection with a unified server (108) and configured to:
receive, by the unified server (108), a request from the integrated application (102a) associated with a first IoT device (104a) of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determine, by the unified server (108), whether a second server (112) associated with the second IoT device (104b) is registered with the unified server (108); and
transmit, by the unified server (108), the configuration settings to the integrated application (102a) upon determining that the second server (112) associated with the second IoT device (104b) is registered with the unified server (108) wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

20. The system (100) as claimed in claim 19, wherein the first IoT device (104a) is associated with a first manufacturer, and wherein each of the second IoT device (104b) and the second server (112) is associated with a second manufacturer different from the first manufacturer.

21. The system (100) as claimed in claim 19, the processor (202) is configured to: receive the request from the integrated application (102a) associated with the first manufacturer.

22. The system (100) as claimed in claim 19, the processor (202) is configured to:
determine, by the unified server (108), whether the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108).

23. The system (100) as claimed in claim 22, the processor (202) is configured to:
identify, by the unified server (108), the second server (112) associated with the second IoT device (104b), upon determining that the configuration settings associated with the second IoT device (104b) are not stored in the unified server (108); and
transmit, by the unified server (108), a request to the second server (112) to receive the configuration settings associated with the second IoT device (104b).

24. A system (100) for enabling an integrated application (102a) in a user device (102b) to control functioning of a plurality of Internet of Things (IoT) devices (104a, 104b), the system (100) comprises:
a processor (202) in connection with the unified server (108) and configured to:
receive, by a unified server (108), a request from the integrated application (102a) associated with a first IoT device (104a) of the plurality of IoT devices (104a, 104b), for configuration settings associated with a second IoT device (104b), of the plurality of IoT devices (104a, 104b);
determine, by the unified server (108), whether the second IoT device (104b) is registered with the unified server (108); and
transmit, by the unified server (108), the configuration settings to the integrated application (102a) upon determining that second IoT device (104b) is registered with the unified server (108) wherein the configuration settings enable the integrated application (102a) to control functioning of the second IoT device (104b).

25. The system (100) as claimed in claim 24, wherein the processor (202) is configured to receive the request from the integrated application (102a) via a first server (110) associated with the first IoT device (104a).

26. The system (100) as claimed in claim 24, wherein the configuration settings associated with the second IoT device (104b) are stored in a local database at the unified server (108) and the second IoT device (104b) is associated with a second manufacturer.