Presence Server Capability Persistence for Offline UE Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing presence servers face issues in determining whether a set of UEs support common capabilities, especially when some UEs go offline and unpublish their capability information, leading to compatibility problems and incorrect initiation of communication sessions.
Innovation Solution
A presence server system that maintains and provides capability information for UEs even after they have unpublished, allowing for determination of common capabilities among UEs, including those that are offline, to ensure communication sessions are initiated in a format supported by all participants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a presence server clears capability information when a UE goes offline (standard unpublish behavior), then the server maintains accurate presence data for online UEs, but it cannot determine common capabilities among UEs including offline ones, leading to compatibility problems
Solution Approach 1:
The patent extracts capability information from the dynamic presence data that gets cleared on unpublish, and stores it separately in a capability database. This separation allows capability data to persist independently of presence state, enabling the server to determine common capabilities among offline and online UEs while maintaining accurate presence information.
Solution Approach 2:
The server performs preliminary action by storing capability information in the capability database before the UE goes offline. This advance storage ensures that capability data remains available for common capability determination even after the UE unpublishes, preventing compatibility problems in future communication sessions.
2Quantity of substance
If a presence server removes capability information upon receiving an unpublish message, then it reduces data storage for offline UEs, but it causes incorrect initiation of communication sessions due to loss of capability data
Solution Approach 1:
The patent extracts capability information from the transient presence data and stores it in a persistent capability database. This extraction allows the server to maintain minimal stored data for offline UEs in the presence server while preserving capability information in the capability database, ensuring correct communication session initiation without excessive data storage.
Solution Approach 2:
The capability database acts as an intermediary between the presence server and the communication session initiation process. It stores capability information independently, allowing the presence server to clear its data while the capability database continues to provide accurate capability data for session initiation, preventing errors.
3Measurement precision
If a presence server polls UEs to obtain capability information, then it can get accurate capability data, but it increases network messages and wakes idle UEs, consuming additional energy
Solution Approach 1:
The patent applies preliminary action by having UEs send capability information to the presence server when they initially connect or register. The server then stores this information in the capability database for future use. This advance collection eliminates the need for subsequent polling, reducing network messages and preventing idle UEs from waking up, thus saving energy while maintaining accurate capability data.
Solution Approach 2:
The patent implements self-service by having UEs proactively provide their own capability information to the presence server during connection establishment. This self-provisioning eliminates the need for the server to poll UEs later, reducing network traffic and energy consumption while ensuring accurate capability information is captured.
4Measurement precision
If a presence server stores capability information for offline UEs, then it can determine common capabilities accurately, but it increases data storage requirements and message filtering complexity
Solution Approach 1:
The patent extracts capability information storage from the presence server's temporary data structure and places it in a dedicated capability database. This separation organizes data by function rather than by presence state, simplifying the message filtering logic. The server only needs to query the capability database for capability data without managing complex storage rules for offline versus online UEs, reducing filtering complexity while maintaining accurate common capability determination.
5Quantity of substance
If a presence server provides all capability information to watchers, then watchers get complete data, but it includes capabilities of offline UEs that may not be relevant, reducing efficiency
Solution Approach 1:
The patent applies local quality by making the capability information delivery selective and context-dependent. The server filters capability information based on the watcher's needs and the target UE's online status, providing only relevant capabilities. This targeted approach maintains completeness of necessary information while excluding irrelevant data from offline UEs, improving delivery efficiency without sacrificing essential capability data.
Data Source
AI summary
A presence server in a network can receive capability information about a UE in a publish message, and make that capability information available to other UEs on the network. When the UE later deregisters from the network, the UE can send an unpublish message. However, the presence server can at least partially disregard the unpublish message and continue to make the capability information about the UE available to other UEs. The presence server can also filter capability information of one or more target UEs provided to a watcher UE based on a registration status of a target UE, capabilities of the watcher UE, and/or whether a set of target UEs associated with a single user share certain capabilities.