Airphone tester for 3GPP on CPRI
(5GC000633)
5G18A
• Working slide deck
• Isabelle Thebeaud, Eric Pugniere + other Authors
1
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Agenda
• High-level introduction
• Scope
• Participants
• Identified impacts
• Dependencies
• Open points
• Miscellaneous
2
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
High Level Introduction
• Feature driven by Feature ID 5GC000633 under 5G18A
• This feature introduces RU emulator function into Airphone Full L1 configuration
• AirPhone should be connected via CPRI to gNB
• gNB as Device under test (DUT) shall run nominal SW without any test mode
introduction
• All documents part of Airphone tester for 3GPP on CPRI are available on Sharenet
repository
https://sharenet-ims.int.net.nokia.com/livelink/livelink?func=ll&objId=557331763&objAction=browse&viewType=1
3
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
Scope
4
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Airphone tester for 3GPP on CPRI - Scope
•
Airphone configuration shall be based on ASIA + ABIK

RU emulator is implemented in Airframe
•
gNB configuration shall be based on ASIK + ABIK
•
CPRI start up and configuration
•
Routing of OAM messages between gNB and Radio Stub
•
RU emulator dynamic configuration, monitoring and measurements
•
OAM scenarios (shutdown, restart CPRI, SW upgrade, temperature, failures…)
5
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI - Scope
• 5GNB Configurations to support (Option 1)
•
One Airscale in front of one Airscale of the gNB
•
One ASIK has to support ONE or up to 2 x RU emulators
6
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI - Scope
• 5GNB Configurations to support (Option 2)
•
One Airphone Airscale in front of multiple Airscales of the gNB
•
One ASIK has to support several RU emulators (up to 6)
7
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI - Scope
• HW connection between 5GNB & 5G Airphone
•
3 options have been identified
•
•
•
Option 1 : Configuration based only on CPRI link
•
Synchro on HDMI cable
•
DHCP, I/Q, C&M managed only from CPRI
Option 2 : Configuration based on CPRI link + Ethernet link ( ASIK-ASIK) [Based on 5GC000425-H delivery]
•
Synchro on HDMI cable
•
I/Q on CPRI
•
DHCP + C&M on Ethernet cable
•
Drawback : modify OAM message routing compared to nominal 5GNB behavior
Option 3 :Configuration based on CPRI link + LMP (ASIK – ASIK) [Based on 5GC000495/496 delivery ??]
•
Synchro on HDMI cable
•
I/Q on CPRI
•
DHCP + C&M on LMP (TBC)
•
Advantage / Drawback : LMP TBD
 Option 1 selected
