Authenticated modifications of multi-party ledger data during user connectivity via in-flight systems
A central computing platform provides users with control over multi-party information involving third-party services during different stages of a travel journey, or while users are provided with data connectivity via different networks or systems. The central computing platform provides a digital ledger on which the multi-party information is recorded. Recording of the multi-party information, as well as modification thereof, requires authentication of each party as well as input (e.g., approval) by the computing platform. The central computing platform can be communicatively coupled with local networks, such as cellular networks, as well as mobile platforms or in-vehicle connectivity systems to which user devices can be connected. As a result, the central computing platform is involved in generation, recording, modification, and fulfillment of multi-party arrangements between users and third-party services.
1 . A computing system comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the computing system to:
provide a digital ledger configured to store ledger entries for users and third-party services based on validations determined by the computing system;
while a user has a first data connectivity provided by a network, generate a ledger entry on the digital ledger to define a contract between a digital identity of the user and a third-party service;
subsequent to the user switching to a second data connectivity provided by an in-vehicle system of a commercial passenger vehicle: detect, from the in-vehicle system, a request by the user to modify the ledger entry on the digital ledger;
validate authentication data obtained from the in-vehicle system relating to the request, the authentication data associated with the digital identity of the user and an identity of the third-party service; and
based on the authentication data being validated, modify the ledger entry on the digital ledger according to the request.
2 . The computing system of claim 1 , wherein the authentication data includes a digital certificate assigned to the third-party service by the computing system and stored, on a user device of the user with the second data connectivity, by a client application that is associated with the third-party service.
3 . The computing system of claim 1 , wherein the request is detected from the in-vehicle system based on a network edge connection between the in-vehicle system and the computing system.
4 . The computing system of claim 1 , wherein the request is detected subsequent to the user being located in the commercial passenger vehicle and the commercial passenger vehicle being located outside of a coverage range of the network.
5 . The computing system of claim 1 , wherein the digital ledger is a distributed ledger maintained by a plurality of computing systems that includes a third-party computing system associated with the third-party service, wherein the modified ledger entry is retrieved by the third-party computing system for the third-party service to provide a modified product or service to the user.
6 . The computing system of claim 1 , wherein the request is detected based on a user device of the user communicating with, via the second data connectivity provided by the in-vehicle system, a hosted application associated with the third-party service and through which the contract is defined.
7 . The computing system of claim 1 , wherein the instructions cause the computing system to:
obtain a timestamp and a vehicle location for the request from the in-vehicle system; and
include the timestamp and the vehicle location with the modified ledger entry on the digital ledger.
8 . The computing system of claim 1 , wherein the network is a terrestrial cellular network that provides the first data connectivity to the user while the user is located below a particular altitude, and wherein the computing system generates the ledger entry based on being communicatively coupled with a hosted application associated with the third-party service through which the contract is defined.
9 . The computing system of claim 1 , wherein the instructions cause the computing system to:
receive, from a third-party system associated with the third-party service, an indication of a second contract between the digital identity of the user and the third-party service;
while the second data connectivity is provided to the user, cause the in-vehicle system to provide the indication of the second contract to the user device based on validating the digital identity of the user and the indication received from the third-party system; and
in response to detecting from the in-vehicle system that the user accepted the second contract via the second data connectivity, generate a second ledger entry on the digital ledger for the second contract.
10 . The computing system of claim 1 , wherein the computing system and the in-vehicle system are associated with an issuing authority that generated the authentication data.
11 . The computing system of claim 1 , wherein the user transfers to one or more other commercial passenger vehicles operated by a mobility entity different than that of the commercial passenger vehicle, and wherein the computing system is communicatively coupled with respective in-vehicle systems of the one or more other commercial passenger vehicles.
12 . An in-vehicle system comprising a processor and a memory storing instructions that, when executed by the processor, cause the in-vehicle system to:
provide data connectivity to a user device located onboard a commercial passenger vehicle on which the in-vehicle system is implemented, wherein the data connectivity enables a communication between the user device and a server associated with a third-party service;
receive, from the user device, a request to modify multi-party ledger data recorded on a digital distributed ledger, the multi-party ledger data defining a contract between a user identity represented by the user device and the third-party service; and
connect to a remote computing platform that provides the digital distributed ledger to modify the multi-party ledger data, wherein the remote computing platform is located external to the commercial passenger vehicle.
13 . The in-vehicle system of claim 12 , wherein connecting to the computing platform includes providing authentication data associated with the user identity and the third-party service to the remote computing platform.
14 . The in-vehicle system of claim 13 , wherein the instructions cause the in-vehicle system to:
obtain the authentication data with the request, the authentication data including a digital certificate associated with the server and that is validated by the computing platform prior to the multi-party ledger data being modified.
15 . The in-vehicle system of claim 13 , wherein the authentication data includes a digital certificate associated with the user identity and provided by the user device based on a biometric security input by a user of the user device.
16 . The in-vehicle system of claim 12 , wherein the instructions cause the in-vehicle system to:
determine a timestamp and a vehicle location at which the request was received; and
transmit the timestamp and the vehicle location to the computing platform to cause the computing platform to include the timestamp and the vehicle location with the multi-party ledger data.
17 . The in-vehicle system of claim 12 , wherein the in-vehicle system provides the data connectivity to the user device subsequent to the commercial passenger vehicle being outside of a coverage range of a network that previously provided a second data connectivity to the user device, wherein the multi-party ledger data was previously recorded on the digital distributed ledger via the second data connectivity provided by the network to the user device.
18 . The in-vehicle system of claim 12 , wherein the commercial passenger vehicle is associated with a first mobility entity, and wherein the instructions cause the in-vehicle system to:
determine that a user of the user device will be transferring to a second commercial passenger vehicle that is operated by a second mobility entity; and
notify a second in-vehicle system implemented on the second commercial passenger vehicle regarding the user transferring to the second commercial passenger vehicle.
19 . A method comprising:
providing, by a processor of a computing platform, a digital ledger configured to store ledger entries for users and third-party services based on validations determined by the computing platform;
generating, by the processor, a ledger entry on the digital ledger to define a contract between a digital identity of a user and a third-party service;
while an in-vehicle system of a commercial passenger vehicle provides a limited data connectivity to the user, detecting, from the in-vehicle system by the processor, a request by the user to modify the ledger entry on the digital ledger;
obtaining, from the in-vehicle system by the processor, authentication data relating to the request by the user; and
based on validating at least the digital identity of the user via the authentication data, modifying, by the processor, the ledger entry on the digital ledger according to the request.
20 . The method of claim 19 , wherein the authentication data includes a digital certificate assigned to the third-party service by the computing platform, and wherein the ledger entry is modified further based on validating an identity of the third-party service via the digital certificate.
21 . The method of claim 19 , wherein the ledger entry is generated in response to communications between the user and the third-party service via a data connectivity provided by a network while the user is outside of the vehicle.
22 . The method of claim 19 , wherein the request is detected from the in-vehicle system based on a network edge connection between the in-vehicle system and the processor of the computing platform.
23 . The method of claim 19 , wherein the commercial passenger vehicle is one of a plurality of commercial passenger vehicles on which a user embarks before the contract is fulfilled, and wherein the plurality of commercial passenger vehicles are operated by one or more mobility entities.