Orange Connected Validation: IoT device labels

Author Hugues Orgitello Last updated 11 July 2026 ~15 min read

Guide - Orange Connected Validation

Orange is a telecommunications group present in France and in around thirty countries across Europe, Africa and the Middle East. Its connected device validation programme, Orange Connected Validation, is run via the IoT Journey portal and delivers three labels: Orange Assessed, Orange Connected and Orange Approved. It complements the GCF inter-operator certifications and the RED in Europe, without substituting for them. This page sets out the group's geographic footprint, the scope of the validation programme, the articulation with the Live Objects platform and the Datavenue suite, the eUICC and RSP topic, the Orange LoRaWAN network and the classic pitfalls of a pan-Orange commercialisation.

A group footprint to map

The Orange group operates or holds interests in several national affiliates, which makes the notion of an Orange network plural rather than singular. A device designed for Orange France does not automatically work as well on Orange Cameroun or Orange Egypte, and a validation programme must take this into account from the framing stage.

Region	Main countries	Specifics
France	Orange France	Legacy network, LTE-M active (no NB-IoT), 5G NSA and SA in deployment, Orange LoRaWAN as a complement, 2G shutdown in waves in 2026
Europe	Spain (via MasOrange, joint venture created in 2024), Romania, Slovakia, Poland, Belgium, Luxembourg, Moldova	Separate national networks, LTE-M deployed on several markets, NB-IoT at Orange in Belgium and Luxembourg
West Africa	Senegal, Cote d'Ivoire, Mali, Burkina Faso, Liberia, Sierra Leone, Guinea	Strong mobile penetration, LTE in deployment, cellular LPWAN availability to verify country by country
Central Africa	Cameroon, Democratic Republic of Congo, Central African Republic	Growing LTE coverage, local spectrum constraints
North Africa	Morocco (Orange Maroc, formerly Meditel), Tunisia	Bands harmonised with Europe, distinct local regulators (ANRT, INT)
Middle East	Jordan, Egypt	Specific operating conditions, local regulatory profile

This list evolves, the group having historically divested or acquired affiliates. The consolidated state at a given point in time should be verified with Orange Business before framing a pan-Orange project.

The practical consequence: a device aimed at the French market does not implicitly cover the African Orange market, and an Orange validation programme must be articulated with the national regulatory requirements (ARCEP in France, ANRT in Morocco, national agencies in West and Central Africa). For the regulator dimension on the French side, see the general page on RED.

Orange Connected Validation, the label programme

Orange Connected Validation is the programme through which Orange evaluates and labels connected devices that are candidates for a listing in its IoT Journey catalogue and for deployment on its networks. It is conducted by Orange teams, the entry point being the address device.validation@orange.com, and covers LoRaWAN, LTE-M, NB-IoT, 4G and 5G connectivity depending on the country.

The process is structured in two phases:

1. Phase 1, maturity assessment. Verification of documentary compliance (CE certificate, technical specifications, user guides), basic functional tests and a network connection test, outside the lab.
2. Phase 2, in-depth validation. Advanced testing in an Orange Innovation laboratory or an approved partner laboratory: network interoperability, roaming, energy consumption analysis and field tests on various infrastructures.

At the end of the validation, the device receives the corresponding label, an Orange connectivity certificate, and can be listed in the IoT Journey catalogue.

The three Orange labels

Label	Scope	Hardware and firmware versions
Orange Assessed	Documentary review (CE certificate, specifications, guides) and basic user tests of network connection and data transfer	Not frozen
Orange Connected	Laboratory testing of connectivity and energy consumption, radio performance and interoperability	Frozen, label tied to the tested versions
Orange Approved	End-to-end testing: connectivity, consumption, security, quality (labelling, packaging, WEEE), integration with Live Objects, GPS performance, functional tests	Frozen, typically for devices commercialised by Orange

On the cellular side, GCF certification remains the baseline expected in practice, Orange being a GCF operator member. The Orange validation then looks at the behaviour of the device on the group's networks: deployed bands (B3 1800 MHz, B7 2600 MHz, B8 900 MHz, B20 800 MHz, B28 700 MHz for LTE and LTE-M, n78 3.5 GHz for 5G NR primarily in France), attachment to the EPC or 5GC core, eSIM/eUICC provisioning, real consumption, PSM and eDRX behaviour for LPWAN profiles.

