Skip to content

Areas API proposal#87

Merged
tlohmar merged 5 commits intocamaraproject:mainfrom
hubertp-ericsson:hubertp-areas-api
Feb 12, 2026
Merged

Areas API proposal#87
tlohmar merged 5 commits intocamaraproject:mainfrom
hubertp-ericsson:hubertp-areas-api

Conversation

@hubertp-ericsson
Copy link
Contributor

@hubertp-ericsson hubertp-ericsson commented Nov 28, 2025

What type of PR is this?

enhancement/feature

What this PR does / why we need it:

This PR proposes a new API to be added to the Dedicated Network API family to provide information about the geographical areas where consistent service coverage according to one or more network profiles is supported. This API makes such areas discoverable.

Which issue(s) this PR fixes:

Fixes #86

Special notes for reviewers:

Changelog input

 A new API is added which provides information about the geographical areas where consistent service coverage according to one or more network profiles is supported. 

Additional documentation

This section can be blank.

docs

@tlohmar tlohmar changed the title Hubertp areas api Areas API proposal Dec 16, 2025
@hubertp-ericsson
Copy link
Contributor Author

Attaching a presentation describing the concept.
AreasAPIforCAMARA.pptx

@Masa8106
Copy link

@hubertp-ericsson, thank you for providing the slide decks.
I see the proposed Areas API is within Dedicated Network repository and is designed only for Dedicated Network as I can see ServiceArea includes networkProfiles. Just in my opinion, I think it would be better if this Areas API can be generalised not only for Dedicated Network but also for other CAMARA APIs.

@Masa8106
Copy link

As far as I see so far, my comments are the followings:

  • AreaName would be good to be kept, as it is used as input parameter of QoS B API.
  • ServiceArea schema would be good to have QoS Profile as well as networkProfiles, as it can be applicable in a case of QoS B API.

@hubertp-ericsson
Copy link
Contributor Author

hubertp-ericsson commented Jan 21, 2026

To align with QoS Booking API I have added to the service area a list of supported QoS profiles. The service area has a 'name' property with content that is not necessarily unique. To uniquely identify the service area QoS Booking API could use the 'id' property which is meant to be unique, and is also a string but in uuid format.

@Masa8106
Copy link

It makes sense that the serviceArea has "name" and "id", so far.

@sergiobrisio

This comment was marked as off-topic.

Copy link
Contributor

@tlohmar tlohmar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@tlohmar tlohmar merged commit 1c362cc into camaraproject:main Feb 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Finding suitable areas where a reservable connectivity service can be provided

4 participants