US20170279894A1 - Universal internet of things (iot) smart translator - Google Patents

Universal internet of things (iot) smart translator Download PDF

Info

Publication number
US20170279894A1
US20170279894A1 US15/298,379 US201615298379A US2017279894A1 US 20170279894 A1 US20170279894 A1 US 20170279894A1 US 201615298379 A US201615298379 A US 201615298379A US 2017279894 A1 US2017279894 A1 US 2017279894A1
Authority
US
United States
Prior art keywords
protocol
iot
application
devices
virtual
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US15/298,379
Other languages
English (en)
Inventor
Li Chen
Ying Xiong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Esmart Tech Inc
Original Assignee
Esmart Tech Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Esmart Tech Inc filed Critical Esmart Tech Inc
Priority to US15/298,379 priority Critical patent/US20170279894A1/en
Priority to CN201611196972.8A priority patent/CN107222454A/zh
Priority to PCT/US2017/020838 priority patent/WO2017165105A1/en
Priority to US15/655,717 priority patent/US10003654B2/en
Publication of US20170279894A1 publication Critical patent/US20170279894A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H04L67/16—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Definitions

  • IoT Internet of things
  • Many Internet of things (IoT) devices such as light bulbs, toasters, televisions, etc. may utilize some IoT protocol and are able to be controlled by or otherwise interact with various applications (or “apps”) that run on various user devices (e.g., smartphones, tablets, personal computers, etc.).
  • applications or “apps”
  • user devices e.g., smartphones, tablets, personal computers, etc.
  • IoT devices utilize a variety of communication protocols.
  • the apps may utilize a variety of protocols. End users are forced to use apps that support the communication protocol of the IoT devices.
  • IoT devices may not be able to interact with each other due to differing protocols.
  • Some embodiments provide a universal Internet of things (IoT) translator.
  • IoT Internet of things
  • Such a translator may allow communication among user devices (and/or associated applications) and IoT devices (and/or associated applications) when the user device protocols do not match the IoT device protocols.
  • Each service and each virtual may be associated with a different protocol.
  • the core may communicate among the services and virtuals using an internal protocol.
  • the universal translator may be able to relay messages, commands, data, etc., between user devices and IoT devices. Messages may be received from a user device at a virtual and converted from the protocol of the virtual to an internal protocol of the universal translator. The messages may be relayed to the service associated with an IoT device. The service may send the message to the IoT device.
  • Messages, data, etc. may be received from the IoT device at the associated services and converted to the internal protocol.
  • the converted message may be relayed to the virtual device associated with the user device protocol and sent by the virtual device to the user device.
  • FIG. 6 illustrates a message flow diagram of an exemplary communication structure used by the system of FIG. 1 ;
  • FIG. 8 illustrates a flow chart of an exemplary process that provides universal translation for an IoT device associated with multiple applications
  • FIG. 9 illustrates a flow chart of an exemplary process that sends operations to an IoT device from a user device.
  • a first exemplary embodiment provides a system that provides communication among user devices and IoT devices.
  • the system includes: at least one user device able to execute at least one application that is able to communicate using at least a first IoT protocol; at least one IoT device able to communicate using at least a second IoT protocol; and a universal translator able to communicate using at least the first IoT protocol and the second IoT protocol.
  • the universal translator 110 may be an electronic device that is able to communicate among the IoT devices 120 and user devices 130 across multiple protocols 140 - 150 , as necessary.
  • the universal translator 110 may be implemented using one or more server devices that are accessible across various appropriate networks (e.g., cellular networks, wireless networks, the Internet, etc.).
  • the translator may be included at a user device 130 , IoT device 120 , and/or a combination of user devices 130 , IoT devices 120 and/or servers.
  • the universal translator 110 may be provided as a fully extensible plug-in to any IoT protocol (whether standard or proprietary).
  • the translator may receive and apply updates automatically and securely.
  • the translator may support existing and/or potential protocols such as wireless protocols.
  • the translator may utilize encrypted communication.
  • the universal translator will be described in more detail in reference to FIGS. 2-5 below.
  • Each IoT device 120 may be an electronic device that is capable of communicating across at least one protocol 140 .
  • the IoT devices 120 may include physical devices, vehicles, buildings, etc. with embedded IoT functionality.
  • Example IoT devices include locksets, power or lighting, appliances, HVAC or heating systems, etc.
  • the IoT devices may include multiple physical components (e.g., a smart light bulb may include a physical bulb and a computer system that resides in the cloud) that are able to communicate across one or more networks.
  • Such devices may include elements such as sensors, actuators, wired or wireless communication transmitters and/or receivers, etc. Such devices may typically be able to connect to one or more local or distributed networks.
  • Each user device 130 may be device such as a smartphone, tablet, personal computer, remote control, etc. That is able to communicate across at least one protocol 150 , typically by executing an application.
  • each user device may include components such as user interface elements (e.g., touchscreens, keypads, buttons, etc.) that may be used to control or otherwise interact with the various IoT devices 140 .
  • an IoT device 120 may server as the user device 130 .
  • an IoT garage door opener may be used to control an IoT light bulb.
  • a user device 130 may attempt to interact with an IoT device 120 (e.g., by sending a command to the IoT device). If the user device 130 is able to communicate using protocol 150 while the IoT device is able to communicate using protocol 140 , the universal translator 110 may receive the command from the user device 130 across protocol 150 and deliver the command to the IoT device 120 across protocol 140 .
  • the universal translator 110 may likewise allow the IoT device 120 to send messages or data by receiving communications from the IoT device over protocol 140 and delivering the communications to the user device 130 across protocol 150 .
  • FIG. 2 illustrates a schematic block diagram of an exemplary universal translator 110 provided by system 100 .
  • the universal translator may include a core 210 , a set of services 220 , and a set of virtual devices 230 .
  • the various components 210 - 230 of translator 110 may be implemented using multiple physical devices or computer systems.
  • the services 220 may include multiple plug-in modules that are able to communicate with various IoT devices 120 and or applications (e.g., via user devices 130 ) using any supported protocol. Such services 220 will be described in more detail in reference to FIG. 4 below.
  • the virtual devices 230 may include multiple plug-in modules that are able to instantiate as an IoT device in order to communicate with various user devices 130 using any supported protocol. Such virtual devices 230 will be described in more detail in reference to FIG. 5 below.
  • the communication module 310 may manage, perform, or otherwise carry out communication (e.g., messaging, threads, etc.) between the services subsystem 220 and the virtual devices subsystem 230 .
  • the communication module 310 may further manage various hardware subsystems.
  • the translator command module 320 may manage command and/or protocol parsing.
  • the main command module 330 may manage a main thread overseeing all other modules with the core subsystem 210 .
  • the user data module 340 may handle user and/or configuration data and maintain the app list 350 and device list 360 .
  • the app list 350 may include a list of associated applications, their status, and/or other relevant information.
  • the applications may be associated based on various relevant criteria such as installation on a user device, previous execution of the applications, a listing of available applications from a provider, etc.
  • the device list 360 may include a list of associated IoT devices, their status, and/or other relevant information.
  • the devices may be associated based on various relevant factors such as previous interactions, association with a manufacturer, etc.
  • FIGS. 1-3 may be implemented in various different ways without departing from the scope of the disclosure. For instance, some embodiments may include additional modules, devices, etc. As another examples, various modules may be eliminated. In addition, the various modules, devices, etc. may be implemented using various different communication pathways or schemes than shown.
  • FIG. 4 illustrates a schematic block diagram of exemplary services 220 provided by the universal translator 110 .
  • the services 220 include a platform 410 , and multiple sets of protocol specific services 420 and associated porting layers 430 .
  • the platform 410 may be provided by the internal protocol of the translator 110 and may allow interaction with the core 210 .
  • the internal protocol may be a complete IoT protocol that is able to be used by an IoT device.
  • Each protocol specific service 420 may be associated with one or more corresponding protocol specific service 420
  • IoT protocols may include communication rules, parameters, attributes, etc. associated with the IoT protocol.
  • one or more protocol specific services 420 may be associated with a single IoT device 120 or user device 130 app, type or brand of device or app, multiple devices or apps associated with a specific protocol, etc.
  • Each porting layer 430 may link the associated specific service 420 to the internal protocol via the platform 410 .
  • FIG. 5 illustrates a schematic block diagram of exemplary virtual devices provided by the universal translator 110 .
  • the virtuals 230 include a platform 510 , and multiple sets of specific virtual devices 520 and associated porting layers 530 .
  • the platform 510 may be provided by the internal protocol of the translator 110 and may allow interaction with the core 210 .
  • Each virtual device 520 may be associated with one or more corresponding protocols and may include communication rules, parameters, attributes, etc. associated with an IoT device or user device protocol, where the protocol may be associated with an application running on the user device.
  • one or more protocol specific virtuals 520 may be associated with a single IoT device 120 or user device 130 , type or brand of device(s), multiple devices associated with a specific protocol, etc.
  • Each porting layer 530 may link the associated specific virtual 520 to the internal protocol via the platform 510 .
  • FIGS. 1-5 may be implemented in various different ways without departing from the scope of the disclosure.
  • some embodiments may include additional modules or components (e.g., hardware modules, user interface elements, etc.), may omit various components, include different arrangements of components, etc.
  • FIG. 6 illustrates a message flow diagram of an exemplary communication structure 600 used by system 100 .
  • the system may include a universal translator 110 , IoT device 120 , and user device 130 .
  • the universal translator 110 in this example includes a core 210 , services 220 , and virtuals 230 .
  • the user device 130 may include new applications 610 and old or previously added applications 615 .
  • the core 210 may send to the services 220 a request 620 to initiate service for each supported IoT protocol.
  • the services 220 may respond to such a request by listening for devices and/or apps on each supported protocol.
  • the IoT device 120 may broadcast an existence message or beacon 625 that is able to be received by one of the services 220 .
  • the service may, in turn, process the discovery of the new device 120 based on the protocol of the message 625 .
  • a new app 610 may then broadcast an existence message or beacon 630 that is able to be received by one of the services 220 .
  • the service may, in turn, process the discovery of the new app 610 based on the protocol of the message 630 .
  • the service 220 may establish a communication channel 635 between the service 220 and the device 120 .
  • the service 220 may send a device notification 640 to the core 210 .
  • the notification 640 may include an indication of a new device, identified protocol associated with the device, a unique identifier or ID associated with the device, etc.
  • the service 220 may then send an app notification 645 to the core 210 .
  • the notification 645 may include an indication of a new app, identified protocol associated with the app, a unique identifier or ID associated with the app, etc.
  • the core 210 may then insert the new app information into the app list and insert the new device information into the device list. For each new devices, the core 210 may loop through the app list and if the protocols do not match, the core may initiate a virtual device instance corresponding to the app protocol. Such initiation may achieved by sending an instantiation request 650 for a new app and/or an instantiation request 655 for an existing app from the core 210 to the virtuals 230 .
  • the core 210 may determine whether the protocol of the old app 615 matches the protocol of the new IoT device 120 and, if the protocols do not match, create a virtual 230 of the IoT device 120 that uses the protocol of the old app 615 .
  • the new virtual 230 may broadcast an existence message 660 to the new app 610 and establish a communication channel 665 between the virtual 230 and the new app 610 .
  • a virtual 230 associated with an existing app 615 may broadcast an existence message 670 to the old app 615 and establish a communication channel 675 between the virtual 230 and the old app 615 .
  • the core 210 may communicate directly with the new app 610 rather than via virtual 230 .
  • the established communication channels may then be utilized to allow two-way communication among the device 120 and apps 610 or 615 .
  • One example scenario is described below in reference to messages 680 - 695 .
  • the normalized message 685 may be sent from the virtual 230 to the core 210 using the internal protocol.
  • the core may identify the IoT device associated with the message using the device list.
  • the normalized operation 690 may then be sent from the core 210 to the specific service 220 identified using the device list.
  • the service may send the operation 695 to the IoT device 120 using the appropriate protocol for the IoT device.
  • a similar communication algorithm may be used to relay messages or data from the IoT device 120 to the user device 130 .
  • the communication structure 600 may be implemented in various different ways without departing from the scope of the disclosure. For instance, although some messages may be represented as single entities, the various communications may include various numbers of packets of data, initialization messages, handshake or other communication protocols, etc. In addition, although the messages have been shown in a particular order, different embodiments may allow different structures and/or messaging sequences depending on the content of one or more messages and/or other relevant factors. Furthermore, the communication structure may be implemented using different specific physical components.
  • FIG. 7 illustrates a flow chart 700 of an exemplary process that provides universal translation. Such a process may begin, for instance, when a user device application is launched, when an IoT device is turned on, etc. The process may be performed by a component such as translator 110 .
  • the process may identify (at 710 ) an IoT device.
  • the process may determine (at 720 ) a protocol and unique identifier (ID) for the IoT device.
  • the protocol determination may be made based on various relevant factors (e.g., messages received from the device).
  • the unique identifier may have been previously generated at the translator 110 and may be associated with a device list such as list 360 .
  • the process may then identify (at 730 ) an application.
  • the application may be executed by a user device such as a smartphone, tablet, personal computer, wearable device, etc.
  • the process may determine (at 740 ) a protocol and unique ID associated with the user device and or application.
  • the protocol determination may be made based on various appropriate criteria (e.g., messages received from the app or device).
  • the unique ID may have been previously generated at the translator 110 and may be associated with an app list such as list 350 .
  • the unique IDs may be at least partly based on information associated with the user device (e.g., a serial number, model number, etc.) and may include automatically incremented elements, randomly generated strings, user input data, protocol specific ID, and/or other appropriate features that may allow for additional unique IDs to be generated for the new apps and devices as they are encountered.
  • the translator 110 may then be able to identify the unique ID based on future communications received from the application(s) or device(s).
  • the unique ID may be unique within the universal IoT system of some embodiments (i.e., it is insufficient for the ID to be unique within its own protocol).
  • Process 700 may then determine (at 750 ) whether the protocols and/or IDs match between the IoT device and the user device. In addition, some embodiments may determine whether the protocols match between a new app or new device and each existing app or device. If the protocols and IDs do not match, the process may insert (at 760 ) a virtual device that is able to translate communications between user devices and IoT devices.
  • the process may receive (at 770 ) an operation such as a command from the application.
  • the process may then send (at 780 ) the operation to the IoT device, where the operation may be sent via the virtual device, as appropriate.
  • a similar process may be used to receive communications at the user device from the IoT device or to allow communications among IoT devices.
  • FIG. 8 illustrates a flow chart of an exemplary process 800 that provides universal translation for an IoT device associated with multiple applications.
  • process 800 describes the handling of new apps and devices. Such a process may begin, for instance, when a user device application is launched, when an IoT device is turned on, etc. The process may be performed by a component such as translator 110 .
  • the process may receive (at 810 ) a device protocol and ID and receive (at 820 ) an app protocol and ID.
  • Such information may be received from the services 220 at the core 210 using messages such as messages 640 - 645 described above.
  • the process may determine (at 830 ) whether the app is a new app (i.e., an application that has not be encountered previously). Such a determination may be made by comparing the received app information to information in the app list. If the process determines that the app is new, the process add (at 840 ) the app to the app list.
  • a new app i.e., an application that has not be encountered previously.
  • Process 800 may then loop (at 845 ) through a list of existing IoT devices and determine (at 850 ) for each device in the device list, whether the protocols of the new app and the existing devices match. If the protocols do not match, the process may initiate (at 855 ) a virtual device instance.
  • the process may determine (at 860 ) whether the device is a new device. Such a determination may be made by comparing the received device information to information in the device list. If the device is not a new device, the process may end.
  • Process 800 may then add (at 865 ) the device to the device list.
  • Process 800 may then loop (at 870 ) through the app list and determine (at 880 ) for each app in the app list, whether the protocols of the new device and the app match. If the protocols do not match, the process may initiate (at 890 ) a virtual device instance and then may end. If the protocols match, the process may end without instantiating any virtual device.
  • FIG. 9 illustrates a flow chart of an exemplary process 900 that sends operations to an IoT device from a user device.
  • a process may begin, for instance, when a command is received at a user device application, when an IoT device responds to a command, etc.
  • the process may be performed by a component such as translator 110 .
  • a similar complementary process may be used to receive messages from the IoT device and send messages to the user device.
  • the process may receive (at 910 ) an operation.
  • Such an operation may be received from an app and be based on various user inputs or actions.
  • the process may normalize (at 920 ) the operation for use within the internal protocol of the translator.
  • the process may then send (at 930 ) the operation to the core.
  • the process may then identify (at 940 ) a device from the device list and identify (at 950 ) the service associated with the device.
  • Process 900 may then send (at 970 ) the operation to the identified service. Finally, the process may send (at 980 ) the operation from the service to the IoT device and then may end.
  • processes 700 - 900 are exemplary and different embodiments may be implemented in different ways without departing from the scope of the disclosure. For instance, some embodiments may perform the operations in different orders, may omit various operations, and/or may include additional operations. As another example, some operations and/or sets of operations may be performed iteratively (e.g., as when relaying a series of commands from a user device to an IoT device). In addition, the processes may be divided into multiple sub-processes and/or combined with other processes or operations in a larger macro process. Furthermore, the processes may be executed by various different physical devices (and/or sets of devices).
  • Many of the processes and modules described above may be implemented as software processes that are specified as one or more sets of instructions recorded on a non-transitory storage medium.
  • these instructions are executed by one or more computational element(s) (e.g., microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.) the instructions cause the computational element(s) to perform actions specified in the instructions.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field programmable gate arrays
  • various processes and modules described above may be implemented completely using electronic circuitry that may include various sets of devices or elements (e.g., sensors, logic gates, analog to digital converters, digital to analog converters, comparators, etc.). Such circuitry may be able to perform functions and/or features that may be associated with various software elements described throughout.
  • FIG. 10 illustrates a schematic block diagram of an exemplary computer system 1000 used to implement some embodiments.
  • the system described above in reference to FIG. 1 may be at least partially implemented using computer system 1000 .
  • the communication structure described in reference to FIG. 6 and/or processes described in reference to FIGS. 7-9 may be at least partially implemented using sets of instructions that are executed using computer system 1000 .
  • Computer system 1000 may be implemented using various appropriate devices.
  • the computer system may be implemented using one or more personal computers (PCs), servers, mobile devices (e.g., a smartphone), tablet devices, and/or any other appropriate devices.
  • the various devices may work alone (e.g., the computer system may be implemented as a single PC) or in conjunction (e.g., some components of the computer system may be provided by a mobile device while other components are provided by a tablet device).
  • computer system 1000 may include at least one communication bus 1005 , one or more processors 1010 , a system memory 1015 , a read-only memory (ROM) 1020 , permanent storage devices 1025 , input devices 1030 , output devices 1035 , audio processors 1040 , video processors 1045 , various other components 1050 , and one or more network interfaces 1055 .
  • processors 1010 may include at least one communication bus 1005 , one or more processors 1010 , a system memory 1015 , a read-only memory (ROM) 1020 , permanent storage devices 1025 , input devices 1030 , output devices 1035 , audio processors 1040 , video processors 1045 , various other components 1050 , and one or more network interfaces 1055 .
  • ROM read-only memory
  • Bus 1005 represents all communication pathways among the elements of computer system 1000 . Such pathways may include wired, wireless, optical, and/or other appropriate communication pathways.
  • input devices 1030 and/or output devices 1035 may be coupled to the system 1000 using a wireless connection protocol or system.
  • the processor 1010 may, in order to execute the processes of some embodiments, retrieve instructions to execute and/or data to process from components such as system memory 1015 , ROM 1020 , and permanent storage device 1025 . Such instructions and data may be passed over bus 1005 .
  • System memory 1015 may be a volatile read-and-write memory, such as a random access memory (RAM).
  • the system memory may store some of the instructions and data that the processor uses at runtime.
  • the sets of instructions and/or data used to implement some embodiments may be stored in the system memory 1015 , the permanent storage device 1025 , and/or the read-only memory 1020 .
  • ROM 1020 may store static data and instructions that may be used by processor 1010 and/or other elements of the computer system.
  • Permanent storage device 1025 may be a read-and-write memory device.
  • the permanent storage device may be a non-volatile memory unit that stores instructions and data even when computer system 1000 is off or unpowered.
  • Computer system 1000 may use a removable storage device and/or a remote storage device as the permanent storage device.
  • Input devices 1030 may enable a user to communicate information to the computer system and/or manipulate various operations of the system.
  • the input devices may include keyboards, cursor control devices, audio input devices and/or video input devices.
  • Output devices 1035 may include printers, displays, audio devices, etc. Some or all of the input and/or output devices may be wirelessly or optically connected to the computer system 1000 .
  • Audio processor 1040 may process and/or generate audio data and/or instructions.
  • the audio processor may be able to receive audio data from an input device 1030 such as a microphone.
  • the audio processor 1040 may be able to provide audio data to output devices 1040 such as a set of speakers.
  • the audio data may include digital information and/or analog signals.
  • the audio processor 1040 may be able to analyze and/or otherwise evaluate audio data (e.g., by determining qualities such as signal to noise ratio, dynamic range, etc.).
  • the audio processor may perform various audio processing functions (e.g., equalization, compression, etc.).
  • the video processor 1045 may process and/or generate video data and/or instructions.
  • the video processor may be able to receive video data from an input device 1030 such as a camera.
  • the video processor 1045 may be able to provide video data to an output device 1040 such as a display.
  • the video data may include digital information and/or analog signals.
  • the video processor 1045 may be able to analyze and/or otherwise evaluate video data (e.g., by determining qualities such as resolution, frame rate, etc.).
  • the video processor may perform various video processing functions (e.g., contrast adjustment or normalization, color adjustment, etc.).
  • the video processor may be able to render graphic elements and/or video.
  • Other components 1050 may perform various other functions including providing storage, interfacing with external systems or components, etc.
  • computer system 1000 may include one or more network interfaces 1055 that are able to connect to one or more networks 1060 .
  • computer system 1000 may be coupled to a web server on the Internet such that a web browser executing on computer system 1000 may interact with the web server as a user interacts with an interface that operates in the web browser.
  • Computer system 1000 may be able to access one or more remote storages 1070 and one or more external components 1075 through the network interface 1055 and network 1060 .
  • the network interface(s) 1055 may include one or more APIs that may allow the computer system 1000 to access remote systems and/or storages and also may allow remote systems and/or storages to access computer system 1000 (or elements thereof).
  • non-transitory storage medium is entirely restricted to tangible, physical objects that store information in a form that is readable by electronic devices. These terms exclude any wireless or other ephemeral signals.
  • modules may be combined into a single functional block or element.
  • modules may be divided into multiple modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer And Data Communications (AREA)
  • User Interface Of Digital Computer (AREA)
  • Mobile Radio Communication Systems (AREA)
