5G New Radio For Even Faster Speeds Accelerating the Growth of Industry 4.0

While the standard was released at the end of 2017, implementing NR requires a combination of hardware and software innovation to proliferate, and four years later, one of the leaders in wireless networking technologies, services, and solutions, Radisys, a company based in the U.S., and owned by Reliance Industries, last week announced the release of their 5G NR offering.

As a global leader of open telecom solutions, Radisys introduced its Release 16 compliant 5G NR protocol software, which supports low latency use cases for 5G private networks.

Radisys’ Connect RAN 5G solution, based on specifications from 3GPP, the Small Cell Forum, and the O-RAN Alliance, enables an elastic and agile 5G network tailored to meet the unique requirements of diverse 5G applications with minimized CAPEX, improved time-to-market, and shortened time-to-revenue.

The new Release 16 compliant 5G NR protocol software delivers enhancements in functionality, capacity, coverage, latency, mobility, reliability, and ease of deployment.

“We are excited to launch the new version of our Connect RAN 5G Software that is now compliant to the 3GPP Release 16 specification, and Open RAN architectures, delivering the critical reliability and ultra-low latency needed for emerging Industry 4.0 use cases,” said Munish Chhabra, SVP and General Manager, Mobility Software and Services, Radisys. “Radisys continues to deliver standards-based 5G software early to market. Working closely with our partners, we remain in lockstep with our customers’ requirements for their 5G solutions and advance the 5G ecosystem.”


Read Full Article

Previous Article
Radisys Jumpstarts the Release 16 5G New Radio Bandwagon
Radisys Jumpstarts the Release 16 5G New Radio Bandwagon

Next Article
UC Trends 2022: Collaboration Round Table
UC Trends 2022: Collaboration Round Table


Ready to talk? Watch our solution in action!

First Name
Last Name
Thank you! We'll be in touch momentarily
Error - something went wrong!