3GPP

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: == Market representation partners ==

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. , the market representation partners are: == Standards == 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. == Specification groups ==

The 3GPP specification work is done in Technical Specification Groups (TSGs) and Working Groups (WGs). 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. 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. == Standardization process ==

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. Specification work is done at WG and at TSG level: • 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: • 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. == See also ==