Definition and Objectives
RedCap (Reduced Capability) is a terminal type defined by 3GPP in 5G NR. By limiting maximum bandwidth, number of MIMO layers, duplex mode, etc., it makes chip and module costs, size, and power consumption lower than eMBB smartphone-class terminals, while still providing better potential than LTE Cat.1 and 5G network features. It is suitable for medium-speed IoT scenarios such as industrial wireless sensors, wearables, and surveillance cameras.
Distinction from eMBB and NB-IoT
RedCap is not a narrowband solution to replace NB-IoT, but a 5G terminal intended for use cases needing IP connectivity and a certain throughput, without requiring smartphone-level performance. Compared with LTE Cat.1/Cat.4, its long-term value lies in being integrated into the 5G network and slicing system, provided that the operator network and module ecosystem are mature.
Deployment Notes
It is necessary to confirm the NR coverage and RedCap feature switches in the target area; the module antenna and RF should still be designed according to 5G certification requirements. Early in the project, compatibility tests with the existing network and SIM card strategies should be conducted.
Engineering Practice Supplement
Regarding the implementation of '5G RedCap' in IoT and cellular module engineering, it is recommended to document network constraints (target market frequency bands and decommission plans, APN and private network strategies, roaming and tariffs, PSM/eDRX power-saving modes) and terminal constraints (antenna and RF layout, power ripple and surge, thermal design and derating, EMC/safety standards) as acceptance criteria during the project initiation phase. During R&D, use weak network simulation, high/low temperature, and voltage offset to reproduce boundary faults, keeping logs and waveforms; in mass production, establish batch and calibration traceability, and for component replacements, follow change review procedures. After launch, include connection success rate, number of reconnections, latency, and power consumption in the operational dashboard, with anomalies traceable to version and batch.
The following are additional tips related to cellular IoT project delivery: it is recommended to keep screen recordings of typical scenarios, screenshots of key indicators, and summaries of masked packet captures during the acceptance phase; in the mass production phase, change records should be kept for software and hardware versions, calibration parameters, and key component batches to facilitate problem attribution, customer audits, and long-term maintenance. When payment or personal information is involved, also check whether log masking and key rotation strategies are executable.
Bandwidth and Duplex Tradeoffs in a Reduced Device
RedCap is a class of terminal capability in 5G New Radio. It is not a new SIM and not an application protocol. It lowers RF and baseband complexity below a handset-class wideband terminal by limiting maximum channel bandwidth and downlink MIMO layers, and by allowing half duplex, while still camping on a 5G cell and using 5G core procedures. It is aimed at a middle rate in both directions, such as industrial sensing, wearables, and ordinary video. It is not extremely low-rate meter reading, and it is not handset peak throughput. Half duplex means transmit and receive cannot happen at the same time. The scheduling and delay model differs from a full-duplex wideband terminal. The antenna still has to be designed for the target 5G bands. "Reduced capability" is not a reason to keep a size that covers only 4G.
The condition of use is that the base-station software on the target cell has this class of terminal enabled, that the core network and the subscription allow access, and that the module version matches the network version. An early network may enable it only on some frequencies and in some cities. If the project needs network slicing or a separate service flow, also confirm that the reduced terminal's protocol stack exposes those capabilities, rather than reading that they exist only in a handset-chip manual.
Camping Behavior When the Feature Is Not Enabled
The most common error is a lab pass on a trial network that already has the feature on, then a field base station that does not recognize the capability. The terminal searches repeatedly or falls back to another radio access technology, and the note says antenna fault. The second is to use it as a replacement for an extremely low-power narrowband design. Half duplex and a wider receive bandwidth change both sleep current and dependence on the network. A battery budget estimated as narrowband meter reading will not be enough. The third is to reserve certification and antennas for the channel count of a full wideband terminal, so cost does not fall, or the opposite: too few receive antennas, so once the live network enables the feature, throughput and sensitivity miss the module's stated figures.
Whether a service can actually be given a different priority is not decided by the terminal alone; see QoS and service flows. Reduced capability does not change the basic move between idle and connected. Frequent small packets still cost signaling; see RRC states.
The selection record should state whether the target cell already allows this class of terminal, and on which bands and duplex mode. Writing that the module model supports it is not enough. After the trial network passes, run at least registration, uplink, downlink, and mobility samples on the live network where deployment is planned, and watch for fallback to another radio access technology. The transmit-receive switch that half duplex adds has to be counted in control delay. Do not write a handset's full-duplex delay into the requirement. Design antenna count and bandwidth to the real ceiling of this class of terminal. Do not reserve channels a full wideband terminal would use and this one will not, and do not omit receive antennas so that sensitivity is short once the live network enables the feature. If the service is still extremely low rate and can be unreachable for a long time, compare whether a narrower power-saving mechanism fits better. Do not replace a meter-reading design because the name contains a fifth generation. Bind network version, subscription policy, and module version in one commissioning check. A failed field search then does not start by taking the antenna apart. If the half-duplex switch was not counted in control delay, an idle result on the trial network cannot be written down as the live-network figure. If the live network enables this terminal class only on some frequencies, the drive-test record should name the frequency and the base-station software version. One successful registration does not mean the whole area is available.