00:00:00
[Music]
00:00:17
we will be discussing the Deep dive into
00:00:19
Oran architecture and hopefully you'll
00:00:22
gain a lot more understanding of the
00:00:24
oran
00:00:26
itself yeah so I I've mentioned during
00:00:29
the overview view of the Learning Hub
00:00:31
course no we will cover the oran
00:00:34
architecture and the relevant
00:00:36
specifications particularly the
00:00:39
evolution of the ran and then the cause
00:00:42
of that or the motivation of that is the
00:00:45
dis agregation of the hardware and
00:00:47
software components now because
00:00:49
originally most of the components are
00:00:52
proprietary know they are very uh vendor
00:00:55
specific so if one component needs to be
00:00:58
changed what happens is they have to
00:01:01
also update all the other components um
00:01:04
so motivation is financial aspect
00:01:09
ifos Capital expenses capex then the
00:01:13
operators will also have limited
00:01:16
opportunities to upgrade and of course
00:01:19
that will translate no less coverage for
00:01:23
the subscribers so what they want is
00:01:26
that um move towards open architecture
00:01:30
so that it's easier to interoperate and
00:01:45
update uh commercial of the Shelf
00:01:48
devices L and then inside would be the
00:01:50
software no yeah so this is also taking
00:01:53
advantage of the virtualization
00:01:55
initiative a lot of different systems
00:01:58
since slowly virtualized talaga so it po
00:02:02
also towards that um goal no an okay so
00:02:06
open run on considers not only open
00:02:10
remote radio unit the one that is
00:02:12
nearest the end user this is the one
00:02:16
containing
00:02:19
antennas change analog to digital and
00:02:22
digital to analog conversion and then
00:02:24
the baseband unit no it's the one nearer
00:02:27
to the remote radio unit no but
00:02:31
um so mostly usually they're in the Run
00:02:37
Part no sometimes near the cell site
00:02:40
some
00:02:42
are somewhere else so not only this two
00:02:45
components no interfaces connecting the
00:02:49
components like my interface connecting
00:02:51
these two and other
00:02:55
interfaces
00:02:58
arito components and
00:03:01
interfaces then finally in introduce the
00:03:04
new components of the oran Alliance
00:03:08
so Rick um you near real time Rick and
00:03:12
non-real time Rick and then other
00:03:15
interfaces as well no so valid the
00:03:17
original architecture is from 3gpp and
00:03:21
then it is modified and added no um
00:03:23
components to allow interoperability no
00:03:26
by Oran
00:03:27
Alliance okay so let's uh proceed sigur
00:03:31
to the
00:03:34
topics andur let me skip sang slides
00:03:39
since we only have around 45 minutes no
00:03:43
so this is the review of the different
00:03:45
ran earlier no uh from 2G 3G and then uh
00:03:50
currently at 5G no in Philippines we
00:03:53
have 5G Network already but uh in
00:03:56
limited cities and places no so you can
00:04:03
check
00:04:06
deoy luro let me copy this
00:04:11
link
00:04:17
um let me ano Lang
00:04:20
saglit Copy Co and then I'll share to
00:04:22
you so that you can checkpoint a bit
00:04:28
no
00:04:38
an okay so let me type the
00:04:43
chat yeah so you can um explore this
00:04:46
later and depending on the location that
00:04:50
there are different mobile coverages
00:04:52
like 2G 3G 4G 4G
00:04:54
plus um towards
00:04:57
5G par LTE Advan in Philippines LTE then
00:05:02
5G is new NR new
00:05:09
radio check coverage on the different
00:05:12
roads some have 5G coverage some have 4G
00:05:17
plus and
00:05:19
possibly remote
00:05:21
locations
00:05:23
available so at this one you can see if
00:05:26
in your
00:05:27
place 5G
00:05:30
or in some
00:05:34
provinces
00:05:36
okay Sal sites RS and at different
00:05:42
Generations
00:05:43
names to differentiate them no so in 2G
00:05:47
we have the GSM Edge or Jan so this is
00:05:53
uh involving the base station controller
00:05:55
and base transceiver
00:05:57
station 3G no so originally 2G Focus
00:06:02
text uh digitized call actually May 1
00:06:07
but in Focus
00:06:09
anals and dig and
00:06:13
encryp it's already digiti and
00:06:19
encrytion
00:06:20
conversation and then in 3G we have here
00:06:24
uh
00:06:24
UMTS UMTS is universal um mobile
00:06:30
terrestrial system and then the name of
00:06:33
the ran is utran there is a radio
00:06:35
network controller
00:06:38
and B station isde
00:06:41
bde
00:06:44
B station and then for 4G we have LTE
00:06:49
long-term Evolution and then the ran is
00:06:51
called utran and then the base station
00:06:54
is known as e node B no then next one is
00:06:58
5G no you new radio it is called as 5G
00:07:02
ran and then the base station is called
00:07:04
as G node B so in the architecture later
00:07:07
no you might find discussion e node b g
00:07:11
node B node B and so on so these are the
00:07:15
base stations for various components or
00:07:17
various cellular
00:07:20
Generations names at different
00:07:22
Generations possibly 6G which is planned
00:07:27
to be deployed by 2013 by the 3gpp no
00:07:30
then may different name then Sil no for
00:07:33
the base station there
00:07:35
no okay so an significance we need to
00:07:39
understand this
00:07:41
R why there are changes in our cellular
00:07:46
networks so siguro let me skip ran
00:07:50
architecture
00:07:53
Evolution so the main motivation for
00:07:55
having a ran architecture for the
00:07:57
evolution of the radio access network is
00:08:00
the disaggregation of the system into
00:08:03
smaller systems so originally the the
00:08:06
main par diagram of the the
00:08:10
Telecommunications Network would involve
00:08:12
the core Network it the transport
00:08:17
Network and then the radio Access
00:08:20
Network UE user equipment via radio
00:08:25
frequency so usually in the past
00:08:31
box
00:08:32
or equipment both hardware and software
00:08:35
R specific
00:08:40
software or
00:08:43
hard as a and
00:08:46
then upgrade to another maybe or change
00:08:49
to another
00:08:51
vendor other components would also
00:08:54
change open in the past yeah and and
00:08:59
then eventually no you later you'll
00:09:01
discuss the the different Rands they
00:09:04
change no into par smaller
00:09:10
subsystems Block No but rather there are
00:09:12
smaller blocks inside which we will
00:09:14
discuss later and it was easier
00:09:22
eventually even P hardware and
00:09:25
software yeah so when I say this
00:09:27
aggregation this means separate of the
00:09:29
hardware and software and since discuss
00:09:33
is
00:09:36
openag component so
00:09:40
component that is nearest the end user
00:09:45
okay so you disaggregation of hardware
00:09:48
and software no started not only in ran
00:09:51
it also happened in other systems no due
00:09:54
to of course the the Improvement of the
00:09:57
technology you
00:10:00
Hardware um
00:10:02
previously
00:10:04
computers
00:10:06
servers before but eventually they get
00:10:10
uh more and more powerful and then that
00:10:14
started
00:10:16
virtualization
00:10:18
components okay so let me go to the
00:10:21
different run
00:10:23
architectures so we have here the
00:10:25
traditional red architecture that is uh
00:10:27
called as parang you
00:10:30
non nonsplit type because Bas band unit
00:10:36
radio unit so this is the configuration
00:10:39
in the early stages 2G
00:10:44
3G par cabinet um baseband unit and
00:10:47
radio unit okay so in this uh
00:10:50
traditional base station the signal
00:10:52
processing RF Equipment and the network
00:10:54
access are found here and then there
00:10:57
will be RF cables no from the radio
00:11:02
unit
00:11:05
so of course we know that the antenna
00:11:08
tower is um has a huge
00:11:12
height then there will be a lot of
00:11:15
losses here transmission
00:11:18
line okay so what they did no is to
00:11:21
update this such that the radio unit is
00:11:25
no longer collocated baseband unit Sila
00:11:29
the the base band unit is here and then
00:11:33
the remote radio unit you rru or
00:11:37
sometimes called as remote radio head
00:11:39
are placed now nearer the antenna so
00:11:43
that there will be less loss no s remote
00:11:46
radio unit since this is the one convert
00:11:50
to digital to analog and analog to
00:11:52
digital so ready for
00:11:54
propagation Ayan
00:11:57
so Sila meron interface front hall
00:12:03
interface and
00:12:05
thenon CP interface so CPR interface is
00:12:10
the front hole interface proprietary
00:12:14
base Bond end Ru so
00:12:18
components remote radio unit near the
00:12:22
antenna connecting to the baseband unit
00:12:25
via the CPR one of the front hle now
00:12:30
interfaces yeah okay so this BBU can
00:12:34
also be connected to other R
00:12:39
areuse doesn't need to just um support
00:12:43
one base station base station uh near as
00:12:48
well
00:12:49
no so Ru is move closer to the antenna
00:12:52
to minimize signal loss and frle so
00:12:57
traditional r
00:13:01
okay so uh these are the two types as
00:13:03
mentioned in the previous slide
00:13:07
nonsplit
00:13:09
cabinet then split
00:13:13
architecture BBU and
00:13:17
rru front hole interface called as
00:13:22
CPR then of course the ran no is
00:13:25
connected to the back to the core
00:13:27
network via a back hole interface or
00:13:31
cable discussed Richard earlier fiber
00:13:35
microwave or even satellite
00:13:39
no another name for traditional run is
00:13:42
also known as classical run or
00:13:43
distributed
00:13:47
run okay next one is the centralized run
00:13:50
so in the centralized run no somehow
00:13:53
this also known as Cloud run because all
00:13:55
the baseband unit
00:13:57
since Ru and BBU all the baseband unit
00:14:01
can just be pulled near the central
00:14:04
office
00:14:10
processing so the base band units are
00:14:14
all near the um in the central office
00:14:18
and
00:14:20
then remote radio units from the central
00:14:23
office and
00:14:27
thenation use front hle connections via
00:14:31
Optical distribution
00:14:33
Network fi
00:14:36
connections locations no so maganda is
00:14:40
it showed that you can pull all the
00:14:42
resources in one in one area and then
00:14:46
control all the
00:14:48
other C
00:14:50
sides but in this model no it's not yet
00:14:54
uh solving the problem of vendor lock in
00:14:57
wherein if you modify or if if you
00:14:58
upgrade if you
00:15:00
change components or some of or the
00:15:04
interfaces then you need to follow still
00:15:07
system
00:15:09
vendor so centralized r or Cloud
00:15:13
R okay then another par version of the
00:15:17
ran is the ran architecture is the
00:15:19
virtualized ran or also known as virtual
00:15:22
ran wherein the bbus can still be pulled
00:15:27
no and placed somewhere else and then is
00:15:31
the bbus are CS Hardware running on
00:15:34
proprietary software with virtualized
00:15:36
network functions so virtualized
00:15:40
functions BBU so they're not necessarily
00:15:43
just one
00:15:44
product but
00:15:47
rather
00:15:49
server mobile network operator and
00:15:57
then
00:15:59
is just reset that BBU without affecting
00:16:02
all the other baseb
00:16:11
units sh to the
00:16:13
other if
00:16:17
operation this started
00:16:22
disagre functions software Hardware
00:16:25
component and limited to just the
00:16:29
baseband unit Hardware C
00:16:32
server an so open run because the front
00:16:37
hle interface connecting this baseband
00:16:40
unit and Ru is still proprietary so
00:16:45
proprietary
00:16:46
software
00:16:49
eventually comp different Generations I
00:16:53
different architectures this D
00:16:56
distributed run or traditional run
00:16:59
cloud or centralized run virtualized or
00:17:02
virtual run and then it open run so uh
00:17:06
what happens is um we have here the
00:17:09
front hole interface no connecting uh
00:17:12
the DU and the room radio unit
00:17:16
then but difference n is that this front
00:17:20
hole interface is also
00:17:23
open they follow proprietary just for
00:17:27
one V
00:17:29
specifications physical and
00:17:32
specifications front hole
00:17:35
interface yeah so to summarize the
00:17:37
architecture Evolution originally
00:17:40
traditional ran has this two types
00:17:43
non-split and split all of the
00:17:46
components are
00:17:47
proprietary centralized run G then all
00:17:50
components are proprietary but uh what
00:17:53
happens is the base band units are
00:17:56
centralized or pulled together in a
00:17:58
different
00:18:00
location efficient manage different
00:18:03
sides virtualized run wherein you now
00:18:07
introduce cots server to allow
00:18:11
virtualized Network functions and then
00:18:14
open run is that we now have the
00:18:18
components into a c based hardware and
00:18:21
then the functions are virtualized and
00:18:24
then there's now an open interface no
00:18:27
and so later they
00:18:29
specifically components under like radio
00:18:33
unit distributed unit and centralized
00:18:36
unit then open
00:18:41
depending maybe the mobile network
00:18:43
operator wants to deploy uh this two the
00:18:47
ru and du nearer the antennas
00:18:52
or anten site
00:18:55
or like small cell
00:19:00
so where they are located that's also
00:19:04
defined by 3gpp as the functional
00:19:08
split okay so this is also no the
00:19:11
summary of the architecture Evolution uh
00:19:13
we have the in the traditional R all the
00:19:17
components are
00:19:18
proprietary the rru the base band unit
00:19:23
and the front hall then for centralized
00:19:26
runat proprietary
00:19:28
update no which is you BBU pooling and
00:19:32
then distribution Network in front hall
00:19:35
no virtualized run all again
00:19:39
proprietary so proprietary is Hardware
00:19:43
baseband unit then finally so open run
00:19:47
all the hardware and the interface are
00:19:49
open no so Hardware Ru Hardware BBU and
00:19:54
then front Hole uh open then no so you
00:19:58
software okay proprietary since
00:20:01
operation main
00:20:03
motivation R Evolution
00:20:10
iser V so as long as all of them can
00:20:14
operate uh physically connect to each
00:20:17
other then it's okay to have a
00:20:19
proprietary software okay but
00:20:21
essentially open run Hardware including
00:20:24
your
00:20:25
interfaces they should be open or
00:20:29
commercial of the
00:20:31
shelf so motivation architecture
00:20:38
Evolution okay and then now let's
00:20:44
proceed important very very important
00:20:47
part course which is about the
00:20:50
architecture of Oran
00:20:53
itself okay so we already know that uh
00:20:56
radio access n Network or ran is here
00:21:01
color red no this access network is the
00:21:04
one connecting our end user or the user
00:21:07
equipment no to the Telco system no via
00:21:12
radio frequency so the access network or
00:21:15
the radio Access Network connects to the
00:21:17
core network via the transport Network
00:21:20
or also known as the back
00:21:22
hole okay so an po main run
00:21:27
components
00:21:29
Network main components the base band
00:21:32
unit and the remote radio unit and
00:21:36
earlier we already show
00:21:42
thatu
00:21:44
interface
00:21:49
Backle remote radio
00:21:53
unit okay so uh naita in the previous
00:21:57
course
00:21:59
you different interfaces and different
00:22:02
components no this is one way of viewing
00:22:05
it no so we have the core Network
00:22:08
involving uh various the high
00:22:10
performance devices and this is not
00:22:13
covered in our course since main focus
00:22:16
is the r this part near nearer the user
00:22:20
equipment okay so the core Network
00:22:22
connects to the Rand via the back hole
00:22:26
and then inside the Rand we be different
00:22:28
components no thewa would be the remote
00:22:31
radio unit and the baseband unit and in
00:22:35
the course you'll also learn functions
00:22:38
remote radio unit
00:22:41
like is it focus on analog to digital
00:22:44
conversion or digital to analog
00:22:46
conversion physical layer uh protocols
00:22:49
and so on okay and then uh we already
00:22:52
know that our Ru and BBU are connected
00:22:54
via front hall and then later
00:23:06
functions further into du and CU or
00:23:10
distributed unit and centralized
00:23:14
unit mid
00:23:16
hle interface main interface front hole
00:23:20
mid hole and back hole connecting you
00:23:23
rru du CU and the core
00:23:26
Network yeah so
00:23:33
later
00:23:36
functionalit Network
00:23:43
operators flexible deployment
00:23:48
scenario maybe on the on the
00:23:51
particular service
00:23:54
area run so they can just put in the
00:23:57
remote radio unit near the the service
00:24:00
area and then the ducu may be just in
00:24:04
their uh central
00:24:07
office
00:24:14
usually
00:24:22
that
00:24:24
fix in one location or but Lu device or
00:24:29
something like
00:24:32
that front hole or FH FH MH s
00:24:40
BH Yan so P sa they introduced more
00:24:47
components
00:24:50
C Oran centralized unit Oran distributed
00:24:56
unit Oran
00:24:58
uh radio unit or remote radio unit
00:25:04
so overview of the
00:25:10
arit so
00:25:14
in is FH front call so
00:25:18
in prefix o to mean it's now open front
00:25:24
hall in the discussion Po in this course
00:25:26
May faces the front hole and then some
00:25:30
are not open so specify but open front
00:25:35
hole for Oran
00:25:37
architecture and then
00:25:40
CU and then it's composed of the control
00:25:43
plane and user
00:25:46
planear
00:25:48
processing
00:25:49
overhead is focus data of the user so
00:25:54
main centralized unit and then the mid
00:25:58
hole interfaces interface again is
00:26:01
connecting the CU and du this one is
00:26:04
what we call the F1 interface no defined
00:26:07
by
00:26:09
3gpp front
00:26:12
hole mid hole no mid hole is
00:26:16
F1 name talaga mid hole is the generic
00:26:19
term no F1 is specific
00:26:23
interface and then uh connecting this cu
00:26:30
um core Network would be the
00:26:33
Backle
00:26:36
architecture Smo sorry Smo and near real
00:26:41
time r
00:26:42
i purpose is for
00:26:47
optimization
00:26:49
especially components and they need to
00:26:51
monitor
00:26:53
manage and it's easier to manage if
00:26:56
other component
00:26:58
to to monitor their operations no yeah
00:27:01
so C Smo or system management and
00:27:04
orchestration this is responsible for
00:27:07
the Rand domain management and then
00:27:09
inside it P non-real time
00:27:14
RC so discuss later and also emphasize
00:27:19
next
00:27:20
course over viw next week yeah so nrt or
00:27:25
near real time RC it supports task that
00:27:29
require less than one second latency so
00:27:33
task requirement
00:27:36
run operations like for
00:27:41
example channels and so on anything that
00:27:45
needs almost real time the
00:27:48
response
00:27:49
process this near real time R can also
00:27:52
connect to other nodes Noz this is just
00:27:56
one node no
00:27:58
parang one base station mer ibang base
00:28:02
station
00:28:04
a PO May question at no maybe you can
00:28:08
chat po so that I can read Po in a
00:28:11
bit and then um what
00:28:16
else okay Soo we can
00:28:19
go
00:28:21
architecture po architecture without uh
00:28:25
interfaces soang earlier
00:28:28
c
00:28:34
r so still Ru and du is connected by the
00:28:38
front hole
00:28:40
interface
00:28:43
centralized control plane user
00:28:47
plane
00:28:49
functions and then this CU connects to
00:28:53
the DU via the mid hle interface yeah so
00:28:59
other
00:29:03
parts this is also what the oran
00:29:06
Alliance use
00:29:11
consistent okay so my Oran Cloud
00:29:14
infrastructure as well not part of the
00:29:17
oran itself or the ran itself
00:29:20
but Cloud native virtualized
00:29:25
functions so po
00:29:28
important slide course this is the oran
00:29:35
architecture
00:29:37
immediately components and
00:29:40
interfaces and actually assignment do a
00:29:44
course um to draw this architecture and
00:29:48
then explain bat parts so that
00:29:53
familiarize Learners and also my reten
00:29:57
if we hand write the the content an so
00:30:01
siman UL Ru no so Ru radio unit again o
00:30:07
here just
00:30:09
specifies
00:30:10
architecture Ru and du distributed unit
00:30:15
is connected by the front hole interface
00:30:18
no open front hole
00:30:23
interface
00:30:25
planes Lang
00:30:28
um parang M plane management plane s
00:30:32
control user and synchronization plane
00:30:35
but essentially
00:30:38
front notice
00:30:43
interfaces
00:30:45
Legend gray those are defined by
00:30:49
3gpp soal architecture before r
00:30:56
buty or no so so that we can incorporate
00:31:00
you other functions other nodes
00:31:04
introduced okay and then uh we know the
00:31:07
DU is connected to the CU and in this
00:31:10
case you CU has two parts because of
00:31:14
May control plane and user plane so mid
00:31:19
hole interface is the F1
00:31:21
no Maya F1 Lang Isa Kasi control Isa
00:31:26
Naman user
00:31:28
an so b r talaga c d
00:31:32
Ru but as mentioned
00:31:38
earlier Network
00:31:42
function by understanding the whole
00:31:45
network including other
00:31:47
nodes near real time r i
00:31:51
so
00:31:54
different different uh task
00:31:57
perform task near real time RC is
00:32:00
anything almost real time less than one
00:32:03
second optimize
00:32:05
operation okay and then uh notice near
00:32:08
real time RC has an interface called E2
00:32:12
E2 is the interface connecting to the
00:32:15
ran no so
00:32:18
CU sa
00:32:23
du
00:32:25
then it
00:32:27
send
00:32:29
updates virtualized functions updates
00:32:32
from time to time if for example maybe
00:32:35
one of the virtualized functions goes
00:32:38
down then P optimize for load balancing
00:32:41
and so on
00:32:44
so
00:32:47
software proprietary software that can
00:32:50
help
00:32:53
optim machine learning aspect to
00:32:57
optimize and
00:32:58
maybe other um applications pa okay and
00:33:03
then no remember e node B Yan po base
00:33:08
station para 4G so
00:33:12
P near real time R to other nodes
00:33:17
so or this is just one node one one base
00:33:23
station Bas
00:33:25
station
00:33:29
so you can connect as well the near real
00:33:31
time RC can also get data from other
00:33:33
nodes via the E2
00:33:36
interface part Oran EOD B contains as
00:33:40
well inside or the CU D and
00:33:44
Ru an so interfaces no so meron then as
00:33:48
well E1 this is just uh the interface
00:33:52
connecting the control plane and the um
00:33:54
user plane and then
00:33:57
X2
00:34:02
NG slid but these are the connections as
00:34:05
well to
00:34:07
other other
00:34:09
nodes okay and then uh what else No you
00:34:12
new real time RC is real time late task
00:34:18
less than one second but nonre time
00:34:23
R
00:34:25
task longer time para
00:34:32
complete so Focus
00:34:43
you okay so you the non-real time RC are
00:34:47
task that require more than one second
00:34:50
for example if you need to uh have
00:34:52
traffic forecasting no or par user
00:34:56
manage
00:34:57
or
00:34:59
anything predict or something
00:35:03
elseas
00:35:05
so data or other important
00:35:08
analytics near real time R via A1
00:35:14
interface interface to show the
00:35:17
connections
00:35:20
and
00:35:23
relationships then service management
00:35:25
and orchestration
00:35:30
um connections like1
00:35:33
plane other nodes and then O2 plane Oak
00:35:39
Cloud
00:35:41
functions and so on okay
00:35:45
so
00:35:46
before color red orange these are the
00:35:51
components of the traditional ran and
00:35:53
the other
00:35:54
rans but when we go
00:35:58
to new new interfaces and new
00:36:03
components purpose is to optimize and
00:36:08
also
00:36:09
um further virtualized
00:36:14
functions impr performance improve
00:36:18
traffic improve user
00:36:21
experience an so uh you can visit
00:36:25
no uh
00:36:27
Oran architecture let me send the link s
00:36:31
chat s Lang
00:36:37
po copy Kang po y
00:36:55
link
00:37:03
okay so s link
00:37:12
architecture initial look components but
00:37:15
essentially no you can separate them
00:37:18
into different
00:37:20
parts yeah okay so May 10 minutes of let
00:37:25
me go into other details about the
00:37:28
architecture an so another way of
00:37:31
looking at the architecture this is what
00:37:34
we call the alliance reference
00:37:38
architecture reference
00:37:42
arit how it is
00:37:46
related color coordination
00:37:49
same non-real time R near real time R
00:37:54
connected by A1
00:37:57
r i r connects to the CU and du so CU
00:38:03
may contain multiple radio access
00:38:06
technology
00:38:07
multiat so it just means though it's not
00:38:11
just 5G you can also have 4G or 3G no
00:38:15
originally the oran system is focused s
00:38:19
on 5G but eventually they were able to
00:38:21
do something even for 4G and
00:38:25
3G prot calls or Generations um open
00:38:29
then
00:38:30
no okay and then um we have the
00:38:34
distributed unit connecting to the CU so
00:38:38
CU to Du is the mid hole another name
00:38:42
for the mid hole interface is F1 this is
00:38:45
the this is specified no by our by our
00:38:49
um 3G PP no and then the front hole
00:38:53
interface connects the DU and the
00:38:55
ru
00:38:59
deta reference architecture inside the
00:39:04
Smo design inventory policy
00:39:07
configuration and so
00:39:09
on
00:39:11
longterm
00:39:13
operation
00:39:16
then near real time R mostly focusing on
00:39:20
task resolve like radio management
00:39:24
Mobility management quality of service
00:39:27
interference and so on
00:39:31
possibly nonre time
00:39:34
R for creation of machine learning
00:39:37
models no and then those machine
00:39:39
learning models may be um um updated
00:39:43
near real time
00:39:44
R trained model is coming from the
00:39:48
non-real time
00:39:53
R optimize andage
00:39:57
du and
00:39:59
CU and then
00:40:02
CU control plane and uh user plane no
00:40:07
connected by
00:40:08
E1 and then are protocols no
00:40:18
later notice E2 connects the near real
00:40:22
time r s CU and on
00:40:27
and then uh F1 is the mid hole
00:40:32
interface um C or CS
00:40:36
platform and then du is uh the one
00:40:40
performing usually this protocols RLC
00:40:44
Mac physical higher higher physical
00:40:46
layer much
00:40:49
later but essentially you R has
00:40:53
different protocols that they need to
00:40:55
perform
00:41:00
and due to the
00:41:11
functional use Case mobile network
00:41:16
operator assment
00:41:18
actually Learners they draw this no at
00:41:22
the start um probably they don't
00:41:25
understand a lot of the details no but
00:41:28
eventually because they will draw them
00:41:30
and try to understand each connection
00:41:33
must
00:41:35
absor architecture this way so important
00:41:40
part course would be this slide and
00:41:44
then Oran architecture
00:41:48
earlier slide showing the 3gpp nodes
00:41:53
3gpp interface Oran interface
00:41:57
face color green and or Oran nodes like
00:42:05
ricko
00:42:08
BPP
00:42:10
Palanga
00:42:13
PA the the nodes are not yet open more
00:42:17
likely they follow the proprietary
00:42:19
version no an and then siguro let me
00:42:24
discuss some of the working groups no C
00:42:26
Oran Alliance include some working
00:42:29
groups they are in charge
00:42:33
of different parts of the or
00:42:36
architecture like working group one use
00:42:39
cases and overall
00:42:41
architecture then we have working group
00:42:43
two they only focus on the non-real time
00:42:46
R A1
00:42:49
interface reference architecture you A1
00:42:54
interface or you uh sorry architecture
00:42:57
Pala No A1 interface is this interface
00:43:01
here no connecting the two
00:43:04
Ricks
00:43:07
so prepare
00:43:12
specifications um details on this is
00:43:15
from working group
00:43:17
two Focus working group three is more on
00:43:22
near realtime r i and E2 interfaces
00:43:25
remember e two interfaces is interface
00:43:28
connecting near real time R
00:43:33
CU an so
00:43:36
part so near real time RSC E2
00:43:41
interface
00:43:43
CU
00:43:45
du and as well as other nodes PA no CU
00:43:49
du other
00:43:54
noage Grand May RS
00:43:58
manage and then other working groups no
00:44:01
like working group four open front hall
00:44:05
working group five other interfaces like
00:44:09
it mid Hall and so on
00:44:13
no okay these are other working groups
00:44:16
but not much
00:44:18
Focus Oran may it is for
00:44:22
orchestration um and so on so
00:44:26
important for this architecture would be
00:44:29
this first five no working
00:44:33
groups okay so to summarize let me use
00:44:38
this
00:44:39
slide discussion so originally no we
00:44:43
know that we have BBU and Ru split
00:44:47
architecture traditional run May front
00:44:51
hle
00:44:52
interface so front hle interface one of
00:44:55
them is you
00:45:04
C changes
00:45:08
Network modifi mobile network operator
00:45:10
according use case particular service
00:45:14
area they can only accommodate Ru no and
00:45:18
then eventually they have this uh 3gpp
00:45:21
approach now specified in the technical
00:45:25
report
00:45:27
38.81 where in the BBU base band
00:45:31
unit further functions into into CU and
00:45:36
du no you centralized unit and
00:45:39
distributed unit they have a mid hle
00:45:42
interface
00:45:44
here so this mid hle interface is you F1
00:45:51
interface techic report
00:45:54
funs vary depending on
00:45:59
split appliations or
00:46:12
function Hardware mobile network
00:46:16
operator perform so maybe it will only
00:46:20
perform a certain portion
00:46:23
so critical par important information or
00:46:28
architecture
00:46:30
andita the the reasoning behind having
00:46:32
this
00:46:34
[Music]
00:46:41
one
