text:
US10205769B2 - Distributed applications across platforms - Google Patents
Distributed applications across platforms Download PDF
utility meter
Arun Sehgal
Shannon M. Votava
Bruce Angelis
Itron Inc
2013-05-31 Application filed by Itron Inc filed Critical Itron Inc
2013-05-31 Priority to US13/907,688 priority Critical patent/US10205769B2/en
2013-09-27 Assigned to ITRON, INC. reassignment ITRON, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ANGELIS, BRUCE, SEHGAL, ARUN, VOTAVA, SHANNON M.
2015-07-06 Assigned to WELLS FARGO, NATIONAL ASSOCIATION reassignment WELLS FARGO, NATIONAL ASSOCIATION SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ITRON, INC.
2018-01-08 Assigned to WELLS FARGO BANK, NATIONAL ASSOCIATION reassignment WELLS FARGO BANK, NATIONAL ASSOCIATION SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ITRON NETWORKED SOLUTIONS, INC., ITRON, INC.
238000004891 communication Methods 0 abstract claims description 42
239000008264 clouds Substances 0 abstract claims description 9
238000009434 installation Methods 0 abstract description 21
230000003213 activating Effects 0 abstract description 11
238000009826 distribution Methods 0 description 12
238000002716 delivery method Methods 0 description 8
230000000153 supplemental Effects 0 description 1
239000003826 tablets Substances 0 description 1
H04L67/10—Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
G06F11/00—Error detection; Error correction; Monitoring
G06F11/30—Monitoring
G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
G06F17/30—
G06F8/00—Arrangements for software engineering
G06Q20/12—Payment architectures specially adapted for electronic shopping systems
G06Q20/123—Shopping for digital content
G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices
G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
G06Q30/06—Buying, selling or leasing transactions
G06Q30/0601—Electronic shopping
G06Q30/0623—Item investigation
G06Q30/0641—Shopping interfaces
G06F9/46—Multiprogramming arrangements
G06F9/54—Interprogram communication
G06F9/547—Remote procedure calls [RPC]; Web services
H04L67/12—Network-specific arrangements or communication protocols supporting networked applications adapted for proprietary or special purpose networking environments, e.g. medical networks, sensor networks, networks in a car or remote metering networks
H04L67/34—Network-specific arrangements or communication protocols supporting networked applications involving the movement of software or configuration parameters
H04W4/001—
H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
H04W4/50—Service provisioning or reconfiguring
H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
Y04S40/10—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them characterised by communication technology
Y04S40/18—Network protocols supporting networked applications, e.g. including control of end-device applications over a network
A utility application store may be configured to present an interface displaying multiple applications that are available from the utility application store. By accessing the interface of the utility application store, a utility supplier may, with a single request, initiate installation or activation of an application on multiple utility meters or other smart sensors in a utility communication network. The utility application store may be configured to provide notification of the availability of applications for utility meters or other smart sensors, consumer computing devices, and/or utility supplier back office computing devices. The utility application store may include one or more distributed applications that include a first portion configured for execution by a utility meter and one or more other portions configured for execution by another computing device (e.g., a personal computer, mobile device, utility supplier back office server, cloud service, or the like).
Utility meters such as electric, water and natural gas meters have evolved from isolated devices that simply measure utility consumption and display a consumption reading to so called "smart meters" that are connected devices capable of reporting resource consumption readings automatically over a utility communication network. Such meters utilize increasingly complex and specialized software to perform required functions. Unfortunately, the software update process is a difficult one, in which administrators utilize tools that are configured for download of specific software code. Considerable time is spent by network professionals, and each update is a customized event requiring consideration and preparation.
In some instances, utility companies may not even be aware that software or updates are available for devices in their network. Thus, in order to install or update software across their entire network, a utility company must first learn that compatible software is available for devices in their network. Consumers are generally completely unaware of what software is running on the meters servicing the properties, and play no role in its selection and operation.
Once installed, the software has been designed to execute on the smart meter to perform metering functionality and to report metering data to devices in the utility's communication network. Smart meter software has been restricted from communication with devices outside the utility's communication network.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
FIG. 1 is a schematic diagram of an example architecture including a utility application store usable to facilitate distribution and installation of applications to one or more smart utility meters, smart sensors, or other network computing devices.
FIG. 2 is a schematic diagram of an example user interface presenting multiple "meter" applications available from a utility application store.
FIG. 3 is a schematic diagram of another example user interface presenting multiple "consumer" applications available from a utility application store.
FIG. 4 is a schematic diagram of an example user interface presenting multiple "other" applications available from a utility application store.
FIG. 5 is a block diagram illustrating details of the example utility application store of FIG. 1.
FIG. 6 is a block diagram illustrating details of one of the example smart sensors of FIG. 1.
FIG. 7 is a flowchart of an example method that may be implemented by a utility application store to provide one or more applications for installation on one or more utility meters or other smart sensors.
FIG. 8 is a schematic diagram of an example architecture which is usable to notify users of the existence of applications available for one or more computing devices.
FIG. 9A is a schematic diagram of an example notification that may be used to notify a utility supplier of an application that is available for a utility meter.
FIG. 9B is a schematic diagram of an example notification that may be used to notify a customer of an application that is available for the customer's computing device.
FIG. 9C is a schematic diagram of an example notification that may be used to notify a utility supplier of an application that is available for a utility supplier computing device.
FIG. 10 is a signal flow diagram of an example method of notifying users of the existence of applications available for one or more computing devices.
FIG. 11 is a schematic diagram of an example architecture in which a first portion of a distributed application is installed on a smart sensor and second portion of the distributed application is installed on another computing device.
FIG. 12 is a schematic diagram of an example user interface of a portion of a distributed application executable on a consumer device, which interacts with a portion of the distributed application that is executable on a smart sensor.
FIG. 13 is a signal flow diagram of an example method that may be implemented by a utility meter or other smart sensor executing a first portion of a distributed application, which interacts with a second portion of the distributed application executing on another computing device.
As discussed above, software for smart utility meters is currently only available directly from the respective manufacturers of the smart utility meters, with different manufacturers making the software available in different ways. Utility companies currently lack a centralized location from which they can easily obtain software for the smart utility meters and other devices in their utility communication networks. Existing systems also lack any mechanism to notify utility companies, customers, and other users when applications are available for their smart utility meters, consumer devices, and other computing devices. Still further, existing utility smart meter applications are incapable of communicating with and leveraging applications running on consumer computing devices, utility backend computing devices, and other web services. This patent application describes a utility application store comprising a repository of applications available for download and installation on one or more smart utility meters or other smart sensors. The term "smart sensor" means a measuring and/or sensing equipment which measures or senses physical parameters (e.g., energy, power, voltage, power factor, temperature, gas pressure, flow rate, etc.) and has the ability to communicate this information via a network. By way of example and not limitation, smart sensors may include utility meters (e.g., electricity, water, or gas meters), relays, repeaters, smart grid routers, transformers or any such utility network computing device. The utility application store may additionally or alternatively include applications available for computing devices other than utility network computing devices, such as personal computers (e.g., desktop computers, laptop computers, etc.), mobile devices (smartphones, tablets, etc.), servers, routers, access points, or the like.
As used herein, the term "application" or "app" means any software or firmware capable of executing on a computing device. Examples of applications include, without limitation, an operating system, an update to an operating system, a software program, an update of a software program, an add-on to a software program, a patch, a plugin, a driver, a firmware image, or a firmware update.
In one aspect, the utility application store may be configured to present an interface displaying multiple applications that are available from the utility application store. By accessing the interface of the utility application store, a utility supplier may, with a single request, initiate installation or activation of one or more applications on multiple utility meters or other smart sensors in the utility's communication network. The multiple utility meters or other smart sensors may comprise a predefined subset (e.g., all meters of a certain model, all meters in a certain geographic region, etc.) of utility meters in the utility's communication network. In some examples, a single application may be installed at a time. However, in other examples, multiple different applications may be installed in a batch or sequentially.
In another aspect, a utility application store or other service may be configured to provide notification of the availability of applications for utility meters or other smart sensors, consumer computing devices, and/or utility back office computing devices. For example, upon receiving a request to install an application on a consumer computing device (e.g., personal computer or mobile device), the utility application store or other service may identify an associated application that is available for a utility meter of a user of the consumer computing device. The utility application store or other service may then send a notification of the availability of the associated application to a utility supplier servicing the utility meter and/or to the consumer computing device.
In yet another aspect, the utility application store may include a distributed application that includes a first portion configured for execution by a utility meter or other smart sensor and a second portion configured for execution by another computing device (e.g., a personal computer, mobile device, utility back office server, cloud service, or the like). In one example, a smart utility meter may have the first portion of the distributed application stored in memory and executable by one or more processors to configure the smart utility meter to cause the second portion of the distributed application installed at a remote computing resource to perform at least a portion of an operation.
Any or all of the foregoing aspects may be performed or made possible by a utility application store, such as that described herein. However, certain aspects described herein may also be accomplished without the need for a utility application store. While many of the examples may be understood in the context of traditional utility supply chains in which utility providing companies (e.g., energy generation companies) supply resources to utility distribution companies, which in turn provide the resources to end customers. The techniques described herein also apply to models in which utility suppliers supply resources to consumers directly or via retailers/vendors, as opposed to through a utility distribution company. As used herein the term "utility supplier" means any provider or distributor of a resource including, without limitation, a utility providing company, a utility distribution company, a smart city, a municipality, a retailer or vendor, a co-op, a micro grid, or an individual.
This brief overview is provided for the reader's convenience and is not intended to limit the scope of the claims, nor the proceeding sections. Furthermore, the techniques described in detail below may be implemented in a number of ways and in a number of contexts. Several example implementations are provided with reference to the following figures, as described below in more detail. However, the following implementations and context are but few of many.
Example Utility Application Store
FIG. 1 is a diagram illustrating an example networked environment or architecture 100 including a utility application store 102. The utility application store or "app store" 102 includes a repository of applications 104 available for installation on one or more utility meters or other smart sensors 106(1), 106(2), 106(3), . . . 106(N) (collectively referred to as "smart sensors 106"), where N is any integer greater than or equal to 1. In the illustrated example, the smart sensors 106 are arranged in a mesh network defining an autonomous routing area 108. However, in other examples, the meters may be arranged in a star network or other network topology. Regardless of the topology of the autonomous routing area 108, individual smart sensors or "nodes" may be in communication by wireless (e.g., radio frequency) and/or wired (e.g., power line communication, Ethernet, serial, etc.) connections. The smart sensors 106 may be configured to collect information (e.g., resource consumption information, network traffic information, weather information, etc.) and to report the collected information to a utility supplier 110 via a wired or wireless network 112, such as the Internet, a cellular network, or the like. The network 112 may itself be made up of one or more other wired and/or wireless networks. In the illustrated example, smart sensor 106(2) acts as a root or edge node of the autonomous routing area 108 to relay communications from other smart sensors 106 in the autonomous routing area 108 to the utility supplier 110 over the network 112. The utility supplier 110 may be representative of a utility distribution company and may include one or more severs or other computing devices, which may be arranged in a single location or in multiple distributed locations. In other examples, the utility supplier 110 may be a utility providing company (e.g., electricity generation company), a smart city, a municipality, a retailer or vendor, a co-op, a micro grid, an individual, or any other provider or distributor of a resource.
The app store repository 104 may include applications designed to run on smart sensors developed by multiple different hardware manufacturers. The app store repository 104 may also include applications designed to run on one or more servers of the utility supplier 110, consumer computing devices 114, or other computing devices. The applications may have been developed by an entity administering the application store 102, one or more utility meter or hardware manufacturers, one or more utility suppliers, and/or one or more independent software vendors. As such, the app store 102 may serve as a central source for all applications that a utility supplier needs for all of the devices in the utility provider's communication network. While the application describes the "utility supplier's communication network" as being owned or administered by the utility provider, in other examples, a separate entity may manage or administer the communication network over which smart sensors and other devices communicate.
Referring back to FIG. 1, a user (e.g., a utility supplier employee, consumer, or other user) may access the utility application store 102 using the computing device 114. Using a web browser or an app store client program resident on computing device 114, the user may access a website or other interface 116 to the utility application store 102. The interface 116 may present a plurality of applications that are available from the app store 102. In the example of FIG. 1, the interface includes multiple tabs 118, each representing a different category of applications available from the app store 102. In the illustrated example, four tabs are shown: meter apps, utility apps, consumer apps, and other. In response to selection of each tab, the interface 116 will display a list or otherwise present applications corresponding to the selected tab/category of application. The interface 116 may also include a search field 120 that may be used to search within the selected tab for applications relevant to an input search term. However, the interface 116 may be configured in any other way suitable to present the applications that are available from the app store 102. For instance instead of having multiple tabs for different categories of users on a single interface, separate interfaces may be presented to users based on their roles. For instance, utility personnel may be presented with only applications for utility computing devices, while consumers may be presented with only applications for consumer computing devices.
In FIG. 1, a user has selected the "meter apps" tab and has input the search query "100 Series." Thus, the interface 116 displays a list of applications for smart meters that are relevant to the search query. From this list, the user may select one or more applications to install or activate. By electing to install an application (e.g., by selection of a download or install control), the user may initiate download or otherwise cause transmission of the application to one or more devices (e.g., meters in this example). By selecting to activate an application, the user may initiate download, cause transmission, or obtain a credential (e.g., key, password, etc.) usable to activate or unlock an application that is already installed (though locked) on the one or more devices. In the illustrated example, each application is shown with the option to "install/activate" the application. However, in other examples, separate controls for "install" and "activate" may be provided, or the interface 116 may only show the relevant controls. In the illustrated example, the user has selected to install or activate the application "OS 2.0: Voltage Quality Add-On." In some examples, selection of the install or activate control alone may be sufficient to initiate the installation or activation. However, in other examples, in response to selection of the install or activate control, the app store 102 may give the user an option to purchase the application.
In some embodiments, the interface 116 may additionally include another tab (not shown) or other interface to display the applications currently installed by the user, on devices of the user, or on devices of an entity with which the user is associated. When present, this tab or interface may also include a list of devices associated with the user or entity and/or provide the ability to update, uninstall, deactivate the applications for each device individually, for classes of device (e.g., device type, model, series, etc.), for devices in a certain geographic area, or the like.
FIG. 2 illustrates an example interface that may be presented to the user to allow the user to purchase the meter application "OS 2.0: Voltage Quality Add-On." As shown, when the user selects to install or activate the application (the left side of FIG. 2), a purchase interface 200 is presented (the right side of FIG. 2) to allow the user to purchase the application. The purchase interface 200 may include a variety of information and/or controls. For instance, in the illustrated example, the purchase interface 200 includes an application "price/device" (shown as $0.99 in this example), a "No. of Devices" field to allow the user to specify the number of devices (in this case 100,000 devices) on which to install the application, and a "Device Type(s)" control to allow the user to specify the type(s) of device(s) on which the application is to be installed. The Device Type(s) control is shown as a drop down menu, but could be a series of radio buttons, check boxes, free text entry fields, or any other control usable to specify one or more device types on which the application is to be installed. In the illustrated example, the Price/Device is the same for all device types, but in other examples the Price/Device may vary depending on the type of device on which the application is to be installed (e.g., a first price for a utility meter and second price for a data collector), the number of devices on which the application is to be installed (e.g., reflecting a volume discount), or the like.
In some examples, the app store 102 may have prior knowledge of the devices associated with the user or an account of the user. In that case, the Device Type(s) control and/or No. of Devices field may be prepopulated with the types and numbers of devices associated with the user or user account. For instance, in the example of FIG. 1, if the app store system 102 is in communication with the utility supplier 110 or otherwise has access to information about the device types and number of each type of device in the utility communication network, the app store 102 may be able to determine which devices in the utility supplier's communication network are compatible with the selected application. The app store 102 may then prepopulate those device types and the number such devices in the purchase interface 200, greatly simplifying the process of purchasing applications across all applicable devices in the utility communication network.
Once the device types and number of devices have been specified (or prepopulated), the purchase interface 200 may display a Total Cost (in this case $99,000) for installation of the application on the specified devices. The purchase interface 200 also includes a "Delivery Method" control allowing the user to specify a preferred delivery method of the application or credential. For instance, in the illustrated example the user is given the option to have the application or credential transmitted directly to the devices over the utility communication network, or to have the application or credential transmitted to the utility supplier 110 for subsequent distribution to the individual devices. The purchase interface 200 also includes a "Payment Method" control to allow the user to specify how to pay for the applications. In FIG. 2, the user is presented with options to "Charge to Account" (e.g., a credit account with the app store or a third party creditor), "Charge to Credit Card," and/or "Prepaid." The Prepaid option may indicate that the user has previously paid for a certain number or dollar value of applications. The prepayment may have taken the form of a one-time payment (e.g., a bulk application purchase), a credit for purchasing another product (e.g., three free applications with the purchase of a new meter), a subscription (e.g., unlimited free apps with subscription), a service or maintenance agreement (e.g., free updates and security patches for 1 year with the purchase of a new software package), or the like. The user may then complete the purchase and initiate the installation or activation by selecting the "Buy Now" control.
FIG. 3 illustrates an example interface that may be presented to a user to allow the user to purchase a consumer application "Electronic Billing." In this example, the user has selected the "Consumer Apps" tab from among tabs 118 and has input the search query "Electricity" in the search field 120. Thus, the interface 116 in this example displays consumer focused applications related to the search query "electricity." As shown, when the user selects to install or activate the application (the left side of FIG. 3), a purchase interface 300 is presented (the right side of FIG. 3) to allow the user to purchase the application. In some embodiments, the purchase interface 300 for consumer applications may be the same or similar to the purchase interface 200 for meter applications. However, in the example of FIG. 3, the purchase interface 300 for consumer applications is different in several respects, reflecting the different needs of consumer users. For example, as shown in FIG. 3, the payment interface 300 omits the No. of Devices field, reflecting the fact that consumers typically will be installing the application on a relatively small number of devices. However, in other variations, the payment interface 300 may include the ability to purchase an application for multiple of the same or different devices, much like the payment interface 200 of FIG. 2. As another example different, the Delivery Method control is omitted in FIG. 3, reflecting the fact that consumers typically will have only one way of installing or activating content on their consumer devices. In still other examples, only the tabs pertinent to the user (e.g., based on the user's role) may be displayed to the user. For instance, only the consumer tab may be shown to the user if the user is a consumer.
The payment interface 300 may also include a link 302 to another app store (e.g., an app store associated with a particular consumer device such as the iTunes® store or the Android® store). In some embodiments, the user may be able to pay for the application from the interface 300 and then navigate to the other app store (e.g., iTunes® store or the Android® store) to download the application. In other embodiments, the user may select the link 302 to navigate to the other app store to both purchase and download the application.
FIG. 4 illustrates an example interface that may be presented to a user to allow the user to purchase an application "Repeater WiFi Hotspot Add-On" for an "Other" computing device. In this example, the user has selected the "Other" tab from among tabs 118 and has input the search query "WiFi" in the search field 120. Thus, the interface 116 in this example displays applications for computing devices other than meters and consumer devices, related to the search query "WiFi." As shown, when the user selects to install or activate the application (the left side of FIG. 4), a purchase interface 400 is presented (the right side of FIG. 4) to allow the user to purchase the application. In some embodiments, the purchase interface 400 for other applications may be the same or similar to the purchase interface 200 for meter applications or the purchase interface 300 for consumer applications. Accordingly, additional discussion of the purchase interface 400 are omitted for brevity.
In the example of FIG. 4, a user (e.g., a utility supplier employee) selects to purchase an add-on application for 100 "X25 Repeaters," at a price of $4.99 per application, for a total of $499. The application in this example may comprise an add-on that allows a radio frequency (RF) repeater to function as a WiFi hotspot. The add-on may be a separate application that is installed on the repeater, or may simply be a key, password, or other credential that unlocks functionality of an application that is already installed on the repeater.
Example Utility Application Store System
FIG. 5 illustrates the example utility application store 102 of FIG. 1 in more detail. The utility application store 102 may be configured as or disposed at a server, a cluster of servers, a server farm, a data center, a cloud computing resource, or any other computing resource capable of storing and/or providing access to a plurality of applications for smart sensors and other computing devices. The utility application store 102 may include one or more processors 500 and memory 502. The memory 502 may include an application repository 104 storing an application index 504 and multiple applications 506(1), 506(2), 506(3), . . . 506(M) (collectively referred to as "applications 506") that are available from the utility application store 102, where M is any integer greater than or equal to 1. The application index 504 may include a listing of the applications 506 by topic, category, feature, product, or the like. The application repository 104 may also include metadata associated with the applications 506. By way of example and not limitation, the metadata may include, for each application, a category of the application (e.g., meter application, consumer application, other application, etc.), a version of the application, compatibility of the application with specific software and/or hardware, keywords associated with the applications, brief descriptions of the application, feature specifications of the application, or the like.
The memory 502 may also include a plurality of modules to implement various functions of the utility application store 102. For instance, an application store interface module 508 may be configured to generate a graphical user interface (e.g., interface 116) presenting the applications that are available in the application repository 104. The application store interface module 508 may make the interface available to one or more users by, for example, publishing the interface to a website accessible by a browser of a client computing device. When accessed by the computing device, the application store interface module 508 may serve the interface to the computing device displaying the multiple applications that are available along with controls usable to request installation or activation of the applications.
A verification module 510 may be configured to verify compatibility of one or more applications with one or more computing devices. In response to receiving a request to install or activate an application, a verification module 510 may verify that the requested application is compatible with each of the devices specified in the request. The verification module 510 may make this verification with reference to a device compatibility index 512, the application index (if present), and/or metadata stored in the application repository 104. For instance, the request may include an identifier for each of the devices on which the application is to be installed. In that case, verifying that a compatible version of the application exists for the devices comprises determining, from the identifier of each of the one or more devices, a type of each of the one or more devices, and determining whether a compatible version of the application exists for the determined type of each of the one or more devices. Alternatively, the type of the devices may be specified directly in the request (e.g., each of the device types specified in the payment interface 200).
Additionally or alternatively, if the utility application store 102 has access to information about the devices in the utility communication network, it may make this compatibility verification prior to presenting the available applications to the user. For instance, the memory 502 may store a topology module 514 that is in communication with the utility supplier 110. The topology module 514 may maintain information about the device types, current software versions, and/or locations of devices in the utility supplier's communication network. Alternatively, the memory 502 may maintain a record of all device types for which the user has previously purchased applications, and the versions of applications purchased. In either case, the user may be presented only with applications that are compatible with devices in the utility's own communication network.
A provisioning module 516 may be configured to prepare the application or credential for transmission to the one or more smart sensors or other devices by, for example, segmenting the application or credential into multiple segments, compressing the application or credential, and/or encrypting the application or credential. The provisioning module 516 may also generate credentials (e.g., based on a private key, a random password generator, or the like), or may provide existing credentials (e.g., passwords or certificates) to activate the requested application.
A payment module 518 may be configured to provide a payment interface (e.g., payment interfaces 200, 300, 400, etc.) usable to allow a user to purchase an application. The payment module 518 may also be configured to receive and process payment information, generate appropriate billing information, and/or update user account information based on the received payments.
Once an application has been purchased, a control module 520 may cause transmission of the application or credential according to the delivery method specified in the request (if any). For instance, in the case of a meter application, the control module 520 may initiate transmission directly to the one or more smart sensors via the utility communication network. Alternatively, the control module 520 may initiate transmission to the utility supplier 110 or any other specified destination for subsequent distribution to the individual smart sensors. Initiating transmission may include the application store performing the transmission, or the application store instructing another computing device (e.g., a distribution computing device not shown) to perform the transmission.
In some embodiments, the memory 502 may also include a notification module 522 configured to provide notification of the availability of applications for utility meters or other smart sensors, consumer computing devices, and/or utility back office computing devices. Additional details of the notification module 522 and its functionality are described below in the section entitled "Example Notification of Application Availability."
The utility application store 102 also includes one or more communication connections 524 to enable the utility application store 102 to communicate with other computing devices locally or over the network 112. Examples of communication connections include, without limitation, power line communication (PLC) connections, Ethernet or other wired network connections, cellular communication connections, RF communication connections, or the like. As such, the utility application store 102 also includes any ancillary hardware, modules, and/or interfaces associated with or needed for the operation of the particular communication connections.
Example Smart Sensor
FIG. 6 is a diagram showing example details of an individual smart sensor 106. As discussed above, the smart sensor may comprise a smart utility meter (e.g., electricity meter, water meter, or gas meter), a relay, a repeater, a smart grid router, a transformer, or any other utility network computing device. The smart sensor 106 may be configured for interaction with the utility application store 102, the utility supplier 110, as well as potentially other computing devices (e.g., consumer computing devices, utility network computing devices, web services, and the like). As noted above, in some examples, the smart sensor 106 may comprise a smart utility meter.
As shown in the example of FIG. 6, the smart sensor 106 may include a radio 602 and a processing unit 604. The radio 602 may provide two-way RF communication with other smart sensors 106 in the autonomous routing area 108 and/or other computing devices via the network 112. The processing unit 604 may include one or more processors 606 and memory 608 and/or other hardware device(s), such as an application specific integrated circuit (ASIC), a gate array or other hardware-based logic device. The memory 608 may include an operating system (OS) 610 and one or more applications. In the illustrated example, the memory 608 includes a first application 612 (e.g., a Voltage Quality Application to monitor voltage quality of service provided to the smart sensor 106), and a second application 614 (e.g., a Home Area Network Application allowing the smart sensor 106 to interface with a home area network hub installed in a user's home).
In embodiments in which the smart sensor 106 comprises a utility meter, the smart sensor 106 may include a metrology module 616 configured to receive consumption data of a resource (e.g., electricity, water, or gas) at a site of the meter. The metrology module 616 may report the consumption data to the central office 110 by RF transmission via the radio 602. The consumption data may be formatted and/or packetized in a manner or protocol for transmission over the utility communication network.
In addition to the radio 602, smart sensor 106 may include one or more other network connections 620, such as power line communications (PLC) connections, Ethernet or other wired network connections, RF connections, cellular communication connections, or the like. As such, the smart sensor 106 also includes any ancillary hardware, modules, and/or interfaces associated with or needed for the operation of the particular network connections.
The OS 610, the first application 612, the second application 614, the metrology module 616, and even software aspects of the radio 602 are all examples of applications that may be executable by the smart sensor 106. Such applications may be installed on the smart sensor 106 by/from the utility application store 102. The memory may also include a portion of a distributed application 618, other or related portions of which are executable by other computing devices (e.g., the utility application store 102, central office 110, other smart sensors 106, or other web services) to perform common or complimentary functions. Additional details of distributed applications are described below in the section entitled "Example Distributed Applications."
Memories 502 and 608 are shown to include software functionality configured as one or more "modules." However, the modules are intended to represent example divisions of the software for purposes of discussion, and are not intended to represent any type of requirement or required method, manner or necessary organization. Accordingly, while various "modules" are discussed, their functionality and/or similar functionality could be arranged differently (e.g., combined into a fewer number of modules, broken into a larger number of modules, etc.).
While detailed examples of certain computing devices (e.g., utility application store 102 and smart sensors 106) are described above, it should be understood that even those computing devices not described in detail may include one or more processors and memory storing processor executable instructions to implement the functionalities they are described as performing. Certain computing devices may additionally or alternatively include one or more hardware components (e.g., application specific integrated circuits, field programmable gate arrays, systems on a chip, and the like) to implement some or all of the functionalities they are described as performing.
The various memories described herein are examples of computer-readable media and may take the form of volatile memory, such as random access memory (RAM) and/or non-volatile memory, such as read only memory (ROM) or flash RAM. Computer-readable media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data for execution by one or more processors of a computing device. Examples of computer-readable media include, but are not limited to, phase change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. As defined herein, computer-readable media does not include communication media, such as modulated data signals and carrier waves.
Example Methods of Installing or Activating Applications
FIG. 7 is a flowchart which illustrates an example flow of operations 700 that may be performed by a first computing resource, such as utility application store 102, to facilitate installation and/or activation of an application on one or more utility meters or other smart sensors. The example flow of operations 700 is described in the context of the example of architecture 100 and with reference to the devices illustrated in FIG. 1. However, the flow of operations 700 is not limited to use with the architecture 100 and devices of FIG. 1 and may be implemented using other architectures and devices.
The flow of operations 700 may begin, at block 702, with the first computing resource serving an interface displaying multiple applications that are available for download by a second computing resource. In some examples, the first computing resource may be administered by a first entity (e.g., an application store hosting company) and the second computing resource may be administered by a second entity (e.g., a utility supplier, consumer, etc.) that is different than the first entity. In one example, the first computing resource comprises one or more servers of an application store (e.g., utility application store 102) having multiple applications that are available for installation or activation, and the second computing resource comprises a personal computer, a mobile device, a utility meter reading device, or other computing device (e.g., other computing device 114). The one or more smart sensors (e.g., smart sensors 106) may include a predefined subset of a plurality of smart sensors in a utility supplier's communication network, such as all smart sensors of a certain type, all smart sensors within a geographical area, etc. In some embodiments, at least some of the smart sensors may include one or more smart utility meters.
At 704, the first computing resource (e.g., the utility application store 102) receives a request from the second computing resource (e.g., computing device 114) to install or activate an application on one or more smart sensors (e.g., one or more of smart sensors 106). In one example, the request may be in the form of selection of the "install/activate" control of the interface 116. In some instances, the application may include instructions to access metrology data collected by the smart sensor (e.g., to process the metrology data, to make the metrology data available, etc.).
The request may include an identifier for each of the one or more smart sensors. In some instances, the identifier may be a serial number or unique identifier of individual smart sensors. However, in other instances, the identifier may be a model name or number, a class or category of devices, or other indicator of device type. At 706, the first computing resource (e.g., utility application store 102) configures the application or a credential to activate the application for the one or more smart sensors based at least in part on the request. Configuring the application or credential for the one or more smart sensors may include, for example, determining, from the identifier of each of the one or more smart sensors, a compatible version of the application for each of the one or more smart sensors.
At 708, the first computing resource (e.g., utility application store 102) may present a price for installation or activation of the application on the one or more smart sensors. The price may be presented in the form, or as part, of a purchase interface (e.g., purchase interfaces 200, 300, or 400). At 710, the first computing resource receives payment or agreement to pay for the installation or activation of the application on the one or more smart sensors. In one example, payment or agreement to pay may be in the form of selection of a "Buy Now" or other purchase control on the purchase interface.
At 712, the first computing resource (e.g., utility application store 102) may prepare the application or credential for transmission to the one or more smart sensors by segmenting the application or credential into multiple segments, compressing the application or credential, and/or encrypting the application or credential. The specific segmenting, compressing, and/or encrypting operations may vary depending on the nature and requirements of the utility communication network and the selected delivery method. For instance, if the application or credential is to be delivered to a utility supplier, fewer preparation operations may be needed than if the application or credential is to be delivered to the individual smart sensors.
At 714, the first computing resource (e.g., utility application store 102) determines how to deliver the application or credential (e.g., based on a delivery method specified in the request, based on a default delivery method, a delivery method previously specified by the user, etc.) and causes transmission of the application (or the credential to activate the application) to the one or more smart sensors. Depending on the method of delivery specified in the request (if any), causing transmission of the application or the credential to the one or more smart sensors may include, at 716, transmitting the application or the credential to the one or more smart sensors directly, and/or, at 718, transmitting the application or credential to the second computing resource (e.g., computing device 114) or to another computing resource (e.g., utility supplier 110) for distribution to the one or more smart sensors. In one example, transmitting the application or the credential to the one or more smart sensors comprises sending a message including the application or the credential to the one or more smart sensors via a utility communication network.
Example Notification of Application Availability
FIG. 8 is a diagram illustrating another example networked environment or architecture 800, which is usable to provide notifications of the existence of applications that may be of interest to various users. For instance, the architecture 800 enables notification of users when applications are available for the users' devices, or when applications are installed on the users' devices.
Like the architecture 100 of FIG. 1, architecture 800 includes the utility application store 102 having the repository 104 of applications available for installation on one or more utility meters or other smart sensors 106. The architecture also includes the utility supplier 110 in communication with the utility application store 102 and the smart sensors 106 via the network 112. However, the architecture 800 of this example also includes a consumer computing device 802, such as a personal computer or mobile device, and one or more other services 804. The other services represent one or more computing devices and may include web services that provide data (e.g., weather services, sensor networks, resource pricing data, current resource demand data, etc.) or computing resources (e.g., cloud storage or processing resources, web hosting resources, analytic processing, calculations, validation, authentication, payment processing, etc.). Other services may also include retailers, manufacturers, suppliers, software developers, municipalities, or other entities that may provide or desire notice of the existence of applications for various computing devices.
The app store repository 104 may include applications 506(1)-506(M), some of which may be designed to run on smart sensors and some of which may be designed to run on one or more servers of the utility supplier 110, consumer computing devices 114, or other computing devices or "other services" 804. The applications may have been developed by an entity administering the application store 102, one or more utility meter or hardware manufacturers, one or more utility suppliers, one or more independent software vendors, and/or one or more providers of the other services 804.
When the utility application store 102 receives a request from a computing device to install an application, the utility application store 102 may be configured to notify the requesting computing device of the existence of one or more complimentary applications. Additionally or alternatively, the utility application store 102 may be configured to notify other computing devices of the existence of the requested application and/or the complimentary application(s). A complimentary application is one that is somehow related or associated with another application. In some instances, a complimentary application may be configured to receive and/or provide additional functionality and/or data to/from another application (e.g., an application for a utility meter that provides data to populate a complimentary smartphone application). In other instances, a complimentary application may be one that includes a feature similar or supplemental to a feature included in another application (e.g., an application that allows a utility meter to connect to a home area network via WiFi may be considered to be complimentary to an application that allows a utility meter to function as a WiFi hotspot).
Referring back to FIG. 8, some of the applications stored in the application repository 104 are designated as being complimentary applications (e.g., applications 506(1), 506(2), and 506(3)). This complimentary designation may be made in, for example, the application index 504 or metadata associated with the applications 506. Thus, upon receiving a request from a computing device for a first application 506(1), the utility application store 102 may notify one or more other computing devices of the existence of complimentary applications 506(2) and 506(3). Additionally or alternatively, the utility application store 102 may notify the one or more other computing devices of the existence of the first application 506(1) and/or that the first application 506(1) has been installed on the first computing device.
FIGS. 9A, 9B, and 9C illustrate three example notifications that may be provided informing various users of the existence of applications.
FIG. 9A illustrates a notification 900A that may be sent to a utility supplier informing the utility supplier that one or more of their customers have installed an application, "How Green Can You Be?—Utility Management Application," on their personal computer or mobile device. The notification 900A also informs the utility supplier that a complimentary application is available for their customer's utility meters that can enhance the application the customers have installed. For instance, the application for the utility meter may include an application programming interface (API) which the customers' application can call to obtain certain additional data or exercise certain functionality of the utility meter that would not otherwise be available to the customers.
In the illustrated example, the notification 900A also includes an indication of two specific customers, Bob Jones and Cindy Johnson, that have recently installed the application and a total number of customers that have installed the application. This information is shown underlined in FIG. 9A to indicate that additional information is available by, for example, selecting the underlined text. By selecting the underlined text, the utility supplier may obtain additional information about the specific customers, details of the installations and devices on which the application was installed, the number of installations, the times of installations, and the like. By providing this information, the utility supplier is able to determine how many customers would benefit from the installation of the meter application.
The notification 900A also includes a price field indicating a price of the application and a preview control allowing the user to preview the application prior to purchasing. The preview control may allow the user to link to screenshots, description, and/or demonstrations of the application. Additionally or alternatively, the preview control may allow the user to install a demo or trial version of the application. A purchase control 902, such the illustrated "Buy Now" button, may allow the user to purchase and install the application quickly and easily directly from the notification. Additionally or alternatively, the notification may include a link 904 to the utility application store 102 in order to install or activate the application.
FIG. 9B illustrates a notification 900B that may be sent to a customer, informing them that their utility supplier has installed an application (e.g., "OS 2.0: Power Quality Add-On") on the customer's utility meter. The notification also informs the customer that a complimentary application is available for the customer's personal computer or mobile device that can provide the customer with additional information about their utility consumption that was not previously available. As in the previous example, the notification 900B also includes a price field and a preview control.
In some instances, such as when the user accesses the notification from a personal computer, the customer may be able to purchase, download, and install the application directly from the notification to the personal computer. However, in other instances, such as when the user accesses the notification from smartphone or other mobile device, the user may need to navigate to an application store for the specific smartphone or mobile device (e.g., the iTunes® store or the Android® store). Accordingly, the notification 900B may include a link 904 to one or more device- or platform-specific application stores from which the application can be obtained.
FIG. 9C illustrates a notification 900C that may be sent to a utility supplier that has installed an application, "OS 2.0: Power Quality Add-On," on one or more utility meters. The notification also informs the utility supplier that a complimentary application is available for their central office servers that can make use of the data and functionality of the meter applications to optimize their power distribution network. As in the previous examples, the notification 900C also includes a price field and a preview control.
As in the example of FIG. 9A above, the notification 900C may include a purchase control 902, which may allow the user to purchase and install the application quickly and easily directly from the notification. Additionally or alternatively, the notification 900C may include a link 904 to the utility application store 102 in order to install or activate the application.
The foregoing examples envision that the customers and utility suppliers would each pay any applicable price for installing their own respective applications. In other embodiments, the utility supplier may subsidize the consumer application, or the consumers may subsidize installation of the application on their meters. That is, the meter application may be priced such that by paying for and installing the meter application, the consumer application may be offered to the customer for free and vice versa.
FIG. 10 is a signal flow diagram which illustrates an example flow of operations 1000 that may be used to provide notification of the existence of applications for installation on one or more computing devices. The example flow of operations 1000 is described in the context of the example of architecture 800 and with reference to the devices illustrated in FIG. 8. However, the flow of operations 1000 is not limited to use with the architecture 800 and devices of FIG. 8 and may be implemented using other architectures and devices.
The flow of operations 1000 may begin, at block 1002, when a first computing device (e.g., utility application store 102) receives a request to install a first application on a second computing device (e.g., consumer device 802). At 1004, the first computing device may transmit the application, a credential to activate the application, or a link to download the application from another site (e.g., a client specific application store). The application, credential, and/or link may be transmitted to the requesting computing device (e.g., consumer device 802) or to another computing device (e.g., smart sensor 106).
The first computing device may also, at 1006, identify a second application, which is associated with the first application and is configured for execution by a third computing device (e.g., smart sensor 106, utility supplier 110, or another computing device not shown) of a type other than the second computing device. At 1008, the first computing device sends a notification of availability of the second application to one or more computing devices (e.g., consumer device 802, computing device 114, utility supplier 110, or another computing device not shown).
In some examples, the associated second application may comprise a complimentary application that is configured to receive and/or provide additional functionality and/or data to the first application. That is, the first application may be configured to interface with the second application to employ functionality and/or data of the second application, or vice versa.
In the illustrated example, the first computing device comprises utility application store 102, the second computing device comprises consumer device 802, and the third computing device comprises smart sensor 106. However, in other examples, the first, second, and third computing devices may comprise other computing devices. For instance, the third computing device may comprise other types of utility network computing device associated with a user or user account. A smart sensor is one example of a utility network computing device, but other examples of utility network computing devices include, without limitation, an electric vehicle charging station, a distributed generation source, a home area network device, a transformer, an appliance, an inverter, or the like. In another example, the second computing device may comprise a utility computing device (e.g., computing device 114) and may request installation of an application on a customer's utility meter. Upon receiving the request, the utility application store 102 may send a notification to the consumer's smartphone (i.e., the third computing device), informing the user of the existence of a complimentary application for the user's smartphone. In yet another example, a computing device other than utility application store 102 may provide the notification of complimentary applications.
In some examples, the notification may include a control usable to purchase the second application, a control usable to cause installation of the second application on the third computing device, and/or a control usable to access an application store from which the first application is installable by computing device. FIGS. 9A, 9B, and 9C illustrate three example notifications that may be provided at operation 1008. However, numerous other notifications may be used to notify other computing devices or users of the existence of applications.
At 1010, any of the computing devices having received the notification may present the notification on a display of the computing device. In the illustrated example, only the computing device 114 is shown as presenting the notification. However, the other computing devices receiving the notification (i.e., consumer device 802 and/or utility supplier 110) may additionally or alternatively present the notification. Subsequently, at 1012, the computing device(s) displaying the notification may receive user selection of a control of the notification presented on the display. Responsive to receiving the selection of the control, at 1014, the computing device(s) (e.g., computing device 114) may request that the first computing device (e.g., utility application store 102) transmit the second application to the computing device (computing device 114) or to another computing device (e.g., smart sensor 106).
At 1016, the first computing device may transmit the second application, or a credential to activate the second application, to the requesting computing device or, as shown in FIG. 10, to a device specified by the requesting device (e.g., smart sensor 106).
The first computing device may also have, at 1006, identified a third (or subsequent) application, which is associated with the first and/or second applications and is configured for execution by a fourth computing device (e.g., utility supplier 110, or another computing device not shown). In that case, the notification displayed at 1010 may have included notification of the existence of both the second and third applications, and the selection of the control received at 1012 may have applied to both the second and third applications. Accordingly, the computing device(s) having displayed the notification (e.g., computing device 114) may, at 1018, additionally request that the first computing device (e.g., utility application store 102) transmit the third application to another computing device (e.g., utility supplier 110).
At 1020, the first computing device may transmit the third application, or a credential to activate the third application, to the device specified by the requesting device (e.g., utility supplier 110).
Example Distributed Applications
FIG. 11 is a diagram illustrating another example networked environment or architecture 1100, illustrating the use of distributed applications amongst multiple computing devices. For instance, the architecture 1100 enables the distribution of multiple portions of a distributed application, which is executable by multiple different devices. For instance, a first portion of the distributed application may configured for execution by a first computing device, while one or more additional portions of the distributed application may be configured for execution by one or more additional computing devices that are separate from the first computing device. The first portion of the distributed application may be configured to interface with the one or more additional portions of the distributed application and to employ functionality and/or data of the one or more additional portions of the distributed application.
In some examples, at least some of the multiple different computing devices comprise different types of devices and/or devices running different operating systems. In one example, the first computing device comprises a smart utility meter and the one or more additional computing devices comprise a utility server, a cloud computing resource, a personal computer, a mobile device, an electric vehicle charger, a distributed generation source, a home area network device, a transformer, an appliance, and/or an inverter. In a further example, a portion of the distributed application may operate on the smart utility meter, and may communicate with another portion of the application which operates on a personal computer or mobile device. The portion of the distributed application running on the smart utility meter may access utility consumption data, while the portion of the application running on the personal computer or mobile device may provide a user interface accessible by a consumer,
Like the architecture 800 of FIG. 8, architecture 1100 includes the utility application store 102 having the repository 104 of applications available for installation on one or more utility meters or other smart sensors 106. The architecture also includes the utility supplier 110, the consumer computing device 802, and the one or more other services 804 in communication with the utility application store 102 and the smart sensors 106 via the network 112.
However, in the architecture 1100, the application repository 104 of utility application store 102 includes applications 1102(1), 1102(2), 1102(3), 1102(4), . . . 1102(L) (collectively referred to as "applications 1102"), where L is any integer greater than or equal to 1. The applications 1102 include a subset of applications 1102(1)-1102(4) that together define a distributed application 1104. As such, the applications 1102(1)-1102(4) may be considered portions of the distributed application 1104. Each portion of the distributed application 1104 may be configured to perform certain operations independently. Additionally, each portion of the distributed application 1104 may also be configured to interface with one or more additional portions of the distributed application, and to employ functionality and/or data of the one or more additional portions of the distributed application.
The applications 1102(1)-1102(4) are also shown installed on multiple different devices of different types. For instance, application 1102(1), the first portion of the distributed application 1104, is installed on smart meter 106(1). Application 1102(2), the second portion of the distributed application 1104, is installed on consumer device 802. Application 1102(3), the third portion of the distributed application 1104, is installed on the utility supplier 110. And, application 1102(4), the fourth portion of the distributed application 1104, is installed on one of the other services 804. Each of these different devices, on which a portion of the distributed application 1104 runs, may comprise different hardware, different operating system, different software or versions of software, or the like. However, the various portions of the distributed application 1104 are able to interact with each other and leverage the data and/or processing capabilities of the other portions of the distributed application. In some examples, communication amongst the portions of the distributed application 1104 may be made possible by one or more application programming interfaces (APIs) presented by one or more portions of the distributed application that may be called by the other portions of the applications to implement certain functions and/or obtain certain data.
FIG. 12 illustrates a simple example of a distributed application 1104 that may be used to perform an operation of informing a customer of his or her electricity consumption. In this example, application 1102(2) executing on the customer device 802 may call APIs of applications 1102(1), 1102(3), and 1102(4). In response to receiving the API call, the application 1102(1) executing on the smart sensor may report current resource consumption data (e.g., electricity usage) of a site at which the smart sensor 106(1) is installed. Similarly, the application 1102(3) executing on the central office 110 may report historical average resource consumption data (e.g., electricity usage) of the customer or the site. The application 1102(3) may additionally or alternatively report consumption data for one or more peers of the customer (e.g., nearby customers, customers with similar consumption patterns, etc.). The application 1102(4) executing on the other services 804 may provide current resource pricing data, for example. The application 1102(2) may then display the data received from the other portions of the distributed application 1104 on a screen of the consumer device 802. Accordingly, the distributed application utilizes the user interface of the consumer device, the consumption data of the smart meter, the pricing or historical consumption information of the central office, and the weather or other information of the other services to provide a unique combination of information that could not readily be provided by a single source. In another example, a distributed application could advantageously provide information to the utility supplier.
FIG. 12 is but one simple example of a distributed application. Numerous other examples are possible using the concept of distributed applications. Several other non-limiting examples are described briefly below. In one example, a first portion of a distributed application may be configured to execute on a utility meter or other smart sensor to collect and process resource consumption data. Compared to other computing resources, the utility meter or smart sensor may be somewhat constrained in terms of memory and/or processing resources. The first portion of the distributed application running on the utility meter or smart sensor may be configured to offload certain processing operations to a second portion of the distributed application running on a computing device which has greater processing power, such as the utility supplier servers or a cloud computing resource. This offload of processing responsibilities may be implemented regularly or on an as needed basis.
In another example of a distributed application, a first portion of a demand response application may execute at the central office. The first portion of the demand response application may receive data from a second portion of the application that resides at a weather service and/or a third portion of the application that resides at an electricity distribution site. The data received from the second and third portions of the application may be used by the first portion to measure and predict resource demands. The first portion of the application may also communicate with a fourth portion of the application that resides on one or more utility meters, control points, or other smart sensors to regulate utility consumption at particular sites based on the measured and predicted resource demands.
FIG. 13 is a signal flow diagram which illustrates an example flow of operations 1300 that may represent the signal flow between devices executing portions of one or more distributed applications. The portions of the distributed application may be configured to run concurrently on the multiple computing devices. The example flow of operations 1300 is described in the context of the example of architecture 1100 and with reference to the devices illustrated in FIG. 11. However, the flow of operations 1300 is not limited to use with the architecture 1100 and devices of FIG. 11 and may be implemented using other architectures and devices.
The flow of operations 1300 may begin, at block 1302, when a first computing device, such as a utility meter or other smart sensor 106, performs a first portion of an operation (e.g., measuring resource consumption). At 1304, the first computing device communicates with a second portion of the distributed application installed at a remote computing resource to cause performance by the remote computing resource of a second portion of the operation. The communication may include a call to an API of the second portion of the distributed application or remote computing resource to cause the remote computing resource to provide data and/or perform a processing operation. The remote computing resource may comprise consumer device 802, utility supplier 110, other computing service 804, or any other computing resource. Some examples of other computing resources include, without limitation, a utility server, a cloud computing resource, a personal computer, a mobile device, an electric vehicle charger, a distributed generation source, a home area network device, a transformer, an appliance, or an inverter.
At 1306, the remote computing resource may perform the second portion of the operation. The second portion of the operation may include any of a wide range of operations. In several non-limiting examples, the second operation may comprise presenting information on a display or obtaining weather information, resource pricing information, resource demand information, resource supply information, demographic data, or validation data. Additionally or alternatively, the second portion of the operation may comprise performing a processing operation (e.g., an offloaded operation of the first portion of the distributed application).
At 1308, the first computing resource may receive a response from the remote computing resource. The response may include a result of performance of the second portion of the operation by the remote computing resource (e.g., the data retrieved by execution of the second portion of the distributed application, a processing result of execution of the second portion of the distributed application, etc.). In some examples, the result may include a call to an API of the first portion of the distributed application or to an operating system of the first computing resource. In some examples, the first portion of the distributed application may run concurrently with the second portion of the distributed application.
At 1310, the first computing resource may receive a request from the remote computing resource (or another remote computing resource) to execute the first portion of the distributed application to perform a third part of the operation. The request may call an API of the first portion of the distributed application or an API of an operating system of the first computing resource. In one example, the third operation may comprise querying a memory or register of the first computing resource (e.g., smart sensor) for one or more sensor readings stored in a memory or register of the first computing resource. In the case where the first computing resource comprises a utility meter, the sensor readings stored in memory of the first computing resource may comprise, for example, resource consumption readings from a metrology module of the first computing resource. Responsive to receiving the request, the first computing resource may, at 1312, execute the first portion of the distributed application to perform the third part of the operation. At 1314, the first computing resource may communicate a result of execution of the first application to the second portion of the distributed application installed at the remote computing resource. In examples in which the first computing resource comprises a utility meter the result may include resource consumption data associated with a site of the utility meter.
While FIG. 13 illustrates implementation of a distributed application across only two computing devices, the techniques described with reference to FIG. 13 can readily be extended to distributed applications running across three, four, or even more computing devices.
The flows of operations illustrated in FIGS. 7, 10, and 13 are illustrated as collections of blocks and/or arrows representing sequences of operations that can be implemented in hardware, software, firmware, or a combination thereof. The order in which the blocks are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order to implement one or more methods, or alternate methods. Additionally, individual operations may be omitted from the flow of operations without departing from the spirit and scope of the subject matter described herein. In the context of software, the blocks represent computer-readable instructions that, when executed by one or more processors, perform the recited operations. In the context of hardware, the blocks may represent one or more circuits (e.g., application specific integrated circuits—ASICs) configured to execute the recited operations.
Although the application describes embodiments having specific structural features and/or methodological acts, it is to be understood that the claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are merely illustrative some embodiments that fall within the scope of the claims of the application.
1. An application store system comprising:
memory coupled to the one or more processors, the memory storing instructions that are executable by the one or more processors to configure the application store to:
receive a request to install or activate a distributed application on a first device, the first device comprising a smart utility meter and the request including a serial number or a unique identifier of the smart utility meter;
determine a compatible version of the distributed application based at least in part on the serial number or the unique identifier of the smart utility meter;
provide a first portion of the compatible version of the distributed application to the first computing device for execution by the first computing device;
identify, by the one or more processors, a second portion of the compatible version of the distributed application based on metadata associated with the first portion of the compatible version of the distributed application or based on an application index accessible by the one or more processors;
provide the second portion of the compatible version of the distributed application to a second computing device separate from the first computing device for execution by the second computing device, the second computing device comprising a personal computer and/or mobile device of a user associated with the first computing device; and
relay a request from the second computing device to the first computing device, the request comprising a request for resource consumption data recorded by the first computing device.
2. The application store system of claim 1, wherein the first portion of the compatible version of the distributed application is configured to run on a first operating system, and the second portion of the compatible version of the distributed application is configured to run on a second operating system different than the first operating system.
3. The application store system of claim 1, wherein the first portion of the compatible version of the distributed application is configured to interface with the second portion of the compatible version of the distributed application and to employ functionality and/or data of the second portion of the compatible version of the distributed application.
4. The application store system of claim 1, further comprising a third portion of the compatible version of the distributed application stored in the memory, the third portion being configured for execution by a third computing device located remotely from the first computing device and the second computing device, the third computing device being under control of a separate entity from an entity in control of the first computing device or the second computing device.
5. The application store system of claim 4, wherein the third computing device comprises a utility supplier server or a device owned and operated by a utility supplier.
6. A smart utility meter comprising:
memory communicatively coupled to the one or more processors; and
a first portion of a distributed application stored in the memory and executable by the one or more processors, the smart utility meter being located at a first location and the first portion of the distributed application including instructions that are executable by the one or more processors to configure the smart utility meter to:
perform a first portion of an operation using a first operating system, the first portion of the operation comprising measuring a consumption of a resource;
communicate with a second portion of the distributed application installed at a remote computing resource having a second operating system that is different than the first operating system to cause performance by the remote computing resource of a second portion of the operation, the computing resource being located at a second location remote from the first location and the second portion of the operation comprising performing an offloaded processing operation of the first portion of the distributed application at the second portion of the distributed application via an application programming interface (API) presented by the first portion or the second portion; and
receive a response at the smart utility meter from the remote computing resource, the response including a result of the offloaded processing operation performed by the remote computing resource.
7. The smart utility meter of claim 6, wherein the second portion of the operation comprises performing a processing operation.
8. The smart utility meter of claim 6, wherein the API is presented by the second portion of the distributed application.
9. The smart utility meter of claim 6, wherein the API is presented by the first portion of the distributed application.
10. The smart utility meter of claim 6, wherein the response includes a call to an application programming interface of the first operating system of the smart utility meter.
11. The smart utility meter of claim 6, wherein the remote computing resource comprises a utility supplier server, a cloud computing resource, a personal computer, a mobile device, an electric vehicle charger, a distributed generation source, a home area network device, a transformer, an appliance, or an inverter.
12. The smart utility meter of claim 6, wherein the second portion of the operation comprises obtaining weather information, resource pricing information, resource demand information, resource supply information, demographic data, or validation data.
13. A method implemented at least in part by a smart utility meter configured with executable instructions, the method comprising:
executing a first application using a first operating system, local to the smart utility meter, to perform a first portion of an operation, the first portion of the operation comprising measuring a consumption of a resource;
sending, by the smart utility meter, a communication to a computing resource that is remote from the smart utility meter, the computing resource having a second operating system that is different than the first operating system and the communication causing execution of a second application by the computing resource to perform a second portion of the operation, the second portion of the operation comprising performing an offloaded processing operation of the first application at the second application via an application programming interface (API) presented by the first application or the second application; and
receiving a response at the smart utility meter from the computing resource, the response including a result of the offloaded processing operation performed by the second application.
14. The method of claim 13, wherein the result comprises at least one of data retrieved by execution of the second application or a processing result of execution of the second application.
15. The method of claim 13, wherein the first application and the second application comprise first and second portions of a distributed application configured to run concurrently on the smart utility meter and the computing resource.
16. The method of claim 13, wherein the API is presented by the second application.
17. The method of claim 13, wherein the API is presented by the first application.
18. The method of claim 13, wherein the response includes a call to an application programming interface of the first operating system of the smart utility meter.
19. The method of claim 13, wherein the computing resource comprises a utility supplier server, a cloud computing resource, a personal computer, a mobile device, an electric vehicle charger, a distributed generation source, a home area network device, a transformer, an appliance, or an inverter.
20. The method of claim 13, further comprising receiving a request from the computing source for consumption data measured by the smart utility meter, and in response to receiving the request, providing the consumption data to the computing resource.
21. The method of claim 13, further comprising receiving, via the API and from the second application of the computing resource, an instruction to perform a demand response operation.
22. A method implemented at least in part by an application store system, the method comprising:
receiving, at the application store, instructions to install multiple portions of a distributed application on multiple different devices, the instructions including a serial number or a unique identifier of at least one smart utility meter;
determining a compatible version of the distributed application based at least in part on the serial number or the unique identifier of the smart utility meter;
installing, in response to the instructions, a first portion of the compatible version of the distributed application onto a first computing device comprising the smart utility meter;
identifying, by the one or more processors, a second portion of the compatible version of the distributed application based on metadata associated with the first portion of the compatible version of the distributed application or based on an application index accessible by the one or more processors;
installing, in response to the instructions, the second portion of the compatible version of the distributed application onto a second computing device separate from the first computing device, the second computing device comprising a personal computer and/or mobile device of a user associated with the first computing device; and
relaying a request from the second computing device to the first computing device, the request comprising a request for resource consumption data recorded by the first computing device.
23. The method of claim 22, wherein the first portion of the compatible version of the distributed application is configured to run on a first operating system, and the second portion of the compatible version of the distributed application is configured to run on a second operating system different than the first operating system.
24. The method of claim 22, wherein the first portion of the compatible version of the distributed application is configured to interface with the second portion of the compatible version of the distributed application by calling one or more application programming interfaces to employ functionality and/or data of the second portion of the compatible version of the distributed application.
25. The method of claim 22, wherein the second computing device is operated by a separate entity from an entity operating the first computing device.
26. The method of claim 22, further comprising installing a third portion of the compatible version of the distributed application onto a third computing device located remotely from the first computing device and the second computing device.
US13/907,688 2013-05-31 2013-05-31 Distributed applications across platforms Active 2035-04-05 US10205769B2 (en)
US13/907,688 US10205769B2 (en) 2013-05-31 2013-05-31 Distributed applications across platforms
SG11201508853XA SG11201508853XA (en) 2013-05-31 2014-03-25 Distributed applications across platforms
AU2014272287A AU2014272287A1 (en) 2013-05-31 2014-03-25 Distributed applications across platforms
PCT/US2014/031783 WO2014193527A2 (en) 2013-05-31 2014-03-25 Distributed applications across platforms
EP14725837.0A EP3005133A4 (en) 2013-05-31 2014-03-25 Distributed applications across platforms
SG10201709438SA SG10201709438SA (en) 2013-05-31 2014-03-25 Distributed applications across platforms
JP2016516645A JP2016527596A (en) 2013-05-31 2014-03-25 Distributed application through the platform
HK16109740.6A HK1221784A1 (en) 2013-05-31 2016-08-15 Distributed applications across platforms
AU2017204167A AU2017204167B2 (en) 2013-05-31 2017-06-20 Distributed applications across platforms
US13/907,688 Active 2035-04-05 US10205769B2 (en) 2013-05-31 2013-05-31 Distributed applications across platforms
US (1) US10205769B2 (en)
SG (2) SG11201508853XA (en)
US9342288B2 (en) 2013-05-31 2016-05-17 Itron, Inc. Surfacing cross platform applications
US10205769B2 (en) * 2013-05-31 2019-02-12 Itron, Inc. Distributed applications across platforms
CN104636140B (en) * 2015-01-29 2018-05-29 小米科技有限责任公司 Firmware compression method, firmware decompressing method and device
WO2003003200A1 (en) 2001-06-28 2003-01-09 Daimlerchrysler Ag Method for transmitting software modules
US20030076242A1 (en) 2001-09-25 2003-04-24 Burns Gordon R. Utility meter having computer network access for receiving an interpretive language program to implement new meter functionality
US20030084435A1 (en) * 2001-10-31 2003-05-01 Alan Messer Method and system for offloading execution and resources for resource-constrained networked devices
US20060248162A1 (en) 2005-04-27 2006-11-02 Sony Ericsson Mobile Communcations Japan, Inc. Software update system and software update manage
JP2007502560A (en) 2003-08-15 2007-02-08 ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニーBritish Telecommunications Public Limited Company System and method for selecting a data provider
US20070169075A1 (en) * 2003-09-05 2007-07-19 David Lill Synchronizing and controlling software downloads, such as for utility meter-reading data collection and processing
US7546595B1 (en) 2004-10-14 2009-06-09 Microsoft Corporation System and method of installing software updates in a computer networking environment
US20090222828A1 (en) 2008-02-28 2009-09-03 Alcatel-Lucent Via The Electronic Patent Assignment System (Epas) Management platform and associated method for managing smart meters
JP2009217656A (en) 2008-03-12 2009-09-24 Hitachi Ltd Software update system in information apparatus
JP2009230422A (en) 2008-03-21 2009-10-08 Canon Inc License file issuing device, image processing apparatus, license file issuing method, and application installation method
JP2010015244A (en) 2008-07-01 2010-01-21 Brother Ind Ltd Install system and program
US20100042372A1 (en) 2008-08-12 2010-02-18 Square D Company Virtual metering
US20100169876A1 (en) 2008-12-31 2010-07-01 Square D Company Automatic firmware updates for intelligent electronic devices
US7783729B1 (en) 2004-03-19 2010-08-24 Single Touch Interactive, Inc. Transmitting mobile device data
US20100233961A1 (en) * 2009-03-16 2010-09-16 Apple Inc. Accessory and mobile computing device communication using an application communication protocol
WO2010111738A1 (en) 2009-03-31 2010-10-07 Freestyle Technology Pty Ltd A communications process and system associated with monitoring and controlling resource consumption
JP2011015521A (en) 2009-07-01 2011-01-20 Hitachi Ltd System and method for charge control of electric vehicle, server, and smart meter
US20110109472A1 (en) * 2009-07-30 2011-05-12 Google Inc. Resource monitoring on a mobile device
JP2011100464A (en) 2010-11-24 2011-05-19 Konica Minolta Business Technologies Inc Program update management apparatus
JP2011130597A (en) 2009-12-18 2011-06-30 Sony Corp Power control method, communication apparatus, and power control system
US20110270721A1 (en) * 2010-04-28 2011-11-03 Sap Ag Monitoring application interactions with enterprise systems
US20110307101A1 (en) * 2009-08-21 2011-12-15 Imes Kevin R Energy management system and method
US20120060152A1 (en) 2010-09-03 2012-03-08 Lsis Co., Ltd. System and method for firmware update of meter, watt hour meter with function of remote firmware update
JP2012059259A (en) 2010-09-03 2012-03-22 Ls Industrial Systems Co Ltd Firmware update system and method
US20120095878A1 (en) 2010-10-19 2012-04-19 Feldman Daniel I Integrated application store for a user device
JP2012079061A (en) 2010-09-30 2012-04-19 Toshiba Corp Communication apparatus and management method
JP2012113670A (en) 2010-11-29 2012-06-14 Renesas Electronics Corp Smart meter and meter reading system
US20120198099A1 (en) 2011-02-01 2012-08-02 Samsung Electronics Co., Ltd. Apparatus and method for providing application auto-install function in digital device
US20120198035A1 (en) 2011-01-31 2012-08-02 Alpine Electronics, Inc. Install system and install method
US20120206274A1 (en) 2011-02-11 2012-08-16 General Electric Company System for sending utility meter alerts
US20120245870A1 (en) 2011-03-22 2012-09-27 Kabushiki Kaisha Toshiba Data converting device, data processing device, power consumption processing system and computer program product
US20120290975A1 (en) 2011-05-11 2012-11-15 General Electric Company Feature license management system
WO2012154856A1 (en) 2011-05-09 2012-11-15 Google Inc. Identifying applications of interest based on application metadata
US20120317638A1 (en) 2011-06-07 2012-12-13 Research In Motion Limited Method and devices for managing permission requests to allow access to a computing resource
JP2012252552A (en) 2011-06-03 2012-12-20 Fujitsu Ltd Distribution method and distribution system
US20120326883A1 (en) 2011-06-22 2012-12-27 Itron Inc. Distributed meter data management
US20120330494A1 (en) 2011-05-26 2012-12-27 Hendrix Walter M Electric vehicle fleet charging system
US20130027217A1 (en) 2011-07-29 2013-01-31 General Electric Company Systems, Methods, and Apparatus for Automatically Configuring a Utility Meter
US20130046866A1 (en) 2011-08-16 2013-02-21 General Electric Company Meter access management system
US20130050498A1 (en) * 2011-08-31 2013-02-28 Next Future, LLC Analog utility meter reading
US20130101448A1 (en) 2011-10-24 2013-04-25 Denso Corporation Rotary machine and pump driving apparatus
US20130114502A1 (en) 2011-11-08 2013-05-09 Cisco Technology, Inc. Managed access to mobile endpoints
US8495621B2 (en) 2009-06-15 2013-07-23 Microsoft Corporation Catalog-based software component management
US20130205022A1 (en) 2011-10-04 2013-08-08 Electro Industries/Gauge Tech Systems and methods for processing meter information in a network of intelligent electronic devices
US20130339079A1 (en) * 2012-06-15 2013-12-19 International Business Machines Corporation Configurable resource policies
US20140040343A1 (en) 2005-09-15 2014-02-06 Peter Nickolov Globally Distributed Utility Computing Cloud
US20140173579A1 (en) 2012-12-17 2014-06-19 Itron, Inc. Utility node software/firmware update through a multi-type package
US20140173580A1 (en) 2012-12-17 2014-06-19 Itron, Inc. Utilizing a multi-system set configuration to update a utility node system set
US20140173586A1 (en) 2012-12-14 2014-06-19 Motorola Mobility Llc Systems and Methods for Managing Updates To Applications
US20140282482A1 (en) 2011-02-10 2014-09-18 Trilliant Networks, Inc. Device and method for facilitating secure communications over a cellular network
US20140349707A1 (en) 2012-02-01 2014-11-27 Young-ki Bang Gas detection system and method using smart phone
US20140359595A1 (en) 2013-05-31 2014-12-04 Itron, Inc. Surfacing cross platform applications
US20140358734A1 (en) 2013-05-31 2014-12-04 Itron, Inc. Utility application delivery platform
US20140358482A1 (en) * 2013-05-31 2014-12-04 Itron, Inc. Distributed applications across platforms
US20150227358A1 (en) 2014-02-10 2015-08-13 General Electric Company Utility meter intelligent firmware update system and method
US20160283284A1 (en) * 2015-03-27 2016-09-29 Mingqiu Sun Technologies for offloading and on-loading data for processor/coprocessor arrangements
US20160323727A1 (en) * 2015-04-30 2016-11-03 247Korea User protection method using smart phone case
US8713574B2 (en) * 2006-06-05 2014-04-29 International Business Machines Corporation Soft co-processors to provide a software service function off-load architecture in a multi-core processing environment
2014-03-25 SG SG11201508853XA patent/SG11201508853XA/en unknown
2014-03-25 SG SG10201709438SA patent/SG10201709438SA/en unknown
2014-03-25 EP EP14725837.0A patent/EP3005133A4/en not_active Withdrawn
2016-08-15 HK HK16109740.6A patent/HK1221784A1/en unknown
2017-06-20 AU AU2017204167A patent/AU2017204167B2/en active Active
JP2006502457A (en) 2001-10-31 2006-01-19 ヒューレット・パッカード・カンパニーHewlett−Packard Company Method and system for offloading the execution and resources of a device having constraints on networked resources
US6990662B2 (en) * 2001-10-31 2006-01-24 Hewlett-Packard Development Company, L.P. Method and system for offloading execution and resources for resource-constrained networked devices
JP2006309516A (en) 2005-04-28 2006-11-09 Sony Ericsson Mobilecommunications Japan Inc Software updating system and software update managing device
US8892699B2 (en) 2008-12-31 2014-11-18 Schneider Electric USA, Inc. Automatic firmware updates for intelligent electronic devices
JP2012059260A (en) 2010-09-03 2012-03-22 Ls Industrial Systems Co Ltd System and method for remote firmware update of energy meter, watthour meter with function of remote firmware update
JP2012159924A (en) 2011-01-31 2012-08-23 Alpine Electronics Inc Installation system
JP2012200094A (en) 2011-03-22 2012-10-18 Toshiba Corp Data conversion device, data processing device, and electricity consumption amount processing system and program
US8812979B2 (en) 2011-05-11 2014-08-19 General Electric Company Feature license management system
US9167100B2 (en) * 2012-02-01 2015-10-20 Young-ki Bang Gas detection system and method using smart phone
US9785899B2 (en) * 2012-06-15 2017-10-10 International Business Machines Corporation Configurable resource policies
US8924950B2 (en) 2012-12-17 2014-12-30 Itron, Inc. Utility node software/firmware update through a multi-type package
US8938730B2 (en) 2012-12-17 2015-01-20 Itron, Inc. Utilizing a multi-system set configuration to update a utility node system set
Non-Patent Citations (43)
"Windows 8, Microsoft Windows 8, Windows 8.Pro.Enterprise/Windows RT," Perfect Master, May 1, 2013, 5 pages.
Australian Office Action dated Jun. 16, 2017 for Australian patent application No. 2014272287, a counterpart foreign application of U.S. Appl. No. 13/907,688, 6 pages.
Australian Office Action dated May 23, 2018 for Australian patent application No. 2017204251, a counterpart foreign application of U.S. Appl. No. 13/907,625, 5 pages.
Australian Office Action dated May 8, 2018 for Australian Patent Application No. 2017204167, a counterpart foreign application of U.S. Appl. No. 13/907,688, 5 pages.
Australian Office Action dated Nov. 3, 2017 for Australian patent application No. 2016273927, a counterpart foreign application of U.S. Pat. No. 9,342,288, 3 pages.
Australian Office Action dated Oct. 14, 2016 for Australian patent application No. 2014272284, a counterpart foreign application of U.S. Appl. No. 13/907,625, 5 pages.
Barry, et. al., "Modern Embedded Computing", Morgan Kaufmann, Feb. 10, 2012, 103 pages.
Coulouris, et. al., "Distributed Systems: Concepts and Design (5th Edition)", May 7, 2011, Addison-Wesley, 696 pages.
European Office Action dated Aug. 28, 2018 for European Patent Application No. 14725836.2, a counterpart foreign application of U.S. Appl. No. 13/907,625, 4 pages.
European Office Action dated Aug. 8, 2018 for European Patent Application No. 14725837.0, a counterpart foreign application of U.S. Appl. No. 13/907,688, 9 pages.
European Office Action dated Dec. 21, 2017 for European patent application No. 147235836.2, a counterpart foreign application of U.S. Appl. No. 13/907,625, 4 pages.
European Office Action dated Jun. 5, 2018 for European patent application No. 14725836.2, a counterpart foreign application of U.S. Appl. No. 13/907,625, 3 pages.
European Office Action dated May 29, 2017 for European Patent Application No. 14725836.2, a counterpart foreign application of U.S. Appl. No. 13/907,625, 4 pages.
Extended European Search Report dated Nov. 24, 2016 for European patent application No. 14723225.0, 13 pages.
Extended European Search Report dated Nov. 30, 2016 for European Patent Application No. 14725837.0, 5 pages.
Japanese Office Action dated Apr. 3, 2018 for Japanese Patent Application No. 2016-516645, a counterpart foreign application of U.S. Appl. No. 13/907,688.
Japanese Office Action dated Dec. 27, 2016 for Japanese Patent Application No. 2016-516645, a counterpart foreign application of U.S. Appl. No. 13/907,688, 7 pages.
Japanese Office Action dated Jul. 4, 2017 for Japanese patent application No. 2016-516644, a counterpart foreing application of U.S. Pat. No. 9,342,288.
Japanese Office Action dated Jun. 27, 2017 for Japanese Patent Application No. 2016-516642, a counterpart foreign application of U.S. Appl. No. 13/907,625.
Japanese Office Action dated Oct. 11, 2016 for Japanese Patent Application No. 2016-516642, a counterpart foreign application of U.S. Appl. No. 13/907,625, 12 pages.
Japanese Office Action dated Oct. 18, 2016 for Japanese patent application No. 2016-516644, a counterpart foreign application of U.S. Pat. No. 9,342,288, 13 pages.
Japanese Office Action dated Sep. 12, 2017 for Japanese patent application No. 2016-516645, a counterpart foreign application of U.S. Appl. No. 13/907,688.
Knapp et al., "Applied Cyber Security and the Smart Grid: Implementing Security Controls into the Modern Power Infrastructure," Syngress, Apr. 19, 2013, 10 pages.
Mitsui, "Real-time energy-saving management for effective iPhone app corresponding demand monitoring equipment," Instrumentation Control Engineering, 2012, vol. 55, No. 2, 5 pages (English translation not currently available).
Office action for U.S. Appl. No. 13/907,625, dated Jan. 8, 2018, Sehgal et al. "Utility Application Delivery Platform", 12 pages.
Office action for U.S. Appl. No. 13/907,625, dated Jun. 16, 2017, Sehgal et al., "Utility Application Delivery Platform ", 11 pages.
Office action for U.S. Appl. No. 13/907,625, dated Jun. 4, 2018, Sehgal et al., "Utility Application Delivery Platform ", 13 pages.
Office Action for U.S. Appl. No. 13/907,665, dated Feb. 23, 2015, Arun Sehgal, "Surfacing Cross Platform Applications," 16 pages.
Office Action for U.S. Appl. No. 13/907,665, dated Sep. 11, 2015, Arun Sehgal, "Surfacing Cross Platform Applications," 17 pages.
Office Action for U.S. Appl. No. 15/090,488, dated Dec. 7, 2017, Arun Sehgal, "Surfacing Cross Platform Applications", 22 pages.
Office Action for U.S. Appl. No. 15/090,488, dated May 26, 2017, Arun Sehgal, "Surfacing Cross Platform Applications", 18 pages.
PCT Search Report and Written Opinion dated Apr. 2, 2015 for PCT application No. PCT/US2014/031783, 8 pages.
PCT Search Report and Written Opinion dated Aug. 29, 2014 for PCT Application No. PCT/US14/31777, 8 Pages.
PCT Search Report and Written Opinion dated Dec. 16, 2014 for PCT Application No. PCT/US14/31780, 9 Pages.
Tanenbaum et al., "Distributed Systems: Principles and Paradigms (2nd Edition)," Prentice Hall, Oct. 12, 2006, 86 pages.
Wikipedia: "Client-server model", Internet Article, May 29, 2013, Retrieved on Jul. 31, 2018 from the Internet: <URL:https://en.wikipedia.org/w/index.phptitle=Clientserver_model&oldid=557254009>, 3 pages.
Wikipedia: "Meter data management", retrieved on Jul. 31, 2018, from: <URL:https://en.wikipedia.org/w/index.php? title=Meter_data_management&oldid=513172850>, published on Sep. 17, 2012, 2 pages.
Wikipedia: "User interface", Internet Article, May 26, 2013, Retrieved on Jul. 31, 2018 from the Internet: <URL: https://en.wikipedia.org/w/index.php?title=User_interface&oldid=556804997>, 8 pages.
Yaghmour, et. al., "Building Embedded Linux Systems", O'Reilly, Aug. 25, 2008, 393 pages.
SG11201508853XA (en) 2015-11-27
SG10201709438SA (en) 2017-12-28
EP2965571B1 (en) 2018-04-11 Systems and methods for managing a distributed wireless power transfer network for electrical devices
US7826822B2 (en) 2010-11-02 Automated billing and distribution platform for application providers
CN105321064B (en) 2019-12-31 System and method for using wireless communication device as point of sale device
US7826421B2 (en) 2010-11-02 Application pod integration with automated mobile phone billing and distribution platform
US20140219118A1 (en) 2014-08-07 Systems and methods for display of supplemental content responsive to location
US20140365662A1 (en) 2014-12-11 Configuring cloud resources
US9967343B2 (en) 2018-05-08 Method for providing internet of things service
US20130132854A1 (en) 2013-05-23 Service Plan Design, User Interfaces, Application Programming Interfaces, and Device Management
US10462627B2 (en) 2019-10-29 Service plan design, user interfaces, application programming interfaces, and device management
KR20130020887A (en) 2013-03-04 Facilitating billing of embedded applications
US8145540B2 (en) 2012-03-27 Management platform and associated method for managing smart meters
US8380163B2 (en) 2013-02-19 Package billing for micro-transactions
US20130191217A1 (en) 2013-07-25 Dynamic Offers Subject To Mobile Device Holder Location
CA2706242A1 (en) 2009-03-19 System and method for providing network availability, performance, and localized content
US10192371B2 (en) 2019-01-29 System and method for a diagnostic software service
KR20060025565A (en) 2006-03-21 Method and corresponding equipment enabling billing for use of applications hosted by a wireless terminal
CN103797771A (en) 2014-05-14 Method and apparatus for m2m device subscription
KR20140009171A (en) 2014-01-22 System and method for providing user notifications
CN109167825A (en) 2019-01-08 The system and method for mobile device application are configured based on position
US20130060945A1 (en) 2013-03-07 Identifying services and associated capabilities in a networked computing environment
KR20120023474A (en) 2012-03-13 System and method for firmware update of household appliances, and meter
CN105612768A (en) 2016-05-25 Lightweight iot information model
CN101959179A (en) 2011-01-26 Method for providing mobile terminal application program, and server and mobile terminal
JP6162819B2 (en) 2017-07-12 Multi-screen application enablement and distribution services
Owner name: ITRON, INC., WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SEHGAL, ARUN;VOTAVA, SHANNON M.;ANGELIS, BRUCE;SIGNING DATES FROM 20130531 TO 20130923;REEL/FRAME:031302/0216
Owner name: WELLS FARGO, NATIONAL ASSOCIATION, NORTH CAROLINA
Free format text: SECURITY INTEREST;ASSIGNOR:ITRON, INC.;REEL/FRAME:036068/0231
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, NORTH CARO
Free format text: SECURITY INTEREST;ASSIGNORS:ITRON, INC.;ITRON NETWORKED SOLUTIONS, INC.;REEL/FRAME:045017/0893