Patent Application
20220335440
This disclosure is related to the control and management of network connected devices, e.g., Internet of Things (IOT) devices.
The number of IoT devices that can collect and communicate data over a network, e.g., the Internet, is increasing. Many businesses use IoT devices to track assets across supply chains and/or manufacturing lines. Many consumer goods also include IoT devices to provide “smart” functionality to end users. IoT devices, however, have lifecycles that typically need to be managed. For example, a typical IoT device needs to be provisioned, modified during its active life, and eventually retired from use at the end of its useful life. Many traditional systems for managing IoT devices are susceptible to attack, e.g., hacking, by malicious actors and/or do not provide for trusted transfers of IoT devices from one entity to another and/or across administrative boundaries, e.g., different zones of liability and/or custody in a supply chain or other environment.
Embodiments of the present disclosure provide for a registry for Internet of Things (IoT) devices that, in turn, may provide for a device identity authorization process. The registry may be maintained by a central trusted authority, e.g., a registrar, such that devices owned and/or operated by different entities and/or user may authenticate each other prior to interacting. Registration of an IoT device may be accomplished via an IoT Universal Identification (IoT UID), as described herein. A registered device may store its assigned IoT UID in the device itself such that the device can present its IoT UID to other devices for verification with the registrar. In embodiments, the IoT UID is associated in a record in the registry with properties of the device that may be unique to the device. As such, registered devices may exchange their IoT UIDs to learn each other's capabilities, e.g., memory capacity, number and types of connections, processing capacity, operating system compatibility, and the like. The IoT UID may also be associated in a record in the registry with a trust and/or risk indicator. As such, registered devices may be prohibited from interacting with devices that do not meet a trust and/or risk level threshold. Thus, embodiments of the current disclosure mitigate the need for an entity's domain controller servers to manage security groups. Such embodiments also improve the ability of a device to trust other devices in real-time without the need to check an approved list maintained by the device (or its domain administrator(s)) and/or to add other devices to the approved list. Embodiments of the registry may provide for the ability to track the histories and/or trust and/or risk indicators of at least hundreds, thousands, hundreds of thousands, millions, billions, and/or trillions of devices.
Accordingly, various applications of apparatuses, methods, and systems may be provided by embodiments, including, as non-limiting examples, an IoT UID registry, a single pane of glass (SPG) system, setup of embedded IoT UIDs for Brownfield devices, setup of embedded IoT UIDs for Greenfield devices, setup of virtual IoT UIDs for Brownfield devices, setup of virtual IoT UIDs for Greenfield devices, lifecycle management for registered IoT devices, tracking of a chain of title for registered IoT devices, a dynamic trust indication/level/rating/score for registered IoT devices, a Device Sentry for registered IoT devices, and fraud detection for registered IoT devices.
Embodiments of an IoT device registry may track and/or provide updates and/or alerts with respect to events relating to registered IoT devices. As explained in greater detail herein, the registrar and the registry are trusted sources that can be used to determine and/or verify data relating to an IoT device. Embodiments of the present disclosure may provide a database that contains records for embedded and virtual IoT UIDs. Embedded IoT UIDs may be present within an associated device/module and the registry. Virtual IoT UIDs may be present within the registry, and may not necessarily be present in an associated device/module. A device may include one or more modules. A module may be any type of electronic device and/or physical asset having properties giving rise to a unique signature. Each module may have its own IoT UID, and each device may also have its own IoT UID in addition to those of its modules.
As such, in an aspect of the present disclosure, there may be provided an apparatus may include an IoT UID processing circuit, a record management circuit, and a record provisioning circuit. The IoT UID processing circuit may be structured to interpret an IoT UID and device property data. The record management circuit may be structured to associate the IoT UID with the device property data via a record. The record provisioning circuit may be structured to transmit the record. In embodiments, the device property data may include an owner identifier value, a manufacturer identifier value, a trusted platform module key, a media access control address, a software version identifier, and/or or a firmware identifier.
In some embodiments of the present disclosure, any information managed by the IoT registry that a user wishes to access and has authority to access may be displayed on one display, or may be all visible at the same time, which may be, for example, on a single display monitor or across a multiple-monitor display system. Embodiments may determine which information regarding a device (or devices) and/or IoT UID is likely to be the most relevant to a particular type of user during a particular use case. The SPG may provide a graphical user interface (GUI) for the user to interact with, such as to input data, commands, and queries, as well as to display the IoT registry data. Embodiments of an SPG, may provide for simplified access to and/or viewing of the status of one or more IoT UIDs associated with a particular entity. For example, embodiments of an SPG may present a view of the data within the IoT device registry that is tailored to a particular user of the SPG. Thus, an SPG may provide an overview of all registered devices owned and/or operated by an end enterprise user, and/or provide for a manufacturer to view registered devices which it made. Embodiments of an SPG may also use filtering to depict only devices and/or corresponding device property data to which an entity using the SPG is authorized to access. For example, an SPG may allow a manufacturer to view certain properties of devices it made, but not view ownership information of said devices. Similarly, an SPG may prevent a current owner of a device from viewing previous ownership data of the device.
As such, in an aspect of the present disclosure, there may be provided an apparatus including a user input processing circuit structured to interpret one or more user input command values, an Internet of Things Universal Identification (IoT UID) identification circuit structured to determine one or more IoT UIDs, based at least in part on the one or more user input command values, a device lookup circuit structured to: generate a query that includes the one or more IoT UIDs, and retrieve device property data corresponding to the one or more IoT UIDs, a query provisioning circuit structured to transmit the query to an IoT device registrar server, a device property processing circuit structured to interpret the device property data generated by the IoT device registrar server in response to the query, and a display circuit structured to display the device property data with the corresponding one or more IoT UIDs.
Embodiments of the present disclosure may provide for a process of capturing a Brownfield device and embedding an IoT UID in it and registering it with the registry. Such capturing may provide for a previously untrusted device to build up its reputation, e.g., its trust level, over time. The process may begin with an end user using an SPG and/or some other interface to send a list of devices to the IoT device registrar that they would like to register via embedded IoT UIDs. The IoT device registrar may then generate/provision IoT UIDs, which may be new or recycled, and may transmit the list of IoT UIDs to the end user for installation/embedding into the devices. The IoT UIDs may be stored in a database in an IoT device registry at the IoT device registrar in association with the device property data so that the IoT UIDs may be associated in the registry with the device. Embodiments may wait to piggyback the provisioned IoT UIDs on an update or another type of event or message sent to the devices via the device management platform. The IoT UID may be stored in a writable memory device on a module of the device.
As such, in an aspect of the present disclosure, there may be provided a method including identifying one or more Brownfield devices, and generating device property data, based at least in part on the one or more Brownfield devices. The method may further include transmitting, to an IoT device registrar server, a registration request that includes the device property data, interpreting one or more IoT UIDs generated in response to the transmitting of the registration request, and embedding the one or more IoT UIDs in the one or more Brownfield devices.
Embodiments of the present disclosure may provide for a process of installing IoT UIDs into Greenfield devices, which may be presale, e.g., prior to their release from a manufacturer for use by end users, or post-sale, e.g., when an end user turns the device on after purchasing from the manufacturer. In a non-limiting pre-sale example, a manufacturer may send device property data for newly-minted devices and/or modules to a device management platform, that then may relay the data to the IoT device registrar, which may generate and send the IoT UIDs to the device management platform, which may then provide them to the manufacturer for installation into the Greenfield devices before they are released to end users. The IoT UIDs may be stored in a database in an IoT device registry at the IoT device registrar in association with the device property data so that the IoT UIDs may be associated in the registry with the device. Embodiments may provide for a bootstrapping IoT UID registration process, which may occur pre-sale or post-sale. Embodiments may provide for batch registration of newly-minted Greenfield devices. Embodiments may provide for a device to be “claimed” upon activation by an end user before registration can proceed, which may include updating ownership information stored in the registry, updating a chain of title stored in the registry, etc. Registering a Greenfield device with the registry may provide for verification of the Greenfield device's entire history.
As such, in an aspect of the present disclosure, there may be provided a method including manufacturing one or more Greenfield devices, and generating device property data based at least in part on the one or more Greenfield devices. The method may further include transmitting, to an IoT device registrar server, a registration request that includes the device property data. The method may further include interpreting one or more IoT UIDs generated in response to the transmitting of the registration request. The method may further include embedding the one or more IoT UIDs in the one or more Greenfield devices.
Embodiments of the present disclosure may provide for a process of capturing a Brownfield device, generating an IoT UID for the Brownfield device, and registering it with the IoT device registry without embedding the IoT UID into the Brownfield device, i.e., the IoT UID for the device may be virtual. For example, a virtual IoT UID may be used in scenarios in which a manufacturer and/or end user does not want to manage the presence of an embedded IoT UID. In embodiments a virtual IoT UID may be generated using a combination of device attributes, e.g., device property data, such that the virtual IoT UID may uniquely correspond to a particular device. The IoT device registry may associate device property data for the Brownfield device with the IoT UIDs in a record in an IoT registry. In a non-limiting scenario, a company with existing unregistered devices may want to track said devices with virtual IoT UIDs. The process may begin with an end user using an SPG and/or some other interface to send a list of devices with corresponding device property data to the IoT device registrar that they would like to register via virtual IoT UIDs. The IoT device registrar may then generate/provision IoT UIDs, which may be new or recycled, and then may pair each IoT UID to a specific set of the device property data corresponding to a particular device. In embodiments, the IoT device registrar may send a notification back to a device management platform indicating that the devices have been registered. Registering a Brownfield device may improve its trust indicator/rating/level/score value as recorded in its associated record in the IoT device registry. Embodiments may provide for the registration process to be initiated by a device management platform when a Brownfield device is added to the device management platform.
As such, in an aspect of the present disclosure, there may be provided a method including identifying one or more Brownfield devices, generating device property data based at least in part on the one or more Brownfield devices, and transmitting, to an IoT device registrar server, a registration request that includes the device property data. The method may further include interpreting one or more IoT UIDs generated in response to the transmitting of the registration request.
Embodiments of the present disclosure may provide for a process of registering Greenfield devices with virtual IoT UIDs, which may be presale, e.g., prior to their release from a manufacturer for use by end users, or post-sale, e.g., when an end user turns the device on after purchasing from the manufacturer. For example, a virtual IoT UID may be used in scenarios in which a manufacturer and/or end user does not want to manage the presence of an embedded IoT UID. In a non-limiting pre-sale example, a manufacturer may send device property data for newly-minted devices (and/or modules) to a device management platform, that then may relay the data to the IoT device registrar, which may generate IoT UIDs and associate each of them with portions of the device property data corresponding to one of the Greenfield devices to be registered in a record in an IoT registry. The IoT device registrar may then send a notification back to the device management platform that the devices have been registered. Embodiments may provide for a bootstrapping IoT UID registration process, which may occur pre-sale or post-sale. In a non-limiting example of the bootstrap registration process, a manufacturer (e.g., pre-sale) or an end user (e.g., post-sale) may boot up a newly-minted Greenfield device, which may then proceeds to contact the device management platform, which may then request the IoT device registrar to register the Greenfield device via a virtual IoT UID. Embodiments may provide for batch registration of newly-minted Greenfield devices. Embodiment may provide for a device to be “claimed” upon activation by an end user before registration can proceed, which may include updating ownership information stored in the registry, updating a chain of title stored in the registry, etc.
As such, in an aspect of the present disclosure, there may be provided a method including identifying one or more Greenfield devices, generating device property data based at least in part on the one or more Greenfield devices, and transmitting, to an IoT device registrar server, a registration request that includes the device property data. The method may further include interpreting one or more IoT UIDs generated in response to the transmitting of the registration request.
Embodiments of the present disclosure may provide for lifecycle management for registered IoT devices. Examples of lifecycle management may include performing status checks of devices and their current configuration states, e.g., installed patches, installed hardware, number of active network cards, etc. Lifecycle management may include detecting changes in the properties of a device, e.g., detecting and/or recording events. Events may come from a device manager, connection management platform (CMP), a Remote Authentication Dial-In User Service (RADIUS) feed (e.g., event stream), and/or a Home Location Register (HLR). Lifecycle management may include detecting security events. Lifecycle management may include tracking of ownership changes in the IoT device registry. Embodiments may provide for retirement of Greenfield and/or Brownfield devices. Embodiments may monitor for instances in which a permanently retired immutable device property, e.g., an International Mobile Equipment Identity (IMEI), appears in another device. Embodiments may provide for reincarnation/reuse/recycling of old IoT UIDs and/or for their permanent retirement. Embodiments may provide for checks on whether data collection makes sense. Down detection may be provided by certain embodiments. Embodiments may facilitate the pushing of updates and/or patches to devices. Lifecyle management may include modifying a trust indicator/rating/level/score of a device based on events. Embodiments may decrease/lower/reduce/drop a device's trust indicator/rating/level/score if the corresponding information in the IoT device registry starts to get stale, for example, if it has not been updated and/or queried for at least a predetermined time. Embodiments may provide for polling of devices to provide updates to their stored property data.
As such, in an aspect of the present disclosure, there may be provided an apparatus including a property-monitoring circuit structured to generate a query for device property data for an IoT device to an IoT device registrar server, interpret the device property data received from the IoT device registrar server to determine whether there is a change in the device property data, if the property-monitoring circuit determines that there is a change in the device property data, generate a notification of the change, and transmit the notification of the change to the IoT device registrar server.
Embodiments of the present disclosure may provide for the maintaining/recording of chain of title for devices. Maintaining and/or recording of the chain of title may be provided via a distributed ledger, e.g., a blockchain. Embodiments may provide for certification that a device is not a stolen device and/or has a fully accountable chain of title. Certification may be used to evaluate an asking price for a registered device, or for a group of devices that may include one or more registered devices. Embodiments provide for an entity to claim ownership of a device. The trust indicator/rating/level/score may be numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. Non-limiting examples of events resulting in title changes include: creation of a device, sale of a device, decommissioning of a device, license of a device, etc. Embodiments may provide for supply chain validation. As non-limiting examples, validation may include determining whether device modules were sourced from authorized vendors, or from fair trade certified sources. Embodiments may provide for determining a carbon rating of a device based on known ratings of their modules' sources. Embodiments may provide for the detection of device properties, e.g., location, usage profile, network, interface language, device settings, associated telephone number, that may be indicative of a change in ownership.
As such, in an aspect of the present disclosure, there may be provided an apparatus including an IoT UID processing circuit, a record management circuit, an ownership analysis circuit, and an ownership provisioning circuit. The IoT UID processing circuit may be structured to interpret an IoT UID corresponding to a device. The record management circuit may be structured to identify, based at least in part on the IoT UID, a record in a database, the record including device ownership data associated with the device. The ownership analysis circuit may be structured to interpret, based at least in part on the record, the device ownership data associated with the device. The ownership provisioning circuit may be structured to transmit the device ownership data.
Embodiments of the present disclosure may provide for a rating of the “trustworthiness” of a device, which may be capable of changing over time as the device experiences “life” events, e.g., ecosystem events. For example, Greenfield devices may automatically start out with a high value trust indicator/rating/level/score because their whole existence history may be known and verifiable. The trust indicator/rating/level/score may be numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. A trust indicator (e.g., trust rating/level/score value) may decrease as software/hardware grows older and/or out of date. Patching may improve a device's trust indicator. Trust indicators may be determined, in part, by device location, e.g., geo-fenced trust indicators. Embodiments may provide for user-defined scores and/or scales. Scores may be converted from one paradigm/entity to another, in which the IoT device registry may serve as a baseline score to which the others can be compared. Embodiments may provide for trust indicators for online servers to include game/metaverse servers. Embodiments may provide for augmented reality (AR) trust indicators to be shown in relation to devices, e.g., ATM and/or card readers, in the real world. Trust indicators may be applied to device manufacturers.
As such, in an aspect of the present disclosure, there may be provided an apparatus including an IoT UID processing circuit structured to interpret an IoT UID corresponding to a device, a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device, a trust analysis circuit structured to determine, based at least in part on the record, a risk indicator of the device, and an indicator provisioning circuit structured to transmit the risk indicator.
Embodiments of the present disclosure may provide for risk and/or trust scores/indicators and/or certification of servers and/or other physical assets supporting metaverse activities. For example, a user in the metaverse may be provided with a risk score of a server before entering an area (e.g., a room) in the metaverse hosted by that server. Embodiments may provide for risk scores of users within the metaverse. Such risk score may be based on the risk score of devices associated with the user. Embodiments may depict/express the risk scores within the metaverse as a trust indicator/rating/level/score that may be numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. Embodiments of the disclosure may provide for an end user application that restricts a user from accessing or interacting with a device/entity in the metaverse, for example, a device, a server, an area, an object, an avatar, or another user, that does not meet a minimum risk threshold and/or does not present a certification. Embodiments of the application may be a parental control software agent. The risk scores may be determined, stored, and/or maintained by an IoT UID device registrar, e.g., in an IoT device registrar server. A device may be a virtual device (an object in the metaverse having a real-world counterpart, e.g., a real-world device counterpart), a real-world device (an object in the real-world having a metaverse counterpart), or a meta-device (an object in the metaverse lacking a real-world counterparts or, in some instances, having one or more real-world counterparts). A device may include virtual devices and meta-devices. A virtual device may be a digital twin of a real-world device. The risk and/or trust indicator/rating/level/score may be tailored to a user. Trust and/or risk scores may be shown with respect to a virtual store for metaverse purchases.
As such, in an aspect of the present disclosure, there may be provided an apparatus including an IoT UID processing circuit, a record management circuit, a trust analysis circuit, and a trust indicator provisioning circuit. The IoT UID processing circuit may be structured to interpret an IoT UID corresponding to a device in a metaverse. The record management circuit may be structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device in the metaverse. The trust analysis circuit may be structured to determine, based at least in part on the record, a trust indicator of the device in the metaverse. The trust indicator provisioning circuit may be structured to transmit the trust indicator.
Embodiments of the present disclosure may provide for the depiction and use of a risk and/or trust indicator/rating/level/score and/or certification via augmented reality (AR). Embodiments may depict risk/trust scores of objected encountered by a user. As a non-limiting example, a user wearing an AR device, such as an AR headset, AR contact lenses, AR glasses, or AR goggles, may see an ATM colored green if the device has a sufficiently high trust indicator (e.g., trust score/rating/level value), or red if the device has a sufficiently low trust indicator. Embodiments may depict trust indicators for individuals based on the trust indicators of devices associated with the scored individuals. Devices may be virtual devices, real-world devices, or meta-devices. Applications of the trust and/or risk scores may be used for virtual stores in a metaverse.
As such, in an aspect of the present disclosure, there may be provided an apparatus including an IoT UID processing circuit structured to interpret an IoT UID corresponding to a device in an AR, a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device in the AR, a trust analysis circuit structured to determine, based at least in part on the record, a trust indicator of the device in the AR, a trust indicator provisioning circuit structured to transmit the trust indicator.
Embodiments of the present disclosure may provide for an agent that monitors registered devices for known vulnerabilities and provides alerts and/or access to remedial measures, e.g., patches. The agent may execute on the same system as the IoT device registry and/or on a system owned and/or operated by an end user, manufacturer, and/or device management platform. Embodiments may provide for the collection of remedial measures from a device manufacturer and/or other source, e.g., the National Security Agency (NSA), Linux Distros, Microsoft, Apple, Google, etc., and may provide the generation of campaigns to manage and/or track implementing the remedial action of a plurality of affected devices, e.g., “software Bill of Materials (SBoM)” and/or “Cybersecurity Bill of materials (CBoM).” Embodiments may provide for the aggregation of hardware and/or software version data, which the agent may use to detect vulnerabilities. Embodiments may access a vulnerability database. Embodiments may generate a vulnerability database. The agent/sentry may send an alert when it detects a configuration change of a module, e.g., when a new network interface controller (NIC) has been installed. In embodiments, the agent/sentry may poll and/or otherwise monitor security sources for relevant information and automatically generate matches, generate alerts/notifications, and/or highlight potentially affected devices (via an alert and/or event message, which may be in an SPG, as disclosed herein) to device users, administrators, manufacturers, etc. In embodiments, the agent/sentry may change/adjust the trust and/or risk levels of the affected devices, e.g., decrease the trust levels (or increase the risk levels) where the devices fall out of compliance due to a new patch. Once action is taken to remedy the vulnerabilities, the trust and/or risk levels will revert to the relevant trust and/or risk level and/or security state. In embodiments, the agent/sentry may maintain audited logs of actions taken to address the vulnerabilities.
As such, in an aspect of the present disclosure, there may be provided an apparatus including a device property data processing circuit structured to: at a first time, interpret, device property data corresponding to a device registered with an IoT device registry, and at a second time, interpret, the device property data corresponding to the device registered with the IoT device registry, a change detection circuit structured to detect a change in the device property data between the first time and the second time, an alert circuit structured to generate, responsive to the detected change, a message that identifies the device corresponding to the device property data, and an alert provisioning circuit structured to transmit the message.
Embodiments of the present disclosure may provide for an agent that monitors registered devices for loss of one or more network connections. Monitoring may be for a single device and/or for multiple devices, e.g., a fleet of devices. The agent may not necessarily be concerned with hardware and/or software version of components; rather, the agent may look at the IoT device registry to detect outage patterns. The IoT device registrar may be in a unique position to view a large number of devices simultaneously, which may provide for greater insight into the existence of a device outage.
As such, in an aspect of the present disclosure, there may be provided an apparatus including a device property data processing circuit, an outage detection circuit, an alert circuit, and an alert provisioning circuit. The device property data processing circuit may be structured to interpret device property data corresponding to one or more devices registered with an IoT device registry. The outage detection circuit may be structured to detect an outage pattern in the device property data. The outage pattern may correspond to an outage of the one or more devices. The alert circuit may be structured to, responsive to the outage pattern, generate an alert message that identifies the one or more devices. The alert provisioning circuit may be structured to transmit the alert message.
Embodiments of the present disclosure may provide for an agent that monitors the IoT device registry for signs of fraudulent activity. This may provide for detection of unusual behavior that may be indicative of fraud and/or a security risk. Correlation of device properties across the various spectrums may provide for a unique ability to detect unusual relationships that may indicate fraud and/or warrant further investigation. Embodiments may send messages to various parties, e.g., manufacturers that may include restricted views of device property data, which may enable the various parties to detect unusual behavior and/or fraud.
As such, in an aspect of the present disclosure, there may be provided an apparatus including a device property data processing circuit, a security analysis circuit, an alert circuit, and an alert provisioning circuit. The device property data processing circuit may be structured to interpret device property data corresponding to a device registered with an IoT device registry. The security analysis circuit may be structured to determine, based at least in part on the device property data, that the device is subject to a fraud event. The alert circuit may be structured to generate, responsive to the determined fraud event, a message that identifies the device. The alert provisioning circuit may be structured to transmit the message.
Embodiments of the present disclosure may provide for the registering of meta-devices with the IoT UID registry. A meta-device, in embodiments, may be a device and/or module that exists in a computer environment, e.g., a metaverse, a virtual environment apart from a metaverse, a software object, etc. A meta-device may have one or more real-world counterparts, or no real-world counterpart. A meta-device with at least one real-world counterpart may be a virtual device. A meta-device may have a set of properties forming a unique signature for the meta-device, e.g., device property data, which may include one or more non-fungible tokens (NFTs). A meta-device may be a Greenfield device and/or a Brownfield device. A non-limiting use case of registering a meta-device includes a programmer registering a newly programmed and instantiated car for use in a multi-player/avatar virtual environment, e.g., a meta-verse, with an IoT device registrar as a Greenfield meta-device. The car may then be purchased by a user/customer, and then event messages may be transmitted to the IoT device registrar to track the life cycle events of the car. The car may also have a NFT, which may be stored by the registry as part of the device property data. In embodiments, a meta-device may be a point-of-sale device in a virtual convenience store where the meta-device may correspond to multiple real-world devices that are not real-world point-of-sale devices, e.g., a server, payment gateway, and/or a firewall.
As such, in an aspect of the present disclosure, there may be provided an apparatus including an IoT UID processing circuit structured to interpret an IoT UID and device property data corresponding to a meta-device, a record management circuit structured to associate the IoT UID with the device property data via a record, and a record provisioning circuit structured to transmit the record.
The description herein references various applications as non-limiting examples of apparatuses, methods, and systems, and for clarity of the present description. However, embodiments herein are applicable to other applications having similar challenges and/or implementations.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiments illustrated in the drawings and described in the following written specification. It is understood that no limitation to the scope of the disclosure is thereby intended. It is further understood that the present disclosure includes any alterations and modifications to the illustrated embodiments and includes further applications of the principles disclosed herein as would normally occur to one skilled in the art to which this disclosure pertains. It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are intended to provide further explanation of the invention as claimed.
For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiments illustrated in the figures and described in the following written specification. It is understood that no limitation to the scope of the disclosure is thereby intended. It is further understood that the present disclosure includes any alterations and modifications to the illustrated embodiments and includes further applications of the principles disclosed herein as would normally occur to one skilled in the art to which this disclosure pertains. Further, skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and may not necessarily be drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the methods and systems disclosed herein. Accordingly:
The present disclosure will now be described in detail by describing various illustrative, non-limiting embodiments thereof with reference to the accompanying figures and exhibits. The disclosure may be embodied in many different forms and should not be construed as being limited to the illustrative embodiments set forth herein. Rather, the embodiments are provided so that this disclosure will be thorough and will fully convey the concept of the disclosure to those skilled in the art.
Embodiments of the current disclosure are described herein with respect to devices, which includes devices that may form a connected ecosystem of various machines, sensors, and/or other types of devices working together and/or independently with or without human interaction. Devices may be modules, e.g., network interface cards, that can be combined with other modules to form other types of devices, e.g., a desktop computer having an ethernet network interface card, an 802.11 Wi-Fi network interface card, a serial RS232 card, etc. Non-limiting examples of modules include network interface cards, processors, memory chips, display controllers/cards, process logic controllers (PLCs), etc. For example, as used herein, the term “device” may refer to a module for a product, a set of modules for a product, or the entirety of the product that may have one or more modules incorporated therein. Devices may also be Internet of Things (IoT) devices. In embodiments a device may be a collection of chipsets and/or modules contained in a device to perform a specific function and/or set of functions. In embodiments, a device may be a collection of associated chipsets and/or modules and/or their accompanying identification attributes combined with attributes of a containing device. Such embodiments may associate embedded components absolutely with respect to a device containing the embedded components.
Traditional approaches of physically securing an enterprise's perimeter do not meet the needs of an enterprise deploying IoT devices. For example, IoT devices used to track products along a supply chain must often pass through several entities, each having their own physical security perimeters where products are allowed to pass between the security perimeters without verifying ownership (and/or security credentials) of IoT devices used to monitor the products.
Accordingly, embodiments of the current disclosure provide for a registry for IoT devices that, in turn, may provide for a device identity authorization process that validates identities of endpoints in an IoT system. Registration of an IoT device may be accomplished via an IoT Universal Identification (IoT UID), as described herein.
In embodiments, a device identity certification process may be configured upon enrollment/entry of a device to a platform or other management system, and informs a service provider of the method to be used when checking a device's identity during the registration process. Embodiments of the present disclosure may also provide for systems and methods for managing a Machine Identity Management platform that instills confidence in a device's identity when it interacts with other devices, applications, clouds, and/or gateways. As will be explained in greater detail herein, embodiments of the current disclosure may provide for the verification of an IoT device prior to joining of the IoT device to a network, thereby fortifying the perimeter of the network. In other words, embodiments of the current disclosure may require (or encourage) an identification and/or verification of an IoT device's identity prior to allowing the IoT device to join a network. In certain aspects, embodiments of the current disclosure provide for a reliable, scalable backbone for an IoT device registry. In certain aspects, embodiments of the current disclosure provide for a subscriber identity module (SIM) for Things, e.g., digital devices, which enables global IoT device monitoring via business intelligence (BI) tools. As will also be explained in greater detail herein, embodiments of the current disclosure provide for systems, methods, and apparatuses that improve an entity's confidence in an IoT device's registration, security, and lifecycle management.
Referring now to
In embodiments, the IoT device registry 1129 may be accessible via a network 1132 to one or more entities 1134, 1136, and/or 1138 that own, possess, operate, and/or otherwise have an interest in the one or more devices 1112, 1114, 1116, 1118, 1120, 1122, and 1124. Non-limiting examples of the entities include a manufacturer 1134 of the devices, an end user 1136 of the devices, and a third party 1138. The manufacturer 1134 may be an original equipment manufacturer (OEM). The end user 1136 may be an enterprise/corporate user and/or a retail user. The third party 1138 may include entities that perform services related to the one or more devices 1112, 1114, 1116, 1118, 1120, 1122, and 1124, such as monitoring the one or more devices 1112, 1114, 1116, 1118, 1120, 1122, and 1124 for security vulnerabilities and/or providing software/firmware updates. In embodiments, the third party 1138 may be a party who has a financial interest in the one or more devices 1112, 1114, 1116, 1118, 1120, 1122, and 1124, such as a lender of a loan used by an enterprise 1136 to purchase the one or more devices 1112, 1114, 1116, 1118, 1120, 1122, and 1124 from a manufacturer 1134.
As explained in greater detail herein, the entities 1134, 1136, and/or 1138 may send communication data 1140, 1142, 1144 to the IoT device registrar 1130 and/or may receive communication data 1146, 1148, 1150 from the IoT device registrar 1130. For example, an enterprise user 1136 may send a registration request 1142 for a device 1114 to the registrar 1130, which may then register the device 1114 via a record 1152, in the registry 1129, as being owned by the enterprise 1136. An employee of the enterprise 1136 operating the device 1114 may then wish to interact, via the device 1114, with another device, e.g., a remote server, operated by a third party 1138. As the device 1114 is registered with the registry 1129, the third party 1138 may send a query to the IoT device registrar server 1126 asking who the registered owner of the device 1114 is. The IoT device registrar server 1126 may then execute the query 1114 against the registry 1129, and may send the result 1150 back to the third party 1138, who may then grant or deny the device 1114 access to its device based on the result 1150. For example, access may be granted if the device 1114 is owned by an approved party, or may be denied if the device 1114 is not owned by an approved party. As will be appreciated, other use case examples of the system 1100 are disclosed herein.
Turning to
As illustrated in
Accordingly, and referring to
Referring again to
In certain aspects, a manufacturer and/or other entity may be permitted by the registry 1129 to advertise a network connected device as “trusted by [the registry's name]”. In certain aspects, the registry 1129 may enable an end consumer to receive continued support and/or tracking capabilities of a network connected device in the event the manufacturer (OEM) goes out of business and/or otherwise ceases support of the network connected device. In certain aspects, the registry 1129 provides manufacturers (e.g., an OEM, module manufacturer, chipset vendor, IoT edge gateway vendor) of network connected devices with the ability to improve consumer trust in their products, which, in turn, may preserve and/or improve the manufacturer's reputation. In certain aspects, the registry 1129 may provide enterprises, e.g., end users of network connected devices, with improved trust in supply chains and/or other industrial and/or commercial processes. Embodiments of the disclosure may also provide internet service providers (ISPs), mobile network operators (MNOs), and mobile virtual network operators (MVNOs) with improved confidence that network connected devices operating on their networks are hardened against network attack and/or exploitation. Embodiments of the current disclosure may also provide consumers with improved confidence in purchasing a network connected device due to the fact that the network connected device can be vetted though the registry. Embodiments of the current disclosure may also enable enterprises to scale their IoT deployments with the knowledge that they will have tools to manage and/or mitigate risks, for example, to include those associated with non-conformance with government and/or industry regulations. Certain aspects of the current disclosure also provide for entities that interact with network connected devices to be agnostic with respect to the type of network connected devices and/or networks on which such devices operate. Embodiments of the current disclosure may provide for centralized identity management in combination with robust device management, and/or for a highly scalable network connected device management system based on an API-centric framework that is suited for exponential growth and deployment of IoT devices. Certain aspects of the registry, as disclosed herein, may also provide for advanced tracking and auditing of network connected devices and/or assets which they monitor.
Illustrated in
Referring to
IoT UIDs may be embedded, e.g., a copy of the IoT UID is stored in a memory device of the corresponding device, or virtual, e.g., a copy of the IoT UID is not stored in a memory device of the corresponding device. A record 1152 corresponding to an embedded IoT UID may be referred to herein as an “embedded record” and/or “an embedded registration”. A record 1152 corresponding to a virtual IoT UID may be referred to herein as a “virtual record” and/or “a virtual registration”. In embodiments, the property data of a device, e.g., 1112, may form and/or contain a unique signature for the device 1112. As such, associating the device data, corresponding to a device, to an IoT UID in a record of the IoT device registry 1129 provides for the ability to either use the IoT UID to identify the device property data or use the device property data to identify the IoT UID. In embodiments, the relationship between unique device property data signatures and IoT UIDs may be one-to-one.
Turning back to
Other fields 6122 stored within a record 6110 may include: various types of metadata associated with a record, e.g., the generation data of the record, a last modified date of the record, access control data concerning the record; pointers to other records in the registry 1129 (
A registration request 6112, as disclosed herein, may include device property data 6124 for one or more devices intended to be registered via the registry 1129 (
A device status value 6114, as disclosed herein, may include data retrieved via querying the registry 1129 (
Device event messages 6116 may be generated in response to querying the registry 1129 and/or transmitted to the registry 1129 for association with an IoT UID 6118, as disclosed herein. Device event messages 6116 may include an IoT UID 6118, device property data 6132, event data 6134, and/or other data 6136. In embodiments, device property data 6132 may include device property data, as disclosed herein, regarding affected properties of a device resulting from undergoing/experiencing an event and/or data relating to the event. Event data 6134 may include data relating to an event, but may not be associated to an IoT UID 6118 within the device event message 6116, e.g., a message indicating that a weather event is occurring in a particular geographic region. Other data 6136 may include metadata related to the event message 6116, e.g., a time of the message, to whom/what the message is being transmitted, etc.
As disclosed therein, a device, e.g., 1112, may include one or more modules, where each module may have its own IoT UID 6118 and/or record 6110 (if registered and/or pre-registered, e.g., where a device has a record but may need to be claimed, as disclosed herein). Accordingly, in embodiments, the device property data 6120 and/or other field/data 6122 of a record 6110 corresponding to a device, e.g., a cell phone, may include the IoT UIDs of other devices/modules, e.g., subscriber identity modules, memory chips, Wi-Fi network interface cards (NICs), etc., that are related to and/or form part of the device and which can be used to retrieve/identify records in the registry 1129 corresponding to such other devices/modules.
In embodiments, the registrar 1130 may provide for an application programming interface (API) and/or web interface that allows a user to register one or more devices and/or to view and/or enter device events. The user may be a manufacturer 1134, an end user 1136, and/or a third party 1138. Non-limiting examples of such interfaces/APIs are described and shown in other portions of this disclosure, e.g.,
In embodiments, events may be transmitted to the registry 1129 via a device manager, connection management platform (CMP), and/or a Remote Authentication Dial-In User Service (RADIUS) feed, e.g., an event stream, or otherwise. In embodiments, events may be retrieved from a Home Location Register (HLR) of a device. Non-limiting examples of events from a device management platform include device provisioning events, device operational events, firmware and/or software update events, battery status events, and/or the like. Non-limiting examples of events from a CMP include, international mobile subscriber identity related events, subscriber identify module (SIM) related events such as activated and/or suspended. Non-limiting examples of RADIUS feed events include network related events, e.g., attached and/or detached to and from a network, data consumption related events, billing events, e.g., indication of a bill being ready for processing. Non-limiting examples of Home Location Register (HLR) events include device on and reachable, device out of coverage, and/or other types of events related to and/or data stored in a device's HLR.
As disclosed herein, the registry 1129 may respond to queries regarding IoT UIDs, e.g., “is X the true owner of the device associated with IoT UID Y?” via transmitting device property data 6128 and/or a device status value 6128, which may include the device property data 6128, IoT UID 6118, and/or other data 6130, e.g., a listing of events. The registry 1129 may provide for restricted access based on permission levels, e.g., an original equipment manufacturer (OEM), may be able to see the patch status of its devices, but not the end users of said devices.
In embodiments, the registry 1129 may provide the provisioning of a record for an IoT UID prior to registration of a corresponding device. For example, a manufacturer 1134 may provide device property data for one or more devices to the registry 1129 that may not have been powered up for the first time. The registry 1129 may then generate IoT UIDs and/or records for the one or more devices, where each record may contain an “claimed” field, e.g., other data 6130, indicating that a corresponding device is unclaimed. When a corresponding device is subsequently powered on, it may contact the registry 1129 to finish the registration process, wherein the registry 1129 updates the “claimed” field to reflect that the corresponding device is active and has been registered.
In embodiments, the apparatus 8100 may further include an unusual activity detection circuit 8118 structured to detect unusual activity corresponding to ownership and/or use of a network connected device 1112, 1114, 1116, 1118, 1120, 1122, 1124. The unusual activity detection circuit 8118 may detect the unusual activity by analyzing one or more of the plurality of records 1131 (
Illustrated in
As shown in
Referring now to
Illustrated in
Turning to
Referring now to
Illustrated in
As shown in
Referring again to
With reference to
Certain further aspects of the example system are described as following, any one or more of which may be present in certain embodiments. In the apparatus 19100, the user input command values 19114 may include the one or more IoT UIDs 19116. In the apparatus 19100, the user input command values 19114 may include credentials 19122. Non-limiting examples of credentials 19122 include public key infrastructure (PKI) encryption keys, username and password, non-PKI encryption keys, and the like. In the apparatus 19100, the IoT UID identification circuit 19104 may be further structured to determine the one or more IoT UIDs 19116 based at least in part on the credentials 19122. The apparatus 19100 may further include a filtering circuit 19134 structured to filter data in the device property data 19120, based at least in part on the one or more user input command values 19114. In the apparatus 19100, the filtered data may relate to historical ownership of a device, e.g., any of devices 1112, 1114, 1116, 1118, 1120, 1122, 1124 (
The method 20100 may include interpreting, via a user input processing circuit, one or more user input command values 20102. The method 20100 may further include determining, via an IoT UID identification circuit, one or more IoT UIDs, based at least in part on the one or more user input command values 20104. The method 20100 may further include generating, via a device lookup circuit, a query that includes the one or more IoT UIDs 20106. The method 20100 may further include retrieving, via the device lookup circuit, device property data corresponding to the one or more IoT UIDs 20108. The method 20100 may further include transmitting, via a query provisioning circuit, the query to an IoT device registrar server 20110. The method 20100 may further include interpreting, via a device property processing circuit, the device property data generated by the IoT UID registrar server in response to the query 20112. The method 20100 may further include displaying, via a display circuit, the device property data with the corresponding one or more IoT UIDs 20114.
With reference to
Certain further aspects of the example system are described herein any one or more of which may be present in certain embodiments. In the system 22100, each of the one or more devices may have an IoT Universal Identification (UID) 22114 associated with the device. The system 22100 may further include a filtering circuit 22116, in communication with the device management server, structured to filter data in the device property data 22110. In the system 22100, the filtered data may relate to historical ownership of a device having an IoT UID associated with the device. In the system 22100, the device property data 22110 may include a patch status 22118 for a device having an IoT UID associated with the device. In the system 22100, the device property data 22110 may include a security risk analysis value 22120 for a device of the corresponding IoT UID. In the system 22100, the device property data 22110 may include a trust level value 22122 for a device of the corresponding IoT UID. The system 22100 may further include a security alert circuit 22124 structured to generate a security alert 22126, based at least in part on the security risk analysis value and/or the trust level value. The system 22100 may further include a patching campaign circuit 22128, in communication with the device management server, structured to generate and track a patching campaign 22130 for devices corresponding to one or more IoT UIDs 22114. The system 22100 may further include a credential verification circuit 22132, in communication with the device management server 22104, structured to determine whether a user of the graphical user interface 22108 is authorized to access the device property data 22110 for the one or more devices. If it is determined that the user of the graphical user interface 22108 is not authorized to access the device property data 22110 for the one or more devices, the credential verification circuit 22132 is further structured to restrict the display of the device property data 22110 for one or more devices.
With reference to
Certain further aspects of the example apparatus are described as following, any one or more of which may be present in certain embodiments. In the apparatus 23100, the user input command values 23110 may include the one or more IoT UIDs 23112. In the apparatus 23100, the user input command values 23110 may include credentials 23111. In the apparatus 23100, the application 23106 stored in the memory device 23104 may be further structured to adapt the at least one processor 23102 to determine the one or more IoT UIDs 23112 based at least in part on the credentials 23111. In the apparatus 23100, the application 23106 stored in the memory device 23104 may be further structured to adapt the at least one processor 23102 to filter data in the device property data 23114, based at least in part on the one or more user input command values 23110. In the apparatus 23100, the filtered data may relate to historical ownership of a device, e.g., any of devices 1112, 1114, 1116, 1118, 1120, 1122, 1124 (
The method 24100 may include generating, via a processor, a graphical user interface structured to receive one or more user input command values, and to communicate with an IoT device registrar server 24102, e.g., server 1126 (
Certain further aspects of the example method are described as following, any one or more of which may be present in certain embodiments. In the method 24100, each of the one or more devices may have an IoT Universal Identification (UID) associated with the device. With reference to
With reference to
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. In the apparatus 27100, the IoT UID 27106 and device property data 27108 may be associated with a device, e.g., any of devices 1112, 1114, 1116, 1118, 1120, 1122, 1124 (
The apparatus 27100 may further include a credential verification circuit 27128, in communication with the record management circuit 27104, structured to determine whether a user of the SPG is authorized to access the device property data 27108 corresponding to the IoT UID. The determination may be based on credentials 27130 provided by the record management circuit 27104. If it is determined that the user of the SPG is not authorized to access the device property data 27108 corresponding to the IoT UID, the credential verification circuit 27128 is further structured to restrict the display of the device property data 27108 on the SPG.
In certain aspects, access to an SPG may be based on a subscription model. In certain aspects, access to an SPG may be provided via an Application Programming Interface (API) or via a GUI, which may be a web-based user interface (UI). Embodiments of the SPG may provide for a user to modify a data record in the IoT device registry for one or more devices. Embodiments of the SPG may provide for the generation and execution of queries against the IoT device registry. Embodiments of the SPG may provide for a user to validate, e.g., visually, a chain of title for a device and/or to inform the IoT device registry of a change in ownership for one or more devices. Embodiments may provide for a user to verify a supply chain for a device and/or associated product. Embodiments may provide for a user to see a list of network entry points into a device, which the user can then monitor for security purposes. In certain aspects, the SPG may restrict and/or filter out displayed devices based on access rights, e.g., an enterprise user may only be able to view devices that they control and/or own. For example, embodiments may provide for a manufacturer to see a patch version of a module they made, but not its location and/or current owner. The filtering may also comprise a search for a subset of device property data, e.g., based on one or more user input command values. In certain aspects, the SPG may be a standalone application, e.g., an Amazon Web Services (AWS) application (“app”), and/or it may be integrated into an existing platform/system.
Thus, embodiments of an SPG, as disclosed herein, provide for simplified access to and/or viewing of the status of one or more IoT UIDs associated with a particular entity, e.g., end user, manufacturer, third party, etc., as compared to traditional systems. For example, embodiments of an SPG may present a view of the data within the IoT device registry that is tailored to a particular user of the SPG, e.g., end user, manufacturer, third part, etc. Thus, an SPG may provide an overview of all registered devices owned and/or operated by an end enterprise user, and/or provide for a manufacturer to view registered devices which it made. Embodiments of an SPG may also use filtering, as described herein, to depict only devices and/or corresponding device property data to which an entity using the SPG is authorized to access. For example, an SPG may allow a manufacturer to view certain properties of devices it made but not view ownership information of said devices. Similarly, an SPG may prevent a current owner of a device from viewing previous ownership data of the device.
Illustrated in
Referring again to
Illustrated in
Flow 30100 concerns a scenario in which the registering party 30112 wants to register one or more Brownfield devices with embedded IoT UIDs prior to the Brownfield devices entering service within an operational network, e.g., the registering party 30112 may be an enterprise user provisioning the Brownfield devices for use in the enterprise user's corporate network. At 30122, the administrator 30114 may prepare the one or more Brownfield devices for embedding of an IoT UID. Such preparation may include updating the firmware and/or software of the one or more Brownfield devices, installing security credentials, e.g., public key infrastructure (PKI) keys and/or certificates, joining to a network domain, etc. The administrator 30114 may then collect/gather/generate device property data from the prepared one or more Brownfield devices, and then provide/transmit 30124 the gathered device property data to the IoT device registrar 1130. Upon receipt of the device property data, the IoT device registrar 1130 may generate 30126 IoT UIDs for each of the one or more Brownfield devices and associates each IoT UID with portions of the device property data corresponding to a particular Brownfield device. As disclosed herein, such associations may be accomplished via a record 1152 (
Flow 30110 also concerns a scenario in which the registering party 30112 wants to register one or more Brownfield devices with embedded IoT UIDs, where the Brownfield devices are already in service within an operational network, e.g., the registering party 30112 may be an enterprise user wishing to register Brownfield devices already in use in the enterprise user's corporate network. Non-limiting examples of such devices/scenarios may include: Brownfield devices forming part of an existing supervisory control and data acquisition (SCADA) network, e.g., weather and/or power monitors on existing powerline towers; Brownfield devices deployed to corporate employees, e.g., cell phone, laptops, printers, tablets, etc.; and/or other devices where it would be beneficial to embed an IoT UID without having to physically bring the Brownfield device to a particular location, e.g., an in-house IT department, for embedding. At 30131, an administrator 30114 may then collect/gather/generate device property data from one or more Brownfield devices, which may currently be deployed on a network managed by the administrator 30114, and provide/transmit 30132 the gathered device property data to the IoT device registrar 1130. Upon receipt of the device property data, the IoT device registrar 1130 may generate 30133 IoT UIDs for each of the one or more Brownfield devices and associates each IoT UID with portions of the device property data corresponding to a particular Brownfield device. As disclosed herein, such association may be accomplished via a record 1152 (
Illustrated in
The Brownfield device may then proceed to setup its control plane functionality by transmitting 31122 device registration data to a device management platform 30116. The device registration data may include the security certificate the Brownfield device used to register with the cloud platform 31112, other device property data, and/or any data the Brownfield device received from the cloud platform 31112 during the data plane setup process 31110. The device management platform 30116 may then verify 31124 the device registration data and transmit 31126 an event message, e.g., 6116 (
Illustrated in
Moving to
Referring to
Illustrated in
Shown in
As illustrated in
Illustrated in
Referring to
An additional non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering sensors on a resource distribution system, e.g., a water, gas/oil, and/or electricity, distribution system, with an IoT UID device registry without an administrator to physical contact and/or visit each of the sensors at their operating location. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering satellites already in orbit with an IoT UID device registry. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering vehicles in a fleet with an IoT UID device registry. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering pallet tracking device already in the field, e.g., attached to pallets, with an IoT UID device registry.
Referring again to
As a non-limiting example, an enterprise user 1136 (
In another non-limiting example, the registrar 1130 may provide the IoT UIDs to the manufacturer 1134 prior to the sale of the laptops 1122 and 1124 to the end user, wherein the manufacturer 1134 is the entity who embeds the IoT UIDs 6118 into the laptops 1122 and 1124 prior to sale of and/or transfer of possession of the laptops 1122 and/or 1124 to the end user 1136.
In another non-limiting example, the end user 1136 may be the first entity to provide the device property data 6124 corresponding to the laptops 1122 and 1124 to the registrar 1130, after purchasing and taking possession of the devices, to register them in the name of the end user 1136. In other words, in embodiments, a manufacturer need not interact with the registrar 1130 to embed IoT UIDs 6118 into devices.
In another non-limiting presale example, a manufacturer 1134 may send device property data 6132 (
As explained in greater detail herein, embodiments of the current disclosure may provide for bootstrapping the IoT UID registration process, which may occur presale or post-sale. In a non-limiting example of the bootstrap, a manufacturer 1134, e.g., a presale embedding, or an end user, e.g., post-sale embedding, boots up a newly-minted Greenfield device, which then proceeds to contact the device management platform to get an IoT UID 6118 from the IoT device registrar 1130. Embodiments of the current disclosure may provide for batch registration of newly-minted Greenfield devices. Embodiments of the current disclosure may provide for a device to be “claimed” upon activation by an end user before registration can proceed, which may include updating ownership information stored in the registry 1129, updating a chain of title stored in the registry, etc.
Accordingly, illustrated in
Flow 40100 concerns a scenario in which the device manufacturer 40114 is the entity embedding the IoT UIDs 6118 into Greenfield devices, which, in embodiments, may be prior to a sale of the Greenfield devices to an Enterprise/Device OEM 40122. Accordingly, at 40120, the manufacturer 40114 may generate and transmit device property data of one or more manufactured Greenfield device to the IoT device registrar 1130. At 40120, the IoT device registrar 1130 may then generate an IoT UID 6118 for each of the one or more Greenfield devices corresponding to the received device property data and transmit the IoT UIDs back to the manufacturer 40114. At 40122, the manufacturer 40114 may load/install/embed the IoT UIDs received from the registrar 1130 into the one or more Greenfield devices. In embodiments, the registrar 1130 may generate records in the registry for the Greenfield devices when the IoT UIDs 6118 are generated but indicate, in the records, that Greenfield devices are “unclaimed”, e.g., that they have not been provisioned by their eventual first end users. In embodiments, the manufacturer 40114 may fully register the one or more Greenfield devices after receiving the IoT UIDs 6118 at 40122, such that the IoT device registrar 1130 records the manufacturer 40114 as the owner of the one or more Greenfield devices.
Flow 40110 concerns post-sale registration and/or claiming of the one or more Greenfield devices from flow 40100 upon a bootstrap event, e.g., turning a device on by a registering party 40112. Accordingly, at 40130 the registering party 40112 may turn on the one or more newly purchased and/or acquired Greenfield devices, which triggers a bootstrap event/process in each of the one or more Greenfield devices. In embodiments, the bootstrap process may cause each of the one or more Greenfield devices to transmit their embedded IoT UID 6118 and/or device property data to the device management platform 40116. At 40132, the device management platform 40116 receives the IoT UIDs 6118 and/or device property data and sends a registration request 6112 (
Illustrated in
Turning to
As shown in
Illustrated in
As shown in
Referring to
As shown in
Illustrated in
Shown in
In embodiments, an embedding tool may be used to embed IoT UIDs 6118 into devices (Greenfield and/or Brownfield). Non-limiting examples of embedding tools include USB cables and/or other type of communication cables, flash memory chips and/or writers, CDs, DVDs, network cards, and/or any type of device capable of loading data to an electronic device.
Referring again to
As a non-limiting example, an enterprise user 1136 (
Illustrated in
Flow 51100 concerns a scenario in which the registering party 51112 wants to register one or more Brownfield devices with virtual IoT UIDs prior to the Brownfield devices entering service within an operational network, e.g., the registering party 51112 may be an enterprise user provisioning the Brownfield devices for use in the enterprise user's corporate network. At 51122, the administrator 51114 may prepare the one or more Brownfield devices for registration with the IoT device registrar 1130. Such preparation may include updating the firmware and/or software of the one or more Brownfield devices, installing security credentials, e.g., public key infrastructure (PKI) keys and/or certificates, joining to a network domain, etc. The administrator 51114 may then collect/gather/generate device property data from the prepared one or more Brownfield devices, and then provide/transmit 51124 the gathered device property data to the IoT device registrar 1130. Upon receipt of the device property data, the IoT device registrar 1130 may generate 51126 IoT UIDs for each of the one or more Brownfield devices and associates each IoT UID with portions of the device property data corresponding to a particular Brownfield device. As disclosed herein, such associations may be accomplished via a record 1152 (
Flow 51110 concerns a scenario where a bootstrap event/process is initiated by the registering party 51112 on a Brownfield device and registers with the IoT device registrar 1130. At 51130, the registering party 51112 initiates the bootstrap event on the Brownfield device which transmits device property data 6124 to the device management platform 51116. The device management platform 51116 may then relay 51132 the device property data 6124 to the IoT device registrar 1130. At 51134, the IoT device registrar 1130 may validate that device property data, e.g., check that the registering party 51112 is authorized to register the Brownfield device using encryption certificates, as disclosed herein; and/or verify that the device property data matches any device property data for the Brownfield device previously submitted to the IoT device registrar 1130 by the administrator, such as in flow 51100. At 51136, the IoT device registrar 1130 may transmit a registration confirmation message to the device management platform 51116 with may include the IoT UID and/or a generated trust and/or risk indicator/level/score for the Brownfield device. At 51138, the IoT device registrar 1130 may transmit the IoT UID, device property data, and/or a trust and/or risk indicator/level/score for the Brownfield device to the SPG 51118. In embodiments, at 51120, the device management platform 51116 may transmit credentials to the Brownfield device.
Illustrated in
The Brownfield device may then proceed to set up its control plane functionality by transmitting 52122 device registration data to a device management platform 51116. The device registration data may include the security certificate the Brownfield device used to register with the cloud platform 52112, other device property data, and/or any data the Brownfield device received from the cloud platform 52112 during the data plane setup process 52100. The device management platform 51116 may then verify 52124 the device registration data and transmit 52126 an event message, e.g., 6116 (
Shown in
As shown in
Illustrated in
As shown in
Illustrated in
As shown in
Illustrated in
As shown in
An additional non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering sensors on a resource distribution system, e.g., a water, gas/oil, and/or electricity, distribution system, with an IoT UID device registry without an administrator to physical contact and/or visit each of the sensors at their operating location. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering satellites already in orbit with an IoT UID device registry. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering vehicles in a fleet with an IoT UID device registry. Another non-limiting use case for the methods and/or apparatuses disclosed herein for provisioning IoT UIDs in Brownfield devices includes registering pallet tracking devices already in the field, e.g., attached to pallets, with an IoT UID device registry.
Referring again to
Illustrated in
Flow 61104 concerns a scenario in which the registering party 61100, e.g. a factory/original equipment manufacturer (OEM) 1134, wants to register one or more pre-sale Greenfield devices with virtual IoT UIDs. Starting with a Greenfield device ready for credentials 61120, at 61122 device property data 6124 (
Flow 61114 concerns a scenario in which the registering party 61100, possibly an enterprise 1136, initiates the bootstrap event 61128 on a Greenfield device which transmits the device property data 6124 to the device management platform 61116. The device management platform 61116 may then relay 61130 the device property data 6124 to the IoT device registrar 1130. At 61132, the IoT device registrar 1130 may validate the module information/device property data 6120 and associate the device property data 6124 and an enterprise name with a virtual IoT UID. At 61134, the IoT device registrar 1130 provides validation of success or failure to the device management platform 61116. At 61138, assigns an appropriate trust level to the module. At 61140, the IoT device registrar 1130 provide the IoT UID, assigned trust level and device property data 6124 to the SPG 61115. At 61142, to the device management platform 61116 may transmit the certificates, other credentials, and/or the IoT UIDs to the registering party 61100. At 61144, the registering party 61100 may load/store/embed the IoT UIDs into the one or more Greenfield devices, resulting in a Greenfield device/module ready for operations 61148.
Illustrated in
At flow 62100, an enterprise administrator 62108 claims ownership of an enterprise Greenfield device 62113. At 62114, the device management partner platform 62116 sends certificates for the enterprise devices 62113 acquired by the enterprise to the cloud platform 62110. At 62118, the device management partner platform 62116 sends certificates for the enterprise devices 62113 to the enterprise administrator 62108. At 62120, the administrator 62108 then claims the certificates on the cloud platform 62110 into an enterprise account. At 62122, an enterprise device 62113 is turned on.
At flow 62102, a data plane between the enterprise Greenfield device 62113 and the cloud platform 62110 is established. At 62124, the enterprise Greenfield device 62113 sends a device registration to the cloud platform 62110. At 62128, the cloud platform 62110 verifies the certificate provided by the enterprise Greenfield device 62113. At 62130, the cloud platform 62110 sends a confirmation of registration success to the enterprise Greenfield device 62113 which, in embodiments, may establish, the data plane 62132 between the enterprise Greenfield device 62113 and the cloud platform 62110.
At flow 62104, a control plane between the enterprise Greenfield device and the device management partner platform 62112 is setup. At 62134, the enterprise Greenfield device sends device registration information to the device management partner platform 62112. At 62138, the device management partner platform 62116 verifies the credentials. At 62140, the device management partner platform 62112 relays the event device provisioning information to the IoT device registrar 1130. At 62142, the IOT device registrar 1130 maps the provided provisioning information onto an IoT UID, updates the registry and provides a trust level. At 62144, the IOT device registrar 1130 relays confirmation of success to the device management partner platform 62116. At 62148, the IOT device registrar 1130 relays confirmation of success and the device trust level to the SPG. At 62150, the device management partner platform 62116 relays confirmation of registration success to the enterprise Greenfield device which mat signal that control plane 62152 between the enterprise Greenfield device and the device management partner platform 62116 is enabled/active. The device may then be provisioned 62154 and managed 62158 and ready to be used 62160.
Illustrated in
At flow 63120, firmware on an enterprise Greenfield device 62113 is updated. At 63124, the ecosystem 63100 exchanges notifications and events with the IoT device registrar 1130. At 63126, the networks 63102 exchange notifications and events with the IoT device registrar 1130. At 63128 the ecosystem 63100 provides the firmware update data, e.g., the module, chipset, device types, and the like, to the IoT device registrar 1130. At 63130, the IoT device registrar 1130 links the firmware update data to a specific IoT UID. At 63132, the IoT device registrar 1130 provides the firmware update, e.g., IoT UID, module, device and the like, to the device management partner platform 62116. At 63134, the device management partner platform 62116 may send a trigger signal to the enterprise device 62113 causing the enterprise device 62113 to update the firmware. At 63140, the enterprise device 62113 may then update the firmware. At 63142, the enterprise device 62113 may relay a status value, reflective of the success of firmware update, to the device management partner platform 62116. At 63144, the device management partner platform 62116 may relay a status value, reflective of the success of the firmware update, to the IoT device registrar 1130. At 63148 the IoT device registrar 1130 may update the device's IoT UID, trust level or the like.
At flow 63122, information regarding a security event is propagated through the system. At 63150, a device attribute change is communicated from the ecosystem 63100 to the IoT device registrar 1130. At 63152, the IoT device registrar 1130 links the device attribute change with the device's virtual IoT UID. At 63154, the IoT device registrar 1130 may provide a security signal, data on the event, information on IoT device, and the like, to the device management partner platform 62116. At 63158, the device management partner platform 62116 may send information regarding the event and IoT UID to the SPG. At 63160, the device management partner platform 62116 may trigger a security action, e.g., patching. At 63162, the IoT device registrar 1130 may send event data to the SPG 61115. In embodiments, at 63164, the IoT device registrar 1130 may provide a security signal event, e.g., the IoT UID, event details, and the like, to the cloud platform 62110. At 63168, the cloud platform 62110 may trigger a security action.
Illustrated in
Illustrated in
Illustrated in
Illustrated in
Illustrated in
In a non-limiting example of the bootstrap registration process, a manufacturer, e.g., pre-sale, or an end user, e.g., post-sale, boots up a newly-minted Greenfield device which then proceeds to contact the device management platform, which may then request (of the IoT device registrar) to register the Greenfield device via a virtual IoT UID. Embodiments may provide for batch registration of newly-minted Greenfield devices. Embodiment may provide for a device to be “claimed” upon activation by an end user before registration can proceed, which may include updating ownership information stored in the registry, updating a chain of title stored in the registry, etc. Embodiments may provide for verifying that the entity requesting registration of the Greenfield device authorized to do so. Verification authorization of the entity requesting registration may include the use of cryptographic keys, a Public Key Infrastructure (PKI), or the like.
Referring again to
Non-limiting examples of user types include one or more end users 1136, e.g., enterprise, manufacturer 1134, e.g., an original equipment manufacturer (OEM) and/or factory employees, the IoT device registrar 1130, and/or a third party 1138. Information may be provided, e.g., displayed, by a Single Pane of Glass (SPG), which may provide a graphical user interface (GUI), e.g., any of GUIs 22108 (
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. With further reference to
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. With further reference to
Certain further aspects of the example method are described herein, any one or more of which may be present in certain embodiments. With further reference to
With reference to
Certain further aspects of the example method are described herein, any one or more of which may be present in certain embodiments. With further reference to
With reference to
The input processing circuit 78102 may be structured to interpret a device property data update request 78114 for an IoT device. The IoT UID identification circuit 78104 may be structured to determine one or more IoT UIDs 78116 corresponding to the IoT device, based at least in part on the device property data update request 78114. The device lookup circuit 78106 may be structured to generate a query 78118 that includes the one or more IoT UIDs 78116, and retrieve first device property data 78120 corresponding to the one or more IoT UIDs 78116. The query provisioning circuit 78108 structured to transmit the query 78118 to an IoT device registrar server, e.g., the server 1126 in the registrar 1130 (
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. With further reference to
Embodiments of the current disclosure may provide for continuous IoT identity lifecycle management.
Embodiments of the current disclosure may also provide for alert management 80110, e.g., the setting and triggering of alerts based on conditional logic. For example, the owner and/or operators of a network connected device may set alerts configured to notify the owner and/or operator of unusual activity associated with one or more network connected devices. Embodiments of the current disclosure may also provide for analytical analysis of data corresponding to the network connected devices, e.g., usage and/or trend data, risk management data, data compliance management, etc. Such analysis may be performed by the registration server 1126 (
The functions 81110 may provide corresponding value, e.g., benefits 81120, such as a trusted device identity registry 81122 that supports secure provisioning and management of network connected device identities, trusted two-way authentication 81124 before initiating secure downloads, identity-based segmentation and maintenance 81126, and/or identity lifecycle management and governance 81128 (which may help an entity, e.g., 1134 (
As will be understood, security in traditional IoT networks is often lacking and/or non-existent due to lack of expertise and/or education regarding IoT security within an enterprise, e.g., a corporate network. When security is considered by an enterprise, it is often an afterthought or considered non-critical when compared to the incentives of launching a new IoT solution early in the marketplace. Lack of experience by an enterprise and/or a failure to understand and/or appreciate IoT security may cause an enterprise to hire a third party to conduct a security assessment/inspection. Such assessments, however, do not provide continuous security. Further, the resources required to manage IoT device lifecycles and security generally scale exponentially. As will be understood, lifecycle management of network connected devices, and the corresponding infrastructure disclosed herein, may ease and/or otherwise improve security and/or risk management of network connected devices, to include easing and/or improving the ability of an entity that owns or operates network connected devices to comply with government and/or industry standards. For example, in certain aspects, the registry 1129 (
With further reference to
The flow 82100 may then include flow 82110. In flow 82110, as depicted by dashed line 82130, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and devices and databases in the ecosystem 82120. In addition, in flow 82110, as depicted by dashed line 82132, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and the one or more networks 82122. In flow 82110, as depicted by line 82134, a notification of a firmware update, e.g., module/chipset/device types, may be transmitted from the ecosystem 82120 to the IoT device registrar 1130.
Next, in flow 82110, as depicted by line 82136, IoT device registrar 1130 may identify an IoT UID associated with the device 82112, and may transmit the firmware update and the IoT UID to the device management partner platform 82116, for example, by piggybacking the IoT UID onto a message containing the firmware update, as described herein, e.g.,
With further reference to
With further reference to
The flow 83100 may then include flow 83102, which may include flow 83104 and flow 83106. In flow 83102, as depicted by dashed line 83110, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and devices and databases in the ecosystem 82120. In addition, in flow 83102, as depicted by dashed line 83112, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and the one or more networks 82122.
With further reference to
Next, in flow 83104, as depicted by line 83116, IoT device registrar 1130 may associate the module/chipset/device type of the notification with one or more IoT UIDs.
Subsequently, in flow 83104, as depicted by line 83118, IoT device registrar 1130 may associate the IoT UIDs with the device type of the device 82112 and/or modules in the device 82112 that should receive the firmware update, and may transmit the firmware update and the IoT UIDs and/or the device and/or module type to the device management partner platform 82116, for example, by piggybacking the IoT UID onto a message containing the firmware update, as described herein. Then, in flow 83104, as depicted by line 83120, the device management partner platform 82116 may trigger the device 82112 to implement the firmware update transmitted with the associated IoT UID. Next, in flow 83104, as depicted by line 83122, the device 82112 may apply the firmware update. Subsequently, in flow 83104, as depicted by line 83124, device 82112 may send a notification to the device management partner platform 82116 that the firmware update was successfully applied. Then, in flow 83104, as depicted by line 83126, the device management partner platform 82116 may send a notification to the IoT device registrar 1130 that the firmware update was successfully applied. Next, in flow 83104, as depicted by line 83128, the IoT device registrar 1130 may update a trust level/rating/score associated with the IoT UID, based on the successful firmware update.
With further reference to
Next, in flow 83106, as depicted by line 83134, the IoT device registrar 1130 may generate a security signal event notification indicating the security event, and may notify the device management partner platform 82116 of device types that are associated with the security event. Also, in flow 83106, as depicted by line 83136, the IoT device registrar 1130 may send a notification to the SPG 82118 regarding the security event and a list of IoT UIDs associated with the security event, which may be displayed by the SPG 82118. Also, in flow 83106, as depicted by line 83138, when the device management partner platform 82116 receives the security signal event notification, it may trigger one or more security actions on the devices of the type associated with the security event, including the device 82112, such as quarantining the devices, disabling the device, notifying the device of the security event, or other actions as described herein.
In flow 83106, as depicted by line 83140, the IoT device registrar 1130 may transmit the security signal event notification to the SPG 82118, e.g., to be displayed. In flow 83106, as depicted by line 83142, the IoT device registrar 1130 may transmit the security signal event notification, the device type associated with the security event, and the IoT UID to the cloud platform 82114. In flow 83106, as depicted by line 83144, when the cloud platform 82114 receives the security signal event notification, it may trigger one or more security actions on the devices of the type associated with the security event, including the device 82112, such as quarantining the devices, disabling the device, notifying the device of the security event, or other actions as described herein.
With further reference to
The flow 84100 may then include flow 84102, which may include flow 84104 and flow 84106. In flow 84102, as depicted by dashed line 84110, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and devices and databases in the ecosystem 82120. In addition, in flow 84102, as depicted by dashed line 84112, notifications and information on events, as described herein, may be transmitted to/from the IoT device registrar 1130 and the one or more networks 82122.
With further reference to
Next, in flow 84104, as depicted by line 84116, IoT device registrar 1130 may associate the module/chipset/device type of the notification with one or more IoT UIDs.
Subsequently, in flow 84104, as depicted by line 84118, IoT device registrar 1130 may associate the IoT UIDs with the device type of the device 82112 and/or modules in the device 82112 that should receive the firmware update, and may transmit the firmware update and device and/or module type and/or the IoT UIDs to the device management partner platform 82116, for example, by piggybacking the information onto a message containing the firmware update, as described herein. Then, in flow 84104, as depicted by line 84120, the device management partner platform 82116 may trigger the device 82112 to implement the firmware update transmitted with the associated IoT UID. Next, in flow 84104, as depicted by line 84122, the device 82112 may apply the firmware update. Subsequently, in flow 84104, as depicted by line 84124, device 82112 may send a notification to the device management partner platform 82116 that the firmware update was successfully applied. Then, in flow 84104, as depicted by line 84126, the device management partner platform 82116 may send a notification to the IoT device registrar 1130 that the firmware update was successfully applied. Next, in flow 84104, as depicted by line 84128, the IoT device registrar 1130 may update a trust level/rating/score associated with the IoT UID, based on the successful firmware update.
With further reference to
Next, in flow 84106, as depicted by line 84134, the IoT device registrar 1130 may generate a security signal event notification indicating the security event, and may notify the device management partner platform 82116 of device types that are associated with the security event. Also, in flow 84106, as depicted by line 84136, the IoT device registrar 1130 may send a notification to the SPG 82118 regarding the security event and a list of IoT UIDs associated with the security event, which may be displayed by the SPG 82118. Also, in flow 84106, as depicted by line 84138, when the device management partner platform 82116 receives the security signal event notification, it may trigger one or more security actions on the devices of the type associated with the security event, including the device 82112, such as quarantining the devices, disabling the device, notifying the device of the security event, or other actions as described herein.
In flow 84106, as depicted by line 84140, the IoT device registrar 1130 may transmit the security signal event notification to the SPG 82118, e.g., to be displayed. In flow 84106, as depicted by line 84142, the IoT device registrar 1130 may transmit the security signal event notification and the device type associated with the security event, and/or the IoT UID, to the cloud platform 82114. In flow 84106, as depicted by line 84144, when the cloud platform 82114 receives the security signal event notification, it may trigger one or more security actions on the devices of the type associated with the security event, including the device 82112, such as quarantining the devices, disabling the device, notifying the device of the security event, or other actions as described herein.
In embodiments, lifecycle management may include performing status checks of devices and their current configuration states, e.g., installed patches, installed hardware, number of active network cards, etc. Lifecycle management may include detecting changes in the properties of a device, e.g., detecting and/or recording events. Events may come, for example, from a device manager, a connection management platform (CMP), a Remote Authentication Dial-In User Service (RADIUS) feed (e.g., event stream), and/or a Home Location Register (HLR). Lifecycle management may include detecting security events. Lifecycle management may include tracking of ownership changes in the IoT device registry. Embodiments may provide for retirement of Greenfield and/or Brownfield devices, which may be real-world devices, virtual devices, or meta-devices. Embodiments may monitor for instances in which a permanently retired immutable device property, e.g., an International Mobile Equipment Identity (IMEI), appears in another device. Embodiments may provide for reincarnation/reuse/recycling of old IoT UIDs and/or for their permanent retirement. Embodiments may provide for data “sanity” checks. For example, determining whether data from a device at 30% battery or less should be collected and/or considered trustworthy. Detection of a device's being down, e.g., unreachable, offline, inoperable, or otherwise unavailable, as disclosed herein, may be provided by certain embodiments. Embodiments may facilitate the pushing of updates and/or patches to devices. Lifecyle management may include modifying a trust indicator/level/score/rating of a device based on events. Embodiments may decrease a device's trust indicator/level/score/rating value if the corresponding information in the IoT device registry starts to get stale, e.g., has not been updated and/or queried for at least a predetermined time. Embodiments may provide for polling of devices to provide updates to their stored property data.
Referring again to
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. The features shown in
With reference to
For example, devices may be virtual devices, e.g., objects in a metaverse having real-world counterparts (real-world devices), where the virtual device is a digital-twin of the real-world counterpart. A digital virtual device may have properties corresponding to its real-world counterpart that may be updated in real-time and/or on a periodic basis. Devices in the metaverse may be real-world devices, e.g., objects in the real-world having metaverse counterparts (digital twin virtual devices) and/or supporting metaverse activities. As another example, devices may be meta-devices, e.g., objects in the metaverse lacking real-world counterparts. In embodiments, a device may have modules that are virtual devices and modules that are meta-devices. In embodiments, an IoT device registry may provide for registration of virtual devices, real-world devices, and/or meta-devices, as disclosed herein, and/or the services and/or functions associated with registration for registered virtual devices, real-world devices, and/or meta-devices, as also disclosed herein. Any of virtual devices, real-world devices, and/or meta-devices may be Greenfield devices and/or Brownfield devices, and/or may have a combination of Greenfield modules and/or Brownfield modules.
In the apparatus 86100, the trust indicator 87108 may be displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. The apparatus 86100 may further include an asking price evaluation circuit 87110 structured to evaluate an asking price 87112 for the device based on at least one of: the device ownership data 86114, a certification that the device is not a stolen device, or a certification that the device has a fully accountable chain of title. The certification that the device is not a stolen device and/or the certification that the device has a fully accountable chain of title may be included in the record 86112 or in the device ownership data 86114, or may be provided from elsewhere, e.g., from the IoT device registrar 1130 (
With reference to
The method 89100 may include interpreting, via an IoT UID processing circuit, an IoT UID corresponding to a device 89102. The method may further include identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database, the record including device ownership data associated with the device 89104. The method may further include interpreting, via an ownership analysis circuit and based at least in part on the record, the device ownership data 89106. The method may further include transmitting, via an ownership provisioning circuit, the device ownership data 89108.
With reference to
With reference to
In the method 89100, the trust indicator may be displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. The method 89100 may further include evaluating an asking price for the device 91104. The evaluating the asking price for the device may be based on at least one of: the device ownership data, a certification that the device is not a stolen device, or a certification that the device has a fully accountable chain of title. The method 89100 may further include evaluating an asking price for a group of devices 91106, which may be based on ownership data for each device. The method 89100 may further include validating a supply chain 91108. The validating the supply chain may further include determining whether modules of the device were sourced from authorized vendors 91110. The validating the supply chain may further include determining whether modules of the device were sourced from fair trade certified sources 91112. The validation may be based on the device ownership data, or may be based on data provided from elsewhere, e.g., from the IoT device registrar 1130 (
With reference to
Certain further aspects of the example system are described herein, any one or more of which may be present in certain embodiments. In the system 92100, the device ownership data 92110 may include a record of historical ownership 92112. In the system 92100, the device may include a plurality of modules, each module having corresponding ownership data. In the system 92100, the server 92104 may be further structured to restrict access to information about the device from an owner of the device. In the system 92100, the server 92104 may be further structured to provide updated ownership data 92114 to replace the device ownership data 92110 associated with the device.
The method 93100 may include interpreting, via an input processing circuit, user input identifying a device ownership query for a device 93102. The method further includes generating, via a query provisioning circuit, a query for an IoT UID, corresponding to the device, to an IoT device registrar server 93104. The method further includes identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database at the IoT device registrar server, the record including device ownership data associated with the device 93106. The method further includes interpreting, via an ownership analysis circuit and based at least in part on the record, the device ownership data 93108. The method further includes transmitting, via an ownership provisioning circuit, the device ownership data to a user 93110.
With reference to
With reference to
Certain further aspects of the example system are described herein, any one or more of which may be present in certain embodiments. In the system 96100, the device ownership data 96118 may include a record of historical ownership 96120. In the system 96100, the device may include a plurality of modules, each module having corresponding ownership data 96118. In the system 96100, the server 96108 may be further structured to restrict access to information about the device from an owner of the device. In the system 96100, the server 96108 may be further structured to provide updated ownership data 96122 to the database to replace the device ownership data 96118 associated with the device.
In certain embodiments, the tracking of a chain of title may include identification of a trust level, score, and/or rating, which may be dynamic. Certification may be used to evaluate an asking price for a device, or a group of devices. Embodiments provide for an entity to claim ownership of a device, which may also relate to device setup and/or provisioning, as disclosed herein. Embodiments may provide for the detection of device properties, e.g., location, usage profile, network, interface language, device settings, associated telephone number, which may be indicative of a change in ownership.
Accordingly, embodiments of the IoT device registry, as disclosed herein, may provide for a trusted source of ownership data relating to device and/or their modules. Such embodiments may provide for improved sales and/or marketplaces processes, e.g., by providing for fast and reliable verification of a chain of title for a device and/or indications that a chain of title for a given device may have one or more discrepancies. Embodiments of the IoT device registry, as disclosed herein, may provide for improved detection of fraud and/or possible security vulnerabilities by tracking chains of title for devices so that such chains of title can quickly be verified using a trusted source. Embodiments of the IoT device registry, as disclosed herein, may provide for improved billing processes by tracking leased and/or licensed devices. For example, embodiments of the current disclosure may provide for accurate tracking of an amount of time a device is in the possession of a party renting and/or leasing the device. Embodiments of the current disclosure may also provide for improved shipment tracking as events for a device, e.g., a white good, such as a refrigerator, may be reported to the IoT device registry, e.g., as event messages, when transfers of possession occur and/or when a device is scanned as a checkpoint in a distribution network. Embodiments of the current disclosure may also provide for improved quality of a supply chain by identifying which entities in the supply chain, who may show up in a chain of title, have low trust and/or high-risk indictors, as disclosed herein, where they can be removed and/or replaced with entities having higher trust and/or lower risk indicators. A non-limiting use case of the current disclosure includes using an IoT device registry, as disclosed herein, to track shipping containers at a port facility and/or between port facilities. Another non-limiting use case of the current disclosure includes using an IoT device registry to track ownership of city assets, e.g., water system devices, such as pumps, in the event of boundary changes, e.g., congressional and/or other legislative district boundaries change, part of a county becomes absorbed by a city or vice-versa, and/or portions of one city are moved to another city.
Embodiments of the current disclosure provide for a method of rating of Internet of Things (IoT) devices. The rating may be an indicator, e.g., a score, that relates to a trust indicator (also referred to as a trustworthiness score or trust indicator herein) and/or a risk indicator (also referred to herein as a risk score), associated with a device. As will be understood, risk and/or trust indicators may be reciprocals of each other, e.g., a device with a low trust score may have a high-risk score and vice-versa. A risk indicator may reflect a confidence measure associated with a device. The confidence measure may relate to a confidence that the device has not been tampered with and/or may reflect the security of a device. A risk indicator may reflect the potential risk that a device may deliberately or inadvertently fail to execute the desired operation, leak sensitive data when operated, meet contractual obligations, and/or comprise the security of other devices.
In embodiments, the risk indicator may be based on the known history of the device, location, predictability of location, predictability of behavior, age of the device, and the like. In some case, a risk indicator may reflect the number of operational anomalies in the lifespan of the device. Operational anomalies may reflect operations outside of expected operating parameters for a device. Operational anomalies may include software crashes, physical locations, movement, power consumption, data gaps, error rates, usage statistics, temperatures, and the like.
In embodiments, a risk indicator may include an objective score over all devices. In some cases, the risk indicator may be normalized or be relative with respect to a class of devices, locations, functions of the devices, and the like. In one example, more complex devices with more hardware, software components, and connectivity may have a higher objective risk indicator than simple sensors with one hardware component and simple wired connectivity. Higher complexity devices may include a relative risk indicator that reflects the relative risk indicator for only a specific type of high complexity devices. The normalized risk indicator may be a score that ranges between (0) and (100), for example with the lowest score assigned to devices with the lowest risk for the particular class of devices and the highest score assigned to devices with the highest risk.
A risk indicator may be dynamic and may change over time as a device ages, changes locations, is updated with different software and hardware, and the like. A risk indicator may change based on an operation of a device. A risk indicator may change for different operations of a device. For example, a device may be operable to receive data and provide data to a user. In one example, the operation of receiving data by the device may have a higher risk indicator than the operation of providing data to a user since there may be a risk that the data that is received by the device may be exposed or leaked.
A risk indicator may be assigned to a new device that is being deployed as well as devices that have already been deployed. Prior to deployment, a Greenfield device may be evaluated and assigned an initial risk indicator. The risk indicator may reflect the complexity of the device, installed software, connectivity, configuration, capabilities of operations, and the like. After the device is deployed the risk indicator may be updated based on the location of deployment, operator of the device, history of operation, predictability of operation, and other metrics described herein. The operation of the device may be monitored and the operation history may be stored at a registrar server and used to compute a risk indicator. A deployed device, such as a Brownfield device, may be assigned an initial risk indicator. An initial risk indicator may be assigned based on an audit of the device hardware, software, location, capabilities, and the like. In many cases, a Brownfield device may be assigned a higher initial risk indicator than an equivalent Greenfield device since the complete history of the Brownfield device may not be known. The operation of the Brownfield device may be monitored and the risk indicator adapted in the same manner as for the Greenfield device.
In embodiments, operations such as updating or patching software of a device may decrease the risk indicator of a device. In embodiments, gaps within the operational record histories of a device may increase the risk indicator of a device. In some embodiments, operators of devices may be provided with reports that include data as to what factors contributed to a particular risk indicator and in some cases operators may be provided with a list of actions for improving (i.e. decreasing) the risk indicator. In some cases, updates and/or modifications to devices to improve the risk indicator may be implemented automatically. Operators of devices may be incentivized to improve the risk indicator of devices by providing timely and complete histories of devices, updating devices, and the like.
In some embodiments, a risk indicator may be computed as a weighted sum of different scores that reflect aspects of the hardware, software, operation history, location, and the like. The weights and/or functions for generating a score may be defined by a user. In some embodiments, weights and functions for computing the risk indicator may be determined by a trained neural network, artificial intelligence system, and the like. In some embodiments, a risk indicator may include a plurality of scores and components that reflect the risk for different functions, components, elements, locations, and the like. The plurality of scores comprising a risk indicator may be processed according to the preferences of a user, organization, and the like to determine a personalized risk indicator.
A risk indicator may be stored in an IoT device registrar server. The registrar server may be queried for a risk indicator for a device. In some cases, a query for a risk indicator may include identifying data for the device and/or contextual data. Contextual data may include location data, time data, type of operation to be executed by the device, and the like. When contextual data is provided with the query the registrar server may return a risk indicator that reflects the contextual data. When contextual data is provided with a query the weights and functions used to compute the risk indicator may be selected to reflect the contextual data.
Indicators and/or scores may be converted from one paradigm/entity to another, in which the IoT device registry may serve as a baseline score to which the others can be compared. For example, a first entity, 1136 (
In embodiments, risk indicators and other trust indicators may be provided for online servers to include game/metaverse servers. Embodiments may provide for augmented reality (AR) trust indicators and risk indicators to be shown in relation to devices. For example, automatic teller machines (ATM) and/or card readers may be identified and the risk indicator for the devices may be queried from the registrars. Augmented reality interfaces may provide a display such as an overlay that identifies the risk indicator and/or the trust indicator for the ATM. The augmented reality may include color codes to show the relative risk or trust associated with the ATM. In some embodiments, a query may include contextual data. For example, continuing with the ATM example, contextual data may include the location (such as GPS location data) of the ATM, the transaction type that the user wishes to use the ATM for, and a picture or a video of the ATM. The contextual data may be used to further customize or personalize the risk indicator and trust indicators. For example, the pictures and video of the ATM may be compared to stored pictures and video of the ATM and the risk indicator may be adjusted if the new pictures or video show differences to a historical image of the ATM.
Referring again to
Turning to
Referring to
Turning to
Referring to
Embodiments may provide for risk and/or trust scores/indicators and/or certification of devices, e.g., servers and/or other physical assets, supporting metaverse activities, and/or devices appearing and/or existing within the metaverse. Devices in the metaverse may be virtual devices, e.g., objects in the metaverse having real-world counterparts (real-world devices), where the virtual device is a digital-twin of the real-world counterpart. Non-limiting examples of virtual devices include: vehicles; rooms; buildings; controllers (thermostats, security system key pads, process logic controllers, and the like); sensors (temperature, pressure, voltage, amperage, magnetic fields, weather conditions, and the like); and/or other types of devices where having both real-world and metaverse versions of the devices provides a benefit. A digital virtual device may have properties corresponding to its real-world counterpart that may be updated in real-time and/or on a periodic basis. In embodiments, a digital twin may be updated with predicted properties for its real-world counterpart in the event the real-world counterpart is unable to communicate with an IoT device registry to which the real-world counterpart and/or its digital twin may be registered with, as described herein. Devices in the metaverse may be real-world devices, e.g., objects in the real-world having metaverse counterparts (digital twin virtual devices) and/or supporting metaverse activities. Non-limiting examples of real-world devices include servers hosting metaverse rooms, servers hosting webstores from which an avatar can purchase goods or services; user devices used to access a metaverse; and/or counterparts to virtual devices, as described herein. Devices in the metaverse may be meta-devices, e.g., objects in the metaverse lacking real-world counterparts. In embodiments, a device may have modules that are virtual devices and modules that are meta-devices. In embodiments, an IoT device registry may provide for registration of virtual devices, real-world devices, and/or meta-devices, as disclosed herein, and/or the services and/or functions associated with registration for registered virtual devices, real-world devices, and/or meta-devices, as also disclosed herein.
A risk score/indictor may be a measure of the risk of taking a particular action (or set of actions) and/or interacting with a device and/or a set of devices. A trust score/indictor may be a measure of trust of a device as disclosed herein. A risk score may equate to a trust score, e.g., high risk equals a low trust score and vice-versa. In embodiments, a scale for a risk score may be user adjustable in relation to a base risk score scale maintained by an IoT device registrar. For example, a user with a low risk tolerance may see objects with red risk warnings that other users with higher risk tolerances may see with green checkmarks. Conversely, a user with a high risk tolerance may see objects with green checkmarks that other users with lower risk tolerances may see with red risk warnings. In embodiments, a user's risk score scale may be defined by the user, another use, and/or inferred/predicted via artificial intelligence based at least in part on one or more characteristics of the user, e.g., age, sex, location, medical condition, etc., and/or by analyzing their actions within the metaverse. In such embodiments, the artificial intelligence may adjust the user's risk score scale as the user spends an increasing amount of time in the metaverse and gains “metaverse street smarts”.
As a non-limiting example, a user in the metaverse may be provided with a risk and/or trust score/indicator of a server (retrieved/queried from an IoT device registrar using the server's IoT UID) before entering an area, e.g., a room, in the metaverse hosted by that server. Embodiments may provide for risk and/or trust scores/indicators of users, a plurality of users, and the like, within the metaverse (that have IoT UIDs registered with an IoT device registrar), such as in an area that a user is about to enter or interact with. Such risk and/or trust scores may be based on the risk and/or trust score of devices associated with the user that are also registered with the IoT device registrar. For example, embodiments may assign a risk score of red (high risk) to an avatar having an IoT UID corresponding to a user associated with fraudulent activities and/or devices registered in an IoT device registry 1129 (
The device in the metaverse may be an area of the metaverse, such as a room, a building, an outside environment, and the like. As the user moves through the metaverse a trust indicator may be determined for the device in the metaverse, where for instance, a trust indicator is transmitted to a user before the user enters an area of the metaverse associated with the device, e.g., a room, an object within a room, an avatar, etc. The trust indicator of the device in the metaverse may be based at least in part on a combination of trust indicators of a plurality of devices associated with the device, e.g., an avatar associated with five (5) devices where four (4) devices have high trust scores and one (1) device has a medium trust score may be assigned a high trust level, whereas the same avatar associated with five (5) devices where four (4) have medium trust scores and one (1) has a high trust score may receive a medium trust score. The trust indicator of the device may be based at least in part on a combination of trust indicators of a plurality of modules associated with the device. The trust indicator may be updated based on interactions with the device, e.g., an device unfamiliar to the IoT UID registry and/or a user using the IoT UID registry may initially receive a low trust/high risk score, where additional interactions with the device (without incident) may raise the trust score/lower the risk score of the device. In embodiments, trust and/or risk scores may be tailored to a particular user/entity using the IoT UID device. For example, a device may be unfamiliar to a first user and receive a low trust/high risk score with respect to the first user. The same device, however, may be familiar to a second user and receive a high trust/low risk score with respect to the second user.
The trust and/or risk indicator may be a numeric value, an enumerated value, and the like. The trust and/or risk indicator may be displayed, such as a value, a color-coded value, a graphic display of a value, and the like. The trust and/or risk indicator may include a trust/risk level, a trust/risk score, a trust/risk rating, and the like. The trust and/or risk indicator may be based at least in part on a location of the device, a time period, a software and/or firmware version of the device, a trust and/or risk indicator of other devices associated with the device, a trust and/or risk indicator of a user associated with the device, and the like. For example, an avatar representing a kids' cartoon character may have a lower trust rating in a metaverse room when a local time is between midnight and 4:00 am than the avatar would have in the same room between 9:00 am to 5:00 pm. As another example, an object appearing in the metaverse outside of a known schedule for the object may receive a lower score than the object has during its scheduled times. The determining of the trust and/or risk indicator may be based at least in part on artificial intelligence. The trust and/or risk indicator may be reflective of the device being a Greenfield device or a Brownfield device, as disclosed herein.
In certain aspects, an interaction may be authorized or prohibited with a device based at least in part on the trust and/or risk indicator, such as where the interaction is an exchange of data with the device, establishing a network connection with the device, and the like. In embodiments, the trust and/or risk indicator may be based on an event of the device, such as a transfer of ownership, a patching of the device, an updating of software or firmware of the device, and the like.
Referring to
Referring to
Referring to
Referring to
In a non-limiting example, a user in the metaverse may approach a room operated by a server. The server may be registered with an IoT device registry, as disclosed herein, such that the user can query the server for its IoT UID and then query the IoT device registry to retrieve the security and/or risk indicator of the server. In another non-limiting example, the server may present the user with a trust and/or risk indictor with an encryption-based certificate from the IoT device registrar. In another non-limiting example, a user may encounter a meta-device, e.g., a jet fighter plane, where a risk score may be depicted above the jet fighter plane such that the user can see and accept the risk, e.g., a cyber security risk, of interacting with the jet, i.e., flying it in the metaverse. The risk score may be based at least in part on the manufacturer/software company who programmed the jet fighter for the metaverse. In another non-limiting example, a user may interact with a virtual home security keypad in the metaverse, where the user may be accessing the metaverse from a location other than their home, where the virtual security keypad is a digital twin of a security keypad in the user's house and can control a corresponding security system for the user's home. If the virtual security keypad and its real-word counterpart are registered with an IoT device registry, as described herein, the user can verify that the virtual security keypad is authenticate and not a spoofed object made by a malicious actor.
Embodiments may provide for the depiction and use of risk and/or risk scores/indicators, as disclosed herein, and/or certification via augmented reality (AR). Embodiments may depict risk scores of objects encountered by a user. As a non-limiting example, a user wearing an AR device, such as an AR headset, AR contact lenses, AR glasses, or AR goggles, may see an automated teller machine (ATM) (in the real-world) associated with a green indicator, e.g., an AR object overlaid on the ATM, if the device has a sufficiently high trust indicator, e.g., trust score/rating/level value, or red if the device has a sufficiently low trust indicator. Embodiments may depict trust indicators for individuals based on the trust indicators of devices associated with the scored individuals.
In embodiments, the device in the AR may be an IoT device, a server, a user, an avatar, and the like. A device in the AR may correspond to an area of a metaverse, such as where the area in the metaverse is a room, a structure, an outside environment, and the like, in the metaverse. The device in the AR may be a virtual device, a real-world device, or a meta-device, as disclosed herein.
In certain aspects, a trust and/or risk indicator of the device in the AR may be determined, such as where the trust indicator has a numeric value, an enumerated value, and the like. In embodiments, the trust and/or risk indicator may be displayed via an AR device, such as in association with a real-world device, overlaid on a real-world device, and the like. The AR device may be an AR headset, AR contact lenses, AR glasses, AR goggles, and the like. In embodiments, the trust and/or risk indicator may be displayed as a color-coded value. The trust and/or risk indicator may be based at least in part on a location of the device, a time period, a software and/or firmware version of the device, a trust and/or risk indicator of a device associated with the device, a trust and/or risk indicator of a user associated with the device, and the like, as disclosed herein. The trust and/or risk indicator may be reflective of the device being a Greenfield device or Brownfield device. In embodiments, the trust and/or risk indicator may be reflective of the device being a virtual device, a real-world device, and/or a meta-device, as disclosed herein. Determining the trust and/or risk indicator may be based at least in part on artificial intelligence, as disclosed herein.
In embodiments, a trust and/or risk indicator may be provided to a user as they interact (or attempt to interact) with a device. An interaction with a device may be authorized, prohibited, cautioned, and the like, based at least in part on the trust and/or risk indicator, such as, for instance, the interaction is an exchange of data with a device, establishing a network connection with the device, and the like. A trust and/or risk indicator of a device in the AR may be based at least in part on a combination of trust and/or risk indicators of a plurality of entities in the AR. A trust and/or risk indicator of the device may be provided to a user before the user enters an area of a metaverse and/or the real world containing the device. A trust and/or risk indicator of the device may be based at least in part on a combination of trust and/or risk indicators of a plurality of modules associated with the device. The trust and/or risk indicator may be updated based on an interaction with the device, as disclosed herein.
In certain aspects, the trust and/or risk indicator may be adjusted based on an event of the device, such as where the event is a transfer of ownership, a patching of the device, and the like. The event may be an updating at least one of software or firmware of the device. Methods and systems may include a parental control software agent.
Referring to
Referring to
Referring to
Referring to
A non-limiting use case may be scenario where a user wearing an AR headset enters a convenience store to purchase a bottle of water. The user may proceed to the checkout counter with the bottle such that a payment device, e.g., debit card reader, is visible within the field of view of the AR headset. If the payment device is registered with an IoT device registry, as disclosed herein, the AR headset may query the IoT device registry for a trust and/or risk identifier for the payment device and depict a visualization of the trust and/or risk identifier in relation to the payment device, e.g., on, above, below, etc., the payment device. For example, if the payment device is registered and has had no known instances of fraudulent transactions, the AR headset may show a green checkmark above the payment device. In the event the payment device is not registered with the IoT device registry or has been associated with one or more fraudulent transactions, the AR headset may depict a red ‘X’ above the payment device. In embodiments, visualization of the trust and/or risk score indicator in AR may be a colorization and/or shading of a real-world object, e.g., shading the payment device green if safe to use or red is potentially unsafe to use. Embodiments may also use such visualizations for stores that are within the metaverse, e.g., a virtual convenience store selling metaverse objects and/or services, such as in-game app purchases.
Embodiments may include an agent that monitors devices having IoT UIDs 6118 (
Such analysis may be performed by the registration server, and/or an agent/sentry executing on one or more of the computing devices disclosed herein, on data, e.g., device property data, retrieved from the plurality of records within the IoT device registry. Risk analysis may be based at least in part on the attributes of one or more devices, e.g., lifecycle events reflected by changes of a device's attributes, e.g., device property data, as recorded in its corresponding record 6110 (
Embodiments of the agent/sentry and/or corresponding apparatuses and/or method, disclosed herein, may form part of the monitor and secure component 2114 (
In embodiments, a SPG may depict one or more metrics related to a campaign, e.g., a patching campaign, such as devices patches vs devices yet to be patched. In embodiments, an entity having a high number and/or percentage, e.g., greater-than 80%, of patched devices may have a higher trust/lower risk score/indicator as compared to an entity which has a low number and/or percentage, e.g., less-than 20%, of patched devices. The SPG may also depict the locations and/or scheduled patch time(s) for one or more devices included within a campaign. In embodiments, the SPG may be structured to manage a campaign on behalf of a manufacturer 1134, end user 1136, and/or a third-party service provider 1138. In embodiments, the SPG may provide a link to a patch, and/or written instructions for the patch, for a corresponding campaign. Thus, as will be appreciated, embodiments of the current disclosure may provide for a succinct graphical user interface (GUI) from which an entity can manage a campaign for a plurality of devices having IoT UIDs 6118 registered with an IoT device registry 1129, as compared to traditional systems. Further, registration of devices with an IoT device registry 1129, as disclosed herein, provides for a manufacturer 1134 of the devices, and/or third-party monitoring service 1138 charged with managing the devices, to manage patching and/or campaigns involving the devices even though the devices may be owned by different end users 1136 and/or change ownership, which could occur during a campaign.
Referring to
In embodiments, the message may be displayed, e.g., on a SPG, and/or on a device corresponding to the IoT UID in the record 1131. Changes in the device property data may be logged in a database and/or another system for tracking a device's history, e.g., a block chain, as disclosed herein. In embodiments, the message may be received at a device management platform, which in turn, may trigger quarantining and/or patching the device, such as where the message is an alert. A trust indicator, as disclosed herein, may be adjusted based at least in part on the change, such as where the trust indicator is a trust score, a rating, a level value, and the like. The adjusting may increase when the change corresponds to a patching and/or an updating of software and/or firmware of the device. The adjusting may decrease when the change corresponds to a vulnerability, and the like. For example, where ownership of the device has passed to an entity associated with one or more IoT UIDs of devices registered in an IoT device registry 1129 having low trust and/or high-risk scores. The change may correspond to an addition of a new module into the device. For example, installing an additional network card into a device may increase a risk score of the device as the additional network card increases the number of access points of the device. Conversely, removing a network card from a device may lower the risk score of the device as doing so removes an access point of the device. The new module may be an input/output device, where the input/output device is a network interface device, a media device, and the like. The change may correspond to a change in ownership of the device, a location of the device, and the like. The security vulnerability may be based on a software and/or firmware of the device, on a hardware version of the device, and the like. A security vulnerabilities database may be accessed to pull security vulnerability signatures to determine if a registered device is affected.
In embodiments, the agent may raise an alert when the age of a module and/or device, as determined by analyzing the records 1131 in the IoT UID registry 1129, increases, e.g., an embedded computer on a vehicle having an operating system that has gone more than two (2) years without an update may pose a security risk.
Referring to
Referring to
Referring to
Referring to
Referring to
Referring again to
In embodiments, the IoT device registrar may source network and ecosystem information sources and/or correlate relevant data to visually show, e.g., in a SPG, affected devices that may be unreachable due to weather, Mobile Network Operator outage, utility outage (power, water, gas, etc.) or other communications outage in a localized area affecting multiple devices or customers (of the affected devices and/or services relating to the affected devices). In embodiments, an agent/sentry residing within the IoT device registry monitors relevant data feeds to create automated alerts, visual displays, and notifications among other actions.
Accordingly, illustrated in
As shown in
In embodiments, the apparatus 115100 may further include a visualization circuit 116112 structured to generate and/or transmit outage visualization data 116124 structured/configured to depict a visualization of the outage and/or outage pattern 115118 on an electronic display, such as on a SPG, e.g., 28102, 28104, and/or 28106 (
Illustrated in
As shown in
Referring to
As a non-limiting example, a plurality of devices 1112, 1114, 1116, 1118 registered with the registry 1129 (1) may be in the possession of users all within a same region, e.g., Massachusetts. A subset of the users and their corresponding devices 1114 and 1118 may be located in Boston, Mass. with other users/devices 1112 and 1116 respectively located in Springfield, Mass. and Worcester, Mass. A device management platform operated by a third-party monitoring service, e.g., 1138 (
Embodiments of the current disclosure may also provide for the detection of manufacturing defects affecting devices made by a manufacturer, e.g., 1134 (
Embodiments of the current disclosure may also provide for the detection of cyber-attacks affecting particular types of devices. For example, embodiments of an agent executing on the apparatus 115100 (
In a non-limiting example, an agent executing on the apparatus 115100 (
In a non-limiting example, one or more devices experiencing an outage of a first network connection may generate and transmit event messages (indicating a network outage with the first network connection) over a second network connection. Such event messages may be transmitted to a device management platform and/or to an IoT device registrar, as disclosed herein.
Referring again to
In embodiments, machine learning and/or other pattern recognition techniques may be used to generate and/or correlate information on device relationships that are behaving ‘normally’ to establish a baseline. Such embodiments may also provide for ‘alerts’ when abnormal behavior patterns are detected, e.g., behavior patterns outside the established baseline. In embodiments, the baseline may be generated by an agent/sentry in the registry 1129 (
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. In the apparatus 120100, the security analysis circuit may include an artificial intelligence (AI) circuit 120116 structured to detect the fraud event, based at least in part on analyzing the device property data using an artificial intelligence process. In the apparatus 120100, the artificial intelligence process may include a neural network. In the apparatus 120100, the neural network may be trained on detecting correlations between the fraud event and at least one of: a cyber-attack, a software version, a firmware version, a hardware version, an unauthorized access, a device failure event, device ownership, a device manufacturer, a location, or a network outage, unauthorized device access, use of property data corresponding to a retired/decommissioned device, etc. In the apparatus 120100, the artificial intelligence process may be based at least in part on a deep learning network. The apparatus 120100 may further include a visualization circuit 120118 structured to generate and transmit fraud event visualization data 120120 configured to depict a visualization of the fraud event on an electronic display. In the apparatus 120100, the visualization may be a map. In the apparatus 120100, the visualization may be a chart depicting at least one of the devices affected by the fraud event. In the apparatus 120100, the alert provisioning circuit may be further structured to transmit the message to at least one of: a device management platform corresponding to the device, a user of the device, a manufacturer of the device, or an entity that monitors the device. In the apparatus 120100, the security analysis circuit may form part of a device management platform. In the apparatus 120100, the security analysis circuit may form part of the IoT device registry, e.g., registry 1129 (
The apparatus 120100 may further include a trust indicator provisioning circuit 120130 structured to provide a trust indicator 120132 for the device, based at least in part on the determined fraud event. In the apparatus 120100, the trust indicator may include any of a numeric value, an alphabetic value, and/or an alphanumeric value. In the apparatus 120100, the trust indicator may include an enumerated value. In the apparatus 120100, the trust indicator may be displayed as a color-coded value. In the apparatus 120100, a value of the trust indicator may be based at least in part on a location of the device. In the apparatus 120100, a value of the trust indicator may be based at least in part on a time period. In the apparatus 120100, a value of the trust indicator may be based at least in part on one or more of a software version or a firmware version of the device. In the apparatus 120100, determining the trust indicator may be based at least in part on artificial intelligence. In the apparatus 120100, the trust indicator may be reflective of the device being a Greenfield device, as disclosed herein. In the apparatus 120100, the trust indicator may be reflective of the device being a Brownfield device, as disclosed herein. In the apparatus 120100, the trust indicator may be reflective of the device being a virtual device, as disclosed herein. In the apparatus 120100, the trust indicator may be reflective of the device being a meta-device, as disclosed herein.
For example, devices may be virtual devices, e.g., objects in a metaverse having real-world counterparts (real-world devices), where the virtual device is a digital-twin of the real-world counterpart. A digital virtual device may have properties corresponding to its real-world counterpart that may be updated in real-time and/or on a periodic basis. Devices in the metaverse may be real-world devices, e.g., objects in the real-world having metaverse counterparts (digital twin virtual devices) and/or supporting metaverse activities. As another example, devices may be meta-devices, e.g., objects in the metaverse lacking real-world counterparts. In embodiments, a device may have modules that are virtual devices and modules that are meta-devices. In embodiments, an IoT device registry may provide for registration of virtual devices, real-world devices, and/or meta-devices, as disclosed herein, and/or the services and/or functions associated with registration for registered virtual devices, real-world devices, and/or meta-devices, as also disclosed herein. Any of virtual devices, real-world devices, and/or meta-devices may be Greenfield devices and/or Brownfield devices, and/or may have a combination of Greenfield modules and/or Brownfield modules.
In the apparatus 120100, the trust indicator may be displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. In the apparatus 120100, the trust indicator provisioning circuit may be further structured to adjust a value of the trust indicator based at least in part on the determined fraud event. In the apparatus 120100, the adjustment may be an increase when the determined fraud event corresponds to at least one of a patching or an updating of at least one of software or firmware of the device. In the apparatus 120100, the adjustment may be a decrease when the determined fraud event corresponds to a cyber-attack.
In the apparatus 120100, the determined fraud event may correspond to an addition of a new module into the device. As a non-limiting example, the new module added to the device may be new software/firmware/hardware and/or a change in the existing software/firmware/hardware and/or a change in the external environment that results in the current software/firmware/hardware being exploitable. For example, a new vulnerability may become known. In the apparatus 120100, the new module may be at least one of an input device or an output device. In the apparatus 120100, the at least one of the input device or the output device may be a network interface device. In the apparatus 120100, the at least one of the input device or the output device may be a media device. In the apparatus 120100, the determined fraud event may correspond to a change in ownership of the device. In the apparatus 120100, the determined fraud event may be based on detecting a change in a location of the device. In the apparatus 120100, the determined fraud event may be based on detecting a change in at least one of a software version or a firmware version of the device. In the apparatus 120100, the determined fraud event may be based on detecting a change in a hardware version of the device. The apparatus may further include an IoT Universal Identification (UID) processing circuit 120134 structured to interpret an IoT UID and the device property data, a record management circuit 120136 structured to associate the IoT UID with the device property data via a record, and a record provisioning circuit 120138 structured to transmit the record.
The method 121100 may include interpreting, via a device property data processing circuit, device property data corresponding to a device, e.g., any of devices 1112, 1114, 1116, 1118, 1120, 1122, 1124 (
With reference to
In the method 121100, the trust indicator may be displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, letter based, or any combination thereof. The method 121100 may further include adjusting a value of the trust indicator based at least in part on the determined fraud event 123112. In the method 121100, the adjusting may be an increase when the determined fraud event corresponds to at least one of a patching or an updating of at least one of software or firmware of the device. In the method 121100, the adjusting may be a decrease when the determined fraud event corresponds to a cyber-attack.
In the method 121100, the determined fraud event may correspond to an addition of a new module into the device. In the method 121100, the new module may be at least one of an input device or an output device. In the method 121100, the at least one of the input device or the output device may be a network interface device. In the method 121100, the at least one of the input device or the output device may be a media device. In the method 121100, the determined fraud event may correspond to a change in ownership of the device. In the method 121100, the determined fraud event may be based on detecting a change in a location of the device. In the method 121100, the determined fraud event may be based on detecting a change in at least one of a software version or a firmware version of the device. In the method 121100, the determined fraud event may be based on detecting a change in a hardware version of the device. The method 121100 may further include accessing, by the security analysis circuit, a fraud event database to interpret fraud event signatures to determine that the device is subject to the fraud event 123114. A fraud event signature may include a set of events and/or data values known to be associated with past fraud events, and/or a set of events and/or data values similar to events and/or data values known to be associated with past fraud events, e.g., recent use of a long-ago retired SIM card and/or MAC address. The method 121100 may further include interpreting, via an IoT UID processing circuit, an IoT UID and the device property data 123122, associating, via a record management circuit, the IoT UID with the device property data via a record 123124, and transmitting, via a record provisioning circuit, the record 123126.
With reference to
Certain further aspects of the example apparatus are described herein, any one or more of which may be present in certain embodiments. In the apparatus 124100, the fraud detection circuit 124106 may include an artificial intelligence circuit 124120 structured to detect the 124116, 124122, based at least in part on analyzing the device property data 124112 using an artificial intelligence process. In the apparatus 124100, the artificial intelligence process may include a neural network. In the apparatus 124100, the neural network may be trained on detecting correlations between the fraud event 124116, 124122 and at least one of: a cyber-attack, a software version, a firmware version, a hardware version, an unauthorized access, a device failure event, device ownership, a device manufacturer, a location, or a network outage.
With reference to
Certain further aspects of the example system are described as following, any one or more of which may be present in certain embodiments. In the system 127100, the fraud detection device 127104 may include an artificial intelligence circuit 127114 structured to detect the fraud event 127110, based at least in part on analyzing the device property data 127106 using an artificial intelligence process. In the system 127100, the artificial intelligence process may include a neural network. In the system 127100, the neural network may be trained on detecting correlations between the fraud event 127110 and at least one of: a cyber-attack, a software version, a firmware version, a hardware version, an unauthorized access, a device failure event, device ownership, a device manufacturer, a location, or a network outage.
The method 128100 may include monitoring, via at least one processor, one or more records in an IoT device registry for changes in device property data corresponding to one or more devices, e.g., any of devices 1112, 1114, 1116, 1118, 1120, 1122, 1124 (
In certain embodiments, the determination or detection of fraudulent activity may include identification of a trust level, score, and/or rating, which may be dynamic. Correlation of device properties across the various spectrums may provide for a unique ability to detect unusual relationships that may indicate fraud and/or warrant further investigation. Embodiments may send messages to various parties, e.g., manufacturers, such as an original equipment manufacturer (OEM), that include restricted views of device property data, which may enable the various parties to detect unusual behavior and/or fraud. Embodiments may provide for the detection of device properties, e.g., location, usage profile, network, interface language, device settings, associated telephone number, which may be indicative of a change in ownership.
Embodiments of the current disclosure may also provide for alert management, for example, the setting and triggering of alerts based on conditional logic, e.g., risk management 5128, compliance management 5130, and/or security 5132 (
Referring to
Accordingly, as shown in
Referring to
Referring to
As such, referring to
Referring to
Referring to
Referring to
With reference to
Referring to
Illustrated in
As shown in
Accordingly, in embodiments, devices may be registered by the manufacturers 139132 with the registry 1129 prior to shipping of the units of vaccine. Once the devices are registered, the registry 1129 may catalogue/record the identification values and make the devices visible to entities within the supply chain, e.g., approved entities may check the status of the devices via one or more interfaces as described herein. A shipping company, prior to taking custody and/or accepting liability of the units of vaccine, may query the registry 1129 to verify that the one or more devices tracking the units of vaccine are registered and/or were registered by the manufacturers 139132. The shipping company may also verify one or more attributes of the devices, e.g., GPS location, temperature, pressure, etc. Upon verifying the devices as being properly registered and owned/assigned to the manufacturer, the shipping company, e.g., airplane 139114, may then accept custody and/or liability of the received units. The manufacturers 139132 and/or the shipping company 139114 may then update the corresponding records 1131 (
In embodiments, the registry 1129 may detect a discrepancy indicative of an unusual event within the supply chain, e.g., via a sentry, as described herein. For example, the number of units of vaccine known to be released from the distribution center 139116 may be different than the number of units of vaccine received by the hospital 139120. The registry 1129 may send an alert message to one or more of the manufacturer 139132, distribution center 139116, and/or shipping companies, e.g., airplane 139114 and/or truck 139118, used to transport the units of vaccine from the manufacturer 139132 to the hospital 139120. Such an unusual event may be the result of a truck 139126 getting lost and/or not completing delivery of the vaccine to the hospital 139120. In certain aspects, the registry 1129 may detect unusual events based on discrepancies within a device's lifecycle and/or attributes.
While the foregoing examples concerned embodiments of the registry 1129 in the context of a vaccine supply chain, it is to be understood that embodiments of the registry 1129 may be used in other types of supply chains, e.g., food, gas, consumer goods, etc., and/or any other type of manufacturing process or environment where devices are utilized. For example, embodiments of the current disclosure may involve a smart thermostat installed in a living room. As will be understood, the smart thermostat may have a serial number (physical ID), a WiFi MAC address (network ID) used to connect to a WiFi network, and/or a human understandable ID such as “Living Room Stat” (meta-ID or service ID, as disclosed herein). In certain aspects, embodiments of the current disclosure provide for an enterprise and/or service provider to manage the identities and/or life cycles of thousands of such devices.
Embodiments of the current disclosure may integrate with a telecommunications number registry, such a Toll-Free Management Platform (TFMP).
Embodiments of the registry 1129, as disclosed herein, may provide for a comprehensive IoT machine identity lifecycle management, e.g., “cradle to grave”, using identities sourced from trusted partners/manufacturers of devices, as disclosed herein.
Embodiments of the registry 1129 and/or the SPGs, as disclosed herein, may improve the problems associated with security fragmentation caused by multiple device IDs, data management, and governance. For example, some embodiments of the current disclosure may provide for a centralized and scalable machine identity, e.g., IoT UID 6118, registry coupled with a SPG-based management, that may be agnostic to use case, platform, network and industry vertical.
The seed of trust, provided by embodiments of the current disclosure, may provide for more granular identity and context information, which may enable incremental services and facilitate device troubleshooting and management.
As disclosed herein, some embodiments of the current disclosure may enable a computer system and/or mobile device manager to quickly identify devices that may be compromised, at risk of being compromised, and/or associated with fraud for purposes of quarantining such devices.
Embodiments of the current disclosure may provide for a chipset/module manufacturer and/or manufacturers further down a device assembly process to: trace components across one or more owners which may provide for premium positioning, improve product support, and/or confirm device activation. Embodiments of the current disclosure may provide for a chipset/module manufacturer to: receive traceable notifications, receive update confirmations, recycle IoT UIDs and/or other types of device identifiers, and/or the like. As will be appreciated, an IoT device registrar, as disclosed herein, may collect device events from multiple sources and/or environments and present them in a manageable and easily understandable interface, e.g., a SPG. Embodiments of the IoT device registrar, as disclosed herein, may provide for easy retrieval of a devices current owner, location, jurisdiction, and the like. Embodiments of the IoT device registrar, as disclosed herein, may provide for user and/or manufacturers of devices to retire devices and be relatively confident that such devices will not be used to produce rouge devices capable of infiltrating a system. Accordingly, some embodiments of the current disclosure may mitigate the risk of a registered device being counterfeited. Embodiments of the current disclosure may provide for secure provisioning of devices into a corporate enterprise environment and subsequent managing of their identities. Embodiments of the IoT device registry, as disclosed herein, may provide for trusted identification between devices, via the IoT UIDs, which, in turn, may mitigate and/or prevent malware downloads.
Embodiments of the current disclosure may also provide for a neutral steward, e.g., the registry 1129, for managing and verifying devices. In certain aspects, the registry 1129 may provide for attestation of a registered device, thereby providing for trusted interactions between entities and registered devices. In certain aspects, a first device may verify and/or authenticate itself to a second device based at least in part on the registry 1129, e.g., some embodiments of the current disclosure provide for one-way authentication. In certain aspects, two devices may verify/authenticate themselves to each other via the registry 1129, e.g., two-way authentication. In certain aspects, the registry may provide for distributed authentication of devices. In certain aspects, the registry 1129 may serve as a centralized authentication authority and/or trusted third party that manages authentication certificates. In embodiments, the registry 1129 may implement and/or facilitate implementation of one or more protocols based, as least in part, on the National Institute of Standards and Technology (NIST) Interagency or Internal Reports (NISTR) “NISTIR 8259”. For example, the registry 1129 may enable the device to signal to networks (that the device wishes to join) information such as the type of device, what type of access is being requested, required network functionality, provisioned credentials, etc. In certain aspects, the registry 1129 may implement one or more protocols based at least in part on the DNS-based Authentication of Named Entities (DANE) standard. Non-limiting examples include defining bindings between a domain name providing a particular service and a key that can be used to establish encrypted connections to that service. In certain aspects, the registry 1129 may implement one or more protocols based at least in part on the Manufacturer Usage Description (MUD) standard, e.g., methods for a device to signal to a network its type, approved access, required functionality, etc. In certain embodiments, the registry 1129 may implement one or more protocols based at least in part on the Type Allocation Code (TAC) standard. In embodiments, the registry 1129 may integrate and/or support a Network of Things based infrastructure.
Embodiments of the current disclosure may provide for a method for managing network connected devices. The method incudes interpreting, at a server, a device registration value that includes a device identification value and an owner identification value. The device identification value corresponds to at least one of the network connected devices. The owner identification value corresponds to an owner of the at least one network connected device. The method further includes storing, in a database via the server, the device identification value in a record corresponding to the owner identification value. The method further includes interpreting, at the server, a device status value that includes the device identification value and a device attribute value. The device attribute value corresponds to an attribute of the at least one network connected device. The method further includes identifying, via the server, the record storing the device identification value. The method further includes modifying, via the server, a field of the record based at least in part on the device attribute value. In certain aspects, the attribute value corresponds to a status of the at least one network connected device. In certain aspects, the status is at least one of: provisioned; active; malfunctioning; suspended; decommissioned; missing; compromised; or unknown. In certain aspects, the attribute value corresponds to at least one of: a location; a temperature; a pressure; a force; or a seal. In certain aspects, the attribute value corresponds to the location and the location corresponds to a product supply chain. In certain aspects, the method further includes verifying, via the server, that at least one of the device registration value or the device status value was generated by an authorized entity. In certain aspects, the authorized entity is the owner of the at least one network connected device. In certain aspects, the authorized entity is a manufacturer of the at least one network connected device. In certain aspects, the method further includes establishing a seed of trust between the server and an entity that generated at least one of the device registration value or the device status value. In certain aspects, establishing the seed of trust occurs prior to interpreting the device registration value. In certain aspects, the device registration value corresponds to a change in ownership of the at least one network connected device. In certain aspects, the method further includes: detecting, via the server and based at least in part on at least one of the device registration value or the device status value, an unusual event corresponding to the at least one network connected device; and transmitting an alert message corresponding to the unusual event.
Embodiments of the current disclosure may provide for a system for managing network connected devices. The system includes a server having at least one processor; and a memory device. The memory device is structured to store a plurality of records, each record of the plurality corresponding to an owner of at least one of the network connected devices. The at least one processor is structured to: interpret a device registration value that includes a device identification value and an owner identification value, the device identification value corresponding to at least one of the network connected devices and the owner identification value corresponding to an owner of the at least one network connected device. The at least one processor is structured to store, in the memory device, the device identification value in a record of the plurality of records, the record corresponding to the owner identification value. The at least one processor is structured to interpret a device status value that includes the device identification value and a device attribute value, the device attribute value corresponding to an attribute of the at least one network connected device. The at least one processor is structured to identify, based at least in part on the device identification value, the record. The at least one processor is structured to modify a field of the record based at least in part on the device attribute value.
Embodiments of the current disclosure may provide for an apparatus for managing network connected devices. The apparatus includes a device registration circuit structured to: interpret a device registration value that includes a device identification value and an owner identification value, the device identification value corresponding to at least one of the network connected devices and the owner identification value corresponding to an owner of the at least one network connected device; and store, in a database, the device identification value in a record corresponding to the owner identification value. The apparatus further includes a device status modification circuit structured to: interpret a device status value that includes the device identification value and a device attribute value, the device attribute value corresponding to an attribute of the at least one network connected device; identify, based at least in part on the device identification value, the record storing the device identification value; and modify a field of the record based at least in part on the device attribute.
Embodiments of the current disclosure may provide for a non-transitory computer readable medium storing instructions. The stored instructions adapt at least one processor to interpret a device registration value that includes a device identification value and an owner identification value, the device identification value corresponding to at least one of a plurality of network connected devices and the owner identification value corresponding to an owner of the at least one network connected device. The stored instructions further adapt the at least one processor to store, in a database, the device identification value in a record corresponding to the owner identification value. The stored instructions further adapt the at least one processor to interpret a device status value that includes the device identification value and a device attribute value. The device attribute value corresponds to an attribute of the at least one network connected device. The stored instructions further adapt the at least one processor to identify the record storing the device identification value; and modify a field of the record based at least in part on the device attribute value.
An example method includes interpreting, via an IoT UID processing circuit, an IoT UID and device property data; associating, via a record management circuit, the IoT UID with the device property data via a record; and transmitting, via a record provisioning circuit, the record.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including storing the record in a database. The device property data includes an owner identifier value. The device property data includes a manufacturer identifier value. The device property data includes at least one of: a trusted platform module key; a media access control address; a software version identifier; or a firmware identifier. The wherein associating the IoT UID with the device property data via a record comprises: including at least one of the IoT UID and the device property data in the record. The method further including identifying the record in a database, based at least in part on the IoT UID. The method further including: polling, via an update management circuit, an external data source to identify changes to a device corresponding to the device property data; and updating, via the record management circuit, the record to reflect the changes. The device property data indicates that a corresponding device is a Greenfield device; and associating, the IoT UID with the device property data via the record comprises including an identifier in the record that indicates the device is a Greenfield device. The device property data indicates that a corresponding device is a Brownfield device; and associating, the IoT UID with the device property data via the record comprises including an identifier in the record that indicates the device is a Brownfield device. The record includes a trust indicator for a device associated with the IoT UID. The trust indicator is a numeric value. The trust indicator is an enumerated type. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes an IoT UID processing circuit structured to interpret an IoT UID and device property data; a record management circuit structured to associate the IoT UID with the device property data via a record; and a record provisioning circuit structured to transmit the record.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data includes an owner identifier value. The device property data includes a manufacturer identifier value. The device property data includes at least one of: a trusted platform module key; a media access control address; a software version identifier; or a firmware identifier. The record management circuit is further structured to include at least one of the IoT UID and the device data in the record. The record management circuit is further structured to identify the record in a database, based at least in part on the IoT UID. The apparatus further including an update management circuit structured to: poll an external data source to identify changes to a device corresponding to the device property data; and update the record to reflect the changes. The device property data indicates that a corresponding device is a Greenfield device; and the record management circuit is further structured to include an identifier in the record that indicates the IoT device is a Greenfield device. The device property data indicates that a corresponding device is a Brownfield device; and the record management circuit is further structured to include an identifier in the record that indicates the IoT device is a Brownfield device. The record includes a trust indicator for a device associated with the IoT UID. The trust indicator is a numeric value. The trust indicator is an enumerated type.
An example method includes interpreting, via an IoT UID processing circuit, an IoT UID; generating, via a device lookup circuit, a query that includes the IoT UID and is structured to retrieve device property data corresponding to the IoT UID; and transmitting, via a query provisioning circuit, the query to an IoT device registrar server.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including interpreting, via a device property data processing circuit, the device property data retrieved by the query. The device property data includes an owner identifier value. The device property data includes a manufacturer identifier value. The device property data includes at least one of a trusted platform module key; a media access control address; a software version identifier; or a firmware identifier. The device property data includes a trust indicator for a device associated with the IoT UID. The method further including displaying, an electronic device, the trust indicator. The trust indicator is a numeric value. The trust indicator is an enumerated type. The method further including denying the device associated with the IoT UID access to another device, based at least in part on the trust indicator. The method further including granting the device associated with the IoT UID access to another device, based at least in part on the trust indicator.
An example apparatus includes an IoT UID processing circuit structured to interpret an IoT UID; a device lookup circuit structured to: generate a query that includes the IoT UID; and retrieve device property data corresponding to the IoT UID; and a query provisioning circuit structured to transmit the query to an IoT device registrar server.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including a device property data processing circuit structured to interpret the device property data retrieved by the query. The device property data includes an owner identifier value. The device property data includes a manufacturer identifier value. The device property data includes at least one of a trusted platform module key; a media access control address; a software version identifier; or a firmware identifier. The device property data includes a trust indicator for a device associated with the IoT UID. The trust indicator is a numeric value. The trust indicator is an enumerated type. The apparatus further including a gatekeeping circuit structured to deny the device associated with the IoT UID access to another device, based at least in part on the trust indicator. The apparatus further including a gate keeping circuit structured to grant the device associated with the IoT UID access to another device, based at least in part on the trust indicator.
An example method includes interpreting, via a user input processing circuit, one or more user input command values; determining, via an Internet of Things Universal Identification (IoT UID) identification circuit, one or more IoT UIDs, based at least in part on the one or more user input command values; generating, via a device lookup circuit, a query that includes the one or more IoT UIDs; retrieving, via the device lookup circuit, device property data corresponding to the one or more IoT UIDs; transmitting, via a query provisioning circuit, the query to an IoT device registrar server; interpreting, via a device property processing circuit, the device property data generated by the IoT UID registrar server in response to the query; and displaying, via a display circuit, the device property data with the corresponding one or more IoT UIDs.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The one or more user input command values include the one or more IoT UIDs. The one or more user input command values include credentials. The determining the one or more IoT UIDs is based at least in part on the credentials. The method further including filtering data in the device property data, based at least in part on the one or more user input command values. The filtered data relates to historical ownership of a device corresponding to one of the IoT UIDs. The device property data includes a patch status for a device of the corresponding IoT UID. The device property data includes a security risk analysis value for a device of the corresponding IoT UID. The method further including generating a security alert, based at least in part on the security risk analysis value. The device property data includes a trust level value for a device of the corresponding IoT UID. The method further including generating a security alert, based at least in part on the trust level value. The method further including generating and tracking a patching campaign for devices corresponding to one or more IoT UIDs. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes a user input processing circuit structured to interpret one or more user input command values; an Internet of Things Universal Identification (IoT UID) identification circuit structured to determine one or more IoT UIDs, based at least in part on the one or more user input command values; a device lookup circuit structured to: generate a query that includes the one or more IoT UIDs; and retrieve device property data corresponding to the one or more IoT UIDs; a query provisioning circuit structured to transmit the query to an IoT device registrar server; a device property processing circuit structured to interpret the device property data generated by the IoT device registrar server in response to the query; and a display circuit structured to display the device property data with the corresponding one or more IoT UIDs.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The user input command values include the one or more IoT UIDs. The user input command values include credentials. The IoT UID identification circuit is further structured to determine the one or more IoT UIDs, based at least in part on the credentials. The apparatus further including a filtering circuit structured to filter data in the device property data, based at least in part on the one or more user input command values. The filtered data relates to historical ownership of a device corresponding to one of the IoT UIDs. The device property data includes a patch status for a device of the corresponding IoT UID. The device property data includes a security risk analysis value for a device of the corresponding IoT UID. The apparatus further including a security alert circuit structured to generate a security alert, based at least in part on the security risk analysis value. The device property data includes a trust level value for a device of the corresponding IoT UID. The apparatus further including a security alert circuit structured to generate a security alert, based at least in part on the trust level value. The apparatus further including a patching campaign circuit structured to generate and track a patching campaign for devices corresponding to one or more IoT UIDs.
An example system includes an Internet of Things (IoT) device registrar server structured to provide access to an IoT device registry; and a device management server structured to: communicate with the IoT device registrar server; and provide a graphical user interface structured to display device property data for one or more devices registered with the IoT device registry, wherein the device property data is retrieved by the graphical user interface from the IoT device registry via querying the IoT device registrar server.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. Each of the one or more devices has a corresponding IoT Universal Identification (UID) associated with the device. The system further including a filtering circuit, in communication with the device management server, structured to filter data in the device property data. The filtered data relates to historical ownership of a device having an IoT UID associated with the device. The device property data includes a patch status for a device having an IoT UID associated with the device. The device property data includes a security risk analysis value for a device of the corresponding IoT UID. The system further including, in communication with the device management server, a security alert circuit structured to generate a security alert, based at least in part on the security risk analysis value. The device property data includes a trust level value for a device of the corresponding IoT UID. The system further including a security alert circuit, in communication with the device management server, structured to generate a security alert, based at least in part on the trust level value. The system further including a patching campaign circuit, in communication with the device management server, structured to generate and track a patching campaign for devices corresponding to one or more IoT UIDs. The system further including a credential verification circuit, in communication with the device management server, structured to: determine whether a user of the graphical user interface is authorized to access the device property data for the one or more devices; and if it is determined that the user of the graphical user interface is not authorized to access the device property data for the one or more devices, restrict the display of the device property data for one or more devices.
An example apparatus includes at least one processor; and a memory device storing an application structured to adapt the at least one processor to generate a graphical user interface structured to: receive one or more user input command values; determine, based at least in part on the one or more user input command values, one or more devices registered with an IoT device registry via corresponding Internet of Things Universal Identifications (IoT UIDs); and display property data for the one or more devices.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The one or more user input command values include the one or more IoT UIDs. The one or more user input command values include credentials. The application stored in the memory device is further structured to adapt the at least one processor to determine the one or more IoT UIDs, based at least in part on the credentials. The application stored in the memory device is further structured to adapt the at least one processor to filter data in the device property data, based at least in part on the one or more user input command values. The filtered data relates to historical ownership of a device corresponding to one of the IoT UIDs. The device property data includes a patch status for a device of the corresponding IoT UID. The device property data includes a security risk analysis value for a device of the corresponding IoT UID. The application stored in the memory device is further structured to adapt the at least one processor to: generate a security alert, based at least in part on the security risk analysis value; and provide the security alert to the graphical user interface to be displayed by the graphical user interface. The device property data includes a trust level value for a device of the corresponding IoT UID. The application stored in the memory device is further structured to adapt the at least one processor to: generate a security alert, based at least in part on the trust level value; and provide the security alert to the graphical user interface to be displayed by the graphical user interface. The application stored in the memory device is further structured to adapt the at least one processor to: generate and track a patching campaign for devices corresponding to one or more IoT UIDs; and provide information about the patching campaign to the graphical user interface to be displayed by the graphical user interface.
An example method includes generating, via at least one processor, a graphical user interface structured to: receive one or more user input command values; and communicate with an Internet of Things (IoT) device registrar server; receiving, via the graphical user interface, the one or more user input command values; determining, via the at least one processor, one or more devices registered with an IoT device registry via querying the IoT device registrar server, based at least in part on the one or more user input command values; and displaying device property data for the one or more devices received in response to querying the IoT device registrar server.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Each of the one or more devices has a corresponding IoT Universal Identification (UID) associated with the device. The method further including filtering data in the device property data. The filtered data relates to historical ownership of a device having an IoT UID associated with the device. The device property data includes a patch status for a device having an IoT UID associated with the device. The device property data includes a security risk analysis value for a device of the corresponding IoT UID. The method further including: generating a security alert, based at least in part on the security risk analysis value; and displaying the security alert on a same display as the device property data. The device property data includes a trust level value for a device of the corresponding IoT UID. The method further including: generating a security alert, based at least in part on the trust level value; and displaying the security alert on a same display as the device property data. The method further including: generating and tracking a patching campaign for devices corresponding to one or more IoT UIDs; and displaying information about the patching campaign on a same display as the device property data. The method further including determining whether a user of the graphical user interface is authorized to access the device property data for the one or more devices; and if it is determined that the user of the graphical user interface is not authorized to access the device property data for the one or more devices, restricting the display of the device property data for one or more devices.
An example apparatus includes a single pane of glass (SPG) interface circuit structured to interpret an Internet of Things Universal Identification (IoT UID) received from an SPG; and a record management circuit structured to retrieve device property data corresponding to the IoT UID, wherein the SPG interface circuit is further structured to transmit the device property data to the SPG.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The IoT UID and device property data are associated with a device. The apparatus further including a filtering circuit, in communication with the record management circuit, structured to filter data in the device property data. The filtered data relates to historical ownership of the device. The device property data includes a patch status for the device. The device property data includes a security risk analysis value for the device. The apparatus further including, in communication with the record management circuit, a security alert circuit structured to: generate a security alert, based at least in part on the security risk analysis value; and provide the security alert to the SPG interface circuit to be displayed by the SPG. The device property data includes a trust level value for a device of the corresponding IoT UID. The apparatus further including a security alert circuit, in communication with the record management circuit, structured to: generate a security alert, based at least in part on the trust level value; and provide the security alert to the SPG interface circuit to be displayed by the SPG. The apparatus further including a patching campaign circuit, in communication with the record management circuit, structured to generate and track a patching campaign for devices corresponding to one or more IoT UIDs; and provide information about the patching campaign to the SPG interface circuit to be displayed by the SPG. The apparatus further including a credential verification circuit, in communication with the record management circuit, structured to: determine whether a user of the SPG is authorized to access the device property data corresponding to the IoT UID; and if it is determined that the user of the SPG is not authorized to access the device property data, restrict display of the device property data on the SPG.
An example method includes identifying one or more Brownfield devices; generating device property data, based at least in part on the one or more Brownfield devices; transmitting, to an Internet of Things (IoT) device registrar server, a registration request that includes the device property data; interpreting one or more Internet of Things Universal Identifications (IoT UIDs) generated in response to the transmitting of the registration request; and embedding the one or more IoT UIDs in the one or more Brownfield devices.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Embedding the one or more IoT UIDs in the one or more Brownfield devices comprises piggybacking the one or more IoT UIDs off one or more base messages transmitted to the one or more Brownfield devices. The one or more base messages are part of at least one of a software update or a firmware update for the one or more Brownfield devices. The one or more base messages are transmitted to the one or more Brownfield devices at one or more scheduled times. The one or more base messages are transmitted in response to the one or more Brownfield devices polling a management device platform. Embedding the one or more IoT UIDs in the one or more Brownfield devices comprises: for each of the one or more Brownfield devices, storing a corresponding one of the IoT UIDs in a memory device of the Brownfield device. Embedding the one or more IoT UIDs in the one or more Brownfield devices comprises: for each of the one or more Brownfield devices, installing a component into the Brownfield device, wherein the component includes the IoT UID. The method further including associating each of one or more portions of the device property data with a distinct IoT UID of the one or more IoT UIDs in an IoT UID device registry, wherein each of the one or more portions of the device property data corresponds to a distinct one of the one or more Brownfield devices. At least one of the following is performed, in part, using a single pane of glass (SPG): identifying the one or more Brownfield devices; generating the device property data; transmitting the registration request; or interpreting the one or more IoT UIDs generated in response to the transmitting of the registration request. The SPG is an application programing interface. The SPG is a graphical user interface. The SPG is hosted by and/or integrated into a device management platform. The SPG is hosted by an IoT device registrar. The method further including transmitting a confirmation message that indicates the one or more IoT UIDs were embedded in the one or more Brownfield devices. The device property data includes one or more owner identifier values, each of the one or more owner identifier values corresponding to an owner of the one or more Brownfield devices. The device property data includes one or more manufacturer identifier values, each of the one or more manufacturer identifier values corresponding to a manufacturer of the one or more Brownfield devices. The device property data includes at least one of a trusted platform module (TPM) key; a media access control (MAC) address; or a manufacturing serial number. The method further including transmitting a set of credentials to the IoT device registrar server, wherein the set of credentials provides authorization to register the one or more Brownfield devices with an IoT device registry associated with the IoT device registrar server. The set of credentials is based at least in part on a public key encryption infrastructure (PKI). The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes a display circuit structured to generate a graphical user interface (GUI) configured to receive one or more user input command values corresponding to device property data for one or more Brownfield devices; a requestor circuit structured to generate a registration request that includes the device property data; a request provisioning circuit structured to transmit the registration request to an Internet of Things (IoT) device registrar server; an Internet of Things Universal Identification (IoT UID) processing circuit structured to interpret one or more IoT UIDs generated by the IoT device registrar server in response to the registration request; and an IoT UID provisioning circuit structured to at least one of: transmit the one or more IoT UIDs; or display the one or more IoT UIDs on an electronic display.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including an embedding verification circuit structured to interpret embedding confirmation data indicating that the one or more IoT UIDs were embedded into the one or more Brownfield devices; and transmit one or more confirmation messages indicating that the one or more IoT UIDs were embedded into the one or more Brownfield devices. The transmission of the one or more confirmation messages is to the display circuit; and the display circuit is further structured to display the embedding confirmation data in the GUI. The device property data includes one or more owner identifier values, each of the one or more owner identifier values corresponding to an owner of the one or more Brownfield devices. The device property data includes one or more manufacturer identifier values, each of the one or more manufacturer identifier values corresponding to a manufacturer of the one or more Brownfield devices. The device property data includes at least one of a trusted platform module (TPM) key; a media access control (MAC) address; or a manufacturing serial number. The apparatus further including a credential circuit structured to interpret a set of credentials corresponding to a user of the GUI; and transmit the set of credentials to the IoT device registrar server, wherein the set of credentials provides authorization to register the one or more Brownfield devices with an IoT device registry associated with the IoT device registrar server. The IoT UID provisioning circuit is structured to transmit the one or more IoT UIDs via piggybacking the one or more IoT UIDs off of one or more base messages transmitted to the one or more Brownfield devices. The one or more base messages are part of at least one of a software update or a firmware update for the one or more Brownfield devices. The one or more base messages are transmitted to the one or more Brownfield devices at one or more scheduled times. The one or more base messages are transmitted in response to the one or more Brownfield devices polling a management device platform. At least one of the display circuit, the requestor circuit, the request provisioning circuit, the IoT UID processing circuit, or the IoT UID provisioning circuit form part of a device management platform.
An example method includes interpreting, via a device registration request circuit, a registration request that maps device property data to one or more Brownfield devices; generating, via an Internet of Things Universal Identification (IoT UID) generation circuit, based at least in part on the registration request, an IoT UID for each of the one or more Brownfield devices; and transmitting, via an IoT UID provisioning circuit, the IoT UID for each of the one or more Brownfield devices.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including interpreting one or more conformation messages indicating that the one or more IoT UIDs were embedded into the one or more Brownfield devices. The method further including associating, based at least in part on the mapping of device property data to the one or more Brownfield devices, each of one or more portions of the device property data with a distinct IoT UID of the one or more IoT UIDs in an IoT UID device registry. The method further including generating a trust level value for each of the one or more Brownfield devices; and transmitting the trust level values. Each of the trust level values for the one or more Brownfield devices has an initial value indicating that the corresponding Brownfield device is less trustworthy than a comparable Greenfield device.
An example method includes interpreting, via a request processing circuit, a registration request that includes device property data for one or more Brownfield devices; generating, via an Internet of Things Universal Identification (IoT UID) generation circuit, one or more IoT UIDs, based at least in part on the device property data; associating, via a record management circuit, each of the one or more IoT UIDs with at least some of the device property data via a record; transmitting, via an IoT UID provisioning circuit, the one or more IoT UIDs; and interpreting, via a registration confirmation circuit, one or more embedding confirmation messages generated in response to transmitting the IoT UIDs, wherein the one or more embedding confirmation messages indicate embedding of the one or more IoT UIDs into the one or more Brownfield devices.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device property data includes one or more owner identifier values, each of the one or more owner identifier values corresponding to an owner of the one or more Brownfield devices.
An example apparatus includes a request processing circuit structured to interpret a registration request that includes device property data for one or more Brownfield devices; an Internet of Things Universal Identification (IoT UID) generation circuit structured to generate one or more IoT UIDs, based at least in part on the device property data; a record management circuit structured to associate each of the one or more IoT UIDs with at least some of the device property data via a record; an IoT UID provisioning circuit structured to transmit the one or more IoT UIDs; and a registration confirmation circuit structured to interpret one or more embedding confirmation messages generated in response to transmitting the IoT UIDs; wherein the one or more embedding confirmation messages indicate embedding of the one or more IoT UIDs into the one or more Brownfield devices.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data includes one or more manufacturer identifier values, each of the one or more manufacturer identifier values corresponding to a manufacturer of the one or more Brownfield devices.
An example method includes manufacturing one or more Greenfield devices; generating device property data based at least in part on the one or more Greenfield devices; transmitting, to an Internet of Things (IoT) device registrar server, a registration request that includes the device property data; interpreting one or more Internet of Things Universal Identifiers (IoT UIDs) generated in response to the transmitting of the registration request; and embedding the one or more IoT UIDs in the one or more Greenfield devices.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. At least one of generating the device property data and transmitting the device property data forms part of a bootstrapping process. The bootstrapping process is initiated at least in part by the one or more Greenfield devices. The method further including verifying that the one or more Greenfield devices are authorized to transmit the device property data to the IoT device registrar. Verifying the one or more Greenfield devices is based at least in part on a cryptographic key. The cryptographic key is based at least in part on a public key infrastructure (PKI). At least one of generating the device property data or transmitting the device property data is performed via a device management platform. The device management platform comprises a single pane of glass (SPG). The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number. Embedding the one or more IoT UIDs into the one or more Greenfield devices comprises: storing the one or more IoT UIDs in one or more memory locations of the one or more Greenfield devices. Embedding the one or more IoT UIDs into the one or more Greenfield devices comprises installing one or more components into the one or more Greenfield device. The one or more components include the one or more IoT UIDs. Embedding the one or more IoT UIDs in the one or more Greenfield devices occurs prior to a sale of the one or more Greenfield devices. Embedding the one or more IoT UIDs in the one or more Greenfield devices occurs after a sale of the one or more Greenfield devices. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example method includes obtaining a Greenfield device; generating device property data corresponding to the Greenfield device; transmitting the device property data to an Internet of Things (IoT) device registrar server; interpreting an Internet of Things Universal Identifier (IoT UID) generated by the IoT device registrar server in response to the device property data; and embedding the IoT UID into the Greenfield device.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. At least one of generating the device property data and transmitting the device property data forms part of a bootstrapping process. The bootstrapping process is initiated at least in part by the Greenfield device. The method further including verifying that the Greenfield device is authorized to transmit the device property data to the IoT device registrar. Verifying the Greenfield device is based at least in part on a cryptographic key. The cryptographic key is based at least in part on a public key infrastructure (PKI). At least one of generating the device property data or transmitting the device property data is performed via a device management platform. The device management platform comprises a single pane of glass (SPG). The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number. Embedding the IoT UID into the Greenfield device comprises storing the IoT UID in a location of the Greenfield device. Embedding the IoT UID into the Greenfield device includes: installing a component into the Greenfield device. The component includes the IoT UID. Embedding the IoT UID in the Greenfield device occurs prior to a sale of the Greenfield device. Embedding the IoT UID in the Greenfield device occurs after a sale of the Greenfield device.
An example system includes one or more manufacturing components structured to manufacture at least a portion of a Greenfield device; a device management platform structured to generate device property data corresponding to the Greenfield device; transmit the device property data to an Internet of Things (IoT) device registrar server; and interpret an Internet of Things Universal Identifier (IoT UID) generated by the IoT device registrar server in response to the device property data; and an embedding tool structured to embed the IoT UID into the Greenfield device.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example apparatus includes device property data; a memory device; and a bootstrapping circuit structured to: initiate a request for an Internet of Things Universal Identifier (IoT UID) from an IoT device registrar server, the request including the device property data; transmit the request; interpret an IoT UID generated in response to the request; and store the IoT UID in the memory device.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number. The apparatus further including a credential circuit structured to transmit one or more credentials that demonstrate authorization to register the apparatus with an IoT device registrar. The one or more credentials are cryptographic keys. The cryptographic keys are public encryption key infrastructure (PKI) keys.
An example method includes powering-on a Greenfield device; and initiating a bootstrapping process on the Greenfield device structured to: register the Greenfield device with an Internet of Things (IoT) device registrar; and embed an Internet of Things Universal Identifier (IoT UID) issued by the IoT device registrar as part of registering the Greenfield device.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Registration of the Greenfield device with the IoT device registrar is based at least in part on device property data that includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number. Powering-on the Greenfield device occurs prior to a first sale of the Greenfield device. Powering-on of the Greenfield device is performed by a first owner of the Greenfield device.
An example method includes interpreting, via a device registration request circuit, a registration request that maps device property data to one or more Greenfield devices; generating, via an Internet of Things Universal Identifier (IoT UID) generation circuit, based at least in part on the registration request, an IoT UID for each of the one or more Greenfield devices; and transmitting, via an IoT UID provisioning circuit, the IoT UIDs for each of the one or more Greenfield devices.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example apparatus includes a device registration circuit structured to interpret a registration request that maps device property data to one or more Greenfield devices; an Internet of Things Universal Identifier (IoT UID) generation circuit structured to generate, based at least in part on the registration request, an IoT UID for each of the one or more Greenfield devices; and an IoT UID provisioning circuit structured to transmit the IoT UID for each of the one or more Greenfield devices.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example method includes identifying one or more Brownfield devices; generating device property data based at least in part on the one or more Brownfield devices; transmitting, to an Internet of Things (IoT) device registrar server, a registration request that includes the device property data; and interpreting one or more Internet of Things Universal Identifiers (IoT UIDs) generated in response to the transmitting of the registration request.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The registration request is for virtual IoT UIDs for the one or more Brownfield devices. The one or more IoT UIDs are virtual IoT UIDs. At least one of identifying the one or more Brownfield devices, generating the device property data, or transmitting the registration request are performed, in part, via a Single Pane of Glass (SPG). The SPG is a graphical user interface. The SPG is hosted by the IoT device registrar server. The SPG forms part of a device management platform. The SPG is an application programming interface (API). The SPG is hosted by the IoT device registrar server. The SPG forms part of a device management platform. The method further including verifying that an entity requesting registration of the one or more Brownfield devices is authorized to do so. Verifying is based at least in part on cryptographic keys. The cryptographic keys are based at least in part on a public key encryption infrastructure. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number. The method further including interpreting, via a device management platform, a message from the IoT device registrar server that provides confirmation that the one or more Brownfield devices were successfully registered with an IoT device registry corresponding to the IoT device registrar server. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes a display circuit structured to generate a graphical user interface configured to receive one or more user input command values corresponding to device property data for one or more Brownfield devices; a requestor circuit structured to generate a virtual registration request that includes the device property data; a request provisioning circuit structured to transmit the virtual registration request to an Internet of Things (IoT) device registrar server; an Internet of Things Universal Identifier (IoT UID) processing circuit structured to interpret one or more virtual IoT UIDs generated by the IoT device registrar server in response to the virtual registration request; and an IoT UID provisioning circuit structured to at least one of: transmit the one or more virtual IoT UIDs; or display the one or more virtual IoT UIDs on an electronic display.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including a verification circuit structured to verify that an entity requesting registration of the one or more Brownfield devices is authorized to do so. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example apparatus includes a device registration request circuit structured to interpret a virtual registration request that maps device property data to one or more Brownfield devices; an Internet of Things Universal Identifier (IoT UID) generation circuit structured to generate, based at least in part on the virtual registration request, an IoT UID for each of the one or more Brownfield devices; a record management circuit structured to generate a record for each of the IoT UIDs, wherein the record management circuit is further structured to associate each of the IoT UIDs with portions of the device property data corresponding to a distinct one of the one or more Brownfield devices; and an IoT UID provisioning circuit structured to transmit each of the IoT UIDs.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including a verification circuit structured to verify that an entity requesting registration of the one or more Brownfield devices is authorized to do so. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example method including interpreting, via a device registration request circuit, a virtual registration request that maps device property data to one or more Brownfield devices; generating, via an Internet of Things Universal Identifier (IoT UID) generation circuit, based at least in part on the virtual registration request, an IoT UID for each of the one or more Brownfield devices; generating, via a record management circuit, a record for each of the IoT UIDs; associating, via the record management circuit, each of the IoT UIDs with portions of the device property data corresponding to a distinct one of the one or more Brownfield devices; and transmitting, via an IoT UID provisioning circuit, each of the IoT UIDs.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including verifying that an entity requesting registration of the one or more Brownfield devices is authorized to do so. The device property data includes at least one of an owner identifier value; a manufacturer identifier value; a Trusted Platform Module (TPM) Key; a Media Access Control (MAC) address; or a manufacturing serial number.
An example method includes manufacturing at least a portion of a Greenfield device generating, via a device management platform, device property data corresponding to the Greenfield device; generating, via the device management platform, a virtual registration request that includes the device property data; transmitting, via the device management platform, the virtual registration request to an IoT device registrar server; and interpreting, via the device management platform, an IoT UID generated by the IoT device registrar server in response to the device property data.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The generating and transmitting the device property data is facilitated by a bootstrapping process initiated by the Greenfield device. The method further including verifying that an entity requesting registration of the Greenfield device is authorized to do so. The verifying authorization of the entity is based at least in part on cryptographic keys. The verifying authorization of the entity is based at least in part on a Public Key Infrastructure (PKI). The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example system including one or more manufacturing components structured to manufacture at least a portion of a Greenfield device; and a device management platform structured to: generate device property data corresponding to the Greenfield device; generate a virtual registration request that includes the device property data; transmit the virtual registration request to an IoT device registrar server; and interpret an IoT UID generated by the IoT device registrar server in response to the virtual registration request.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The device management platform comprises a Single Pane of Glass (SPG). The device property data includes an owner identifier value. The device property data includes a manufacturer identifier value. The device property data includes a Trusted Platform Module (TPM) Key. The device property data includes a Media Access Control (MAC) address. The device property data includes a serial number.
An example apparatus including device property data; and a bootstrapping circuit structured to: initiate a virtual registration request that includes the device property data; and transmit the virtual registration request to an IoT device registrar server.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data includes an owner identifier value. The device property data includes at least one of a manufacturer identifier value or a serial number. The device property data includes at least one of a Trusted Platform Module (TPM) Key or a Media Access Control (MAC) address.
An example method including powering-on a Greenfield device; and initiating a bootstrapping process on the Greenfield device structured to virtually register the Greenfield device with an IoT device registrar.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The registration is pre-sale. The registration is post-sale. The method further including releasing the Greenfield device for use by an end user. The method further including embedding an IoT UID in the Greenfield device, wherein embedding comprises storing the IoT UID in a memory location of the Greenfield device. The method further including embedding an IoT UID in the Greenfield device, wherein embedding comprises installing a component into the Greenfield device, and wherein the component includes the IoT UID.
An example method including interpreting, via a device registration request circuit, a virtual registration request that maps device property data to one or more Greenfield devices; generating, via an IoT UID generation circuit, based at least in part on the virtual registration request, an IoT UID for each of the one or more Greenfield devices; generating, via a record management circuit, a record for each of the IoT UIDs; associating, via the record management circuit, each of the IoT UIDs with portions of the device property data corresponding to a distinct one of the one or more Greenfield devices; and transmitting, via an IoT UID provisioning circuit, the IoT UIDs.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The IoT UIDs are transmitted to a device management platform operated by a manufacturer of the one or more Greenfield devices. The IoT UIDs are transmitted to a device management platform operated by an IoT device registrar. The IoT UIDs are transmitted to a device management platform operated by an end user.
An example apparatus includes a property-monitoring circuit structured to: generate a query for device property data for an Internet of Things (IoT) device to an IoT device registrar server; interpret the device property data received from the IoT device registrar server to determine whether there is a change in the device property data; if the property-monitoring circuit determines that there is a change in the device property data, generate a notification of the change; and transmit the notification of the change to the IoT device registrar server.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The query is initiated by at least one of: the device, a user of the device, a seller of the device, a purchaser of the device, a manufacturer of the device, or the IoT device registrar server. The change is determined by analyzing historical device property data. The change is determined by monitoring a device property change flag. The change comprises a change in device hardware. The change comprises a change in a network. The change comprises a change in ownership of the device. The change comprises a security event. The determining that the device has reached end-of-life comprises receiving a user input indicating that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a security notification indicating a device decommissioning. The determining that the device has reached end-of-life comprises receiving a decommission notification indicating a device decommissioning. The property-monitoring circuit is further structured to generate a quarantine value indicating that a device should be quarantined. The property-monitoring circuit is further structured to generate a decommission value indicating that a device should be decommissioned. The property-monitoring circuit is further structured to generate a security value indicating that a device may be subject to a security event. The property-monitoring circuit is further structured to generate an ownership notification indicating that an ownership value corresponding to the device has changed. The apparatus further including a display circuit structured to display the notification of the change. The display circuit comprises a Single Pane of Glass (SPG) display circuit included in an SPG system. The SPG system comprises a graphical user interface. The graphical user interface is hosted by an IoT device registrar that includes the IoT device registrar server. The SPG system is included in a device management platform. The SPG system comprises an Application Programing Interface (API). The API is hosted by the IoT device registrar. The API is included in a device management platform.
An example method including generating a query for device property data for an Internet of Things (IoT) device to an IoT device registrar server; interpreting the device property data received from the IoT device registrar server to determine whether there is a change in the device property data; if it is determined that there is a change in the device property data, generating a notification of the change; and transmitting the notification of the change to the IoT device registrar server.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The query is initiated by at least one of: the device, a user of the device, a seller of the device, a purchaser of the device, a manufacturer of the device, or the IoT device registrar server. The change is determined by analyzing historical device property data. The change is determined by monitoring a device property change flag. The change comprises a change in device hardware. The change comprises a change in a network. The change comprises a change in ownership of the device. The change comprises a security event. The determining that the device has reached end-of-life comprises receiving a user input indicating that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a security notification indicating a device decommissioning. The determining that the device has reached end-of-life comprises receiving a decommission notification indicating a device decommissioning. The method further including generating a quarantine value indicating that a device should be quarantined. The method further including generating a decommission value indicating that a device should be decommissioned. The method further including generating a security value indicating that a device may be subject to a security event. The method further including generating an ownership notification indicating that an ownership value corresponding to the device has changed. The method further including displaying the notification of the change via a display circuit. The notification of the change is displayed via a Single Pane of Glass (SPG) system. The SPG system comprises a graphical user interface. The graphical user interface is hosted by an IoT device registrar that includes the IoT device registrar server. The SPG system is included in a device management platform. The SPG system comprises an Application Programing Interface (API). The API is hosted by the IoT device registrar. The API is included in a device management platform.
An example method includes determining that a device has reached end-of-life; generating a query for Internet of Things Universal Identification (IoT UID) data corresponding to the device to an IoT device registrar server; interpreting IoT UID data received from the IoT device registrar server to identify a set of IoT UIDs corresponding to the device; identifying a first UID list including a first subset of the set of IoT UIDs to be reused; identifying a second UID list including a second subset of the set of IoT UIDs, different from the first subset, to be retired; and transmitting the first UID list and the second UID list to the IoT device registrar server.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Either of the first subset or the second subset of the set of IoT UIDs is an empty subset. The method further including storing the second UID list, including the second subset of the set of IoT UIDs to be retired in a global retired UID registry, in the IoT device registrar server. The determining that the device has reached end-of-life comprises receiving a user input indicating that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a security notification indicating a device decommissioning. The determining that the device has reached end-of-life comprises receiving a decommission notification indicating a device decommissioning.
An example apparatus includes a device retirement circuit structured to determine that a device has reached end-of-life; a query-generating circuit structured to generate a query for Internet of Things Universal Identification (IoT UID) data corresponding to the device to an IoT device registrar server; an IoT UID interpretation circuit structured to: interpret the IoT UID data received from the IoT device registrar server to identify a set of IoT UIDs corresponding to the device; identify a first UID list including a first subset of the set of IoT UIDs to be reused; and identify a second UID list including a second subset of the set of IoT UIDs, different from the first subset, to be retired; and a retirement reporting circuit structured to transmit the first UID list and the second UID list to the IoT device registrar server.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. Either of the first subset or the second subset of the set of IoT UIDs is an empty subset. The second UID list, including the second subset of the set of IoT UIDs to be retired in a global retired UID registry, is stored in the IoT device registrar server. The determining that the device has reached end-of-life comprises receiving a user input indicating that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a security notification indicating a device decommissioning. The determining that the device has reached end-of-life comprises receiving a decommission notification indicating a device decommissioning.
An example method includes interpreting, via a user input processing circuit, a user input identifying a device to be retired; generating a query for Internet of Things Universal Identification (IoT UID) data corresponding to the device to an IoT device registrar server; interpreting the IoT UID data received from the IoT device registrar server to identify a set of IoT UIDs corresponding to the device; identifying a first UID list including a first subset of the set of IoT UIDs to be reused; identifying a second UID list including a second subset of the set of IoT UIDs, different from the first subset, to be retired; transmitting the first UID list and the second UID list to the IoT device registrar server; interpreting, via the IoT device registrar server, the first UID list and the second UID list corresponding to the device; and displaying, via a display circuit, the first UID list and the second UID list corresponding to the device.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. Either of the first subset or the second subset of the set of IoT UIDs is an empty subset. The method further including storing the second UID list, including the second subset of the set of IoT UIDs to be retired in a global retired UID registry, in the IoT device registrar server.
An example apparatus includes a user input processing circuit structured to interpret a user input identifying a device to be retired; a query-generating circuit structured to generate a query for Internet of Things Universal Identification (IoT UID) data corresponding to the device to an IoT device registrar server; an IoT UID interpretation circuit structured to: interpret the IoT UID data received from the IoT device registrar server to identify a set of IoT UIDs corresponding to the device; identify a first UID list including a first subset of the set of IoT UIDs to be reused; and identify a second UID list including a second subset of the set of IoT UIDs, different from the first subset, to be retired; a device end-of-life interpretation circuit at the IoT device registrar server structured to interpret the first UID list and the second UID list corresponding to the device; and a display circuit structured to display the first UID list and the second UID list corresponding to the device.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. Either of the first subset or the second subset of the set of IoT UIDs is an empty subset. The second UID list, including the second subset of the set of IoT UIDs to be retired in a global retired UID registry, is stored in the IoT device registrar server.
An example method includes interpreting, via an input processing circuit, a device property data update request for an Internet of Things (IoT) device; determining, via an IoT UID identification circuit, one or more Internet of Things Universal Identifications (IoT UIDs) corresponding to the IoT device, based at least in part on the device property data update request; generating, via a device lookup circuit, a query that includes the one or more IoT UIDs; retrieving, via the device lookup circuit, first device property data corresponding to the one or more IoT UIDs; transmitting, via a query provisioning circuit, the query to an IoT device registrar server; interpreting, via a device property processing circuit, the device property data generated by the IoT UID server in response to the query, the device property data being included in a device entry in the IoT UID server corresponding to the IoT device; generating, via the query provisioning circuit, a request to the device for second device property data; receiving, via the query provisioning circuit, the second device property data from the device in response to the request; transmitting, via the query provisioning circuit, the updated device property data to the IoT device registrar server in response to the request to at least one of: replace at least a portion of the first device property data with the second device property data in the device entry in the IoT device registrar server; or add the second device property data to the device entry in the IoT device registrar server; interpreting, via the device property processing circuit, a comparison between the device property data the updated device property data; and displaying, via a display circuit, a result of the comparison between the device property data the updated device property data.
An example apparatus includes an input processing circuit structured to interpret a device property data update request for an Internet of Things (IoT) device; an Internet of Things Universal Identification (IoT UID) identification circuit structured to determine one or more IoT UIDs corresponding to the IoT device, based at least in part on the device property data update request; a device lookup circuit structured to: generate a query that includes the one or more IoT UIDs; and retrieve first device property data corresponding to the one or more IoT UIDs; a query provisioning circuit structured to transmit the query to an IoT device registrar server; a device property processing circuit structured to interpret the first device property data generated by the IoT UID server in response to the query, the first device property data being included in a device entry in the IoT UID server corresponding to the IoT device, wherein the query provisioning circuit is further structured to: generate a first request to the device for second device property data, receive the second device property data from the device in response to the first request, and transmit the second device property data to the IoT device registrar server in response to a second request to at least one of: replace at least a portion of the first device property data with the second device property data in the device entry in the IoT device registrar server, or add the second device property data to the device entry in the IoT device registrar server, and wherein the device property processing circuit is further structured to interpret a comparison between the first device property data and the second device property data; and a display circuit structured to display a result of the comparison between the first device property data and the second device property data.
An example apparatus includes an event data processing circuit structured to interpret an Internet of Things Universal Identification (IoT UID) and corresponding device property data; an event detection circuit structured to determine, based at least in part on the device property data, an event corresponding to a device corresponding to the IoT UID; and a record management circuit structured to update a record corresponding to the IoT UID, based at least in part on the event.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The event comprises determining that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a user input indicating that the device has reached end-of-life. The determining that the device has reached end-of-life comprises receiving a security notification indicating a device decommissioning. The determining that the device has reached end-of-life comprises receiving a decommission notification indicating a device decommissioning.
An example apparatus includes an Internet of Things Universal Identification (IoT UID) processing circuit structured to interpret an IoT UID corresponding to a device; a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database, the record including device ownership data associated with the device; an ownership analysis circuit structured to interpret, based at least in part on the record, the device ownership data associated with the device; and an ownership provisioning circuit structured to transmit the device ownership data.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of one or more entities. The record of one or more entities comprises an historic record of one or more entities that have owned the device. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The apparatus further including an access restriction circuit structured to restrict access to information about the device from an owner of the device. The access restriction circuit is further structured to restrict access to information about a first owner of the device from a second owner of the device. The apparatus further including a display circuit structured to display the device ownership data for the device. The apparatus further including an ownership data update provisioning circuit structured to provide updated ownership data to replace the device ownership data associated with the device. The ownership data update provisioning circuit is further structured to provide updated ownership data for one or more modules of the device. The updated ownership data comprises a claim of ownership of the device. Events resulting in the updated ownership data include at least one of: creation of the device, sale of the device, decommissioning of the device, transfer of ownership of the device, or licensing of the device. The apparatus further including a security notification provisioning circuit structured to: compare the device ownership data to a record of authorized owners; and generate a security notification if the device ownership data is not included in the record of authorized owners. The database comprises a blockchain. The apparatus further including a device theft notification circuit structured to certify that the device is not a stolen device. The apparatus further including a device title certification circuit structured to certify that the device has a fully accountable chain of title. The apparatus further including a trust indicator provisioning circuit structured to provide a trust indicator for the device. The trust indicator comprises a numeric value. The trust indicator comprises an enumerated value. The trust indicator is displayed as a color-coded value. A value of the trust indicator is based at least in part on a location of the device. A value of the trust indicator is based at least in part on a time period. A value of the trust indicator is based at least in part on at least one of a software version or a firmware version of the device. Determining the trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being a Greenfield device. The trust indicator is reflective of the device being a Brownfield device. The trust indicator is reflective of the device being a virtual device. The trust indicator is reflective of the device being a meta-device. The trust indicator is displayed as at least one of: at least one of: numeric based, color based, symbol based, alphanumeric based, letter based. The apparatus further including an asking price evaluation circuit structured to evaluate an asking price for the device based on at least one of: the device ownership data; a certification that the device is not a stolen device; or a certification that the device has a fully accountable chain of title. The asking price evaluation circuit is further structured to evaluate an asking price for a group of devices based on ownership data for each device. The apparatus further including a supply chain validation circuit structured to validate a supply chain. The validating the supply chain comprises determining whether modules of the device were sourced from authorized vendors. The validating the supply chain comprises determining whether modules of the device were sourced from fair trade certified sources. The apparatus further including a carbon rating provisioning circuit structured to provide a carbon rating of the device based on known ratings of sources of modules of the device, determined based on the device ownership data. The apparatus further including a device property detection circuit structured to detect a device property that indicates a change in ownership data. The device property comprises a location of the device.
An example method includes interpreting, via an Internet of Things Universal Identification (IoT UID) processing circuit, an IoT UID corresponding to a device; identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database, the record including device ownership data associated with the device; interpreting, via an ownership analysis circuit and based at least in part on the record, the device ownership data; and transmitting, via an ownership provisioning circuit, the device ownership data.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of one or more entities. The record of one or more entities comprises an historic record of one or more entities that have owned the device. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The method further including restricting access to information about the device from an owner of the device. The method further including restricting access to information about a first owner of the device from a second owner of the device. The method further including displaying the device ownership data for the device. The method further including providing updated ownership data to replace the device ownership data associated with the device. The method further including providing updated ownership data for one or more modules of the device. The updated ownership data comprises a claim of ownership of the device. Events resulting in the updated ownership data include at least one of: creation of the device, sale of the device, decommissioning of the device, transfer of ownership of the device, or licensing of the device. The method further including comparing the device ownership data to a record of authorized owners; and generating a security notification if the device ownership data is not included in the record of authorized owners. The database comprises a blockchain. The method further including certifying that the device is not a stolen device. The method further including certifying that the device has a fully accountable chain of title. The method further including providing a trust indicator for the device. The trust indicator comprises a numeric value. The trust indicator comprises an enumerated value. The trust indicator is displayed as a color-coded value. A value of the trust indicator is based at least in part on a location of the device. A value of the trust indicator is based at least in part on a time period. A value of the trust indicator is based at least in part on at least one of a software version or a firmware version of the device. Determining the trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being a Greenfield device. The trust indicator is reflective of the device being a Brownfield device. The trust indicator is reflective of the device being a Greenfield device. The trust indicator is reflective of the device being a Brownfield device. The trust indicator is displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, or letter based. The method further including evaluating an asking price for the device based on at least one of: the device ownership data; a certification that the device is not a stolen device; or a certification that the device has a fully accountable chain of title. The method further including evaluating an asking price for a group of devices based on ownership data for each device. The method further including validating a supply chain. The validating the supply chain comprises determining whether modules of the device were sourced from authorized vendors. The validating the supply chain comprises determining whether modules of the device were sourced from fair trade certified sources. The method further including providing a carbon rating of the device based on known ratings of sources of modules of the device, determined based on the device ownership data. The method further including detecting a device property that indicates a change in ownership data. The device property comprises a location of the device. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example system includes a database structured to store records associating Internet of Things Universal Identifications (IoT UIDs) with device ownership data; and a server structured to: communicate with the database interpret an IoT UID corresponding to a device; identify, based at least in part on the IoT UID corresponding to the device, a record in the database, the record including the device ownership data associated with the device; interpret, based at least in part on the record, the device ownership data; and transmit the device ownership data.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The server is further structured to restrict access to information about the device from an owner of the device. The server is further structured to provide updated ownership data to replace the device ownership data associated with the device.
An example method includes interpreting, via an input processing circuit, user input identifying a device ownership query for a device; generating, via a query provisioning circuit, a query for an Internet of Things Universal Identification (IoT UID), corresponding to the device, to an IoT device registrar server; identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database at the IoT device registrar server, the record including device ownership data associated with the device; interpreting, via an ownership analysis circuit and based at least in part on the record, the device ownership data; and transmitting, via an ownership provisioning circuit, the device ownership data to a user.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The method further including restricting access to information about the device from an owner of the device. The method further including providing updated ownership data to replace the device ownership data associated with the device.
An example apparatus includes an input processing circuit structured to interpret user input identifying a device ownership query for a device; a query provisioning circuit structured to generate a query for an Internet of Things Universal Identification (IoT UID) corresponding to the device to an IoT device registrar server; a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database at the IoT device registrar server, the record including device ownership data associated with the device; an ownership analysis circuit structured to interpret, based at least in part on the record, the device ownership data; and an ownership provisioning circuit structured to transmit the device ownership data to a user.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The apparatus further including an access restriction circuit structured to restrict access to information about the device from an owner of the device. The apparatus further including an ownership data update provisioning circuit structured to provide updated ownership data to replace the device ownership data associated with the device.
An example system includes an input processing circuit structured to interpret user input identifying a device ownership query for a device; a query provisioning circuit structured to generate a query for an Internet of Things Universal Identification (IoT UID) corresponding to the device; a database structured to store records associating IoT UIDs with device ownership data; and a server structured to: communicate with the database; interpret the query corresponding to the device; identify an IoT UID associated with the device; identify, based at least in part on the IoT UID associated with the device, a record in the database, the record including the device ownership data associated with the device; interpret, based at least in part on the record, the device ownership data; and transmit the device ownership data.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The device ownership data comprises a record of historical ownership. The device comprises a plurality of modules, each module having corresponding ownership data. The server is further structured to restrict access to information about the device from an owner of the device. The server is further structured to provide updated ownership data to the database to replace the device ownership data associated with the device.
An example method includes interpreting, via an Internet of Things Universal Identifier (IoT UID) processing circuit, an IoT UID corresponding to a device; identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database corresponding to the device; determining, via a trust analysis circuit and based at least in part on the record, a risk indicator of the device; and transmitting, via an indicator provisioning circuit, the risk indicator.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The risk indicator is a numeric value. The risk indicator is an enumerated value. The risk indicator is displayed as a color-coded value. The risk indicator is based at least in part on at least one of a location of the device, a time period, a software, or firmware version of the device. The risk indicator is based at least in part on artificial intelligence. The risk indicator is reflective of the device being a Greenfield device or a Brownfield device. The method further including authorizing an interaction with the device based at least in part on the risk indicator. The method further including prohibiting an interaction with the device based at least in part on the risk indicator. The interaction is an exchange of data with the device or is establishing a network connection with the device. The method further including adjusting the risk indicator based on an event of the device, wherein the event is at least one of a transfer of ownership, patching of the device, or an updating of a software and/or a firmware of the device. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes an Internet of Things Universal Identifier (IoT UID) processing circuit structured to interpret an IoT UID corresponding to a device; a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device; a trust analysis circuit structured to determine, based at least in part on the record, a risk indicator of the device; and an indicator provisioning circuit structured to transmit the risk indicator.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The risk indicator is a numeric value. The risk indicator is an enumerated value. The risk indicator is displayed as a color-coded value. The risk indicator is based at least in part on at least one of a location of the device, a time period, a software, or firmware version of the device. The risk indicator is based at least in part on artificial intelligence. The risk indicator is reflective of the device being a Greenfield device or a Brownfield device. The apparatus further including a trust indicator processing circuit structured to authorize an interaction with the device based at least in part on the risk indicator. The apparatus further including a trust indicator processing circuit structured to prohibit an interaction with the device based at least in part on the risk indicator. The apparatus wherein the interaction is an exchange of data with the device or is establishing a network connection with the device. The apparatus wherein the trust analysis circuit is further structured to adjust the risk indicator based on an event of the device, wherein the event is at least one of a transfer of ownership, patching of the device, or an updating of a software and/or a firmware of the device.
An example method includes interpreting, via an Internet of Things Universal Identifier (IoT UID) processing circuit, an IoT UID corresponding to a device; generating, via a trust verification circuit, a trust indicator request value that includes the IoT UID corresponding to the device; transmitting, via a trust indicator request provisioning circuit, the trust indicator request value to an IoT device registrar server; and interpreting, via a trust indicator processing circuit, a trust indicator generated by the IoT device registrar server in response to the trust indicator request value.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The trust indicator is based at least in part on at least one of a location of the device, a time period, a software, or firmware version of the device. The method further including authorizing an interaction with the device based at least in part on the trust indicator. The method further including prohibiting an interaction with the device based at least in part on the trust indicator. The trust indicator request further comprises contextual data and wherein the trust indicator is based on the contextual data. The contextual data comprises at least one of a location, a time, or an operation for execution by the device.
An example apparatus includes an Internet of Things Universal Identifier (IoT UID) processing circuit structured to interpret an IoT UID corresponding to a device; a trust verification circuit structured to generate a trust indicator request value that includes the IoT UID corresponding to the device; a trust indicator request provisioning circuit structured to transmit the trust indicator request value to an IoT device registrar server; and a trust indicator processing circuit structured to interpret a trust indicator generated by the IoT device registrar server in response to the trust indicator request value.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The trust indicator is based at least in part on at least one of a location of the device, a time period, a software, or firmware version of the device. The trust indicator processing circuit is further configured to authorize an interaction with the device based at least in part on the trust indicator. The trust indicator processing circuit is further configured to prohibit an interaction with the device based at least in part on the trust indicator. The trust indicator request further comprises contextual data and wherein the trust indicator is based on the contextual data. The contextual data comprises at least one of a location, a time, or an operation for execution by the device.
An example system includes at least one processor; an electronic display; and a memory device storing an application that adapts the at least one processor to: interpret an Internet of Things Universal Identifier (IoT UID) corresponding to a device; transmit the IoT UID; interpret at least one of a risk indicator or a trust indicator transmitted in response to transmission of the IoT UID by the at least one processor; and display the at least one of the risk indicator or the trust indicator on the electronic display.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The application further adapts the at least one processor to prohibit an interaction with the device corresponding to the IoT UID based at least in part on the at least one of the risk indicator or the trust indicator. The application further adapts the at least one processor to authorize an interaction with the device corresponding to the IoT UID based at least in part on the at least one of the risk indicator or the trust indicator. The at least one processor transmits the IoT UID corresponds to a unique combination of properties of the device. The device is registered with an IoT device registrar.
An example method includes interpreting, via an Internet of Things (IoT) Universal Identification (UID) processing circuit, an IoT UID corresponding to a device in a metaverse; identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database corresponding to the device in the metaverse; determining, via a trust analysis circuit and based at least in part on the record, a trust indicator of the device in the metaverse; and transmitting, via a trust indicator provisioning circuit, the trust indicator.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device in the metaverse is at least one of a server; a user; an avatar; an area; or an object. The device in the metaverse is at least one of a virtual device; a real-world device; or a meta-device. The device in the metaverse is an area of the metaverse. The area in the metaverse is a room in the metaverse. The trust indicator is at least one of a numeric value; or an enumerated value. The trust indicator is displayed as a color-coded value. The trust indicator comprises one or more of a trust level; a trust score; or a trust rating. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being at least one of a Greenfield device; or a Brownfield device. The method further including displaying the trust indicator. The method further including authorizing an interaction with the device based at least in part on the trust indicator. The method further including prohibiting an interaction with the device based at least in part on the trust indicator. The interaction is an exchange of data with the device. The interaction is establishing a network connection with the device. The method further including adjusting the trust indicator based on an event of the device. The event is a transfer of ownership. The event is a patching of the device. The event is an updating at least one of software or firmware of the device. The method further including a parental control software agent. The method further including providing the trust indicator to a user before the user enters an area of the metaverse containing the device. Providing the trust indicator to a user before the user enters the area of the metaverse is based at least in part on a trust indicator of the area of the metaverse. The area of the metaverse contains a plurality of devices. The trust indicator of the area in the metaverse is based at least in part on a combination of trust indicators of the plurality of devices in the area. The trust indicator of the device is based at least in part on a combination of trust indicators of a plurality of modules associated with the device. The method further including updating the trust indicator based on an interaction with the device. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes an Internet of Things (IoT) Universal Identification (UID) processing circuit structured to interpret an IoT UID corresponding to a device in a metaverse; a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device in the metaverse; a trust analysis circuit structured to determine, based at least in part on the record, a trust indicator of the device in the metaverse; and a trust indicator provisioning circuit structured to transmit the trust indicator.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device in the metaverse is at least one of a server; a user; an avatar; an area; or an object. The trust indicator is displayed as a color-coded value. The trust indicator comprises one or more of a trust level; a trust score; or a trust rating. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The trust indicator is reflective of the device being at least one of a Greenfield device; or Brownfield device. The apparatus further including displaying the trust indicator. The apparatus further including prohibiting an interaction with the device based at least in part on the trust indicator. The apparatus further including adjusting the trust indicator based on an event of the device. The apparatus further including providing the trust indicator to a user before the user enters an area of the metaverse containing the device. The apparatus of further including updating the trust indicator based on an interaction with the device.
An example method includes interpreting, via an Internet of Things (IoT) Universal Identification (UID) processing circuit, an IoT UID corresponding to a device in a metaverse; generating, via a trust verification circuit, a trust indicator request value that includes the IoT UID corresponding to the device in the metaverse; transmitting, via a trust indicator request provisioning circuit, a trust indicator request to an IoT device registrar server; and interpreting, via a trust indicator processing circuit, a trust indicator generated by the IoT device registrar server in response to the trust indicator request.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device in the metaverse is at least one of a server; a user; an avatar; or an object. The trust indicator is displayed as a color-coded value. The trust indicator comprises one or more of a trust level; a trust score; or a trust rating. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The trust indicator is reflective of the device being at least one of a Greenfield device; or a Brownfield device. The method further including displaying the trust indicator. The method further including prohibiting an interaction with the device based at least in part on the trust indicator. The method further including adjusting the trust indicator based on an event of the device. The method further including providing the trust indicator to a user before the user enters an area of the metaverse containing the device. The method further including updating the trust indicator based on an interaction with the device.
An example apparatus includes an Internet of Things (IoT) Universal Identification (UID) processing circuit structured to interpret an IoT UID corresponding to a device in a metaverse; a trust verification circuit structured to generate a trust indicator request value that includes the IoT UID corresponding to the device in the metaverse; a trust indicator request provisioning circuit structured to transmit a trust indicator request to an IoT device registrar server; and a trust indicator processing circuit structured to interpret a trust indicator generated by the IoT device registrar server in response to the trust indicator request.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device in the metaverse is at least one of a server; a user; an avatar; or an object. The trust indicator is displayed as a color-coded value. The trust indicator comprises one or more of a trust level; a trust score; or a trust rating. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The trust indicator is reflective of the device being at least one of a Greenfield device; or a Brownfield device. The apparatus further including displaying the trust indicator. The apparatus further including prohibiting an interaction with the device based at least in part on the trust indicator. The apparatus further including adjusting the trust indicator based on an event of the device. The apparatus further including providing the trust indicator to a user before the user enters an area of the metaverse containing the device. The apparatus further including updating the trust indicator based on an interaction with the device.
An example method includes interpreting, via an Internet of Things (IoT) Universal Identification (UID) processing circuit, an IoT UID corresponding to a device in an augmented reality (AR); identifying, via a record management circuit and based at least in part on the IoT UID, a record in a database corresponding to the device in the AR; determining, via a trust analysis circuit and based at least in part on the record, a trust indicator of the device in the AR; and transmitting, via a trust indicator provisioning circuit, the trust indicator.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device in the AR is at least one of an IoT device; a server; a user; or an avatar. The device in the AR corresponds to an area of a metaverse. The area in the metaverse is a room in the metaverse. The device in the AR is an object. The object is at least one of a virtual device; a real-world device; or a meta-device. The device in the AR is a real-world device. The trust indicator is at least one of a numeric value; or an enumerated value. The trust indicator comprises one or more of a trust level; a trust score; or a trust rating. The method, further including displaying the trust indicator in association with a real-world device. The method further including displaying the trust indicator overlaid on a real-world device. The trust indicator is displayed via an AR device. The AR device is one or more of an AR headset; AR contact lenses; AR glasses, or AR goggles. The trust indicator is displayed as a color-coded value. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. Determining the trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being at least one of a Greenfield device; or a Brownfield device. The method further including displaying the trust indicator. The method further including authorizing an interaction with the device based at least in part on the trust indicator. The method further including prohibiting an interaction with the device based at least in part on the trust indicator. The interaction is an exchange of data with a device. The interaction is an exchange of data with a device. The interaction is establishing a network connection with the device. The method further including adjusting the trust indicator based on an event of the device. The event is a transfer of ownership. The event is a patching of the device. The event is an updating at least one of software or firmware of the device. The method further including a parental control software agent. The method further including providing the trust indicator to a user interacts with the device. A trust indicator of a device in the AR is based at least in part on a combination of trust indicators of a plurality of entities in the AR. The method further including providing the trust indicator of the device to a user before the user enters an area of a metaverse containing the device. A trust indicator of the device is based at least in part on a combination of trust indicators of a plurality of modules associated with the device. The method further including updating the trust indicator based on an interaction with the device. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes an Internet of Things (IoT) Universal Identification (UID) processing circuit structured to interpret an IoT UID corresponding to a device in an augmented reality (AR); a record management circuit structured to identify, based at least in part on the IoT UID, a record in a database corresponding to the device in the AR; a trust analysis circuit structured to determine, based at least in part on the record, a trust indicator of the device in the AR; and a trust indicator provisioning circuit structured to transmit the trust indicator.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device in the AR is at least one of an IoT device; a server; a user; or an avatar. The device in the AR corresponds to an area of a metaverse. The apparatus further including displaying the trust indicator in association with a real-world device or overlaid on the real-world device. The trust indicator is displayed via an AR device, wherein the AR device is one or more of an AR headset; AR contact lenses; AR glasses, or AR goggles. The trust indicator is displayed as a color-coded value. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The apparatus further including authorizing an interaction with the device based at least in part on the trust indicator. The apparatus further including prohibiting an interaction with the device based at least in part on the trust indicator. The apparatus further including adjusting the trust indicator based on an event of the device. The apparatus further including a parental control software agent. A trust indicator of a device in the AR is based at least in part on a combination of trust indicators of a plurality of devices in the AR. The apparatus further including providing the trust indicator of the device to a user before the user enters an area of a metaverse containing the device.
An example method includes interpreting, via an Internet of Things (IoT) Universal Identification (UID) processing circuit, an IoT UID corresponding to a device in an augmented reality (AR); generating, via a trust verification circuit, a trust indicator request value that includes the IoT UID corresponding to the device in the AR; transmitting, via a trust indicator request provisioning circuit, a trust indicator request to an IoT device registrar server; and interpreting, via a trust indicator processing circuit, a trust indicator generated by the IoT device registrar server in response to the trust indicator request.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The device in the AR is at least one of an IoT device; a server; a user; or an avatar. The device in the AR corresponds to an area of a metaverse. The method further including displaying the trust indicator in association with a real-world device or overlaid on the real-world device. The trust indicator is displayed via an AR device, wherein the AR device is one or more of an AR headset; AR contact lenses; AR glasses, or AR goggles. The trust indicator is displayed as a color-coded value. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The method further including authorizing an interaction with the device based at least in part on the trust indicator. The method further including prohibiting an interaction with the device based at least in part on the trust indicator. The method further including adjusting the trust indicator based on an event of the device. The method further including a parental control software agent. The method wherein a trust indicator of a device in the AR is based at least in part on a combination of trust indicators of a plurality of devices in the AR. The method further including providing the trust indicator of the device to a user before the user enters an area of a metaverse containing the device.
An example apparatus includes an Internet of Things (IoT) Universal Identification (UID) processing circuit structured to interpret an IoT UID corresponding to a device in an augmented reality (AR); a trust verification circuit structured to generate a trust indicator request value that includes the IoT UID corresponding to the device in the AR; a trust indicator request provisioning circuit structured to transmit a trust indicator request to an IoT device registrar server; and a trust indicator processing circuit structured to interpret a trust indicator generated by the IoT device registrar server in response to the trust indicator request.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device in the AR is at least one of an IoT device; a server; a user; or an avatar. The device in the AR corresponds to an area of a metaverse. The apparatus further including displaying the trust indicator in association with a real-world device or overlaid on the real-world device. The trust indicator is displayed via an AR device, wherein the AR device is one or more of an AR headset; AR contact lenses; AR glasses, or AR goggles. The trust indicator is displayed as a color-coded value. The trust indicator is based at least in part on one of a location of the device; a time period; a software and/or firmware version of the device; a trust indicator of a device associated with the device; or a trust indicator of a user associated with of the device. The apparatus further including authorizing an interaction with the device based at least in part on the trust indicator. The apparatus further including prohibiting an interaction with the device based at least in part on the trust indicator. The apparatus further including adjusting the trust indicator based on an event of the device. The apparatus further including a parental control software agent. The apparatus wherein a trust indicator of a device in the AR is based at least in part on a combination of trust indicators of a plurality of entities in the AR. The apparatus further including providing the trust indicator of the device to a user before the user enters an area of a metaverse containing the device.
An example method includes monitoring, via at least one processor, one or more records in an internet of things (IoT) device registry for changes in device property data corresponding to one or more devices, each corresponding to one of the one or more records; detecting, via the at least one processor, a change in the device property data of at least one record; determining, via the at least one processor, that the change corresponds to a security vulnerability; generating, via at least one processor and responsive to the determined security vulnerability, a message that identifies a device corresponding to the change in the device property data; and transmitting, via the at least one processor, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including displaying the message. The method further including logging the change in a database. The method further including receiving the message at a device management platform and at least one of quarantining or patching the device. The message is an alert. The method further including adjusting a trust indicator based at least in part on the change. The trust indicator is at least one of a trust score, a rating, or a level value. The adjusting is an increase when the change corresponds to a patching or an updating of software and/or firmware of the device. The adjusting is a decrease when the change corresponds to a vulnerability. The change corresponds to an addition of a new module into the device. The new module is an input/output device. The input/output device is a network interface device. The input/output device is a media device. The change corresponds to a change in ownership of the device. The change is a location of the device. The security vulnerability is based on a software and/or firmware of the device. The security vulnerability is based on a hardware version of the device. The method further including accessing a security vulnerabilities database to pull security vulnerability signatures to determine if a registered device is affected. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example method includes at a first time, interpreting, via a device property data processing circuit, device property data corresponding to a device registered with an IoT device registry; at a second time, interpreting, via the device property data processing circuit, the device property data corresponding to the device registered with the IoT device registry; detecting, via a change detection circuit, a change in the device property data between the first time and the second time; generating, via an alert circuit and responsive to detecting the change, a message that identifies the device corresponding to the device property data; and transmitting, via an alert provisioning circuit, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including displaying the message. The method further including receiving the message at a device management platform and at least one of quarantining or patching the device. The method further including adjusting a trust indicator based at least in part on the change. The method wherein the change corresponds to an addition of a new module into the device. The method wherein the change corresponds to a change in ownership of the device. The method wherein the change is a location of the device.
An example apparatus includes a device property data processing circuit structured to: at a first time, interpret, device property data corresponding to a device registered with an IoT device registry; and at a second time, interpret, the device property data corresponding to the device registered with the IoT device registry; a change detection circuit structured to detect a change in the device property data between the first time and the second time; an alert circuit structured to generate, responsive to the detected change, a message that identifies the device corresponding to the device property data; and an alert provisioning circuit structured to transmit the message.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including the device property data processing circuit structured to display the message. The apparatus further including the device property data processing circuit structured to receive the message at a device management platform and at least one of quarantining or patching the device. The apparatus further including the device property data processing circuit structured to adjust a trust indicator based at least in part on the change. The change corresponds to an addition of a new module into the device. The change corresponds to a change in ownership of the device. The change is a location of the device.
An example system includes a device management platform structured to manage one or more devices registered with an IoT device registry; and a sentry device structured to: monitor the IoT device registry for changes in property data corresponding to the registered one or more devices; detect a change in the property data for at least one of the one or more devices; determine that the detected change corresponds to a security vulnerability; generate, responsive to the determined security vulnerability, a message that identifies the at least one device of the one or more devices; and transmit the message to the device management platform, wherein the device management platform is further structured to: interpret the message transmitted by the sentry device; and at least one of: quarantine the at least one device; or patch the at least one device.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The system further including the sentry device structured to display the message. The system further including the sentry device structured to receive the message at a device management platform and at least one of quarantining or patching the one or more devices. The system further including the sentry device structured to adjust a trust indicator based at least in part on the change. The change corresponds to an addition of a new module into the one or more devices. The change corresponds to a change in ownership of the one or more devices. The change is a location of the one or more devices.
An example method includes interpreting, via a device property data processing circuit, device property data corresponding to a device registered with an IoT device registry; detecting, via a security analysis circuit, based at least in part on the device property data, that the device is subject to a security vulnerability; generating, responsive to the detected security vulnerability, via an alert circuit, a message that identifies the device; and transmitting, via an alert provisioning circuit, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including displaying the message. The method further including receiving the message at a device management platform and at least one of quarantining or patching the device.
An example apparatus includes a device property data processing circuit structured to interpret device property data corresponding to a device registered with an IoT device registry; a security analysis circuit structured to determine, based at least in part on the device property data, that the device is subject to a security vulnerability; an alert circuit structured to generate, responsive to the determined security vulnerability, a message that identifies the device; and an alert provisioning circuit structured to transmit the message.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The device property data processing circuit further structured to display the message. The device property data processing circuit further structured to receive the message at a device management platform and at least one of quarantining or patching the device.
An example apparatus includes a device property data processing circuit structured to interpret device property data corresponding to one or more devices registered with an Internet of Things (IoT) device registry; an outage detection circuit structured to detect an outage pattern in the device property data, the outage pattern corresponding to an outage of the one or more devices; an alert circuit structured to, responsive to the outage pattern, generate an alert message that identifies the one or more devices; and an alert provisioning circuit structured to transmit the alert message.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The outage detection circuit comprises an artificial intelligence circuit structured to detect the outage pattern, based at least in part on analyzing the device property data using an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between outage patterns and at least one of a weather event; a cyber-attack; a device failure event; device ownership; a device manufacturer; a location; or a network outage. The artificial intelligence process is based at least in part on a deep learning network. The apparatus further including a visualization circuit structured to generate and transmit outage visualization data configured to depict a visualization of the outage on an electronic display. The visualization is a map. The visualization is a chart depicting an amount of the one or more devices affected by the outage. The alert provisioning circuit is structured to transmit the alert message to at least one of a device management platform corresponding to the one or more devices; a user of the one or more devices; a manufacturer of the one or more devices; or an entity that monitors the one or more devices. The outage detection circuit forms part of a device management platform. The outage detection circuit forms part of the IoT device registry.
An example method includes interpreting, via a device property data processing circuit, device property data corresponding to one or more devices registered with an Internet of Things (IoT) device registry; detecting, via an outage detection circuit, an outage pattern in the device property data, the outage pattern corresponding to an outage of the one or more devices; responsive to the outage pattern, generating, via an alert circuit, an alert message that identifies the one or more devices; and transmitting, via an alert provisioning circuit, the alert message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The detecting, via the outage detection circuit, an outage pattern in the device property data, the outage pattern corresponding to an outage of the one or more devices comprises detecting the outage pattern via analyzing the device property data with an artificial intelligence circuit that uses an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between outage patterns and at least one of a weather event; a cyber-attack; a device failure event; device ownership; a device manufacturer; a location; or a network outage. The method further including generating, via a visualization circuit, visualization data configured to depict a visualization of the outage on an electronic display; and transmitting, via the visualization circuit, the visualization data. The visualization is a map. The visualization is a chart depicting an amount of the one or more devices affected by the outage. The method further including interpreting the visualization data; and displaying, via the electronic display, the visualization of the outage. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example non-transitory computer-readable medium includes instructions to interpret device property data corresponding to one or more devices registered with an Internet of Things (IoT) device registry; detect an outage pattern in the device property data, the outage pattern corresponding to an outage of the one or more devices; responsive to the outage pattern, generate an alert message that identifies the one or more devices; and transmit the alert message.
Certain further aspects of the example non-transitory computer-readable medium are described following, any one or more of which may be present in certain embodiments. The stored instructions further adapt the at least one processor to detect the outage pattern via an artificial intelligence process. The outage pattern is detected based at least in part on one of a weather event; a cyber-attack; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example method includes collecting a data set including: one or more outage patterns; and device property data; creating a first training set including one or more portions of the device property data that correspond to the one or more outage patterns; creating a second training set including one or more portions of the device property data that incorrectly identify the one or more outage patterns; training the AI on the first training set; and training the AI on the second training set.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. At least one of the first training set and the second training set is based at least in part on at least one of a weather event; a cyber-attack; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example apparatus includes a device property data processing circuit structured to interpret device property data corresponding to a device registered with an Internet of Things (IoT) device registry; a security analysis circuit structured to determine, based at least in part on the device property data, that the device is subject to a fraud event; an alert circuit structured to generate, responsive to the determined fraud event, a message that identifies the device; and an alert provisioning circuit structured to transmit the message.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The security analysis circuit comprises an artificial intelligence circuit structured to detect the fraud event, based at least in part on analyzing the device property data using an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage. The artificial intelligence process is based at least in part on a deep learning network. The apparatus further including a visualization circuit structured to generate and transmit fraud event visualization data configured to depict a visualization of the fraud event on an electronic display. The visualization is a map. The visualization is a chart depicting at least one of the device affected by the fraud event. The alert provisioning circuit is further structured to transmit the message to at least one of a device management platform corresponding to the device; a user of the device; a manufacturer of the device; or an entity that monitors the device. The security analysis circuit forms part of a device management platform. The security analysis circuit forms part of the IoT device registry. The apparatus further including a display circuit structured to display the message. The apparatus further including a fraud event log circuit structured to log the fraud event in a database. The apparatus further including a device management platform structured to interpret the message transmitted by the alert provisioning circuit; and at least one of quarantine the at least one device; disable the at least one device; disable at least part of the device; disable at least some functionality of the device; send an alert to the device; send an alert to an entity associated with the device; or patch the at least one device. The apparatus further including a trust indicator provisioning circuit structured to provide a trust indicator for the device, based at least in part on the determined fraud event. The trust indicator comprises at least one of: a numeric value, an alphabetic value, or an alphanumeric value. The trust indicator comprises an enumerated value. The trust indicator is displayed as a color-coded value. A value of the trust indicator is based at least in part on a location of the device. A value of the trust indicator is based at least in part on a time period. A value of the trust indicator is based at least in part on at least one of a software version or a firmware version of the device. Determining the trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being a Greenfield device. The trust indicator is reflective of the device being a Brownfield device. The trust indicator is reflective of the device being a virtual device. The trust indicator is reflective of the device being a meta-device. The trust indicator is displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, or letter based. The trust indicator provisioning circuit is further structured to adjust a value of the trust indicator is adjusted based at least in part on the determined fraud event. The adjustment is an increase when the determined fraud event corresponds to at least one of a patching or an updating of at least one of software or firmware of the device. The adjustment is a decrease when the determined fraud event corresponds to a cyber-attack. The determined fraud event corresponds to an addition of a new module into the device. The new module is at least one of an input device or an output device. The at least one of the input device or the output device is a network interface device. The at least one of the input device or the output device is a media device. The determined fraud event corresponds to a change in ownership of the device. The determined fraud event is based on detecting a change in a location of the device. The determined fraud event is based on detecting a change in at least one of a software version or a firmware version of the device. The determined fraud event is based on detecting a change in a hardware version of the device. The security analysis circuit is further structured to access a fraud event database to interpret fraud event signatures to determine that the device is subject to the fraud event. The apparatus further including an IoT Universal Identification (UID) processing circuit structured to interpret an IoT UID and the device property data; a record management circuit structured to associate the IoT UID with the device property data via a record; and a record provisioning circuit structured to transmit the record.
An example method includes interpreting, via a device property data processing circuit, device property data corresponding to a device registered with an Internet of Things (IoT) device registry; determining, via a security analysis circuit based at least in part on the device property data, that the device is subject to a fraud event; generating, responsive to the determined fraud event, via an alert circuit, a message that identifies the device; and transmitting, via an alert provisioning circuit, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The determining, via the security analysis circuit, that the device is subject to a fraud event comprises detecting the fraud event via analyzing the device property data with an artificial intelligence circuit that uses an artificial intelligence process. The artificial intelligence process includes a neural network. The method further including training the neural network on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage. The artificial intelligence process is based at least in part on a deep learning network. The method further including generating and transmitting, via a visualization circuit, fraud event visualization data configured to depict a visualization of the fraud event on an electronic display. The visualization is a map. The visualization is a chart depicting at least one of the device affected by the fraud event. The method further including transmitting, via the alert provisioning circuit, the message to at least one of a device management platform corresponding to the device; a user of the device; a manufacturer of the device; or an entity that monitors the device. The security analysis circuit forms part of a device management platform. The security analysis circuit forms part of the IoT device registry. The method further including displaying the message via a display circuit. The method further including logging the fraud event in a database via a fraud event log circuit. The method further including interpreting, via a device management platform, the message transmitted by the alert provisioning circuit; and by the device management platform, at least one of: quarantining the device; disabling the device; or patching the device. The method further including providing a trust indicator for the device, based at least in part on the determined fraud event. The trust indicator comprises at least one of: a numeric value, an alphabetic value, or an alphanumeric value. The trust indicator comprises an enumerated value. The trust indicator is displayed as a color-coded value. A value of the trust indicator is based at least in part on a location of the device. A value of the trust indicator is based at least in part on a time period. A value of the trust indicator is based at least in part on at least one of a software version or a firmware version of the device. Determining the trust indicator is based at least in part on artificial intelligence. The trust indicator is reflective of the device being a Greenfield device. The trust indicator is reflective of the device being a Brownfield device. The trust indicator is reflective of the device being a virtual device. The trust indicator is reflective of the device being a meta-device. The trust indicator is displayed as at least one of: numeric based, color based, symbol based, alphanumeric based, or letter based. The method further including adjusting a value of the trust indicator based at least in part on the determined fraud event. The adjusting is an increase when the determined fraud event corresponds to at least one of a patching or an updating of at least one of software or firmware of the device. The adjusting is a decrease when the determined fraud event corresponds to a cyber-attack. The determined fraud event corresponds to an addition of a new module into the device. The new module is at least one of an input device or an output device. The at least one of the input device or the output device is a network interface device. The at least one of the input device or the output device is a media device. The determined fraud event corresponds to a change in ownership of the device. The determined fraud event is based on detecting a change in a location of the device. The determined fraud event is based on detecting a change in at least one of a software version or a firmware version of the device. The determined fraud event is based on detecting a change in a hardware version of the device. The method further including accessing, by the security analysis circuit, a fraud event database to interpret fraud event signatures to determine that the device is subject to the fraud event. The method further including interpreting, via an IoT UID processing circuit, an IoT UID and the device property data; associating, via a record management circuit, the IoT UID with the device property data via a record; and transmitting, via a record provisioning circuit, the record. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes a device property data processing circuit structured to: at a first time, interpret device property data corresponding to a device registered with an Internet of Things (IoT) device registry; and at a second time, interpret the device property data corresponding to the device registered with the IoT device registry; a change detection circuit structured to detect a change in the device property data between the first time and the second time; a fraud detection circuit structured to determine that the change corresponds to a fraud event; an alert circuit structured to generate, responsive to the determining that the change corresponds to a fraud event, a message that identifies the device corresponding to the device property data; and an alert provisioning circuit structured to transmit the message.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The fraud detection circuit comprises an artificial intelligence circuit structured to detect the fraud event, based at least in part on analyzing the device property data using an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example method includes at a first time, interpreting, via a device property data processing circuit, device property data corresponding to a device registered with an Internet of Things (IoT) device registry; at a second time, interpreting, via the device property data processing circuit, the device property data corresponding to the device registered with the IoT device registry; detecting, via a change detection circuit, a change in the device property data between the first time and the second time; determining, by a fraud detection circuit, that the change corresponds to a fraud event; generating, via an alert circuit and responsive to the determining that the change corresponds to a fraud event, a message that identifies the device corresponding to the device property data; and transmitting, via an alert provisioning circuit, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The determining, via the fraud detection circuit, that the change corresponds to a fraud event comprises detecting the fraud event via analyzing the device property data with an artificial intelligence circuit that uses an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example system includes a device management platform structured to manage one or more devices registered with an Internet of Things (IoT) device registry; and a fraud detection device structured to: monitor the IoT device registry for changes in device property data corresponding to the registered one or more devices; detect a change in the device property data for at least one device among the one or more devices; determine that the detected change corresponds to a fraud event; generate, responsive to the determined fraud event, a message that identifies the at least one device; and transmit the message to the device management platform, wherein the device management platform is further structured to: interpret the message transmitted by the fraud detection device, and at least one of: quarantine the at least one device, disable the at least one device, disable at least part of the device, disable at least some functionality of the device, send an alert to the device, send an alert to an entity associated with the device, or patch the at least one device.
Certain further aspects of the example system are described following, any one or more of which may be present in certain embodiments. The fraud detection device comprises an artificial intelligence circuit structured to detect the fraud event, based at least in part on analyzing the device property data using an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example method includes monitoring, via at least one processor, one or more records in an Internet of Things (IoT) device registry for changes in device property data corresponding to one or more devices, each of the one or more devices corresponding to one of the one or more records; detecting, via the at least one processor, a change in the device property data of at least one record among the one or more records; determining, via the at least one processor, that the change corresponds to a fraud event; generating, via the at least one processor and responsive to the detected fraud event, a message that identifies the device, corresponding to the changed device property data; and transmitting, via the at least one processor, the message.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The determining that the change corresponds to a fraud event comprises detecting the fraud event via analyzing the device property data with an artificial intelligence circuit that uses an artificial intelligence process. The artificial intelligence process includes a neural network. The neural network is trained on detecting correlations between the fraud event and at least one of a cyber-attack; a software version; a firmware version; a hardware version; an unauthorized access; a device failure event; device ownership; a device manufacturer; a location; or a network outage.
An example method includes interpreting, via an Internet of Things Universal Identification (IoT UID) processing circuit, an IoT UID and device property data corresponding to a meta-device; associating, via a record management circuit, the IoT UID with the device property data in a record in a database; and transmitting, via a record provisioning circuit, the record.
Certain further aspects of the example method are described following, any one or more of which may be present in certain embodiments. The method further including transmitting at least one of the IoT UID or the record to a user in a virtual environment. The method further including displaying at least one of the IoT UID or the record in a virtual environment. The method further including generating at least one of a trust indicator and/or a risk indicator for the meta-device; and storing the trust indicator and/or the risk indicator in the record associated with the IoT UID. The method further including transmitting the trust indicator and/or the risk indicator to a user in a virtual environment. The method further including displaying the trust indicator and/or the risk indicator in a virtual environment in relation to the meta-device. The method further including interpreting a device event message and updating a record in an IoT device registry based at least in part on the device event message.
An example apparatus includes an IoT UID processing circuit structured to interpret an IoT UID and device property data corresponding to a meta-device a record management circuit structured to associate the IoT UID with the device property data via a record; and a record provisioning circuit structured to transmit the record.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The apparatus further including an authentication circuit structured to generate a trust indicator and/or a risk indicator for the meta-device; and store the trust indicator and/or the risk indicator in the record associated with the IoT UID. The meta-device lacks a real-world counterpart. The meta-device has at least one real-world counterpart. The meta-device has at least two real-world counterparts. The at least two real-world counterparts are in different locations. The device property data is at least one of an NFT, an owner identifier value, a manufacturer identifier value, a Trusted Platform Module (TPM) Key, a Media Access Control (MAC) address, a serial number, a software version, or a firmware version. The meta-device is at least one of a Greenfield device or a Brownfield device.
An example apparatus includes an IoT UID processing circuit structured to interpret an IoT UID associated with a meta-device; a device lookup circuit structured to generate a query that includes the IoT UID and is structured to retrieve device property data corresponding to the IoT UID; and a query provisioning circuit structured to transmit the query to an IoT device registrar server.
Certain further aspects of the example apparatus are described following, any one or more of which may be present in certain embodiments. The meta-device lacks a real-world counterpart. The meta-device has at least one real-world counterpart. The meta-device has at least two real-world counterparts. The at least two real-world counterparts are in different locations. The device property data is at least one of an NFT, an owner identifier value, a manufacturer identifier value, a Trusted Platform Module (TPM) Key, a Media Access Control (MAC) address, a serial number, a software version, or a firmware version.
The methods and systems described herein may be deployed in part or in whole through a machine having a computer, computing device, processor, circuit, and/or server that executes computer readable instructions, program codes, instructions, and/or includes hardware configured to functionally execute one or more operations of the methods and systems herein. The terms computer, computing device, processor, circuit, and/or server, (“computing device”) as utilized herein, should be understood broadly. Non-limiting examples include the IoT device registrar server 1126 (
An example computing device includes a computer of any type, capable to access instructions stored in communication thereto such as upon a non-transient computer readable medium, whereupon the computer performs operations of the computing device upon executing the instructions. In certain embodiments, such instructions themselves comprise a computing device. Additionally or alternatively, a computing device may be a separate hardware device, one or more computing resources distributed across hardware devices, and/or may include such aspects as logical circuits, embedded circuits, sensors, actuators, input and/or output devices, network and/or communication resources, memory resources of any type, processing resources of any type, and/or hardware devices configured to be responsive to determined conditions to functionally execute one or more operations of systems and methods herein.
Network and/or communication resources include, without limitation, local area network, wide area network, wireless, internet, or any other known communication resources and protocols. Example and non-limiting hardware and/or computing devices include, without limitation, a general-purpose computer, a server, an embedded computer, a mobile device, a virtual machine, and/or an emulated computing device. A computing device may be a distributed resource included as an aspect of several devices, included as an interoperable set of resources to perform described functions of the computing device, such that the distributed resources function together to perform the operations of the computing device. In certain embodiments, each computing device may be on separate hardware, and/or one or more hardware devices may include aspects of more than one computing device, for example as separately executable instructions stored on the device, and/or as logically partitioned aspects of a set of executable instructions, with some aspects comprising a part of one of a first computing device, and some aspects comprising a part of another of the computing devices.
A computing device may be part of a server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform. A processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like. The processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon. In addition, the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application. By way of implementation, methods, program codes, program instructions and the like described herein may be implemented in one or more threads. The thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code. The processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere. The processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere. The storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.
A processor may include one or more cores that may enhance speed and performance of a multiprocessor. In embodiments, the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).
The methods and systems described herein, including those relating to the IoT device registrar 1130, manufacturer 1134, user 1136, third party 1138, and/or other entities disclosed herein, may be deployed in part or in whole through a machine that executes computer readable instructions on a server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware. The computer readable instructions may be associated with a server that may include a file server, print server, domain server, internet server, intranet server and other variants such as secondary server, host server, distributed server and the like. The server may include one or more of memories, processors, computer readable transitory and/or non-transitory media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like. The methods, programs, or codes as described herein and elsewhere may be executed by the server. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
The server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, and the like. Additionally, this coupling and/or connection may facilitate remote execution of instructions across the network. The networking of some or all of these devices may facilitate parallel processing of program code, instructions, and/or programs at one or more locations without deviating from the scope of the disclosure. In addition, all the devices attached to the server through an interface may include at least one storage medium capable of storing methods, program code, instructions, and/or programs. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for methods, program code, instructions, and/or programs.
The methods, program code, instructions, and/or programs may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like. The client may include one or more of memories, processors, computer readable transitory and/or non-transitory media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like. The methods, program code, instructions, and/or programs as described herein and elsewhere may be executed by the client. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
The client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers, and the like. Additionally, this coupling and/or connection may facilitate remote execution of methods, program code, instructions, and/or programs across the network. The networking of some or all of these devices may facilitate parallel processing of methods, program code, instructions, and/or programs at one or more locations without deviating from the scope of the disclosure. In addition, all the devices attached to the client through an interface may include at least one storage medium capable of storing methods, program code, instructions, and/or programs. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for methods, program code, instructions, and/or programs.
The methods and systems described herein may be deployed in part or in whole through network infrastructures. The network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules, and/or components as known in the art. The computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like. The methods, program code, instructions, and/or programs described herein and elsewhere may be executed by one or more of the network infrastructural elements.
The methods, program code, instructions, and/or programs described herein and elsewhere may be implemented on a cellular network having multiple cells. The cellular network may either be frequency division multiple access (FDMA) network or code division multiple access (CDMA) network. The cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like.
The methods, program code, instructions, and/or programs described herein and elsewhere may be implemented on or through mobile devices. The mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices. The computing devices associated with mobile devices may be enabled to execute methods, program code, instructions, and/or programs stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices. The mobile devices may communicate with base stations interfaced with servers and configured to execute methods, program code, instructions, and/or programs. The mobile devices may communicate on a peer-to-peer network, mesh network, or other communications network. The methods, program code, instructions, and/or programs may be stored on the storage medium associated with the server and executed by a computing device embedded within the server. The base station may include a computing device and a storage medium. The storage device may store methods, program code, instructions, and/or programs executed by the computing devices associated with the base station.
The methods, program code, instructions, and/or programs may be stored and/or accessed on machine readable transitory and/or non-transitory media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g. USB sticks or keys), floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
Certain operations described herein include interpreting, receiving, and/or determining one or more values, parameters, inputs, data, or other information (“receiving data”). Operations to receive data include, without limitation: receiving data via a user input; receiving data over a network of any type; reading a data value from a memory location in communication with the receiving device; utilizing a default value as a received data value; estimating, calculating, or deriving a data value based on other information available to the receiving device; and/or updating any of these in response to a later received data value. In certain embodiments, a data value may be received by a first operation, and later updated by a second operation, as part of the receiving a data value. For example, when communications are down, intermittent, or interrupted, a first receiving operation may be performed, and when communications are restored an updated receiving operation may be performed.
Certain logical groupings of operations herein, for example methods or procedures of the current disclosure, are provided to illustrate aspects of the present disclosure. Operations described herein are schematically described and/or depicted, and operations may be combined, divided, re-ordered, added, or removed in a manner consistent with the disclosure herein. It is understood that the context of an operational description may require an ordering for one or more operations, and/or an order for one or more operations may be explicitly disclosed, but the order of operations should be understood broadly, where any equivalent grouping of operations to provide an equivalent outcome of operations is specifically contemplated herein. For example, if a value is used in one operational step, the determining of the value may be required before that operational step in certain contexts (e.g., where the time delay of data for an operation to achieve a certain effect is important), but may not be required before that operation step in other contexts (e.g. where usage of the value from a previous execution cycle of the operations would be sufficient for those purposes). Accordingly, in certain embodiments an order of operations and grouping of operations as described is explicitly contemplated herein, and in certain embodiments re-ordering, subdivision, and/or different grouping of operations is explicitly contemplated herein.
The methods and systems described herein may transform physical and/or or intangible items from one state to another. The methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.
The methods and/or processes described above, and steps thereof, may be realized in hardware, program code, instructions, and/or programs or any combination of hardware and methods, program code, instructions, and/or programs suitable for a particular application. The hardware may include a dedicated computing device or specific computing device, a particular aspect or component of a specific computing device, and/or an arrangement of hardware components and/or logical circuits to perform one or more of the operations of a method and/or system. The processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory. The processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine readable medium.
The computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and computer readable instructions, or any other machine capable of executing program instructions.
Thus, in one aspect, each method described above, and combinations thereof, may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof. In another aspect, the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware. In another aspect, the means for performing the steps associated with the processes described above may include any of the hardware and/or computer readable instructions described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.
While the disclosure has been disclosed in connection with certain embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the present disclosure is not to be limited by the foregoing examples but is to be understood in the broadest sense allowable by law.
This application claims benefit of priority to U.S. Provisional Patent Application 63/175,920, filed Apr. 16, 2021 (attorney docket reference SMS8-0010-P01), and entitled “NETWORK CONNECTED DEVICE MANAGEMENT PLATFORM”. The above application is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63175920 | Apr 2021 | US |