Unlike the Verizon Open Development programme, which maintains a public and formalised Verizon Approved Module List, or Vodafone Global IoT Acceptance, Orange proceeds by labelling devices in the IoT Journey catalogue and by project review, leveraging existing GCF certifications. This governance difference affects the duration and the format of the interactions, but not the finality: without validation, a volume deployment ships without a safety net.

Orange compared to Vodafone and Deutsche Telekom

The three large pan-European operators (Orange, Vodafone, Deutsche Telekom) have structured their IoT acceptance programmes differently. The comparison is not trivial for a device aimed at multiple operators in Europe.

Criterion	Orange Connected Validation	Vodafone Global IoT Acceptance	Deutsche Telekom IoT Acceptance
Direct footprint	France, Central and Eastern Europe, Africa, Middle East	Germany, United Kingdom, Italy, Spain, other European markets, Vodafone Idea in India (stake), South Africa (Vodacom)	Germany, Central Europe, selected markets
Formalised module list	IoT Journey catalogue of labelled devices (Assessed, Connected, Approved)	Vodafone IoT validated module list	T-Mobile IoT validated module list
Associated IoT platform	Live Objects (Datavenue suite)	Vodafone GDSP, Vodafone IoT Connectivity Platform	T-IoT, Cloud of Things, NB-IoT Cloud
eUICC RSP	SGP.02 on legacy base, SGP.22, SGP.32 depending on contract	SGP.22, SGP.32, SGP.02	SGP.22, SGP.32, SGP.02
Own public LoRaWAN	Yes, Orange network in France, committed at least until end of 2027	No, partnerships	No, partnerships
Cellular validation	Labels recommended, contractually required for some volume deployments	Yes for GDSP onboarding	Yes for T-IoT onboarding

For a device aimed at the three operators, the programme is not mutualisable: each operator conducts its own reviews and accepts or refuses separately. The common baseline remains GCF (Europe) and possibly PTCRB (for the North American leg where applicable).

Live Objects and the Datavenue suite

Live Objects is the Orange Business IoT platform, distinct from the validation programme. It addresses the application layer: device fleet management, data ingestion, API exposure, integration with customer IT systems. It is part of the Datavenue suite, which also includes the Datavenue Ready partner label and the Datavenue Market marketplace.

The typical functional scope:

• Device management. Provisioning of devices, lifecycle management, OTA firmware, state monitoring and diagnostics.
• Data ingestion. Reception of messages originating from cellular or LoRaWAN via IP, SMS, MQTT or CoAP, storage, event and alert management.
• Exposure API. Standardised APIs and notifications for the customers' business applications.
• Connectors. Towards Microsoft Azure, AWS and specific business applications.
• Multi-bearer. Cellular 4G/5G, LTE-M, NB-IoT depending on the country, Orange LoRaWAN, handled homogeneously on the API side.

A device labelled by Orange is not necessarily connected to Live Objects. Conversely, Live Objects may ingest data from varied devices via its standard APIs. The distinction matters: the validation looks at the network behaviour and consumption of the device, Live Objects looks at the application sequence, and only the Orange Approved label includes Live Objects integration in its test scope.

The Datavenue Ready label, carried by the Orange partner programme, attests that a device has been tested with the Live Objects platform, and Datavenue Market allows buying devices, connectivity and platform access to start a project.

Cellular technology coverage

The Orange validation programme covers the technologies deployed by group affiliates, with varying intensity by country.

Technology	Typical Orange bands	Use cases	Availability
LTE Cat-1 / Cat-1bis	B3 1800 MHz, B7 2600 MHz, B20 800 MHz, B28 700 MHz, B8 900 MHz	Tracking, telematics, gateways, VoLTE voice	France and most affiliates
LTE-M (Cat-M1)	B20 800 MHz in France	Low-power mobile objects, alarms, connected health	France (more than 99% of the metropolitan population), Belgium, Spain, Poland, Romania notably
NB-IoT (Cat-NB1, Cat-NB2)	B8 or B20 depending on the country	Fixed low-power sensors, metering, agriculture	Not in France, deployed notably by Orange in Belgium and Luxembourg
5G NR NSA	n78 3.5 GHz primarily, n28 700 MHz for coverage	Very high throughput, low latency	France and European markets, deployment ongoing in Africa
5G NR SA	n78, n28	Slicing, URLLC, critical IoT	France in deployment, other markets to follow
GSM/2G	B8 900 MHz, B3 1800 MHz	Legacy M2M, in retreat	Metropolitan France: shutdown in waves in 2026, 3G from end of 2028, distinct calendars elsewhere

