Presence Management via Category-Based Renewal
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In presence systems, managing multiple presences owned by an entity is cumbersome, especially when entities have a plurality of presences, as existing systems fail to efficiently update and manage these presences without disclosing the entire structure, leading to privacy concerns and increased burden on both the presentity and the renewer.
Innovation Solution
A presence system that utilizes a user identifier to manage presences, including a reception unit for renewal requests, a category acquisition unit, an association table for presence identifiers, and a presence specification unit to set presences based on category information, allowing for efficient renewal and subscription management without revealing the entire presence structure, thus protecting privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a renewer wants to update presences of a presentity, then the presence can be renewed, but the renewer must investigate the structure of presences and disclose the entire presence structure, which increases complexity and reveals privacy information
Solution Approach 1:
The patent extracts only the necessary presence information (presence ID and content) that needs to be renewed, rather than requiring the renewer to access or disclose the entire presence structure. The presence server selectively retrieves and updates only the specific presence data needed for the renewal operation, minimizing information exposure while enabling the renewal function.
2Adaptability or versatility
If a presentity has multiple presences, then more functionality is provided, but managing and updating each presence individually becomes troublesome and time-consuming
Solution Approach 1:
The patent implements a universal presence renewal mechanism where a single renewal operation can affect multiple presences. The presence server maintains a mapping between presence IDs and their corresponding data, allowing the system to efficiently locate and update the correct presence without requiring the renewer to manually manage each presence individually. This multi-functional approach handles both single and multiple presence renewals through a unified process.
3Measurement precision
If the renewer designates specific presence IDs for renewal, then precision is improved, but the renewer must know the presence structure in advance, which increases complexity
Solution Approach 1:
The presence server acts as an intermediary between the renewer and the presence data. Instead of requiring the renewer to directly access or know the presence structure, the server mediates the communication by receiving renewal requests, resolving presence IDs, and performing the actual updates. This intermediary approach maintains precise presence identification while shielding the renewer from complexity in the presence structure.
4Reliability
If the entire presence structure is disclosed to enable renewal, then the renewer can accurately update presences, but privacy protection is compromised
Solution Approach 1:
The patent segments the presence information into discrete, manageable units (presence IDs and their corresponding content). Instead of disclosing the entire presence structure at once, the system retrieves and processes only the specific presence segments needed for the renewal operation. This segmentation allows reliable presence updates while minimizing the exposure of private information about the presentity's overall structure.
Data Source
AI summary
A presence server stores a presence that is identified by presence IDs “a1” and “a2”, as the presence of a user “A”. User “A” can pass a card that they hold through a card reader at a timing of their choosing. The card reader reads in data from the card and transmits a renewal request to the presence server. The renewal request includes a renewer ID, an object ID, category information and the presence. When the presence server receives the renewal request, it specifies the presence ID “a1” of user “A” to be the presence that is to be renewed, based on the category information, and moreover, rewrites the presence of the presence ID “a1” to a presence “meeting room A” that is included in the renewal request. Thus, the card reader can renew the presence designated by the “category information”. As for the presence that is renewed, it is notified to a watcher of the presence “a1” from the presence server.