Service Management Agent for Multi-Vendor User Class Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing user service classes across multiple disparate services or software vendors is costly, time-consuming, and error-prone, requiring multiple trained administrators and costly hardware for central databases and directory development, as well as frequent updates and cross-vendor alignment issues.

Innovation Solution

The system extends the management interface with an agent and multiple service templates, allowing administrators to update user service classes at the role level without individual attribute management, using evaluation functions and templates to dynamically set attribute settings, and enables message-based updates across services without a central directory, reducing the need for multiple administrators and costly infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a central database or directory is implemented to manage service attributes across multiple services, then service management becomes centralized and consistent, but hardware costs and system complexity increase significantly

Engineering Contradiction:
Improveservice management consistencyVSAvoidcentral database infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

An agent is introduced as an intermediary component that runs on each service platform. This agent translates service attribute information from a simplified format into the specific formats required by each service, eliminating the need for a complex central database while maintaining consistent service management across multiple platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of maintaining a single source of truth in a central database, the system creates copies of service attribute information through agents on each service platform. Each agent maintains a local representation of service attributes and translates them appropriately for its service, reducing centralized infrastructure requirements.

Inventive Principle:
Principle #26Copying

2Reliability

If multiple trained administrators are assigned to manage different services, then each service can be managed by experts, but training costs and operational complexity increase

Engineering Contradiction:
Improveservice management expertiseVSAvoidadministrator training time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The agent automatically performs the complex task of translating and applying service attribute settings across multiple services. Instead of requiring administrators to manually configure each service, the system enables self-service through automated translation and application of settings, reducing the need for highly trained administrators.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A single administrator can manage service attributes across multiple different services through a unified interface. The agent handles the service-specific translation automatically, making the administration process universal across different service types and reducing the need for service-specific training.

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

3Manufacturing precision

If service attributes are managed individually for each service, then each service can be configured precisely, but the time and effort required to update attributes across multiple services increases

Engineering Contradiction:
Improveservice attribute configuration accuracyVSAvoidattribute update speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system segments service attribute management into two parts: a unified service attribute definition and service-specific translation rules. This allows administrators to define attributes once at the service level while the agent handles the segmentation and translation to each specific service platform, maintaining precision while improving update speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The agent pre-configures translation rules and mappings for each service platform in advance. When service attributes need to be updated, the agent already has the translation templates ready, allowing for rapid and accurate application of settings across multiple services without manual reconfiguration each time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8954879B2Method and apparatus for sharing user service classes
Publication Date: 2015.02.10 RINGCENTRAL INC
  • US8954879B2 patent drawing
  • US8954879B2 patent drawing
  • US8954879B2 patent drawing

AI summary

This disclosure describes a system in which individual employee records can be updated across multiple services by an administrator at the interface to a particular service. Multiple services may be provided with this capability. This will eliminate the need in the current art for a central directory that contains a service description that will be common across all services. The technology eliminates the need for the development of this directory and the training of administrators in its interface. Administrators may utilize their training in one service interface to update records across multiple services. This will enable the more rapid development of solutions utilizing services from multiple vendors. Administrators need not be trained on interfaces for all services but can apply routine global updates from a convenient and familiar interface.