The bands effectively available in a given country are set by the local regulator (ARCEP in France, ANRT in Morocco, ART in Cameroon, INT in Tunisia and so on). A device intended for the Orange France market and the Orange Cameroun market must support the common band subset or be declined in two variants.

For the technology dimension of the bearers and the LTE-M vs NB-IoT difference, see the spilma glossary.

The Orange LoRaWAN network

Orange operates, in parallel with its cellular network, a public LoRaWAN network on the French territory, with an announced coverage of around 95% of the population. Orange confirmed in 2023 that this network will be maintained in France and Reunion at least until 31 December 2027. This network is part of the LoRa Alliance ecosystem: the gateways operated by Orange are connected to a LoRaWAN core network operated by Orange, and candidate devices must be LoRaWAN Certified by the Alliance via LCTT testing.

A few structural points:

• Spectrum. The Orange LoRaWAN network uses the EU868 band (863-870 MHz), regulated by ARCEP and subject to the ETSI EN 300 220 duty cycle.
• Device certification. Admission on the Orange LoRaWAN network requires a valid LoRaWAN Certified certification for the EU868 regional pack. RED radio certification remains mandatory and is not covered by the Alliance.
• Network profile. Orange may impose ADR settings, payload size constraints and transmission windows aligned on its capacity planning.
• Compatibility with other LoRaWAN networks. A LoRaWAN Certified device remains, as a general rule, portable between public networks, subject to the frequency plan, the join parameters and the commercial conditions.

The history of the French market deserves a marker: Bouygues Telecom announced in 2022 the end of LoRaWAN commercialisation by its Objenious subsidiary and targeted a network shutdown at the end of 2024. The Objenious LoRaWAN assets were finally taken over in late 2023 by Sweden's Netmore Group, which operates and expands this network in France, while part of the customer base migrated to Orange or to private networks. The consequence for a device initially designed for Objenious: verify that the network profile (DevEUI, JoinEUI, AppKey, ADR parameters) is portable to the target core. See also LoRa Alliance, certification programme for the Alliance scope.

eUICC and RSP, Orange requirements

Orange is aligned on the GSMA standards for eSIM and RSP management. The three branches of the architecture coexist in the base:

• GSMA SGP.02 on the legacy M2M base, in gradual retreat. Push-mode architecture, central SM-SR, downloads driven by the operator.
• GSMA SGP.22 for consumer products and some devices with a UI, pull-mode, LPAd on the device side, SM-DP+ and SM-DS on the operator side.
• GSMA SGP.32 for new IoT deployments without a user interface, with eIM (eSIM IoT Manager), IPAd on the device side and IPAe on the eUICC side.

For a new headless industrial IoT device, the industry's technical target is SGP.32, to be confirmed with Orange Business depending on the contract and deployment calendar. The eUICC profile must be installed on a GSMA SAS-UP certified eUICC, and the LPA or IPA on the device side must correctly dialogue with the operator's SM-DP+. A robust eSIM verification plan, to run before and during validation, typically includes:

• LPA to operator SM-DP+ handshake;
• profile download, activation, disable, deletion;
• behaviour on network failure during download (rollback, exploitable error log);
• multi-profile handling if relevant (Orange France and Orange African affiliate on the same eUICC).

The classic mistake is to integrate a GSMA-certified eUICC but a non-compliant proprietary LPA. The LPA must be certified or, more often, inherited from the cellular module when the module embeds one. See Verizon Open Development, eUICC for the North American counterpart, and the spilma glossary for the definitions ES9+, ES10b, IPAd, IPAe.

Orange Business managed connectivity and roaming

The Orange Business IoT Managed Global Connectivity offer aggregates SIMs, attachment policies, APN rules and billing for cellular IoT fleets. It covers:

