Commonalities Proposal: Standardize Group Management for CAMARA Sub-Projects

[shilpa-padgaonkar]

Problem description
Across CAMARA sub-projects (CQM family, Device Status, Iot Network optimization, Subscription-APIs, etc.), resource supports only a single device, represented by MSISDN, IP address, etc.).

This works for basic use cases, for one-to-one operations, but real-world use cases increasingly require APIs to operate on multiple devices or logical collections of devices.

Today, CAMARA APIs assume operations on one device at a time. This causes challenges in scenarios where API consumers need to:

• Execute actions on large sets of devices (IoT fleets, enterprise device pools)
• Define logical groups based on attributes (location/area, subscription type, devices)
• Create subscription for events for many devices in a single request
• Apply batch operations or coordinated actions across devices

Several sub-projects (e.g., CQM-family, Device Status, IoT Connectivity) are encountering similar requirements and addressing them independently. This indicates the need for a standardized, cross-API solution.

Possible evolution
To address this cross-cutting need, we propose defining a Group Management API as a draft PR to this issue for review.

Feedback on scope, modeling, and alignment is welcome.

Disclaimer:
Although the problem statement and examples emphasize device groups, the requirement emerges across other resource types as well, such as groups of locations, and potentially others.
To support these broader scenarios consistently, the proposed solution should be framed as a general Group Management API, with device groups being the initial and most visible use case.

Alternative solution

Additional context
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/421265431/2025-12-12+Connectivity+Quality+Management+Minutes

cc: @gmuratk

[PedroDiez]

Some initial comments:

• It would be relevant to know the purpose and how to use this functionality in different APIs mentioned
• To think about how this "Group management feature" fits in 3-legged scenarios (i.e. all the devices are under the control of the same subscription? how to manage token retrieval and guarantee the scope, or even are initially though for B2B scenarios -2-legged tokens?)
• Aspects regarding privacy (grouping of elements that are susceptible to contain personal information, management of consents)
• Routing aspects in case a "group of elements" may contain elements belonging to different Telco Operators

Then, it seems to be a wider topic than the definition of a new API.

[gmuratk]

Update: Idea was presented at the Commonalities Meeting on 22 December 2025.