3GPP 3GPP 2017 1
Partnership Organizational Partners (SDOs) Regional standards organizations: ARIB (Japan), ATIS (USA), CCSA (China), ETSI (Europe), TTA (Korea), TTC (Japan), TSDSI (India) Market Representative Partners 17 Market partners representing the broader industry: 5G Americas, 5GIA, 5GAA, COAI (India), CTIA, GCF, GSA, GSMA, IPV6 Forum, MDG (formerly CDG), NGMN Alliance, PSC Europe, Small Cell Forum, TCCA, TD Industry Alliance, TD-Forum, Wireless Broadband Alliance 3GPP 2017 2
The 3GPP Eco-system Developing Recommendations ITU-R/T Input specs Referring to 3GPP specs (contributed by individual members) Developing Wireless LAN/MAN specs Cross reference of specs Partners of 3GPP Referring to 3GPP specs for the local specs Referring to specs Cross reference Requirements Terminal certification based on 3GPP specs Terminal Certification Developing internet protocol specs Developing Mobile application specs Market Partners EU Japan Korea China North America India 3GPP 2017 3
Organization chart 3GPP 2017 4
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 3GPP Facts and Figures ~400 Companies from 39 Countries 50.000 delegate days per year 40.000 documents per year 1.200 specs per Release 8000 New Release every ~18 months 7000 Approved CRs per year per Release 6000 5000 North America 21% Asia 38% Europe 41% 4000 3000 2000 1000 0 R99 R4 R5 R6 R7 R8 R9 R10 R11 R12 R13 R14 Participation by Region 3GPP 2017 5
3GPP Process Stage 1: Requirements Stage 2: Architecture Other MCPTT MCPTT user database Interworking function to legacy system Other group MCPTT-3 MCPTT-2 IWF-1 CSC-7 CSC-5 MCPTT Media distribution function Floor control CSC-3 Group MCPTT-5 MCPTT-6 MCPTT-7 MCPTT-8 MCPTT-1 MCPTT-4 MCPTT-9 CSC-2 Rx MB2C MCPTT UE MCPTT client Media mixer Floor participant Group client Stage 3: Protocols Work is completed in Releases of typically 15 18 months Working groups involved in Mission Critical standardisation: SA1 Requirements normally come from operators (MNOs) High public safety presence from Europe and USA for Mission Critical applications CSC-13 CSC-6 CSC-9 Configuration Identity Key Common services core CSC-10 CSC-4 CSC-1 CSC-8 EPS Configuration client Identity client Key client SA6 Mission Critical application architecture SA3 Security architecture and protocols SA2 Overall LTE (2G, 3G etc) system architecture CT1 Core protocols CT4 Database aspects SA3 Security protocols SA4 Codec and multicast aspects + RAN groups for radio specifications New specifications issued at the completion of each release Change requests then make corrections as needed 3GPP 2017 6
Membership 3GPP Working Procedure highlights 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 2017 7
Release-based work 3GPP Working Procedure highlights Releases or major packages of Features Work plan built using Features, Building Blocks and Work Tasks Work Item Description exists for each of these WI may cover more than one specification WI may cover more than one committee WI Description document exists for each WI Multiple releases maintained in parallel 3GPP WorkPlan: http://www.3gpp.org/work-plan 3GPP 2017 8
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 2017 9
Maintaining multiple releases Change Control Each release progressively frozen as it is developed Specifications pass under Change Control Rapporteur may no longer update drafts All changes managed by TSG Change Request process to introduce corrections/updates Package of CRs approved 4 times per year at TSG Plenary meeting CR database: CRs also searchable per specification via 3GPP website http://www.3gpp.org/ftp/information/databases/change_request/ CR process provides full traceability of all changes to every specification Release and CR process closely related to network equipment development and supply contracts 3GPP 2017 10