Application Profiles for Wireless Data Session Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems lack the ability for network operators and service providers to track and bill users based on application-specific usage, as they are limited to generic data sessions, which does not allow for differentiated billing or usage tracking.

Innovation Solution

The implementation of systems and methods that provision wireless devices with multiple application profiles, enabling application-specific network address identifiers for data sessions, allowing service providers to track and bill based on application usage, and incorporating priority categorization to manage data session conflicts and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single generic data session is used for multiple applications, then device operation is simplified and convenient, but network operators cannot track application-specific usage for differentiated billing

Engineering Contradiction:
Improvedata session managementVSAvoidapplication usage tracking information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the single generic data session into multiple application-specific data sessions, each associated with a unique application profile containing network address identifiers. This allows the system to maintain separate tracking information for each application while preserving the convenience of automated session management through profile-based configuration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different network address identifiers and profile characteristics to different applications. Each application profile contains specific configuration parameters (APN, authentication details, etc.) tailored to that application's requirements, enabling differentiated billing and tracking while maintaining overall system simplicity through centralized profile management.

Inventive Principle:
Principle #3Local quality

2Loss of information

If multiple application profiles with separate data sessions are implemented, then application-specific usage tracking and differentiated billing are enabled, but device complexity and data session management overhead increase

Engineering Contradiction:
Improveapplication usage tracking informationVSAvoidprovisioning information management
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a universal application profile structure that can serve multiple applications with similar requirements. The standardized profile format allows the same framework to handle diverse applications (messaging, browsing, email) by simply changing the profile parameters, reducing the need for application-specific customization logic and simplifying device provisioning.

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

Solution Approach 2:

The patent applies preliminary action by pre-configuring application profiles with all necessary provisioning information (network address identifiers, authentication credentials, APN settings) before the applications are executed. This advance configuration eliminates the need for complex runtime decision-making and reduces device complexity during actual operation, as the session management follows predetermined profile rules.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If multiple data sessions are established for different applications, then usage tracking precision is improved, but resource utilization efficiency decreases due to potential session conflicts

Engineering Contradiction:
Improveapplication usage measurementVSAvoidnetwork resource utilization
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent merges multiple application-specific data sessions when they share common profile characteristics and network address identifiers. Applications with identical or compatible profiles can share the same data session, reducing the total number of active sessions and improving resource utilization while maintaining precise tracking by associating usage records with individual applications through their profile identifiers.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent dynamically adjusts session parameters based on application priority and current network conditions. When resource conflicts are detected, the system modifies session parameters (such as bandwidth allocation, session activation/deactivation) according to predefined priority levels in the application profiles, enabling efficient resource utilization while maintaining measurement precision through continuous parameter monitoring and adjustment.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2204053B1Systems and methods for provisioning wireless devices based on multiple network-service application profiles and data session conflict resolution
Publication Date: 2019.05.15 QUALCOMM INC
  • EP2204053B1 patent drawingFigure 1
  • EP2204053B1 patent drawingFigure 2
  • EP2204053B1 patent drawingFigure 3

AI summary

Apparatus and methods of differentiated data session access on a wireless communication device and dynamic source determination of provisioning information on a wireless communication device are disclosed. User Identity Modules (UIMs) are provisioned such that network-service applications resident on the wireless device are associated with a corresponding application profile within the UIM. Each networkservice application has a corresponding network address identifier defined within the user profile. The network address associated with the identifier is used to establish a data session for the corresponding network service application. By providing for application-specific network addresses, service providers and/or network operators can differentiate between what services a user is accessing during a data session. In addition, the UIMs may be provisioned with priority category identifiers that allow the associated network-service application to be prioritized for data session establishment.