Abstract: An event management architecture (EMA) for managing gaming events includes a plurality of sub-events associated with a gaming event. Each sub-event has at least one sub-event participant and provides a sub-event score to each sub-event participant according to a set of sub-event rules during a sub-event interval. A scheduling coordinator schedules, for each sub-event, the sub-event interval. A registration coordinator registers, for each sub-event, each participant. A scoring processor records, for each sub-event, the sub-event score for each participant, where the sub-event score is converted into a standard format. Each sub-event may be associated with a generic sub-event container, which takes advantage of the common characteristics or functionality requirements of the sub-events to facilitate the management of the sub-events. The EMA minimizes the need to administer the events individually, and can be scalably used to manage complex arrangements of interdependent sub-events of varying types.

Abstract: A system and method of managing delivery of data files receives a user request for a data file and determines a user profile and permission level based upon the received user request. The system and method establishes a delivery file path for the requested data file based upon the user profile and permission level, prioritizes delivery of the requested file based upon the user profile and permission level, and delivers the requested file using the established file path and the prioritization determination. A requester may upgrade their user profile and permission level to gain performance resources to access requested files, and the system re-prioritizes deliveries based on the new levels. If sufficient resources are not available to service a user request, the request enters a delivery queue based upon the user profile and permission level. When resources are available, the system delivers the requested file.

Abstract: An event management architecture (EMA) for managing gaming events includes a plurality of sub-events associated with a gaming event. Each sub-event has at least one sub-event participant and provides a sub-event score to each sub-event participant according to a set of sub-event rules during a sub-event interval. A scheduling coordinator schedules, for each sub-event, the sub-event interval. A registration coordinator registers, for each sub-event, each participant. A scoring processor records, for each sub-event, the sub-event score for each participant, where the sub-event score is converted into a standard format. Each sub-event may be associated with a generic sub-event container, which takes advantage of the common characteristics or functionality requirements of the sub-events to facilitate the management of the sub-events. The EMA minimizes the need to administer the events individually, and can be scalably used to manage complex arrangements of interdependent sub-events of varying types.