GATT Server EATT Bearer Database View Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Bluetooth LE systems do not allow different applications on a GATT client to access different GATT databases or views of a database, even with multiple EATT bearers, leading to scenarios where applications may not need access to the entire database.
Innovation Solution
A system and method where the GATT server identifies the EATT bearer used by each application and associates it with a customized view of the GATT database, allowing each application to access a unique view based on its EATT bearer identity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If a single GATT database is made accessible to all applications, then all applications can access the complete data set, but applications may access data that is not relevant or private to them
Solution Approach 1:
The patent segments the single GATT database into multiple application-specific views or databases. Each application receives a customized view containing only the data relevant to it, achieved by creating separate GATT database instances or filters for each application based on its EATT bearer identity.
Solution Approach 2:
The patent applies local quality by making each application's data view unique and tailored to its specific needs. Each application sees a customized version of the GATT database with data selected based on its identity, ensuring data privacy and relevance through application-specific data presentation.
2Ease of operation
If multiple EATT bearers are established for different applications, then each application can have dedicated communication channels, but the same GATT database is still presented to all applications
Solution Approach 1:
The patent merges the EATT bearer identity with the GATT database presentation logic. The server combines the communication channel identification (EATT bearer) with data filtering to present the appropriate customized database view to each application through its dedicated bearer.
Solution Approach 2:
The patent introduces an intermediary mechanism at the GATT server that sits between the EATT bearer layer and the GATT database layer. This intermediary filters and customizes the database content based on the EATT bearer identity, preventing direct access to the raw database while enabling application-specific views.
3Loss of information
If the GATT server presents different database views to different applications, then data privacy and relevance are improved, but the system complexity increases
Solution Approach 1:
The patent uses copying by creating virtual copies or views of the GATT database for each application rather than maintaining entirely separate physical databases. Each application receives a customized view that appears as a separate database but is managed through the same underlying infrastructure, reducing complexity.
Solution Approach 2:
The patent changes parameters such as the EATT bearer identity to dynamically determine which database view to present to each application. By using parameter-based routing and filtering, the system can present different database views without requiring complex manual configuration for each application.
Data Source
AI summary
A system and method for presenting different GATT databases or different views of a GATT database based on the EATT bearer identity is disclosed. The GATT server identifies the EATT bearer being used and associates an application with that EATT bearer identity. The GATT server then creates an association between the application and a customized view of the GATT database that is presented to that application. In this way, a GATT client, with several applications resident thereon, may create a plurality of different connections to the GATT server, each with a unique EATT bearer identity. Each of these applications may have its unique customized view of the GATT database, based on that EATT bearer identity.