MVNO Wireless – TMF Fx eTOM, SID, TAM & REST APIs

Posted by cfaurer on March 24th, 2015 filed in BPMN, Frameworx Consulting, Frameworx Training, REST APIs

I have a phone that I purchased from Google that uses a SIM card and minutes purchased from a reseller for an MVNO, which depends on a network operator. Can these engaged parties and their various relationships be understood as MVNO Wireless – TMF Fx eTOM, SID, TAM & REST APIs?

We’ll see! That’s the goal of this series of articles. In part-1 we’ll outline the scope of the scenario introduced above using TMF Fx eTOM, SID, TAM & REST APIs covering E2E business scenarios: C2M, O2C, U2P and T2R.

A Mobile Virtual Network Operator (MVNO) does not manage it’s own network, rather it buys network capability in bulk and resells it to end customers. A SIM card reseller has a similar business model in that it resells the MVNO service as it’s own product offering.

The handset provider utilizes industry standard specifications and engaged party relationships to ensure that the mobile device it sells will operate on the specified 2G, 3G and 4G networks. The mobile network operator (MNO) provides access to the network infrastructure that makes using the mobile device possible for voice, data, text and video services.

Who will purchase the product offerings and use the services and resources provided? The customer.

The engaged parties discussed include; customer, mobile device provider, SIM & minutes reseller, MVNO and MNO.

The TMF membership have defined 4 key business scenarios that are of interest to us:

  • Concept to Market (C2M)
  • Order to Cash (O2C)
  • Usage to Payment (U2P)
  • Trouble to Resolve (T2R)

Concept to Market (C2M)

Adapted from TM Forum QuickStart Pack – GB955_Concept_to_Market_v0.4

eTOM Concept to Market Scope

eTOM Concept to Market Scope

SID Business Entities supporting C2M

Mappings adapted from GB942MAP

Concept to Market supporting SID ABEs

Concept to Market supporting SID ABEs

TAM Application Capability supporting C2M

Mappings adapted from GB942MAP

Concept to Market supporting TAM Application Capability

Concept to Market supporting TAM Application Capability

Business Services supporting C2M

Concept to Market supporting Business Services

Concept to Market supporting Business Services

Order to Cash (O2C)

Adapted from TM Forum E2E Business Scenarios – GB921_E_Release 13-5_v1-13-2

eTOM Ordet to Cash Scope

eTOM Ordet to Cash Scope

SID Business Entities supporting O2C

Mappings adapted from GB942MAP

Order to Cash supporting SID ABEs

Order to Cash supporting SID ABEs

TAM Application Capability supporting O2C

Mappings adapted from GB942MAP

Order to Cash supporting TAM Application Capability

Order to Cash supporting TAM Application Capability

Business Services supporting O2C

Order to Cash supporting Business Services

Order to Cash supporting Business Services

Usage to Payment (U2P)

Adapted from TM Forum E2E Business Scenarios – GB921_E_Release 13-5_v1-13-2

eTOM Usage to Payment Scope

eTOM Usage to Payment Scope

SID Business Entities supporting U2P

Mappings adapted from GB942MAP

Usage to Payment supporting SID ABEs

Usage to Payment supporting SID ABEs

TAM Application Capability supporting U2P

Mappings adapted from GB942MAP

Usage to Payment supporting TAM Application Capability

Usage to Payment supporting TAM Application Capability

Business Services supporting U2P

Usage to Payment supporting Business Services

Usage to Payment supporting Business Services

Trouble to Resolve (T2R)

Adapted from TM Forum E2E Business Scenarios – GB921_E_Release 13-5_v1-13-2

eTOM Trouble to Resolve Scope

eTOM Trouble to Resolve Scope

SID Business Entities supporting T2R

Mappings adapted from GB942MAP

Trouble to Resolve supporting SID ABEs

Trouble to Resolve supporting SID ABEs

TAM Application Capability supporting T2R

Mappings adapted from GB942MAP

Trouble to Resolve supporting TAM Application Capability

Trouble to Resolve supporting TAM Application Capability

Business Services supporting T2R

Trouble to Resolve supporting Business Services

Trouble to Resolve supporting Business Services

The material presented represents the general scope of the engaged party scenario based on TM Forum Frameworx content – a phone purchased from Google that uses a SIM card and minutes purchased from a reseller for an MVNO, which depends on a network operator. Is this the necessary and sufficient material required to understand this business scenario?

TM Forum Frameworx & TOGAF

AMKBCloud-TOGAF-Fx

A validation that the material presented does provide a solid base understanding of the business scenario is represent by the figure above showing the relationship between The Open Group Architectural Framework (TOGAF) and TM Forum Frameworx – Process Framework (eTOM), Information Framework (SID), Application Framework (TAM), Integration Framework (Business Services & APIs). Available from TMF Fx but not covered are Business Metrics.

Assignment of activities to roles in the organization is beyond the scope of responsibility of TMF Frameworx and therefore TBD.

In the next article we’ll look at each TMF Frameworx eTOM E2E scenario in turn – C2M, O2C, U2P and T2R for the MVNO Wireless example.

Leave a Comment

You must be logged in to post a comment.