Transmission of an application download via an encoded image identifying the authorized recipient

Disclosed are various embodiments for transmitting an application download from a donor to a recipient or recipients. The donor defines parameters for transferring the application download, including payment distribution between the donor and recipient, delivery method of a notification of the application download to the recipient, identification of the recipient or recipients, a deadline for downloading the application, a maximum number of recipients, and other data relevant to transmitting an application download. Parameters are encoded in an identifier that may be decoded by the recipient's client device or that may be imaged and sent to a server providing the application download service. Various embodiments display the encoded identifier to the recipient via electronic displays or printed mediums. The recipient scans or captures an image of the displayed encoded identifier using a client device.

BACKGROUND

DETAILED DESCRIPTION

Users download applications from application stores. An application store may have many applications available for download at a variety of prices. Users may seek to provide an application download to another user. For example, a user may seek to give a download of a tennis game application to a friend as a birthday gift. When gifting an application download, the user may define parameters for providing the application download to the other user. For example, a user may seek to gift an application download to another by paying for all or a portion of the application download, give a certain number of downloads to others, allow others to download an application for a certain amount of time, or otherwise define parameters for giving application downloads to others. The user may identify the recipient of the application download by identifying an account used by the recipient to download applications from the application store. Alternatively, or additionally, the user may identify the recipient by credentials of the device the recipient may use for downloading the application or in some other way that allows the application store providing the download to verify the identity of the recipient requesting the application download.

The recipient may be notified of the application download given by the donor in many ways. For example, an encoded identifier may be generated that contains information concerning the application purchase for a given recipient, the parameters associated with the download, and other information relevant to providing an application download to a recipient. The encoded identifier may comprise, for example, a barcode, such as a quick response (QR) code, an image, text, or some other identifier that may contain information regarding the application download gift. The encoded identifier may be transmitted to the recipient by many delivery methods. For example, a printed image of the encoded identifier may be provided to the recipient, such as in a greeting card, advertisement, or other printed medium. Alternatively, or additionally, an image of the encoded identifier may be electronically transmitted, such as through email, social media, electronic billboards, or another electronic display of the encoded identifier.

The recipient may obtain the application download from the encoded identifier in many ways. For example, the recipient may obtain the application download by capturing an image of the encoded identifier using a client device. This may be done by using the camera in the client device to capture an image of the encoded identifier. Alternatively, or additionally, an application on the client device may scan and capture an image of the encoded identifier. Capturing the image may occur automatically or upon an action by the client device. For example, while executing an application store application, if an encoded image is recognized automatically by the camera on the device, the encoded identifier may be automatically captured without executing the camera application. Alternatively, the client device may notify the user of the presence of the encoded identifier and capture the image upon direction to do so through a camera application, application store application, or other application executing on the client device. Once the image of the encoded identifier is obtained, the client device may decode the encoded identifier, the client device may send the image to a server from which it will download the application for the server to decode the image, or the client device may send the image to another device for decoding.

The client device may be authenticated based on the parameters identified by the donor of the application prior to initiating the application download. Parameters may define limitations on the recipient or recipients of the application download. For example, the client device credentials may be verified as matching the credentials of the intended recipient identified by the donor. As another example, if a maximum number of downloads of the application was identified in the parameters, then authorization may include comparing the total number of downloads thus far to the maximum number of authorized application downloads. If a deadline or timeframe for downloading the application was identified, then authorization may include comparing the timestamp of the authorization to the deadline or timeframe. Other parameters may be checked during authorization. If a client device is not authorized to download the application, the donor may be notified and given the opportunity to authorize the application download. If a client device is authorized to download the application, then the download may be automatically initiated or initiated upon some further action.

In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.

With reference toFIG. 1, shown is a networked environment100according to various embodiments. The networked environment100includes a computing environment103, a donor client device105, and a recipient client device107, which are in data communication with each other via a network109. The network109includes, for example, the Internet, intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, or other suitable networks, etc., or any combination of two or more such networks.

Various applications and/or other functionality may be executed in the computing environment103according to various embodiments. Also, various data is stored in a data store112that is accessible to the computing environment103. The data store112may be representative of a plurality of data stores112as can be appreciated. The data stored in the data store112, for example, is associated with the operation of the various applications and/or functional entities described below.

