Proxy Presence Server Caching for RCS Load Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing presence servers face high workload and capacity exhaustion due to frequent queries from poorly configured Rich Communication Service (RCS) clients, leading to inefficiencies in managing presence information across different carrier networks.

Innovation Solution

A proxy presence server is deployed to act as an intermediary, caching presence information with a configurable Time To Live (TTL) and serving subsequent requests directly from the cache, thereby reducing the load on internal presence servers and preventing inter-carrier communication overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If presence servers directly handle all queries from RCS clients, then presence information can be provided accurately, but the servers experience high workload and capacity exhaustion

Engineering Contradiction:
Improvepresence information accuracyVSAvoidserver workload capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces a proxy presence server as an intermediary component between RCS clients and the internal presence server. This proxy server receives presence information queries from RCS clients, caches the information locally, and serves subsequent queries from its cache without forwarding them to the internal presence server. This mediator architecture maintains accurate presence information delivery while protecting the internal server from overload by poorly configured clients that continuously query presence status.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If presence information is cached with a configurable TTL, then subsequent requests can be served from cache reducing server load, but the presence information may become stale

Engineering Contradiction:
Improvequery response efficiencyVSAvoidpresence information freshness
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The proxy presence server performs preliminary actions by caching presence information received from the internal presence server with a configurable Time-To-Live (TTL) value. When queries arrive, the server checks its cache first and serves information from the cache if it is still valid (within TTL), avoiding real-time queries to the internal server. This preliminary caching action improves query response efficiency while the configurable TTL mechanism ensures information freshness by invalidating cache entries after a specified duration.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the proxy presence server caches presence information, then inter-carrier communication overload is prevented, but additional system complexity is introduced

Engineering Contradiction:
Improvenetwork stabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the presence server functionality into two distinct components: the internal presence server that maintains authoritative presence information and the proxy presence server that handles client queries with local caching. This segmentation allows the system to prevent inter-carrier communication overload by distributing the query handling responsibility, while the added complexity is confined to the proxy layer without affecting the core internal server architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10992608B2Proxy presence server
Publication Date: 2021.04.27 VERIZON PATENT & LICENSING INC
  • US10992608B2 patent drawing
  • US10992608B2 patent drawing
  • US10992608B2 patent drawing

AI summary

A method, device, and computer-readable medium provide for receiving, from an first presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network; sending the presence status request to a second presence server in the home carrier network; receiving the presence status of the user device and storing the presence status of the user device in an associated database; sending presence status to the first presence server; receiving at least one subsequent request for the presence status of the user device; and sending the presence status.