Presence Server Batching and Group Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current presence systems face computational and network inefficiencies due to the need for frequent XML parsing and high network traffic caused by individual updates and subscriptions, especially as the number of users and presence updates increase, leading to overwhelming burdens on presence servers.
Innovation Solution
The presence system addresses these inefficiencies by accepting batches of publication updates and subscription requests, introducing new expiration types that eliminate the need for frequent refreshes, and using membership groups instead of individual user lists for access control, thereby reducing computational and network loads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If individual presence updates are processed one at a time with XML parsing, then presence information can be updated accurately, but the computational load on the presence server becomes overwhelming as the number of users increases
Solution Approach 1:
The patent combines multiple individual presence updates into a single batch update operation. Instead of processing each presence change separately with full XML parsing, the system accumulates multiple updates and processes them together in one operation, significantly reducing the total computational overhead on the presence server while maintaining accuracy of presence information.
Solution Approach 2:
The system performs preliminary actions by pre-compiling and validating presence update data before submitting it to the presence server. Updates are prepared in advance in a batch format with necessary validations performed beforehand, reducing the processing burden on the server during actual update operations.
2Adaptability or versatility
If individual user lists are used for access control to presence collections, then fine-grained authorization can be implemented, but the network traffic and processing overhead increase significantly
Solution Approach 1:
The patent merges individual user access lists into group-based membership definitions. Instead of managing separate authorization entries for each user, the system organizes users into membership groups and assigns collections to these groups. This consolidation dramatically reduces network traffic and processing overhead while preserving fine-grained authorization capabilities through group-based access control.
3Reliability
If frequent presence information refreshes are implemented to ensure data currency, then presence information remains up-to-date, but network traffic and server load increase excessively
Solution Approach 1:
The patent implements periodic batch updates instead of continuous individual refreshes. Presence information is updated at scheduled intervals in consolidated batches rather than being continuously refreshed individually. This periodic approach maintains presence data currency while dramatically reducing network traffic and server load compared to frequent individual updates.
Solution Approach 2:
The batch update mechanism serves multiple functions simultaneously: it updates presence information, validates data integrity, manages authorization checks, and notifies subscribers all in a single operation. This multi-functionality reduces the need for separate refresh operations while maintaining information currency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and system for increasing the computational and network efficiency of presence servers having collections of publications is provided. The presence system uses several techniques that enable a presence server to provide rich presence information without requiring expensive processing. First, the presence system accepts batches of publication updates in a single presence update request. Similarly, the presence system accepts batches of subscription requests. Next, the presence system supports new expiration types for publication update requests that eliminate the need for a publishing user to continually refresh presence information that has not changed. Finally, the presence system accepts access lists that contain membership groups rather than an individual list of users that are to have access to a particular presence collection.