The components executed on the computing environment103, for example, include an electronic commerce system115, application transfer system116, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein. The electronic commerce system115is executed to facilitate the purchase of items over network109. The electronic commerce system115also performs various backend functions associated with the online presence of a merchant or electronic marketplace to facilitate the online purchase of items. For example, the electronic commerce system115may generate network pages or portions thereof that are provided to donor clients105and recipient clients107for the purposes of selecting items for purchase, rental, download, lease, or other forms of consumption. The electronic commerce system115executes an application store137for purchasing application downloads.

The application transfer system116is executed to generate and facilitate transmission of application downloads via encoded identifiers between donors and recipients. The application transfer system116also performs various backend functions associated with transferring application downloads. For example, the application transfer system116may obtain and modify applications121available in the application store137, user accounts124that identify parties to a transmission of an application download, and other data necessary for transferring application downloads.

The data stored in the data store112includes, for example, applications121, user accounts124, and potentially other data. Applications121includes data related to applications available for download. For instance, applications121may include game titles, prices, developers, ratings, or other data related to applications. User accounts124contain data related to users of the electronic commerce system115, the application store137, and the application transfer system116. Each user account124has log in information such as an email127and a password131, data related to a gift134of an application download, and/or other information.

The donor client105is representative of a plurality of client devices that may be coupled to the network109. The donor client105may comprise, for example, a processor-based system such as a computer system. Such a computer system may be embodied in the form of a desktop computer, a laptop computer, personal digital assistants, cellular telephones, smartphones, set-top boxes, music players, web pads, tablet computer systems, game consoles, electronic book readers, or other devices with like capability. The donor client105may include a display154. The display154may comprise, for example, one or more devices such as liquid crystal display154(LCD) display154, gas plasma-based flat panel display154, organic light emitting diode (OLED) display154, LCD projectors, or other types of display154devices, etc.

The donor client105may be configured to execute various applications such as a client application151and/or other applications. The client application151may be executed in a donor client105, for example, to access network content served up by the computing environment103and/or other servers, thereby rendering a user interface157on the display154. To this end, the client application151may comprise, for example, a browser, a dedicated application, etc., and the user interface157may comprise a network page, an application screen, etc. The donor client105may be configured to execute applications beyond the client application151such as, for example, email applications, social networking applications, word processors, spreadsheets, and/or other applications.

The recipient client107is representative of a plurality of client devices that may be coupled to the network109. The recipient client107may comprise, for example, a processor-based system such as a computer system. Such a computer system may be embodied in the form of a desktop computer, a laptop computer, personal digital assistants, cellular telephones, smartphones, set-top boxes, music players, web pads, tablet computer systems, game consoles, electronic book readers, or other devices with like capability. The recipient client107may include a display164. The display164may comprise, for example, one or more devices such as liquid crystal display164(LCD) display164, gas plasma-based flat panel display164, organic light emitting diode (OLED) display164, LCD projectors, or other types of display164devices, etc.

The recipient client107may be configured to execute various applications such as a client application161and/or other applications. The client application161may be executed in a recipient client107, for example, to access network content served up by the computing environment103and/or other servers, thereby rendering a user interface167on the display164. To this end, the client application161may comprise, for example, a browser, a dedicated application, etc., and the user interface167may comprise a network page, an application screen, etc. The recipient client107may be configured to execute applications beyond the client application161such as, for example, email applications, social networking applications, word processors, spreadsheets, and/or other applications.

Next, a general description of the operation of the various components of the networked environment100is provided. To begin, a donor at a donor client105may access the application store137in the electronic commerce system115through one or more user interfaces157rendered from content generated at least in part by an electronic commerce system115and sent across the network109to be rendered for display154by a client application151. A donor may be an individual, a manufacturer, an application developer, an advertiser, or other entity seeking to donate application downloads to one or more recipients. In the application store137, the donor may select an application download to purchase for a third party.

