Serverless Peer-to-Peer Invitation API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current server-based communication systems and peer-to-peer networking technologies face challenges in facilitating seamless, secure, and efficient invitations for collaborative activities within serverless networks, particularly in determining endpoint capabilities and sending invitations without a central server.

Innovation Solution

The method involves initiating an invitation from a first user entity on a computing endpoint, selecting a second user entity, and determining if the activity is supported by the second endpoint's computing application, using a presence store to locate the endpoint, and sending invitations synchronously or asynchronously, with options for secure or unsecure transmission, leveraging a presence system and communication network to manage presence and capability information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a server-based system is used to manage invitations and presence information, then centralized control and coordination are improved, but system complexity and dependency on central infrastructure increase

Engineering Contradiction:
Improveinvitation delivery reliabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the presence information store from central server infrastructure and places it on individual peer endpoints. Each peer maintains its own presence information locally, eliminating the need for centralized presence management while maintaining invitation reliability through direct peer-to-peer communication.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments invitation management into independent peer-to-peer interactions rather than centralized server mediation. Each peer independently manages its own invitation sending and receiving, with presence information distributed across multiple endpoints rather than centralized in one location.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If peer-to-peer direct communication is used for invitations, then system simplicity and reduced infrastructure dependency are improved, but capability determination accuracy and security verification worsen

Engineering Contradiction:
Improvesystem architecture complexityVSAvoidendpoint capability determination accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent implements preliminary capability advertisement where peers publish their supported activities and capabilities in advance through the presence information store. This allows capability determination to occur before invitation sending, ensuring accurate matching without requiring complex verification during the invitation process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses presence information as feedback mechanism where peers continuously publish and update their capability status. This feedback loop enables accurate capability determination by allowing inviting peers to query current capability information before sending invitations.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If asynchronous invitation sending is used, then network flexibility and continued operation despite connectivity issues are improved, but invitation status tracking and confirmation time increase

Engineering Contradiction:
Improvenetwork connectivity adaptabilityVSAvoidinvitation confirmation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic invitation sending that adapts to network conditions. The system can switch between synchronous and asynchronous modes based on connectivity status, and peers continuously update their presence information to reflect availability changes, enabling dynamic adjustment of invitation delivery timing.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system maintains continuous presence information updates and invitation status tracking even during network disruptions. Peers continuously publish their status, allowing invitation confirmation to proceed as soon as connectivity is restored, maintaining continuous useful action rather than pausing during interruptions.

Inventive Principle:
Principle #20Continuity of useful action

4Measurement precision

If comprehensive presence information storage is implemented, then capability matching accuracy is improved, but information security risks and data exposure increase

Engineering Contradiction:
Improvecapability matching accuracyVSAvoidinformation security risks
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

The patent implements local presence information storage where each peer maintains its own capability and status data locally rather than centralizing all information. This distributed approach improves capability matching accuracy through localized queries while reducing security risks by limiting data exposure to only what is locally stored and shared on a need-to-know basis.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8036140B2Application programming interface for inviting participants in a serverless peer to peer network
Publication Date: 2011.10.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8036140B2 patent drawing
  • US8036140B2 patent drawing
  • US8036140B2 patent drawing

AI summary

Methods and computer readable mediums are described that facilitate inviting user entities on a network. The method may include initiating a first application for sending an invitation by a first user entity on a first endpoint, selecting a second user entity to receive the invitation, and selecting an activity. The method may also include sending from the first endpoint to the second user entity the invitation to participate in the activity if the first endpoint determines the activity is supported by a computing application on the first endpoint.