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

Commit 469e66c

Browse files
author
Larry Peterson
committed
final v1.0 fixes
1 parent 2ea24a6 commit 469e66c

File tree

7 files changed

+24
-11
lines changed

7 files changed

+24
-11
lines changed

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
Version 0.3-dev
1+
Version 1.0

disaggregate.rst

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ available servers). The following introduces the basic idea, starting
215215
with the RAN.
216216

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

310+
In summary, the goal of RAN slicing is to programmatically create
311+
virtual RAN nodes (base stations) that operate on the same hardware
312+
and share the spectrum resources according to a given policy for
313+
different applications, services, users, and so on. Tying RAN slicing
314+
back to RAN disaggregation, one can imagine several possible
315+
configurations, depending on the desired level of isolation between
316+
the slices. :numref:`Figure %s <fig-ran-slicing>` shows four examples,
317+
all of which assume slices share the antennas and RF components, which
318+
is effectively the RU: (a) RAN slices share RU, DU, CU-U and CU-C; (b)
319+
RAN slices share RU and DU, but have their own CU-U and CU-C; (c) RAN
320+
slices share RU, CU-U and CU-C, but have their own DU; and (d) RAN
321+
slices share RU, but have their own DU, CU-U and CU-C.
322+
323+
.. _fig-ran-slicing:
324+
.. figure:: figures/Slide40.png
325+
:width: 700px
326+
:align: center
327+
328+
Four possible configurations of a disaggregated RAN in support of
329+
RAN slicing.
330+
310331
Core Slicing
311332
~~~~~~~~~~~~
312333

figures.pptx

1.39 KB
Binary file not shown.

figures/Slide39.png

30.6 KB
Loading

figures/Slide40.png

30.9 KB
Loading

figures/Slide41.png

-33.3 KB
Binary file not shown.

ran.rst

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -341,15 +341,7 @@ also shows the additional O-RAN prescribed interfaces.
341341

342342
.. _fig-disagg:
343343
.. figure:: figures/Slide39.png
344-
:width: 500px
345-
:align: center
346-
347-
.. figure:: figures/Slide40.png
348-
:width: 500px
349-
:align: center
350-
351-
.. figure:: figures/Slide41.png
352-
:width: 500px
344+
:width: 450px
353345
:align: center
354346

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

0 commit comments

Comments
 (0)