Then, the donor may select parameters for giving the application download to one or more others. For example, the donor may select parameters related to the recipient or recipients of the application download. These parameters may include authentication credentials, such as an identifier of a specific recipient (e.g., an email address, name, or other unique identifier), or thresholds related to how many application downloads may be done or a deadline for downloading the application. Other parameters may include payment of a portion or all of the cost of the application download. Parameters may describe a delivery method for notifying the recipient of the application download. For example, the delivery method may be an electronic display or printed medium depicting an encoded identifier that may be scanned by the recipient's client device. Alternatively, or additionally, parameters may be automatically identified.

Continuing the non-limiting example, after the donor has selected parameters, the application transfer system116generates an encoded identifier for delivery to the recipient. The encoded identifier may be any image, text, diagram, or other symbol that may embody the parameters needed for a recipient to retrieve the application download. For example, the encoded identifier may be a barcode, such as a QR code, or other symbol or text that may be scanned and decoded.

The application transfer system116then initiates providing the encoded identifier to the recipient via the deliver method identified by the donor. This may be done by electronic display, electronic message, or printed medium. For example, an electronic image of the encoded identifier may be electronically messaged to the recipient via email, simple message service (SMS), or other system. In various embodiments, the electronic image may be displayed on an electronic display, such as a digital billboard. The printed medium may be delivered to the recipient via, for example, a greeting card, advertisement, or other method of delivering a printed form of the encoded identifier.

Continuing the non-limiting example, the recipient at a recipient client107obtains the application download by using a client application161to capture an image of the encoded identifier. For example, the recipient client application161may execute a client application161to capture an image of the encoded image that may be analyzed to decode the data in the encoded identifier. In various embodiments, other client applications161may be executed to obtain an image of the encoded image. For example, an application store application may be executed to automatically obtain an image of the encoded identifier through the camera on the device. Another embodiment may involve an email client application161executed on the recipient client107that scans the image from the email when the email is opened in the email client application161. The image may be obtained automatically or upon some indication through a user interface167interacting with the client application161.

The image of the encoded identifier may be decoded by a client application161and the decoded data sent across the network109to the application transfer system116. Alternatively, the image of the encoded identifier captured by the recipient client107may be transmitted across the network109to the application transfer system116for decoding.

Continuing the non-limiting example, the application transfer system116authenticates the recipient client107. Authentication may involve verifying that many of the parameters are satisfied. In various embodiments, where a recipient has been identified by the donor, the recipient may be authenticated by verifying that the recipient has logged into the identified account on the recipient client107. Where a threshold maximum number of application downloads or a threshold deadline for obtaining the application download was identified, authentication may involve comparing the total number of application downloads obtained to the threshold maximum or the timestamp of the authentication to the threshold deadline or download timeframe. When authorization fails, the application transfer system116may contact the donor client105for authorization or transmit an error message indicating a failed authorization to the recipient client107. When authorization succeeds, the application transfer system116initiates a download of the application to the recipient client107.

Referring next toFIG. 2A, shown is one example of a user interface157(FIG. 1), denoted herein as157a, rendered by a client application151(FIG. 1) executed in a donor client105(FIG. 1) in the networked environment100(FIG. 1). The user interface157aincludes an application store network page211for browsing application downloads214and defining parameters221for transmitting the application download to another. A donor at a donor client105selects an application download214. Here, the donor is an individual. Alternatively, the donor may be an application distributor, application developer, advertisement entity, a promotions entity, or other entity. Here, the donor has selected the Crazy Taxi Driver application download214. The donor has selected via a transaction type pick list217to transmit the application download as a gift to an individual. Alternatively, the donor may have selected to allow a threshold maximum number of application downloads for multiple recipients or to allow application downloads until a threshold deadline. The donor then defined parameters221including the recipient's Liz Smith and the recipient's identifier account liz@mail.com. The donor selected to email the application download to the recipient. Finally, the donor defined the payment distribution parameter221to be $0 charged to the recipient. Once the parameters are defined, the donor selects generate barcode224to generate the encoded identifier for transmitting to the recipient. Alternatively, another symbol, text, or other encoded identifier may be generated. Because the donor defined the payment distribution to charge nothing to the recipient, the donor will pay the $1.99 owed for the application download through a checkout pipeline. Alternatively, the donor may define another payment distribution, such that the recipient will pay a portion of the $1.99.

