# US 2020/0396285 A1 · Cell phone synchronization server

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0396285 A1
- Document ID: US20200396285A1
- Status: Published application
- Kind: A1
- Application number: 16/382,172
- Filed: 2019-04-11
- Published: 2020-12-17
- Earliest claimed: 2018-04-11
- Inventors: Adam Scheirman; Robert Dugan; Rayce Stipanovich
- Web page: https://patentgrep.com/patent/US20200396285A1

## CPC

- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04W 4/029: Location-based management or tracking services
- H04W 12/06: Authentication
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The invention is a solution for providing timing and geosynchronous events to clients attending events with devices capable of receiving synchronization data. Through the use of a distributed computing network client devices send and received event based data which is processed by modules on a time synchronization server and clients and client devices can be authorized as to attendance at events and event data can be sent to the devices for timed geosynchronous playback.

## Claims

### Claim 1

A method for a timing based synchronization system comprising:
a. Checking to see if a client is near a synchronization event;
b. Checking to see if said event requires authentication via an Authentication Manager;
c. Checking to see if said event has event time data and if said event time data has passed.

### Claim 2 (depends on 1)

The method of claim 1 further comprising the additional steps of:
a. Said authentication manager determines whether a client device is authorized to participate in an event based on ticketing data before checking to see whether the event time data has passed.

### Claim 3 (depends on 2)

The method of claim 2 wherein the timing based synchronization system further comprises:
a. A control server which sends and receives system data via a communication network with an
i. An administrative device; and
ii. Client Device;
b. Wherein the control server further comprises:
i. An authentication manager;
ii. An event server; and
iii. And a syncing module.

### Claim 4 (depends on 3)

The method of claim 3 wherein the client device further comprises a client interface wherein the client interface further comprises:
a. An inventive interface;
b. A signup interface;
c. A ticketing interface;
d. An event interface; and
e. An event history interface which displays event history data.

### Claim 5

A system for a timing based synchronization system comprising:
a. A control server which sends and receives system data via a communication network with an
i. An administrative device; and
ii. Client Device;
b. Wherein the control server further comprises:
i. An authentication manager;
ii. An event server; and
iii. And an syncing module.

### Claim 6 (depends on 5)

The system of claim 5 wherein the syncing module sends and receives event data via said communications network.

### Claim 7 (depends on 5)

The system of claim 5 wherein the client device further comprises a client interface wherein the client interface further comprises:
a. An inventive interface;
b. A signup interface;
c. A ticketing interface;
d. An event interface; and
e. An event history interface which displays event history data.

### Claim 8 (depends on 7)

The system of claim 7 wherein the syncing module further comprises a time synchronizing module and an event relative start manager.

### Claim 9 (depends on 8)

The system of claim 8 wherein event data further comprises:
a. Event Time Data;
b. Mapping Details;
c. Media Content;
d. Other Synchronous Event Data;
e. Ticketing Data;
f. User Meta Data;
g. Cue Data, wherein cue data further comprises cue action data, cue location data, cue timing data;
h. Event Location Data.