Patent Grant
9992158
This disclosure relates data communication profiles for systems, devices, methods, and related computer program products for smart buildings, such as a smart home. This disclosure relates to a fabric network that couples electronic devices using one or more network types and a locale profile used to identify and/or provide information about the electronic devices.
Some homes today are equipped with smart home networks to provide automated control of devices, appliances and systems, such as heating, ventilation, and air conditioning (“HVAC”) systems, lighting systems, alarm systems, and home theater and entertainment systems. Smart home networks may include control panels that a person may use to input settings, preferences, and scheduling information that the smart home network uses to provide automated control the various devices, appliances and systems in the home. For example, a person may input a desired temperature and a schedule indicating when the person is away from home. However, these networks may include various devices that may have different languages and/or locations that cause communications between the devices and/or users to be less effective than desired.
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.
Embodiments of the present disclosure relate to systems and methods a fabric network that includes one or more logical networks that enables devices connected to the fabric to communicate with each other using a list of protocols and/or profiles known to the devices. The communications between the devices may follow a typical message format that enables the devices to understand communications between the devices regardless of which logical networks the communicating devices are connected to in the fabric. Within the message format, a payload of data may be included for the receiving device to store and/or process. The format and the contents of the payload may vary according to a header (e.g., profile tag) within the payload that indicates a specific profile (including one or more protocols) and/or a type of message that is being sent according to the profile.
According to some embodiments, two or more devices in a fabric may communicate using various profiles. For example, in certain embodiments, a locale profile, a network provisioning profile, or a core profile (including status reporting protocols) that are available to devices connected to the fabric. For example, using a locale profile, devices may send or request information to or from other devices in the fabric in an understood message format to cause the devices to indicate a location and/or language that is currently being used and/or that is available. Furthermore, a device may change the location and/or language being used by another device that is remote from the device being changed.
Various refinements of the features noted above may exist in relation to various aspects of the present disclosure. Further features may also be incorporated in these various aspects as well. These refinements and additional features may exist individually or in any combination. For instance, various features discussed below in relation to one or more of the illustrated embodiments may be incorporated into any of the above-described aspects of the present disclosure alone or in any combination. The brief summary presented above is intended only to familiarize the reader with certain aspects and contexts of embodiments of the present disclosure without limitation to the claimed subject matter.
Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings in which:
One or more specific embodiments of the present disclosure will be described below. These described embodiments are only examples of the presently disclosed techniques. Additionally, in an effort to provide a concise description of these embodiments, features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but may nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. Additionally, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
Embodiments of the present disclosure relate generally to an efficient fabric network that may be used by devices and/or services communicating with each other in a home environment. Generally, consumers living in homes may find it useful to coordinate the operations of various devices within their home such that of their devices are operated efficiently. For example, a thermostat device may be used to detect a temperature of a home and coordinate the activity of other devices (e.g., lights) based on the detected temperature. In this example, the thermostat device may detect a temperature that may indicate that the temperature outside the home corresponds to daylight hours. The thermostat device may then convey to the light device that there may be daylight available to the home and that thus the light should turn off.
In addition to operating these devices efficiently, consumers generally prefer to use user-friendly devices that involve a minimum amount of set up or initialization. That is, consumers may generally prefer to purchase devices that are fully operational after performing a few number initialization steps that may be performed by almost any individual regardless of age or technical expertise.
With the foregoing in mind, to enable to effectively communicate data between each other within the home environment, the devices may use a fabric network that includes one or more logical networks to manage communication between the devices. That is, the efficient fabric network may enable numerous devices within a home to communicate with each other using one or more logical networks. The communication network may support Internet Protocol version 6 (IPv6) communications such that each connected device may have a unique local address (LA). Moreover, to enable each device to integrate with a home, it may be useful for each device to communicate within the network using low amounts of power. That is, by enabling devices to communicate using low power, the devices may be placed anywhere in a home without being coupled to a continuous power source (e.g., battery-powered).
I. Fabric Introduction
By way of introduction,
The sensors 12, in certain embodiments, may detect various properties such as acceleration, temperature, humidity, water, supplied power, proximity, external motion, device motion, sound signals, ultrasound signals, light signals, fire, smoke, carbon monoxide, global-positioning-satellite (GPS) signals, radio-frequency (RF), other electromagnetic signals or fields, or the like. As such, the sensors 12 may include temperature sensor(s), humidity sensor(s), hazard-related sensor(s) or other environmental sensor(s), accelerometer(s), microphone(s), optical sensors up to and including camera(s) (e.g., charged coupled-device or video cameras), active or passive radiation sensors, GPS receiver(s) or radiofrequency identification detector(s). While
One or more user-interface components 14 in the device 10 may receive input from the user and/or present information to the user. The user-interface component 14 may also include one or more user-input components that may receive information from the user. The received input may be used to determine a setting. In certain embodiments, the user-input components may include a mechanical or virtual component that responds to the user's motion. For example, the user can mechanically move a sliding component (e.g., along a vertical or horizontal track) or rotate a rotatable ring (e.g., along a circular track), the user's motion along a touchpad may be detected, or motions/gestures may be detected using a contactless gesture detection sensor (e.g., infrared sensor or camera). Such motions may correspond to a setting adjustment, which can be determined based on an absolute position of a user-interface component 104 or based on a displacement of a user-interface components 104 (e.g., adjusting a setpoint temperature by 1 degree F. for every 10° rotation of a rotatable-ring component). Physically and virtually movable user-input components can allow a user to set a setting along a portion of an apparent continuum. Thus, the user may not be confined to choose between two discrete options (e.g., as would be the case if up and down buttons were used) but can quickly and intuitively define a setting along a range of possible setting values. For example, a magnitude of a movement of a user-input component may be associated with a magnitude of a setting adjustment, such that a user may dramatically alter a setting with a large movement or finely tune a setting with s small movement.
The user-interface components 14 may also include one or more buttons (e.g., up and down buttons), a keypad, a number pad, a switch, a microphone, and/or a camera (e.g., to detect gestures). In one embodiment, the user-input component 14 may include a click-and-rotate annular ring component that may enable the user to interact with the component by rotating the ring (e.g., to adjust a setting) and/or by clicking the ring inwards (e.g., to select an adjusted setting or to select an option). In another embodiment, the user-input component 14 may include a camera that may detect gestures (e.g., to indicate that a power or alarm state of a device is to be changed). In some instances, the device 10 may have one primary input component, which may be used to set various types of settings. The user-interface components 14 may also be configured to present information to a user via, e.g., a visual display (e.g., a thin-film-transistor display or organic light-emitting-diode display) and/or an audio speaker.
The power-supply component 16 may include a power connection and/or a local battery. For example, the power connection may connect the device 10 to a power source such as a line voltage source. In some instances, an AC power source can be used to repeatedly charge a (e.g., rechargeable) local battery, such that the battery may be used later to supply power to the device 10 when the AC power source is not available. In certain embodiments, the power supply component 16 may include intermittent or reduced power connections that may be less than that provided via an AC plug in the home. In certain embodiments, devices with batteries and/or intermittent or reduced power may be operated as “sleepy devices” that alternate between an online/awake state and an offline/sleep state to reduce power consumption.
The network interface 18 may include one or more components that enable the device 10 to communicate between devices using one or more logical networks within the fabric network. In one embodiment, the network interface 18 may communicate using an efficient network layer as part of its Open Systems Interconnection (OSI) model. In certain embodiments, one component of the network interface 18 may communicate with one logical network (e.g., WiFi) and another component of the network interface may communicate with another logical network (e.g., 802.15.4). In other words, the network interface 18 may enable the device 10 to wirelessly communicate via multiple IPv6 networks. As such, the network interface 18 may include a wireless card, Ethernet port, and/or other suitable transceiver connections.
The processor 20 may support one or more of a variety of different device functionalities. As such, the processor 20 may include one or more processors configured and programmed to carry out and/or cause to be carried out one or more of the functionalities described herein. In one embodiment, the processor 20 may include general-purpose processors carrying out computer code stored in local memory (e.g., flash memory, hard drive, random access memory), special-purpose processors or application-specific integrated circuits, other types of hardware/firmware/software processing platforms, and/or some combination thereof. Further, the processor 20 may be implemented as localized versions or counterparts of algorithms carried out or governed remotely by central servers or cloud-based systems, such as by virtue of running a Java virtual machine (JVM) that executes instructions provided from a cloud server using Asynchronous Javascript and XML (AJAX) or similar protocols. By way of example, the processor 20 may detect when a location (e.g., a house or room) is occupied, up to and including whether it is occupied by a specific person or is occupied by a specific number of people (e.g., relative to one or more thresholds). In one embodiment, this detection can occur, e.g., by analyzing microphone signals, detecting user movements (e.g., in front of a device), detecting openings and closings of doors or garage doors, detecting wireless signals, detecting an IP address of a received signal, detecting operation of one or more devices within a time window, or the like. Moreover, the processor 20 may include image recognition technology to identify particular occupants or objects.
In some instances, the processor 20 may predict desirable settings and/or implement those settings. For example, based on presence detection, the processor 20 may adjust device settings to, e.g., conserve power when nobody is home or in a particular room or to accord with user preferences (e.g., general at-home preferences or user-specific preferences). As another example, based on the detection of a particular person, animal or object (e.g., a child, pet or lost object), the processor 20 may initiate an audio or visual indicator of where the person, animal or object is or may initiate an alarm or security feature if an unrecognized person is detected under certain conditions (e.g., at night or when lights are off).
In some instances, devices may interact with each other such that events detected by a first device influences actions of a second device using one or more common profiles between the devices. For example, a first device can detect that a user has pulled into a garage (e.g., by detecting motion in the garage, detecting a change in light in the garage or detecting opening of the garage door). The first device can transmit this information to a second device via the fabric network, such that the second device can, e.g., adjust a home temperature setting, a light setting, a music setting, and/or a security-alarm setting. As another example, a first device can detect a user approaching a front door (e.g., by detecting motion or sudden light pattern changes). The first device may cause a general audio or visual signal to be presented (e.g., such as sounding of a doorbell) or cause a location-specific audio or visual signal to be presented (e.g., to announce the visitor's presence within a room that a user is occupying).
With the foregoing in mind,
The depicted structure 32 includes multiple rooms 38, separated at least partly from each other via walls 40. The walls 40 can include interior walls or exterior walls. Each room 38 can further include a floor 42 and a ceiling 44. Devices can be mounted on, integrated with and/or supported by the wall 40, the floor 42, or the ceiling 44.
The home environment 30 may include multiple devices, including intelligent, multi-sensing, network-connected devices that may integrate seamlessly with each other and/or with cloud-based server systems to provide any of a variety of useful home objectives. One, more or each of the devices illustrated in the home environment 30 may include one or more sensors 12, a user interface 14, a power supply 16, a network interface 18, a processor 20 and the like.
Example devices 10 may include a network-connected thermostat 46 that may detect ambient climate characteristics (e.g., temperature and/or humidity) and control a heating, ventilation and air-conditioning (HVAC) system 48. Another example device 10 may include a hazard detection unit 50 that can detect the presence of a hazardous substance and/or a hazardous condition in the home environment 30 (e.g., smoke, fire, or carbon monoxide). Additionally, entryway interface devices 52, which can be termed a “smart doorbell”, can detect a person's approach to or departure from a location, control audible functionality, announce a person's approach or departure via audio or visual means, or control settings on a security system (e.g., to activate or deactivate the security system).
In certain embodiments, the device 10 may include a light switch 54 that may detect ambient lighting conditions, detect room-occupancy states, and control a power and/or dim state of one or more lights. In some instances, the light switches 54 may control a power state or speed of a fan, such as a ceiling fan.
Additionally, wall plug interfaces 56 may detect occupancy of a room or enclosure and control supply of power to one or more wall plugs (e.g., such that power is not supplied to the plug if nobody is at home). The device 10 within the home environment 30 may further include an appliance 58, such as refrigerators, stoves and/or ovens, televisions, washers, dryers, lights (inside and/or outside the structure 32), stereos, intercom systems, garage-door openers, floor fans, ceiling fans, whole-house fans, wall air conditioners, pool heaters 34, irrigation systems 36, security systems, and so forth. While descriptions of
In addition to containing processing and sensing capabilities, each of the example devices described above may be capable of data communications and information sharing with any other device, as well as to any cloud server or any other device that is network-connected anywhere in the world. In one embodiment, the devices 10 may send and receive communications via a fabric network discussed below. In one embodiment, fabric may enable the devices 10 to communicate with each other via one or more logical networks. As such, certain devices may serve as wireless repeaters and/or may function as bridges between devices, services, and/or logical networks in the home environment that may not be directly connected (i.e., one hop) to each other.
In one embodiment, a wireless router 60 may further communicate with the devices 10 in the home environment 30 via one or more logical networks (e.g., WiFi). The wireless router 60 may then communicate with the Internet 62 or other network such that each device 10 may communicate with a remote service or a cloud-computing system 64 through the Internet 62. The cloud-computing system 64 may be associated with a manufacturer, support entity or service provider associated with a particular device 10. As such, in one embodiment, a user may contact customer support using a device itself rather than using some other communication means such as a telephone or Internet-connected computer. Further, software updates can be automatically sent from the cloud-computing system 64 or devices in the home environment 30 to other devices in the fabric (e.g., when available, when purchased, when requested, or at routine intervals).
By virtue of network connectivity, one or more of the devices 10 may further allow a user to interact with the device even if the user is not proximate to the device. For example, a user may communicate with a device using a computer (e.g., a desktop computer, laptop computer, or tablet) or other portable electronic device (e.g., a smartphone) 66. A webpage or application may receive communications from the user and control the device 10 based on the received communications. Moreover, the webpage or application may present information about the device's operation to the user. For example, the user can view a current setpoint temperature for a device and adjust it using a computer that may be connected to the Internet 62. In this example, the thermostat 46 may receive the current setpoint temperature view request via the fabric network via one or more underlying logical networks.
In certain embodiments, the home environment 30 may also include a variety of non-communicating legacy appliances 68, such as old conventional washer/dryers, refrigerators, and the like which can be controlled, albeit coarsely (ON/OFF), by virtue of the wall plug interfaces 56. The home environment 30 may further include a variety of partially communicating legacy appliances 70, such as infra-red (IR) controlled wall air conditioners or other IR-controlled devices, which can be controlled by IR signals provided by the hazard detection units 50 or the light switches 54.
As mentioned above, each of the example devices 10 described above may form a portion of a fabric network. Generally, the fabric network may be part of an Open Systems Interconnection (OSI) model 90 as depicted in
Keeping this in mind, the physical layer 92 may provide hardware specifications for devices that may communicate with each other. As such, the physical layer 92 may establish how devices may connect to each other, assist in managing how communication resources may be shared between devices, and the like.
The data link layer 94 may specify how data may be transferred between devices. Generally, the data link layer 94 may provide a way in which data packets being transmitted may be encoded and decoded into bits as part of a transmission protocol.
The network layer 96 may specify how the data being transferred to a destination node is routed. The network layer 96 may also provide a security protocol that may maintain the integrity of the data being transferred. The efficient network layer discussed above corresponds to the network layer 96. In certain embodiments, the network layer 96 may be completely independent of the platform layer 100 and include any suitable IPv6 network type (e.g., WiFi, Ethernet, HomePlug, 802.15.4, etc).
The transport layer 98 may specify a transparent transfer of the data from a source node to a destination node. The transport layer 98 may also control how the transparent transfer of the data remains reliable. As such, the transport layer 98 may be used to verify that data packets intended to transfer to the destination node indeed reached the destination node. Example protocols that may be employed in the transport layer 98 may include Transmission Control Protocol (TCP) and User Datagram Protocol (UDP).
The platform layer 100 includes the fabric network and establishes connections between devices according to the protocol specified within the transport layer 98 and may be agnostic of the network type used in the network layer 96. The platform layer 100 may also translate the data packets into a form that the application layer 102 may use. The application layer 102 may support a software application that may directly interface with the user. As such, the application layer 102 may implement protocols defined by the software application. For example, the software application may provide serves such as file transfers, electronic mail, and the like.
II. Fabric Device Interconnection
As discussed above, a fabric may be implemented using one or more suitable communications protocols, such as IPv6 protocols. In fact, the fabric may be partially or completely agnostic to the underlying technologies (e.g., network types or communication protocols) used to implement the fabric. Within the one or more communications protocols, the fabric may be implemented using one or more network types used to communicatively couple electrical devices using wireless or wired connections. For example, certain embodiments of the fabric may include Ethernet, WiFi, 802.15.4, ZigBee®, ISA100.11a, WirelessHART, MiWi™ power-line networks, and/or other suitable network types. Within the fabric devices (e.g., nodes) can exchange packets of information with other devices (e.g., nodes) in the fabric, either directly or via intermediary nodes, such as intelligent thermostats, acting as IP routers. These nodes may include manufacturer devices (e.g., thermostats and smoke detectors) and/or customer devices (e.g., phones, tablets, computers, etc.). Additionally, some devices may be “always on” and continuously powered using electrical connections. Other devices may have partially reduced power usage (e.g., medium duty cycle) using a reduced/intermittent power connection, such as a thermostat or doorbell power connection. Finally, some devices may have a short duty cycle and run solely on battery power. In other words, in certain embodiments, the fabric may include heterogeneous devices that may be connected to one or more sub-networks according to connection type and/or desired power usage.
A. Single Network Topology
The network 1002 includes one or more nodes 1004, 1006, 1008, 1010, 1012, 1014, and 1016, referred to collectively as 1004-1016. Although the illustrated network 1002 includes seven nodes, certain embodiments of the network 1002 may include one or more nodes interconnected using the network 1002. Moreover, if the network 1002 is a WiFi network, each of the nodes 1004-1016 may be interconnected using the node 1016 (e.g., WiFi router) and/or paired with other nodes using WiFi Direct (i.e., WiFi P2P).
B. Star Network Topology
Although the illustrated fabric 1018 includes fourteen nodes, each referred to individually by reference numbers 1024-1052, respectively, it should be understood that the fabric 1018 may include any number of nodes. Communication within each network 1020, 1022, or 1024, may occur directly between devices and/or through an access point, such as node 1042 in a WiFi/Ethernet network. Communications between periphery network 1022 and 1024 passes through the hub network 1020 using inter-network routing nodes. For example, in the illustrated embodiment, nodes 1034 and 1036 are be connected to the periphery network 1022 using a first network connection type (e.g., 802.15.4) and to the hub network 1020 using a second network connection type (e.g., WiFi) while the node 1044 is connected to the hub network 1020 using the second network connection type and to the periphery network 1024 using a third network connection type (e.g., power line). For example, a message sent from node 1026 to node 1052 may pass through nodes 1028, 1030, 1032, 1036, 1042, 1044, 1048, and 1050 in transit to node 1052.
C. Overlapping Networks Topology
D. Fabric Network Connection to Services
In addition to communications between devices within the home, a fabric (e.g., fabric 1000) may include services that may be located physically near other devices in the fabric or physically remote from such devices. The fabric connects to these services through one or more service end points.
In certain embodiments, the service 1074 may also connect to a consumer device 1088, such as a phone, tablet, and/or computer. The consumer device 1088 may be used to connect to the service 1074 via a fabric, such as fabric 1076, an Internet connection, and/or some other suitable connection method. The consumer device 1088 may be used to access data from one or more end points (e.g., electronic devices) in a fabric either directly through the fabric or via the service 1074. In other words, using the service 1074, the consumer device 1088 may be used to access/manage devices in a fabric remotely from the fabric.
E. Communication Between Devices in a Fabric
As discussed above, each electronic device or node may communicate with any other node in the fabric, either directly or indirectly depending upon fabric topology and network connection types. Additionally, some devices (e.g., remote devices) may communicate through a service to communicate with other devices in the fabric.
i. Unique Local Address
As discussed above, data transmitted within a fabric received by a node may be redirected or passed through the node to another node depending on the desired target for the communication. In some embodiments, the transmission of the data may be intended to be broadcast to all devices. In such embodiments, the data may be retransmitted without further processing to determine whether the data should be passed along to another node. However, some data may be directed to a specific endpoint. To enable addressed messages to be transmitted to desired endpoints, nodes may be assigned identification information.
Each node may be assigned a set of link-local addresses (LLA), one assigned to each network interface. These LLAs may be used to communicate with other nodes on the same network. Additionally, the LLAs may be used for various communication procedures, such as IPv6 Neighbor Discovery Protocol. In addition to LLAs, each node is assigned a unique local address (ULA).
The fabric ID 1103 is a unique 64-bit identifier used to identify a fabric. The fabric ID 1103 may be generated at creation of the associated fabric using a pseudo-random algorithm. For example, the pseudo-random algorithm may 1) obtain the current time of day in 64-bit NTP format, 2) obtain the interface ID 1104 for the device, 3) concatenate the time of day with the interface ID 1104 to create a key, 4) compute and SHA-1 digest on the key resulting in 160 bits, 5) use the least significant 40 bits as the global ID 1100, and 6) concatenate the ULA and set the least significant bit to 1 to create the fabric ID 1103. In certain embodiments, once the fabric ID 1103 is created with the fabric, the fabric ID 1103 remains until the fabric is dissolved.
The global ID 1100 identifies the fabric to which the node belongs. The subnet ID 1102 identifies logical networks within the fabric. The subnet ID 1102 may be assigned monotonically starting at one with the addition of each new logical network to the fabric. For example, a WiFi network may be identified with a hex value of 0x01, and a later connected 802.15.4 network may be identified with a hex value of 0x02 continuing on incrementally upon the connection of each new network to the fabric.
Finally, the ULA 1098 includes an interface ID 1104 that includes 64 bits. The interface ID 1104 may be assigned using a globally-unique 64-bit identifier according to the IEEE EUI-64 standard. For example, devices with IEEE 802 network interfaces may derive the interface ID 1104 using a burned-in MAC address for the devices “primary interface.” In some embodiments, the designation of which interface is the primary interface may be determined arbitrarily. In other embodiments, an interface type (e.g., WiFi) may be deemed the primary interface, when present. If the MAC address for the primary interface of a device is 48 bits rather than 64-bit, the 48-bit MAC address may be converted to a EUI-64 value via encapsulation (e.g., organizationally unique identifier encapsulating). In consumer devices (e.g., phones or computers), the interface ID 1104 may be assigned by the consumer devices' local operating systems.
ii. Routing Transmissions Between Logical Networks
As discussed above in relation to a star network topology, inter-network routing may occur in communication between two devices across logical networks. In some embodiments, inter-network routing is based on the subnet ID 1102. Each inter-networking node (e.g., node 1034 of
Additionally, inter-network routing nodes may regularly transmit Neighbor Discovery Protocol (NDP) router advertisement messages on the hub network to alert consumer devices to the existence of the hub network and allow them to acquire the subnet prefix. The router advertisements may include one or more route information options to assist in routing information in the fabric. For example, these route information options may inform consumer devices of the existence of the periphery networks and how to route packets the periphery networks.
In addition to, or in place of route information options, routing nodes may act as proxies to provide a connection between consumer devices and devices in periphery networks, such as the process 1105 as illustrated in
iii. Consumer Devices Connecting to a Fabric
To join a fabric, a consumer device may discover an address of a node already in the fabric that the consumer device wants to join. Additionally, if the consumer device has been disconnected from a fabric for an extended period of time may need to rediscover nodes on the network if the fabric topology/layout has changed. To aid in discovery/rediscovery, fabric devices on the hub network may publish Domain Name System-Service Discovery (DNS-SD) records via mDNS that advertise the presence of the fabric and provide addresses to the consumer device
III. Data Transmitted in the Fabric
After creation of a fabric and address creation for the nodes, data may be transmitted through the fabric. Data passed through the fabric may be arranged in a format common to all messages and/or common to specific types of conversations in the fabric. In some embodiments, the message format may enable one-to-one mapping to JavaScript Object Notation (JSON) using a TLV serialization format discussed below. Additionally, although the following data frames are described as including specific sizes, it should be noted that lengths of the data fields in the data frames may be varied to other suitable bit-lengths.
It should be understood that each of the following data frames, profiles, and/or formats discussed below may be stored in memory (e.g., memory of the device 10) prior to and/or after transmission of a message. In other words, although the data frame, profiles, and formats may be generally discussed as transmissions of data, they may also be physically stored (e.g., in a buffer) before, during, and/or after transmission of the data frame, profiles, and/or formats. Moreover, the following data frames, profiles, schemas, and/or formats may be stored on a non-transitory, computer-readable medium that allows an electronic device to access the data frames, profiles, schemas, and/or formats. For example, instructions for formatting the data frames, profiles, schemas, and/or formats may be stored in any suitable computer-readable medium, such as in memory for the device 10, memory of another device, a portable memory device (e.g., compact disc, flash drive, etc.), or other suitable physical device suitable for storing the data frames, profiles, schemas, and/or formats.
A. Security
Along with data intended to be transferred, the fabric may transfer the data with additional security measures such as encryption, message integrity checks, and digital signatures. In some embodiments, a level of security supported for a device may vary according to physical security of the device and/or capabilities of the device. In certain embodiments, messages sent between nodes in the fabric may be encrypted using the Advanced Encryption Standard (AES) block cipher operating in counter mode (AES-CTR) with a 128-bit key. As discussed below, each message contains a 32-bit message id. The message id may be combined with a sending nodes id to form a nonce for the AES-CTR algorithm. The 32-bit counter enables 4 billion messages to be encrypted and sent by each node before a new key is negotiated.
In some embodiments, the fabric may insure message integrity using a message authentication code, such as HMAC-SHA-1, that may be included in each encrypted message. In some embodiments, the message authentication code may be generated using a 160-bit message integrity key that is paired one-to-one with the encryption key. Additionally, each node may check the message id of incoming messages against a list of recently received ids maintained on a node-by-node basis to block replay of the messages.
B. Tag Length Value (TLV) Formatting
To reduce power consumption, it is desirable to send at least a portion of the data sent over the fabric that compactly while enabling the data containers to flexibly represents data that accommodates skipping data that is not recognized or understood by skipping to the next location of data that is understood within a serialization of the data. In certain embodiments, tag-length-value (TLV) formatting may be used to compactly and flexibly encode/decode data. By storing at least a portion of the transmitted data in TLV, the data may be compactly and flexibly stored/sent along with low encode/decode and memory overhead, as discussed below in reference to Table 7. In certain embodiments, TLV may be used for some data as flexible, extensible data, but other portions of data that is not extensible may be stored and sent in an understood standard protocol data unit (PDU).
Data formatted in a TLV format may be encoded as TLV elements of various types, such as primitive types and container types. Primitive types include data values in certain formats, such as integers or strings. For example, the TLV format may encode: 1, 2, 3, 4, or 8 byte signed/unsigned integers, UTF-8 strings, byte strings, single/double-precision floating numbers (e.g., IEEE 754-1985 format), boolean, null, and other suitable data format types. Container types include collections of elements that are then sub-classified as container or primitive types. Container types may be classified into various categories, such as dictionaries, arrays, paths or other suitable types for grouping TLV elements, known as members. A dictionary is a collection of members each having distinct definitions and unique tags within the dictionary. An array is an ordered collection of members with implied definitions or no distinct definitions. A path is an ordered collection of members that described how to traverse a tree of TLV elements.
As illustrated in
In embodiments having the control byte, the control byte may be sub-divided into an element type field and a tag control field. In some embodiments, the element type field includes 5 lower bits of the control byte and the tag control field occupies the upper 3 bits. The element type field indicates the TLV element's type as well as the how the length field 1124 and value field 1126 are encoded. In certain embodiments, the element type field also encodes Boolean values and/or null values for the TLV. For example, an embodiment of an enumeration of element type field is provided in Table 1 below.
The tag control field indicates a form of the tag in the tag field 1122 assigned to the TLV element (including a zero-length tag). Examples, of tag control field values are provided in Table 2 below.
In other words, in embodiments having a control byte, the control byte may indicate a length of the tag.
In certain embodiments, the tag field 1122 may include zero to eight bytes, such as eight, sixteen, thirty two, or sixty four bits. In some embodiments, the tag of the tag field may be classified as profile-specific tags or context-specific tags. Profile-specific tags identify elements globally using a vendor Id, a profile Id, and/or tag number as discussed below. Context-specific tags identify TLV elements within a context of a containing dictionary element and may include a single-byte tag number. Since context-specific tags are defined in context of their containers, a single context-specific tag may have different interpretations when included in different containers. In some embodiments, the context may also be derived from nested containers.
In embodiments having the control byte, the tag length is encoded in the tag control field and the tag field 1122 includes a possible three fields: a vendor Id field, a profile Id field, and a tag number field. In the fully-qualified form, the encoded tag field 1122 includes all three fields with the tag number field including 16 or 32 bits determined by the tag control field. In the implicit form, the tag includes only the tag number, and the vendor Id and profile number are inferred from the protocol context of the TLV element. The core profile form includes profile-specific tags, as discussed above. Context-specific tags are encoded as a single byte conveying the tag number. Anonymous elements have zero-length tag fields 1122.
In some embodiments without a control byte, two bits may indicate a length of the tag field 1122, two bits may indicate a length of the length field 1124, and four bits may indicate a type of information stored in the value field 1126. An example of possible encoding for the upper 8 bits for the tag field is illustrated below in Table 3.
As illustrated in Table 3, the upper 8 bits of the tag field 1122 may be used to encode information about the tag field 1122, length field 1124, and the value field 1126, such that the tag field 112 may be used to determine length for the tag field 122 and the length fields 1124. Remaining bits in the tag field 1122 may be made available for user-allocated and/or user-assigned tag values.
The length field 1124 may include eight, sixteen, thirty two, or sixty four bits as indicated by the tag field 1122 as illustrated in Table 3 or the element field as illustrated in Table 2. Moreover, the length field 1124 may include an unsigned integer that represents a length of the encoded in the value field 1126. In some embodiments, the length may be selected by a device sending the TLV element. The value field 1126 includes the payload data to be decoded, but interpretation of the value field 1126 may depend upon the tag length fields, and/or control byte. For example, a TLV packet without a control byte including an 8 bit tag is illustrated in Table 4 below for illustration.
As illustrated in Table 4, the first line indicates that the tag field 1122 and the length field 1124 each have a length of 8 bits. Additionally, the tag field 1122 indicates that the tag type is for the first line is a container (e.g., the TLV packet). The tag field 1124 for lines two through six indicate that each entry in the TLV packet has a tag field 1122 and length field 1124 consisting of 8 bits each. Additionally, the tag field 1124 indicates that each entry in the TLV packet has a value field 1126 that includes a 32-bit floating point. Each entry in the value field 1126 corresponds to a floating number that may be decoded using the corresponding tag field 1122 and length field 1124 information. As illustrated in this example, each entry in the value field 1126 corresponds to a temperature in Fahrenheit. As can be understood, by storing data in a TLV packet as described above, data may be transferred compactly while remaining flexible for varying lengths and information as may be used by different devices in the fabric. Moreover, in some embodiments, multi-byte integer fields may be transmitted in little-endian order or big-endian order.
By transmitting TLV packets in using an order protocol (e.g., little-endian) that may be used by sending/receiving device formats (e.g., JSON), data transferred between nodes may be transmitted in the order protocol used by at least one of the nodes (e.g., little endian). For example, if one or more nodes include ARM or ix86 processors, transmissions between the nodes may be transmitted using little-endian byte ordering to reduce the use of byte reordering. By reducing the inclusion of byte reordering, the TLV format enable devices to communicate using less power than a transmission that uses byte reordering on both ends of the transmission. Furthermore, TLV formatting may be specified to provide a one-to-one translation between other data storage techniques, such as JSON+ Extensible Markup Language (XML). As an example, the TLV format may be used to represent the following XML Property List:
As an example, the above property list may be represented in tags of the above described TLV format (without a control byte) according to Table 5 below.
Similarly, Table 6 illustrates an example of literal tag, length, and value representations for the example XML Property List.
The TLV format enables reference of properties that may also be enumerated with WL, but does so with a smaller storage size. For example, Table 7 illustrates a comparison of data sizes of the XML Property List, a corresponding binary property list, and the TLV format.
By reducing the amount of data used to transfer data, the TLV format enables the fabric 1000 transfer data to and/or from devices having short duty cycles due to limited power (e.g., battery supplied devices). In other words, the TLV format allows flexibility of transmission while increasing compactness of the data to be transmitted.
C. General Message Protocol
In addition to sending particular entries of varying sizes, data may be transmitted within the fabric using a general message protocol that may incorporate TLV formatting. An embodiment of a general message protocol (GMP) 1128 is illustrated in
i. Packet Length
In some embodiments, the GMP 1128 may include a Packet Length field 1130. In some embodiments, the Packet Length field 1130 includes 2 bytes. A value in the Packet Length field 1130 corresponds to an unsigned integer indicating an overall length of the message in bytes, excluding the Packet Length field 1130 itself. The Packet Length field 1130 may be present when the GMP 1128 is transmitted over a TCP connection, but when the GMP 1128 is transmitted over a UDP connection, the message length may be equal to the payload length of the underlying UDP packet obviating the Packet Length field 1130.
ii. Message Header
The GMP 1128 may also include a Message Header 1132 regardless of whether the GMP 1128 is transmitted using TCP or UDP connections. In some embodiments, the Message Header 1132 includes two bytes of data arranged in the format illustrated in
The Message Header 1132 also includes an Encryption Type field 1162. The Encryption Type field 1162 includes four bits that specify which type of encryption/integrity checking applied to the message, if any. For example, 0x0 may indicate that no encryption or message integrity checking is included, but a decimal 0x1 may indicate that AES-128-CTR encryption with HMAC-SHA-1 message integrity checking is included.
Finally, the Message Header 1132 further includes a Signature Type field 1164. The Signature Type field 1164 includes four bits that specify which type of digital signature is applied to the message, if any. For example, 0x0 may indicate that no digital signature is included in the message, but 0x1 may indicate that the Elliptical Curve Digital Signature Algorithm (ECDSA) with Prime256v1 elliptical curve parameters is included in the message.
iii. Message Id
Returning to
iv. Source Node Id
In certain embodiments, the GMP 1128 may also include a Source Node Id field 1136 that includes eight bytes. As discussed above, the Source Node Id field 1136 may be present in a message when the single-bit S Flag 1158 in the Message Header 1132 is set to 1. In some embodiments, the Source Node Id field 1136 may contain the Interface ID 1104 of the ULA 1098 or the entire ULA 1098. In some embodiments, the bytes of the Source Node Id field 1136 are transmitted in an ascending index-value order (e.g., EUI[0] then EUI[1] then EUI[2] then EUI[3], etc.).
v. Destination Node Id
The GMP 1128 may include a Destination Node Id field 1138 that includes eight bytes. The Destination Node Id field 1138 is similar to the Source Node Id field 1136, but the Destination Node Id field 1138 corresponds to a destination node for the message. The Destination Node Id field 1138 may be present in a message when the single-bit D Flag 1160 in the Message Header 1132 is set to 1. Also similar to the Source Node Id field 1136, in some embodiments, bytes of the Destination Node Id field 1138 may be transmitted in an ascending index-value order (e.g., EUI[0] then EUI[1] then EUI[2] then EUI[3], etc.).
vi. Key Id
In some embodiments, the GMP 1128 may include a Key Id field 1140. In certain embodiments, the Key Id field 1140 includes two bytes. The Key Id field 1140 includes an unsigned integer value that identifies the encryption/message integrity keys used to encrypt the message. The presence of the Key Id field 1140 may be determined by the value of Encryption Type field 1162 of the Message Header 1132. For example, in some embodiments, when the value for the Encryption Type field 1162 of the Message Header 1132 is 0x0, the Key Id field 1140 may be omitted from the message.
An embodiment of the Key Id field 1140 is presented in
The Key Id field 1140 also includes a Key Number field 1168 that includes twelve bits that correspond to an unsigned integer value that identifies a particular key used to encrypt the message out of a set of available keys, either shared or fabric keys.
vii. Payload Length
In some embodiments, the GMP 1128 may include a Payload Length field 1142. The Payload Length field 1142, when present, may include two bytes. The Payload Length field 1142 corresponds to an unsigned integer value that indicates a size in bytes of the Application Payload field. The Payload Length field 1142 may be present when the message is encrypted using an algorithm that uses message padding, as described below in relation to the Padding field.
viii. Initialization Vector
In some embodiments, the GMP 1128 may also include an Initialization Vector (IV) field 1144. The IV field 1144, when present, includes a variable number of bytes of data. The IV field 1144 contains cryptographic IV values used to encrypt the message. The IV field 1144 may be used when the message is encrypted with an algorithm that uses an IV. The length of the IV field 1144 may be derived by the type of encryption used to encrypt the message.
ix. Application Payload
The GMP 1128 includes an Application Payload field 1146. The Application Payload field 1146 includes a variable number of bytes. The Application Payload field 1146 includes application data conveyed in the message. The length of the Application Payload field 1146 may be determined from the Payload Length field 1142, when present. If the Payload Length field 1142 is not present, the length of the Application Payload field 1146 may be determined by subtracting the length of all other fields from the overall length of the message and/or data values included within the Application Payload 1146 (e.g., TLV).
An embodiment of the Application Payload field 1146 is illustrated in
In addition, the Application Payload field 1146 includes a Profile Id field 1176. The Profile Id 1176 indicates a “theme of discussion” used to indicate what type of communication occurs in the message. The Profile Id 1176 may correspond to one or more profiles that a device may be capable of communicating. For example, the Profile Id 1176 may indicate that the message relates to a core profile, a software update profile, a status update profile, a data management profile, a climate and comfort profile, a security profile, a safety profile, and/or other suitable profile types. Each device on the fabric may include a list of profiles which are relevant to the device and in which the device is capable of “participating in the discussion.” For example, many devices in a fabric may include the core profile, the software update profile, the status update profile, and the data management profile, but only some devices would include the climate and comfort profile. The APVersion field 1170, Message Type field 1172, the Exchange Id field, the Profile Id field 1176, and the Profile-Specific Header field 1176, if present, may be referred to in combination as the “Application Header.”
In some embodiments, an indication of the Profile Id via the Profile Id field 1176 may provide sufficient information to provide a schema for data transmitted for the profile. However, in some embodiments, additional information may be used to determine further guidance for decoding the Application Payload field 1146. In such embodiments, the Application Payload field 1146 may include a Profile-Specific Header field 1178. Some profiles may not use the Profile-Specific Header field 1178 thereby enabling the Application Payload field 1146 to omit the Profile-Specific Header field 1178. Upon determination of a schema from the Profile Id field 1176 and/or the Profile-Specific Header field 1178, data may be encoded/decoded in the Application Payload sub-field 1180. The Application Payload sub-field 1180 includes the core application data to be transmitted between devices and/or services to be stored, rebroadcast, and/or acted upon by the receiving device/service.
x. Message Integrity Check
Returning to
xi. Padding
The GMP 1128 may also include a Padding field 1150. The Padding field 1150, when present, includes a sequence of bytes representing a cryptographic padding added to the message to make the encrypted portion of the message evenly divisible by the encryption block size. The presence of the Padding field 1150 may be determined by whether the type of encryption algorithm (e.g., block ciphers in cipher-block chaining mode) indicated by the Encryption Type field 1162 in the Message Header 1132 uses cryptographic padding.
xii. Encryption
The Application Payload field 1146, the MIC field 1148, and the Padding field 1150 together form an Encryption block 1152. The Encryption block 1152 includes the portions of the message that are encrypted when the Encryption Type field 1162 in the Message Header 1132 is any value other than 0x0.
xiii. Message Signature
The GMP 1128 may also include a Message Signature field 1154. The Message Signature field 1154, when present, includes a sequence of bytes of variable length that contains a cryptographic signature of the message. The length and the contents of the Message Signature field may be determined according to the type of signature algorithm in use and indicated by the Signature Type field 1164 of the Message Header 1132. For example, if ECDSA using the Prime256v1 elliptical curve parameters is the algorithm in use, the Message Signature field 1154 may include two thirty-two bit integers encoded in little-endian order.
IV. Profiles and Protocols
As discussed above, one or more schemas of information may be selected upon desired general discussion type for the message. A profile may consist of one or more schemas. For example, one set of schemas of information may be used to encode/decode data in the Application Payload sub-field 1180 when one profile is indicated in the Profile Id field 1176 of the Application Payload 1146. However, a different set of schemas may be used to encode/decode data in the Application Payload sub-field 1180 when a different profile is indicated in the Profile Id field 1176 of the Application Payload 1146.
The profiles library 300 may also include a device control profile 320, a network provisioning profile 322, a fabric provisioning profile 324, and a service provisioning profile 326. The device control profile 320 allows one device to request that another device exercise a specified device control (e.g., arm failsafe, etc.) capability. The network provisioning profile 322 enables a device to be added to a new logical network (e.g., WiFi or 802.15.4). The fabric provisioning profile 324 allows the devices to join a pre-existing fabric or create a new fabric. The service provisioning profile 326 enables the devices to be paired to a service.
The profiles library 300 may also include a strings profile 328, a device description profile 330, a device profile 332, device power extended profile 334, a device power profile 336, a device connectivity extended profile 338, a device connectivity profile 340, a service directory profile 342, a data management profile 344, an echo profile 346, a security profile 348, and a core profile 350. The device description profile 330 may be used by a device to identify one or more other devices. The service directory profile 342 enables a device to communicate with a service. The data management profile 344 enables devices to view and/or track data stored in another device. The echo profile 346 enables a device to determine whether the device is connected to a target device and the latency in the connection. The security profile 348 enables the devices to communicate securely.
The core profile 350 includes a status reporting profile 352 that enables devices to report successes and failures of requested actions. Additionally, in certain embodiments, each device may include a set of methods used to process profiles. For example, a core protocol may include the following profiles: GetProfiles, GetSchema, GetSchemas, GetProperty, GetProperties, SetProperty, SetProperties, RemoveProperty, RemoveProperties, RequestEcho, NotifyPropertyChanged, and/or NotifyPropertiesChanged. The Get Profiles method may return an array of profiles supported by a queried node. The GetSchema and GetSchemas methods may respectively return one or all schemas for a specific profile. GetProperty and GetProperties may respectively return a value or all value pairs for a profile schema. SetProperty and SetProperties may respectively set single or multiple values for a profile schema. RemoveProperty and RemoveProperties may respectively attempt to remove a single or multiple values from a profile schema. RequestEcho may send an arbitrary data payload to a specified node which the node returns unmodified. NotifyPropertyChange and NotifyPropertiesChanged may respectively issue a notification if a single/multiple value pairs have changed for a profile schema.
To aid in understanding profiles and schemas, a non-exclusive list of profiles and schemas are provided below for illustrative purposes.
A. Status Reporting
A status reporting schema is presented as the status reporting frame 1182 in
i. Profile Field
In some embodiments, the profile field 1184 includes four bytes of data that defines the profile under which the information in the present status report is to be interpreted. An embodiment of the profile field 1184 is illustrated in
ii. Status Code
In certain embodiments, the status code field 1186 includes sixteen bits that encode the status that is being reported. The values in the status code field 1186 are interpreted in relation to values encoded in the vendor Id sub-field 1192 and the profile Id sub-field 1194 provided in the profile field 1184. Additionally, in some embodiments, the status code space may be divided into four groups, as indicated in Table 8 below.
Although Table 8 identifies general status code ranges that may be used separately assigned and used for each specific profile Id, in some embodiments, some status codes may be common to each of the profiles. For example, these profiles may be identified using a common profile (e.g., core profile) identifier, such as 0x00000000.
iii. Next Status
In some embodiments, the next status code field 1188 includes eight bits. The next status code field 1188 indicates whether there is following status information after the currently reported status. If following status information is to be included, the next status code field 1188 indicates what type of status information is to be included. In some embodiments, the next status code field 1188 may always be included, thereby potentially increasing the size of the message. However, by providing an opportunity to chain status information together, the potential for overall reduction of data sent may be reduced. If the next status field 1186 is 0x00, no following status information field 1190 is included. However, non-zero values may indicate that data may be included and indicate the form in which the data is included (e.g., in a TLV packet).
iv. Additional Status Info
When the next status code field 1188 is non-zero, the additional status info field 1190 is included in the message. If present, the status item field may contain status in a form that may be determined by the value of the preceding status type field (e.g., TLV format)
B. Software Update
The software update profile or protocol is a set of schemas and a client/server protocol that enables clients to be made aware of or seek information about the presence of software that they may download and install. Using the software update protocol, a software image may be provided to the profile client in a format known to the client. The subsequent processing of the software image may be generic, device-specific, or vendor-specific and determined by the software update protocol and the devices.
i. General Application Headers for the Application Payload
In order to be recognized and handled properly, software update profile frames may be identified within the Application Payload field 1146 of the GMP 1128. In some embodiments, all software update profile frames may use a common Profile Id 1176, such as 0x0000000C. Additionally, software update profile frames may include a Message Type field 1172 that indicates additional information and may chosen according to Table 9 below and the type of message being sent.
Additionally, as described below, the software update sequence may be initiated by a server sending the update as an image announce or a client receiving the update as an image query. In either embodiment, an Exchange Id 1174 from the initiating event is used for all messages used in relation to the software update.
ii. Protocol Sequence
1. Service Discovery
In some embodiments, the protocol sequence 1196 begins with a software update profile server announcing a presence of the update. However, in other embodiments, such as the illustrated embodiment, the protocol sequence 1196 begins with a service discovery 1202, as discussed above.
2. Image Announce
In some embodiments, an image announce message 1204 may be multicast or unicast by the software update server 1200. The image announce message 1204 informs devices in the fabric that the server 1200 has a software update to offer. If the update is applicable to the client 1198, upon receipt of the image announce message 1204, the software update client 1198 responds with an image query message 1206. In certain embodiments, the image announce message 1204 may not be included in the protocol sequence 1196. Instead, in such embodiments, the software update client 1198 may use a polling schedule to determine when to send the image query message 1206.
3. Image Query
In certain embodiments, the image query message 1206 may be unicast from the software update client 1198 either in response to an image announce message 1204 or according to a polling schedule, as discussed above. The image query message 1206 includes information from the client 1198 about itself. An embodiment of a frame of the image query message 1206 is illustrated in
a. Frame Control
The frame control field 1218 includes 1 byte and indicates various information about the image query message 1204. An example of the frame control field 128 is illustrated in
b. Product Specification
The product specification field 1220 is a six byte field. An embodiment of the product specification field 1220 is illustrated in
c. Vendor Specific Data
The vendor specific data field 1222, when present in the image query message 1206, has a length of a variable number of bytes. The presence of the vendor specific data field 1222 may be determined from the vendor specific flag 1232 of the frame control field 1218. When present, the vendor specific data field 1222 encodes vendor specific information about the software update client 1198 in a TLV format, as described above.
d. Version Specification
An embodiment of the version specification field 1224 is illustrated in
e. Locale Specification
In certain embodiments, the locale specification field 1226 may be included in the image query message 1206 when the locale specification flag 1234 of the frame control 1218 is 1. An embodiment of the locale specification field 1226 is illustrated in
f. Integrity Types Supported
An embodiment of the integrity types field 1228 is illustrated in
The integrity type list field 1252 may contain at least one element from Table 10 or other additional values not included.
g. Update Schemes Supported
An embodiment of the schemes supported field 1230 is illustrated in
Upon receiving the image query message 1206, the software update server 1200 uses the transmitted information to determine whether the software update server 1200 has an update for the software update client 1198 and how best to deliver the update to the software update client 1198.
4. Image Query Response
Returning to
An embodiment of a frame of the image query response 1208 is illustrated in
a. Query Status
The query status field 1258 includes a variable number of bytes and contains status reporting formatted data, as discussed above in reference to status reporting. For example, the query status field 1258 may include image query response status codes, such as those illustrated below in Table 12.
b. URI
The URI field 1260 includes a variable number of bytes. The presence of the URI field 1260 may be determined by the query status field 1258. If the query status field 1258 indicates that an update is available, the URI field 1260 may be included. An embodiment of the URI field 1260 is illustrated in
c. Integrity Specification
The integrity specification field 1262 may variable in length and present when the query status field 1258 indicates that an update is available from the software update server 1198 to the software update client 1198. An embodiment of the integrity specification field 1262 is illustrated in
d. Update Scheme
The update scheme field 1264 includes eight bits and is present when the query status field 1258 indicates that an update is available from the software update server 1198 to the software update client 1198. If present, the update scheme field 1264 indicates a scheme attribute for the software update image being presented to the software update server 1198.
e. Update Options
The update options field 1266 includes eight bits and is present when the query status field 1258 indicates that an update is available from the software update server 1198 to the software update client 1198. The update options field 1266 may be sub-divided as illustrated in
The update condition field 1278 includes three bits that may be used to determine conditional factors to determine when or if to update. For example, values in the update condition field 1278 may be decoded using the Table 14 below.
The report status flag 1280 is a single bit that indicates whether the software update client 1198 should respond with a download notify message 1210. If the report status flag 1280 is set to 1 the software update server 1198 is requesting a download notify message 1210 to be sent after the software update is downloaded by the software update client 1200.
If the image query response 1208 indicates that an update is available. The software update client 1198 downloads 1210 the update using the information included in the image query response 1208 at a time indicated in the image query response 1208.
5. Download Notify
After the update download 1210 is successfully completed or failed and the report status flag 1280 value is 1, the software update client 1198 may respond with the download notify message 1212. The download notify message 1210 may be formatted in accordance with the status reporting format discussed above. An example of status codes used in the download notify message 1212 is illustrated in Table 15 below.
In addition to the status reporting described above, the download notify message 1208 may include additional status information that may be relevant to the download and/or failure to download.
6. Notify Response
The software update server 1200 may respond with a notify response message 1214 in response to the download notify message 1212 or an update notify message 1216. The notify response message 1214 may include the status reporting format, as described above. For example, the notify response message 1214 may include status codes as enumerated in Table 16 below.
In addition to the status reporting described above, the notify response message 1214 may include additional status information that may be relevant to the download, update, and/or failure to download/update the software update.
7. Update Notify
After the update is successfully completed or failed and the report status flag 1280 value is 1, the software update client 1198 may respond with the update notify message 1216. The update notify message 1216 may use the status reporting format described above. For example, the update notify message 1216 may include status codes as enumerated in Table 17 below.
In addition to the status reporting described above, the update notify message 1216 may include additional status information that may be relevant to the update and/or failure to update.
C. Bulk Transfer
In some embodiments, it may be desirable to transfer bulk data files (e.g., sensor data, logs, or update images) between nodes/services in the fabric 1000. To enable transfer of bulk data, a separate profile or protocol may be incorporated into one or more profiles and made available to the nodes/services in the nodes. The bulk data transfer protocol may model data files as collections of data with metadata attachments. In certain embodiments, the data may be opaque, but the metadata may be used to determine whether to proceed with a requested file transfer.
Devices participating in a bulk transfer may be generally divided according to the bulk transfer communication and event creation. As illustrated in
Bulk data transfer may occur using either synchronous or asynchronous modes. The mode in which the data is transferred may be determined using a variety of factors, such as the underlying protocol (e.g., UDP or TCP) on which the bulk data is sent. In connectionless protocols (e.g., UDP), bulk data may be transferred using a synchronous mode that allows one of the nodes/services (“the driver”) to control a rate at which the transfer proceeds. In certain embodiments, after each message in a synchronous mode bulk data transfer, an acknowledgment may be sent before sending the next message in the bulk data transfer. The driver may be the sender 1402 or the receiver 1406. In some embodiments, the driver may toggle between an online state and an offline mode while sending messages to advance the transfer when in the online state. In bulk data transfers using connection-oriented protocols (e.g., TCP), bulk data may be transferred using an asynchronous mode that does not use an acknowledgment before sending successive messages or a single driver.
Regardless of whether the bulk data transfer is performed using a synchronous or asynchronous mode, a type of message may be determined using a Message Type 1172 in the Application Payload 1146 according the Profile Id 1176 in the Application Payload. Table 18 includes an example of message types that may be used in relation to a bulk data transfer profile value in the Profile Id 1176.
i. SendInit
An embodiment of a SendInit message 1420 is illustrated in
The transfer control field 1422 includes a byte of data illustrated in
The range control field 1424 includes a byte of data such as the range control field 1424 illustrated in
Returning to
The start offset field 1430, when present, has a length indicated by the BigExtent flag 1470. The value of the start offset field 1430 indicates a location within the file to be transferred from which the sender 1402 may start the transfer, essentially allowing large file transfers to be segmented into multiple bulk transfer sessions.
The length field 1432, when present, indicates a length of the file to be transferred if the definite length field 1474 indicates that the file has a definite length. In some embodiments, if the receiver 1402 receives a final block before the length is achieved, the receiver may consider the transfer failed and report an error as discussed below.
The file designator field 1434 is a variable length identifier chosen by the sender 1402 to identify the file to be sent. In some embodiments, the sender 1402 and the receiver 1406 may negotiate the identifier for the file prior to transmittal. In other embodiments, the receiver 1406 may use metadata along with the file designator field 1434 to determine whether to accept the transfer and how to handle the data. The length of the file designator field 1434 may be determined from the file designator length field 1426. In some embodiments, the SendInit message 1420 may also include a metadata field 1480 of a variable length encoded in a TLV format. The metadata field 1480 enables the initiator to send additional information, such as application-specific information about the file to be transferred. In some embodiments, the metadata field 1480 may be used to avoid negotiating the file designator field 1434 prior to the bulk data transfer.
ii. SendAccept
A send accept message is transmitted from the responder to indicate the transfer mode chosen for the transfer. An embodiment of a SendAccept message 1500 is presented in
iii. SendReject
When the receiver 1206 rejects a transfer after a SendInit message, the receiver 1206 may send a SendReject message that indicates that one or more issues exist regarding the bulk data transfer between the sender 1202 and the receiver 1206. The send reject message may be formatted according to the status reporting format described above and illustrated in
In some embodiments, the send reject message 1520 may include a next status field 1524. The next status field 1524, when present, may be formatted and encoded as discussed above in regard to the next status field 1188 of a status report frame. In certain embodiments, the send reject message 1520 may include an additional information field 1526. The additional information field 1526, when present, may store information about an additional status and may be encoded using the TLV format discussed above.
iv. ReceiveInit
A ReceiveInit message may be transmitted by the receiver 1206 as the initiator. The ReceiveInit message may be formatted and encoded similar to the SendInit message 1480 illustrated in
v. ReceiveAccept
When the sender 1202 receives a ReceiveInit message, the sender 1202 may respond with a ReceiveAccept message. The ReceiveAccept message may be formatted and encoded as the ReceiveAccept message 1540 illustrated in
vi. ReceiveReject
If the sender 1202 encounters an issue with transferring the file to the receiver 1206, the sender 1202 may send a ReceiveReject message formatted and encoded similar to a SendReject message 48 using the status reporting format, both discussed above. However, the status code field 1522 may be encoded/decoded using values similar to those enumerated as indicated in the Table 20 below.
vii. BlockQuery
A BlockQuery message may be sent by a driving receiver 1202 in a synchronous mode bulk data transfer to request the next block of data. A BlockQuery impliedly acknowledges receipt of a previous block of data if not explicit Acknowledgement has been sent. In embodiments using asynchronous transfers, a BlockQuery message may be omitted from the transmission process.
viii. Block
Blocks of data transmitted in a bulk data transfer may include any length greater than 0 and less than a max block size agreed upon by the sender 1202 and the receiver 1206.
ix. BlockEOF
A final block in a data transfer may be presented as a Block end of file (BlockEOF). The BlockEOF may have a length between 0 and the max block size. If the receiver 1206 finds a discrepancy between a pre-negotiated file size (e.g., length field 1432) and the amount of data actually transferred, the receiver 1206 may send an Error message indicating the failure, as discussed below.
x. Ack
If the sender 1202 is driving a synchronous mode transfer, the sender 1202 may wait until receiving an acknowledgment (Ack) after sending a Block before sending the next Block. If the receiver is driving a synchronous mode transfer, the receiver 1206 may send either an explicit Ack or a BlockQuery to acknowledge receipt of the previous block. Furthermore, in asynchronous mode bulk transfers, the Ack message may be omitted from the transmission process altogether.
xi. AckEOF
An acknowledgement of an end of file (AckEOF) may be sent in bulk transfers sent in synchronous mode or asynchronous mode. Using the AckEOF the receiver 1206 indicates that all data in the transfer has been received and signals the end of the bulk data transfer session.
xii. Error
In the occurrence of certain issues in the communication, the sender 1202 or the receiver 1206 may send an error message to prematurely end the bulk data transfer session. Error messages may be formatted and encoded according to the status reporting format discussed above. For example, an error message may be formatted similar to the SendReject frame 1520 of
D. Locale Profile
Using the locale profile, smart devices may present supported localizations to other devices in the mesh network. Specifically, the locale profile enables smart devices to specify which locations and languages are supported in a specific format recognizable by other devices in the network.
In some embodiments, any communication using the locale profile may be identified using a profile ID. For example, in some embodiments, the profile ID for the locale profile may be 0x0000 0011. Any communication tagged with the locale profile ID may be interpreted as a locale identifier organized in a format that is mutually understood by other devices in the network. Moreover, in some embodiments, the bits of data in the profile may be formatted in a big endian or little endian. Furthermore, in some embodiments, the locale profile may be instanced for each device using a node identifier as a unique identifier for each respective device in the network.
a. Locale Profile Schema
The schema version field 1602 may include a profile-specific tag number (e.g., 0x0002) that allows a receiving device to determine that the version field 1602 is being sent. In some embodiments, this tag may be formatted according to the locale profile or another profile (e.g., core profile) that enables receiving data to interpret the tag. Furthermore, in some embodiments, the data following the schema version tag may be an unsigned integer that indicates the version. In some embodiments, the unsigned integer may be limited to a number of values (e.g., 0-255). For example, the integer may be limited by an amount of bits allocated to the schema version field 1602. In other embodiments, the number may be constrained beyond the integers that may be represented using the available bits. Furthermore, in some embodiments, the schema version field 1602 may be read by other devices in the network using the locale profile. Furthermore, in some embodiments, the other devices may write to the schema version using another profile (e.g., software update profile, etc.). In some embodiments, at least some of the devices in the network are not able to write the schema version field.
The schema version 1602 value may be largely advisory in nature and intended to signal to schema readers a change in the schema from this specification. In some embodiments, when changes to the schema are additive, the schema number is simply advisory to the schema reader that new top-level schema fields are present. In such embodiments, normal schema lookup or iteration would make these new fields known without a reliance on this particular field or value. However, a schema change coupled with a change in this field value helps software validation checks confirm that these additions are intended and not simply implementation errors.
The active locale field 1604 includes an active locale sub-field 1608 that indicates which locale is active for the device. In other words, the active locale field 1604 may indicate which language and/or location is being used by the device. For example, the device may display a user interface based on the selected location and/or language. The available locales field 1606 includes one or more available locales sub-fields 1610. Each available locale sub-field 1610 indicates an available locale that is supported and understood by the device.
i. Locale Sub-Fields Representation
The following Table 23 represents formatting that may be used to represent the active locale sub-field 1608 and/or the available locale sub-fields 1610.
Each of the sub-fields 1608 and 1610 include respective tag numbers used to identify the tagged information as the active locale sub-field 1608 or an available locale sub-field 1610. In some embodiments, the tagged data may be formatted in a specific format (e.g., Universal Character Set and Transformation Format-8 bit). Furthermore, in certain embodiments, the tagged data may have further constraints. For example, in some embodiments, the tagged data may include strings of data formatted according to the Internet Engineering Task Force (IETF) Best Current Practices (BCP) 47 specification.
b. Retrieving and Setting Locales
Upon receiving the available locales, the requesting device may select an active profile form the available profiles (block 1616). In some embodiments, the requesting device may present the available locales to a user and receive a selection from a user. In certain embodiments, the requesting device may select the active profile to a preferred locale that may be stored on the requesting device, another device, and/or the service. In some embodiments, the preferred locale may be a locale atop a list of available locale. In other words, one or more locales may be prioritized into a list with the requesting device selecting the highest priority locale available to the other device. After selecting a new active profile, the requesting device sends a request to change the active locale to the selected locale (block 1618).
In some embodiments, the requesting device may store the available locales for a device without setting a new active profile. For example, a user wishing to see available locales (or a set active profile) for another device may be physically located at the requesting device without changing the active profile. In such embodiments, the requesting device may not choose and active profile or send a request to change the active profile.
Herebelow is an example of the process for setting an active locale. The requesting device requests all available locales. The responding device responds with British English, United States English, United States Spanish, Canadian French, and Netherlands Dutch among one or more other similar locales. The requesting device sets the active profile to United States English. Table 25 below illustrates an example encoding of these communications.
The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.
This application is a continuation of U.S. Non-Provisional patent application Ser. No. 14/588,081, filed Dec. 31, 2014, entitled “LOCALE PROFILE FOR A FABRIC NETWORK,” which claims the benefit of Provisional Application Ser. No. 62/061,593, filed Oct. 8, 2014, entitled “FABRIC NETWORK,” which are each incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4551842 | Segarra | Nov 1985 | A |
| 4956875 | Bernard et al. | Sep 1990 | A |
| 5777549 | Arrowsmith et al. | Jul 1998 | A |
| 6097288 | Koeppe, Jr. | Aug 2000 | A |
| 7065579 | Traversat et al. | Jun 2006 | B2 |
| 7103834 | Humpleman et al. | Sep 2006 | B1 |
| 7103875 | Kaneko et al. | Sep 2006 | B1 |
| 7161483 | Chung | Jan 2007 | B2 |
| 7162090 | Miura et al. | Jan 2007 | B2 |
| 7162690 | Gupta et al. | Jan 2007 | B2 |
| 7324824 | Smith et al. | Jan 2008 | B2 |
| 7496622 | Brown et al. | Feb 2009 | B2 |
| 7571092 | Nieh | Aug 2009 | B1 |
| 7613703 | Kakivaya et al. | Nov 2009 | B2 |
| 7617328 | Lewis et al. | Nov 2009 | B2 |
| 7620934 | Falter et al. | Nov 2009 | B2 |
| 7636656 | Nieh | Dec 2009 | B1 |
| 7676586 | Kaler et al. | Mar 2010 | B2 |
| 7683773 | Goodal et al. | Mar 2010 | B1 |
| 7685288 | Kakivaya et al. | Mar 2010 | B2 |
| 7698398 | Lai | Apr 2010 | B1 |
| 7756049 | Chen et al. | Jul 2010 | B2 |
| 7958258 | Yeung | Jun 2011 | B2 |
| 7990897 | Jing et al. | Aug 2011 | B2 |
| 8001232 | Saulpaugh et al. | Aug 2011 | B1 |
| 8014321 | Kakivaya et al. | Sep 2011 | B2 |
| 8037202 | Yeager et al. | Oct 2011 | B2 |
| 8194681 | Kaarela et al. | Jun 2012 | B2 |
| 8239665 | Liu et al. | Aug 2012 | B2 |
| 8279874 | Lu et al. | Oct 2012 | B1 |
| 8331544 | Kraus et al. | Dec 2012 | B2 |
| 8341595 | Arner et al. | Dec 2012 | B2 |
| 8370522 | McCanne | Feb 2013 | B2 |
| 8374183 | Alkhatib et al. | Feb 2013 | B2 |
| 8488624 | Fries et al. | Jul 2013 | B2 |
| 8539567 | Logue et al. | Sep 2013 | B1 |
| 8543640 | Qiu et al. | Sep 2013 | B2 |
| 8560645 | Linden et al. | Oct 2013 | B2 |
| 8594850 | Gourlay et al. | Nov 2013 | B1 |
| 8635373 | Supramaniam et al. | Jan 2014 | B1 |
| 8655995 | Elston et al. | Feb 2014 | B2 |
| 8670946 | Salazar et al. | Mar 2014 | B2 |
| 8675557 | Le | Mar 2014 | B2 |
| 8700743 | Tebbs et al. | Apr 2014 | B2 |
| 8706856 | Mengle et al. | Apr 2014 | B2 |
| 8725851 | Kiley | May 2014 | B2 |
| 8755289 | Kliger et al. | Jun 2014 | B2 |
| 8755913 | McCormack | Jun 2014 | B2 |
| 8868672 | Hummel et al. | Oct 2014 | B2 |
| 8879604 | Woo et al. | Nov 2014 | B2 |
| 8886809 | Nass | Nov 2014 | B2 |
| 8913611 | Koponen et al. | Dec 2014 | B2 |
| 8942189 | Chou et al. | Jan 2015 | B2 |
| 8953446 | Wang et al. | Feb 2015 | B1 |
| 8994539 | Grohman et al. | Mar 2015 | B2 |
| 9000896 | Kim | Apr 2015 | B1 |
| 9037633 | Tukol et al. | May 2015 | B2 |
| 9054961 | Kim et al. | Jun 2015 | B1 |
| 9054976 | Chen et al. | Jun 2015 | B2 |
| 9141370 | Nay | Sep 2015 | B1 |
| 9241270 | Logue | Jan 2016 | B1 |
| 9270761 | Logue et al. | Feb 2016 | B1 |
| 9311811 | Szewczyk et al. | Apr 2016 | B1 |
| 9338071 | Erickson et al. | May 2016 | B2 |
| 9351193 | Raleigh et al. | May 2016 | B2 |
| 9410712 | Smith et al. | Aug 2016 | B2 |
| 9432464 | Logue et al. | Aug 2016 | B2 |
| 9497261 | Mawrey et al. | Nov 2016 | B1 |
| 9503443 | Krauss et al. | Nov 2016 | B2 |
| 9515906 | Jang et al. | Dec 2016 | B2 |
| 9529635 | Werth et al. | Dec 2016 | B2 |
| 9531550 | Jabbaz et al. | Dec 2016 | B2 |
| 9582598 | Kalgi | Feb 2017 | B2 |
| 9661093 | Logue et al. | May 2017 | B2 |
| 9819638 | Szewczyk et al. | Nov 2017 | B2 |
| 9847964 | Logue | Dec 2017 | B2 |
| 20010025349 | Sharood et al. | Sep 2001 | A1 |
| 20020010688 | Shah et al. | Jan 2002 | A1 |
| 20020022991 | Sharood et al. | Feb 2002 | A1 |
| 20020111948 | Nixon | Aug 2002 | A1 |
| 20020124082 | San Andres | Sep 2002 | A1 |
| 20020165929 | McLaughlin et al. | Nov 2002 | A1 |
| 20030023755 | Harris | Jan 2003 | A1 |
| 20040022257 | Green et al. | Feb 2004 | A1 |
| 20040032847 | Cain | Feb 2004 | A1 |
| 20040049590 | Collier et al. | Mar 2004 | A1 |
| 20040102931 | Ellis | May 2004 | A1 |
| 20040114601 | Watanabe et al. | Jun 2004 | A1 |
| 20040236874 | Largman et al. | Nov 2004 | A1 |
| 20040268306 | Cheng | Dec 2004 | A1 |
| 20050091346 | Krishnaswami et al. | Apr 2005 | A1 |
| 20050108332 | Vaschillo et al. | May 2005 | A1 |
| 20050132055 | Neogi | Jun 2005 | A1 |
| 20050138648 | Ahmed et al. | Jun 2005 | A1 |
| 20050147069 | Rink et al. | Jul 2005 | A1 |
| 20050199716 | Shafer et al. | Sep 2005 | A1 |
| 20050260989 | Pourtier et al. | Nov 2005 | A1 |
| 20060026304 | Price | Feb 2006 | A1 |
| 20060053234 | Kumar et al. | Mar 2006 | A1 |
| 20060069791 | Patrick et al. | Mar 2006 | A1 |
| 20060080082 | Ravindra | Apr 2006 | A1 |
| 20060082461 | Andres et al. | Apr 2006 | A1 |
| 20060092012 | Kaiser et al. | May 2006 | A1 |
| 20060092890 | Gupta et al. | May 2006 | A1 |
| 20060143560 | Gupta et al. | Jun 2006 | A1 |
| 20060173985 | Moore | Aug 2006 | A1 |
| 20060174106 | Bell et al. | Aug 2006 | A1 |
| 20060179349 | Tyma et al. | Aug 2006 | A1 |
| 20060200766 | Lakritz | Sep 2006 | A1 |
| 20060259160 | Hood et al. | Nov 2006 | A1 |
| 20060282498 | Muro | Dec 2006 | A1 |
| 20070008099 | Kimmel et al. | Jan 2007 | A1 |
| 20070011673 | Melo | Jan 2007 | A1 |
| 20070055758 | McCoy et al. | Mar 2007 | A1 |
| 20070061018 | Callaghan et al. | Mar 2007 | A1 |
| 20070177603 | Calme et al. | Aug 2007 | A1 |
| 20070185814 | Boccon-Gibod | Aug 2007 | A1 |
| 20070218875 | Calhoun et al. | Sep 2007 | A1 |
| 20070220907 | Ehlers | Sep 2007 | A1 |
| 20070240154 | Berzymisch et al. | Oct 2007 | A1 |
| 20070282944 | Odaka et al. | Dec 2007 | A1 |
| 20070294360 | Ebling | Dec 2007 | A1 |
| 20080001713 | Dasgupta et al. | Jan 2008 | A1 |
| 20080005287 | Harvey | Jan 2008 | A1 |
| 20080092057 | Monson et al. | Apr 2008 | A1 |
| 20080103610 | Ebrom et al. | May 2008 | A1 |
| 20080184151 | Agarwal et al. | Jul 2008 | A1 |
| 20080188963 | McCoy | Aug 2008 | A1 |
| 20080189637 | Krajewski et al. | Aug 2008 | A1 |
| 20080281472 | Podgorny et al. | Nov 2008 | A1 |
| 20080301669 | Rao et al. | Dec 2008 | A1 |
| 20080301672 | Rao et al. | Dec 2008 | A1 |
| 20080305806 | Jung | Dec 2008 | A1 |
| 20090058618 | Gopalan et al. | Mar 2009 | A1 |
| 20090063659 | Kazerouni et al. | Mar 2009 | A1 |
| 20090132070 | Ebrom et al. | May 2009 | A1 |
| 20090177462 | Alfven | Jul 2009 | A1 |
| 20090210803 | Brignull et al. | Aug 2009 | A1 |
| 20090222659 | Miyabayashi | Sep 2009 | A1 |
| 20090228696 | McKelvey et al. | Sep 2009 | A1 |
| 20090300744 | Guo | Dec 2009 | A1 |
| 20100011354 | Gharabally et al. | Jan 2010 | A1 |
| 20100030549 | Lee | Feb 2010 | A1 |
| 20100067705 | Boccon-Gibod et al. | Mar 2010 | A1 |
| 20100106313 | Grohman | Apr 2010 | A1 |
| 20100106330 | Grohman | Apr 2010 | A1 |
| 20100106814 | Hadzidedic | Apr 2010 | A1 |
| 20100114853 | Fisher | May 2010 | A1 |
| 20100138507 | Sun et al. | Jun 2010 | A1 |
| 20100146611 | Kuzin et al. | Jun 2010 | A1 |
| 20100211224 | Keeling et al. | Aug 2010 | A1 |
| 20100325313 | Asensio et al. | Dec 2010 | A1 |
| 20110013630 | Nanda et al. | Jan 2011 | A1 |
| 20110082685 | Ahlin | Apr 2011 | A1 |
| 20110093535 | Takakura et al. | Apr 2011 | A1 |
| 20110099547 | Banga | Apr 2011 | A1 |
| 20110139924 | Nakayama | Jun 2011 | A1 |
| 20110153766 | Ramchandani | Jun 2011 | A1 |
| 20120016659 | Miura et al. | Jan 2012 | A1 |
| 20120033568 | Park et al. | Feb 2012 | A1 |
| 20120082091 | Siomina | Apr 2012 | A1 |
| 20120094643 | Brisebois et al. | Apr 2012 | A1 |
| 20120101453 | Boettger | Apr 2012 | A1 |
| 20120110077 | Merchant et al. | May 2012 | A1 |
| 20120117497 | Uola et al. | May 2012 | A1 |
| 20120122476 | Lee | May 2012 | A1 |
| 20120144058 | Ohashi et al. | Jun 2012 | A1 |
| 20120184907 | Smith et al. | Jul 2012 | A1 |
| 20120195235 | Balla et al. | Aug 2012 | A1 |
| 20120198218 | Tukol | Aug 2012 | A1 |
| 20120246345 | Contreras et al. | Sep 2012 | A1 |
| 20120254554 | Nakajima | Oct 2012 | A1 |
| 20120271619 | Abdel-Kader | Oct 2012 | A1 |
| 20120331182 | Bishop | Dec 2012 | A1 |
| 20130024799 | Fadell et al. | Jan 2013 | A1 |
| 20130035098 | Das et al. | Feb 2013 | A1 |
| 20130110942 | Shen et al. | May 2013 | A1 |
| 20130124186 | Donabedian et al. | May 2013 | A1 |
| 20130136117 | Schrum et al. | May 2013 | A1 |
| 20130151563 | Addepalli | Jun 2013 | A1 |
| 20130159476 | Hilburn et al. | Jun 2013 | A1 |
| 20130173064 | Fadell | Jul 2013 | A1 |
| 20130198516 | Fenton et al. | Aug 2013 | A1 |
| 20130201980 | Rahul | Aug 2013 | A1 |
| 20130297477 | Overman et al. | Nov 2013 | A1 |
| 20130303234 | Kakkad | Nov 2013 | A1 |
| 20130305357 | Ayyagari et al. | Nov 2013 | A1 |
| 20130311140 | Schecter | Nov 2013 | A1 |
| 20130318343 | Bjarnason et al. | Nov 2013 | A1 |
| 20130322281 | Ludlow et al. | Dec 2013 | A1 |
| 20130326605 | Betz | Dec 2013 | A1 |
| 20130339480 | Smithson | Dec 2013 | A1 |
| 20130343343 | Shahid | Dec 2013 | A1 |
| 20130346064 | Chen et al. | Dec 2013 | A1 |
| 20140001977 | Zacharchuk et al. | Jan 2014 | A1 |
| 20140006660 | Frei et al. | Jan 2014 | A1 |
| 20140016513 | Martin et al. | Jan 2014 | A1 |
| 20140022061 | Apte et al. | Jan 2014 | A1 |
| 20140047080 | Piccolo, et al. | Feb 2014 | A1 |
| 20140068041 | Obligacion | Mar 2014 | A1 |
| 20140097953 | Jelveh et al. | Apr 2014 | A1 |
| 20140108018 | Phillips et al. | Apr 2014 | A1 |
| 20140120861 | Kwak et al. | May 2014 | A1 |
| 20140122055 | Hobson | May 2014 | A1 |
| 20140123123 | Bahls | May 2014 | A1 |
| 20140129209 | Saleme et al. | May 2014 | A1 |
| 20140145962 | Radhakrishnan | May 2014 | A1 |
| 20140149270 | Lombard et al. | May 2014 | A1 |
| 20140163948 | Daly | Jun 2014 | A1 |
| 20140164474 | Issa et al. | Jun 2014 | A1 |
| 20140164519 | Shah | Jun 2014 | A1 |
| 20140169214 | Nakajima | Jun 2014 | A1 |
| 20140180671 | Osipova | Jun 2014 | A1 |
| 20140187224 | Liu et al. | Jul 2014 | A1 |
| 20140195664 | Rahnama | Jul 2014 | A1 |
| 20140208393 | Yasukawa et al. | Jul 2014 | A1 |
| 20140235171 | Molettiere et al. | Aug 2014 | A1 |
| 20140237595 | Sridhara | Aug 2014 | A1 |
| 20140238964 | Casner | Aug 2014 | A1 |
| 20140278343 | Tran | Sep 2014 | A1 |
| 20140280520 | Baier et al. | Sep 2014 | A1 |
| 20140282923 | Narayan et al. | Sep 2014 | A1 |
| 20140303961 | Leydon et al. | Oct 2014 | A1 |
| 20140304357 | Bestler et al. | Oct 2014 | A1 |
| 20140304760 | Kim et al. | Oct 2014 | A1 |
| 20140306833 | Ricci | Oct 2014 | A1 |
| 20140316585 | Boesveld et al. | Oct 2014 | A1 |
| 20140344330 | Copeland | Nov 2014 | A1 |
| 20140357357 | Boyd | Dec 2014 | A1 |
| 20140358516 | Lin et al. | Dec 2014 | A1 |
| 20140359101 | Dawes et al. | Dec 2014 | A1 |
| 20140359601 | Constable et al. | Dec 2014 | A1 |
| 20140359606 | Salameh | Dec 2014 | A1 |
| 20140366011 | Rector et al. | Dec 2014 | A1 |
| 20140366080 | Gupta et al. | Dec 2014 | A1 |
| 20140369345 | Yang et al. | Dec 2014 | A1 |
| 20140376405 | Erickson et al. | Dec 2014 | A1 |
| 20140380388 | Lee et al. | Dec 2014 | A1 |
| 20150006633 | Vandwalle et al. | Jan 2015 | A1 |
| 20150006696 | Dershberg | Jan 2015 | A1 |
| 20150016407 | Erickson et al. | Jan 2015 | A1 |
| 20150023336 | Ilsar et al. | Jan 2015 | A1 |
| 20150026102 | Anantharam et al. | Jan 2015 | A1 |
| 20150034161 | Tamayo et al. | Feb 2015 | A1 |
| 20150057808 | Cook et al. | Feb 2015 | A1 |
| 20150073907 | Purves | Mar 2015 | A1 |
| 20150074259 | Ansari et al. | Mar 2015 | A1 |
| 20150089375 | Liu et al. | Mar 2015 | A1 |
| 20150098358 | Park et al. | Apr 2015 | A1 |
| 20150113172 | Johnson et al. | Apr 2015 | A1 |
| 20150128126 | Brunet et al. | May 2015 | A1 |
| 20150131485 | Brandt et al. | May 2015 | A1 |
| 20150142947 | Dyba et al. | May 2015 | A1 |
| 20150151194 | Ziran et al. | Jun 2015 | A1 |
| 20150156546 | Moon et al. | Jun 2015 | A1 |
| 20150161114 | Buryak et al. | Jun 2015 | A1 |
| 20150172120 | Dwarampudi et al. | Jun 2015 | A1 |
| 20150178347 | Mutalik et al. | Jun 2015 | A1 |
| 20150186156 | Brown | Jul 2015 | A1 |
| 20150215297 | Rathod et al. | Jul 2015 | A1 |
| 20150222517 | McLaughlin et al. | Aug 2015 | A1 |
| 20150334545 | Maier et al. | Nov 2015 | A1 |
| 20150341184 | Tatzel | Nov 2015 | A1 |
| 20150341979 | Gallo | Nov 2015 | A1 |
| 20150347114 | Yoon | Dec 2015 | A1 |
| 20150347378 | Poiesz | Dec 2015 | A1 |
| 20150350850 | Edge | Dec 2015 | A1 |
| 20150373482 | Barnard | Dec 2015 | A1 |
| 20150381737 | Quinn | Dec 2015 | A1 |
| 20160102878 | Smith et al. | Apr 2016 | A1 |
| 20160103908 | Fletcher | Apr 2016 | A1 |
| 20160103911 | Logue et al. | Apr 2016 | A1 |
| 20160104369 | Szewczyk et al. | Apr 2016 | A1 |
| 20160105314 | Logue et al. | Apr 2016 | A1 |
| 20160105339 | Erickson et al. | Apr 2016 | A1 |
| 20160105360 | Erickson et al. | Apr 2016 | A1 |
| 20160173613 | Logue et al. | Jun 2016 | A1 |
| 20160191483 | Larson et al. | Jun 2016 | A1 |
| 20160225250 | Szewczyk et al. | Aug 2016 | A1 |
| 20160306879 | Logue et al. | Oct 2016 | A1 |
| 20160344830 | Smith et al. | Nov 2016 | A1 |
| 20160373907 | Dowlatkhah | Dec 2016 | A1 |
| 20170134479 | Kalgi | May 2017 | A1 |
| 20170300675 | Betz | Oct 2017 | A1 |
| 20170353573 | Harris | Dec 2017 | A1 |
| Entry |
|---|
| Phillips et al., Internet Engineering Task Force. Tags for Identifying Languages. BCP 47. Sep. 2009. http://tools.ietf.org/html/bcp47. |
| J. Klensin, Internationalized Domain Names in Applications (IDNA): Protocol, Aug. 2010. http://tools.ietf.org/html/rfc5891. |
| USB Implementers' Forum. Universal Serial Bus (USB): Device Class Definition for Human Interface Devices (HID). Version 1.11. Jun. 27, 2001; http://www.usb.org/developers/hidpage/HID1_11.pdf. |
| Language Tags in HTML antd XML, Sep. 10, 2009, http://www.w3.org/international/articles/language-tags/Overview.en.php. |
| Ping, Oracle Manual Pages Section 1M: System Administration Commands, pp. 1706-1710, 2013 http://www.w3.org/International/articles/language-tags/Overview.en.php. |
| Markus Mathes; “Time Constrained Web Services for Industrial Automation,” Dissertation from Philipps Universitat—Marburg; pp. 1-201, Jul. 9, 2009. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2015/054287 dated Jan. 22, 2016; 14 pgs. |
| “Advisory Action”, U.S. Appl. No. 14/590,495, dated Feb. 16, 2016, 3 pages. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 14/665,913, dated Jul. 28, 2016, 4 pages. |
| “Final Office Action”, U.S. Appl. No. 14/590,468, dated Apr. 28, 2016, 31 pages. |
| “Final Office Action”, U.S. Appl. No. 14/590,495, dated Nov. 27, 2015, 19 pages. |
| “First Action Interview Office Action”, U.S. Appl. No. 14/588,086, dated Dec. 4, 2015, 3 pages. |
| “First Action Interview Office Action”, U.S. Appl. No. 14/588,104, dated Aug. 25, 2015, 6 pages. |
| “First Action Interview Office Action”, U.S. Appl. No. 14/590,495, dated Jun. 25, 2015, 3 pages. |
| “First Action Interview Office Action”, U.S. Appl. No. 14/590,468, dated Jul. 1, 2015, 5 pages. |
| “First Action Interview Office Action”, U.S. Appl. No. 14/665,913, dated Nov. 2, 2015, 4 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/588,075, dated May 21, 2015, 13 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/588,081, dated Jul. 22, 2015, 15 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/590,468, dated Oct. 30, 2015, 36 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/590,495, dated Jun. 17, 2016, 18 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/588,075, dated Sep. 21, 2015, 6 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/588,081, dated Jan. 6, 2016, 12 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/588,086, dated Mar. 31, 2016, 18 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/588,104, dated Nov. 27, 2015, 16 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/592,469, dated Oct. 23, 2015, 5 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/665,913, dated Feb. 18, 2016, 6 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/588,086, dated Aug. 7, 2015, 4 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/588,104, dated Jul. 8, 2015, 4 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/590,468, dated Feb. 23, 2015, 4 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/590,495, dated Apr. 6, 2015, 5 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/592,469, dated Jun. 17, 2015, 7 pages. |
| “Pre-interview First Office Action”, U.S. Appl. No. 14/665,913, dated Aug. 24, 2015, 4 pages. |
| “Final Office Action”, U.S. Appl. No. 14/590,495, dated Mar. 13, 2017, 26 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 15/096,063, dated Feb. 17, 2017, 34 pages. |
| “Notice of Allowance”, U.S. Appl. No. 15/050,195, dated Jan. 25, 2017, 7 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/590,468, dated Mar. 31, 2017, 8 pages. |
| “International Preliminary Report on Patentability”, U.S. Appl. No. PCT/US2015/054287, dated Apr. 20, 2017, 9 pages. |
| “Notice of Allowance”, U.S. Appl. No. 15/096,063, dated Jul. 27, 2017, 9 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/590,495, dated Aug. 28, 2017, 20 pages. |
| “Pre-Interview Office Action”, U.S. Appl. No. 15/187,531, dated Oct. 18, 2017, 4 pages. |
| Billure, et al., “Internet of Things—A Study on the Security Challenges”, 2015 IEEE International Advance Computing Conference (IACC), 2015, pp. 247-252. |
| Hein, et al., “A Service Oriented Platform for Health Services and Ambient Assisted Living”, 2009 IEEE Computer Society, 2009, pp. 531-537. |
| “Non-Final Office Action”, U.S. Appl. No. 15/228,939, dated Jan. 8, 2018, 13 pages. |
| “Notice of Allowance”, U.S. Appl. No. 15/187,531, dated Feb. 5, 2018, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160248647 A1 | Aug 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62061593 | Oct 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14588081 | Dec 2014 | US |
| Child | 15143082 | US |
