Merged
Conversation
Closed
chinaunicomyangfan
approved these changes
May 7, 2024
Collaborator
chinaunicomyangfan
left a comment
There was a problem hiding this comment.
Look goot to me
tlohmar
reviewed
May 7, 2024
| | API family name | Network Slicing API | | ||
| | API family owner | China Unicom, China Telecom, Huawei | | ||
| | API family supporter | China Mobile, China Unicom, China Telecom, Huawei, TBD | | ||
| | API summary | There are emerging requirements in high-rate time-critical applications in the areas of Cloud-gaming, AR/VR, Live Video Streaming, Real-time Multi-Media etc through mobile networks. The on-demand network slicing service technology can provide a network slice reservation method for such scenarios to meet the SLA assurance expected by developers for a specific time period and a dedicated service area. The Network Slicing API provides such abilities for developers to reserve, dynamically provisioning, query, dynamically destroy a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. <br /> <br /> Proposed API Definitions <br /> -Input Parameters:<br />Service Time：Start Time ~ End Time<br />Service Area：Geographical area (Point, Line, Area)<br />Guaranteed terminals：Number of terminals<br />SLA Targets：SLA KPIs (such as DL/UL Avg Throughput, Latency) <br /> <br /> -Output Parameters:<br />Slice Reservation Result： network slice reservation success (with Slice ID) or failure. <br /> <br /> An example: a developer may use this API to book a network slice with expected service time, expected service area, expected guaranteed numbers of terminals and expected SLA targets for 2 hours to 2 weeks in advance for some scheduled events like a live stream festival scheduled in some place.| |
Collaborator
There was a problem hiding this comment.
on-demand network slicing service: We should avoid the slogan "on-demand" here to avoid confusion with QOD..
| | API family name | Network Slicing API | | ||
| | API family owner | China Unicom, China Telecom, Huawei | | ||
| | API family supporter | China Mobile, China Unicom, China Telecom, Huawei, TBD | | ||
| | API summary | There are emerging requirements in high-rate time-critical applications in the areas of Cloud-gaming, AR/VR, Live Video Streaming, Real-time Multi-Media etc through mobile networks. The on-demand network slicing service technology can provide a network slice reservation method for such scenarios to meet the SLA assurance expected by developers for a specific time period and a dedicated service area. The Network Slicing API provides such abilities for developers to reserve, dynamically provisioning, query, dynamically destroy a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. <br /> <br /> Proposed API Definitions <br /> -Input Parameters:<br />Service Time：Start Time ~ End Time<br />Service Area：Geographical area (Point, Line, Area)<br />Guaranteed terminals：Number of terminals<br />SLA Targets：SLA KPIs (such as DL/UL Avg Throughput, Latency) <br /> <br /> -Output Parameters:<br />Slice Reservation Result： network slice reservation success (with Slice ID) or failure. <br /> <br /> An example: a developer may use this API to book a network slice with expected service time, expected service area, expected guaranteed numbers of terminals and expected SLA targets for 2 hours to 2 weeks in advance for some scheduled events like a live stream festival scheduled in some place.| |
Collaborator
There was a problem hiding this comment.
SLA assurance expected by developers: This SLA will not only cover the time period and the service area. The commitment should also include the provided service quality.
| | API family name | Network Slicing API | | ||
| | API family owner | China Unicom, China Telecom, Huawei | | ||
| | API family supporter | China Mobile, China Unicom, China Telecom, Huawei, TBD | | ||
| | API summary | There are emerging requirements in high-rate time-critical applications in the areas of Cloud-gaming, AR/VR, Live Video Streaming, Real-time Multi-Media etc through mobile networks. The on-demand network slicing service technology can provide a network slice reservation method for such scenarios to meet the SLA assurance expected by developers for a specific time period and a dedicated service area. The Network Slicing API provides such abilities for developers to reserve, dynamically provisioning, query, dynamically destroy a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. <br /> <br /> Proposed API Definitions <br /> -Input Parameters:<br />Service Time：Start Time ~ End Time<br />Service Area：Geographical area (Point, Line, Area)<br />Guaranteed terminals：Number of terminals<br />SLA Targets：SLA KPIs (such as DL/UL Avg Throughput, Latency) <br /> <br /> -Output Parameters:<br />Slice Reservation Result： network slice reservation success (with Slice ID) or failure. <br /> <br /> An example: a developer may use this API to book a network slice with expected service time, expected service area, expected guaranteed numbers of terminals and expected SLA targets for 2 hours to 2 weeks in advance for some scheduled events like a live stream festival scheduled in some place.| |
Collaborator
There was a problem hiding this comment.
Guaranteed terminals：Number of terminals: At time of booking, only an approximate number of terminals may be known.
| | API family name | Network Slicing API | | ||
| | API family owner | China Unicom, China Telecom, Huawei | | ||
| | API family supporter | China Mobile, China Unicom, China Telecom, Huawei, TBD | | ||
| | API summary | There are emerging requirements in high-rate time-critical applications in the areas of Cloud-gaming, AR/VR, Live Video Streaming, Real-time Multi-Media etc through mobile networks. The on-demand network slicing service technology can provide a network slice reservation method for such scenarios to meet the SLA assurance expected by developers for a specific time period and a dedicated service area. The Network Slicing API provides such abilities for developers to reserve, dynamically provisioning, query, dynamically destroy a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. <br /> <br /> Proposed API Definitions <br /> -Input Parameters:<br />Service Time：Start Time ~ End Time<br />Service Area：Geographical area (Point, Line, Area)<br />Guaranteed terminals：Number of terminals<br />SLA Targets：SLA KPIs (such as DL/UL Avg Throughput, Latency) <br /> <br /> -Output Parameters:<br />Slice Reservation Result： network slice reservation success (with Slice ID) or failure. <br /> <br /> An example: a developer may use this API to book a network slice with expected service time, expected service area, expected guaranteed numbers of terminals and expected SLA targets for 2 hours to 2 weeks in advance for some scheduled events like a live stream festival scheduled in some place.| |
Collaborator
There was a problem hiding this comment.
SLA Targets: Suggestion, include the intended service area and time period onto the SLA Target. The provided service is only available during the time period and at the service area.
| | API family name | Network Slicing API | | ||
| | API family owner | China Unicom, China Telecom, Huawei | | ||
| | API family supporter | China Mobile, China Unicom, China Telecom, Huawei, TBD | | ||
| | API summary | There are emerging requirements in high-rate time-critical applications in the areas of Cloud-gaming, AR/VR, Live Video Streaming, Real-time Multi-Media etc through mobile networks. The on-demand network slicing service technology can provide a network slice reservation method for such scenarios to meet the SLA assurance expected by developers for a specific time period and a dedicated service area. The Network Slicing API provides such abilities for developers to reserve, dynamically provisioning, query, dynamically destroy a slice with customized SLA assurance capabilities, customized service duration, expected slice covered locations and so on. <br /> <br /> Proposed API Definitions <br /> -Input Parameters:<br />Service Time：Start Time ~ End Time<br />Service Area：Geographical area (Point, Line, Area)<br />Guaranteed terminals：Number of terminals<br />SLA Targets：SLA KPIs (such as DL/UL Avg Throughput, Latency) <br /> <br /> -Output Parameters:<br />Slice Reservation Result： network slice reservation success (with Slice ID) or failure. <br /> <br /> An example: a developer may use this API to book a network slice with expected service time, expected service area, expected guaranteed numbers of terminals and expected SLA targets for 2 hours to 2 weeks in advance for some scheduled events like a live stream festival scheduled in some place.| |
Collaborator
There was a problem hiding this comment.
a developer: Suggestion, only consider the API user / API consumer. The developers will only use the APIs during testing.
|
|
||
| **API End Users:** | ||
|
|
||
| OTT Customers Eg: Tiktok Influencer Studios |
Collaborator
There was a problem hiding this comment.
OTT Customers: Suggestion to rename to 'Tiktok Customer'.
| **API End Users:** | ||
|
|
||
| OTT Customers Eg: Tiktok Influencer Studios | ||
| 1. Influencers Companies or Studios may order "Dedicate/Premium Streaming Service" provided by Tiktok. |
Collaborator
There was a problem hiding this comment.
order: suggestion to replacer 'order' with 'book'
|
|
||
| **API Consumers:** | ||
|
|
||
| Enterprises Developer. Eg: TV Station Developer |
Collaborator
There was a problem hiding this comment.
TV Station Developer: Suggestion to replace with "TV Station" or "News Company". They are likely NOT doing developments around the API.
|
|
||
| Enterprises Developer. Eg: TV Station Developer | ||
| 1. TV Stations usually have grand TV Live Streaming Business. They need Slice Assurance Services to assure that they have dedicated network resources for their streaming. | ||
| 2. TV Stations APP developer call Slice Assurance Services provided by Telecom NaaS Platform/Aggregator Platform directly. And developer make it "Streaming Assurance" function on the APP. |
Collaborator
There was a problem hiding this comment.
TV Stations APP developer: "The Program Director of the TV Station will trigger the call for .."
| **API End Users:** | ||
|
|
||
| Enterprise. Eg: TV Station | ||
| 1. Live Video Streaming Team One have a Live Streaming Task. Team One order the "Streaming Assurance" Service on TV Stations APP. |
Collaborator
There was a problem hiding this comment.
Team One order the "Streaming Assurance" Service on TV Stations APP. suggested rewording: 'The TV producers book the "Streaming Assurance" Services for their TV production teams'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
add user story
Add one of the following kinds:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.