• Multi-IMSI / steered roaming. An Orange SIM can switch between IMSIs depending on the country of attachment, to optimise cost and quality of service.
• Dedicated APNs. To separate IoT traffic from consumer mobile traffic, with possible firewall, QoS and static IP rules.
• Roaming between Orange affiliates. Moving from Orange France to Orange Cote d'Ivoire or Orange Maroc benefits from intra-group agreements, but the boundary behaviour remains to be verified.
• Partner roaming. Beyond the group affiliates, Orange has roaming agreements with third-party operators. Not all of those partners necessarily support LTE-M or NB-IoT, and the expected bearer may fall back to generic LTE or to 2G where the LPWAN profiles have no agreement.
• Management APIs. Activation, suspension, reactivation of SIMs, exposed via the Orange Developer APIs (Live Objects, IoT Managed Global Connectivity).

The roaming topic is central for mobile devices that cross borders. An Orange deployment review typically includes a mapping of target countries, of expected bearers in each country and of the applicable roaming agreements.

Orange validation journey

The typical journey to submit a device to Orange Connected Validation involves several steps, the duration of which depends on the complexity of the product and on the number of affiliates targeted.

1. Prerequisites. GCF certification obtained or planned for cellular devices, RED compliance in Europe or local regulatory compliance in the target country, GSMA SAS-UP certified eUICC if the product embeds an eSIM.
2. Commercial framing. Opening of a contact with Orange Business, definition of the scope (France, Europe, Africa), of expected bearers (LTE Cat-1, LTE-M, NB-IoT depending on the country, 5G, LoRaWAN), of expected volumes and of possible Live Objects integration.
3. Submission. Contact via device.validation@orange.com and provision of the dossier: product documentation (CE certificate, technical specifications, user guides), GCF and RED reports, eUICC profile and LPA where applicable.
4. Phase 1, maturity assessment. Documentary verification, basic functional tests and network connection test.
5. Phase 2, in-depth validation. Testing in an Orange Innovation laboratory or an approved partner laboratory: network interoperability, roaming, energy consumption, field tests.
6. Label and listing. Award of the label (Orange Assessed, Orange Connected or Orange Approved), delivery of the Orange connectivity certificate, possible listing in the IoT Journey catalogue.
7. Lifecycle. The Orange Connected and Orange Approved labels are tied to the tested hardware and firmware versions: any significant evolution of the cellular stack, the firmware or the LPA calls for a revalidation.

Orange does not publish a contractual SLA on the validation duration. Qualitatively, count several weeks to a few months depending on complexity and on the number of affiliates targeted. For the global cost-schedule perspective, see certification costs and certification timeline.

ARCEP and the regulatory dimension

Orange validation is an operator programme. It does not substitute for the regulatory dimension, which in France is the responsibility of ARCEP for spectrum and of the European Commission via RED for placement on the market.

The breakdown:

• Regulator (ARCEP, European authorities, African authorities): issues the band usage authorisation to the operator, sets the conditions for placement on the market of terminal equipment (RED in Europe).
• Operator (Orange): operates the network, decides which equipment it labels and lists, in compliance with regulatory constraints and with its own technical policies.
• Device manufacturer: must satisfy both. RED or equivalent local compliance for placement on the market, Orange validation for a serene deployment on the network.

