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

Commit

Permalink
final v1.0 fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
Larry Peterson committed May 30, 2020
1 parent 2ea24a6 commit 469e66c
Show file tree
Hide file tree
Showing 7 changed files with 24 additions and 11 deletions.
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
Version 0.3-dev
Version 1.0
23 changes: 22 additions & 1 deletion disaggregate.rst
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ available servers). The following introduces the basic idea, starting
with the RAN.

But before getting into the details, we note that a network slice is a
generalization of the QoS Class Index (QCI) discussed earlier. 3GPP
realization of the QoS Class Index (QCI) discussed earlier. 3GPP
specifies a standard set of network slices, called *Standardized Slice
Type (SST)* values. For example, SST 1 corresponds to mobile broadband,
SST 2 corresponds to Ultra-Reliable Low Latency Communications, SST 3
Expand Down Expand Up @@ -307,6 +307,27 @@ the underlying system, as they have historically been in 4G’s eNodeBs.
Centralized near-realtime control applications
cooperating with distribute real-time RAN schedulers.

In summary, the goal of RAN slicing is to programmatically create
virtual RAN nodes (base stations) that operate on the same hardware
and share the spectrum resources according to a given policy for
different applications, services, users, and so on. Tying RAN slicing
back to RAN disaggregation, one can imagine several possible
configurations, depending on the desired level of isolation between
the slices. :numref:`Figure %s <fig-ran-slicing>` shows four examples,
all of which assume slices share the antennas and RF components, which
is effectively the RU: (a) RAN slices share RU, DU, CU-U and CU-C; (b)
RAN slices share RU and DU, but have their own CU-U and CU-C; (c) RAN
slices share RU, CU-U and CU-C, but have their own DU; and (d) RAN
slices share RU, but have their own DU, CU-U and CU-C.

.. _fig-ran-slicing:
.. figure:: figures/Slide40.png
:width: 700px
:align: center

Four possible configurations of a disaggregated RAN in support of
RAN slicing.

Core Slicing
~~~~~~~~~~~~

Expand Down
Binary file modified figures.pptx
Binary file not shown.
Binary file modified figures/Slide39.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified figures/Slide40.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed figures/Slide41.png
Binary file not shown.
10 changes: 1 addition & 9 deletions ran.rst
Original file line number Diff line number Diff line change
Expand Up @@ -341,15 +341,7 @@ also shows the additional O-RAN prescribed interfaces.

.. _fig-disagg:
.. figure:: figures/Slide39.png
:width: 500px
:align: center

.. figure:: figures/Slide40.png
:width: 500px
:align: center

.. figure:: figures/Slide41.png
:width: 500px
:width: 450px
:align: center

Three tiers of RAN disaggregation: (a) horizontal, (b) vertical
Expand Down

0 comments on commit 469e66c

Please sign in to comment.