Credential Updating Server for Automatic Service Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for application servers communicating with network provider servers face challenges in securely updating credentials without user interaction, leading to potential service interruptions due to outdated credentials.

Innovation Solution

A system and method that allow credentials to be updated automatically by a credential updating server, without user interaction, using a token generation server and credential update server, which generates and provides updated credentials to the application server, enabling secure and timely updates without disrupting services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If credentials are updated manually with user interaction, then security is improved, but service interruption and user error risk increase

Engineering Contradiction:
ImprovesecurityVSAvoidservice continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service credential updating where the credential updating server automatically generates, transmits, and implements new credentials without requiring user interaction. The application server autonomously receives and applies the updated credentials, eliminating manual intervention while maintaining security through automated authentication protocols.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The credential updating server generates and transmits updated credentials to the application server before the current credentials expire or before potential security issues arise. This preliminary action ensures that credentials are refreshed proactively, preventing service interruptions and maintaining continuous secure access.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If credentials are updated automatically without user interaction, then service continuity is improved, but security verification complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidsecurity verification complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The credential updating server acts as an intermediary between the network provider server and the application server, managing the complex security verification processes. It generates updated credentials, transmits them securely, and coordinates with both parties to ensure proper authentication and authorization, thereby simplifying the overall system architecture while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If credentials are updated frequently for security purposes, then security is improved, but system overhead and update management complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidupdate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs credential updates in advance before current credentials become obsolete or potentially compromised. The credential updating server proactively generates and distributes new credentials, allowing the application server to switch seamlessly without service interruption, thereby managing update frequency efficiently without excessive overhead.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9154482B2Secure access credential updating
Publication Date: 2015.10.06 VERIZON PATENT & LICENSING INC
  • US9154482B2 patent drawing
  • US9154482B2 patent drawing
  • US9154482B2 patent drawing

AI summary

One or more first servers may receive a token, generated by a second server based on the second server validating an authorization parameter received by a third server; receive, from the second server, a token parameter, associated with the token and being associated with the authorization parameter and identifying a credential associated with the third server; receive, from the third server, a request to update the credential, the request including the token; validate the token; form an updated credential based on the token parameter and based on validating the token; and provide the updated credential to the third server. The credential may be replaced, by the third server, with the updated credential without interaction with a user of the third server.