Turning now toFIG. 2B, shown is one example of a user interface157(FIG. 1), denoted herein as157b, rendered by a client application151(FIG. 1) executed in a recipient client107(FIG. 1) depicted on a display154, denoted herein as154a, in the networked environment100(FIG. 1). The user interface157bincludes an email network page229for receiving email. The network page211depicts a message informing the recipient of the application download that was transmitted to a recipient client107from the donor231. Also depicted inFIG. 2Bis another example of a user interface157, denoted herein as157c, rendered by a client application151executed in a recipient client107depicted on a display164, denoted herein as164b, in the networked environment100(FIG. 1). The user interface167adepicts a camera client application161capturing an image236of the QR code. To obtain the application download, the recipient client107captures an image of the QR code234shown on the display164awith the camera238on the recipient client107. The display164amay be other than a monitor, such as, the display of a smartphone, digital billboard, or other device. The resulting image is decoded, either by the recipient client107or the application transfer system116(FIG. 1) and, if the recipient client107is authenticated, the application download is initiated.

Moving on toFIG. 2C, shown is a printed advertisement251. The printed advertisement contains a promotion254informing multiple recipients of the application download. The threshold maximum number of application downloads has been defined by the donor to be 50. To obtain the application download, 50 recipient clients107(FIG. 1) may obtain an image of the QR code257. Upon capture of the image, the image may be sent to the application transfer system116across the network109(FIG. 1) for decoding or decoded by the client devices.

Referring next toFIG. 3A, shown is a flowchart that provides one example of the operation of a portion of the application transfer system116according to various embodiments. It is understood that the flowchart ofFIG. 3Aprovides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the application transfer system116as described herein. As an alternative, the flowchart ofFIG. 3Amay be viewed as depicting an example of steps of a method implemented in the computing environment103(FIG. 1) according to one or more embodiments.FIG. 3Adepicts obtaining application download parameters from a donor client device and generating an encoded identifier for providing to a recipient client device.

Beginning with box311, the application transfer system116obtains application download data from a donor client105(FIG. 1). The data may include, for example, identification of an application to transmit to a recipient. The data may also include payment from the donor for the recipient device to download the application. The data includes any information relevant to transmitting an application download to another. For example, the application transfer system116may obtain the data from a donor client105as it was input via a user interface.

In box314, the application transfer system obtains download parameters from the donor's client device. Application download parameters include constraints on the transmission of the application download to another. For example, one application download parameter may be an identifier of the client device authorized to receive the application download when one recipient has been identified. Another application download parameter may be a maximum number of application downloads allowed if multiple recipients exist. One application download parameter may include a deadline for downloading the application. The application download parameters may include a payment distribution between the donor and the recipient if the donor only wants to pay a portion of the cost of the application download. The application download parameters may include delivery methods for transmitting the encoded identifier to the recipient. For example, the delivery method may be by electronic display via email, digital billboard, or another electronic display, or in printed form.

In box317, the application transfer system116evaluates whether the download parameters indicate a specific recipient for the application download. This may be done by evaluating whether the donor client device provided an identifier of the recipient or whether it merely identified a threshold, such as, for example, a deadline for downloading or a maximum number of downloads. If a specific recipient is identified, then the application transfer system116proceeds to box321. If no specific recipient is identified, then the application transfer system116proceeds to box324.

In box321, the application transfer system116associates the application download with the recipient's user account124(FIG. 1) as a gift134(FIG. 1) in the data store112(FIG. 1). Thus, the application transfer system116may authenticate the recipient client device by comparing the gift134data to the client device credentials. Alternatively, the application transfer system116may encode the authentication data into the encoded identifier and decode the data when received from the recipient client device for authentication.

In box324, the application transfer system116generates the encoded identifier by encoding the relevant application download data and download parameters into an encoded identifier. The relevant data and parameters may include any data not stored in the data store, data needed for the recipient client device to download the application, or other data needed for the transmission of an application download. The encoded identifier may be a barcode, such as a QR code, symbols used for encoding data, test, or other encoded identifiers.

In box327, the application transfer system116delivers the encoded identifier to the recipient of the application download. The method of delivery was identified in the application parameters. The encoded identifier may be delivered by, for example, electronic display or printed medium. If the encoded identifier is delivered via electronic display, the encoded identifier may be emailed, messaged, posted on to social media, depicted on a network page, depicted on a digital billboard, or otherwise electronically displayed to the recipient. If the encoded identifier is delivered via a printed medium, it may be printed to posters, flyers, greeting cards, advertisements, papers, books, or other printed materials. Thereafter, this portion of the application transfer system116ends.

