Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

New Proposal-Network Slicing API #317

Closed
chinaunicomyangfan opened this issue Sep 28, 2023 · 10 comments
Closed

New Proposal-Network Slicing API #317

chinaunicomyangfan opened this issue Sep 28, 2023 · 10 comments

Comments

@chinaunicomyangfan
Copy link
Contributor

PR-https://github.com/camaraproject/WorkingGroups/pull/316

@chinaunicomyangfan
Copy link
Contributor Author

chinaunicomyangfan commented Sep 28, 2023

This api is mainly to provide developers the ability to reserve, dynamically provisioning, query, dynamically delete a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. Any suggestions will be great for us. And if you have any question with this API, please feel free to ask me at anytime, Thank you!

@chinaunicomyangfan chinaunicomyangfan changed the title New Proposal-Service Booking API New Proposal-Network Slicing API Oct 20, 2023
@jordonezlucena
Copy link
Contributor

PR-https://github.com/camaraproject/WorkingGroups/pull/316

We don't have a PR linked to this issue (the old one is closed and no longer works). Could you please check and submit a new one?

@chinaunicomyangfan
Copy link
Contributor Author

I'm sorry, I accidentally rolled back the previous version, which caused the previous PR to be closed. Now I have submitted a new PR,#333

@chinaunicomyangfan
Copy link
Contributor Author

chinaunicomyangfan commented Oct 27, 2023 via email

@eric-murray
Copy link
Contributor

I commented in the PR conversation

@FabrizioMoggio
Copy link
Contributor

This API is very interesting and we are also discussing about it in GSMA OPAG. A first discussion in GSMA was about what is actually offered to the developer: a 3GPP Slice or a Communication Service? The feeling is that we are going to expose a Communication Service that can leverage on a 3GPP Network Slice or not, depending on the Networks underneath or by policies or other commercial aspects.

@Kai-hw
Copy link

Kai-hw commented Dec 15, 2023

Thank you @FabrizioMoggio , I just saw your comment here.
I made some explanation for the purpose of this proposed API, please see my latest reply AT:
here - in the PR conversation

A developer may use this user-friendly API to book a network slice with expected service time period, expected service area, expected guaranteed numbers of terminals and expected SLA targets in advance (e.g. 2 hours or 2 weeks in advance) for some planned event like a live video streaming show scheduled in some place during some time period.

The Network slicing API allows Operators/CSPs to offer dedicated resources to different tenants (as B2B customers) via the Network slice as a Service. This is a kind of commodity and business monetization opportunities for operators to sell on-demand slice service to third-party tenants.

@jordonezlucena
Copy link
Contributor

@chinaunicomyangfan @Kai-hw @DanXu-ChinaTelecom: The API proposal has been approved in the TSC meeting held in 18th Jan, with some activities for the APIBacklog WG to act upon -- minutes available here.

As for next steps:

  1. [API owner, Supporting companies] Decide on Sub-Project name. Options:
  • Network Slicing Booking
  • Network Slicing Reservation
  1. ** [API backlog chair]** To inform TSC about sub-project name via mail list.
  2. [CAMARA admins] Create the subproject repository, following official nomination from TSC.

@Kai-hw
Copy link

Kai-hw commented Jan 23, 2024

Thanks @jordonezlucena for the information.

For the Sub-Project name, we prefer "Network Slicing Booking".

@jordonezlucena
Copy link
Contributor

The new sub project is available: https://github.com/camaraproject/NetworkSliceBooking
Together with the mailing list: https://lists.camaraproject.org/g/sp-nsb

The issue can be closed. Please, continue work on the new sub-project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants