System, method, and device for delivering communications and storing and delivering data

• US 10,291,619 B2
• Filed: 03/05/2018
• Issued: 05/14/2019
• Est. Priority Date: 04/06/2012
• Status: Active Grant

• Current Assignee: Karolyn Gee
• Original Assignee: Karolyn Gee, Wayne Odom
• Inventors: Odom, Wayne, Gee, Karolyn
• Primary Examiner(s): Popham, Jeffrey D.
• Application Number:
  US15/912,565
• Publication Number:
  US 20180234422A1
• Time in Patent Office: 435 Days
• CPC Class Codes: G06F 21/1078 Logging; Metering
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications

Abstract

A system, method, and device includes a platform data storage that stores a wrap that secures an executable controller and executable sensors. The wrap is verified, optionally through a downloaded authentication driver. After verifying the wrap, the wrap is opened and a sister of the executable controller is installed into the platform memory to cooperate with the executable controller. Additionally or alternatively, the authentication driver may cooperate with the executable controller. The executable controller allows the platform processor to access data secured in a vault and/or verify the platform to create a connection to an application server.

Claims

1. A system comprising:

a hardware platform;

an application server in communication with said platform having an application server processor operative to execute specified program instructions to conduct the steps of;

receiving a specific transaction request from said platform, wherein said transaction request includes a reference to a last completed transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated the last transaction or installed new application;

authenticating said platform;

generating a new transaction code after authenticating said platform and

specific platform application request or requirements;

opening an application server port identified by an application server port address;

reconnecting to said authenticated platform via said application server port at said application server port address; and

communicating between said application server and said authenticated platform via said application server port;

wherein if the transaction request includes a specific reference to a previous related transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated a previous transaction for any type of refund, inventory replacement, or smart contract procedures are required to be included and authenticated within the transaction locks;

whereas if no related previous transaction history is required then normal application procedures continue to authenticate transaction balances for all parties;

an authorization server in communication with said application server, said authorization server having an authorization server processor operative to execute program instructions to conduct the steps of;

receiving said transaction code from said application server;

authenticating said transaction code received from said application server; and

recording the receipt of said transaction code from said application server in a database of database records;

at least one custodian server in communication with said authorization server, said custodian server having a custodian server processor operative to execute program instructions to conduct the steps of;

opening a connection to said application server after said authorization server has authenticated said transaction code;

receiving said transaction request from said application server;

verifying said transaction request;

generating a transaction authorization key after verifying said transaction request; and

transmitting said transaction authorization key to said application server authorizing said transaction request after verifying said transaction request; and

a data server in communication with said application server, said data server comprising;

a data server processor;

a data server communication device controlled by said data server processor and operative for selective communication with said application server via ports assigned by said data server processor; and

a data server data storage readable by said data server processor, wherein said data server data storage is operative to store, in non-volatile storage, program instructions executable by said data server processor to conduct the steps of;

communicating between said data server and said application server via said secure random socket connection including recording a database record at said data server data storage of said transaction request along with said transaction key and any reference to a related transaction request; and

locking each database record lock in said data server data storage in chronological sequence after being recorded and allowing read only capability of locks by identified internal network servers.

2. The system of claim 1 further comprising:

an authentication server in communication with said platform, wherein said platform comprises a platform processor physically associated, and in communication, with memory, wherein said platform processor is operative to run a platform operating system, and a data storage physically separate from said memory and readable by said platform processor, wherein said data storage is operative to store, in non-volatile storage, a vault which secures data and at least one executable wrap which secures an executable controller, wherein said at least one wrap includes instructions executable by said platform processor to (a) contact said authentication server to prompt said authentication server to transmit an executable authentication driver to said platform, (b) install said authentication driver into said memory and authenticate said platform using said authentication driver, and (c) only when said platform is authenticated using said authentication driver, control said authentication driver in said memory to cooperate with said executable controller in said data storage to automatically and continuously permit or deny access by said platform processor to only permit said platform processor to access said secure data protected by said vault when both said authentication driver in said memory and said executable controller in said data storage are accessible and to otherwise deny access, wherein said platform processor can execute only said authentication driver and is prevented by said at least one wrap from executing said executable controller directly.

