NDS VISBY Radio 6626 4466 4456

Ericsson Internal
Implementation Description 1 (431)

Prepared (Subject resp) No.
ENNADEG Andras Engel 566/102 68-300/FCP 131 4743 Uen

Approved (Document resp) Checked Date Rev Reference
2023-12-21 PF24
Authors:
Albert Wei (Radio 6626), Xu Tian (FDD Radio 4466) CA Radio
Yangu Liu (Radio 6626), Xingzheng Li (FDD Radio 4466), Siyu Ma(MR9268-sp1) Function System
Chao Huang V(Radio 6626), Jerry Yang T (Radio 6626), Yubin Jiang (FDD Radio 4466) DMS Driver
Xiaobo Su (Radio 6626), Juan Liao (FDD Radio 4466) Radio SW OPO
Xingyang Liu, CA CAT SPOC
Yuanfei Cai, Menghan Zhao, Edyta Pajor XQ, GSM G1 SPOC
Shan Jiang, WCDMA G1 SPOC
Dana Chen, RICR SPOC
Qiang He (Radio 6626), Edwin Hu (FDD Radio 4466), XCS SPOC
Daniel Derezinski, BI system,
Patrik Norman, ERS HW system,
Joakim Forsberg X, ERS HW system,
Hongxia Li, Lisa Wang(MR9268-sp1) Test Manager）
Xiaoyang Wang, Test Manager
Jimmy Huang R (Radio 6626), Biao Li (FDD Radio 4466), Lei Zhang I(MR9268-sp1) Integration Spoc
Olof Molander, BI NCR System
Shawn Mei, Security system
Johan Jacobsson M, Network Deployment (NRO)
Jorge Aduna, Customer support, Hardware Services
Peter Olander, Jeanette Lindblad, TrxCtrl SPOC
Bernadette Robinsion, Trade compliance Specialist
David Ge, Supply early phase Driver
Yi Jin, Packaging Spoc
Martin Schmidt, (MR9268-sp1) CPI System
Johan Klerborg, Piotr Sobczyk XX ECT system
Mary Mcmahon, Suresh Koukuntla, OSS/ENM System
Chakradhar Ghantasala, Apostolos Karadimitrakis (MR9268-sp1) DL Asic
Naga Thejus Mruthyunjaya, UL Asic
Lars Johansson B (Radio 4456), CA Radio
NDS VISBY Radio 6626 4466 4456
Abstract
Ericsson Internal

2023-12-21 PF24
Contents
1 Introduction.................................................................................................................5
1.1 Scope of NDS.................................................................................................5
1.2 Input Documents.............................................................................................8
1.3 Revision History..............................................................................................9
1.4 Tracking of Issues and Assumptions............................................................10
1.5 Technical Debt..............................................................................................13
2 Main Requirement (MR) and Solution Package (SP) Analysis.............................15
2.1 MR Background............................................................................................15
2.2 MR Scope Analysis.......................................................................................15
2.3 SP Description and Definition of Done..........................................................28
2.4 MR/SP Dependencies and Priority...............................................................32
2.5 Mapping of Detailed Requirements to SP(s).................................................36
2.6 Description of Feature/Functionality/Configuration.......................................37
3 Use Case (UC) Analysis...........................................................................................49
3.1 External RAN Node Impact and Network Level UC Analysis.......................49
3.2 RAN Level UC Analysis................................................................................49
3.3 Network Function UC Analysis.....................................................................49
3.4 Node Group UC Analysis..............................................................................49
3.5 Node Level UC Analysis...............................................................................49
4 Cost Estimates..........................................................................................................50
4.1 GSM G1 Specific Cost Estimation Summary................................................50
4.2 Cost for SP 10565-0937/09002-SP1............................................................52
4.3 Cost for SP 10565-0937/09002-SP4............................................................53
4.4 Cost for SP 10565-0937/8930-SP1..............................................................54
4.5 Cost for SP 105 65-0937/09609-1................................................................54
4.6 Cost for SP 10565-0937/09002-8.................................................................56
4.7 Cost for SP 10565-0937/09002-15...............................................................57
4.8 Cost for SP 10565-0937/09268-1.................................................................57
4.9 Cost for MR11742 Wind noise (Man-hours).................................................58
5 Realization Overview................................................................................................59
5.1 Description....................................................................................................59
5.2 System Class Descriptions...........................................................................59
5.3 Realizations...................................................................................................59
6 Impact on Behavior/Monitoring/Handling of the System......................................60
6.1 Licensing.......................................................................................................60
6.2 Network Impact.............................................................................................62
6.3 Standardized Interfaces and Ericsson Proprietary Interfaces.......................62
6.4 Algorithms.....................................................................................................62
6.5 Security/Privacy (mandatory)........................................................................62
6.6 Upgrade (SW Management).........................................................................63
6.7 Deployment and Customer Tools.................................................................64
6.8 Configuration Management (CM)..................................................................85
6.9 Performance Management (PM)...................................................................85
6.10 Fault Management (FM)................................................................................85
6.11 Diagnostics and behavioural observability....................................................86
Ericsson Internal

2023-12-21 PF24
6.12 Characteristics and Traffic Model.................................................................86

6.13 Migration.......................................................................................................86
6.14 Power Consumption......................................................................................86
6.15 Supply (Production).......................................................................................87
6.16 Services (Network Deployment & Customer Support)..................................87
6.17 Other technical areas....................................................................................88
7 Feature Interaction....................................................................................................89
8 Impact on SW Products............................................................................................90
8.1 Common........................................................................................................90
8.2 RC (Radio Control) Function Module............................................................91
8.3 RP (Radio Processing) Function Module......................................................91
8.4 PP (Packet Processing) Function Module....................................................91
8.5 LRAT_RC (LTE Radio Control) Function Module.........................................91
8.6 LRAT_BB (LTE G1 Baseband) Function Module.........................................92
8.7 WCDMA........................................................................................................92
8.8 GSM............................................................................................................137
8.9 EW CAT Function Module...........................................................................146
8.10 TN Function Module....................................................................................178
8.11 BBI Function Module...................................................................................178
8.12 RCS Function Module.................................................................................178
8.13 OSE Platform Function Module..................................................................178
8.14 ENM/OSS-RC.............................................................................................178
8.15 Radio SW....................................................................................................179
8.16 Radio Function System...............................................................................220
8.17 HW Abstraction Layer Interface (HALI).......................................................261
8.18 Site Support Software.................................................................................261
8.19 TRXCTRL....................................................................................................262
8.20 DL ASIC......................................................................................................263
8.21 UL ASIC......................................................................................................263
8.22 Radio XCS platform....................................................................................264
8.23 RICR...........................................................................................................266
9 Impact on HW Products.........................................................................................269
9.1 ERS HW Solution........................................................................................269
9.2 Radio...........................................................................................................300
9.3 XMU............................................................................................................312
9.4 P614............................................................................................................312
9.5 Digital..........................................................................................................313
9.6 Enclosure & Power......................................................................................313
9.7 Site..............................................................................................................323
9.8 Packaging Material Design.........................................................................324
9.9 Virtualization................................................................................................328
10 Impact on CPI..........................................................................................................329
10.1 General.......................................................................................................329
10.2 Input to Network Impact Report (NIR).........................................................329
10.3 Document List.............................................................................................330
11 Impact on Verification............................................................................................337
11.1 General.......................................................................................................337
11.2 FOA/FFI......................................................................................................340
11.3 Field Trial....................................................................................................341
Ericsson Internal

2023-12-21 PF24
11.4 IODT............................................................................................................341
11.5 Transport test..............................................................................................341
12 Impact on External Stakeholders..........................................................................342
12.1 Product Documents.....................................................................................342
12.2 Legal Aspects, Export Control and Third-Party Products (3PP).................343
12.3 Patent Ideas................................................................................................348
12.4 Future Enhancements.................................................................................348
13 Terminology............................................................................................................349
13.1 Abbreviations..............................................................................................349
13.2 Concepts.....................................................................................................349
14 References...............................................................................................................350
Ericsson Internal

2023-12-21 PF24
[1] (SYSFUNC Siyu)Introduction

The Radio 6626 is a 3-sector dual band radio with 6T6R/6T6R and totally 6
antenna ports. This is product variant of the Triple Band Radio platform
VISBY.
The FDD Radio 4466 is a type of Triple band radio with 4T4R/4T4R/4T4R and
totally 4 antenna ports. This is product variant of the Triple Band Radio
platform VISBY.
1.1 Scope of NDS
1.1.1 Description
This NDS covers the pre-study of the MRs:

 MR 105 65-0937/09002-SP1 Radio 6626 in Ericsson Radio Systems
(Visby Class B PV 6T6R/6T6R with 3 sector)
– MR 105 65-0937/09003 Radio 6626 66B1 66B3 C (Visby FV)
first release
 MR 105 65-0937/09002-SP4 Radio 6626 Low Band in Ericsson Radio
systems
– MR 105 65-0937/09176 Radio 6626 66B8 66B20 C (Visby Low
Band FV) first release
 MR 105 65-0937/08930-SP1 FDD Radio 4466 in Ericsson Radio
Systems (Visby Class B PV 4T4R/4T4R/4T4R)
– MR 105 65-0937/08932-SP1 FDD Radio 4466 B1B3B7 (Visby
FV) first release
 MR 105 65-0937/09609 FDD Radio 4456 in Ericsson Radio Systems
(Visby Class B PV 4T4R/4T4R/4T0R). Because of no additional FV for
the 4456 PV, the 4456 PV and FV have the same MR number
– SP 105 65-0937/09609-1 FDD Radio 4456 44B1C 44B3J
40B75C C (Visby FV) first release
Note: Because of no additional FV for the 4456 PV, the 4456 PV and
FV have the same MR number
 MR9268-SP1 LTE GB NB-IoT coexistence with ESS on Visby

Radios.
 MR 105 65-0937/10135-SP1 FDD Radio 6626 in Ericsson Radio
Systems (Visby Class C FV 6T6R/6T6R/6T6R)
– MR 105 65-0937/10135-SP1 FDD Radio 6626 B0A B28 C
(Visby FV) first release
Ericsson Internal

2023-12-21 PF24
1.1.2 Intended Release
The target SW release is as below.
 MR9002-SP1
G21.Q3, W21.Q3, L21.Q3, NR21.Q3, RBS21.Q3, Radio SW 21.Q3
Note：ESS is included in NR of RAN SW.
The target PRA release is as below.
21.Q3
 MR8930-SP1 FDD Radio 4466
21.Q4
 MR9002-SP4
22.Q2
22.Q2
 MR9268-SP1
22.Q4
Ericsson Internal

2023-12-21 PF24
1.1.3 Design Base
 MR9002-SP1
Following SW baseline are applicable:

 GSM G20.Q4
 WCDMA W20.Q4
 LTE L21.Q1
 RBS RBS21.Q1
 NR N21.Q1
 Radio SW 20.Q4
HW baseline is as below.
 BL 16A
 MR9002-SP4

 GSM G21.Q3
 WCDMA W21.Q3
 LTE L21.Q3
 RBS RBS21.Q3
 NR N21.Q3
 Radio SW 21.Q3
 BL 16A

 GSM G21.Q1
 WCDMA W21.Q1
 LTE L21.Q1
 RBS RBS21.Q1
 NR N21.Q1
 Radio SW 21.Q1
 BL 16A
Ericsson Internal

2023-12-21 PF24

 LTE L21.Q1
 RBS RBS21.Q1
 NR N21.Q1 (HW prepared for B75C)
 Radio SW 21.Q1
 BL 16A
 MR9268-SP1 LTE GB NB-IoT coexistence with ESS on Visby Radios.

 Radio SW 22.Q3
 BL 16A
1.2 Input Documents

Table 1: Input documents
Title Document Number
OA MR7341 Visby Platform 500/0363-200/

FCP1314743Uen
OA_MR8930 Radio 4466 4T4R TB_ MR9002 Radio 6626 501/0363-200/
6T6R DB 3-sector FCP1314743Uen
Visby Function IP 1/159 41-FCP 133
0875
Visby Radio DMS1 RTC presentation
Visby Radio DMS2 RTC presentation
Hardware Implementation Proposal for Visby Platform 2/15941-300/
FCP1330875
NDS VISBY Radio 6626 4466 4456 (SP5 for Quasi-Dynamic 534/102 68-500/FCP
PA VDD) 131 4742 Uen
OA report AAS G3 low power states link
NDS MR8881 AAS G3 mid-band radio deep sleep 610/10268-300/

FCP1314743
Ericsson Internal

2023-12-21 PF24
Title Document Number
Visby Radio 6626 Low band DMS2 RTC presentation

TA: DVSWR Tor sharing Link
OA report MR9609, Visby Radio 4456 Link
5G_NDS_PPS732_MR7602_LteNrFddSpectrSharingWithNBIo 602/102 68-500/FCP
T 131 4742 Uen
Solution Agreement of MR9002-SP13 140/03633-200/
FCP1314743Uen
1.3 Revision History

Table 2: Revision history
Revision Date Description
A 2021/01/22 MR9002-SP1&IR
B 2020/05/14 MR8930-SP1
C 2021/06/23 MR9002-SP3
MR9002-SP1 Remove GSM support for LMC of Radio6626
CPI impact update for MR09003-1 and MR08932-1, MR08930-
1
D 2021/06/29 MR8930-SP1 GSM G1 support Radio 4456.

MR9002-SP3 Add DRS and correction of the typos.
E 2021/08/27 MR9002-SP4 & IR for MR9002-SP4
F 2021-11-25 MR9609-SP1 added

ECT impact in chapter 6.7 updated (erakleb)
G 2022-03-04
Remove DUS from the requirement of Visby radios
Remove DVSWR impact on 4466. Revise TOR sharing solution
for Mongoose based products.
MR9002-SP8 ''25 Gbps CPRI Verification for
GSM/WCDMA''
MR9002-SP15 ''7CC per port on B3 UL for Visby Radio
H 2022-04-19
6626 B1B3 and Radio 4466 B1B3B40/B41''
Update section 2.6.4 to add limitation regarding AxC ID conflict
J 2022-06-22
between DUW on Data1 port and G2 BB and onward on Data3
port, and mulitple cascading link configuration
MR9002-SP8 scope change, remove single/mixed mode
WCDMA because BB G3.1 has problem to support WCDMA on
25Gbps CPRI
MR9268-SP1: LTE GB NB-IoT coexistence with ESS on Visby
PF25 2022-7-11
added.
MR9268-SP1: LTE GB NB-IoT coexistence with ESS on Visby
K 2022-8-30
added.
Ericsson Internal

2023-12-21 PF24
Revision Date Description

Remove RBB44_2X, RBB44_2Y, RBB44_2Z support from
L 2023-1-6
Visby radios due to the CAT limitation to support multiple
cascading links. Update section 6.7.3, section 6.7.9, section
6.7.11, section 9.1.1.1.2
Add 4.9 for MR11742 wind noise effort estimation
Add 9.6.2 for MR11742 wind noise Enclosure update
Add new RBB configurations for supporting 1*4T4R+1*2T2R for
M 2023-04-14
single 6626 radios, in section 9.1.1.1.2
2023-05-31
6.7.15 – ECT impact added (qpiosob)
2023-05-31 RBB44_3E&3F replaced with RBB44_3F&3G
Add info for MR9002-SP16, the realization of GSM with 28MHz

N 2023-07-14
IBW on Visby 6626 B1B3 only, requested by Bharti
MR10135-1: Add new FV radio, Visby 6626 B0AB28 (Update in
O 2023-07-25
October)
Update MR9002-SP13, SHP enbable on 6626 B1B3 and 4466
P 2023-12-01
B1B3B7 (B1B3)
Update CPI impact for MR10135-1 and MR9002-13
PL21 2023-12-21
1.4 Tracking of Issues and Assumptions
1.4.1 Issues
Table 3: List of issues
No Description Open/Closed
1 Clarify the maximum output power for VISBY platform: Closed

720W -40 ~ 50 degree
600W -40 ~ 55 degree
[25th,Aug]Fixed the power accuracy definition in CRS between SPM
and CRS owner.
2 Not clear release plan for FDD NR 25MHz, 30MHz and 40 MHz from Closed
sub-6GHz
The related MR8340-SP3 is planned 22Q1 release
3 New GSM G1 HWAC impact is still under review led by Joakim Closed.
Forsberg X
SPM made the decision to go for 480W update with fixed 20W steps.
4 The CBCI signals for configuration and fault indication are still under Closed
discussion with CBCI guradian.
Agreement: Alternative 2 is accepted.
5 Proposed HW BL15A is under discussion and synced with Stockholm Closed

PL led by Patrik Norman. Latest decision: HW BL16A
Ericsson Internal

2023-12-21 PF24
6 G3.0/G3.1 (SP204) 25G ESS support Closed

decision: G3.1 (SP204) 25G ESS support would delivery with Radio
6626, while G3.0 had be analyzed with radio 6626 and wait for
planning, which would not be a dependency for FDD Radio 4466.
7 Power drop function issue on mongoose Closed

Solution: slave power drop use GPIO on Randon.
8 There is memory shortage on G1 GSM for FDD Radio 4466 package Closed
adding related to mongoose.
0401: no confirmed feedback from G1 GSM team up to now for
following Options proposed by G1 GSM team
Option1: Extend memory
Option2: In MRO, BTS SW don’t integrate new LMC, running SW
version controlled by other RAN(LTE/W).
And need update the description in correponding chapter
0430: Solution with option2 would be planned in seperated SP,
MR9002-SP3
9 Force Less support on FDD Radiio 4466 need study/ implementation/ Closed
verification from RAN level while not only from radio side.
0401: will request seperated SP which should be required to meet the
timeplan of FDD Radio 4466 release. It would be closed as SP request
approved.
0430: FDD FLESS would start from OA
10 For FDD Radio 4466 project, would these 3 expected functions Open
(Quasi-Dynamic PA VDD, Deep Sleep, Force Less), at least the study
of which, be uplift to cover all presented classic Radios series (Dublin,
G3 Micro, Oslo, Visby, …).
0401: Need review functions design for Visby with function guardians,
including function design and interactions with other functions.
Issue would be still open even reviewed for Visby
0430: reviewed by Function Guardians, no doubt for Quasi-Dynamic
PA VDD, Deep Sleep for Visby would be OK, FDD FLESS would
handled by a seperated OA.
11 FDD Radio 4466 project need get alignment with MR9784 “Mixed Closed
Mode Radio with up to 4 ME”, especially for flex NGS sync 2ME
cascading scenarios.
0401: MR9784 only cover 3ME/4ME. Visby team will request
seperated SP under MR9003 for “flex NGS sync 2ME cascading
scenarios” which should be required to meet the timeplan of Radio
6626 release. It would be closed as SP request approved.
0430: MR9002-2 has been requested for “FLEX NGS SYNC 2ME
scenarios support on Visby Radio”
Ericsson Internal

2023-12-21 PF24
12 There is an open issue on ECP part for the production which want to Closed
use all the 4 CPRI ports, such as Radio 6626, FDD Radio 4466
Here is a radon ECP buffer used as inband buffer, so the O&M link
can’t use that. Mean that the related CPRI port can’t be used.
0430: after reviewed by CD local RTC, XCS solution would be updated
and implemented
Detailed functions support on G3.1 and corresponding timeplan
13 Closed
clarification, and clarify whether meet the release of Visby
0401: list related SP in dependency chapter
14 CRS Radio function update timeplan for FDD Radio 4466 Closed.
[25th, Aug]Upload in Eridoc.
15 Interaction of Quasi Dynamic PA VDD Open
16 Visby FDD Radio 4466 output power clarification Closed

[20th April 3:20 PM] Anders Pers (MR description updated)
● The Radio shall support the following characteristics:
● 4T4R Triple Band radio. Port 1-4: B1, B3, B7
● 640W total power in normal temp range without fan.
60W/band/port (12x60W). Still limited to max 640W.
● ACMA support required. OFCOM support not required. No
India customer to be considered.
● Release (Module PRA) Q4 2021.
17 MARS DRS Closed
18 Visby Radio 6626 B1 B3 support for G+W using 24.3G RI in BB3.1, Closed by
while BB3.0 would not support G or W. MR9002-8
BB3.1 need new SP for study while under discussion at this moment BB G3.1 has
problem to
support
WCDMA on
25Gbps
CPRI，HZ7779
9
19
G3.0 can only handle ESS on 10G line rate, so when Visby Closed
connects on 25G and try to run ESS it will fail.
[25th,Aug]For G3.0, only 10.1G ESS is required, a new SP of

MR9002-SP7 “restrict 25G CPRI capacity to half to support ESS
on BB G3.0”is triggered to handle it.
20 Open
MR9002-SP4 will not introduced new RBBs impact the same as
MR9002-SP1 but highly depend on MR9002-SP2 2ME with
flexible NGS synchronization. MR9002-SP2 release time is still
under discussion.
Ericsson Internal

2023-12-21 PF24
21 Open
DP SW impact on DVSWR Tor sharing solution is to be planned
ready on October according to the feedback from TA study team.
22 Closed.
Mounting pole pattern decision for MR9002-SP4 6626 Low band
radios has been done by SPM as below.
Go with upward hole pattern by120mm.

23 Open
Release of MR9983, SDL support for NR CA. The release of
MR9983 is not scheduled before 2nd half of 2023. It has to be
prioritized by an MA
24 Closed
Not aligned with CRS in-band 9/1056-
CRS in-band defines RAT support per sub-band and not per
multi-band combinations. Radio 4456 B1CB3JB75C shall not
support GSM and WCDMA. Radio 4456 sub-bands (B1C,B3J)
have inherited the RAT support that are “normal” RAT support for
those bands
1.4.2 Assumptions
 Radon based Radio would not have to rely on SBPR support for
linearization. Using internal PM is sufficient. Stockholm will be the 1st
Radio to lead SBPR feature together with BB. MR9002-SP1 is based
on Radon and no need to support SBPR.
 PIMA/PIMD is baseband function. No dependency on Radio for

MR9002-SP1 to release PIMA/PIMD.
 For DUS 3.0, it is still no clear plan to release ESS with 24,3 Gbit.
According to the discussion with Kent Persson H, Dana Chen and
Radio SW team, RSW needs to be updated to support it with the IQ
Move function to do IQ reshuffle. This means only Radio SW update
no HW impact for released Radios if DU decided to trigger a new SP
to support ESS with 24,3 Gbit for DUS 3.0.
From the Rolf Nordlander O’s feedback, DUS 3.0 can use a MOM
attribute to force link to 10.1 Gbit. This came up quite late as a
“QaD” alternative. For this solution, there is no RU impact on RSW
and HW. But this decision for fixed MOM handling has not been
done within DU(G3?) project yet.
 For MR9784 Mixed Mode Radio with up to 4 ME support on FDD

Radio 4466, it is required HW prepared (including Type2, Auboot,
PIS, RICR ready with assumption ASIC implementation and info
input are qualified) when PRA if delivery plan could not meet.
However, FDD Radio 4466 would be HW prepared based on the

assumption ASIC implementation and info input are qualified.
Ericsson Internal

2023-12-21 PF24
Note:
MR9784 SP2 is to be released on RAN SW 22.Q3.
 All design and solution for Mongoose would be valid from FDD
Radio 4466.
1.5 Technical Debt

 Only 4 CPRI with one or 2 DU is covered in MR9002-SP1.
Other New configurations with 3 or 4 nodes will not be covered
in MR9002 SP1. If SPM needed it, a new SP should be
triggered.
 MORAN with more than 2 baseband connection is not covered
in MR9002-SP1.Need a new SP to trigger the study.
 Quasi dynamic Vdd adjustment/Deep sleep is not included in
MR9002-SP1.
 From DMS team, the impact on Low Band radio with single
GSM will not be covered on DMS2. A new DMS2 study will
cover it. More detailed info. is as below.
– Site solution, Bracket, BP solution, Thermal and all
related the Radio HW solution changed in Low Band
should be updated in the new DMS2
– Radio SW, Radio Function, Trxctrl, CAT, DUW/DUG
impact has been covered in MR9002-SP1.
 SRO GSM function origin from Oslo is not included in MR9002-
SP1.It depends on the DMS study of Low Band radio. If
needed, a kind of SP for SRO GSM function shall be added.
No need to support SRO GSM from platform MR.
 WCDMA G1 MB supporting for MB radios is not included in
MR9002-SP1.
Ericsson Internal

2023-12-21 PF24
[2] (SYSFUNC Siyu)Main Requirement (MR) and Solution

Package (SP) Analysis
1.6[2.1] MR Background
MR7341 is a VISBY platform MR. It contains which types of radios that

can be expected to be released with the VISBY program and to some
extent requirements for each radio type. MR7341 will not be released
i.e. no F1 decision will be taken for that MR, instead the F1 will be
taken on each radio type.
MR9002 is a PV MR and a class B 6T6R/6T6R variant of the Triple

Band Radio platform VISBY. It contains which types of radios that can
be expected to be released within the VISBY Dual band project.
MR9003 is a FV MR based on MR9002-SP1 which defines a detailed

radio 6626 66B1 66B3 C to be released.

Low Band radio 6626 66B8 66B20 C to be released.
MR8930 is a PV MR and a class B 4T4R/4T4R/4T4R variant (FDD

Radio 4466) of the Triple Band Radio platform VISBY. It contains
which types of radios that can be expected to be released within the
VISBY Triple band project. And MR8930-SP1 covers FDD Radio
4466 only.
MR8932 is the first FV MR based on MR8930-SP1 which defines a

detailed FDD radio 4466 44B1 44B3 44B7 C to be released as first
FV.
MR9609 is a PV MR based on MR8930-SP1 which defines a detailed

first FV FDD radio 4456 44B1C 44B3J 40B75C C to be released, in
which B75C is DL only.

FDD radio 4466 44B2/B25 44B66 44B7 C to be released.
MR9268 is a feature MR based on MR7602-SP2B which defines

the LTE GB NB-IoT coexistence with ESS on Visby Radios to be
released.
MR10135 is a FV MR based on MR9176. MR10135 defines a detailed

low band FDD radio 6626 66B0A 66B28 C to be released.
Ericsson Internal

2023-12-21 PF24
1.7[2.2] MR Scope Analysis

Table 4: MR compliance
Item Content
MR ID 105 65-0937/07341 PA31
Slogan NGR Visby platform

Ericsson Internal

2023-12-21 PF24
MR Text
A new general multiband radio platform allowing for up to 12T12R.
The platform shall be possible to use for single band, dual band or
triple band radios with up up 12T12R.
General
The radios shall be developed as â€œGlobal radiosâ€ supporting
needed certificates related to countries and frequency bands. This
includes ACMA and OFCOM requirements.
Return Rate
0,7% is target for new platforms including Visby and all Visby radios
(PV, FV).
RF Power
Total radio RF power 320-720W
40-80W/port/band limited by total radio RF power
Frequency range
600MHz - 5GHz.
600MHz acceptable with bigger size radio.
Frequency bands
As defined in CRS. Support all frequency bands within the frequency
range.
Power consumption
TBD
Duplex Mode
FDD, TDD and mix FDD/TDD shall be supported.
FDD/TTD to be supported in same RF port.
RAT support
GSM, WCDMA, LTE, NR and NB-IoT.
GSM mixed mode support
GSM SRAT not supported.
IBW
Up to 400MHz, max supported by one Radon or two Krypton ASIC's
20 MHz IBW for GSM or LTE1.4/3MHz and SA NB IoT carriers
Radio Volume
Without fan, mid band
720W output power: Target 42L
320W output power: Target 32L
Without fan, mid band >1GHz

720W output power: Target 40L, 45kg
320W output power: Target 32L, 36kg
Ericsson Internal

2023-12-21 PF24
With fan
See MR for specific FV.
Declaration of temperature range at max output power to be discussed

for each FV.
Dimensions:
Width: 384mm (Oslo legacy, radio behind antenna)
Height mid band: 580mm
Height low band: 700mm
CPRI ports
4 ports shall be supported
The radio shall support legacy plug-in modules, SFP2.5 and forward.
Up to 4 separate basebands shall be supported enabling MORAN

setup.
CPRI rates
2.5Gb/s, 4.9Gb/s, 9.8Gb/s, 10.1Gb/s, 24.33Gb/s
Note. 4.9Gb/s is used by XMU03 (Ericsson CPRI port expander,
R503)
RF ports and connectors

Up to 12 ports
Kenia 4.3-10 is preferred. NEX10 to be used if cannot fit 4.3-10.
The radio shall support self-protection for high power return on the
ARP port.
TX monitor port
Need to be supported (Japan, Korea customers)
Ant Cal port

Support for radios having 8T8R on one TDD band
Power supply / DC feeds
3-wire DC power supply system possible to connect as 3-wire or 2-

wire.
The radio shall support the following use cases

1. Single power cable, -48V legacy, for radios up to 480W power.
2. Dual power cables(both connected), -48V legacy, for radios with
more than 480W RF power.
2.1 Using two DC cables from power supply
2.2 Using one DC cable from power supply and a Y-cable at radio
side (possibly DC booster needed in this use case?)
3. Single power cable with Power booster providing -58V at power
supply unit.
Ericsson Internal

2023-12-21 PF24
3. The radio shall support Power booster providing -58V at power

supply unit.
AISG
All RF ports shall support AISG 3.0 Ping.
All RF ports shall support OOK signaling, 9.6kb/s only. Double check
for AC...
TMA support
FDD radios shall support 12 dB TMA according to internal

requirements, no 24 dB TMA support required.
No TMA support for TDD radios.
No TMA support for radios with FDD+TDD in common antenna ports
TMA support only for FDD ports for radios with FDD+TDD in
separate ports.
Antenna Syst Voltage, RET/TMA

BiasT on every second port for radios having 4 RF ports or more with
up to 1.5A on each applicable RF port.
DC supply via RF port (Bias T)
General: Minimum one DC supply per sector and per antenna group in
order to have one DC supply for each antenna system.
FDD radios shall support DC supply on every second RF port for

radios having 4 RF ports or more.
Other radios, see specific FV MR.
Support up to 1.5A on each applicable RF port.
Support TMA/RET power supply with a total of 3,2A.

Antenna System voltage support should be configurable for RF ports,
RET port, or both.
Antenna System Voltage is 30V only
VSWR
VSWR support on each band and each port
Class A/B
Current assumption is to only support Class B
Class B: Support for RET/TMA over RF port/RS-485 and optional
FAN
Ericsson Internal

2023-12-21 PF24
NEBS
NEBS compliant to be supported for USA customers
FAN option
Fan solution to be supported as an option. (Cooling of heatsink)
Mounting
Portrait and bookshelf mounting to be supported.
Bookshelf might be removed for low band radios due to weight ans
size.
Cascading
To be supported.
1 ME or CPRI connected to radio: Cascading on one port to be

supported.
2 ME or CPRI connected to radio: Cascading on two ports to be
supported.
3 ME or CPRI connected to radio: Cascading on one port to be
supported.
PIMC
PIMC to be supported in all products using the Krypton ASIC.
The PIMC function shall be handling in-line and inter-branch PIM

cancellation, aka PIMC3.
Performance and KPIâ€™s

1. The PIMC function is to be used for improved performance related
to PIM in live traffic.
2. The PIMC function shall give improved RX sensitivity in channels
with PIM issues.
3. The PIMC function shall include performance measurements and
KPIâ€™s that shows quantified improved performance using this
function.
Ericsson Internal

2023-12-21 PF24
4. The PIMC function shall be capable to cancel 15dB of 3rd order

PIM
5. The PIMC function shall be capable to cancel 10dB of 5rd order
PIM (not lower than noise floor of the receiver)
PIMD
The radio shall be complient with PIMD baseband function.
PIMA
The radio shall be complient with PIMA baseband function.
EOC
EOC to be supported in all products using the Krypton ASIC.
(addressing linearization of wideband PAâ€™s)
Power Overbooking and Power pooling

Shall support Power Overbooking and Dynamic Power Pooling.
Power save
The platform shall support all legacy power save features, baseline is
Oslo for FDD and Dublin for TDD.
In addition, the following features shall be supported
1. Micro Sleep TX Enhanced with ASIC dynamic clock gating.

MR 8939
Ongoing implementation in radio 6449
2. Micro Sleep TX Enhanced extended with pre-driver.
3. Micro Sleep TX feature shall be default on and only turned off
if the actual configuration is not supported by SBPS
4. Component power save enhanced, similar like MR 5710
5. Cell sleep enhanced with ASIC static clock gating. MR 9083.
Partly implemented in 6449. Contact person Cathy Yin.
Quasi Dynamic PA VDD

The radio shall support Quasi Dynamic PA VDD, MR 8497.
PreDev finished Q2 2020 with good results. Contact Haiying Cao.
oRAN/C2-lite
TBD (only to be supported in products using the Krypton ASIC)
MORAN
To be supported where operators using separate BB/DU.
TDD Pattern
Support different switching points per band
Ericsson Internal

2023-12-21 PF24
RIBS
TBD
Configuration
Support ESS for FDD
Other requirements
Energy efficiency requirements shall be according to the document
"Energy Efficiency Requirements on Classic Radios 2021-2025".
The product variants shall fulfill all applicable requirements on FDD

Radio 4415 G3, Radio 4422 G3, NGR Dual Band Radio platform Oslo
and TDD Radio 8863.
Compliance of This NDS is compliant to this MR.
suggested solution
Deep sleep,Quasi Dyanmic PA VDD,PIMC,PIMD,PIMA and EOC
shall not be covered in MR9002-SP1.
MORAN with more than 2 baseband connection is not covered in
MR9002-SP1
SPM agreed on 43.6L with LDMOS PA and 39.5L with GaN PA for
MR9002-SP1.
This is agreed in the OA report of OP MR8930 Radio 4466 4T4R TB_
MR9002 Radio 6626 6T6R DB 3-sector and OR MR7341 Visby
platform.
1ME cascading on one port and 2ME connected to the same radio
without cascading is supported in MR9002-SP1.
2ME cascading on 2 ports is supported in MR9002-SP2 with certain
limitations.
3-4 ME cascading is out of MR9784 scope but 3-4 ME connected to
the same radio will be supported in MR9784 SP2.
Deep sleep,Quasi Dyanmic PA VDD shall be supported in MR9002-

SP4.
SPM agreed to update the volume and weight for Low band radio in
MR7341 as below .
Without fan, low band <1GHz
720W output power: Target 47 45L, 49 50kg
Note:
There is a requirement priority defined in the OA report of OP MR8930

Radio 4466 4T4R TB_ MR9002 Radio 6626 6T6R DB 3-sector as
below.
Visby FV MRs > Visby PV MRs > Visby Platform MR(7341) > Oslo
Dual band Platform MR(5274)>G3 Platform MR(3639)
Ericsson Internal

2023-12-21 PF24
Visby FV MRs and Visby PV MRs must be within the scope of Visby
Platform MR.
Item Content
MR ID 105 65-0937/09002 PA7
Slogan Radio 6626 in Ericsson Radio Systems (VisbyPV)
MR Text
Radio 6626 is a 3-sector dual band radio, 6T6R / 6T6R, totally 6
antenna ports.
This is a variant of the Triple Band Radio platform Visby.
Radio 6626 shall support the following characteristics:
320-720W total power in normal temp range without fan.
Output power per band and branch is defined in FV MRs.
The product variant shall fulfil all applicable requirements on Radio

4415 G3, Radio 4422 G3 and NGR Dual Band Radio platform Oslo.

suggested solution
Radio 4422 is not covered in MR9002-SP1 FDD paltform.Because
Radio 4422 G3 is a TDD platform.
Item Content
MR ID 105 65-0937/09003 PA9
Slogan Radio 6626 66B1 66B3 C (VisbyFV)

Ericsson Internal

2023-12-21 PF24
MR Text
The Radio shall support the following characteristics:
6T6R Dual Band radio.

Port 1-6: B1, B3
720W total power without fan. Limited temp range.

720W total power with fan. Full temp range -40C to +55C.
600W total power without fan. Full temp range -40C to +55C.
B1: 60W/band/port (6x60W)

Radio size
Max 43,6L using LDMOS PA's
Max 39,5L using GaN PA's
HW prepared supporting up to 4 basebands.

suggested solution
Item Content
MR ID 105 65-0937/09176 PA11
Slogan Radio 6626 66B8 66B20 C (VisbyFV)
MR Text

Port 1-6: B8, B20
Max 720W total power without fan.
Thermal dimension 600W, 17% (0,8dB) thermal pooling relaxation.

720W total power without fan. Temp range -40C to +50C.
720W total power with fan. Temp range -40C to +55C.

Target size 45L/50kg.
GSM/WCDMA support not needed for B20.

Compliance of This MR9002-SP4 of NDS is compliant to this MR.
suggested solution
Ericsson Internal

2023-12-21 PF24
Item Content
MR ID 105 65-0937/8930 PAX
Slogan Radio 4466 in Ericsson Radio Systems (VisbyPV)
MR Text
Radio 4466 is a variant of the Triple Band Radio platform Visby.
This includes the following configurations
TB: 4T4R / 4T4R / 4T4R (Tot 4 ports. 3 bands in 4 ports)
TB: 4T4R / 4T4R // 4T4R (Tot 8 ports. 2 bands in 4 ports, 1 band 4

ports)
TB: 4T4R // 4T4R // 4T4R (Tot 12 ports. 1 band in 4 ports, 1 band in

4 ports, 1 band in 4 ports)
QB: 4T4R / 4T4R // 4T4R / 4T4R (Tot 8 ports. 2 bands in 4 ports, 2

bands in 4 ports)
QB: 4T4R / 4T4R // 4T4R // 4T4R (Tot 12 ports. 2 bands in 4 ports, 1

band in 4 ports, 1 band in 4 ports)
QB: 2T2R / 2T2R // 4T4R / 4T4R (Tot 6 ports. 2 bands in 2 ports, 2

bands in 4 ports)
320-720W total power in normal temp range without fan

Output power per band and branch is defined in FV MRs.
Radio names
4466 for radios with output power >480W
4456 for radios with output power <480W

suggested solution
Ericsson Internal

2023-12-21 PF24
Item Content
MR ID 105 65-0937/10135
Slogan Radio 6626 66B0A 66B28 C (VisbyFV)
MR Text

Port 1-6: B0A, B28
Max 720W total power without/with fan.
Thermal dimension 800W, 17% (0.8dB) thermal pooling relaxation.

600W total power without fan. Temp range -40C to +55C (E-busy)
B0A: 80W/band/port (6x80W)

Non-standard BW to support 8,6MHz at B0A, LTE/NR (Bharti

customer request)
Target size 48.7L/51kg.
Compliance of This MR10135-SP1 of NDS is compliant to this MR. But non-

suggested solution standard CBW 8.6 MHz is removed according to SPM’s confirmation
in SPM weekly forum.

Item Content
MR ID 105 65-0937/08932 PA9
Slogan Radio 4466 44B1 44B3 44B7 C (VisbyFV)
MR Text
● 4T4R Triple Band radio. Port 1-4: B1, B3, B7
● 640W total power in normal temp range without fan.
60W/band/port (12x60W). Still limited to max 640W.
● ACMA support required. OFCOM support not required. No
India customer to be considered.
● Release (Module PRA) Q4 2021.

suggested solution
Ericsson Internal

2023-12-21 PF24
Item Content
MR ID 105 65-0937/09609 PA23
Slogan Radio 4456 in Ericsson Radio Systems (VisbyFV)
MR Text
Radio 4456 is a variant of the Triple Band Radio platform Visby
Radio 4466.
This includes the following configurations
TB: 4T4R / 4T4R / 4T0R (Tot 4 ports. 3 bands in 4 ports)
320W total power in normal temp range without fan

Output power per band and branch is defined in FV MR’s.
Radio names
4456 for radios with output power <480W

suggested solution

Item Content
MR ID 105 65-0937/09609 PA23
Slogan
Radio 4456 44B1C 44B3J 40B75C C (VisbyFV)
Ericsson Internal

2023-12-21 PF24
MR Text
 4T4R Triple Band radio
 Port 1-4: B1C, B3J, B75C

 Sub band as below
 B1C: 1960 – 1980 & 2150 – 2170 MHz
 B3J: 1710 – 1750 & 1805 – 1845 MHz
 B75C: 1452 – 1472 MHz
RAT support
- LTE, NR, NB-IoT
- GSM, WCDMA not required
 Max 320W total power without fan.

 Thermal dimension 300W, 6% (0,3dB) thermal pooling
relaxation.
 320W total power without fan. Temp range -40C to +50C.
 300W total power without fan. Temp range -40C to +55C.
 B1C 20W/port
 B3J 30W/port
 B75C 30W/port
 Target size 25L

 Target Weight <30kg
 Ofcom not required
 No optional fan required

 No TX monitor ports required
 Power consumption: 1000W and 23A (label)
 Antenna Syst Voltage, RET, DC supply via RF port (Bias T)

 Support DC supply on every second RF port (port A and C)
 Release (Module PRA) Q2 2022

suggested solution

Ericsson Internal

2023-12-21 PF24
Item Content
MR ID 105 65-0937/10083 PAX
Slogan
Radio 4466 B2/B25 B66 B7 C (VisbyFV)
MR Text
4T4R Triple Band radio.

Port 1-4: B2/25, B66, B7
720W total power in normal temp range without fan,

60W/band/port (12x60W)
Release (Module PRA) Q3 2022.
suggested solution

Item Content
MR ID 105 65-0937/09268
LTE GB NB-IoT coexistence with ESS on Visby Radios
Slogan
MR Text
Support of ESS + NB IoT (IB and GB) to be implemented for
Visby platform including all PV's and FV's.
Release target 22.Q42
suggested solution Support: Radio6626B1B3
Radio6626B8B20
Radio4466B1B3B7
Radio4456B1CB3JB75C
Ericsson Internal

2023-12-21 PF24
1.8[2.3] SP Description and Definition of Done

Table 14: Definition of Done per SP
SP Number, Name Definition of Done
105 65-0937/09002-SP1  Radio 6626 will support the following SRO: LTE, NR,
NB IoT, WCDMA, ESS
Radios 6626 G,W,L,NR and
ESS with 3 sectors  Mixed Mode Radio(MRO) supported in following RATs:
GSM,LTE, NR,NB-IOT, WCDMA,ESS
 Mixed Mode Radio for Max 3 RATS+NB per RF port
per Band
 Support 3-sectors
 NR Channel BW: support all necessary Radon defined
CBW
 LTE Channel BW: support 1.4, 3,5,10,15 and 20 MHz
 WCDMA Channel BW: support 5MHz
 NB-IoT: support IB,GB and SA
 Radio 6626 shall support maximum output power with
720 W.
 All above features can be common for Radio 4466.
 SP1 will not handle more than 2 DU scenario. It will be
handled by a separate SP.
105 65-0937/09002-SP3  Due to the restriction of GSM BTS flash card size,
GSM G1 will not integrate Radio SW app, DUG20
GSM G1 support Visby would remove the radio SW version control in MRO,
Radios & Stockholm Radios leave the Radio SW App upgrade/control by other DU.
in mix mode only
 Agreed short-term solution for Visby and Stockholm
radios: GSM G1 not integrate new Radio SW App in
UP. In MRO configuration, update the legacy radio SW
selection Logic, DUG20 will not upgrade Radio SW to
Radio Unit, choose the PIS or Running SW version.
Ericsson Internal

2023-12-21 PF24
105 65-0937/09002-SP4 Radio  Legacy requirements based on MR9002-SP1 for

6626 Low Band G, W,L,NR and Radio 6626 Low band as below
ESS supported with 3 sectors
and Tor sharing DVSWR
– Radio 6626 will support the following SRO:
LTE, NR, NB IoT, WCDMA,
– Mixed Mode Radio(MRO) supported in
following RATs: GSM, LTE, NR, NB IOT,
WCDMA,ESS
– Mixed Mode Radio for Max 3 RATS+NB per
Band per RF port
– support 3-sectors
– NR Channel BW: support all necessary Radon
defined CBW as below
– NR 5/10/15/20/25/30/40 MHz
– LTE Channel BW: support 1.4, 3, 5, 10, 15
and 20 MHz
– WCDMA Channel BW: support 5 MHz
– NB IoT: support IB, GB and SA
– Radio 6626 shall support maximum output
power with 720W
 Legacy requirements based on MR8930-SP1 for
Radio 6626 low band as below.
– support Quasi-dynamic Vdd
– support Deep sleep
 Additional requirements
– Tor sharing for DVSWR(TA)
Ericsson Internal

2023-12-21 PF24
Table 15: Definition of Done per SP

Ericsson Internal

2023-12-21 PF24
105 65-0937/09002-8  It is a verification only SP

25 Gbps CPRI Verification for  This SP will deliver the following improved
GSM functionality/characteristics 25Gbps CPRI for GSM on
BB3.1 + Visby radios for GSM mixed mode
configurations
 This feature is verifed on Visby Radio 6626 B1 B3 and
BB3.1
105 65-0937/09002-15  Deliver a generic solution to handle mixed mode

configurations with up to 6 GSM TRX'es per 2T2R
7CC per port on B3 UL for Visby
sector on Visby RU.
Radio 6626 B1B3 and Radio
4466 B1B3B40/B41  The max number of UL carriers per port on B1 has to
be reduced from 6 to 5 to shift one filter branch per
port from B1 to B3, in order to support 7CC on B3 UL
for Visby.
 6 GSM TRX'es cannot be supported with DUG，G2
and G3.1 BB node should support up to 6 GSM
TRX'es per 2T2R sector in mixed mode configurations
when connected with Radio 6626 B1B3, and support
up to12 GSM TRX'es per 4T4R sector in mixed mode
configurations.
105 65-0937/09002-16  Deliver a solution to handle GSM IBW expansion from

20MHz to 28MHz on Visby 6626 B1B3. Based on the
elementary verifications, different requirements are set
on different HW version, after aligned with SPM.
 On B1B3 R1D and R2C version, GSM mix mode total
IBW maximum till 40MHz, GSM IBW max increase till
28MHz. GSM maximum 20W per carrier. In mix mode,
NB SA with max 20MHx IBW, and LTE or NR with
5/10/15/20MHz.
 On both versions, power backoff maybe considered,
depending on the verification performance. Will align
with SPM and update in NDS.
105 65-0937/09002-13  Enabling SHP supporting on Visby 6626 B1B3 and

4466 B1B3B7 (B1B3), replacing GaN Boost solution
SHP Enable on Visby 6626
and reducing power consumption while securing good
B1B3 and 4466 B1B3B7
EVM.
 Solution for B7 will remain the conclusion that
SHP+GaN Boost (due to the EVM performance) from
MR11923-SP1, which is not included in the scope of
this SP.
 New supporting of GaN Boost switch based on
different bands is considered. SW and TRXCTRL
needs to find a solution for realizing this pre-condition.
 Verification includes HW perofrmance test and Node
FV, for power saving performance, as well as the SW
regular regression test.
105 65-0937/08930-SP1  FDD Radio 4466 will support the following SRO: LTE,
Ericsson Internal

2023-12-21 PF24
Table 16: Definition of done per SP

105 65-0937/09609-1  FDD Radio 4456 will support the following SRO: LTE,
NR, NB IoT,ESS
FDD Radios 4456 L,NR and
ESS  Mixed Mode Radio(MRO) supported in following RATs:
LTE, NR, NB-IOT, ESS
 Mixed Mode Radio for Max 3 RATS+NB per RF port
per Band
 NR Channel BW: support all necessary Radon defined
CBW
 LTE Channel BW: support 1.4, 3,5, 10, 15 and 20 MHz
 NB-IoT: support IB, GB and SA
 FDD Radio 4456 shall support maximum output power
with 320 W.
 All above features can be common for FDD Radio
4456.
 Support Quasi-dynamic PA VDD
 Support Deep Sleep
 HW prepared (including Type2, Auboot, PIS, RICR
ready with assumption ASIC implementation and info
input are qualified) for MR9784 Mixed Mode Radio with
up to 4 ME
105 65-0937/09268-1  To deliver a generic solution to support LTE GB

NB-IoT coexistence with ESS to be implemented
LTE GB NB-IoT coexistence
for Visby platform including all PV's and FV's.
with ESS on Visby Radios
 The DL filters will be redesigned.
 The Radio external database will be updated to
support ESS+NB-IoT on Visby Radios.
 Support G2/G3/G3.1 basebands and RGW
R608/R308
 Support release on Radios:
Radio6626B1B3
Radio6626B8B20
Radio4466B1B3B7
Study effort estimation of Radios:
Radio4466B1B3B40
Radio4466B1B3B41
Radio4466B7B25B66
Radio4456B1CB3JB75C
Ericsson Internal

2023-12-21 PF24
105 65-0937/10135-1  Radio 6626 B0AB28 will support B0A and B28, 120W
(w.o. and with fan) per port
Visby 6626 66B0A 66B28 C
FDD Radio  FDD Radio 6626 B0AB28 will support the following
SRO: GSM, WCDMA, LTE, NR, NB IoT (IB/GB/SA),
ESS
 Mixed Mode Radio(MRO) supported in following RATs:
GSM, WCDMA, LTE, NR, NB-IOT, ESS
 NR Channel BW: 5/10/15/20 MHz, 25/30/40 MHz
supporting depends on ongoing MR verification on PL.
 LTE Channel BW: support 1.4, 3,5, 10, 15 and 20 MHz
 NB-IoT: support IB, GB and SA
 ESS BW: 10/15/20 MHz
 All WCDMA and GSM is supported on B0A only
 Quasi-Dynamic PA VDD and Deep Sleep are not
required in this radio.
 Supporting other features that have been realized on
PL
1.9[2.4] MR/SP Dependencies and Priority

Table 17: MR/SP Dependencies and Priority
MR/SP Dependencies and Priority
SP number SP name Prio External dependency (to SP number)

rity
Radio 6626 G, W, L,
105 65- 1 SP 5280-1 Full G, W, LTE-FDD Support
NR and ESS with 3
0937/09002 -1 (For G1 and W1 only SB)
sectors
SP 5280-2 NR support for Radio 4480
SP 5279-3 WCDMA G1 MB support for

MB radios
SP 5273-3 Radio 2238 B8B20B28B

L+W+G+NR+ESS
MR4438 SP5 AISG 3.0 feature support,

SP5 Device Scan functionality
Ericsson Internal

2023-12-21 PF24
MR 8340-3: NR Support for FDD

25MHz,30MHz,40MHz,50MHz Carrier
Bandwidth Global (planned delivery
22Q1)
MR 8341 NR support for FDD 25MHz for

US market/40MHz for China Market
G3 SP204: to support ESS on G3.1 HW
MR5710 Component power saving
MR5657 Power overbooking
MR6596 Force less
MR6699 TX Micro sleep for ESS FDD
105 65-0937/04106-3 Radio Self-Test

Stand-Alone-SP3, Power source test
105 65- FDD Radio 4466 G, 1 105 65-0937/09002 -1 Radio 6626 G, W,

0937/08930 -1 W, L, NR and ESS L, NR and ESS with 3 sectors
SP8881-1 AAS MB G3 radio deep sleep
105 65-0937/06861 Mid-band TDD AAS

Hangzhou platform (for Quasi-Dynamic
PA VDD)
MR9784 Mixed Mode Radio with up to 4

ME (planned delivery 22Q1)
MR9002-2 Flex NGS Sync 2ME

scenarios support on Visby Radio
(planned delivery 21Q3)
SP08978-5 FM when HW initialization

faults (planned delivery 21Q3)
MR8340-3: NR Support for FDD

25MHz,30MHz,40MHz,50MHz Carrier
Bandwidth Global (planned delivery
22Q1)
MR9002-SP2 Flex NGS Sync 2ME

scenarios support on Visby Radio
MR9002-SP3 GSM G1 support Visby

Radios & Stockholm Radios in mix mode
only
Ericsson Internal

2023-12-21 PF24
SP8583-1/2/3 PIM detection in BB
SP180 “GSM single standard feature

parity on BB6648/BB6621/BB6631” -
G21.Q3
SP181 “WCDMA single standard feature

parity on BB6648/BB6631/BB6621” -
W21.Q3
SP184 “GWL mixed mode feature parity

on BB6648/BB6631/BB6621” - G21.Q3;
W21.Q3; L21.Q3
SP192 “NR Mid-Band (C2) first call and

feature parity on G3.1 HW” -
N21.Q3(BB6631); N21.Q4(RANP6651);
N22.Q1(RP6339); N21.Q4(RP6353);
N21.Q4(RANP6647)
SP193 & SP194 NR C1 first call and

feature parity on G3.1 HW" -
N21.Q3(BB6631); N21.Q4(RANP6651);
N22.Q1(RP6339); N21.Q4(RP6353);
N21.Q4(RANP6647)
SP197 “LTE C1 Single Standard first call

and feature parity on G3.1 HW” -
L21.Q3(BB6621); L21.Q3(BB6631);
L21.Q4(RANP6651); L22.Q1(RP6339);
L21.Q4(RP6353); L21.Q4(RANP6647)
SP198 “LTE C2 Single Standard first call

and feature parity on G3.1 HW”’ -
L21.Q3(BB6631); L21.Q4(RANP6651);
L22.Q1(RP6339); L21.Q4(RP6353);
L21.Q4(RANP6647)
SP200 “NR High Band C1 first call and

feature parity on G3.1 HW” -
N21.Q3(BB6631); N21.Q4(RANP6651);
N22.Q1(RP6339); N21.Q4(RP6353);
N21.Q4(RANP6647)
SP201 “NR/LTE Mixed Mode First call

and Feature parity on G3.1 HW” –
L/N21.Q3(BB6631);
Ericsson Internal

2023-12-21 PF24
L/N21.Q4(RANP6651);L/N22.Q1(RP633
9);L/N21.Q4(RP6353);L/N21.Q4(RANP6
647)
105 65- Radio 6626 Low 1 105 65-0937/9002-1 Radio 6626 G,W,L,
0937/09002 -4 Band G, W, L, NR NR and ESS with 3 sectors
and ESS with 3
sectors and Tor 105 65-0937/8930-1 Radio 4466 G, W,
sharing DVSWR L, NR and ESS
105 65-0937/9002-2 Flex NGS Sync

2ME cascading scenarios support
MR9784 Mixed mode radio with up to

4ME
MR8340-3 NR Support for FDD 25MHz,

30MHz, 40MHz, 50MHz Carrier
Bandwidth Global(planned delivery
22.Q1)Bandwidth
MR8583-1/2/3/4/5/6/7/8/9 PIMD
Detection in BB
MR9002-5 Radio Modular Database
MR9002-6 Module System

Systemization
105 65-0937/9002-3 GSM G1 support

Visby Radios & Stockholm in mix mode
only
1/12702-106/FCP 105 0091 TA: Tor

sharing for DVSWR
105 65- Radio 4456, L, NR Common FDD/TDD dependency:

0937/09609-1 and ESS
MR8930-1: Radios 4466
G,W,L,NR,ESS with Deep sleep,
Quasi-Dynamic VDD adjustment
MR9784-2: Mixed mode radio with

up to 4 ME (22.Q3)
MR7777: Dynamic Latency

Handling/new TA model
MR8583-1/2/3/4/5/6/7/8/9 PIMD
Ericsson Internal

2023-12-21 PF24
Detection in BB
MR8497 Quasi-Dynamic VDD

adjustment
MR5710 Component Power saving
MR8939: SBPS extended to

Dynamic Clock gating (Radon
onwards)
MR9083: ASIC Static Clock Gating

for Visby and future radios (to be
started)
MR6941: Oslo section based VDD
MR6155: MIMO sleep for C1 radio
TA studies: Booster Carrier Sleep,

Booster Carrier Deep Sleep (for long
term signaling solution for deep
sleep)
FDD only dependency:
G3-SP204: ESS BB G3.1 (21.Q4)
MR5759/5760 Dual band for Oslo

Radio 4480/4499 B2/25 B66A
MR8340-4: NR FDD 25,30,40,50

MHz BW support (MR8340-3 (which
should be released in 22Q2) does
not include HW
integration/verification/certification,
this part will be included in MR8340-
4 for which the release date is not
available yet)
MR9002-4/9176-1: Radios 6626 low

band TOR sharing for DVWSR (see
also TA: TOR sharing for DVSWR)
MR 6641/2: LTE/NR mixed mode

BBG2/G3 25Gbps (Dublin) (Gap:
GRAT/WRAT 25Gbps)
MR9983: SDL support for NR CA

(No firm plans for SDL support in
2022 or in first half of 2023)
Ericsson Internal

2023-12-21 PF24
105 65- LTE GB NB-IoT MR7602-SP3, RGW supporting is

0937/09268-1 coexistence with implemented by MR7602-3MR9268-SP1
ESS on Visby support RGW R608/R308, which is
105 65- RadiosESS+NBIOT implemented on Visby radios by
0937/07602-3 with RGW MR7602-SP3
1.10[2.5] Mapping of Detailed Requirements to SP(s)

Table 18: Links to RS in MARS per SP
SP Number MARS Link
105 65-0937/09002-1 MR9002-SP1
105 65-0937/09002-3 MR9002-SP3
105 65-0937/09002-4 MR9002-SP4
105 65-0937/08930-1 MR8930-SP1
105 65-0937/09609-1 MR9609-SP1
105 65-0937/09002-8 Refer to MR9002-SP1 , update item 38976
105 65-0937/09002-15 Refer to MR9002-SP1 , update item 38923/38924
105 65-0937/09268-1 MR9002-SP1, MR8930-SP1, MR9002-SP4
105 65-0937/10135-1 MR10135-SP1
105 65-0937/09002-13 MR9002-SP13
1.11[2.6] Description of Feature/Functionality/Configuration
1.11.1[2.6.1] Feature/Functionality/Configuration Presentation
N/A. Not a feature or functionality.
1.11.2[2.6.2] Commercial Aspects, Feature Description
Radio 6626 is the VISBY dual band radio based on Radon with
6T6R/6T6R. The key requirements are as below.
Ericsson Internal

2023-12-21 PF24
 Maximum Output Power: 720 W

Note:
1. Output power per band per branch is defined in FV MRs.
2. Till now, the maximum output power defined in FV MR9002 and
MR9176 is 720W.
3. Not clear FV MR to define the maximum output power as
320W, although this requirement is clarified in MR9002.
 Full band IBW/OBW:
– Maximum 90 MHz for Radio 6626 per band
Note:
1. Maximum GSM/NB-SA/LTE 1.4&3MHz IBW: DL 20 MHz UL full
band IBW. Refers to NDS VISBY Radio 6626 4466 4456.
2. B65/N65 is the max IBW in UL/DL defined in 3GPP 38.104.
 Support Dual band configuration

Note:
1.Detailed Band information is defined in FV MRs.1st FV is for
B1,B3.
 Maximum number of carriers per Band per RF port

– 6 for LTE and WCDMA
– 6 for NR FDD
– 6 for ESS
– MRO: 4 for GSM in downlink, 5 for GSM in uplink
SRO: 4 for GSM in downlink, 6 for GSM in uplink
– 2 for NB-IOT SA in downlink, 6 for NB-IOT SA in uplink
– 6 for mixed mode
 Maximum number of carriers per Band per Radio
– 36 for NR FDD
– 36 for ESS
SRO: 24 for GSM in downlink, 36 for GSM in uplink
– 12 for NB-IOT SA in downlink, 36 for NB-IOT SA in
uplink
Ericsson Internal

2023-12-21 PF24
Note：
The maximum number of carriers is also limited by IBW and
CBW for different Bands.
The maximum number of carriers is also limited by filter branch
resource in Radon. Refers to Radon RS.
 RAN support
– MR9002-SP1
GSM, WCDMA, FDD-LTE, NR, ESS, NB-
IOT(SA,GB,IB) for Radio 6626
Note:
SRO GSM is not in MR9002-SP1 scope for Radio 6626. It
depends on the HW DMS study on low band radio.
 CPRI: 2.5,4.9,9.8,10.1 and 25Gbps
Note:
Slave supports all CPRI line rates, Master only supports
2.5,9.8,10,1 and 25Gbps.
 TX-monitor ports only support for bands used in Korea and
Japan
 No Antenna Calibration
 Support Max 6 radio cascade
 NR support
– 5MHz, 10MHz, 15MHz, 20MHz,25 MHz,30MHz,40MHz
with 15 kHz SCS.
Note:
1.Currently, only 15 kHz SCS for NR FDD is released in 5G
BB.
2. 25MHz/30MHz/40MHz is developed by MR8340-3 and
to be released on 22.Q1.
 ESS support
10MHz, 15MHz, 20MHz with 15 kHz SCS
 LTE Channel BW
1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, 20MHz
 Additional LTE Channel BW
B3: 4.6 MHz, 4.8 MHz and 9 MHz
Note:
1. Subsequent FVs have different CBWs. If there is
special CBW requirement in FVs, Radio system should
align with SPM firstly.
Ericsson Internal

2023-12-21 PF24
2. No need to support 14.8 MHz CBW. This decision is

made from Oslo 4T4R requirement forum and Ottawa
requirement forum(14.8MHz LTE BW support).
 Not support internal PIMC
 Mixed Mode Radio for Max 3 RATS+NB per RF port per band
Note:
1. GSM+WCDMA+another RAT shall not be supported per
RF port per band.
2. ESS is 2 RATs(NR+ESS) at the same time, so
GSM+LTE+NR+ESS shall also be supported and shall be
considered as triple RAT configuration.
 Radio 6626 shall be supported with the following DUs and
Baseband units:
– MR9002-SP1
DUG 20, DUW v1, DUW v2, DUS 31, DUS 41, Baseband
5212, Baseband 5216, Baseband 6303, Baseband 6318,
Baseband 6620, Baseband 6630, Baseband 6641, Baseband
6648, Radio Processor 6337, Radio Processor 6347.
Additionally, there are Baseband G3 and Baseband G3.1 that
are not released yet. Those shall also support Radio 6626.
Additionally, Radio 6626 shall be supported in configurations
with Baseband R503.
Note:
BB G3 has been released on 20. Q4. G3.1 is planned to be
released on 21.Q2.
– MR9002-SP4
Additionally, there are Baseband G3 and Baseband G3.1 that
are not released yet. Those shall also support Radio 6626.
Additionally, Radio 6626 shall be supported in configurations
with Baseband R503.
Additionally, Visby Radios shall be supported by Radio
Gateway(R608&R308&R609).
Additionally, Visby Radios shall also be supported with P614.
Note:
1. BB G3 has been released on 20.Q4. G3.1 is planned to be
released from 21.Q3.(BB6621/6631 to be released on
Ericsson Internal

2023-12-21 PF24
21.Q3, RANP6651/RANP6647/RP6353 to be released on

21.Q4, RP6339 to be released on 22.Q1).
2. DUS is not required by SPM anymore.
FDD Radio 4466 for MR8930-SP1 is the VISBY Triple band radio based
on Radon with 4T4R/4T4R/4T4R. The key requirements are as below.
 Maximum Output Power: 320W-720W
Note:
2. Specific Max Output Power is defined in FV MRs, e.g Max
Output Power for FDD Radio 4466 is 640w.
– Maximum 90 MHz for FDD Radio 4466 per band
Note:
1. Maximum GSM/NB-SA/LTE 1.4&3MHz IBW: DL 20 MHz UL full
band IBW.
2. B65/N65 is the max IBW in UL/DL defined in 3GPP 38.104.

Note:
B1B3B7.

– 6 for NR FDD
– 6 for ESS
– 24 for NR FDD
– 24 for ESS
Ericsson Internal

2023-12-21 PF24

uplink
Note：
 RAN support
GSM, WCDMA, FDD-LTE, NR, ESS, NB-IOT (SA, GB,
IB) for FDD Radio 4466
Note:
SRO GSM is not in MR8930-SP1 scope for FDD Radio
4466. It
depends on the HW DMS study on low band radio.
There is a separated SP for DUG support on Visby Radio
 CPRI: 2.5, 4.9, 9.8,10.1 and 25Gbps
Note:
Slave supports all CPRI line rates, Master only supports 2.5,
9.8, 10,1 and 25Gbps.
Japan
 NR support
– 5MHz, 10MHz, 15MHz, 20MHz, 25 MHz, 30MHz,
40MHz with 15 kHz SCS.
Note:
BB.
 ESS support
 LTE Channel BW
 Additional LTE Channel BW
B3: 4.6 MHz, 4.8 MHz and 9 MHz
Ericsson Internal

2023-12-21 PF24
Note:
3. Subsequent FVs have different CBWs. If there is
special CBW requirement in FVs, Radio system should
align with SPM firstly.
4. No need to support 14.8 MHz CBW. This decision is
made from Oslo 4T4R requirement forum and Ottawa
requirement forum(14.8MHz LTE BW support).
 Not support PIMC, PIMD, PIMA and EOC for Radon based
radios
Note:
3. GSM+WCDMA+another RAT shall not be supported per
RF port per band.
4. ESS is 2 RATs (NR+ESS) at the same time, so
GSM+LTE+NR+ESS shall also be supported and shall be
considered as triple RAT configuration.
 FDD Radio 4466 shall be supported with the following DUs and
Baseband units:
Additionally, there are Baseband G3.0 and Baseband G3.1
that are not released yet. Those shall also support FDD Radio
4466.
Additionally, FDD Radio 4466 shall be supported in
configurations with Baseband R503 and
configurations with R608 as one of XMU04.
Note:
BB G3 has been released on 20.Q4 while G3.1 is planned to
be released on 21.Q2.
FDD Radio 4456 for MR9609-SP1 is the VISBY Triple band radio based
on Radon with 4T4R/4T4R/4T0R. The key requirements are as below.
 Maximum Output Power: 320W
Note:
4. Max Output Power for FDD Radio 4456 is 320w.
Ericsson Internal

2023-12-21 PF24
– Maximum 40 MHz for FDD Radio 4456 per band

Note:
3. Maximum NB-SA/LTE 1.4&3MHz IBW: DL 20 MHz UL full band
IBW.
Note:
B1CB3JB75C.

– 6 for LTE-FDD
– 6 for NR FDD
– 6 for ESS
– 24 for LTE-FDD
– 24 for NR-FDD
– 24 for ESS
uplink
Note：
 RAN support for Radio 4456
LTE-FDD, NR-FDD, ESS, NB-IOT (SA, GB, IB) and
SDL support for NR CA
 CPRI: 2.5, 4.9, 9.8,10.1 and 25Gbps

Note:
Slave supports all CPRI line rates, Master only supports 2.5,
9.8, 10,1 and 25Gbps.
Ericsson Internal

2023-12-21 PF24

Japan
 NR support
– 5MHz, 10MHz, 15MHz, 20MHz, 25 MHz, 30MHz,
40MHz with 15 kHz SCS.
Note:
BB.
 ESS support
 LTE Channel BW
 Not support PIMC, PIMD, PIMA and EOC for Radon based
radios
 FDD Radio 4456 shall be supported with the following
Baseband units:
Baseband 6648, Radio Processor 6337, Radio Processor
6347.
Additionally, there are Baseband G3.0 and Baseband G3.1
that are not released yet. Those shall also support FDD Radio
4456.
configurations with Baseband R503 and
configurations with R608 as one of XMU04.
1.11.3[2.6.3] Interaction
Not Applicable for MR9002-1, since it does not introduce any new
feature.
For MR8930-1 FDD Radio 4466 and MR9002-SP4

Ericsson Internal

2023-12-21 PF24
When in “Deep Sleep” mode, there would be no traffic, neither be

temperature-related power backoff functions running. So the function
“Deep Sleep” does not impact legacy features on RU.
This “Deep Sleep” function shall support BB G2/G3.
The Dynamic PA VDD function may interact with other legacy

functions, for example, PA VDD temperature/frequency compensation
(a legacy PA Control function).
Dynamic PA VDD have dependency on DPD functionality. If the DPD

is in idle state or recalibration state, this function should not update PA
VDD value.
The adjustment may be combined for both functions affecting PA VDD

voltage value. To avoid ping-pong effect, the interval of Dynamic PA
VDD would be longer than PA VDD temperature/frequency
compensation period (current setting period is 1s). The Dynamic PA
VDD adjust interval may be 15-30s. Even the increase request step
and decrease request interval can be adjusted separately to mitigate
risk to PA.
This function shall support both BB G2 and G3.
1.11.4[2.6.4] Limitations
 Only NR SCS with 15 kHz is released on FDD radios.
 ESS has not been supported on 25Gbit CPRI on G3 BB and
G3.1 BB.
 GSM G1 only supports fixed 3-sectors configurations. For RBB
44_2W, RBB44_2S, RBB44_2T, 4WRXD was not supported
by GSM G1. Only 2-way RX diversity can be supported in
above RBBs.
 Radio 6626 cascading was not be supported from DUG side.
 Maximum two radio 6626 can be supported by one DUG.
 All 2ME scenarios would be supported when MR8930-1 with
limitation
– Operator must connect different MEs to DATA1 and
DATA2 on Visby, since there is only 1 NGS
synchronization path (between DATA1 and DATA2)
– For cascading scenario, DATA1In->DATA2Out,
DATA3In->DATA4Out.
Ericsson Internal

2023-12-21 PF24
– What’s more, every bridge level radio in the same cascading line should
configured with the same either DATA1In->DATA2Out or DATA3In-
>DATA4Out as the first level.
 When MR9002-2 delivered, support up to 2ME scenarios with

only limitation as blow
DATA3In->DATA4Out.
 When MR9784 delivered, support 3ME/4ME scenarios with
only limitation as blow
DATA3In->DATA4Out.
– What’s more, every bridge level radio in the same cascading line should
configured with the same either DATA1In->DATA2Out or DATA3In-
>DATA4Out as the first level.
 While WCDMA DU Radio Node is connected to RiPort DATA_1 on

Visby Radios, the Baseband Radio Node must not be connected to
RiPort DATA_3 on Visby Radios. This is because the default AxC ID
pool on DATA_1 used by DUW for mixed mode configuration conflicts
with the pool on DATA_3 used by G2 BB and onward.
 Because multiple cascading link configuration is not support by CAT
on the single BB, Visby Radios will not support any multiple cascading
link configuration on single BB. (It is agreed by SPM). Cases that more
than one Ri links are configured between single BB and the first
cascaded radio will be identified as multiple cascading link
configuration by CAT, including cases in below diagram. Please Note
that below diagram shows the cases that the first and the second
cascaded radios are all Visby Radios, but the limitation will also be
applicable to cases that second cascaded radio and all next radios
can be either Visby radios or other type of radios.
Ericsson Internal

2023-12-21 PF24
Ericsson Internal

2023-12-21 PF24
1.11.5[2.6.5] Benefits
1.11.5.1[2.6.5.1] Description
A 6T6R/6T6R 3-sector dual band radio with 6 antenna ports.
A 4T4R/4T4R/4T4R Triple band FDD radio with 4 antenna ports.
More total output power（up to 720W）
1.11.5.2[2.6.5.2] Observability of Benefits
N/A
1.11.6[2.6.6] Serviceability
N/A
Ericsson Internal

2023-12-21 PF24
2[3] Use Case (UC) Analysis
2.1[3.1] External RAN Node Impact and Network Level UC Analysis
No functional, no impact on Use Case foreseen.
2.2[3.2] RAN Level UC Analysis
2.3[3.3] Network Function UC Analysis
No functional, no impact on Use Case foreseen
2.4[3.4] Node Group UC Analysis
2.4.1[3.4.1] MSMM/MSSM UC Analysis
2.4.2[3.4.2] MORAN UC Analysis
No functional, no impact on Use Case foreseen. Legacy MORAN

support.
2.5[3.5] Node Level UC Analysis
2.5.1[3.5.1] UC Diagram
2.5.2[3.5.2] UC Anatomy

Ericsson Internal

2023-12-21 PF24
[4] (SYSFUNC Siyu)Cost Estimates
2.6[4.1] GSM G1 Specific Cost Estimation Summary

Table 19 Cost summary in team weeks (state explicitly if something else is used)
US<n> XFT BSC
US1 190 mhours
US2 2810 mhours
US3 1050 mhours
US4 1-2 TWs

US5 470 mhours
US6 440 mhours
US7 710 mhours
US8 150 mhours
Ericsson Internal

2023-12-21 PF24
2.7[4.2] Cost for SP 10565-0937/09002-SP1

Coste estimates from
Phase Competence area Pre-prestudy Prestudy

Prestudy Total Prestudy cost
Value Package Proof Point activities
PD LRAT FM
WRAT FM
GRAT FM
BBI FM
CAT FM 22760
COAM
COAM-RBS TOOLS
HWM 22760
HWM-NC 280
HWM-Radio 22480
HWM-XMU
NCI
IELL
APC
ASC
SCH
SYNC
TN FM
RBS CS FM
OSE Platform FM
CPI 638
HW 48712
HW Sys & Config 5140
RBS CPI 30
Product Package 20
Enclosure & Power Design 4488
Radio Design 39034
Digital Design
Site Equipment 400
AIS
OSS
ENM
WCDMA G1 3840
BEM 800
BOAM 280
TEC 2760
UBP
DBP
W RNC
GSM BTS G1 4860
G BSC
CDMA
pRBS
Verification 16890
RA Verification 11640
Test Analysis (DTAR) 120
Feature Verification 8520
Legacy Test Development 3000
BPV 200
HW Node & Module I&V (EEF) 3610
IODT 0
SV 840
CIRV 600
Value Package Proof Point activities 0
PD Total 98100
Ericsson Internal

2023-12-21 PF24
2.8[4.3] Cost for SP 10565-0937/09002-SP4

Ericsson Internal

2023-12-21 PF24
2.9[4.4] Cost for SP 10565-0937/8930-SP1
2.10[4.5] Cost for SP 105 65-0937/09609-1
2.10.1[4.5.1] HW Development Cost
~49.7 MSEK (includes KRC design, RSW, FuncSys, Supply, TrxCtrl, PTD)
2.10.1.1[4.5.1.1] TK Fulfillment compared to target at PRG
103.5%
2.10.2[4.5.2] SW Development Cost (man-hours)
5164h
2.10.3[4.5.3] TrxCtrl Development cost (man-hours)
320h
2.10.4[4.5.4] FuncSys Cost (man-hours)
180h
2.10.5[4.5.5] HW Verification cost – EEF

Ericsson Internal

2023-12-21 PF24
Table 20 HW Verification cost
Updated Updated
Man- Other Cost; hours kSEK after
Discipline Level hours kSEK after VEM VEM Comments
Integration Node 120
RA Radio Node 1200 200
EMC Node 520 200
Module
SUP
Safety Node
Module 120 120
SUP
RPV Node 600
Module 1880
Antenna
system Node Beam properties
RPE Node 760
Module
SUP
TE SW 160 TE SW estimation
HW 40 TE HW estimations
Functional verification
SUP cyclone
NEBS Design
I&V
Total: 5400 520 ???? ????
hours kSEK hours kSEK
2.10.6[4.5.6] SW Verification Cost
Table 21 SW Verification cost
Verification Discipline
RA Verification 600
Test Analysis
(OTAC&DTAR) 100
SSI/SSV 200
BPV 0
HW Node & Module I&V NA
Ericsson Internal

2023-12-21 PF24
(EEF)
IODT 0
SV 0
CIRV 0
Value Package Proof Point
activities
PD Total 600
2.11[4.6] Cost for SP 10565-0937/09002-8
2.11.1 Pre-study Cost:
Man-hours
Pre-study 120
2.11.2 Verification cost:

Verification Discipline Man-hours
RA Verification 200
Test Analysis (OTAC&DTAR) 40
SSI/SSV 0
BPV 0
HW Node & Module I&V (EEF) NA
IODT 0
SV 0
CIRV 0
Value Package Proof Point activities
CPI 30
PD Total 230
2.12[4.7] Cost for SP 10565-0937/09002-15
200h
Ericsson Internal

2023-12-21 PF24
180h
2.12.5[4.7.5] Verification cost
Man-
Verification Discipline hours
RA Verification 44600
Test Analysis
(OTAC&DTAR) 100
SSI/SSV 200
BPV 0
HW Node & Module I&V
(EEF) 40
IODT 0
SV 0
CIRV 0
Value Package Proof Point
activities
CPI 20
PD Total 5060
2.13 4.8 (SYSFUNC Siyu)Cost for SP 10565-0937/09268-1
4.8.1 Cost estimate for SP 10565-0937/09268-1
AREAS CA Study Execution
SYS FUNC 100mhrs 60mhrs
HW SYS 20mhrs 20mhrs

Ericsson Internal

2023-12-21 PF24
SW 100mhrs 300mhrs
NFV Test 104mhrs 16mhrs
Integration 200mhrs 640mhrs
EEF test 80mhrs 720 man-hour & 300KSEK
Filter team 100mhrs UL:40mhrs/DL: 34 mhrs
Total 704mhrs 1830mhrs &300KSEK
[4.7.6] HW Development Cost
2.13.1 SW Development Cost (man-hours)
40h
2.13.2 TrxCtrl Development cost (man-hours)
2.13.3 FuncSys Cost (man-hours)
320h
2.13.4 Verification cost
Man-
Integration 640
RA Verification 880
Test Analysis
(OTAC&DTAR) 460
SSI/SSV 260
BPV 0
(EEF) 720
IODT 0
SV 0
Ericsson Internal

2023-12-21 PF24
CIRV 0
Value Package Proof
Point activities
PD Total 2240
2.14 Cost for MR11742 Wind noise (Man-hours)
2.14.1 HW development Cost:
Man-hours
Mechanical design 160

study
2.14.2 Verification cost:

Verification Discipline Man-hours
Thermal & I&V 50
PD Total 120
2.15 Cost for SP 10565-0937/09002-16
[4.7.7] HW Development Cost
360h
20h
None
40h
Verification Discipline Man-

Ericsson Internal

2023-12-21 PF24
hours
RA Verification
Test Analysis
(OTAC&DTAR) 60
Feature Verification
SSI/SSV
BPV
(EEF) 360
IODT
SV
CIRV
Integration 720
CPI 20
PD Total 1560
2.16 Cost for SP 10565-0937/10135-1
1800h
2000h
200h
400h
Man-
RA Verification
Test Analysis
(OTAC&DTAR) 480
Ericsson Internal

2023-12-21 PF24
Feature Verification
SSI/SSV 400
BPV
(EEF) 3320
IODT
SV
CIRV
CPI 20
PD Total 8870
2.17 Cost for SP 10565-0937/09002-13
2.17.1[4.7.17] HW development cost (manhours)
In this SP, the feature enabling needs to depend on the HW BOM update,
which fixed the voltage drop issue found by MR11923-1. The HW
development is estimated around 40 manhours.
80 manhours
40 manhours
80 manhours
Man-
RA Verification
Test Analysis
(OTAC&DTAR) 40
SSI/SSV 20
BPV
HW Node & Module I&V 80
Ericsson Internal

2023-12-21 PF24
(EEF)
IODT
SV
CIRV
CPI 20
PD Total 380
Ericsson Internal

2023-12-21 PF24
3 Realization Overview
3.1[4.8] Description
The realization of Visby Radio 6626 is illustrated in the following

chapters including SW and HW solution.
3.2[4.9] System Class Descriptions
See chapter 7 and Chapter 8.
3.3[4.10] Realizations
N/A
Ericsson Internal

2023-12-21 PF24
4[5] Impact on Behavior/Monitoring/Handling of the System
4.1[5.1] Licensing
There exists power license for Radio. And the default value is 20W for
the total power. No need extra license for LTE(G1,
G2)&WCDMA(G1,G2)&GSM G2.
4.1.1[5.1.1] HWAC/Capacity features/functions
Existing HWACs support the required Output Power for GSM

Baseband Node (GSM G2), WCDMA, LTE and NR but not for GSM
DU Radio Node (GSM G1).
Existing HWACs support the carrier/bandwidth necessary for GSM,

WCDMA, LTE and NR.
The existing HWACs are described in Table 22 Existing HWACs.
Table 22 Existing HWACs
HWAC Product Name HWAC Product Comment

Number
GSM Output Power 20W to 40W FAK 101 0009 GSM G1
Fixed 20 W step
Fixed 20 W step
Fixed 20 W step
Fixed 20 W step
Fixed 20 W step
Fixed 20 W step
Fixed 20 W step
Output Power 20W Step FAK 101 0155 GSM G2, W, L & NR
20W step incr.
GSM Cell Carrier (TRX) FAK 101 0008 GSM G1
GSM Cell Carrier (TRX) ERS FAK 101 0076 GSM G2
WCDMA Number of Cell Carriers FAJ 121 1344 WCDMA
LTE FDD Channel Bandwidth FAK 101 0157 LTE FDD 5 MHz incr.
LTE TDD Channel Bandwidth FAK 101 0213 LTE TDD 5 MHz incr.
NR FDD Channel Bandwidth 5 FAK 101 0153 NR FDD 5 MHz incr.
MHz
Ericsson Internal

2023-12-21 PF24
NR TDD Channel Bandwidth 5 FAK 101 0154 NR TDD 5 MHz incr.

MHz
The limitation in the legacy HWACs is that the Output Power on GSM
DU Radio Node (GSM G1) is limited to 160 W.
Extending the GSM Output Power HWACs can be done in two ways:
1) Adding 15 new fixed 20 W steps.
This is the extension suggested in this NDS, see Table 23

Extending GSM G1 HWACs to 240 W Output Power. This is
included in the F2 scope but can be removed.
The extension includes both defining and releasing new HWACs

and implementation in GSM G1 SW to support new CXCs.
No new inf is required since the inf is a 20 W incremental inf.
2) Change the GSM Output Power HWACs to a single 20 W

incremental HWAC.
This has not been further analyzed since the cost will be higher
even though that the benefit would be that the maximum limitation
in the HWACs for GSM Output Power would once and for all be
removed.
Table 23 Extending GSM G1 HWACs to 240 W Output Power
HWAC Product Name HWAC Comment

Product
Number
GSM Output Power 160W to 180W TBD GSM G1 (fixed 20W step)
Ericsson Internal

2023-12-21 PF24
Decision from SPM Anders Pers and Kabir Kathuria in SPM

requirement forum on 24th , Aug::
Go for 240 W update with fixed 20 W steps for MR9002-SP1.
4.2[5.2] Network Impact
No impact.
4.3[5.3] Standardized Interfaces and Ericsson Proprietary Interfaces
No impact on Standardized interfaces.
Impact on Ericsson Proprietary interfaces on RRU-CBCI, TR-DCI

interface. More detailed info. refers to 8.1.2.
No impact on Standardized interfaces and Ericsson Proprietary

interfaces for MR9002-SP4.
4.4[5.4] Algorithms
N/A
[5.5] (SYSFUNC Siyu)Security/Privacy (mandatory)
After discussion with S-RA forum, there is no new or changed legacy

risks identified this feature.
https://eteamproject.internal.ericsson.com/browse/SRAF-800 (MR 9002-

SP1).
After discussions with S-RA Forum, no new or changed legacy have

been identified for below. The feature implements an updated triple
band radio.
https://eteamproject.internal.ericsson.com/browse/SRAF-1041 (MR
8930-SP1).
After discussion with S-RA Forum, no new or changed legacy risks

have been identified, and PTI value is 0 for MR9002-SP4.
[SRAF-1381] Radio, Radio 6626 Low Band Visby MR9002-SP4 -

eTeamProject (ericsson.com) (MR 9002-SP4)
After discussions with S-RA Forum, no new or changed legacy risks

have been identified for below triple band radio.
Ericsson Internal

2023-12-21 PF24
https://eteamproject.internal.ericsson.com/browse/SRAF-1533
(MR9609-SP1)
After discussions with S-RA Forum, no new or changed legacy risks

have been identified. PTI=0：
[SRAF-1814] MR9002-SP8 25Gbps CPRI Verification for

GSM/WCDMA - eTeamProject (ericsson.com)(MR 9002-SP8)
After discussion with S-RA Forum, no new or changed legacy risks

have been identified, and PTI value is 0 for MR9002-SP15.
[SRAF-1880] 7CC per port on B3 UL for Visby Radio 6626 B1B3 and
Radio 4466 B1B3B40/B41 - eTeamProject (ericsson.com)
After discussions with S-RA Forum, no new or changed legacy

risks have been identified and PTI=0 for MR9268- SP1.
[SRAF-2204] LTE GB NB-IoT coexistence with ESS - eTeamProject

(ericsson.com)(MR 9268- SP1)

risks have been identified and PTI=0 for MR9002-SP16.
[SRAF-3115] MR9002-16 Supporting GSM with IBW 28M on Visby

6626 B1B3 - eTeamProject (ericsson.com)

risks have been identified and PTI=0 for MR10135-1.
[SRAF-3141] SP Study for MR10135 Visby 6626 B0AB28 -

eTeamProject (ericsson.com)

risks have been identified and PTI=0 for MR9002-SP13.
[SRAF-3335] MR9002-SP13 Enable SHP on Visby 6626 B1B3 and

4466 B1B3B7 (B1B3) - eTeamProject (ericsson.com)
4.4.1[5.5.1] Mitigations and Vulnerability Management
N/A
For MR9002-SP4, [DVTA-889] 105 65-0937/09002-4 Radio 6626 Low

Band G, W, L, NR and ESS with 3 sectors and Tor sharing DVSWR -
eTeamProject (ericsson.com)
For MR9609-SP1: DVTA-1127 is Approved
For MR9002-SP8: DVTA-1400, No VA Impact

Ericsson Internal

2023-12-21 PF24
4.5[5.6] Upgrade (SW Management)
No impact on Upgrade process, but introduce a new HW that

impacts Upgrade Control File(UCF) and FDF. And new load
module should be added into G1,G2 and G3 DU. GSM need to
provide script for Visby binary file split and update document “RUS
SW Metadata file and deliveries to GSM”(2/1013-CRH 109 0526
Uen).
Note：
Introduced by MR9002-SP3, no need update in GSM binary file

split and document of “RUS SW Metadata file and deliveries to
GSM”.
4.5.1[5.6.1] Upgrade in MR9002_SP4
No impact for GSM G1 just UCF update.
No impact for WCDMA G1 just UCF update.
No impact on the Upgrade process and only need to update the FDF
file for G2,G3&G3.1 based on the new radio hardware.
4.6[5.7] Deployment and Customer Tools
The impact on ECT is updated in December 2021 due to that the new RBB will be
documented different than legacy RBB’s in RS Radio configurations 2/1056-
HRB105600.
This will impact ECT infrastructure with new or modified features:
1) We need to allow the user to select data port on Radio side for 58 RBB’s
2) Rules for combination of multi-sector configurations needs to be rewritten
3) Sector cascading needs to be modified due to that Radio now have 4 RiPorts.
4) Validation of configurations needs modification.
5) Transformation needs to be modified due to new selection of Data ports on radio
side.
6) ECT Diagram needs to handle and show user selection of data port on Radio.
Ericsson Internal

2023-12-21 PF24
4.6.1[5.7.1] Background for ECT impact analysis:
New Triple Band Radio 6626 with 6TX/6RX RfPorts and 4 RiPorts needs new Multi
sector RBB’s in order for the customer to use the radio for 3 sectors using 2TX/2RX
per sector or using 2 Radio units and get 4TX/4RX per sector.
Radio 6626 also supports a mix of FDD and TDD cells using same RfPort.
New Dual Band Radio 4466 with 4TX/4RX RfPorts and 4 RiPorts is included in
analysis.
- Support for RGW has been added to ECT and the new RBB shall be possible to
use with RGW.
- Some of the required RBBs are already supported by ECT but needs to be
modified.
4.6.2[5.7.2] Allow user to select RiPort on Radio side
The selection of Data port on radio side depends on Cascading, Mixed mode Radio
and Node Group Sync. When Radio has 4 RiPorts there are several alternatives that
can be used dependent on use case. The proposal is that ECT will have a default
connection of RiPorts but if the user wants another RiPort the user can open up GUI
and select ports freely.
In order to handle the RiPort choices, the RBB’s can be divided in fronthaul cases:
Table 24 Fronthaul cases
Case Fronthaul cases

a 1 Radio with 4 RiPorts or 1 AAS with 5 RiPorts used with 1-4/5 RiLinks
b 2 Radio with 4 RiPorts used with 2-8 RiLinks, No internal cascading
c 2 Radio with 4 RiPorts used with 1-2 RiLinks, With 1 internal cascaded RiLinks
d (Future) 2 Radio with 4 RiPorts used with 2 RiLinks, With 2 internal cascaded RiLinks
Each case can then be divided dependent on how many RiLinks is used in the RBB:
Table 25 Fronthaul cases with RiLinks
1 2 3 4 6 7 8
Case RiLink RiLink RiLink RiLink 5 RiLink RiLink RiLink RiLink
a a1 a2 a3 a4 a5 (ASS) na na na
b na b2 na b4 na b6 na b8
c c1 c2 na na na na na na
Ericsson Internal

2023-12-21 PF24
d (Future) na d2 na na na na na na
na = the case is not applicable, No RBB exist with this fronthaul.
These Fronthaul cases can then be applied on several RBB’s using same fronthaul even
though the RfPort part of the RBB is different.
This means that these fronthaul cases can be applied to all RBB’s that have radios with
more than 2 RiPorts,
a1 User need to select 1 Data port on radio

a4 User do not need to select, all ports used on Radio
a1 User need to select 1 Data port on AAS

a2 User need to select 2 Data port on AAS
a3 User need to select 3 Data port on ASS
a4 User need to select 4 Data port on ASS
a5 User do not need to select, all ports used on AAS
b2 User need to select 2 Data ports on radio

b8 User do not need to select, all ports used
c1 User need to select 1 Data port on radio plus cascade ports

c2 User need to select 2 Data port on radio plus cascade ports
d2 User needs to select data ports on second radio for cascade ports
For details about GUI impact see excel sheet:
4.6.3[5.7.3] RBBs to be modified or added to ECT.
RBBs’ that needs to be modified are listed per fronthaul case

Table 26 Fronthaul case per RBB
# from RBB Radio Radio ECT Radio Fronhaul

chp 6626 4466 Type Case
9.1.1
n=New
11 RBB11_1C x x Multi sector a1
12 RBB11_1D x x Multi sector a1
Ericsson Internal

2023-12-21 PF24
13 RBB11_1E x x Multi sector a1

14 RBB11_1F x x Multi sector a1
15 RBB11_1G x Multi sector a1
16 RBB11_1H x Multi sector a1
5 RBB22_1F x x Multi sector a1
6 RBB22_1G x x Multi sector a1
7 RBB22_1H x Multi sector a1
4466 RBB44_1D x Radio a1
17 RBB11_2A x x Multi sector a2
18 RBB11_2B x x Multi sector a2
19 RBB11_2C x x Multi sector a2
20 RBB11_2D x x Multi sector a2
21 RBB11_2E x Multi sector a2
22 RBB11_2F x Multi sector a2
8 RBB22_2K x x Multi sector a2
9 RBB22_2L x x Multi sector a2
10 RBB22_2M x Multi sector a2
4466 RBB44_2F x Radio a2
n21 RBB11_3A x x Multi sector a3
n22 RBB11_3B x x Multi sector a3
n23 RBB11_3C x x Multi sector a3
n24 RBB11_3D x x Multi sector a3
n25 RBB11_3E x Multi sector a3
n26 RBB11_3F x Multi sector a3
n14 RBB22_3C x Multi sector a3
4466_n1 RBB44_3E x Radio a3
n29 RBB11_4C x x Multi sector a4
n30 RBB11_4D x x Multi sector a4
n31 RBB11_4E x Multi sector a4
n32 RBB11_4F x Multi sector a4
n17 RBB22_4C x Multi sector a4
4466_n2 RBB44_4B x Radio a4
3 RBB44_2S x Multi sector b2
4 RBB44_2T x Multi sector b2
n2 RBB44_2W x Multi sector b2
n3 RBB44_4C x Multi sector b4
n4 RBB44_4D x Multi sector b4
Ericsson Internal

2023-12-21 PF24
n5 RBB44_4E x Multi sector b4

n6 RBB44_6A x Multi sector b6
n7 RBB44_6B x Multi sector b6
n9 RBB44_8A x Multi sector b8
n10 RBB44_8B x Multi sector b8
1 RBB44_1N x Multi sector c1
2 RBB44_1P x Multi sector c1
n1 RBB44_1S x Multi sector c1
n18 RBB44_2X x Multi sector c2
n19 RBB44_2Y x Multi sector c2
n20 RBB44_2Z x Multi sector c2
4.6.4[5.7.4] Changes for cell centric mode
The changes for the RBBs shall be visible in in sector definitions and the user
shall select RiPort on the Radio. If the RBB need different selections of RiPort
on Radio side then additional sector definitions needs to be created. In this
way the CIQ for Cell centric CIQ is not impacted.
Ericsson Internal

2023-12-21 PF24
4.6.5[5.7.5] Impact on transformation
Today ECT generate Radio port Data 1 and 2 by default , this not good since the ports
are also unlocked even if it’s not connected to a RiLink and this becomes a problem on
the live site since all unlocked equipment should be enabled and this cause problem. i.e.,
upgrade since a unused unlocked RiPort will become disabled.
So, the best would be to remove to create port that are not used even for legacy RBB’s,
note that if mixed mode is used in legacy Data 2 is used but not Data 1.
This means that for the modified or new RBB’s, ECT shall only create the RiPorts the
shall be used for a RiLink.
4.6.6[5.7.6] Mixed mode
Today Node Group Synch (NGS) can only use Data 1 and Data 2 but with new Visby
Radio all 4 ports can be used. This means that if the radio is used in mixed mode any port
can be selected.
This also means that when the user can select the data port on Radio/AAS side the user
can handle the ports for mixed mode Radio by selecting the RiPort they want to use.
This means that the choice that ECT have today after selecting “Add Radio used in Mixed
mode” shall be removed for the RBB’s where they can select RiPort on Radio side and
instead shall the choice be changed to “Radio Used in Mixed mode” with Boolean
expression true/false.
If then “Radio Used in Mixed mode” is set to true ECT shall add for each FRU
isSharedWithExternalMe = true.
4.6.7[5.7.7] Cascading
With RBB’s that have 4 RiPorts the cascading of sector needs to be modified.
A cascade chain may contain a mix of “old” RBB’s with a Radio that only have 2 Data ports
and “new” RBB’s with Radio’s with 4 Data ports.
The ECT logic have to consider all cases.
For the new RBB’s with 4 Data ports the following rule apply:
1) If Data 1 is connected toward Baseband, Data 2 can be used for cascading.
2) If Data 3 is connected toward Baseband, Data 4 can be used for cascading.
3) If both Data 2 and Data 4 is available for cascading Data 2 shall be used.
4) Only one cascade link / Radio is supported

Ericsson Internal

2023-12-21 PF24
When user selects connect sector to “Sector” then ECT can find the RiPort to cascade to
based on the rules.
If a free cascade port can’t be found an error shall be issued.
Cascading with 1 RiLinks

One Radio in first Sector
Case 1 2
Data 1 Data 1
Sector 1 or Data 2 Data 2
Data 3
Data 4
Sector 2 Data Data
Cascade to S1
1) If D1 to BB use D2, if not: If D3 to BB use D4.

2) Legacy, ECT will select Data 2
Figure 1 Cascading with 1 RiLink

Ericsson Internal

2023-12-21 PF24
Figure 2 Cascading with 1 RiLink error cases
Figure 3 Cascading with 2 RiLinks and 2 Radio

Ericsson Internal

2023-12-21 PF24
Figure 4 Ring topology
4.6.8[5.7.8] Impact on ECT HW support validation
The validation in ECT checks that a RAT cell is allowed to use the RBB, it does not
consider Band or if separate ports are used.
Radio 6626 is a triple band Radio with support for FDD and TDD which means that
GSM, WCDMA, LTE FDD, LTE TDD, NR FDD and NR TDD (F1) cells can be
allocated to a sector using Radio 6626. NB-IoT cells will also be possible to use on
Radio 6626.
The RS Radio configurations is updated for Single RAT dual RAT and triple RAT
including LTE FDD NbIot Stand alone. See enclosed excel sheet for updates
according to RS.
Cells marked with new shall be set to “yes”.
Open issue:
1) LTE TDD, NR TDD and LTE TDD+NR TDD does not have full support for new
RBB’s, shall they have that?
2) Since both FDD and TDD are allowed, how to allow such a configuration?
Ericsson Internal

2023-12-21 PF24
3) We should remove column LTEFDD_NBIOTG (Guard Band) and

LTEFDD_NBIOTI (InBand) since they need a LTE_FDD cell and that cell will be
validated for that sector.
4.6.9[5.7.9] RBBs to be added to ECT.
Legacy RBB’s supported in ECT that will be used with new RBB’s to form a 3 sector
configuration.
# from chp 9.1.1 Legacy RBB RfPorts RiPorts Multi sector? Node2 & TX/RX
Cascade
1 RBB44_1N A+B, A+B 1+ Internal cascade YES, Group 1 Yes 4+4
2 RBB44_1P C+D, C+D 1+ Internal cascade YES, Group 1 Yes 4+4
3 RBB44_2S A+B, A+B 2 YES, Group 2 Yes 4+4
4 RBB44_2T C+D, C+D 2 YES, Group 2 Yes 4+4
Legacy RBB's supported in ECT:

# from chp 9.1.1 Legacy RBB ECT Status Multi sector?
5 RBB22_1F Supported YES, Group 3
6 RBB22_1G Supported YES, Group 3
7 RBB22_1H Supported YES, Group 3
8 RBB22_2K Supported YES, Group 3
9 RBB22_2L Supported YES, Group 4
10 RBB22_2M Supported YES, Group 4
11 RBB11_1C Supported YES, Group 3
12 RBB11_1D Supported YES, Group 3
13 RBB11_1E Supported YES, Group 3
15 RBB11_1G Supported YES, Group 3
16 RBB11_1H Supported YES, Group 3
17 RBB11_2A Supported YES, Group 4
18 RBB11_2B Supported YES, Group 4
19 RBB11_2C Supported YES, Group 4
20 RBB11_2D Supported YES, Group 4
21 RBB11_2E Supported YES, Group 4
New RBB's to be added to ECT for both Radio 6626 and 4466
The most of them are multisector, but at the end of the list there are two non-multisector RBBs.
# form New RBB RfPorts RiPorts Multi sector? Node2 & TX/RX
Ericsson Internal

2023-12-21 PF24
9.1.1 Cascade
n=new
n1 RBB44_1S E+F, E+F 1+ Internal cascade YES, Group 1 Yes 4+4
n2 RBB44_2W E+F, E+F 2 YES, Group 2 Yes 4+4
n3 RBB44_4C A+B, A+B 4 YES, Group 5 Yes 4+4
n4 RBB44_4D C+D, C+D 4 YES, Group 5 Yes 4+4
n5 RBB44_4E E+F, E+F 4 YES, Group 5 Yes 4+4
n6 RBB44_6A A+B, A+B 6 YES, Group 6 Yes 4+4
n7 RBB44_6B C+D, C+D 6 YES, Group 6 Yes 4+4
n8 RBB44_6C E+F, E+F 6 YES, Group 6 Yes 4+4
n9 RBB44_8A A+B, A+B 8 YES, Group 7 No 4+4
n10 RBB44_8B C+D, C+D 8 YES, Group 7 No 4+4
n11 RBB44_8C E+F, E+F 8 YES, Group 7 No 4+4
n12 RBB22_3A A+B 3 YES, Group 8 Yes 2+2
n13 RBB22_3B C+D 3 YES, Group 8 Yes 2+2
n14 RBB22_3C E+F 3 YES, Group 8 Yes 2+2
n15 RBB22_4A A+B 4 YES, Group 9 No 2+2
n16 RBB22_4B C+D 4 YES, Group 9 No 2+2
n17 RBB22_4C E+F 4 YES, Group 9 No 2+2
n18 RBB44_2X A+B, A+B 2+ Internal cascade YES, Group 10 Yes 4+4
n19 RBB44_2Y C+D, C+D 2+ Internal cascade YES, Group 10 Yes 4+4
n20 RBB44_2Z E+F, E+F 2+ Internal cascade YES, Group 10 Yes 4+4
n21 RBB11_3A A 3 YES, Group 8 Yes 1+1
n22 RBB11_3B B 3 YES, Group 8 Yes 1+1
n23 RBB11_3C C 3 YES, Group 8 Yes 1+1
n24 RBB11_3D D 3 YES, Group 8 Yes 1+1
n25 RBB11_3E E 3 YES, Group 8 Yes 1+1
n26 RBB11_3F F 3 YES, Group 8 Yes 1+1
n27 RBB11_4A A 4 YES, Group 9 Yes 1+1
n28 RBB11_4B B 4 YES, Group 9 Yes 1+1
n29 RBB11_4C C 4 YES, Group 9 Yes 1+1
n30 RBB11_4D D 4 YES, Group 9 Yes 1+1
n31 RBB11_4E E 4 YES, Group 9 Yes 1+1
n32 RBB11_4F F 4 YES, Group 9 Yes 1+1
4466_n1 RBB44_3E A+B+C+D 3 NO Yes 4+4
4466_n1 RBB44_4B A+B+C+D 4 NO No 4+4
4.6.10[5.7.10] ABB and additional …
The modified RBB’s shall have same ABBs in legacy.

Ericsson Internal

2023-12-21 PF24
The new RBB’s shall follow the legacy rules.
1 RfBranch: ABB1_1A
2 RfBranches: ABB2_1A or ABB2_2A
4 RfBranches: ABB4_1A , ABB4_2A, ABB4_1B or ABB4_2B
The new Radio’s support TMA, all additional devices and have 2 external alarm
ports.
4.6.11[5.7.11] Impact on the way how ECT lists possible combinations.
The column with “Multi sector?” in the tables above groups RBB’s that
can be used together to form a multi sector configuration. Only RBBs
sharing the same Group id can be mixed on the same physical radio
resources. Currently ECT has very restrictive approach to what
combinations are allowed. The allowed ones are listed explicitly, see
the below code snippet. Each line shown below corresponds to a valid
combination (subsets are also possible).
<xsl:variable name="allowedRBBs" select="(

'RBB11_1C,RBB11_1D,RBB11_1E,RBB11_1F,RBB11_1G,RBB11_1H,RBB11_1J,RBB11_1K', //1_1
'RBB11_2A,RBB11_2B,RBB11_2C,RBB11_2D,RBB11_2E,RBB11_2F,RBB11_2G,RBB11_2H',
'RBB12_1C,RBB12_1D',
'RBB12_1E,RBB12_1F',
'RBB12_2B,RBB12_2C',
'RBB12_2D,RBB12_2E',
'RBB22_1F,RBB22_1G,RBB22_1H,RBB22_1J', //1_2
'RBB22_1P,RBB22_1Q',
'RBB22_2K,RBB22_2L,RBB22_2M,RBB22_2N',
'RBB22_2T,RBB22_2U',
'RBB22_1L,RBB22_1M',
'RBB22_2Q,RBB22_2R',
'RBB44_1E,RBB44_1F', //1_3
'RBB44_2G,RBB44_2H',
'RBB44_1J,RBB44_1K',
'RBB44_2U,RBB44_2V',
'RBB44_2N,RBB44_2P',
'RBB22_1F,RBB22_1G,RBB44_1F', //1_4
'RBB44_1E,RBB22_1H,RBB22_1J', //1_5
'RBB22_2K,RBB22_2L,RBB44_2H',
'RBB44_2G,RBB22_2M,RBB22_2N',
'RBB22_1F_B13,RBB22_1G_B13',
'RBB22_2K_B13,RBB22_2L_B13'
)"/>
All the yellow RBBs have the same radio equipment part and they are connected to
baseband in exactly the same way, which means that theoretically we could consider
combining them. Unfortunately, users are not able to combine e.g. RBB11_1C,
RBB11_1D with RBB22_1G (and many others) because in the allowedRBBs list
there is no entry covering that combination.
The way how allowedRBBs is currently defined and interpreted causes that the
following combinations are either allowed or prohibited (let’s focus on the yellow
ones only):
Ericsson Internal

2023-12-21 PF24
a) All sectors sharing the same radio equipment use the same number of RfPorts:
- 1x RfPort per sector à Allowed: line 1_1
- 2x RfPorts per sector à Allowed: line 1_2
- 4x RfPorts per sector à Allowed line 1_3
b) Combining sectors that use different number of RfPorts

- sectors with 2x RfPorts and with 4x RfPorts à Allowed: 1_4 and 1_5)
- sectors with 1x RfPorts and with 2x RfPorts àNot supported
- sectors with 1x RfPorts and with 4x RfPorts àNot supported
- sectors with 1x RfPorts, with 2x RfPorts and with 4x RfPorts àNot supported
The goal is to start supporting all combinations within each group even the red ones.
The way how “allowedRBBs” variable is defined shall be updated. Consider

something like in the below example. Or course, if XFT decides that another way of
implementing this idea will be better/easier, use it instead of the below code. All the
5x yellow lines were merged into one common line. RBBs belonging to group 4 were
also merged. The turquoise lines correspond to RBBs that are to be added due to
this MR.
<xsl:variable name="allowedRBBs_2" select="(
'RBB11_1C,RBB11_1D,RBB11_1E,RBB11_1F,RBB11_1G,RBB11_1H,RBB11_1J,RBB11_1K,RBB22_1F,RBB22_1G,RBB2
2_1H,RBB22_1J,RBB44_1E,RBB44_1F', // Group 3
'RBB11_2A,RBB11_2B,RBB11_2C,RBB11_2D,RBB11_2E,RBB11_2F,RBB11_2G,RBB11_2H,RBB22_2K,RBB22_2L,RBB2
2_2M,RBB22_2N,RBB44_2G,RBB44_2H', // Group 4
'RBB12_1C,RBB12_1D',
'RBB12_1E,RBB12_1F',
'RBB12_2B,RBB12_2C',
'RBB12_2D,RBB12_2E',
'RBB22_1P,RBB22_1Q',
'RBB22_2T,RBB22_2U',
'RBB22_1L,RBB22_1M',
'RBB44_1J,RBB44_1K',
'RBB44_2U,RBB44_2V',
'RBB44_2N,RBB44_2P',
'RBB22_1F_B13,RBB22_1G_B13',
'RBB22_2K_B13,RBB22_2L_B13',
'RBB11_3A,RBB11_3B,RBB11_3C,RBB11_3D,RBB11_3E,RBB11_3F,RBB22_3A,RBB22_3B,RBB22_3C, //
Group 8
'RBB11_4A,RBB11_4B,RBB11_4C,RBB11_4D,RBB11_4E,RBB11_4F,RBB22_4A,RBB22_4B,RBB22_4C, //
Group 9
'RBB44_4C,RBB44_4D,RBB44_4E’, // Group 5
'RBB44_2X,RBB44_2Y,RBB44_2Z', // Group 10
'RBB44_2S,RBB44_2T,RBB44_2W', // Group 2
'RBB44_1N,RBB44_1P,RBB44_1S', // Group 1
'RBB44_6A,RBB44_6B,RBB44_6C', // Group 6
'RBB44_8A,RBB44_8B,RBB44_8C', // Group 7
)"/>
Ericsson Internal

2023-12-21 PF24
4.6.12[5.7.12] Validation
Unlike the existing approach, not every combination of sectors from one group
defined in one line in “allowedRBBs_2” is possible. A new validation rule must be
defined to make sure that the sectors defined using RBBs belonging the same group
can be combined on the same radio equipment. The rule shall check that:
There may be no more than one sector connected to the same RfPort instance.
It means that e.g. RBB11_3C cannot coexist together with RBB22_3B, as both try to
use RfPort=C. Such combination should result in validation error
4.6.13[5.7.13] Drawing impact due to multisector RBB’s
The shared equipment part must be drawn in a flexible way to match the actual
combination.
– The number of RfPorts displayed per Radio unit (either 2, 4, 6 or 8) must correspond
to the actual combination. Currently the case with 6x RfPorts is not supported.
– Currently RfPorts used by the same sector are drawn close to each other. Bigger gap
between RfPorts used by different sectors. Would be nice to keep that approach, but
if it turns out to be too complex, we may use the same distance between RfPorts
regardless of what sectors they are connected to
The way how the diagrams look like is defined in

/ect-generator-front-end/configuration-generator/src-ts/configuration-generator/
regions/diagramregion/elements/boxes/sector/RadioBox.ts
Currently only some combinations can be drawn. Each picture is associated to a

specific definition from RadioBox.ts that is responsible for drawing it.
Radio with 2x RfPorts
Existing
rbbTypes: ['RBB11_1C', 'RBB11_1D']
Existing
rbbTypes: ['RBB11_1C', 'RBB11_1D', 'RBB11_1E', 'RBB11_1F']

Ericsson Internal

2023-12-21 PF24
rbbTypes: ['RBB22_1F','RBB22_1G']
New
A possibility to draw the below combinations must be added:
Existing
None
New
Currently not covered at all. The possibility of drawing different

combinations like the ones below must be added:
Ericsson Internal

2023-12-21 PF24
Currently when any of RBBs using RfPort >= E is present it is

assumed that it is an 8Tx/8Rx Radio. It shall be changed and Ports G
and H shall be displayed only if used.
Existing
rbbTypes: ['RBB11_1C', 'RBB11_1D', 'RBB11_1E', 'RBB11_1F',

'RBB11_1G', 'RBB11_1H', 'RBB11_1J', 'RBB11_1K']
Ericsson Internal

2023-12-21 PF24
rbbTypes: ['RBB22_1F','RBB22_1G','RBB22_1H','RBB22_1J']
rbbTypes: ['RBB22_1F','RBB22_1G','RBB44_1F']
Ericsson Internal

2023-12-21 PF24
rbbTypes: ['RBB44_1E','RBB22_1H','RBB22_1J']
rbbTypes: ['RBB44_1E','RBB44_1F']
New
It needs to be extended to enable drawing new combinations like that:

Ericsson Internal

2023-12-21 PF24
4.6.14[5.7.14] Drawing impact due to user can select RiPort
Today in ECT the Data ports are shown in the digram:
If we now allow the user to select Data port this shall be visible in the digram.
I.e. The user select D1+D3+D4 instead then the diagram shall show it.
SectorId 1
RadioType AIR-AAS
RBB RBBAIR_3A
Used in Mixed mode false
Connect sector to BB
Connect RiLink 1 to BB port A
Connect RiLink 2 to BB port B
Connect RiLink 3 to BB port C
¤ Change Radio Data Port? Yes
RiLink 1 Data port 1
The proposal is to still show same amount of ports but change the name.
Ericsson Internal

2023-12-21 PF24
If user selects D1+ D4+ D3 then ECT has to follow this since the RiLink need to follow what
is specified to connect to for BB side also:
SectorId 1
RadioType AIR-AAS
RBB RBBAIR_3A
Used in Mixed mode false
¤ Change Radio Data Port? Yes
Same principle to be used for RBB’s with 2 Radio:
SectorId 1
RadioType MultiSector
RBB RBBxx_4x
Sector Owns Radio yes
Used in Mixed mode true/false
Ericsson Internal

2023-12-21 PF24

Connect RiLink 4 to BB port D
¤ Change Radio Data port for
RiLink: Yes
RiLink 1 Radio 1 Data port 1
For case c where the Radio changes it seems like we can handle to move RiLink to Radio 2
for mixed mode in design base so this would solve case c when user specify “connect to”
Radio 2:
Ericsson Internal

2023-12-21 PF24
Regarding mixed mode, ECT now show Node 1 or Node 2 as dotted line dependent user
selection. This dotted line needs to be removed for RBB’s with 4 RiPorts since we don’t
know which port that is used for the other node.
Discussion: If user select “Used in Mixed mode” = true the drawing could add a symbol to
the Radio. The problem is then shall that be added to legacy RBB also? Since the mixed
mode may auto detected if Radio is used in mixed mode or not in the future I suggest not
to add any symbol for mixed mode in the drawing since the attribute will be set
automatically after integration.
4.6.15[5.7.15] MR11743 (qpiosob)
According to 9.3.3.1.2 (see eight last RBBs starting from RBB44_1E onwards) couple of
new RBBs are needed. Some legacy RBBs must be modified.
HwSupport should be set according to the below example.
Newly added RBBs should have support for adding TMA and other additional devices
(RET, RAE and so forth). ABB4_1A and ABB4_2A shall be used.
RBB44_1E (Modify). Currently user can select only port 1 or 2. It must be modified in
such way that ports 3 and 4 should also available (just as for RBB44_1D), see below
Now After update

Ericsson Internal

2023-12-21 PF24
RBB44_1T (New) It must be introduced to ECT in "Multi_sector_Radio" group It should

look just like updated RBB44_1E shown above but with RfPorts C,D,E,F instead
RBB44_2G (Modify). Currently this RBB uses all available RiPorts (2 out of 2) so we
don't allow any selection here. As now it will use 2 out of 4, it shall have the possibility to
"Change Radio Data port" added and also to set "Radio used in Mixed Mode". It should
look similarly to updated RBB44_1E above but with list of RiLink Data ports like fort
RBB44_2F. See below
Now After update
RBB44_2AD (New) Must be added in "Multi_sector_Radio" group. It should be

implemented just like updated RBB44_2G shown above but with RfPorts C,D,E,F instead
RBB44_3F (New). Will look just like RBB44_3E. The only difference is that it should
belong to “Multi_sector_Radio” group (currently supporte RBB44_3E belongs to "Radio"
group)
Ericsson Internal

2023-12-21 PF24
RBB44_3G (New) Must look just like RBB44_3F shown above. The only difference is
that it will use RfPorts C, D, E, F instead of A, B, C, D
RBB44_4F (New). As all 4 Data ports are used, no selection by Change Radio Data port
is needed. Also Radio used in Mixed Mode is not needed.
RBB44_4G (new) Must be added to ECT. It will looks exactly like RBB44_4F, but with
RfPorts C,D,E,F instead
EquipmentSupportFunctions.java
Groups of allowed multi sector radio sets defined in this class (set
ALLOWED_MULTI_SECTOR_RADIO_SETS) must be updated
new TreeSet<>(Arrays.asList("RBB11_1C", "RBB11_1D", "RBB11_1E", "RBB11_1F",

"RBB11_1G", "RBB11_1H", "RBB11_1J", "RBB11_1K", "RBB22_1F", "RBB22_1G",
Ericsson Internal

2023-12-21 PF24
"RBB22_1H", "RBB22_1J", "RBB44_1E", "RBB44_1F")),  RBB44_1T must be

added here. RBB44_1E is already on that list
new TreeSet<>(Arrays.asList("RBB11_2A", "RBB11_2B", "RBB11_2C", "RBB11_2D",

"RBB11_2E", "RBB11_2F", "RBB11_2G", "RBB11_2H", "RBB22_2K", "RBB22_2L",
"RBB22_2M", "RBB22_2N", "RBB44_2G", "RBB44_2H")),  RBB44_2AD must be
added here. RBB44_2G is already on that list
new TreeSet<>(Arrays.asList("RBB22_3A", "RBB22_3B", "RBB22_3C", "RBB11_3A",

"RBB11_3B", "RBB11_3C", "RBB11_3D", "RBB11_3E", "RBB11_3F")),  RBB44_3F
RBB44_3G must be added her
new TreeSet<>(Arrays.asList("RBB22_4A", "RBB22_4B", "RBB22_4C", "RBB11_4A",

"RBB11_4B", "RBB11_4C", "RBB11_4D", "RBB11_4E", "RBB11_4F")),  RBB44_4F
RBB44_4G must be added here
RBBDefinitions.java
This class contains list of all RBBs with info if they are allowed to use Visby specific
RiPorts 3 and 4. For the RBBs modified because of MR11743 flag NON_VISBY should
be removed (For RBB44_1E use A1 instead of A1_NON_VISBY and for RBB44_2G use
A2 instead of A2_NON_VISBY).
4.6.16[5.7.16] MR10135-SP1
[QPIOSOB 23.08.2023]
his chapter describes all changes that are needed in ECT because of MR10135-1 and
MR12096-1.
See 6.7.10 for more info about what ABBs shall be enabled for the new/modified RBBs
and about TMA/Additional Devices/Alarm Ports
Unfortunately seems that currently not all RBBs added in previous Visby SPs/MRs have
the possibility to add TMA and Additional Devices enabled in ECT (example: RBB11_3F,
RBB22_3A and so forth). Please fix it also in scope of MR10135-SP1 and add missing
support for TMA/ALD for all Visby RBBs.
The table below summarizes all RBBs that shall be added/changed.

The meaning of “FH” (Fronthaul) column is rather straightforward:
M+N: there are 4 RiPorts in total (M+N=4). M of them are used to connect the Radio to
this node, the remaining N ports will be used by other nodes, or for cascaded connection
to other Radios.
For FHs: 1+3, 2+2, 3+1 user must be able to select which of the available ports will be
taken. It means that not ECT must have the below attributes present on the GUI:
For FH: 4+0: there is need to have “Add Change Radio Data port” attribute, as all 4
RiPorts must be taken. Only “Radio used in Mixed Mode” is needed.
Ericsson Internal

2023-12-21 PF24
NEW RBB ECT RfBranch ABB FH HwSupport

or RadioType
OLD
RBB44_1Q
OLD Multi sector A,B,E,F ABB4_1A, ABB4_2A, 1+3 WCDMA, LTE FDD, NR FDD
OLD RBB44_1R Multi sector C,D,G,H ABB4_1A, ABB4_2A, 1+3 WCDMA, LTE FDD, NR FDD
OLD RBB44_2U Multi sector A,B,E,F ABB4_1A, ABB4_2A, 2+2 WCDMA, LTE FDD, NR FDD
OLD RBB44_2V Multi sector C,D,G,H ABB4_1A, ABB4_2A, 2+2 WCDMA, LTE FDD, NR FDD
NEW RBB11_3G Multi sector G ABB1_1A 3+1 LTE_FDD, NR FDD
ABB1_1A
NEW RBB11_3H Multi sector H 3+1 LTE_FDD, NR FDD
ABB1_1A
NEW RBB11_4G Multi sector G 4+0 LTE_FDD, NR FDD
ABB1_1A
NEW RBB11_4H Multi sector H 4+0 LTE_FDD, NR FDD
NEW RBB22_3D Multi sector G+H ABB2_1A, ABB2_2A 3+1 LTE_FDD, NR FDD
NEW RBB22_4D Multi sector G+H ABB2_1A, ABB2_2A 4+0 LTE_FDD, NR FDD
NEW RBB44_3H Multi sector E+F+G+H ABB4_1A, ABB4_2A 3+1 LTE_FDD, NR FDD
NEW RBB44_3J Multi sector A+B+E+F ABB4_1A, ABB4_2A 3+1 WCDMA, LTE_FDD, NR FDD
NEW RBB44_3K Multi sector C+D+G+H ABB4_1A, ABB4_2A 3+1 WCDMA, LTE_FDD, NR FDD
NEW RBB44_4H Multi sector E+F+G+H ABB4_1A, ABB4_2A 4+0 LTE_FDD, NR FDD
NEW RBB44_4J Multi sector A+B+E+F ABB4_1A, ABB4_2A 4+0 WCDMA, LTE_FDD, NR FDD
NEW RBB44_4K Multi sector C+D+G+H ABB4_1A, ABB4_2A 4+0 WCDMA, LTE_FDD, NR FDD
OLD RBB88_1A Radio A…H ABB8_1A, ABB8_1B, ABB8_4A 1+3 WCDMA, LTE_FDD, LTE TDD, NR FDD, NR MB TDD
OLD RBB88_2A Radio A…H ABB8_1A, ABB8_1B, ABB8_4A 2+2 WCDMA, LTE_FDD, LTE TDD, NR FDD, NR MB TDD
NEW RBB88_3A Radio A….H ABB8_1A, ABB8_1B, ABB8_4A 3+1 WCDMA, LTE_FDD, NR FDD
NEW RBB88_4B Radio A….H ABB8_1A, ABB8_1B, ABB8_4A 4+0 WCDMA, LTE_FDD, NR FDD
Scope of changes for RBBs marked as OLD in the above table:
- Replace old FH with 2 RiPorts with new FH that has 4 RiPorts.
- Replace old logic with “Add Radio used in Mixed Mode as” with new logic
with “Radio used in Mixed Mode” + Add Change Radio Data port
- Add WCDMA to the HW Support table
- For Multi sector radios - make it possible to combine them with other
RBBs with the same FH
- Update the diagrams

Ericsson Internal

2023-12-21 PF24
The content of HwSupport column was prepared based on current knowledge, As stated
in 9.3.5 MR10135-SP1: supports GSM, WCDMA, LTE-FDD, NR-FDD, NB-
IOT(SA,GB,IB) and ESS which suggests that the final set of supported RATs for each of
the RBBs may be different (especially in GSM and NBIOTS columns). It must be
checked during implementation in the latest /ch4 Building Blocks and Topologies – RS
Radio Config/.
EquipmentSupportFunctions.java
Groups of allowed multi sector radio sets defined in this class (set
ALLOWED_MULTI_SECTOR_RADIO_SETS) must be updated
Currently we have two sets for RBBs that in the table above are marked as “1+3”
new TreeSet<>(Arrays.asList("RBB44_1Q", "RBB44_1R")),
"RBB22_1H", "RBB22_1J", "RBB44_1E", "RBB44_1F", "RBB44_1T")),
They are separate because they have different assumptions. RBB44_1Q/1R assumed
that the Radio has 2 RiPorts only but 8x RfPorts (fixed number). The second group
consists of RBBs that have 4 RiPorts and flexible number of RfPorts dynamically shown
on the diagram. The sets must be merged into one common set.
It means that this picture…
… shall be substituted with picture that shows 4x RiPorts. RfPorts E and H are shown
only when needed.
Ericsson Internal

2023-12-21 PF24
After merging the 1+3 set should look like that:

"RBB22_1H", "RBB22_1J", "RBB44_1E", "RBB44_1F", “RBB44_1Q", "RBB44_1R
"RBB44_1T")),
Currently we also have two sets for RBBs that use 2x RiLinks (Group 2+2). The reason
is the same as for 1+3 group described above.
new TreeSet<>(Arrays.asList("RBB44_2U", "RBB44_2V")),

"RBB22_2M", "RBB22_2N", "RBB44_2G", "RBB44_2H", "RBB44_2AD")),
Also here the sets must be merged into one common set, and we should stop showing
8x RfPorts
It means that this picture…
…shall be substituted with picture that shows 4x RiPorts. RfPorts E and H are shown
only when needed.
Ericsson Internal

2023-12-21 PF24
After merging the common 2+2 set should look like that:
"RBB22_2M", "RBB22_2N", "RBB44_2G", "RBB44_2H", "RBB44_2AD", "RBB44_2U",
"RBB44_2V")),
Set for 3+1 RBBs shall be extended by adding new members:

"RBB11_3A", "RBB11_3B", "RBB11_3C", "RBB11_3D", "RBB11_3E", "RBB11_3F",
"RBB11_3G", "RBB11_3H", "RBB44_3E","RBB44_3F", "RBB44_3G",
"RBB44_3H","RBB44_3J","RBB44_3K"))
Set for 4+0 RBBs shall also be extended:

new TreeSet<>(Arrays.asList("RBB22_4A", "RBB22_4B", "RBB22_4C",
"RBB22_4D","RBB11_4A", "RBB11_4B", "RBB11_4C", "RBB11_4D", "RBB11_4E",
"RBB11_4F", "RBB11_4G","RBB11_4H" "RBB44_4F", "RBB44_4G",
"RBB44_4H","RBB44_4J","RBB44_4K")),
4.7[5.8] Configuration Management (CM)
No impact.
4.8[5.9] Performance Management (PM)
No impact.
4.9[5.10] Fault Management (FM)
4.9.1[5.10.1] General
New FaultID will be introduced to indicate slave power drop over

TRDCI interface, mapping to exist alarm. Details are as given below.
Item FaultID raised from Alarm to be mapped Severity Managed

RU to DU alarm Object
Class
1 POWER_SUPPL_48V_ Power Disturbance MINOR ExternalPower

Ericsson Internal

2023-12-21 PF24
NOT_AVAIL_PARTIAL Probable cause: 48V input

failure at slave port
POWER_INTERRUPT_I
NPUT_POWER_INSUF Additional text: Insufficient
FICIENT power, see additional info
for affected unit(s).
Probable cause: 48V
input failure at slave port
Additional text:
For FDD Radio 4466, there is no additional impact based on Radio

6626, which should be aligned with Radio 6626.
For MR 9002-SP4, no impact on Radio 6626 Low band based on

MR9002-SP1.
4.9.2[5.10.2] Alarm “Power Disturbance”
No impact.
Use Case Scenario:
Raise alarm - NODEUC638.A101
Cease alarm - NODEUC397.A38
4.10[5.11] Diagnostics and behavioural observability
No impact.
4.11[5.12] Characteristics and Traffic Model
No impact.
4.12[5.13] Migration
N/A
4.13[5.14] Power Consumption
The power consumption values for Radio 6626 should be filled into the
Power Calc2 tool.
4.14[5.15] Supply (Production)
Detailed refer to document below:

Ericsson Internal

2023-12-21 PF24
Industrialization IP for Visby PF
[5.16] (SYSFUNC Siyu)Services (Network Deployment & Customer

Support) (NO impact for MR9268)
4.14.1[5.16.1] Network Deployment (NRO)
BNEW Service Area Network (SAN) - Network Roll-Out (NRO) will

perform Service Adaptation work for Radio 6626, FDD Radio 4466
and FDD Radio 4456 developed by BNEW/DNEW. Below are listed
both deliverables and activities that may be created/performed by
NRO. This work is done using BNEW SAN NRO’s budget why the
NRO recourses do not directly impact the BNEW/DNEW product
development projects budgets.
Scope:
 Usability shall always be done on complete product before
released to market.
 NRO shall be invited to Usability test performed during the
development.
 Norm Hours for installing Radio 6626, FDD Radio 4466 and FDD
Radio 4456 shall be measured by the project during usability and
reported to NRO SPM. NRO will populate Premium Proposal with
the normhours.
 A Standard Service Object (SSO) shall be created or updated by
NRO so Radio 6626, FDD Radio 4466 and FDD Radio 4456 is
included in the SSO structure.
 Animation shall be produced by CPI for Radio 6626, FDD Radio
4466 and FDD Radio 4456 and NRO will attend in reviews.
 NRO shall be invited to FOA or FFI activities if such activity will be
performed
 The product shall be developed with a high focus on servicability
and easy deployment.
4.14.2[5.16.2] Customer Support, Hardware Services
SAN Customer Support, HW Services requirements should be verified and

implemented within development/design phase. The SoC should be reviewed
before PD2 and followed up before PD4. See requirement list in RBS
Baseline on this document 107/1056-HRB 105 600.
 Spare parts must be defined and documented in the Spare

Parts List for Ericsson Radio System & RBS 6000 (110/15411-
Ericsson Internal

2023-12-21 PF24
3/FAF 102 468) and Enclosures Spare Parts List (131/15411-

3/FAF 102 468)
 All spare parts should be easily replaceable in field, spare
parts can´t be configurable objects and must have a fixed
product number
 Requirements will be verified via mock-up/usability Test or
similar that should be arranged by PDU development project.
SAN CS must be invited to the Mock-up/usability verification
test
 Service Friendly Maintenance Engineering /spare part should
be secured. Correct instruction of replacement in field for all
defined spare parts should be described in the Maintenance
Manual.
 SAN CS HW Support should be part of PRA and GA release
meetings where service readiness will be assessed.
 Spare parts information should be provided, and all defined
spare parts are available in Spare Parts Catalogue with good
quality.
 Repair preparation should be fully developed and documented
before PRA and coordinated with SAN repair solutions
 Single unit package must be developed and prepared for all
spare parts and should be suitable for re-use in return flow.
4.15[5.17] Other technical areas
N/A
Ericsson Internal

2023-12-21 PF24
5[6] Feature Interaction

No impacts on the performance or observability of any other features
have been identified.
Ericsson Internal

2023-12-21 PF24
[7] (SW Xiaobo Su)Impact on SW Products
5.1[7.1] Common
[7.1.1] General
[7.1.2] -
[7.1.3] General
5.1.1 Interfaces Between Products
5.1.1.1[7.1.3.1] Impact on Node Public Interfaces
5.1.1.2[7.1.3.2] Impact on FM Public Interfaces
 WCDMA G1 RRU-CBCI:
 Because Visby extend RF port to E and F, and below signals

need update:
RRU_ANTENNA_POWER
RRU_CONFIG_SV
RRU_CONFIG_POWER_SV
More detailed info. refers to 8.7.3.4.3.
 New Fault Types for RF ports E-H (G&H are prepared for
future):
RRU_AUX_POW_SV_FAULT(CEASE)_IND:
RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_ANTENNA_BRANCH
_{E|F|G|H}
Enabler: RRU_ANTENNA_POWERx_REQ with corresponding auxPowerPort(x)

IE set to ‘ON’
RRU_TMA_LNA_SV_FAULT(CEASE)_IND:
RBS_FAULT_TYPE_LNA_{FAILURE|DEGRADED}_ANTENNA_BRANCH_{E|F|
G|H}
Enabler: RRU_CONFIG_SVx_REQ with corresponding tmaCurrent{Low|

High}LimPort(x) IE used.
Ericsson Internal

2023-12-21 PF24
RRU_CABLE_SV_FAULT(CEASE)_IND:
RBS_FAULT_TYPE_FEEDER_CABLE_DISCONNECTED_ANTENNA_BRANCH
_{E|F|G|H}
Enabler: RRU_CONFIG_POWER_SVx_REQ with corresponding

lowCurrentSupervision(x) IE set to ‘ON’.
Refer to chapter 8.7.3.9.1 for details.
 G2 TRDCI:
New faultId POWER_SUPPL_48V_NOT_AVAIL_PARTIAL

POWER_INTERRUPT_INPUT_POWER_INSUFFICIENT will be
added in TRS_FAULT/FAULTCEASE_ID message over TRDCI.
More detailed info. Refers to 8.9.4
5.1.1.3[7.1.3.3] Impact on FM Private Interfaces
WCDMA G1 MPSW:
The third shared sector info should be added in Eclm structure

EclmRfapAllocDevCfmS::EclmEraRfapAllocCfmParamsS
More detailed info. refers to chapter 8.7.3.7.
5.1.2[7.1.4] SW Architecture
No SW Architecture change in DU/Baseband and Radio.
5.1.3[7.1.5] SW Deployment
Only on Visby Radio 6626 and FDD Radio 4466 Radios.
5.2[7.2] RC (Radio Control) Function Module
No impact
5.3[7.3] RP (Radio Processing) Function Module
5.3.1[7.3.1] Inter-XBM Support
No impact
Ericsson Internal

2023-12-21 PF24
5.4[7.4] PP (Packet Processing) Function Module
5.4.1[7.4.1] Inter-XBM Support
No impact
5.5[7.5] LRAT_RC (LTE Radio Control) Function Module
No impact
5.6[7.6] LRAT_BB (LTE G1 Baseband) Function Module
No impact
5.7[7.7] WCDMA
5.7.1[7.7.1] Common
5.7.2[7.7.2] WRAT Function Module Specific
5.7.3[7.7.3] WCDMA G1 Specific for Radio 6626
5.7.3.1[7.7.3.1] Overview
For WCDMA DU node (G1), following functionalities need to be

supported on Radio 6626 66B1 66B3 C.
 New radio types with new radio load modules.
 RF ports E&F support (system only supports up to 4 RF ports

radio in design base), as well as the AISG 2.0 function on port
E (only port A-C in design base).
 3 sectors sharing on one radio unit (system only supports up to

2 sectors in design base).
 New RBBs to support 3-Sector configuration.
Note: Those RBBs more than 2T2R in each radio unit will not
be covered in this MR.
 Maximum 360W Output Power for all RF ports on B1.

Ericsson Internal

2023-12-21 PF24
5.7.3.2[7.7.3.2] Supported Frequency Bands on WCDMA
In a general Ericsson policy, frequency bands 1/2/4/5/8 are the

commonly used bands for WCDMA. For other bands that 3GPP claims
support on WCDMA, like Band 3 or Band 7, are generally not
supported by Ericsson if no explicit requirement from market.
But there are some exceptions, like B66, WCDMA is supported for the
B4 part of the spectrum.
Other similar relations:
B25 <-> B2
B26 <-> B5
B66 <-> B4
Therefore, WCDMA DU node (G1) with some Dual-Band or Triple-

Band radios can only work on Single Band configuration. For example,
Radio 6626 66B1 66B3 C will only work on Band 1.
5.7.3.3[7.7.3.3] New radio types with new radio load modules
UCF needs to be updated for new radio types. For Radon and Krypton
based radios, each of them shall have an individual
<PiuTypeLoadList> in UCF.
The LMs for Visby Platform should be added in Upgrade Package.
5.7.3.4[7.7.3.4] Support RF ports E&F
It is possible to support RF ports E&F on Radio 6626. While in

baseline, system can only support RF ports A-D.
To support more RF ports, the corresponding impacts in terms of

MOM structure, logical handling of device as well as fault handling of
possible RF ports E&F need also be analyzed.
5.7.3.4.1[7.7.3.4.1] MOM impact
1. Add possible values ANT_E & ANT_F for

AntFeederCable::objectAConnector.
2. Number of DPCL, TR, TPA, AI devices should be increased.

Ericsson Internal

2023-12-21 PF24
Note: The device cardinality changed from 4(AI/TPA)/24(TR/DPCL) to

8/48 to get MOM prepared for future 8 RF ports Radio, but MPSW will
only support 6(AI/TPA)/36(TR/DPCL) for Radio 6626.
1. Description of DPCL, TR, TPA and AI should be updated.
Take AiDevice as an example:
The RDN of this MO is AiDevice=1 to AiDevice=2 (if on an

AIU/sAIU/FU/RUW/RRU), or AiDevice=1 to AiDevice=4 (if on an AIR or RRUW),
or AiDevcie=1 to AiDevice=8 (if on an RRUW).
AiDevice=7 to AiDevice=8 are reserved for future radios.
5.7.3.4.2[7.7.3.4.2] MPSW impact
1. EC
a. RRU-CBCI, handle configuration of functionality for the new

ports
With support for Radios with 6 RF-ports, there are some CBCI
procedure requests that are inadequate, in that they can only
address up to the (first) four legacy RF ports (A-D).
Ericsson Internal

2023-12-21 PF24
The affected procedures are:
 RRU_ANTENNA_POWER
 RRU_CONFIG_SV
 RRU_CONFIG_POWER_SV
There are two different possibilities:
Alt 1) Revise requests through adding new IEs for new ports:
The request messages’ name of the above procedures will

be kept, only append extra IEs to represent the
configuration intention for RF ports/branches E&F.
Introduce a new capability for indicating supported RF

ports. MPSW only set IEs of RF ports E&F to valid values
when the capability represents.
Alt 2) New procedures for configuration of one RF port at a time

(preferred):
To make the procedure more extensible, it is proposed to

introduce three new messages with an RF-port-identifying
IE and IE(s) to represent the configuration intention for the
identified RF port/branch for new Radio units. MPSW shall
send the signal, with the port info identified, for each
configured RF ports.
Both new and legacy messages of the procedures above

shall be kept in CBCI signal file (cbci_rru.sig).
To distinguish between new and legacy Radio units, a new

capability RRU_CAP_RF_PORT_SUPPORT, for indicating
supported RF ports, shall also be introduced, and MPSW
will only send new signals when the capability is reported.
Refer to chapter 8.7.3.4.3 for detailed update of CBCI

signals.
b. RRU-CBCI, identification of new RF ports/branches in

fault(cease) indications
This part is corresponding to Fault Handling, so refer to

chapter 8.7.3.9 for details.
c. ECMI update for new ANT_E & ANT_F
d. Increase Device instances for DPCL, TR, TPA, AI
1) The statics device number should be increased in EC.

Ericsson Internal

2023-12-21 PF24
2) SUE for increased devices.
2. BOAM
a. MOM adaption for new MOM structure
b. ECMI adaption
c. AUE for DPCL, TR, TPA, AI devices
Add new Data Conversion (DC) to expand these devices.
5.7.3.4.3[7.7.3.4.3] RRU-CBCI update
This section listed the detailed update of each CBCI file.
cbci_rru.h:
…
/********************************************************/
/******** Capability identity ********/
/********************************************************/
#define RRU_CLOCK_DISTRIBUTION 0x01

#define RRU_DIGITAL_DELAY_MANAGEMENT_SUPPORT 0x02
…
#define RRU_CAP_RF_PORT_SUPPORT 0x0F
…
/********************************************************
* IE: RruRfPortSupportS::rfPorts[]
* IE: RruAntennaPower3ReqS::rfPort
* IE: RruAntennaPower2CfmS::rfPort
* IE: RruAntennaPower2CfmS::rfPort
* IE: RruConfigSv3ReqS::rfPort
* IE: RruConfigSv2CfmS::rfPort
* IE: RruConfigSv2RejS::rfPort
* IE: RruConfigPowerSv3ReqS::rfPort
* IE: RruConfigPowerSv2CfmS::rfPort
* IE: RruConfigPowerSv2RejS::rfPort
* Type: U16
* Mapping: [0..7] - RF port [A..H],
* [8...0xFFFF] - reserved (mapping extensions are compatible
addition)
* Range: (0-0xFFFF)
********************************************************/
#define RRU_RF_PORT_A 0
#define RRU_RF_PORT_B 1
#define RRU_RF_PORT_C 2
#define RRU_RF_PORT_D 3
#define RRU_RF_PORT_E 4
#define RRU_RF_PORT_F 5
#define RRU_RF_PORT_G 6
#define RRU_RF_PORT_H 7
…
Ericsson Internal

2023-12-21 PF24
/**********************************************
* IE: RruRfPortSupportS::numberOfRfPorts
* Type:U16
* Mapping: 1-to-1
* Range: [1..RRU_MAX_NUMBER_OF_RF_PORTS]
********************************************/
#define RRU_MAX_NUMBER_OF_RF_PORTS 12
…
cbci_rru.sig:
…
struct RruTmaSvModeSupportS
{
U16 numberOfTmaSvModes ;
U16 tmaSvModes[RRU_MAX_NUMBER_OF_TMA_SV_MODES];
};
/*
* Capability: RRU_CAP_RF_PORT_SUPPORT
* Explanation: This capability denotes the ability to report supported
RF ports
* Attributes:
* numberOfRfPorts Number of valid RF port entries in the list
* rfPorts[] List of supported RF ports. For values, see
* RRU_RF_PORT_* in cbci_rru.h.
*/
struct RruRfPortSupportS
{
U16 numberOfRfPorts;
U16 rfPorts [RRU_MAX_NUMBER_OF_RF_PORTS];
};
struct RruCapabilityS
{
U16 capabilityIdentity;
U16 capabilityLength;
union
{
struct RruClockDistributionS clockDistribution;
struct RruDigitalDelayManagementSupportS digitalDelay;
struct RruAnalogDelayManagementSupportS analogDelay;
struct RruExtAuxControlSupportS extAuxControl;
struct RruSettableIqDataFormatS settableIqDataFormat;
struct RruAdjustablePowerSupplyVoltageS
adjustablePowerSupplyVoltage;
struct RruRxOutputPortGainCharacteristicsS
rxOutputPortGainCharacteristics;
struct RruTmaSvModeSupportS tmaSvModeSupport;
struct RruRfPortSupportS rfPortSupportS;
} capability;
};
#define RRU_ANTENNA_POWER_REJ (TRP_RRU_SIGBASE + 0x21) /* !- SIGNO(struct

RruAntennaPowerRejS) -! */
struct RruAntennaPowerRejS
{
SIGSELECT sigNo;
Ericsson Internal

2023-12-21 PF24
U16 errorCode;
};
/
*************************************************************************
****************
* Revised procedure: RRU_ANTENNA_POWER(3_REQ,2_CFM,2_REJ)
* Addressing a single RF port in each invocation, port identity
reciprocated in CFM/REJ
*************************************************************************
****************/
/
*************************************************************************
*****
*
* Signal Name: RRU_ANTENNA_POWER3_REQ
* Allowed for capability: EXT_AUX_CONTROL_SUPPORT & RF_PORT_SUPPORT
* Description: Request for DC power feeding on RRU board.
* If the voltage level has not been set using
RRU_SET_POWER_SUPPLY_VOLTAGE_REQ,
* the 3GPP-band-specific default level shall be set
autonomously by the server.
*
* Data :
* rfPort RF port identifier
* auxPowerPort Power feed state through antenna feeder
*
*************************************************************************
*****/
#define RRU_ANTENNA_POWER3_REQ (TRP_RRU_SIGBASE + 0x47) /* !-

SIGNO(struct RruAntennaPower3ReqS) -! */
struct RruAntennaPower3ReqS
{
SIGSELECT sigNo;
U16 rfPort;
U16 auxPowerPort;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_ANTENNA2_POWER_CFM
*
* Data :
*
*************************************************************************
*****/
#define RRU_ANTENNA_POWER2_CFM (TRP_RRU_SIGBASE + 0x48) /* !-

SIGNO(struct RruAntennaPower2CfmS) -! */
struct RruAntennaPower2CfmS
{
SIGSELECT sigNo;
Ericsson Internal

2023-12-21 PF24
U16 rfPort;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_ANTENNA_POWER2_REJ
*
* Data :
* errorCode Code for the specific error. Refer to rbs_sd_cci.h in
BlibSdCciSysLU
* RBS_ERROR_CODE_UNSUPPORTED_CAPABILITY must be used if
the capability
* EXT_AUX_CONTROL_SUPPORT and RF_PORT_SUPPORT are not
supported.
*
*************************************************************************
*****/
#define RRU_ANTENNA_POWER2_REJ (TRP_RRU_SIGBASE + 0x49) /* !-

SIGNO(struct RruAntennaPower2RejS) -! */
struct RruAntennaPower2RejS
{
SIGSELECT sigNo;
U16 rfPort;
U16 errorCode;
};
…
#define RRU_CONFIG_SV_REJ (TRP_RRU_SIGBASE + 0x32) /*!-SIGNO(struct

RruConfigSvRejS)-!*/
struct RruConfigSvRejS
{
SIGSELECT sigNo;
U16 errorCode;
};
/
*************************************************************************
****************
* Revised procedure: RRU_CONFIG_SV(3_REQ,2_CFM,2_REJ)
*************************************************************************
****************/
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_SV3_REQ
*
* Allowed for capability: TMA_LNA_SV_SUPPORT & RF_PORT_SUPPORT
*
Ericsson Internal

2023-12-21 PF24
* Description: Request to configure TMA LNA supervision thresholds.

*
* Data :
* rfPort; RF port identifier
* tmaCurrentLowLim (0-200 Current in mA or 'Not Used')
* tmaCurrentHighLim (0-600 Current in mA or 'Not Used')
* tmaDegradedSvCtrl (0=reporting of LNA degraded fault
* indications off.
* 1=reporting of LNA degraded fault
* indications power=on
(default)).
*
*************************************************************************
*****
*/
#define RRU_CONFIG_SV3_REQ (TRP_RRU_SIGBASE + 0x4A) /*!-SIGNO(struct
RruConfigSv3ReqS)-!*/
struct RruConfigSv3ReqS
{
SIGSELECT sigNo;
U16 rfPort;
U16 tmaCurrentLowLim;
U16 tmaCurrentLowLim;
U16 tmaDegradedSvCtrl;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_SV2_CFM
*
* Description: The message is sent as an confirmation that the TMA
LNA failure
* configuration parameters have been changed
successfully.
*
* Data :
*
*************************************************************************
*****
*/
#define RRU_CONFIG_SV2_CFM (TRP_RRU_SIGBASE + 0x4B) /*!-SIGNO(struct
RruConfigSv2CfmS)-!*/
struct RruConfigSv2CfmS
{
SIGSELECT sigNo;
U16 rfPort;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_SV2_REJ
*
* Description: The message is sent as an reject of the request.
*
* Data :
Ericsson Internal

2023-12-21 PF24
* rfPort; RF port identifier
* errorCode Code for the specific error

*
*************************************************************************
*****
*/
#define RRU_CONFIG_SV2_REJ (TRP_RRU_SIGBASE + 0x4C) /*!-SIGNO(struct
RruConfigSv2RejS)-!*/
struct RruConfigSv2RejS
{
SIGSELECT sigNo;
U16 rfPort;
U16 errorCode;
};
…
#define RRU_CONFIG_POWER_SV_REJ (TRP_RRU_SIGBASE + 0x36) /*!-SIGNO(struct

RruConfigPowerSvRejS)-!*/
struct RruConfigPowerSvRejS
{
SIGSELECT sigNo;
U16 errorCode;
};
/
*************************************************************************
****************
* Revised procedure: RRU_CONFIG_POWER_SV(3_REQ,2_CFM,2_REJ)
*************************************************************************
****************/
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_POWER_SV3_REQ
* Allowed for capability: RRU_CAP_CONFIG_ANT_LOW_CURRENT_SV_SUPPORT &
RF_PORT_SUPPORT
* Description: Request to turn on or off the low current
supervision.
* Reporting of RRU_CABLE_SV_FAULT_IND is
enabled/disabled.
*
* Data :
* lowCurrentSupervision {ON, OFF}
*
*************************************************************************
*****
*/
#define RRU_CONFIG_POWER_SV3_REQ (TRP_RRU_SIGBASE + 0x4D) /*!-
SIGNO(struct RruConfigPowerSv3ReqS)-!*/
Ericsson Internal

2023-12-21 PF24
struct RruConfigPowerSv3ReqS
{
SIGSELECT sigNo;
U16 rfPort;
U16 lowCurrentSupervision;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_POWER_SV2_CFM
*
* Description: The message is sent as an confirmation that the
power supervision
* configuration parameters have been changed
successfully.
*
* Data :
*
*************************************************************************
*****
*/
#define RRU_CONFIG_POWER_SV2_CFM (TRP_RRU_SIGBASE + 0x4E) /*!-
SIGNO(struct RruConfigPowerSv2CfmS)-!*/
struct RruConfigPowerSv2CfmS
{
SIGSELECT sigNo;
U16 rfPort;
};
/
*************************************************************************
*****
*
* Signal Name: RRU_CONFIG_POWER_SV2_REJ
*
* Description: The message is sent as an reject of the request.
*
* Data :
* errorCode Code for the specific error
*
*************************************************************************
*****
*/
#define RRU_CONFIG_POWER_SV2_REJ (TRP_RRU_SIGBASE + 0x4F) /*!-
SIGNO(struct RruConfigPowerSv2RejS)-!*/
struct RruConfigPowerSv2RejS
{
SIGSELECT sigNo;
U16 rfPort;
U16 errorCode;
};
…
cbci_rru_unioncontent.h:
Ericsson Internal

2023-12-21 PF24
…
struct RruRdPortSvFaultIndS rruRdPortSvFaultInd;
struct RruRdPortSvFaultceaseIndS rruRdPortSvFaultceaseInd;
struct RruAntennaPower3ReqS rruAntennaPower3Req;

struct RruAntennaPower2CfmS rruAntennaPower2Cfm;
struct RruAntennaPower2RejS rruAntennaPower2Rej;
struct RruConfigSv3ReqS rruConfigSv3Req;

struct RruConfigSv2CfmS rruConfigSv2Cfm;
struct RruConfigSv2RejS rruConfigSv2Rej;
struct RruConfigPowerSv3ReqS rruConfigPowerSv3Req;

struct RruConfigPowerSv2CfmS rruConfigPowerSv2Cfm;
struct RruConfigPowerSv2RejS rruConfigPowerSv2Rej;
5.7.3.5[7.7.3.5] Expand RF port E to support AISG 2.0 protocol
It’s possible to connect antenna units on RF port E as well.
In baseline, RBS supports ATMA connections on PF ports A-D, in

which only A-C port can support AISG 2.0 (not support AISG 3.0).
5.7.3.5.1[7.7.3.5.1] BCP impact
DU-BCP
BXP processes need to be expanded to support AISG device on port

E besides A-C.
BXP processes in baseline (for antenna ports A, B and C)
Po c c c c c c c c c c c c
a a a a a a a a a a a a
no s s s s s s s s s s s s
c c c c c c c c c c c c
. . . . . . . . . . . .
N N N N N N N
N O o O N O o N o N N O
o = = = o = = O = O o =
= 0 1 1 = 2 3 = 4 = = 5
0 , , , 2 , , 3 , 4 5 ,
, A A A , A A , A , , A
n U n n U U n
A t 1 t A t 1 A 1 A A t
U ( U n n U
1 u R u 1 u ( t ( t 1 u
n R n n R R n
( i U i ( i R u R u ( i
R t ) t R t U n U n R t
R s s R s ) i ) i R s
U U t t U
) ) s s )
B B B B B B B B B B B B
Ericsson Internal

2023-12-21 PF24
X X X X X X X X X X X X
P P P P P P P P P P P P
_ _ _ _ _ _ _ _ _ _ _ _
0 6 1 1 2 3 3 4 4 5 6 6
2 8 4 0 6 2 8 4 0 6
_ _ _ _ _ _ _ _ _ _ _ _
1 7 1 1 2 3 3 4 4 5 6 6
3 9 5 1 7 3 9 5 1 7
_ _ _ _ _ _ _ _ _ _ _ _
2 8 1 2 2 3 3 4 5 5 6 6
4 0 6 2 8 4 0 6 2 8
_ _ _ _ _ _ _ _ _ _ _ _
3 9 1 2 2 3 3 4 5 5 6 6
5 1 7 3 9 5 1 7 3 9
_ _ _ _ _ _ _ _ _ _ _ _
4 1 1 2 2 3 4 4 5 5 6 7
0 6 2 8 4 0 6 2 8 4 0
_ _ _ _ _ _ _ _ _ _ _ _
5 1 1 2 2 3 4 4 5 5 6 7
1 7 3 9 5 1 7 3 9 5 1
Po C C C C C C C C C C C C
a a a a a a a a a a a a
no s s s s s s s s s s s s
c c c c c c c c c c c c
N
N N o N N N N N N N N N
o o = o o o o o o o o o
= = 1 = = = = = = = = =
0 0 , 1 2 2 3 3 4 4 5 5
, , A , , , , , , , , ,
A n A A A A A
A n t n A n n A n A A n
n t . t n t t n t n n t
t . U . t . . t . t t .
. U n U . U U . U . . U
n i n n n n n
U i t i U i i U i U U i
n t C t n t t n t n n t
i i i i i
Ericsson Internal

2023-12-21 PF24
t B B t B C t C t t B
C C B B C
B B B B B B B B B B
B B
X X X X X X X X X X
X X
P P P P P P P P P P
P P
_ _ _ _ _ _ _ _ _ _
_ _
1 1 3 3 4 4 5 5 6 6
6 6
8 8 0 0 2 2 4 4 6 6
_ _
_ _ _ _ _ _ _ _ _ _
C B
C B C B C B C B C B
B B B B B B B B B B
B B
X X X X X X X X X X
X X
P P P P P P P P P P
P P
_ _ _ _ _ _ _ _ _ _
_ _
1 1 3 3 4 4 5 5 6 6
7 7
9 9 1 1 3 3 5 5 7 7
_ _
_ _ _ _ _ _ _ _ _ _
C B
C B C B C B C B C B
B B B B B B B B B B
B B
X X X X X X X X X X
X X
P P P P P P P P P P
P P
_ _ _ _ _ _ _ _ _ _
_ _
2 2 3 3 4 4 5 5 6 6
8 8
0 0 2 2 4 4 6 6 8 8
_ _
_ _ _ _ _ _ _ _ _ _
C B
C B C B C B C B C B
B B B B B B B B B B
B B
X X X X X X X X X X
X X
P P P P P P P P P P
P P
_ _ _ _ _ _ _ _ _ _
_ _
2 2 3 3 4 4 5 5 6 6
9 9
1 1 3 3 5 5 7 7 9 9
_ _
_ _ _ _ _ _ _ _ _ _
C B
C B C B C B C B C B
_ _ _ _ _ _ _ _ _ _ _ _
1 1 2 2 3 3 4 4 5 5 7 7
0 0 2 2 4 4 6 6 8 8 0 0
_ _ _ _ _ _ _ _ _ _ _ _
C B C B C B C B C B C B
B
B B B B B B B B B B B
X
X X X X X X X X X X X
P
P P P P P P P P P P P
_
_ _ _ _ _ _ _ _ _ _ _
2
1 1 2 3 3 4 4 5 5 7 7
3
1 1 3 5 5 7 7 9 9 1 1
_
_ _ _ _ _ _ _ _ _ _ _
_
C B B C B C B C B C B
C
Ericsson Internal

2023-12-21 PF24
New BXP processes (for antenna port E)
Po C C C C C C
a a a a a a
no s s s s s s
c c c c c c
N N N N N N
o o o o o o
= = = = = =
0 1 2 3 4 5
, , , , , ,
A A A A A A
n n n n n n
t t t t t t
. . . . . .
U U U U U U
n n n n n n
i i i i i i
t t t t t t
E E E E E E
B B B B B
B
X X X X X
X
P P P P P
P
_ _ _ _ _
_
1 3 4 5 6
6
8 0 2 4 6
_
_ _ _ _ _
E
E E E E E
B B B B B
B
X X X X X
X
P P P P P
P
_ _ _ _ _
_
1 3 4 5 6
7
9 1 3 5 7
_
_ _ _ _ _
E
E E E E E
B B B B B
B
X X X X X
X
P P P P P
P
_ _ _ _ _
_
2 3 4 5 6
8
0 2 4 6 8
_
_ _ _ _ _
E
E E E E E
B B B B B B
X X X X X X
P P P P P P
_ _ _ _ _ _
9 2 3 4 5 6
_ 1 3 5 7 9
E _ _ _ _ _
Ericsson Internal

2023-12-21 PF24
E E E E E
B B B B B B
X X X X X X
P P P P P P
_ _ _ _ _ _
1 2 3 4 5 7
0 2 4 6 8 0
_ _ _ _ _ _
E E E E E E
B B B B B B
X X X X X X
P P P P P P
_ _ _ _ _ _
1 2 3 4 5 7
1 3 5 7 9 1
_ _ _ _ _ _
E E E E E E
BXP_6_E will represent devices on antenna port E.
As showed in below figure for Antenna unit on port E, BCP need to

create XXP_4 (XP ATF server) located on the cascaded AU1 for
BXP_n_E processes (where n=0...5). BCP will hunt the XXP_4
process on radio to establish the ATFI connection for devices on
antenna port E.
Example of address antenna unit on port E.
Ericsson Internal

2023-12-21 PF24
BP
BXP_0 BXP_6_E port_6_dev_2 EPP_6_3 EPP_AISG_6_4
create
port_0_dev_1/XXP_4 port_0_dev_1/port_0_dev_2 port_0_dev_1/EPP_4_3 port_0_dev_1/EPP_AISG_4_4
Linkhandler create
(LINX
)
Port 0
CPRIi
2
RRU (AU1)
cascade no=1
logical address=1
XXP_4 port_0_dev_2 EPP_4_3 EPP_AISG_4_4
Linkhandler connect
(LINX
) XHP_4 create
create
Linkhandler create
(GLH)
UA T
R
Port 4
CPRIi RS485 Antenna unit s
2
RRU (AU1) ASC (AU1) RET (AU2) ATMAU or ARET
cascade no=2 logical address=2 logical address=3 (AISG compliant AU2)
logical address=4
CPRIi
2
XCS
No impact on XCS SW.
5.7.3.5.2[7.7.3.5.2] MPSW impact
1. EC
Ericsson Internal

2023-12-21 PF24
MP needs to support to address, setup, configure and handling AISG

compliant AU (ATMA or ARET) that possible connected to RF port E
in cascaded radio unit, which will be fulfilled mainly from following
aspects for those AUs.
 Setup ATFI connection to BXP processes in BCP.
 Add connection Map.
 Configure EP-Adaptor.
 Setup CBCI and CDCI connection.
 Support AU in setup, configuration, operation as well as fault

handling.
For details, refer to AU2 Primary ATF Connection (including its

subsequences and its related reference) within ISVR AU Connection
in MBSE ICBR Equipment Startup and Initiation 534/155 16-HRB 105
102/1.
5.7.3.6[7.7.3.6] Device Scan on RF port E
For Device Scan functionality, in baseline, it can only scans the AISG
units connected to RF port A/C and RET port. But for RF port B, even
it supports AISG, the AISG units connected to it cannot be scanned. (It
probably missed when introducing AISG on B port.)
As the RF port E shall supports AISG 2.0, the Device Scan function
should also be supported on this port.
5.7.3.6.1[7.7.3.6.1] MPSW impact
1. EC
EC shall possible to perform Device Scan on port E.
2. BOAM
BOAM shall save the units info from port E.
5.7.3.7[7.7.3.7] 3 sectors sharing on one radio unit
In baseline (after feature MR31846 for RRUS32) system can be able

to support Multi-Sector Per Radio (FAJ 121 4160). However up to 2
sectors is limited. So we need to enhance the feature to support 3
sectors.
Ericsson Internal

2023-12-21 PF24
5.7.3.7.1[7.7.3.7.1] MPSW impact
1. RBS Element Manager (BEM)
3 sectors configuration shall be supported by both GUI and XML

file via “SITE Equipment Configuration” Wizard on RBS Element
Manager (BEM).
The 3 sectors configuration shall also be

modified/exported/deleted by using “Modify RBS Equipment
Configuration” or “Export and Delete” Wizard on BEM.
General Rule for 3 Sectors configuration:
1. Rule for SITE configuration
When configuring 3 sectors in SITE Wizard, the column “Radio

Shared By”, in BEM Site Equipment Configuration page – Sector
options, of the first two sectors should be chosen by each other
(keep legacy behavior), and the third sector can choose either of
first two, to indicate the sectors sharing same radio unit(s). See
example in Figure 5 Example for "Radio Shared By" configuration
of 3 sectors.
Figure 5 Example for "Radio Shared By" configuration of 3 sectors
2. Rule for MODIFY configuration file (.xml)
a. Triple Sector -> Dual or Single Sector
Delete sector directly in XML file.
BEM shall handle “radioSharedBySector”

internally/automatically for remaining sector(s).
b. Dual Sector -> Triple Sector
The “radioSharedBySector” for added/modified sector can

be set to either of existing two sectors.
Ericsson Internal

2023-12-21 PF24
c. Single Sector -> Triple Sector
The “radioSharedBySector” for first added/modified sector

should be set to existing sector, the second added/modified
sector can be set to either of another two sectors.
Related limitations of dual sectors in BEM consistency check shall

be improved.
2. EC
a) The third Sector and corresponding Sector Antenna info should

be stored in internal structures.
b) Eclm update
The third shared sector info should be added in Eclm structure

EclmRfapAllocDevCfmS::EclmEraRfapAllocCfmParamsS
eclm_types.h
#define MAX_SHARED_SECTOR_NUM 2
typedef struct
{
S32 sharedSecoterFroId;
S32 sharedSectorNo;
} EclmRfapSharedSectorDataS;
typedef struct
{
S32 clientId;
S32 serverId;
S32 sectorRdnIndex;
EclmDpclDeviceInfoS dpclData[ECLM_MAX_NO_DPCL_PER_SECTOR];
EclmRfapRetDeviceDataS retData[MAX_NO_SA_PER_SECTOR];
EclmRfapAiDeviceDataS aiData[MAX_NO_AI_PER_SECTOR];
EclmRfapTmaDeviceDataS tmaData[MAX_NO_TMA_PER_SECTOR];
EclmRfapDeviceDataS tpaData[DEVICE_DATA_ARRAY_SIZE];
S32 radioFroId[DEVICE_DATA_ARRAY_SIZE];
S32 numberOfTx;
S32 numberOfRadio;
S32 sharedSectorFroId;
S32 isTheSecondSector;
EclmRfapSharedSecoterDataS
sharedSector[MAX_SHARED_SECTOR_NUM];
S32 numberOfSharedSector; // 0: not shared sector 1: 2 shared sector
per radio; 2: 3 shared sector per radio
Ericsson Internal

2023-12-21 PF24
S32 sectorSequenceInRadio; // current sector sequence in radio, valid

value 1-3
EclmConfigurationGroupTypeT obifConfigurationGroup;
EclmDuiCapabilityTypeT duiCapability;
EclmSectorAntennaDataS
sectorAntennaData[MAX_NO_SA_PER_SECTOR];
S32 noiseFigure;
} EclmEraRfapAllocCfmParamsS;
3. SCC
In baseline, SCC can only handle 2 sectors sharing case (“Dual

Sector” is used in SCC), so this should be updated to support 3
sectors.
The shared Sector info in updated Eclm structure

EclmEraRfapAllocCfmParamsS should be stored and handled
correctly.
5.7.3.7.2[7.7.3.7.2] License Control
As this function will be regarded as an enhancement of the existing

feature Multi-Sector Per Radio, the license control mechanism will be
aligned to the existing one.
If more than one sector are configured in the way of this feature using
resources in one radio unit, the sector status should be affected by the
license and feature status, a.k.a.
NodeBFunction::licenseStateMultiSectorPerRadio and
NodeBFunction::featureStateMultiSectorPerRadio.
5.7.3.7.3[7.7.3.7.3] Cabinet Viewer (CabV)
No impact on Cabinet Viewer, it can display 3 sectors as expected.

But verification is needed.
5.7.3.8[7.7.3.8] New RBBs to support 3 sectors
3 sectors configuration can be implemented in following RBB

combinations:
RBB22_1F (legacy), RBB22_1G (legacy), RBB22_1H (new)
RBB44_1N (new), RBB44_1P (new), RBB44_1S (new)

Ericsson Internal

2023-12-21 PF24
RBB44_2S (new), RBB44_2T (new), RBB44_2W (new)
RBBs using single radio unit:
RBB22_1H
RI Link RF Branch
Node 1 Data 1
1: TX A / RX A
E
Radio 1 2: TX B / RX B
F
Node 2 or Data 2
Cascade
Ge13146
RBBs using two radio units:
RBB44_1N
RI Link RF Branch
1: TX A / RX A
Node 1 Data 1 A
Data 2 B
3: TX C / RX C
Data 1 A
Radio 2 4: TX D / RX D
Node 2 or
Data 2 B
cascade
RBB44_1N
RBB44_1P
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
1: TX A / RX A
Node 1 Data 1 C
Data 2 D
3: TX C / RX C
Data 1 C
Node 2 or
Data 2 D
cascade
RBB44_1P
RBB44_1S
RBB44_2S
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
1: TX A / RX A
Data 1 A
Node 1
Data 2 B
3: TX C / RX C
Data 1 A
Node 2 or Radio 2 4: TX D / RX D
cascade Data 2 B
RBB44_2S
RBB44_2T
RI Link RF Branch
1: TX A / RX A
Data 1 C
Node 1
Data 2 D
3: TX C / RX C
Data 1 C
cascade Data 2 D
RBB44_2T
RBB44_2W
Ericsson Internal

2023-12-21 PF24
5.7.3.8.1[7.7.3.8.1] Device Model extension
In order to handle device addressing for 6 RF ports, the ‘Device

Model’ must be extended with mapping information for additional
DPCL, TR, TPA and AI devices.
In case the supported RF ports will be increased again, we propose to

extend the Device Model cover up to 8 RF ports. It can be visualized
through the following table (maintained in Radio Functional
specification). In short new AI and TPA devices 5-8 to represent RF
ports E to H, and DPCL and TR devices 25-48 added for interleaved
allocation to first E and F, then G and H, to support both 6 and 8 port
HW. Mappings for up to 4 branches are the same as in legacy:
TPA AI local
local ID ID RF port
(2- (2- (2-
TR branch/ branch/ branch/
DPCL local 4- 4- 4-
local ID ID branch/ branch/ branch/
(=portId (=portId 6,8- 6,8- 6,8-
Dl) Ul) branch) branch) branch)
1 1 1/1/1 1/1/1 A/A/A
5 2 2/2/2 2/2/2 B/B/B
2 3 1/1/1 1/1/1 A/A/A
6 4 2/2/2 2/2/2 B/B/B
3 5 1/1/1 1/1/1 A/A/A
7 6 2/2/2 2/2/2 B/B/B
4 7 1/1/1 1/1/1 A/A/A
Ericsson Internal

2023-12-21 PF24
8 8 2/2/2 2/2/2 B/B/B

9 9 1/1/1 1/1/1 A/A/A
10 10 2/2/2 2/2/2 B/B/B
11 11 1/1/1 1/1/1 A/A/A
12 12 2/2/2 2/2/2 B/B/B
13 13 1/3/3 1/3/3 A/C/C
14 14 2/4/4 2/4/4 B/D/D
15 15 1/3/3 1/3/3 A/C/C
16 16 2/4/4 2/4/4 B/D/D
17 17 1/3/3 1/3/3 A/C/C
18 18 2/4/4 2/4/4 B/D/D
19 19 1/3/3 1/3/3 A/C/C
20 20 2/4/4 2/4/4 B/D/D
21 21 1/3/3 1/3/3 A/C/C
22 22 2/4/4 2/4/4 B/D/D
23 23 1/3/3 1/3/3 A/C/C
24 24 2/4/4 2/4/4 B/D/D
25 25 -/-/5 -/-/5 -/-/E
26 26 -/-/6 -/-/6 -/-/F
27 27 -/-/5 -/-/5 -/-/E
28 28 -/-/6 -/-/6 -/-/F
29 29 -/-/5 -/-/5 -/-/E
30 30 -/-/6 -/-/6 -/-/F
31 31 -/-/5 -/-/5 -/-/E
32 32 -/-/6 -/-/6 -/-/F
33 33 -/-/5 -/-/5 -/-/E
34 34 -/-/6 -/-/6 -/-/F
35 35 -/-/5 -/-/5 -/-/E
36 36 -/-/6 -/-/6 -/-/F
37 37 -/-/7 -/-/7 -/-/G
38 38 -/-/8 -/-/8 -/-/H
39 39 -/-/7 -/-/7 -/-/G
40 40 -/-/8 -/-/8 -/-/H
41 41 -/-/7 -/-/7 -/-/G
42 42 -/-/8 -/-/8 -/-/H
43 43 -/-/7 -/-/7 -/-/G
44 44 -/-/8 -/-/8 -/-/H
45 45 -/-/7 -/-/7 -/-/G
46 46 -/-/8 -/-/8 -/-/H
47 47 -/-/7 -/-/7 -/-/G
48 48 -/-/8 -/-/8 -/-/H
Ericsson Internal

2023-12-21 PF24
5.7.3.8.2[7.7.3.8.2] Maximum supported Sector number
It will keep legacy limitation for supported Sector number in this MR,
which is:
 Maximum 12 sectors for 2T2R RBBs
 Maximum 6 sectors for 4T4R RBBs
5.7.3.8.3[7.7.3.8.3] Maximum supported Carrier number
Maximum 6 DL and 6 UL carrier branches per RF port on Radio 6626.
DUW only supports 2.5 Gbps CPRI rate, and the maximum number of
Carrier branches on per 2.5 Gbps CPRI link is 16 UL and 16 DL.
With optional feature FAJ 121 3928 Increased Cell Carrier Support
(ICC) enabled, it can support maximum 24 cell carrier branches on
Single DUW (DUW 30/31/41) configuration, or 36 cell carrier branches
on Dual DUW (with DUW 30/31/41 as primary DUW) configuration.
Therefore, the supported carrier number should be:
 Without RBB combination

Max number of Carriers per
Sector
RBB Carrier with Carrier with
2 RX 4 RX
Branches Branches
RBB22_1H -
RBB44_1N
RBB44_1P 4
RBB44_1S 4, 6(FCA)
RBB44_2S
RBB44_2T 4, 6(FCA)
RBB44_2W
 With RBBs combination

Max number of Carriers in 3
RBB Sectors
Combinatio Carrier Carrier
n with 2 RX with 4 RX
Branches Branches
RBB22_1F
RBB22_1G 8 -
RBB22_1H
RBB44_1N
RBB44_1P 8 4
RBB44_1S
RBB44_2S 12 (single 6 (single
Ericsson Internal

2023-12-21 PF24
DUW) DUW)
RBB44_2T
16 (dual 8 (dual
RBB44_2W
DUW) DUW)
5.7.3.8.4[7.7.3.8.4] MOM impact
The possible values of new RBBs shall be added in MO attribute

Sector::radioBuildingBlock.
5.7.3.8.5[7.7.3.8.5] MPSW impact
1. BEM
Support configuration of new RBBs via both GUI and XML file.
2. BOAM
Support new RBBs for sector configuration, MOM adaption and

ECMI adaption for new RBBs.
3. EC
a. ECMI
Add new RBB types in ECMI.
b. Add device allocation table for each RBB, make sure all HW
resources can be allocated for all RBBs.
c. CableThroughWalkDui adaption for new RBBs.
Carrier resources allocation
RBB22_1H:
DL device allocation RBB22_1H
D
T
D R P T A
P
L U C R I
A
L
f
2 2
1 1 5 5
5 5
a
f
2 2
1 1 6 6
6 6
b
f
2 2
2 1 5 5
7 7
a
f 1 2 2 6 6
2 8 8
Ericsson Internal

2023-12-21 PF24
b
f
2 2
3 1 5 5
9 9
a
f
3 3
3 1 6 6
0 0
b
f
3 3
4 1 5 5
1 1
a
f
3 3
4 1 6 6
2 2
b
UL device allocation RBB22_1H

R R
U U
f f
T A
o o
R I
r r
T A
R I
f
2
1 1 1 5
5
a
f
2
1 1 1 6
6
b
f
2
2 1 1 5
7
a
f
2
2 1 1 6
8
b
f
2
3 1 1 5
9
a
f
3
3 1 1 6
0
b
f
3
4 1 1 5
1
a
f 1 3 1 6
4 2
Ericsson Internal

2023-12-21 PF24
DL device allocation RBB22_1H

(FCA)
D
T
D R P T A
P
L U C R I
A
L
d
l 2 2
1 5 5
1 5 5
a
d
l 2 2
1 6 6
1 6 6
b
d
l 2 2
1 5 5
2 7 7
a
d
l 2 2
1 6 6
2 8 8
b
d
l 2 2
1 5 5
3 9 9
a
d
l 3 3
1 6 6
3 0 0
b
d
l 3 3
1 5 5
4 1 1
a
d
l 3 3
1 6 6
4 2 2
b
d
l 3 3
1 5 5
5 3 3
a
d 1 3 3 6 6
l 4 4
5
Ericsson Internal

2023-12-21 PF24
b
d
l 3 3
1 5 5
6 5 5
a
d
l 3 3
1 6 6
6 6 6
b
UL device allocation RBB22_1H

(FCA)
R R
U U
f f
T A
o o
R I
r r
T A
R I
u
l 2
1 1 5
1 5
a
u
l 2
1 1 6
1 6
b
u
l 2
1 1 5
2 7
a
u
l 2
1 1 6
2 8
b
u
l 2
1 1 5
3 9
a
u
l 3
1 1 6
3 0
b
u 1 3 1 5
l 1
4
Ericsson Internal

2023-12-21 PF24
a
u
l 3
1 1 6
4 2
b
u
l 3
1 1 5
5 3
a
u
l 3
1 1 6
5 4
b
u
l 3
1 1 5
6 5
a
u
l 3
1 1 6
6 6
b
RBB44_1N/RBB44_2S:
DL device allocation
RBB44_1N/2S
D
T
D R P T A
P
L U C R I
A
L
f
1 1 1 1 1 1
a
f
1 1 5 2 2 2
b
f
2 2 1 1 1 1
c
f
2 2 5 2 2 2
d
f
3 1 3 5 1 1
a
f
3 1 7 6 2 2
b
f 2 3 5 1 1
Ericsson Internal

2023-12-21 PF24
4
c
f
4 2 7 6 2 2
d
UL device allocation
RBB44_1N/2S
R R
U U
f f
T A
o o
R I
r r
T A
R I
f
1 1 1 1 1
a
f
1 1 2 1 2
b
f
1 2 3 2 1
c
f
1 2 4 2 2
d
f
2 1 3 1 1
a
f
2 1 4 1 2
b
f
2 2 1 2 1
c
f
2 2 2 2 2
d
f
3 1 5 1 1
a
f
3 1 6 1 2
b
f 2 7 2 1
Ericsson Internal

2023-12-21 PF24
3
c
f
3 2 8 2 2
d
f
4 1 7 1 1
a
f
4 1 8 1 2
b
f
4 2 5 2 1
c
f
4 2 6 2 2
d
DL device allocation
RBB44_1N/2S (FCA)
D
T
D R P T A
P
L U C R I
A
L
d
l
1 1 1 1 1
1
a
d
l
1 5 2 2 2
1
b
d
l
1 2 3 1 1
2
a
d
l
1 6 4 2 2
2
b
d
l
1 3 5 1 1
3
a
d 1 7 6 2 2
l
3
Ericsson Internal

2023-12-21 PF24
b
d
l
1 4 7 1 1
4
a
d
l
1 8 8 2 2
4
b
d
l
1 9 9 1 1
5
a
d
l 1 1
1 2 2
5 0 0
b
d
l 1 1
1 1 1
6 1 1
a
d
l 1 1
1 2 2
6 2 2
b
d
l
2 1 1 1 1
1
c
d
l
2 5 2 2 2
1
d
d
l
2 2 3 1 1
2
c
d
l
2 6 4 2 2
2
d
d
l
2 3 5 1 1
3
c
d 2 7 6 2 2
l
3
Ericsson Internal

2023-12-21 PF24
d
d
l
2 4 7 1 1
4
c
d
l
2 8 8 2 2
4
d
d
l
2 9 9 1 1
5
c
d
l 1 1
2 2 2
5 0 0
d
d
l 1 1
2 1 1
6 1 1
c
d
l 1 1
2 2 2
6 2 2
d
UL device allocation
RBB44_1N/2S (FCA)
R R
U U
f f
T A
o o
R I
r r
T A
R I
u
l
1 1 1 1
1
a
u
l
1 2 1 2
1
b
u 1 3 1 1
l
2
Ericsson Internal

2023-12-21 PF24
a
u
l
1 4 1 2
2
b
u
l
1 5 1 1
3
a
u
l
1 6 1 2
3
b
u
l
1 7 1 1
4
a
u
l
1 8 1 2
4
b
u
l
1 9 1 1
5
a
u
l 1
1 1 2
5 0
b
u
l 1
1 1 1
6 1
a
u
l 1
1 1 2
6 2
b
u
l
2 1 2 1
1
c
u
l
2 2 2 2
1
d
u 2 3 2 1
l
2
Ericsson Internal

2023-12-21 PF24
c
u
l
2 4 2 2
2
d
u
l
2 5 2 1
3
c
u
l
2 6 2 2
3
d
u
l
2 7 2 1
4
c
u
l
2 8 2 2
4
d
u
l
2 9 2 1
5
c
u
l 1
2 2 2
5 0
d
u
l 1
2 2 1
6 1
c
u
l 1
2 2 2
6 2
d
RBB44_1P/RBB44_2T:
DL device allocation RBB44_1P|
2T
D
T
D R P T A
P
L U C R I
A
L
f 1 1 1 3 3
Ericsson Internal

2023-12-21 PF24
1
3 3
a
f
1 1
1 1 4 4
4 4
b
f
1 1
2 2 3 3
3 3
c
f
1 1
2 2 4 4
4 4
d
f
1 1
3 1 3 3
7 7
a
f
1 1
3 1 4 4
8 8
b
f
1 1
4 2 3 3
7 7
c
f
1 1
4 2 4 4
8 8
d
UL device allocation RBB44_1P|

2T
R R
U U
f f
T A
o o
R I
r r
T A
R I
f
1
1 1 1 3
3
a
f
1
1 1 1 4
4
b
f
1
1 2 2 3
5
c
f
1
1 2 2 4
6
d
f 1 1 1 3
Ericsson Internal

2023-12-21 PF24
2
5
a
f
1
2 1 1 4
6
b
f
1
2 2 2 3
3
c
f
1
2 2 2 4
4
d
f
1
3 1 1 3
7
a
f
1
3 1 1 4
8
b
f
1
3 2 2 3
9
c
f
2
3 2 2 4
0
d
f
1
4 1 1 3
9
a
f
2
4 1 1 4
0
b
f
1
4 2 2 3
7
c
f
1
4 2 2 4
8
d
DL device allocation RBB44_1P|

2T (FCA)
D
T
D R P T A
P
L U C R I
A
L
d
l 1 1
1 3 3
1 3 3
a
d 1 1 1 4 4
Ericsson Internal

2023-12-21 PF24
l
1 4 4
b
d
l 1 1
1 3 3
2 5 5
a
d
l 1 1
1 4 4
2 6 6
b
d
l 1 1
1 3 3
3 7 7
a
d
l 1 1
1 4 4
3 8 8
b
d
l 1 1
1 3 3
4 9 9
a
d
l 2 2
1 4 4
4 0 0
b
d
l 2 2
1 3 3
5 1 1
a
d
l 2 2
1 4 4
5 2 2
b
d
l 2 2
1 3 3
6 3 3
a
d
l 2 2
1 4 4
6 4 4
b
d
l 1 1
2 3 3
1 3 3
c
d 2 1 1 4 4
Ericsson Internal

2023-12-21 PF24
l
1 4 4
d
d
l 1 1
2 3 3
2 5 5
c
d
l 1 1
2 4 4
2 6 6
d
d
l 1 1
2 3 3
3 7 7
c
d
l 1 1
2 4 4
3 8 8
d
d
l 1 1
2 3 3
4 9 9
c
d
l 2 2
2 4 4
4 0 0
d
d
l 2 2
2 3 3
5 1 1
c
d
l 2 2
2 4 4
5 2 2
d
d
l 2 2
2 3 3
6 3 3
c
d
l 2 2
2 4 4
6 4 4
d
UL device allocation RBB44_1P|

2T (FCA)
R T R A
Ericsson Internal

2023-12-21 PF24
U U
f f
o o
R I
r r
T A
R I
u
l 1
1 1 3
1 3
a
u
l 1
1 1 4
1 4
b
u
l 1
1 1 3
2 5
a
u
l 1
1 1 4
2 6
b
u
l 1
1 1 3
3 7
a
u
l 1
1 1 4
3 8
b
u
l 1
1 1 3
4 9
a
u
l 2
1 1 4
4 0
b
u
l 2
1 1 3
5 1
a
u
l 2
1 1 4
5 2
b
Ericsson Internal

2023-12-21 PF24
u
l 2
1 1 3
6 3
a
u
l 2
1 1 4
6 4
b
u
l 1
2 2 3
1 3
c
u
l 1
2 2 4
1 4
d
u
l 1
2 2 3
2 5
c
u
l 1
2 2 4
2 6
d
u
l 1
2 2 3
3 7
c
u
l 1
2 2 4
3 8
d
u
l 1
2 2 3
4 9
c
u
l 2
2 2 4
4 0
d
u
l 2
2 2 3
5 1
c
u
l 2
2 2 4
5 2
d
Ericsson Internal

2023-12-21 PF24
u
l 2
2 2 3
6 3
c
u
l 2
2 2 4
6 4
d
RBB44_1S/RBB44_2W:
DL device allocation RBB44_1S|
2W
D
T
D R P T A
P
L U C R I
A
L
f
2 2
1 1 5 5
5 5
a
f
2 2
1 1 6 6
6 6
b
f
2 2
2 2 5 5
5 5
c
f
2 2
2 2 6 6
6 6
d
f
2 2
3 1 5 5
9 9
a
f
3 3
3 1 6 6
0 0
b
f
2 2
4 2 5 5
9 9
c
f
3 3
4 2 6 6
0 0
d
UL device allocation RBB44_1S|

2W
R T R A
U R U I
Ericsson Internal

2023-12-21 PF24
f f
o o
r r
T A
R I
f
2
1 1 1 5
5
a
f
2
1 1 1 6
6
b
f
2
1 2 2 5
7
c
f
2
1 2 2 6
8
d
f
2
2 1 1 5
7
a
f
2
2 1 1 6
8
b
f
2
2 2 2 5
5
c
f
2
2 2 2 6
6
d
f
2
3 1 1 5
9
a
f
3
3 1 1 6
0
b
f
3
3 2 2 5
1
c
f
3
3 2 2 6
2
d
f
3
4 1 1 5
1
a
f
3
4 1 1 6
2
b
Ericsson Internal

2023-12-21 PF24
f
2
4 2 2 5
9
c
f
3
4 2 2 6
0
d
DL device allocation RBB44_1S|2W (FCA)

D
T
D R P T A
P
L U C R I
A
L
d
l 2 2
1 5 5
1 5 5
a
d
l 2 2
1 6 6
1 6 6
b
d
l 2 2
1 5 5
2 7 7
a
d
l 2 2
1 6 6
2 8 8
b
d
l 2 2
1 5 5
3 9 9
a
d
l 3 3
1 6 6
3 0 0
b
d
l 3 3
1 5 5
4 1 1
a
d
l 3 3
1 6 6
4 2 2
b
d 1 3 3 5 5
l 3 3
5
Ericsson Internal

2023-12-21 PF24
a
d
l 3 3
1 6 6
5 4 4
b
d
l 3 3
1 5 5
6 5 5
a
d
l 3 3
1 6 6
6 6 6
b
d
l 2 2
2 5 5
1 5 5
c
d
l 2 2
2 6 6
1 6 6
d
d
l 2 2
2 5 5
2 7 7
c
d
l 2 2
2 6 6
2 8 8
d
d
l 2 2
2 5 5
3 9 9
c
d
l 3 3
2 6 6
3 0 0
d
d
l 3 3
2 5 5
4 1 1
c
d
l 3 3
2 6 6
4 2 2
d
d 2 3 3 5 5
l 3 3
5
Ericsson Internal

2023-12-21 PF24
c
d
l 3 3
2 6 6
5 4 4
d
d
l 3 3
2 5 5
6 5 5
c
d
l 3 3
2 6 6
6 6 6
d
UL device allocation RBB44_1S|2W (FCA)

R R
U U
f f
T A
o o
R I
r r
T A
R I
u
l 2
1 1 5
1 5
a
u
l 2
1 1 6
1 6
b
u
l 2
1 1 5
2 7
a
u
l 2
1 1 6
2 8
b
u
l 2
1 1 5
3 9
a
u
l 3
1 1 6
3 0
b
Ericsson Internal

2023-12-21 PF24
u
l 3
1 1 5
4 1
a
u
l 3
1 1 6
4 2
b
u
l 3
1 1 5
5 3
a
u
l 3
1 1 6
5 4
b
u
l 3
1 1 5
6 5
a
u
l 3
1 1 6
6 6
b
u
l 2
2 2 5
1 5
c
u
l 2
2 2 6
1 6
d
u
l 2
2 2 5
2 7
c
u
l 2
2 2 6
2 8
d
u
l 2
2 2 5
3 9
c
u
l 3
2 2 6
3 0
d
Ericsson Internal

2023-12-21 PF24
u
l 3
2 2 5
4 1
c
u
l 3
2 2 6
4 2
d
u
l 3
2 2 5
5 3
c
u
l 3
2 2 6
5 4
d
u
l 3
2 2 5
6 5
c
u
l 3
2 2 6
6 6
d
5.7.3.9[7.7.3.9] Fault handling for RF ports E&F
5.7.3.9.1[7.7.3.9.1] Faults via CBCI fault indication
The Radio needs to be able to convey fault associations to new RF

ports/branches.
There are separate fault types for faults related to different RF

ports/branches, in Common Constants I/F file (rbs_sd_cci.h).
New fault types must be added to enable pinpointing of faults related

to RF ports/branches E-H (G&H are prepared for future 8 RF ports
radios in I/F file).
The fault messages and types concerned are:
RRU_AUX_POW_SV_FAULT(CEASE)_IND
RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_ANTENNA_BRANCH_{A|
B|C|D|E|F|G|H}
Ericsson Internal

2023-12-21 PF24
Enabler: RRU_ANTENNA_POWERx_REQ with corresponding auxPowerPort(x) IE

set to ‘ON’
RRU_TMA_LNA_SV_FAULT(CEASE)_IND:
RBS_FAULT_TYPE_LNA_{FAILURE|DEGRADED}_ANTENNA_BRANCH_{A|B|C|D|
E|F|G|H}
Enabler: RRU_CONFIG_SVx_REQ with corresponding tmaCurrent{Low|

High}LimPort(x) IE used.
RRU_CABLE_SV_FAULT(CEASE)_IND:
RBS_FAULT_TYPE_FEEDER_CABLE_DISCONNECTED_ANTENNA_BRANCH_{A|
B|C|D|E|F|G|H}
Enabler: RRU_CONFIG_POWER_SVx_REQ with corresponding

lowCurrentSupervision(x) IE set to ‘ON’.
EC shall be able to map the fault on Radio Branch E&F to the alarm
on MO AntennaBranch or SectorAntenna for each RBB.
5.7.3.9.2[7.7.3.9.2] Faults via CDCI fault indication
Besides CBCI fault-IND, as there are new AI devices on RF ports

E&F, below faults reported on new AI devices via CDCI fault-IND shall
also be mapped to corresponding AntennaBranch MO.
 AI_FAULT_TYPE_ANTENNA_FEEDER_CURRENT_TOO_LOW
 AI_FAULT_TYPE_ANTENNA_FEEDER_CURRENT_TOO_HIGH
 AI_FAULT_TYPE_DISCONNECTED_ANTENNA
 AI_FAULT_TYPE_VSWR_FAULT
5.7.3.10[7.7.3.10] Maximum 360W Output Power for all RF ports on B1
In feature MR6211 SP4, legacy Output Power HWAC of

OutputPowerxxxW (with license control
NodeBFunction::licenseStateNumxxxWPowerAmplifiers) was replaced
by OutputPower20WStep (with new license control
NodeBFunction::licenseCapacityOutputPower20WStep, CXC 401
2338), and the limitation of 240W per radio on DUW was removed.
However, it’s not verified as no Radio HW requires more than 240W
on WCDMA G1.
So verification on this part shall be taken in scope.

Ericsson Internal

2023-12-21 PF24
5.7.3.11[7.7.3.11] ULSA
From MOM and MPSW perspective, it can support ULSA functionality

on new RF port E&F, but verification is still needed to make sure it can
work.
5.7.3.12[7.7.3.12] Cabinet Viewer
Cabinet Viewer should be adapted for the extended AI/TPA/TR/DPCL

devices, to make sure the Radio and 3 Sectors are visible on Cabinet
Viewer.
5.7.3.13[7.7.3.13] System Documents Impact

Do
cu
me
Classif
Document Name nt Update content
ication
Nu
mb
er
503/
CBR Equipment 1) ISVR Configuration Radio
155
Configuration Equipment, add new RBBs.
16
1) ISVR Initiate Sector
Description, add device
517/ allocation rule (AI, TR, TPA,
CBR Site DPLC) for new RBBs.
155
Configuration
16 2) ISVR Initiate Sector
Description, add reference
MBSE model for new RBBs.
1) ISVR Antenna Feeder
Power On or Off, add ANT_E
534/ and ANT_F.
ICBR Equipment
155
Startup and Initiation 2) ISVR Startup Auxiliary Unit
16
of Class 2, update for
BXP_E_N.
18/1
1) Add sub-chapter in 18.2.5
UCR Add Capacity 555
for new RBBs.
6
RBS EM Import File 8/15
Support 519
EriDoc
Site Equipment 5/19
Configuration 605
5.7.3.14[7.7.3.14] WCDMA CPI impact

Title Doc. Node Update description Owner
number Type
Compatibilities 11/1551- DU Product number to be added. WCDM
for Hardware LZA 701 RN A SW
and Software 6003/1
WCDMA RBS 14/1553- Section 7.16 FAJ 121 4160: Multi- WCDM
Ericsson Internal

2023-12-21 PF24
Configuration LZA 701 Sector Per Radio A SW

Guidelines 6003/1
Multi-Sector 217/1553- Three sectors can be supported on WCDM
Per Radio HSD 101 the new radio, which will affect the A SW
02/1 description of this feature.
Basic Features 218/1553- Update the description of the Multi- WCDM
HSD 101 Sector Per Sector feature. A SW
02/1
Network 18/109 48- New topic for this enhancement WCDM
Impact report HSD 101 A SW
02/1
Building 24/1551- PDU HW
Blocks LZA 701
6001/1-
A46
Radio 24/1551- PDU HW
Configurations LZA 701
for WCDMA 6001/1-A5
Radio Network 186/006 The value of WCDM
Parameters 51-HSD AntFeederCable::objectAConnector A SW
101 02 updated.
New RBBs.
File 13/1553- New RBB added, and the value of WCDM
Descriptions LZA 701 the attribute radiobuildingblock will A SW
for Site 6003/1 be updated.
Configuration
Manage Radio 2/1553- The note in section 2.8.44.2 needs to WCDM
Network LZA 701 be updated. A SW
6003/1
Example Files 1/006 91- New example file WCDM
for Site LZA 701 A SW
Equipment 6003/1
Configuration
DTD for Site 5/006 91- New DTD file WCDM
Equipment LZA 701 A SW
Configuration 6003/1
Example Files 3/006 91- New example file WCDM
for Modify LZA 701 A SW
RBS 6003/1
Equipment
Configuration
DTD for 7/006 91- New DTD file WCDM
Modify RBS LZA 701 A SW
Equipment 6003/1
Configuration
Note: This part only covers WCDMA CPI impact.
5.7.3.15[7.7.3.15] Cost Estimation
This part only focuses on design efforts.

B
Sub- l
Cost Estimation
Syste o
(mhr)
m c
k
MOM - 80
MPSW B 800
Ericsson Internal

2023-12-21 PF24
E
M
B
O
200
A
M
E 1500 + 800 (new fault
C handling)
S
C 300
C
Cabinet
- 50
Viewer
BCP - 80
CPI - 80 (WCDMA part)
System
- 80
Doc
Total 3970
5.7.4[7.7.4] WCDMA G1 Specific for FDD Radio 4466
5.7.4.1[7.7.4.1] Multi-Band configuration
In WCDMA G1 system design base, maximum Dual-Band

configuration is supported with some limitations:
1. Multi-Band VSWR is not supported, only the worst case (worst

band) could be reported by radio.
2. Design effort of Dual-Band ATMA is done by MR3256-2, but not

verified because no proper ATMA HW for testing at that time.
According to chapter Error: Reference source not found, frequency

bands 1/2/4/5/8 are commonly used bands on WCDMA. So for FDD
Radio 4466 B1B3B7, B1B3B75A frequency combined products,
only single band is required on WCDMA G1.
If Triple-Band on WCDMA G1 is really wanted in future, MPSW for

Triple-Band solution should be studied and implemented then.
5.7.4.2[7.7.4.2] UCF update for new Radio products
The UCF should be updated for new Radio products.
As FDD Radio 4466 will have a new LMC product number, which is
different to Radio 6626, it is needed to add a new <PiuTypeLoadList>
in UCF.
Ericsson Internal

2023-12-21 PF24
The new LMC for Radio 4466 should also be included in Upgrade
Package.
Note:
As the Upgrade Packages are stored in Volume C on DUW board

(WCDMA G1 DU board), and some DUW types only have total 1147
MB available space on Volume C. After the new LMCs of Radio 6626
and 4466 be included in UP, it is not possible to install more than
two UPs on these DUW boards. This should be a limitation and
recorded in CPI and corresponding release documents.
5.7.4.3[7.7.4.3] RBBs for FDD Radio 4466
Legacy RBBs RBB44_1D, RBB22_1F and RBB22_1G shall be

supported on FDD Radio 4466.
5.7.4.4[7.7.4.4] Legacy features on FDD Radio 4466
See below table for the support of legacy features/functions (on

WCDMA G1) on Radio 4466. It is also can be found in document CRS
Radio Functions (17/1056-HRB105700).
Function/Feature Name Description Radio

4466
HSDPA Dynamic Power Sharing “Single RAT Power Pooling” on Radio Yes
(HSDPA DPS) side.
Enables dynamic borrowing of unused
configured power from other WCDMA
carrier(s) in the same frequency band
within a sector.
HSDPA Mixed Mode Dynamic “Multi RAT Power Pooling” on Radio Yes
Power Sharing (HSDPA side.
MMDPS) Enables WCDMA cells dynamic
borrowing of unused configured power
from GSM or LTE.
Uplink Spectrum Analyzer Provide RF uplink spectrum Yes
(ULSA) characteristics, to support analysis of
performance and interferences in
network operation.
Narrowband Interference A method for suppressing the effects of Yes
Rejection (NBIR) external narrowband radio interferers.
Filtering of static or slow-moving
narrowband interferers in the spectrum
dedicated to a WCDMA carrier.
VSWR measurement Supervision of the antenna system Yes
PSI Coverage The Psi-Coverage feature allows a No
Node-B with one radio to provide the (Only
same coverage as a standard three- support
sector Node-B having three radios. on
It provides a solution offering several Single
Ericsson Internal

2023-12-21 PF24
cost savings, including 45% energy Band

savings. Radio)
5.7.5[7.7.5] WCDMA G1 Specific for Radio 6626 Low Band (MR90002-4)
5.7.5.1[7.7.5.1] Overview
The radio variant is on B8&B20, based on MR9002-1, MR9002-2,

here is the change on the SP.
 New radio types with new radio load modules.
 Support configuration Wcdma carriers on Band8 only.
Maximum 480W Output Power for all RF ports per radio on B8.
5.7.5.2[7.7.5.2] New radio types with new radio load modules
UCF needs to be updated for new radio types. For Radon and Krypton
based radios, each of them shall have an individual
<PiuTypeLoadList> in UCF.
The LMs for Visby Platform should be added in Upgrade Package.
5.7.5.3[7.7.5.3] Configuration
Highly depend on MR9002-2’s decision. Refer the chapter for

MR9002-2.
5.7.5.4[7.7.5.4] Legacy features on FDD Radio 6626 B8B20
See below table for the support of legacy features/functions (on

WCDMA G1) on Radio 6626. It is also can be found in document CRS
Radio Functions (17/1056-HRB105700).
Function/Feature Name Description Radio
6626
HSDPA Dynamic Power Sharing “Single RAT Power Pooling” on Radio Yes
(HSDPA DPS) side.
Enables dynamic borrowing of unused
configured power from other WCDMA
carrier(s) in the same frequency band
within a sector.
HSDPA Mixed Mode Dynamic “Multi RAT Power Pooling” on Radio Yes
Power Sharing (HSDPA side.
MMDPS) Enables WCDMA cells dynamic
borrowing of unused configured power
from GSM or LTE.
Uplink Spectrum Analyzer Provide RF uplink spectrum Yes
(ULSA) characteristics, to support analysis of
performance and interferences in
Ericsson Internal

2023-12-21 PF24
network operation.
Narrowband Interference A method for suppressing the effects of Yes
Rejection (NBIR) external narrowband radio interferers.
Filtering of static or slow-moving
narrowband interferers in the spectrum
dedicated to a WCDMA carrier.
VSWR measurement Supervision of the antenna system Yes
PSI Coverage The Psi-Coverage feature allows a No
Node-B with one radio to provide the (Only
same coverage as a standard three- support
sector Node-B having three radios. on
It provides a solution offering several Single
cost savings, including 45% energy Band
savings. Radio)
5.7.6[7.7.6] WCDMA G1 Specific for SP15
5.7.6.1[7.7.6.1] Limit Maximum 5 DL/UL Carriers per RF Port on B1
This SP requires 7 carriers per RF port on B3 UL for Visby Radio 6626 B1B3
and Radio 4466 B1B3B40/B41, thus up to 5 carriers on per RF port of B1 UL
can be supported on these Radios.
No new RBB will be introduced for this SP, same RBBs (see corresponding
sections in 8.7.3 and 8.7.4) shall be used on these specific Radios and other
FV Radio products (like 6626 B8B20).
From MPSW point of view, it’s hard to limit different allowed carrier numbers
in the same RBB on different Radio types. So, the proposal of achieving 5CC
on per RF port is that the maximum carrier numbers can be configured on
each port are still 6, but only 5 of them can be enabled and working normal.
The 5CC limitation on B1 shall be described in CPI. In case 6 carriers are

configured on one RF port, RadioSW will disable the sixth carrier of each RF
port by rejecting specific CDCI signals of related TR and DPCL devices, with
errorCode = CONFIG_DATA_ERROR /
CBD_DPCL_INCONSISTENT_OR_MISSING_CONFIGURATION_DATA (0x05). In this
case, the operationalState and availabilityStatus of that carrier shall be set to
DISABLED and DEPENDENCY_FAILED, and no alarm will be raised towards the
Radio or Carrier MO.
The impacted Device ID:
DPCL local ID TR local RF port

(=portIdDl) ID (=portIdUl) (4-branch/6-branch)
11 11 A/A
12 12 B/B
Ericsson Internal

2023-12-21 PF24
23 23 C/C
24 24 D/D
35 35 -/E
36 36 -/F
The impacted CDCI signals:
 CDCI_TR_GET_DEVICE_CAPABILITY_REQ
 DPCL_SETUP4_REQ
5.8[7.8] GSM
5.8.1[7.8.1] Common
5.8.2[7.8.2] GRAT Function Module Specific
5.8.3[7.8.3] GSM G1 Specific
Feature Short Name:
Radio6626
FDD Radio4466
Expected Release:
Radio6626: G21.Q3
FDD Radio4466: G21.Q4
For GSM G1, this feature will cover:
 MR7341: Visby platform
 MR9002: Radio6626 in Ericsson Radio Systems (PV)
 MR9002-SP3: GSM G1 support Visby Radios & Stockholm

Radios in mix mode only
 MR9003: Radio6626 66B1 66B3 C (Visby FV)
 MR8930-SP1: FDD Radio4466 in Ericsson Radio Systems (Visby

PV)
Ericsson Internal

2023-12-21 PF24
 MR8932: Radio4466 44B1 44B3 44B7 C (Visby FV)
 MR9002-SP4: Radio6626 Low Band in Ericsson Radio Systems
 MR09176 Radio 6626 66B8 66B20 C (Visby Low Band FV)
Requirement clarifications for this Radio6626/Radio4466 are as below:

Item Description/Example Radio6626/Radio4466
Type
specific
Based
Platfor
platform Visby
m
type
Introduce new
load file
Radio 6626, New
radio LMC
Radio 4466, New
radio LMC
Reuse
Reuse
legacy
Radio4466 LMC
Load load file or
But, these LMC
file create
will not be
new load
included in the
file
GSM load file,
and the
corresponding
implementation
is in MR9002-
SP3.
Radio6626: B3
and other FV
bands
Band
B0/B2/B3/B5/B8/B25/… Radio4466: B3
Number
and other FV
Band bands
GSM G1 only
Single band/ dual band/ triple
Multi-band support single
band/…
band
IBW 20M
Mixed mode (if clearly stated that no

Mixed Mode single mode support)/ Mixed mode &
Mixed mode
mode support Single mode (default value if no clear
objection to single mode support)
Three Three Yes, radio6626

Sector Sector is a 3-sector
support radio
Ericsson Internal

2023-12-21 PF24
Radio4466 does
not support 3
sectors
Radio6626
introduce new
If new RBB shall support in
Cascad Cascading RBB
cascading, the new RBB shall be
ing support No new RBBs
added into radio configuration doc
introduced by
Radio4466
Radio6626
Product
Check if it's a known name pre-fix Radio4466
Name
Radio 6626
Name 66B1 66B3 C
Radio 4466
1. Valid from NGR radios.
44B1 44B3 44B7
Market 2. Check if it's a known name pre-fix
C
Name 3. Check if it's a known naming
convention
Radio 6626
66B8 66B20 C
TR-DCI
update
No impact
(revision if
updated)
BCI
IWD
update
No impact
(revision if
updated)
ANTPI
update
No impact
(revision if
updated)
GSM
supported
UL/DL
carrier
Hardcoded now for GSM, due to lack DL:4
Carrier number
of GSM specific info in TR-DCI UL:5
per
band/per
port/per
radio
Power power per Radio6626

Config band/port/ B1:
radio 60W/band/port(6
x60W)
B3,B8:
80W/band/
port(6x80W))
Ericsson Internal

2023-12-21 PF24
Radio4466:
B1/B3/B7:
60W/band/port
maximum
20W per
carrier
when BW 1. Not valid for Platform based radios 20W per carrier
range with and valid from NGR radios Follow Legacy
in 0 ~
GSM
IBW
no larger
than 1/6
MCPA
1. Not valid for Platform based radios
power Valid
and valid from NGR radios
when BW Follow Legacy
range
above
GSM IBW
1. AIR don't support TMA

TMA
2. TMA can't support when RET is Yes
Support
configured
1. Class A radio don't support RET on

RF ports
2. Class B radio supports RET on RF
AISG
ports
RET
3. Air product normally has internal Yes
Support
RET, but except the Birka Air
platform, not support RET
4. RET can't support when TMA is
configured
TMA/RET
30V
Voltage
Feeder
Check if
Feeder supervisio
ANTP_CAP_DEVICE_FEEDER_CO
Supervi n Yes
NNECTIVITY is supported in ANTP
sion configurati
for this radio
on
Micro sleep TX GSM for new Radios.

Since radio baseline for micro sleep
tx GSM is ongoing, we'd better to
double confirm with Radio SW that
Micro
Power whether SBPS is enable for GSM
Sleep TX No
Feature carriers or not. The principle for
GSM
supporting Micro sleep TX GSM is
that if LTE side support SBPS, then
GSM should support SBPS and Micro
sleep TX GSM shall be supported.
Ericsson Internal

2023-12-21 PF24
1. Normal radios, except Air and

Radio 2468, support normal
VSWR. No VSWR support on Birka2.
VSWR
VSWR 2. Multi-VSWR is only supported in Yes
interface level, i.e. IWD is supported
but OMT and BTS are not supporting
now.
1. Local radio don't support EC port,

then no APC-light.
SU (APC-
2. Air product don't support EC port,
SU light/EC- Yes
then no APC-light.
light)
- Exception: AIR4435 supports EC
port and SU.
Air product don't support EC port,

Externa External then no APC-light.
Yes
l Alam Alarm - Exception: AIR4435 supports EC
port and external alarm.
DRS
DRS complianc Yes
e
5.8.3.1[7.8.3.1] Issues/Assumptions
1. Issue: How to split the platform Visby binary file?
Conclusion: Closed. GSM need to provide script for Visby binary

file split and update document “RUS SW Metadata file and
deliveries to GSM”(2/1013-CRH 109 0526 Uen).
GSM will not introduce new LMC, so this issue will not exist.
2. Issue: How the build procedure should look like?
It shall be checked whether build flow or special scripts needed for

build procedure.
Conclusion: Closed. Some minor update needed, EE team will

work on this.
GSM will not introduce new LMC, so this issue will not exist.
3. Issue: GSM BTS will not be able to control RUS SW version if

radio introduce MR9002-SP3, it brings incompatibility issue later if
peer DU use very old release while GSM BTS SW is new, protocol
between GSM BTS and radio such as TR-DCI/ BCI/ RICI/ ANTPI/
NGSI, may be not negotiated successfully.
Ericsson Internal

2023-12-21 PF24
Conclusion: Confirmed with IWD guardian in radio side, Radio

should keep a golden version (TR-DCI:10, BCI:3, RICI:3, ANTPI:4,
NGSI:2) supported in future and it should be brought up to OA/PS
of a particular feature where BTS needs to support multi-version
negotiation for these protocols.
4. Issue: BTS CI will not be able to detect the potential RUS SW

issue in DUG20+OtherRAN+new Radio HW configuration if
MR9002-SP3 apply to the new radio HW.
Conclusion: Radio side will take the responsibility to monitor RUS

SW issue in DUG20+OtherRAN+new radio HW configuration and
suggest covering DUG20+OtherRAN+new radio HW configuration
in MSMM NSV and GRAN CI.
5. Issue: In MR9002-SP3, if DU do nothing in the scenario that DUG

has no APP RUS SW for the radio and the radio has no pre-
installed SW and runs on AUBoot, and just wait for the “other DUs”
take actions, it may end up into a hanging scenario. This issue has
no impact on Visby and Stockholm radios since these radios will
be pre-installed with RUS SW before delivery to customers.
Conclusion: DUG would restart radio and try to establish BCI

connection on only protocol version 3(Radio runs on APP RUS
SW). Other DU would be possible to establish BCI connection on
protocol version 1 and load RUS SW to the radio.
5.8.4[7.8.4] User Story Impact Summary

U U U U U U U U
S S S S S S S S
1 2 3 4 5 6 7 8
Status (NDS P P P P T T T P
rev) R R R R A A A R
E E E E P P P E
L L L L P P P L
Technical 3 4 3 2 2 2 3 2
Complexity 1
Function O O O B O O O P
Areas*) & & M S & & & l
M M T C M M M a
, , P P P t
P P l l l f
l l a a a o
a a t t t r
tf tf f f f m
o o o o o
r r r r r
m m m m m
, , O
O R O M O
M a M T M
T d T T
i
Ericsson Internal

2023-12-21 PF24
o
,
O
M
T
HW Impacts - - - - - - -
BTS CPI - Y - - Y Y Y N
Impact
Product - - - - - - -
Packaging
Supply - - - - - - -
Preparation
Licensing or - - - H - - -
ECCN W
A
C
Upgrade and - - - Y - - -
Update
Security - - - - - - -
Impact
Standards - - - - - - -
Test Tools - R - - - - -
B
S
M
a
s
t
e
r
3PP/FOSS - - - - - - -
impact
External - - - - - - -
Nodes
Impacted:
- MSC - - - - - - -
- SGSN - - - - - - -
- MS - - - - - - -
- other - - - - - - -
- - - - - - -
Dependencies
to other
features
planned to be
developed
Lead time - - - - - - -
aspects
PLM - - - - - - -
Other - - - - - - -
Table 27 User Story Impact US1-US8

Ericsson Internal

2023-12-21 PF24
5.8.5[7.8.5] Solution Package and User Stories
5.8.5.1[7.8.5.1] FEAD
SP1: Radios 6626 G,W,L,NR and ESS with 3 sectors
US1: Software key for 6 RF ports US4: Support for new HWAC(BSC)
Support for new CXP load module
US2: Take one Radio6626 into US3: Support two Radio 6626 Star,
operational Cascade and configuration
MR8930 SP1: Radio 4466 in Ericsson Radio Systems
US5:
BTS and OMT support for radio4466
Ericsson Internal

2023-12-21 PF24
MR9002 SP3: GSM G1 support Visby Radios & Stockholm

Radios in mix mode only
US7:
GSM G1 support new Radio HW in mix mode only
MR9002 SP4: Radio6626 Low Band in Ericsson Radio

Systems
US8:
BTS support for Radio 6626 Low Band product
5.8.5.2[7.8.5.2] Inter Working Description
No Impact
5.8.5.3[7.8.5.3] Business Perspective
For GSM RAN, Radio6626 can be delivered for the deployment in

RBS6000 DUG20.
Required User Stories: 1,2,3,4
For GSM RAN, Radio4466 can be delivered for the deployment in

RBS6000 DUG20.
Required User Stories: 6
For GSM RAN, Visby and Stockholm radios will be able to be

delivered for deployment in RBS6000 DUG20 in MSMM without LMC
handling.
For GSM RAN, Radio6626 Low Band can be delivered for the
deployment in RBS6000 DUG20.
Ericsson Internal

2023-12-21 PF24
5.8.5.4[7.8.5.4] System Improvements
Not applicable
5.8.5.5[7.8.5.5] Impact on Legacy
No Impact.
5.9[7.9] EWCAT Function Module
The below part which is for Radio 6626 is also applicable to FDD Radio
4466.
5.9.1[7.9.1] Common
 Duplex Mode
NR don't support mixed FDD/TDD mode(G2)
NR will support mixed FDD/TDD mode on the same DU (but different XBM) (G3)
LTE support mixed FDD/TDD mode on the same DU with license
 CPRI Rate
G3 C1 will support 24.33Gb/s in 20.Q4; G2 support the max CPRI rates 10.1Gb/s
 TMA Configuration
No change.
 ESS
SP172: ESS FDD C1 functionality up to 10.1G
 Upgrade
Routine change for new product in CAT, update FDF
 Others
Radio6626 can communicate with antenna system on RET port or RF port.

Ericsson Internal

2023-12-21 PF24
No extra work is needed for I/F. e.g. TRDCI, BCI.
For VSWR function, Radio6626 support multi-band VSWR, which means that they
will indicate DU side with supporting VSWR on per port per band by reporting
device capability with MB_VSWR via ANTPI.
5.9.2[7.9.2] Supported configuration

Ericsson Internal

2023-12-21 PF24
Note:
1. For cascading on one DU or 2 DU connected to the same Radio:
 DATA 1 in and DATA 2 out: DATA1 => DATA2
 DATA 3 in and DATA 4 out: DATA3 => DATA4
2. For NGS synchronization for 2DU connected to the same Radio:
 Only DATA1 and DATA2 can be used for NGS synchronization.
3. Update the Radio Node Configurations and Manage Node Group Synchronization documents.
5.9.3[7.9.3] Sector configuration
Typical configurations as below based on:
The RfPort A/B/C/D/E/F support B1/B3 UL
The RfPort A/B/C/D/E/F support B1/B3 DL
1. Single band B1(Legacy Configuration)
2. Dual band B1 B3 (Legacy Configurations)

Ericsson Internal

2023-12-21 PF24
3. Dual band B1B3 with TMA B1/B3(2-2) (Legacy Configurations)
Note:
Ericsson Internal

2023-12-21 PF24
For these sector configurations, need verification as many as possible.
5.9.4[7.9.4] New Fault
New fault will be introduced to indicate 48V input failure at slave port.
FaultID: POWER_SUPPL_48V_NOT_AVAIL_PARTIAL
POWER_INTERRUPT_INPUT_POWER_INSUFFICIENT
AdditionalData: Carrier IDs for all setup affected carriers.
Singnal: DC_TRS_FAULT_IND, DC_TRS_FAULTCEASE_IND
1. Forward to APC module to raise alarm

Ericsson Internal

2023-12-21 PF24
2. MO state propagation follows the legacy behavior
3. Forward to RRC module to handle the state propagation
Note:
Ericsson Internal

2023-12-21 PF24
POWER_SUPPL_48V_NOT_AVAIL_PARTIAL
POWER_INTERRUPT_INPUT_POWER_INSUFFICIENT will not
coexist with legacy fault
POWER_DISTURBANCE_INPUT_POWER_LOW, which means that
these two faults will not be reported from Radio at the same time.
5.9.5[7.9.5] User Stories
5.9.5.1[7.9.5.1] User Story 1 – Software key for 6 RF port Support for new CXP
load module
5.9.5.1.1[7.9.5.1.1] User Story Description and Acceptance Criteria
Team found some CF card's space is insufficient during the PD stage.

The insufficient is caused by CF card's file system FAT table partly
corrupted. After impact analysis, it was determined that the LMC of
Radio6626 would not be introduced into the load file of GSM.
The realization of corresponding functions depends on MR9002-SP3.
As an operator I will be able to download BTS and RUS SW that

supports Visby and I will not able to download an old SW that are
incompatible with Visby.
There are the acceptance criteria:
1. New load files for the new CXP shall be included in UCF
2. Function Change with no fault, SW load to Radio6626 with no

fault.
3. It is not possible to load legacy BTS SW in radio 6626

configuration.
4. Radio6626 can only be configured in Mix mode.
5. The OMT shall indicate a warning when install/check IDB in case

the IDB and Radio6626 configuration mismatch.
6. The OMT shall indicate a warning when install/check IDB in case

the related BTS SW version does not support radio6626
5.9.5.1.2[7.9.5.1.2] General
The purpose with this user story is to ensure that the downloaded BTS
SW is capable to handle new Visby Platform.
A new CXP number and new load files will be provided by RUS SW.
The size of the SW will be around 30M and probably will be divided
into 4 load files.
Ericsson Internal

2023-12-21 PF24
Radio 6626 has 6 RF ports, BTS needs to add a SW key(6TXRX) to

support this configuration.
5.9.5.1.3[7.9.5.1.3] Function Area
BTS FA: O&M
BTS FA: Platform
BTS FA: OMT
5.9.5.1.4[7.9.5.1.4] BSC Implementation Description

NA
5.9.5.1.5[7.9.5.1.5] BTS G1 Implementation Description
5.9.5.1.5.1[7.9.5.1.5.1] Overview of Solution
The BTS shall introduce new SW key in File Info File to reduce the risk
for the operator to download an old BTS SW that does not support
Visby Radio6626LMC.
Adding the new load file information in UCF SW.
Adding the new load file information in DEST_LF.
REMP need to be updated to be able to handle new load module.
The new BTS software file package need to be able to be stored on a

flash card via the OMT.
Implement script to split RUS software into several parts.
PP(Program production) and SW tools need to be updated to handle

the delivery of RUS SW to GSM.
Function change shall be updated with new load files and software
key.
5.9.5.1.5.2[7.9.5.1.5.2] System Implementation
O&M Scenario Radio Equipment Handling
Handle the new Radio load files in load of RE software.
O&M Scenario Function Change

Ericsson Internal

2023-12-21 PF24
Handle the new radio load files when doing SW load and Activation.
Function change scenario needs to be updated due to new key
attribute.
O&M Scenario Operation And Terminal

FS Check IDB should be updated for the new key attribute. The OMT
shall compare the IDB towards the key attribute of the RBS SW.
5.9.5.1.5.3[7.9.5.1.5.3] Upgrade Impact
No Impact
5.9.5.1.6[7.9.5.1.6] ENM Implementation Proposal
No impact
5.9.5.1.7[7.9.5.1.7] STN Implementation Proposal
No Impact
5.9.5.1.8[7.9.5.1.8] Test Tools Implementation Proposal
No Impact
5.9.5.1.9[7.9.5.1.9] CI Product Impact
No impact
5.9.5.1.10[7.9.5.1.10] External Dependencies
No impact
5.9.5.1.11[7.9.5.1.11] Characteristics
The SW download time should be increased from BSC to DUG.
In PD phase, record the SW download time from BSC to DUG.
No Impact
5.9.5.1.12[7.9.5.1.12] O&M Impacts
No Impact
5.9.5.1.13[7.9.5.1.13] Test Configuration
BSC+DUG20+ Radio6626.
Ericsson Internal

2023-12-21 PF24
Abisco+DUG20+BB+Radio6626.
5.9.5.1.14[7.9.5.1.14] Test and Verification
Function Change scenario shall be tested for BTS SW.
Install IDB/Check IDB shall be tested.
EBU upgrade test shall be performed.
External function change and SW load of RE shall be performed in

L&S.
5.9.5.1.15[7.9.5.1.15] Technical Complexity
31
5.9.5.1.16[7.9.5.1.16] Rough Cost Estimation
Idea man hours
OMT 50
O&M 20020
Platform 30020
FV 30050
BTS CI 50
L&S 10050
Total 1000190 mhrs
5.9.5.1.17[7.9.5.1.17] Lead Time Consideration
Not applicable
5.9.5.2[7.9.5.2] User Story 2 – Take one Radio6626 into operational
As an operator, I can create and install IDB for one Radio 6626 in 3
sectors and take TRXs into operational.
As an operator, I can supervise faults which are related to RF E and F.
Acceptance Criteria:
Ericsson Internal

2023-12-21 PF24
1. OMT can configure one Radio 6626 in 3 continuous available

sectors. Each sector should be 2T2R 2-way RX diversity
configuration with correct RBB information.
2. OMT can configure MCTR mode for new RF port E and F.
3. OMT MMI shall display Radio 6626 information correctly in Radio,

Cabinet and Object view.
4. When OMT defining ALD System Setup for Radio 6626, N/A, RET
and RF A,C,E can be selected.
5. BTS shall report carrier capability to BSC bellow:

The TRX pool id shall be reported as 0 for the MCTR MOs related
to RF port A and B.
to RF port C and D.
to RF port E and F.
TRX pool size shall be 5, max number of TRX per MCTR shall be
4.
6. Maximum power per MCTR shall be supported up to 80W.
7. All configured TRX can be taken into operational, and mobile calls
can be set up successfully.
8. Fault codes for Radio Unit Antenna System Output Voltage and
RX Path Lost shall be raised if related fault happen on RF port E
and F.
9. Monitors “VSWR at TX Antenna” and “TMA Current” can supervise

on RF port E.
5.9.5.2.2[7.9.5.2.2] General
This user story will basically support Radio 6626 in OMT and BTS SW,
it covers:
 6T6R Radio, should be configured in 3 sectors.
 New RF port support : RF E, RF F
 OMT Configuration and Display.
 Fault handling and monitors on RF E, RF F.
 New RBB support: RBB 22 1 h

Ericsson Internal

2023-12-21 PF24
5.9.5.2.3[7.9.5.2.3] Function Area
BTS FA: OMT
BTS FA: O&M
BTS FA: Platform
BTS FA: Radio

NA
5.9.5.2.5[7.9.5.2.5] OMT Implementation Description
Radio 6626 is a 6T6R Radio and should be configured in 3 continuous

sectors, each sector shall be 2T2R with correct RBB.
Radio Equipment Setup:
Radio 6626 is selectable in RE Type if selected sector has 2 following

available sectors, Radio 6626 in following sectors shall show the RE
instance to indicate which RE it belongs to. Configuration rule can be
same as Dual Sector configuration.
MCTR mode can be configured for E and F for “Single or Mixed”.
An example:
OMT online help shall describe changes above.
RBB information:
First sector: RBB 22 1 f

Second sector: RBB 22 1 g
Third sector: RBB 22 1 h (New for DUG)
DBB combination for RBB 22 1h shall be same as RBB 22 1f/ RBB 22

1g in star configuration.
Radio View
Ericsson Internal

2023-12-21 PF24
Display Radio 6626 with RF A~F, its connection with DUG and
Antenna Sector information. New RF E and F should be included in
Radio 6626’s third Antenna Sector.
IDB Impact
New RU_Type RUS (6TX6RX) for FuncType RXD, RE and MCTR.
New RU_Type 8:0 for Radio 6626.
Basic Config shall be updated for new RBB.
ALD System Setup
All Radio 6626 RF port will support ALD power supply and signaling,
ALD Port Option: RET, N/A, RF A, RF C, RF E.
Monitor
“VSWR at TX Antenna with port X” shall be extended to support RF E-

F.
“TMA Current at PortX” shall be extended to support RF E.
8.8.6.2.6.1 Overview of Solution
Radio Profile Struct
Pr RU_Type 8:0 G G R A
od S S e i
uct M M m r
Na ot
me D U e F
L L Fl l
a a
g g
R LocalIDB_RU_Typ 4 6 T F
R e8_0Radio_6626 5 r a
U6 u l
62 e s
6 e
Adaption for RF port E and F
BTS SW packages are impact by extend RF support from A~D to A~F.
New KRC
Ericsson Internal

2023-12-21 PF24
Introduce new KRC for Radio 6626 66B1 66B3 C
Fault Handling on RF E and F
New SEs: SE_RE_OUTPUT_VOLTAGE_E and

SE_RE_OUTPUT_VOLTAGE_F shall be introduced. Raise and cease
rule shall be same as legacy
SE_RE_OUTPUT_VOLTAGE_A_B_C_D.
Monitor
Mon_VSWR_AtTX_Antenna shall be supported at RF E~F.
Mon_TMA_Current shall be supported at RF E.
8.8.6.2.6.2 System Implementation
RBS Products
Radio 6626 shall be included.
O&M Scenario Operation And Maintenance Terminal (OMT) and
O&M Scenario Installation Database Handling (IDH)
Support for Radio 6626, new RBB and new RF ports configuration.
O&M Scenario Radio Supervision
Handling faults on new RF ports.
Fault Code Description
Need to be updated due to new RF ports.
5.9.5.2.7[7.9.5.2.7] ENM & STN Implementation Description
No impact
5.9.5.2.8[7.9.5.2.8] Test Tools Implementation Description
Abisco: No impact.
RBS Master: Will be impact by increasing number of RF-branches.
OMT CI:
Radio 6626 shall be included in OMT CI.
OMT CI script need to be updated to adapt Radio 6626.
Ericsson Internal

2023-12-21 PF24
BTS CI:
Radio 6626 shall be included in BTS CI traffic cases.
BTS CI script need to be updated to adapt Radio 6626.
5.9.5.2.11[7.9.5.2.11] O&M Impacts
Abisco + 1 DUG 20 + BB + 1 Radio 6626
According to FV Baseline Level, Radio 6626 should be L1. That

means L1 to L5 cases should be performed on Radio 6626.
L&S shall be performed to verify the BTS stability and robustness.
T&S shall be tested for regression.
4 out of 5.
Idea man hours
OMT 500
O&M 240
Radio 500
Platform 30
FV 900
OMT CI & BTS CI 440
L&S 80
T&S 120
Total 2810 mhrs

Ericsson Internal

2023-12-21 PF24
Not Applicable
5.9.5.3[7.9.5.3] User Story 3 – Support two Radio 6626 Star, Cascade configuration
As an operator I can create and install an IDB for two Radio6626 star,
cascade configuration.
1. Create and install IDB for Radio6626 with 2 way RX diversity using
RBB44_1S, RBB44_1N, RBB44_1P, there should be no fault or
mismatch generated.
2. Create and install IDB for Radio6626 with 2 way RX diversity using
RBB44_2W, RBB44_2S, RBB44_2T, there should be no fault or
mismatch generated.
3. For two radio6626 Star, Cascade configuration, all configured

TRXs can be taken into operational with 2 way RX diversity.
4. RUS software can be loaded on RE with no fault.
5. Call shall be successfully set up for two radio6626 Star, cascade

configuration.
5.9.5.3.2[7.9.5.3.2] General
New radio block in the OMT need to be created and supported.
5.9.5.3.3[7.9.5.3.3] Function Area
BTS FA: OMT
BSC FA: NA

NA
8.8.6.3.5.1 Overview of Solution
Two Radio6626 Star, cascade configuration shall be supported in

OMT.
Ericsson Internal

2023-12-21 PF24
New radio block RBB44_1S, RBB44_1N, RBB44_1P, RBB44_2W,

RBB44_2S, RBB44_2T need to be supported by OMT for 2 way RX
diversity.
No new DBB added, reuse existing DBB.
8.8.6.3.5.2 System Implementation

Data Base Description
Adding 2 way RX diversity configuration using new RBB44_1S,

RBB44_1N, RBB44_1P.
Adding 2 way RX diversity configuration using new RBB44_2W,
RBB44_2S, RBB44_2T.
RS RBS6000 Radio Configurations
Include that GSM supports 3 new RBBs in star and cascading

configurations.
8.8.6.3.5.3 Upgrade Impact

No Impact
No Impact
No Impact
No impact
Impact on OMT CI
No impact
No impact
Ericsson Internal

2023-12-21 PF24
5.9.5.3.12[7.9.5.3.12] O&M Impacts
No impact
Abisco+DUG20+BB+ Two Radio6626
FV shall be performed for new RBB configuration.
Create/install/Check IDB, RE equipment handling, call setup shall be

tested with new RBB configuration.
OMT CI shall be tested due to new RBB.
No BSC/ENM/OSS impact, NLT not needed.
Idea man hours
OMT 700
FV 200
OMT CI 150
Total 1050 mhrs
Not Applicable
5.9.5.4[7.9.5.4] User Story 4 – Support for new HWAC
As an operator I can configure Radio 6626 with the maximum power it

can support.

Ericsson Internal

2023-12-21 PF24
1. New license controlled MCTR power HWACs, required to

configure 480W per radio unit, shall be supported in the BSC.
2. The BSC shall be able to configure 6 MCTRs and the power 480W
per radio unit.
5.9.5.4.2[7.9.5.4.2] Function Area
BTS FA: NA
BSC FA: O&M, BSC AP, Configuration
The following new AXE parameters: MCTRPWR340, MCTRPWR360,

MCTRPWR380, MCTRPWR400, MCTRPWR420, MCTRPWR440,
MCTRPWR460, MCTRPWR480 shall be added to the parameter set
CME20BSCS.
The new AXE parameters shall be introduced to the capacity lock

handling framework, and they shall be handled the same way as
existing HWACs like MCTRPWR320 etc.
Use of new power HWACs shall be visible on RXCLP and RACLP

printouts.
Capacity lock maximum volume for the new capacity locks shall be
added to the BSC model to MOC CapacityLockBsc.
Handling of MCTR configuration shall be updated to be able to

configure collocated MCTRs with the power 480W per radio unit. If
MCTR configuration is not possible due to lack of required HWACs the
existing mismatch PWRHWAC shall be set for the MCTR.
NA
5.9.5.4.5[7.9.5.4.5] Upgrade Impact
FBU shall not attempt to set the new AXE parameters.
Follow-John
No Impact
Ericsson Internal

2023-12-21 PF24
No impact
No impact
No impact
No impact
5.9.5.4.12[7.9.5.4.12] O&M Impacts
Operator shall be aware about a need of ordering new HWACs for

power above 320W.
The parameter CLNAME shall have new values: MCTRPWR340,

MCTRPWR360, MCTRPWR380, MCTRPWR400, MCTRPWR420,
MCTRPWR440, MCTRPWR460, MCTRPWR480.
The parameter pwrhwac of the printout RADIO X-CEIVER

ADMINISTRATION CAPACITY LOCK USE DATA shall have new
values: 340W, 360W, 380W, 400W, 420W, 440W, 460W, 480W.
The new attributes: mctrPwr340ClMax, mctrPwr360ClMax,

mctrPwr380ClMax, mctrPwr400ClMax, mctrPwr420ClMax,
mctrPwr440ClMax, mctrPwr460ClMax, mctrPwr480ClMax shall be
introduced to the BSC model MOC CapacityLockBsc.
A BSC STP with the BSC development track SW is needed with

APG43L and APZ 212 60. Real BTS is not needed, it is enough to use
2Gsim.
It shall be verified whether it is possible to configure 6 MCTRs and the

output power up to 480W per radio unit.
BSC response to changing capacity by LKF installation shall be

verified.
Ericsson Internal

2023-12-21 PF24
Cost: 1-2 TW
5.9.5.5[7.9.5.5] User Story 5 – BTS and OMT support for radio4466
As an operator I can select radio4466 when creating IDB for radio4466

in OMT.
As an operator I can take TRXs into operational with 2-way or 4-way

RX diversity on radio4466.
1. Create and install IDB for Radio4466 with 2-way or 4-way RX

diversity, there should be no fault or mismatch generated in OMT.
2. Radio4466 shall only be supported as Mix mode in GSM G1.
3. Radio4466 shall be displayed correctly in Radio, Cabinet and

Object view in OMT MMI.
4. When defining ALD System Setup for Radio4466, the value shall
be set according to below list:
{
RET port,
RF port A, C,
N/A
}
If degrading function applied, the value shall be set according to

below list:
{
RET port,
RF port A
N/A
}
5. The BTS shall report the following capabilities towards the BSC:
Ericsson Internal

2023-12-21 PF24
- The TRX pool id shall be reported as 0 for the MCTR MOs

related to RF port A and B.
- The TRX pool size shall be set to 5.
- The “Max number of TRXs per MCTR” shall be set to 4.
- The TRX pool id shall be reported as 1 for the MCTR MOs

related to RF port C and D.
- The TRX pool size shall be set to 5.
- The “Max number of TRXs per MCTR” shall be set to 4.
6. All configured TRX can be taken into operational, and mobile calls
can be set up successfully.
7. Maximum power per MCTR shall be supported up to 60W.
8. BTS shall reject the configuration when the configured carrier

spacing violates the IBW/VIBW limitations (reported by radio) on
MCPA and/or RE level.
9. Radio4466 shall work correctly when degrading to 2TX and 1TX

configurations.
10. Create and Install IDB shall succeed for radio4466 with dual
sectors.
11. For dual-sector configurations, all configured TRXs can be taken

into operational and mobile calls can be set up successfully.
5.9.5.5.2[7.9.5.5.2] General
The purpose with this user story is to support a new Visby PV FDD
Radio4466 and the first FV Radio4466 44B1 44B3 44B7 C.
5.9.5.5.3[7.9.5.5.3] Function Area
BTS FA: O&M
BTS FA: Platform
BTS FA: OMT

NA

Ericsson Internal

2023-12-21 PF24
New KRC numbers shall be added into UCF SW, how to add the KRC
number is depend on MR9002-SP3 solution.
New item for Radio4466 should be added in GSM G1 Radio Input

Table.
New parameter A,C added for attribute Class Type, OMT can handle
the new parameter.
Following radio profile shall be added for Radio 4466.
Pro RU_Type 8:0 G G R A

duct S S e i
Na M M m r
me ot
D U e F
L L Fl l
a a
g g
Rad LocalIDB_RU_Type8 4 5 Tr F
io44 _0Radio_4466 u a
66 e l
s
e
New RU_Type8_0 shall be introduced for Radio4466.
Radio 4466 shall be configured with the same RBB as

Radio4415/4417.
O&M Scenario Installation Database Handling
Radio 4466 shall be selected during configure 4T4R radio in dialogue

“RE setup” and shall be visible in cabinet, radio and object view in OMT.
Data Base Description

Define RU_Type8_0 for Radio 4466
5.9.5.5.5.3[7.9.5.5.5.3] Upgrade Impact
No Impact
No impact
Ericsson Internal

2023-12-21 PF24
No Impact
No Impact
No impact
No impact
No impact
5.9.5.5.12[7.9.5.5.12] O&M Impacts
No Impact
Abisco+DUG20+other DU/BB+Radio4466.
According to FV Baseline Level, Radio 4466 should be L3.
Idea man hours
OMT 90
O&M 20
Platform 40
FV 260
Ericsson Internal

2023-12-21 PF24
L&S 30
BTS&GRAN CPI 30
Total 470
Not applicable
5.9.5.6[7.9.5.6] User Story 7 – GSM G1 support new Radio HW in mixed mode only
Due to the restriction of BTS flash card memory size, DUG20 will not
be able to support any new radio which introduces new load module.
Optional ideas have been put forward and discussed for new radio
LMCs handling in GSM G1. User story 7 will base on one of the ideas
with agreement from Visby and Stockholm SPMs and provide a detail
solution to support Visby and Stockholm radios working in only MSMM
in GSM G1 and leave the RUS SW version control to peer DU.
Without specific statement, the radio described in below sub-chapters

in this US stands for any radio in Visby or Stockholm family.
As an operator, I can upgrade/downgrade BTS SW but RUS SW of

the radio will not be upgraded/downgraded through GSM G1 BTS.
These are the acceptance criteria:
1. During external function change, BTS will not download and

upgrade/downgrade the RUS SW of the radio, and the radio will
not be restarted by BTS SW activation.
2. If pre-installed RUS SW exists on the radio, the radio can start on

pre-installed RUS SW when the radio is rebooted.
3. If no pre-installed RUS SW exists on the radio, legacy fault

“SE_RE_SWLOAD_FAILED” will raise on the radio when the radio
is rebooted. The fault will not be ceased until peer DU load RUS
SW to the radio and start the radio on the RUS SW in specified
time.
4. If the radio has running RUS SW in MSMM, the running RUS SW

will not be changed by GSM BTS.
5. OMT shall display the information in RBS software information that

RE[inst] (Radio Name) can’t be upgraded from DUG20, it will be
supported in mixed mode only.
Ericsson Internal

2023-12-21 PF24
5.9.5.6.2[7.9.5.6.2] General
The purpose with this user story is to ensure that GSM G1 can support
Visby & Stockholm radios in mixed mode only.
5.9.5.6.3[7.9.5.6.3] Function Area
BTS FA: OMT
BTS FA: Platform (REMP & UCF)
BTS FA: O&M

NA
GSM G1 will not integrate the LMC and corresponding metadata file
for the new radio HW into BTS UP and will support this HW in mixed
mode only.
UCF support new radio HW in mixed mode only
UCF will introduce new tag “NoLoadFileList/HwProdNbrList”, the

product number and revision of the new radio will be inserted under
this tag. If BTS detected a radio HW, and the product number match
one of the product numbers recorded under the new tag, this HW
would be identified as Known_HW_without_LMC.
Support new radio HW in MSMM in load of RE function
REMP will not perform SW loading for the radio identified as

Known_HW_without_LMC and will not restart this radio by SW
activation during external function change.
Ericsson Internal

2023-12-21 PF24
New RUS SW selection logic as specified in below table will be set up

in REMP for the radio identified as Known_HW_without_LMC.
BTS Pre- RUS SW

connect conditio selection Consequence
radio on n logic
Select
PIS exists Radio will start on PIS
PIS.
Radio will keep on

BCI
AUBOOT.
Protocol
version
No PIS No SW BTS will handle and try to
== 1
exists selected. recover from this fault
scenario refer to “Fault
handling for radio missing
PIS SW” section.
BCI
Gives up
Protocol Radio keeps on the
- RUS SW
version != running RUS SW.
selection.
1
Table 28. RUS SW selection logic for known HW without LMC
Fault handling for radio missing PIS SW
If DUG established BCI connection on protocol version 1 with radio

identified as Known_HW_without_LMC and it happened no pre-
installed RUS SW exist on this radio HW. DU would take following
actions in order.
1. Raise legacy SE “SE_RE_SWLOAD_FAILED”.
2. Restart the radio.
3. Inhibit BCI connection establishment on protocol version 1 with
this radio.
During handle the BCI connection, if it’s inhibited to establish BCI

connection on protocol version 1, DU would loop to request BCI
connection establishment on ELIB_BC_REV (3) with retry interval of
10 sec (refer to legacy) if the request was rejected until
1. BCI connection is established on protocol version 3. SE
“SE_RE_SWLOAD_FAILED” would be ceased.
2. The number of retries reach the maximum value (refer to
legacy). DU would give up BCI connection with the radio.
Note: The maximum number of retries should be reviewed and

reconsidered in radio project as the availability of PV=3 depends on
the size of LMC to download.
OMT support new radio HW working in mixed mode only

Ericsson Internal

2023-12-21 PF24
OMT will introduce a new attribute in Radio Input Table to indicate

whether BTS UP contains the load module for this radio.
For the radio for which BTS is not capable of upgrading, it will be
limited at mixed mode (single standard single mode such as
DUAL_DUG configuration will not be supported) during create IDB,
and an indicative note should be displayed on “RBS Software
Information” UI of OMT for this radio.
O&M Scenario Radio Equipment Handling
Setup new RUS SW selection logic for the radio without LMC supported
in GSM G1.
UCF
Ericsson Internal

2023-12-21 PF24
UCF support the radio without LMC integrated into BTS UP.
Fault code Description
Update fault handling for “SE_RE_SWLOAD_FAILED”
5.9.5.6.5.3[7.9.5.6.5.3] Upgrade Impact
No Impact
No impact
No Impact
No impact
BTS CI will not be able to detect potential RUS SW issue in MSMM. It

should be considered to uplift MSMM NSV and GRAN CI to cover the
configuration DUG20+otherRAN+new radio HW
No impact
No Impact
5.9.5.6.12[7.9.5.6.12] O&M Impacts
No Impact
DUG20+BB5216+Radio6626(see note)
Note: Any radio HW in Visby/Stockholm platform can replace

Radio6626 in the configuration.
Ericsson Internal

2023-12-21 PF24
The EFC procedure shall be tested.
OMT Function Display RBS software Information shall be tested.
RUS SW selection logic shall be tested.
Idea man hours
OMT 150
Platform 330
O&M 30
FV 240
Total 750
Not applicable
5.9.5.7[7.9.5.7] User Story 8 – BTS Support for Radio6626 Low Band
As an operator I can take TRXs into operational on Radio6626 B8B20.
1. BTS can recognize the Radio6626 Low Band HW as Known

hardware and the load file will not be integrated in BTS SW.
2. All AC for MR9002-1 should also applied for MR9002-4.
5.9.5.7.2[7.9.5.7.2] General
The purpose with this user story is to support Radio6626 Low Band.
Ericsson Internal

2023-12-21 PF24
5.9.5.7.3[7.9.5.7.3] Function Area
BTS FA: Platform
No Impact
The UCF should be updated to add new product KRC number.
UCF
Add the KRC number into the new label

"NoLoadFileList/HwProdNbrList" of UCF SW.
Abisco+DUG20+other DU/Baseband+Radio6626 B8B20
Function Change test should be performed for new HW.
Suggest that basic traffic function testing for regression.
Idea
man
hour
s
Platfor 20
m
FV 130
Ericsson Internal

2023-12-21 PF24
Total 150
5.10[7.10] TN Function Module
N/A
5.11[7.11] BBI Function Module
N/A
5.12[7.12] RCS Function Module
N/A
5.13[7.13] OSE Platform Function Module
N/A
5.14[7.14] ENM/OSS-RC
It follows John impact on ENM to support new MCTR Power license

capacity locks (mctrpwr340, mctrpwr360…) from the BSC model. This
is reviewed with Mary Mcmahon and Suresh Koukuntla.
5.15[7.15] Radio SW
Overvieww
The Radio SW for DB Radio 6626 should be developed on top of the NGR G2/G3
based DB Radio SW. The Radio SW baseline to be used for the Radio 6626 SW
development will contain the following components:
 NGR G2 based DB Radio SW for supporting dual-band radios

DB4442/DB4480 as well as DB4443 and DB2242.
 Reuse digital power controller UCD3138128A from Oslo.
 Palau Pre-Dev Radio SW for supporting the new transceiver

Palau.
 MTB Pre-Dev Radio SW for supporting the new ASIC Radon

1.1.
Ericsson Internal

2023-12-21 PF24
From a Radio Function and radio SW application point of view, the

Radio 6626 inherits most of its functionality from the legacy Oslo
which is multiple band platform. The TRX driver set used will be
“810”and the TPA driver set will be “810”. Mainly modification located
in services layer and drivers layer. Figure 8.15.1-1 shows an
architecture overview.
MR9002-SP4 is based on Radio 4466 MR8930-SP1(Mongoose +

radon), will use 0.8 pitch radon compared with platform
radio6626/4466. 0.8 pitch radon compared with 1.0 pitch has added
some PINs which are invisible for SW, and also no changes for the
total functions, but will use new component configuration
ID(“dra_2_1_2”) for 0.8 pitch radon, then SW need add component
related database.
MR9002-SP4 will follow platform 4466/6626 for the TRX and PA driver
set,’810’ TRX driver set and PA driver set will be used.
Figure 8.15.1-1 Architecture Overview
A new Radon 1.1 ASIC is used by the Radio 6626. Compare to Radon
1.1, CPRI cascading and JESD204C 32.44 Gbps Interface supported.
As Radon 1.1 has a new SERDES IP, a new SERDES start up and
FW load procedure is needed. In the new IP the PLL clock control is
moved from ADC_DAC_IF to SERDES. The radio SW application
needs to adapt to this driver sets change. New componentConfigId
“dra_2.1.0” used.
A new TRX transceiver Palau is used. Consist of eight transmitters,

Eight receivers and two observation receivers. Fully integrated clock
synthesizer and JESD204B/C digital interface up to 19.66/32.44 Gbps.
Driver codes employ new FW of function block implementation from
MTB pre-dev. Making the code easier to understand and maintain by
using smaller modules. New componentConfigId “transceiver_4.0.0”
used.
Ericsson Internal

2023-12-21 PF24
Radio 6626 use the JESD204C protocol as an interface between ASIC

Radon 1.1 and component Palau. Service codes employ new FW of
JESD204B/JESD204C functional systemization from AIR6449. By
grouping all lanes/links used for a TRX device into a JesdLinkGroup.
So as to reflect the limitation in Radon that transmitter and the receiver
are grouped into lanes, which cannot be operated independently.
Radio 6626 has use case of two cable feed. Radio SW need to
monitor two 48V_OK signal and handle associated new power drop
function. Also Radio SW handle the two back off for two DC
independently under insufficient power supply.
3PP SW,
Vendor SW Name(FD in Ericsson Design

Name PRIM) Product NO Countr
including y
R_STATE
Synopsi Digital R1.1 2/ US

s SerDes FW,3PP CTX1010306
SOFTWARE R1A(1.16-4)
ADI Palau, ADRV9030 CTC102767/ SE

API 1 R1A
SE
Palau, ADRV9030 CTC102767/
ARM FW 2 R1A SE
Palau, ADRV9030 CTC102767/ SE

Gain Tables 3 R1A
SE
GUI 4 R1A
US
Visby Radio 6626 CXC 201
Palau config 3051/2 R1A
B1+B3
1/CTX 101
ADRV903x, 0319 R1A
Analog Device Inc
FOSS Device Tree 1/CAX 105 US

Compiler 8805 R1A
SE
DTC libfdt CXS 102
7391/1 R1A
Wind WRL18 for XCS CTC 101 SE

River 6832 R1A
US
34/CAX 105
3085 R1A
Wind Customer Content CTC 101 SE

River Management 6833 R2A
(CCM), Additions US
to WRL18 for XCS 33/CAX 105
9820 R1A
Xilinx 3PP 9/CAX 105 US

Ericsson Internal

2023-12-21 PF24
SOFTWARE/Vivad 8968
o, Xilinx
[7.15.1] Branch mapping
The following database parameters for the band, RfPort and branch
mappings in external sysDataParamRru6626 database file shall be
defined for DB Radio 6626:
 /Band[I|III]I/bandId
 bandId[0|1]/[dl|ul]/rfPorts
 bandId[0|1]/[dl|ul]/branches
 [ul|dl]/rfAnt[A|B|C|D|E|F]/[rx|tx]Branches
 [dl|ul][A|B|C|D|E|F]/carriers
 [dl|ul][A|B|C|D]E|F]/bandId[0|1]/carriers
 [dl|ul][A|B|C|D|E|F]/mcbNumber
 dl[A|B|C|D|E|F]/lbNumber
 ul[A|B|C|D|E|F]/adcbNumbers
 ul[A|B|C|D|E|F]/mcbsgNumber
The band, RfPort and branch mappings for 6 RfPorts solution (i.e.,
combined RfPorts for the bands) are shown in Figure 8.15.2-1 and
Figure 8.15.2-2.
3226 TX Mapping SW Branch View : Radon Port vs ANT Br

Mapping
FB Numbers: 4*4*6=96 B1
MCB Numbers: 2*2*4=16
LB Numbers: 2 *2*4=16 B3 FU IN(PA FU OUT(ANT Port,
Out) SW Br View)
Radon MCBG0 DAC_IF_0

MRIX_0/1 /2/3 TX0 TX0 PA0
FB00-05 MCB0 LB0 B1
MRIX_4/5 /6/7
TX1 TX6 PA6 B3 A
FB06- 11 MCB1 LB1
MRIX_8/9 /10/11
FB12- 17 MCB 2 LB2 TX2 TX5 PA5
MRIX_12/ 13/14/15
FB18- 23 MCB 3 LB3 TX3 TX3 PA3 B1
Palau_0 B3 B
CPRI 0 MCBG1 MRIX_16/ 17/18/19 TX4 TX7 PA7
FB24- 29 MCB0 LB4
ADCB0
MRIX_20/ 21/22/23 TX5 TX1 PA1 B1
FB30- 35 MCB1 LB5 B3 E
FB 36-41 MCB 2 LB6 2
ADCB
MRIX_24/ 25/26/27 TX6 TX2 PA2
MRIX_28/ 29/30/31 PA4
FB 42-47 MCB 3 TX7 TX4
CONNECT
CPRI 1 LB7 B1
F
B3
DAC_IF_1
MCBG2
FB48- 53 MCB0 LB8
MRIX_4/5 /6/7 TX1 TX2 PA10 B1
FB54- 59 MCB1 LB9 B3 C
FB60 - 65 MCB 2 LB10 MRIX_16/ 17/18/19 TX2 TX0 PA8
FB66 - 71 MCB 3 LB113
ADCB MRIX_20/ 21/22/23 TX3 TX3 PA11
B1
D
MCBG3
Palau_1 B3
FB72 - 77 MCB0 LB12

FB78 - 83 MCB1 LB13
FB84-89 MCB 2 LB14
FB90-95 MCB 3 LB15
Figure 8.15.2-1 TX Mapping

Ericsson Internal

2023-12-21 PF24
3226 RX Mapping SW Branch View : Radon Port vs ANT Br

Mapping
ADC Numbers: 2*2*4=16 B3 FU OUT(LNA FU IN(ANT Port,
IN SW Br View)
Radon MCBG0:MCBSG0 ADC_IF_0

MRIX_0/1 /2/3 RX0 RX7 LNA0
FB00-05 MCB0 ADCB0 B1
MRIX_4/5 /6/7
RX1 RX6 LNA1 B3 A
FB06- 11 MCB1 ADCB1
MRIX_8/9 /10/11
FB12- 17 MCB 2 ADCB2 RX2 RX5 LNA10
MRIX_12/ 13/14/15
FB18- 23 MCB 3 ADCB3 RX3 RX4 LNA11 B1
Palau_0 B3 B
CPRI 0 MCBG0:MCBSG1 MRIX_16/ 17/18/19 RX4 RX0 LNA2
FB24- 29 MCB0 ADCB0
ADCB0
MRIX_20/ 21/22/23 RX5 RX1 LNA3 B1
FB30- 35 MCB1 ADCB1 B3 E
FB 36-41 MCB 2 ADCB2
ADCB 2
MRIX_24/ 25/26/27 RX6 RX2 LNA8
FB 42-47 MCB 3
MRIX_28/ 29/30/31
RX7 RX3 LNA9
CONNECT
CPRI 1 ADCB3 B1
F
B3
ADC_IF_1
MCBG1:MCBSG0 MRIX_0/1 /2/3 RX0 RX1 LNA5
FB48- 53 MCB0 ADCB0
MRIX_4/5 /6/7 RX1 RX2 LNA6 B1
FB54- 59 MCB1 ADCB1 B3 C
FB60 - 65 MCB 2 ADCB2 MRIX_16/ 17/18/19 RX2 RX0 LNA4
FB66 - 71 MCB 3 ADCB3
ADCB 3 MRIX_20/ 21/22/23 RX3 RX3 LNA7 B1
D
MCBG1:MCBSG1 Palau_1 B3
FB72 - 77 MCB0 ADCB0

FB84-89 MCB 2 ADCB2
FB90-95 MCB 3 ADCB3
Figure 8.15.2-2 RX Mapping
For MR9002-SP4, the band/RfPort and branch mappings solution has

some changes, below Figure 8.15.2-3 and Figure 8.15.2-4 show the
changes, and database below maybe need to be added with prdType
for the new mapping.
/810/radonJesd:x/txLink:0 U8 0, 0, 3, 1, 2, 4, 6, 5, 7 /* link resource 0
(txLink:0) from DAC_IF_0, Mapping to Palau_0 lanes 0, 1, 2, 3, 4, 5, 6, 7 */
/810/radonJesd:x/txLink:1 U8 1, 7, 4, 5, 6 /* link resource 1

(txLink:1) from DAC_IF_1, Mapping to Palau_1 lanes 7, 4, 5, 6 */
/810/radonJesd:x/rxActiveLinks U8 0, 1, 2, 3 /* Which rx links are active

for radon:x */
/810/radonJesd:x/rxLink:0 U8 0, 3, 0, 2, 1 /* link resource 0 (rxLink:0)

from ADC_IF_0, Mapping to Palau_0 lanes 0, 1, 2, 3 */
/810/radonJesd:x/rxLink:1 U8 0, 4, 7 /* link resource 1 (rxLink:1)

from ADC_IF_0, Mapping to Palau_0 lanes 4, 7 */

/810/radonJesd:x/rxLink:3 U8 1, 5 /* link resource 3 (rxLink:3)

from ADC_IF_1, Mapping to Palau_1 lanes 5 */
Ericsson Internal

2023-12-21 PF24
4456 44B1C 44B3J 40B75C C, the third band B75C just support TX,
do not support Rx, so Rx drivers and services for 4xB75C branches
will be removed
Drivers
TRX Driver Set
There will be a new “/board/trxDrivers/set = 810” in production DB for

Radio 6626. Based on Dublin, change list shows bellow,
driverName subDriverName Comments
trxDrivers ruLtu, ltuPllSv

Ericsson Internal

2023-12-21 PF24
radonSerdes:0
radonSerdes:1
Rn1.1
radonCpriSerde
radon:0 s:x
bfxTddLte0Int:x
bfxTddNr0Int:x
bfxTddNr1Int:x
parallellJobRun trxTransceiver:0
Two Palau used
ner trxTransceiver:1
I2C addr and init

dfeFpgaSvTemp
sequence
rxSvTemp HW IWD change.
accelerometer HW IWD
pressureSensor
HW IWD
:0
temperatureSe
HW IWD
nsor
Follow Oslo. T
dcDcDrivers:0 8.15.3.7
chips used
2 external static LO
rxLoDrivers:0/1 8.15.5
chips
paPInterrupt:x. SRL interrupt for

x PAP
PA Driver Set
There will be a new “/board/paDrivers/set = 810” in production DB

for Visby RU6626.
Product Type ID
New product ID prd_1.1.0 is defined in production database

/componentConfigId. The PrdTypeId may be used as a part of keys in
database to distinguish different configurations on different Radio
product. When Radio SW startup, it will get the PrdTypeId from
/componentConfigId and use it to decode databases.
Ericsson Internal

2023-12-21 PF24
For RadioSW, the PrdTypeId should be added in some databases that

have different configurations with baseline products.
For TrxCtrl, the TrxCtrl team should be notified when the new
PrdTypeId for Visby 6626 is determined. They will add it into Txl code
and DPD configurations in order to support Visby 6626 in their
releases.
For RUxTest, the RUxTest team should be notified when the new
RuTypeId for Visby 6626 is determined. They will add it into
configuration file Common/RuTypeMap.txt in order to support Visby
6626 in their release. And the local INT team should be notified
because they maybe need to update their RUxTest configuration file
by themselves.
ETSW also need to add database support and adapt code change.
Like file etswBootMode.cc.
The impact is
For production database /componentConfigId:
1524- need to be updated accordingly to use prd_1.1.0 to replace

ruType_x.y.z.
For RadioSW database:
Need to add prefix prd_1.1.0 for some new databases.
For RadioSW Code:
The following classes should be updated accordingly to support prd_1.1.0

when searching databases.
class Database
class ComponentConfigID
The following interfaces between RadioSW and Txl will be updated

accordingly when initDeviceId():
txlIfRequiredCtrl.cc
For TrxCtrl:
TrxCtrl also check prd_1.1.0 from /componentConfigId to determine current

Radio product and use different configurations.
For RUxTest:
RUxTest need to support prdTypeId to recognize Radio products.

Ericsson Internal

2023-12-21 PF24
For MR9002-SP4, new prdType ID is needed. ‘/id_prdType_1.4.x’ has

been assigned for this radio.
The related DB items with prdType ID all need to add a set of DB with
‘/id_prdType_1.4.x’ and the channels.txt, deviceDrivers.txt,
driverSets.txt and serviceSets.txt are involved.
LTU
The LTU config follow Dublin solution, but new chip LMK04832 used.
Consist of two stage configuration from SW point of view,
The first step initialization sequence ‘0initCont’ in XCS SW for

initializing LTU in early phase (Output request clock to PL.)
SW programs LTU configuration and SW LTU PLL supervision.
The initialize sequence flow shows bellow.
Associated init sequence should be provided by HW, like “0initCont” in

uboot, “pllFreeRunningSeq” for free run, “pllExternalRefSeq” for
external ref clk, .etc. PLL locked status indicated by FPGA GPIO.
/810/gpioFpga/indicator#LtuFreqLock:0 char "0:xx"

/*LTU_STATUS_LD2*/
Palau
Architecture description
Ericsson Internal

2023-12-21 PF24
Radio 6626 using two TRX-ASICs support dual band 6T6R product.
The chip offers eight transmitters, two observation receivers for
monitoring transmitter channels, eight receivers, integrated LO and
clock synthesizers, and digital signal processing functions. One
Radon1.1 connect with two chips’ TRX-ASIC through JESD204C
interface. An overview refer to chapter 8.15.2 branch mapping.
The device driver DeviceImplPalau for the Tokelau transceiver will be

used. Which is introduced in MTB pre-dev project and refactoring to a
new architecture by splitting the TRX ASIC drivers into small function
blocks. A function block is basically a software representation of a
physical block inside the component. Common resources like SPI
access and various mutexes are created once at startup and are then
passed on to each function block. The Device function block is the
entry point of the TRX ASIC driver in the new framework. It is started
by the Radio SW driver framework. An overview shows in Figure
8.15.3.1.5.1-1.
Figure 8.15.3.1.5.1-1 Driver Overview
Interface description
SPI Slave
A new function block TrxAsicSpiAccessPalau for the SPI access to the

new Palau transceiver (ADI ADRV903X) should be created. And
associated SPI paraments defined in database, like hubCs, hubPort,
masterTag .etc.
Device
This is the entry point for controlling the entire device. Responsible for
creating and registering whole function block instances into
DrvFactory. Also itself contains methods of,
Reset – Reboots the entire device

Ericsson Internal

2023-12-21 PF24
LoadAndInit – Run the entire initialize sequence across all function

blocks
During initialize phase, four kind of binary files needed.
Firmware binary for dual core embedded ARM processors. Delivered

by supplier ADI.
Stream binary is a stream for co-processor which is mainly used for

setting up and managing the transmit / receive chains on occurrence
of certain events, such as transmit / receive enable. Generated by
ACE tool, with .jason config file.
Profile binary consists of the ADRV903x configuration generated for a

particular use case in binary format. Generated by ACE tool,
with .jason config file.
RX gain table. The front end gain look up tables for the ADRV903x
receiver. Generated by ACE tool, with .jason config file.
Gain
The gain blocks are used to adjust the signal level. And be controlled
by service layer according HALI1 interface called RawValueControl.
Add database definitions for TX/RX/TOR Gain, like bellow,

/810/id_transceiver_4.0.0/trxTxGain:0.0/rawValueControl#TxGain:Br0 char "GAININDEX,0" /* TX_GAIN1 */
/810/id_transceiver_4.0.0/trxTorGain:0.0/rawValueControl#TorAttenuation:Br0 char "GAININDEX,0" /* TOR_GAIN1 */
/810/id_transceiver_4.0.0/trxRxGain:0.0/rawValueControl#RxGain:Br0 char "GAININDEX,0" /* GAIN_RX1 */
Filter Branch
Filter branch function blocks offer function of enable/disable,

initialization calibration and autonomous calibration. The capability for
TX/RX/TOR filter branch is in table bellow.
Filter Branch Init Cal Tracking
TX Follow RX do QEC
initialize calc
RX TRX_IF_TX_BB N/A
_FILTER
TRX_IF_TX_DA
C
TRX_IF_ADC_T
UNER
TRX_IF_RX_DC
_OFFSET
TRX_IF_IC_TXL
B_FILTER
TRX_IF_TX_QE
Ericsson Internal

2023-12-21 PF24
C_INIT
TRX_IF_EXTER
NAL_PATH_DE
LAY
TOR TRX_IF_ORX_T N/A

IA
TRX_IF_ORX_
DC_OFFSET
TRX_IF_ORX_L
O_DELAY
TRX_IF_ORX_
QEC_INIT
TRX_IF_ADC_T
UNER
JESD
Reuse systemize common JESD interfaces from AIR6449

Jesd204::AllLayersDeviceIf, Jesd204::AllLayersTxLinkIf and
Jesd204::AllLayersRxLinkIf. Driver
jesd204AllLayersDevicePalau/jesd204AllLayersTxLinkPalau/jesd204A
llLayersTxLinkPalau are the concreate implementation for this kind of
interface.
PLL
The Pll interface is used to set the PLL frequency and check status
(locked /unlocked ) of a PLL. Palau has two RF PLLs. But not used.
Radio 6626 using an external LO source.
Temperature Sensor
This interface is defined to read the temperature from the sensor.

/810/id_transceiver_4.0.0/trxTemp:x.x/type char "TemperatureSensorPalau"
GPIO
Debug purpose for Palau GPIO config.

/810/id_transceiver_4.0.0/trxGpio:x.x/type char "GPIOPalau"
PA Protection
Palau has two Power Amplifier (PA) protection blocks, a peak power
block and an average power block. They can be used individually or in
parallel. These blocks can monitor the signal at the output of the QEC
correction block or at the input to the digital attenuation block.
/id_prdType_1.1.x/trxPaProtection:x.x/tx0papCfg U32
Ericsson Internal

2023-12-21 PF24
0, /*ADI_ADRV903X_HB1_OUTPUT = 0x0000, ADI_ADRV903X_TXQEC_ACTUATOR_OUTPUT =

0x0001*/
0xFFFF, /*Power monitor peak power threshold. Peak Threshold[dBFS] = 10 *

Log10(peakThreshold/65535)*/
10, /*Power monitor peak and avg power measurement duration: Duration =
2^(measDuration + 7) number of cycles. Valid range [0-15]*/
14, /*Peak count causing peak power error.*/
1, /*Set this to make the peak power error sticky. When set, user needs to
call adi_adrv903x_TxProtectionErrorClear to clear peak power error*/
1, /*This enables peak power measurement block. 1 = Peak power error is

flagged when peak count is above peak count threshold, 0 = disabled*/
1, /*1 = enables peak power error interrupt, 0 = no IRQ*/
0x203B, /*Power monitor average power threshold. Average Threshold[dBFS] = 10

* Log10(avgThreshold/65535)*/
1, /*Set this to make the average power error sticky. When set, user needs to
call adi_adrv903x_TxProtectionErrorClear to clear average power error*/
1, /*This enables average power measurement block. 1 = PA error is flagged

when average power measurement is above average power threshold, 0 =
disabled*/
1, /*1 = enables average power error interrupt, 0 = no IRQ*/
1 /*1 = enables average to peak power ratio calculation block, both avgPower
and peakPower calculations must be enabled before enabling ratio calculation,
0 = disabled*/
/id_prdType_1.1.x/trxPaProtection:x.x/type char "PaProtectionImplPalau"
/id_prdType_1.1.x/trxPaProtection:x.x/papEnable U8 0 /*valid for legacy

format. palau use new format to configure pap*/
/id_prdType_1.1.x/trxPaProtection:x.0/txChannelMask U32 0xFF
/id_prdType_1.1.x/trxPaProtection:x.1/txChannelMask U32 0x0F
/id_prdType_1.1.x/trxPaProtection:x.x/tx1ProtectionRampCfg U32 0x80,0

been assigned for this radio.MR9002-SP4 will follow platform design,
new trxlcSw_1_4_Palau.txt of external database file related with
prdTypeID need to be added.
The related DB items with prdType ID of trxlcSw_1_4_Palau.txt all

need to add a set of DB with ‘/id_prdType_1.4.x’ in the new external.
When JESD 204C link error/Deframer error occurs, Palau GP_INT

signal is assert and ramp down function would be triggered. The
GP_INT signal is made sticky, once JESD link is recovered, requiring
user intervention to de-assert GP_INT and ramp up.
Ericsson Internal

2023-12-21 PF24
One of Visby platform Radio 6626, External RF LO is used instead of

using internal LO inside Palau. So external RF LO unlock error will
also trigger PAP function. This function is also called GPIO PAP
feature.
Slew Rate Limiter
IQ samples are taken observed at one of two possible tap off points,
Tx QEC correction output and digital attenuator input. The slew result
is compared to a 16-bit threshold (srd_slew_offset[15:0]). If the result
is greater than the threshold a slew alarm is triggered. The Tx QEC
correction block is the last block in the data path which can modify the
digital data based on ADI algorithms so it may be preferable to monitor
at this point to ensure that if QEC introduced a slew event it would be
detected by the slew rate detection. Two possible methods of slew
rate correction can be used, E// special mode or general mode.
/id_prdType_1.1.x/trxSrl:x.x/tx0srlCfg U32

0x0001*/
0x4D58, /*hese bits sets the offset (threshold) for the slew. Threshold[dBFS]
= 10 * Log10(srdOffset/65535)*/
1, /*1:Enable // 0:Disable the slew rate detection block */
1, /*1:Enable // 0:Disable slew rate interrupt signal*/
11, /*HW will clear the SRD error after this wait time. Any new slew event
during the countdown period reinitializes the timer.*/
/*This counter runs at the sample rate. Wait period in cycles =

2^(autoRecoveryWaitTime + 6). Valid Range[0-15]*/
1, /*1:Enable 0:Disable auto-recovery. If enabled, HW will clear SRD error

after autoRecoveryWaitTime. If disabled,*/
/*user needs to call adi_adrv903x_TxProtectionErrorClear to clear SRD error.*/
0, /*1:Disable // 0:Enable timer when Tx off. If disabled, auto-recovery

counter is disabled when TxOn is low and during txon_wait_period.*/
1, /*1:Enable SRD statistics // 0:Disable SRD statistics. When enabled, user

can read statistics through adi_adrv903x_TxSlewRateStatisticsRead*/
0 /*0:Record the maximum slew observed. 1:Record the number of samples which
have slew above threshold.*/
/*Slew Rate Limitation configuration*/
/id_prdType_1.1.x/trxSrl:x.x/type char "SrlImplPalau"
/id_prdType_1.1.x/trxSrl:0.0/txChannelMask U32 0xFF
/id_prdType_1.1.x/trxSrl:0.1/txChannelMask U32 0x0F

Ericsson Internal

2023-12-21 PF24
/id_prdType_1.1.x/trxSrl:x.x/tx1srlCfg U32 1, 0x4D58, 1, 1, 11, 1, 0, 1, 0


AI ADC
Reuse Oslo solution, device Ad93681 is used for dual band VSWR
measurement. Driver code is ready and mature. Database need to be
updated.
SPI timing parameter
Init sequence reuse legacy
AiRfFreqLock and AiClkSynthLock for supervision.
UCD3138128A
Two DCDC chip used in 6626 and offers a digital power controller. SW
should provide SPI communication and regarding configuration
towards power control micro. Each chips has different function scope
and separate supervision channel. RSW should create corresponding
config or supervision driver for each channel.
Ericsson Internal

2023-12-21 PF24
PACC
Radio6626 will reuse PACC chip AD7298 and AMC7834, both these
two chips have legacy driver code. In board parameter, there are
“componentConfigId” to distinguish different chip. And we need to
update database to mapping PACC and antenna branch.
StepATT and VVA
The StepATT is located in Arcadia for Visby 6626. The VVA is located
in Palau.
For StepATT, RadioSW control it when power level is changed. Visby

3228 follows the same solution in Dublin product. The services is
already implemented in class TxStepAttSrvGlitchFree. Some
databases may be updated accordingly.
For VVA, TrxCtrl will control it to do power control. The service part is
implemented in Txl. They need to take care of ramping step and
tuning step of VVA. The driver part is implemented in RadioSW. Visby
6626 follows the same solution in Dublin products.
For MR9002-SP4, the VVA relative database should add, can use the
new prdTypeID (‘id_prdType_1.4.0’) to distinguish with platform radio.
The following databases need to be added into deviceDrivers.txt,
/810/id_prdType_1.4.x/txVva:1/initSeq U32 0x000081, /* SOFT RESET
= 1 */
0x000100, /* Streaming
mode, read back from active register */
0x000200, /* Power mode

= normal operation */
0x00107F, /* VVA DAC

*/
0x001116, /* DSA
control */
0x000F01 /* Transfer
buffer to active registers */
Ericsson Internal

2023-12-21 PF24

= 1 */


*/
0x001116, /* DSA
control */
buffer to active registers
/810/id_prdType_1.4.x/txVva:1/type
/810/id_prdType_1.4.x/txVva:1/toggleSDO
Acadia and AC DSA
Acadia is include VVA and DSA, SW mapping VVA and DSA to

txAttenuation and txGain , chip driver reuse Adl631xDevice. Channel
No 0 is operate VVA, channel No 1 is operate DSA.
AC DSA is reuse IDTF1951 Digital Attenuator, it mapping to

TxAcAttenuation. Reuse SingleChannelSpiDevice driver. SPI
configure need change base on HW IWD.
Over temperature handling in TX
Over temperature handing function reuse Olso solution, SW select

and collect temperature sensor values, perform TempHandingState
control and calculate the temperature values. Coordinate Back-off
Power.
Create service overTempSrv for 12 branches radio 6626.
Define the temperature sensor check point per branch.

/id_prdType_1.1.x/pa[A~L]/tempSensors char "TMpa:0 TMpa:1
TMpa:2 TMpa:3 TMpa:4 TMpa:5 TMpa:6 TMpa:7 TMpa:8 TMpa:9
TMpa:10 TMpa:11 TDpa:0 TDpa:1 TDpa:2 TDpa:3 TDpa:4 TDpa:5
TDpa:6 TDpa:7 TDpa:8 TDpa:9 TDpa:10 TDpa:11 fpgaTemp
draTemperature"
No support for external back-off
The temperature sensor check point may change for MR9002-SP4,

depended on HW’s finally decision. Then in SP4, it needs to add new
database using new prdTypeID(‘id_prdType_1.4.0’). The following
databases need to be added into deviceDrivers,
Ericsson Internal

2023-12-21 PF24
/810/id_prdType_1.4.x/supDrivers/drivers
Frequency handling in TX
The frequency handling in TX includes configuration of TX RF LO, TX

ADC NCO in Palau and NCO in Radon. The TX RF LO and TX ADC
NCO are static, which is configured when RadioSW startup. The TX
ADC NCO in Palau is configured when loading Palau firmware.
RadioSW should configure NCO in Radon according to current carrier
configuration. Because the TX ADC NCO in Palau is different for Band
I and Band III, the source code of setting NCO in Radon need to be
updated accordingly.
For LO service, we add new service TxLoSrv81 for visby 6626.
actually, txLoFreq is exactly the center frequency of band.
The txLoFreq will be saved in ResourceHandler::TxLoFrequencyData

and be used by Ncosrv and Txlsrv.
Legacy service NcoSrv7 is used for visby 6626
New TorLoSrv81 service is used by visby 6626.
/id_prdType_1.1.0/BandI/torLoFreq S32 2140000
/id_prdType_1.1.0/BandIII/torLoFreq S32 1842500
/*frequency offset between torLo and txLo*/
/id_prdType_1.1.0/tx/torLo/BandI/freqOffset S32 0
/id_prdType_1.1.0/tx/torLo/BandIII/freqOffset S32 0
Frequency handling in TX for FDD radio 4466 B1B3B7
For B1B3 on FDD Radio 4466, it follows LO setting of radio6626.
For B7 on FDD Radio 4466, RF LO use the internal LO in

Palau instead of TRX shared LO and the frequency is 2655.24M. we
can reuse TxLoSrv81 to do some adaption.
Frequency handling in TX for FDD radio 4456 B1CB3JB75C
For B1CB3J on FDD Radio 4456, it follows LO setting in radio6626
For B75C on FDD Radio 4456, RF LO use the internal LO in Palau

instead of TRX shared LO.
The frequency is 1462.00 MHz
Frequency handling in TX for FDD radio 6626 B8B20

Ericsson Internal

2023-12-21 PF24
For B8B20 on FDD Radio 6626, RF LO use the external LO and the
frequency is 997.5M. The tor LO is 942.5M for B8 and 806M for B20.
we can reuse TxLoSrv81 to do some adaption.

New txSwDb_1_4.txt of external database file related with prdTypeID
need to be added.
The related DB items with prdType ID of txSwDb_1_4.txt all need to

add a set of DB with ‘/id_prdType_1.4.x’ in the new external.
/id_prdType_1.4.x/BandVIII/torLoFreq S32 942500
/id_prdType_1.4.x/BandXX/torLoFreq S32 806000
/id_prdType_1.4.x/tx/torLo/BandVIII/freqOffset S32 0
/id_prdType_1.4.x/tx/torLo/BandXX/freqOffset S32 0
Power saving in TX
TX Clock Configuration
The TX Clock Configuration on Radon based radio products is already

implemented in service class ClkCtrlSrvAasR1x and driver class
DlClkCtrlImplRadon, which enable or disable clock configuration in DL-
FBG. The clocks in DL-MCB and DL-LB-ALG are enabled by default in DB
/radon:x/initSeq. Radio 6626 can reuse the existing service and drivers.
Need to check the DB setting for dynamic power saving:

/* 0 Disable DPS, 1 Enable DPS */
/powerSaveCtrlDfeDpsTxEnable
/* 0 FbufOrEvc, 1 Evc, 2 FBuf, 3 FBufAndEvc */
/powerSaveCtrlDfeDpsTxCtrl
TX HW Component Power Save
Until now, there is no Radio product enable the TX HW component power

save function, that’s the following objects of class TxPowerSaveCtrl are not
added into any /txServices:
/tx/txPowerSaveCtrl/type char "TxPowerSaveCtrl"
/tx/txPowerSaveCtrl_2tx/type char "TxPowerSaveCtrl"

Ericsson Internal

2023-12-21 PF24
In the beginning, the TX HW component power save function on Visby 6626

will be disabled. The candidate TX HW component for power save is
TXLOW. If Visby 6626 need to enable those TX HW component power save
function, the Radio SW code is ready, but some databases should be updated
accordingly.
/id_prdType_1.1.x/powerSaveCtrlTxEnable U8 1
/id_prdType_1.1.x/powerSaveCtrlBoardTxPwrDwn char "TXLOW"
/id_prdType_1.1.x/powerSaveCtrlTxPwrDwn char "TXLOW"
MR9002-SP4 will follow platform design, New sysDataParam_1_4.txt

of external database file which related with prdTypeID need to be
added.
The following databases need to be added in the new external

database file sysDataParam_1_4.txt.
/id_prdType_1.4.x/ powerSaveCtrlBoardTxPwrDwn char "TXLOW"
/id_prdType_1.4.x/ powerSaveCtrlTxPwrDwn char "TXLOW"
Symbol Based Power Saving (SBPS)
Follow solution on Dublin product.. The RadioSW code is ready in class

SbpsSrvRadon1x, which is used in Radon based radios.
DL Amplification
PAVDD sharing, The PAVDD is shared by 4 branches.
TOR sharing, from HW aspect, radio 6626 will use two Palau chip, and
support 12 MCB branch. For first Palau, TX0-TX7 will be used. And
TX0-TX3 will be used in second Palau. TOR HW link is shared for 4
branches, totally 4*3 =12 branches. The database
“/tx/torLoSrv7_4tx/txBranchId” should be updated
Frequency handling in RX
Ericsson Internal

2023-12-21 PF24
The frequency handling in RX include configuration of RX RF LO, RX

ADC NCO in Palau and NCO in Radon. The RX RF LO and RX ADC
NCO are static, which is configured when RadioSW startup. The RX
configuration. Because the RX ADC NCO in Palau is different for Band
For rx LO service, we add new service RxLoSrv81 for visby 6626. The
following database serves RxLoSrv8.
The rxLoFreq will be used by NCO and FreqHop service
New RxNcoSrv81 service is used for visby 6626
Frequency handling in RX for 4466
For B7 on FDD Radio 4466, rx RF LO use the internal LO and NCO in

Palau instead of trx shared LO. we can reuse RxLoSrv81 to do some
adaption.
Frequency handling in RX for MR9002-SP4
For MR9002-SP4, the frequency handling will follow platform using

external LO, and can use the same RXLOSrv as platform. new
prdType ID is needed. ‘/id_prdType_1.4.x’ has been assigned for this
radio.MR9002-SP4 will follow platform design, New txSwDb_1_4.txt of
external database file related with prdTypeID need to be added.

/* External Lo */
/id_prdType_1.4.x/txRxRfLo/initFreq U32 997500
/*RX NCO in Palau*/
/id_prdType_1.4.x/rx/rxIfLo/BandVIII/initFreq S32 100000
/id_prdType_1.4.x/rx/rxIfLo/BandXX/initFreq S32 150500
Power saving in RX
RX Clock Configuration
Ericsson Internal

2023-12-21 PF24
The RX Clock Configuration on Radon based radio products is already

implemented in service class Rx::ClkCtrlServiceR1x and driver class
UlClkCtrlV4ImplRadon, which enable or disable clock configuration in UL-
MCB and UL-FBG. Radio 6626 can reuse the existing service and drivers.

/powerSaveCtrlDfeDpsRxEnable
/* 0 Tdd_antCal_N_DPS_CTRL, 1 DPS_CTRL */
/powerSaveCtrlDfeDpsRxOperMode
/* 0 - Heterodyne SDC, 1 - Homodyne */
/ul/downConversionType
RX HW Component Power Save
Different Radio products use different TX HW component power save, that’s

the following objects of class Rx::PowerSaveCtrl are added into /rxServices:
/810/rx/powerSaveCtrl/type char "Rx::PowerSaveCtrl"
At first, the RX HW component power save function on Olso products will

be followed by Visby 6626. The candidate RX HW component for power
save is RFMIXER, RX_BE_SOC and LNA. If Visby 6626 need to enable
those RX HW component power save function, the Radio SW code is ready,
but some databases should be updated accordingly.
/id_prdType_1.1.x/powerSaveCtrlRxEnable U8 1
/id_prdType_1.1.x/powerSaveCtrlBoardRxPwrDwn char "RFMIXER LNA

RX_BE_SOC"
/id_prdType_1.1.x/powerSaveCtrlRxPwrDwn char "RFMIXER LNA

RX_BE_SOC"

of external database file related with prdTypeID need to be added.


RX_BE_SOC"
Ericsson Internal

2023-12-21 PF24

RX_BE_SOC"
RX Gain handling
For Visby RU6626 B1 B3 radio, there will be 12 RX Branches (6 for

each band) and 6 RfPorts, each combining 2 branches of different
bands (delta of these bands should not be obvious) or the same band,
6 dual branch RALF are needed to handle the Rx Gain.
The Rx Front-End solution follows Dual Band Oslo, about the details
you can refer : 155 19-ROZ 104 7014 Uen
New requirements and dependencies:
Oslo used xenon, now we used Radon1.1 , so the SPI map will be
different.
There will be 6 RALFs, has two kinds of sources: IDT F0443(control

handle is same with IDT F0442, and the componentConfigId is
rxRfVga_1.3.0) and Qorvo QPB9346, branch mapping needed.
Qpb9346Device initSeq.
Update rxCalibration.txt (external DB)
componentConfigId : eg . rxRfVga@0_2.0.0
IF AGC 6db DSA located in Palau in front of the ADC, RF AGC follows
Olso. RX AGC: RALF DSA1_6db, RALF DSA3_18db, Palau DSA_6db
Power drop handling for two DC power feed
How to distinguish which cables is dropped.

Ericsson Internal

2023-12-21 PF24
The radon has two signals source for N48_OK, corresponding to two
cable power drop detection.
FPGA responsible for capturing and generating MISC_IRQ interrupts.
RSW received 48V alarm via UioInterruptHelper and forward to

powerDrop client for alarm handling.
Two powerDrop client to handle different cable power drop event.
Three types of MISC_IRQ interrupts for each cable.

POWER_FAILURE_48V_ALARM_100US_EVENT
POWER_FAILURE_48V_ALARM_10MS_EVENT
POWER_FAILURE_48V_ALARM_10MS_CEASE_EVENT
Handling of Power Feed 1 48V_lost > power hold up time (New

handling)
48V_OK_1 to radon EVC block and start the behaviors to shut down
PA, add event to EVC database.
Based on rfPort and branch mapping. 4*PAX need to turn off.

Ericsson Internal

2023-12-21 PF24
Handling of Power Feed 1 48V_lost > CPU hold up time (New

handling)
New fault RF_POWER_LOSS_PARTIAL_PORT, this just the Radio

internal fault, for the reporting fault to DU still under discussion.
Handling of Power Feed 1 48V_recover (New handling)

Ericsson Internal

2023-12-21 PF24
Handling of Power Feed 2 48V_lost > power hold up time (Follow

Dublin)
RICR CPRI INBAND inform BB PFA, no use RSW report fault, the
POWER_SUPPL_48V_NOT_AVAIL_2 is just radio internal fault, uesd
for fault suppress handling.
Ericsson Internal

2023-12-21 PF24
Handling of Power Feed 2 48V_lost > CPU hold up time (Follow

Dublin)
Handling of Power Feed 2 48V_recover (Follow Dublin)
Power Drop on Mongoose

Ericsson Internal

2023-12-21 PF24
Mongoose
POR Reset Radon
SXP
RST GEN
PA_CTRL EVC/LNA PA
protection
EVC
SW
Inform SW and record reset cause
Glich
filter
-48V_OK_0(M) -48V_OK_1(S)
Primary power drop is connect to PA_CTRL of radon to protect PA,

meanwhile connect to mongoose RST_GEN, when primary power
drops, mongoose will generate interrupt to inform SW, then SW will
follow the procedure of 6626 primary power drop procedure.
For secondary power drop, because there’s no PL in mongoose, so

when secondary power drop happens, mongoose cannot inform SW
like ZU4 done, so there’s one difference between 6626 secondary
power drops and 4466 secondary power drops. secondary power drop
for 4466 is connect to Radon EvC GPIO to protect PA, do not need to
connect back to mongoose like 6626 does. 100us glitch filter will be
done by digital, when power drop timer longer than glitch timer, radon
GPIO will generate interrupt to RSW to raise alarm to DU.
4456 B1CB3JB75C
4456 DCDC HW Base design is 4466 B1B3B40, One DC connector is

used,1 input stage PIX is removed except some capacitors and one
AUX converter, 3 PAVDDs are used. But still use two UDC devices
and has the same interrupt signal connection.
This change will impact Radio SW code and internal database.
JESD204C link handling
JESD204C link supervision is implemented in the service layer. The

supervision services are polling the status of the JESD link (using
HALI-1), raising a fault if an error is detected on the link. New solution
is grouping all lanes/links used for a TRX device (both ADC links and
DAC links) into a JesdLinkGroup. First time implemented in AIR6449.
Reuse the same solution. But add driver implementation for 6626. An
overview shows in Figure 8.15.12-1.
Ericsson Internal

2023-12-21 PF24
<<Service>>
txBrFaultAdvisor_12tx
+ onSvSrFault ()
+ onFaultRaised()
+ onFaultCeased()
Create Create
<<Sub-Service>> <<Sub-Service>>
jesdGroupSvSrv:0 jesdGroupSvSrv:1
+ subscribeOnFault() + subscribeOnFault()
Create Create
jesdGroupSv:0 jesdGroupSv:1
+ start() + start()
+ subscribeOnStatus() + subscribeOnStatus()
+ subscribeSuspendAndMute() + subscribeSuspendAndMute()
+ subscribeUnmuteAndResume() + subscribeUnmuteAndResume()
Use Use
<<StereoType>> <<Block Interface>>

Jesd204BCHelperBase jesd204CLinkGroupV1
+ getStatus() + getStatus()
+ setup() + setup()
+ clearErrorCounters() + clearErrorCounters()
Extend
Implement
<<StereoType>>
<<StereoType>>
Jesd204CHelper
Refer to Jesd204CLinkGroupV1ImplV1
+ getStatus()
+ setup()
+ clearErrorCounters()
Use
Use Use Use Use Use
<<Interface>>
LtuSysrefIf
+ sysrefCommand()
<<Interface>> <<Interface>> <<Interface>> <<Interface>> <<Interface>> <<Interface>>

AllLayersDeviceIf AllLayersTxLinkIf AllLayersRxLinkIf ProtocolLayersRxLinkIf ProtocolLayersTxLinkIf PhysicalLayerDuplexLaneIf
+ allLayersDeviceAlignClocksToSysref() + allLayersTxLinkStart() + allLayersRxLinkStart() + protocolLayersRxLinkAlignClkToSysref() + protocolLayersTxLinkAlignClkToSysref() + physicalLayerDuplexLaneEnable()

+ allLayersDeviceClearErrorCounters() + allLayersTxLinkGetStatus() + allLayersRxLinkGetStatus() + protocolLayersRxLinkGetStatus() + protocolLayersTxLinkGetStatus()
Implement
Implement Implement Implement Implement Implement
<<StereoType>>
<<StereoType>> <<StereoType>> <<StereoType>> <<StereoType>>
HS32GCF08
jesd204AllLayersDevicePalau jesd204AllLayersTxLinkPalau jesd204AllLayersRxLinkPalau RadonJesd
Figure 8.15.12-1 JESD Architecture Overview
User case,
IBW TX RX FB LO
Component xTxRxFxLO [MHz]

FDD/TDD mode
DAC SCLK JESD JESD JESD
Bits Data-rate[Msps]
Lane rate[Gsps] Bits ADC SCLK[MHz]
Data-rate[Msps]
Lane rate[Gbps] Bits ADC SCLK[MHz][3]
Data-rate[Msps]
Lane rate[Gsps] Mode
[MHz] LMFS LMFS LMFS
Palau 1#
8T8R2F1LO FDD 60/75 16 2949.12 491.52 16.22016 8 16 4 1 16 2949.12 245.76 16.22016 4 16 8 1 16 5898.24 491.52 16.22016 2441 1xLO, sta
B1+B3
Palau 2#
4T4R1F1LO FDD 60/75 16 2949.12 491.52 16.22016 4841 16 2949.12 245.76 16.22016 2881 16 5898.24 491.52 16.22016 1241 1xLO, sta
B1+B3
In Radio 6626 we have two TRX ASIC components. The consequence

is two JesdLinkGroup instance created for supervision. Each group
consist of three links, one "Downlink" JESD link, one "Uplink" JESD
link and "TOR" JESD link. The configuration for each group is,
jesd204Group0:
/810/id_transceiver_4.0.0/jesd204Group:x.0/links U8 0, 1, 2
/810/id_transceiver_4.0.0/jesd204Group:x.0/link0/link char "LT radon:x 0 PT radonSerdes:0 0 1 2 3 4 5 6 7 LR

trxAsicJesdAllLayersRxLink:x.0 0"
/810/id_transceiver_4.0.0/jesd204Group:x.0/link1/link char "LT trxAsicJesdAllLayersTxLink:x.0 0 PR radonSerdes:0 0 1 2 3

LR radon:x 0"
/810/id_transceiver_4.0.0/jesd204Group:x.0/link2/link char "LT trxAsicJesdAllLayersTxLink:x.0 1 PR radonSerdes:0 4 5 LR

radon:x 1"
jesd204Group1:
Ericsson Internal

2023-12-21 PF24
/810/id_transceiver_4.0.0/jesd204Group:x.1/link0/link char "LT radon:x 1 PT radonSerdes:1 0 1 2 3 LR

trxAsicJesdAllLayersRxLink:x.1 0"
/810/id_transceiver_4.0.0/jesd204Group:x.1/link1/link char "LT trxAsicJesdAllLayersTxLink:x.1 0 PR radonSerdes:1 0 1 2 3

LR radon:x 1"
/810/id_transceiver_4.0.0/jesd204Group:x.1/link2/link char "LT trxAsicJesdAllLayersTxLink:x.1 1 PR radonSerdes:1 4 LR

radon:x 1"
Fault report. New fault ID added for FDD product (first classic FDD
product to employ JESD link group supervision).
TX_FDD_JESD_LOST_X = 1287,
TOR_FDD_JESD_LOST_X = 1288,
RX_FDD_JESD_LOST_X = 1289,
Power back-off for insufficient power supply
Because has two DC feeds, so RSW need handle power back off
separately.
Will have different batterySupplyMode parameter for each DC feeder.
Need 2 sets of DB in paSwDb (external DB), like backoffThreshold,

recoveryThreshold, recoveryHoldOffTime, monitorCurrentInterval,
normalAttenuation and powerBackoffStepSize.
/batterySupplyMode/powerBackoffEnable U8 1 /* 0 = disabled, 1 = activated */
Two OverPowerSrv in txServices. For separate branch group control.

Create service OverPowerMultiSrv inherit from OverPowerSrv.
Current sensor for insufficient power measurement, reported from

UCD.
Logging handling for single/dual power cable failure
The detail information still under discussion with system.
VSWR Measurement and Supervision
DVSWR is used and the measurement is per port and per band as
Multi-band DVSWR, AD9368 as ADC chip for
DVSWR Measurement analog-digital conversion. Algorithm follow
legacy solution.
Ai path selector need reconfigure, base on HW&FU solution. The

selector will use 3 switch bit for six antenna branches.
Supervision is no impact.
VSWR Measurement and Supervision for FDD Radio 4466
FDD Radio 4466 VSWR would use AD93681+Radon solution, the

forward channel and reflect channel in radon for VSWR is reuse
unused 4 branches in UL same as radio8863. The RTS related
configurations refer to Dublin.
Ericsson Internal

2023-12-21 PF24
Due to the limitation of the AIADC(AD93681)’s maximum support

6.1Gbps lane rate and Radon's minimum support 122.88Msps
sampling rate, radio4466 VSWR is likely to use 2 lanes to support
4.9Gbps line rate. the detail JESD configuration as below:
C
o
VSW n
R fi
JESD g
ur
Link a
Para ti
mete o
rs n
L 2
M 4
F 8
JESD
samp 1
le 2
rate 2.
(Msp 8
s) 8
4,
Bit 9
rate 1
(Mb 5.
ps) 2
To realize this feature the JESD204B configuration on Radon1.1 and

AIADC will update to support 4.9152G line data rate(8B/10B).
For radon side, MCB sampling rate input 122.88Msps and having 2x
interpolation output 245.76Msp and 8x decimation to make output data
rate in FB down to 30.72M.
Ericsson Internal

2023-12-21 PF24
Tor sharing solution
TOR sharing for DVSWR is by means of sharing the TOR ADC for
VSWR function, this solution saves dedicated ADC device (used in
legacy solution), and thus leads to cost down in Radio Unit. This
solution could be used in Visby.
In this solution, the TOR ADC sampled data should be used for both
DPD and DVSWR function. So, RF switches are needed on PCB to
connect both TOR data path and DVSWR data path to TOR ADC.
When the TOR ADC sampled data get into Radon, it should also be
routed to both LB and MCB/FB. The LB path is for traditional DPD
function, and the MCB/FB path is for DVSWR function.
For software, this solution will capture DVSWR sample data through
TOR ADC in a time-switched mode, so it’s necessary to modify DPL
software as well as DPCPRI to realize the real time control of data
path.
For SW interface, the following interfaces
DVSWR_MEAS_REQ
DVSWR_MEAS_RSP
DVSWR_MEAS_IND
Need to be added between RSW and DPCPRI.

Ericsson Internal

2023-12-21 PF24
For SW implementation, Radio Application software needs to create

two new class for DP setting and add two function in GenericRequest
class used separately to choose whether it needs DVSWR share Tor
configuration instance and set DVSWR share Tor configuration
instance for GenericRequest.
The solution will be used firstly in 4466 B1B3B7, and MR9002-SP4 will
reuse it.
Antenna port capability and services
Antenna port will support voltage and current supervision, multiband

vswr ,modem. So capability is defined：
Port dc tx rx dcSup ulGainSetting

anu modem mbvswr vswrSweep
dcSupHigh
dcCurrMeas
ACE √ √ √ √ √ √ √ √ √ √
BDF √ √ √ √ √ √
RET √ √ √
Antenna capability DB defied, /810/rf_b[A~F]/antPortCap
Service modemSharedService and antVCCSharedService need

mapping to ModemServiceNgr2 and AntVCCServiceG3.
Radon FDD support
For Radio 6626, this is the first product to support FDD in Radon ASIC
chip. And we need to update services “pa1Srv93.cc” and
“cfrSrvRadon10.cc” to support FDD.
Power Over Booking
For MR9002-SP4, Power Overbooking impact is same as the latest

decision on MR9002-SP1 from SPM. No need to support Power
Overbooking.
Basic the power over booking function follow MR5657, but this MR is
based on Xenon ASIC, exist some changes for PPL(implemented in
DP) for RADON ASIC.
ADD_CONFIG_CAPABILITY.OVERBOOKING_CONFIG_SUPPORT
= 0x0004 means that Radio support power overbooking, control by
system DB "/addConfigCapability"
Ericsson Internal

2023-12-21 PF24
When DU send DC_TRS_ADD_CONFIG_REQ.overbookingConfigs to

Radio, then Radio will set the flag MplSvr::m_powerOverBookingOn to
true, this flag has two useages:
used to Calculate the MPL available power for

carrier(MplSrv::calcPowerPoolingAvailablePwr())
Used to Get the number of limited slots ( MplSrv7::getLimitedSlots() ),

If Power overbooking service enabled, return MPL + PPL counters
(PPL counters get from DP, through sig
DIGGAINCTRLIF_READ_COUNTER_IND)
TRDCI_ACTIVE_REQ will trigger the

PowerOverBookingSrv::handleCarrierActivateRequest, to start
communicate with PPL(DP) and start a timer to sendReadCounterReq
to DP periodically.
TRDCI_DEACTIVE_REQ will trigger the

PowerOverBookingSrv::handleCarrierDeactivateRequest.
The DPS function is controlled by reporting through

DC_TR_REPORT_IND, there are two parameters will report to DU:
POWER_LIMITED_SLOT: report trigger by BFN_IRQ, so need FPGA

add this kind of IRQ
POWER_POOLING: report trigger by Tx carrier cycle state changed.
Need add new Drivers for PPL function, control by sw db "/createPPL"
Whether need add pplImplRadon need check with DP designer.
Need add the pa0V2ImplRadonPpl to write pa0Gain to DP
Antenna Port support WCDMA
Due to all antenna port support WCDMA, expand RF port E/F

compatibility for CBCI signal RRU_ANTENNA_POWER2_REQ,
RRU_CONFIG_SV2_REQ, RRU_CONFIG_POWER_SV2_REQ.
Current compatibility only support four antennal ports. Follow functions
need to adapt code to support maximum six antennal port
CbcRRu::handleRruAntennaPowerReq(SIGNAL * rec_p)
CbcRRu::handleRruConfigSvReq(SIGNAL* rec_p)
CbcRRu::handleRruConfigPowerSvReq(SIGNAL* rec_p)
DU will send six port parameters to radio 6626, radio will do

configuration based on its own RF port compatibility.
For fault handling, also need to expand the compatibility as well.

Ericsson Internal

2023-12-21 PF24
RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_ANTENN
A_BRANCH_{E|F}
RBS_FAULT_TYPE_LNA_{FAILURE|DEGRADED}
_ANTENNA_BRANCH_{E|F}
RBS_FAULT_TYPE_FEEDER_CABLE_DISCONNECTED_BRANCH
_{E|F}
FPGA
Based on current 8863 design, the high-level block diagram of the

design as below. Some interfaces marked blue are added as
requirement.
EMIO
The EMIO setting is added to 64 as below and it is no impact on

psu_init; The black part are keep the 8863 design and the red part are
added as below. Concrete info refer to DS.
Signal FPGA EMIO Nr SW GPIO Nr Direction
1 HW_ID_0 EMIO[0] 78 in
4 RADON_EXT_RSTEMIO[3] 81 in
5 ALARM_EXT1 EMIO[4] 82 in
6 ALARM_EXT2 EMIO[5] 83 in
Ericsson Internal

2023-12-21 PF24
7 EMIO[6] 84 in
8 EMIO[7] 85 in
9 EMIO[8] 86 in
10 DCDC_RESTART_CTRL
EMIO[9] 87 out
11 DC_RES_MEAS_AEMIO[10] 88 out
12 DC_RES_MEAS_BEMIO[11] 89 out
13 DC_ANT_VCC_ENEMIO[12] 90 out
14 DC_AIB_VCC_ON_N
EMIO[13] 91 out
15 SFP2_POW_EN EMIO[14] 92
16 SFP3_POW_EN EMIO[15] 93
17 LED_CPRI_2 EMIO[16] 94
18 LED_CPRI_3 EMIO[17] 95
19 SFP2_TX_DIS EMIO[18] 96
20 SFP3_TX_DIS EMIO[19] 97
21 SFP2_AVAIL_N EMIO[20] 98
22 SFP3_AVAIL_N EMIO[21] 99
23 SFP2_RX_LOS EMIO[22] 100
24 SFP3_RX_LOS EMIO[23] 101
25 GPIO_EXT_RESETEMIO[24] 102
26 AI_SW_CTRL_0 EMIO[25] 103
27 AI_SW_CTRL_1 EMIO[26] 104
28 AIB_SW_0 EMIO[27] 105
29 AIB_SW_1 EMIO[28] 106
30 AIB_SW_2 EMIO[29] 107
31 AIB_SW_3 EMIO[30] 108
32 AIB_SW_4 EMIO[31] 109
34 AIB_SW_5 EMIO[32] 110
36 AIB_SW_6 EMIO[33] 111
37 AISG_MD_SW_0 EMIO[34] 111
38 AISG_MD_SW_1 EMIO[35] 111

Ericsson Internal

2023-12-21 PF24
SPI
Three AXI SPI controllers would be used and assigned three section
separated address for them. One is assigned for AI-ADC chip, and
others are assigned to LO. It is no impact on XCS.
I2C
Two AXI I2C controllers would be used for the new SFP and also
assigned two section separated address for them. It is no impact on
XCS.
AI ADC(VSWR)
The MIB1.0 AI-ADC solution for VSWR detection would be follow.

After initial the AI ADC, SW would trigger FPGA get VSWR data by
2.5G JESD204B interface every 5s and buffer and decimate 8192
sample for 30.72M sample rate to report for SW.
Cover all Radios, inclusive Indoor (RDS).Quasi Dynamic VDD

Adjustment
This function needs DPD, TXL and RSW part. PaVddQd supervision will start
after the first carrier active.
After carrier activation is done, TXL will periodically poll peak gain values,
these values will be compared with peak gain max and min value.
peakGainLimMax and peakGainLimMin is defines in DBs.
If peakGain > peakGainLimMax the PA Vdd shall be increased,

incPaVdd()
If peakGainLimMin < peakGain < peakGainLimMax the PA Vdd shall stay

constant
If peakGain < peakGainLimMin the PA Vdd shall be decreased, decPaVdd()
TxBranchCtrl will subscribe PA Vdd action updating request from TXL. And
call PaSrvSharedNgrG2 service to store the required action for each branch.
PaSrvSharedNgrG2 service will read the paVddQdPeriod out from DBs, when
the time is out or all the Vdd update request has received from TXL,
PaSrvSharedNgrG2 will decide the final VDD offset value according to the
following rules:
Always take the worst action as the actual action for PaVdd.
Up>Hold>Down
Only when action for every branch is down, Vdd will be decreased with
one step size
Ericsson Internal

2023-12-21 PF24
If action for any one branch is up, then Vdd will be increased with one
step size
Once Vdd up/down action is done, action for each branch will be reset
as hold.
If one branch is shutdown, its action should be ignored.
TempFreqCompEngineQdVddNgrG3 will rewrite the “calculate” function,

based on temperate and frequency compensation to add the offset that
caused by QdVdd function get the final VDD value and call
CorrectionWithLimitingResource to write it.
For Visby 4466, RSW will be based on the following procedure of AAS,
paSrvShareAasX1x will be replace with PaSrvSharedNgrG2 and
TempFreqCompEngineQdVdd will be replaced with
TempFreqCompEngineQdVddNgrG3 in Visby. For DPD, no changes compare
to AAS.
Radio SW Workflow
For MR9002-SP4, will follow platform solution, database may need to

be added for this new radio. These database values may be changed
in future.
/810/paVddQdEnable U8 0
/810/paVddQdDynamicLimitEnable U8 0
Ericsson Internal

2023-12-21 PF24
/810/paVddQdPwrLimit U32 600 /*-dbfs */
/810/paVddQdParLimit U32 750 /*0.01dB*/
/810/paVddQdEvmLimit U32 0x1FFFFFFF
/810/paVddQdVoltMin S32 150 /*DAC Value */
/810/paVddQdCPRGainMax U32 550 /*0.01dB */
/810/paVddQdCPRGainMin U32 500 /*0.01dB */
Deep Sleep
Visby will refer to SP8881 (AAS G3 MB deep sleep) feature. Under

deep sleep mode, Radio will power off or reset as much as possible
component to save power. The difference is that in AAS Radio, CPRI
link is connected to EO then to Radon, but in Visby, CPRI connect to
Radon directly. So, In AAS, Radon can be reset, but in Visby, to keep
the connection between Radio and DU, we cannot reset the whole
Radon like AAS radio do. In Visby, there’s no work on RICR and XCS
side, most of the works are on RSW side.
There should have two big stage of deep sleep.
Stage one is trigger deep sleep mode by coli-command. DU can send

Moshell command radio. Radio will follow the below steps (one by
one) to enter deep sleep mode.
Stage two is to communicate with DU, four new BCI messages will
introduce:
ELIB_BC_DEEP_SLEEP_ENABLE_REQ
ELIB_BC_DEEP_SLEEP_ENABLE_CFM
ELIB_BC_DEEP_SLEEP_IND
ELIB_BC_DEEP_SLEEP_ENABLE_REJ
ELIB_BC_SUBSCRIBE_DEEP_SLEEP_REQ
ELIB_BC_SUBSCRIBE_DEEP_SLEEP_CFM
ELIB_BC_SUBSCRIBE_DEEP_SLEEP_REJ
RU report deep sleep capability by capability signal and DU client

could subscribe the deep sleep by
ELIB_BC_SUBSCRIBE_DEEP_SLEEP_REQ.
Ericsson Internal

2023-12-21 PF24
After all the client subscribe success, DU client could enable deep
sleep by ELIB_BC_DEEP_SLEEP_ENABLE_REQ.
If all the client subscribed and all the clients send the enable signals, RU
will go to deep sleep mode.
1. stop supervision
2. suppress fault
3. turn off LNA
4. turn off PA, driver, PACC, TX_LOW
5. turn off RALF
6. turn off TRXIC
7. turn off AI Receiver
Reset Method in Visby
R
e
s
e
t
M
e
t
Com h
pone o
nt d
P
A
_
R
E
S
E
T
PAC _
C 0
Ericsson Internal

2023-12-21 PF24
P
A
_
PA O
and N
drive _
r 0
T
X
_
0
…
1
1
_
R
F
TX_ _
LO O
W N
T
R
X
0
_
R
E
S
E
T
TRX _
IC N
LNA F
D
D
_
L
N
A
_
P
D
_
0
.
.
.
Ericsson Internal

2023-12-21 PF24
.
1
1
A
I
_
R
E
S
E
AI T
Rece _
iver N
R
X
_
F
E
_
I
C
_
S
T
B
Y
_
0
…
RAL 1
F 1
[7.15.2] Overview
The Radio SW for DB Radio 6626 should be developed on top of the

NGR G2/G3 based DB Radio SW. The Radio SW baseline to be used
for the Radio 6626 SW development will contain the following
components:
 NGR G2 based DB Radio SW for supporting dual-band radios

DB4442/DB4480 as well as DB4443 and DB2242.
 Reuse digital power controller UCD3138128A from Oslo.
 Palau Pre-Dev Radio SW for supporting the new transceiver

Palau.
Ericsson Internal

2023-12-21 PF24
 MTB Pre-Dev Radio SW for supporting the new ASIC Radon

1.1.
From a Radio Function and radio SW application point of view, the

Radio 6626 inherits most of its functionality from the legacy Oslo
which is multiple band platform. The TRX driver set used will be
“810”and the TPA driver set will be “810”. Mainly modification located
in services layer and drivers layer. Figure 8.15.1-1 shows an
architecture overview.
MR9002-SP4 is based on Radio 4466 MR8930-SP1(Mongoose +

radon), will use 0.8 pitch radon compared with platform
radio6626/4466. 0.8 pitch radon compared with 1.0 pitch has added
some PINs which are invisible for SW, and also no changes for the
total functions, but will use new component configuration
ID(“dra_2_1_2”) for 0.8 pitch radon, then SW need add component
related database.
MR9002-SP4 will follow platform 4466/6626 for the TRX and PA driver
set,’810’ TRX driver set and PA driver set will be used.
Figure 8.15.1-1 Architecture Overview
A new Radon 1.1 ASIC is used by the Radio 6626. Compare to Radon
1.1, CPRI cascading and JESD204C 32.44 Gbps Interface supported.
As Radon 1.1 has a new SERDES IP, a new SERDES start up and
FW load procedure is needed. In the new IP the PLL clock control is
moved from ADC_DAC_IF to SERDES. The radio SW application
needs to adapt to this driver sets change. New componentConfigId
“dra_2.1.0” used.
Ericsson Internal

2023-12-21 PF24
A new TRX transceiver Palau is used. Consist of eight transmitters,

Eight receivers and two observation receivers. Fully integrated clock
synthesizer and JESD204B/C digital interface up to 19.66/32.44 Gbps.
Driver codes employ new FW of function block implementation from
MTB pre-dev. Making the code easier to understand and maintain by
using smaller modules. New componentConfigId “transceiver_4.0.0”
used.
Radio 6626 use the JESD204C protocol as an interface between ASIC

Radon 1.1 and component Palau. Service codes employ new FW of
JESD204B/JESD204C functional systemization from AIR6449. By
grouping all lanes/links used for a TRX device into a JesdLinkGroup.
So as to reflect the limitation in Radon that transmitter and the receiver
are grouped into lanes, which cannot be operated independently.
Radio 6626 has use case of two cable feed. Radio SW need to
monitor two 48V_OK signal and handle associated new power drop
function. Also Radio SW handle the two back off for two DC
independently under insufficient power supply.
3PP SW,
Vendor SW Name(FD in Ericsson Design

Name PRIM) Product NO Countr
including y
R_STATE
Synopsi Digital R1.1 2/ US

s SerDes FW,3PP CTX1010306
SOFTWARE R1A(1.16-4)
ADI Palau, ADRV9030 CTC102767/ SE

API 1 R1A
SE
ARM FW 2 R1A SE
Palau, ADRV9030 CTC102767/ SE

Gain Tables 3 R1A
SE
GUI 4 R1A
US
Visby Radio 6626 CXC 201
Palau config 3051/2 R1A
B1+B3
1/CTX 101
ADRV903x, 0319 R1A
Analog Device Inc
FOSS Device Tree 1/CAX 105 US

Compiler 8805 R1A
SE
DTC libfdt CXS 102
7391/1 R1A
Wind WRL18 for XCS CTC 101 SE

River 6832 R1A
US
Ericsson Internal

2023-12-21 PF24
34/CAX 105
3085 R1A
Wind Customer Content CTC 101 SE

River Management 6833 R2A
(CCM), Additions US
to WRL18 for XCS 33/CAX 105
9820 R1A
Xilinx 3PP 9/CAX 105 US

SOFTWARE/Vivad 8968
o, Xilinx
5.15.1 Branch mapping
The following database parameters for the band, RfPort and branch
mappings in external sysDataParamRru6626 database file shall be
defined for DB Radio 6626:
 /Band[I|III]I/bandId
 bandId[0|1]/[dl|ul]/rfPorts
 bandId[0|1]/[dl|ul]/branches
 [ul|dl]/rfAnt[A|B|C|D|E|F]/[rx|tx]Branches
 [dl|ul][A|B|C|D|E|F]/carriers
 [dl|ul][A|B|C|D]E|F]/bandId[0|1]/carriers
 [dl|ul][A|B|C|D|E|F]/mcbNumber
 dl[A|B|C|D|E|F]/lbNumber
 ul[A|B|C|D|E|F]/adcbNumbers
 ul[A|B|C|D|E|F]/mcbsgNumber
The band, RfPort and branch mappings for 6 RfPorts solution (i.e.,
combined RfPorts for the bands) are shown in Figure 8.15.2-1 and
Figure 8.15.2-2.
Ericsson Internal

2023-12-21 PF24
3226 TX Mapping SW Branch View : Radon Port vs ANT Br

Mapping
LB Numbers: 2 *2*4=16 B3 FU IN(PA FU OUT(ANT Port,
Out) SW Br View)
Radon MCBG0 DAC_IF_0

FB00-05 MCB0 LB0 B1
MRIX_4/5 /6/7
TX1 TX6 PA6 B3 A
FB06- 11 MCB1 LB1
MRIX_8/9 /10/11
FB12- 17 MCB 2 LB2 TX2 TX5 PA5
MRIX_12/ 13/14/15
FB18- 23 MCB 3 LB3 TX3 TX3 PA3 B1
Palau_0 B3 B
CPRI 0 MCBG1 MRIX_16/ 17/18/19 TX4 TX7 PA7
FB24- 29 MCB0 LB4
ADCB0
MRIX_20/ 21/22/23 TX5 TX1 PA1 B1
FB30- 35 MCB1 LB5 B3 E
FB 36-41 MCB 2 LB6 2
ADCB
MRIX_24/ 25/26/27 TX6 TX2 PA2
MRIX_28/ 29/30/31 PA4
FB 42-47 MCB 3 TX7 TX4
CONNECT
CPRI 1 LB7 B1
F
B3
DAC_IF_1
MCBG2
FB48- 53 MCB0 LB8
MRIX_4/5 /6/7 TX1 TX2 PA10 B1
FB54- 59 MCB1 LB9 B3 C
FB60 - 65 MCB 2 LB10 MRIX_16/ 17/18/19 TX2 TX0 PA8
FB66 - 71 MCB 3 LB113
ADCB MRIX_20/ 21/22/23 TX3 TX3 PA11
B1
D
MCBG3
Palau_1 B3
FB72 - 77 MCB0 LB12

FB78 - 83 MCB1 LB13
FB84-89 MCB 2 LB14
FB90-95 MCB 3 LB15
3226 RX Mapping SW Branch View : Radon Port vs ANT Br

Mapping
ADC Numbers: 2*2*4=16 B3 FU OUT(LNA FU IN(ANT Port,
IN SW Br View)
Radon MCBG0:MCBSG0 ADC_IF_0

MRIX_0/1 /2/3 RX0 RX7 LNA0
FB00-05 MCB0 ADCB0 B1
MRIX_4/5 /6/7
RX1 RX6 LNA1 B3 A
FB06- 11 MCB1 ADCB1
MRIX_8/9 /10/11
FB12- 17 MCB 2 ADCB2 RX2 RX5 LNA10
MRIX_12/ 13/14/15
FB18- 23 MCB 3 ADCB3 RX3 RX4 LNA11 B1
Palau_0 B3 B
CPRI 0 MCBG0:MCBSG1 MRIX_16/ 17/18/19 RX4 RX0 LNA2
FB24- 29 MCB0 ADCB0
ADCB0
MRIX_20/ 21/22/23 RX5 RX1 LNA3 B1
FB30- 35 MCB1 ADCB1 B3 E
FB 36-41 MCB 2 ADCB2
ADCB 2
MRIX_24/ 25/26/27 RX6 RX2 LNA8
FB 42-47 MCB 3
MRIX_28/ 29/30/31
RX7 RX3 LNA9
CONNECT
CPRI 1 ADCB3 B1
F
B3
ADC_IF_1
MCBG1:MCBSG0 MRIX_0/1 /2/3 RX0 RX1 LNA5
FB48- 53 MCB0 ADCB0
MRIX_4/5 /6/7 RX1 RX2 LNA6 B1
FB54- 59 MCB1 ADCB1 B3 C
FB60 - 65 MCB 2 ADCB2 MRIX_16/ 17/18/19 RX2 RX0 LNA4
FB66 - 71 MCB 3 ADCB3
ADCB 3 MRIX_20/ 21/22/23 RX3 RX3 LNA7 B1
D
MCBG1:MCBSG1 Palau_1 B3

FB84-89 MCB 2 ADCB2
FB90-95 MCB 3 ADCB3
For MR9002-SP4, the band/RfPort and branch mappings solution has

some changes, below Figure 8.15.2-3 and Figure 8.15.2-4 show the
changes, and database below maybe need to be added with prdType
for the new mapping.
/810/radonJesd:x/txLink:0 U8 0, 0, 3, 1, 2, 4, 6, 5, 7 /* link resource 0
(txLink:0) from DAC_IF_0, Mapping to Palau_0 lanes 0, 1, 2, 3, 4, 5, 6, 7 */
/810/radonJesd:x/txLink:1 U8 1, 7, 4, 5, 6 /* link resource 1
(txLink:1) from DAC_IF_1, Mapping to Palau_1 lanes 7, 4, 5, 6 */
/810/radonJesd:x/rxActiveLinks U8 0, 1, 2, 3 /* Which rx links are active
for radon:x */
/810/radonJesd:x/rxLink:0 U8 0, 3, 0, 2, 1 /* link resource 0 (rxLink:0)
from ADC_IF_0, Mapping to Palau_0 lanes 0, 1, 2, 3 */
/810/radonJesd:x/rxLink:3 U8 1, 5 /* link resource 3 (rxLink:3)
from ADC_IF_1, Mapping to Palau_1 lanes 5 */
Ericsson Internal

2023-12-21 PF24
4456 44B1C 44B3J 40B75C C, the third band B75C just support TX,
do not support Rx, so Rx drivers and services for 4xB75C branches
will be removed
5.15.2 Drivers
5.15.2.1.1 TRX Driver Set
There will be a new “/board/trxDrivers/set = 810” in production DB for

Radio 6626. Based on Dublin, change list shows bellow,
subDriverNa Comment
driverName
me s
trxDri ruLtu, ltuPllSv 8.15.3.4
Ericsson Internal

2023-12-21 PF24
radonSerdes:
0
New
radonSerdes:
FW for
1
Rn1.1
radonCpriSer
des:x
radon:0
bfxTddLte0In
t:x
Add
bfxTddNr0Int
FDD
:x
driver
bfxTddNr1Int
:x
trxTransceive
parallellJobRu r:0 Two Palau
nner trxTransceive used
r:1
I2C addr
dfeFpgaSvTe
and init
mp
vers sequence
HW IWD
rxSvTemp
change.
acceleromete HW IWD
r change.
pressureSens HW IWD
or:0 change.
temperatureS HW IWD
ensor change.
Follow
Oslo. Two
dcDcDrivers:0 8.15.3.7
chips
used
2 external
rxLoDrivers:0/
8.15.5 static LO
1
chips
SRL
paPInterrupt:
interrupt
x.x
for PAP
5.15.2.1.2 PA Driver Set
There will be a new “/board/paDrivers/set = 810” in production DB

for Visby RU6626.
Ericsson Internal

2023-12-21 PF24
5.15.2.1.3 Product Type ID
New product ID prd_1.1.0 is defined in production database

/componentConfigId. The PrdTypeId may be used as a part of keys in
database to distinguish different configurations on different Radio
product. When Radio SW startup, it will get the PrdTypeId from
/componentConfigId and use it to decode databases.
For RadioSW, the PrdTypeId should be added in some databases that

have different configurations with baseline products.
For TrxCtrl, the TrxCtrl team should be notified when the new
PrdTypeId for Visby 6626 is determined. They will add it into Txl code
and DPD configurations in order to support Visby 6626 in their
releases.
For RUxTest, the RUxTest team should be notified when the new
RuTypeId for Visby 6626 is determined. They will add it into
configuration file Common/RuTypeMap.txt in order to support Visby
6626 in their release. And the local INT team should be notified
because they maybe need to update their RUxTest configuration file
by themselves.
ETSW also need to add database support and adapt code change.
Like file etswBootMode.cc.
The impact is
1. For production database /componentConfigId:
1524- need to be updated accordingly to use prd_1.1.0 to replace

ruType_x.y.z.
2. For RadioSW database:
Need to add prefix prd_1.1.0 for some new databases.
3. For RadioSW Code:
The following classes should be updated accordingly to support

prd_1.1.0 when searching databases.
class Database
class ComponentConfigID
The following interfaces between RadioSW and Txl will be updated

accordingly when initDeviceId():
txlIfRequiredCtrl.cc
4. For TrxCtrl:
Ericsson Internal

2023-12-21 PF24
TrxCtrl also check prd_1.1.0 from /componentConfigId to

determine current Radio product and use different configurations.
5. For RUxTest:
RUxTest need to support prdTypeId to recognize Radio products.

been assigned for this radio.
The related DB items with prdType ID all need to add a set of DB with
‘/id_prdType_1.4.x’ and the channels.txt, deviceDrivers.txt,
driverSets.txt and serviceSets.txt are involved.
5.15.2.1.4 LTU
The LTU config follow Dublin solution, but new chip LMK04832 used.
Consist of two stage configuration from SW point of view,
1) The first step initialization sequence ‘0initCont’ in XCS SW

for initializing LTU in early phase (Output request clock to
PL.)
2) SW programs LTU configuration and SW LTU PLL

supervision.
The initialize sequence flow shows bellow.
Associated init sequence should be provided by HW, like “0initCont” in

uboot, “pllFreeRunningSeq” for free run, “pllExternalRefSeq” for
external ref clk, .etc. PLL locked status indicated by FPGA GPIO.
Ericsson Internal

2023-12-21 PF24
/810/gpioFpga/indicator#LtuFreqLock:0 char "0:xx"

/*LTU_STATUS_LD2*/
5.15.2.1.5 Palau
5.15.2.1.5.1 Architecture description
Radio 6626 using two TRX-ASICs support dual band 6T6R product.
The chip offers eight transmitters, two observation receivers for
monitoring transmitter channels, eight receivers, integrated LO and
clock synthesizers, and digital signal processing functions. One
Radon1.1 connect with two chips’ TRX-ASIC through JESD204C
interface. An overview refer to chapter 8.15.2 branch mapping.
The device driver DeviceImplPalau for the Tokelau transceiver will be

used. Which is introduced in MTB pre-dev project and refactoring to a
new architecture by splitting the TRX ASIC drivers into small function
blocks. A function block is basically a software representation of a
physical block inside the component. Common resources like SPI
access and various mutexes are created once at startup and are then
passed on to each function block. The Device function block is the
entry point of the TRX ASIC driver in the new framework. It is started
by the Radio SW driver framework. An overview shows in Figure
8.15.3.1.5.1-1.
Figure 8.15.3.1.5.1-1 Driver Overview
5.15.2.1.5.2 Interface description
5.15.2.1.5.2.1 SPI Slave
A new function block TrxAsicSpiAccessPalau for the SPI access to the

new Palau transceiver (ADI ADRV903X) should be created. And
associated SPI paraments defined in database, like hubCs, hubPort,
masterTag .etc.
Ericsson Internal

2023-12-21 PF24
5.15.2.1.5.2.2 Device
This is the entry point for controlling the entire device. Responsible for
creating and registering whole function block instances into
DrvFactory. Also itself contains methods of,
 Reset – Reboots the entire device
 LoadAndInit – Run the entire initialize sequence across

all function blocks
During initialize phase, four kind of binary files needed.
1) Firmware binary for dual core embedded ARM

processors. Delivered by supplier ADI.
2) Stream binary is a stream for co-processor which is

mainly used for setting up and managing the transmit /
receive chains on occurrence of certain events, such
as transmit / receive enable. Generated by ACE tool,
3) Profile binary consists of the ADRV903x configuration

generated for a particular use case in binary format.
Generated by ACE tool, with .jason config file.
4) RX gain table. The front end gain look up tables for the
ADRV903x receiver. Generated by ACE tool,
5.15.2.1.5.2.3 Gain
The gain blocks are used to adjust the signal level. And be controlled
by service layer according HALI1 interface called RawValueControl.
Add database definitions for TX/RX/TOR Gain, like bellow,

/810/id_transceiver_4.0.0/trxTxGain:0.0/rawValueControl#TxGain:Br0 char "GAININDEX,0" /* TX_GAIN1 */
/810/id_transceiver_4.0.0/trxTorGain:0.0/rawValueControl#TorAttenuation:Br0 char "GAININDEX,0" /* TOR_GAIN1 */
/810/id_transceiver_4.0.0/trxRxGain:0.0/rawValueControl#RxGain:Br0 char "GAININDEX,0" /* GAIN_RX1 */
5.15.2.1.5.2.4 Filter Branch
Filter branch function blocks offer function of enable/disable,

initialization calibration and autonomous calibration. The capability for
TX/RX/TOR filter branch is in table bellow.
Filter Init Cal Tracking

Branch Cal
TX Follow RX do initialize calc QEC
RX TRX_IF_TX_BB_FILTER N/A
Ericsson Internal

2023-12-21 PF24
TRX_IF_TX_DAC
TRX_IF_ADC_TUNER
TRX_IF_RX_DC_OFFSET
TRX_IF_IC_TXLB_FILTER
TRX_IF_TX_QEC_INIT
TRX_IF_EXTERNAL_PATH_DELAY
TOR TRX_IF_ORX_TIA N/A
TRX_IF_ORX_DC_OFFSET
TRX_IF_ORX_LO_DELAY
TRX_IF_ORX_QEC_INIT
TRX_IF_ADC_TUNER
5.15.2.1.5.2.5 JESD
Reuse systemize common JESD interfaces from AIR6449

Jesd204::AllLayersDeviceIf, Jesd204::AllLayersTxLinkIf and
Jesd204::AllLayersRxLinkIf. Driver
jesd204AllLayersDevicePalau/jesd204AllLayersTxLinkPalau/jesd204A
llLayersTxLinkPalau are the concreate implementation for this kind of
interface.
5.15.2.1.5.2.6 PLL
The Pll interface is used to set the PLL frequency and check status
(locked /unlocked ) of a PLL. Palau has two RF PLLs. But not used.
Radio 6626 using an external LO source.
5.15.2.1.5.2.7 Temperature Sensor
This interface is defined to read the temperature from the sensor.

/810/id_transceiver_4.0.0/trxTemp:x.x/type char "TemperatureSensorPalau"
5.15.2.1.5.2.8 GPIO
Debug purpose for Palau GPIO config.

/810/id_transceiver_4.0.0/trxGpio:x.x/type char "GPIOPalau"
Ericsson Internal

2023-12-21 PF24
5.15.2.1.5.2.9 PA Protection
Palau has two Power Amplifier (PA) protection blocks, a peak power
block and an average power block. They can be used individually or in
parallel. These blocks can monitor the signal at the output of the QEC
correction block or at the input to the digital attenuation block.
/id_prdType_1.1.x/trxPaProtection:x.x/tx0papCfg U32
0x0001*/
0xFFFF, /*Power monitor peak power threshold. Peak Threshold[dBFS] = 10 *
Log10(peakThreshold/65535)*/
10, /*Power monitor peak and avg power measurement duration: Duration =
2^(measDuration + 7) number of cycles. Valid range [0-15]*/
14, /*Peak count causing peak power error.*/
1, /*Set this to make the peak power error sticky. When set, user needs to
call adi_adrv903x_TxProtectionErrorClear to clear peak power error*/
1, /*This enables peak power measurement block. 1 = Peak power error is
flagged when peak count is above peak count threshold, 0 = disabled*/
1, /*1 = enables peak power error interrupt, 0 = no IRQ*/
0x203B, /*Power monitor average power threshold. Average Threshold[dBFS] = 10
* Log10(avgThreshold/65535)*/
1, /*Set this to make the average power error sticky. When set, user needs to
call adi_adrv903x_TxProtectionErrorClear to clear average power error*/
1, /*This enables average power measurement block. 1 = PA error is flagged
when average power measurement is above average power threshold, 0 =
disabled*/
1, /*1 = enables average power error interrupt, 0 = no IRQ*/
1 /*1 = enables average to peak power ratio calculation block, both avgPower
and peakPower calculations must be enabled before enabling ratio calculation,
0 = disabled*/
/id_prdType_1.1.x/trxPaProtection:x.x/type char "PaProtectionImplPalau"
/id_prdType_1.1.x/trxPaProtection:x.x/papEnable U8 0 /*valid for legacy
format. palau use new format to configure pap*/
/id_prdType_1.1.x/trxPaProtection:x.0/txChannelMask U32 0xFF
/id_prdType_1.1.x/trxPaProtection:x.1/txChannelMask U32 0x0F
/id_prdType_1.1.x/trxPaProtection:x.x/tx1ProtectionRampCfg U32 0x80,0


When JESD 204C link error/Deframer error occurs, Palau GP_INT

signal is assert and ramp down function would be triggered. The
GP_INT signal is made sticky, once JESD link is recovered, requiring
user intervention to de-assert GP_INT and ramp up.
One of Visby platform Radio 6626, External RF LO is used instead of

using internal LO inside Palau. So external RF LO unlock error will
also trigger PAP function. This function is also called GPIO PAP
feature.
Ericsson Internal

2023-12-21 PF24
5.15.2.1.5.2.10 Slew Rate Limiter
IQ samples are taken observed at one of two possible tap off points,
Tx QEC correction output and digital attenuator input. The slew result
is compared to a 16-bit threshold (srd_slew_offset[15:0]). If the result
is greater than the threshold a slew alarm is triggered. The Tx QEC
correction block is the last block in the data path which can modify the
digital data based on ADI algorithms so it may be preferable to monitor
at this point to ensure that if QEC introduced a slew event it would be
detected by the slew rate detection. Two possible methods of slew
rate correction can be used, E// special mode or general mode.
/id_prdType_1.1.x/trxSrl:x.x/tx0srlCfg U32
0x0001*/
0x4D58, /*hese bits sets the offset (threshold) for the slew. Threshold[dBFS]
= 10 * Log10(srdOffset/65535)*/
1, /*1:Enable // 0:Disable the slew rate detection block */
1, /*1:Enable // 0:Disable slew rate interrupt signal*/
11, /*HW will clear the SRD error after this wait time. Any new slew event
during the countdown period reinitializes the timer.*/
/*This counter runs at the sample rate. Wait period in cycles =
2^(autoRecoveryWaitTime + 6). Valid Range[0-15]*/
1, /*1:Enable 0:Disable auto-recovery. If enabled, HW will clear SRD error
after autoRecoveryWaitTime. If disabled,*/
/*user needs to call adi_adrv903x_TxProtectionErrorClear to clear SRD error.*/
0, /*1:Disable // 0:Enable timer when Tx off. If disabled, auto-recovery
counter is disabled when TxOn is low and during txon_wait_period.*/
1, /*1:Enable SRD statistics // 0:Disable SRD statistics. When enabled, user
can read statistics through adi_adrv903x_TxSlewRateStatisticsRead*/
0 /*0:Record the maximum slew observed. 1:Record the number of samples which
have slew above threshold.*/
/*Slew Rate Limitation configuration*/
/id_prdType_1.1.x/trxSrl:x.x/type char "SrlImplPalau"
/id_prdType_1.1.x/trxSrl:0.0/txChannelMask U32 0xFF
/id_prdType_1.1.x/trxSrl:0.1/txChannelMask U32 0x0F
/id_prdType_1.1.x/trxSrl:x.x/tx1srlCfg U32 1, 0x4D58, 1, 1, 11, 1, 0, 1, 0


5.15.2.1.6 AI ADC
Reuse Oslo solution, device Ad93681 is used for dual band VSWR
measurement. Driver code is ready and mature. Database need to be
updated.
 SPI timing parameter
 Init sequence reuse legacy

Ericsson Internal

2023-12-21 PF24
 AiRfFreqLock and AiClkSynthLock for supervision.
5.15.2.1.7 UCD3138128A
Two DCDC chip used in 6626 and offers a digital power controller. SW
should provide SPI communication and regarding configuration
towards power control micro. Each chips has different function scope
and separate supervision channel. RSW should create corresponding
config or supervision driver for each channel.
5.15.2.1.8 PACC
Radio6626 will reuse PACC chip AD7298 and AMC7834, both these
two chips have legacy driver code. In board parameter, there are
“componentConfigId” to distinguish different chip. And we need to
update database to mapping PACC and antenna branch.
5.15.2.1.9 StepATT and VVA
The StepATT is located in Arcadia for Visby 6626. The VVA is located
in Palau.
Ericsson Internal

2023-12-21 PF24
For StepATT, RadioSW control it when power level is changed. Visby

3228 follows the same solution in Dublin product. The services is
already implemented in class TxStepAttSrvGlitchFree. Some
databases may be updated accordingly.
For VVA, TrxCtrl will control it to do power control. The service part is
implemented in Txl. They need to take care of ramping step and
tuning step of VVA. The driver part is implemented in RadioSW. Visby
6626 follows the same solution in Dublin products.
For MR9002-SP4, the VVA relative database should add, can use the
new prdTypeID (‘id_prdType_1.4.0’) to distinguish with platform radio.
The following databases need to be added into deviceDrivers.txt,
= 1 */
*/
0x001116, /* DSA
control */
buffer to active registers */
= 1 */
*/
0x001116, /* DSA
control */
buffer to active registers
/810/id_prdType_1.4.x/txVva:1/type
/810/id_prdType_1.4.x/txVva:1/toggleSDO
5.15.2.1.10 Acadia and AC DSA
Acadia is include VVA and DSA, SW mapping VVA and DSA to

txAttenuation and txGain , chip driver reuse Adl631xDevice. Channel
No 0 is operate VVA, channel No 1 is operate DSA.
AC DSA is reuse IDTF1951 Digital Attenuator, it mapping to

TxAcAttenuation. Reuse SingleChannelSpiDevice driver. SPI
configure need change base on HW IWD.
Ericsson Internal

2023-12-21 PF24
5.15.3 Over temperature handling in TX
Over temperature handing function reuse Olso solution, SW select

and collect temperature sensor values, perform TempHandingState
control and calculate the temperature values. Coordinate Back-off
Power.
 Create service overTempSrv for 12 branches radio 6626.
 Define the temperature sensor check point per branch.

/id_prdType_1.1.x/pa[A~L]/tempSensors char "TMpa:0
TMpa:1 TMpa:2 TMpa:3 TMpa:4 TMpa:5 TMpa:6 TMpa:7
TMpa:8 TMpa:9 TMpa:10 TMpa:11 TDpa:0 TDpa:1 TDpa:2
TDpa:3 TDpa:4 TDpa:5 TDpa:6 TDpa:7 TDpa:8 TDpa:9
TDpa:10 TDpa:11 fpgaTemp draTemperature"
 No support for external back-off
The temperature sensor check point may change for MR9002-SP4,

depended on HW’s finally decision. Then in SP4, it needs to add new
database using new prdTypeID(‘id_prdType_1.4.0’). The following
databases need to be added into deviceDrivers,
 /810/id_prdType_1.4.x/supDrivers/drivers
5.15.4 Frequency handling in TX
The frequency handling in TX includes configuration of TX RF LO, TX

ADC NCO in Palau and NCO in Radon. The TX RF LO and TX ADC
NCO are static, which is configured when RadioSW startup. The TX
configuration. Because the TX ADC NCO in Palau is different for Band
For LO service, we add new service TxLoSrv81 for visby 6626.
actually, txLoFreq is exactly the center frequency of band.
The txLoFreq will be saved in ResourceHandler::TxLoFrequencyData

and be used by Ncosrv and Txlsrv.
Legacy service NcoSrv7 is used for visby 6626
New TorLoSrv81 service is used by visby 6626.
/id_prdType_1.1.0/BandI/torLoFreq S32 2140000
/id_prdType_1.1.0/BandIII/torLoFreq S32 1842500
/*frequency offset between torLo and txLo*/

Ericsson Internal

2023-12-21 PF24
/id_prdType_1.1.0/tx/torLo/BandI/freqOffset S32 0
/id_prdType_1.1.0/tx/torLo/BandIII/freqOffset S32 0
5.15.4.1 Frequency handling in TX for FDD radio 4466 B1B3B7
For B7 on FDD Radio 4466, RF LO use the internal LO in

Palau instead of TRX shared LO and the frequency is 2655.24M. we
can reuse TxLoSrv81 to do some adaption.
5.15.4.2 Frequency handling in TX for FDD radio 4456

B1CB3JB75C
For B1CB3J on FDD Radio 4456, it follows LO setting in radio6626
For B75C on FDD Radio 4456, RF LO use the internal LO in Palau

instead of TRX shared LO.
The frequency is 1462.00 MHz
5.15.4.3 Frequency handling in TX for FDD radio 6626 B8B20
For B8B20 on FDD Radio 6626, RF LO use the external LO and the
frequency is 997.5M. The tor LO is 942.5M for B8 and 806M for B20.
we can reuse TxLoSrv81 to do some adaption.

New txSwDb_1_4.txt of external database file related with prdTypeID
need to be added.

/id_prdType_1.4.x/BandVIII/torLoFreq S32 942500
/id_prdType_1.4.x/BandXX/torLoFreq S32 806000
/id_prdType_1.4.x/tx/torLo/BandVIII/freqOffset S32 0
/id_prdType_1.4.x/tx/torLo/BandXX/freqOffset S32 0
5.15.4.4 Frequency handling in Tx for FDD radio 6626 B0AB28
For B0AB28 on FDD Radio 6626, RF LO use the external LO and the
frequency is 997.5M. The tor LO is 947.5M for B0A and 780.5M for
B28. we can reuse TxLoSrv81 to do some adaption.
Ericsson Internal

2023-12-21 PF24
For MR10135-SP1, new prdType ID is needed. ‘/id_prdType_1.10.x’

has been assigned for this radio.MR10135-1 will follow platform
design, New txSwDb_1_10.txt of external database file related with

/id_prdType_1.10.x/Band0.A/torLoFreq S32 947500
/id_prdType_1.10.x/Band28/torLoFreq S32 780500
/id_prdType_1.10.x/tx/torLo/Band0.A/freqOffset S32 0
/id_prdType_1.10.x/tx/torLo/Band28/freqOffset S32 0
5.15.5 Power saving in TX
5.15.5.1 TX Clock Configuration
The TX Clock Configuration on Radon based radio products is already

implemented in service class ClkCtrlSrvAasR1x and driver class
DlClkCtrlImplRadon, which enable or disable clock configuration in DL-
FBG. The clocks in DL-MCB and DL-LB-ALG are enabled by default in DB
/radon:x/initSeq. Radio 6626 can reuse the existing service and drivers.

/powerSaveCtrlDfeDpsTxEnable
/* 0 FbufOrEvc, 1 Evc, 2 FBuf, 3 FBufAndEvc */

/powerSaveCtrlDfeDpsTxCtrl
5.15.5.2 TX HW Component Power Save
Until now, there is no Radio product enable the TX HW component power

save function, that’s the following objects of class TxPowerSaveCtrl are not
added into any /txServices:
/tx/txPowerSaveCtrl/type char "TxPowerSaveCtrl"
In the beginning, the TX HW component power save function on Visby 6626

will be disabled. The candidate TX HW component for power save is
TXLOW. If Visby 6626 need to enable those TX HW component power save
function, the Radio SW code is ready, but some databases should be updated
accordingly.
/id_prdType_1.1.x/powerSaveCtrlBoardTxPwrDwn char "TXLOW"
/id_prdType_1.1.x/powerSaveCtrlTxPwrDwn char "TXLOW"

of external database file which related with prdTypeID need to be
added.
Ericsson Internal

2023-12-21 PF24

/id_prdType_1.4.x/ powerSaveCtrlBoardTxPwrDwn char "TXLOW"
/id_prdType_1.4.x/ powerSaveCtrlTxPwrDwn char "TXLOW"
5.15.5.3 Symbol Based Power Saving (SBPS)
Follow solution on Dublin product.. The RadioSW code is ready in class

SbpsSrvRadon1x, which is used in Radon based radios.
5.15.6 DL Amplification
PAVDD sharing, The PAVDD is shared by 4 branches.
TOR sharing, from HW aspect, radio 6626 will use two Palau chip, and
support 12 MCB branch. For first Palau, TX0-TX7 will be used. And
TX0-TX3 will be used in second Palau. TOR HW link is shared for 4
branches, totally 4*3 =12 branches. The database
“/tx/torLoSrv7_4tx/txBranchId” should be updated
5.15.7 Frequency handling in RX
The frequency handling in RX include configuration of RX RF LO, RX

ADC NCO in Palau and NCO in Radon. The RX RF LO and RX ADC
NCO are static, which is configured when RadioSW startup. The RX
configuration. Because the RX ADC NCO in Palau is different for Band
For rx LO service, we add new service RxLoSrv81 for visby 6626. The
following database serves RxLoSrv8.
The rxLoFreq will be used by NCO and FreqHop service
New RxNcoSrv81 service is used for visby 6626
5.15.7.1 Frequency handling in RX for 4466
For B7 on FDD Radio 4466, rx RF LO use the internal LO and NCO in

Palau instead of trx shared LO. we can reuse RxLoSrv81 to do some
adaption.
Ericsson Internal

2023-12-21 PF24
5.15.7.2 Frequency handling in RX for MR9002-SP4
For MR9002-SP4, the frequency handling will follow platform using

external LO, and can use the same RXLOSrv as platform. new
prdType ID is needed. ‘/id_prdType_1.4.x’ has been assigned for this
radio.MR9002-SP4 will follow platform design, New txSwDb_1_4.txt of
external database file related with prdTypeID need to be added.

/* External Lo */
/id_prdType_1.4.x/txRxRfLo/initFreq U32 997500
/*RX NCO in Palau*/
/id_prdType_1.4.x/rx/rxIfLo/BandVIII/initFreq S32 100000
/id_prdType_1.4.x/rx/rxIfLo/BandXX/initFreq S32 150500
5.15.8 Power saving in RX
5.15.8.1 RX Clock Configuration
The RX Clock Configuration on Radon based radio products is already

implemented in service class Rx::ClkCtrlServiceR1x and driver class
UlClkCtrlV4ImplRadon, which enable or disable clock configuration in UL-
MCB and UL-FBG. Radio 6626 can reuse the existing service and drivers.

/powerSaveCtrlDfeDpsRxEnable
/* 0 Tdd_antCal_N_DPS_CTRL, 1 DPS_CTRL */
/powerSaveCtrlDfeDpsRxOperMode
/* 0 - Heterodyne SDC, 1 - Homodyne */

/ul/downConversionType
5.15.8.2 RX HW Component Power Save
Different Radio products use different TX HW component power save, that’s

the following objects of class Rx::PowerSaveCtrl are added into /rxServices:
/810/rx/powerSaveCtrl/type char "Rx::PowerSaveCtrl"
At first, the RX HW component power save function on Olso products will

be followed by Visby 6626. The candidate RX HW component for power
save is RFMIXER, RX_BE_SOC and LNA. If Visby 6626 need to enable
those RX HW component power save function, the Radio SW code is ready,
but some databases should be updated accordingly.
RX_BE_SOC"
RX_BE_SOC"
Ericsson Internal

2023-12-21 PF24

of external database file related with prdTypeID need to be added.

RX_BE_SOC"
RX_BE_SOC"
5.15.9 RX Gain handling
For Visby RU6626 B1 B3 radio, there will be 12 RX Branches (6 for

each band) and 6 RfPorts, each combining 2 branches of different
bands (delta of these bands should not be obvious) or the same band,
6 dual branch RALF are needed to handle the Rx Gain.
The Rx Front-End solution follows Dual Band Oslo, about the details
you can refer : 155 19-ROZ 104 7014 Uen
New requirements and dependencies:
1. Oslo used xenon, now we used Radon1.1 , so the SPI map will be
different.
2. There will be 6 RALFs, has two kinds of sources: IDT

F0443(control handle is same with IDT F0442, and the
componentConfigId is rxRfVga_1.3.0) and Qorvo QPB9346,
branch mapping needed.
3. Qpb9346Device initSeq.
4. Update rxCalibration.txt (external DB)
5. componentConfigId : eg . rxRfVga@0_2.0.0
Ericsson Internal

2023-12-21 PF24
6. IF AGC 6db DSA located in Palau in front of the ADC, RF AGC

follows Olso. RX AGC: RALF DSA1_6db, RALF DSA3_18db,
Palau DSA_6db
5.15.10 Power drop handling for two DC power feed
5.15.10.1 How to distinguish which cables is dropped.
The radon has two signals source for N48_OK, corresponding to two
cable power drop detection.
 FPGA responsible for capturing and generating MISC_IRQ

interrupts.
 RSW received 48V alarm via UioInterruptHelper and forward to

powerDrop client for alarm handling.
 Two powerDrop client to handle different cable power drop

event.
 Three types of MISC_IRQ interrupts for each cable.

POWER_FAILURE_48V_ALARM_100US_EVENT
POWER_FAILURE_48V_ALARM_10MS_EVENT
POWER_FAILURE_48V_ALARM_10MS_CEASE_EVENT
5.15.10.2 Handling of Power Feed 1 48V_lost > power hold up time (New
handling)
48V_OK_1 to radon EVC block and start the behaviors to shut down
PA, add event to EVC database.
Based on rfPort and branch mapping. 4*PAX need to turn off.

Ericsson Internal

2023-12-21 PF24
5.15.10.3 Handling of Power Feed 1 48V_lost > CPU hold up time (New
handling)
 New fault RF_POWER_LOSS_PARTIAL_PORT, this just the

Radio internal fault, for the reporting fault to DU still under
discussion.
Ericsson Internal

2023-12-21 PF24
5.15.10.4 Handling of Power Feed 1 48V_recover (New handling)
5.15.10.5 Handling of Power Feed 2 48V_lost > power hold up time (Follow
Dublin)
 RICR CPRI INBAND inform BB PFA, no use RSW report fault,

the POWER_SUPPL_48V_NOT_AVAIL_2 is just radio internal
fault, uesd for fault suppress handling.
Ericsson Internal

2023-12-21 PF24
5.15.10.6 Handling of Power Feed 2 48V_lost > CPU hold up time (Follow
Dublin)
5.15.10.7 Handling of Power Feed 2 48V_recover (Follow Dublin)

Ericsson Internal

2023-12-21 PF24
5.15.10.8 Power Drop on Mongoose
Mongoose
POR Reset Radon
SXP
RST GEN
PA_CTRL EVC/LNA PA
protection
EVC
SW
Inform SW and record reset cause
Glich
filter
-48V_OK_0(M) -48V_OK_1(S)
Primary power drop is connect to PA_CTRL of radon to protect PA,

meanwhile connect to mongoose RST_GEN, when primary power
drops, mongoose will generate interrupt to inform SW, then SW will
follow the procedure of 6626 primary power drop procedure.
For secondary power drop, because there’s no PL in mongoose, so

when secondary power drop happens, mongoose cannot inform SW
like ZU4 done, so there’s one difference between 6626 secondary
power drops and 4466 secondary power drops. secondary power drop
for 4466 is connect to Radon EvC GPIO to protect PA, do not need to
connect back to mongoose like 6626 does. 100us glitch filter will be
done by digital, when power drop timer longer than glitch timer, radon
GPIO will generate interrupt to RSW to raise alarm to DU.
5.15.10.9 4456 B1CB3JB75C
4456 DCDC HW Base design is 4466 B1B3B40, One DC connector is

used,1 input stage PIX is removed except some capacitors and one
AUX converter, 3 PAVDDs are used. But still use two UDC devices
and has the same interrupt signal connection.
This change will impact Radio SW code and internal database.

Ericsson Internal

2023-12-21 PF24
5.15.11 JESD204C link handling
JESD204C link supervision is implemented in the service layer. The

supervision services are polling the status of the JESD link (using
HALI-1), raising a fault if an error is detected on the link. New solution
is grouping all lanes/links used for a TRX device (both ADC links and
DAC links) into a JesdLinkGroup. First time implemented in AIR6449.
Reuse the same solution. But add driver implementation for 6626. An
overview shows in Figure 8.15.12-1.
<<Service>>
txBrFaultAdvisor_12tx
+ onSvSrFault ()
+ onFaultRaised()
+ onFaultCeased()
Create Create
jesdGroupSvSrv:0 jesdGroupSvSrv:1
+ subscribeOnFault() + subscribeOnFault()
Create Create
jesdGroupSv:0 jesdGroupSv:1
+ start() + start()
+ subscribeOnStatus() + subscribeOnStatus()
+ subscribeSuspendAndMute() + subscribeSuspendAndMute()
+ subscribeUnmuteAndResume() + subscribeUnmuteAndResume()
Use Use
<<StereoType>> <<Block Interface>>

Jesd204BCHelperBase jesd204CLinkGroupV1
+ getStatus() + getStatus()
+ setup() + setup()
+ clearErrorCounters() + clearErrorCounters()
Extend
Implement
<<StereoType>>
<<StereoType>>
Jesd204CHelper
Refer to Jesd204CLinkGroupV1ImplV1
+ getStatus()
+ setup()
+ clearErrorCounters()
Use
Use Use Use Use Use
<<Interface>>
LtuSysrefIf
+ sysrefCommand()
<<Interface>> <<Interface>> <<Interface>> <<Interface>> <<Interface>> <<Interface>>

AllLayersDeviceIf AllLayersTxLinkIf AllLayersRxLinkIf ProtocolLayersRxLinkIf ProtocolLayersTxLinkIf PhysicalLayerDuplexLaneIf
+ allLayersDeviceAlignClocksToSysref() + allLayersTxLinkStart() + allLayersRxLinkStart() + protocolLayersRxLinkAlignClkToSysref() + protocolLayersTxLinkAlignClkToSysref() + physicalLayerDuplexLaneEnable()

+ allLayersDeviceClearErrorCounters() + allLayersTxLinkGetStatus() + allLayersRxLinkGetStatus() + protocolLayersRxLinkGetStatus() + protocolLayersTxLinkGetStatus()
Implement
Implement Implement Implement Implement Implement
<<StereoType>>
<<StereoType>> <<StereoType>> <<StereoType>> <<StereoType>>
HS32GCF08
jesd204AllLayersDevicePalau jesd204AllLayersTxLinkPalau jesd204AllLayersRxLinkPalau RadonJesd
Figure 8.15.12-1 JESD Architecture Overview
User case,
TX RX FB
Compon xTxRxFx FDD/TDD ADC
[MHz] Data- Lane ADC Data- Lane Data- Lane
ent LO mode DAC SCLK SCLK[
rate[Ms rate[Gsp SCLK[M rate[Ms rate[Gb rate[Ms rate[Gsp Mode
[MHz] LMFS LMFS MHz] LMFS
ps] Hz] ps] ps] ps]
[3]
Palau 1#
8T8R2F1 16.2201 16.2201 5898.2 16.2201 1xLO,
FDD 60/75 2949.12 491.52 8 16 4 1 2949.12 245.76 4 16 8 1 491.52 2441
LO static
B1+B3
Palau 2# 4T4R1F1 16.2201 16.2201 5898.2 16.2201 1xLO,
FDD 60/75 2949.12 491.52 4841 2949.12 245.76 2881 491.52 1241
B1+B3 LO static
In Radio 6626 we have two TRX ASIC components. The consequence

is two JesdLinkGroup instance created for supervision. Each group
consist of three links, one "Downlink" JESD link, one "Uplink" JESD
link and "TOR" JESD link. The configuration for each group is,
jesd204Group0:
/810/id_transceiver_4.0.0/jesd204Group:x.0/link0/link
trxAsicJesdAllLayersRxLink:x.0 0" char "LT radon:x 0 PT radonSerdes:0 0 1 2 3 4 5 6 7 LR
LR radon:x 0" char "LT trxAsicJesdAllLayersTxLink:x.0 0 PR radonSerdes:0 0 1 2 3
radon:x 1" char "LT trxAsicJesdAllLayersTxLink:x.0 1 PR radonSerdes:0 4 5 LR
Ericsson Internal

2023-12-21 PF24
jesd204Group1:
trxAsicJesdAllLayersRxLink:x.1 0" char "LT radon:x 1 PT radonSerdes:1 0 1 2 3 LR
LR radon:x 1" char "LT trxAsicJesdAllLayersTxLink:x.1 0 PR radonSerdes:1 0 1 2 3
radon:x 1" char "LT trxAsicJesdAllLayersTxLink:x.1 1 PR radonSerdes:1 4 LR
Fault report. New fault ID added for FDD product (first classic FDD
product to employ JESD link group supervision).
TX_FDD_JESD_LOST_X = 1287,
TOR_FDD_JESD_LOST_X = 1288,
RX_FDD_JESD_LOST_X = 1289,
5.15.12 Power back-off for insufficient power supply
Because has two DC feeds, so RSW need handle power back off
separately.
Will have different batterySupplyMode parameter for each DC feeder.
 Need 2 sets of DB in paSwDb (external DB), like

backoffThreshold, recoveryThreshold, recoveryHoldOffTime,
monitorCurrentInterval, normalAttenuation and
powerBackoffStepSize. /batterySupplyMode/powerBackoffEnable U8
1 /* 0 = disabled, 1 = activated */
 Two OverPowerSrv in txServices. For separate branch group
control. Create service OverPowerMultiSrv inherit from
OverPowerSrv.
 Current sensor for insufficient power measurement, reported
from UCD.
5.15.13 Logging handling for single/dual power cable failure
The detail information still under discussion with system.
5.15.14 VSWR Measurement and Supervision
DVSWR is used and the measurement is per port and per band as
Multi-band DVSWR, AD9368 as ADC chip for
DVSWR Measurement analog-digital conversion. Algorithm follow
legacy solution.
 Ai path selector need reconfigure, base on HW&FU solution.

The selector will use 3 switch bit for six antenna branches.
 Supervision is no impact.
Ericsson Internal

2023-12-21 PF24
5.15.14.1 VSWR Measurement and Supervision for FDD Radio 4466
FDD Radio 4466 VSWR would use AD93681+Radon solution, the

forward channel and reflect channel in radon for VSWR is reuse
unused 4 branches in UL same as radio8863. The RTS related
configurations refer to Dublin.
Due to the limitation of the AIADC(AD93681)’s maximum support

6.1Gbps lane rate and Radon's minimum support 122.88Msps
sampling rate, radio4466 VSWR is likely to use 2 lanes to support
4.9Gbps line rate. the detail JESD configuration as below:
VSWR JESD
Link Parameters Configuration
L 2
M 4
F 8
JESD sample rate
(Msps) 122.88
Bit rate (Mbps) 4,915.2
To realize this feature the JESD204B configuration on Radon1.1 and

AIADC will update to support 4.9152G line data rate(8B/10B).
For radon side, MCB sampling rate input 122.88Msps and having 2x
interpolation output 245.76Msp and 8x decimation to make output data
rate in FB down to 30.72M.
5.15.14.2 Tor sharing solution
TOR sharing for DVSWR is by means of sharing the TOR ADC for
VSWR function, this solution saves dedicated ADC device (used in
legacy solution), and thus leads to cost down in Radio Unit. This
solution could be used in Visby.
In this solution, the TOR ADC sampled data should be used for both
DPD and DVSWR function. So, RF switches are needed on PCB to
connect both TOR data path and DVSWR data path to TOR ADC.
When the TOR ADC sampled data get into Radon, it should also be
routed to both LB and MCB/FB. The LB path is for traditional DPD
function, and the MCB/FB path is for DVSWR function.
Ericsson Internal

2023-12-21 PF24
For software, this solution will capture DVSWR sample data through
TOR ADC in a time-switched mode, so it’s necessary to modify DPL
software as well as DPCPRI to realize the real time control of data
path.
For SW interface, the following interfaces
1. DVSWR_MEAS_REQ
2. DVSWR_MEAS_RSP
3. DVSWR_MEAS_IND
Need to be added between RSW and DPCPRI.
For SW implementation, Radio Application software needs to create

two new class for DP setting and add two function in GenericRequest
class used separately to choose whether it needs DVSWR share Tor
configuration instance and set DVSWR share Tor configuration
instance for GenericRequest.
The solution will be used firstly in 4466 B1B3B7, and MR9002-SP4 will
reuse it.
5.15.15 Antenna port capability and services
Antenna port will support voltage and current supervision, multiband

vswr ,modem. So capability is defined：
u
l
G
P a d
or i v d c
t n s c C
c S w S u
a e r u r
p t S p r
a t m m w H M
bi dc i od bv e i e
li Su n e s e g a
ty dc tx rx p g anu m wr p h s
A
C
E √ √ √ √ √ √ √ √ √ √
B
D
F √ √ √ √ √ √
R
E
T √ √ √
Ericsson Internal

2023-12-21 PF24
 Antenna capability DB defied, /810/rf_b[A~F]/antPortCap
 Service modemSharedService and antVCCSharedService need

mapping to ModemServiceNgr2 and AntVCCServiceG3.
5.15.16 Radon FDD support

For Radio 6626, this is the first product to support FDD in Radon ASIC
chip. And we need to update services “pa1Srv93.cc” and
“cfrSrvRadon10.cc” to support FDD.
5.15.17 Power Over Booking
For MR9002-SP4, Power Overbooking impact is same as the latest

decision on MR9002-SP1 from SPM. No need to support Power
Overbooking.
Basic the power over booking function follow MR5657, but this MR is
based on Xenon ASIC, exist some changes for PPL(implemented in
DP) for RADON ASIC.
1. ADD_CONFIG_CAPABILITY.OVERBOOKING_CONFI
G_SUPPORT = 0x0004 means that Radio support
power overbooking, control by system DB
"/addConfigCapability"
2. When DU send
DC_TRS_ADD_CONFIG_REQ.overbookingConfigs to
Radio, then Radio will set the flag
MplSvr::m_powerOverBookingOn to true, this flag has
two useages:
 used to Calculate the MPL available power for

carrier(MplSrv::calcPowerPoolingAvailablePwr())
 Used to Get the number of limited slots

( MplSrv7::getLimitedSlots() ), If Power overbooking
service enabled, return MPL + PPL counters (PPL
counters get from DP, through sig
DIGGAINCTRLIF_READ_COUNTER_IND)
3. TRDCI_ACTIVE_REQ will trigger the

PowerOverBookingSrv::handleCarrierActivateRequest,
to start communicate with PPL(DP) and start a timer to
sendReadCounterReq to DP periodically.
4. TRDCI_DEACTIVE_REQ will trigger the

PowerOverBookingSrv::handleCarrierDeactivateReque
st.
Ericsson Internal

2023-12-21 PF24
5. The DPS function is controlled by reporting through

DC_TR_REPORT_IND, there are two parameters will
report to DU:
 POWER_LIMITED_SLOT: report trigger by

BFN_IRQ, so need FPGA add this kind of IRQ
 POWER_POOLING: report trigger by Tx carrier cycle

state changed.
6. Need add new Drivers for PPL function, control by sw

db "/createPPL"
 Whether need add pplImplRadon need check with

DP designer.
 Need add the pa0V2ImplRadonPpl to write pa0Gain

to DP
5.15.18 Antenna Port support WCDMA
Due to all antenna port support WCDMA, expand RF port E/F

compatibility for CBCI signal RRU_ANTENNA_POWER2_REQ,
RRU_CONFIG_SV2_REQ, RRU_CONFIG_POWER_SV2_REQ.
Current compatibility only support four antennal ports. Follow functions
need to adapt code to support maximum six antennal port
 CbcRRu::handleRruAntennaPowerReq(SIGNAL * rec_p)
 CbcRRu::handleRruConfigSvReq(SIGNAL* rec_p)
 CbcRRu::handleRruConfigPowerSvReq(SIGNAL* rec_p)
DU will send six port parameters to radio 6626, radio will do

configuration based on its own RF port compatibility.
For fault handling, also need to expand the compatibility as well.
 RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_ANT
ENNA_BRANCH_{E|F}
 RBS_FAULT_TYPE_LNA_{FAILURE|DEGRADED}
_ANTENNA_BRANCH_{E|F}
 RBS_FAULT_TYPE_FEEDER_CABLE_DISCONNECTED_BRA
NCH_{E|F}
Ericsson Internal

2023-12-21 PF24
5.15.19 FPGA
Based on current 8863 design, the high-level block diagram of the

design as below. Some interfaces marked blue are added as
requirement.
1. EMIO
The EMIO setting is added to 64 as below and it is no impact on

psu_init; The black part are keep the 8863 design and the red part are
added as below. Concrete info refer to DS.
S
W
G
P
FPG I
A O Dire
EMI N ctio
Signal O Nr r n
EMI 7
1 HW_ID_0 O[0] 8 in
EMI 7
2 HW_ID_1 O[1] 9 in
EMI 8
3 HW_ID_2 O[2] 0 in
RADON_EXT_R EMI 8
4 ST O[3] 1 in
EMI 8
5 ALARM_EXT1 O[4] 2 in
EMI 8
6 ALARM_EXT2 O[5] 3 in
EMI 8
7 O[6] 4 in
EMI 8
8 O[7] 5 in
EMI 8
9 O[8] 6 in
1 DCDC_RESTAR EMI 8
0 T_CTRL O[9] 7 out
Ericsson Internal

2023-12-21 PF24
EMI
1 DC_RES_MEAS O[10 8
1 _A ] 8 out
EMI
1 DC_RES_MEAS O[11 8
2 _B ] 9 out
EMI
1 DC_ANT_VCC_ O[12 9
3 EN ] 0 out
EMI
1 DC_AIB_VCC_O O[13 9
4 N_N ] 1 out
EMI
1 SFP2_POW_EN O[14 9
5 ] 2
EMI
1 SFP3_POW_EN O[15 9
6 ] 3
EMI
1 LED_CPRI_2 O[16 9
7 ] 4
EMI
1 LED_CPRI_3 O[17 9
8 ] 5
EMI
1 SFP2_TX_DIS O[18 9
9 ] 6
EMI
2 SFP3_TX_DIS O[19 9
0 ] 7
EMI
2 SFP2_AVAIL_N O[20 9
1 ] 8
EMI
2 SFP3_AVAIL_N O[21 9
2 ] 9
EMI 1
2 SFP2_RX_LOS O[22 0
3 ] 0
EMI 1
2 SFP3_RX_LOS O[23 0
4 ] 1
EMI 1
2 GPIO_EXT_RES O[24 0
5 ET ] 2
EMI 1
2 AI_SW_CTRL_0 O[25 0
6 ] 3
EMI 1
2 AI_SW_CTRL_1 O[26 0
7 ] 4
EMI 1
2 AIB_SW_0 O[27 0
8 ] 5
EMI 1
2 AIB_SW_1 O[28 0
9 ] 6
EMI 1
3 AIB_SW_2 O[29 0
0 ] 7
EMI 1
3 AIB_SW_3 O[30 0
1 ] 8
EMI 1
3 AIB_SW_4 O[31 0
2 ] 9
EMI 1
3 AIB_SW_5 O[32 1
4 ] 0
Ericsson Internal

2023-12-21 PF24
EMI 1
3 AIB_SW_6 O[33 1
6 ] 1
EMI 1
3 AISG_MD_SW_0 O[34 1
7 ] 1
EMI 1
3 AISG_MD_SW_1 O[35 1
8 ] 1
2. SPI
Three AXI SPI controllers would be used and assigned three

section separated address for them. One is assigned for AI-ADC
chip, and others are assigned to LO. It is no impact on XCS.
3. I2C
Two AXI I2C controllers would be used for the new SFP and also
assigned two section separated address for them. It is no impact
on XCS.
4. AI ADC(VSWR)
The MIB1.0 AI-ADC solution for VSWR detection would be follow.

After initial the AI ADC, SW would trigger FPGA get VSWR data
by 2.5G JESD204B interface every 5s and buffer and decimate
8192 sample for 30.72M sample rate to report for SW.
Quasi Dynamic VDD Adjustment
This function needs DPD, TXL and RSW part. PaVddQd supervision will start
after the first carrier active.
After carrier activation is done, TXL will periodically poll peak gain values, these
values will be compared with peak gain max and min value. peakGainLimMax
and peakGainLimMin is defines in DBs.
1. If peakGain > peakGainLimMax the PA Vdd shall be increased, incPaVdd()
2. If peakGainLimMin < peakGain < peakGainLimMax the PA Vdd shall stay constant
3. If peakGain < peakGainLimMin the PA Vdd shall be decreased, decPaVdd()
TxBranchCtrl will subscribe PA Vdd action updating request from TXL. And call
PaSrvSharedNgrG2 service to store the required action for each branch.
PaSrvSharedNgrG2 service will read the paVddQdPeriod out from DBs, when
the time is out or all the Vdd update request has received from TXL,
PaSrvSharedNgrG2 will decide the final VDD offset value according to the
following rules:
Ericsson Internal

2023-12-21 PF24
1. Always take the worst action as the actual action for PaVdd.
Up>Hold>Down
2. Only when action for every branch is down, Vdd will be decreased with one
step size
3. If action for any one branch is up, then Vdd will be increased with one step
size
4. Once Vdd up/down action is done, action for each branch will be reset as
hold.
5. If one branch is shutdown, its action should be ignored.
TempFreqCompEngineQdVddNgrG3 will rewrite the “calculate” function, based

on temperate and frequency compensation to add the offset that caused by
QdVdd function get the final VDD value and call
CorrectionWithLimitingResource to write it.
For Visby 4466, RSW will be based on the following procedure of AAS,
paSrvShareAasX1x will be replace with PaSrvSharedNgrG2 and
TempFreqCompEngineQdVdd will be replaced with
TempFreqCompEngineQdVddNgrG3 in Visby. For DPD, no changes compare to
AAS.
Radio SW Workflow
Ericsson Internal

2023-12-21 PF24
For MR9002-SP4, will follow platform solution, database may need to

be added for this new radio. These database values may be changed
in future.
/810/paVddQdEnable U8 0
/810/paVddQdDynamicLimitEnable U8 0
/810/paVddQdPwrLimit U32 600 /*-dbfs */
/810/paVddQdParLimit U32 750 /*0.01dB*/
/810/paVddQdEvmLimit U32 0x1FFFFFFF
/810/paVddQdVoltMin S32 150 /*DAC Value */
/810/paVddQdCPRGainMax U32 550 /*0.01dB */
/810/paVddQdCPRGainMin U32 500 /*0.01dB */
5.15.20 Deep Sleep
Visby will refer to SP8881 (AAS G3 MB deep sleep) feature. Under

deep sleep mode, Radio will power off or reset as much as possible
component to save power. The difference is that in AAS Radio, CPRI
link is connected to EO then to Radon, but in Visby, CPRI connect to
Radon directly. So, In AAS, Radon can be reset, but in Visby, to keep
the connection between Radio and DU, we cannot reset the whole
Radon like AAS radio do. In Visby, there’s no work on RICR and XCS
side, most of the works are on RSW side.
There should have two big stage of deep sleep.
Stage one is trigger deep sleep mode by coli-command. DU can send

Moshell command radio. Radio will follow the below steps (one by
one) to enter deep sleep mode.
Stage two is to communicate with DU, four new BCI messages will
introduce:
RU report deep sleep capability by capability signal and DU

client could subscribe the deep sleep by
ELIB_BC_SUBSCRIBE_DEEP_SLEEP_REQ.
Ericsson Internal

2023-12-21 PF24
After all the client subscribe success, DU client could enable

deep sleep by ELIB_BC_DEEP_SLEEP_ENABLE_REQ.
If all the client subscribed and all the clients send the enable
signals, RU will go to deep sleep mode.
1. stop supervision
2. suppress fault
3. turn off LNA
5. turn off RALF
6. turn off TRXIC
Reset Method in Visby
Compo
nent Reset Method
PACC PA_RESET_0
PA and
driver PA_ON_0
TX_LO TX_0…
W 11_RF_ON
TRX0_RESET
TRXIC _N
FDD_LNA_P
LNA D_0....11
AI
Receive
r AI_RESET_N
RX_FE_IC_S
RALF TBY_0…11
Step 1 and Step 2 is to make sure no fault raised after step 3 to

step 7 performed. If any steps are wrong during enter deep sleep mode,
radio will send ELIB_DEEP_SLEEP_ENABLE_IND with fault reason, DU
should restart radio to recover.
For stage two, its release target is Q4, maybe delayed, so in 4466,
we will only support stage one, Node FV can test based on the Moshell
command.
To recover from deep sleep mode, will follow SP8881 to use the legacy
radio restart procedure. Re-initialize the whole radio, can avoid unexpected
errors between SW module, like the dependency between modules and
wrong sequency is took. This is also the less effort solution.
Ericsson Internal

2023-12-21 PF24
RSW architecture
The above is the RSW solution architecture of SP8881, yellow and red
box means they are new for deep sleep feature, Visby can reuse this
architecture to do some adaption works. Like to the method to reset
every component. So, 4466 is totally depend on SP8881, if SP8881
delayed, 4466 will be delayed also.
MR9002-SP4 will follow 4466 solution on MR8930-SP1.
5.15.21 MR9002-SP15 7CC per port on B3 UL for Visby Radio
Refer to MR9002 SP15, it’s need support 7cc feature in order to

support more GSM on band3. The original visby plantform just support
6cc per port per band. So need adjust filter branch mapping and
capability report to support such feature.
The RX filter branch mapping change from 6ccB1 + 6ccB3 to 5ccB1 +

7ccB3.
Ericsson Internal

2023-12-21 PF24
As visby is based on chip radon1.1, for radon1.1 it has two UL MCBG,

each MCBG can mapping arbitrarily to corresponding 48 filter
branches(MCBG0 to FBG0 and FBG1, MCBG1 to FBG2 and FBG3).
So adjust one original B1 filter branch to B3, as the radio sw code just
support numerically equal filter branches per band. For such 5ccB1 +
7ccB3 unequal filter branches per band, it is needed to fit sw code so
that can get expected filter branch for handling.
The original method:
1. Using filter branch index(original radio sw) to find expected filter

branch or corresponding MCB/rf port
The fitted method:
1. Deal the filter branch index(original radio sw) to find exact filter
branch index
2. Using exact filter branch index to find expected filter branch or

corresponding MCB/rf port
The RX GainCompRx4 module and filter branch converter which is

used by RX services need adjust.
The TX mapping not need amend, still keep 6ccB1 + 6ccB3.
The capability need change accordingly so that telling DU setup

suitable number of carriers on RU.
For G1 DUG: No change
For G1 DUW:
as G1 DUW setup carriers process not matter with the capability RU

reported, it’s dependent on another designed table, so DUW will setup
carrier on the 6th filter branch. For such case, RU need feedback
reject in the TR_CDCI and DPCL interface to keep DUW work normal:
1. CDCI_TR_GET_DEVICE_CAPABILITY_REQ for the sixth carrier
reject with error code: CONFIG_DATA_ERROR
2. DPCL_SETUP4_REQ for the sixth carrier
reject with error code:

CBD_DPCL_INCONSISTENT_OR_MISSING_CONFIGURATION
_DATA
For G2 and G3:

Ericsson Internal

2023-12-21 PF24
The DU will depend on RU’s capability report to setup suitable number

of carriers adaptively.
for band1 the max filter branch number is Tx = 5 and Rx = 5
The corresponding db need to change:
/ulMaxNumberCarrier U32 12
/bandId0/ulMaxNumberCarrier U32 5
/dlMaxNumberCarrier U32 11
/bandId0/dlMaxNumberCarrier U32 5
No impact to RSW. Radio will receive

DC_TR_MODIFY_ATTACH_REQ request if to attach a NbIoT carrier
on ESS host carrier. Full scope SSV regression test needed during PD
phase, due to DL filter coefficient update for
essFdd100_Id1/essFdd150_Id2/essFdd200_Id3.
Step 1 and Step 2 is to make sure no fault raised after step 3 to step 7
performed. If any steps are wrong during enter deep sleep mode,
radio will send ELIB_DEEP_SLEEP_ENABLE_IND with fault reason,
DU should restart radio to recover.
For stage two, its release target is Q4, maybe delayed, so in 4466, we
will only support stage one, Node FV can test based on the Moshell
command.
To recover from deep sleep mode, will

follow SP8881 to use the legacy radio restart procedure. Re-initialize
the whole radio, can avoid unexpected errors between SW module,
like the dependency between modules and wrong sequency is took.
This is also the less effort solution.
Ericsson Internal

2023-12-21 PF24
RSW architecture
The above is the RSW solution architecture of SP8881, yellow and red
box means they are new for deep sleep feature, Visby can reuse this
architecture to do some adaption works. Like to the method to reset
every component. So, 4466 is totally depend on SP8881, if SP8881
delayed, 4466 will be delayed also.
MR9002-SP4 will follow 4466 solution on MR8930-SP1.
MR9002-SP15 7CC per port on B3 UL for Visby Radio
Refer to MR9002 SP15, it’s need support 7cc feature in order to

support more GSM on band3. The original visby plantform just support
6cc per port per band. So need adjust filter branch mapping and
capability report to support such feature.
The RX filter branch mapping change from 6ccB1 + 6ccB3 to 5ccB1 +

7ccB3.
Ericsson Internal

2023-12-21 PF24
As visby is based on chip radon1.1, for radon1.1 it has two UL MCBG,

each MCBG can mapping arbitrarily to corresponding 48 filter
branches(MCBG0 to FBG0 and FBG1, MCBG1 to FBG2 and FBG3).
So adjust one original B1 filter branch to B3, as the radio sw code just
support numerically equal filter branches per band. For such 5ccB1 +
7ccB3 unequal filter branches per band, it is needed to fit sw code so
that can get expected filter branch for handling.
The original method:
Using filter branch index(original radio sw) to find expected filter

branch or corresponding MCB/rf port
The fitted method:
Deal the filter branch index(original radio sw) to find exact filter branch
index
Using exact filter branch index to find expected filter branch or

corresponding MCB/rf port
The RX GainCompRx4 module and filter branch converter which is

used by RX services need adjust.
The TX mapping not need amend, still keep 6ccB1 + 6ccB3.
The capability need change accordingly so that telling DU setup

suitable number of carriers on RU.
For G1 DUG: No change
For G1 DUW:
as G1 DUW setup carriers process not matter with the capability RU

reported, it’s dependent on another designed table, so DUW will setup
carrier on the 6th filter branch. For such case, RU need feedback
reject in the TR_CDCI and DPCL interface to keep DUW work normal:
CDCI_TR_GET_DEVICE_CAPABILITY_REQ for the sixth carrier
reject with error code: CONFIG_DATA_ERROR
DPCL_SETUP4_REQ for the sixth carrier
reject with error code:

CBD_DPCL_INCONSISTENT_OR_MISSING_CONFIGURATION_DA
TA
For G2 and G3:

Ericsson Internal

2023-12-21 PF24
The DU will depend on RU’s capability report to setup suitable number

of carriers adaptively.
The corresponding db need to change:
SSV TCs,
tcESSNbiotAttachLowAndHighGuardBandPrbTo10MhzFullbandHost
tcESSNbiotAttachLowAndHighGuardBandPrbTo15MHzFullbandHost
tcMmEssCarrierConfigurationNbiotGbNr
tcMmEssCarrierConfigurationNbiotGbLte
tcMmEssCarrierConfigurationNbiotGb
5.15.22[7.15.3] MR9268-1 LTE GB NB-IoT coexistence with ESS on Visby

Radios
No impact to RSW. Radio will receive

DC_TR_MODIFY_ATTACH_REQ request if to attach a NbIoT carrier
on ESS host carrier. Full scope SSV regression test needed during PD
phase, due to DL filter coefficient update for
essFdd100_Id1/essFdd150_Id2/essFdd200_Id3.
SSV TCs,
tcESSNbiotAttachLowAndHighGuardBandPrbTo10MhzFullbandHost
Ericsson Internal

2023-12-21 PF24
tcMmEssCarrierConfigurationNbiotGbNr
tcMmEssCarrierConfigurationNbiotGbLte
tcMmEssCarrierConfigurationNbiotGb
5.15.23 MR9002-16 GSM IBW 28MHz Supporting on Visby 6626 B1B3
The realization of this feature needs to depend on the external database

update, as well as the modification of DRT table. External DB change is
universal for all versions of B1B3 HW. However, DRT will be adjusted based
on different HW version (R1D on Zu4 and R2C on Mongoose)
No SSI/SSV TCs are needed to be involved.
Node FV test is planned for different HW versions. The available SW version

is 23.Q2.IP5 and after.
5.15.24[7.15.4] SHP Enabled (Brian)
Except for radio 4456 on Visby radios, others are using GaN PA currently and
GaN Boost is the strategy that is using on radios, from the legacy. But GaN
Boost has obvious shortcomings on power consumption, especially when the
output power is at low levels. GaN Boost also has negative impacts on return
rates as PA is pushed harder even during the low traffic.
Based on this, SHP (Strong Hysteresis Protect), shall be implemented on

GaN based Visby radios, to reduce the radio power consumption as well as
securing good EVM performance.
Currently, on Visby radios,
 6626 B8B20/ 6626 B8B28/ 6626 B0AB28 (execution ongoing) is

enabled with SHP and show good performance.
 6626 B1B3/4466 B1B3B7 is being planned to be implemented with

SHP but will be covered in another SP (MR9002-SP13). Noted the
SHP enable on B1B3 needs the BOM update supporting, but B7 could
realize this with no change. Details see the MR9002-SP13.
 4466 B1B3B40 and 4466 B1B3B41 don’t have the request yet. Will be
discussed and planned in the future.
Ericsson Internal

2023-12-21 PF24
5.15.24.1[7.15.4.1] MR9002-SP13 SHP Enabled on Visby 6626 B1B3 and 4466

B1B3B7
As Required from function, it needs to be supported that SHP enable on B1

and B3 with GaN Boost enabled, but in SW execution, GaN Boost control
needs to be realized on different HW version and bands, which is developed
with the effort from TRX CTRL.
More details, see in chap 8.16.12.1, function description.
[7.16] (SYSFUNC Siyu)Radio Function System
Visby Platform are developed based Building practice of Bamboo,

which support up to 12T12R (internal TX/RX branch). This chapter
describe the impact functions which triggered by the Bamboo building
practice and new features requested in following product variance.
 Radio 6626, FDD dual band 3 sector radio, 2T2R per sector, 6 external
antennas
 Radio 4466, FDD triple band radio, 4T4R per band and 4 external
antennas. All impact of Mongoose would be valid starting from Radio
4466.
 Radio 4456, FDD triple band radio, 4T4R per band. Based on Radio
4466.
Supplemented documents:
 CRS Radio function (17/1056-HRB105700) to be updated content for

Radio 6626 and FDD Radio 4466
 Visby Function IP (1/159 41-FCP 133 0875)
 Common OA (204/0360-200/FCP131 47 ) , refers to Database Chapter.
[7.16.1] (SYSFUNC Siyu)Database impact and Autoget()
From Visby we would like to change the ruType to prdType.
Proposal of way forward (from Siamand Khizri)
1. Func Sys will provide the prdID : prdType _1.1.0 for first KRC
product of Visby as input to production database
2. Func Sys will create new repo for Bamboo building practice, for
SW external database parameters
Ericsson Internal

2023-12-21 PF24
3. CM will register new CAH number for the new building practice
repo
proposal : Chengdu will be release responsible of the repo
4. Func Sys will provide first folder structure with empty files
5. Visby team update the files with correct parameters
6. The SW build team need to include the new repo in the build for
visby LMC
This item may need to breakdown in further work activities.
For MR9002-SP4, prdType_1.4.0 is dedicated for Visby Radio 6626

B8 B20.
For MR9268-SP1,
[1.] Added new carrier type ESS+NBIoT, following database per

radio need update for capability reporting and time alignment:
– sysDataParam_1_1, timingParam_1_1,
sysDataParam_1_4, timingParam_1_4, for Radio 6626
– sysDataParam_1_2, timingParam_1_2,
sysDataParam_1_3, timingParam_1_3,
sysDataParam_1_6, timingParam_1_6, for Radio 4466
– sysDataParam_1_5, timingParam_1_5, for Radio 4456
[2.] Due to the re-design for DL filters, need update common

database for Radon filter configurations:
– radonDlFilters_essFdd100_Id1/radonDlFilters_essFdd150_Id2/
radonDlFilters_essFdd200_Id3
[7.16.2] Impact on Radio Capability
5.15.24.2[7.16.2.1] TRDCI
To support power overbooking (413/102 68-300/FCP 131 4743),

below attributes of TR_DCI will have new definition:
TX_PORT_AVAILABLE_OUTPUT_POWER to report available power

including overbooking margin
TX_PORT_MAXIMUM_OUTPUT_POWER is unaffected and shows

the actual possible output power the radio can transmit.
Radio 6626 B1.B3 (Available power > Maximum TX power per port):
Ericsson Internal

2023-12-21 PF24
RF_CHAR::TX_PORT_MAXIMUM_OUTPUT_POWER 120W
CAPABILITY_PORT_ARRAY::TX_PORT_AVAILABLE_OUTPUT_POWE
R 140W
TRX_RF_CHAR: OVERBOOKING_CAPABILITY::
NUMBER_OF_FREQUENCY_RANGES 2
FREQUENCY_RANGE_ID 0
TRX_RF_CHAR: OVERBOOKING_CAPABILITY:: OVERBOOKING_TYPE

1
Radio 4466 B1.B3.B7(Available power = Maximum TX power per port)
R 180W
TRX_RF_CHAR: OVERBOOKING_CAPABILITY
NUMBER_OF_FREQUENCY_RANGES 3
FREQUENCY_RANGE_ID 0

0
5.15.24.2.1[7.16.2.1.1] TR-DCI impact on MR9002-SP4
As a decision from SPM and Platform, Power overbooking will not be

needed on Visby Radios.
TX_PORT_AVAILABLE_OUTPUT_POWER will be the same as

TX_PORT_MAXIMUM_OUTPUT_POWER.
OVERBOOKING_CAPABILITY will not be suppoted with 0.
Radio 6626 B8 B20(Available power = Maximum TX power per port)
R 140W

0
Ericsson Internal

2023-12-21 PF24
5.15.24.3[7.16.2.2] CBCI
Because Visby extend RF port to E and F, and below signals need

update:
RRU_ANTENNA_POWER
RRU_CONFIG_SV
RRU_CONFIG_POWER_SV
To avoid some “old RU” which support RRU_ANTENA_POWER2

only, not working at customer site with new signals. i.e. DUW had
update the UP version, but “old RU” fail to upgrade APP on site.
Those old Radio will not work and bring troubles. Four alternatives as
below.
Alternative 1:
Extend the attribute of the signal to support E and F, as below:
>RRU_ANTENNA_POWER2_REQ
>>auxPowerPortA
>>auxPowerPortB
>>auxPowerPortC
>>auxPowerPortD
>>auxPowerPortE
>>auxPowerPortF
>RRU_CONFIG_SV2
>>PortE (new IE)
>>PortF (new IE)
>RRU_CONFIG_POWER_SV2
>>PortE (new IE)
>>PortF (new IE)
Because at Radio side, the SW will any select the parameters

according to the RF ports, if the radio support 4 antenna only, radio
will only read first 4 parameters.
For the fault, we add new fault ID for the extended ports
Ericsson Internal

2023-12-21 PF24
RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_ANTENN
A_BRANCH_ E/F/G/H
RBS_FAULT_TYPE_FEEDER_CABLE_DISCONNECTED_ANTENN
A_BRANCH_ E/F/G/H
RBS_FAULT_TYPE_LNA_FAILURE_ANTENNA_BRANCH_E/F/G/H
RBS_FAULT_TYPE_LNA_DEGRADED_ANTENNA_BRANCH_
E/F/G/H
Keep the old PROTOCOL revision (Rev 11) of CBCI interface.
Alternative 2:
Add one capability, to report the RF port number to DUW, then DUW
can select which signal send to Radio.
RRU_GET_GROUP_CAPABILITY_CFM:: RruRfPortNumber
e.g. IfRadio report 4 or less antenna ports, or not report the number of
antenna ports,
DUW will send RRU_ANTENA_POWER2 to Radio.
If Radio report 6 or more antenna number,
DUW will send RRU_ANTENA_POWER3 which support extended

ports.
 Introduce easy extension signals for new Radios.
RRU_ANTENNA_POWER3
Data:
rfPort: RF port identifier
auxPowerPort: Power feed state through antenna feeder
RRU_CONFIG_SV3
Data:
tmaCurrentLowLim : 0-200 Current in mA or 'Not Used')
tmaCurrentHighLim: 0-600 Current in mA or 'Not Used')

Ericsson Internal

2023-12-21 PF24
tmaDegradedSvCtrl: 0=reporting of LNA degraded fault indications off.

1=reporting of LNA degraded fault indications power=on (default)).
RRU_CONFIG_POWER_SV3
Data:
lowCurrentSupervision : ON, OFF
 Introduce a new capability to identify whether the radio supports new

signals.
New Capability: RRU_CAP_RF_PORT_SUPPORT
Explanation: denotes the ability to report supported RF ports
Attributes:
numberOfRfPorts: number of valid RF ports
rfPorts[]: list of RF ports
 Both new signals (e.g RRU_ANTENNA_POWER3) and legacy

signals (RRU_ANTENNA_POWER2) coexist in CBCI files.
 DU (MPSW) sends new signals if new capability reported, otherwise

legacy signals will be used.
 For the fault, add new fault ID for the extended ports (same with
Alternative 1)
 Keep the old PROTOCOL revision (Rev 11) of CBCI interface not
changed.
Alternative 3:
 Introduce easy extension signals to replace legacy signals(same

with Alternative 2).
 Remove legacy signals to _deprecated.sig file, which will not be

used in DU (MPSW).
 Update CBCI PROTOCOL revision to rev 12.
 MPSW will always use new signals(e.g RRU_ANTENNA_POWER3)

on ALL RRU radios.
Ericsson Internal

2023-12-21 PF24
 According to legacy mandated practice for incompatible CBCI

changes, it requires ALL related Radio applications in DUW UP have
ALWAYS been uplifted to the latest protocol revision. (Like what
legacy features did)
Alternative 4:
 The overall idea for this one is same with 1-3 of Alternative 3.
 It’s hard for Radio SW to accept the mandated practice to uplift all
Radio applications to the latest protocol revision, so they suggest
MPSW to introduce a new CBCI protocol revision negotiation
procedure, which is not supported in MPSW design base. MPSW
use new revision/signals for new radios, and legacy revision/signals
for legacy radios.
5.15.24.3.1[7.16.2.2.1] Comparison of 4 alternatives

Positives Negatives
Alt 1. It’s a compatible change, ALL 1. The expandability is not good
1 radios will use legacy signals, no enough (than others), as it cannot
impact on legacy radios. cover more than 8 RF ports radios.
2. It could cover maximum 8 RF
ports in future.
3. Smallest design efforts on both
DU (MPSW) and Radio SW
(compared to other proposals).
4. Less verification efforts on legacy
radios.
5. Looks like it does not break CBCI
Design Rule.
Alt 1. It’s a compatible change, only 1. It violates the design rules for the
2 new Radio support new signals, no multi-standard RBS (5/102 60-HRB 105
design impact on legacy radio 700).
applications. RBS_DM:39
2. No further CBCI interface impact It is not allowed to add a new message and
even more RF ports will be make it an alternative to an already
introduced in future. (better than existing message. The old one shall be
Alt1) removed and the new one shall have new
3. Small design efforts on both DU name and number.
(MPSW) and Radio SW.
4. Less verification efforts on legacy
radios.
Alt 1. It follows CBCI Design Rule. 1. It’s an incompatible with CBCI I/F
3 2. No further CBCI interface impact Rev 11.
even more RF ports will be 2. Large Radio SW efforts to uplift ALL
introduced in future. Radio applications to the latest CBCI
3. Small design efforts on DU protocol revision and signals.
(MPSW). 3. Large verification efforts on legacy
radios.
4. Medium risk on legacy radios,
compared to Alt4.
Alt 1. It follows CBCI Design Rule 1. It’s an incompatible with CBCI I/F
4 2. No further CBCI interface impact Rev 11.
even more RF ports will be 2. The new protocol revision
introduced in future. negotiation has very large impact on
3. Small design efforts on Radio DU (MPSW). It may break MPSW
SW. legacy systemization, include the
4. No design efforts on legacy radio existing Radio LM negotiation, fault
Ericsson Internal

2023-12-21 PF24
applications. handling, etc.

3. Large design on MPSW and test
For future feature: efforts for “negotiation”.
5. Small impact on legacy radios if 4. Large risk on legacy radios and
new PROTOCOL revision updated customer network than that on Alt3,
in future. because not only RRU radios but also
6. Reduce Radio SW design efforts, other RU{W|S} radios will be impacted,
avoid legacy Radio SW uplifting for as the CBCI connection is a common
CBCI protocol revision stepping in part for RRU and RU, even Baseband
future. in MPSW.
7. Verification efforts reduced on 5. Considering to the CDCI interface
legacy radios. (another I/F between DU and Radio), if
same negotiation requires on it, more
efforts needed.
For future:
6. A running cost needed for MPSW to
maintain the different protocol signals
for each revision in future.
7. A specific study on “protocol
revision” impact is needed for CBCI
“across version” uplift on legacy radios.
And more design/test efforts may
require. For example: if protocol uplift
from REV_5 to REV_7, the impact of
new signals introduced in REV_6
should be take into account.
Visby choose Alternative 2 after discussion with Magnus Engström

based on these considerations below.
1. From WCDMA RAN Roadmap (1/224 01-FGB 101 135 Uen slide 26),
DUW HW is going to be supported till W22.Q4, in the year of 2021,
DUW SW support corrections only and limited feature
enhancement. To decrease the risk in field, Alternative 3 and
Alternative 4 which need upgrade protocol revision are not
recommended.
2. Alternative 2 is more flexible on multi RF ports of multi standard

and multi RAT radios than Alternative 1(maximum RF ports
number is limited to 8). For alternative 2, there is no risk to be
used in customer network when legacy Radios and Visby radios
coexisted. Old and legacy Radios will not be impacted if alternative
2 is chosen for RRU-CBCI update.
5.15.25[7.16.3] Impact on TX function
5.15.25.1[7.16.3.1] TX/TOR mapping
Channel mapping from CPRI to Antenna port:

Ericsson Internal

2023-12-21 PF24
Palau- Channe l
Carrie r NO.
PA Branch
DL- MCBG
MCB NO.
DL- MCB
DL- FBG
DAC/ IF
DAC/ IF
RF port
DL- FB
DL- LB
Palau
Band
B1 0,1,2,3,4,5 DL- FBG0 DL- FB12~ DL- FB17 2 DL- MCBG0
DL- MCB2 DL- LB2 DAC_IF_0 MRIX_data0(2) Palau0 TX2 PA0 Ant- A
DL- MCB3 DL- LB7 DAC_IF_0 MRIX_data1(3) Palau0 TX7 PA6 Ant- B
DL- MCB0 DL- LB4 DAC_IF_0 MRIX_data1(0) Palau0 TX4 PA5 Ant- E
DL- MCB1 DL- LB1 DAC_IF_0 MRIX_data0(1) Palau0 TX1 PA3 Ant- F
DL- MCB2 DL- LB6 DAC_IF_0 MRIX_data1(2) Palau0 TX6 PA7 Ant- A
DL- MCB3 DL- LB3 DAC_IF_0 MRIX_data0(3) Palau0 TX3 PA1 Ant- B
DL- MCB0 DL- LB0 DAC_IF_0 MRIX_data0(0) Palau0 TX0 PA2 Ant- E
DL- MCB1 DL- LB5 DAC_IF_0 MRIX_data1(1) Palau0 TX5 PA4 Ant- F
DL- MCB1 DL- LB9 DAC_IF_1 MRIX_data4(1) Palau1 TX1 PA9 Ant- C
DL- MCB2 DL- LB10 DAC_IF_1 MRIX_data4(2) Palau1 TX2 PA10 Ant- D
DL- MCB0 DL- LB8 DAC_IF_1 MRIX_data4(0) Palau1 TX0 PA8 Ant- C
DL- MCB3 DL- LB11 DAC_IF_1 MRIX_data4(3) Palau1 TX3 PA11 Ant- D
TOR sharing 4:1, PA Vdd distribution as following figure
5.15.25.2[7.16.3.2] TX/TOR mapping impact on MR9002-SP4
Channel mapping from CPRI to Antenna port:

Palau- Channe l
PA Branch
DL- MCBG
MCB NO.
DL- MCB
DL- FBG
DAC/ IF
RF port
DL- FB
DL- LB
Palau
Band
B8 DL- FBG0 DL- FB0~ DL- FB5 0 DL- MCBG0 DL- MCB0 DL- LB0 DAC_IF_0 Palau0 TX0 PA0 An
TOR sharing 4:1, PA Vdd distribution as following logic figure

Ericsson Internal

2023-12-21 PF24
5.15.25.3[7.16.3.3] TX LO
Visby using the static LO, TX and RX have the same LO: 1995MHz
Additional Palau NCO is needed to cover wide frequency range.
B3 TX NCO = B3_DL_MidFreq – LO
Ericsson Internal

2023-12-21 PF24
5.15.25.3.1[7.16.3.3.1] TX LO impact on MR9002-SP4
Visby using the static LO, TX and RX have the same LO: 997.5MHz
for Radio 6626 B8 B20.
Additional Palau NCO is needed to cover wide frequency range.
5.15.25.4[7.16.3.4] TX power saving
5.15.25.4.1[7.16.3.4.1] Component power saving
/powerSaveCtrlBoardTxPwrDwn char "TXLOW"
/powerSaveCtrlTxPwrDwn char "TXLOW"
5.15.25.5[7.16.3.5] ASIC: clock control
If no carriers in one rf-branch, disable relative clocks ASIC clocks
TX: FBG, FREHO(GSM), MCB clocks, hard clipping, DPD clocks
MCB clocks: DL_MCBG_CB_[0-3]_CLK_CFG
DPD clocks:
DL_LB_ALG_CB_CCR_MOD_CLK_ENABLE_CFG(MIMO sleep/Cell
sleep)
5.15.25.6[7.16.3.6] Power Overbooking
Power overbooking follows MR5657 NDS 413/10268-300-

FCB1314743
The implementation in Xenon is to read power meter with 200 us loop.

But Visby support more carriers, DP need read 72 carrier filter
branches instead of 24 filter branches.
Consider the TTI (transmission interval), because the power within a

TTI is stable. as min TTI is 0.5ms for NR, the period of each reading
cycle need less than 0.5ms/2, the power can be adjusted within a TTI.
DP people (Georgios Theodoros Daglaridis) is running some

experiments on 2242Ft to check the CPU load when the algorithm
runs and decide if it could work for 72 branches.
Ericsson Internal

2023-12-21 PF24
As checked by DP expert Tomas Elgeryd, there is no CPU load

problem when the algorithm runs monitoring and doing gain
adjustments of 72 FB’s (Filter Branches).
The same as the latest decision on MR9002-SP1. No need to support

Power Overbooking on MR9002-SP4.
5.15.25.7[7.16.3.7] Over temperature handling
Because of limited thermal dimension, Visby radio cannot support

720W from -40degC to 55degC. According to thermal simulation,
when ambient temperature higher than 50degC, maximum power
supported by Visby is 600W. Visby radio need extra degradation(0.8
dB backoff) with 720W output from 25 degree to 30 degree.
Environmen 600W full 720W full
t temp traffic traffic
<= 25C No NO NO backoff
airflow backoff
25C< <= NO 0.8dB backoff
30C No backoff
airflow
30C< <= maximum maximum
40C No 2.5dB 2.5dB backoff
airflow backoff
40C< <= maximum maximum
45C No 2.5dB 3.3dB backoff
airflow backoff
<= 50C with maximum maximum
air flow 2.5dB 2.5dB backoff
backoff
50C< <= 55C with maximum maximum
air flow 2.5dB 3.3dB backoff
backoff
According to the thermal results on Radio 6626 B1B3, PA coin limit is

the bottle neck in normal temperature both for 720w and 600W output
power.
Based on the requirement and thermal results, these temperature

attribute should be updated according to the thermal and integration
results.
 The attribute of NormalHi in temperatue dB should be

considered from PA coin limit.
 The attribute of Hot in temperatue dB should be updated to

control 0.8 dB backoff according to the temperature curve.
Ericsson Internal

2023-12-21 PF24
 The attribute of ExceptionalHi and maxAttenuationExtra in

temperature db should be updated to cover 2.5db and extra 0.8
db total 3.3 dB backoff.
5.15.26[7.16.4] Impact on RX function
5.15.26.1[7.16.4.1] RX mapping
Palau- Channe l
UL- MCBSG
Carrie r NO.
RX channe l
UL- MCBG
MCB NO.
UL- MCB
UL- FBG
UL- FB
ADCB
Palau
Band
LNA
B1 0- 5 UL- FBG0 UL- FB24~ UL- FB29 4 UL- MCBG0
UL- MCBSG1 UL- MCB0 ADCB0 Palau 0 RX4 LNA4 Ant- A
UL- MCBSG1 UL- MCB1 ADCB1 Palau 0 RX5 LNA5 Ant- B
UL- MCBSG0 UL- MCB1 ADCB1 Palau 0 RX1 LNA1 Ant- E
UL- MCBSG0 UL- MCB0 ADCB0 Palau 0 RX0 LNA0 Ant- F
UL- MCBSG1 UL- MCB2 ADCB2 Palau 0 RX6 LNA6 Ant- A
UL- MCBSG1 UL- MCB3 ADCB3 Palau 0 RX7 LNA7 Ant- B
UL- MCBSG0 UL- MCB3 ADCB3 Palau 0 RX3 LNA3 Ant- E
UL- MCBSG0 UL- MCB2 ADCB2 Palau 0 RX2 LNA2 Ant- F
UL- MCBSG2 UL- MCB2 ADCB2 Palau 1 RX2 LNA10 Ant- C
UL- MCBSG2 UL- MCB1 ADCB1 Palau 1 RX1 LNA9 Ant- D
B3 60- 65 UL- FBG2 UL- FB66- UL- FB71 11 UL- MCBG1
UL- MCBSG2 UL- MCB3 ADCB3 Palau 1 RX3 LNA11 Ant- C
UL- MCBSG2 UL- MCB0 ADCB0 Palau 1 RX0 LNA8 Ant- D
5.15.26.1.1[7.16.4.1.1] RX mapping impact on MR9002-SP4
Palau- Channe l
UL- MCBSG
RX channel
UL- MCBG
MCB NO.
UL- MCB
UL- FBG
UL- FB
ADCB
Palau
Band
LNA
B20 UL- FBG0 UL- FB0~ UL- FB5 0 UL- MCBG0 UL- MCBSG0 UL- MCB0 ADCB0 Palau 0 RX0 LNA0 Ant- E
B8 UL- FBG0 UL- FB6~ UL- FB11 1 UL- MCBG0 UL- MCBSG0 UL- MCB1 ADCB1 Palau 0 RX1 LNA1 Ant- F
B8 UL- FBG0 UL- FB12~ UL- FB17 2 UL- MCBG0 UL- MCBSG0 UL- MCB2 ADCB2 Palau 0 RX2 LNA2 Ant- E
B20 UL- FBG0 UL- FB18~ UL- FB23 3 UL- MCBG0 UL- MCBSG0 UL- MCB3 ADCB3 Palau 0 RX3 LNA3 Ant- F
B20 UL- FBG1 UL- FB24~ UL- FB29 4 UL- MCBG0 UL- MCBSG1 UL- MCB0 ADCB0 Palau 0 RX4 LNA4 Ant- B
B8 UL- FBG1 UL- FB30~ UL- FB35 5 UL- MCBG0 UL- MCBSG1 UL- MCB1 ADCB1 Palau 0 RX5 LNA5 Ant- A
B8 UL- FBG1 UL- FB36~ UL- FB41 6 UL- MCBG0 UL- MCBSG1 UL- MCB2 ADCB2 Palau 0 RX6 LNA6 Ant- B
B20 UL- FBG1 UL- FB42~ UL- FB47 7 UL- MCBG0 UL- MCBSG1 UL- MCB3 ADCB3 Palau 0 RX7 LNA7 Ant- A
B20 UL- FBG2 UL- FB48~ UL- FB53 8 UL- MCBG1 UL- MCBSG2 UL- MCB0 ADCB0 Palau 1 RX0 LNA8 Ant- C
B8 UL- FBG2 UL- FB54~ UL- FB59 9 UL- MCBG1 UL- MCBSG2 UL- MCB1 ADCB1 Palau 1 RX1 LNA9 Ant- D
B8 UL- FBG2 UL- FB60~ UL- FB65 10 UL- MCBG1 UL- MCBSG2 UL- MCB2 ADCB2 Palau 1 RX2 LNA10 Ant- C
B20 UL- FBG2 UL- FB66- UL- FB71 11 UL- MCBG1 UL- MCBSG2 UL- MCB3 ADCB3 Palau 1 RX3 LNA11 Ant- D
5.15.26.2[7.16.4.2] RX LO
Visby using the static LO, TX and RX have the same LO: 1995MHz
Additional Palau NCO is needed
B3 RX NCO = B3_UL_MidFreq – LO
Ericsson Internal

2023-12-21 PF24
RX power saving
5.15.26.2.1[7.16.4.2.1] RX LO for MR9002-SP4
Visby using the static LO, TX and RX have the same LO: 997.5 MHz
for Radio 6626 B8 B20
Additional Palau NCO is needed
5.15.26.3[7.16.4.3] RX Power saving
5.15.26.3.1[7.16.4.3.1] Component power saving
/powerSaveCtrlBoardRxPwrDwn char "RFMIXER LNA RX_BE_SOC"
/powerSaveCtrlRxPwrDwn char "RFMIXER LNA RX_BE_SOC"
5.15.26.4[7.16.4.4] ASIC: clock control
If no carriers in one rf-branch, disable relative clocks ASIC clocks
RX: FBG, FREHO(GSM), MCB clocks
MCB clocks: UL_MCBG_CB_[0-1]_CCR_CLK_0_CFG.

Ericsson Internal

2023-12-21 PF24
5.15.27[7.16.5] Impact on Board Function
5.15.27.1[7.16.5.1] Dual Power Handling
Because Radon only have one 48V_NOK signal as power

interference, additional interference signal need add to indicate the
power failure.
N48V_OK_0 is from the master DC module; it connects to the

48V_NOK on radon.
N48V_OK_1 is from the slave DC module; it connects to the additional

interference signal of Radon. EVC database will update for the new
event.
Note:
Figure for function instruction only
Unlike other radio with dual power supply (Radio 4449, 8843, 4442,
4443), Visby digital part can work with single power input (Power input
module0, master port). The FS for the dual power supply need update
for Visby as below table.
FS Nr FS title Master Slave

port port
RSWR2648 Power drop Follow /

shorter than
Radio holdup
time
Ericsson Internal

2023-12-21 PF24
RSWR27969 Power drop / New

for slave for
shorter than Visby
Radio holdup
time
RSWR2649 Power drop Follow Follow

longer than
radio holdup
time but
shorter than
CPU holdup
time
RSWR2650 Power drop Follow /

for master
longer than
CPU holdup
time
RSWR2651 Power drop / Not

for slave be
longer than used
CPU holdup
time
RSWR27967 Power drop / New

for slave for
longer than Visby
Radio holdup
time
RSWR2652 Connection of Not /

the power be
supply to used
master only
RSWR27968 Connection of New /

the power for
supply to Visby
master only
RSWR2653 Connection of / Follow

the power
supply to
slave only

power supply
to slave when
master is
already
Ericsson Internal

2023-12-21 PF24
connected

power supply
to master
when slave is
already
connected
1) New add for Slave port (RSWR27969)
RSWR2648 description: When a power drop is detected, the

radio shall set the PFA bit on the CPRI link. When power returns,
any active carrier shall be restored within 100 ms.
RSWR27969 description: when a power drop is detected, the

Radio will shut down mapping PA; if frequent input voltage drops,
will do back off and report the PAXs which mapped to the slave
port shut down power low; if the back off achieve max backoff, will
cease power low and report the PAXs which mapped to the slave
port shut down insufficient.
2) New add for Slave port( RSWR27967)
RSWR2651 description: When a power drop is detected, the

radio shall set the PFA bit on the CPRI link. When the radio holdup
time expires, the radio shall restart. The radio will do cyclic restarts
until the power is restored.
RSWR27967 description: When a power drop is detected at

slave port, When the radio holdup time expires, the radio shall
report the PAXs which mapped to the slave port shut down without
power and release those carriers.
3) New add for Master port(RSWR27968)
RSWR2652 description: The master starts up. The master will

detect that the slave is not working and restart. The radio will
restart cyclically until both power supply cables are connected. All
LED will remain OFF.
RSWR27968 description: The master starts up; radio is on

application SW. but reject to setup carriers to the PAXs which
mapped to the slave port.
 The Behavior of power drop as below table shows:

Ericsson Internal

2023-12-21 PF24
Power Power Behavior

input input
stage stage
module0 module1
48V_0_ 48V_1_O
• No any fault raise
OK K
1) power drop only one time:
Shut down mapping PA, no fault report

to DU
2) frequent input voltage drops, when
power recovery
Radio is doing backoff:
Raise
ELIB_CONST_FH_FAULT_ID_POWER
48V_1_N
_DISTURBANCE_INPUT_POWER_LO
48V_0_ OK<Radi
W (radio will check which branch need
OK o hold up
do backoff, and report_ind to DU)
time
Radio achieve max backoff:
Cease
W (cell degrade)
Raise
ELIB_CONST_FH_FAULT_ID_POWER_
INTERRUPT_INPUT_POWER_INSUFFI
CIENT (cell degrade)
Cease
48V_1_N
OK >
48V_0_ W
Radio
OK Raise
hold up
time
_INTERRUPT_INPUT_POWER_INSUF
FICIENT (cell degrade)
48V_0_ Shut down all PA, no fault report to DU,

NOK< just Radio internal fault, send PFA
48V_1_O
Radio through CPRI inband to DU
K
hold up 2) frequent input voltage drops, when
time power recovery

Ericsson Internal

2023-12-21 PF24
W,
Cease
W
Raise
W_LIMIT_EXCEEDED
Same behavior as above.
Shut down all PA, no fault report to DU,

just Radio internal fault, send PFA
through CPRI inband to DU
2) frequent input voltage drops, when

power recovery
48V_0_ 48V_1_N
NOK< OK<
Radio Radio
W,
hold up hold up
time time
Cease
W
Raise
W_LIMIT_EXCEEDED
48V_0_ 48V_1_N Raise
NOK< OK>
Radio Radio ELIB_CONST_FH_FAULT_ID_POWER_DI
hold up hold up STURBANCE_INPUT_POWER_LOW_LIMI
time time T_EXCEEDED
Radio / Radio will restart itself
hold up
time <
48V_0_
NOK<
Ericsson Internal

2023-12-21 PF24
CPU
hold up
time
48V_0_
NOK>
CPU / Radio will restart to Auboot
hold up
time
 DataBase impact
– New database(System DB) need to indicate the PA branch

which mapping to the DC ports respectively :
/dc0/paxBranch char A, B, E, I, L /* for master

DC module */
/dc1/paxBranch char C,D,F,G, H, J, K /* for slave DC

module */
– EVC Database:
BGA Si B Pin ' G E B
name gn G Pack G P V o
al A age P I C o
Na Nam I O t
me n e on O G
u Rad n P I
m on G u I /
b r m O O
e o b -
r u e n m
p r u u
m x
b
e m
r o
d
e
DC_48 N4 A IO_ 1 1 d 0
Vok_r[ 8V K GPI 0 3 e
2] _O 3 O_10 f
K_ 1 _13 a
0 u
l
Ericsson Internal

2023-12-21 PF24
This GPIO is 'DC_48VOK' by default: is the main power interrupt which is same as legacy N48V_OK
alarm will trigger PA protection and log register then board restart
N4
A IO_
EvC_tri 8V 2
L GPI 1 1
g_ext_r _O . D
3 O_10 0 0
[2]_[0] K_ 0
3 _10
1
Second 48V rail only supply two PA_VDD, when this power loses, it will not impact CPU SW normal
working, Radio will only shut down related PA branches
 HW logging impact:
ID616: 48V input failure at slave port
 Event log impact:
– Current event log records the power drop via:
ID21: DC lost longer than power hold-up time
ID33: DC 48V drop cnt
– New event log need added for the slave port
ID21: Slave DC lost longer than power hold-up time
ID31: Slave DC 48V drop cnt
 New fault need:
faultId: POWER_INTERRUPT_INPUT_POWER_INSUFFICIENT
faultDescription: 48V input failure at slave port (External power supply

insufficient due to interrup)
additionalData: TR-DC Device IDs for all setup affected carriers.
expect DU action: block related cells, when fault raise;
de-block related cells when fault cease.

Ericsson Internal

2023-12-21 PF24
Fault Autonomously Ceaseable: applicable （can be recover）
Fault Indication Signal to Clients: DC_TRS_FAULT_IND,

DC_TRS_FAULTCEASE_IND
5.15.27.2[7.16.5.2] Power backoff with insufficient power
FD: 10528 Power Back-Off for Insufficient Power Supply
Because two DC feeds, Radio SW need handle power back off

separately
1) Database update:
Parameters for DC-PA branch mapping, which also used in power

drop handling
Add and set different threshold (BackoffThreshold/recoveryThreshold)

to every DC port, value depend on power consumption (HW input)
/dc1/BackoffThreshold U8
/dc2/recoveryThreshold U8
2) Radio SW handle the two back off for two DC independently, but
keep same backoff report
Independent backoff process
Request PA1 gain -> ResourceHandler -> m_onPa1BackoffReq->

emit(emitGain)
Backoff report handling
m_pResourceHandler->updateBackoffData(data);
O&M signal for carrier backoff (DC_TR_REPORT2_IND) will request

with TR_DEVICE_ID
5.15.27.3[7.16.5.3] Unit power measurement
Follow RSWR14980 for the dual DC power measurement
e.g.
Initiation:
Cellular Operator enters COLI command, "eqpm pwrc s"
Description:
Ericsson Internal

2023-12-21 PF24
In response to $ eqpm pwrc s COLI command, radio returns following

(Watt & Volt values are an example):
Total Power Consumption
Instantaneous power consumption (W): 1177.04
Average power consumption:
over last 60 sec (W): 1177.20
over last 15 min (W): 1177.20
Consumed since last restart: (kWh): 2354.40
Power Supply 1
Voltage (V) 47.8
Power Supply 2
Voltage (V) 48.3
5.15.27.4[7.16.5.4] Build-in Test Support
MR4106-SP3 279/102 68-300/FCP 131 4743 introduce power source

test for for single power cable feeds to each radio. To implemented
power source test function in Visby, Test sequence, database and
elog need update.
Test sequence update in red part of below

Ericsson Internal

2023-12-21 PF24
Press Maintain Operational

BIST function Energy Efficiency PA handler
Button indcator
LED fast flash (16Hz)
pwrMearReq
return V and I of each DC port
PA Biased On
return
pwrMearReq
return V and I of each DC port
PA Biased Off
return
Caclculate estimated
voltage of each DC port
alt
Meaured Voltage and estimated voltage > threshold

LED Steady On
return
Eles LED flash (2Hz)
return
Database update for each DC port. Database names should not be

treated as absolute and may be subject for change in PD, also need
aligned with MR4106-SP3
• Unit Pmax
• Voltage Test Pass criteria
o Nominal threshold
o
Margin
E-log: log the test characteristics in blow list of all DC ports in E-log
• Test result
• K-value
• Us
Ericsson Internal

2023-12-21 PF24
• Measured voltage/current at both idle/PA biased mode
• Estimated U@Pmax, delta voltage to test threshold
• Used database parameters values (Pmax,

threshold, margin
5.15.27.5[7.16.5.5] MMI
Although Visby Radios HW support up to 4 CPRI connection, The MMI

handling is covered for maintain button, Fault, Operational and
Maintenance only, there is no impact on BCI. MMI behavior follow
RBS 6000, Site and Energy products LED handling and Semantics
13/102 60-HRB 105 700
CPRI interface 1-4 is handle by RICR.
Mongoose impact on MMI function:
Mongoose doesn’t have flexible logic as provided by traditional

FPGA chip. Some functions need to be taken by SW. This imposes
big challenge to SW especially on “real-time” control signals such as
external reset signals, etc. Thus both the 7s MMI button and L1 reset
solution are impacted upon selection of Mongoose chip.
5.15.27.6[7.16.5.6] Fault handling
5.15.27.6.1[7.16.5.6.1] New fault needs for power drop handling:
faultId: POWER_INTERRUPT_INPUT_POWER_INSUFFICIENT
faultDescription: 48V input failure at slave port
additionalData: TR-DC Device IDs(Carrier IDs) for all setup affected

carriers.
Ericsson Internal

2023-12-21 PF24
Fault Autonomously Ceaseable: Applicable (can be recover)
Fault Indication Signal to Clients: DC_TRS_FAULT_IND,

DC_TRS_FAULTCEASE_IND
Next Behavior in CAT: Disable Cell
New alarm additional Txt need to be added in CAT.
5.15.27.6.2[7.16.5.6.2] Without Branch Info in FaultType
Due to the Radio Branch number is extending to 12 from 8, and the

extending work for current fault structure is repetitive, so we want to
remove the Branch Info from the FaultTypeId(The design request from
Global Function team).But those existed faults(with Branch info) can
still work for the legacy Radios, from Visby and later classic Radios
will use the new faultTypeID without Branch Info.
From the Faults collection result we can see 3 scenarios followed:
1. For the Radio Internal faults without the Branch Info, so no impact
for those faults.
2. For the Radio Internal fault with Branch info, will add the new
internal fault without Branch info keep the old the mapping to Reported
FaultType, so the FAULT_IND signal will be not change and the CAT
is not influenced too, just RU internal update.
Used the new DB to indicate the Radio Internal Fault Branch Info, for
example:
Ericsson Internal

2023-12-21 PF24
 /id_prdType_1.1.0/fmxxx(LocalFaultId)/branchInfo char “A B C D E F G H I J K L”
 / id_prdType_1.1.0/fmxxx(LocalFaultId)/branchInfo char “AB CD EF GH IJ KL”
 / id_prdType_1.1.0/fmxxx(LocalFaultId)/branchInfo char “CIL DF BEH AGJK”
 / id_prdType_1.1.0/fmxxx(LocalFaultId)/branchInfo char “ABCDEFGHIJKL”
3. For DUW G1 there are several FaultType with Branch Info, and now
for Visby will extend the support for Rfport E and F, you can see that
both reported FaultType and Radio Internal Fault defined with Branch
Info.
For DUW G1 the final solution:

RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_A
FU_FT_SHORT_CIRCUIT_BR NTENNA_BRANCH_A/B/C/D/E/F
FT_FEEDER_CABLE_DISCONNECTED_PORT NTENNA_BRANCH_A/B/C/D/E/F
Sub module
FaultManager CFHE CCIE DUW
W fault detected RBS_FAULT_TYPE_SHORT_CIRCUIT_TOWARDS_TMA_A
FU_FT_TMA19_LNA_BR_FAULT NTENNA_BRANCH_A/B/C/D/E/F
FU_FT_TMA19_LNA_BR_DEGRAD NTENNA_BRANCH_A/B/C/D/E/F
 The reported FaultType to DUW G1 still with Branch Info, so no

change for the FAULT/CEASE_IND signal structure. Due to
CBCI protocol upgrade cost is big.
 In Radio side the Internal FaultId defined without Branch Info,

this has better expansibility for the future radios (maybe support
8 ports).
 New reported FaultType ID need add, due to support port E and

F
In radio software raise/cease fault to FaultManager:
 The fault is not related to Branch Info keep the old procedure.
 New internal fault defined without Branch Info, use

RU_FM_LOCAL_FAULT4_IND to raise fault to FaultManager and
use RU_FM_LOCAL_FAULTCEASE3_IND to cease fault to
FaultManager. For example:
Ericsson Internal

2023-12-21 PF24
Fault Suppress in Radio software:
 Each Radio Internal Fault has a depend fault list , the fault in the
list means has higher priority, and when the higher priority
fault raised can suppress the lower fault.
 Here is an example for depend fault list :

– LINEARIZATION_FAULT_PORT_A : DepList52a
– LINEARIZATION_FAULT_PORT_B : DepList52b
– After restructure , FT_ LINEARIZATION_FAULT_PORT just has one DepList52

(all faults in this list without branch info)
5.15.28[7.16.6] Impact on Antenna Function
For Radio 6626

Ericsson Internal

2023-12-21 PF24
Visby VSWR solution of FDD is based on AI receiver. The HW

architecture as below figure:
Main behavior of each module:
Radio SW: Send VSWR measurement request to ZU4, capture

VSWR IQ data from ZU4 and execute VSWR algorithm, Report VSWR
measurement result.
Radon: S0/RFS sync signal to ZU4, LO setting to AI receiver to

support multi band VSWR
ZU4: JESD link setup with AI receiver, AIB_SW_CTRL antenna switch

matrix control, AI_LO_MUTE control to AI receiver, Capture and store
IQ data FWD and REFL signal
When VSWR is not measured, AI_LO_MUTE will break the signal

path from antenna to AI receiver, to prevent AI_LO leak to TX path.
IQ data from AI receiver is already down link to 30.72MHz, there is no

data processing in ZU4. The capture length of each measurement is:
8192 IQ data, I 16 bit and Q 16 bit.
Time sequence of each module

Ericsson Internal

2023-12-21 PF24
RSW VSWR
ANTPI ZU4 AI receiver AIB
service
VSWR MeasReq
loop every 5s
LO setting
Return
VSWR Measure Request

AIB_SW_CTRL
Return
Waiting for next RFS

and delay offset
AI_LO_MUTE(disable)
Return
Capture IQ
Return
Interrup
Capture data
Return
VSWR algorithm
VSWR MeasReport
For FDD Radio 4466
As Mongoose would be introduced since FDD Radio 4466, here

comes the impact of Mongoose on DVSWR function:
The VSWR solution would be impacted. VSWR data is now captured

by Radon and down sampled in MCB, and then send to RSW in
Mongoose. This is different for 6626 solution.
5.15.28.1[7.16.6.1] DVSWR TOR sharing solution for MR9002-SP4 Mongoose

based products
Traditionally the forward and backward signals needed for DVSWR

measurement is sampled by dedicated ADC chip. If TOR paths can be used
to capture forwards and backwards signals from antenna, the ADC chip
dedicated for legacy DVSWR measurement may be saved, which means cost
down of Radio hardware. For example, the AI receiver of AD9368 in Visby
can be removed based this new solution.
Ericsson Internal

2023-12-21 PF24
This DVSWR TOR sharing solution reuse most of the solution from the
DVSWR TA solution for Visby. More detailed info is in the TA report:
https://ericsson.sharepoint.com/:w:/r/sites/Visby/Shared%20Documents/
MR8932%20Radio%204466%20B1B3B7%20PV/01_PreStudy/
03_Tor_sharing/DVSWR_tor_sharing_technical_report_pa2.docx?
d=w3469ce9b7a274db68f41b2d370df5626&csf=1&web=1&e=v0NzE3
5.15.28.1.1[7.16.6.1.1] Function description
Below is the data path schematic of TOR sharing for DVSWR solution.
In this solution, the TOR ADC sampled data should be used for both DPD
and DVSWR function. So RF switches are needed on PCB to connect both
TOR data path and DVSWR data path to TOR ADC. When the TOR ADC
sampled data get into Radon, it should also be routed to both LB and
MCB/FB. The LB path is for traditional DPD function, and the MCB/FB path is
for DVSWR function.
As the TOR ADC sample data at a rate of 491.52Msps, and the data needed
for VSWR algorithm is 30.72Msps. MCB/FB is used here to down-convert the
ADC output data. The down-converted data is then captured into TEME just
as in legacy VSWR implementation, and finally transferred to RSW (Radio
Software) for return loss calculation.
5.15.28.1.2[7.16.6.1.2] Actions
The DVSWR measurement flow (for a specific antenna, band and

carrier) would be like below:
RSW select antenna, band and carrier, config AIB, config RTS (not
triggering of RTS data capture) and inform DPCPRI about start of
DVSWR measurement.
DPCPRI (according to 10ms RFS signal and also carrier related delay
information) config RTS data capture trigger, TOR ADC and RF switch
for DVSWR measurement; inform DPL to suspend DPD functionality;
and later on re-config TOR ADC and RF switch for DPD functionality;
inform DPL to resume DPD functionality.
Ericsson Internal

2023-12-21 PF24
(DPL suspend or resume DPD functionality according to DPCPRI

message.)
Upon reception of RTS interrupt, RSW fetch data from RTS for
DVSWR calculation and reporting to DU. This finalize DVSWR
measurement operation.
 Measurement flow in TOR sharing solution
DVSWR measurement is a periodical task when activated by ANTPI

message. Below is the sequence diagram of TOR sharing for DVSWR.
The measurement sequence flow can be divided into two parts:

control part and one shot DVSWR measurement.
The “control part” acts as a scheduler which arranges DVSWR

measurement on each antenna and each frequency band in fixed
period (5 seconds).
The “one shot DVSWR measurement” represents a concrete

execution on a specific antenna and frequency band.
Below is an abstracted timing graph of “one shot DVSWR

measurement”. Blue rectangle represents RSW job, and yellow
rectangle represents DPCPRI job.
Ericsson Internal

2023-12-21 PF24
Note:
1. Parameter “t2” is the time before RFS at which DPCPRI should

config the trigger of RTS data capture. May be 50us for example
2. Parameter “t3” is carrier type specific. It means RTS capture

DVSWR data at a time delay from RFS. It’s calculated based on
parameter from database antennaInterface.
3. The DPD idle time for one DVSWR measurement would be about
0.31ms.
5.15.28.1.3[7.16.6.1.3] Interaction on other features
Generally speaking, DVSWR TOR sharing solution is the TK down

version for legacy DVSWR function. Because DPD feedback data path
will be interrupted from time to time by DVSWR measurement, this
may impact on DPD performance.
Verification on EVM and ACLR is necessary to ensure compliant with

internal requirement.
5.15.29[7.16.7] New/Enhanced Functions for FDD Radio 4466 and MR9002-SP4
5.15.29.1[7.16.7.1] Deep sleep for Visby
This is a Visby Radio specific solution for “deep sleep” with power
consumption (in deep sleep mode) requirement “down to around 60w”.
Radio power consumption is a big problem for customer, especially

when there have rolled-out many 5G sites, but few 5G users. They
hope the site can be in power saving mode.
Ericsson Internal

2023-12-21 PF24
There is no carrier active when radio in idle mode. Some customers

choose to shut off the power to the radios at night. Shutting down the
power completely reduces the life time of the radio, and may result in
unwanted problems to get the network up and running smoothly when
traffic demand comes back. To avoid such situation, a deep sleep
feature would be beneficial. It is assumed that the start-up time
requirement to wake-up after Deep Sleep shall be similar to the start-
up time after Power-ON.
This function is focused on radio unit. It’s required designers to

evaluate the impact of usage of reset pins (on radio components).
This function will use BCI message to communicate with DU.
5.15.29.1.2[7.16.7.1.2] Actions
5.15.29.1.2.1[7.16.7.1.2.1] Actions to enable Deep Sleep:
1. stop supervision
2. suppress fault
3. turn off LNA
5. turn off RALF
6. turn off TRXIC

Ericsson Internal

2023-12-21 PF24
During Deep Sleep, Radio should report board temperature to DU

periodically. DU should determine whether or not Radio need to be
waked up according to the reported temperature to prevent it to be in
an abnormal state (e. g. cannot be waked up because of low
temperature).
5.15.29.1.2.2[7.16.7.1.2.2] Actions to disable Deep Sleep:
To recover from deep sleep mode, SP8881 is followed to use the

legacy radio restart procedure.
Re-initialize the whole radio can avoid unexpected errors between SW

modules, like the dependency between modules and wrong sequency
is taken. This is also the less effort solution.
The radio components (PA, LNA, etc.) are chosen to be set in reset
mode. This help to reduce power consumption as well as heat
dissipation.
The digital part of RU was also evaluated. The saving of function

module inside Mongoose would be less than 1W. It’s not worthy of
much workload on it for just such little saving of power consumption.
When connecting to multi DUs, Radio will go into Deep Sleep only if
Radio receive request from all DUs. Radio will wake up from Deep
Sleep when Radio receive wakeup request from either one DU.
5.15.29.1.3[7.16.7.1.3] Interaction on other features:
There couldn’t have any traffic on RU when it can be set in “Deep

Sleep” mode, and thus no temperature-related backoff functions
running. So this function does not impact such types of features on
RU.
Function “Deep Sleep” support both G2 and G3.

Ericsson Internal

2023-12-21 PF24
5.15.29.2[7.16.7.2] Quasi Dynamic PA VDD
This function is to adjust PA drain voltage (VDD) based on PA

nonlinearity estimation to reach good energy efficiency while still
meeting linearity requirement.
PA VDD value is selected to cover batch variation, aging effects and

full throughput requirement under a certain power class, which
reduces PA energy efficiency in many scenarios.
In RU, PA consume more than half of the total power. Therefore, the
energy efficiency of PA is important to the overall energy efficiency of
RU. One of the most effective methods to improve efficiency of PA is
to change its drain voltage based on the traffic.
The logic behind this function is to utilize the margin we have in our
products to increase the efficiency of the final PA while the radio
performance is still kept. The architecture of dynamic PA VDD voltage
adjustment is illustrated in Figure below.
TOR
DAC &
To
Data DPD Analogue PA
Circuits Filter
Additional Control DC
Converter
Figure Architecture of dynamic voltage adjustment
5.15.29.2.2[7.16.7.2.2] Database Parameters used in this functions:
paVddQdEnable: function enable for TXL. 1: Enabled 0: Disabled
Location: [sysDataParam]
paVddQdUpdate: function enable for Radio SW. 1: Enabled 0:

Disabled
paVddQdPwrLimit: the lowest TX power for PaVddQd

Ericsson Internal

2023-12-21 PF24
pavddSetStep: tuning step for dynamic PA VDD
Location: [PaSwDb]
paVddQdCPRGainMax: CPR gain max limit
Location: [ sysDataParam]
paVddQdCPRGainMin: CPR gain min limit
paVddQdReportInterval: The min interval between two reports from

Txl to RadioSw.
5.15.29.2.3[7.16.7.2.3] Actions:
This function is implemented in DP, TXL and RSW. Each part takes its
own actions according to below figure.
Dynamic PA VDD adjustment
This function decreases PA VDD when there is margin in PA.
Step 1: DP calculates peak and average gain for each branch.
Step 2: TXL periodically poll peak gain values.

Ericsson Internal

2023-12-21 PF24
These values will be compared with peak gain min & max values, and
sends out requests to RSW. These requests could be: decrease PA
VDD, hold PA VDD or increase PA VDD.
The actions for each branch is sent to PA Service

Module (via TxBranchCtrl) by txlRequiredInterface.
TXL must wait paVddQdReportInterval between two requests for each

branch.
When there is a fault from DPD, TXL will trigger RSW to do the PA
VDD offset recovery action.
Step 3: In RSW, when the first carrier is activated, PA

VDD supervision would be started in PaSrv module. This supervision
would stop after the last carrier is released.
It saves the requests from TXL in every paVddQdPeriod, and get the
final decision for the PA VDD setting.
5.15.29.2.4[7.16.7.2.4] Interaction with legacy functions:
The Dynamic PA VDD function may interact with other legacy

functions, for example, PA VDD temperature/frequency compensation
(a legacy PA Control function).
The adjustment of PA VDD voltage may be combined for both

functions. To avoid ping-pong effect, the interval of Dynamic PA VDD
would be set 15-30 seconds, longer than PA VDD
temperature/frequency compensation period (1s). Even the tuning
step for increase request and decrease request can be adjusted
separately to mitigate risk to PA (the decrease step can be larger than
increase step).
Dynamic PA VDD have dependency on DPD functionality. If the DPD

is in idle state or recalibration state, this function should not update PA
VDD value.
This function support both G2 and G3.

Ericsson Internal

2023-12-21 PF24
5.15.29.3[7.16.7.3] Dynamic latency handling
This function is for the System Improvement proposed to RBS Time

Alignment for C1/CPRI based RUs, with use of new time alignment
model 3.0 that was introduced for C2/eCPRI based RUs with internal
CPRI links as part of SP655. More details could refer to MR7777.
In legacy radio always report worst case delay with a large margin at
carrier setup in order to always be able to setup a new carrier without
impacting timing of carrier that are already active.
With the introduction of NR (with large flexibility of CarrierTypes) and

eCPRI/C2 fronthaul with packet delay variations, there is a need to
optimize the time alignment settings for a SectorCarrier and have
more dynamic latency handling.
The new time alignment model was introduced (SP655) in

configurations with C2 based AAS radios (with internal CPRI) and was
driven by numerous TRs in the area in legacy and the specific need
from new carrier types for NR (over TR-DCI).
This new time alignment model will handle the NR and LTE dynamic
latency over C1 RUs.
5.15.29.3.2[7.16.7.3.2] Database Parameters updated in this function:
capIqMsgSupport: Capability CARRIER_TYPE
IQ_MSG_FS_INFO_FIXED 0x0004 (0000 0100)
reportingCap: Reporting Capabilities
TIMING_INFO 0x10000 (0001 0000 0000 0000 0000)
5.15.29.3.3[7.16.7.3.3] Interaction on other features:
This function introduces a new time alignment model so that it will

affect the implementation of radio SW.
Ericsson Internal

2023-12-21 PF24
5.15.30[7.16.8] Radio 4456
Radio 4466 is the functional baseline for Radio 4456. No new/updated

function.
Branch mapping can be seen in HW IWD.
Some highlights:
 Radio 4456 uses one DC/DC solution.
 No function impacts. SW needs to do corresponding

adjustment.
 TOR sharing
 One 4:1 switch handle 4 branches. The other 8

branches: 2 sets of two 2 to1 switches that handle 1 of the
signals from the PAB as well as 2 signals from the ROA. In
the figure below, left side is Radio 4466 B1 B3 B7 solution,
right side is Radio 4456 B1C B3J B75C solution.
 No function impact, database impact. DP need to do

corresponding configuration.
 For MR9609-SP1 prdType_1.5.x is reserved for Visby Radio 4456

B1CB3JB75C
 LDMOS instead of GaN transistor in the platform
 No function impact
 EnE feature
 Quasi dynamic VDD inherit from Radio 4466
 Deep sleep inherits from Radio 4466

Ericsson Internal

2023-12-21 PF24
5.15.31[7.16.9] MR9002-SP15 7CC per port on B3 UL for Visby Radio
5.15.31.1[7.16.9.1] Function description
The current design of Visby Radio 6626 B1B3 and 4466

B1B3B40/B41 is required to support up to 4 DL and 5 UL GSM
carriers per band per port, up to 6 DL and 6 UL carriers per band per
port for WCDMA/LTE/NR/ESS RAT types and mixed mode
configurations.
Now the new requirement from SPM for mixed mode GSM support on
B3 for Visby 6626 B1B3 is: support up to 6 GSM TRX'es per 2T2R
sector (up to 7CC (6 GSM + 1 LTE) per port per B3 UL). The
requirement of mixed mode GSM support on B3 for 4466
B1B3B40/B41 is: for single sector 4T4R – support up to 12 GSM
TRX'es per sector, for split sector 2 x 2T2R – support up to 6 GSM
TRX'es per sector (up to 7 CC (6 GSM + 1 LTE) per port per B3 UL).
5.15.31.2[7.16.9.2] Database Parameters used in this function
The max number of UL carriers per port on B1 has to be reduced from

6 to 5 to shift one filter branch per port from B1 to B3, in order to
support 7CC on B3 UL for Visby. To stay symmetric, max DL number
of carriers per port on B1 will be reduced to 5 as well.
So we just need adjust filter branch mapping and capability report to

support such feature.
DB changed in sysDataParam
DB changed in hwResourceConfig
ulA/bandId0/carriers U8 24, 25, 26, 27, 28

Ericsson Internal

2023-12-21 PF24
ulB/bandId0/carriers U8 30, 31, 32, 33, 34
ulC/bandId0/carriers U8 60, 61, 62, 63, 64
ulD/bandId0/carriers U8 54, 55, 56, 57, 58
ulE/bandId0/carriers U8 6, 7, 8, 9, 10
ulF/bandId0/carriers U8 0, 1, 2, 3, 4
ulA/bandId1/carriers U8 29, 36, 37, 38, 39, 40, 41
ulB/bandId1/carriers U8 35, 42, 43, 44, 45, 46, 47
ulC/bandId1/carriers U8 65, 66, 67, 68, 69, 70, 71
ulD/bandId1/carriers U8 48, 49, 50, 51, 52, 53, 59
ulE/bandId1/carriers U8 11, 18, 19, 20, 21, 22, 23
ulF/bandId1/carriers U8 5, 12, 13, 14, 15, 16, 17
5.15.32[7.16.10] MR9268-1 LTE GB NB-IoT coexistence with ESS on Visby

Radios
5.15.32.1 Function(Feature) description
The Ericsson has provided NB-IoT service in legacy LTE deployment.

Many operators are planning to support NR, using the ESS solution
(dynamic spectrum sharing). The smooth spectrum migration to NR in
LTE requires the coexistence of NB-IoT and ESS.
MR7602 covers Warp and Xenon based radios, feature on BB

G2/G3/G3.1 is ready. Visby radios which are radon 1.1 based also
need to support this feature, MR7602 will be the baseline.
5.15.32.2 Database Parameters used in this function
Due to the re-design for DL filters, need update common database for
Radon filter configurations:
radonDlFilters_essFdd100_Id1/radonDlFilters_essFdd150_Id2/
radonDlFilters_essFdd200_Id3
Ericsson Internal

2023-12-21 PF24
5.15.33 MR9002-16 GSM 28M IBW Supporting on B1B3
5.15.33.1[7.16.10.1] Function (feature) Description
This feature is specially requested by Bharti Customers, on Visby 6626 B1B3.

For covering wider GSM IBW, it is requested to expand the GSM IBW (mixed
mode) from 20MHz to 28MHz. On Visby now, the single mode of GSM is not
supported yet, so the verifications are based on GSM mixed with LTE/NB SA
and so on.
Because of R1D and R2C versions are deployed / planned to be deployed on

Bharti sites and the separate tests are needed to be considered. From SW
perspective, only database parameter needs to be modified. However, from
HW perspective, the performance of GSM IBW 28M supporting needs to be
covered and ensured. It will involve the debugging of DRT table from
Integration team, power backoff may be considered depending on
EVM/OBUE performance and the limitations need to be clarified as well.
5.15.33.2[7.16.10.2] Database Parameters used in this Function
It is considered in ‘sysDataParam’, the GSM IBW needs to supports 28M

according to the new request.
‘capabilityDlBwNarrow’ is accordingly to be expanded till 40MHz (But we

just claim performance of GSM carriers within 28MHz could be guaranteed)
5.15.34[7.16.11] MR9002-SP13 SHP Enabled on Visby 6626 B1B3 and 4466 B1B3B7
5.15.34.1[7.16.11.1] Function (Feature) Description
Based on the previous Medley study result, SHP has been enabled on
BandVII of 4466 B1B3B7 (On band VII, it is GaN Boost + SHP
implementation). Voltage drop issue is found on B1B3 which is the hinder of
SHP implementation. After BOM update on 6626 B1B3 (>=R2D) and 4466
B1B3B7 (>=R1E), it is HW prepared to enable SHP.
From Function’s perspective, like GaN Boost, SHP only functions when low
traffic mode, which requires TM2.0a Env for performance test of EVM. What’s
more, OBUE has also been considered under TM3.1 Env. As for the dynamic
traffic mode, the SHP enabled and disabled scenario will be triggered, which
could be realized by Node FV Env, via different AILG controlled. As well as
the power consumption data could be obtained, compared with GaN Boost
enabled.
One noteworthy part of this feature implementation is GaN Boost Switch

supporting on different bands even in one radio (4466 B1B3B7). More
precisely, it is requested SHP+GaN Boost on B7, but SHP only on B1B3,
which means GaN boost mode needs to be flexibly supported on and off for
different HW versions and different bands. Since GaN Boost mode needs to
be accordant with all bands, when the switch is controlled in Paswdb.
Ericsson Internal

2023-12-21 PF24
The solution for this issue in this SP, TRX Ctrl create another parameter
which is stored in DRT table, which shares the higher priority to determine
GaN Boost mode should be on or off, depending on the current HW version
and band info. The solution has been realized by TRX Ctrl and SW
adaptation, which is verified by INT team.
Accordingly, it needs to be clearly aware that, Visby Middle-band radios has

different SHP supporting solution, which is distinguished by HW versions.
5.15.34.2[7.16.11.2] Database Parameter used in this Function
The database parameter modification/addition mainly includes new parameter

(/general/ganBoostMode) introduction to DRT table due to the GaN Boost
switch requirement. And SW internal Database made some adaptation as
well.
The final code logic will be,
If /ganBoostMode exists in paSwDb AND its value is 1:
If /general/ganBoostMode exists in DRT:
If its value is 0:
Disable GaN boost
Else if its value > 0:
Enable GaN boost
Else:
Enable GaN boost
Else:
Disable GaN boost
Note: the GaN Boost/SHP solution will be determined jointly by parameters in

Paswdb and DRT.
Paswdb: DRT: Result

ganBoostMode /general/ganBoostMode
1 1 Enable
0 1 Disable
1 0 Disable
1 1 Enable
For each HW versions, the following table could be referred.

Ericsson Internal

2023-12-21 PF24
Radio KRC R-state SHP GaN

Radio 6626 B1B3 >=R2D B1: Enable B1: Disable
B3: Enable B3: Disable
<=R2C B1: Disable B1: Enable
(including B3: Disable B3: Enable
R1x)
Radio 4466 >=R1E B1: Enable B1: Disable
B1B3B7 B3: Enable B3: Disable
B7: Enable B7: Enable (same
bias boost as R1D)
R1D B1: Disable B1: Enable
B3: Disable B3: Enable
B7: Enable B7: Enable
5.16[7.17] HW Abstraction Layer Interface (HALI)
N/A, never break HALI backward compatibility.
5.17[7.18] Site Support Software
N/A
5.18[7.19] TRXCTRL
In general, the TrxCtrl is a deliverable product in the Radio Function,

which contains the Ericsson Digital Pre-Distortion linearization (DPD)
together with its configuration, HW and SW support (starting,
stopping and supervision). It is a defined interface between the radio
SW application, FPGA and/or ASIC, and the radio HW, to control and
supervise the DPD functionality.
The TrxCtrl is basically just a label/tag that defines a complete

baseline of top level CXA, which points to several SW and HW
products for DPD implementation, shown as the following (note: this
list is a general description applicable for various types of radios, i.e.
not specifically dedicated to the 6626):
 The TxL is the SW module of TrxCtrl, acting as an interface

between the radio SW application and the TX Linearization
function, to control and supervise the linearization function.
 The DPD is the algorithm that realizes the TX linearization.
 The DPD firmware (FPGA or ASIC) is the place, where the

DPD algorithm is embedded.
Ericsson Internal

2023-12-21 PF24
 The DPL (Device Processor for Linearization) is the fast

control layer between the TxL and the DPD, and it handles the
DPD state machine.
In the Visby platform there will be a lot of challenges.

 First time running FDD and GSM in Radon
 Palau, using ADI IQ-compensation when offsetting the band
with NCO:s in Palau
 Palau and GSM
 Noise limitations in ORx when running wideband
 Noise in TX?
 How the modularization will impact
 GaN support
 To secure stability and enhance performance power-
information is needed both in TD and FDD. To get the
intended performance from Rn1.1 SBPR would be required.
Some tests with only using internal-power measurements has
shown that they could be used but with some degradation in
performance.
 GSM Frequency hopping
 This feature is currently under development. There
exists an interface in DP to configure each branch.
When a branch configuration is fully configured and
activated, DP CPRI decode TX CTRL IQC messages and
writes to the frequency hopping hardware block. More
information about this will be available when the
feature is complete.

 Both FDD and TDD in the same radio, this can have impact
on leakage and strobes
 Things we haven’t foreseen when running FDD/TDD and
triple band
None of these challenges are clear right now, most will be understood
as soon as HW is up and running.
The gain-setting and NCO:s in the tor chain can be controlled by

GPIO:s, most probably we also need to do same adaptation in DPL.
5.18.1[7.19.1] TRXCTRL Impact on MR9002-SP4

 support Quasi-dynamic Vdd
o TrxCtrl impact. Difficult to say at this stage what
exactly needs to be done and also hard to predict any
estimation workload wise. Work is hence already
ongoing
 support Deep sleep
Ericsson Internal

2023-12-21 PF24
oTrxCtrl impact. Difficult to say at this stage what

exactly needs to be done and also hard to predict any
estimation workload wise. Work is hence already
ongoing.
 Tor sharing for DVSWR (TA study ongoing, Fernando and Peter
are involved)
o Mostly DP CPRI impact. Difficult to say at this stage
what exactly needs to be done and also hard to predict
any estimation workload wise. Work is hence already
ongoing
[7.20] (DL filter Apostolos)DL ASIC
nrFdd250_Id5, nrFdd300_Id12 and nrFdd400_Id13 can be utilised for

products using Radon 1.1. Visby Radio build label(CXC1123339_38)
shall include the filer files. This is reviewed with Chakradhar
Ghantasala.
5.19[7.21] UL ASIC
nrFdd250_Id5, nrFdd300_Id12 and nrFdd400_Id13 has been defined

for Radon Ul filters. Visby Radio build label(CXC1123339_38) shall
include the filter files. This is reviewed with Naga Thejus
Mruthyunjaya.
5.20[7.22] Radio XCS platform
5.20.1[7.22.1] Radio Common
5.20.1.1[7.22.1.1] PFA cease
Legacy XCS systemization is that each O&M link uses a dedicated

ECP buffer and inband handling also uses a dedicated ECP buffer. On
Visby, there could be 4 O&M links, so one possible solution is that 2
O&M links share one ECP buffer then there’s free ECB buffer
available for inband handling.
5.20.2[7.22.2] Radio 6626
5.20.2.1[7.22.2.1] Pboot
Based on ZU4, pboot reuse radio8863-pboot since radio should have

the same interface (MIO cfg, DDR cfg, PLL cfg, etc) at PS side.
Ericsson Internal

2023-12-21 PF24
5.20.2.2[7.22.2.2] Bootimage
Based on ZU4, bootimage reuse radio8863-bootimage (same flash

layout, same ram size. same bring up steps) and bootimage should
support fpga version select.
5.20.2.3[7.22.2.3] xcs-plf
Based on ZU4, plf will reuse xcs-plf(MDC) wrl18-radio8863-plf, with

same BSP, delivery , but a new MACHINE_VARIANT.
For radio6626 MACHINE_VARIANT configurations:
 new radio6626 svl(pinmux) will be added in xcs-board.
 new radio6626 ltuscript and fpga version for u-boot-script-lm in

xcs-board
 additional radio6626 dts in meta-xcs
 additional radio6626 dto in meta-xcs
 additional xcs-nereus.bb in meta-xcs for Visby FPGA.
 to support different FPGA version with radio8863, there is an

additional OVERRIDE variable fpga-nereus.with that XCS will
use fpga-nereus. Without will use fpga-pegasus.
5.20.3[7.22.3] FDD Radio 4466
5.20.3.1[7.22.3.1] Pboot
new pboot mongoose-radio4466-pboot, Bitstream and Build project is

needed for that.
 Bitstream: Mongoose bitstream is one essential input for building

pboot. The bitstream is delivered by Mongoose ASIC team and
highly depends on the hardware design. Visby hardware/digital
team should provide Mongoose ASIC team with all the
fundamental parameters that will impact the bitstream.
5.20.3.2[7.22.3.2] Bootimage
We can expect that FDD radio4466 can use the common mongoose
bootimage which should be able to handle different DDR layout. Uboot
environment will provide extra parameters to bootimage for flexible
DDR layout support.
Ericsson Internal

2023-12-21 PF24
5.20.3.3[7.22.3.3] xcs-plf
Radio4466 will reuse mongoose-plf(MDC) which will be shared by all

the mongoose based products.
It should be noted that MACHINE_VARIANT “radio4466” should be

defined in the top build, instead of xcs build.
For FDD radio4466 MACHINE_VARIANT configurations:
 Linux device tree: Mongoose-plf already provides a platform

level common device tree for mongoose HPS and Fabric part.
FDD Radio4466 will define which components should be
enabled basing on that common base. FDD Radio4466 will also
add dtb overlay for radon1.1, similar to what have been done in
ZU4 track.
 Mama configuration file: FDD Radio4466 will add mama

configuration files to define what XCS daemons and applications
will be launched and how, similar to what have been done in
ZU4 track.
 SVL: FDD Radio4466 will add needed SVL (XCS data base),
similar to what have been done in ZU4 track.
 LTU init script: LTU init will be performed under Linux, instead of
under uboot which is the case for ZU4 track.
 Drivers: FDD Radio4466 will have a new driver for mmi button,
gpio based.
 Rootfs: For AAS and classic radios, different XCS packages will
be included in root file system. So flexible package select will be
implemented in FDD radio4466.
5.21[7.23] RICR
5.21.1[7.23.1] RICR SW
- SW Interfaces
RICI, RICRAI, LTUI interfaces keep the same.
- CPRI link setup
Visby will have 4 external CPRI links and support cascading. RICR
SW will interact with ASIC Radon1.1 for Visby radios.
o Support 4 external CPRI links

Ericsson Internal

2023-12-21 PF24
1. Since only 1 of 4(0-3) in 8 CPRI ports could be selected

for external reference clock selection according to
Radon1.1 UG, make sure that CPRI port 0-3 are used
for Visby radios.
2. Current RICR SW only supports external reference

clock switch for 2 ports, new implementation is needed
for Visby radios. The implementation will be to choose
Main0 and Main1 with the best available CPRI ports. If
some ports have the same clock quality, then port with
smaller number will have higher priority.
o Setup of slave CPRI ports
All ports are setup as slave mode after RICR SW is

initialized. Implementation for ASIC Radon1.1 needs to be
done.
o Setup of master CPRI ports
Implementation of master CPRI link port setup is needed

for Visby radios.
o Cascading
Some port(s) is(are) asked to setup as master mode when

receiving RICI_START_CPRI_LINK#_REQ from RICM.
Besides, some new configuration on IQC_X and ECP_X for
cascading needs to be implemented. Please note that
RICR needs to know the cascading relation between the
slave and master port pair.
o Line rates support
Slave Master
AUBOOT 2.5G 2.5G
APPLIC 5 line- 4 line-

rates: rates:
2.5G, 2.5G,
4.9G, 9.8G,
9.8G, 10.1G,
10.1G, 24.3G
24.3G
Note:
Note: 4.9G is
4.9G is for not
XMU03 needed
Ericsson Internal

2023-12-21 PF24
1. Since Applic master doesn't need to support 5 line-rates, no

impact on RICR SW for speed negotiation algorithm.
2. Since the bitrates are used from board parameters and RICR
SW chooses the bitrates from minimal to maximum, 4.9G
should be skipped for applic master mode, “master-skip-br” will
be added in BP.
- Delay handling
To be implemented as legacy delay values, such as hard delay,

SerDes delay, RTD delay, etc.
For RFS/BFN difference delay value, RICR SW will support

calculation between any 2 CPRI ports based on Radon1.1, the 2
ports’ number used are portX and portY in
RICI_GET_RFS_DIFF_REQ.
- SFP info handling
Keeps the same.
- Fault handling
Keeps the same.
5.21.2[7.23.2] RICR SW dependencies
- RICR SW only starts CPRI FSM management after Radio (app)

SW initializes it by RICR_initRICR.
- CPRI FSM needs to know the LTU locked status from Radio (app)
SW or LTU server process.
- RICR SW depends on the board parameters published by digital

SW for some information such as retimer
configuration/parameters, bitrates, SerDes tuning parameters, etc.
5.21.3[7.23.3] RICR SW SBC (Function Test)
- RICR testapp SW development
Mainly on LTU server.
- Test configuration:
1*BB6648, 1*BB6630, 2*radio6626, 6*SFP28s at least, 4*SFP28s or

SFP+s, 5*Optical fibers
Power supply, FIC boards*2, serial IP/ports

Ericsson Internal

2023-12-21 PF24
- Test suites/cases:
RICR regression test
RICR stability test

Ericsson Internal

2023-12-21 PF24
[8] (HWSYS Jerry Yang T)Impact on HW Products
5.22[8.1] ERS HW Solution
5.23[8.2] Radio CRS requirement, BL16A and forward
5.23.1[8.2.1] Radio CRS for RRU MSR FDD and TDD Systems, General and Inband
Requirements (incl. PIMC) exist in BL16A.
The requirements of the regulatory authorities /regions are covered inband

CRS.
Further details are available on this link rsp-66637142-00000293
5.24[8.3] Radio CRS for RRU MSR FDD and TDD Systems, Out-of-band
Requirements exist in BL16A.
The requirements of the regulatory authorities /regions are covered in CRS.
Complete list of requirements can be found on rsp-66637142-00000293
5.24.1[8.3.1] Visby 6626 B0AB28
The requirements of the regulatory authorities /regions are: LATAM, Brazil,

Africa, APAC, India, SEA, Australia.
The regulatory requirement for ACMA is preliminary => RE code is needed

and ACMA can´t be declared as regulatory compliance in UDB.
5.24.2[8.3.2] MR9002-SP16 - GSM IBW 28MHz Supporting on Visby 6626 B1B3
MR9002-SP16 - GSM IBW 28MHz Supporting on Visby 6626 B1B3

Characteristic Radio specification, CRS, TRM requirement to be updated as
below:
Ericsson Internal

2023-12-21 PF24
5.24.3[8.3.3] ERS Radio Configurations
Radio 6626 and FDD Radio 4466 shall be supported with Radio Gateway
R608 and Radio Gateway R308, once they are released. Current plan as on
2021.03.18 is to release Radio Gateway R608 in July 2021 and Radio
Gateway R308 in September 2021.
5.24.3.1[8.3.3.1] Radio 6626 (updated 2020-12-01)
Radio 6626 shall be supported with existing RBBs, described in

chapter 9.1.1.1 and with new RBBs described in chapter 9.1.1.2
The following rules shall be taken into consideration when connecting

the Radio to 1 node, 2 nodes as well as for star and cascade
configurations.
0. According to the latest findings by the project, Data port 3 cannot be

used in 21.Q3. This is due to the ECP_BUF function that needs to
have Data 3 reserved for PFA function. This limitation shall be uplifted
in 21.Q4 together with the 2nd PRA. Therefore, all of the RBBs that are
defined to use port number 3 cannot be used in 21.Q3.
1. Radio 6626 can be connected to a node with 1, 2, 3 or 4 CPRI.

Some limitations apply for DUG 20 and DUW v1 and DUW v2, where
only 1 CPRI cable can be used.
2. Any port on the radio can be used for connections to a node.

Exception to that rule is DUW v1 and DUW v2, where only Data 1 is
supported and DUG 20 where either Data 1 or Data 2 is supported.
3. Cascade configurations can be supported with Data 1 connected to

a node and the cascaded radio to Data 2, or vice versa, Data 2
connected to a node and the cascaded radio to Data 1. This is the
same configurations as with the legacy, 2 Data ports radios.
Additionally, a node can be connected to Data 3 and the cascaded
radio shall be connected to Data 4, or vice versa, node can be
connected to Data 4 and the cascaded radio shall be connected to
Data3.
4. For mixed mode configurations from 2 nodes, one node has to use
Data 1 and the other has to use Data 2. This rule is determined by
sync, which works only between Data 1 and Data 2. Additional ports
can be used be either of the nodes or by both nodes, one port each.
Ericsson Internal

2023-12-21 PF24
5. For configurations with 2 x Radio 6626 in one RBB and 2 nodes for
the mixed mode. One node shall be connected to Data 1 on Radio 1
and Data 1 on Radio 2, while the second node shall be connected to
Data 2 on the 1st Radio and Data 2 on the 2nd Radio. In that
configuration, cascading is not supported, since this would require
Data 2 usage as cascaded port for a connection to Data 1. And Data 2
is already used by the 2nd Node. Data ports 3 and 4 on Radio 1 and
Radio 2 can be used for connections towards node 1, or node 2 or
node 1 and node 2.
6. For configuration described in bullet 5, If one of the radios is used

only by 1 node, this particular radio can be used in a cascade
configuration. For example if node 1 is connected to Data 1 on Radio
1 and Data 1 on Radio 2 and node 2 is connected to Data 2 on Radio
1 only, Radio 2 can be cascaded from Data 2 to another 3rd radio.
7. For a configuration with 2 x Radio 6626 in RBB, if the second Radio

is connected in a cascade configuration to the 1st Radio, only 1 link
between Radio 1 and Radio 2 can be used. For example if 1st Radio is
connected with Data 1 and Data 3 – Data 2 or Data 4 can be used for
connection of the 2nd Radio towards 1st Radio.
8. For configurations with 1 x Radio 6626 connected with 3 x CPRI

towards one node, the 4th CPRI port can be used for cascading.
Please note cascading rules from bullet 3.
9. Cascading from a Radio can be configured only on 1 of the ports.

For example, id Radio 6626 is connected with 2 x CPRI cables, 1st
cable to Data 1 and 2nd cable to Data 3, only Data 2 or Data 4 can be
used for cascading purposes.
10. Even though Radio 6626 has 4 CPRI ports, currently it can be
connected only to 2 nodes. Configurations with more than 2 nodes
require a new MR.
For MR9002-SP4, additionally cascade options will most likely be

released with SP2 of MR9002 and shall be treated as legacy for
MR9002-SP4.
5.24.3.1.1[8.3.3.1.1] Existing RBBs
All of the existing RBBs are defined in a way, that they use only Data 1
and Data 2 port. For the time being, those pictures are not going to be
changed. The work will be done together with the release of Radio
6626 on the node level. Instead, numbers next to Data ports shall be
considered as any 2 ports on the Radio. For the rules which ports that
can be used, see chapter 9.3.1. For RBB specific rules, see the
description under the diagram of each RBB.
1. RBB 44 1N
Ericsson Internal

2023-12-21 PF24
Applicable rules from chapter 9.1.1: 1, 2, 3, 4, 7, 9, 10
2. RBB 44 1P
RI Link RF Branch
1: TX A / RX A
Node 1 Data 1 C
Data 2 D
3: TX C / RX C
Data 1 C
Node 2 or
Data 2 D
cascade
RBB44_1P
3. RBB 44 2S
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
1: TX A / RX A
Data 1 A
Node 1
Data 2 B
3: TX C / RX C
Data 1 A
cascade Data 2 B
RBB44_2S
Applicable rules from chapter 9.1.1: 1, 2, 3, 4, 5, 6, 9, 10
4. RBB 44 2T
RI Link RF Branch
1: TX A / RX A
Data 1 C
Node 1
Data 2 D
3: TX C / RX C
Data 1 C
cascade Data 2 D
RBB44_2T
5. RBB 22 1F
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Node 1 Data 1
1: TX A / RX A
A
B
Node 2 or Data 2
Cascade
Ge13144
Applicable rules from chapter 9.1.1: 1, 2, 3, 4, 9, 10
6. RBB 22 1G
RI Link RF Branch
Node 1 Data 1
1: TX A / RX A
C
D
Node 2 or Data 2
Cascade
Ge13145
7. RBB 22 1H
RI Link RF Branch
Node 1 Data 1
1: TX A / RX A
E
F
Node 2 or Data 2
Cascade
Ge13146
8. RBB 22 2K
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Data 1
1: TX A / RX A
A
Node 1 Radio 1 2: TX B / RX B
B
Data 2
Ge14144
Notes – RBB can be also used in cascade configurations. Picture will be modified for
the release. See rules in 9.1.1.
9. RBB 22 2L
RI Link RF Branch
Data 1
1: TX A / RX A
C
D
Data 2
Ge14145
10. RBB 22 2M
RI Link RF Branch
Data 1
1: TX A / RX A
E
F
Data 2
Ge14146
Ericsson Internal

2023-12-21 PF24
11. RBB 11 1C
RI Link RF Branch
Node 1 Data 1
1: TX A / RX A
Radio 1 A
Node 2 or
Data 2
Cascade
Ge13140
12. RBB 11 1D
RI Link RF Branch
Node 1
Data 1
1: TX A / RX A
Radio 1 B
Node 2 or Data 2
Cascade
Ge13142
13. RBB 11 1E
RI Link RF Branch
Node 1
Data 1
1: TX A / RX A
Radio 1 C
Node 2 or Data 2
Cascade
RBB11_1E
14. RBB 11 1F
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Node 1
Data 1
1: TX A / RX A
Radio 1 D
Node 2 or Data 2
Cascade
RBB11_1F
15. RBB 11 1G
RI Link RF Branch
Node 1
Data 1
1: TX A / RX A
Radio 1 E
Node 2 or Data 2
Cascade
RBB11_1G
16. RBB 11 1H
RI Link RF Branch
Node 1
Data 1
1: TX A / RX A
Radio 1 F
Node 2 or Data 2
Cascade
RBB11_1H
17. RBB 11 2A
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 A
Data 2
Ge13141
Ericsson Internal

2023-12-21 PF24
18. RBB 11 2B
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 B
Data 2
Ge13143
19. RBB 11 2C
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 C
Data 2
RBB11_2C
20. RBB 11 2D
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 D
Data 2
RBB11_2D
21. RBB 11 2E
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 E
Data 2
RBB11_2E
22. RBB 11 2F
RI Link RF Branch
Data 1
1: TX A / RX A
Node 1 Radio 1 F
Data 2
RBB11_2F
5.24.3.1.2[8.3.3.1.2] New RBBs
Data port numbers are on purpose not shown on the RBB diagrams.
Instead letters are used to indicate that those or different port
numbers. In order to determine which port that can be used in a
specific RBB, mixed mode configuration with 2 nodes or in a cascade
configuration, see rules in chapter 9.1.1.
1. RBB 44 1S
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
1: TX A / RX A
Node 1 Data A E
Data B F
3: TX C / RX C
Data C E
Node 2 or
Data D F
cascade
RBB44_1S
Applicable rules from chapter 9.1.1: 0,1, 2, 3, 4, 7, 9, 10
2. RBB 44 2W
RI Link RF Branch
1: TX A / RX A
Data A E
Node 1
Data B F
3: TX C / RX C
Data C E
cascade Data D F
RBB44_2W
Applicable rules from chapter 9.1.1: 0,1, 2, 3, 4, 5, 6, 9, 10
3. RBB 44 4C
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Data A 1: TX A / RX A
A
Data B
Node 1 Radio 1
Data C 2: TX B / RX B
Data D B
Data E 3: TX C / RX C
A
Data F
Node 2 or Radio 2
cascade Data G 4: TX D / RX D
B
Data H
RBB44_4C
Please note that for cascade configurations, only one of the Data ports on each of the
radio can be used, either Data 2 or Data 4.
Applicable rules from chapter 9.1.1: 0, 1, 2, 3, 4, 5, 6, 9, 10
Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 4C + RBB 44 4C can not be
suppor.ted.
4. RBB 44 4D
RI Link RF Branch
C
Data B
Node 1 Radio 1
Data D D
C
Data F
Node 2 or Radio 2
D
Data H
RBB44_4D
Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 4D + RBB 44 4D can not be
supported..
Ericsson Internal

2023-12-21 PF24
5. RBB 44 4E
RI Link RF Branch
E
Data B
Node 1 Radio 1
Data D F
E
Data F
Node 2 or Radio 2
F
Data H
RBB44_4E
Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 4E + RBB 44 4E can not be
supported.
6. RBB 44 6A
RI Link RF Branch
A
Data B
Data C Radio 1 2: TX B / RX B
Node 1 B
Data D
A
Data F
Node 2 or Data G
B
cascade Data H
RBB44_6A

Note:
Limitation only valid for Radio released on 21.Q3. Only Node 1 can be supported. Node
2 or cascade can not be supported.
Ericsson Internal

2023-12-21 PF24
7. RBB 44 6B
RI Link RF Branch
C
Data B
Node 1 D
Data D
C
Data F
Node 2 or Data G
D
cascade Data H
RBB44_6B

Note:
8. RBB 44 6C
RI Link RF Branch
E
Data B
Node 1 F
Data D
E
Data F
Node 2 or Data G
F
cascade Data H
RBB44_6C

Note:
9. RBB 44 8A
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
A
Data B
Data D B
Node 1
A
Data F
Data G
B
Data H
RBB44_8A
Applicable rules from chapter 9.1.1: 0, 1, 2

Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 8A can not be supported.
10. RBB 44 8B
RI Link RF Branch
C
Data B
Data D D
Node 1
C
Data F
Data G
D
Data H
RBB44_8B

Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 8B can not be supported.
11. RBB 44 8C
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
E
Data B
Data D F
Node 1
E
Data F
Data G
F
Data H
RBB44_8C

Note:
Limitation only valid for Radio released on 21.Q3. RBB 44 8C can not be supported.
12. RBB 22 3A
RI Link RF Branch
Data A
1: TX A / RX A
Node 1 A
Data B
Data C B
Node 2 or
cascade Data D
RBB22_3A

Note:
13. RBB 22 3B
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Data A
1: TX A / RX A
Node 1 C
Data B
Data C D
Node 2 or
cascade Data D
RBB22_3B

Note:
14. RBB 22 3C
RI Link RF Branch
Data A
1: TX A / RX A
Node 1 E
Data B
Data C F
Node 2 or
cascade Data D
RBB22_3C

Note:
15. RBB 22 4A
RI Link RF Branch
Data A
1: TX A / RX A
A
Data B
Data C B
Data D
RBB22_4A

Note:
Ericsson Internal

2023-12-21 PF24
16. RBB 22 4B
RI Link RF Branch
Data A
1: TX A / RX A
C
Data B
Data C D
Data D
RBB22_4B

Note:
17. RBB 22 4C
RI Link RF Branch
Data A
1: TX A / RX A
E
Data B
Data C F
Data D
RBB22_4C

Note:
18. RBB 44 2X
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
A
Node 1 Data B
Data D B
A
Data F
Data G
cascade B
Data H
RBB44_2X

Removed due to the limitation on multiple cascading links support from CAT, refer to section
2.6.4
[19.] RBB 44 2Y
RI Link RF Branch
C
Node 1 Data B
Data D D
C
Data F
Data G
cascade D
Data H
RBB44_2Y

2.6.4
19.[20.] RBB 44 2Z
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
E
Node 1 Data B
Data D F
E
Data F
Data G
cascade F
Data H
RBB44_2Z

2.6.4
20.[21.] RBB 11 3A
RI Link RF Branch
Data A
Node 1 Data B 1: TX A / RX A
Data C
Radio 1 A
Node 2 or Data D
Cascade
RBB11_3A

Note:
21.[22.] RBB 11 3B
Ericsson Internal

2023-12-21 PF24
RI Link RF Branch
Data A
Data C
Radio 1 B
Node 2 or Data D
Cascade
RBB11_3B

Note:
22.[23.] RBB 11 3C
RI Link RF Branch
Data A
Data C
Radio 1 C
Node 2 or Data D
Cascade
RBB11_3C

Note:
2 and cascade can not be supported.
23.[24.] RBB 11 3D
RI Link RF Branch
Data A
Data C
Radio 1 D
Node 2 or Data D
Cascade
RBB11_3D

Note:
Ericsson Internal

2023-12-21 PF24
24.[25.] RBB 11 3E
RI Link RF Branch
Data A
Data C
Radio 1 E
Node 2 or Data D
Cascade
RBB11_3E

Note:
25.[26.] RBB 11 3F
RI Link RF Branch
Data A
Data C
Radio 1 F
Node 2 or Data D
Cascade
RBB11_3F

Note:
26.[27.] RBB 11 4A
RI Link RF Branch
Data A
Data B 1: TX A / RX A
Node 1
Data C
Radio 1 A
Data D
RBB11_4A

Note:
Ericsson Internal

2023-12-21 PF24
27.[28.] RBB 11 4B
RI Link RF Branch
Data A
Node 1
Data C
Radio 1 B
Data D
RBB11_4B

Note:
28.[29.] RBB 11 4C
RI Link RF Branch
Data A
Node 1
Data C
Radio 1 C
Data D
RBB11_4C

Note:
29.[30.] RBB 11 4D
RI Link RF Branch
Data A
Node 1
Data C
Radio 1 D
Data D
RBB11_4D

Note:
Limitation only valid for Radio released on 21.Q3. RBB 11 4D can not be supported.
Ericsson Internal

2023-12-21 PF24
30.[31.] RBB 11 4E
RI Link RF Branch
Data A
Node 1
Data C
Radio 1 E
Data D
RBB11_4E

Note:
Limitation only valid for Radio released on 21.Q3. RBB 11 4E can not be supported.
31.[32.] RBB 11 4F
RI Link RF Branch
Data A
Node 1
Data C
Radio 1 F
Data D
RBB11_4F

Note:
Limitation only valid for Radio released on 21.Q3. RBB 11 4F can not be supported.
The following newly added RBB configurations help the realization of 1*4T4R+1*2T2R
for single 6626 radio, with combination of existing 2T2R RBBs.
1. Modification of existing RBB44_1E, so the schematics is like below:
Ericsson Internal

2023-12-21 PF24
2. Modification of existing RBB44_1T, so the schematics is like below:
3. Modification of existing RBB44_2G, so the schematics is like below:
4. Modification of existing RBB44_2AD, so the schematics is like below:

Ericsson Internal

2023-12-21 PF24
5. Modification of existing RBB44_3E, so the schematics is like below:
6. New RBB44_3F:
Ericsson Internal

2023-12-21 PF24
7. New RBB44_4F:
8. New RBB44_4G:
Ericsson Internal

2023-12-21 PF24
Notes:
All the new RBBs, shall be supported by Baseband G2, G3 and G3.1 for all standards.
All 2T/2R RBBs already exist, cand no modification is needed.
However, all the combinations of 4T/4R and 2T/2R RBBs have to be added to show
multisector per Radio combinations.
Additionally, combinations of two RBBs from two nodes must be added.
5.24.3.2[8.3.3.2] FDD Radio 4466
(Introduction of FDD Radio 4466 has an impact on RS Radio

Configurations document 2/1056-HRB105600.)
The following rules shall be taken into consideration when connecting

the Radio to 1 node, 2 nodes as well as for star and cascade
configurations.
1. FDD Radio 4466 can be connected to a node with 1, 2, 3 or 4 CPRI.

Some limitations apply for DUG 20 and DUW v1 and DUW v2, where
only 1 CPRI cable can be used.
2. Any port on the radio can be used for connections to a node.

Exception to that rule is DUW v1 and DUW v2, where only Data 1 is
supported and DUG 20 where either Data 1 or Data 2 is supported.
3. Cascade configurations can be supported with Data 1 connected to

a node and the cascaded radio to Data 2, or vice versa, Data 2
connected to a node and the cascaded radio to Data 1. This is the
same configurations as with the legacy, 2 Data ports radios.
Additionally, a node can be connected to Data 3 and the cascaded
radio shall be connected to Data 4, or vice versa, node can be
connected to Data 4 and the cascaded radio shall be connected to
Data3.
Ericsson Internal

2023-12-21 PF24
4. For mixed mode configurations from 2 nodes, one node has to use
Data 1 and the other has to use Data 2. This rule is determined by
sync, which works only between Data 1 and Data 2. Additional ports
can be used be either of the nodes or by both nodes, one port each.
5. For configurations with Radio 4466 connected with 3 x CPRI

towards one node, the 4th CPRI port can be used for cascading.
Please note cascading rules from bullet 3.
6. Cascading from a Radio can be configured only on 1 of the ports.

For example, id Radio 4466 is connected with 2 x CPRI cables, 1st
cable to Data 1 and 2nd cable to Data 3, only Data 2 or Data 4 can be
used for cascading purposes.
7. Even though Radio 4466 has 4 CPRI ports, currently it can be

connected only to 2 nodes. Configurations with more than 2 nodes
require a new MR.
5.24.3.2.1[8.3.3.2.1] Existing RBBs
FDD Radio 4466 shall be supported with the following legacy RBBs:
1. RBB11_1C
2. RBB11_1D
3. RBB11_1E
4. RBB11_1F
5. RBB11_2A
6. RBB11_2B
7. RBB11_2C
8. RBB11_2D
9. RBB22_1F
10. RBB22_1G
11. RBB22_2K
12. RBB22_2L
13. RBB44_1D
14. RBB44_2F
Ericsson Internal

2023-12-21 PF24
Existing RBBs can be found in

https://erilink.ericsson.se/eridoc/erl/objectId/09004cff8760d543?
docno=2/1056-HRB105600Uen&action=current&format=msw12
5.24.3.2.2[8.3.3.2.2] Common RBBs with Radio 6626
1. RBB11_3A
2. RBB11_3B
3. RBB11_3C
4. RBB11_3D
5. RBB11_4A
6. RBB11_4B
7. RBB11_4C
8. RBB11_4D
9. RBB22_3A
10. RBB22_3B
11. RBB22_4A
12. RBB22_4B
The above RBBs can be found in NDS part for Radio 6626.
5.24.3.2.3[8.3.3.2.3] New RBBs
1. RBB44_3E
Ericsson Internal

2023-12-21 PF24
2. RBB44_4B
5.24.3.3[8.3.3.3] FDD Radio 4456
Introduction of FDD Radio 4456 has an impact on RS Radio

Configurations document 2/1056-HRB105600.
All configurations and RBBs applicable for Radio 4466 are also
applicable for Radio 4456.
One common RBB covering all bands simultaneously including the

SDL-Band. Therefore, no need for any new RBBs.
5.24.4[8.3.4] Information Model and Product Packaging
5.24.4.1[8.3.4.1] Product information Model
Radio 6626, Radio 4466 and Radio 4456 shall be handled as Dynamic
Product Packages along the same principles as todays Radio
products in the Product Information Model for SSC with some updates.
The product shall be possible to configure and order as single items
(expansions and spare parts) and as complete nodes. configured as
Dynamic Product Packages, DPP, in ECP. The NR RAT std will be
implemented in the Expansion Product Packages which already
are prepared for the NR RAT standard. Mixed mode is not
possible to configure by use of the Expansion Products
Packages. Mixed mode with NR, NR+NR, NR+LTE support, will be
supported in the new ECP model for product packages, EPT,
Ericsson Planning and Configuration Tool. Dual Band and Triple
Band radios will also be handled in EPT model and available in
ECP.
Ericsson Internal

2023-12-21 PF24
5.24.4.2[8.3.4.2] Impact on Product Package
Radio 6626, Radio 4466 and Radio 4456 with NR RAT std for RBS
node configurations will be implemented in the new ECP model for
product packages, EPT, Ericsson Planning and Configuration
Tool. Mixed mode with NR, NR+NR and NR+LTE support will be
supported in EPT. The EPT model is prepared for dual and triple
band radios and NR RAT std including NR in mixed mode. This
means that only SSC data Base updates are required.
The Expansion PP model is prepared for dual band and triple RAT
radios and the NR RAT std which means that only SSC Data Base
updates are required
Standard updates, in addition to mentioned above, of the SSC code

for support of the new Radio 6626, Radio 4466 and Radio 4456 are
required. MU flag for the product must be set in SAP/One by
supply/NPI. The MU flag is not required for PP/SSC to put the Radio
6626, Radio 4466, and Radio 4456 in the Bill of Material (BoM) for the
DPP in the ECP order view but required to make it possible to order
the radio unit in the production plants. The product and material must
be uploaded in SAP/One (by support from MDM) for all relevant
production plants and all master data for the product should be
defined and put in SAP/One by supply/NPI as well.
All supported radio configurations and RBS system input (RBBs etc.)
required for the PP/SSC work shall be defined by RBS system. PSU
calculations for the product are also required as input for PP/SSC and
must be performed by Enclosure & Power.
The PP commercial view in ECP will be updated with questions for the
selections that shall be possible to do. Also, price objects must be
defined and released in ECP with cost. The price object and
commercial questions shall be defined in the PPD (by SPM).
5.24.4.3[8.3.4.3] Affected RBS PPs
The following RBS PPs will be affected by the introduction of Radio

6626, Radio 4466, and Radio 4456
PP Update PP Product number
ERS Enclosure (HGM, HPM) FAN 102 038
RBS Expansion FAP 230 13
ERS Radio Solution FAP 230 41
ERS Site Product Package FAP 230 44
ERS Spare Part Product Package FAP 130 4570
Ericsson Internal

2023-12-21 PF24
5.24.4.4[8.3.4.4] Cost
30 mhrs.
5.24.5[8.3.5] Unit database
Radio 6626 PV should be added to the unit data base in below table.
Table 29 Product Information
Product Name Product Number
Radio 6626 66B1 66B3 C KRC 161 924/1

Radio 6626 66B8 66B20 C KRC 161 948/1
Radio 6626 66B0A 66B28 C KRC 161 947/1
Note:
MR9002-SP1: supports GSM, WCDMA, LTE-FDD, NR-FDD, NB-

IOT(SA,GB,IB) and ESS


5.24.6[8.3.6] Impact on ERS Product Structure
5.24.6.1[8.3.6.1] Source System HRB 105 600
Radio 4456 shall comply to the source system requirements as defined in

the ERS HW BL16A
 Ericsson Radio System HW Architecture Specification 8/1056-HRB
105 600
No need for update
 RS Product information Data (PID) for ERS HW Products 27/1056-HRB

105 600
Radio 66xx, 44xx and 88xx has been covered in Chapter 4.4.2.1 Capacity
and Variants for Multi-Band Radio Products defined in 27/1056-HRB
105 600. No need to update it.
Ericsson Internal

2023-12-21 PF24
5.24.6.2[8.3.6.2] Application System HSD 101 101
The following Application System documents shall be updated with respect

to Radio 4456:
 Radio Configuration Document 2/1056-HRB 105 600 and ERS

Combination Document 2/1056-HSD 101 101
o Add the Radio with relevant Radio Configuration

data/capabilities and relations/dependencies to Baseband,
RAT Support and RAN SW
 HWAC for Radio and Digital Units (1/1551-3/HRB105601)
o Add the radio and all its relevant HWACs
 SFP Approved List (1/006 51-HRB 105 601)
o Add the radio and information about applicable SFPs
 ERS HW Product Information Data (PID) (3/00651-HSD101101)
o Add PID information for the radio 4456
 ERS Site Products (1/001 21-HSD 101 01)
o Add information about applicable site products for

Radio 4456
Radio 4456 shall in terms of external interfaces follow the FRU-type: “ERS
Radio” as described in ERS HW Architecture Specification (8/1056-
HRB 105 600).
5.25[8.4] Radio
5.25.1[8.4.1] Radio general
Visby radio is developed as new platform radio
It consists of below parts:
 Front cover, it is also IP cover.
 Filter, new filters using black-box product concept a
 EMC cover.
 A MOB (Motherboard) containing all electronics expect PA

Ericsson Internal

2023-12-21 PF24
 PAX and PAM containing PA part
 A heatsink
 A front foot
 Several panel connectors.
Exploded view was showed as below:
FU cover
F
PAB+4x
PAB cover
MOX
8x PAXs
MO
Frame
Figure 6 Visby Exploded View
The total output power at -40~50degC is 720W, when temperature at -

40~55degC, the power is 600W.
Fan is an optional and new designed module.
Most parts are new design due to new platform. Detailed information is
described into the HW Implementation Proposal document.
Digital part:
The digital implementation in Visby at least for first product will based
Radon 1.1 +ZU4. The anatomy as follow:
Ericsson Internal

2023-12-21 PF24
Figure 7 Visby 6626 B1B3 Digital architecture
From Visby second product, digital implementation will changed to

eASIC(Mongoose)+Radon 1.1 The anatomy as follow:
Cha nge ZU4 by Mongoose for TK

down TRX- IC TRX- IC
8T8R 4T4R
Ma x 200M IBW
JESD204C RX 16G JESD204C RX 16G
Do not support: PIMC/ eCRPI / oRAN Radio
ctrl AI
3- Axis Pressure
Sensor Sensor LTU (AC/PA
/ LNA/ T ADC
X_LO W) 204B
SPI SPI SPI 4.9G JESD204C TX 16G JESD204C TX 16G
204B
temperature SPI 204B

AI
sensor re ceive r
sXP
Mongoose Ctrl UART

Reset Radon1.1
CPU eMMC
UCD
DFE
SPI
QSPI DC
Flash supervision
SPI
LO
DDR
CPRI_0,1,2,3
Recovered
I2C x4 + GPIO Retimer
Clock
TSP/ x4
RET/
MMI LED/
X- alarm EC light/
Push SFP28 x4 LTU
Modem
Button
Figure 8 Visby 4466 B1B3B7 Digital architecture
For Visby LB 6626 B8B20, digital implementation will changed to

eASIC(Mongoose)+Radon 1.1(0.8 pitch) The anatomy as follow:
Ericsson Internal

2023-12-21 PF24
Figure 9 Visby 6626 B8B20 Digital architecture
Details can refer to the HW IP.

Ericsson Internal

2023-12-21 PF24
5.25.1.1[8.4.1.1] Radio 4456
Visby Radio 4456 is developed as a product variant based on platform variant

Radio 4466. Because of the weight and volume requirements Radio 4456 has
a less depth than Radio 4466.
Radio 4456 consists of below parts:
 1-layer metal FU with FU cover
 PAB with 4 x PAX’s
 PAB EMC Cover
 MOX EMC Cover
 8 x PAX’s
 MOX Board
 Frame/Heatsink with removed Vapor Chamber
Fi Heatsink
F
U
Figure 10 Radio 4456 Architecture illustration

Ericsson Internal

2023-12-21 PF24
FU
PAB (4x PAs)
PAB EMC Cover
MOX EMC
Cover
8x PAX
External MOX
Connectors
Foot
Heatsink
Figure 11 Radio 4456 exploded view
Total output power for Radio 4456

 No optional fan
 320W total power. Temp range -40C to +50C.
 300W total power. Temp range -40C to +55C.
Ericsson Internal

2023-12-21 PF24
5.25.1.1.1[8.4.1.1.1] Radio 4456 Block Diagram and MOX board
 Base is Radio 4466 B1B3B7 MOX board
 MOX board uses 16-layer PCB stack up from Radio 4419 because of
removal of one DC/DC port. -48V must be routed from right side
connector to left PAVDD’s
 4 internal interconnect RX ports not used, B75C is only DL
AC connector (not
needed for FDD)
MOX Gain block Pre-driver

driver
PA
PAX B3J B3J RF A
Visby 4456 44B1C 44B3J 40B75C

B3J RF B
KRC 161 949/1 PAX B3J
PA
PAX B3J B3J RF C

PA
PAX B3J B3J RF D

PA
LNA2 LNA1
TX1-4 TX
TOR TOR
8 x 16G JESD204B TX RX1-4 RX
4 x 16G JESD204B RX
2 x 16G JESD204B TOR
RFIC (Palau0)
DCDC
122.88MHz
TX5-8 TX
PAX B1C B1C
sysref PA
LTU TOR TOR
DC 122
RX5-8 RX
sensor FB 491 PAX B1C B1C
1.92 PA
SPI 1.92MHz 491.52MHz MHz
48V_OK
FBx24 MCBx4 LB
PAX B75C B75C
PA
FBx24 MCBx4 LB
Radon 122.88
LB ALG
1.1
FBx24 MCBx4 LB
MHz
PAX B75C B75C
PA
DATA1 CPRI
DATA2 CPRI
FBx24 MCBx4 LB
DATA3 CPRI
DATA4 CPRI
LNA2 LNA1
SXP UART
Alarm Flash
RET/ALD Mongoose
CPU
TSP FPGA (ZU4) DDR
Push button
FLT eMMC 1 x 2.5G JESD204B VSWR
OPER
Maint VSWR FWD
CPRI1
AD9368-1
CPRI2
CPRI3 VSWR REV
CPRI4
PAX B1C
B1C
PA
TX9-12 TX PAX B1C B1C

PA
TOR TOR
4 x 16G JESD204B TX RX9-12 RX
2 x 16G JESD204B RX
1 x 16G JESD204B TOR PAX B75C B75C
PA
RFIC (Palau1)
PAX B75C B75C
TX
PA
TOR
PAB
RX
FU
Figure 12 Radio 4456 Block Diagram
Ericsson Internal

2023-12-21 PF24
Figure 13 MOX board
5.25.1.1.2[8.4.1.1.2] Radio 4456 Digital Part
Cha nge ZU4 by Mongoose for TK

down TRX- IC TRX- IC
8T8R 4T4R
Ma x 200M IBW
JESD204C RX 16G JESD204C RX 16G
Do not support: PIMC/ eCRPI / oRAN Radio
ctrl AI
3- Axis Pressure
Sensor Sensor LTU (AC/PA
/ LNA/ T ADC
X_LO W) 204B
SPI SPI SPI 4.9G JESD204C TX 16G JESD204C TX 16G
204B
temperature SPI 204B

AI
sensor re ceive r
sXP
Mongoose Ctrl UART

Reset Radon1.1
CPU eMMC
UCD
DFE
SPI
QSPI DC
Flash supervision
SPI
LO
DDR
CPRI_0,1,2,3
Recovered
I2C x4 + GPIO Retimer
Clock
TSP/ x4
RET/
MMI LED/
X- alarm EC light/
Push SFP28 x4 LTU
Modem
Button
Figure 14 Visby Radio 4456 B1CB3JB75C Digital Architecture
5.25.1.1.3[8.4.1.1.3] PA
 LDMOS on all bands
o No GaN PA transistor available for B75C

Ericsson Internal

2023-12-21 PF24
o Not possible to mix GaN and LDMOS. PACC can’t have both
negative and positive gate bias
 Re-use of 6626/4466 PAB and PAX size
 Re-use of B1 and B3 PA drivers. New PA driver for B75C (same as for

Oslo Radio 4020 B75B
 Re-use of B1 and B3 isolators. B75C will use Oslo Radio 4020 isolator
 New 26dB coupler to be designed in PAX and PAB boards
5.25.1.1.4[8.4.1.1.4] DC/DC
 Re-use of Visby Radio 4466 B1B3B40
 One DC/DC connector. Left DC/DC connector removed. Left input

stage removed (PIX)
 AUX_VCC_1 not removed, still needed
 PAVDD 17-32V for LDMOS
 PAVDD_2, FAN_VCC and GPA_VGG not used
5.25.1.1.5[8.4.1.1.5] Filter Unit
 Filter height 49.5mm including fin height
 Filter target weight 12kg

Ericsson Internal

2023-12-21 PF24
Figure 15 Weight estimation
5.25.1.1.6[8.4.1.1.6] Floor plan
 Position of PAX boards and PAB floor plan is impacted by Filter Unit
design
 TX, RX and TOR traces are re-routed compared to Visby Radio 4466
B1B3B7
 3 PAVDD’s are used and are re-routed compared to Visby Radio 4466
B1B3B7
Ericsson Internal

2023-12-21 PF24
Figure 16 Visby Radio 4456 B1CB3JB75C floor plan
5.25.2[8.4.2] Radio Modularity
HW Module blocks:
• Block diagram
• Digital
• DL/UL line up
• PA
• FU
• DC/DC
• Thermal
• PIM/EMC
• Production
Ericsson Internal

2023-12-21 PF24
Figure 17 Visby Modularity plan
Note:
The schematic & layout level review are continually with each module
guardian.
Ericsson Internal

2023-12-21 PF24
5.25.3[8.4.3] Architecture Impact on Radio HW
5.25.3.1[8.4.3.1] Radio Architecture Impact on HW Blocks Diagram
Figure 18 Visby Architecture impact
Note:
Common OA study is driving the architecture impact with module system

for the whole Visby platform. More detailed information refers to
Common OA study. This is suggested by Architecture System Marin
Sikiric.
[8.4.4] (Integration Lei Zhang I)Integration
5.25.3.2[8.4.4.1] A new CPRI line rate 25Gbps shall be supported.
 New CTDU25 should be purchased.
 RUX supported CTDU25 and 25Gbps_CPRI shall be requested.
 25Gbps CDL file shall be requested.
5.25.3.3[8.4.4.2] A new carrier type, NR_30MHz_FDD, shall be supported.
 RUX supported NR_30MHz_FDD shall be requested.
 NR_30MHz_FDD CDL file shall be requested.

Ericsson Internal

2023-12-21 PF24
5.25.3.4[8.4.4.3] New ASIC supported
 RUX supported Radon and Palau shall be requestedsted.
 MR9268 ESS + NB-IoT
This MR will cover all Visby Radios for supporting ESS+NB-IoT. Additional
tests are needed as follows:
1.TA Verification: DL
essFdd100_Id1/dlDelayDeltaCfrOff
2.TA Verification: UL
essFdd100_Id1/ulDelayDelta
3.Clipping and DRT db verification
4. UL performance: 1+0 three BWs Gain、EVM and NF
5. DL performance: 1+0 1+1 1+N OBUE and EVM
[8.4.4.4] MR9268-1 LTE GB NB-IoT coexistence with ESS on Visby Radios
This MR will cover all Visby Radios for supporting ESS+NB- IoT.
Additional tests are needed. as follows:
1.TA Verification: DL
2.TA Verification: UL
Ericsson Internal

2023-12-21 PF24
3.Clipping and DRT DdBb verification
4. UL performance: 1+0 three BWs Gain、EVM and NF
5. DL performance: 1+0 1+1 1+N OBUE and EVM
6.The test radio scope:
Covering releases for 6626 B1B3, 4466 B1B3B7 and 6626B8B20.
Other Visby radios release should be taken by each project.
5.26 XMU
N/A
5.27[8.5] P614
N/A
5.28[8.6] Digital
N/A
5.29[8.7] Enclosure & Power
Visby radio is new platform, so the BP is different with others
The size of Visby 6626 B1B3 is 580x384x181mm (MB dual-layer FU).

The corresponding product volume is 40.3L. The estimated weight is
around 43kg without fan. The fin height on the heatsink is 75mmm.
Ericsson Internal

2023-12-21 PF24
Figure 19 Radio 6626 B1B3B
The size of Visby 4466 B1B3B7 is 580x384x197mm (MB dual-layer

FU). The corresponding product volume is 43.6L. The estimated
weight is around 48kg without fan. The fin height on the heatsink is
90mmm.
Figure 20 Radio 4466 B1B3B7

Ericsson Internal

2023-12-21 PF24
For LB radio the size of Visby 6626 B8B20 is 700x384x181mm (LB

dual-layer FU). The corresponding product volume is 48.7L. The
estimated weight is around 51kg without fan. The fin height on the
heatsink is 75mm.
Figure 21 Radio 6626 B8B20
The maximum power supply shall be up to 2500 W.
The position and type of external interface as shown in the figure

below.
Ericsson Internal

2023-12-21 PF24
Figure 22 Radio 6626 B1B3 external interface
Figure 23 Radio 4466 B1B3B7 external interface

Ericsson Internal

2023-12-21 PF24
Figure 24 Radio 6626 B8B20 external interface
Table 30 External connectors on a 6-port Visby Radio

I Design Q Descri Conn Comments
t ation ty ption ector
e
m
9 RF A, 6 Antenn 4.3- Symbol on

RF B, a ports 10 Radio:
RF C, (f A-L,
RF D, or TX/RX A, B, C, D,
RF E, 6 , Band E, F,
RF F, 6 x and
2 Band y
6) on all
4 ports
(f Mode
or m data
4 on all
4 RF
6 ports,
6) and
DC on
every
secon
d port
Ericsson Internal

2023-12-21 PF24
I Design Q Descri Conn Comments

t ation ty ption ector
e
m
5 DATA 4 CPRI SFP/ Symbol on

1, SFP+ Radio:
DATA or
2, SFP2 1, 2, 3, 4
DATA 8
3,
DATA
4
4 ALD 1 DC Exter
/RET power nal Text on
and conne Radio:
mode ctor 8 ALD
m data pin
femal
e
accor
ding
to IEC
60
130-9
3 Ext. 1 Extern Exter Symbol on
Alarm/ al nal Radio
FAN alarm conne
ctor
EC 14 pin
light femal
bus e
FAN accor
ding
to IEC
60
130-9
1 Power 1- -48V Symbol on
/ 1, 2 DC Radio:
7 Power 1, 2
2 3-wire
8 GND 1 Groun Dual Symbol on

d lug. Radio:
2xM6.
• MR for mounting：
- Portrait, bookshelf mounting. NO horizontal mounting.
- The rail installation need 100mm space without fan.
- For LB Portrait mounting only. No bookshelf mounting and

horizontal mounting.
Ericsson Internal

2023-12-21 PF24
• Hole pattern:
- CC110mm x CC110mm, aligned with Radio4460
• Brackets including rail/single/dual/multi:
- New. Support weight up to 60kg
Since radios have used integrated handle on the top, no top side
installation scenario for ERS radio any more.
Rail 2.0 is to be used in Rail mounting for Radio 6626.

Ericsson Internal

2023-12-21 PF24
Note:
Rail 2.0 is not compatible with rail 1.0. The existed Rail CPI like ERS
site products CPI should be updated.
5.29.1[8.7.1] Radio 4456, Enclosure and Power
Figure 25 Radio 4456 B1CB3JB75C
The size of Visby 4456 B1CB3JB75C is 580x384x118.6mm (MB one-

layer FU). The corresponding product volume is 26.4L. The estimated
weight is around 29.9kg with no optional fan. The fin height on the
heatsink is 48mm.
Ericsson Internal

2023-12-21 PF24
2 3 4 5 1 7
Figure 26 Radio 4456 B1CB3JB75C External Interface
Table 31 External connectors on a 4-port Visby Radio
Item Function Qty Description EPN Pic Note
1 Power 1 55A power connector RPT 447 38/02 Reused from Oslo
2 MMI 1 7x LEDs+ Reset New design
3 Alarm 1 14-pin DIN connector RNT 493 516/014 Reused from Oslo
4 RET 1 8-pin DIN connector RNT 493 516/008 Reused from Oslo
5 CPRI 4 SFP Cage: SDD 510 289/01 Reused from Oslo

FullAx bulkhead: RNY
104 74/04
7 GND 1 two position, M6 dual SXK 109 2172/1 and Reused from Oslo
lug SRB 901 31/1
8 Ant Port 4 Kenia 4.3-10 RNT 408 Reused from Dublin

6009/03(Kenia)
RNT 408
6010/03(NEX10)
Ericsson Internal

2023-12-21 PF24
5.29.2[8.7.2] Wind noise version for MR11742
Since some radios are complained due to whistle issue by customer, Visby add a new requirement to
solve this issue. The main change is adding cut-out features on the top of heatsink fin. Others no change.
Figure 27 Radio 6626 B1B3(wind noise version)
Figure 28 Radio 6626 B1B3B7(wind noise version)

Ericsson Internal

2023-12-21 PF24
5.30[8.8] Site
5.30.1[8.8.1] Site Impact – Power supply
Power Supply dimensioning
Guideline/estimation based on what we know today
● Calculated CB rating based on adding 50% margin (Requirement on/from BL16A) gives us a 40A
CB
● However, considering a more realistic maximum output power that newer reach 320W due to
several circumstances such as triple band newer have full output power at the same time,
power saving features and if we should reach 320W at some point it would be for a very
limited time, seconds or parts of seconds probably.
● This gives us at this point a basis to estimate a reasonably CB rating to 30A
Continued estimation and setting guidelines for Power Supply
PRA of Visby Radio 4456 B1C B3J B75C is planned June 2022.
During Execution, we expect to continue the investigation and learn more about Visby Radio 4456
B1C B3J B75C and Power Supply needs.
This could involve updated Power Consumption figures as well as a better understanding of the
actual power consumption levels at the site. This may be based on statistics and experience from
field.
Important is to get confident input for our calculations and actions to accomplish this needs to be
taken during the continued execution and in conjunction with the general studies/evaluations in
this area.
5.30.2[8.8.2] Site Impact – Mounting
At this point the Radio 4456 follows the mounting concept from legacy OSLO Radio
Platform. The weight is slightly lower than the OSLO Radio.
With this we can see that we will reuse the same mounting/installation materials, same
mounting hole patterns and positions as for OSLO Radios.
No new Site mounting material needed.

Ericsson Internal

2023-12-21 PF24
5.31[8.9] Packaging Material Design
5.31.1[8.9.1] General impact on MR9002-SP4
The packaging material for Visby Radio 4456 will be designed to meet the
general packaging requirements in the document 1056-CSX 101 58, baseline
revision.
Packaging Material used for delivery of Visby Radio 4456 products to

Ericsson customer shall be defined, designed, verified, registered, and
maintained as a HW component of the Ericsson product.
For Visby Radio 4456 the following packaging material will be designed:
single package solution; spare parts packaging where applicable.
Required input to packaging material design process: Mechanical properties

(e.g., dimensions, max G force, electrostatic discharge (ESD) sensitivity,
moisture sensitivity), supply chain definition (SCD). Changes made, e.g., to
mechanical properties or SCD may require late changes to packaging
material design.
Ericsson Internal

2023-12-21 PF24
5.31.1.1[8.9.1.1] General impact on MR9002-SP4
The packaging material for Visby Low band Radio 6626 B8 B20 will be
designed to meet the general packaging requirements in the document 1056-
CSX 101 58, baseline revision.
Packaging Material used for delivery of Visby Low band Radio 6626 B8 B20
products to Ericsson customer shall be defined, designed, verified, registered
and maintained as a HW component of the Ericsson product.
For Visby Visby Low band Radio 6626 B8 B20 the following packaging
material will be designed: single package solution; spare parts packaging
where applicable.
Required input to packaging material design process: Mechanical properties

(e.g. dimensions, max G force, electrostatic discharge (ESD) sensitivity,
moisture sensitivity), supply chain definition (SCD). Changes made, e.g., to
mechanical properties or SCD may require late changes to packaging
material design.
5.31.2[8.9.2] Applicable requirements
5.31.2.1[8.9.2.1] Packaging for white box products
Packaging material for white box products shall be designed by Ericsson

according to the requirements in 11/1056-CSX 101 58.
5.31.2.2[8.9.2.2] Packaging for Black box products
Packaging material for black box products shall be designed by the black box
supplier according to the requirements in 12/1056-CSX 101 58. Outbound
black box packaging sets shall have an Ericsson product number. Black box
product packaging material shall be reviewed and accepted by Ericsson.
5.31.2.3[8.9.2.3] Inbound multi-packaging
Inbound multi-packaging material used for delivery of components from the

supplier to Ericsson assembly facilities shall be designed by the supplier
according to the requirements in 15/1056- CSX 101 58. The supplier shall
guarantee product protection during transportation.
5.31.2.4[8.9.2.4] Spare part packaging
If spare parts packaging is needed, the spare parts list should be made
available to PMD as early as possible.
Ericsson Internal

2023-12-21 PF24
5.31.3[8.9.3] Preferred (single) packaging solution for MR9002-SP4
Similar packaging building practice as below will be used. Radio 4456 and
6626 B1B3 share the same fitments, with different box dimensions due to
product height difference. All dimensions given are estimated.
Estimated single packaging dimensions based on Radio 4456:
Height: 265mm
Width: 570mm
Depth: 790mm
Estimated dimensions for unitized loads based on Radio 4456:
Height: 930mm (including pallet)

Width: 800mm
Depth: 1200mm
5.31.3.1[8.9.3.1] Preferred (single) packaging solution for MR9002-SP4
Since product length increased 120mm, whole product dimensions are close
to Massive MIMO product. Thus packaging building practice for Massive
MIMO products as below will be used. All dimensions given are estimated.
Ericsson Internal

2023-12-21 PF24
Estimated single packaging dimensions:
Height: 310mm
Width: 565mm
Depth: 920mm
Estimated dimensions for unitized loads:
Height: 1100mm (including pallet)

Width: 570mm
Depth: 970mm
5.31.4[8.9.4] Cost estimates for MR9002-SP4
Estimated cost for design activities is about 120 hours.

Ericsson Internal

2023-12-21 PF24
5.31.4.1[8.9.4.1] Cost estimates for MR9002-SP4
Estimated cost for design activities is about 200 hours.
5.32[8.10] Virtualization
N/A
Ericsson Internal

2023-12-21 PF24
[9] (CPI unkown)Impact on CPI
5.33[9.1] General
Table 32: Checklist CPI Impact
Checklist item New Removed Changed
Impact on Configuration Management (parameters) <No> <No> <No>

6.7
Impact on Performance Management (KPIs, <No> < No> < No>

pmCounters, pmEvents)
6.9
Impact on CPI Parameter and Counter Limitations <No> <No> < No>
Impact on Fault Management (Alarms) <No> < No> <No >

6.10
Impact on RAN CPI <No> <No> <No>
Impact on RBS CPI <Yes > <No> <No>
Impact on Site CPI < No> < No> <Yes >
Table 33: Checklist TDD/FDD Impact
Checklist item TDD/FDD functionality
TDD/FDD impact < FDD only >
5.34[9.2] Input to Network Impact Report (NIR)
Case 1: 48V input failure at slave DC port , a new fault will be reported to DU
from Radio. Du will disable cell according to this fault.
Access Type: N/A

Hardware Platform: N/A
Licensing: N/A
Value Package: N/A
Node Type Baseband Radio Node
Access Type NR, LTE
Ericsson Internal

2023-12-21 PF24
Benefits
Help the operator to understand the root cause when the corresponding
existed alarm (Power Disturbance) is raised.
Capacity and Performance
No impact.
Operation
The existing alarms may be raised for slave port DC power supply due to the
case1.
Hardware:
Visby Radio 6626
Interfaces
No impact
Other Network Elements
No impact
5.35[9.3] Document List
CPI analysis summary

Table 34: CPI analysis summary
CPI analysis by: QMARJOH, ZENGAND
CPI cost MR9002-1 and MR9003-1: 668 h +16 additional SW
summary: MR08932-1: 528 h HW + 15 h SW+ 4h additional SW
MR08930-1: 27 h HW (updated) + 5 h SW
Title Doc. number Node RAT WP New Update CPI Update descr. Owner
Type (h) (h) verific.
Radio Description - G1, G2 G,W,L, MR9002-1 80 Note: apart from the Radio HW
Radio 6626 NR,ESS “standard” information, also
add information about
Connection to Baseband per
RAT, in a similar way as for
AIR 6449.
Also note that this
information might not be
placed under Chapter
Connection Interfaces as for
AIR 6449 – to be further
discussed during PD.
Install Radio - G1, G2 G,W,L, MR9002-1 100 Note: new brackets. Radio HW
Radio 6626 NR,ESS
Replace Radio - G1, G2 G,W,L, MR9002-1 80 Radio HW
Radio 6626 NR,ESS
Preventive 61/1541-LZA 701 G1, G2 G,W,L, MR9002-1 40 Radio HW
Maintenance 6001/1 NR,ESS
Radio 6626
Package Radio 75/1543-LZA 701 G1, G2 G,W,L, MR9002-1 10 Radio HW
6001 NR,ESS
Animation - G1, G2 G,W,L, MR9002-1 100 Radio HW
Story Board NR,ESS
Power Consumption 3/006 51-LZA G1, G2 G,W,L, MR9002-1 1 Radio HW
Data 701 6001 NR,ESS
Ericsson Internal

2023-12-21 PF24
Radio Software 1/155 51-LZA G1, G2 G,W,L, MR9002-1 1 Radio HW

Support 701 6001 NR,ESS
Animation - G1, G2 G,W,L, MR9002-1 100 BI HW
Animation NR,ESS
development
Radio Node 24/1551-LZA 701 G1, G2 G,W,L, MR9002-1 20 BI HW
Configurations 6001/1 NR,ESS
Spare Parts 4/154 11-LZA G1, G2 G,W,L, MR9002-1 5 BI HW
Catalogue 701 6001 NR,ESS
Radio Connections 217/1551-LZA G1, G2 G,W,L, MR9002-1 10 BI HW
701 6001/1 NR,ESS
Main-Remote 16/1551-LZA 701 G1, G2 G,W,L, MR9002-1 10 New brackets BI HW
Installation Products 0003 NR,ESS
Overview
Hardware-related 51/1551-LZA 701 G1, G2 G,W,L, MR9002-1 5 No New HWAC for GSM 4G5G SW
Capabilities 6014/1 NR,ESS
Manage Node Group 55/1553-LZA 701 G1, G2 G,W,L, MR9002-1 10 add illustration about Radio 4G5G SW
Synchronization 6014/1 NR,ESS 6626 with Baseband Radio
Nodes using only two ports
in NGS configuration.
(update: ZENGAND. XFT
contact: Albert Wei
albert.wei@ericsson.com
and Petar Kresic
petar.kresic@ericsson.com)
Compatibilities for 11/1551-LZA 701 G1 W MR9002-1 10 Product number to be WCDMA
Hardware and 6003/1 added. SW
Software
WCDMA RBS 14/1553-LZA 701 G1 W MR9002-1 10 Section 7.16 FAJ 121 4160: WCDMA
Configuration 6003/1 Multi-Sector Per Radio SW
Guidelines
Multi-Sector Per 217/1553-HSD G1 W MR9002-1 5 Three sectors can be WCDMA
Radio 101 02/1 supported on the new radio, SW
which will affect the
description of this feature.
Basic Features 218/1553-HSD G1 W MR9002-1 5 Update the description of the WCDMA
101 02/1 Multi-Sector Per Sector SW
feature.
Network Impact 18/109 48-HSD G1 W MR9002-1 5 New topic for this WCDMA
report 101 02/1 enhancement SW
Radio Network 186/006 51-HSD G1 W MR9002-1 5 The value of WCDMA
Parameters 101 02 AntFeederCable::objectACo SW
nnector updated.
New RBBs.
File Descriptions for 13/1553-LZA 701 G1 W MR9002-1 5 New RBB added, and the WCDMA
Site Configuration 6003/1 value of the attribute SW
radiobuildingblock will be
updated.
Manage Radio 2/1553-LZA 701 G1 W MR9002-1 5 The note in section 2.8.44.2 WCDMA
Network 6003/1 needs to be updated. SW
Example Files for 1/006 91-LZA G1 W MR9002-1 10 New example file WCDMA
Site Equipment 701 6003/1 SW
Configuration
DTD for Site 5/006 91-LZA G1 W MR9002-1 10 New DTD file WCDMA
Equipment 701 6003/1 SW
Configuration
Example Files for 3/006 91-LZA G1 W MR9002-1 10 New example file WCDMA
Modify RBS 701 6003/1 SW
Equipment
Configuration
DTD for Modify RBS 7/006 91-LZA G1 W MR9002-1 10 New DTD file WCDMA
Equipment 701 6003/1 SW
Configuration
Fault List RBS 6000 1/006 51-LZA G1 G MR9002-3 10 Fault handling for new GSM SW
701 6002 scenario
BTS Parameter G1 G MR9002-1 8 No Add new radio GSM SW
Description
GSM RAN Gnnn x/10948- G1 G MR9002-1 8 No Add new HWAC GSM SW
Ericsson Internal

2023-12-21 PF24
Network Impact HSC10312/25 Add new radio

Report
BTS Parameter G1 G MR8930-1 8 No Add new radio GSM SW
Description
GSM RAN Gnnn x/10948- G1c G MR8930-1 8 No Add new HWAC GSM SW
Network Impact HSC10312/25 Add new radio
Report
User Description, G1 G MR9002-1 8 No Add new HWAC GSM SW
GSM RAN Handling
of Software Licenses
and Hardware
Activation Codes.
MR9003-1 Need to add 6TX/6RX Radio CDS SW
Multi-Sector Per 289/221 04-LZA G,W,L,N
G1, G2 (same as 4 Y Units for Multi-Section
Radio 701 6014/1 R,ESS
9002-1) configuration.
MR9003-1 Radio 6626 (6T/6R) CDS SW
Manage Radio 44/1553-LZA 701 G,W,L,N
G1, G2 (same as 4 Y supports Multi-sector per
Network LTE 6014/1-V1 R,ESS
9002-1) Radio configuration.
Radio 4466 has four-port CDS SW
Cascadable Radio 24/221 04-LZA G,W,L,N and is applicable to FDD.
G1, G2 MR9003-1 4 No
Units 701 6014/1 R,ESS Need to update Section 8.1
Configuration.
Radio Description - G1, G2 G,W,L, MR08932- 80 Radio HW
Radio 4466 NR,ESS 1
Install Radio - G1, G2 G,W,L, MR08932- 100 Radio HW
Radio 4466 NR,ESS 1-1
Replace Radio - G1, G2 G,W,L, MR08932-1 80 Radio HW
Radio 4466 NR,ESS
Preventive x/1541-LZA 701 G1, G2 G,W,L, MR08932-1 40 Radio HW
Maintenance 6001/1 NR,ESS
Radio 4466
Animation - G1, G2 G,W,L, MR08932-1 100 Radio HW
Story Board NR,ESS
Animation - G1, G2 G,W,L, MR08932-1 100 BI HW
Animation NR,ESS
development
Radio Node 24/1551-LZA 701 G1, G2 G,W,L, MR08932-1 20 Radio 4466 is a four-port BI HW
Configurations 6001/1 NR,ESS MR08930-1 radio, suggested
documents for update:
Building Blocks (A46)- New
building block
Yuhan Zhao had been
informed,
Radio Cascade
Configuration Rules (A45)-
Add Data port 3 and Data
port 4 for the four-port
Radio,
Spare Parts Catalog 4/154 11-LZA G1, G2 G,W,L, MR08932-1 5 BI HW
701 6001 NR,ESS
Glossary of Terms 1/0033-LZA 701 G1, G2 G,W,L, MR08932-1 1 N Update the Glossary with the BI HW
and Acronyms 6001 NR,ESS new terms.
Manage Node Group 55/1553-LZA 701 G1, G2 G,W,L, MR08932-1 10 4G5G SW
Synchronization 6014/1 NR,ESS
Hardware-related 51/1551-LZA 701 G1, G2 G,W,L, MR08932-1 5 No check if new HWAC is 4G5G SW
Capabilities 6014/1 NR,ESS needed for Radio 4466
Check if an example is need CDS SW
for four-port radio unit.
Manage Hardware 24/1553-LZA 701 G,W,L,N MR8932-1
G1, G2 4 No Section 10.9.6 Configuration
Equipment 6014/1 R,ESS MR8980-1
of Two Cascaded Radios
supporting the same sector.
Radio Description G1, G2 G,W,L, MR8930-1 20 Radio HW
Radio 4466 NR,ESS
Ericsson Internal

2023-12-21 PF24

Radio Node 24/1551-LZA 701 G1, G2 G,W,L, MR8930-1 20 to be released together with BI HW
Configurations 6001/1 NR,ESS MR08932-1.
Spare Parts Catalog 4/154 11-LZA G1, G2 G,W,L, MR8930-1 5 BI HW
701 6001 NR,ESS
Hardware-related 51/1551-LZA 701 G1, G2 G,W,L, MR8930-1 5 No check if new HWAC is 4G5G SW
Capabilities 6014/1 NR,ESS needed for introduced Radio
4466 variants
Valid for: GSM, WCDMA, LTE, NR, ESS
Customer specific No
feature:
Comment: MR08932-1: Depending on GSM and WCDMA input, additional 100 h may be needed (24 GSM + 76 WCDMA),
considering whether new HWACs are implemented for Radio 4466. Currently (03.10) no such information is
available in NDS, it is supposed that no new HWACs will be introduced.
5.35.1[9.3.1] CPI analysis summary for MR9609-1
CPI analysis by: ZENGAND

CPI cost MR9609-1: 526 h
summary: (Radio HW 401h + BI HW 125h)
Title Doc. Number Node RAT SP New Update CPI Update Descr. Owner
Type (h) (h) Verific.
Radio Description - G1, G2 L, NR, MR9609- 80 No Add new radio unit Radio
Radio 4456 ESS 1 description. HW
Install Radio - G1, G2 L, NR, MR9609- 100 Yes Radio

Radio 4456 ESS 1 HW
Replace Radio - G1, G2 L, NR, MR9609- 80 Yes Radio

Radio 4456 ESS 1 HW
Preventive x/1541-LZA 701 G1, G2 L, NR, MR9609- 40 No Radio

Maintenance 6001/1 ESS 1 HW
Radio 4456
Power Consumption 3/006 51-LZA G1, G2 L, NR, MR9609- 1 No Radio
Data 701 6001 ESS 1 HW
Radio Software 1/155 51-LZA G1, G2 L, NR, MR9609- 1 No Radio

Support 701 6001 ESS 1 HW
Animation of - G1, G2 L, NR, MR9609- 100 No Radio

Installation, Story ESS 1 HW
board
Animation of - G1, G2 L, NR, MR9609- 100 Yes BI HW
Installation, ESS 1
Animation team
Radio Node 24/1551-LZA 701 G1, G2 L, NR, MR9609- 20 No BI HW
Configurations 6001/1 ESS 1
Spare Parts 4/154 11-LZA G1, G2 L, NR, MR9609- 5 No BI HW

Catalogue 701 6001 ESS 1
Valid for: L, NR,ESS
5.35.2[9.3.2] CPI analysis summary for MR9002-SP4
The main differences between LB and MB 6626 radio are weight and size -
something that might impact the installation procedure.
Ericsson Internal

2023-12-21 PF24
Assumption:
LB and MB products can be included in same Description, same Install and

same Replace CPI, with only additions to already released MB 6626 radio.
Impact on animation is estimated to be limited. The general information will be

the same but some differences between MB and LB might need to be
described in some cases.
This means that the introduction of SP4 (LB) will have limited impact on Radio
CPI since MB CPI already exist and should be updated. However, the impact
is bigger than for introduction of a new FV.
One other impact is that the power cable dimensioning (length of power
cable) will be affect by the use of a voltage booster.
Also, the CB ratings will be affected depending on which of the three different
power options that are being use. The Power options needs to be described
in Install and Replace CPI as well.
Table 35: CPI analysis summary for MR9002-SP4
CPI analysis by: QMARJOH
summary:
Radio Description - G1, G2 G,W,L, MR9002- 20 No Apart from “standard impact” Radio
Radio 6626 NR,ESS 4 information about the HW
different power options
needs to be described
(including the use of Y-cable
and voltage booster). In
addition there will be a need
to specify the CB ratings for
these cases since the CB
recommendations will differ.
Install Radio - G1, G2 G,W,L, MR9002- 40 Yes Apart from “standard impact” Radio
and voltage booster
Replace Radio - G1, G2 G,W,L, MR9002- 30 Yes Apart from “standard impact” Radio
and voltage booster
Power Consumption 3/006 51-LZA G1, G2 G,W,L, MR9002- 1 No Radio
Data 701 6001 NR,ESS 4 HW
Animation of - G1, G2 G,W,L, MR9002- 40 No Radio
Installation, Story NR,ESS 4 HW
board
Animation of - G1, G2 G,W,L, MR9002- 40 Yes Radio
Installation, NR,ESS 4 HW
Animation team
Radio Node 24/1551-LZA 701 G1, G2 G,W,L, MR9002- 20 No NSV HW
Configurations 6001/1 NR,ESS 4
Site Installation 16/1551-LZA 701 G1, G2 G,W,L, MR9002- 60 Section Power Cable NSV HW
Products Overview 0003/1 NR,ESS 4 Dimensioning needs to be
updated due to the
possibility to use longer
Ericsson Internal

2023-12-21 PF24
power cables if a voltage

booster is used. This is not
included in the document
today.
Spare Parts 4/154 11-LZA G1, G2 G,W,L, MR9002- 5 No CDS HW
Catalogue 701 6001 NR,ESS 4
Compatibilities for 11/1551-LZA 701 G1 W MR9002- 10 Product number to be WCDMA
Hardware and 6003/1 4 added. SW
Software
Network Impact 18/109 48-HSD G1 W MR9002- 5 WCDMA
report 101 02/1 4 SW
BTS Parameter G1 G MR9002- 8 No Add new radio GSM
Description 4 SW
GSM RAN Gnnn x/10948- G1 G MR9002- 8 No Add new radio GSM
Network Impact HSC10312/25 4 SW
Report
Valid for: G,W,L, NR,ESS
feature:
Comment:

Table 36: CPI analysis summary for MR9002-8
CPI analysis by: QMARJOH
summary:
Radio Description - G1, G2 G MR9002-8 5 No Add 25 Gbps CPRI support Radio
Radio 6626 (if not already stated) HW
Radio Description - G1, G2 G MR9002-8 5 No Add 25 Gbps CPRI support Radio
Radio 4466 (if not already stated) HW
Radio Node 24/1551-LZA 701 G1, G2 G MR9002-8 20 No NSV
Configurations 6001/1
Valid for: G
feature:
Comment:

CPI analysis by: ZENGAND
CPI cost CPI: 20 hrs
summary:
Title Doc. Node RAT WP New Update CPI Update descr. Owner
number Type (h) (h) verific.
N Please issue a CR for Radio Configurations CDS
24/1551- Team PDU BI Systems HW
DU, G,W,L,
LZA 701 20 <PDLDIOCONF@pdl.internal.ericsson.com
BB N
Radio Node 6001 >
Configurations
Valid for: GSM, WCDMA, NB-IoT, LTE, NR, ESS
Customer No
specific feature:
Comment:
Ericsson Internal

2023-12-21 PF24

Table 38: CPI analysis summary for MR9268
CPI analysis by: ENNADEG / ZENGAND
CPI cost 35 h (15h Radio HW+ 20h CDS HW)
summary:
Title Doc. number Node RAT WP New Update CPI Update descr. Owner
Type (h) (h) verific.
Radio 4456 330/1551-LZA BB ESS, MI MR09268 5 N Add ESS support Radio HW
701 6001/1 (ESS+NB IoT).
701 6001/1 (ESS+NB IoT).
701 6001/1 (ESS+NB IoT).
Radio Node 24/1551-LZA BB ESS, MI MR09268 20 N Add ESS support CDS HW
Configurations 701 6001/1 (ESS+NB IoT).
Valid for: ESS, MI (NB-IoT In-band, Guard band)
Customer No
specific feature:
Comment: It is possible that ESS and NB-IoT support is already included in the listed Visby radio descriptions, in
this case, only review the documents.

CPI analysis by:
CPI cost CPI:
summary:
Radio Node DU, N
Configurations BB
Valid for:
Customer No
specific feature:
Comment:

CPI analysis by: ENNADEG
CPI cost CPI: 34 h
summary:
Radio Description 303/1551- G2, LTE, 1013 10 N Add frequency variant 6626 66B0A 66B28 C Radio
Radio 6626 LZA 701 G3 NR, 5-1 HW
6001/1 ESS
Power 3/006 51-LZA G2, LTE, 1013 2 N Add frequency variant 66B0A 66B28 C Radio
Consumption Data 701 6001 G3 NR, 5-1 HW
ESS
Radio Node 24/1551-LZA G2, LTE, 1013 20 N Add frequency variant NWS
Configurations 701 6001/1 G3 NR, 5-1
ESS
Spare Parts 4/154 11-LZA G2, LTE, 1013 1 N CSI HW
Ericsson Internal

2023-12-21 PF24
Catalogue 701 6001 G3 NR, 5-1

ESS
Valid for:
Customer No
specific feature:
Comment:

CPI analysis by:
CPI cost CPI:
summary:
Radio Node DU, N
Handled through CR.
Configurations BB
Valid for:
Customer No
specific feature:
Comment: Similarly as MR11923 SP 1, I consider this SP has no CPI impact.
Ericsson Internal

2023-12-21 PF24
[10] (EEF Xiaoyang Wang) (NFV Lisa Wang)Impact on Verification
5.36[10.1] General
[10.1.1] Radio SW verification(NFV Lisa Wang)
5.36.1.1[10.1.1.1] OTAR link for MR9002-SP1 Radio 6626 Dual band is as below.
306/1597-FCP 131 4771 Uen
OTAR link for MR9002-SP4 Radio 6626 Dual band

https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc846c89d?docno=431/1597-
FCP1314771Uen&action=current&format=ppt12
5.36.1.2[10.1.1.2] OTAR link for MR9002-15 7CC per port on B3 UL for Visby Radio
6626 B1B3 and Radio 4466 B1B3B40/B41: OTAR MR9002-15, the
analysis is in the sheet ‘OTAR remaining programs
5.36.1.3[10.1.1.3] OTAR link for MR9268-1 LTE GB NB-IoT coexistence with ESS on
visby radios
OTAR link for MR9268 LTE GB NB-IoT coexistence with ESS on Visby radios
5.36.1.4[10.1.1.4] For FDD Radio 4466,
For legacy functionalities 4466B1B3B7 refer to module and node level cases
from Visby 6626B1B3 with smaller scope coverage. Test vectors refer to
Visby 6626B1B3 also.
Visby 4466 mongoose impacted functionalities (VSWR, L1 reset, MMI

maintenance button, power drop handling, watch dog etc.) with SW/HW
change will be prioritized in module and node level testing.
4466 LO solution/branch mapping impacted area (carrier setup) will be

prioritized in module and node test.
New case coverage are needed for Visby platform new features (Deep sleep,
Quasi-Dynamic PA VDD), but can refer to AAS radio cases first as messages
between Radio and DU are the same.
OTAR MR8930-1 Visby Triple Band Radio 4466:

https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc6d3d6d1?
docno=428/1597-FCP1314771Uen&action=current&format=ppt12
Ericsson Internal

2023-12-21 PF24
5.36.1.5[10.1.1.5] For FDD Radio 4456
OTAR link for MR9609-1 Visby Triple Band Radio 4456:

Link
OTAR link for MR9002-8 25 Gbps CPRI Verification for GSM/WCDMA:

4G5G OTAR, the analysis is in the sheet ‘OTAR remaining programs’
5.36.1.6 OTAR link for MR9002-16 GSM 28M IBW Supporting on 6626 B1B3
OTAR link for MR9002-16 GSM IBW 28M Supporting on Visby 6626 B1B3.
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffcec5c93a?
5.36.1.7[10.1.1.6] OTAR link for MR10135-1 Radio 6626 B0AB28
OTAR link for MR10135-1, radio 6626 B0AB28
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffcebeeb32?
docno=596/1597-600/FCP1314771Uen&action=current&format=ppt12
[Note: Since this radio has been reverted from PV to FV, the NFV is not
planned anymore]
5.36.1.8[10.1.1.7] OTAR link for MR9002-SP13 SHP enable on 6626 B1B3 and
4466 B1B3B7
OTAR link for MR9002-SP13, SHP enable on 6626 B1B3 and 4466 B1B3B7
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffd02a8a33?
[10.1.2] HW IV(EEF Xiaoyang Wang)
Only one document to draft all I&V test analysis, represent in EEF which link is as
below:
All the products in Visby product family, including PV and FV are included in this
document and the document will be continuously updated.
Document link: 870/00653-3/FEA1018280Uen
Note 1: L1TM for 25G CPRI:
There is no impact on L1TM for 25G CPRI if it is supported by BBI and baseband
already. This is confirmed with Jean Toussaint.
Ericsson Internal

2023-12-21 PF24
Note 2: Required/Requested Test Vector link is as below.

https://ericsson.sharepoint.com/:x:/r/sites/Visby/Shared%20Documents/CA/
test_vector/Test_Vector_Request.xlsx?
d=w17191e47a7b94a70bbb3169005177423&csf=1&web=1&e=oaAwBU
(ESS/NR/LTE/SA-NB IOT with 10.1G/25G CPRI is included)
MR9002-8: no impact for HW IV view, confirmed by Xiaoyang Wang
5.36.1.9[10.1.2.1] General Analysis for Visby 6626
For B1 B3, it is the first product in the Visby product family, so I&V will perform
full scope test on the first product. All existing gaps including test house and test
equipment has been identified and solved during the PS stage.
For the coming frequency variants, it’s not fully analyzed at this time, and should be
done when more product information has been secured, including product design
change and target customer, etc.
5.36.1.9.1[10.1.2.1.1] General Analysis for Visby 6626 Low band
EEF document updated.

https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc5498029?
docno=870/00653-3/FEA1018280Uen&action=current&format=msw12
5.36.1.10[10.1.2.2] General Analysis for Visby FDD Radio 4466
For B1 B3 B7, it’s treated as the platform variant from Visby 6626 B1 B3, so there
are some test cases can refer to Visby 6626 B1 B3, e.g., time alignment, phase error,
power PLD and CE, CS, …
Based on the analysis result from Visby 6626 B1 B3, from I&V view, there is no new
added knowledge gaps, all activities should be treated as normal activities.
Only one thing that is not defined at this time is NGTE or ONE TE. It will be decided
during F3 of the project execution, depends on maturity of NGTE and project time
plan.
For the coming frequency variants, it’s not analyzed right now because of lack of
product information. This extra analysis will be done when more input documents are
ready.
5.36.1.11[10.1.2.3] General Analysis for Visby FDD Radio 4456
Radio 4456 B1C B3J B75C is treated as a product variant of Visby Radio
4466 B1B3B7
Link to EEF report for Visby Radio 4456

Ericsson Internal

2023-12-21 PF24
5.36.1.12[10.1.2.4] MR9002-SP15
In this SP, radio will support more GSM RX carriers for B3 (from 5 to 6), and
at the same time, B1 LTE/WCDMA carrier number will reduce from 6 to 5.
Only SW and function update and no HW change for this SP.
This SP will cover Radio 6626 B1 B3 and Radio 4466 B1 B3 B40 & Radio
4466 B1 B3 B41.
for 6626B1 B3:
RPV internal: no impact, no test needed.
ENV: no impact, no test needed.
EMC internal: no impact, no test needed.
EMC legal: no impact, no test needed.
RA: it will impact on the CE certification, minor scope tests are needed.
Report & certificate update are also needed.
for 4466 B1 B3 B40 & 4466 B1 B3 B41:
There will be no impact since they haven’t started testing. This feature will
merge with release test.
5.36.1.13 MR9268 ESS + NB-IoT
This MR will cover all Visby Radios for supporting ESS+NB-IoT. Additional
tests are needed as follows:
RPV internal will do some verification to secure radio performance for this
new RAT combination.
RA will be impacted, for CE & FCC (if any), additional tests and certification
works is needed.
ENV, EMC internal and EMC legal will not be impacted, and performance on
this new RAT combination will refer to previous release test results.
RPV
 DL: 1+N, 6+6dB boost, no SC offset
 UL: 1+0 3 SC spill over the ESS carrier edge
 Inband tests only
CE
 Carrier Config: 1+1 and 1+0, test on node level
 Both inband and out-of-band tests are needed
Ericsson Internal

2023-12-21 PF24
FCC/ISED
 1+0, 1+1, 1+N should all be tested
 all BW needs to be tested
 all products sold to US/Canada need to be tested.
Test Strategy
 RPV internal:
 One unit where selected to represent each platform.
 CE legal:
 One unit where selected to represent each platform.
 FCC
 all units to be tested
more information refer to EEF: link
5.36.1.14 MR9002-SP16
In this SP, radio 6626 B1B3 will support GSM IBW with 28MHz, increasing
from 20MHz previously.
Only SW and function update and no HW change for this SP.
This SP will cover only Radio 6626 B1 B3.
Only for 6626B1 B3:
RPV internal: Regression test is needed both on R1D and R2C.
RA: No impact to RA.
5.36.1.15[10.1.2.5] General Analysis for Visby FDD Radio 6626 B0AB28
This radio is treated as FV in Visby product family, ENV, EMC, RPV, RA and
also R&R will be impacted and tested.
For ENV, climate, mechanical, power PLD, Acoustic, EQ needs to be tested.
for EMC, both internal requirements and legal requirements are needed to be
tested.
for RA, CE certification is needed and CB certification is needed from safety

view.
for RPV, both in band and out of band requirements will be verified, and still,
multi-band test strategy will be applied.
Ericsson Internal

2023-12-21 PF24
for R&R, LTTC will be planned, considering component quality issues.ss
more details, refer to EEF, document link as follows
https://login.microsoftonline.com/92e84ceb-fbfd-47ab-be52-080c6b87953f/
saml2?client-request-id=421193a4-fe67-4246-9e29-
68a45b8620a0&sso_nonce=AwABAAEAAAACAOz_BQD0_zV5ZKt7eKs3WF
z-
A9fRZUcpiv9EIyLJ037MPa6IrvkXg4HX69RjlWDWUOHhW0bSPN7TX7hJz1n
ZhMIhlwNYX10gAA&mscrid=421193a4-fe67-4246-9e29-68a45b8620a0
5.36.1.16[10.1.2.6] MR9002-SP13
In this SP, radio 6626 B1B3 and 4466 B1B3B7 will support SHP on B1 and
B3, respectively.
HW update has been ready for this SP.
This SP will cover only Radio 6626 B1 B3 and Radio 4466 B1B3B7.
For both radios:
RPV internal: Regression test is needed both on R1F (4466 B1B3B7) and
R2D (6626 B1B3).
RA: No impact to RA.
https://anon.ericsson.se/eridoc/component/eriurl?docno=838/00653-3/
FEA1018281Uen&objectId=09004cffd0234c02&action=approved&format=ms
w12
5.37[10.2] FOA/FFI
FFI is needed for both MR9002-SP1 Radio 6626 middle band and MR8930-
SP1 FDD Radio 4466.
FFI is needed for MR9002-SP4 Radio 6626 Low band.
5.38[10.3] Field Trial
N/A
Ericsson Internal

2023-12-21 PF24
5.39[10.4] IODT
N/A
5.40[10.5] Transport test
N/A
Ericsson Internal

2023-12-21 PF24
6[11] Impact on External Stakeholders
6.1[11.1] Product Documents
Table 36 Document lists for MR9002-SP1
Doc number System document Impact Note

9/1056-HRB 105 700 Radio CRS for MSR WA FDD and TDD Y
Systems, General and Inband
91/1056-HRB105700 Radio CRS for MSR WA FDD and TDD Y

Systems, Out-of-band
2/10903-HRB105600 RBS6000 HW System Design Baseline Report N Visby as a

platform
already on
BL16A
1315-HRB105600 RBS 6000 HW Product Structure Y New Radio

Y New Radios
3/006 51-HSD 101 ERS HW Product information Data（PID)
101
N No need to
27/1056-HRB 105 600 RS Product information Data (PID) for ERS HW update for
Products MR9002-
SP1
Y
2/1056-HSD 101 101 Requirement Specification for ERS Combination
Y Impact from
2/1056-HRB 105 600 RS RBS 6000 Radio Configurations Radio 4466
pls refer to
9.1.1.2.
Impact from
Radio 4456
pls refer to
9.1.1.3
Y New HWAC
3/1551-3/HRB HWAC for Radio and Digital units for GSM G1
105 601
Y
1/001 21-HSD 101 ERS Site Products
101
Y
1/006 51-HRB 105 SFP Approved List
601
Table 37 Document lists for MR9002-SP4

Ericsson Internal

2023-12-21 PF24
Doc number System document Impact Note

9/1056-HRB 105 700 Radio CRS for MSR WA FDD and TDD Y
Systems, General and Inband
91/1056-HRB105700 Radio CRS for MSR WA FDD and TDD Y

Systems, Out-of-band
2/10903-HRB105600 RBS6000 HW System Design Baseline Report N Visby as a

platform
already on
BL16A
1315-HRB105600 RBS 6000 HW Product Structure Y New Radio

Y New Radios
3/006 51-HSD 101 ERS HW Product information Data（PID)
101
N No need to
27/1056-HRB 105 600 RS Product information Data (PID) for ERS HW update for
Products MR9002-
SP1
Y
2/1056-HSD 101 101 Requirement Specification for ERS Combination
Y
2/1056-HRB 105 600 RS RBS 6000 Radio Configurations
N Refer to
3/1551-3/HRB HWAC for Radio and Digital units Visby
105 601 platform
Y
1/001 21-HSD 101 ERS Site Products
101
N Refer to
1/006 51-HRB 105 SFP Approved List Visby
601 platform
6.2[11.2] Legal Aspects, Export Control and Third-Party Products (3PP)
1. There is no modification and addition of any information security

functionality for MR9002-SP1 Visby platform and MR8930-SP1 Visby PV.
There is no modification and addition of any information security

functionality for MR9002-SP4 in addition to Visby platform.
2. No new SW
3. New HW used encryption. Asic Mongoose is providing encryption for

Secure Boot based on ECDSA-384 encryption.
4. HW and SW products for US origin content and 3PP are listed as below.
For HW of Radio 6626 MR9002-SP1

Ericsson Internal

2023-12-21 PF24
Vendor Name or Ericsson Company HW name (FD in PRIM), version & Ericsson Product no including R- Design Country of
Name & Address web address State origin (COO)
TI RS485 HD Transceiver RYT1097749/1 US
TI AISG V3.0 OOK modem RYT1096418/2 US
VECTRON Modem SPXO RTL201697/1 US
ANALOG DEVICES Modem RF Switch RYT1226081/1 US
MICRON eMMC FLASH RYT9431000/081 US
MICRON QSPI FLASH RYT1434008/5129 US
MICRON DDR4 RYT1441602/5 US
MAXIM DDR4 LDO RYT1136497/3 US
TI Temperature sensor RYT124007/1 US
TI Buffer RYT3398245/1 US
XILINX ZU4 FPGA RYT139707/1 US
MARVELL RADON1.1 ROP1019160/2 US
TI Retimer RYT1097722/3 US
TI LTU RYT1021042/1 US
TI LDO RYT1136703/2 US
TI Digital controller RYT1137001/2 US
TI Boost controller RYT1136711/1 US
TI Full-Bridge PWM controller RYT1136706/1 US
TI Buck controller for DPA RYT1137004/1 US
Buck controller for FAN and
TI RYT1137013/1
ANT US
TI Buck converter RYT1131515/2 US
Onsemi 80V secondary MOSFET RYN1236189/1 US
Pulse 10uH, 26.3A power inductor REG7246352/10M US
Pulse 4.7uH, 39A power inductor REG7246351/47S US
Qorvo LNA RYT1016712/3 US
Qorvo RALF RYT1017123/1 US
ADI Acadia RYT1017120/2 US
Qorvo Acadia RYT1017119/2 US
Qorvo SPST RYT1226105/3 US
IDT SP4T RYT1226180/2 US
Qorvo SP4T RYT1226180/2 US
ADI AI Receiver RYT1026313/2 US
Anaren Attenuator 10dB 10W 6GHz UMF104009/10 US
IDT DSA,6-bit, 0.5dB LSB RYT1156072/1 US
ANALOG DEVICES PACC US
RYT120148/1
TEXAS IN PACC US
ANAREN M Driver input 3dB coupler UND106165/1 US
Ericsson Internal

2023-12-21 PF24
ANAREN M US
Driver output 3dB coupler UND106267/1
MURATA JPN
ANAREN M US
50 ohm Load REP015152/1
TDK JPN
ON SEMI PA Switch RYN123717/2 US
TOSHIBA JPN
ADI Palau RYT1026422/1 US
For HW of Radio 4466 MR8930-SP1 and Radio 4456 MR9609-SP1

Vendor Name or Ericsson Company HW name (FD in PRIM), version & Ericsson Product no Design Country
Name & Address web address including R-State of origin (COO)
TI RS485 HD Transceiver RYT1097749/1 US
TI AISG V3.0 OOK modem RYT1096418/2 US
VECTRON Modem SPXO RTL201697/1 US
ANALOG DEVICES Modem RF Switch RYT1226081/1 US
MICRON eMMC FLASH RYT9431000/081 US
MICRON QSPI FLASH RYT1434008/5129 US
MICRON DDR4 RYT1441602/5 US
MAXIM DDR4 LDO RYT1136497/3 US
MAXIM Reset supervision RYT1266207/1 US
TI Reset timmer RYT1086025/1 US
ON SEMI US
TI Reset buffer RYT3266000/7C US
TOSHIBA JPN
TI Reset buffer RYT3266000/52C US
TI Level shifter RYT3398245/1 US
TI
I2C translator RYT1096317/3
ON SEMI US
TI Temperature sensor RYT124007/1 US
Onsemi CLK buffer RYT1081013/2 US
Intel Mongoose ROP1019168/1 US
MARVELL RADON1.1 ROP1019160/2 US
TI Retimer RYT1097722/3 US
TI Timer RYT1086025/1 US
MAXIM Watch dog RYT1266207/1 US
TI LTU RYT1021042/1 US
TI Digital controller RYT1137001/2 US
TI Boost controller RYT1136711/1 US
TI Full-Bridge PWM controller RYT1136706/1 US
TI Buck controller for DPA RYT1137004/1 US
Buck controller for FAN and
TI RYT1137013/1
ANT US
Ericsson Internal

2023-12-21 PF24

Onsemi 80V secondary MOSFET RYN1236189/1 US
Pulse 10uH, 26.3A power inductor REG7246352/10M US
Pulse 4.7uH, 39A power inductor REG7246351/47S US
Qorvo LNA RYT1016712/3 US
Qorvo RALF RYT1017123/1 US
Qorvo Pre-driver ERYT1016704/1 US
Qorvo Acadia RYT1017119/2 US
Qorvo SPST RYT1226105/3 US
IDT SP4T RYT1226180/2 US
Qorvo SP4T RYT1226180/2 US
ADI AI Receiver RYT1026313/2 US
Anaren Attenuator 10dB 10W 6GHz UMF104009/10 US
IDT DSA,6-bit, 0.5dB LSB RYT1156072/1 US
ANALOG DEVICES PACC US
RYT120148/1
TEXAS IN PACC US
ANAREN M Driver input 3dB coupler UND106165/1 US
ANAREN M US
Driver output 3dB coupler UND106267/1
MURATA JPN
ANAREN M US
50 ohm Load REP015152/1
TDK JPN
ON SEMI US
PA Switch RYN123717/2
TOSHIBA JPN
ADI LO RYT1026411/1 US
ADI Palau RYT1026422/1 US
Mongoose ASIC, OPN
Intel ROP1019168/1
16001E, 3PP Software US
For HW of Radio 6626 MR9002-SP4
Only below new HW components are listed.

Vendor Name or Ericsson Company HW name (FD in PRIM), version & Ericsson Product no Design Country
Name & Address web address including R-State of origin (COO)
MARVELL Radon 1.1 (0.8) ASIC ROP1019160/3 US
Renseas LNA RYT1017171/1 US
Renseas RALF RYT1017169/1 US
Murata/Anaren COUPLER UND106265/1 US
ANAREN M B8 Driver output 3dB coupler UND 106 286/1 US
ANAREN M B8 Final input 2dB coupler UND 106 266/1 US
B20 Driver output 3dB
ANAREN M UND 106 265/1
coupler US
ANAREN M Driver input 3db coupler UND106188/1 US
Ericsson Internal

2023-12-21 PF24
NXP B8 Driver RYT 101 7114/1 US

NXP B20 Driver RYT 101 7059/1 US
For SW of Radio 6626, Radio 4466 and Radio 4456

Vendor Name or Ericsson Company SW name (FD in PRIM), version & Ericsson Product no including R- Design Country of
Name & Address web address State origin (COO)
Digital R1.1 SerDes FW, 3PP 2/CTX1010306 R1A(1.16-
Synopsis
Software 4) US
Palau, ADRV9030 API, 3PP CTC102767/1 R1A SE
ADI
Software 1/CTX 101 0319 R1A US
GNU Arm Embedded CTC 101 1005 R1A SE
ARM developer
Toolchain, 3PP Software 1/CTX 102 1854 R1A US
CXS 102 7391/1 R1A SE
FOSS DTC libfdt, 3PP Software
1/CAX 105 8805 R1A US
Xilinx Vivado, 3PP Software 9/CAX 105 8968 R1A US
WRL18 for XCS, 3PP CTC 101 6832 R1A SE
Wind River
Software 34/CAX 105 3085 R1A US
Customer Content
Management (CCM), CTC 101 6833 R2A
Wind River
Additions to WRL18 for 33/CAX 105 9820 R1A SE
XCS, 3PP Software US
Mongoose ASIC, OPN TBD, FW for Mongoose
Intel
16001E, 3PP Software ASIC US
Note:
This SW list was only valid for MR9002-SP1 and MR9002-SP2 in

previous study.
5. 3PP
New LMC CXP 203 0045/27 would be used in Visby Radio 6626 middle band
for MR9002-SP1.
New LMC CXP 203 0133/30 would be used in Visby FDD Radio 4466 for
MR8930-SP1 and Visby Low band Radio 6626 for MR9002-SP4.
For CXP 203 0133/30, CXP 203 0045/27 is as a base with new Mongoose
related 3PP instead of FPGA related 3PP.
As Mongoose is new, Mongoose will introduce new 3PP SW with TBD version
for MR8930-SP1 and MR9002-SP4.
For MR9002-16, there are no 3PPs and/or encryption algorithms included. No

changed, removed or added 3rd party products and/or encryption
algorithms/security functionality.
Ericsson Internal

2023-12-21 PF24
6.3[11.3] Patent Ideas
N/A
6.4[11.4] Future Enhancements
N/A
Ericsson Internal

2023-12-21 PF24
7[12] Terminology
7.1[12.1] Abbreviations
7.2[12.2] Concepts
Ericsson Internal

2023-12-21 PF24
8[13] References
[1] NDS Template and Instruction, 14/00201-1/FEA 202 8800 Uen

[2] MS RBS System Architecture (SAD), 1/155 53-HRB 105 700 Uen
(Link is to latest approved, as it reflects what is released)
[3] Architecture Runway (ARW), 8/006 71-11/FCP 130 4300/15 Uen
(Link is to latest, as it moves quicker than formal approval)
[4] DNEW Pre-Study Process, BURA-15:004202 Uen
[5] Common OA, 204/0360-200/FCP131 47
[6] Hardware Implementation Proposal for Visby Platform, 2/15941-300/FCP1330875
[7] MR7777 NDS: https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc36b2995?
docno=484/10268-300/FCP1314743Uen&action=current&format=msw12
[8] MR7777 OA report:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc22e5087?docno=260/0363-
400/FCP1314742Uen&action=current&format=ppt12

NDS VISBY Radio 6626 4466 4456

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NDS VISBY Radio 6626 4466 4456

Uploaded by

Copyright:

Available Formats

Ericsson Internal

Implementation Description 1 (431)

ENNADEG Andras Engel 566/102 68-300/FCP 131 4743 Uen