US15/298,379 2016-03-22 2016-10-20 Universal internet of things (iot) smart translator Abandoned US20170279894A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US15/298,379 US20170279894A1 (en) 2016-03-22 2016-10-20 Universal internet of things (iot) smart translator
CN201611196972.8A CN107222454A (zh) 2016-03-22 2016-12-22 通用物联网（IoT）智能转换器
PCT/US2017/020838 WO2017165105A1 (en) 2016-03-22 2017-03-04 Universal internet of things (iot) smart translator
US15/655,717 US10003654B2 (en) 2016-03-22 2017-07-20 Universal internet of things (IoT) smart translator

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662311729P 2016-03-22 2016-03-22
US15/298,379 US20170279894A1 (en) 2016-03-22 2016-10-20 Universal internet of things (iot) smart translator

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/655,717 Continuation US10003654B2 (en) 2016-03-22 2017-07-20 Universal internet of things (IoT) smart translator

Publications (1)

Publication Number Publication Date
US20170279894A1 true US20170279894A1 (en) 2017-09-28

Family

ID=59898270

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/298,379 Abandoned US20170279894A1 (en) 2016-03-22 2016-10-20 Universal internet of things (iot) smart translator
US15/655,717 Expired - Fee Related US10003654B2 (en) 2016-03-22 2017-07-20 Universal internet of things (IoT) smart translator

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/655,717 Expired - Fee Related US10003654B2 (en) 2016-03-22 2017-07-20 Universal internet of things (IoT) smart translator

