Authorization Code Decoupling for Mobile Content Charging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile service providers face trust issues and revenue challenges due to fraudulent content partners in the off-deck content model, leading to customer dissatisfaction, increased support costs, and revenue leakage, which limits their ability to partner with a large number of content providers.

Innovation Solution

A method and apparatus that generate and verify an authorization code for content purchases, decoupling the authorization process from the ordering process, allowing asynchronous authorization and batch processing, thereby ensuring transparent and controlled content delivery without redirecting users to the service provider's site.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service providers adopt the off-deck model to partner with content providers, then content variety and volume increase, but trust and control over charging claims deteriorate

Engineering Contradiction:
Improvecontent varietyVSAvoidtrust in charging claims
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an authorization code as an intermediary mechanism between the service provider and content provider. The authorization code is generated by the service provider and sent to the customer through a separate channel (SMS), acting as a mediator that verifies legitimate content purchases without requiring the service provider to fully trust the content provider's charging claims. This resolves the contradiction by enabling content variety through off-deck partnerships while maintaining reliability through the intermediary authorization verification system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the charging authorization process into distinct components: content request, authorization code generation, separate channel transmission, and verification. By dividing the trust verification into separate steps and channels, the system enables content variety while preventing fraudulent charging claims. The segmentation allows the service provider to maintain control over authorization without limiting content provider participation.

Inventive Principle:
Principle #1Segmentation

2Loss of energy

If service providers verify all content purchases through their channel, then revenue control improves, but customer convenience and transaction speed deteriorate

Engineering Contradiction:
Improverevenue leakageVSAvoidcustomer convenience
Core Design Contradiction:
Loss of energyVSEase of operation

Solution Approach 1:

The service provider performs preliminary action by generating and sending the authorization code to the customer through SMS before the actual content delivery. This preliminary verification step ensures revenue control is maintained while the customer experience remains convenient, as the authorization code is automatically delivered without requiring customer action. The preliminary action prevents revenue leakage while preserving ease of operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically delivering the authorization code to the customer's mobile device via SMS without requiring the customer to contact the service provider or navigate to a website. The customer simply receives the code and can proceed with the transaction, maintaining convenience while the service provider retains verification control to prevent revenue leakage.

Inventive Principle:
Principle #25Self-service

3Reliability

If service providers redirect users to their site for authorization, then control and verification improve, but user experience and usability deteriorate

Engineering Contradiction:
Improveauthorization controlVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The authorization code sent via SMS acts as an intermediary that carries the verification information directly to the customer without requiring redirection to the service provider's website. The code serves as a portable verification token that maintains authorization control while eliminating the need for users to navigate away from the content provider's interface, thus preserving user experience and ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Object-generated harmful factors

If service providers implement strict authorization verification, then fraudulent transactions decrease, but processing time and system complexity increase

Engineering Contradiction:
Improvefraudulent transactionsVSAvoidauthorization system complexity
Core Design Contradiction:
Object-generated harmful factorsVSDevice complexity

Solution Approach 1:

The patent extracts the complex verification logic from the main transaction flow and implements it as a separate authorization code generation and verification process. The authorization code contains the necessary verification information, allowing fraudulent transactions to be prevented without requiring complex real-time verification systems. This extraction reduces system complexity while maintaining effectiveness against fraudulent transactions.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10068236B2Methods and arrangements for third party charging authorization for mobile service providers
Publication Date: 2018.09.04 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10068236B2 patent drawing
  • US10068236B2 patent drawing
  • US10068236B2 patent drawing

AI summary

Methods and arrangements for handling web-based purchase requests. A customer request for content of a third party content provider is received at a charging service provider. An authorization code on behalf of the content provider is generated and returned to the customer via a channel other than a channel which links the customer with the third party content provider. The authorization code is accepted from the third party content provider as received by the third party content provider from the customer, the authorization code is verified, and charging for the requested content is executed.