3GPP

The 3rd Generation Partnership Project initiative eventually arose from a strategic initiative between Nortel Networks and AT&T Wireless. In 1998 AT&T Wireless was operating an IS-136 (TDMA) wireless network in the United States. In 1997 Nortel Networks' Wireless R&D center in Richardson, Texas, the wireless division of Bell Northern Research had developed a vision for "an all Internet Protocol (IP)" wireless network that went under the internal name "Cell Web". As the concept progressed, Nortel launched the industry vision as "Wireless Internet". AT&T Wireless, poised to evolve its network in the United States, took a strong interest in Wireless Internet and its promise of Internet Protocol (with Nortel Networks as the potential supplier). Within 12 months or so, AT&T launched a global initiative that they named "3GIP", a third generation wireless standard that was "natively" Internet Protocol based.[6] Initially, principal participants included British Telecom, France Telecom, Telecom Italia, and Nortel Networks, but were eventually joined by NTT DoCoMo, BellSouth, Telenor, Lucent, Ericsson, Motorola, Nokia, and others.[7] A 3GIP standards forum was instituted and standards began to be developed. The forum progressed into the 2000 time frame, up until AT&T Wireless and British Telecom formed a strategic "partnership project" to facilitate "global roaming" between U.S. and European markets. With this business arrangement, GSM, the prevailing European standard was adopted as the basis of AT&T Wireless' network evolution for North America. Very specifically, this included the deployment of GSM data capabilities, i.e. GPRS, EDGE, and its evolution to UMTS.

The seven 3GPP Organizational Partners are from Asia, Europe and North America. Their aim is to determine the general policy and strategy of 3GPP and perform the following tasks:

• The approval and maintenance of the 3GPP scope;
• The maintenance of the Partnership Project Description;
• Take the decision to create or cease a Technical Specification Groups, and approve their scope and terms of reference;
• The approval of Organizational Partner funding requirements;
• The allocation of human and financial resources provided by the Organizational Partners to the Project Co-ordination Group;
• Act as a body of appeal on procedural matters referred to them.

Together with the Market Representation Partners (MRPs) perform the following tasks:

• The maintenance of the Partnership Project Agreement;
• The approval of applications for 3GPP partnership;
• Take the decision against a possible dissolution of 3GPP.

The Organizational Partners are:[8]

The 3GPP Organizational Partners can invite a Market Representation Partner to take part in 3GPP, which:

• Has the ability to offer market advice to 3GPP and to bring into 3GPP a consensus view of market requirements (e.g., services, features and functionality) falling within the 3GPP scope;
• Does not have the capability and authority to define, publish and set standards within the 3GPP scope, nationally or regionally;
• Has committed itself to all or part of the 3GPP scope;
• Has signed the Partnership Project Agreement.

As of January 2021, the Market Representation Partners are:[8]

3GPP standards are structured as Releases. Discussion of 3GPP thus frequently refers to the functionality in one release or another.

Each release incorporates hundreds of individual Technical Specification and Technical Report documents, each of which may have been through many revisions. Current 3GPP standards incorporate the latest revision of the GSM standards.

The documents are made available without charge on 3GPP's web site. The Technical Specifications cover not only the radio part ("Air Interface") and Core Network, but also billing information and speech coding down to source code level. Cryptographic aspects (such as authentication, confidentiality) are also specified.

The 3GPP specification work is done in Technical Specification Groups (TSGs) and Working Groups (WGs).[21]

There are three Technical Specifications Groups, each of which consists of multiple WGs:

• RAN (Radio Access Network): RAN specifies the UTRAN and the E-UTRAN. It is composed of six working groups.

• SA (Service and System Aspects): SA specifies the service requirements and the overall architecture of the 3GPP system. It is also responsible for the coordination of the project. SA is composed of six working groups.

• CT (Core Network and Terminals): CT specifies the core network and terminal parts of 3GPP. It includes the core network – terminal layer 3 protocols. It is composed of five working groups.

• GERAN (GSM/EDGE Radio Access Network):

The closure of GERAN was announced in January 2016.[22] The specification work on legacy GSM/EDGE system was transferred to RAN WG, RAN6. RAN6 was closed in July 2020 (https://www.3gpp.org/news-events/2128-r6_geran).

The 3GPP structure also includes a Project Coordination Group, which is the highest decision-making body. Its missions include the management of overall timeframe and work progress.

3GPP standardization work is contribution-driven. Companies ("individual members") participate through their membership to a 3GPP Organizational Partner. As of December 2020, 3GPP is composed of 719 individual members.[23]

Specification work is done at WG and at TSG level:[24]

• the 3GPP WGs hold several meetings a year. They prepare and discuss change requests against 3GPP specifications. A change request accepted at WG level is called "agreed".
• the 3GPP TSGs hold plenary meetings quarterly. The TSGs can "approve" the change requests that were agreed at WG level. Some specifications are under the direct responsibility of TSGs and therefore, change requests can also be handled at TSG level. The approved change requests are subsequently incorporated in 3GPP specifications.

3GPP follows a three-stage methodology as defined in ITU-T Recommendation I.130:[25]

• stage 1 specifications define the service requirements from the user point of view.
• stage 2 specifications define an architecture to support the service requirements.
• stage 3 specifications define an implementation of the architecture by specifying protocols in details.

Test specifications are sometimes defined as stage 4, as they follow stage 3.

Specifications are grouped into releases. A release consists of a set of internally consistent set of features and specifications.

Timeframes are defined for each release by specifying freezing dates. Once a release is frozen, only essential corrections are allowed (i.e. addition and modifications of functions are forbidden). Freezing dates are defined for each stage.

The 3GPP specifications are transposed into deliverables by the Organizational Partners.

3GPP systems are deployed across much of the established GSM market.[26][27] They are primarily Release 6 systems, but as of 2010, growing interest in HSPA+ and LTE is driving adoption of Release 7 and its successors. Since 2005, 3GPP systems were seeing deployment in the same markets as 3GPP2 systems (for example, North America[28]). With LTE the official successor to 3GPP2's CDMA systems, 3GPP-based systems will eventually become the single global mobile standard.

• List of mobile phone generations
• Universal Mobile Telecommunications System (UMTS)
• 3GPP Long Term Evolution
• Evolution to 3G
• IP Multimedia Subsystem
• 3GP
• 3GPP2 – The 3GPP's counterpart in the CDMA2000 sphere.
• GSM services
• Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN)
• Open Mobile Alliance
• Service layer
• European Telecommunications Standards Institute

• 3GPP website
• 3GPP Standards List of Acronyms & Terminology
• 3GPP freely published, detailed technical specifications
• 3GPP releases descriptions
• ETSI GSM UMTS 3GPP Numbering Cross Reference
• TS/TR
• specification numbering
• Tool for visualizing multiple inter-related 3gpp standards
• Tool for visualizing, decoding, encoding network protocol messages defined by 3gpp
• LTE-3GPP.info: online 3GPP messages decoder fully supporting Rel.15