Selective Service Invocation Function SIP Network
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SIP protocol mechanisms for invoking service logics are inefficient, as they only allow service triggering on the initial request initiating a session or transaction, leading to unnecessary overload and extended call set-up delays, particularly for conversational applications, and do not account for the state of the requested terminal or allow application servers to exit calls dynamically.
Innovation Solution
A method and system that selectively invoke application servers based on conditional triggering criteria, including response receipt, timeout, and terminal state, allowing service logics to be triggered only when necessary and enabling application servers to exit calls at any time, by managing two distinct dialogs and storing messages to restore them for service invocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application servers are invoked on every initial SIP request, then service coverage is maximized, but call set-up delay increases and server load increases
Solution Approach 1:
The patent applies preliminary action by pre-establishing dialogs and storing messages between the selective service invocation function and user agents before service triggering. When a triggering event occurs, the pre-stored messages are restored and forwarded to the application server, eliminating the need to reconstruct the dialog context in real-time and reducing call set-up delay.
Solution Approach 2:
The selective service invocation function acts as an intermediary between user agents and application servers. It manages dialogs, stores messages, and selectively invokes servers based on triggering criteria. This intermediary role allows the system to buffer and manage service invocations efficiently, reducing both delay and unnecessary server loads.
2Reliability
If application servers are invoked on every initial SIP request, then no service is missed, but server load increases unnecessarily
Solution Approach 1:
By pre-establishing dialogs and storing messages before service triggering, the system prepares all necessary context in advance. This allows the application server to be invoked only when actual triggering criteria are met, rather than on every initial request, thereby reducing unnecessary server load while ensuring service coverage when needed.
Solution Approach 2:
The patent changes the invocation parameter from 'every initial request' to 'based on triggering criteria'. The selective service invocation function monitors dialog states and message content, and only restores and forwards messages to application servers when specific triggering events occur, optimizing server resource utilization.
3Productivity
If service triggering is limited to initial requests only, then server load is reduced, but services requiring response-based triggering cannot be implemented
Solution Approach 1:
The selective service invocation function serves as an intermediary that monitors all SIP messages within established dialogs, not just initial requests. It can identify triggering events in responses or subsequent requests and restore pre-stored messages accordingly, enabling versatile service triggering while maintaining server load reduction through selective invocation.
Solution Approach 2:
The system performs preliminary actions by establishing dialogs and storing messages in advance for potential service triggering. This preparation enables the system to respond to triggering events occurring at any point in the dialog (responses, subsequent requests) without requiring actual service invocation until the triggering criteria are met, thus reducing server load while increasing flexibility.
4Reliability
If application servers remain in calls from start to end, then service availability is ensured, but call set-up delay and server load increase unnecessarily
Solution Approach 1:
The system performs preliminary actions by establishing dialogs and storing messages before service triggering occurs. The application server is invoked only when triggering criteria are met, and can exit the call after service execution. This ensures service availability when needed while avoiding unnecessary server involvement in calls where services are not triggered, reducing call set-up delay.
Solution Approach 2:
The patent implements dynamic service invocation where application servers are added to and removed from calls based on triggering events. The selective service invocation function manages the dynamic lifecycle of server participation, establishing dialogs in advance and activating servers only when required, thereby ensuring availability on-demand while minimizing server involvement and associated delays.
Data Source
Figure 1a~4d
Figure 1c~1e
Figure 2a~2c
AI summary
The invention concerns a method for invoking at least one service application server (AS) during a communication between an originating user agent (O_UA) and end user agent (T_UA). It consists at least in opening (A) two separate dialogues, between a service selecting function (SIF) and, respectively, the originating agent (O_UA) and the end agent (T_UA). The function (SIF) is substituted to the user agent (T_UA) in its dialogue with the user agent (O_UA) and to the user agent (O_UA) in its dialogue with the user agent (T_UA). The messages from the user agents during the two opened dialogues are stored (B) and at least one service conditional triggering criterion on the two dialogues is verified (C). If the triggering criterion is verified, at least part of the messages is restored (D) to the server so as to trigger the invocation thereof. The invention is useful for invoking application servers in a SIP network.