3. The system of claim 1 further comprising:

an authentication server in communication with said platform, and wherein said platform comprises a modified permission access device having a modified permission access device processor physically associated, and in communication, with memory, and a data storage physically separate from said memory and readable by said modified permission access device processor, wherein said data storage is operative to store, in non-volatile storage, an executable sensor and a vault which secures data, an executable detector, and at least one executable wrap which secures an executable controller, custom libraries, and a permissions file defining transaction requests permitted by said modified permission access device and wherein said at least one wrap includes instructions executable by said modified permission access device processor to (a) contact a remote server separate from said modified permission access device to prompt said remote server to transmit an executable application to said modified permission access device, (b) install said application into said memory, collect identifying information about said modified permission access device and transmit said identifying information to said remote server, authenticate said modified permission access device using said application, and, upon authentication of said modified permission access device, create a user account associated with said modified permission access device using said identifying information, and (c) only when said modified permission access device is authenticated using said application, install said executable sensor to said memory, wherein said application in said memory cooperates with said executable controller in said data storage to automatically and continuously permit or deny access by said modified permission access device processor to only permit said modified permission access device processor to access said secure data protected by said vault when both said application in said memory and said executable controller in said data storage are accessible and to otherwise deny access, wherein said modified permission access device processor can execute only said application and is prevented by said at least one wrap from executing said executable controller directly, and wherein said executable sensor is operative to monitor at least one of said modified permission access device and said data storage for anomalies and, upon detecting an anomaly, deny access to said secure data secured by said vault by said executable sensor deleting said application from said memory upon detecting an anomaly thereby rendering said secure data inaccessible to said modified permission access device processor, and wherein said executable detector is operative to confirm the integrity of said data secured by said vault and, in the event that the integrity of said data is unconfirmed, rendering said executable controller inoperable for said unconfirmed data.

4. The system of claim 1 wherein said program instructions executable by said data server processor further comprise:

establishing a connection to said at least one custodian server via said data server communication device upon a predetermined event detected by said data server processor; and

communicating between said data server and said at least one custodian server via said connection.

5. The system of claim 1 wherein said transaction request includes at least one transaction and said program instructions executable by said data server processor further comprise said data server processor conducting said at least one transaction contained in said transaction request.

6. The system of claim 5 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for said transaction amount.

7. The system of claim 5 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for an amount different from said transaction amount.

8. The system of claim 1 comprising a plurality of custodian servers each having a custodian server processor, wherein said step of generating a transaction authorization key comprises generating a transaction authorization key having a plurality of components with at least two of said plurality of custodian servers adding a component to said transaction authorization key after verifying said transaction request.

9. A system comprising:

an authentication server;

a modified permission access device in communication with said authentication server comprising;

a modified permission access device processor physically associated, and in communication, with memory; and

a data storage physically separate from said memory and readable by said modified permission access device processor, wherein said data storage is operative to store, in non-volatile storage, an executable sensor and a vault which secures data, an executable detector, and at least one executable wrap which secures an executable controller, custom libraries, and a permissions file defining transaction requests permitted by said modified permission access device and wherein said at least one wrap includes instructions executable by said modified permission access device processor to (a) contact a remote server separate from said modified permission access device to prompt said remote server to transmit an executable application to said modified permission access device, (b) install said application into said memory, collect identifying information about said modified permission access device and transmit said identifying information to said remote server, authenticate said modified permission access device using said application, and, upon authentication of said modified permission access device, create a user account associated with said modified permission access device using said identifying information, and (c) only when said modified permission access device is authenticated using said application, install said executable sensor to said memory, wherein said application in said memory cooperates with said executable controller in said data storage to automatically and continuously permit or deny access by said modified permission access device processor to only permit said modified permission access device processor to access said secure data protected by said vault when both said application in said memory and said executable controller in said data storage are accessible and to otherwise deny access, wherein said modified permission access device processor can execute only said application and is prevented by said at least one wrap from executing said executable controller directly, and wherein said executable sensor is operative to monitor at least one of said modified permission access device and said data storage for anomalies and, upon detecting an anomaly, deny access to said secure data secured by said vault by said executable sensor deleting said application from said memory upon detecting an anomaly thereby rendering said secure data inaccessible to said modified permission access device processor, and wherein said executable detector is operative to confirm the integrity of said data secured by said vault and, in the event that the integrity of said data is unconfirmed, rendering said executable controller inoperable for said unconfirmed data;

