Virtual models for access/control of internet of things (IoTs) devices

A network device enables browsing of a plurality of pre-defined VMs associated with IoT devices. The network device receives, from a user device, selection of a first pre-defined VM from the plurality of pre-defined VMs, wherein the first pre-defined VM includes at least one first device state and at least one first sensor type, and receives, from the user device, instructions to modify the first pre-defined VM, by adding an additional device state or an additional sensor type to the first pre-defined VM or by removing the at least one first device state or the at least one first sensor type from the first pre-defined VM, to create a first customized VM associated with a first physical IoT device. The network device stores the first customized VM in a database, and uses the first customized VM for accessing or controlling the first physical IoT device.

BACKGROUND

The “Internet of Things” (IoT) is a network of physical devices (i.e., “things”) specially designed for a specific function, unlike general computing devices like desktop or laptop computers. IoT devices are embedded with electronics and network connectivity that enable these devices to collect, store and exchange data. The network connectivity may include, for example, Bluetooth™ connectivity, Wi-Fi connectivity, and/or cellular network connectivity. An IoT device may additionally have computational capability, with various installed software (e.g., apps), and may also include one or more of various types of sensors. An IoT device may be, via the network connectivity, controlled remotely across existing network infrastructure. An IoT device may use the network connectivity to communicate with other IoT devices, or with certain nodes (e.g., a particular server or computer) across the Internet.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Exemplary embodiments described herein use virtual models (VMs) to abstract the behavior of physical IoT devices and to provide a unified way to access and/or control the IoT devices. Through the use of VMs, heterogeneous physical IoT devices are normalized under well defined VMs such that user device applications are able to interact with the IoT devices in a normalized way regardless of the Original Equipment Manufacturer's (OEM's) hardware implementation. Through the use of VMs for IoT device access and control, customized VMs may be created that enable new and different types of physical IoT devices, having different types of functionality, to be accessed and controlled via the customized VMs. A thingspace platform may provide network functionality for user devices to create customized VMs and store those VMs in a database for future use. The pre-defined VMs used herein may include generic VMs for certain types of IoT devices, or for well-known vendor models, in addition to customized VMs created by different users for their particular IoT device(s).

FIGS. 1A and 1Billustrate an exemplary overview of the creation, and use of, Thing Virtual Models (VMs) for accessing and controlling physical IoT devices in a network environment.FIG. 1Adepicts a user device100creating and/or selecting a VM, via a thingspace platform105, for a particular physical IoT device for storing in a thing VM database (DB)110. The physical IoT device(s) may also be registered, in IoT Registered device DB145, in association with the selected/created VM. Subsequent to storage in thing VM DB110, the created/selected VMs may be used for accessing and controlling one or more IoT devices.

As shown inFIG. 1A, a user device100may execute an IoT virtual model (VM) app115to permit a user (not shown) of user device100to browse, via a thing VM browser120, VMs and/or subcomponents of VMs to create and/or select125a VM for associating with a particular IoT device of IoT devices130-1through130-n. IoT VM app105may include software and/or hardware that enables the user of user device100to display, via, for example, a graphical user interface, pre-defined VMs and/or pre-defined subcomponents of VMs for selection by a user of user device100to create a customized VM for a particular physical IoT device(s). In one implementation, thing VM browser120may include software and/or hardware which interacts with IoT VM app115to enable the user of user device100to browse a catalog of pre-defined VMs and/or pre-defined components of VMs135for selection when creating a customized VM. In another implementation, thing VM browser120may include software and/or hardware at user device100(e.g., a web browser). The software and/or hardware enables user device100to download software and/or documents, from thingspace platform105, that includes pre-defined VMs and/or pre-defined subcomponents of VMs135. The downloaded software and/or documents may be used by the user of user device100for selecting pre-defined VMs and/or pre-defined subcomponents of VMs for creating a customized VM.

The selected/created VM may include a previously created, pre-defined VM that may be selected, including all of its pre-defined subcomponents, by the user of user device100for association with a particular physical IoT device(s). The selected/created VM may also include one or more pre-defined individual subcomponents of VMs that may be selected by the user of user device100for creating a customized VM. To enable the user of user device100to browse pre-defined VMs and/or pre-defined components of VMs, thingspace platform105retrieves VM information, including the pre-defined VMs and pre-defined VM subcomponents135, from thing VM DB110for presentation via user device100as a catalog. The user of user device105may, via IoT VM app115and/or thing VM browser120, browse through the catalogued VM information to select an appropriate VM, or one or more subcomponents of a VM, to create a custom VM for one or more physical IoT devices.

