Request-Oriented Service Architecture for Flexible Network Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The development of new products or features in network services is hindered by the need for substantial time and effort, as existing approaches require substantial system integration and concrete implementation, leading to increased costs and delayed time-to-market.

Innovation Solution

A request-oriented service architecture (ROSA) that allows new products or features to be decoupled from the network and integrated into requests, using a communication integration platform to transform verb-noun requests into canonical forms, enabling decomposition into child requests and routing to appropriate resource managers for execution, thus reducing the burden on servers and improving flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If new products or features are integrated into the network using traditional service architectures, then system implementation is achieved, but development time and effort increase substantially

Engineering Contradiction:
Improvedevelopment speedVSAvoidtime-to-market
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the service architecture into request-oriented components where new products or features are decomposed into independent requests that can be processed separately. This allows parallel development and integration without requiring comprehensive system reconfiguration, thereby reducing development time and accelerating time-to-market while maintaining implementation quality

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a request-oriented service architecture as an intermediary layer between the network infrastructure and new product implementations. This mediator translates implementation requirements into standardized requests, eliminating the need for direct system integration and substantially reducing development effort and time

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If traditional service architectures are used for system integration, then product implementation is achieved, but development costs increase

Engineering Contradiction:
Improveease of implementationVSAvoiddevelopment cost
Core Design Contradiction:
Ease of manufactureVSLoss of energy

Solution Approach 1:

The patent creates a universal request-oriented service architecture that can handle multiple product implementations through a common framework. This multi-functional approach allows the same infrastructure to support diverse products without requiring separate integration efforts for each, thereby reducing development costs while maintaining ease of implementation

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

3Adaptability or versatility

If concrete implementation approaches are used, then product features are delivered, but system complexity increases

Engineering Contradiction:
Improveflexibility of service deploymentVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the implementation-specific logic from the core system architecture and encapsulates it within request objects. This separation allows the system to remain simple and stable while accommodating flexible service deployments through request variations, thereby reducing system integration complexity while maintaining deployment flexibility

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8868713B2Method and apparatus providing a user interface for a request-oriented service architecture
Publication Date: 2014.10.21 VERIZON PATENT & LICENSING INC
  • US8868713B2 patent drawing
  • US8868713B2 patent drawing
  • US8868713B2 patent drawing

AI summary

An approach for providing a request in a request-oriented service architecture is described. A user interface is presented. A verb-noun request based on an input into a user interface causes generation of a transaction based on a feature, declaration information, an action to be performed on the feature, and a current state of the feature. A response is received indicating that the current state of the feature is updated, at least in part, by the transaction. An indication relating to the response is presented by the user interface.