Local Presence Authorization Rules for RCS Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Rich Communications Services (RCS) platforms face network traffic inefficiencies and service disruptions due to the reliance on external XML Document Management Servers (XDMS) for presence authorization rules, leading to potential nationwide outages during XDMS service interruptions.
Innovation Solution
Implementing a presence server that stores and uses local presence authorization rules as a default policy, allowing for global application and reducing network traffic, while also providing a fallback mechanism to ensure service continuity during XDMS failures by using locally stored rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the RCS platform relies on external XDMS for presence authorization rules, then centralized management and control are improved, but network traffic efficiency deteriorates and service reliability worsens due to potential nationwide outages
Solution Approach 1:
The patent segments the centralized authorization rules into two parts: (1) a global default policy stored locally in the presence server, and (2) user-specific custom rules stored in the XDMS. This segmentation allows the system to maintain centralized management for custom rules while having a local fallback mechanism that ensures service continuity when XDMS is unavailable, thus resolving the contradiction between centralized management capability and service continuity.
Solution Approach 2:
The patent implements preliminary action by pre-storing global default presence authorization rules locally in the presence server before any XDMS failure occurs. This preliminary local storage ensures that when the XDMS becomes unavailable, the presence server can immediately continue processing authorization requests using the pre-loaded default rules, maintaining service continuity without requiring real-time communication with the XDMS.
2Adaptability or versatility
If the RCS platform uses external XDMS for presence authorization rules, then centralized policy management is improved, but network traffic increases due to continuous external communication
Solution Approach 1:
The patent segments authorization rule management into global default rules handled locally and user-specific custom rules handled by XDMS. This reduces network traffic by eliminating redundant communication for global policy enforcement, while maintaining centralized management capability for user-specific customizations through selective XDMS access only when custom rules are needed.
Solution Approach 2:
The patent extracts the global default presence authorization rules from the external XDMS and places them locally in the presence server. This extraction eliminates the need for continuous external communication for global policy enforcement, significantly reducing network traffic while preserving centralized management capability for user-specific custom rules that remain in the XDMS.
3Device complexity
If the RCS platform stores presence authorization rules externally in XDMS, then system complexity is reduced, but service reliability deteriorates due to single point of failure
Solution Approach 1:
The patent segments the authorization rule storage into two locations: global default rules stored locally in the presence server and user-specific custom rules stored in the external XDMS. This segmentation creates a fallback mechanism where the local storage acts as a backup, eliminating the single point of failure and improving service reliability while maintaining relatively simple system architecture.
Solution Approach 2:
The patent creates a local copy of the global default presence authorization rules in the presence server, duplicating the essential authorization policy from the external XDMS. This copying provides redundancy that protects against XDMS failures, improving service reliability while keeping the system architecture simple by using standard data replication techniques.
Data Source
AI summary
A request from a watcher client to obtain presence information of a presentity client may be processed at a presence server using a system configuration of the presence server that stores local presence authorization rules (“pres-rules”). By storing pres-rules locally at the presence server, these pres-rules may be used by the presence server in lieu of, or in combination with, other pres-rules that may be maintained by a separate pres-rules storage server, such as an eXtensible Markup Language (XML) Document Management Server (XDMS). The system configuration may specify configurable parameters that control the behavior of the presence server in engaging the XDMS when processing requests from watcher clients, as well as the behavior of the presence server in merging pres-rules retrieved from the XDMS with the local pres-rules maintained by the presence server.