Service Mapper for Distributed Application Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current implementations of Bluetooth profiles for distributing services between devices are limited by inadequate standardization, leading to difficulties in developing applications that work across different devices with varying connectivity standards, and the gap between link-specific communication and Internet Protocol (IP) communication remains unaddressed.

Innovation Solution

A service mapping method that utilizes a service registry and a service mapper to facilitate the distribution of services between applications by receiving notifications, requesting subscriptions, selecting appropriate subscription records, modifying service records to include localhost sockets, and registering these records with the service registry, allowing for communication independent of specific connectivity standards.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Bluetooth profiles are used for service distribution, then wireless communication between devices is enabled, but application compatibility across different devices deteriorates due to inadequate standardization

Engineering Contradiction:
Improveservice distribution capabilityVSAvoidapplication compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a service mapper as an intermediary component that sits between the application layer and the connectivity layer. This service mapper translates service requests into connectivity-specific protocols, allowing applications to work with standardized interfaces while supporting multiple connectivity standards (Bluetooth, WiFi, wired connections) without requiring application modification for each device type.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If link-specific communication interfaces are used, then device connectivity is established, but development complexity increases due to programming difficulties and device variability

Engineering Contradiction:
Improvedevice connectivityVSAvoidprogramming complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates a universal service distribution framework that can operate across multiple connectivity standards through a single standardized interface. The service mapper provides multi-functional capability by supporting Bluetooth, WiFi, and wired connections through the same application programming interface, eliminating the need for developers to write separate code for each connectivity type and reducing device-specific programming complexity.

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

3Reliability

If standardized IP interfaces are used, then application portability across devices is improved, but the gap between link-specific communication and IP communication remains unaddressed

Engineering Contradiction:
Improveapplication portabilityVSAvoidconnectivity standard support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The service mapper acts as a bridge between the IP-based application layer and link-specific communication protocols. It receives standardized IP interface requests from applications and translates them into appropriate connectivity-specific protocols (Bluetooth, WiFi, wired), thereby maintaining application portability while enabling support for multiple connectivity standards without requiring applications to be modified.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7493373B2Providing service distribution between distributed applications
Publication Date: 2009.02.17 HFI INNOVATION INC
  • US7493373B2 patent drawing
  • US7493373B2 patent drawing
  • US7493373B2 patent drawing

AI summary

A system is provided to facilitate distribution of a service between a first application and a second application. The system includes a remote socket object, a service registry, and a service mapper. The service mapper receives notification from the service registry indicating registration of the remote socket object created in response to a request for a service at the first application. The service mapper requests an active subscription list from the service registry and selects a subscription record from the active subscription list. The subscription record is associated with the second application. The service mapper sends the selected subscription record to the second application using a remote device port mapped to a localhost port and receives a service record from the second application including a socket for communicating with the second application. The service mapper sends a modified service record that includes a localhost socket mapped to the socket to the service registry that registers the second application using information from the modified service record.