MANAGING TRANSPORT OCCUPANTS DURING TRANSPORT EVENTS

1 . A method, comprising:

identifying a target device has entered a transport and has initiated a transport event at a target location;

applying permissions, associated with the target device, to the transport event;

determining a transport event modification has occurred, when the transport has stopped moving for a predetermined period of time and one or more transport operations have occurred, prior to arriving at a transport event destination;

determining whether the permissions permit the transport event modification; and

notifying one or more registered devices associated with the target device of the transport event modification.

2 . The method of claim 1 , further comprising:

receiving a request to perform the transport event modification during the transport event;

determining whether the request originated from one or more of the registered devices; and

responsive to determining the request originated from one or more of the registered devices, permitting the transport event modification.

3 . The method of claim 2 , further comprising:

responsive to permitting the transport event modification, adding another destination location to the transport event as a next destination for the transport; and

determining an estimated amount of transport stop time and one or more of the transport operations which are expected to occur during the transport stop time.

4 . The method of claim 3 , further comprising:

identifying the transport has arrived at the next destination;

determining whether an amount of transport stop time has exceeded the estimated amount of transport stop time;

determining whether the one or more expected transport operations have occurred during the transport stop time; and

notifying one or more of the registered devices when at least one of the amount of transport stop time has exceeded the estimated amount of transport stop time and at least one prohibited transport operation has occurred during the transport stop time.

5 . The method of claim 1 , further comprising:

receiving a request to perform the transport event modification during the transport event;

determining the request originated from the target device;

determining the request comprises a modified destination;

retrieving a user device profile associated with a user device associated with the modified destination;

transmitting a request for confirmation of the transport event modification to the user device associated with the modified destination;

transmitting a request for permission to the one or more registered devices; and

responsive to receiving a confirmation from the user device associated with the modified destination and a permission response from the one or more registered devices, permitting the transport event modification.

6 . The method of claim 1 , further comprising:

retrieving a smart contract from a distributed ledger;

invoking the smart contract responsive to identifying the transport event; and

determining, from the smart contract, the target device requires a specific category of transport and is permitted to be transported to one or more identified destination locations.

7 . The method of claim 6 , further comprising:

creating a blockchain transaction comprising a date of the transport event, a time of the transport event, the target location, a transport event destination and transport identification information; and

storing the blockchain transaction in the distributed ledger.

8 . A system, comprising:

a server configured to:

identify a target device has entered a transport and has initiated a transport event at a target location;

apply permissions, associated with the target device, to the transport event;

determine a transport event modification has occurred, when the transport has stopped movement for a predetermined period of time and one or more transport operations have occurred, prior to arrival at a transport event destination;

determine whether the permissions permit the transport event modification; and

notify one or more registered devices associated with the target device of the transport event modification.

9 . The system of claim 8 , the server configured to:

receive a request to perform the transport event modification during the transport event;

determine whether the request originated from one or more of the registered devices; and

responsive to determination that the request originated from one or more of the registered devices, permit the transport event modification.

10 . The system of claim 9 , the server configured to:

responsive to permit the transport event modification, add another destination location to the transport event as a next destination for the transport; and

determine an estimated amount of transport stop time and one or more of the transport operations which are expected to occur during the transport stop time.

11 . The system of claim 10 , the server configured to:

identify the transport has arrived at the next destination;

determine whether an amount of transport stop time has exceeded the estimated amount of transport stop time;

determine whether the one or more expected transport operations have occurred during the transport stop time; and

notify one or more of the registered devices when at least one of the amount of transport stop time has exceeded the estimated amount of transport stop time and at least one prohibited transport operation has occurred during the transport stop time.

12 . The system of claim 9 , the server configured to:

receive a request to perform the transport event modification during the transport event;

determine the request originated from the target device;

determine the request comprises a modified destination;

retrieve a user device profile associated with a user device associated with the modified destination;

transmit a request for confirmation of the transport event modification to the user device associated with the modified destination;

transmit a request for permission to the one or more registered devices; and

responsive to receive a confirmation from the user device associated with the modified destination and a permission response from the one or more registered devices, permit the transport event modification.

13 . The system of claim 8 , the server configured to:

retrieve a smart contract from a distributed ledger;

invoke the smart contract responsive to the identified transport event; and

determine, from the smart contract, the target device requires a specific category of transport and is permitted to be transported to one or more identified destination locations.

14 . The system of claim 13 , the server configured to:

create a blockchain transaction comprising a date of the transport event, a time of the transport event, the target location, a transport event destination and transport identification information; and

store the blockchain transaction in the distributed ledger.

15 . A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:

identifying a target device has entered a transport and has initiated a transport event at a target location;

applying permissions, associated with the target device, to the transport event;

determining a transport event modification has occurred, when the transport has stopped moving for a predetermined period of time and one or more transport operations have occurred, prior to arriving at a transport event destination;

determining whether the permissions permit the transport event modification; and

notifying one or more registered devices associated with the target device of the transport event modification.

16 . The non-transitory computer readable medium of claim 15 , further comprising:

receiving a request to perform the transport event modification during the transport event;

determining whether the request originated from one or more of the registered devices; and

responsive to determining the request originated from one or more of the registered devices, permitting the transport event modification.

17 . The non-transitory computer readable medium of claim 16 , further comprising:

responsive to permitting the transport event modification, adding another destination location to the transport event as a next destination for the transport; and

determining an estimated amount of transport stop time and one or more of the transport operations which are expected to occur during the transport stop time.

18 . The non-transitory computer readable medium of claim 17 , further comprising:

identifying the transport has arrived at the next destination;

determining whether an amount of transport stop time has exceeded the estimated amount of transport stop time;

determining whether the one or more expected transport operations have occurred during the transport stop time; and

notifying one or more of the registered devices when at least one of the amount of transport stop time has exceeded the estimated amount of transport stop time and at least one prohibited transport operation has occurred during the transport stop time.

19 . The non-transitory computer readable medium of claim 15 , further comprising:

receiving a request to perform the transport event modification during the transport event;

determining the request originated from the target device;

determining the request comprises a modified destination;

retrieving a user device profile associated with a user device associated with the modified destination;

transmitting a request for confirmation of the transport event modification to the user device associated with the modified destination;

transmitting a request for permission to the one or more registered devices; and

responsive to receiving a confirmation from the user device associated with the modified destination and a permission response from the one or more registered devices, permitting the transport event modification.

20 . The non-transitory computer readable medium of claim 15 , further comprising:

retrieving a smart contract from a distributed ledger;

invoking the smart contract responsive to identifying the transport event; and

determining, from the smart contract, the target device requires a specific category of transport and is permitted to be transported to one or more identified destination locations.