Telephony Configuration via Time-Limited Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for remotely managing telephony device configuration are insecure, particularly as they rely on identifying MAC addresses, require prior secret information, or are vendor-specific, making them vulnerable to attacks and costly to implement.

Innovation Solution

A method and apparatus for remotely managing telephony device configuration using a provisioning server that authenticates service credentials, activates a temporary configuration time period, and transmits configuration data only during this period, minimizing requirements on the device and using a self-provisioning service that does not need prior secret information for decryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If configuration files are made publicly accessible via MAC address, then device configuration is simple and automatic, but security is compromised as attackers can easily retrieve credentials

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidsecurity vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system dynamically changes the accessibility of configuration files from permanent/public to temporary/limited. Configuration files are only accessible during a specific time window (T1 to T2) after authentication, then become inaccessible. This temporal dynamicity resolves the contradiction by maintaining ease of configuration while eliminating permanent security vulnerabilities.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements periodic action by creating a time-limited access window for configuration files. The configuration is made available only during a specific period (configuration time period) and automatically becomes inaccessible afterward. This periodic availability allows devices to retrieve configuration automatically while limiting the window for attacks.

Inventive Principle:
Principle #19Periodic action

2Object-affected harmful factors

If encryption with master key is used, then security is improved, but vendor-specific implementation complexity increases and requires custom development work

Engineering Contradiction:
Improvesecurity protectionVSAvoidvendor-specific integration work
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The system extracts the security mechanism from the configuration file itself and places it in the provisioning server. Instead of encrypting files with device-specific master keys requiring custom integration, the server uses authentication credentials to control access. This extraction eliminates vendor-specific complexity while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The authentication mechanism acts as an intermediary between the attacker and the configuration file. Instead of relying on complex encryption keys stored in devices, the system uses a simpler authentication credential system that mediates access to configuration files, reducing implementation complexity while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Object-affected harmful factors

If pre-configured secrets are used, then security is enhanced, but deployment cost and complexity increase due to required staging steps

Engineering Contradiction:
Improvesecurity enhancementVSAvoiddeployment cost
Core Design Contradiction:
Object-affected harmful factorsVSEase of manufacture

Solution Approach 1:

The system performs preliminary authentication action before allowing configuration access. Instead of requiring physical staging and manual secret configuration during deployment, the system automatically authenticates devices based on their credentials and grants access to configuration files without requiring manual intervention or specialized deployment procedures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service deployment where devices automatically authenticate and retrieve their configuration files without requiring manual staging or configuration by deployment personnel. This eliminates the need for costly and complex manual deployment processes while maintaining security through automated authentication.

Inventive Principle:
Principle #25Self-service

4Object-affected harmful factors

If client-side certificates are used, then security verification is improved, but hardware requirements and manufacturing complexity increase

Engineering Contradiction:
Improvesecurity verificationVSAvoidhardware support requirements
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

Instead of using complex hardware-based certificates that require specialized storage and processing capabilities, the system uses simpler software-based authentication credentials. These credentials can be stored in standard memory and processed by conventional processors, eliminating the need for special hardware support while maintaining security verification functionality.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9231932B2Managing remote telephony device configuration
Publication Date: 2016.01.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9231932B2 patent drawing
  • US9231932B2 patent drawing

AI summary

The remote configuration of a telephony device is managed by transmitting configuration data to the device. The data is transmitted via a data communication network. One of more service credentials are received. The credentials are authenticated. A configuration time period is activated in response to authentication of the credentials. A request for configuration data is received via the network, which includes identification data indicative that the request is from a telephony device associated with the credentials. It is determined how to proceed with processing of the request dependent on whether the request is received during the time period. If so, configuration data is transmitted via the network in response to the request. If the request is received after the time period, transmission of configuration data via the network in response to the request is inhibited.