Mobile Application Framework for Context-Driven Channel Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile communication systems lack an efficient mechanism for context-driven data communication channel selection, which hinders the ability to provide differentiated communication treatments for various services and applications, leading to inefficiencies in service request processing and increased development time for mobile applications.
Innovation Solution
A mobile application framework that utilizes a single application programming interface (API) to manage service requests across multiple communication channels, employing a business logic manager to map service request signatures to appropriate access point nodes (APNs) for context-driven channel selection, enabling flexible and adaptive communication treatments without requiring extensive integration with individual applications or networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobile applications communicate with application servers through multiple communication channels without a unified framework, then service requests can be processed, but the complexity of integration between applications and networks increases significantly
Solution Approach 1:
The patent introduces a mobile application framework as an intermediary layer between mobile applications and communication networks. This framework includes a service request generator in the application that creates standardized service requests, which are then processed by a service request interpreter in the network that translates them into appropriate communication actions. This intermediary structure enables multiple communication channels to be supported without increasing application complexity, as the framework handles the adaptation logic centrally.
Solution Approach 2:
The mobile application framework provides universal service request handling that works across multiple communication channels (billing and non-billing data traffic). The service request generator and service request interpreter are designed to handle diverse communication scenarios through a unified interface, allowing the same framework structure to support different communication channels without requiring channel-specific integration code in each application.
2Ease of operation
If each mobile application implements its own communication channel selection logic, then communication can be established, but the development time and effort for mobile applications increases
Solution Approach 1:
The framework enables self-service communication channel selection by embedding a service request generator within the mobile application that automatically generates service requests based on application needs. The service request interpreter in the network automatically interprets and routes these requests to appropriate communication channels. This self-service mechanism eliminates the need for developers to manually implement channel selection logic, reducing development time while maintaining ease of communication establishment.
Solution Approach 2:
The framework performs preliminary action by pre-defining service request structures and interpretation rules in the mobile application framework. The service request generator is pre-configured with knowledge of available communication channels and selection criteria, allowing it to automatically generate appropriate service requests without runtime decision-making complexity. This preliminary structuring of communication logic reduces development effort while ensuring proper channel selection.
3Adaptability or versatility
If differentiated communication treatments are implemented for various services without a framework, then service differentiation is possible, but the complexity of managing multiple communication channels increases
Solution Approach 1:
The service request interpreter acts as a mediator between standardized service requests and differentiated communication treatments. It contains the logic for interpreting service request types and routing them to appropriate communication channels (billing or non-billing data traffic). This centralizes the complexity of channel management in the network infrastructure rather than in each application, enabling service differentiation without proportionally increasing overall system complexity.
Solution Approach 2:
The framework enables service differentiation by changing parameters in the service request structure (such as service type, priority, data traffic category) that the service request interpreter uses to determine appropriate communication channel treatment. By encoding differentiation criteria in request parameters rather than in application logic, the system achieves versatile service differentiation while keeping channel management complexity centralized and manageable.
Data Source
AI summary
A user equipment (UE) comprising a processor, a memory, a radio transceiver, and a mobile application framework client stored in the memory. When executed by the processor the client receives a request for a communication service via an API, builds a service request message comprising an application identity and an identity of the requested service, transmits the service request message via the radio transceiver directed through a first communication channel defined by a first access point node (APN) specified by the client to a server, receives a first service response message comprising a second APN from the server, transmits the service request message via the radio transceiver directed through a second communication channel defined by the second APN to the server, and receives a second service response message from the second communication channel defined by the second APN from the server.