Computerized Scenario Development And Execution System

• US 20080235237A1
• Filed: 03/21/2007
• Published: 09/25/2008
• Est. Priority Date: 03/21/2007
• Status: Abandoned Application

• Current Assignee: Talmadge Williams
• Original Assignee: Talmadge Williams
• Inventors: Williams, Talmadge
• Application Number:
  US11/689,410
• Publication Number:
  US 20080235237A1
• Time in Patent Office: Days
• US Class Current: 707/10
• CPC Class Codes: A63F 13/10 Control of the course of the game, e.g. start, progess, end
• CPC Class Codes: A63F 13/12 involving interaction between a plurality of game devices, e.g. transmisison or distribution systems protocols for networked virtual reality, networked games H04L29/06034
• CPC Class Codes: A63F 13/30 Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
• CPC Class Codes: A63F 13/45 Controlling the progress of the video game
• CPC Class Codes: A63F 13/60 Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor
• CPC Class Codes: A63F 13/71 using secure communication between game devices and game servers, e.g. by encrypting game data or authenticating players
• CPC Class Codes: A63F 13/77 involving data related to game devices or game servers, e.g. configuration data, software version or amount of memory
• CPC Class Codes: A63F 2300/407 Data transfer via internet
• CPC Class Codes: A63F 2300/532 using secure communication, e.g. by encryption, authentication
• CPC Class Codes: A63F 2300/534 for network load management, e.g. bandwidth optimization, latency reduction
• CPC Class Codes: A63F 2300/6009 for importing or creating game content, e.g. authoring tools during game development, adapting content to different platforms, use of a scripting language to create content

Abstract

A computer based scenario development and execution system permitting a plurality of players (co-located or geographically dispersed) to execute any number of different scenarios that have been defined to the system and are available for execution. During normal use the Scenario Engine (SE) will be running, a user will log-on to said system, complete an authentication procedure, select a scenario for execution, and receive a response indicating that there is a scenario available requiring an additional user, or a new copy of the requested scenario will be loaded and made available for execution. A scenario is made available for execution by retrieving the Scenario Description Language (SDL) for the scenario from the system'"'"'s library of scenarios, and processing the SDL to provide an executable version of the scenario.

Claims

1. A method of providing a computer-based scenario development and execution system, comprising:

providing a log-on screen on a remote computer console, said log-on screen providing connectivity between a prospective player and a scenario execution server, said server at least partially under the control of a Scenario Engine algorithm;

performing a user verification step for each prospective user requesting to log-on to said server;

allowing each authorized player to select a desired scenario;

providing a scenario previously created using a Scenario Development Language(SDL), said SDL being a high-level programming language that describes a scenario, said SDL comprising;

a THEATER Object;

a DISTRICT Class;

a ELEMENT Class; and

a CONNECTOR Class;

executing each selected scenario using a Scenario Development Language Interpreter (SDLI) in combination with said Scenario Engine algorithm to process user inputs until a conclusion is reached; and

recording a set of scenario statistics upon conclusion of each scenario.

3. The computer-based scenario development and execution system of claim 1 or claim 2, wherein said Scenario Engine algorithm maintains a database, said database contains a record of authorized users, and users'"'"' statistics.

4. The computer-based scenario development and execution system of claim 1 or claim 2, wherein said Scenario Engine algorithm maintains a database, said database contains a record of authorized users, and users'"'"' statistics, wherein said user statistics includes for each user details on every scenario executed including:

scenario title and version, date executed, names of opponent users, scenario result, total number of wins, and total number of losses.

5. The computer-based scenario development and execution system of claim 1 or claim 2, wherein said Scenario Engine algorithm maintains a real-time record of all users and scenarios currently in execution, including, but not limited to, the user identity and the scenario being requested or currently in execution.

6. The computer-based scenario development and execution system of claim 1 or claim 2, wherein for each scenario currently in-execution said Scenario Engine algorithm matches users waiting to execute a selected scenario.

2. The computer-based scenario development and execution system, wherein said components:

Scenario Description Language, Scenario Description Language Interpreter and Scenario Engine algorithm, are stored and executed within a single personal computer shared by all of the scenario users.

7. A computer-based system for developing and executing an active scenario, comprising:

a Scenario Descriptor Language(SDL);

a Scenario Descriptor Language Interpreter (SDLI); and

a Scenario Engine algorithm (SE);

wherein said interpreter (SDLI) receives as inputs statements in said scenario language (SDL) to generate commands and messages for execution by said SE to provide the active scenario on the user'"'"'s computer;

said SDL being a high-level programming language that is utilized to describe a given scenario, comprising;

a THEATER Object;

a DISTRICT Class;

a CONNECTOR Class; and

an ELEMENT Class,

wherein said THEATER Object is responsive to inputs that define;

the layout of the scenario theater or execution environment,

the rules of the scenario execution, and

the conditions defining a win;

wherein said DISTRICT Class comprises Objects which are responsive to inputs that define;

an area of execution within said THEATER, and

the set of said CONNECTOR Objects or moves permitted between said DISTRICTs;

wherein said ELEMENT Class comprises Objects which are responsive to inputs that define;

tokens included in the scenario, the permitted moves associated with each of said tokens, permitted interactions between said tokens, and

permitted interactions with the said DISTRICT(s);

wherein said CONNECTOR Class comprises Objects which are responsive to inputs that define;

at least one permitted move between DISTRICTs;

said SDLI being an interpreter of SDL;

wherein said SDLI is responsive to inputs comprising of statements in said SDL that when processed by said SDLI will result in;

graphical display output by said SE of the scenario theater on each user'"'"'s computer display, and

graphical display output by said SE of the current active scenario tokens and moves on each user'"'"'s computer display;

said SE being an execution engine;

wherein said SE is responsive to commands and

messages from the SDLI which will result in;

accepting as input each user'"'"'s move, updating the graphical display of each user'"'"'s move(s) on the display of the scenario theater,

computing and maintaining each user'"'"'s current score,

terminating the scenario upon determination of a win or tie.

8. The computer-based system of claim 7, wherein the SDL is capable of describing existing, modified existing, and newly developed, versions of scenarios.

9. The computer-based system of claim 7, wherein the SDL descriptions of all the scenarios available for execution on that server or stand-alone personal computer (if not networked) is stored in a database or library.