HI Dan Kehn It was vey easy and simple to understand the basic VRAN concpet Could you please make a video on the Antenna, RRU, RRH, RDU, Rectifier, Battery and also how these are connected on the cell site
Hi, Thanks for sharing this video. I believe this is an awesome intro. -->I have some basic questions, please advise. Thanks.... 1. Is this used for sharing 4G & 5G networks only. Is this network also compatible for previous generation phones also, or what is the limitation on the phones? -->The Virtualization provides dynamic flexibility for creating a dedicated useability for each individual user. 2. Is there a limitation for the number of users based on the Tower capacity? 3. What is the server configuration which can provide this flexibility? Is there a dedicated smart interface to support this functionality? 4. Can we have multiple CSP's configuration inside one server? -->Multiple dedicated hardware is replaced by this software 5. Is this an open software? if Yes please advice the level of security provided between each CSP's within a server? 6. How will be the load be balanced between primary and the secondary servers?
The individual xNF like vDU and vCU will run on servers acting like a cloud or local cloud close to the location. So the vDU will always be close to the antenna as it doesn’t make sense to do it any other way. The vCU could be back in the data center, again, on servers acting like a cloud or local cloud. To be clear, both would be on the CSP’s infrastructure, which could be a private cloud or public. But in reality, a CSP is unlikely to allow a Public Cloud provider to carry such important traffic. As for how the tower RU -> vDU -> vCU are connected, according to my telco expert who was involved in such installs, the answer is “it depends”. The vDU is at the cell site, so it’s hardwired to the RU; the vDU to vCU connection choice depends on distance and cost. Optical fiber is an ideal option, assuming it’s logistically realistic to run a line, otherwise a microwave vDU -> vCU connection or even over existing coax cabling are alternatives.
Thank you for the feedback! As for your question, we shared some behind the scenes of our videos on the Community page, check it out here 👉 ibm.co/3dWpZoL 😉
Short answer: Yes, the vDU is a virtual machine. Longer answer: Yes, the vDU is commercial off-the-shelf hardware with VNFs software installed; conceptually, think of the vDU as a "mini" cloud server [with appropriate network cards installed], either housed on-site in an equipment enclosure or at the CSP's data center.
Wish you have a good day Sir and thanks this video , I learned a lot. I have a question, regarding devices VCU+VDU, are they installed in the site or in the core ?
Hi Dan, thank you for this informative video. It is very helpful. However, I have a couple questions: First question: You said that one of the benefits of vRAN over RAN is it can dynamically adjust capacity according to demand -- And the way vRAN does this is by having a cluster of vDUs that can "switch on and off" depending on the demand, therefore increasing/decreasing capacity. However, what's stopping us to have a cluster of BBUs instead? I have read that BBUs also have proprietary software installed on them. So couldn't we just add to that proprietary software a function that can "switch on and off" BBUs depending on demand? Second question: In the "Campus" example, how was the cell tower and the vDU communicating? Was the cell tower in the school connected to the vDU directly (using fiber optic perhaps) or does the cell tower send its signals to the RU first then the RU sends it to the vDU?
A1). Yes, you could have a cluster of proprietary, expensive BBUs, if you’re willing to accept that they’re idle most of the time. Your idea of installing BBU software functionality on hardware is essentially a vDU, the key difference is that vDU hardware is general purpose off-the-shelf servers that cost less than proprietary hardware and the VNFs are standards-based functionality versus closed, proprietary software. A2). The vDUs are typically installed at the foot of the cell tower and directly connected to the RU, though the VDUs could be shared by multiple towers IF they’re in close proximity to serve a small region (e.g., in our fictitious example, the campus and possibility nearby businesses/residences). Ideally, the VDUs are connected to the core network via fiber optic (backhaul), but if that’s too costly due to existing roads/buildings, radio transmission can be used. [And thanks to our IBM UK expert on telecoms, Alan Sullivan, for verifying the accuracy of my response above]
Hi Dan, is the core in the vran still an physical architecture located on the providers base or is it also an virtual core. Because a 5g SA Core is the most expensive physical part and that makes the 5G providers dependent on the manufactures
Sorry for the delayed response: The 5G Core SA is a software defined entity and not a physical entity and can be deployed on x86 servers in a similar way to the vRAN. [And thanks to our IBM UK expert on telecoms, Alan Sullivan, for verifying the accuracy of my response above]
Sorry for the delayed response: The 5G networks have been designed in such a way to reduce the latency across the network. The main impact of this is that the network requires many more cell sites closer together to deliver the lower latency and increased bandwidths - probably 10-100 times more in urban locations, so lamp posts, telephone boxes etc. 😲
And oRAN? Thanks for sharing
HI Dan Kehn
It was vey easy and simple to understand the basic VRAN concpet
Could you please make a video on the Antenna, RRU, RRH, RDU, Rectifier, Battery and also how these are connected on the cell site
Really informative video !
Hi, Thanks for sharing this video. I believe this is an awesome intro.
-->I have some basic questions, please advise. Thanks....
1. Is this used for sharing 4G & 5G networks only. Is this network also compatible for previous generation phones also, or what is the limitation on the phones?
-->The Virtualization provides dynamic flexibility for creating a dedicated useability for each individual user.
2. Is there a limitation for the number of users based on the Tower capacity?
3. What is the server configuration which can provide this flexibility? Is there a dedicated smart interface to support this functionality?
4. Can we have multiple CSP's configuration inside one server?
-->Multiple dedicated hardware is replaced by this software
5. Is this an open software? if Yes please advice the level of security provided between each CSP's within a server?
6. How will be the load be balanced between primary and the secondary servers?
Where will vRAN VNF will be running?If it is running in a private cloud(openstack maybe) how they establish connection between it and a mobile tower?
The individual xNF like vDU and vCU will run on servers acting like a cloud or local cloud close to the location. So the vDU will always be close to the antenna as it doesn’t make sense to do it any other way. The vCU could be back in the data center, again, on servers acting like a cloud or local cloud. To be clear, both would be on the CSP’s infrastructure, which could be a private cloud or public. But in reality, a CSP is unlikely to allow a Public Cloud provider to carry such important traffic.
As for how the tower RU -> vDU -> vCU are connected, according to my telco expert who was involved in such installs, the answer is “it depends”. The vDU is at the cell site, so it’s hardwired to the RU; the vDU to vCU connection choice depends on distance and cost. Optical fiber is an ideal option, assuming it’s logistically realistic to run a line, otherwise a microwave vDU -> vCU connection or even over existing coax cabling are alternatives.
@@homebarista so the vDU and vCU are HWs installed at the site ?!
@@homebarista great explanations. Thanks
This was beautifully explained. Thank you!!
One of the best decision was to subscribe to your Chanel.
Thanks for subscribing, Darshan! 🙌
Really informative video..One out of topic question. What tool u r using as a whiteboard?
Thank you for the feedback! As for your question, we shared some behind the scenes of our videos on the Community page, check it out here 👉
ibm.co/3dWpZoL 😉
Please a VDU is a virtual machine or it is a container (serverless) ???
Short answer: Yes, the vDU is a virtual machine. Longer answer: Yes, the vDU is commercial off-the-shelf hardware with VNFs software installed; conceptually, think of the vDU as a "mini" cloud server [with appropriate network cards installed], either housed on-site in an equipment enclosure or at the CSP's data center.
Wish you have a good day Sir and thanks this video , I learned a lot.
I have a question, regarding devices VCU+VDU, are they installed in the site or in the core ?
in the core
Ran stand for?
Thanks for asking! It stands for Radio Access Network.
Thank you sir
Hi Dan, thank you for this informative video. It is very helpful. However, I have a couple questions:
First question:
You said that one of the benefits of vRAN over RAN is it can dynamically adjust capacity according to demand -- And the way vRAN does this is by having a cluster of vDUs that can "switch on and off" depending on the demand, therefore increasing/decreasing capacity. However, what's stopping us to have a cluster of BBUs instead? I have read that BBUs also have proprietary software installed on them. So couldn't we just add to that proprietary software a function that can "switch on and off" BBUs depending on demand?
Second question:
In the "Campus" example, how was the cell tower and the vDU communicating? Was the cell tower in the school connected to the vDU directly (using fiber optic perhaps) or does the cell tower send its signals to the RU first then the RU sends it to the vDU?
A1). Yes, you could have a cluster of proprietary, expensive BBUs, if you’re willing to accept that they’re idle most of the time. Your idea of installing BBU software functionality on hardware is essentially a vDU, the key difference is that vDU hardware is general purpose off-the-shelf servers that cost less than proprietary hardware and the VNFs are standards-based functionality versus closed, proprietary software.
A2). The vDUs are typically installed at the foot of the cell tower and directly connected to the RU, though the VDUs could be shared by multiple towers IF they’re in close proximity to serve a small region (e.g., in our fictitious example, the campus and possibility nearby businesses/residences). Ideally, the VDUs are connected to the core network via fiber optic (backhaul), but if that’s too costly due to existing roads/buildings, radio transmission can be used.
[And thanks to our IBM UK expert on telecoms, Alan Sullivan, for verifying the accuracy of my response above]
Ohhh I see! Thank you very much for your quick reply and clear explanation!
Hi Dan, is the core in the vran still an physical architecture located on the providers base or is it also an virtual core. Because a 5g SA Core is the most expensive physical part and that makes the 5G providers dependent on the manufactures
Sorry for the delayed response: The 5G Core SA is a software defined entity and not a physical entity and can be deployed on x86 servers in a similar way to the vRAN.
[And thanks to our IBM UK expert on telecoms, Alan Sullivan, for verifying the accuracy of my response above]
Cool. Interesting. Thx
What about latency?
Sorry for the delayed response: The 5G networks have been designed in such a way to reduce the latency across the network. The main impact of this is that the network requires many more cell sites closer together to deliver the lower latency and increased bandwidths - probably 10-100 times more in urban locations, so lamp posts, telephone boxes etc. 😲
very good!!!