1 Requirements for European Harmonised Standards: The ETSI/3GPP relationship explainedAdrian Scrase, ETSI CTO CEPT Workshop on 5G Mobile Communications, Mainz, 2-4 November 2016 © ETSI All rights reserved

2 3GPP: Some key facts 40 000 meeting documents per yeardelegate days per year meeting documents per year change requests (CRs) per year 1 200 specifications per Release 514 Companies from 45 Countries New Release every ~18 months     Project Co-ordination Group (PCG) TSG RAN Radio Access Network RAN WG1 Radio Layer 1 spec RAN WG2 Radio Layer 2 spec Radio Layer 3 RR spec RAN WG3  lub spec, lur spec, lu spec UTRAN O&M requirements RAN WG4 Radio Performance Protocol aspects RAN WG5 Mobile Terminal Conformance Testing RAN WG6 GSM EDGE Radio Access Network TSG CT Core Network & Terminals CT WG1 MM/CC/SM (lu) CT WG3 Interworking with external networks CT WG4 MAP/GTP/BCH/SS  CT WG6 Smart Card Application Aspects TSG SA Service & Systems Aspects  SA WG1  Services SA WG2 Architecture SA WG3 Security  SA WG4 Codec SA WG5 Telecom Management SA WG6 Mission-critical applications © ETSI All rights reserved

3 3GPP and its relationship with other bodiesDeveloping internet protocol specs ITU-R/T Developing Mobile application specs Reference to 3GPP specs Partners referring to 3GPP specs for the local use Referring to specs Cross reference Requirements Japan EU Korea China North America Market Partners Developing Recommendations Terminal Certification Terminal certification based on 3GPP specs Cross reference of specs India Key takeaways 3GPP is not a legal entity as such, it is a partnership between seven SDOs 3GPP produces Technical Specifications (TSs) and Technical Reports (TRs) which are published by the Partners in their regions 3GPP does not work in isolation but incorporates result from other bodies where appropriate © ETSI All rights reserved

4 ETSI: Preparing significant 5G building blocksKey takeaways There will be many contributors to the 5G standard, it cannot all be done in one place ETSI is already developing significant building blocks which will form cornerstones of 5G 3GPP is specifying a complete 5G system description, using building blocks from other SDOs where appropriate ETSI is preparing significant 5G building blocks: Network Functions Virtualization (ISG NFV) Open Source MANO (OSG OSM) Mobile Edge Computing (ISG MEC) Millimetre Wave Transmission (ISG wWT) Next Generation Protocols (ISG NGP) Mobile/Broadcast Convergence (ISG MBC) ..as well as existing activities, e.g.: Use of whitespace spectrum, Spectrum Sharing (licensed and unlicensed) (TC RRS) Quantum Safe Cryptology (ISG QSC) Energy Efficiency (TC EE) Use of Satellites in 5G (TC SES) …and many more © ETSI All rights reserved

5 The three high level 5G use case familiesEnhanced Mobile Broadband Massive Machine Type Communications Ultra Reliable and Low Latency Communications Source: ITU-R © ETSI All rights reserved

6 Performance RequirementsKey takeaways To meet these requirements, 3GPP will specify: a new radio interface (NR) an evolved LTE radio interface a new core network (NextGen) An evolved LTE core network (EPC) Use Case order of priority: First: Enhanced Mobile Broadband and some Ultra Reliable/Low Latency functionality Later: Massive Machine Type communications and more comprehensive Ultra Reliable/Low Latency functionality Enhancement of key capabilities from IMT-Advanced to IMT-2020 The importance of key capabilities in different usage scenarios Source: ITU-R M.2083 © ETSI All rights reserved

7 When will 5G be ready? 2020 is the headline date for 5GThis date has been chosen more for political rather than technical reasons It is also happens to coincide with the Olympic Games in Japan, July 2020 However, there is a push to bring the date forward because of: Mobile Operator rush “to be the first” Winter Olympic Games to be held in Korea, February 2018 Rugby World Cup to be held in Japan, September 2019 5G Open Trial Specification Alliance formed by SK Telecom, KT, NTT DoCoMo and Verizon: To speed up deployment To meet the early deployment objective © ETSI All rights reserved

8 Radio Equipment DirectiveRadio Equipment Directive (RED) Replaces Radio & Telecommunication Terminal Equipment Directive (RTTED) 1999/5/EC Covers equipment which intentionally transmits or receives radio waves for communications or radio determination, regardless of primary function Operating up to 3000 GHz (NB: no lower frequency limit) LVD & EMCD will no longer apply to RED equipment Many products under the scope of RED: e.g. anything with a GPS, Bluetooth, RFID, RLAN, NFC…. RED to be applied from 13 June 2016 (+ 1 year for manufacturers to comply) Key takeaways All 5G radio products (not just those derived from 3GPP specifications) placed on the European market will need to comply with the Radio Equipment Directive Requirements include both transmitter and receiver characteristics © ETSI All rights reserved

9 Use of Harmonised StandardsA manufacturer can demonstrate meeting the RED essential requirements by applying ETSI Harmonised Standards Mandate under RED Harmonised Standards © ETSI All rights reserved