Country Status (3)

Country Link
US (2) US20170279894A1 (zh)
CN (1) CN107222454A (zh)
WO (1) WO2017165105A1 (zh)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170031333A1 (en) * 2015-07-31 2017-02-02 Arm Ip Limited Managing interaction constraints
US20170374490A1 (en) * 2016-06-22 2017-12-28 Intel Corporation Internet of things protocol handler
US20180034914A1 (en) * 2016-07-29 2018-02-01 American Megatrends, Inc. System and method for controlling heterogeneous internet of things (iot) devices using single application
CN108040051A (zh) * 2017-12-12 2018-05-15 开放物联（北京）科技发展有限公司 一种可配置的物联网网关协议转换方法
EP3474131A1 (en) * 2017-10-19 2019-04-24 Libre Wireless Technologies, Inc. Multiprotocol audio7voice internet-of-things devices and related systems
WO2019112734A1 (en) * 2017-12-06 2019-06-13 Intel Corporation Plugin management for internet of things (iot) network optimization
US10419385B2 (en) * 2017-12-11 2019-09-17 Mastercard International Incorporated Systems and methods for use in transmitting electronic messages between different protocols
US20200021670A1 (en) * 2016-12-27 2020-01-16 Intel IP Corporation Framework for iot protocol identification and management
EP3657732A4 (en) * 2017-10-18 2020-07-29 Samsung Electronics Co., Ltd. ELECTRONIC DEVICE CONTROL SYSTEM FOR CONTROL OF AN ELECTRONIC DEVICE, AND METHOD OF ELECTRONIC DEVICE CONTROL
US11026063B2 (en) 2017-10-19 2021-06-01 Libre Wireless Technologies Inc. Internet-of-things devices and related methods for performing in-call interactions
US11038966B1 (en) 2020-04-28 2021-06-15 Arm Ip Limited Remote device operation
US11133857B2 (en) * 2017-03-29 2021-09-28 Intel Corporation Relay selection for communication in multi-rat environment
US20210397526A1 (en) * 2020-06-18 2021-12-23 General Electric Company Systems and methods of providing an abstraction layer between an application layer and hardware components of a computing device
EP3924808A4 (en) * 2019-02-14 2022-10-26 Fluence Bioengineering, Inc. CONTROLLED AGRICULTURAL SYSTEMS AND METHODS FOR MANAGING AGRICULTURAL SYSTEMS
US11663414B2 (en) 2018-02-20 2023-05-30 Fluence Bioengineering, Inc. Controlled agricultural systems and methods of managing agricultural systems

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017172993A1 (en) 2016-03-29 2017-10-05 Resolution Products, Inc. Universal protocol translator
EP3634018A1 (en) * 2018-10-02 2020-04-08 Siemens Aktiengesellschaft System for data communication in a network of local devices
CN111031138B (zh) * 2019-12-19 2022-08-05 青岛海尔科技有限公司 物联网的通信方法和装置及计算机可读存储介质
US20230086979A1 (en) * 2020-02-20 2023-03-23 Huawei Technologies Co., Ltd. Integration of Internet of Things Devices
TWI810523B (zh) * 2020-03-12 2023-08-01 日商愛德萬測試股份有限公司 自動測試裝備系統及設備、以及用於測試受測裝置的方法
CN114051219A (zh) * 2021-11-12 2022-02-15 中国电力科学研究院有限公司 一种边缘节点无线传感器连接方法及系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010052031A1 (en) * 2000-01-14 2001-12-13 Information Design Inc. Uniform application programming interface for messaging middleware
US8005937B2 (en) * 2004-03-02 2011-08-23 Fatpot Technologies, Llc Dynamically integrating disparate computer-aided dispatch systems
US7305289B2 (en) * 2004-05-28 2007-12-04 Spx Corporation Universal translator for vehicle information
US7715433B2 (en) * 2006-07-14 2010-05-11 Boren Gary W Universal controller and signal monitor
WO2012145715A2 (en) * 2011-04-22 2012-10-26 Expanergy,Llc. Systems and methods for analyzing energy usage
WO2013123445A1 (en) * 2012-02-17 2013-08-22 Interdigital Patent Holdings, Inc. Smart internet of things services
US9413827B2 (en) * 2013-02-25 2016-08-09 Qualcomm Incorporated Context aware actions among heterogeneous internet of things (IOT) devices
WO2014164538A1 (en) * 2013-03-12 2014-10-09 Tait Towers Manufacturing, LLC Universal translator for an automation and motion control system
CN105453047B (zh) * 2013-05-06 2019-12-10 康维达无线有限责任公司 提供物联网(iot)适配服务的系统和方法
KR101560470B1 (ko) * 2014-01-07 2015-10-16 한국과학기술원 스마트 연결 장치 및 스마트 연결 장치를 활용하여 ＩｏＴ 장치를 제어하기 위한 방법
US9111214B1 (en) * 2014-01-30 2015-08-18 Vishal Sharma Virtual assistant system to remotely control external services and selectively share control
EP2950510B1 (en) * 2014-05-28 2018-07-11 Samsung Electronics Co., Ltd Apparatus and method for controlling internet of things devices
US10009707B2 (en) * 2014-07-22 2018-06-26 Convida Wireless, Llc Interworking light weight machine-to-machine protocol with device management protocol
US9210534B1 (en) * 2015-02-19 2015-12-08 Citrix Systems, Inc. Location assistance in a machine to machine instant messaging system
US10572296B2 (en) * 2015-02-27 2020-02-25 Savi Technology, Inc. System and method for a data processing architecture
US10425811B2 (en) * 2015-08-24 2019-09-24 Ayla Networks, Inc. Linked user accounts for an internet-of-things platform
US20170060911A1 (en) * 2015-08-31 2017-03-02 Synchronoss Technologies, Inc. Systems and Methods For an Open System Internet of Things Data Hub
US10110697B2 (en) * 2015-10-28 2018-10-23 Adobe Systems Incorporated Environmental detection of internet of things devices
US10681027B2 (en) * 2016-01-19 2020-06-09 Honeywell International Inc. Gateway mechanisms to associate a contractor account
US20170237623A1 (en) * 2016-02-15 2017-08-17 Kilton Patrick Hopkins Methods and apparatus for unified integration and processing of a variety of information sensors and systems

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170031333A1 (en) * 2015-07-31 2017-02-02 Arm Ip Limited Managing interaction constraints
US11218855B2 (en) * 2015-07-31 2022-01-04 Arm Ip Limited Managing interaction constraints
US20170374490A1 (en) * 2016-06-22 2017-12-28 Intel Corporation Internet of things protocol handler
US10299091B2 (en) * 2016-06-22 2019-05-21 Intel Corporation Internet of things protocol handler
US20180034914A1 (en) * 2016-07-29 2018-02-01 American Megatrends, Inc. System and method for controlling heterogeneous internet of things (iot) devices using single application
US10834586B2 (en) * 2016-07-29 2020-11-10 Amzetta Technologies, Llc System and method for controlling heterogeneous internet of things (IoT) devices using single application
US11076024B2 (en) * 2016-12-27 2021-07-27 Intel Corporation Framework for IoT protocol identification and management
US11770459B2 (en) * 2016-12-27 2023-09-26 Intel Corporation Framework for IoT protocol identification and management
US20220109743A1 (en) * 2016-12-27 2022-04-07 Intel Corporation Framework for iot protocol identification and management
US20200021670A1 (en) * 2016-12-27 2020-01-16 Intel IP Corporation Framework for iot protocol identification and management
US11133857B2 (en) * 2017-03-29 2021-09-28 Intel Corporation Relay selection for communication in multi-rat environment
EP3657732A4 (en) * 2017-10-18 2020-07-29 Samsung Electronics Co., Ltd. ELECTRONIC DEVICE CONTROL SYSTEM FOR CONTROL OF AN ELECTRONIC DEVICE, AND METHOD OF ELECTRONIC DEVICE CONTROL
JP2019087994A (ja) * 2017-10-19 2019-06-06 リブレ ワイヤレス テクノロジーズ インコーポレイテッドＬｉｂｒｅ Ｗｉｒｅｌｅｓｓ Ｔｅｃｈｎｏｌｏｇｉｅｓ， Ｉｎｃ． マルチプロトコルオーディオ／音声ＩｏＴ機器及び関連システム
US11026063B2 (en) 2017-10-19 2021-06-01 Libre Wireless Technologies Inc. Internet-of-things devices and related methods for performing in-call interactions
US10887123B2 (en) 2017-10-19 2021-01-05 Libre Wireless Technologies, Inc. Multiprotocol audio/voice internet-of-things devices and related system
EP3474131A1 (en) * 2017-10-19 2019-04-24 Libre Wireless Technologies, Inc. Multiprotocol audio7voice internet-of-things devices and related systems
JP7410640B2 (ja) 2017-10-19 2024-01-10 リブレ ワイヤレス テクノロジーズ インコーポレイテッド マルチプロトコルオーディオ／音声ＩｏＴ機器及び関連システム
WO2019112734A1 (en) * 2017-12-06 2019-06-13 Intel Corporation Plugin management for internet of things (iot) network optimization
US11483418B2 (en) * 2017-12-06 2022-10-25 Intel Corporation Plugin management for internet of things (IoT) network optimization
US10419385B2 (en) * 2017-12-11 2019-09-17 Mastercard International Incorporated Systems and methods for use in transmitting electronic messages between different protocols
CN108040051A (zh) * 2017-12-12 2018-05-15 开放物联（北京）科技发展有限公司 一种可配置的物联网网关协议转换方法
US11663414B2 (en) 2018-02-20 2023-05-30 Fluence Bioengineering, Inc. Controlled agricultural systems and methods of managing agricultural systems
EP3924808A4 (en) * 2019-02-14 2022-10-26 Fluence Bioengineering, Inc. CONTROLLED AGRICULTURAL SYSTEMS AND METHODS FOR MANAGING AGRICULTURAL SYSTEMS
US11038966B1 (en) 2020-04-28 2021-06-15 Arm Ip Limited Remote device operation
US20210397526A1 (en) * 2020-06-18 2021-12-23 General Electric Company Systems and methods of providing an abstraction layer between an application layer and hardware components of a computing device

