-
Notifications
You must be signed in to change notification settings - Fork 60
New Proposal-Network Slicing API #317
Comments
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! |
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? |
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 |
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
…________________________________
杨帆
中国联通智网创新中心-网络中台产品部
18610102235
***@***.***
发件人: Jose ***@***.***>
发送时间: 2023-10-26 21:51
收件人: ***@***.***>
抄送: ***@***.***>; ***@***.***>
主题: [警惕!外部邮件]Re: [camaraproject/WorkingGroups] New Proposal-Network Slicing API (Issue #317)
PR-#316<url>
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?
—
Reply to this email directly, view it on GitHub<#317 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7EAU7UXQ4DS2ISSVA2ZHY3YBJTGVAVCNFSM6AAAAAA5KQPJBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGE3TCMZTHE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 ***@***.***,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to ***@***.*** ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.
|
I commented in the PR conversation |
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. |
Thank you @FabrizioMoggio , I just saw your comment here. 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. |
@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:
|
Thanks @jordonezlucena for the information. For the Sub-Project name, we prefer "Network Slicing Booking". |
The new sub project is available: https://github.com/camaraproject/NetworkSliceBooking The issue can be closed. Please, continue work on the new sub-project. |
PR-https://github.com/camaraproject/WorkingGroups/pull/316
The text was updated successfully, but these errors were encountered: