EP2920707A2 - Control of transmission to a target device with a cloud-based architecture - Google Patents
Control of transmission to a target device with a cloud-based architectureInfo
- Publication number
- EP2920707A2 EP2920707A2 EP13855139.5A EP13855139A EP2920707A2 EP 2920707 A2 EP2920707 A2 EP 2920707A2 EP 13855139 A EP13855139 A EP 13855139A EP 2920707 A2 EP2920707 A2 EP 2920707A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- practicability index
- transmission practicability
- part via
- computing
- cloud architecture
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Definitions
- United States Patent Application No. 13/678,010 entitled CONTROL OF TRANSMISSION TO A TARGET DEVICE WITH A CLOUD-BASED ARCHITECTURE; naming Richard T. Lord; Robert W. Lord; Craig J. Mundie; and Clarence T. Tegreene as inventors; filed 15 November 2012.
- United States Patent Application No. 13/678,082 entitled CONTROL OF TRANSMISSION TO A TARGET DEVICE WITH A CLOUD-BASED ARCHITECTURE; naming Richard T. Lord; Robert W. Lord; Craig J. Mundie; and Clarence T. Tegreene as inventors; filed 15 November 2012.
- United States Patent Application No. 13/678,010 entitled CONTROL OF TRANSMISSION TO A TARGET DEVICE WITH A CLOUD-BASED ARCHITECTURE; naming Richard T. Lord; Robert W. Lord; Craig J. Mundie; and Clarence T. Tegreene as inventors; filed 15 November 2012.
- Systems, methods, computer-readable storage mediums including computer- readable instructions and/or circuitry for control of transmission to a target device with a cloud-based architecture may implement operations including, but not limited to: computing, at least in part via a cloud architecture, a prospective transmission practicability index based at least in part on localized context information associated with a target device; comparing, at least in part via a cloud architecture, the prospective transmission practicability index against a threshold transmission practicability index associated with the target device; and transmitting, at least in part via a cloud-based architecture, at least one notification associated with the comparison to at least one transmission generating computing device.
- FIG. 1 shows a high-level block diagram of an operational environment.
- FIG. 2 shows a high-level block diagram of an operational environment.
- FIG. 3 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 4 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 5 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 6 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 7 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 8 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 9 shows operations for control of transmission to a target device with a cloud-based architecture.
- FIG. 1 is a block diagram of a cloud-based computing system 100 employing a cloud-based architecture.
- the cloud-based computing system 100 may include a variety of computing devices 101 connected via a network 102.
- the network 102 may be the Internet, a Local Area Network (LAN), a wireless network (such as a wireless LAN or WLAN), or other network, or a combination of networks.
- the cloud-based computing system 100 may further include a cloud-based server 103, operably coupled to the computing devices 101 via the network 102.
- the computing devices 101 may each be any type of computer or computing device, such as a desktop computer, laptop computer, netbook, tablet computer, mobile computing device (such as a cell phone, smartphone, personal digital assistant or other mobile or handheld or wireless computing device), or any other computer/computing device.
- the computing devices 101 may include one or more of a user input/output devices such as a display, keyboard, and a pointing device (such as a track ball, mouse, touch pad, touch screen or other pointing device).
- the computing devices 101 may include memory to store data and software/computer instructions, a processor for executing software/computer instructions and providing overall control to the computer.
- the computing devices 101 may each include an operating system (OS) stored in memory and executed at startup, for example.
- OS operating system
- the computing devices 101 may execute or run a web browser application 104 configured to access data maintained on one or more other computing devices 101 and/or the cloud-based server 103 via the network 102.
- the cloud-based server 103 may run one or more applications, such as server application 105 to provide a cloud-based service (or a cloud-based computing service) where cloud-based server 103 (and/or other servers associated with the cloud-based service) may provide resources, such as software, data, media (e.g., video, audio files) and other information, and management of such resources, to computing devices 101 via the network 102.
- server application 105 may provide resources, such as software, data, media (e.g., video, audio files) and other information, and management of such resources, to computing devices 101 via the network 102.
- computing resources such as application programs and file storage may be remotely provided by the cloud-based service (e.g., by cloud-based server 103) to a computing device 101 over the network 102 through the web browser application 104 running on the computing device 101.
- a client computing device 101 may include the web browser application 104 running applications (e.g., Java applets or other applications), which may include application programming interfaces (“API's”) to more sophisticated applications (such as server application 105) running on remote servers that provide the cloud-based service (cloud- based server 103), as an example embodiment.
- applications e.g., Java applets or other applications
- API's application programming interfaces
- server application 105 running on remote servers that provide the cloud-based service
- server application based server 103 e.g., a user can use a computing device 101 to log on to cloud-based services (e.g., by the web browser application 104 communicating with cloud-based server 103 of the cloud-based computing system 100) to access a server application 105.
- the user may create, edit, save and delete files on cloud-based server 103, and may establish (set up) or change/edit various options, such as user preferences and/or system settings, and/or may receive or download software (e.g., operating system or other software) or software updates, various data files or media files, user preferences and/or system settings, and other information previously stored on the cloud-based server 103, via the server application 105 running on the cloud- based server 103.
- a user of a first computing device 101 may compose a message 106 (e.g.
- the first computing device 101 may access a message creation server application 105 running on cloud-based server 103 to compose the message 106 and the message 106 may be stored to a message storage queue 107 maintained in memory by the cloud-based server 103.
- the cloud-based server 103 may, in turn, employ a message transmission server application 105’ to transmit one or more messages 106 stored in the message storage queue 107 to the target computing device 101’.
- the determination of when to transmit messages 106 stored in the message storage queue 107 to the target computing device 101’ may carried out solely by the cloud- based server 103 architecture and not at the direction of either the transmitting computing device 101 or the target computing device 101’. Rather, the cloud-based server 103 may direct the transmission of messages 106 to the target computing device 101’ according to one or more cloud-based server defined parameters.
- the cloud-based server defined parameter may be associated with local environments and/or network connectivity parameters based on local context data 108 (e.g. location data, connection data, environmental data) associated with a given target computing device 101’.
- the message transmission server application 105’ may be configured to authorize the transmission of messages 106 to the target computing device 101’ only when context data 108 (e.g. a network address, a geographical identifier, a power indicator, a bandwidth indicator, an inertial signal, an imaging signal, or a user input/output indicator, a communications signal strength, a connection type, etc.) associated with the target computing device 101’) indicates that there is a likelihood that a message 106 transmitted to the target computing device 101’ will be successful or occur in accordance with certain parameters (e.g. occur at a given speed, occur only when a device is in a specific location, occur only when the target computing device 101’ is capable of receiving a message 106, etc.).
- context data 108 e.g. a network address, a geographical identifier, a power indicator, a bandwidth indicator, an inertial signal, an imaging signal, or a user input/output indicator, a communications signal strength, a connection type, etc.
- the message transmission server application 105’ may be configured to authorize the transmission of messages 106 to the target computing device 101’ only when a prospective transmission practicability index computed from context data 108 associated with the target computing device 101’ complies with one or more threshold metrics maintained by a server data store 109 as a threshold prospective transmission practicability index 110 indicative of context data 108 having characteristics reflecting a likelihood of success in transmitting a message 106 to the target computing device 101’.
- the cloud-based server 103 may obtain/receive device identification data associated with the target computing device 101’ (e.g. a serial number, a model number, a network address) as well as context data 108 associated with the target computing device 101’.
- the message transmission server application 105’ may compare a transmission practicability index computed from the context data 108 associated with the target computing device 101’ to the threshold prospective transmission practicability index 110. If the transmission practicability index computed from the context data 108 associated with the target computing device 101’ complies with the threshold prospective transmission practicability index 110, the message transmission server application 105’ may authorize the transmission of a message 106 to the target computing device 101’. Otherwise, the message 106 may be retained in the message storage queue 107 until the transmission practicability index computed from the context data 108 associated with the target computing device 101’ complies with the threshold prospective transmission practicability index 110, if ever.
- FIG. 3 and the following figures include various examples of operational flows, discussions and explanations may be provided with respect to the above-described exemplary environment of FIGS. 1 -2. However, it should be understood that the operational flows may be executed in a number of other environments and contexts, and/or in modified versions of FIGS. 1 -2. In addition, although the various operational flows are presented in the sequence(s) illustrated, it should be understood that the various operations may be performed in different sequential orders other than those which are illustrated, or may be performed concurrently.
- FIG. 3 illustrates an operational procedure 300 for practicing aspects of the present disclosure including operations 302, 304 and 306.
- Operation 302 illustrates computing, at least in part via a cloud architecture, a prospective transmission practicability index based at least in part on localized context information associated with a target device.
- the message transmission server application 105’ may differentiate between varying local environments and/or network connectivity parameters based on context data 108 (e.g. location data, connection data, environmental data) associated with a given target computing device 101’ and only authorize transmission of messages 106 to the target computing device 101’ when threshold contextual data parameters are satisfied for a target computing device 101’.
- a target computing device 101’ may include one or more context sensors 111.
- the message transmission server application 105’ may query one or more of the context sensors 111 of the target computing device 101’ to obtain context data 108 associated with the target computing device 101’.
- the target computing device 101’ may periodically provide context data 108 to the message transmission server application 105’.
- the server data store 109 may maintain reference context data 112 corresponding to potential context data 108 which may be received from a target computing device 101’.
- the reference context data 112 may be mapped to one or more prospective transmission practicability indices 113 associated with practicalities (e.g. likelihood of successful transmission of a message 106 to target computing device 101’ and/or a resultant perception of the message 106 by an end-user) of transmission of a message 106 to the target computing device 101’ under certain conditions defined by context data 108 (e.g.
- a high probability may exist for a target computing device 101’ having a high power level, a location close to a high- bandwidth wireless network node and an indicated high user device use level; a low probability may exist for a device having a low power level, a location distant from a low- bandwidth wireless network node and an indicated low user device use level).
- the message transmission server application 105’ may compute a prospective transmission practicability index 113 by comparing the received context data 108 to the reference context data 112 (e.g. determining a range of reference context data 112 into which the context data 108 falls) and assign a prospective transmission practicability index 113 to the target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 304 illustrates comparing, at least in part via a cloud architecture, the prospective transmission practicability index against a threshold transmission practicability index associated with the target device.
- the message transmission server application 105’ may compare that prospective transmission practicability index 113 associated with the received context data 108 to a threshold prospective transmission practicability index 110 (e.g. a threshold quantification indicative of context data 108 having characteristics reflecting a likelihood of success in transmitting a message 106 to the target computing device 101’) associated with (e.g.
- Operation 306 illustrates transmitting, at least in part via a cloud-based architecture, at least one notification associated with the comparison to at least one transmission generating computing device.
- a cloud-based architecture For example, it may be the case that a user of a message generating computing device 101 may desire to know the practicality of transmitting a message 106 to a target computing device 101’ resulting from localized context information associated with the target computing device 101’. As such, as shown in FIGs.
- the message transmission server application 105’ may provide at least one notification 121 to the web browser application 104 of the message generating computing device 101 indicative of the practicality of the transmission of a message 106 to a target computing device 101’. For example, if the context data 108 is of such a nature that a likelihood of success in transmitting a message 106 to the target computing device 101’ is low due to various factors (e.g.
- the message transmission server application 105’ may transmit a notification 121 (e.g. an e-mail, text message, and the like) indicating such a likelihood to the message generating computing device 101.
- the notification 121 may include an estimated delivery time of a message 106 (if any), a summary of the localized context data for the target computing device 101’, and the like.
- Such a notification may allow a user of the message generating computing device 101 an opportunity to attempt and alternate avenue of communication with a user of the target computing device 101’ or at least be made aware that the user of the target computing device 101’ may not receive the message 106.
- Operation 402 illustrates computing, at least in part via a cloud architecture, a prospective transmission practicability index based at least in part on localized context information associated with a target device in response to an enqueuing of a transmission.
- a user of the computing device 101 may employ the message creation server application 105 to create a message 106 for transmission to the target computing device 101’.
- the message 106 may be enqueued in the message storage queue 107.
- Operation 404 illustrates computing, at least in part via a cloud architecture, a prospective transmission practicability index based at least in part on localized context information associated with a target device in response to an enqueuing of a transmission.
- a user of the computing device 101 may employ the message creation server application 105 to create a number of messages 106 for transmission to the target computing device 101’.
- FIG. 5 further illustrates an example embodiment where operation 302 of example operational flow 300 of FIG.
- Operation 502 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based al least in part on a geographical identifier associated with at least one computing device.
- the message transmission server application 105’ may differentiate may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on the respective geographic locations of the target computing devices 101’ (e.g. transmissions of messages 106 to target computing devices 101’ in a first geographic location (e.g. a remote wilderness area) may be less practical than transmission of messages 106 to target computing devices 101’ in a second geographic location (e.g.
- a target computing device 101’ may include a global positioning system sensor 114.
- the message transmission server application 105’ may query the global positioning system sensor 114 of the target computing device 101’ for geographic location context data 108 for the target computing device 101’ and compare that geographic location context data 108 to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 504 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on a power indicator associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on the performance characteristics, system status, remaining battery life etc. (e.g. transmissions of messages 106 to target computing devices 101’ having a high level of remaining battery life may be more practical than transmission of messages 106 to target computing devices 101’ having a low level of remaining battery life).
- the reference context data 112 associated with a device power level context data 108 may be mapped to a prospective transmission practicability index 113.
- a target computing device 101’ may include a power level sensor 115 (e.g. a battery level sensor).
- the message transmission server application 105’ may query the power level sensor 115 of the target computing device 101’ for its current power level context data 108 for the target computing device 101’ and compare that power level context data 108 to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 506 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on an inertial signal associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on a usage profile of the target computing devices 101’ (e.g. transmissions of messages 106 to target computing devices 101’ having a high level of device usage may occur on a time scale shorter than transmission of messages 106 to target computing devices 101’ having a low level of usage).
- the reference context data 112 associated with a device power level context data 108 may be mapped to a prospective transmission practicability index 113.
- a target computing device 101’ may include an inertial sensor 116 (e.g. an accelerometer) configured to detect motion of the target computing device 101’ indicative of use of the target computing device 101’.
- the message transmission server application 105’ may query the inertial sensor 116 of the target computing device 101’ for an indication of usage of the target computing device 101’ and compare that usage level context data 108 to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- FIG. 6 illustrates an example embodiment where operation 302 of example operational flow 300 of FIG.
- Operation 602 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on an imaging signal associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on the respective environment or geographic locations of the target computing devices 101’ (e.g. transmissions of messages 106 to target computing devices 101’ in a first environment or location (e.g. an office during the daytime) may be more practical than transmission of messages 106 to target computing devices 101’ in a second environment or location (e.g. at a home during the night)).
- a target computing device 101’ may include an image capture sensor 117 (e.g. a camera configured for still image or video capture).
- the message transmission server application 105’ may query the image capture sensor 117 of the target computing device 101’ to obtain one or more images of the current environment of the target computing device 101’.
- the image of the environment may be analyzed (e.g.
- Operation 604 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on a user- input/output associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on a usage profile of the target computing devices 101’ (e.g.
- a target computing device 101’ may include a user input/output device 118 (e.g. a touchscreen, a keypad, a display, a microphone, a speaker, etc.) configured to receive/provide user input/output of the target computing device 101’ (e.g. for control of one or more functions of the target computing device 101’).
- a user input/output device 118 e.g. a touchscreen, a keypad, a display, a microphone, a speaker, etc.
- the message transmission server application 105’ may query the user input/output device 118 of the target computing device 101’ for device usage context data 108 for the target computing device 101’ and compare that device usage context data 108 to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 606 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on an audio signal associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on the respective environment or geographic locations of the target computing devices 101’ (e.g. transmissions of messages 106 to target computing devices 101’ in a first environment or location (e.g. an office during the daytime) may be more practical than transmission of messages 106 to target computing devices 101’ in a second environment or location (e.g. at a home during the night)).
- the reference context data 112 associated with various geographic locations may be mapped to a prospective transmission practicability index 113.
- a target computing device 101’ may include an audio capture sensor 119 (e.g. a microphone configured for recording environmental sounds).
- the message transmission server application 105’ may query the audio capture sensor 119 of the target computing device 101’ to obtain one or more sound recordings of the current environment of the target computing device 101’.
- the sound recordings of the environment may be analyzed (e.g. by sound recognition software running on the cloud-based server 103) to determine the current environment of the target computing device 101’ and compared to sound reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the image reference context data 112 and the prospective transmission practicability index 113.
- FIG. 7 illustrates an example embodiment where operation 302 of example operational flow 300 of FIG. 3 may include at least one additional operation.
- Operation 702 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on a signal strength associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on differing network connectivity (e.g. transmissions of messages 106 to target computing devices 101’ via a network 102 connection having a first signal strength may be more or less practical than transmission of messages 106 to target computing devices 101’ via a network 102 connection having a second signal strength).
- the reference context data 112 may include one or more signal strength ranges associated with communications signal strengths for target computing devices 101’ connected to network 102. One or more signal strength ranges may be mapped to at least one threshold prospective transmission practicability index 110 in the server data store 109.
- the message transmission server application 105’ may query the network 102 and/or the target computing device 101’ for the signal strength context data 108 indicative of a signal strength between the target computing device 101’ and the network 102 and compare that signal strength context data 108 to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 704 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on a bandwidth associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based on differing network connectivity (e.g. transmissions of messages 106 to target computing devices 101’ via a network 102 connection having a first bandwidth may be more or less practical than transmission of messages 106 to target computing devices 101’ via a network 102 connection having a second bandwidth).
- the reference context data 112 associated with various bandwidth e.g. data throughput metrics
- ranges may be mapped to a prospective transmission practicability index 113.
- the message transmission server application 105’ may query the network 102 and/or the target computing device 101’ for the bandwidth between the target computing device 101’ and the network 102 and compare that bandwidth to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the reference context data 112 and the prospective transmission practicability index 113.
- Operation 706 illustrates computing, at least in part via a cloud architecture, the prospective transmission practicability index based at least in part on a connection type associated with at least one computing device.
- the message transmission server application 105’ may differentiate the practicality of transmission of messages 106 to target computing devices 101’ based differing network connectivity (e.g. transmissions of messages 106 to target computing devices 101’ via a wired network 102 connection type may be more or less practical than transmission of messages 106 to target computing devices 101’ having a wireless network 102 connection type).
- the reference context data 112 associated with various network connection types may be mapped to a prospective transmission practicability index 113.
- the message transmission server application 105’ may query the network 102 and/or the target computing device 101’ for the network connection type between the target computing device 101’ and the network 102 and compare that network connection type to the reference context data 112 in order to compute a prospective transmission practicability index 113 for that target computing device 101’ according to the mapping between the network connection type reference context data 112 and the prospective transmission practicability index 113 [0051]
- FIG. 8 illustrates an example embodiment where operation 304 of example operational flow 300 of FIG. 3 may include at least one additional operation. Additional operations may include an operation 802, 804 and/or 806.
- Operation 802 illustrates comparing, at least in part via a cloud architecture, the prospective transmission practicability index against a threshold prospective transmission practicability index associated with a serial number of at least one computing device.
- the message transmission server application 105 may compare that prospective transmission practicability index 113 to a threshold prospective transmission practicability index 110 associated with the target computing device 101’ and maintained by the server data store 109 of the server data store 109.
- the message transmission server application 105’ may differentiate between multiple target computing devices 101’ and maintain distinct threshold prospective transmission practicability indices 110 for each target computing device 101’ or groups of target computing devices 101’ based on their respective device performance characteristics, bandwidth usage, usage histories, etc. (e.g. transmissions of messages 106 to a target computing device 101’ having a first serial number may be more or less practical than transmission of messages 106 to a target computing device 101’ having a second serial number).
- the server data store 109 may maintain a device ID database 120.
- the device ID database 120 may include one or more serial numbers assigned to target computing devices 101’.
- One or more serial numbers assigned to respective target computing devices 101’ may be mapped to at least one threshold prospective transmission practicability index 110 in the server data store 109.
- the message transmission server application 105’ may query the target computing device 101’ for its serial number, and obtain the appropriate threshold prospective transmission practicability index 110 for that target computing device 101’ according to the mapping between the serial number for that target computing device 101’ in the device ID database 120 and the threshold prospective transmission practicability index 110.
- Operation 804 illustrates comparing, at least in part via a cloud architecture, the prospective transmission practicability index against a threshold prospective transmission practicability index associated with a model identifier of at least one computing device. For example, as shown in FIGs.
- the message transmission server application 105’ may compare that prospective transmission practicability index 113 to a threshold prospective transmission practicability index 110 associated with the target computing device 101’ and maintained by the server data store 109 of the server data store 109. It may be the case that the message transmission server application 105’ may differentiate between multiple target computing devices 101’ and maintain distinct threshold prospective transmission practicability indices 110 for groups of target computing devices 101’ based on their respective device performance characteristics, bandwidth usage (e.g.
- the device ID database 120 may include one or more model identifiers (e.g. a model identifier associate with a vendor of target computing devices 101’ such as Apple ® , Sony ® , Samsung ® , Google ® , HTC ® and/or device-specific model identifiers) associated with the target computing devices 101’.
- model identifiers e.g. a model identifier associate with a vendor of target computing devices 101’ such as Apple ® , Sony ® , Samsung ® , Google ® , HTC ® and/or device-specific model identifiers
- One or more model identifiers assigned to respective target computing devices 101’ may be mapped to at least one threshold prospective transmission practicability index 110 in the server data store 109.
- Operation 806 illustrates comparing, at least in part via a cloud architecture, the prospective transmission practicability index against a threshold prospective transmission practicability index associated with a network address of at least one computing device. For example, as shown in FIGs.
- the message transmission server application 105’ may compare that prospective transmission practicability index 113 to a threshold prospective transmission practicability index 110 associated with the target computing device 101’ and maintained by the server data store 109 of the server data store 109. It may be the case that the message transmission server application 105’ may differentiate between multiple target computing devices 101’ and maintain distinct threshold prospective transmission practicability indices for each target computing device 101’ or groups of target computing devices 101’ based on the network connectivity for various branches of network 102 (e.g.
- the device ID database 120 may include one or more network addresses (e.g. IP addresses for a LAN, WAN, the Internet, etc.) associated with the target computing devices 101’ connected to network 102.
- One or more network addresses assigned to respective target computing devices 101’ may be mapped to at least one threshold prospective transmission practicability index 110 in the server data store 109.
- the message transmission server application 105’ may query the target computing device 101’ for its network address or extract the destination network address from the message 106 itself, and obtain the appropriate threshold prospective transmission practicability index 110 for that target computing device 101’ according to the mapping between the network address for that target computing device 101’ in the device ID database 120 and the threshold prospective transmission practicability index 110.
- FIG. 9 illustrates an example embodiment where example operational flow 300 of FIG. 3 may include at least one additional operation. Additional operations may include an operation 902.
- Operation 902 illustrates determining a threshold prospective transmission practicability index associated with the target device.
- the message transmission server application 105’ may be configured to compute and store a threshold prospective transmission practicability index 110 based on multiple parameters.
- the threshold prospective transmission practicability index 110 may be a combination of several threshold prospective transmission practicability indices 110 associated with location, power level, usage, and/or environmental factors associated with context data 108 of a target computing device 101’.
- the message transmission server application 105’ aggregate two or more of these factors to compute a combined (e.g. averaged, weighted average, etc.) threshold prospective transmission practicability index 110.
- Such computed threshold prospective transmission practicability indices 110 may vary according to one or more inputs (e.g.
- Operation 904 illustrates determining a threshold prospective transmission practicability index associated with the target device at least in part based on historical localized context information associated with the target device. For example, as shown in FIGs. 1 -2, over time the message transmission server application 105’ may transmit messages 106 to target computing devices 101’ and receive context data 108 feedback from target computing devices 101’. Historical data regarding the transmission of messages 106 in varying contextual circumstances of the target computing devices 101’ (e.g.
- success/failure data, transmission time data, retry data, message volume data may be used by the message transmission server application 105’ to refine the threshold prospective transmission practicability indices 110 to accurately reflect operations of the cloud-based computing system 100. For example, when transmission of messages 106 sent to target computing devices 101’ over a connection with a given bandwidth historically fail due to bandwidth limitations, it may be the case that the threshold prospective transmission practicability index 110 associated with bandwidth for those target computing devices 101’ should be increased such that higher bandwidth context data 108 is required to satisfy the threshold prospective transmission practicability index 110 (e.g. a higher bandwidth connection) thereby resulting in more timely delivery.
- a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
- electrical circuitry includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment
- a typical data processing system generally includes one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities).
- a typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
- any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality.
- operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
Abstract
Description
Claims
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/678,010 US10250638B2 (en) | 2012-05-02 | 2012-11-15 | Control of transmission to a target device with a cloud-based architecture |
US13/678,082 US20130298199A1 (en) | 2012-05-02 | 2012-11-15 | Control of Transmission to a Target Device with a Cloud-Based Architecture |
US13/707,261 US9148331B2 (en) | 2012-05-02 | 2012-12-06 | Control of transmission to a target device with a cloud-based architecture |
US13/729,802 US20130297725A1 (en) | 2012-05-02 | 2012-12-28 | Control of Transmission to a Target Device with a Cloud-Based Architecture |
PCT/US2013/070319 WO2014078662A2 (en) | 2012-11-15 | 2013-11-15 | Control of transmission to a target device with a cloud-based architecture |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2920707A2 true EP2920707A2 (en) | 2015-09-23 |
EP2920707A4 EP2920707A4 (en) | 2016-06-22 |
Family
ID=50731828
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13854491.1A Withdrawn EP2920944A4 (en) | 2012-11-15 | 2013-11-15 | Control of transmission to a target device with a cloud-based architecture |
EP13855139.5A Withdrawn EP2920707A4 (en) | 2012-11-15 | 2013-11-15 | Control of transmission to a target device with a cloud-based architecture |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13854491.1A Withdrawn EP2920944A4 (en) | 2012-11-15 | 2013-11-15 | Control of transmission to a target device with a cloud-based architecture |
Country Status (3)
Country | Link |
---|---|
EP (2) | EP2920944A4 (en) |
DE (2) | DE202013012283U1 (en) |
WO (2) | WO2014078644A2 (en) |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US20050255833A1 (en) * | 2004-05-13 | 2005-11-17 | Mobile (R&D) Ltd. | Message aggregation system and method for a mobile communication device |
US7400578B2 (en) * | 2004-12-16 | 2008-07-15 | International Business Machines Corporation | Method and system for throttling network transmissions using per-receiver bandwidth control at the application layer of the transmitting server |
US7707276B2 (en) * | 2005-07-28 | 2010-04-27 | Cisco Technology, Inc. | Remote configuration and management via electronic mail |
WO2007113516A1 (en) * | 2006-03-30 | 2007-10-11 | British Telecommunications Public Limited Company | Routing communications to devices with likely presence of user |
US8763071B2 (en) * | 2008-07-24 | 2014-06-24 | Zscaler, Inc. | Systems and methods for mobile application security classification and enforcement |
US8281027B2 (en) * | 2008-09-19 | 2012-10-02 | Yahoo! Inc. | System and method for distributing media related to a location |
US9357024B2 (en) * | 2010-08-05 | 2016-05-31 | Qualcomm Incorporated | Communication management utilizing destination device user presence probability |
CN103404193B (en) * | 2010-11-22 | 2018-06-05 | 七网络有限责任公司 | The connection that adjustment data transmission is established with the transmission being optimized for through wireless network |
US20140025747A1 (en) * | 2011-04-01 | 2014-01-23 | San Diego State University Research Foundation | Electronic devices, systems and methods for data exchange |
TWI592051B (en) * | 2012-02-07 | 2017-07-11 | 蘋果公司 | Network assisted fraud detection apparatus and methods |
US8874671B2 (en) * | 2012-02-10 | 2014-10-28 | Blackberry Limited | Electronic message metering and traffic management in a networked environment |
-
2013
- 2013-11-15 DE DE202013012283.8U patent/DE202013012283U1/en not_active Expired - Lifetime
- 2013-11-15 WO PCT/US2013/070276 patent/WO2014078644A2/en active Application Filing
- 2013-11-15 EP EP13854491.1A patent/EP2920944A4/en not_active Withdrawn
- 2013-11-15 WO PCT/US2013/070319 patent/WO2014078662A2/en active Application Filing
- 2013-11-15 EP EP13855139.5A patent/EP2920707A4/en not_active Withdrawn
- 2013-11-15 DE DE202013012254.4U patent/DE202013012254U1/en not_active Expired - Lifetime
Also Published As
Publication number | Publication date |
---|---|
WO2014078644A2 (en) | 2014-05-22 |
WO2014078662A2 (en) | 2014-05-22 |
EP2920944A2 (en) | 2015-09-23 |
DE202013012283U1 (en) | 2016-01-13 |
WO2014078662A3 (en) | 2014-07-17 |
EP2920944A4 (en) | 2016-06-15 |
DE202013012254U1 (en) | 2015-11-11 |
WO2014078644A3 (en) | 2014-11-20 |
EP2920707A4 (en) | 2016-06-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20130298199A1 (en) | Control of Transmission to a Target Device with a Cloud-Based Architecture | |
US9628582B2 (en) | Social-driven precaching of accessible objects | |
US10771533B2 (en) | Adaptive communication control device | |
US9733695B2 (en) | Battery life management in portable terminal | |
US8111154B1 (en) | Systems and methods for monitoring a mobile-computing device using geo-location information | |
US10437581B1 (en) | Internet of things platform for handling firmware transfer on machine-to-machine devices | |
EP3941022B1 (en) | Systems and methods for storage-efficient sensors | |
TW201336281A (en) | Managing data transfers over network connections based on priority and a data usage plan | |
US11095717B2 (en) | Minimizing data loss in a computer storage environment with non-guaranteed continuous network connectivity | |
US20180245935A1 (en) | Monitoring air pollution | |
JP6788501B2 (en) | Methods, systems, and computer programs for collecting usage data to determine user availability on multiple communication devices. | |
US10075387B1 (en) | Mobile server connection | |
US11630851B2 (en) | Systems and methods for providing predictions to applications executing on a computing device | |
WO2017020781A1 (en) | Power saving processing method, device, mobile terminal and cloud server | |
CN103634327A (en) | Remote terminal control method and remote terminal control device | |
US10148303B2 (en) | Methods and systems for aquatic infrastructure recharge and data transfer | |
US9148331B2 (en) | Control of transmission to a target device with a cloud-based architecture | |
AU2021238984B2 (en) | Predictive provisioning of remotely-stored files | |
US20130297725A1 (en) | Control of Transmission to a Target Device with a Cloud-Based Architecture | |
US20170147603A1 (en) | System, method and program product for managing mobile device operation | |
EP2920707A2 (en) | Control of transmission to a target device with a cloud-based architecture | |
US20210058478A1 (en) | Communication proxy for devices in mobile edge computing networks | |
US20190149566A1 (en) | Risk area determination in communication network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20150615 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20160520 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 29/06 20060101ALI20160513BHEP Ipc: G06F 15/16 20060101AFI20160513BHEP Ipc: H04L 29/08 20060101ALI20160513BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20170925 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20180713 |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: LORD, RICHARD T. Inventor name: LORD, ROBERT W. Inventor name: MUNDIE, CRAIG J. Inventor name: TEGREENE, CLARENCE T. |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20181124 |