5G Transport Slice Connectivity Interface
draft-rokui-5g-transport-slice-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Reza Rokui , Shunsuke Homma , Diego Lopez , Xavier de Foy , Luis M. Contreras , Jose A. Ordonez-Lucena , Pedro Martinez-Julia , Mohamed Boucadair , Philip Eardley , Kiran Makhijani , Hannu Flinck | ||
| Last updated | 2020-01-03 (Latest revision 2019-07-02) | ||
| Replaced by | draft-rokui-5g-ietf-network-slice | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-rokui-5g-ietf-network-slice | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The 5G Network slicing is an approach to provide separate independent E2E logical network from user equipment (UE) to applications where each network slice has different SLA requirements. Each E2E network slice consists of multitude of RAN-slice, Core-slice and Transport- slices, each with its own controller. To provide automation, assurance and optimization of the network slices, an E2E network slice controller is needed which interacts with controller in RAN, Core and Transport slices. The interfaces between the E2E network slice controller and RAN and Core controllers are defined in various 3GPP technical specifications. However, 3GPP has not defined the same interface for transport slices. The aim of this document is to provide the clarification of this interface and to provide the information model of this interface for automation, monitoring and optimization of the transport slices.
Authors
Reza Rokui
Shunsuke Homma
Diego Lopez
Xavier de Foy
Luis M. Contreras
Jose A. Ordonez-Lucena
Pedro Martinez-Julia
Mohamed Boucadair
Philip Eardley
Kiran Makhijani
Hannu Flinck
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)