Service Management Entity for Clientless Wireless Context

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Providing consistent value-added services to multi-RAT devices across heterogeneous wireless networks is challenging due to the lack of contiguous coverage and the need for specific client software, which disrupts service delivery when devices roam between different network types, such as business and home networks.

Innovation Solution

The implementation of a Service Management Entity (SME) and a Service Delivery Entity (SDE) system that uses Proxy Auto-Configuration (PAC) files to manage and deliver services without requiring specific client software on wireless receive/transmit units (WRTUs), allowing for location-based triggering of transactions and messages across HTTP transfers without disrupting wireless network configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If client software is downloaded on WRTU to enable server interrogation, then service delivery can be enabled, but device complexity increases and ease of operation decreases

Engineering Contradiction:
Improveservice delivery consistencyVSAvoidclient software requirement
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a Service Management Entity (SME) as an intermediary component within the access point that manages service delivery without requiring client software on the WRTU. The SME intercepts HTTP requests, determines service applicability based on device characteristics and location, and delivers services through the existing web browser, thereby eliminating the need for additional client software while maintaining reliable service delivery

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables WRTUs to receive services through their built-in web browsers without requiring any special client software installation. The service delivery mechanism uses standard HTTP protocols that any web-capable device can handle, allowing devices to serve themselves through existing functionality rather than requiring external software assistance

Inventive Principle:
Principle #25Self-service

2Reliability

If registration is controlled by domain server at business hot-spot, then service delivery is enabled, but service continuity is disrupted when roaming to home network

Engineering Contradiction:
Improveservice deliveryVSAvoidservice consistency across networks
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The Service Management Entity is designed to operate universally across different network types (business hot-spots, home networks, enterprise networks) using standard HTTP protocols. It can handle multiple functions including service delivery, location tracking, and device characterization without requiring network-specific configurations, enabling consistent service delivery across heterogeneous networks

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

Solution Approach 2:

The system dynamically adjusts service delivery parameters based on the WRTU's location, network type, and device characteristics. The SME modifies service parameters such as content delivery timing, format, and method according to the current network environment, ensuring optimal service delivery whether the device is on a business network or home network

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If WRTU roams between different network types, then coverage flexibility increases, but service delivery is disrupted

Engineering Contradiction:
Improvenetwork roaming capabilityVSAvoidservice delivery continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The Service Management Entity maintains continuous service delivery across network transitions by monitoring WRTU movements and pre-positioning service content. When a device roams between networks, the SME ensures uninterrupted service by maintaining session continuity and delivering content through the current network connection without requiring re-registration or service interruption

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If advanced services are provided to multi-RAT devices, then service functionality increases, but network heterogeneity complexity increases

Engineering Contradiction:
Improvemulti-RAT service supportVSAvoidnetwork management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Service Management Entity acts as a centralized intermediary that manages all service delivery to multi-RAT devices regardless of which radio access technology is being used. It abstracts away the complexity of different network types (3G, 4G, WiFi, Bluetooth) by providing a unified service management interface, thereby supporting advanced services without increasing overall system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11224040B2Clientless method for context driven wireless interactions
Publication Date: 2022.01.11 CHARTER COMM OPERATING LLC
  • US11224040B2 patent drawing
  • US11224040B2 patent drawing

AI summary

Described herein are methods and apparatuses for the provision and management of value added services without a requirement for specific client software on a wireless receive/transmit unit (WRTU). The methods and apparatuses described may be applied to wireless networks supporting HTTP transfers without disrupting the wireless network configuration. In the embodiments described herein, a web request may be received by a Service Management Entity (SME) that may be located in an access point (AP) from a WRTU. The SME may transmit a proxy auto-configuration (PAC) file to the WRTU. This PAC file may include a uniform resource locator (URL) associated with a Service Delivery Entity (SDE), and the URL chosen may be based on rules associated with a location of the WRTU. The SDE may then receive a second web request from the WRTU and respond by transmitting a message to the WRTU such as a transaction trigger.