US 2018/0025135 A1Published application

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

OwnerWayne Odom, Karolyn Geeinventors

Life of this patent

Estimating the term…

Loading patent…

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.

Claims20

Dependent claims

A system comprising:

an authentication server;
and
a modified permission access device in communication with said authentication server, said modified permission access device 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.

3 more elements

A system comprising:

an authentication server;
and
a hardware platform in communication with said authentication server, said platform comprising:
a platform processor physically associated, and in communication, with memory;
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, 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 platform and wherein said at least one wrap includes instructions executable by said platform processor to (a) contact a remote server separate from said platform to prompt said remote server to transmit an executable application to said platform, (b) install said application into said memory, collect identifying information about said platform and transmit said identifying information to said remote server, authenticate said platform using said application, and, upon authentication of said platform, create a user account associated with said platform using said identifying information, and (c) only when said platform 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 platform processor to only permit said platform 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 platform 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 platform 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 platform 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.

3 more elements

A system comprising:

an authentication server;
a plurality of hardware platforms in communication with said authentication server each having a unique platform identification, each said platform comprising:
a platform processor physically associated, and in communication, with memory;
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, an executable sensor and a vault which secures data, an executable detector, and at least one executable wrap which secures an executable controller, wherein said data secured by said wrap includes a permissions file defining transaction requests permitted by said platform and wherein said at least one wrap includes instructions executable by said platform processor to (a) contact a remote server separate from said platform to prompt said remote server to transmit an executable application to said platform, (b) install said application into said memory, collect identifying information about said platform and transmit said identifying information to said remote server, authenticate said platform using said application, and, upon authentication of said platform, create a user account associated with said platform using said identifying information and said unique platform identification, and (c) only when said platform 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 platform processor to only permit said platform 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 platform 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 platform 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 platform 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 platforms having an application server processor operative to execute program instructions to conduct the steps of:
receiving a transaction request from at least one of said platforms, wherein said data secured by said wrap includes instructions for each said platform to transmit said transaction request from said platform to said application server only if said transaction request is permitted by said unique permissions file stored at said platform, wherein said transaction request includes the unique platform identification for each platform associated with said transaction request;
authenticating said platform from which said transaction request was received;
generating a single transaction code after authenticating said platform from which said transaction request was received such that each platform associated with said transaction request utilizes the same transaction code;
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;
and
authenticating said transaction code received from said application server;
a data server in communication via a connection 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;
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, at least one account, an account history for each said account, and program instructions executable by said data server processor to conduct the steps of:
conducting a transaction for at least one account in response to said transaction request;
and
recording said transaction in said account history for said account.

21 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/715,105Filed 25 Sep 2017
Priority: 6 Apr 2012
Published: 25 Jan 2018
Term ends: Not estimatedThe source records don’t support an estimate.

Classification39 codes

H04L 67/02
Protocols: based on web technology, e.g. hypertext transfer protocol [HTTP]
G06F 9/46
Using stored programs, i.e. using an internal store of processing equipment to receive or retain programs: multiprogramming arrangements
G06F 9/5016
The resources being hardware resources other than CPUs, Servers and Terminals: the resource being the memory
G06F 9/5038
The resource being a machine, e.g. CPUs, Servers, Terminals: considering the execution order of a plurality of tasks, e.g. taking priority or time…

Family

Application13/441,675Continuation in part · filed 6 Apr 2012
Application13/708,661Continuation in part · filed 7 Dec 2012
Application13/898,460Continuation in part · filed 20 May 2013
Application14/065,402Continuation in part · filed 28 Oct 2013
Application14/216,438Continuation in part · filed 17 Mar 2014
Application14/493,284Continuation in part · filed 22 Sep 2014
Application14/720,925Continuation in part · filed 25 May 2015
Application15/194,551Continuation in part · filed 27 Jun 2016
Application15/418,399Continuation in part · filed 27 Jan 2017
Application15/489,275Continuation in part · filed 17 Apr 2017
Application15/715,105Continuation in part
US 2012/0192274 A1Published application
US 2014/0053283 A1Published application
US 2014/0201810 A1Published application
US 2015/0012758 A1Published application
US 2015/0254438 A1Published application
US 2016/0344721 A1Published application
US 2017/0220781 A1Published application
US 8,375,455 B2Related patent
US 8,448,236 B1Related patent
US 8,572,720 B1Related patent
US 8,677,510 B2Related patent
US 8,844,054 B2Related patent
US 9,043,934 B2Related patent
US 9,378,339 B2Related patent
US 9,590,981 B2Related patent
US 9,628,473 B1Related patent
US 9,773,099 B2Related patent
US 9,910,969 B2Related patent
US 2018/0025135 A1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key