Application Router Dynamic Registration via Event Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems lack a standard method to dynamically deploy multiple applications without modifying the application router when new applications are added, leading to slow adaptation and unnecessary recoding/upgrading.
Innovation Solution
A process for registering applications to monitor communication sessions is introduced, where applications can request registration based on specific events, and the application router detects these events to dynamically manage the registration and notification of applications within a SIP JSR 289 environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the application router implementation is specific to applications in the chain, then the router can process SIP messages correctly through chained applications, but the code must be modified or upgraded as new applications are added, resulting in slow adaptation and unnecessary recoding work
Solution Approach 1:
The patent segments the application router into two independent parts: a core router component that handles SIP message routing, and a separate application registration mechanism that manages application chains. This segmentation allows the core router to remain unchanged while new applications are registered and added to the chain through the registration mechanism, resolving the contradiction between adaptability and code complexity.
Solution Approach 2:
The patent implements a universal application registration interface that can register multiple types of applications without modifying the core router. The registration mechanism serves multiple functions: registering applications, managing application chains, and coordinating SIP message routing to multiple applications simultaneously. This universality enables the system to adapt to new applications without increasing router code complexity.
2Adaptability or versatility
If multiple applications are chained together to process SIP messages, then application composition is achieved, but there is no standard way to dynamically deploy applications without modifying the application router
Solution Approach 1:
The patent introduces an intermediary registration mechanism that sits between the applications and the core router. This intermediary handles application registration, validation, and chain management, allowing applications to be dynamically deployed without direct modifications to the router. The intermediary translates application registration requests into router-compatible formats, enabling dynamic deployment while maintaining ease of implementation.
Solution Approach 2:
The patent implements preliminary registration and validation of applications before they are added to the processing chain. Applications are registered in advance with the router, their capabilities are validated, and their position in the chain is predetermined. This preliminary action allows for smooth dynamic deployment without requiring router modifications when new applications are introduced.
3Productivity
If the application router is updated or modified to support new applications, then new applications can be integrated into the chain, but this results in unnecessary recoding work and slow adaptation
Solution Approach 1:
The patent implements a dynamic application registration system where applications can be registered, added to chains, and removed without static code modifications. The router dynamically adjusts its application chain based on registration information, allowing rapid integration of new applications. This dynamic approach eliminates the need for recoding and upgrading, significantly improving integration speed while reducing time loss.
Data Source
AI summary
A process for registering applications is disclosed. The applications typically work in a Session Initiation Protocol (SIP) JSR 289 environment. A request to register a application to monitor a communication session is received. A first instruction that identifies a first event in the communication session is received from the application. An event may be the sending of a specific type of packet, such as a SIP INVITE. The first event in the communication session is detected. In response to detecting the first event in the communication session, the application is registered to monitor the communication session according to the first instruction. A notification is also sent to the application to monitor the communication session according to the first instruction.