International Telecommunications, Commercial Agreements & Market CoordinationPractice area
Cross-Border Roaming, MVNO & Wholesale-Access Agreement Architecture
Before a cross-border mobile relationship is committed, decision makers may need a disciplined record of whether the stated model is roaming, host-MVNO, direct wholesale access or wholesale resale. This page provides fact-specific legal information on aligning the relevant agreement suite and dependencies; it does not determine authorisation, access rights, applicable law, technical performance or commercial rates.
The starting point
Make the next decision with the commercial context in view.
An identified cross-border roaming, host-MVNO, direct wholesale-mobile-access or wholesale-resale model often sits across a principal agreement and several connected records. Before signature, the commercial question is not simply what a single document says, but whether the document set records the same stated operating model, party roles and hand-offs. This practice is limited to that pre-signature agreement architecture.The starting point is a defined relationship, rather than a generic connectivity, software, distribution, shared-network or strategic-alliance arrangement. The work maps how the stated model appears across heads of terms, a principal wholesale or roaming agreement, relevant schedules, reporting and billing records, change-control materials and transition or exit documentation. It keeps non-technical interface assumptions visible without designing a network or assessing performance.The analysis can identify pricing-governance inputs, measurement assumptions, reporting and audit-record allocation, and the location of suspension, migration and termination records, without calculating rates, determining payment treatment or reaching a commercial conclusion. Questions that depend on a regulatory, competition, data, consumer, payment, tax, sanction or dispute framework are preserved as fact-led questions for separately qualified review. The scope does not decide authorisation, access rights, legal effect, validity, enforceability, applicable law or compliance.
How we help
The work around the decision.
01
Operating-model and role record
The analysis begins by recording the stated commercial model: international roaming, a host-MVNO arrangement, direct wholesale mobile access or wholesale resale. It distinguishes that model from an ordinary technology, distribution or connectivity arrangement, because the agreement architecture depends on the relationship the documents say they describe. The record can identify stated home and visited, host and virtual, provider and access-seeker, retail-provider and subcontractor roles. It does not determine a party’s regulatory status, corporate capacity, eligibility, authority or entitlement to access a network.
02
Agreement-suite alignment
A principal agreement may be read alongside heads of terms, roaming or service schedules, billing and reporting schedules, change records, notices and transition or termination materials. This workstream maps the apparent function of each item and the dependencies between them, including which assumptions are repeated, qualified or deferred. It can expose an unclear hand-off between the main agreement and a connected record for focused consideration. It does not prescribe a template, prepare a complete agreement, determine incorporation by reference or state that any document set is sufficient, valid or enforceable.
03
Non-technical hand-off dependencies
The document map can identify non-technical assumptions that need a consistent home in the record, such as activation or handover descriptions, information-exchange expectations, reporting windows, incident-notice pathways and escalation records. The purpose is to make visible how a stated operating relationship moves between commercial documents and supporting records before signature. This is not network design or an operational delivery assessment. It does not address routing, configuration, testing, resilience, cybersecurity, interoperability, traffic management, outage response or service-quality conclusions.
04
Pricing-governance and assurance records
For the identified model, the architecture may locate the documents that refer to pricing inputs, measurement assumptions, billing or settlement records, reporting cadence, audit information and change-control steps. Separating those record functions can help show whether a later operational or commercial input has a stated documentary path. The exercise remains descriptive: it neither sets nor calculates a rate, tariff, charge, cap or formula. It also does not determine tax, foreign-exchange, accounting, credit-support, payment, revenue-assurance or valuation treatment, or assess a regulatory pricing framework.
05
Question log, transition and exit record
A pre-signature record can identify where suspension, migration, transition, termination or exit materials connect to the stated model and to the wider agreement suite. It can also preserve a focused question log: the factual trigger, relevant provision or record, and the question requiring separately qualified review. This avoids treating an unresolved issue as settled merely because it is referenced in a document. The workstream does not advise on disputes, remedies, proceedings, access continuation, regulatory consequences or legal effect, and it does not provide a conclusion on a jurisdiction-specific position.
Commercial context
A bounded record architecture for an identified mobile operating model
Model first, document second
The name given to a mobile relationship does not by itself settle what the agreement suite records. In roaming, the commercial description may involve a home operator purchasing a service that enables a subscriber to use a visited operator’s network. A host-MVNO or wholesale-resale description may instead foreground the host, virtual operator, wholesale provider or retail provider. Recording the stated model and roles first helps prevent a general connectivity document from being treated as though it captures the same assumptions as the identified relationship.
Connected records carry distinct functions
A heads of terms, principal agreement, service schedule, reporting or billing schedule, change record and transition material may each carry different facts or process assumptions. The architecture maps those functions and highlights where one record appears to rely on another. It can distinguish a reference to a pricing input from a rate conclusion, and an audit-information allocation from a finding about assurance. The result is an organised factual map, not a prescribed contract package, calculation, technical design or statement about the effect of the documents.
Conditional jurisdictional questions
Where a particular country connection is material to the proposed model, such as a home-network, visited-network, host-network, governing-law, payment-flow, service-delivery or dispute-forum connection, the record can identify the factual trigger and the specific question that follows. The question may concern a regulatory, competition, data, consumer, payment, tax, sanction or dispute framework. It is kept as a question for separately qualified review rather than answered through the agreement map. This sequencing avoids inferring a legal position from an operator’s location or from a document label.
Questions, not prescriptions
What may matter.
What distinguishes roaming from a host-MVNO or wholesale-resale model for this purpose?
The distinction starts with the relationship the proposed documents state, not with a legal classification. A roaming description may use home-operator and visited-operator roles; a host-MVNO description may use host and virtual-operator roles; wholesale resale may foreground a provider, access seeker and retail provider. The agreement map records those stated roles and identifies where they appear across the agreement suite. It does not decide whether a party fits a regulatory category, has authority, holds an authorisation or may obtain access. A generic software, distribution, connectivity or shared-network arrangement falls outside this narrowly defined entry point.
Which documents may need to align before the model is committed?
The relevant documents may include heads of terms, a principal roaming or wholesale agreement, service or roaming schedules, reporting and billing schedules, change-control records, notices and transition, suspension or termination materials. Their relevance depends on the facts of the identified model. The exercise is to map the apparent function of each record, trace stated dependencies and identify where an assumption is repeated, qualified or deferred. It does not create a universal document checklist or determine whether a document is incorporated, complete, valid, enforceable or sufficient. Connected records may need separate qualified consideration where a material question remains unresolved.
Why keep regulatory and commercial questions in a separate question log?
A proposed operating model may raise questions that depend on the relevant regulatory, competition, data, consumer, payment, tax, sanction or dispute framework. A record architecture can preserve the triggering fact, the document provision or supporting record and the question to be considered, without converting that issue into a conclusion. This helps keep a reference to pricing governance separate from a rate decision, and a reference to access from an assertion of entitlement. Where a material connection or issue is identified, it may require separately qualified review. The question log is not a legal opinion, compliance assessment, regulator engagement plan or determination of applicable law.
Begin with context
Discuss the agreement-record question
Contact TRW & Co with a non-confidential summary of the identified operating model, decision stage and timing.Legal information only. Legal information on this page is general and fact-specific; it is not legal advice and does not create a lawyer-client relationship. Do not send confidential information through this contact route.