SaaS Trusted Relationship Management to Reduce Unsolicited Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users of online platforms frequently encounter spam and unsolicited communications, which consume computing resources and expose users to security risks, making it difficult for trusted entities to engage in communications.

Innovation Solution

A software-as-a-service (SaaS) platform establishes and manages trusted relationships between client accounts based on mutual authentication and authorization, enabling secure communication channels and reducing unwanted messages by requiring user authorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If open communication channels are provided on the platform, then communication versatility is improved, but spam and unsolicited communications increase

Engineering Contradiction:
Improvecommunication versatilityVSAvoidspam and unsolicited communications
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary authentication mechanism between communicating parties. Before establishing communication channels, the system mediates through mutual authentication processes that verify entity identities and establish trusted relationships, thereby filtering out spam while maintaining legitimate communication versatility

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If authentication and authorization mechanisms are implemented, then security is improved, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary authentication and authorization actions before communication occurs. By pre-establishing trusted relationships and verifying entity credentials in advance, the system ensures security requirements are met while avoiding the need for complex real-time security checks during communication

Inventive Principle:
Principle #10Preliminary action

3Reliability

If trusted relationship establishment processes are required, then communication reliability is improved, but communication speed decreases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidcommunication speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system performs trusted relationship establishment as a preliminary action before communication begins. Once the authentication and authorization are complete, subsequent communications can proceed rapidly without repeated verification, thus maintaining reliability while minimizing speed impact

Inventive Principle:
Principle #10Preliminary action

4Object-affected harmful factors

If user authorization is required for each communication, then security against spam is improved, but productivity decreases

Engineering Contradiction:
Improvespam protectionVSAvoidcommunication productivity
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The patent implements preliminary user authorization where users grant communication permissions in advance to trusted entities. Once authorized, multiple communications can occur without requiring repeated user approvals, thus maintaining spam protection while improving communication productivity

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12425411B1Establishing and managing trusted relationships between entities of a software-as-a-service (SaaS) platform
Publication Date: 2025.09.23 BLABBER INC
  • US12425411B1 patent drawing
  • US12425411B1 patent drawing
  • US12425411B1 patent drawing

AI summary

Methods and systems for establishing and managing trusted relationships between entities of a software-as-a-service (SaaS) platform are provided herein. A request associated with a first client account of a SaaS platform is received to establish a trusted relationship between a second and third client account of the platform. A client device associated with the third client account is identified based on information included in the request. A request is transmitted to the client device to establish the trusted relationship. A determination is made of whether response criteria associated with the request are satisfied. Responsive to a determination that the response criteria are satisfied, a data structure is updated to indicate the trusted relationship established between the second and third client account. A communication operation is performed to enable communication between client devices associated with the second and third client accounts, in accordance with the trusted relationship.