# US 2018/0321052 A1 · Controller > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0321052 A1 - Document ID: US20180321052A1 - Status: Published application - Kind: A1 - Application number: 15/773,936 - Filed: 2016-11-07 - Published: 2018-11-08 - Earliest claimed: 2015-11-05 - Assignees: Intercept IP Ltd - Applicants: Intercept IP Ltd - Inventors: Wayne GILBERT - Web page: https://patentgrep.com/patent/US20180321052A1 ## CPC - G01C 21/26: specially adapted for navigation in a road network - G01C 21/36: Input/output arrangements for on-board computers - G08G 1/0112: {from the vehicle, e.g. floating car data [FCD]} - G08G 1/0129: {for creating historical data or processing based on historical data} - G08G 1/0141: {for traffic information dissemination} - G08G 1/096716: {where the received information does not generate an automatic action on the vehicle control} - G08G 1/096741: {where the source of the transmitted information selects which information to transmit to each vehicle} - G08G 1/096775: {where the origin of the information is a central station} - H04L 65/80: Responding to QoS - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 67/125: involving control of end-device applications over a network - H04L 67/61: taking into account QoS or priority requirements - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H 40/67: for remote operation - H04W 4/046 - G01C: MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY (measuring liquid level G01F; radio navigation, determining distance or velocity by use of propagation effects, e.g. Doppler effects, propagation time, of radio waves, analogous arrangements using other waves G01S) - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract A controller for managing data demand to and from an asset is described. In particular, the controller is configured to obtain streams of local data from one or more local data sources, said local data providing local information of a current condition of the asset. Once received, the controller determines one or more potential future conditions of the asset based on the current condition of the asset and on changes in the local data. A bandwidth requirement is then determined to obtain streams of remote data from one or more remote data sources potentially relevant to the one or more potential future conditions. This bandwidth requirement is then compared to an available bandwidth; and a priority order determined for obtaining the remote data if the available bandwidth is below the bandwidth requirement. ## Claims ### Claim 1 A controller for managing data demand to and from an asset, wherein the controller is configured to: obtain streams of local data from one or more local data sources, said local data providing local information of a current condition of the asset; determine one or more potential future conditions of the asset based on the current condition of the asset and on changes in the local data; determine a bandwidth requirement to obtain streams of remote data from one or more remote data sources potentially relevant to the one or more potential future conditions; compare the bandwidth requirement to an available bandwidth; and determine a priority order for obtaining the remote data if the available bandwidth is below the bandwidth requirement. ### Claim 2 (depends on 1) The controller of claim 1 further configured to determine the priority order by calculating the relevance of the remote data to the one or more potential future conditions based on changes in the local data. ### Claim 3 (depends on 2) The controller of claim 2 further configured to dynamically alter the priority order to prioritise obtaining the remote data in order of relevance within the available bandwidth. ### Claim 4 (depends on 2, 3) The controller of claim 2 or claim 3, wherein the controller determines the order of relevance based on an event sequence describing a task priority for handling of the remote data. ### Claim 5 (depends on 4, 5) The controller of claim 4 or claim 5, wherein the event sequence is dynamically altered based on the available bandwidth. ### Claim 7 (depends on 4, 5, 6) The controller of any one of claims 4 to 6, wherein the event sequence further describes a task priority for handling of the local data. ### Claim 8 (depends on 4, 5, 6, 7) The controller of any one of claims 4 to 7, wherein the event sequence defaults to a root sequence defining a default task priority for handling of remote data if the available bandwidth is at or above the bandwidth requirement. ### Claim 9 (depends on 8) The controller of claim 8, wherein the event sequence defaults to the root sequence if the available bandwidth is insufficient to obtain any remote data sources. ### Claim 10 (depends on 4, 5, 6, 7, 8, 9) The controller of any one of claims 4 to 9, wherein the event sequence comprises one or more data planes of remote data and local data, said data planes defining the one or more potential future conditions. ### Claim 11 (depends on 10) The controller of claim 10, wherein a data plane is populated by: the remote data from the one or more remote data sources; and the local information from the one or more local data sources. ### Claim 12 (depends on 10, 11) The controller of claim 10 or claim 11, wherein each data plane has a downstream bandwidth requirement for obtaining the remote data from the one or more remote data sources. ### Claim 13 (depends on 12) The controller of claim 12, wherein the bandwidth requirement is the sum of the downstream bandwidth requirements for every data plane. ### Claim 14 (depends on 12) The controller of claim 12, wherein each data plane has an upstream bandwidth requirement for reporting the local data or changes in the local data to a remote server. ### Claim 15 (depends on 14) The controller of claim 14, wherein the bandwidth requirement is the sum of the upstream and downstream bandwidth requirements for every data plane. ### Claim 16 (depends on 10, 11, 12, 13, 14, 15) The controller of any one of claims 10 to 15, wherein the data planes combine the local and remote data based on a location of the asset. ### Claim 17 (depends on 10, 11, 12, 13, 14, 15, 16) The controller of any one of claims 10 to 16, wherein the data planes are arranged in a tensor. ### Claim 18 (depends on 10, 11, 12, 13, 14, 15, 16, 17) The controller of any one of claims 10 to 17, wherein the data planes are arranged according to the event sequence. ### Claim 19 The controller of any preceding claim, further configured to assign a critical time value to each potential future condition that defines the time by which the potential future condition requires refreshed remote data. ### Claim 20 (depends on 19) The controller of claim 19, wherein the controller calculates a remote bandwidth required to obtain the remote data within the critical time value for a or each potential future condition. ### Claim 21 (depends on 20) The controller of claim 20, wherein the bandwidth requirement comprises the sum of the remote bandwidth required for all potential future conditions. ### Claim 22 (depends on 21) The controller of claim 21, further configured to determine which potential future conditions are most probable. ### Claim 23 (depends on 22) The controller of claim 22 wherein the bandwidth requirement comprises the sum of the remote bandwidth required for the most probable potential future conditions. ### Claim 24 (depends on 23) The controller of claim 23 further configured to alter the behaviour of the asset to mitigate any risk associated with the most probable potential future conditions if the available bandwidth is below the bandwidth requirement for longer than the critical time. ### Claim 25 (depends on 19, 20, 21, 22, 23) The controller of any one of claims 19 to 23, wherein the controller alters the behaviour of the asset to mitigate any risk associated with the one or more potential future conditions if the available bandwidth is below the bandwidth requirement for longer than each potential future condition's critical time. ### Claim 26 The controller of any preceding claim, wherein the bandwidth requirement comprises the bandwidth required to transmit the local data from the asset to a server. ### Claim 27 The controller of any preceding claim, wherein the bandwidth requirement comprises the bandwidth required to transmit changes in the local data to the or a server. ### Claim 28 The controller of any preceding claim, wherein the controller is further configured to determine the one or more potential future conditions of the asset based on one or more potential future locations of the asset. ### Claim 29 (depends on 28) The controller of claim 28, further configured to predict the available bandwidth based on the potential future locations of the asset. ### Claim 30 The controller of any preceding claim, wherein the asset is a motor vehicle. ### Claim 31 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29) The controller of any one of claims 1 to 29, wherein the asset is a health device. ### Claim 32 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28) The controller of any one of claims 1 to 28, wherein the asset is a robotic device. ### Claim 33 The controller of any preceding claim wherein the local data sources are sensors monitoring the condition of the asset. ### Claim 34 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33) A system for managing data demand to and from an asset, said system comprising: a controller according to any one of claims 1 to 33; an output channel associated with the controller and configured to transceive the streams of remote data to and from the controller. ### Claim 35 (depends on 34) The system of claim 34, wherein the output channel comprises a plurality of data communication devices, such as wireless fidelity and/or wireless mobile telecommunications technology. ### Claim 36 A method of managing data demand for an asset, said method comprising the steps of: receiving streams of local data from one or more local data sources, said local data monitoring a current condition of the asset; identifying changes in the current condition of the asset from changes in the local data sources; determining one or more potential future conditions of the asset based on the changes; determining a bandwidth requirement for obtaining streams of remote data from one or more remote data sources relevant to the one or more potential future conditions; and comparing the bandwidth requirement to an available bandwidth; and prioritising the order in which the streams of remote data are retrieved. ### Claim 37 (depends on 36) The method of claim 36, wherein the prioritising is based on the bandwidth requirement of each stream of remote data. ### Claim 38 (depends on 36, 37) The method of claim 36 or claim 37, wherein the prioritising is based on a time criticality for refreshing the remote data.