3gpp & ietf collaboration on 5g
TRANSCRIPT
1
3GPP&IETFCollaborationon5GGeorgMayer,3GPPCTChairman,Huawei
2
TSG RANRadio Access
Networks
TSG SAServices & Architecture
TSG CTCore Network &
Terminal
CT1end-2-end
aspects
CT3interworking with external networks
CT4network internal
protocols
CT6smart card
applications
RAN1radio layer 1
RAN2radio layer 2 & 3
RAN3RAN-CN interface
RAN4radio performance
RAN5terminal testing
RAN6legacy radio
SA1services &
requirements
SA2architecture
SA3security
SA4Codec
SA5management
SA6(mission critical)
applications
PCGProject Coordination Group
Partners
China
Japan
Japan
India
Europe
Korea
North America
MemberOranizations&Companies
ofPartnersparticipatein3GPPTSGs&WGs
3
How3GPPworks
› 3Stagesofspecification› Stage1:Requirements› Stage2:Architecture› Stage3:Protocols
› Consensusdriven(tougherthanrough)
› Contributiondriven› youneedtoparticipateinordertogetyourideasdiscussed
› Face-to-facemeetings
› Releaseswithstrictdeadlines
4
3GPPsofar› 3G/UMTS
› CircuitSwitched(CS)&PacketSwitched(PS)Domainsinparallel
› LTE› AllIP› MobileBroadband› VoiceoverLTE(IMS/VoLTE)
› LTEAdvancedPro› Pavesthewayfor5G› CellularInternetofThings› MissionCriticalPushToTalk› DedicatedCoreNetworks,TrafficSteering,...
5
6
7
One .
8
One .(please)
9
5Gin3GPP
› 3GPPdevelopsadeployable5Gsystemnow
› StudyPhase› Rel-14studiesonrequirements– completed
› Rel-15studiesonarchitectureandprotocols
› Twophasesforthenormativework› Phase1(Rel-15)tobecompletedbyJune2018
addressesthemoreurgentsubsetforcommercialdeployments
› Phase2(Rel-16)tobecompletedbyMarch2020IMT2020submission,addressesallidentifiedusecases&requirements
10
P2Studies
P2Normative
P2NormativeP2Studies
P2Normative
5GTimeline
10
2016
Q1 Q3Q2 Q4
2017
Q1 Q3Q2 Q4
2018
Q1 Q3Q2 Q4
2019
Q1 Q3Q2 Q4
Rel-14/5GStudyRel-15/5GPhase1
Rel-16/5GPhase2
Archite
cture
Protocols P1Studies
P1NormativeP1Studies
P1Normative
P1NormativeP1Studies
Requ
iremen
ts
11
R15:September2018
11
12
NOTEWELL:WorkinProgress
› Thestatementsconcerning5GRequirements,Architecture,Protocols,Security,etcarecurrentlyunderdiscussionin3GPPandcanchangeanytime.
› Tofollowtheworkyoucan› readourspecifications(updatedeveryfewmonths)› followtheworkinggroups(meetingseveryfewweeks)
13
SomeDocumentation(CoreNetwork)› Requirements
› High-Level5GRequirements– TS22.261http://www.3gpp.org/DynaReport/22261.htm
› Architecture› Completedstudy– TR23.799http://www.3gpp.org/DynaReport/23799.htm
› Architecture– TS23.501http://www.3gpp.org/DynaReport/23501.htm
› SystemFlows– TS23.502http://www.3gpp.org/DynaReport/23502.htm
› Security› Completedstudy– TR33.899http://www.3gpp.org/DynaReport/33899.htm
› Normativework– TS33.501 http://www.3gpp.org/DynaReport/33501.htm
› Operation,Orchestration› CompletedstudyNetworkSlicing– TR28.801http://www.3gpp.org/DynaReport/28801.htm
› ProvisioningofNetworkSlicing– TS28.531http://www.3gpp.org/DynaReport/28531.htm
› Protocols&APIs› CT1Study– End-2-End– TR24.890http://www.3gpp.org/DynaReport/24890.htm
› CT3Study– Interworking– TR29.890http://www.3gpp.org/DynaReport/29890.htm
› CT4Study– Core-Internal– TR29.891http://www.3gpp.org/DynaReport/29891.htm
› CT6Study– SmartCard Apps– TR31.890http://www.3gpp.org/DynaReport/31890.htm
14
15
5G– EnablerPlatformforDifferentServices
› NewStakeholders…› CriticalCommunications(MCC)
› InternetofThings(IoT)
› TactileInternet,Ultra-HDMedia
› Automotive(e.g.5GAA),Railways(e.g.UIC),Maritime
› AutonomousSystems(robots,drones,…)
› SmartCities,SmartFactories,…
› EnergyProviders,BroadcastAgencies,SatelliteOperators,…
› …requireaflexibleenablerplatform› Openupthecore– capabilityexposure
› On-demandresourceallocation– localandend-2-end
› Internalarchitectureofthecoreneedstobeservicebased
› Guaranteecertaincapabilitiesexclusively– networkslicing
› Ultralowlatency&highreliability
16
112
5GLandscape
W
H
A
A
R
R
E
D
BIGD a t a <header>
<type>web-service
</type>---
</header>…
bps
12
NB-IoT
LTE
Internet
Enterprise
3rd Party Service Providers
A P I
17
Software&ServiceCentricTransformation
› OneNetworkfitsall->Open&FlexibleEnabler
› Telecoms->MultipleStakeholders
› Phones->Things
› Procedures->Services
› Protocols->APIs
› DedicatedHardware->OrchestratedResources› NetworkFunction->Virtualization› Network->Slice
18
ArchitecturePrinciples
› ControlPlane(CP)andUserPlane(UP)separation
› Modularfunctiondesign
› DefineServicesinsteadofProcedures(re-usability)
› DirectNetworkFunctioncommunication
› AccessIndependence
› CapabilityExposure(APIs)
› UnifiedAuthenticationFramework
19
Essential3GPPCapabilities
› Mobility&Roaming
› VoiceCalls(viaIMS,i.e.SIP),SMS
› EmergencyTelecommunicationServices
› Non-3GPPAccesses(Fixed/BBF,WiFi,…)
› MobileNetworkSharing
› InterworkingwithLTE/Legacy
› 3GPPAuthenticationFramework
20
NewRAN
› NewRAN(NR)
› TS38.300– NRArchitecturehttp://www.3gpp.org/DynaReport/38300.htm
21
CP: N2UP: N3
AccessIndependence&ProtocolHarmonization
N1
22
› Functionalentities
› SingleCore
› Dedicatedprotocols
› Services
› VirtualCore
› InternalCommunication:APIs
› Harmonizedprotocols
› Function/serviceexposure
› CP/UPSeparation
TransformationoftheCoreNetworkLTE
5G
23
ServiceBasedArchitecutre
NEF Network Exposure Function
NRF Network Repository Function
PCF Policy Control Function
UDM Unified Data Management
AF Application Function
AUSF Authentication Server Function
AMF Access and Mobility Management Function
SMF Session Management Function
UE User Equipment
(R)AN (Radio) Access Network
UPF User Plane Function
DN Data Network
UE (R)AN UPF
AF
AMF SMF
PCF UDM
DNN6
N1
NRFNEF
N3
N2 N4
AUSF
Nausf Namf Nsmf
NpcfNnrfNnef Nudm Naf
NEF Network Exposure FunctionNRF Network Repository FunctionPCF Policy Control Function
UDM Unified Data ManagementAF Application Function
AUSF Authentication Server FunctionAMF Access &Mobility Management FunctionSMF Session Management Function
UE User Equipment(R)AN (Radio) Access Network
UPF User Plane FunctionDN Data Network
24
SBA– TopicsUnderDiscussion› ServiceGranularity
› Service/APIFramework
› Protocolscurrentlyunderevaluationin3GPP(CT4/CT3)
› HTTP1.1
› HTTP2/TCP+TLS
› HTTP2/QUIC
› Diameter
› …
› ThismightresultinearlycooperationwithIETF
25
NorthboundAPIs
› NEF– NetworkExposureFunction
› CoreNetworkcapabilitiesexposedto3rd parties
› Servicespecific› e.g.oneM2Mspecific(NAPS)
› Frameworkstudycurrentlyongoing(SA6)
26
5GNetworkSlicing› NetworkSlice
› Alogicalend-to-endnetwork› Dynamicallycreated› pulltogethertheresourcesyouneedtodeliverspecificservice
› Differentslicesfordifferentservicestypes› Committedserviceswithverydifferentrequirements– slicetypes› Dedicatedcustomers
› Maycomprise› 5GCoreNetwork(CP&UP)› 5GRadioAccessNetwork› InterworkingFunctionstonon-3GPPAccessNetworks
› UEconnects› Max8slicesinparallel› CommonAMFforoneUEinallslices
27
StandardSliceType(STT)Values TS23.501,section5.15.2.2-1
Slice/Service type SST value
Characteristics.
eMBB (enhanced Mobile Broadband)
1 Slice suitable for the handling of 5G enhanced Mobile broadband, useful, but not limited to the general consumer space mobile broadband applications including - streaming of High Quality Video, -Fast large file transfers etc.
It is expected this SST to aim at supporting High data rates and high traffic densities
URLLC (ultra- reliable low latency communications)
2 Supporting ultra-reliable low latency communications for applications including, - industrial automation, - (remote) control systems.
MIoT (massive IoT) 3 Allowing the support of a large number and high density of IoT devices efficiently and cost effectively.
28
ForwardCompatibility
› 5Gisdesignedtobeamodular&opensystem
› AfterR15/R16thesystemwillbefurtherimproved
› Incrementalchangeswillbepossible
› Newprotocolsandchangestothearchitecturewillbedoneinlaterreleases
› Thisisjustthebeginningof5G
29
30
IETF/3GPPCollaborationSoFar› 3GPPismakinguseofawiderangeofIETFprotocols
› IPv6,TCP,UDP› DNS,DHCP› HTTP,SIP,SDP,Diameter…
› IETFand3GPPworkedandareactivelyworkingtogetheronnumerousissues.
› IMS/SIP,SDP,RTP,XCAP,WebRTC,Telepresence/CLUE,Diameter› IPv6› Security(e.g.AKA)› ExplicitCongestionNegotiation(ECN)› RobustHeaderCompression(RHOC)
› Bothbodieshavealonghistoryofcollaboration– it’snotalwayseasy,butintheenditworks
31
Prob…Challenges› Strict3GPPReleasedeadlines(incrementalview)
› stillopenInternet-Drafts(IDs)forRel-12andearlier› 5Gdeadlinesmustnotbecrossed
› Open-endedProcessinIETF› IETFwantsfirstrequirementdrafts,thenworkonsolutionscanstart› Coststime
› Lackof3GPPparticipationinIETF
› Mostofthetechnicalissuesareend-to-end› e.g.slicing,lowlatency› involvesCT,RANandSA
32
PragmaticApproachforCollaboration› Investigatepossiblesolutionsearlytogether
› Exchangeexpertise› TeachusaboutREST,YANG,etc› HearusonSlicing,SBA,etc
› Rel-15:› collaborationwillbeconstrainedbywhatcanbeachievedby9/2018.› newideasneedtobebroughtdirectlyto3GPP
› BeyondRel-15› Workshopsondedicatedissues
33