10 ETSI Technical Committee “Mobile Standards Group” (TC MSG)MSG is responsible for: addressing issues relating to the transposition of 3GPP Technical Specifications and Technical Reports into ETSI Deliverables (noting that the transposition is performed by the ETSI Secretariat and is normally done without direct involvement of ETSI MSG) the development of Harmonised Standards covering essential requirements under the Radio Equipment Directive and related ETSI deliverables for GSM, IMT systems and technologies evolving therefrom. Close liaison should be maintained with 3GPP, 3GPP2, IEEE and WiMAX Forum as well as related ETSI bodies which might be affected by the deliverables made by MSG  TFES (Joint TC MSG/TC ERM Task Force) is responsible for:   developing European Norms (ENs) intended to become Harmonised Standards under the Radio Equipment Directive, for members of the IMT family organizing its work to ensure that, as far as possible, Harmonised Standards are available to meet market needs and timescales for placing on the market and putting into service of IMT equipment within the European Community. © ETSI All rights reserved

11 The ETSI and 3GPP relationshipEMC and Radio Spectrum Matters (ERM) Mobile Standards Group (MSG) Joint ERM/MSG Task Force (TFES) TSG Radio Access Network (RAN) ETSI Technical Committees ETSI Partnership Project 3GPP Key takeaways ETSI TFES prepares draft Harmonised Standards derived from specifications produced in 3GPP RAN To do so, it is imperative that Members active in 3GPP engage in this work More active engagement of Administrations is encouraged Work items in TFES are created by ETSI Members who are also active in 3GPP TFES is dependent on those ETSI Members to provide the intellect needed to draft the Harmonised Standards Historically, ETSI Administrations have been conspicuous by their absence in this work © ETSI All rights reserved

12 TFES Working Methods The TFES task force:uses the ECC/ETSI MoU under which ETSI Members co-operate with ECC Administrations to ensure that Harmonised Standards are aligned in terms of content and timing bases its work on the relevant EC and ECC Decisions on the IMT bands and any additional guidance from ECC and ERC Recommendation 74/01E on Spurious Emissions takes into account the continuing development of the IMT family. In particular, it bases its work on the most recent versions of the specifications of the SDOs that are referenced in ITU-R Recommendation M.1457 develops Harmonised Standards in a modular structure with common/generic parts and specific parts. The structure is a trade-off between minimising duplication of content and enabling completed parts of the work to proceed to EN Approval Procedure (ENAP) in a timely manner liaises with other organizations such as 3GPP and ITU/R WP5D, SDOs. The normal method of liaison will be through individual members. © ETSI All rights reserved

13 What if the source specifications are incomplete or inadequate?Key takeaways ETSI TFES: Prepares draft Harmonised Standards derived from source specifications produced by external SDOs May propose modifications to the source specifications if needed Is responsible to ensure that Harmonised Standards are fit for purpose In the unlikely case that the source specifications (e.g., those produced by 3GPP) are incomplete or inadequate, TFES may recommend modifications to those source specifications If such modifications are not implemented, TFES may: Modify the ETSI transposed versions of the source specifications Add/modify the content of the Harmonised Standards to take account of European needs/requirements Ultimately, ETSI is responsible (and therefore empowered) to ensure that Harmonised Standards are fit for purpose © ETSI All rights reserved

14 What should be included in the Harmonised Standard?ETSI has published a Guide which explains the recommended contents and structure of Harmonised Standards for the Radio Equipment Directive (EG ): 5 Technical parameters for article 3.2 of Directive 2014/53/EU 5.1 General 5.2 Transmitter parameters under article 3.2 of Directive 2014/53/EU 5.3 Receiver parameters under article 3.2 5.4 Protocol elements, interference mitigation techniques and type of modulation 5.5 Antennas 6 Technical parameters for article 3.1(b) (EMC) of Directive 2014/53/EU 6.1 General 6.2 Combined equipment within the scope of Directive 2014/53/EU 7 Structure of Harmonised Standards 7.1 General 7.2 Methods of Measurement 7.3 Scope Annex A: Harmonised Standard Skeleton Document Annex B: Principles of the difference between radio and EMC requirements Annex C: Bibliography © ETSI All rights reserved

15 The EN Approval Process (simplified)ETSI Harmonised Standards are produced using the EN Approval Process (ENAP) Selection of relevant 3GPP requirements into HS NSO Public Enquiry & National Vote No Comments + Successful Vote TB Resolution NSO Voting Publication Comments Submitted © ETSI All rights reserved

16 The EN Approval ProcessIt takes a minimum of 144 days from the completion of a draft HS to publication if no technical comments are received, or 294 days if technical comments are received The HS then needs to be cited in the Official Journal of the EU which can take several weeks too © ETSI All rights reserved

17 What if Harmonised Standards are not cited in time?If the Harmonised Standards for 5G are not cited in the OJ in time: Draft standards on ENAP can be used by manufacturers as the basis of a technical file submitted to a Notified Body EG (Guide to selection of technical parameters for Harmonised Standards) can be used if no public draft exists Can also be used by Notified Bodies and enforcement authorities as a technical basis for assessment Key takeaways It takes roughly one year to draft, approve and publish a Harmonised Standard and for it to be cited in the Official Journal of the EU Harmonised Standards may be the most practical way to demonstrate compliance with the Radio Equipment Directive, but not the only way © ETSI All rights reserved

18 Conclusions 3GPP is preparing a complete 5G system description, for early implementation in 2018 and full implementation in 2020 ETSI is preparing significant building blocks which will form 5G cornerstones ETSI MSG/TFES will prepare Harmonised Standards to assist industry in demonstrating compliance with the Radio Equipment Directive It takes roughly one year from beginning to end to produce a Harmonised Standard and requires engagement from industry and administrations This is an iterative process, repeated periodically as the 3GPP system evolves, and usually synchronised with updates to related ITU IMT recommendations Industry must anticipate the time when they wish to place 5G radio products on the European market and plan accordingly © ETSI All rights reserved

19 Contact Details: [email protected]Thank you! © ETSI All rights reserved