View
6
Download
0
Category
Preview:
Citation preview
Jens IrrgangNg4T GmbHJune 2018
ng4T Testing Solutionng4T Testing Solutionand integration in OAI CI and integration in OAI CI
benchbench
Why is ng4T part of OAI?
ng4T – a new member of the OAI community
Company based in Berlin, Germany
ng4T develops protocol test systems, so called Network Emulators
Proprietary code – independent from OAI code
ng4T solutions not designed for productive operation (purely for testbed)
ng4T is an early adaptor of new mobile technologies-> 5G Non-Standalone Option 3.x (EN-DC) already supported (beta)-> 3GPP Rel. 15 from December 2017
OAI / ng4T roadmap alignment-> autarkic test solution -> independent from OAI development tool chain
ng4t.com © 2018 ng4T GmbH 2
2G - GSM & GPRS3G - Femto 5G EN-DC 4G - LTE
InternetInternet
BTS
NR gNB
LTE eNB
HeNBHeNB
HeNB
2G - GSM & GPRS
NG40 CORE and extensions
MSCSMS-C
SGSN
GGSN
PGW
PCRF
P-CSCFPSTNPSTN IMSIMSApplication
FunctionApplication
Function
MMESGW
HLR / HSS / EIR
Packet Generator
Packet Generator
NG40 Radio Access Modules
eNB
HeNB-GW
ng4T – from RAN to CORE:Virtual RAN Modules
HNB
HNB-GW
Non-3GPP
TTG
WiFi-APWiFi-AP
TTG
WiFi-AP
ePDG
ng4T – from RAN to CORE: Splitted CORE
ng4t.com © 2018 ng4T GmbH 4
SGi
IODT Test Line: Integration Testing and Development
TAC Test Line: Patch Testing and Issue Reproduction
HNB/HeNB
HNB/HeNB
HNB/HeNB
Test Line: Product Testing and Feature Validation
TAC Gateway
DQA Gateway
IODT Gateway
Iu over IPIu over ATM
S1/S1-U over IP
S1
IuCS
S1-U
IuPS
NG40 - 3G 4G Core
Network EmulatorInternet
ng4T – from RAN to CORE: Combined CORE
ng4t.com © 2018 ng4T GmbH 5
SGW
HSSMME
vMME
diameter
vRAN
Application Server
vHSS
vSGW
PCRF
vPCRF
OCS
vOCS
DIA_net[6]Gx
Gy
S6aS6a
S1-MME_net[3]
S1-U_net[4]
S11_net[1]
PGW
vPGW
Gx/Gy
SGi_net[7]
S5_net[5]
s1ap/nas
gtpv1
gtpv2
gtpv1/v2
4 8 12 16 20 24 28 320
20
40
60
80
100
120
140
160
180
NG40-vRAN: Generated User Plane Throughput for EPC Verification
INTEL CPU Server: Required number of CORES
[Gb
ps
UL
+ D
L]
NG40 Performance Figures
4 8 12 16 20 24 28 320
2
4
6
8
10
12
14
16
18
NG40-vRAN Capacity: Number of emulated UEs for EPC Verification
INTEL CPU Server: Required number of CORES
[Mio
]
4 8 12 16 20 24 28 320
10000
20000
30000
40000
50000
60000
70000
80000
90000
NG40-vRAN: Number of eNBs
INTEL CPU Server: Number of CORES
4 8 12 16 20 24 28 320
10000
20000
30000
40000
50000
60000
70000
80000
90000
NG40-vRAN: Control Plane Procedures
INTEL CPU Server: Number of CORES
[tps]
NG40 Performance Figures
ng4T at the 2nd ETSI NFV Plugtests:Integration with OAI
ng4T at the 2nd ETSI NFV Plugtests:Network Service Architecture
Non-Standalone (E-UTRA-NR Dual Connectivity)vs. Standalone Architecture
Current Activities
ng4t.com © 2018 ng4T GmbH 10
5G Core Topology and Interfaces
NSA vs. SA Architecture – Control Plane Comparison
N1 / N2
NAS
NG-AP
SCTP
IP
Ethernet
S1-MME
NAS
S1AP
SCTP
IP
Ethernet
Non-Standalone Standalone3GPP TS 24.501 V1.0.0 (2018-3): Non-Access-Stratum (NAS) protocol for 5GC
NSA = LTE protocol stack
3GPP TS 38.413 V0.7.0 (2018-03): NG Application Protocol (NGAP)
3GPP TS 24.301 V15.1.0 (2017-12): Non-Access-Stratum (NAS) protocol for EPS
SA → new protocol stack
→ disruptive innovation
NG40 Roadmap - 3GPP R15 Specifications Details
23.501: System Architecture for the 5G System 23.502: Procedures for the 5G System 24.501: Non-Access-Stratum (NAS) protocol for 5G System 38.300: NR; NR and NG-RAN Overall Description 38.401: NG-RAN Architecture Description 38.410: NG-U, Userplane interface (gNB - UPF) 38.413: NG-RAN; NG Application Protocol (NGAP) 38.420: Xn interface control plane description 38.801: NR Radio access & interfaces
Describes Non standalone options, see section 10,1,2
Describes Xx interface (LTE eNB – NR gNB), see sections: 10.1.2.x.y,
Realization of Network slicing, see section: 8
38.413 is for N1 interface describing NG-AP (ASN.1 definitions are incomplete) 38.410 is for N3 interface describing NG-U (GTP-U new extension header) 24.501 is for N2 interface describing 5G NAS (New context handling)
Definitions
EN-DC: E-UTRA-NR Dual Connectivity
EN-gNB / NR-gNBNode providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC.
ng-eNB / eLTE eNBNode providing E-UTRA user plane and control plane protocol terminations towards the UE. Connected via the NG-interface to the 5GC or via S1-interface to the EPC.
NG-C: Control plane interface between NG-RAN and 5GC
NG-U: User Plane interface between NG-RAN and 5GC
NG-RAN node: either a gNB or a ng-eNB
ng4t.com © 2018 ng4T GmbH 14
EN-DC: What’s new?
ng4t.com © 2018 ng4T GmbH 15
S1AP: 3GPP TS36.413 V15.1.0 (2018-03)
New S1AP Procedures: Secondary RAT Data Usage Report
The purpose of the Secondary RAT Data Usage Report procedure is to provide information on the used NR resources during EN-DC operation.
The eNB initiates the procedure by sending the SECONDARY RAT DATA USAGE REPORT message to MME.
EN-DC: What’s new?
ng4t.com © 2018 ng4T GmbH 16
S1AP: 3GPP TS36.413 V15.1.0 (2018-03)
New S1AP Messages: Secondary RAT Data Usage Report
This message is sent by the eNB to report Secondary RAT data usage.
Direction: eNB MME
IE/Group Name Presence Range IE type and reference
Message Type M 9.2.1.1
MME UE S1AP ID M 9.2.3.3
eNB UE S1AP ID M 9.2.3.4
Secondary RAT Usage Report list
M 9.2.1.124
Handover Flag O 9.2.1.125
EN-DC: What’s new?
ng4t.com © 2018 ng4T GmbH 17
S1AP: 3GPP TS36.413 V15.1.0 (2018-03) New S1AP IE’s:
Secondary RAT Usage Report List
This IE provides information on the NR resources used with EN-DC.
EN-DC: What’s new?
ng4t.com © 2018 ng4T GmbH 18
S1AP: 3GPP TS36.413 V15.1.0 (2018-03) New S1AP IE’s:
Handover Flag
The Handover Flag IE indicates that the MME should buffer the secondary RAT data usage report since the report is sent due to handover.
EN-DC: What’s new?
ng4t.com © 2018 ng4T GmbH 19
S1AP: 3GPP TS36.413 V15.1.0 (2018-03) New S1AP IE’s:
NR UE Security Capabilities
Optional IE for several existing messages (INITIAL CONTEXT SETUP REQUEST, UE CONTEXT MODIFICATION REQUEST, HANDOVER REQUEST, PATH SWITCH REQUEST, PATH SWITCH REQUEST ACKNOWLEDGE, DOWNLINK NAS TRANSPORT)
IE/Group Name Presence Description
NR Encryption Algorithms
M Algorithms as defined in TS 33.401
NR Integrity Protection Algorithms
M Algorithms as defined in TS 33.401
Thank You For Listening
ng4t.com © 2018 ng4T GmbH 20
Recommended