For the African affiliates, the regulator is local (ANRT in Morocco, ARTCI in Cote d'Ivoire, ART in Cameroon, ARTP in Senegal, NTRA in Egypt, TRC in Jordan and so on). The Orange validation programme can be common to the group, but the regulator side is multiple. A pan-Orange Africa dossier must be aligned on each national authority in addition to the operator validation.

Frequent pitfalls

Assuming Orange France covers Orange Africa

The most costly mistake in commercial framing. Orange Africa networks are separate national networks, operated by affiliates with their own cores, bands and policies. A device validated for Orange France is not implicitly valid on Orange Mali or Orange Cameroun. If the commercial target is pan-Orange Africa, this must be framed from the start with country-level reviews planned.

Confusing the Orange validation and Live Objects

Orange Connected Validation = device labels and validation. Live Objects = application platform. The two can be contracted together or separately. Validation can be done without engaging Live Objects, and a Live Objects connection does not waive validation. The confusion leads to muddled contractual framing and unnecessarily long test periods.

Underestimating the eUICC topic

A GSMA-certified eUICC without a compliant and certified LPA compromises the eSIM deployment and the Orange review. This is the same pitfall as on Verizon Open Development. Practical rule: use the LPA embedded in the cellular module when that module is qualified, or select a third-party LPA certified SGP.22 or SGP.32, and do not reimplement a proprietary LPA.

Designing an NB-IoT device for France

Orange France does not operate an NB-IoT network: the strategic choice is LTE-M plus LoRaWAN. An NB-IoT-only device aimed at Orange France has no bearer. Either switch the design to LTE-M or LoRaWAN, or target an operator or a country where Orange NB-IoT exists (Belgium, Luxembourg notably). For NIDD use cases, support depends on the core network of each country and must be tested end to end where NB-IoT is actually used.

Confusing Orange LoRaWAN and private LoRaWAN networks

Orange operates a public LoRaWAN network in France. A device on this network must be LoRaWAN Certified for the EU868 pack and commercially connected to Orange. A private LoRaWAN network (ChirpStack stood up by an industrial site, or community The Things Network) does not require Orange validation. Confusing the two leads to incorrect framing of the certification programme.

Ignoring the Objenious history

Projects engaged on the Objenious network before its commercial shutdown may still have devices in the field with a legacy LoRaWAN parameter set. That network is now operated by Netmore Group, and a migration to Orange or to another operator is not automatic: it requires a review of the ABP or OTAA profile, of the keys and of the frequency plans. Manufacturers concerned must include this topic in their lifecycle.

Ignoring the partner roaming dimension

Orange roaming agreements with third-party operators do not cover all bearers. An LTE-M device that roams in a country where Orange has no LTE-M agreement will fall back to generic LTE or to 2G where available, keeping in mind that 2G disappears in metropolitan France in 2026. This behaviour must be tested, and the firmware must handle the fallback cleanly.

Launching production before validation

Orange validation takes weeks to a few months. Launching volume production before its obtention exposes the project to late hardware modifications (antenna, RF front-end) or firmware modifications (cellular stack, LPA, profile metadata) which impose another validation pass, the labels being tied to the tested versions. As everywhere in cellular, validation precedes volume production, not the other way around.

See also

• Vodafone Global IoT: device acceptance and eSIM
• Deutsche Telekom IoT: acceptance, nuSIM and Cloud of Things
• NTT DoCoMo, KDDI, SoftBank, Rakuten: Japan cellular
• China Mobile, Telecom, Unicom: cellular IoT acceptance

References and support

Working on cellular IoT module design suitable for Orange network validation for a real product? AESTECHNO can audit your design and certification plan. Get in touch →

See also PTCRB for the North American dimension, Vodafone Global IoT Acceptance, Deutsche Telekom IoT Acceptance for the other large pan-European operators, LoRa Alliance for the LoRaWAN side and the spilma glossary for definitions of GCF, eUICC, IPAd, SM-DP+, EU868.

Orange IoT programme

Let us frame your Orange validation dossier in 30 minutes.

AESTECHNO is the French electronics design house editing spilma and designing cellular and LoRaWAN IoT modules suitable for validation on the Orange France and Orange Africa networks. Audit of the validation plan, of the module choice, of the LPA and of the eUICC target, free of charge, by video call.

Book a cellular audit

Sources & references

1. Orange Connected Validation, IoT Journey , Orange iotjourney.orange.com/en/catalogue/orange-connected-validation
2. Validation of devices, Orange labels, IoT Journey FAQ , Orange iotjourney.orange.com/en/support/faq/validation-of-devices-:-orange-labels
3. Live Objects, IoT platform , Orange Business www.orange-business.com/en/solutions/data-intelligence-iot/live-objects
4. Orange LoRa coverage , Orange Business www.orange-business.com/fr/reseau-iot
5. PTCRB Certification Program , PTCRB www.ptcrb.com/
6. GCF, Global Certification Forum , GCF www.globalcertificationforum.org/
7. GSMA eSIM specifications hub, SGP.22 and SGP.32 , GSMA www.gsma.com/esim/
8. LoRa Alliance, certification programme , LoRa Alliance lora-alliance.org/lorawan-certification/