Whatisreducedcapability（RedCap）NR？
到⽬前为⽌，在⽀持5G的设备的服务，订购和可⽤性⽅⾯，5G的推出速度已经超过了4G长期
演进（LTE），这在最新的《爱⽴信移动性报告》中已清楚地表明了这⼀事实。此外，在未来⼏年中，预计5G背后的势头将继续强劲，预计2026年5G⽤户将达到35亿。
推动5G快速增长和迅速采⽤的引擎是其⽆线接⼊技术。作为新电台（NR）。5G NR的灵活性和可扩展性 makes it possible to introduce timely enhancements to address new u cas to
help expand the 5G ecosystem and connect more and more devices to the network. One recent example is NR support for reduced capability (RedCap) devices. This work item has recently been approved in the 3GPP RAN plenary in December 2020 and the feature will be introduced in 3GPP Relea 17. The introduction of reduced capability NR devices can facilitate the expansion of the NR device ecosystem to cater to the u cas that are not yet best rved by current NR specifications.
U cas
The u cas that motivate the specification work on NR RedCap include wearables (e.g. smart watches, wearable medical devices, AR/VR goggles, etc.), industrial wireless nsors, and video survei希拉穆仁
llance. The key requirements of the u cas, described in the 3GPP document RP-202933, “New WID on support of reduced capability NR devices”, are summarized in Table 1. To maximize the benefit of economies of scale, it is desirable that all the three u cas can be addresd by a common NR RedCap framework.
Table 1: Requirements of wearables, industrial wireless nsors, and video surveillance u cas
Referring to Table 1, the three u cas have less stringent data rate requirements than enhanced mobile broadband (eMBB) u cas, and do not require tight or deterministic latency requirement as time-critical communications u cas. Therefore, starting from the Relea 15 NR devices as a baline, there is room for trading off device capabilities for complexity or cost reduction.
什么是渣男
On the other hand, the u cas have very different requirements than the low-power wide-area (LPWA) u cas currently addresd by the LTE-M and NB-IoT solutions. For example, the data rates need to be higher than for LPWA. Furthermore, there is a constraint on device form factor for certain wearable u cas. The consideration of u-ca requirements drives the choices of key physical-layer parameters for RedCap. The choices have a direct impact on the complexity and cost of the device hardware platform. We foree that RedCap devices will be positioned as a lower gment than eMBB, but higher than LPWA devices.
The technology positioning of RedCap is illustrated in Figure 1. Generally speaking, RedCap去火食物
is positioned to address u cas that are today not best rved using eMBB, ultra-reliable
low-latency communications (URLLC) or LPWA solutions.
Figure 1: Illustration of technology positioning of RedCap in relation to eMBB, URLLC, and mMTC.
Reduced device capabilities
中班折纸So how is cost reduction achieved? The capabilities of a RedCap device compared to tho of Relea 15 NR devices are summarized in Table 2 and illustrated in Figure 2. Bandwidth reduction, reducing the maximum number of MIMO layers, and the relaxation of the maximum downlink modulation order all help reduce baband complexity. Reducing the minimum number of required receive branches and allowing half-duplex (HD) operations in all bands help reduce the bill of material costs in terms of antennas and RF components. Each of the reduced capability features are described in more details below.
Table 2: Device capabilities, Relea 15 baline NR devices versus Relea 17 RedCap devices.
长痘吃什么
Figure 2: Illustration of the differences between RedCap device and baline NR device capabilities.
奢侈品的包包Maximum device bandwidth: A baline NR device is required to support 100 MHz in frequency range 1 (FR1), and 200 MHz in FR2, for transmission and reception. For RedCap, the requirements are reduced to 20 MHz and 100 MHz, respectively. Such bandwidth reductions however still allow all the physical channels and signals specified for initial acquisition to be readily reusable for RedCap devices, therefore minimizing the impact on network and device deployment when introducing RedCap to support the new u cas. Minimum number of device receive branches: The number of receive branches is related to the number of receive antennas. Reducing the number of receive branches therefore results in a reduction in the number of receive antennas and cost saving. The requirements on the minimum number of receive branches depends on frequency bands. Some frequency bands (most of the FR1 frequency-division duplex (FDD) bands, a handful of FR1 time-division duplex (TDD) bands, and all FR2 bands) require a baline NR device to be equipped with two receive branches, whereas some other frequency bands, mostly in the FR1 TDD bands, require the device to be equipped with four receive branches.
For the bands where a baline NR device is required to be equipped with a minimum of two receive branches, a RedCap device is only required to have one receive branch. For the bands where a baline NR device is required to be equipped with a minimum of four receive branches, it is yet to be decided whether a RedCap device is required to have one or two receive branches.
Maximum number of downlink MIMO layers: The maximum number of downlink MIMO layers for a RedCap device is the same as the number of receive branches it supports. This is a reduction compared to the requirements for a baline device.
Maximum downlink modulation order: A baline NR device is required to support 256QAM in the downlink in FR1. For a RedCap device, the support of downlink 256QAM is optional. For FR1 uplink and FR2, both downlink and uplink, a RedCap device is required to support
64QAM, same as the requirement for a baline device.
田奇念什么Duplex operation: Regarding duplex operations, the only relaxation is for operations in FDD bands. A baline NR device is required to support a full duplex (FD) operation in an FDD band, i.e., transmitting and receiving on different frequencies at the same time. A typical full-duplex device incorporates a duplex filter to isolate the interference between the device’s transmit and receive paths. In practice, the same device may need to support multiple FDD bands; therefore, multiple duplex filters may be needed to support the FD-FDD operation.
对于RedCap设备，对FD-FDD的⽀持是可选的，即，在上⾏链路频率中传输时不需要在下⾏链路频率中接收，反之亦然。这种双⼯操作称为半双⼯FDD（HD-FDD）。HD-FDD消除了对双⼯滤波器的需
求。取⽽代之的是，可以使⽤开关选择发射器或接收器以连接到天线。由于交换
机⽐多个双⼯器便宜，因此可以节省成本。
此外，预计RedCap设备⼀次只能在单个频带中运⾏，并且将不⽀持载波聚合和双重连接。
根据3GPP中的研究，表3总结了相对于基线NR设备的物料清单成本和复杂性指标的总体降低。可以看出，可以实现成本和复杂性的⼤幅降低。这有助于将RedCap建⽴为与eMBB或时间紧迫的通信设备段不同的设备段。
鉴于上述降低的功能，对于具有⼀个接收分⽀的设备，RedCap设备在FR1中⽀持85 Mbps的峰值物理层数据速率，⾜以满⾜预期⽤例的所有数据速率和等待时间要求。对于⽀持更多接收分⽀的RedCap设备，峰值物理层数据速率要⾼得多。
FR1 FDD FR1 TDD FR2
总减少量~65%如果RedCap设备⽀持2
个接收分⽀，则约为
58％
如果RedCap设备⽀持1
个接收分⽀，则约为
71％
~48%
表3：相对于基线NR设备，RedCap设备的成本/复杂性指标的总降低。
LTE到NR的迁移路径
3GPP Relea 17⽀持低容量NR设备的⼯作是进⼀步扩展5G NR潜在市场的重要⼀步。它使能⼒降低的设备能够在任何NR频带中运⾏。
值得⼀提的是，基于LTE的解决⽅案⽬前已解决了⼀些可穿戴和视频监控⽤例。对于这些⽤例，NR RedCap提供了从LTE迁移到NR的途径。这样的迁移路径很重要，因为它可以在未来数年内加速从LTE到NR的频谱重新分配。
从性能的⾓度来看，⽆论是⽹络还是设备，都存在采取从LTE到NR迁移的动⼒，因为RedCap 是本机NR技术，它涵盖了所有关键的NR构建块，包括波束成形，可扩展命理，⽹络能效
游戏怎么全屏
等。RedCap设备将⽀持在NR载波上完全共存，该NR载波已配置为针对eMBB或时间紧迫的通信性能进⾏了优化。
这对于⼯业⽆线传感器⽤例尤为重要，因为在⼯业4.0中实现全⾃动⼯⼚的⽹络需要同时⽀持与功能更强的设备和低端传感器设备的时间紧迫的通信。可以优化此类⽹络的配置，以确保时间紧迫的通信性能，同时要求低端传感器设备仍然有效运⾏。
