_Technical Paper_

Open RAN and the Machines - NB-IoT

NB-IoT was first introduced by 3GPP many countries and serves millions of officially approved the full NB-IoT
in 2016. It is one of the low power wide subscribers (IoT devices). According specification. The s olution we
area (LPWA) networks defined by to GSMA, as of Feb. 2022, there are present is a pre-standard solution
3GPP for Internet of Things (IoT) 110 NB-IoT networks around the which is agreed upon with a close DU
applications. NB-IoT is the foundation globe. software partner, that aligns with
for applications like remote metering, For Open RAN to be deployed in where we believe the standard is
environmental monitoring and other brownfield networks, NB-IoT is a heading.
sensor networks which rely on battery mandatory feature to reach service NB-IoT can be deployed in guard-
powered IoT devices. The standard parity. To maximise the depth and band and in-band modes, so the
enables the much-needed energy- breadth of the NB-IoT coverage, an solution should be able to handle
saving and extended coverage MNO usually deploys it in a low- both scenarios.
features that match the application frequency FDD band like 800MHz.
scenarios. This technology has since Although it is a very important feature
been deployed by many operators in for Open RAN networks, the O-RAN

Downlink User Plane

In the DL user plane, there are LTE carriers, Comba is using the depicts, the NB-IoT carrier will
mainly two solution alternatives, common endpoint in our solution have a higher power density than
one is using a separate endpoint, to handle guard band NB-IoT the LTE carrier. The O-RU will allow
while another is using a common carrier and use an extended PRB a maximum of 6dB higher power
endpoint for both NB-IoT and LTE space approach that can be used for the NB-IoT carrier.
c a r r i e rs. S i n ce f ro m t h e R U to indicate the guard band NB-IoT
perspective, NB-IoT is similar to carrier. As the below diagram

Guard-band and In-band NB-IoT carriers with host LTE carrier

Note: The subcarrier spacing depicted represents the downlink 15kHz SCS used for both LTE and NB-IoT, while NB-IoT
would use either 15KHz or 3.75KHz in the uplink.

© 2023 Comba Group. All rights reserved. comba-ctnsl.com

_Technical Paper_

Uplink User Plane and RACH

In the uplink, there are NPUSCH and of 15kHz SCS, it is similar to the normal remove and when to add the Cyclic
NPRACH functions. O-DU has to LTE. However, for 3.75kHz SCS, we prefix (CP) packets.
distinguish the NB-IoT RACH from must use a separate endpoint. According to the O-RAN standard, a
the LTE carriers RACH, because NB- control plane packet should be
IoT RACH has multiple repetitions, to THE CONTROL PLANE provided for every TTI or subframe,
enhance the coverage area. To While the user plane is simple, the however, as mentioned above,
handle this different, separated control plane is more complicated. NPRACH has multiple reptitions, and
endpoint is inevitable. Therefore, the One of the main functions of the the NPUSCH subframe duration is
solution uses different eAxC IDs for control plane is to manage how the O- not aligned with the NPRACH groups.
the NPRACH and PRACH. RU processes the signal, for example,
For the NPUSCH U plane packets, in one can instruct the O-RU when to

NPUSCH
1 2 3 4 5 6 7
0.5ms

NPRACH
group 1 group 2 group 3 group 4
symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol symbol
CP 1 2 3 4 5 CP 1 2 3 4 5 CP 1 2 3 4 5 CP 1 2 3 4 5

0ms 1.396ms 2.792ms 4.188ms 5.548ms

0ms 1.596ms 3.192ms 4.788ms 6.348ms
1 preamble
Misalignment of normal TTI frame and NPRACH frame

Given the above, Comba and our DU NETCONF NETCONF

partner defined a method to align the Server (O-RU) Client (O-DU/SMO)

timing of NPRACH by customized NETCONF Hello/Capabilities

Netconf Hello/Capabilities
control plane packet which ensures Static-low-level-tx-endpoint with endpoint-type capable of NB-IOT
Static-low-level-rx-endpoint with endpoint-type capable of NB-IOT
that the O-RU can timely know how to
U-Plane Configuration
group the symbols and how many Number-of-prb-per-scs,
Check which NB-IoT
configuration is
tx-array-carriers, supported
repetitions there are in the NPRACH rx-array-carrier

that the DU has configured. Internal signal

calibration; Setting up the
carrier parameter
“State” ready

Configure “active” active

THE MANAGEMENT PLANE
(Image 1)
The management plane covers both
in-band and guard-band operation of
multiple NB-IoT carriers with the host LTE Channel Bandwidth Start PRB num Stop PRB num
carrier. It follows the sample user 10 MHz 0 51
plane configuration procedure as LTE 20 MHz 0 105
or NR.
(Image 2)
As per the endpoint capability
(Image 1), a new entry in the Yang RADIO UNIT The O-RU can then use a common
model is also required. To keep the As mentioned in the DL User plane, gain control for both LTE and NB-IoT
minimal modification in our solution both in-band and guard-band NB-IoT carriers.
before the O-RAN specification is carriers will transmit at a higher power Another important feature in the O-
finalized, only the endpoint type “NB- level than the LTE carrier, and the O- RU is the shaper digital filter design
IoT” is introduced to represent O-RU RU will allow +6dB power for the which allows extra PRB at the edge of
support NB-IoT. N B - I O T c a r r i e r. To u n i f y t h e the LTE channel bandwidth for the
The extended PRB value will be implementation, it is expected that the guard band NB-IoT deployment.
presented to indicated guard-band DU sends a higher power scale of the
NB-IoT (Image 2). input IQ symbol to the O-RU.

© 2023 Comba Group. All rights reserved. Contact us for more: [email protected]