[API Proposal] <InHomeDeviceManagementAPI>

[abd-abhisek]

Description

API provides ability to manage household devices connected to modem in the customer’s household.

API provides information on current and recent connections, network details(IP and MAC address, connected to, etc..), typing, visibility state and personalization information for customers.

API's functionality covers a wide range of devices connected to the home network, including Customer Devices (Mobile, Tablet, Laptop, Desktop, IoT device etc.) & Operator Provided Devices (Boosters, Pods).

API ensures comprehensive device management, including retrieval of device information, addition of new devices, updating device configurations, deleting device records, and executing specific actions on devices
Use cases

Related to

Supporting material

[eric-murray]

Hi @abd-abhisek

What use cases would such an API support that could not be achieved using TR-369?

And if you do see gaps in TR-369, why do you think it is better to develop a new API within CAMARA, rather than evolving TR-369 within the Broadband Forum?

[albertoramosmonagas]

Hi @abd-abhisek

I’ve added the new InHomeDeviceManagement API to the minutes for the next API Backlog meeting, and I’ll also include it in the agenda for next week.

That said, I’m a bit concerned about a possible overlap with the already approved Home Devices QoD API, since both build on the same household device inventory.

Thanks,
Alberto

[ravim95-eng]

Hi @abd-abhisek

What use cases would such an API support that could not be achieved using TR-369?

And if you do see gaps in TR-369, why do you think it is better to develop a new API within CAMARA, rather than evolving TR-369 within the Broadband Forum?

Hi @eric-murray

• BBF TR369 standard focus is on low-level aspects of broadband networks, primarily for service providers to implement. Camara provide higher level of abstraction, simplifying APIs for consumption by varied consumers without knowledge of underlying network standards/protocols.
• Proposed Camara Device API can be consumed by non-telecom domain consumers as it is agnostic to underlying standards like TR369, TR069, TR181 etc. These BBF standards used by service providers to internally work with connected devices.

[ravim95-eng]

Hi @abd-abhisek

I’ve added the new InHomeDeviceManagement API to the minutes for the next API Backlog meeting, and I’ll also include it in the agenda for next week.

That said, I’m a bit concerned about a possible overlap with the already approved Home Devices QoD API, since both build on the same household device inventory.

Thanks, Alberto

Hi @albertoramosmonagas
I see the proposed InHomeDeviceAPI to be foundational/pre-requisite API for usecases like Home Devices QOD API rather than functional overlap