Referring next toFIG. 3B, shown is a flowchart that provides one example of the operation of a portion of the application transfer system116according to various embodiments. It is understood that the flowchart ofFIG. 3Bprovides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the application transfer system116as described herein. As an alternative, the flowchart ofFIG. 3Bmay be viewed as depicting an example of steps of a method implemented in the computing environment103(FIG. 1) according to one or more embodiments.FIG. 3Bdepicts a recipient client device obtaining the application download where the donor identified a specific recipient client device.

Beginning with box341, the application transfer system116obtains an image of an encoded identifier and client device credentials from a recipient client device107(FIG. 1). The encoded identifier may be in the form of a barcode, image, text, or other symbol containing encoded data. The client device credentials may be an account used to download applications, a login name, or some other unique identifier for the client device. Alternatively, the application transfer system116may obtain the data decoded from the encoded identifier by the recipient client device107(FIG. 1). The image may have been obtained by the client device in a variety of manners. In one embodiment, the image may have been captured by a camera on the client device. The camera may have captured the image from an electronic display on another client device or from a printed medium. In various embodiments, the image may have been captured by an application executed in the client device. For example, an email application executed in the client device may obtain the image from an email. As another example, an application download store executed on the client device may obtain an image of the encoded identifier from a network page, application screen, or other depiction of the encoded identifier.

Continuing with box341, the image may be obtained by the application through an automatic recognition, a manual selection, or other identification of the existence of the encoded identifier. For example, a screenshot may be captured by the device to obtain the image. Alternatively, a scan of the network page, application screen, or other depiction of the encoded identifier may be performed to obtain the image. A user may manually identify the encoded image on the screen through various input mechanisms, such as, for example, touching the screen, providing input through an input device, or other identification methods.

In box344, the application transfer system116extracts and decodes recipient authentication data from the encoded identifier. The recipient authentication data was provided as an application download parameter by the donor to uniquely identify the intended recipient of the application download.

In box351, the application transfer system116evaluates whether the client device credentials match the authentication data. This ensures that the client device attempting to receive the application download was the intended recipient. If the client device credentials do not satisfy the authentication data, the application transfer system116continues to box353. If the client device credentials satisfy the authentication data, the application transfer system116continues to box358.

In box353, the application transfer system116evaluates whether authorization may be obtained from the donor client device. This may be done by the application transfer system116sending the donor client device a message indicating failed authorization of the recipient client device and indicating the client device credentials of the device attempting to download the application. The donor client device may provide new authentication data in response. Alternatively, or additionally, the application transfer system116may request authorization without verifying the recipient client device107. If the donor client device provides the authorization or if the new authentication data matched the client device credentials, the application transfer system116continues to box357. If the authorization still fails, the application transfer system116continues to box358.

In box357, if authorization to allow the download was obtained, the application transfer system116extract application data from the encoded identifier and initiates the application download to the recipient client device107. In box358, if authorization to allow the download was not obtained, the application transfer system116sends an error to the recipient client device indicating authorization failed. Thereafter, this portion of the application transfer system116ends.

Referring next toFIG. 3C, shown is a flowchart that provides one example of the operation of a portion of the application transfer system116according to various embodiments. It is understood that the flowchart ofFIG. 3Cprovides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the application transfer system116as described herein. As an alternative, the flowchart ofFIG. 3Cmay be viewed as depicting an example of steps of a method implemented in the computing environment103(FIG. 1) according to one or more embodiments.FIG. 3Cdepicts recipient client devices obtaining the application download where the donor identified a threshold for when the application download would expire.

Beginning with box361, the application transfer system116obtains the encoded identifier from the recipient client device. The encoded identifier may be in the form of a barcode, image, text, or other symbol containing encoded data. Alternatively, the application transfer system116may obtain the data decoded from the encoded identifier by the recipient client device107(FIG. 1).

In box364, the application transfer system116extracts and decodes application download expiration data from the download parameters encoded in the encoded identifier. The application download expiration data may comprise a threshold number of application downloads, a threshold timeframe or deadline for downloading the application, or some other threshold indicating when the application download expires.

