OTT Voice for IoT Devices via SIP Client and Gateway

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

IoT devices with voice services often incur unnecessary costs and resource wastage due to their 'always-on' registration with IMS networks, even for low usage and call destination-restricted devices, which is inefficient in terms of network resource allocation.

Innovation Solution

Implementing an over-the-top (OTT) voice service for IoT devices that uses a Session Initiation Protocol (SIP) client without an IMS client, allowing registration only upon user-initiated calls and limited post-call registration duration, utilizing a voice gateway outside the IMS network for call routing based on enterprise identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IoT devices use IMS client for voice service, then advanced calling features and network integration are improved, but network resource consumption and device complexity increase

Engineering Contradiction:

Improvevoice service capabilityVSAvoidnetwork resource consumption

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts the voice service functionality from the IMS network infrastructure and implements it locally on the IoT device using a SIP client. This removes the need for continuous IMS network registration and resource allocation, allowing the device to provide voice services independently while consuming minimal network resources.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The IoT device is equipped with a SIP client that enables it to autonomously establish and manage voice calls without requiring IMS network services. The device self-manages call routing, registration, and communication protocols, eliminating dependency on network-based voice service provisioning.

Inventive Principle:

Principle #25Self-service

2Reliability

If IoT devices register always-on with IMS network, then voice service availability is improved, but network resource allocation efficiency deteriorates

Engineering Contradiction:

Improvevoice service availabilityVSAvoidnetwork resource allocation efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Instead of continuous IMS network registration, the device performs periodic SIP registration only when voice services are actively needed. The SIP client registers with the SIP server on-demand, maintains registration during active use, and deregisters when idle, creating an efficient periodic registration pattern that balances availability with resource efficiency.

Inventive Principle:

Principle #19Periodic action

3Device complexity

If IoT device includes SIP client without IMS client, then device complexity and network resource usage are reduced, but advanced calling features are limited

Engineering Contradiction:

Improveclient implementationVSAvoidcalling feature capability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent employs a lightweight SIP client implementation that provides essential voice calling functionality without the overhead of a full IMS client. This simplified client uses standard SIP protocols to achieve core voice service needs, accepting limited advanced features in exchange for significantly reduced device complexity and resource consumption.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS10567446B2Method and system for over-the-top voice for internet of things devices

Publication Date: 2020.02.18 VERIZON PATENT & LICENSING INC

AI summary

A method, a device, and a non-transitory storage medium are provided to receive from an end device, a session establishment message pertaining to a voice service that restricts the end device to place a voice call to and receive a voice call from a designated call center; replace a uniform resource identifier of the designated call center included in the session establishment message, with an enterprise identifier included in subscription data pertaining to the end device; select, based on the enterprise identifier, another network device to transmit the session establishment message; and transmit the session establishment message to another device based on the selection.