.
8
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI - Scope
• HW connection between 5GNB & 5G Airphone
•
Option 1: configuration based only on CPRI link
•
Synchro on HDMI cable
•
DHCP, C&M, I/Q on CPRI
gN
B
AirPhon
e
RU
Emulator
AirFrame
(ASIA)/ASIK
ABIK
9
For internal use
© Nokia Mobile Networks 2017
HDMI Cable (sync)
Megazone
ASIK
CPRI (I/Q + C&M
+DHCP)
ABIK
Airphone tester for 3GPP on CPRI - Scope
• HW connection between 5GNB & 5G Airphone
•
Option 2: configuration based on CPRI link + Ethernet link [Based on 5GC000425-H delivery]
•
Synchro on HDMI cable
•
I/Q on CPRI
•
DHCP + C&M on Ethernet cable
•
Drawback : Requires modification about 5GC000425-H Test Mode, DHCP + OAM CM message route different from nominal 5GNB behavior
AirPhon
e
RU
Emulator
Airframe
(ASIA)/ASIK
HDMI Cable (sync)
PDCCHSendR
eq
Ethernet
(DHCP + C&M)
CPRI (I/Q)
10
For internal use
ABIK
© Nokia Mobile Networks 2017
gN
B
Megazone
ASIK
ABIK
Airphone tester for 3GPP on CPRI - Scope
• HW connection between 5GNB & 5G Airphone
•
Option 3: configuration based on CPRI link + LMP (ASIK – ASIK) [Based on 5GC000495/496 delivery ??]
•
Synchro on HDMI cable
•
I/Q on CPRI
•
DHCP + C&M on LMP (TBD)
•
Advantage / Drawback : TBD, requires dedicated test mode, DHCP + OAM CM message route different from nominal 5GNB behavior
AirPhon
e
RU
Emulator
AirFrame
(ASIA)/ASIK
ABIK
11
For internal use
© Nokia Mobile Networks 2017
HDMI Cable (sync)
gN
B
Megazone
LMP
(DHCP + C&M)
ASIK
CPRI (I/Q)
ABIK
Airphone tester for 3GPP on CPRI - Scope
• Restrictions
•
eLLF not supported by 5G Airphone
•
SW update (TBC)
12
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
Participants
13
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Participants
Area
Name/Team
Contact info
Product Management
Richard Korbacher
Korbacher, Richard (Nokia - DE/Ulm)
System Engineering
Eric Pugniere
Isabelle Thebeaud
Désiré Guel (L1)
Fatma Kharrat Kammoun (L1)
Jeffrey Scott (OAM)
Patrick Moisy
Emmanuel Froger (L1)
Alexandre Brandon
Slim Chabbouh
John Torregoza (OAM)
Armin Splett/Stacy Fishkin (RF)
Pawel Koch (OAM RF)
Pugniere, Eric (Nokia - FR/Nozay)
Thebeaud, Isabelle (Nokia - FR/Nozay)
Guel, Desire (Nokia - FR/Nozay)
Kharrat Kammoun, Fatma (Nokia - FR/Nozay)
Scott, Jeffrey (Nokia - US/Irving)
Moisy, Patrick (Nokia - FR/Nozay)
Froger, Emmanuel (Nokia - FR/Nozay)
Brandon, Alexandre (Nokia - FR/Nozay)
Chabbouh, Slim (Nokia - FR/Nozay)
Torregoza, John (Nokia - PL/Wroclaw)
Splett, Armin (Nokia - DE/Ulm)/Fishkin, Stacy (Nokia - US/Murray Hill)
Koch, Pawel (Nokia - PL/Wroclaw)
SME AirPhone
Mickael Morette
Daniel Guigui
Morette, Michael (Nokia - FR/Nozay)
Guigui, Daniel (Nokia - FR/Nozay)
A&T
Mikko Taskinen (L1)
Edgards Curkste (L1)
Taskinen, Mikko (Nokia - FI/Espoo)
Curkste, Edgars (Nokia - FI/Espoo);
BBP
Xavier Boutaud
Jean-François Jamond
Boutaud De La Combe, Xavier (Nokia - FR/Lannion)
Jamond, Jean-Francois (Nokia - FR/Nozay)
Others
14
For internal use
Lukasz Grabinski (RF)
Chadhi Tarhini
Tomasz Antczak
Mani Iyer (RF)
© Nokia Mobile Networks 2017
Bartosz Jelonkiewisz
Grabinski, Lukasz (Nokia - PL/Wroclaw)
Tarhini, Chadi (Nokia - FR/Nozay)
Antczak, Tomasz (Nokia - PL/Wroclaw)
Iyer, Mani 1. (Nokia - US/Murray Hill)
Jelonkiewicz, Bartosz (Nokia - PL/Wroclaw)
Airphone tester for 3GPP on CPRI
Identified Impacts
15
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Airphone tester for 3GPP on CPRI – Identified impacts
Current impact list
• HW configuration :
o Airphone configuration shall be based on ASIA + ABIK
o gNB configuration shall be based on ASIK + ABIK
• Assumption : Only one GNSS source used between AirPhone and gNB
• HW connection between 5GNB & 5G Airphone : It needs to be put in place with following impacts
o 3 Options : (see above slides)
o ABIK to ABIK interface (Master/Master or Master/Slave ?)
o New SysCom link needed from Airphone side to manage Megazone - RU Emulator
communication
o Figure below gives the proposal for RFSW RP1 communication protocol stack for the following
configuration :
 gNB (ASIK/ABIK) vs Airphone (Airframe/ABIK)