In box367, the application transfer system116authorizes the client device by evaluating whether the application download has expired. This may be done by comparing the threshold number of application downloads to a counter of the number of application downloads completed as of the authorization. For example, the application transfer system116may have a counter that tracks the number of downloads completed. Each time a new download is completed, the application transfer system116may increment the counter. This counter is then compared to the threshold number of downloads prior to authorizing the next download. Alternatively, or additionally, the authorization may comprise comparing the threshold timeframe to a timestamp as of the authorization. The threshold timeframe defines when the application download may be requested by a client. For example, the donor may define the download timeframe to be between Sunday, May 5, 2013, and Sunday, May 12, 2013, and, therefore, the application download may be authorized during that download timeframe. If the application download has expired, the application transfer system116proceeds to box368. If the application download has not expired, the application transfer system116proceeds to box371.

In box368, if authorization failed, the application transfer system116notifies the client device that the application download has expired and/or that the client device is not authorized to download the application. Thereafter, this portion of the application transfer system116ends.

In box371, if authorization succeeded, the application transfer system116extracts application data from the encoded identifier and initiates the application download. Thereafter, this portion of the application transfer system116ends.

Referring next toFIG. 3D, shown is a flowchart that provides one example of the operation of a portion of a recipient client application161(FIG. 1) as it interacts with a portion of the application transfer system116according to various embodiments. It is understood that the flowchart ofFIG. 3Dprovides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the application transfer system116as described herein. As an alternative, the flowchart ofFIG. 3Dmay be viewed as depicting an example of steps of a method implemented in the computing environment103(FIG. 1) according to one or more embodiments.FIG. 3Ddepicts the recipient client device obtaining the encoded image, decoding the application download parameters contained in the encoded image, and sending the decoded data to a server hosting the application transfer system116.

Beginning with box381, a client application161executed on the recipient client107obtains an image of an encoded identifier. In one embodiment, a camera client application161may obtain the image through the camera in the recipient client107. Where a camera in the recipient client107obtains the image, the camera lens in the recipient client107is aligned approximately parallel with the electronic display or printed material depicting the encoded identifier. In various embodiments, an application store client application161executed on the recipient client107may obtain the image through the camera in the recipient client107. Alternatively, the client application161may otherwise scan the encoded identifier to obtain the image.

In box384, the client application161may extract and decode application download parameters from the encoded identifier. Application download parameters include constraints on the transmission of the application download to another. For example, one application download parameter may be an identifier of the client device authorized to receive the application download. Another application download parameter may be a maximum number of application downloads allowed. One application download parameter may include a deadline for downloading the application. Other data may be included in the application download parameters.

In box387, the decoded download parameters are transmitted across the network109to the computing device400(FIG. 4) executing the application transfer system116. Alternatively, the encoded identifier may be sent to the server executing the application transfer system116for decoding.

In box391, the recipient client application161verifies that the application was successfully downloaded. Alternatively, the client application161may receive an error or message from the application transfer system116indicating that authorization or the download failed. Thereafter, this portion of the client application161as it interacts with the application transfer system116ends.

With reference toFIG. 4, shown is a schematic block diagram of the computing environment103according to an embodiment of the present disclosure. The computing environment103includes one or more computing devices400. Each computing device400includes at least one processor circuit, for example, having a processor403and a memory406, both of which are coupled to a local interface409. To this end, each computing device400may comprise, for example, at least one server computer or like device. The local interface409may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated.

Stored in the memory406are both data and several components that are executable by the processor403. In particular, stored in the memory406and executable by the processor403are the electronic commerce system115, the application transfer system116, and potentially other applications. Also stored in the memory406may be a data store112and other data. In addition, an operating system may be stored in the memory406and executable by the processor403.

Also, the processor403may represent multiple processors403and/or multiple processor cores and the memory406may represent multiple memories406that operate in parallel processing circuits, respectively. In such a case, the local interface409may be an appropriate network that facilitates communication between any two of the multiple processors403, between any processor403and any of the memories406, or between any two of the memories406, etc. The local interface409may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. The processor403may be of electrical or of some other available construction.