Messaging Format Conversion for Cellular Network Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Wireless networks face complexity and inefficiencies when handling messages between user equipment (UEs) operating on different standards, such as 3GPP and 3GPP2, due to differences in messaging formats and protocols, leading to issues with acknowledgment messages and delivery receipts.

Innovation Solution

An application server device associated with the recipient UE converts messaging formats and communicates with other networks via SIP over IP, standardizing the architecture and interfaces, and handling billing information independently of the standards used by sending and receiving UEs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If wireless networks handle messages between UEs operating on different standards (3GPP and 3GPP2) using different messaging formats and protocols, then communication compatibility between diverse networks is maintained, but network complexity and implementation difficulty increase

Engineering Contradiction:

Improvecommunication compatibilityVSAvoidnetwork complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an application server as an intermediary component that mediates message transmission between UEs on different standards. The application server receives messages in the sender's native format, processes them, and delivers them to the recipient's device in the appropriate format, thereby maintaining compatibility without requiring complex multi-protocol support throughout the network infrastructure

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The application server performs multiple functions including message routing, format conversion, acknowledgment handling, and delivery receipt management. This multi-functional approach consolidates what would otherwise require separate specialized components for each function, reducing overall system complexity while maintaining support for multiple standards

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If wireless networks implement separate routing and handling procedures for different messaging formats, then message delivery accuracy is maintained, but processing time and operational efficiency decrease

Engineering Contradiction:

Improvemessage delivery accuracyVSAvoidprocessing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The application server performs preliminary processing of messages including format validation, routing determination, and conversion preparation before actual message delivery. By preparing messages in advance and establishing routing paths beforehand, the system ensures accurate delivery while reducing real-time processing delays

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system dynamically adapts message handling procedures based on the specific standards and formats involved. The application server automatically adjusts its processing logic according to the sender's and recipient's device capabilities and network requirements, optimizing the balance between accuracy and efficiency for each specific communication scenario

Inventive Principle:

Principle #15Dynamics

3Reliability

If wireless networks use standard-specific routing devices and formats, then protocol compliance is maintained, but interface complexity and implementation difficulty increase

Engineering Contradiction:

Improveprotocol complianceVSAvoidimplementation ease

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The application server acts as a standardized intermediary interface between different network standards. It maintains protocol compliance by properly formatting messages according to recipient requirements while presenting a uniform interface to sending devices, thereby ensuring compliance without requiring each network element to implement multiple protocol stacks

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of requiring sending devices to adapt to recipient formats, the system inverts the adaptation process by having the application server convert messages from sender format to recipient format. This inversion simplifies the sending end while maintaining compliance at the receiving end through centralized conversion logic

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS10244366B2Messaging format conversion for a cellular network

Publication Date: 2019.03.26 VERIZON PATENT & LICENSING INC

AI summary

A network device may receive, from a sending device, a message in a first messaging format en route to user equipment. The first messaging format may correspond to one of a 3GPP cellular network standard or a 3GPP2 cellular network standard. The network device may determine whether the user equipment is associated with the first messaging format or with a second messaging format. The second messaging format may correspond to one of the 3GPP cellular network standard or the 3GPP2 cellular network standard. The first messaging format and the second messaging format may be associated with different cellular network standards. The device may selectively provide the message in the first messaging format or the second messaging format based on whether the user equipment is associated with the first messaging format or the second messaging format. The device may transmit an acknowledgment message based on the first messaging format.