5 European telcos publish Open RAN Technical Priorities Document
Five major European network operators have issued a white paper outlining their technical requirements for the open, disaggregated radio access network products they want to deploy in significant deployments starting next year.
The telco quintet – Deutsche Telekom, Orange, Telefónica, TIM (Telecom Italia) and Vodafone – signed the Memorandum of Understanding (MoU) on The Implementation of Open RAN Based Networks In Europe earlier this year and have now set out their technical stall so that the vendor community has some guidance with which to work.
The ‘Technical Priorities Document’ provides a set of “technical requirements that the signatories of the Open RAN MoU consider priorities for Open RAN architecture. It serves as a guidance to the RAN supplier industry on where to focus to accelerate market deployments in Europe, focusing on commercial product availability in the short term, as well as solution development in the medium term. In terms of timeframe, the operators wish to ensure the readiness of Open RAN solutions for large scale network roll-out from 2022 onwards. Macro deployment is identified as the primary target for the operators.”
The telco quintet say they are not seeking to develop new specifications or standards in this process, but simply identify their preferences in terms of technology and architecture that are based primarily on the specifications being developed by the O-RAN Alliance.
There are many requirements, particularly around the IT requirements underpinning the Open Cloud architecture that needs to support containerized cloud native functions (CNFs). You can read the full document here.
Opinion:
How many Open RAN technical requirements and spec writing consortiums/alliances are necessary? We already have O-RAN Alliance, TIP Open RAN Project, Open RAN Policy Committee, and slew of company alliances. That is NOT the way specifications are created as there are surely overlaps, duplications and gaps in one or more of these entities requirements documents. This will surely result in mass confusion and slow the market for Open RAN equipment.
The way to proceed, IMHO, is to have the operators work through the O-RAN Alliance to state which of their requirements are mandatory and which are optional. This is what PTT’s did from 1976-1996 within CCITT to standardize X.21, X.25, ISDN, Frame Relay, and ATM. They did likewise from 1998-2000 to standardize ADSL and VDSL within ITU-T.
……………………………………………………………………………………………………………………………………………….
The Open RAN Requirements document highlights multiple interfaces that need specific attention by technology developers. For example, adherence to an Open F1 interface for the centralized unit/distributed unit (CU/DU) split, as well as Open X2/Xn interfaces for connectivity between base stations – but stresses the importance of open fronthaul, described as “the prime interface to be supported in a fully interoperable manner, without compromising network performance, especially for Massive-MIMO.” The O-RAN Alliance 7.2x interface the preference of the five operators, though they note there is the need to “further investigate UL [uplink] enhancements for the 7.2x split in order to improve performance and robustness particularly in mobility scenarios.”
The paper also stresses that focus should be on 4G/5G in the 3.4-3.8 GHz bands as well as legacy FDD (frequency division duplex) bands. The operators believe that mmWave bands are more specific to certain markets and so not as important initially for this set of operators. As for interoperability with legacy mobile networks, the paper notes that “the operators are interested in inter-operability between 2G/3G baseband units and RUs, based on proprietary interfaces, since no open interface has been specified successfully. This applies mainly to hybrid Radio Units supporting 2G/3G/4G/5G, but also for legacy 2G/3G only RUs already deployed.”
In addition, the operators need to be sure that the Open RAN technology they deploy will enable RAN sharing: “While MORAN [multi-operator RAN] with shared O-RU only and MOCN [multi-operator core network] support is unanimously requested, both shared infra and dedicated infra per operator is relevant, depending on whether the infra is deployed on the same site or deployed autonomously by each operator in their target location (e.g. in their own cloud). Efficient RAN sharing management is required to allow sufficient independence between operators to manage their own CNFs on a shared infra, while avoiding any potential conflicts.”
References:
2 thoughts on “5 European telcos publish Open RAN Technical Priorities Document”
Comments are closed.
Open RAN will struggle to fit in, despite Euro telco demands, by IAIN MORRIS of Light Reading:
Littered with phrases like “MORAN with shared O-RU only and MOCN support is unanimously requested,” the document is guaranteed to give the average policymaker a splitting headache.
Asked to make a cash commitment to open RAN, policymakers will be curious to know why they should care. Of course, in this case, they are not the target audience. After begging authorities for money, Deutsche Telekom, Orange, Telefónica, Telecom Italia (whose friends call it TIM) and Vodafone are presenting their equipment makers and software companies with a checklist of requirements. It is a technical job spec for open RAN.
But it surfaces at an odd time and features some questionable statements. The most glaring is about ensuring open RAN is ready “for large-scale network rollout from 2022 onwards.” Just a few weeks ago, Orange was saying it did not expect open RAN to have full “parity” with a traditional RAN until the mid-2020s. There does not appear to have been any particular breakthrough since then.
The timing is odd because operators are, right now, investing billions of euros in the rollout of traditional 5G networks. Only this week, Deutsche Telekom, the very largest of the operators wielding an open RAN begging bowl, said its 5G network in Germany would cover 90% of people by the end of the year. That network, built by China’s Huawei and Sweden’s Ericsson, ticks none of the open RAN boxes.
It’s all about the fronthaul
At this stage, it is probably worth explaining what open RAN actually does. In the Huawei part of Deutsche Telekom’s network, just about everything comes from the Chinese vendor. Trying to use a Huawei radio in conjunction with some baseband technology from Ericsson would simply not work. Open RAN, very basically, is an attempt to fix this sort of interoperability problem through new and improved interfaces.
A safe assumption is that Deutsche Telekom will have nearly finished building its 5G network by the time open RAN is fit and muscled. Using the technology, then, would mean either replacing equipment that is only a few years old, and barely depreciated, or introducing new gear into a network that already provides near-nationwide coverage.
One of the most interesting technical requests in the wish-list is for new “fronthaul gateways” that would “allow reuse of already deployed radio units as an interim solution.”
The interface between this gateway and the radio could remain proprietary, the operators concede. But openness in the other direction would allow another vendor’s baseband systems to be used. In theory, Deutsche Telekom could have its Huawei-and-Ericsson mash-up without scrapping all the gear it has already installed.
This will not happen without revolution in the market, mainly because Huawei continues to insist open RAN is going nowhere fast. A likelier scenario is that Deutsche Telekom forces Ericsson to produce fronthaul gateways, whips out its baseband technology and introduces someone like Mavenir, a new kid on the block, or even Nokia.
It unceremoniously booted the Finnish company out of its radio access network in 2017 but has recently been cooing about Nokia’s enthusiasm for open RAN.
Yet this would punish one of Europe’s big 5G vendors without lessening Deutsche Telekom’s reliance on Huawei, a firm that looks increasingly dodgy to European authorities. Orange, with which Deutsche Telekom jointly procures equipment, would prefer to see Huawei suffer, judging by what Michael Trabbia, Orange’s chief technology officer, has said.
“We need to have strong providers and with the current ecosystem and situation between China and the US – that is not changing that much with the change of US president – it is more difficult to have some providers in Europe,” he recently told reporters. “It is certainly not our intention to not work anymore with or decrease the share of the European vendors.”
Unfortunately, if Huawei stubbornly refuses to build open RAN gateways, Deutsche Telekom’s only options would be to wait for its products to depreciate or swap them early.
A decision to rip and replace would entail some expense, to the probable dismay of shareholders who might not appreciate Deutsche Telekom’s sudden desire to cultivate open RAN competition. Supplier diversity, after all, is unlikely to have any noticeable effect on telco profitability or give operators the stock market profile of Google.
Even if Huawei did provide new gateways, they are unlikely to come free of charge. Investors would still face additional spending on those and a baseband overhaul when customers might already be enjoying top-notch services. Commercially, it does not sound very sensible.
Another possibility is that open RAN is used for densification – that is, for completely new mobile sites. Operators could try selling this move to the investor community as an essential coverage boost that will bring service-quality improvements, and one that is needed to overcome the limitations of the higher-frequency spectrum assigned to 5G.
The trouble is that several operators, including Orange, have downplayed the need for densification. “We are using more efficient technology and think we will be able to have the same coverage and won’t need to add sites,” said Trabbia last December.
Beamforming and massive MIMO are among the 5G technologies designed to overcome the signal limitations of higher-frequency spectrum. And both are mentioned in this week’s wish-list.
That document, like the public-sector funding request before it, contains not a single firm commitment to use open RAN, despite all the demands operators make of their vendors.
“It’s like sending a wish-list to Santa but saying we can’t guarantee you will get a Christmas present,” says John Strand, the CEO of Danish advisory group Strand Consult.
What’s more, the only one of the five telco signatories to have made any short-term open RAN promise is Vodafone. Last year, its UK subsidiary promised to use open RAN at about 2,500 sites in the west of the UK currently served by Huawei.
But its decision followed a government ban on the use of Huawei’s 5G products. The vehemence of Vodafone’s lobbying against that ban suggests it would not otherwise have been so bold.
https://www.lightreading.com/open-ran/open-ran-will-struggle-to-fit-in-despite-euro-telco-demands/a/d-id/769509?
Iain Morris of Light Reading:
The danger of open RAN is that it substitutes a series of dependencies for reliance on a couple of giant kit vendors. So far, there seem to be limited options for each disaggregated element – Dell, HPE and Supermicro on the server side, for instance, or Altiostar, Mavenir and Parallel Wireless in software. The smallest companies lack the financial strength of Ericsson and Nokia. And in the absence of Arm-based alternatives, Intel rules over baseband. A vulnerability in any part of the chain could bring the whole system crashing down.
https://www.lightreading.com/open-ran/britains-got-open-ran-talent-hopes-clueless-govt/a/d-id/770638?