Skip to main content

T-Mobile's DevEdge Versus Telstra's Nokia Network as Code via muru-D Labs

Both T-Mobile and Telstra are having a crack at turning their 5G networks into programmable platforms by using standardised APIs. But their approaches are a bit different when it comes to what they're aiming for, how they're going about it, and how they're getting it done. T-Mobile's DevEdge platform, which is all hooked up with GSMA Open Gateway, is really pushing a big, broad API ecosystem for both everyday punters and big businesses, chucking in a mix of Operations Support Systems (OSS) and Business Support Systems (BSS) APIs.

On the flip side, Telstra's gone through its Muru-D Labs and Nokia's Network as Code platform, mainly focusing on OSS APIs for enterprise use cases. This lines up nicely with their Connected Future 30 strategy and the Aduna joint venture. Below, we'll compare these different ways of doing things, suss out the good bits and the not-so-good bits, see who else is using Nokia's platform, and highlight the differences in their go-to-market (GTM) and business strategies.









How T-Mobile's DevEdge Differs from Telstra's muru-D Labs with Nokia Network as Code

Scope and What APIs They're Keen On:

T-Mobile (DevEdge + GSMA Open Gateway):

  • Offers a mix of OSS APIs (like Quality on Demand (QoD), Device Status) and BSS APIs (like Carrier Billing – Check Out, Number Verification) to back up apps for both consumers and businesses.
  • Focuses on everyday consumer stuff (like gaming, streaming) and big business solutions (like IoT, edge computing), making the most of T-Mobile's massive 5G network, which covers a fair chunk of people (326 million).
  • Hooks into GSMA Open Gateway’s CAMARA-based APIs, making sure it all plays nice globally across 67 operators.

Telstra (muru-D Labs + Nokia Network as Code):

  • Mainly keen on OSS APIs (like network slicing, QoD) for business use cases, such as managing network traffic for big events, getting better visibility, and giving priority to critical services.
  • Poking around with fixed network use cases through Nokia's service orchestration software, putting a lot of emphasis on industrial applications (like mining, logistics)
  • Lies hand-in-glove with Aduna, a joint venture with 14 telcos (including T-Mobile), focusing on OSS APIs, with a fair bit less BSS integration compared to T-Mobile.

Platform and The Whole Ecosystem:

T-Mobile:

  • DevEdge is T-Mobile's very own developer portal, integrated with Open Gateway and backed by partnerships with the big cloud players (AWS, Microsoft Azure) and aggregators (like Vonage).
  • Makes a big song and dance about making it easy for developers to get stuck in, with sandboxes, SDKs, and events like the Telecommunications Network API Challenge.

Telstra:

  • Uses Nokia's Network as Code platform via muru-D Labs, which is a hub for cooking up new ideas, offering live and simulated APIs in a lab environment.
  • Got a local hackathon planned to get developers involved, focusing on innovation for businesses and testing things out in the real world.
  • Leans on Nokia's ecosystem (over 50 partners, including telcos, hyperscalers, and CPaaS providers) and Aduna's multi-telco setup.

Go-to-Market (GTM) Strategy:

T-Mobile:

  • Direct and Global: DevEdge is aimed at developers all over the world through Open Gateway’s hyperscaler partnerships and aggregators, targeting both everyday punters (like gaming, streaming subscriptions) and businesses (like IoT, enterprise connectivity).
  • Marketing Approach: Promotes developers getting involved through competitions and an easy-to-use portal, cashing in on T-Mobile's 5G leadership to get people on board.
  • Revenue Model: Makes a buck from APIs through premium services (like Go5G Plus plans, fixed wireless broadband), which aligns with their reinvestment strategy (5.09% revenue growth in Q3 2024).

Telstra:

  • Collaborative and Business-Focused: muru-D Labs and Aduna are targeting enterprise developers, with APIs dished out through Nokia’s Network as Code and aggregator platforms.The planned hackathon is all about local engagement.
  • Marketing Approach: Focuses on business-to-business (B2B) use cases (like mining, logistics) and Telstra’s Network as a Product vision, testing APIs in controlled lab environments.
  • Revenue Model: Shares costs and revenue across Aduna’s 14 telcos, aiming for high-margin business sectors (like 18% of private 5G users in mining/agriculture).

Business Strategy:

T-Mobile:

  • Prioritises getting new customers and keeping the ones they've got (0.86% churn, 834,000 postpaid additions in 2024) over handing out dividends, instead chucking money back into 5G and modernising their BSS/OSS.
  • Uses APIs to boost Average Revenue Per User (ARPU) through premium services and partnerships within their ecosystem, supporting a strong valuation (PEG ratio 1.13).

Telstra:

  • Balances the consumer and business markets, with Aduna spreading the API development costs across telcos to get the most bang for their buck.
  • Focuses on enterprise revenue and making things run smoothly, lining up with its Connected Future 30 strategy to turn network capabilities into products.

The Good Bits and the Not-So-Good Bits

T-Mobile (DevEdge + GSMA Open Gateway):

