3gpp - eustandards.ineustandards.in/wp-content/uploads/2016/11/standardization... · 3gpp seeks...
Post on 20-May-2018
217 Views
Preview:
TRANSCRIPT
© 3GPP 2016 2
Outline
Project SESEI - Seconded European Standardization Expert in India
3GPP
• Structure, Approach, Process, facts & Figures and Deliverables
Status Report
• RAN, System and Core Network Evolution and Future Plans
• IoT & 5G
3© 3GPP 2016
SESEI
Seconded European Standardization Expert in India,
Project Owner CEN, CENELEC, ETSI, EC and EFTA
Managed by ETSI
Support EU-India dialogue and cooperation on standards, R&D and Innovation, policy and regulation around standardization
Priority Sector for SESEI (3 Year until June 2019)• ICT including Services, Automotive, Electrical Equipment including
Consumer Electronics, Smart City
• Keep Track of Manufacturing, Energy Efficiency, R&D and Innovation
• EU-INDIA FTA
• Support other EU projects such as CITD, EU-INDIA on ICT standards etc.
© 3GPP 2016 4
Headlines
3GPP is expanding the LTE platform for new services and improving its efficiency to meet the growing demand of mobile broadband
At the same time 3GPP has a timeline for the standardization of next generation cellular technology, aka 5G, with the goal to address the expanded connectivity needs of the future
© 3GPP 2016 5
Organizational Partners (SDOs)
• Regional standards organizations:
Market Representative Partners
• 14 Market partners representing the broader industry:
Partnership
• 4G Americas, • COAI (India), • GSA, • GSMA, • IPV6 Forum, • MDG (formerly CDG), • NGMN Alliance,
• Small Cell Forum, • TCCA, • TD Industry Alliance, • TD-Forum, • UMTS Forum
NEW (April 2016):• GCF• CTIA
• ARIB (Japan), • ATIS (USA), • CCSA (China),
• ETSI (Europe), • TTA (Korea), • TTC (Japan), • TSDSI (India)
6© 3GPP 2016
Role of 3GPP – OP such as TSDSIThe seven 3GPP Organizational Partners - from Asia, Europe and North America - determine the general policy and strategy of 3GPP and perform the following tasks:
Approval and maintenance of the 3GPP scope;
Maintenance of the Partnership Project Description;
Taking decisions on the creation or cessation of Technical Specification Groups, and approving their scope and terms of reference;
Approval of Organizational Partner funding requirements;
Allocation of human and financial resources provided by the Organizational Partners to the Project Co-ordination Group;
Acting as a body of appeal on procedural matters referred to them.
The Organizational Partners and Market Representation Partners (MRPs) jointly perform the following tasks:
Maintenance of the Partnership Project Agreement;
Approval of applications for 3GPP partnership;
Taking decisions relating to the dissolution of 3GPP.
© 3GPP 2016 7
Developing internet protocol specs
ITU-R/TDeveloping Mobile application
specs
Referring to 3GPP specs(contributed by individual
members)
Partners of 3GPPReferring to 3GPP specs for
the local specs
Referring to specs
Cross referenceDeveloping Wireless
LAN/MAN specs
Requirements
Input specs
JapanEU Korea China North America
MarketPartners
Developing Recommendations
Terminal Certification
Terminal certification based on 3GPP specs
Cross reference of specs
The 3GPP Eco-system
India
© 3GPP 2016 8
TSG GERANGSM EDGE
Radio Access Network
GERAN WG1Radio Aspects
GERAN WG2Protocol Aspects
GERAN WG3Terminal Testing
TSG RANRadio Access Network
RAN WG1Radio Layer 1 spec
RAN WG2Radio Layer 2 spec
Radio Layer 3 RR spec
RAN WG3lub spec, lur spec, lu spec
UTRAN O&M requirements
RAN WG4Radio Performance
Protocol aspects
RAN WG5Mobile Terminal
Conformance Testing
TSG SAService & Systems Aspects
SA WG1Services
SA WG2Architecture
SA WG3Security
SA WG4Codec
SA WG5Telecom Management
TSG CTCore Network & Terminals
CT WG1MM/CC/SM (lu)
CT WG3Interworking with external networks
CT WG4MAP/GTP/BCH/SS
CT WG6Smart Card Application Aspects
Project Co-ordination Group (PCG)
SA WG6Mission-critical applications
Organizational changes…2016
© 3GPP 2016 9
GERAN WG3Terminal Testing
TSG RANRadio Access Network
RAN WG1Radio Layer 1 spec
RAN WG2Radio Layer 2 spec
Radio Layer 3 RR spec
RAN WG3lub spec, lur spec, lu spec
UTRAN O&M requirements
RAN WG4Radio Performance
Protocol aspects
RAN WG5Mobile Terminal
Conformance Testing
TSG SAService & Systems Aspects
SA WG1Services
SA WG2Architecture
SA WG3Security
SA WG4Codec
SA WG5Telecom Management
TSG CTCore Network & Terminals
CT WG1MM/CC/SM (lu)
CT WG3Interworking with external networks
CT WG4MAP/GTP/BCH/SS
CT WG6Smart Card Application Aspects
SA WG6Mission-critical applications
RAN WG6GSM EDGE
Radio Access Network
GERAN WG1Radio Aspects
GERAN WG2Protocol Aspects
Project Co-ordination Group (PCG)
TSG GERANGSM EDGE
Radio Access Network
GERAN WG1Radio Aspects
GERAN WG2Protocol Aspects
GERAN WG3Terminal Testing
Organizational changes…2016
© 3GPP 2016 10
TSG RANRadio Access Network
RAN WG1Radio Layer 1 spec
RAN WG2Radio Layer 2 spec
Radio Layer 3 RR spec
RAN WG3lub spec, lur spec, lu spec
UTRAN O&M requirements
RAN WG4Radio Performance
Protocol aspects
RAN WG5Mobile Terminal
Conformance Testing
RAN WG6GSM EDGE
Radio Access Network
TSG SAService & Systems Aspects
SA WG1Services
SA WG2Architecture
SA WG3Security
SA WG4Codec
SA WG5Telecom Management
SA WG6Mission-critical applications
TSG CTCore Network & Terminals
CT WG1MM/CC/SM (lu)
CT WG3Interworking with external networks
CT WG4MAP/GTP/BCH/SS
CT WG6Smart Card Application Aspects
Project Co-ordination Group (PCG)
Organizational changes…2016
© 3GPP 2016 11
ServicesThe Core networkRadio Interfaces
Whole System Approach
All-IP network
Improved security
Support of non-3GPP accesses
Greater device diversity
More IMS applications
Greater session continuity
Higher data throughput
Lower latency
More spectrum flexibility
Improved CAPEX and OPEX
Legacy
Interworking
© 3GPP 2016 12
3GPP Working Procedure highlights
Membership
• Open to members of 3GPP Organizational Partners
Decision making
• 1 member 1 vote
• Voting rights are earned: member added to voting list if attends 2 meetings, removed from list if he misses 3 consecutive meetings
• Proxies permitted
Access to information
• All working documents open to the public
• www.3gpp.org/ftp
• All e-mail lists open to the public
• Meeting participation restricted to 3GPP members
• Meeting documents, e-mail lists, next meeting details etc.:• http://www.3gpp.org/Specification-Groups
• 3GPP Work Plan: http://www.3gpp.org/Work-Plan
© 3GPP 2016 13
3GPP Process
Identity management
client
MCPTT-1
CSC-1
CSC-2
CSC-3
Common services core
Floorcontrol server
Floorparticipant
MCPTT-4
Group management
client
Identity management
server
Group management
server
CSC-4 Configuration management
client
Configuration management
server
Interworking function to
legacy system
IWF-1
MCPTT-3Other MCPTT server
MCPTT server
MCPTT clientMCPTT-5
Media distribution
function
MCPTT UE
Media mixer
MCPTT-7
MCPTT-8
MCPTT-6
EPS
MCPTT user database
MCPTT-2
MB2C
Rx
CSC-5
Other group management
server
CSC-7
MCPTT-9
CSC-6
Key management
client
CSC-8Key management
server
CSC-10
CSC-9
CSC-13
Stage 1:
Requirements
Stage 2:
Architecture
Stage 3:
Protocols
SA1
• Requirements normally
come from operators
(MNOs)
• High public safety
presence from Europe
and USA for Mission
Critical applications
SA6
• Mission Critical application
architecture
SA3
Security architecture and
protocols
SA2
• Overall LTE (2G, 3G etc)
system architecture
Working groups involved in Mission Critical standardisation:
CT1
• Core protocols
CT4
• Database aspects
SA3
• Security protocols
SA4
• Codec and multicast
aspects
Work is completed in Releases of typically 15 – 18 months
New specifications issued at the completion of each release
Change requests then make corrections as needed
+ RAN groups for radio
specifications
© 3GPP 2016 14
Ways of working
New work initiated by member companies via Work Items outlining scope and time plan.
Work Items prioritised if all estimated work cannot be done by the scheduled release deadline.
All 3GPP member companies contributes on equal terms on any work item
3GPP seeks consensus on all technical matters (but has mechanisms if consensus cannot be reached)
Release deadline respected, unfinished work deferred to a later release
© 3GPP 2016 15
• ~400 Companies from 39 Countries• 50.000 delegate days per year• 40.000 documents per year• 1.200 specs per Release• New Release every ~18 months
3GPP Facts and Figures
Europe
41%
Asia
38%
North
America21%
Participation by Region
© 3GPP 2016 16
Releases of 3GPP RAN specifications
‘99 ‘00 ‘01 ‘02 ‘03 ‘04 ‘05 ‘06 ‘07 ‘08 ‘09 ‘10 ‘11 ‘12 ‘13 ‘14 ‘15 ‘16
▼Release 99: W-CDMA (UMTS)
▼ Release 4: 1.28Mcps TDD
▼ Release 5: HSDPA (& IMS)
▼ Release 6: HSUPA, MBMS
▼ Release 7: HSPA+ (MIMO, Higher order modulation)
▼ Release 8: LTE (OFDMA)
▼ Release 9 LTE improvement, SON
Release 10: LTE-Advanced (Carrier Aggregation, eMIMO, eICIC) → ▼
Release 11: CoMP, E-PDCCH → ▼
Release 12: FDD/TDD CA, ProSe (D2D), eMTC → ▼
▽
• Expanding Carrier Aggregation• Narrowband IoT• Elevation Beamforming/Full-
Dimension (FD) MIMO for LTE• LAA
Release 13: LTE-Advanced Pro→
© 3GPP 2016 17
History of Major Stepsin System Architecture
R99 Rel-14Rel-13Rel-12Rel-11Rel-10Rel-9Rel-8Rel-7Rel-6Rel-5Rel-4
Initia
l 3G
PP
syste
m
arc
h b
ased o
n G
SM
IMS
EP
C
UM
TS
HS
PA
DL
HS
PA
UL
HS
PA
+
LT
E
LT
E
Ad
v
MM
Te
l
Ne
xt
Ge
ne
ration
Syste
m
C-p
lane/U
-pla
ne
split
on C
S n
etw
ork
Pro
Se
NB
-
IoT
MT
C
En
ha
nce
ments
MC
PT
T, D
EC
OR
GC
SE
Radio
Syste
m A
rchitectu
re
DECOR is Dedicated Core Networks selection mechanism
© 3GPP 2016 18
LTE evolution (Rel 14)
Large proportion of work on LTE verticals
• V2V, Broadcast, IOT, Proximity, Public Safety, etc
Work items are initiated on V2V, eLAA, eLWA, VoLTEenhancements, Mobility enhancements, Indoor positioning enhancements, MUST, FD-MIMO, eMBMSenhancements, etc.
Study items started on V2X, Latency reduction, D2D enhancements, UE to network relays for and IoT and wearables, network synchronization, etc.
© 3GPP 2016 19
UE Categories (TS 36.306)
UL Category “Approx. Throughput”
M1“1Mbps”Low complexity MTC device with narrowband + single TX
NB1(Not final)
“1Mbps”NB-IoT device
13“150Mbps” 40MHz + 64QAM
14“9.6Gbps” 640MHz + 4 layer MIMO + 64QAM
DL Category “Approx. Throughput”
M1“1Mbps”Low complexity MTC device with narrowband + single RX
NB1(Not final)
“680kbps”NB-IoT device
13“400Mbps” 20MHz + 4 layer MIMO + 256QAM 40MHz + 2 layer MIMO + 256QAM
14“4Gbps” 100MHz + 8 layer MIMO + 256QAM
15
“800Mbps” 40MHz + 4 layer MIMO + 256QAM 80MHz + 2 layer MIMO + 256QAM
“750Mbps” 50MHz + 4 layer MIMO + 64QAM 100MHz + 2 layer MIMO + 64QAM {60MHz + 2 layer MIMO + 256QAM} + {20MHz + 2 layer MIMO + 64QAM} {30MHz + 4 layer MIMO + 256QAM} + {20MHz + 2 layer MIMO + 64QAM}
16
“1Gbps” 50MHz + 4 layer MIMO + 256QAM 100MHz + 2 layer MIMO + 256QAM {40MHz + 4 layer MIMO + 256QAM} + {20MHz + 2 layer MIMO + 256QAM}
17“25Gbps” 640MHz + 8 layer MIMO + 256QAM
© 3GPP 2016 20
© All rights
reserved
3GPP on IoT Work had began from 3GPP Release 10, MTC (Machine Type
Communication), having requirements: Rel 10 feature - MTC device overload control; Rel11 feature - MTC device triggering; Rel12 feature -recall/replace device triggering, power saving mode.
In Rel. 13, 3GPP defines features such as Service exposure with 3rd party service providers features and Charged party selection. These additional Rel. features are exposed by the 3GPP architecture through its Service Capability Exposure framework.
Also for the present Release 13 (and related continuations to Release 14 when appropriate) work could include e.g.:
More on Lower latency,
More on Peak rate capacity: LAA, Carrier CA, etc
More and on Massive Connections: Narrowband IoT (NB-IoT), LTE-D
20
© 3GPP 2016 21
Standard/Global
ecosystemBand
SystemBandwidth
CoverageModule
costBattery
lifeCapacity
Time to market (years)
SigFox O Unlicensed250kHz~ ?MHz
UL 100HzGSM 14dB+ X
Lower than NB-IoTP
LoRa O Unlicensed 7.8k~500kHz GSM 18dB+ X P
EC-GSM (R13) P GSM band 2.4MHz GSM ~20dB+ 2XAbout 1/10 of
NB-IoT per unit BW
1~2
eMTC (R13) P LTE band 1.4MHz LTE 15dB+ 3~10X Similar as NB-IoT 1~2
NB-IOT (standalone) P
G/U/L MSR/dedicated
200kHz GSM 25dB+ X >50k/cell/200kHz 1~2
NB-IOT (guard-band) P LTE band 200kHz GSM 20dB+ X 1~2
NB-IOT (in-band) P LTE band 200kHz GSM 17dB+ X 1~2
Non-standard v.s. Cellular IoT
© 3GPP 2016 24
3GPP 5G Roadmap
5G RAT features will be phased as it will be not possible to standardize all in time for Rel-15 completion and early deployments
Release 15 will aim at a first phase of expected 5G deployments in 2020Release 16 will meet the ITU IMT-2020 submission requirements
Key requirement: NR design should be forward compatible at its core so that features can be added in later releases in an optimal way
© 3GPP 2016 25
5G Architectural considerations
Two radio technologies have been considered in the 5G discussions• LTE (in its Rel-15 version) aka “eLTE” in SA2
• Next generation Radio (“NR”)
Plus radio level aggregation of both radio technologies in 2 variants
Two Core Network concepts have to be considered in the 5G discussions • EPC (with potential evolutions)
• Next Generation Core (“nGcn“)
This results in 6 options (RP-161266)
© 3GPP 2016 26
Scope & Use cases
The latest plenary meeting of the 3GPP Technical Specifications Groups (TSG#72) has agreed on a detailed work plan for Release-15, the first release of 5G specifications.
3GPP TSG RAN further agreed that the target NR scope for Release 15 includes support of the following:• Standalone and Non-Standalone NR operation (with work for both starting in conjunction and
running together)
• Non-standalone NR in this context implies using LTE as control plane anchor. Standalone NR implies full control plane capability for NR.
• Some potential architecture configuration options are shown in RP-161266 for information and will be analyzed further during the study
• Target use cases: Enhanced Mobile Broadband (eMBB), as well as Low Latency and High Reliability to enable some Ultra-Reliable and Low Latency Communications (URLCC) use cases
• Frequency ranges below 6GHz and above 6GHz
The latest agreed requirements and deployment scenarios for NR can be found in TR 38.913.
© 3GPP 2016 27
RAN-SA coordination
Close coordination between RAN and SA (System Architecture group) on Next Generation Architecture is needed. 1. Radio requirements established by RAN2. Service/System requirements established by SA1/SA2 as study item
called ‘SMARTER’*
(*Study on New Services and Markets Technology Enablers)
By December 2016, RAN and SA to converge on:1) What are the goals / objectives of the Next Generation Architecture
work?2) Timing for work: e.g. what scenarios and/or architecture(s) (if there are
options) need to be developed when (by which release?)
For instance; one key decision that will have to be made by December is whether we need to support NR standalone operation in Rel-15 and, if so, for what scenarios
29© 3GPP 2016
Contact Details:
Dinesh Chand Sharma(Seconded European Standardization Expert in India)
Director – Standardization, Policy and Regulation
European Business Technology Centre, DLTA Complex, South Block, 1st Floor, 1, Africa Avenue, New Delhi 110029
Mobile: +91 9810079461, Tel: +91 11 3352 1500, dinesh.chand.sharma@eustandards.in
Thank you!
Q&A
top related