16
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts
Protocol stack (tbc)
Real Radio Unit
APPLI
(RFSW RP1)
UDPCP
UDP
IP
Eth
RU (Emulated) on AirFrame
ASIK OAM
CPRI R8
APPLI
(RFSW RP1)
SICP
Linux IPC
C&M
Syscom GW
SICP
17
SICP
SCTP
SCTP
IP
IP
IP
ETH
Linux
IPC
CC&S
Airframe
Syscom GW
UDPCP
UDP
SICP
ETH
OAM RU
Syscom GW
Fs-In-C
SICP
SRIO
(T11)
ETH
AXM, ASIA
© Nokia Mobile Networks 2017
Syscom GW
UDPCP
SICP
ETH Switch
GRETAP
CC&S, K2, ABIK
AirScale(Airphone)
SICP
Linux
IPC
Linux
IPC
IP
ETH Switch
SRIO
(T11)
1GE
SICP
UDP
1GE
CPRI R8
ABIK, FE FPGA
CPRI R8
ETH
GRETAP
GRE
GRE
IPV4
IPV4
ETH
ETH
CC&S
K2+FE
AirScale (5GNB)
Node OAM
Airphone tester for 3GPP on CPRI – Identified impacts
Current impact list
• Functions handling by Radio emulator shall include :
• RAP startup in order to proceed the Radio Stub (RU Emulator) auto/detection and
configuration,
• Airphone Radio Emulator shall be able to support gNB IP internal address allocation
• CPRI to setup ( This will involve CPRI driver startup & configuration),
• RU emulator dynamic configuration, monitoring and measurements
• OAM scenarios list to identify (shutdown, restart CPRI, SW upgrade, t°, etc…)
• Dependencies impacts:
• Strong dependency on 5GC000425 feature, need to clarify L1 impact on
5GC000633 based on 5GC000425 feature content
• Dependency on 5GC000350 (should not involve any impact on 5GC000633 if test
mode is available on gNB, tbc)
18
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Reference : 5G Node B Users scenarios in Doors.
Take care that described scenarios are based on ASIA and 2nd generation 5G RF
Enabling RU during BTS startup phase (USR_398) 1/2
•
Pre-condition :Route for IP connectivity between ASIA and radio unit(s) connected to ABIK has been
configured
1. OAM SW requests PSSW to enable interface towards the 2nd generation 5G RF unit.
2. PSSW configures the IP route from ABIK towards ASIA.
3. PSSW configures a host route from ASIA towards the 2nd generation 5G RF unit.
• Open point : How PSSW will configure host route to RU emulator – impact to be analyzed
•
Post condition: Enabling RU connections during BTS startup is done and OAM is able to do RP1 level
functionalities
19
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Enabling RU during BTS startup phase (USR_398) 2/2
• Tasks to be handled by RU emulator :
o L3a DiscoveryMessage for CPRI link received from RFSW
It indicates L3a topology detection information from radio unit(s) connected to ABIK's QSFP ports.
CPRI L3a Discovery message has the content like specified in SM-RM CPRI L3 5G IFS.
How RFSW handle the L3a Discovery messages? (message content, when and what is the trigger so
that RFSW will send those messages…)
o RU IP allocation by means of DHCP
-
RFSW (DHCP Client) asks own RF module IP address and other radio protocol specific DHCP
options to FCT AXM in ASIA (DHCP Server).
How RFSW ask for its own IP address? (message content, when and what is the trigger…)
Clarify “other radio protocol specific DHCP options “
-
FCT AXM in ASIA (DHCP Server) allocates RF module IP address and other requested data to
RFSW (DHCP Client).
How RFSW handle those received info?
20
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Autodetect and configure during RU startup (USR_372) 1/5
• Pre conditions :
- RU is connected with optical cable(s) to Baseband Module(s) and RU is powered on.
- 5GNB_USR_398: US: Enabling RU connections during BTS startup
- Ethernet and RP1 connection between RAC and RU are enabled
- OAM has enabled SysCom communication between OAM and Radio Unit (RU)
• Post conditions:
Radio Unit (RU) is autodetected and configured. Radio unit's states in BIM and in WebUI are:
- availabilityState = onLine
- proceduralStatus = configured
- operationalState = enabled
21
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Autodetect and configure during RU startup (USR_372) 2/5
Tasks to be handled by RU emulator :
• Keep alive connectivity via RP1
1. RFSW starts to send RP1 moduleReadyInd messages to OAM.
2. OAM receives moduleReadyInd and updates RU HW states (proceduralStatus = Initializing, availabilityStatus = Online) to
BIM.
3. OAM sends moduleReadyAck towards RFSW and informs about keep-alive polling period.
RP1 moduleReadyInd (msg content, what is the trigger/preconditions …..)
How RFSW handle moduleReadyAck (actions done following this message..)
Every keep alive polling period,RFSW sends RP1 moduleReadyInd msg to OAM (tbc)
• RU SW version negotiation via RP1
1. OAM sends SW Inventory Request (swInventoryReq) to RFSW.
2. RFSW sends SW Inventory Response (swInventoryRsp) including the active SW version (bldVersion &
bldName) and active & passive files to OAM.
SW inventory procedure: how is it handled in RFSW? Proposition is that RF SW version is up to date (=> no RF
SW Update will be done). (swInventoryRsp message content …)
22
For internal use
3. OAM checks the active and passive file versions and the integrity of files.lities
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Autodetect and configure during RU startup (USR_372) 3/5
Tasks to be handled by RU emulator :
• ModifyParameterReq messages (step1)
1. OAM subscribes itself to alarms from RFSW (configuration of fault management MO (subscribe
parameter) with modifyParameterReq)
2. RFSW enables alarm notifications and acks with parValueChangeInd.
3. OAM subscribes itself to LED indications from RFSW (configuration of LED MO (subscribe parameter)
with modifyParameterReq)
4. RFSW acks the configuration of LED managed object by sending parValueChangeInd to
OAM.
How RFSW handle ModifyParameterReq?
What should be done in RU emulator?
<CPRI timing configuration using CPRI timing related MOs or fixedly in L1 (details
specified in RPSW spec item 5GC000253-A-c)>
23
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Autodetect and configure during RU startup (USR_372) 4/5
Tasks to be handled by RU emulator :
• ModifyParameterReq messages (step2)
1. OAM requests configuration of Module MO (subscribe parameter) by sending modifyParameterReq to RFSW.
2. RFSW acks the module configuration with parValueChangeInd.
3. OAM checks whether RU is in working state (FDEV: RU's blockingState is blocked).
4. OAM request configuration of the Antenna Line MO parameters with modifyParameterReq to RFSW.
5. RFSW acks the Antenna Line configuration with parValueChangeInd.
6. OAM requests configuration of the Temperature Control MO parameters (default profile) with modifyParameterReq to
RFSW.
7.. RFSW acks the Temperature Control profile configuration with parValueChangeInd.
8. OAM provides a valid date and time (DateTime MO) reference (BCN and local time pair obtained from CC&S) to the
RFSW.
9. OAM updates RU HW states (availabilityStatus = Online, proceduralStatus = Configured, operationalState = Enabled) to
BIM.
10.. WebUI gets notification about enabled RU in BIM.
24
How RFSW handle ModifyParameterReq? What should be done in RU emulator?
What should be the value(s) to set for module MO / Antenna Line / Temperature Control profile configuration.
© Nokiawith
Mobileack
Networks
2017
(is “stub
response”
a suitable solution ?)
For internal use
.
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Autodetect and configure during RU startup (USR_372) 5/5
Tasks to be handled by RU emulator :
8. OAM provides a valid date and time (DateTime MO) reference (BCN and local time pair obtained from CC&S) to the
RFSW.
Point 8; How RFSW handle DateTime MO info ?
Does RFSW use this DateTime MO?
What should be done in RU emulator?
.
25
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
RU Reset
Tasks to be handled by RU emulator :
1. OAM stops polling of RU.
2. OAM sends modifyStateRequest (restart) to RFSW to initiate HW (power-on) reset for the module.
3. OAM updates reset cause (reset requested) and following HW states to RU in BIM:
- Operational state = Disabled, - Availability status = Offline, Procedural status = Reset
How RFSW handle ModifyStateReq?
What should be done in RU emulator?
.
26
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Antenna carrier configuration and activation during cell service startup (US_320)
• Pre conditions :
•
5GNB_USR_372: Autodetect and configure RU during startup
• Post conditions:
•
Antenna carrier configuration towards 5G-L1-DL and RU AND antenna carrier activation towards RU is done during cell service
startup.
•
How RFSW handle ModifyParameterReq? What should be done in RU emulator?
27
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Antenna carrier configuration and activation during cell service startup (US_320)
Tasks to be handled by RU emulator
1.1 OAM sends modifyParemeterReq to RFSW to create CpriAirFrameTiming object (see details from SM-RM
CPRI L3 5G IFS, ref. also to 5GC000229).
1.2 RFSW responds to the requests by parValueChangeInd message to OAM.
2. OAM sends/receives modifyParamReq/parValueChangeInd RP1 messages to/from RFSW to create antenna
carriers (dynamic Managed Objects created like specified in resource allocation examples in RP1 IFS / SM-RM
CPRI L3 5G IFS) but does not activate carriers yet in this phase (Tx.active / Rx.active is set to FALSE)):
2.1 OAM sends modifyParameterReq to RFSW to create
DownlinkAntennaCarrierContainer/UplinkAntennaCarrierContainer objects as a part of resource allocation.
2.2 RFSW responds to the requests by parValueChangeInd message to OAM.
2.3 OAM sends modifyParameterReq to create Tx objects (for configuration of single downlink antenna
carriers) and Rx objects (for configuration of single uplink antenna carriers) including center frequencies (SCF),
bandwidth (SCF), delays and TX carrier power (SCF) as a part of resource allocation.
2.4 RFSW responds to the requests by parValueChangeInd message to OAM.
How RFSW handle ModifyParameterReq? What should be done in RU emulator?
28
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts - RAP startup
Antenna carrier configuration and activation during cell service startup (US_320)
Tasks to be handled by RU emulator
3. OAM sends “Antenna carrier mapping request” (sub cell, antenna line, Tx/Rx) to 5G-L1-DL.
4. 5G-L1-DL sends “Antenna carrier mapping response” to OAM.
5.. <5GC000254: Subcell Group setup from OAM to 5G-CP-CM (includes resource mapping towards L2), see
5GNB_USR_220: Cell service startup>
6. OAM sends modifyParamReq RP1 message to RFSW to activate antenna carriers created in step 1
(Tx.active / Rx.active is set to TRUE) (Trigger to this step is that OAM has received
CPCM_AntennaCarrierActivationReq from 5G-CP-CM (see 5GNB_USR_220: Cell service startup)), OAM can
activate antenna carriers right after it reseives this message.)
7. RFSW sends parValueChangeInd RP1 message to OAM.
8. <5GC000254: Setup all the Cells, see 5GNB_USR_220: Cell service startup>r mapping response” to OAM.
How RFSW handle ModifyParameterReq? What should be done in RU emulator?
29
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts – OAM – RU Emulator
Exchanges
Points to focus on during analysis
• During OAM – Ru emulator exchanges we should focus on the following points :
- What should be the values of the datas sent in RU emulator response ? Does the data value
matters or not for OAM?
- Is the RU emulator response mandatory? Meaning if the RU emulator does not answer (or if it
sends bad values), will the OAM be blocked?
- Is OAM – RU interface stateless or not?
30
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
Dependencies
31
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Airphone tester for 3GPP on CPRI – Feature Dependencies
• 5GC000425 - E2E call with 3GPP-compliant L1 and L2 (5G18A)
• 5GC000350 – Long fiber support between RAU and RU (5G17A)
• 5GC000608 – Supported 5G RAP configurations – III (5G18A)
• 5GC000555 – Startup with ASIK and ABIK for Cloud BTS (5G18A)
• 5GC000644 – CPRI Looping on ABIK
• 5GC000620 - One RAU Dual common plugin unit operation
• (tbu)
32
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
Open Points
33
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Airphone tester for 3GPP on CPRI – Identified impacts Open points
o Full Object Model of all 5G Radio Units must be supported (read/write emulation) to avoid
errors with ASIA/ASIK.
AEWA 39GHz, AEUA 28GHz, AEQA 3.5GHz AEQD 3.7GHz, AETB 4.5GHz, etc.
How RU emulator handle the different types of RU?
o CM Config mgmt:
What parameters are needed? Use a Manual configuration instead of reception from gNB (bw,
carrier freq, etc) on Airphone? Is this possible? Validation/consistency checks on related
parameters? Investigation needed..
o PM Counters: Airphone to support most 5G18A Counters? Part of 5G633 or 5G425 carry forward?
Already part of L1 / L2 support for 5G18A, what is supported on RU? RF counters sent to OAM? 1st
point: Do these exist on RF side? Mani?
o FM Alarm generation : How RU emulator handle FM alarms? Should RU emulator generate FM
alarms?. If yes which Alarms ?
34
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts Open points
o Sync via HDMI between ASIA-ASIK
Number of RUs supported by RU emulator : refer to slides “5GNB Configurations to support
(option 2)“ in this document
o OAM scenarios supported by RU emulator has to be identified :
(shutdown, restart CPRI, SW upgrade, temperature, failures…)
RU is power off/Up, RU is reset,
Use cases: RU power up before gNB – gNB power up before RU
o 5GNB_USR_411: US: CPRI link synchronization lost :
o
- RU resets triggering CPRI link synchronization loss (5GNB_USR_266, 5GNB_USR_279).
- RU is powered off.
- The cable between RU and Baseband Module is broken or otherwise unusable.
- SFP for the cable is removed at Baseband Module.
o 5GNB_USR_279: RU Reset (CPRI L1 Level) (Further Development)
(a reset of 5G Radio Unit (RU) using the CPRI-specific HW reset).
o 5GNB_USR_320: US: Antenna carrier configuration and activation during cell service
startup
35
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Identified impacts Open points
o Synchro when gNB ABIK (Master) is in front to AirPhone ABIK (Master)
o Tunelling (GRE) from ASIK to ABIK
o C&M Channel termination in Airphone
o Protocol Stack RU <-> OAM
o 5GC000579 (long fiber and automatic fiber length measurement) impact on RU emulator
Hearbeat Messages are used to compute the fiber length. Need to clarify if response from Real RU is
sent by CPRI L3 or CPRI L1/L2. Analysis to be done for RU emulator.
o How RU emulator handle the following scenarios (lower priority) :
5GNB_USR_385: US: Show RAP HW in WebUI (Show as Airphone or real RF Unit based on
RAC/RAP config?)
5GNB_USR_307: US: Monitor BTS VNF States and RAP HW States (RU State always ‘green’?)
5GNB_USR_294: US: RAP HW LED Display(Not Needed?)
36
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI – Open Points
Overall open points summary
• OAM and RF SW synchronization to manage
• Radio emulator design strategy based either on existing RF SW or either from scratch
• RU functions to emulate shall be consolidated
• OAM messages to support between OAM SW instance running on Aiscale and OAM SW
RU
• OAM scenario list to identify based on gNB running original SW outside any test mode
• Radio emulator emulates a single RU or several RUs
• L1 impact to clarify
• Repository for OAM specifications
37
For internal use
© Nokia Mobile Networks 2017
Airphone tester for 3GPP on CPRI
Miscellaneous
38
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID
Miscellaneous
• Next meeting
Dedicated separate meeting or weekly meeting
• Next step
FS1TA offline review to define
39
For internal use
© Nokia Mobile Networks 2017
40
07/07/2017
For internal use
© Nokia 2017 Airphone_Tester_for_3GPP_on_CPRI_Slide_Deck - Version 1 - 5G Airphone TD - DocID