Device capability

eRedCap devices

eRedCap continues the reduction in complexity and power for applications that need less capability than RedCap while retaining integration with the 5G system.

Device classFurther reduced 5G capability
5G SASA-oriented
Slice readinessCore design goal
Commercial availabilityEarly ecosystem

Where it fits

eRedCap continues the reduction in complexity and power for applications that need less capability than RedCap while retaining integration with the 5G system.

The useful question is not merely whether the radio can attach to 5G. It is whether the full device platform can register on the required SA network, present the correct subscription, request or accept the permitted S-NSSAI and establish the intended PDU session.

Capability chain

Check the modem chipset, RF bands, carrier aggregation profile, SA mode, firmware, operating system or router UI, SIM profile, operator certification and enterprise service contract. Any missing layer can prevent the intended behaviour.

Private APN versus slice

A private APN or DNN can provide addressing, routing and security separation without end-to-end network slicing. Conversely, a slice can still use a DNN to reach a particular enterprise data network. They solve related but different problems.

Procurement questions

  • Which modem and firmware version is installed?
  • Is 5G SA enabled for the required bands?
  • Can the host expose requested and allowed NSSAI information?
  • Has the exact hardware revision been certified by the operator?
  • How will support, updates and regression testing be handled?
Deployment rule: standards capability, device implementation, firmware exposure, SIM entitlement and operator service availability must all align. A tick beside “5G SA” is not proof that a device can use a commercial enterprise slice.