FIG. 1Billustrates an exemplary overview of the use of thing VMs for accessing and controlling physical IoT devices in a network environment. As shown inFIG. 1B, an IoT access/control app140, executing at user device100, may use one or more Application Programming Interfaces (APIs)150to send commands to thingspace platform105for accessing data at one or more of IoT devices130-1through130-nand/or for controlling some aspect of the operation of one or more of IoT devices130-1through130-n. Thingspace platform105may use IoT registered device DB145and thing VM DB110, to retrieve an appropriate thing VM(s)160and, based on the commands received via APIs150and based on the retrieved thing VM(s)160, may send access and/or control signaling155-1through155-nto respective ones of IoT devices130-1through130-n. Thingspace platform105may return messaging (not shown inFIG. 1B) to user device100that includes data accessed at IoT device(s)130(e.g., sensor data), and/or data acknowledging control over the aspect of the operation of IoT device(s)130.

FIG. 1Cdepicts an exemplary implementation of thing VM160. Thing VM160may include a thing VM name165, thing VM subcomponents170, and thing VM APIs175. Thing VM name165includes a name or identifier that uniquely identifies thing VM160. The name or identifier may include alphanumeric characters in any combination, and may additionally include various other types of symbols (e.g., *, &, %, or # symbols). Thing VM subcomponents170may include data and one or more generalized software mechanisms for accessing and/or controlling a physical IoT device. Thing VM subcomponents170include one or more thing VM device states180, and one or more thing VM sensor types185.

Thing VM device states180include generalized software mechanisms that specify one or more operational states of the physical IoT device with which the thing VM may be associated, where each device state may be defined by one or more parameters that may each have one or more discrete values, or a range of continuous values. The device states may include, for example, a brightness state, a longitude state, an altitude state, a latitude state, a time state, a temperature state, a distance state, etc. For example, an IoT device may be a “smart light” and may have a device state of “brightness.” A color parameter (e.g., red, green, blue) and a light intensity parameter (0 to 100, low to high intensity) may be associated with the “brightness” device state. The device states of a thing VM may include any type of state associated with measurements performed by sensors at a physical IoT device, or any type of device state associated with the operation of a physical IoT device.

Thing VM sensor types185include data and software mechanisms for specifying the one or more types of sensors of a physical IoT device with which the thing VM may be associated. The data and software mechanisms further specify the parameter(s) to be sensed and/or measured at the type of sensor, and include mechanisms for accessing data associated with the sensed and/or measured parameter(s) and mechanisms for controlling the operation of the one or more types of sensors.

Thing VM APIs175may include one or more APIs associated with implementing the thing VM to access data at, and/or control the operation of, a physical IoT device associated with the particular thing VM. For example, the one or more APIs may include APIs for specifying parameters of device states of the thing VM. As another example, the one or more APIs may include APIs for requesting measured data from sensors associated with the sensor types of the thing VM160.

FIG. 2illustrates an exemplary network environment200in which thing VMs are created, and subsequently used for accessing and controlling physical IoT devices. Network environment200may include user device100, thingspace platform105, thing VM DB110, IoT devices130-1through130-n, IoT registered device DB145, and network(s)210.

User device100includes an electronic device that further includes a communication interface (e.g., wired or wireless) for communicating via network(s)210. User device100may include, for example, a cellular radiotelephone; a smart phone; a personal digital assistant (PDA); a wearable computer; a desktop, laptop, palmtop or tablet computer; or a media player. User device100may, however, include any type of electronic device that includes a communication interface for communicating via network(s)210. A “user” (not shown inFIG. 2) may be associated with user device100, where the user may be an owner, operator, and/or a permanent or temporary user of user device100. As shown, user device100may execute IoT VM app115and/or IoT access/control app140, described above with respect toFIGS. 1A and 1B.

Thingspace platform105includes one or more network devices that enable user device100to select/create a VM for one or more of IoT devices130-1through130-n, to register the one or more of IoT devices130-1through130-nin IoT registered device DB145, and to store the selected/created VM in thing VM DB110for future retrieval and use in accessing/controlling the one or more registered IoT devices130-1through130-n.

Thing VM DB110includes one or more network devices that store a data structure(s) that enables the storage and retrieval of VMs for associating with and/or registering with one or more physical IoT devices and for accessing data at, or controlling the operation of, the one or more physical IoT devices via use of the VMs. Thing VM DB110may additionally store one or more APIs for use in accessing data at, or controlling the operation of, the one or more physical IoT devices.

IoT devices130-1through130-n(generically referred to herein as “IoT device130” or “IoT devices130”) each include a physical object or device (i.e., a “thing”) that may be designed for a specific function and which may be embedded with electronics, memory storage, and network connectivity that enables these objects or devices to collect, store and exchange data with other IoT devices or with certain network nodes. Each device130's network connectivity may include, for example, Bluetooth™ connectivity, Wi-Fi connectivity, and/or cellular network connectivity.

IoT registered device DB145includes one or more network devices that store a data structure(s) that enables the storage and retrieval of account information for a particular user of a user device100, including an account identifier (ID), information for uniquely identifying one or more IoT devices, and a name of the VM to be used for accessing and/or controlling the identified one or more IoT devices.

Network(s)210may include one or more networks of various types including, for example, a public land mobile network (PLMN) (e.g., a Code Division Multiple Access (CDMA) 2000 PLMN, a Global System for Mobile Communications (GSM) PLMN, a Long Term Evolution (LTE) PLMN and/or other types of PLMNs), a satellite mobile network, a telecommunications network (e.g., Public Switched Telephone Networks (PSTNs)), a wired and/or wireless local area network (LAN), a wired and/or wireless wide area network (WAN), a metropolitan area network (MAN), an intranet, the Internet, or a cable network (e.g., an optical cable network). In one implementation, network(s)210may include a PLMN or satellite mobile network connected to the Internet. In another implementation, network(s)210may include a fixed network (e.g., an optical cable network) connected to the Internet.

The configuration of the components of network environment200depicted inFIG. 2is for illustrative purposes only, and other configurations may be implemented. Therefore, network environment200may include additional, fewer and/or different components, that may be configured differently, than depicted inFIG. 2. For example, though a single user device100is depicted inFIG. 2, multiple different user devices100may connect to network(s)210, with each of the user devices100possibly being associated with a different user.

FIG. 3is a diagram that depicts exemplary components of a computational device300(referred to herein as “device300”). User device100, thingspace platform105, IoT device130, thing VM DB110, and IoT registered device DB145may each be configured similarly to device300, possibly with some variations in components and/or configuration. Device300may include a bus310, a processing unit320, a main memory330, a read only memory (ROM)340, a storage device350, an input device(s)360, an output device(s)370, and a communication interface(s)380.

Bus310may include a path that permits communication among the components of device300. Processing unit320may include one or more processors or microprocessors, or processing logic, which may interpret and execute instructions. Main memory330may include a random access memory (RAM) or another type of dynamic storage device that may store information and instructions for execution by processing unit320. ROM340may include a ROM device or another type of static storage device that may store static information and instructions for use by processing unit320. Storage device350may include a magnetic and/or optical recording medium. Main memory330, ROM340and storage device350may each be referred to herein as a “tangible non-transitory computer-readable medium.”

Input device360may include one or more mechanisms that permit an operator to input information to device300, such as, for example, a keypad or a keyboard, a display with a touch sensitive panel, voice recognition and/or biometric mechanisms, etc. Output device370may include one or more mechanisms that output information to the operator or user, including a display, a speaker, etc. Input device360and output device370may, in some implementations, be implemented as a graphical user interface (GUI) that displays GUI information and which receives user input via the GUI. In an instance where device300is user device100, the GUI of input device360and output device370may include a touch screen GUI that uses any type of touch screen device. Communication interface(s)380may include a transceiver that enables device300to communicate with other devices and/or systems. For example, communication interface(s)380may include wired and/or wireless transceivers for communicating via network(s)210.

The configuration of components of device300shown inFIG. 3is for illustrative purposes. Other configurations may be implemented. Therefore, device300may include additional, fewer and/or different components, arranged in a different configuration, than depicted inFIG. 3. For example, an IoT device130may include similar components to those shown inFIG. 3, but may omit input device(s)360, output device(s)370, and storage device350.

FIG. 4is a diagram that depicts an exemplary implementation of thing VM DB110. As shown, a data structure of DB110may include multiple entries400, with each entry400including a thing VM name(s) field410, a thing VM attributes field420, and a thing VM APIs field430.

Thing VM name(s) field410stores a unique name identifier associated with a particular thing VM. Thing VM attributes field420stores attributes of a particular thing VM including, among other data, information that specifies one or more subcomponents of the thing VM. For example, the subcomponents may include one or more device states and one or more sensor types. Thing VM APIs field430stores one or more APIs, for a particular VM, for use by a user device100in accessing data at an IoT device(s) and/or controlling the operation of the IoT device(s).

To locate a particular entry of thing VM DB110, DB110may be indexed with, for example, a thing VM name to locate an entry400having a matching thing VM name stored in field410. When such an entry400is located, data may be stored in one or more fields420and/or430of the entry400, or data may be retrieved from one or more fields420and/or430of the entry400. Other fields of an entry400, instead of thing VM name(s) field410, may be used for indexing DB110.

FIG. 5is a diagram that depicts an exemplary implementation of IoT Registered Device DB145. As shown, a data structure of DB145may include multiple entries500, with each entry500including an account ID field510, a thing VM name field520, an IoT device ID(s) field530, and a label(s) field540.

Account ID field510stores a unique account identifier associated with a particular user. The unique account identifier may, for example, include the mobile telephone number of the particular user. Any type of unique ID, however, may be used for identifying the user account. Thing VM name field520stores an identifier of the particular VM to be associated with the IoT devices identified in field530. The VM name identifier may be alphabetic, numeric, alphanumeric, or symbolic, or any combination of such identifiers. The VM name stored in field520corresponds to a VM, with a matching VM name stored in field410of thing VB DB110.

IoT device ID(s) field520stores unique identifiers of each physical IoT device that is associated, in entry500, with the account ID and the identified VM. In one implementation, each unique identifier may include a network address (e.g., Internet Protocol (IP) address) associated with a particular physical IoT device. Label(s) field530stores a label for identifying the combination of the account ID in field510, the thing VM name in field520, and the IoT devices identified in field530. The label stored in field530, thus, represents a type of “short hand” identifier for an identified group of IoT devices affiliated with a particular account, and associated with a particular VM that is used for accessing and/or controlling the devices of the group of IoT devices.

To locate a particular entry of thing IoT registered device DB145, DB145may be indexed with, for example, an IoT device ID to locate an entry500having a matching IoT device ID stored in field530. When such an entry500is located, data may be stored in one or more fields510,520,530and/or540of the entry500, or data may be retrieved from one or more fields510,520,530and/or540of the entry500. Other fields of an entry500, instead of thing IoT device ID(s) field530, may be used for indexing DB145.

VM DB110and IoT registered device DB145are depicted inFIGS. 4 and 5as including tabular data structures with certain numbers of fields having certain content. The tabular data structures of DBs110and145shown inFIGS. 4 and 5, however, are for illustrative purposes. Other types of data structures may alternatively be used. The number, types, and content of the entries and/or fields in the data structures of DBs110and145illustrated inFIGS. 4 and 5are also for illustrative purposes. Other data structures having different numbers of, types of and/or content of, the entries and/or the fields may be implemented. Therefore, VM DB110and IoT registered device DB145may include additional, fewer and/or different entries and/or fields than those depicted inFIGS. 4 and 5. In one implementation, use of thing VMs stored in thing VM DB110may be restricted to the owner of the account ID that originally created the thing VMs and registered it in IoT registered device DB145. In other implementations, the owner of the account ID may, at the time of creation of a particular VM, permit the VM to be “published” and made publicly available to other users in a global context. Such publicly available VMs may be, based on a user scoring system as to the quality of each of the VMs, promoted (i.e., ranked higher than other VMs within a ranked list) within a catalog of VMs provided to a user selecting and/or creating a VM for association with one or more physical IoT devices. Once a given VM is allowed by its creator to be globally published, the creator may no longer be able to edit the VM.

FIGS. 6A and 6Bare flow diagrams that illustrate an exemplary process for selecting and/or creating a thing VM for association with one or more physical IoT devices, and for registering the one or more physical IoT devices in conjunction with the selected/created thing VM. The exemplary process ofFIGS. 6A and 6Bmay be implemented by user device100, in conjunction with thingspace platform105, thing VM DB110, and IoT registered device DB145.

The exemplary process includes IoT VM app115retrieving, from thingspace platform105, virtual model information and attributes of pre-defined virtual models (block600). IoT VM app115requests VM information from thingspace platform105which, in turn, retrieves pre-defined VM information from thing VM DB110. For example, thingspace platform105may retrieve the contents of fields410and420for each entry400of DB110that is considered to be publicly available (i.e., globally available to all users), and format the retrieved DB contents into an easily viewable/readable VM catalog document.FIG. 7depicts IoT VM app115of user device100retrieving700VM information from thingspace platform105, and thingspace platform further retrieving703the requested VM information from thing VM DB110. Thingspace platform105returns the requested VM information to IoT VM app115at user device100.

App115displays a catalog of pre-defined virtual models, including virtual model information and attributes, for browsing and selection (block605). IoT VM app115receives the formatted VM catalog document from thingspace platform105, and displays the catalog document via a display of user device100. The catalog of pre-defined virtual models may include those VMs permitted to be “published” and available in a global context for use by all users. Based on a scoring system related to the quality and/or popularity of each published VM, the VMs, within the catalog document, may be ranked relative to one another, with an indication of quality and/or popularity being associated with each VM within the catalog. In one implementation, the VM catalog document may be displayed via a graphical user interface (GUI) at user device100, such as, for example, via a touch screen GUI.FIG. 13depicts IoT VM app115displaying705a catalog of pre-defined VMs for browsing and selection.

FIG. 8illustrates one example of a touch screen GUI800that enables the user of user device100to select a pre-defined thing VM type from a list of thing VM types. As shown, GUI800may display a scrollable list containing multiple different pre-defined thing VM types805-1through805-p(where p is a positive integer greater than one). Each displayed thing VM type may include a VM name810and a thing VM description820. The thing VM description820may contain (not shown) at least a brief description of the functionality of the thing type, and the attributes and/or parameters associated with the thing VM type. The thing VM types may include, but are not limited to, a smart light, a smart camera, a smart thermometer, a smart altimeter, a smart geo-location device, a clock (i.e., timer), a smart humidity sensor, a smart water sensor, a smart door sensor, a smart window sensor, a smart power usage sensor, a smart window shade sensor, a smart door lock sensor, a smart sound sensor, a smart smoke sensor, a smart light sensor, a smart sprinkler system, a smart contact sensor, a smart water usage sensor, a smart toothbrush usage sensor, a smart orientation sensor, a smart presence sensor, a smart vibration sensor, and a smart earthquake sensor. The thing VM types, however, may include a VM associated with any type of IoT device having any type of functionality.

The attributes may include one or more sensor types associated with the thing VM type, and one or more device states associated with the thing VM type. The one or more sensor types may include, but are not limited to, a thermometer, an altimeter, a geo-location device, a humidity sensor, a water sensor, a door sensor, a window sensor, a power usage sensor, a window shade sensor, a door lock sensor, a sound sensor, a smoke sensor, a light sensor, a motion sensor, a water usage sensor, an orientation sensor, a physical presence sensor, a vibration sensor, and an earthquake sensor. The one or more device states associated with the thing VM type may include, but are not limited to, a light brightness level, a latitude, a longitude, a color, and a distance-traveled alarm. The device states, however, may include any type of device state associated with any type of IoT device, including any type of monitorable and/or controllable device state of an IoT device.

App115determines if a selection of a virtual model from the displayed catalog has occurred (block610). Referring to the example ofFIG. 8, the user of user device100may select (e.g., touch) a specific pre-defined thing VM type805from the catalog of VM types displayed at user device100. As a specific example, the user of user device100may select “smart motion sensor” VM thing type805-2from GUI800of user device100. As another specific example, the user of user device100may select “smart vibration sensor” VM type805-4from GUI800of user device100.FIG. 7depicts three different exemplary methods of selecting/creating a customized VM for association with one or more physical IoT devices. In the first method (identified with a “1” within a circle), the user of user device100selects710an existing, pre-defined VM to be associated with the one or more IoT devices, and used “as is” (i.e., with no user modifications of the selected, pre-defined VM). In the second method (identified with a “2” within a circle), the user of user device100selects an existing, pre-defined VM, but then modifies the VM to add, or eliminate, one or more subcomponents or attributes to the VM. In the third method (identified with a “3” within a circle), the user of user device100selects one or more pre-defined subcomponents of a VM to create a new, custom VM. For example, the user of user device100may select one or more pre-defined device states and/or one or more pre-defined sensor types to compose a new, custom VM. If the user of user device100selects an existing, pre-defined VM for use in its entirety, or for modification, to create a VM for one or more physical IoT devices, the created VM would inherit all subcomponents of the selected parent VM, including all device states and sensors, via single inheritance.

If there has been a selection of a pre-defined virtual model (YES—block610), the exemplary process continues at block640with registration of one or more IoT devices to be associated with the selected pre-defined VM.FIG. 7depicts IoT VM app115at user device100sending740the device name(s) and label(s) for registration to thingspace platform105, and thingspace platform105registering745the device(s) in IoT registered device DB145.

If a pre-defined VM is not selected (NO—block610), the app115determines if the creation of a custom virtual model is selected (block615). If not (NO—block615), then the exemplary process may return to block605. If the creation of a custom virtual model is selected (YES—block615), then app115determines if the custom virtual model is to be created based on an existing VM, or based on an entirely new custom VM (block620). If the custom virtual model is to be created based on an existing VM (“EXISTING VM”—block620), then app115receives user input customizing one or more certain attributes of the selected, existing virtual model (block625). Customizing one or more attributes of the selected, existing virtual model may include adding one or more selected device states and/or sensor types, and/or may include deleting one or more selected device states and/or sensor types that were initially subcomponents of the existing virtual model.FIG. 7depicts IoT VM app115sending a selection715, of an existing VM to customize, to thingspace platform105, and IoT VM app115sending user input720that customizes certain attributes of the selected VM.

FIG. 9depicts an example of a GUI900displayed at user device100for customizing a selected, pre-defined virtual model. InFIG. 9, the user of user device100selects, in field905, an existing VM type, which in the particular example shown, is a “light” IoT device. Upon selection of a “light” VM type, the pre-defined device state types of “brightness”910, longitude915, and color920are presented in a “State Type” section925of GUI900. The pre-defined state types may be deleted from the virtual model by user selection of “deletion boxes”935. Touching, or “clicking on,” a “deletion box”935causes a corresponding device state to be deleted from the virtual model. Additional device states may be added to the virtual model via selection of “add another state” button940. Additionally, upon selection of the “light” VM type, a sensor type section930is presented which permits the user to “add sensors” to the virtual model by selecting particular “checkboxes” associated with each type of desired sensor type to be added. In the example shown, “temperature” and “motion” sensor types have been selected in selection930for adding to the virtual model. When modifications to the existing, pre-defined VM are completed, the user of user device100may enter a custom VM name in “Name” field945, an optional description of the virtual model in “Description” field950, and may then select the “Save” button955to cause the customized VM to be stored in thing VM DB110.

If the custom virtual model is to be created based entirely on a new, custom virtual model (“NEW CUSTOM VM”—block620), then app115receives user input that customizes attributes of a new virtual model (block630). For example, a GUI, similar to that shown inFIG. 8, may be presented to the user of user device100, with the list instead including a list of pre-defined VM subcomponents, such as, for example, a comprehensive list of different device states and/or a comprehensive list of different sensor types. The user may select one or more VM subcomponents from the list of pre-defined VM subcomponents to become part of the new, custom VM. For example, if the list includes device states device_state_1 through device_state_x, then one or more of the device states1through x may be selected from the list to become part of the new, custom VM. Additionally, if the list includes sensor types sensor_1 through sensor_y, then one or more of the sensor types1through y may be selected from the list to become part of the new, custom VM. Additionally, the GUI may enable the user of user device100to create entirely new VM subcomponents, such as entirely new device states and/or device sensor types. Creation of the custom VM may, therefore, include selections of one or more pre-defined VM subcomponents, and/or creation of one or more new VM subcomponents.

App115stores the custom/customized virtual model in thing VM DB110(block635). Thingspace platform105may store the name of the VM in thing VM name(s) field410, the custom/customized attributes in thing VM attributes420, and appropriate APIs for the VM in thing VM APIs field430of an entry of thing VM DB110.FIG. 7depicts thingspace platform105storing735the custom/customized VM in thing VM DB110.

App115determines whether a single IoT device is to be registered in association with the custom/customized virtual model (block640). The user of user device100may, via a user interface of user device100, enter one or more device IDs for the IoT devices which the user desires to register in association with the custom/customized VM selected/created by the user. In one implementation, each of the device IDs for the IoT devices may include a network address (e.g., IP address) for a respective IoT device. If a single IoT device ID is entered by the user, then only a single IoT device is to be registered in association with the custom/customized VM. If multiple IoT device IDs are entered by the user, then the multiple different device IDs are to be registered in association with the custom/customized VM.

If a single IoT device is to be registered (YES—block640), the app115receives a device ID and label(s) (block645). The user of user device100may enter, via a user interface of device100, a device ID and at least one label(s) for the IoT device. App115registers the IoT device, including the device ID, label(s), and the selected/created virtual model (block650). To register the IoT device, app115of device100may store the device ID in field520, the label(s) in field530, and the VM name in field540of an entry500of IoT registered device DB145. User device100may use a Web API or RESTful API for registering the single IoT device.

If more than a single IoT device is to be registered (NO—block640), then app115receives device IDs, and label(s) for the multiple IoT devices (block655). App115registers the multiple IoT devices in a batch mode, including the device IDs, label(s), and the selected/created virtual model (block660). To register the multiple IoT devices in a batch mode, app115of device100may store the device IDs in field520, the label(s) in field530, and the VM name in field540of an entry500of IoT registered device DB145. The payload of the batch registration may be in JavaScript Object Notation (JSON) format, and a RESTful API may be used for the batch registration.FIG. 7depicts IoT VM app115sending a device ID(s) and label(s)740for registration to thingspace platform105, and, in turn, thingspace platform105registering the IoT device(s) in IoT registered device DB145.

FIG. 10is a flow diagram that illustrates an exemplary process for enabling the access to data of, and/or control of, a physical IoT device using a previously selected or created thing virtual model associated with the IoT device. The exemplary process ofFIG. 10may be implemented by thingspace platform105, in conjunction with a user device100.

The exemplary process includes thingspace platform105receiving a command(s) from IoT access/control app140at a user device100, regarding access to data of, and/or control of, a registered IoT device(s) (block1000). The user of user device105may enter/select, via a user interface of user device105, a command(s) to access data at a particular selected IoT device(s)130, or a command(s) to control the operation of a particular selected IoT device(s). The command(s) to access data at the particular selected IoT device(s)130may include a command to access measured or sensed data by a particular sensor of the IoT device(s)130. The command(s) to control the operation of the particular selected IoT device(s) may include a command(s) to control a device state of the IoT device(s). The command(s) includes an identification of the particular IoT device(s) to which the command(s) is directed. In one implementation, the identification may include the network address of the particular IoT device(s). The messaging diagram ofFIG. 11depicts user IoT access/control app140of device100sending IoT device access/control command(s)1100to thingspace platform105.

FIG. 12depicts an exemplary GUI1300that may be used at user device100for controlling one or more device states of one or more physical IoT devices. The user of user device100may, via the user interface, select a label that identifies one or more physical IoT devices (e.g., “truck-01” in this example), and may then select a “States” button1205from the GUI1300. Upon selection of the “States” button1205, one or more device states associated with the physical IoT device(s) corresponding to the selected label are displayed (e.g., “State 1,” “State 2,” “State 3,” and “State 4” shown inFIG. 12). The user of user device100may select a tab1210, from GUI1200, corresponding to “State 1,” to access and control the parameters of device “state 1.” In this particular example, the device state is “brightness”1215, with a current state value1220of “50%”. As further shown in GUI1200under “State 1” tab1210, the brightness device state has an enumeration1225that ranges from “parameter_1” to “parameter 2.” For example, if parameter_1 equals 0%, and parameter_2 equals 100%, then the enumeration range for the brightness device state may range from 0% (low) to 100% (high). As also shown in GUI1200under “State 1” tab1210, one or more commands1230may be associated with the particular device state for exercising control over the device state. In the example shown, the available command for controlling the “brightness” device state is “Set_Brightness” with a corresponding control argument “parameter_3.” When the user of user device100selects the “Set_Brightness” command, and further enters an argument value within the enumeration range, user device100sends the command and argument value to thingspace platform105which, based on the VM for the particular IoT device, sends command instructions to the IoT device instructing the device to change its “brightness” device state to the user's argument value.

In addition to commands for controlling IoT devices, the user of user device100may specify rules by selecting “rules” button1235via GUI1200. Selection of “rules” button1235enables the user to specify one or more conditional “If-Then” rules to control the operation of the particular IoT device(s). For example, one rule specified by the user could be “If the room temperature measurement is over 90 degrees Fahrenheit, then turn on the air conditioning in that room.” Various different rules may be specified by the user related to controlling a single IoT device, or to controlling multiple different IoT devices.

Thingspace platform105retrieves a virtual model of the registered IoT device(s) (block1010). Thingspace platform105, upon extracting the identification of the particular IoT device(s) to which the command(s) is directed from the received command(s), may index IoT registered device DB145to locate an entry500having an ID(s) within IoT device ID(s) field520that matches the extracted identification. For example, if the extracted identification is a network address, thingspace platform105indexes DB145to locate an entry500having a network address in field520that matches the extracted network address. Upon locating an entry500with the matching network address, thingspace platform105retrieves the virtual model name from field520of the located entry500.

Thingspace platform105, upon retrieval of the virtual model name from DB145, may index thing VM DB110to locate an entry400having a VM name in field410that matches the retrieved virtual model name. Upon locating an entry400with the matching VM name, thingspace platform105retrieves the thing VM attributes stored in field420, as the virtual model corresponding to the VM name.FIG. 11depicts thingspace platform105engaging in virtual model retrieval1110from DBs110and145.

Thingspace platform105applies the virtual model to the received command(s) to derive appropriate access and/or control messaging for the registered IoT device(s) (block1020). Thingspace platform105uses the VM's attributes, retrieved in block1010), to derive appropriate data access and/or control messaging for sending to the IoT device(s). The messaging diagram ofFIG. 11depicts thingspace platform105applying1115the retrieved VM attributes to the received command(s) to derive the access/control messaging for the IoT device(s).

Thingspace platform105sends access and/or control messaging to the registered IoT device(s) (block1030).FIG. 11depicts thingspace platform105sending access/control messaging1320to one or more IoT device(s)130for which the user at user device100is accessing sensor/measurement data or device operational data, or controlling the operation of the IoT device(s)130.

Thingspace platform105receives access/control acknowledgment(s) (ACK(s)) and/or IoT device data from the registered IoT device(s) responsive to the access and/or control messaging (block1040).FIG. 11depicts thingspace platform105receiving access/control ACK(s) and/or IoT device data1125from IoT device(s)130. Thingspace platform105returns access/control acknowledgment(s) and/or the received IoT device(s) data to the user device100(block1050).FIG. 11depicts thingspace platform105forwarding1130access/control acknowledgments (ACKs) and/or IoT device(s) data received from IoT device(s)130.FIG. 13depicts an exemplary GUI1300for receiving and displaying sensor data from one or more physical IoT devices. Upon selection of the IoT physical device(s) associated with the label “truck-01,” the user of user device100may select the “sensors” button1305from GUI1300to display the various sensor types associated with the IoT physical device(s), and the current sensed/measured values associated with those sensor types. For example, as shown inFIG. 13, an altitude sensor1310, a latitude sensor1315, a longitude sensor1320, an “ontime” sensor1325, and a temperature sensor1330are displayed in GUI1300, along with current sensed/measured values received from the IoT physical device(s) via thingspace platform105. For example, altitude sensor1310shows a current measured altitude of 50 kilometers, latitude sensor1315shows a current measured latitude of 69.4303049, longitude sensor1320shows a current measured longitude of −52.1703861, the “ontime” sensor1325shows a value of “none,” and the temperature sensor1330shows a current measured temperature of 12 degrees Fahrenheit. The exemplary process ofFIG. 10may be repeated for each received command(s) regarding access/control of a registered IoT device.

The foregoing description of implementations provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, while series of blocks have been described with respect toFIGS. 6A, 6B and 10, and message flows with respect toFIGS. 7 and 11, the order of the blocks and/or message flows may be varied in other implementations. Moreover, non-dependent blocks may be performed in parallel.