# US 2020/0396146 A1 · Managing transport network data access > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2020/0396146 A1 - Document ID: US20200396146A1 - Status: Published application - Kind: A1 - Application number: 16/439,790 - Filed: 2019-06-13 - Published: 2020-12-17 - Earliest claimed: 2019-06-13 - Assignees: Toyota Motor North America, Inc. - Applicants: Toyota Motor North America, Inc. - Inventors: Louis Brugman - Web page: https://patentgrep.com/patent/US20200396146A1 ## CPC - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]} - H04L 41/147: for predicting network behaviour - H04L 41/149: for prediction of maintenance - H04L 41/5019: Ensuring fulfilment of SLA - H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade - H04L 43/0811: by checking connectivity - H04W 40/30: for proactive routing - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 2209/84: Vehicles - 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) ## Abstract An example operation may include one or more of determining a transport will lose a data network connection at a target time based on a route plan associated with the transport, determining an estimated amount of network down time until the transport regains the data network connection once the data network connection is lost, responsive to determining the data network connection will be lost and the estimated amount of network down time, invoking an off-network transport mode prior to the target time, responsive to invoking the off-network transport mode, recording one or more data segments of a data service currently used in the transport, and initiating the one or more data segments on a computing device at the target time. ## Claims ### Claim 1 A method, comprising: determining a transport will lose a data network connection at a target time based on a route plan associated with the transport; determining an estimated amount of network down time until the transport regains the data network connection once the data network connection is lost; responsive to determining the data network connection will be lost and the estimated amount of network down time, invoking an off-network transport mode prior to the target time; responsive to invoking the off-network transport mode, recording one or more data segments of a data service currently used in the transport; and initiating the one or more data segments on a computing device at the target time. ### Claim 2 (depends on 1) The method of claim 1, comprising: determining a period of time between a current time and the target time; and when the period of time is below a threshold period of time, initiating the recording of the one or more data segments. ### Claim 3 (depends on 2) The method of claim 2, comprising: determining the threshold period of time based on a type of data associated with the one or more data segments and an amount of data required to occupy the estimated amount of time until the transport regains the data network connection; and determining the amount of data of the one or more data segments based on a type of data associated with the one or more data segments and the estimated amount of time until the transport regains the data network connection. ### Claim 4 (depends on 1) The method of claim 1, comprising: determining a current map position and a future map position of the transport based on the route plan; identifying portions of the map between the current map position and the future map position which are known to have lost data network connections; and determining the estimated amount of network down time based on one or more distances associated with the identified portions of the map. ### Claim 5 (depends on 1) The method of claim 1, wherein recording the one or more data segments further comprises recording a first data segment of the data service currently used in the transport and a second data segment comprising content that is contextually related to the first data service, and wherein the second data segment is approximately a same amount of data as the amount of data of the first data segment, and wherein when at least one of the first and second data segments have completed, initiating a data service via the data network connection. ### Claim 6 (depends on 1) The method of claim 1, comprising: retrieving a smart contract from a distributed ledger; invoking the smart contract when the transport is determined to lose the data network connection at the target time; and determining, from the smart contract, the estimated amount of network down time based on the route plan. ### Claim 7 (depends on 1) The method of claim 1, comprising: creating a blockchain transaction comprising a date associated with the lost data network connection, a time the transport lost access to the data network, a time the transport regained access to the data network, a location of the transport prior to losing access to the data network, a location of the transport after regaining access to the data network; and storing the blockchain transaction in a distributed ledger. ### Claim 8 A system, comprising: a transport; and a server configured to determine a transport will lose a data network connection at a target time based on a route plan associated with the transport; determine an estimated amount of network down time until the transport regains the data network connection once the data network connection is lost; responsive to the determination that the data network connection will be lost and the estimated amount of network down time, invoke an off-network transport mode prior to the target time; responsive to the off-network transport mode being invoked, record one or more data segments of a data service currently used in the transport; and initiate the one or more data segments on a computing device at the target time. ### Claim 9 (depends on 8) The system of claim 8, wherein the server is further configured to determine a period of time between a current time and the target time; and when the period of time is below a threshold period of time, record one or more of the data segments. ### Claim 10 (depends on 9) The system of claim 9, wherein the server is further configured to determine the threshold period of time based on a type of data associated with the one or more data segments and an amount of data required to occupy the estimated amount of time until the transport regains the data network connection; and determine the amount of data of the one or more data segments based on a type of data associated with the one or more data segments and the estimated amount of time until the transport regains the data network connection. ### Claim 11 (depends on 8) The system of claim 8, wherein the server is further configured to determine a current map position and a future map position of the transport based on the route plan; identify portions of the map between the current map position and the future map position which are known to have lost data network connections; and determine the estimated amount of network down time based on one or more distances associated with the identified portions of the map. ### Claim 12 (depends on 8) The system of claim 8, wherein the one or more recorded data segments further comprises the server configured to record a first data segment of the data service currently used in the transport and a second data segment comprising content that is contextually related to the first data service, and wherein the second data segment is approximately a same amount of data as the amount of data of the first data segment, and wherein when at least one of the first and second data segments have completed, initiate a data service via the data network connection. ### Claim 13 (depends on 8) The system of claim 8, wherein the server is further configured to retrieve a smart contract from a distributed ledger; invoke the smart contract when the transport is determined to lose the data network connection at the target time; and determine, from the smart contract, the estimated amount of network down time based on the route plan. ### Claim 14 (depends on 8) The system of claim 8, wherein the server is further configured to create a blockchain transaction comprising a date associated with the lost data network connection, a time the transport lost access to the data network, a time the transport regained access to the data network, a location of the transport prior to losing access to the data network, a location of the transport after regaining access to the data network; and store the blockchain transaction in a distributed ledger. ### Claim 15 A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform: determining a transport will lose a data network connection at a target time based on a route plan associated with the transport; determining an estimated amount of network down time until the transport regains the data network connection once the data network connection is lost; responsive to determining the data network connection will be lost and the estimated amount of network down time, invoking an off-network transport mode prior to the target time; responsive to invoking the off-network transport mode, recording one or more data segments of a data service currently used in the transport; and initiating the one or more data segments on a computing device at the target time. ### Claim 16 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform: determining a period of time between a current time and the target time; and when the period of time is below a threshold period of time, initiating the recording of the one or more data segments. ### Claim 17 (depends on 16) The non-transitory computer readable storage medium of claim 16, wherein the processor is further configured to perform: determining the threshold period of time based on a type of data associated with the one or more data segments and an amount of data required to occupy the estimated amount of time until the transport regains the data network connection; and determining the amount of data of the one or more data segments based on a type of data associated with the one or more data segments and the estimated amount of time until the transport regains the data network connection. ### Claim 18 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform: determining a current map position and a future map position of the transport based on the route plan; identifying portions of the map between the current map position and the future map position which are known to have lost data network connections; and determining the estimated amount of network down time based on one or more distances associated with the identified portions of the map. ### Claim 19 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein recording the one or more data segments further comprises recording a first data segment of the data service currently used in the transport and a second data segment comprising content that is contextually related to the first data service, and wherein the second data segment is approximately a same amount of data as the amount of data of the first data segment, and wherein when at least one of the first and second data segments have completed, initiating a data service via the data network connection. ### Claim 20 (depends on 15) The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform: retrieving a smart contract from a distributed ledger; invoking the smart contract when the transport is determined to lose the data network connection at the target time; determining, from the smart contract, the estimated amount of network down time based on the route plan.