an application server in communication with said modified permission access device having an application server processor operative to execute program instructions to conduct the steps of;

receiving a transaction request from said modified permission access device, wherein said transaction request includes a reference to a specific previous related transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated a previous transaction for any type of refund, inventory replacement, or smart contract procedures are required to be included and authenticated within the transaction locks;

whereas if no related previous transaction history is required then normal application procedures continue to authenticate transaction balances for all parties;

authenticating said modified permission access device;

generating a transaction code after authenticating said modified permission access device;

opening an application server port identified by an application server port address;

reconnecting to said authenticated modified permission access device via said application server port at said application server port address; and

communicating between said application server and said authenticated modified permission access device via said application server port;

an authorization server in communication with said application server, said authorization server having an authorization server processor operative to execute program instructions to conduct the steps of;

receiving said transaction code from said application server;

authenticating said transaction code received from said application server; and

recording the receipt of said transaction code from said application server in a database of database records;

at least one custodian server in communication with said authorization server, said custodian server having a custodian server processor operative to execute program instructions to conduct the steps of;

opening a connection to said application server after said authorization server has authenticated said transaction code;

receiving said transaction request from said application server;

verifying said transaction request;

generating a transaction authorization key after verifying said transaction request; and

transmitting said transaction authorization key to said application server authorizing said transaction request after verifying said transaction request; and

a data server in communication with said application server, said data server comprising;

a data server processor;

a data server communication device controlled by said data server processor and operative for selective communication with said application server via ports assigned by said data server processor; and

a data server data storage readable by said data server processor, wherein said data server data storage is operative to store, in non-volatile storage, program instructions executable by said data server processor to conduct the steps of;

communicating between said data server and said application server via said secure random socket connection including recording a database record at said data server data storage of said transaction request along with said transaction key and any reference to a related transaction request; and

locking each lock database record in said data server data storage in chronological sequence after being recorded and allowing read only capability of stored locks by identified internal network servers for validation of current transaction.

10. The system of claim 9 wherein said program instructions executable by said data server processor further comprise:

establishing a connection to said at least one custodian server via said data server communication device upon a predetermined event detected by said data server processor; and

communicating between said data server and said at least one custodian server via said connection.

11. The system of claim 9 wherein said transaction request includes at least one transaction and said program instructions executable by said data server processor further comprise said data server processor conducting said at least one transaction contained in said transaction request.

12. The system of claim 11 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for said transaction amount if no previous transaction history is required to be included that may effect transaction fees then normal application procedures continue to authenticate transaction balances for all parties.

13. The system of claim 11 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for an amount different from said transaction amount in reference to a specific previous related transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated a previous transaction for any type of refund, inventory replacement, or smart contract procedures are required to be included and authenticated within the transaction locks at lower specific fees.

14. The system of claim 9 comprising a plurality of custodian servers each having a custodian server processor, wherein said step of generating a transaction authorization key comprises generating a transaction authorization key having a plurality of components with at least two of said plurality of custodian servers adding a component to said transaction authorization key after verifying said transaction request.

15. A system comprising:

an authentication server;

