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

new API proposal Network Slicing API #333

Merged
merged 14 commits into from
Jan 12, 2024
Merged
Show file tree
Hide file tree
Changes from 13 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
| **Field** | Description |
| ---- | ----- |
| 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.|
| Technical viability | This API requires the availability of RAN slicing, UDM, PCF, and network slicing management services as expressed in 3GPP TS 28.531 (network slice provisioning operations), TS 28.541 (Information model definitions for network slice NRM) standards.|
| Commercial viability | Network Slicing has been commercialized in many fields. Static Slicing has helped operators monetized. Dynamic Slicing is on the way of huge potential value. It’s especially valuable in influencer live video stream, new media, power fiber scenario, industry fileds, there already appear many commercial use cases.|
| YAML code available? | No, needs to be provided in yaml. |
| Validated in lab/productive environments? | Yes, in productive network. |
| Validated with real customers? | Yes |
| Validated with operators? | Yes , 3 operators participated in the evaluations. |
| Others | More details can be refered in PPT. |
Binary file not shown.