CR for TS 38.101-2 Rel-17 clarification on Redcap Applicability in FR2 power classes
Rel-17 · revised
23.501 · CR 3155 rev.1
Support RedCap UEs differentiation in 5GC
Rel-17 · approved
38.133 · CR 2467 rev.1
CR on applicability of requirements for RedCap Ues
Rel-17 · approved
38.822 · CR 0012 rev.1
UE Feature List for Rel-17
Rel-17 · approved
38.413 · CR 0675
CR for support of RedCap UEs for 38.413
Rel-17 · status unknown
38.133 · CR 2465
CR for introduction of RRC connection mobility control test cases in FR1 for RedCap Ues
Rel-17 · revised
38.413 · CR 0659
Introduction of RedCap eDRX over NGAP
Rel-17 · status unknown
38.133 · CR 3915
[NR_redcap] High priority search with eDRX in IDLE mode – R17
Rel-17 · status unknown
38.423 · CR 0670
Inter-node Coordination for RedCap over Xn
Rel-17 · status unknown
38.133 · CR 2465 rev.1
CR for introduction of RRC connection mobility control test cases in FR1 for RedCap Ues
Rel-17 · endorsed
38.822 · CR 0012
UE Feature List for Rel-17
Rel-17 · revised
Rel-98 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-98; they are not automatically attributed to the feature.
No CR activity targeting the mapped specifications is indexed for Rel-98.
Traceability limits
What this lineage is not claiming
The reviewed topic-to-specification mapping is Atlas-curated and non-normative even when its source is an official 3GPP record.
When an explicit stage classification is unavailable, specification layers are inferred from the TS/TR series and are labelled inferred rather than presented as official 3GPP stage assignments.
Connected Work Items and release-context Change Requests share mapped specifications; only the topic source Work Item is treated as primary evidence for the reviewed topic mapping.
This is traceability evidence and navigation, not a clause-by-clause normative feature definition.