Pros:

  • Broad Ecosystem: Access to Open Gateway’s 67 operators and hyperscalers means global reach and everything playing nice, spot on for consumer and business apps.
  • BSS Integration: APIs like Carrier Billing crank up commercial innovation (like streaming subscriptions), helping T-Mobile grow (6% expected Q4 2024 revenue).
  • Developer Engagement: Competitions and a solid DevEdge portal get people involved, making the most of T-Mobile’s 5G leadership (326 million covered).
  • Consumer Focus: Lines up with T-Mobile’s "Un-carrier" strategy, boosting customer loyalty and ARPU.

Cons:

  • Limited API Overlap: Only the Device Status API overlaps with AT&T and Verizon, meaning less interoperability across the U.S.
  • BSS Gaps: The BSS API offerings aren't as comprehensive as the OSS ones, which could limit commercial use cases.
  • Competition: Copping heat from Verizon and AT&T, also being part of Open Gateway, so they've gotta keep finding ways to stand out.
  • Adoption Variability: Not as many developers are taking it up in the U.S. (30%) compared to places like India (60–70%).

Telstra (muru-D Labs + Nokia Network as Code):

Pros:

  • Enterprise Strength: Focuses on high-margin B2B use cases (like managing event traffic, prioritising critical services), leveraging Telstra’s 5G and fixed networks.
  • Cost Efficiency: Aduna’s multi-telco model (14 operators, including T-Mobile) shares API development costs, making it more scalable.
  • Nokia Partnership: Nokia’s Network as Code platform (50+ partners) provides ripper tools (SDKs, sandboxes) and CAMARA/GSMA standards for interoperability.
  • Innovation Hub: muru-D Labs and planned hackathons encourage enterprise developers to get cracking and test things out in the real world.

Cons:

  • Limited BSS Focus: Aduna and Muru-D Labs are all about OSS APIs, missing out on opportunities for innovation in billing and customer management.
  • Regional Scope: Telstra’s Australia-centric approach limits global reach compared to T-Mobile’s Open Gateway ecosystem.
  • Capacity Constraints: 5G home internet is facing scalability issues, which can impact how well it delivers enterprise services.
  • Developer Onboarding: The multi-telco Aduna model might make it a bit trickier for developers to get access compared to T-Mobile’s single-operator DevEdge.

Other Operators Using Nokia’s Network as Code Platform

Nokia’s Network as Code platform, which kicked off in September 2023, has over 50 partners, including operators, hyperscalers, CPaaS providers, and system integrators. Some of the notable users include:

  • DISH Wireless (EchoStar/Boost Mobile): Teamed up with Nokia in 2023 to develop enterprise applications using 5G capabilities (like network slicing, QoS management). Uses Nokia’s platform for advanced traffic controls and device status APIs.
  • GlobalLogic (Hitachi Group): Leans on Nokia’s platform for automotive, industrial, and financial use cases, focusing on apps that are aware of the network.
  • Elmo (Estonian Company): Uses Nokia’s platform with Infobip for real-time remote driving in Helsinki, making the most of low-latency 5G APIs.
  • Other Telcos: Includes 16 operators (like AT&T, Deutsche Telekom, Vodafone) as of October 2024, with Nokia aiming for 30 by the end of the year.
  • Hyperscalers: Google Cloud is integrating Nokia’s platform to give developers better access with AI capabilities (Vertex AI, Gemini 1.5 Pro).

Key Differences in GTM and Business Strategies

T-Mobile (DevEdge + Open Gateway):

  • GTM: Straight to the developer via DevEdge, with global distribution through Open Gateway’s hyperscalers (AWS, Azure) and aggregators (Vonage). Targets both everyday punters (gaming, streaming) and big businesses (IoT, edge computing) with developer competitions.
  • Business Strategy: Chasing profits to fuel 5G growth and customer acquisition (22.19% annualised return over 5 years), using APIs to ramp up premium services and ARPU. Focuses on being top dog in the U.S. market with potential for a global ecosystem.

Telstra (muru-D Labs + Nokia Network as Code):

  • GTM: Collaborative through muru-D Labs and Aduna, targeting enterprise developers via Nokia’s platform and aggregators. Local hackathons put the spotlight on B2B innovation here in Australia.
  • Business Strategy: Balances consumer and enterprise markets, with Aduna’s cost-sharing model aimed at high-margin B2B sectors (like mining). Lines up with Connected Future 30 to productise network capabilities, with a focus on running things efficiently.

The Wrap-Up

T-Mobile’s DevEdge and Open Gateway strategy offers a much broader API ecosystem, hitting both consumers and businesses. It really makes the most of their 5G network for global reach, but they've got a few hurdles with the depth of their BSS and API overlap in the U.S. Telstra’s muru-D Labs and Nokia Network as Code, through Aduna, are more focused on enterprise OSS APIs. They get a leg up from cost-sharing and Nokia’s robust platform, but they're a bit limited by their regional focus and some gaps in BSS. Other companies like DISH, GlobalLogic, and Elmo are using Nokia’s platform for all sorts of different things, showing how versatile it is

Comments