a platform in communication with said authentication server comprising;

a platform processor physically associated, and in communication, with memory, wherein said platform processor is operative to run a platform operating system; and

a data storage physically separate from said memory and readable by said platform processor, wherein said data storage is operative to store, in non-volatile storage, a vault which secures data and at least one executable wrap which secures an executable controller, wherein said at least one wrap includes instructions executable by said platform processor to (a) contact said authentication server to prompt said authentication server to transmit an executable authentication driver to said platform, (b) install said authentication driver into said memory and authenticate said platform using said authentication driver, and (c) only when said platform is authenticated using said authentication driver, control said authentication driver in said memory to cooperate with said executable controller in said data storage to automatically and continuously permit or deny access by said platform processor to only permit said platform processor to access said secure data protected by said vault when both said authentication driver in said memory and said executable controller in said data storage are accessible and to otherwise deny access, wherein said platform processor can execute only said authentication driver and is prevented by said at least one wrap from executing said executable controller directly;

an application server in communication with said platform having an application server processor operative to execute program instructions to conduct the steps of;

receiving a transaction request from said platform, wherein said transaction request includes a reference to a previous related transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated the previous transaction for any type of refund, inventory replacement, or smart contract procedures must be included and authenticated within the transaction locks;

authenticating said platform;

generating a transaction code after authenticating said platform;

opening an application server port identified by an application server port address;

reconnecting to said authenticated platform via said application server port at said application server port address; and

communicating between said application server and said authenticated platform via said application server port;

an authorization server in communication with said application server, said authorization server having an authorization server processor operative to execute program instructions to conduct the steps of;

receiving said transaction code from said application server;

authenticating said transaction code received from said application server; and

recording the receipt of said transaction code from said application server in a database of database records;

at least one custodian server in communication with said authorization server, said custodian server having a custodian server processor operative to execute program instructions to conduct the steps of;

opening a connection to said application server after said authorization server has authenticated said transaction code;

receiving said transaction request from said application server;

verifying said transaction request;

generating a transaction authorization key after verifying said transaction request; and

transmitting said transaction authorization key to said application server authorizing said transaction request after verifying said transaction request; and

a data server in communication with said application server, said data server comprising;

a data server processor;

a data server communication device controlled by said data server processor and operative for selective communication with said application server via ports assigned by said data server processor; and

a data server data storage readable by said data server processor, wherein said data server data storage is operative to store, in non-volatile storage, program instructions executable by said data server processor to conduct the steps of;

communicating between said data server and said application server via said secure random socket connection including recording a database record at said data server data storage of said transaction request along with said transaction key and any reference to a related transaction request; and

locking each database lock record in said data server data storage in chronological sequence after being recorded and allowing read only capability of locks by identified internal network servers for current and future transaction validation.

16. The system of claim 15 wherein said program instructions executable by said data server processor further comprise:

establishing a connection to said at least one custodian server via said data server communication device upon a predetermined event detected by said data server processor; and

communicating between said data server and said at least one custodian server via said connection.

17. The system of claim 15 wherein said transaction request includes at least one transaction and said specific program instructions executable by said data server processor further comprise said data server processor conducting said at least one transaction contained in said transaction request.

18. The system of claim 17 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for said transaction amount.

19. The system of claim 17 wherein said transaction request includes a transaction amount and said step of conducting said at least one transaction includes conducting said transaction for an amount different from said transaction amount in reference to a specific previous related transaction lock number, transaction id and authorization key stored on platform electronic receipt vault that originated a previous transaction that may require a type of refund, inventory replacement or smart contract procedures is required to be included and authenticated within the transaction locks with explanation of specific fees.

20. The system of claim 15 comprising a plurality of custodian servers each having a custodian server processor, wherein said step of generating a transaction authorization key comprises generating a transaction authorization key having a plurality of components with at least two of said plurality of custodian servers adding a component to said transaction authorization key after verifying said transaction request.