5G helps when its coverage, mobility, uplink capacity or managed network features solve a real application problem. Compare the requirement first, then ask which device, network and operating model can meet it.
Compare the ten applications
| Application | Useful benefit | Prerequisites and alternatives | Evidence to request |
|---|---|---|---|
| 1. Connected mobility | Mobile data, updates and cooperative awareness | Vehicle support; network or compatible direct V2X. Onboard processing remains a separate layer. | Exact service, route, participant support and outage behavior. |
| 2. Smart cities | Connect distributed cameras and mobile teams | Power, permissions, privacy and maintenance. Fiber, Wi-Fi or low-power networks may fit fixed devices. | A measurable public-service outcome and ongoing operator. |
| 3. Connected care | Data access for mobile clinical workflows | Supported equipment and clinical governance. Wired broadband or Wi-Fi may already meet the task. | Validated workflow, coverage and continuity requirements. |
| 4. AR and VR | Mobile access to content or nearby rendering | Compatible headset, software and compute. Local rendering or Wi-Fi can suit bounded spaces. | End-to-end response, visual quality and battery use. |
| 5. Industrial automation | Connect moving equipment and changing layouts | Engineered network, supported modems and integration. Compare industrial Ethernet and Wi-Fi. | Representative-load pilot and application acceptance criteria. |
| 6. IoT and RedCap | Cellular connectivity for intermediate device needs | Module and deployed network support. Compare LTE-M, NB-IoT and other appropriate options. | Power profile, certification, coverage and service lifetime. |
| 7. Drones | Send telemetry or inspection imagery | Mission-compatible radios, coverage and lawful operation. Other command links may remain essential. | Coverage in the operating volume and validated loss-link behavior. |
| 8. Cloud, edge and APIs | Connect applications to placed compute or network capabilities | Available service/API, identity and application integration. Regional cloud may be sufficient. | Supported region, service terms and measured complete response. |
| 9. Wearables | Connectivity away from a companion phone | Compatible modem, plan and power budget. Bluetooth plus a phone may be simpler. | Actual battery/runtime and device/carrier support. |
| 10. Entertainment and media | Mobile viewing, contribution and venue production | Sufficient capacity in the required direction. Fixed links or venue Wi-Fi may be suitable. | Busy-event performance, upload stability and recovery. |
This is a requirements comparison, not a deployment ranking. Ordinary mobile data is widely used, while a bounded industrial installation, an advanced V2X feature and a remote clinical system each require their own evidence. A successful demonstration establishes what happened in its stated setup.
Mobility and public infrastructure
Connected vehicles can exchange maps, diagnostics, traffic context and fleet records. The connected-car guide separates cloud services, direct messages and onboard processing. For mobile links, route continuity matters alongside peak throughput: tunnels, changing beams and cell transitions affect the experience.
City projects should begin with the public task, such as collecting maintenance data or improving access to a service. Camera streams and occasional sensor reports have different power and traffic needs. Specify retention, access, coverage, ownership and the cost of replacing devices over the project’s life. Useful connectivity supports a service that someone can operate and evaluate.
Connected care and immersive applications
A mobile clinic, ambulance data workflow or remote consultation may benefit from cellular access where a fixed connection is impractical. The service must be designed and validated for its clinical purpose, with appropriate equipment, privacy and continuity arrangements. This connectivity overview provides no clinical procedure or basis for relying on public mobile service for a safety-critical intervention.
AR and VR place different demands on rendering location, media rate, interaction delay and battery use. Test the complete headset-to-application path. Moving compute to an edge location helps only when the resulting route and processing behavior improve the intended experience. A responsive speed-test page is weak evidence about a rendering pipeline.
Industrial networks, IoT and wearables
Factories and logistics sites can evaluate private 5G for mobile equipment, inspection traffic and flexible layouts. The factory guide supplies a pilot brief with workload, acceptance and ownership questions. Treat the application requirement as the basis for comparing wired and wireless designs.
3GPP’s RedCap overview describes reduced-capability NR devices introduced in Release 17 for use cases between very simple IoT and full broadband devices. Reduced capability is a specific device profile, not a guarantee of a particular battery life. Check modem support, network availability, sleep behavior, reporting frequency and data allowance.
A wearable that sends occasional status reports has a different power budget from a body camera or an immersive headset. Measure the intended duty cycle and weak-signal behavior. Direct cellular service can reduce dependence on a nearby phone, while a companion-phone design can remain practical for other tasks.
Remote operations and media
Drones may use cellular links for selected telemetry or payload-data tasks. A usable ground-level coverage map does not establish aerial coverage. Mission design must address supported equipment, the operating volume, loss-link behavior and applicable aviation rules; a 5G connection alone authorizes no flight operation.
Media viewing mainly consumes downstream data. Live contribution and production cameras require sustained uploads, suitable encoding and a plan for congestion or link failure. The two-way performance guide provides a worked capacity example. At a crowded venue, ask what capacity is actually reserved or engineered for the service and how it is measured.
Check the enabling architecture
3GPP’s system overview explains the functions behind a 5G service. Standalone core support, device compatibility, service policies and application integration determine which advanced capabilities can be used. Slicing and network APIs require a supported offering and an agreed service behavior; a phone’s 5G icon supplies much less information.
Release 18 introduces the 5G-Advanced phase; Release 19 continues it. A standards release describes specified capabilities. Ask an operator or vendor for the exact implemented feature, version, supported devices and region. Compute and routing and Cloud RAN architecture explain two different parts of that system.