Тёмный

A tutorial on O RAN and Open RAN 

Institute for the Wireless Internet of Things
Подписаться 1 тыс.
Просмотров 18 тыс.
50% 1

Rajarajan Sivaraj will describe the foundational principles of the O-RAN architecture, with details on interfaces, components, and standardization activities.

Опубликовано:

 

1 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 11   
@ashwanisharma8903
@ashwanisharma8903 6 месяцев назад
Excellent presentation Mr. Sivaraj. Proud of you.
@MrQwertymnb
@MrQwertymnb Год назад
Excellent presentation. Thank you.
@muhammadyousaf5844
@muhammadyousaf5844 Год назад
v good info
@stevencrutchley
@stevencrutchley 11 месяцев назад
Hey everyone. I'm relatively new to the world of 5G and just wanted to ask what might seem like a dumb question... but what is an "interface" in this context? It's obviously not an interface in the sense of an ethernet interface or anything like that. But the terms E1 and F1 are a little confusing. When he says that the E1 interface exists between The O-CU-CP and the O-CU-UP - what is this? Are there literal bits on a wire between two components like a hello packet or an BGP update? Or is it more abstract? Is it like a common format of communication between these components? e.g. each side agrees to communicate using a particular format so that they can understand each other? If so, what form does this "format" take - is it similar to the format of an ethernet frame where the headers are expected at certain byte counts and then interpreted as such. Or is it like a higher layer protocol involving updates of a particular type to be commonly agreed upon and interpreted by either side? Sorry I'm hoping these questions make sense. I very much come from the "OSI model, layers 1-7, bits on a wire with an IGP running over it" kind of world, and making the pivot to 5G is proving challenging. Great video though :)
@cresirj6238
@cresirj6238 4 месяца назад
It is a functional interface - logical in nature. APIs between two functions. This API can also be realized on a physical ethernet link
@ndiayemohamadou5765
@ndiayemohamadou5765 Год назад
good presentation
@MrMahoark
@MrMahoark Год назад
in vRAN, F1 and E1 are still standardised by 3gpp, so why do you say they are proprietary?
@cresirj6238
@cresirj6238 Год назад
Yes, they are standardized, but due to lack of implementing them as open interfaces without the necessity of having multi-vendor inter-operability between the CU-CP and CU-UP, and between CU-CP and DU in legacy products, there could be proprietary closed implementations of the F1/E1 interfaces, unless they talk to other vendors, which is the point of opening them up (which O-RAN focuses on)
@Rajeshnaik-q1y
@Rajeshnaik-q1y Год назад
Nice presentation
@ndiayemohamadou5765
@ndiayemohamadou5765 Год назад
can we have the presentation slide?
Далее
Open RAN in Colosseum
49:16
Просмотров 2,1 тыс.
Iran launches wave of missiles at Israel
00:43
Просмотров 556 тыс.
Tech Unveiled S1E1: The four components of Cloud RAN
12:28
RAN Functional Splits 101
12:59
Просмотров 15 тыс.
Introduction to Open RAN
37:53
Просмотров 3,9 тыс.
Zero Trust Architecture for secure Open RAN
26:38
Introduction to O-RAN Philosophy
13:19
Просмотров 12 тыс.
Introduction to OpenStack
32:38
Просмотров 147 тыс.
Iran launches wave of missiles at Israel
00:43
Просмотров 556 тыс.