Event Management System Using Member Scope Interaction Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event management systems lack a simple user interface and effective interaction control between participants and devices, making it difficult for event creators and participants to easily manage and interact within events.
Innovation Solution
An event management system utilizing an API database and event database with an API registration processing unit, event creation processing unit, and communication processing unit, which employs a 'member scope' to control interactions between participants and devices, allowing for easy event creation and participation, and providing advanced interaction control through attribute management and scenario execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an event management system is designed with comprehensive management functions, then the system's functionality and control capability are improved, but the user interface complexity and ease of operation deteriorate
Solution Approach 1:
The system segments event management into standardized scenarios that can be independently selected and configured. Each scenario represents a modular functional unit that can be combined to create comprehensive event management capabilities while presenting a simplified interface to users through scenario-based selection rather than exposing individual management functions.
Solution Approach 2:
The patent introduces scenario definitions as an intermediary layer between the user and the complex event management system. Scenarios act as pre-configured templates that mediate between user intentions and system functions, allowing users to select high-level scenarios rather than directly managing complex individual functions, thus simplifying the interface while maintaining comprehensive functionality.
2Adaptability or versatility
If the system provides detailed interaction control between participants, then the interaction management capability is improved, but the device complexity increases
Solution Approach 1:
The system segments interaction control into participant scope definitions that separate the control logic from the underlying system complexity. By defining scopes at the participant level rather than implementing complex permission matrices, the system achieves detailed interaction control while maintaining simpler system architecture.
Solution Approach 2:
The patent implements dynamic scope assignment where participant scopes can be flexibly configured and changed during event execution. This dynamic approach allows detailed interaction control adaptability without requiring complex static permission structures, reducing overall system complexity while maintaining high control capability.
3Reliability
If event management functions are hard-coded in the server, then the system reliability is improved, but the adaptability and reusability across different events deteriorate
Solution Approach 1:
The system performs preliminary configuration by defining reusable scenario templates and participant scope definitions before events are executed. These pre-defined structures are stored in the database and can be reliably executed across multiple events, providing both system reliability through standardized processes and adaptability through template reusability.
Solution Approach 2:
The patent creates universal scenario definitions and scope templates that can be applied across different event types and contexts. Rather than hard-coding event-specific logic, the system uses universal templates that can be configured for various events, improving reusability while maintaining reliability through consistent execution of standardized templates.
4Stability of the object's composition
If the system uses traditional event management architecture, then the implementation stability is improved, but the cost-effectiveness and flexibility deteriorate
Solution Approach 1:
The system segments event management into reusable scenario templates and scope definitions that can be independently developed, tested, and deployed. This segmentation allows stable core functions to be implemented once and reused across multiple events, improving cost-effectiveness while maintaining implementation stability through standardized modular components.
Solution Approach 2:
The patent implements copying and reusing of scenario templates and scope definitions across different events. Rather than re-implementing event management logic for each event, the system copies proven templates and adapts them, reducing development costs and improving efficiency while maintaining stable, tested implementations.
Data Source
AI summary
[Problem]To allow an event creator to create an executable program easily[Means of Solution]An event management system comprising an API database that stores an event execution management API and a resource management API,an event database, an API registration processing unit, an event creation processing unit, an event registration processing unit that determines whether an event execution program accords with criteria and registers, in the event database, an event execution program whose result is affirmative,and a communication processing unit that carries out transmission and reception, wherein the event execution program controls, by using an object called a member scope which is an array of groups and is a set of participant groups, an interaction between a plurality of event participants or a plurality of devices, and further executes control by using an attribute, a current processing group, and one or more functions to perform a set operation or a relevance extraction operation.