For VoLTE Design & Optimization, check out the complete playlist below :) 🌐VoLTE Design & Optimization 💡ruclips.net/p/PL4OXTttOk9WiY6DKS3flR_NIYJf6NCLLJ
ROHC is happening at PDCP layer so why its not taking at eNB while sedning out the recieved packets from UE to the next eNB? there is also a chance of potential packet loss?
Basically, over the air interface, we need to conserve as much bandwidth as possible since air interface is bandwidth limited while the eNB to eNB communication is over X2 and does not really have a bandwidth limitation. Now, from practical perspectives, the IP header is required to know the destination address so eNB needs to remove RoHC compression from the header so that all that routing information is used.
@@OurTechPlanet sorry ，I mean in your video like the time 7:44 , it show that it's still 40Bytes header between two base station , is there anyway to compress this header not only between UE and basestation , but also between two base station in the picture( contain the network like AS and NAS components)
Because the header contains source and destination IPs that will be required by many entities (core elements) between the two eNBs. So, the packets need to be decompressed before sending them to the core for correct routing.
For VoLTE Design & Optimization, check out the complete playlist below :)
🌐VoLTE Design & Optimization
💡ruclips.net/p/PL4OXTttOk9WiY6DKS3flR_NIYJf6NCLLJ
But could you please share more on Counter level tuning of any Vendor w.r.t ROHC
Little bit more light on U Mode, O/R mode what and how it works?
@@swarnban8634 We strive to keep things vendor agnostic :) I will add the RoHC modes in my to-do list!
Excellent 🎉
Thanks
Very well explained
Thanks!
But could you please share more on Counter level tuning of any Vendor w.r.t ROHC?
As a rule, we try not to discuss vendor-specific details. Thanks for understanding! :)
excellent
Thanks!
ROHC is happening at PDCP layer so why its not taking at eNB while sedning out the recieved packets from UE to the next eNB? there is also a chance of potential packet loss?
Basically, over the air interface, we need to conserve as much bandwidth as possible since air interface is bandwidth limited while the eNB to eNB communication is over X2 and does not really have a bandwidth limitation. Now, from practical perspectives, the IP header is required to know the destination address so eNB needs to remove RoHC compression from the header so that all that routing information is used.
May I ask why between network , the ROHC is disabled ?
Can you elaborate a bit more? Are you saying that in your network, suddenly ROHC stopped working?
@@OurTechPlanet sorry ，I mean in your video like the time 7:44 , it show that it's still 40Bytes header between two base station , is there anyway to compress this header not only between UE and basestation , but also between two base station in the picture( contain the network like AS and NAS components)
@@OurTechPlanet 🤣
@@shuoyang411 I mean the question is relevant, but why do you even need that feature to takes place. It hardly affects the customer perception.
@@OurTechPlanet probably the question is why no ROHC bewteen eNBs. even that is also an over the air communication only
Any specific reason why source enb is decompressing it before sending it to the target enb
Because the header contains source and destination IPs that will be required by many entities (core elements) between the two eNBs. So, the packets need to be decompressed before sending them to the core for correct routing.
Please do a session on M-MIMO also...
Sure, will plan this as well
Please make sessions on LTE optimization also
I have started those sessions as well. The first one on ERAB Setup Success Rate is already published.
ruclips.net/video/LHAfy45zImg/видео.html
@@OurTechPlanet please make more sessions on LTE KPI optimization... thanks!
@@OurTechPlanet Please give me a job......now...I undertood VOLTE.
Very well explained
Glad it was helpful!