Also Published As

Publication number Publication date
US10003654B2 (en) 2018-06-19
US20180115612A1 (en) 2018-04-26
WO2017165105A1 (en) 2017-09-28
CN107222454A (zh) 2017-09-29

Similar Documents

Publication Publication Date Title
US10003654B2 (en) Universal internet of things (IoT) smart translator
AU2016301394B2 (en) Managing a device cloud
EP3389230B1 (en) System for providing dialog content
AU2016335997B2 (en) Cloud-synchronized architecture for a home automation system
CN105471686B (zh) 终端控制方法、装置及系统
KR101924163B1 (ko) Hdmi 소스의 출력을 관리하기 위한 방법들, 시스템들 및 매체들
EP3128476A1 (en) Managing a device cloud
KR102636605B1 (ko) 어시스턴트 클라이언트 장치에 의해 로컬로 스마트 장치 제어 및/또는 등록
WO2018137521A1 (zh) 虚拟场景交互客户端中语音直播的实现方法、装置及存储介质
KR20160019087A (ko) 미디어 컨텐츠를 제시하기 위한 시스템들, 방법들 및 컴퓨터 판독 가능 매체들
WO2020168568A1 (zh) 数据处理方法、装置、电子设备及可读存储介质
US11122318B2 (en) Methods and systems for implementing legacy remote and keystroke redirection
KR102203757B1 (ko) 자막기능을 지원하는 컨텐츠 수신장치와 디스플레이장치, 그것을 구비하는 시스템 및 그 자막 제공방법
CN112929246B (zh) 操作指令的处理方法、存储介质及用户终端
CN111028839B (zh) 一种智能家居控制方法、装置及电子设备
WO2016150191A1 (zh) 一种数据共享方法及装置
JP2021121564A (ja) エレベータ制御方法、装置、電子機器、記憶媒体及びシステム
US20160088328A1 (en) Password protected stream receivers
US10298879B2 (en) Method and system for switching a push-based video call between devices in a group
US11575793B2 (en) Service system supporting voice call using digital assistant device, method thereof, and non-transitory computer readable medium having computer program recorded thereon
US20240028315A1 (en) Automatically Creating Efficient Meshbots
KR102676627B1 (ko) 어시스턴트 클라이언트 장치에 의해 로컬로 스마트 장치 제어 및/또는 등록
US11937085B2 (en) Methods, systems, and media for creating temporary virtual access points using WiFi routers when portals cannot be presented
US20220413882A1 (en) Operating environment personalizations
US20240064883A1 (en) Requesting a lighting device to control other lighting devices to render light effects from a light script

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION