Third-Party Program Invocation in Messaging Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for users to invoke third-party programs in messaging systems are inconvenient, difficult, and often yield inaccurate results, as they require searching through app stores or traversing category trees.
Innovation Solution
A system and method for registering third-party programs with triggering conditions, such as keywords, and monitoring chat session events to automatically invoke relevant programs as additional participants, using a registry to associate conditions with programs and invoking them when the conditions are met.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If users search for third-party programs in app stores or traverse category trees, then they can locate available programs, but the process becomes inconvenient, difficult, and yields inaccurate results
Solution Approach 1:
The system performs preliminary actions by monitoring chat events in real-time and proactively presenting relevant third-party programs before users need to search. The event monitoring component continuously watches for triggering conditions, and when matched, the system automatically retrieves and presents relevant programs, eliminating the need for users to manually search through app stores.
Solution Approach 2:
The patent introduces an intermediary event monitoring component that acts as a mediator between chat events and third-party programs. This component receives triggering conditions from programs, monitors chat events, and automatically connects users with relevant programs by presenting them when conditions are met, thereby improving both accuracy and convenience.
2Ease of operation
If the system monitors chat events and automatically invokes third-party programs when triggering conditions are met, then the invocation process becomes more convenient and accurate, but the system complexity increases
Solution Approach 1:
The system is segmented into distinct functional components: an event monitoring component that watches chat events, a program management component that stores triggering conditions and program information, and an invocation component that executes the invocation process. This segmentation allows each component to handle specific tasks independently, managing complexity through modular design.
Solution Approach 2:
The event monitoring component serves multiple functions: it monitors chat events in real-time, compares events against stored triggering conditions, identifies matches, and initiates invocation processes. This multi-functionality reduces the need for separate specialized components, thereby managing system complexity while maintaining convenience and accuracy.
Data Source
Figure 1
Figure 2A~2B
Figure 3
AI summary
Systems and methods for invoking a third-party program as an additional participant of a chat session include monitoring events of a chat session of a messaging platform. At least one of the events of the chat session is determined to satisfy a triggering condition associated with a third-party program. In response to determining that the at least one of the events of the chat session satisfies the triggering condition associated with the third-party program, the third-party program is invoked as an additional participant of the chat session.