Endpoint Extension Mobility Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current extension mobility systems lack the ability to efficiently manage user preferences and unauthorized access, particularly in shared mode scenarios, where multiple users may inadvertently or intentionally share phone extensions, leading to potential security and service level issues.

Innovation Solution

The method allows users to log on to an endpoint in either private or shared mode, configuring the endpoint to support either a single user's extension or multiple users' extensions, respectively, while maintaining user preferences and security settings, and enabling features like concurrent access and shared usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an endpoint supports only a single user's extension (private mode), then security and user preference management are simplified, but the endpoint cannot be shared by multiple users

Engineering Contradiction:
Improveendpoint sharing capabilityVSAvoidconfiguration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The endpoint dynamically changes its configuration mode between private and shared based on user login events. When a user logs in, the system determines whether to activate private mode (single user) or shared mode (multiple users), and the endpoint adapts its behavior accordingly. This dynamic switching resolves the contradiction by allowing the endpoint to be simple when privately used and versatile when shared, without requiring permanent complex infrastructure.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the operational parameters of the endpoint based on login mode. In private mode, the endpoint is configured with single-user parameters (one extension, one user profile). In shared mode, parameters change to support multiple extensions and multiple user profiles concurrently. This parameter transformation allows the same physical endpoint to serve different functional requirements without hardware changes.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If an endpoint is configured for shared mode supporting multiple users, then user flexibility and sharing capability are improved, but managing user preferences and preventing unauthorized access becomes more difficult

Engineering Contradiction:
Improvemulti-user supportVSAvoidunauthorized access prevention
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The shared endpoint configuration is segmented into separate user profiles, each with their own extension, preferences, and access rights. Instead of a monolithic shared configuration, the system divides the endpoint into isolated user spaces (e.g., User A profile, User B profile), where each user's data and settings are segregated. This segmentation prevents unauthorized access to other users' preferences while maintaining the ability to support multiple users concurrently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary authentication mechanism that mediates between multiple users and the shared endpoint. Before allowing access, the intermediary verifies user credentials and determines the appropriate login mode (private or shared). This intermediary layer prevents unauthorized access by enforcing authentication protocols and ensuring that only authorized users can access the endpoint in either mode, while still enabling legitimate multi-user sharing.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If extension mobility systems allow concurrent access by multiple users, then service availability and user flexibility improve, but the system complexity and difficulty of managing user preferences increase

Engineering Contradiction:
Improveservice availabilityVSAvoidconcurrent access management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The endpoint is designed with universal functionality to handle both private and shared modes within a single device. Rather than requiring separate endpoints or complex multi-instance configurations, the universal endpoint can seamlessly switch between supporting a single user and supporting multiple users concurrently. This multi-functionality reduces system complexity by consolidating capabilities into one adaptable device while maintaining high service availability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses virtual copying of user profiles and configurations rather than physical duplication of endpoint hardware. When multiple users need concurrent access, the system creates virtual instances of user profiles (extensions, preferences, settings) that are copied and assigned to different users on demand. This virtual copying approach enables concurrent multi-user access without the complexity of managing multiple physical endpoints or complex hardware configurations.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8194836B2Enhanced extension mobility
Publication Date: 2012.06.05 CISCO TECHNOLOGY INC
  • US8194836B2 patent drawing
  • US8194836B2 patent drawing
  • US8194836B2 patent drawing

AI summary

In one embodiment, a method for enhanced extension mobility includes accessing user input indicating either a desire of a user to logon at an endpoint in a private mode according to which the endpoint supports only an extension of the user or a desire of the user to logon at the endpoint in a shared mode according to which the endpoint concurrently supports an extension of the user and one or more other extensions of one or more other users. The method includes configuring the endpoint to support only an extension of the user if the user input indicates a desire of the user to logon at the endpoint in a private mode according to which the endpoint supports only an extension of the user. The method includes configuring the endpoint to concurrently support an extension of the user and one or more other extensions of one or more other users if the user input indicates a desire of the user to logon at the endpoint in a shared mode according to which the endpoint concurrently supports an extension of the user and one or more other extensions of one or more other users.