| HCRP case study |
| |
| The ‘profiles’ are sometimes also identified as
‘middleware’. When the word ‘middleware’
is used in the documentation delivered with the profile components,
It means the collection of Bluetooth profiles components between
the stack and the application which can be shown in Figure 2. |
| |
 |
| |
The architecture of the middleware is represented in
the figure 3.
This figure shows that profiles are working independent from each
other. Now here comes the HCRP, where it forms a single independent
component. |
| |
 |
| |
| Specifications of the HCRP Profile software |
The main specification about HCRP |
- An Application profile, for connecting devices such as printers
and scanners to devices such as laptops and desktop computers
without a physical cable.
- Defines the interoperability requirements for the applications
within the Hardcopy Cable Replacement application profile.
|
| |
 |
| |
