Web Services Architecture for Federated Mobile Device Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of software development for mobile devices and the need for seamless integration of access methods across various devices and content hosts in the mobile web services environment pose challenges in providing comprehensive information and service environments, particularly in addressing architectural issues for proper interaction and data flow between web services components.

Innovation Solution

A web services architecture that includes a telecommunications provider system, a service provider, and a mobile application, which facilitates rapid development and deployment of mobile internet applications by leveraging a framework of business components for identifying mobile devices, federating information, and providing location-based services, thereby enabling efficient data exchange and service delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If web services architecture is implemented for mobile devices, then service delivery and data exchange are improved, but architectural complexity increases

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidarchitectural complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the web services architecture into distinct functional components: mobile device layer, wireless network layer, service provider layer, and content host layer. Each layer handles specific tasks independently, reducing overall architectural complexity while maintaining efficient service delivery. The service provider acts as an intermediary that simplifies interactions between mobile devices and content hosts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service provider functions as an intermediary component that mediates between mobile devices and content hosts. It manages authentication, authorisation, and service delivery workflows, thereby reducing the complexity burden on both mobile devices and content hosts while improving overall service delivery efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If comprehensive information federation is implemented across multiple devices and content hosts, then service completeness is improved, but system complexity increases

Engineering Contradiction:
Improveservice completenessVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service provider implements universal authentication and authorisation mechanisms that work across multiple devices and content hosts. This multi-functional approach allows a single service provider to manage federated information across diverse platforms, improving service completeness without requiring each system to implement complex individual solutions.

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

Solution Approach 2:

The system performs preliminary authentication and authorisation actions through the service provider before actual service delivery. This pre-processing of identity verification and permission checks simplifies subsequent interactions between mobile devices and content hosts, reducing overall system complexity while enabling comprehensive information federation.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If custom web services applications are developed for mobile devices, then functionality is improved, but development time and programming effort increase

Engineering Contradiction:
Improveapplication functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent enables copying and reuse of service provider configurations, authentication mechanisms, and service delivery workflows across multiple mobile applications. Instead of developing custom authentication and service management code for each application, developers can replicate proven service provider implementations, significantly reducing development time while maintaining functionality.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The service provider implements self-service capabilities that automatically handle authentication, authorisation, and service delivery without requiring extensive custom programming. The system self-manages service workflows and device interactions, allowing developers to focus on application-specific functionality rather than infrastructure code, thereby reducing development time.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8369875B1Web services architecture for providing federated data relating to a mobile device
Publication Date: 2013.02.05 T MOBILE INNOVATIONS LLC
  • US8369875B1 patent drawing
  • US8369875B1 patent drawing
  • US8369875B1 patent drawing

AI summary

The present disclosure is directed to a web services architecture comprising a component operable for rapid development of a web services application, a mobile application. The web services architecture also includes a telecommunications provider system and a service provider. The mobile application is related to the web services application deployable on a mobile device. The telecommunications provider system is operable to host the web services application and to identify the mobile device and federate information related to the mobile device. The service provider is operable to provide a mobile device service associated with the web services application. The service provider is in communication with the web services application and operable to use the federated information related to the mobile device to provide application services to the mobile device.