Core Network Entity for Non-A/V Media Capability Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers face challenges in determining whether a consumer's domain supports non-A/V media output, such as scent or tactile feedback, especially in wireless communication networks, as existing methods require proprietary applications or URI differentiation, which can be cumbersome and difficult to implement.
Innovation Solution
A method and system for retrieving and providing capability information from a subscriber database in a core network domain, allowing content providers to determine if a subscriber's device supports non-A/V media by sending a subscriber capability request and receiving a response indicative of support for tactile, olfactory, or other non-A/V media, enabling selective enablement or disablement of these features on a per-session basis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If proprietary applications are installed on consumer devices to determine non-A/V media capability, then capability information can be obtained, but device complexity and ease of operation are worsened
Solution Approach 1:
The patent introduces a core network entity as an intermediary that stores and provides capability information about non-A/V media support. Instead of requiring proprietary applications on consumer devices, the network entity acts as a mediator that content providers can query to obtain capability information, thereby eliminating the need for device-side applications while still achieving the goal of determining capability.
Solution Approach 2:
The system enables self-service by allowing the network to automatically manage and provide capability information without requiring consumer action. The core network entity maintains capability information and makes it available to content providers through standardized interfaces, eliminating the need for consumers to install or interact with proprietary applications.
2Loss of information
If URI differentiation is used to support non-A/V media, then capability-based access is achieved, but ease of operation and adaptability are worsened
Solution Approach 1:
The core network entity serves as an intermediary that provides capability information through standardized interfaces, replacing the need for complex URI differentiation schemes. Content providers can query the network entity to obtain capability information and adapt their content delivery accordingly, without needing to implement complex URI tagging systems.
Solution Approach 2:
The patent changes the approach from modifying URIs to changing the parameter of capability information retrieval. Instead of encoding capability information in URIs, the system uses standardized network interfaces where capability information is provided as queryable parameters, simplifying both implementation and adaptability.
3Loss of information
If proprietary applications are used for capability determination, then capability information is obtained, but ease of operation is worsened
Solution Approach 1:
The network automatically manages capability information without requiring consumer participation. The core network entity maintains and provides capability information through standardized interfaces, allowing content providers to determine capability without consumers installing or interacting with any applications, thereby greatly improving ease of operation.
Data Source
AI summary
A technique of handling capability information stored in a subscriber database in a core network domain of a wireless communication network is presented. A method implementation of the technique comprises receiving a subscriber capability request, wherein the subscriber capability request includes an identifier associated with a subscription. The method further comprises retrieving from the subscriber database, in response to the subscriber capability request, subscriber capability information for the subscription associated with the first identifier. The subscriber capability information is indicative of support of at least one non-A/V medium different from video (V) and audio (A) in a subscriber domain, such as a olfactory (scent-related) or tactile (haptic) medium. Further still, the method comprises sending a subscriber capability response including the subscriber capability information.