Business Server Duplex Messaging Identifier Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business messaging systems face cost inefficiencies and challenges in routing reply messages due to the requirement of unique public identifiers for each user, especially in systems with a large number of users, leading to prohibitively expensive rentals of phone numbers for SMS services.

Innovation Solution

A system and method that uses a business server to manage public identifiers, allowing multiple business users to share a limited number of public identifiers, and employs an API to interact with SMS systems, enabling duplex message exchange by associating business users with mobile devices and switching to temporary identifiers when necessary, thereby reducing the need for individual phone numbers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a unique public identifier (phone number) is rented for each business user to enable duplex message exchange, then message routing reliability is improved, but system cost increases prohibitively

Engineering Contradiction:
Improvemessage routing reliabilityVSAvoidnumber of public identifiers required
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple business users under a single public identifier (the business server's identifier). Instead of each user having their own unique identifier, multiple users share the business server's identifier, dramatically reducing the number of public identifiers needed while maintaining routing capability through additional metadata fields.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the identifier functionality into two parts: the public identifier (shared by the business server) and internal user identifiers (unique to each user). This segmentation allows the public identifier to be reused across multiple users while internal identifiers maintain uniqueness for accurate routing.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If a limited number of public identifiers is rented to reduce costs, then system cost is reduced, but the ability to route reply messages to specific users is lost

Engineering Contradiction:
Improvenumber of public identifiersVSAvoiduser identification information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent introduces an intermediary mechanism (the business server) that sits between the SMS system and individual users. The server uses its single public identifier to receive messages and then routes them to appropriate users using internal identifiers, acting as a mediator that preserves user identification capability without requiring multiple public identifiers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds another dimension to the identification system by introducing internal user identifiers as a secondary layer. Instead of relying solely on the public identifier dimension, the system now uses a two-dimensional identification approach: public identifier for receiving messages and internal identifier for routing, preventing information loss.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Quantity of substance

If multiple business users share a single public identifier, then cost efficiency is improved, but message routing complexity increases

Engineering Contradiction:
Improvenumber of public identifiersVSAvoidmessage routing complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where the business server automatically manages the routing process using pre-configured mappings between internal user identifiers and the shared public identifier. The system handles the routing complexity internally without requiring external intervention, making the shared identifier approach viable despite the increased routing logic.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9712984B1System and method for sending messages
Publication Date: 2017.07.18 HIGHER GROUND LLC
  • US9712984B1 patent drawing
  • US9712984B1 patent drawing
  • US9712984B1 patent drawing

AI summary

A system for exchanging messages between a business user and a mobile device, and methods for making and using the same. The system may include a business server, an application programming interface (“API”) and/or an SMS database. The business server may be configured to exchange messages with the business user and to obtain a public identifier for the business user to enable duplex message exchange between the business user and the mobile device by either retrieving the public identifier or associating the business user with the mobile device and a public identifier. The business user may be unambiguously determined according to the public identifier or a combination of the mobile device and the public identifier, which may enable the mobile device to direct a reply message to the business user that may be the sender of a direct message.