PoC Server Presence Attribute Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems, particularly with Push-to-Talk over Cellular (PoC) services, conflicting presence status information can be reported by both the PoC client and server to the presence server, leading to confusion and unnecessary network traffic, as both entities may report the same information independently.
Innovation Solution
The PoC server informs the PoC client which presence attributes it will report to the presence server, and the client then avoids reporting those attributes, ensuring that only the PoC server reports the specified presence information, thereby preventing conflicts and redundant reporting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If both the PoC client and server independently report presence status to the presence server, then comprehensive presence information can be obtained, but conflicting information and redundant network traffic occur
Solution Approach 1:
The patent introduces a coordination mechanism where the PoC server acts as an intermediary that manages presence reporting between the PoC client and presence server. The server receives capability information from the client, determines which entity should report specific presence attributes, and coordinates the reporting process to avoid conflicts while maintaining comprehensive presence information.
Solution Approach 2:
The patent applies preliminary action by having the PoC client send capability information to the PoC server before actual presence reporting occurs. This advance coordination allows the system to pre-determine the reporting responsibilities for different presence attributes, preventing conflicts before they happen and reducing redundant network traffic.
2Speed
If the PoC client reports presence status independently, then real-time presence information can be provided, but conflicts with server-reported information occur during status transitions
Solution Approach 1:
The capability information exchange between PoC client and server is performed in advance, establishing a clear division of reporting responsibilities before presence status changes occur. This preliminary coordination ensures that real-time reporting by the client does not conflict with server reporting, maintaining both speed and consistency.
Solution Approach 2:
The patent segments the presence reporting function by attribute type, with different entities (client or server) responsible for reporting different presence attributes based on their capabilities and the determined coordination scheme. This segmentation allows real-time reporting for certain attributes while maintaining consistency across all presence information.
3Reliability
If both entities report all presence attributes, then complete presence coverage is achieved, but unnecessary redundant network traffic is generated
Solution Approach 1:
The PoC server acts as a mediator that coordinates reporting responsibilities between the client and presence server. By managing which entity reports which presence attributes, the system achieves complete presence coverage while eliminating redundant reporting, thus improving network traffic efficiency without sacrificing information completeness.
Solution Approach 2:
Instead of both entities reporting all presence attributes (excessive action), the patent implements partial reporting where each entity reports only the specific attributes for which it is responsible. This approach maintains complete presence information coverage while significantly reducing redundant network traffic and energy consumption.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A system for presence publication, such as in a push-to-talk over cellular service, provides means for avoiding the reporting of conflicting presence information to a presence server. Two different entities may be capable of reporting status information for the same entity, the status information corresponding to a plurality of status attributes. The first entity would typically inform the second entity which ones of the plurality of status attributes for which the first entity will be reporting status information to the presence server. For the ones of the plurality of status attributes for which the first entity will be reporting status information, the second entity will typically not report status information. For the ones of the plurality of status attributes for which the first entity will not be reporting status information, the second entity will typically report status information if capable.